Information processing device, information processing method, and program

Abstract

Provide appropriate information regarding the subject matter. [Solution] When a user accesses the system, the system determines the user class corresponding to the user from among a predetermined number of user classes, generates the first information corresponding to the determined user class based on second information that defines the first information that can be provided to users belonging to a predetermined user class, and provides the generated first information to the user.

Description

Technical Field

[0001] The present invention relates to an apparatus for providing information.

Background Art

[0002] There is a technology for managing a supply chain involving multiple companies. In this regard, Patent Document 1 discloses a system for sharing information on traded goods between vendor companies and customer companies.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The present disclosure aims to appropriately provide information regarding an object.

Means for Solving the Problems

[0005] One aspect of an embodiment of the present disclosure is an information processing apparatus that provides a user with first information regarding a predetermined object generated based on one or more data regarding the predetermined object, the information processing apparatus including: a storage unit that stores the one or more data, user data that defines a user who accesses the information processing apparatus in association with a user class, and second information that defines the first information that can be provided to a user belonging to a predetermined user class; a control unit that, when there is an access from a user, determines the user class corresponding to the user based on the user data, generates the first information corresponding to the determined user class based on the second information, and outputs the generated first information to the terminal of the user.

[0006] One embodiment of the present disclosure is: An information processing device that provides a user with first information relating to a predetermined object, generated based on one or more data relating to the predetermined object, and having a control unit that, when accessed by a user, determines a user class corresponding to the user from among a plurality of predefined user classes, generates the first information corresponding to the determined user class based on second information that defines the first information that can be provided to users belonging to the predetermined user class, and provides the generated first information to the user.

[0007] One embodiment of the present disclosure is: An information processing method performed by an information processing device that provides a user with first information about a predetermined object, generated based on one or more data points relating to the predetermined object, the method includes: determining a user class corresponding to a user from among a plurality of predefined user classes when accessed by a user; generating the first information corresponding to the determined user class based on second information defining the first information that can be provided to users belonging to the predetermined user class; and providing the generated first information to the user.

[0008] Furthermore, in other embodiments, a program for causing a computer to execute the above method, Alternatively, a computer-readable storage medium in which the program is stored non-temporarily may be used. [Effects of the Invention]

[0009] This disclosure allows for the appropriate provision of information regarding the subject matter. [Brief explanation of the drawing]

[0010] [Figure 1] A schematic diagram of the information processing system according to the first embodiment. [Figure 2]Figure showing the types of data generated for a vehicle battery. [Figure 3] Figure showing an overview of the processing performed between the terminal (vehicle server) and the management server. [Figure 4] Figure showing an overview of the processing performed between the terminal (vehicle server) and the management server. [Figure 5] Hardware configuration diagram of the management server according to the first embodiment. [Figure 6] Hardware configuration diagram of the terminal according to the first embodiment. [Figure 7] Hardware configuration diagram of the vehicle server according to the first embodiment. [Figure 8] Software configuration diagram of the management server according to the first embodiment. [Figure 9] Figure showing an example of data stored in the user management DB. [Figure 10] Figure showing an example of data stored in the battery information DB. [Figure 11] Figure showing an example of data stored in the provided information DB. [Figure 12] Software configuration diagram of the terminal according to the first embodiment. [Figure 13] Software configuration diagram of the vehicle server according to the first embodiment. [Figure 14A] An example of a dashboard screen provided to the user. [Figure 14B] An example of a dashboard screen provided to the user. [Figure 15] An example of a model data screen provided to the user. [Figure 16] An example of a BIN data screen provided to the user. [Figure 17] Flowchart of the processing executed by the management server. [Figure 18] Sequence diagram of the processing between the management server and the terminal.

Modes for Carrying Out the Invention

[0012] On the other hand, as electric vehicles become more popular, the management of information regarding the installed drive battery (hereinafter simply referred to as the battery or vehicle battery) becomes important. For example, it is predicted that as electric vehicles become more popular, the business of removing and trading batteries from used vehicles will become active. However, if the batteries of used vehicles are not recycled properly, they may harm the environment. Also, if the state (performance, etc.) of the battery cannot be grasped, an appropriate evaluation of the used vehicle cannot be performed.

[0013] Therefore, the construction of a platform for unified management of information regarding batteries for electric vehicles is being considered. In the life cycle of vehicle batteries, various businesses are involved, such as battery manufacturers, vehicle manufacturers, used vehicle dealers, battery dismantlers, and battery recyclers. By collecting information from these businesses, managing it centrally, and providing it appropriately, the value of the battery and electric vehicle can be increased, and troubles such as ignition accidents can be prevented.

[0014] On the other hand, when collecting information from multiple businesses and managing it centrally, appropriate access rights must be granted. This is because the information regarding vehicle batteries includes design information, personal information of vehicle users, and information related to privacy regarding movement, so it is not preferable to provide these to multiple businesses related to vehicle batteries without restrictions.

[0015] Furthermore, when providing information to multiple businesses, the design of the user interface screen becomes an issue. Since the stages in which multiple businesses are involved in the life cycle of the battery may differ, the user interface screens provided to each business may also be separate, but it is not practical to define user interface screens for each business that the user logs in to. The information processing device disclosed herein solves such problems.

[0016] An information processing device relating to one aspect of this disclosure is: An information processing device that provides a user with first information about a predetermined object, generated based on one or more data points relating to the predetermined object, and includes a control unit that, when accessed by a user, determines a user class corresponding to the user from among a plurality of predefined user classes, generates the first information corresponding to the determined user class based on second information that defines the first information that can be provided to users belonging to the predetermined user class, and provides the generated first information to the user.

[0017] A specified item is an item in which multiple businesses are involved throughout its lifecycle, including manufacturing, distribution, and recycling. A typical example of a specified item is a drive battery designed for electric vehicles. In addition to manufacturing and distribution, many businesses are involved in the process of removing drive batteries from used vehicles, dismantling them, refining them, rebuilding them, re-installing them in vehicles, installing them in non-vehicle applications, and recycling them.

[0018] An information processing device is configured to store or acquire one or more pieces of data relating to a predetermined object. For example, if the object is a vehicle battery, during the battery manufacturing phase, such information may include information on carbon footprint (CFP), recycling rate, due diligence (DD), and specifications. During the vehicle manufacturing phase, information such as vehicle model information, design information, and information on the CFP and DD met may be generated. During the battery removal phase, information regarding dismantling companies, dismantling sites, battery transfer destinations, and transportation companies may be generated. The information processing device centrally manages data related to an object that may be generated throughout the object's lifecycle. This data is collected from multiple businesses, users, devices, etc.

[0019] Based on such data, the control unit generates primary information about the object and provides it to multiple users. Each of these users may be an end-user who owns an electric vehicle, or a business involved in the manufacturing, distribution, dismantling, or recycling of batteries.

[0020] When a user accesses the system, the control unit determines the user class corresponding to the user from among a predefined group of user classes. A user class is defined based on the user's attributes, such as the user's role with respect to the object (e.g., manufacturer, distributor, recycler, etc.) or their scope of responsibility (e.g., which manufacturer they belong to). Furthermore, the control unit generates first information corresponding to the determined user class based on the second information. The second information defines the first information that can be provided to users belonging to a given user class. The second information may, for example, define the design of the screens provided to users belonging to each user class, and the first information that can be provided to each user belonging to each user class through each screen.

[0021] In this way, the second information allows for the description of a user interface screen and the information provided by that user interface screen for each user class. The second information may also include the logic for generating the first information using one or more of the aforementioned data.

[0022] The following describes specific embodiments of this disclosure with reference to the drawings. Unless otherwise specified, the hardware configurations, module configurations, functional configurations, etc., described in each embodiment are not intended to limit the technical scope of the disclosure to those configurations alone.

[0023] (First embodiment) The information processing system according to this embodiment is a system for managing information related to vehicle batteries designed for electric vehicles. Figure 1 is a schematic diagram of the information processing system according to this embodiment. The information processing system according to this embodiment consists of a management server 1, one or more terminals 2, and one or more vehicle servers 3.

[0024] Management Server 1 is a server device that manages information related to the target vehicle battery. Management Server 1 obtains and centrally manages information about the battery from multiple users involved in the vehicle battery's lifecycle. It also provides information about the battery to these users upon request.

[0025] Terminal 2 is a terminal device used by multiple users involved with a vehicle battery throughout its lifecycle. These multiple users include the vehicle owner (end-user) and various businesses. These businesses are involved in the manufacturing, distribution, and recycling of batteries, and include, for example, vehicle manufacturers, battery manufacturers, battery collection businesses, used car dealers, and battery recycling businesses. Terminal 2 provides information about the battery to and receives information from Management Server 1.

[0026] Management Server 1 can collect information about the batteries under its management not only from the operators but also from the vehicles in which the batteries are installed. For example, in order to estimate the state of a battery, information about the vehicle's operation (hereinafter referred to as vehicle operation information), such as voltage, current, temperature, and charging frequency, may be required. Vehicle Server 3 communicates with multiple vehicles 10, collects vehicle operation information from the multiple vehicles 10, and provides it to Management Server 1. This enables Management Server 1 to collect real-time data about the batteries installed in the vehicles. The vehicle server 3 may relay the vehicle driving information to the management server 1 without processing it, or it may perform predetermined calculation processing on the collected vehicle driving information before sending it to the management server 1.

[0027] Next, we will describe the multiple stages included in the vehicle battery lifecycle and the multiple users involved in each stage. Figure 2 illustrates the multiple stages included in the lifecycle of a vehicle battery and the types of data (information types) generated at each stage.

[0028] For example, in the stage of manufacturing vehicle batteries, information such as greenhouse gases (carbon footprint (also known as CFP)), information representing the recycling rate of raw materials, and information regarding responsibility in raw material procurement (due diligence (also known as DD)) may be generated by the battery manufacturer. Furthermore, in the vehicle manufacturing stage, vehicle model information and the CFP used are used. Information regarding rules, DD rules, and compliance with regulations may be generated by vehicle manufacturers.

[0029] Furthermore, in the stage where newly sold vehicles are used, information related to vehicle sales, vehicle driving data, customer information, and battery status information may be generated. Examples of battery status information include battery capacity (SoCE, State of Certified Energy), battery safety level (SoS, State of Safety), and battery health level (SoH, State of Health). This information is obtained from the vehicle. It can be calculated based on (voltage value, current value, temperature, charging frequency, etc.).

[0030] Furthermore, in the stage where used vehicles are resold, vehicle information, vehicle history information (mileage, repair history, etc.), sales price information, battery performance information at the time of resale, and transfer certificates may be generated by used car dealers, etc. Furthermore, at the stage when a vehicle is dismantled, information such as vehicle information, dismantling company location information, dismantling company information, transportation information, and waste battery collection information may be generated by the vehicle dismantling company, etc. Furthermore, in the stage of reusing batteries removed from scrapped vehicles, battery model information, battery diagnostic results, CFP information, battery transfer certificates, and recycling process information may be generated by battery recycling companies, etc.

[0031] The management server 1 according to this embodiment collects and centrally manages this type of information from each operator's terminal 2 or vehicle 10 (vehicle server 3). It also processes and provides this information upon request from operators and end users.

[0032] In this embodiment, businesses that perform a predetermined role at each stage are referred to as "actors." Examples of actors include "battery manufacturers," "vehicle manufacturers," "vehicle dismantling businesses," and "battery recycling businesses."

[0033] Next, we will describe the process by which management server 1 collects information. Figure 3 is a diagram illustrating the overview of the information collection process that takes place between terminal 2 or vehicle server 3 and management server 1.

[0034] In this example, a single vehicle server 3 periodically acquires information (voltage, current, temperature, charging frequency, etc.) from multiple vehicles 10 under its management to calculate battery status, and periodically transmits this information to the management server 1. Furthermore, at each stage, terminals 2 owned by businesses involved in the manufacturing, distribution, and recycling of batteries provide information handled by their respective companies to the management server 1. The timing of providing the information may be at any time. For example, a battery manufacturer may provide the information when the target battery is completed. Similarly, a battery dismantling company may provide the information when the dismantling of the target battery is completed. If there are multiple operators, the system may include multiple terminals 2. Information transmitted from each of the terminals 2 and the vehicle server 3 is stored in a database on the management server 1.

[0035] Next, we will describe the overview of the process by which the management server 1 provides information. Figure 3 is a diagram illustrating the overview of the information provision process that takes place between terminal 2 or vehicle server 3 and management server 1.

[0036] In this example, multiple terminals 2 can receive information from the management server 1. The terminals 2 that receive the information are terminals owned by end users (for example, vehicle owners). It may be a device owned by the service provider, or it may be a device owned by the service provider. End users can obtain information about the battery of their vehicle via terminal 2. For example, by accessing management server 1 via terminal 2, end users can check the certified energy (capacity) (SoCE) and safety status (SoS) of the battery installed in their vehicle.

[0037] On the other hand, a business operator can obtain information about the batteries they handle via terminal 2, within the scope of the access permissions set for them. For example, if the target business operator is a vehicle manufacturer and is authorized to access battery information for its own vehicles, that business operator can obtain battery information for its own vehicles. However, if access to private information such as vehicle location information is not authorized, this information may be excluded from the information provided.

[0038] Furthermore, in this embodiment, access rights are differentiated depending on whether the business operator is a competent business operator or not. A competent business operator refers to a business operator that has management responsibility for the batteries it has manufactured. In this specification, other businesses are referred to as general businesses. A competent business operator may, for example, be a business operator responsible for supervising to prevent the illegal dumping of the batteries in question, or a business operator responsible for monitoring the safety status of the batteries in question.

[0039] If the business operator is the responsible operator, in addition to the above-mentioned rights, they will be granted access to information related to their management responsibility for the batteries in question. For example, if the business operator is responsible for supervising to prevent the illegal dumping of batteries, they will be granted access to information for tracking the location of the batteries (e.g., transfer certificates and disposal certificates generated at each stage). Furthermore, if the business operator is responsible for monitoring the safety status of the batteries, they will be granted access to information obtained by diagnosing the safety status of the batteries (e.g., information on internal resistance values, abnormal capacity values, and physical damage).

[0040] [Hardware configuration] Next, we will describe the hardware configuration of each device that makes up the system. Figure 5 is a schematic diagram showing an example of the hardware configuration of the management server 1 according to this embodiment. The management server 1 is configured as a computer having a control unit 11, a storage unit 12, a communication module 13, and an input / output device 14.

[0041] Management Server 1 can be configured as a computer having a processor such as a CPU or GPU, main memory such as RAM or ROM, and auxiliary storage such as EPROM, hard disk drive, or removable media. The auxiliary storage contains an operating system (OS), various programs, various tables, etc., and by executing the programs stored therein, various functions that match the predetermined purpose, as described later, can be realized. However, some or all of the functions may be realized by hardware circuits such as ASICs or FPGAs.

[0042] The control unit 11 is a computing unit that realizes various functions of the management server 1 by executing a predetermined program. The control unit 11 can be implemented by a hardware processor such as a CPU. The control unit 11 may also be configured to include RAM, ROM (Read Only Memory), cache memory, etc.

[0043] The memory unit 12 is a means for storing information and is composed of storage media such as RAM, magnetic disks, and flash memory. The memory unit 102 stores programs executed by the control unit 11, data used by those programs, and so on. Furthermore, a database is constructed in the memory unit 12, and multiple Battery information collected from terminal 2 (or vehicle server 3) is stored. Further details will be provided later.

[0044] The communication module 13 is a communication interface for connecting the management server 1 to the network. The communication module 13 consists of, for example, a network interface board and a wireless communication interface for wireless communication. The management server 1 can communicate data with other computers (for example, each terminal 2) via the communication module 13.

[0045] The input / output device 14 is a means of receiving input operations performed by the operator and presenting information to the operator. Specifically, the input / output device 14 includes devices for input such as a mouse and keyboard, and devices for output such as a display and speakers. The input / output device may be integrated with, for example, a touch panel display.

[0046] The specific hardware configuration of the management server 1 can be appropriately omitted, replaced, and added depending on the embodiment. For example, the control unit 11 may include multiple hardware processors. The hardware processors may consist of microprocessors, FPGAs, GPUs, etc. The input / output device 14 may be omitted, or input / output devices other than those exemplified (e.g., optical drives) may be added. Furthermore, the management server 1 may be composed of multiple computers. In this case, the hardware configurations of each computer may or may not be the same.

[0047] Figure 6 is a schematic diagram showing an example of the hardware configuration of terminal 2 according to this embodiment. Terminal 2 is configured as a computer having a control unit 21, a storage unit 22, a communication module 23, and an input / output device 24.

[0048] Terminal 2, like management server 1, can be configured as a computer having a processor such as a CPU or GPU, main memory such as RAM or ROM, and auxiliary storage such as EPROM, hard disk drive, or removable media. However, some or all of its functions may be implemented by hardware circuits such as ASICs or FPGAs.

[0049] The control unit 21 is a processing unit that realizes various functions of terminal 2 by executing a predetermined program. The control unit 11 can be realized by a hardware processor such as a CPU. The control unit 21 may also be configured to include RAM, ROM (Read Only Memory), cache memory, etc.

[0050] The memory unit 22 is a means for storing information and is composed of storage media such as RAM, magnetic disks, and flash memory. The memory unit 22 stores programs executed by the control unit 21, data used by those programs, and so on.

[0051] The communication module 23 is a communication interface for connecting terminal 2 to the network. The communication module 23 consists of, for example, a network interface board and a wireless communication interface for wireless communication. Terminal 2 can communicate data with other computers (for example, management server 1) via the communication module 23.

[0052] The input / output device 24 is a means of receiving input operations performed by the operator and presenting information to the operator. Specifically, the input / output device 24 includes devices for input such as a mouse and keyboard, and devices for output such as a display and speakers. The input / output device may be integrated with, for example, a touch panel display.

[0053] Furthermore, the specific hardware configuration of terminal 2 can be modified as appropriate, depending on the embodiment, by omitting, substituting, or adding components, similar to the management server 1.

[0054] Figure 7 is a schematic diagram showing an example of the hardware configuration of the vehicle server 3 according to this embodiment. The vehicle server 3 is configured as a computer having a control unit 31, a storage unit 32, and a communication module 33.

[0055] Vehicle server 3, like management server 1, can be configured as a computer having a processor such as a CPU or GPU, main memory such as RAM or ROM, and auxiliary storage such as EPROM, hard disk drive, or removable media. However, some or all of its functions may be implemented by hardware circuits such as ASICs or FPGAs.

[0056] The control unit 31 is a computing unit that realizes various functions of the vehicle server 3 by executing a predetermined program. The control unit 31 can be implemented by a hardware processor such as a CPU. The control unit 31 may also be configured to include RAM, ROM (Read Only Memory), cache memory, etc.

[0057] The memory unit 32 is a means for storing information and is composed of storage media such as RAM, magnetic disks, and flash memory. The memory unit 32 stores programs executed by the control unit 31, data used by those programs, and so on.

[0058] The communication module 33 is a communication interface for connecting the vehicle server 3 to a network. The communication module 33 is comprised of, for example, a network interface board and a wireless communication interface for wireless communication. The vehicle server 3 can communicate data with other computers (for example, the management server 1 or an in-vehicle device installed in the vehicle 10) via the communication module 33.

[0059] Furthermore, the specific hardware configuration of the vehicle server 3 can be modified as appropriate, depending on the embodiment, by omitting, substituting, or adding components, similar to the management server 1.

[0060] [Software Configuration] Next, we will describe the software configuration of each device that makes up the system. Figure 8 is a schematic diagram showing the software configuration of the management server 1 according to this embodiment. In this embodiment, the control unit 11 is configured to have three functional modules: a user authentication unit 111, an information acquisition unit 112, and an information provision unit 113. Each functional module may be implemented by the control unit 11 (CPU) executing a program stored in the storage unit 12.

[0061] The user authentication unit 111 authenticates users who attempt to log in to the device. The data collected and provided by management server 1 may vary depending on the type of user using terminal 2, or which stage, as illustrated in Figure 2, the user using terminal 2 belongs to. For example, users of the management server 1 can be classified into multiple actors, such as "vehicle users (end users)," "vehicle manufacturers," "battery manufacturers," "vehicle sales companies," "vehicle dismantling companies," and "battery distributors." In this embodiment, these classification results are referred to as "actor classes." Furthermore, even the same actor can be further classified into multiple attributes depending on the vehicle or battery manufacturer, etc. In this embodiment, these classification results are referred to as "user classes." The management server 1 provides user interface screens, Each actor class and user class is associated with a specific screen, and the appropriate screen is provided to terminal 2.

[0062] The user authentication unit 111 may perform user authentication itself, or it may obtain the results of user authentication performed by another system or device. For example, if there are multiple businesses that handle batteries and user authentication is performed on a business-by-business basis, the user authentication unit 111 may obtain the results of user authentication from an authentication server provided for each business. Furthermore, the user authentication unit 111 uses the user authentication database (user-related DB) built in the storage unit 12 to determine the actor class and user class of the user who accessed the system. In this embodiment, each operator logs in to the management server 1 via terminal 2 using the corresponding operator's account, thereby enabling interaction between the management server 1 and terminal 2.

[0063] Figure 9 is a diagram illustrating the user-related database. In this embodiment, the user-related database consists of class data and user data. User data is data that defines individual users, and class data is data that defines actor classes and user classes. As shown in the diagram, in this embodiment, multiple actor classes are defined, such as "end user," "vehicle manufacturer," "battery manufacturer," and "vehicle dealer."

[0064] Each actor class is associated with a user class. A user class is a further subdivision of an actor class into multiple attributes, such as manufacturer. In the illustrated example, a logged-in user might be classified into user classes such as "Vehicle Manufacturer of Automobile A" or "Vehicle Manufacturer of Automobile B".

[0065] Each user class has multiple users associated with it. If the user class is "end user," the user data may include information that identifies the vehicle and battery owned by the user.

[0066] The information acquisition unit 112 acquires battery-related information from the terminal 2 or vehicle server 3 and stores this information in a database (battery information DB) located within the storage unit 12. Hereafter, the information stored in the battery information DB will be referred to as "battery information". Battery information is, for example, one of the multiple types of information exemplified in Figure 2.

[0067] The information acquisition unit 112 acquires battery-related data (battery information) from the business operator or end user. If the data provider is a business operator, the information acquisition unit 112 generates a user interface screen for the terminal 2 used by the business operator to input the data to be collected, and acquires the data entered through the user interface screen. The user interface screen provided to terminal 2 is determined based on the actor class determined by the user authentication unit 111.

[0068] For example, for a user whose actor class is "battery manufacturer," the information acquisition unit 112 provides a user interface screen for inputting information such as the carbon footprint of the manufactured batteries, recycling information, and due diligence information. Furthermore, for users whose actor class is "battery distributor," the information acquisition unit 112 provides a user interface screen for inputting information such as the carbon footprint of the target battery, information about the battery model, battery diagnostic results, and information about the battery transfer certificate. The information acquisition unit 112 generates a different user interface screen for each actor class and provides it to the terminal 2. The user on terminal 2 inputs the information to be provided to the management server 1 via this user interface screen.

[0069] In some cases, the information provider may be the end user, not the service provider. For example, if the vehicle's end user has given prior consent to the provision of information for battery monitoring, the information acquired by the vehicle is transmitted to the information acquisition unit 112 via the vehicle server 3. In this case, the user interface screen is not used. For example, the vehicle sends information indicating the battery's SoC (State of Charge) to the management server 1. It can be transmitted. The information transmitted from the vehicle may be processed by management server 1 or vehicle server 3. For example, management server 1 (vehicle server 3) may acquire information indicating the target vehicle's driving load, current value, voltage value, SoC change rate, etc., and management server 1 (vehicle server 3) may calculate the target vehicle's SoCE (State of Certified Energy) based on this information. It may be provided. The logic for calculation may be pre-stored or provided by the service provider as part of the battery information.

[0070] Next, we will explain the details of the data acquired by the information acquisition unit 112. Figure 10 shows an example of battery information stored in the battery information database. As mentioned above, the information acquisition unit 112 collects multiple types of information from users belonging to multiple actor classes and user classes, respectively, and stores them in the battery information database. For example, the information acquisition unit 112 acquires information on the carbon footprint (CFP) of batteries from users belonging to the actor class "battery manufacturer" or "battery distributor," and stores it in the battery information database as information of type "CFP information."

[0071] Each piece of data stored in the battery information database is granted a different type of access permission. Access permissions will be explained later.

[0072] In this example, the information acquisition unit 112 acquires information from terminal 2 or vehicle server 3, but the sources of information acquisition are not limited to these. For example, if management server 1 is connected to another system that oversees businesses involved in battery manufacturing and distribution, battery information may be acquired from that other system.

[0073] The information provision unit 113, based on a request from terminal 2, extracts battery information stored in the battery information DB and performs the process of providing it to terminal 2. As described above, in this embodiment, the management server 1 classifies users of terminal 2 into multiple actor classes and user classes. The information provision unit 113, like the information acquisition unit 112, also provides terminal 2 with a different user interface screen for each actor class. Users of terminal 2 can receive battery information through the user interface screen provided by the information provision unit 113.

[0074] The information provision unit 113 may provide the battery information stored in the battery information DB to the terminal 2 as is, or it may process or perform calculations on the battery information before providing it to the terminal 2. The processed or calculated information may also be referred to as "battery information" in this specification.

[0075] In this embodiment, the management server 1 stores data (provided information DB) that defines what information to provide to users belonging to which actor class / user class, and the information provision unit 113 generates a user interface screen for providing battery information based on this data.

[0076] Figure 11 shows an example of information stored in the provided information database. The provided information database defines the information that can be provided to users belonging to specific actor classes and user classes, on a screen-by-screen basis. In the illustrated example, it is defined that three screens can be provided to a user belonging to the actor class "Vehicle Manufacturer (A002)": "Recycling Status," "Battery Collection and Storage Status," and "Battery Information Awaiting Collection (by Prefecture)." Furthermore, the design data for generating these screens and the logic (data used and calculation methods) for generating the information provided through these screens are defined.

[0077] In the illustrated example, if the user's actor class is the same, the design of the provided screen will also be the same. However, if the user's actor class is different, the design of the provided screen may also be different. This allows for different information to be provided to users belonging to one actor class compared to users belonging to a different actor class. For example, it becomes possible to provide different information to a user belonging to the actor class with the ID "A002" compared to a user belonging to the actor class with the ID "A003". Furthermore, it becomes possible to, for example, not provide some of the information provided to a user belonging to the actor class with the ID "A002" to a user belonging to the actor class with the ID "A003".

[0078] Note that even if the actor class is the same, the information provided via the screen may differ if the user class is different. For example, even on the same "Recycling Status" screen, a user with user class "C002001" may be shown "Recycling Status for Battery of Vehicle A," while a user with user class "C002002" may be shown "Recycling Status for Battery of Vehicle B."

[0079] When an access is received from terminal 2, the information provision unit 113 determines the actor class and user class of the user involved in the access, and based on the determined actor class, determines which screens can be provided to the user. The information provision unit 113 may also generate a menu containing a list of available screens and provide it to terminal 2. Furthermore, when a specific screen is specified, the information provision unit 113 determines, based on the determined user class, what information to embed and provide on that screen. Based on the determination result, it extracts battery information stored in the battery information DB, generates a screen with the information to be provided embedded, and provides it to the terminal 2.

[0080] Next, the software configuration of terminal 2 according to this embodiment will be described. Figure 12 is a schematic diagram showing the software configuration of terminal 2 according to this embodiment. In this embodiment, the control unit 21 is configured to have an access unit 211 as a functional module. The functional module may be realized by the control unit 21 (CPU) executing a program stored in the storage unit 22.

[0081] The access unit 211 performs the function of accessing and interacting with the management server 1. This function may be implemented by a web browser running on terminal 2 or by dedicated application software. The access unit 211 outputs a user interface screen generated by the management server 1 and performs information input and output through this screen.

[0082] Next, the software configuration of the vehicle server 3 according to this embodiment will be described. Figure 13 is a schematic diagram showing the software configuration of the vehicle server 3 according to this embodiment. ru. In this embodiment, the control unit 31 is configured to include a data collection unit 311 as a functional module. The functional module may be realized by the control unit 31 (CPU) executing a program stored in the storage unit 32.

[0083] The collection unit 311 communicates with multiple vehicles 10 under its management and collects information related to driving (vehicle driving information) from these multiple vehicles. The collection unit 311 transmits the collected vehicle driving information, or battery information generated based on the vehicle driving information, to the management server 1. For example, the collection unit 311 may perform a predetermined calculation process (for example, a process to estimate the SoCE value) on the collected vehicle driving information, convert it into battery information (for example, the SoCE value), and then transmit this to the management server 1.

[0084] [Example of provided user interface screen] Next, an example of a user interface screen provided from the management server 1 to the terminal 2 will be described. In this embodiment, the management server 1 is configured to provide information to the terminal 2 via three types of screens described below.

[0085] (1) Dashboard screen The dashboard screen provides statistical information about the batteries handled by the business. For example, suppose a business that logs into management server 1 is a business that redistributes batteries removed from scrapped vehicles. In this case, the business can obtain statistical information from management server 1 regarding, for example, the collection status, storage status, and regional distribution of the batteries it handles. Figure 14A is an example of a dashboard screen. In the illustrated example, the collection status and storage status of the target batteries by region are shown. By specifying a region, it is also possible to check information such as how many batteries are at each dismantling company, or the breakdown by manufacturer and type. This screen can be generated based on battery information sent from businesses that dismantle scrapped vehicles and collect batteries.

[0086] Furthermore, let's assume, for example, that the business that logs into management server 1 is the business that manufactured the battery. In this case, the business can, for example, obtain statistical information regarding the recycling status of the batteries it manufactured. Figure 14B is another example of a dashboard screen. In the illustrated example, the recycling status of each resource for the target battery is shown. This screen can be generated based on battery information sent from businesses that dismantle and recycle batteries.

[0087] (2) Model data screen The model data screen provides information about a specific battery model. The model data screen is a screen for providing publicly available information about a specific battery model and can be accessed by multiple businesses involved with that battery. Figure 15 shows an example of the model data screen. In the illustrated example, information about a specified battery model is displayed. On the model data screen, users can check, for example, basic battery information, battery specifications, carbon footprint information, and information on disposal and management methods. This screen can be generated based on battery information sent by the businesses that designed and manufactured the batteries.

[0088] (3) BIN data screen The BIN data screen is a screen that provides information about a specific battery. The BIN data screen is a screen for providing status information about a specific battery, and typically shows the end user who owns the battery, and the status of the battery. Access is available to the business operator responsible for managing the battery. Figure 16 shows an example of the BIN data screen. In the illustrated example, information regarding the status of the battery with the specified BIN (Battery Identification Number) is displayed. BIN data The screen displays information such as the battery's certified energy (capacity) (SoCE, State of Certified Energy), safety level (SoS, State of Safety), health level (SoH, State of Health), charge / discharge status, and inspection results. It can be generated based on information transmitted from the target vehicle via the -3.

[0089] [Battery information access permission] Next, we will explain the permissions required to access the data stored in the battery information database. To generate the aforementioned screen, it is necessary to extract the required battery information from the battery information database. However, if unlimited access to the data is permitted, it could lead to the disclosure of information that is undesirable from a privacy standpoint. For example, an OEM (Original Equipment Manufacturer) responsible for managing batteries might access the BIN data screen to check the health and safety status of the target battery. However, if the BIN data screen contains information related to the privacy of the target battery (vehicle) (e.g., vehicle driving information), it would be undesirable to provide this to the OEM. Therefore, in this embodiment, access permissions are granted to each user for each piece of battery information stored in the database.

[0090] Refer to Figure 10, which shows the configuration of the battery information database, to explain access permissions. In this embodiment, access rights are granted to battery information for each type of information. In the illustrated example, four types of access rights are defined: "Users who own the target battery," "Vehicle OEM operators," "All users," and "Operators who provided the data." Access rights are granted when new battery information is stored.

[0091] For example, carbon footprint information for a particular battery is accessible to the end user who owns that battery and to the vehicle's OEM. On the other hand, information regarding the vehicle's operation (vehicle operation information) may contain private information and is therefore accessible only to the vehicle's end user. Furthermore, information regarding the vehicle and battery model (specifications) (vehicle information and battery information) is public information and is accessible to all users. However, information regarding the battery's design (battery design information) contains confidential information and is therefore accessible only to the company that provided the data. In addition, information regarding the chemical composition of the positive electrode active material, such as the ratio of nickel, cobalt, and manganese, may be available from battery recycling companies. Furthermore, information regarding the dismantling process (secondary dismantling) of battery packs, specifically the removal of modules and cells, may be available from certain companies. Thus, in this embodiment, each user is granted access rights to the battery information stored in the database, and each user is allowed to retrieve the information within the scope of the granted access rights.

[0092] Furthermore, users who own a vehicle and a battery will be granted at least access to information regarding the status of the battery (Primary Information). If ownership of the vehicle is transferred, such as when a user sells the vehicle, the access rights granted to that user may be revoked, and they may also be denied access to past information (during the ownership period).

[0093] Furthermore, users responsible for managing batteries (such as OEMs) are granted at least access rights to information (secondary information) that falls within the scope of their responsibility for managing those batteries.

[0094] If the responsibility for battery management is a responsibility for safety, then "information within the scope of battery management responsibility" refers to information regarding the health and safety of the battery, such as battery inspection results and information indicating the degree of battery degradation. This information includes, for example, information regarding the effective capacity of the battery, information regarding the temperature of the battery, information regarding physical damage to the battery, and information regarding the internal resistance of the battery.

[0095] If the responsibility for managing the battery is also the responsibility for its disposal, then "information within the scope of the responsibility for managing the battery" includes, for example, information for tracking the battery's location, such as a battery transfer certificate, or information indicating that the battery was disposed of in the correct manner, such as a battery disposal certificate. Transfer certificates and disposal certificates may also include information indicating the transferor, transferee, disposal method, or disposal location.

[0096] [Processing flow] Next, the processing flow executed by the management server 1 and terminal 2 will be explained with reference to Figures 17 and 18. Figure 17 is a flowchart of the process by which the management server 1 grants access rights to newly acquired battery information. The illustrated process is executed by the information acquisition unit 112 when the management server 1 receives battery information from terminal 2 or vehicle server 3 and stores it in the database.

[0097] First, in step S11, it is determined whether the battery information to be stored pertains to a battery that is installed in a vehicle and has an owner. If the target battery is installed in a vehicle and has an owner, the process proceeds to step S12. If the target battery is not installed in a vehicle, the process proceeds to step S13.

[0098] In step S12, the user who owns the battery information is granted access permission to read the stored battery information.

[0099] In step S13, it is determined whether the battery information to be stored pertains to a battery for which a specific OEM is responsible for management. If the battery information to be stored pertains to a battery for which a specific OEM is responsible for management, the process proceeds to step S14. If the battery information to be stored pertains to a battery for which a specific OEM is responsible for management, the process proceeds to step S15.

[0100] In step S14, the user who is the OEM responsible for managing the battery in question is granted access permissions. Note that access permissions may be granted only within the scope of their responsibility.

[0101] In step S15, it is determined whether the information to be stored can be provided to the OEM that manufactured the battery in question. If the information to be stored can be provided to the OEM that manufactured the battery in question, the process proceeds to step S16. If the information to be stored cannot be provided to the OEM that manufactured the battery in question, the process proceeds to step S17.

[0102] Even the OEM that manufactured the battery in question does not have access to all battery information. For example, the latest SoCE value needs to be calculated based on data collected from the vehicle, but if a data provision agreement has not been concluded with the vehicle owner, the data cannot be legally collected, and therefore the SoCE value cannot be provided to the OEM. Furthermore, even if a data provision agreement has been concluded, if the ownership of the vehicle is transferred (for example, if it is sold as a used car), the SoCE value cannot be provided to the OEM after the transfer. In step S15, the decision on whether or not to grant the authority is made after taking these circumstances into consideration. .

[0103] In step S16, the user, who is the OEM that manufactured the battery in question, is granted access to the stored information.

[0104] In step S17, access rights are granted to other users who are authorized to provide the stored information. For example, if there are other rules regarding access rights, such as "providing information on the recycling status of batteries handled to businesses that recycle batteries," access rights are granted in this step within the scope of those rules.

[0105] Although the process shown in Figure 17 is executed at the time the given battery information is stored, the illustrated process may be executed at other times. For example, as mentioned above, if ownership of the vehicle in which the target battery is installed is transferred, the vehicle's OEM may lose access to specific battery information. Therefore, the process in Figure 17 may be re-executed to update the access rights at the time of such ownership transfer or when the stage changes.

[0106] Next, we will explain the process by which the management server 1 provides information to terminal 2 based on the information stored in the battery information DB. Figure 18 is a sequence diagram corresponding to the process by which the management server 1 provides information to terminal 2.

[0107] The interaction between management server 1 and terminal 2 is initiated when an operator (or end user) of each service provider logs into management server 1 via terminal 2 using the corresponding account.

[0108] First, in step S21, terminal 2 (access unit 211) obtains information (login information) for authenticating the user. The login information may be a password or an access token. The obtained login information is sent to management server 1 (user authentication unit 111), and in step S22, the user authentication unit 111 performs user authentication. In this example, terminal 2 sends login information to management server 1, but user authentication may be performed by an external system (e.g., an authentication platform). In this case, the user authentication unit 111 receives the authentication result from the external system and identifies the user related to the access based on this result.

[0109] In step S23, the user authentication unit 111 determines the actor class and user class of the user involved in the access. The actor class and user class can be determined based on the user-related DB stored in the storage unit 12. As explained with reference to Figure 11, the actor class is associated with the screens that can be provided to the user, and the user class is associated with the information provided through the screens.

[0110] In step S24, based on the determination result in step S23, the system determines which screens can be provided to the user and generates a menu screen for accessing those screens. This menu screen includes menus for transitioning to one or more screens accessible to the user. The screens accessible to the user belong to at least one of the following: a dashboard screen, a model data screen, or a BIN data screen. The generated menu screen is provided to terminal 2.

[0111] In step S25, the user selects the destination screen from the menu on terminal 2. When a destination screen is selected, the destination screen specification is sent to the management server 1, and the information provision unit 113 retrieves information from the battery information DB based on this and generates the screen (step S26). Screen design data stored in the provided information DB is used to generate the screen. If the target screen includes a reference to data for which the user does not have permission to view, that data is omitted. The generated screen is sent to terminal 2 and provided to the user.

[0112] As described above, the management server 1 according to this embodiment collects and centrally manages battery-related information from multiple businesses or end users involved in the battery lifecycle. The management server 1 also classifies users involved in access by actor class and user class, and determines the screens and information to be provided based on the classification results. With this configuration, it becomes possible to improve the efficiency of screen display control and to provide appropriate information to users with various attributes.

[0113] (modified version) The embodiments described above are merely examples, and this disclosure may be modified as appropriate without departing from its essence. For example, the processes and means described in this disclosure can be freely combined and implemented, as long as no technical inconsistencies arise.

[0114] Furthermore, in the description of the embodiment, the management server 1 stores battery information in a database, but battery information may be stored by means other than a database.

[0115] Furthermore, a process described as being performed by a single device may be divided and executed by multiple devices. Conversely, a process described as being performed by different devices may be executed by a single device. In a computer system, the hardware configuration (server configuration) by which each function is implemented can be flexibly changed.

[0116] The present disclosure can also be realized by supplying a computer program implementing the functions described in the embodiments above to a computer, and having one or more processors in the computer read and execute the program. Such a computer program may be provided to the computer by a non-temporary computer-readable storage medium that can be connected to the computer's system bus, or it may be provided to the computer via a network. Non-temporary computer-readable storage mediums include, for example, any type of disk such as magnetic disks (floppy disks, hard disk drives (HDDs), etc.), optical disks (CD-ROMs, DVDs, Blu-ray discs, etc.), read-only memory (ROM), random access memory (RAM), EPROM, EEPROM, magnetic cards, flash memory, optical cards, and any type of medium suitable for storing electronic instructions. [Explanation of Symbols]

[0117] 1. Management Server 2. Terminal 3. Vehicle Server 11, 21, 31... Control Unit 12,22,32...Storage section 13, 23, 33... Communication Modules 14,24... Input / Output Devices

Claims

1. An information processing device that provides a user with first information relating to a predetermined object, which is generated based on one or more data relating to the predetermined object, The one or more data mentioned above, The user accessing the aforementioned information processing device is defined as user data, which is data associated with a user class. Second information defining the first information that can be provided to users belonging to a predetermined user class, A memory unit that stores, When a user accesses the system, the system determines the user class corresponding to the user based on the user data, Based on the second information, the first information corresponding to the determined user class is generated, Outputting the generated first information to the user's terminal, A control unit that performs the following: An information processing device having

2. An information processing device that provides a user with first information relating to a predetermined object, which is generated based on one or more data relating to the predetermined object, When a user accesses the system, the system determines the user class corresponding to the user from among a predefined set of user classes. Based on second information that defines the first information that can be provided to users belonging to a predetermined user class, the first information corresponding to the determined user class is generated, To provide the generated first information to the user, An information processing device having a control unit that performs the following.

3. The aforementioned first information is provided on a screen-by-screen basis. The second information defines the design of a screen to be provided to a user belonging to a predetermined user class, and the first information to be provided on that screen. The information processing apparatus according to claim 2.

4. The second information includes a logic for generating the first information using one or more of the data, The information processing apparatus according to claim 2.

5. The system further has a storage unit that stores one or more of the aforementioned data. The information processing apparatus according to claim 2.

6. The memory unit further stores the second information. The information processing apparatus according to claim 5.

7. The aforementioned predetermined object is a battery installed in a predetermined vehicle. The information processing apparatus according to claim 2.

8. The first information includes information regarding the degree of degradation of the battery, The information processing apparatus according to claim 7.

9. An information processing method performed by an information processing device that provides a user with first information about a predetermined object, generated based on one or more data points relating to the predetermined object, When a user accesses the system, the system determines the user class corresponding to the user from among a predefined set of user classes. Based on second information that defines the first information that can be provided to users belonging to a predetermined user class, the first information corresponding to the determined user class is generated, To provide the generated first information to the user, Information processing methods, including those mentioned above.

10. The aforementioned first information is provided on a screen-by-screen basis. The second information defines the screen design to be provided to a user belonging to a predetermined user class, and the first information that can be provided. The information processing method according to claim 9.

11. The second information includes a logic for generating the first information using one or more of the data, The information processing method according to claim 9.

12. The information processing device acquires one or more of the data from the storage device it has. The information processing method according to claim 9.

13. Further acquisition of the second information from the aforementioned storage device, The information processing method according to claim 12.

14. The aforementioned predetermined object is a battery installed in a predetermined vehicle. The information processing method according to claim 9.

15. The first information includes information regarding the degree of degradation of the battery, The information processing method according to claim 14.

16. A program for causing a computer to execute the information processing method described in any one of claims 9 to 15.

Images