Registration examination system and registration examination method

Abstract

The registration review will be conducted by clearly distinguishing the greenhouse gas emissions, reductions, or removals of each project by project implementation details. [Solution] When a registration request including project implementation details related to GHG emissions or reduction / absorption is associated with an object that will cause these, and if it is determined that the above object related to the registration request does not match the object in the registration information, the system associates the implementation details related to the registration request with the object related to the registration request and adds them to the registration information; when the above object is not associated with the registration request but the registration request is associated with a location where GHG emissions or reduction / absorption will be caused, the system converts the location into coordinates, and if the converted coordinates do not overlap with the coordinates in the registration information, the system associates the project implementation details related to the registration request with the converted information and adds them to the registration information.

Description

[Technical Field]

[0001] The present invention relates to a registration examination system and a registration examination method. [Background technology]

[0002] In recent years, in order to reduce the burden on the environment, there has been a call for global efforts to reduce greenhouse gas (GHG) emissions, which cause climate change, and many countries around the world (125 countries and 1 region as of 2021) are aiming to achieve carbon neutrality by 2050, which means reducing greenhouse gas emissions to zero overall.

[0003] One way to achieve carbon neutrality is through carbon credits, in which greenhouse gas emission reductions or absorptions are traded between countries and companies as credits. Carbon credits are the reductions or absorptions of greenhouse gases achieved through the introduction of energy-saving equipment or the use of renewable energy, which are measured, reported, verified, and certified by a certification body, and can then be traded as credits between countries and companies. Carbon credit trading, which offsets a company's own GHG emissions, is gaining attention as a realistic means of achieving emission reduction targets.

[0004] On the other hand, there are no uniform global standards for the carbon credit system or its specific operation, and there are a variety of carbon credit management organizations, including those led by the United Nations or governments, as well as those led by the private sector.Each management organization has different systems, operations, and certification methods, resulting in a proliferation of carbon credit systems and operation methods.

[0005] The Integrity Council for Voluntary Carbon Markets (ICVCM), which aims to establish uniform standards for global carbon markets, has announced 10 Core Carbon Principles. One of these principles is "No Double Counting: GHG reductions or removals from reduction activities must not be counted twice, i.e., they must be counted only once toward achieving a reduction target or goal. Double counting includes duplicate issuance, duplicate billing, and duplicate use." Examples of double counting include the double counting of the same greenhouse gas emission reduction or removal amount within a carbon credit scheme (e.g., J-Credit) operated by a single carbon credit management organization, or the duplicate registration of the same greenhouse gas emission reduction or removal project as a separate project. Furthermore, double counting must be prevented not only within a single carbon credit scheme (e.g., J-Credit), but also across multiple carbon credit schemes (e.g., J-Credit, VCM) operated by multiple carbon credit management organizations. For example, it is necessary to check whether a particular greenhouse gas emission reduction or absorption project is registered not only under J-Credit but also under VCM, another carbon credit scheme, and to prevent double registration so that the same project is not registered under multiple carbon credit schemes.

[0006] Regarding the method of managing the certificates, which are the proof data, after a carbon credit project has been registered, for example, Patent Document 1 discloses a technology in which proof data of greenhouse gas reductions is received from a certification authority and the proof data, buyer data, amortization data, etc. are recorded on a blockchain. [Prior art documents] [Patent documents]

[0007] [Patent Document 1] Japanese Patent Application Publication No. 2023-68752

[0008] However, at present, there is no adequately developed mechanism to accurately distinguish between the implementation of each greenhouse gas emission reduction or absorption at the stage before carbon credits are registered, and to effectively prevent duplicate registration. Summary of the Invention [Problem to be solved by the invention]

[0009] The present invention has been made in light of the above circumstances, and its purpose is to provide a registration review system and registration review method that can reliably distinguish the greenhouse gas emissions, reductions, or absorption amounts of a project according to the implementation details of the project and conduct registration review. [Means for solving the problem]

[0010] One aspect of the present invention for solving the above-mentioned problems includes a storage device that stores, as registration information, the implementation details of a project related to greenhouse gas emissions, reduction, or absorption, in association with information on objects that cause greenhouse gas emissions, reduction, or absorption, or location information in a predetermined coordinate system that indicates the location where the greenhouse gas emissions, reduction, or absorption occurs; a process for receiving a registration request including the implementation details of a project related to greenhouse gas emissions, reduction, or absorption, determining whether or not the registration request is associated with information on objects that cause greenhouse gas emissions, reduction, or absorption, and when it is determined that the registration request is associated with information on objects that cause greenhouse gas emissions, reduction, or absorption, determining whether or not the objects that cause greenhouse gas emissions, reduction, or absorption in the registration request match the objects that cause greenhouse gas emissions, reduction, or absorption in the registration information, and and if it is determined that the object that will cause greenhouse gas emission, reduction or absorption does not match, it associates the implementation details of the project related to the registration request with information on the object that will cause greenhouse gas emission, reduction or absorption related to the registration request and adds the associated information to the registration information; if it is determined that the information on the object is not associated with the registration request, it determines whether area information of a location where greenhouse gas emission, reduction or absorption will be caused is associated with the registration request; if it is determined that area information of a location where greenhouse gas emission, reduction or absorption will be caused is associated with the registration request, it converts the area information of the location into position information in the coordinate system and determines whether the converted position information overlaps with the position information in the coordinate system in the registration information; and if it is determined that the converted position information of the location in the registration request does not overlap with the position information in the coordinate system in the registration information, it associates the implementation details of the project related to the registration request with the converted position information and adds the associated information to the registration information. [Effects of the Invention]

[0011] According to the present invention, the amount of greenhouse gas emissions or reductions or removals resulting from a project can be reliably distinguished for each implementation detail of the project and then examined for registration.

[0012] Configurations and effects other than those described above will become apparent from the following description of the embodiments. [Brief explanation of the drawings]

[0013] [Figure 1] 1 is a diagram illustrating an example of a carbon credit registration and examination system according to an embodiment of the present invention. [Figure 2] 1 is a diagram illustrating an example of hardware and functions of a carbon credit registration examination device 1. FIG. [Figure 3] FIG. 10 is a diagram illustrating an example of a project validity period DB. [Figure 4] FIG. 10 is a diagram illustrating an example of a similar methodology DB. [Figure 5] FIG. 10 is a flow diagram illustrating an outline of a carbon credit registration examination process. [Figure 6] FIG. 10 is a diagram illustrating an example of an application data DB. [Figure 7] FIG. 10 is a diagram illustrating an example of a registered data DB. [Figure 8] FIG. 10 is a flowchart illustrating details of a target specific information generation process. [Figure 9] FIG. 10 is a flowchart illustrating details of a duplication confirmation process. [Figure 10] FIG. 10 is a flowchart illustrating details of an area confirmation process. [Figure 11] FIG. 10 is a flowchart illustrating details of an overlapping area determination process. [Figure 12] FIG. 10 is a diagram illustrating an example of determining whether an area overlaps with another area; [Figure 13] FIG. 10 is a diagram showing an example of an examination result screen. [Figure 14] FIG. 10 is a diagram showing an example of a carbon credit inquiry screen. DETAILED DESCRIPTION OF THE INVENTION

[0014] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described with reference to the drawings.

[0015] 1 is a diagram showing an example of a carbon credit management system 100 according to this embodiment. The carbon credit management system 100 is a registration management system including one or more carbon credit application systems 10 (10A, 10B) that each register carbon credits, and a registry DB3 (3A, 3B) corresponding to each carbon credit application system 10.

[0016] Each carbon credit application system 10 has a plurality of registration applicant terminals 4 used by businesses applying for carbon credit registration (hereinafter referred to as registration applicants), and a carbon credit registration review device 1 managed by each carbon credit operating organization (such as a national government, local government, public organization, or private organization) that accepts applications from each registration applicant terminal 4 and conducts reviews of the applications.

[0017] Each registry DB3 is a database that stores carbon credit data (hereinafter referred to as registration information or registered data) that has been registered after undergoing a prescribed review of carbon credit application data received by each carbon credit registration review device 1 from the registration applicant terminal 4.

[0018] The registry DB3 and each carbon credit application system 10, and the registration applicant terminal 4 in the carbon credit application system 10 and the carbon credit registration review device 1 are communicably connected via a wired or wireless communication network 2 such as the Internet, a LAN (Local Area Network), a WAN (Wide Area Network), or a dedicated line. The registry DB3 may be configured as a distributed ledger database having a blockchain linked to the carbon credit registration review device 1.

[0019] In this embodiment, each carbon credit registration and examination device 1 is managed by a different carbon credit operating organization.

[0020] Here, the carbon credit registration review device 1 accepts carbon credit registration applications from each registration applicant, but conventional devices like this do not necessarily check multiple applications sufficiently, so there is a possibility that multiple applications that are essentially the same will be accepted in duplicate.

[0021] For example, there is a risk that multiple applications for substantially the same implementation content from the same applicant may be accepted by the same device, or that multiple applications for substantially the same implementation content from multiple applicants may be accepted.

[0022] Furthermore, even between different devices, there was a risk that multiple applications by the same applicant with substantially identical implementation details would be accepted by each of the carbon credit registration review devices 1, or that applications by multiple applicants with substantially identical implementation details would be accepted by each of the carbon credit registration review devices 1 (A, B).

[0023] The carbon credit management system 100 of this embodiment is an information processing system that can prevent such erroneous registration (duplicate registration, and the resulting duplicate issuance of carbon credits and duplicate execution of projects related to carbon credits).

[0024] FIG. 2 is a diagram showing an example of the hardware and functions of the carbon credit registration and examination device 1. As shown in FIG.

[0025] First, the carbon credit registration examination device 1 comprises an arithmetic device 21 such as a CPU (Central Processing Unit), a storage device 22 such as a RAM (Random Access Memory), a ROM (Read Only Memory), an HDD (Hard Disk Drive), or an SSD (Solid State Drive), an input device 23 such as a keyboard, a mouse, or a touch panel, an output device 24 such as a display or a touch panel, and a communication device 25 consisting of a NIC (Network Interface Card), a wireless communication module, a USB (Universal Serial Interface) module, a serial communication module, etc. The registration applicant terminal 4 and the registry DB 3 may also have a similar hardware configuration.

[0026] The carbon credit registration and examination device 1 includes an application data reception function 211 , a registered data acquisition function 212 , a target identification information generation function 213 , a duplication confirmation function 214 , an examination function 215 , and an output function 216 .

[0027] The application data reception function 211 receives carbon credit application data from the registration applicant terminal 4. The application data is a registration request that includes the implementation details of carbon credits, which are the details of rights related to greenhouse gas reduction or absorption effects. Specifically, for example, the application data includes the applicant's name, an outline of the project that will bring about greenhouse gas reduction or absorption effects, information on how to achieve this (methodology), the implementation period of the project, location information such as the address where the project will be implemented, etc.

[0028] The registered data acquisition function 212 receives registered data (data on carbon credits for which applications have been registered) that has already been registered from the registry DB 3 and stores it in the registered data DB 700.

[0029] The target identification information generation function 213 has a data extraction function 2131 , a map data digitization function 3132 , and an identification number assignment function 2133 .

[0030] In other words, the target identification information generation function 213 determines whether the application data is associated with information (hereinafter referred to as a unique number) that identifies an object (hereinafter referred to as an object) that brings about a greenhouse gas reduction or absorption effect, or information (hereinafter referred to as location information) that identifies a location where a greenhouse gas reduction or absorption effect is brought about, and if it determines that information (hereinafter referred to as target identification information) that identifies an object or location where a greenhouse gas reduction or absorption effect is brought about is associated with the registration request, it sets an identification number that is associated with the implementation details (methodology, project date and time, etc.) of the project indicated in the registration request, including the unique number that identifies the object or the location information that identifies the target location.

[0031] The target identification information that identifies the target object or target location is, for example, the product number of the equipment that reduces greenhouse gas emissions more than usual, or location information such as the latitude and longitude of the target object's address or area.

[0032] Furthermore, the target identification information generation function 213 determines whether or not the application data is associated with information on the location where the greenhouse gas reduction or absorption effect will be brought about (point data such as an address, or area data such as a map or area), and if it determines that the application data is associated with information on the location where the greenhouse gas reduction or absorption effect will be brought about, converts the location information into location information based on latitude and longitude. The location may be, for example, the address of the project implementation location, a forest cultivation / management / afforestation area, an agricultural implementation site (farmland, rice cultivation area, livestock or dairy farming area, etc.), a factory, etc.

[0033] Specifically, for example, if the map data digitization function 3132 determines that information on a place that does not have an area, such as an address, is associated with the application data, it converts the location information, such as the address, into location information (point data) based on latitude and longitude, and if it determines that area information (map data, area, etc.) is associated with the application data, it converts the location information into location information based on latitude and longitude that represents the area information (for example, location information based on latitude and longitude of the vertices of the area of ​​the target area; polygon data).This map is, for example, a map of a predetermined area that includes multiple scattered locations where greenhouse gas emissions, reductions, or absorption effects are achieved.

[0034] The overlap confirmation function 214 includes a validity period calculation function 2141 and an overlap determination function 2142 .

[0035] That is, the validity period calculation function 2141 calculates the validity period of (the implemented work indicated by) the right to emit, reduce, or absorb greenhouse gases in each carbon credit system. Specifically, it calculates the validity period of (the implemented work indicated by) the right to carbon credits stated in the application data from the project implementation period stated in the application data and the project validity period (project validity period DB300) for each methodology of each carbon credit system used in the project.

[0036] The duplication determination function 2142 determines whether or not the application data and registered data are duplicated.

[0037] Specifically, the similar methodology DB is used to determine whether the methodology associated with the application data is similar to the methodology in the registration information (registered data DB700), and registration information in which a methodology similar or identical to the application data is registered is extracted from the registered data DB700 as similar registration data.

[0038] The overlap determination function 2142 determines whether there is an overlap between the application data and the registered information by determining whether the project period (validity period) related to the application data overlaps with the project period (validity period) in the registered information (registered data DB700).

[0039] In addition, the duplication determination function 2142 determines whether or not there is duplication between the application data and the registered information by determining whether or not the object related to the application data matches the object (unique number 708 of the target identification information) in the registered information (registered data DB700).

[0040] In addition, the overlap determination function 2142 determines whether there is overlap between the application data and the registered information by determining whether the location information (latitude and longitude) of the project location related to the application data overlaps with the location information (latitude and longitude 709 of the target specific information) of the target location in the registered information (registered data DB700).

[0041] In addition, if the project location data related to the application data includes area information (area or map data, etc.), the overlap determination function 2142 determines whether there is overlap between the application data and the registration information by determining whether there is overlap between the area information (map data, etc.) of the project location and the location information of the target location in the registration information (registered data DB700) (area information (multiple data) of latitude and longitude 709 of the target specific information).

[0042] The review function 215 includes an automatic review function 2151, a manual review function 2152, and an application data registration function 2153.

[0043] The automatic screening function 2151 executes screening processing using a predetermined algorithm for carbon credit registration applications related to application data that does not have duplicates.

[0044] The manual review function 2152 receives input of review implementation details from the review organization or reviewer.

[0045] The application data registration function 2153 adds the data that has passed the screening and been approved as registered data to the registered data DB 700 and the registry 3 of the relevant carbon credit scheme.

[0046] The output function 216 displays a screen showing the results of the examination process on the carbon credit registration examination device 1 or the registration applicant terminal 4.

[0047] Next, the carbon credit registration review device 1 stores each data (database) of an application data DB600, a registered data DB700, a project validity period DB300 that registers the validity period of projects in each carbon credit system, a similar methodology DB400 that defines methodologies that are similar to each other, and a methodology DB500 that stores the implementation details of each methodology in each carbon credit system.

[0048] (Project validity period DB) 3 is a diagram showing an example of a project validity period DB 300. The project validity period DB 300 has data on methodology 301 indicating the name of each methodology, project validity period 302 of each methodology, and re-registration date 303 (re-execution date) indicating the date on which a project can be re-registered if each methodology is used.

[0049] (Similar methodology DB) 4 is a diagram showing an example of a similar methodology DB 400. The similar methodology DB 400 has data on each methodology 401 in each carbon credit system, and similar methodologies 402 that indicate methodologies similar to each methodology 401 in terms of field and implementation details.

[0050] The functions of each information processing device in the carbon credit management system 100 described above are realized by the computing device 21 of each information processing device reading a program from the storage device 22. Each program can be recorded on, for example, a portable or fixed recording medium and distributed. All or part of each program in each information processing device may be realized using virtual information processing resources provided using virtualization technology, process space separation technology, or the like, such as a virtual server provided by a cloud system. All or part of these programs may be realized by a service provided by a cloud system via an API (Application Programming Interface), for example.

[0051] Next, the processing performed in the carbon credit management system 100 will be described.

[0052] <Carbon credit management processing> 5 is a flow diagram illustrating an outline of the carbon credit management process. The carbon credit management process is repeatedly executed as needed, for example, after the carbon credit registration review device 1 is started. Note that the process performed by one of the multiple carbon credit registration review devices 1 will be described here.

[0053] The carbon credit registration examination device 1 receives data (application data) for a new carbon credit application (hereinafter referred to as the main application) from the registration applicant terminal 4, and registers the data in the application data DB 600 (s1).

[0054] The carbon credit registration review device 1 executes a target identification information generation process s2 for setting information (unique number or latitude and longitude of the location (point or area information)) that identifies the target (target object or target location) that will bring about a greenhouse gas reduction or absorption effect, for the application data of this application received in s1.

[0055] The carbon credit registration review device 1 executes a duplication confirmation process s3 to confirm whether the implementation details of the application data received in s1 overlap (including whether they are identical or partially overlap) with the implementation details of the carbon credit registered in the registered data DB700.

[0056] If the implementation contents overlap (s4: NO), the carbon credit registration review device 1 executes the process of s11, and if the implementation contents do not overlap (s4: YES), the carbon credit registration review device 1 executes the process of s5.

[0057] In s5, the carbon credit registration examination device 1 executes an examination of this application.

[0058] First, in s5, the carbon credit registration examination device 1 performs an automatic examination of the application and determines whether the examination is successful.

[0059] For example, the carbon credit registration and examination device 1 determines whether or not predetermined items have been registered in the application data, and whether or not necessary information has been associated with the application data (for example, whether or not a report has been attached).

[0060] Next, the results are sent to the carbon credit review organization and the carbon credit system administrator / committee, and the review and certification results for the application are received from the respective review organizations and system administrator / committee. For example, the carbon credit registration review device 1 displays a predetermined input screen and receives input of approval or rejection from the review organization.

[0061] If the inspection result is passed (s6: Y), the carbon credit registration inspection device 1 executes the process of s7, and if the inspection result is failed (s6: N), the carbon credit registration inspection device 1 executes the process of s11.

[0062] In s7, the carbon credit registration examination device 1 examines the application and determines that it is approved.

[0063] If the review of this application is approved, the carbon credit registration review device 1 sets an identification number that identifies the implementation details of the project indicated by the application data (s8). The identification number is assigned a number that can identify the implementation details of the application data to be registered in the carbon credit registry 3, such as the applicant, project outline of the application, methodology, project validity period, project location, and target specific information (items registered in the registered data DB 700). The identification number may be, for example, a number that is converted or encrypted based on a predetermined rule from the implementation details of the application data (such as the methodology number or the date and time of the project validity period).

[0064] Then, the carbon credit registration and examination device 1 registers the application data and data including an identification number that can identify the implementation details of the application data in the registered data DB 700 and the register 3 (s9).

[0065] The carbon credit registration review device 1 displays a screen showing the results of the above processing on the screen of the carbon credit registration review device 1 or the registration applicant terminal 4 (s10). This completes the carbon credit management processing.

[0066] On the other hand, in s11, the carbon credit registration review device 1 rejects the application, and the carbon credit management process ends (s11, s10). For example, the carbon credit registration review device 1 displays a screen indicating that the application data has been rejected on the screen of the carbon credit registration review device 1 or the registration applicant terminal 4.

[0067] (Application data DB) 6 is a diagram showing an example of the application data DB 600. The application data DB 600 is a database of data (application data) applied for registration from the registration applicant terminal 4. Specifically, the application data DB 600 has the following data: applicant 601 for each application, carbon credit methodology 602 used in the project for each application, project implementation period 603 indicating the period during which the project was implemented, project location 604 indicating the location where the project was implemented, object unique number 605 identifying the object of the project, and project summary 606 indicating an outline of the project.

[0068] The methodology 602 is the name of the method that each carbon credit management organization defines, such as the method of calculating the amount of greenhouse gas reduction or absorption, and the monitoring method.

[0069] Location 604 always includes address information for the project location. Additionally, location 604 may include map information for the area of ​​the project location or a specific region that includes multiple target areas. This map information includes information about the boundary (perimeter) of the project location.

[0070] The unique number 605 of the object is, for example, the manufacturing number or serial number of the device.

[0071] (Registered data DB) 7 is a diagram showing an example of a registered data DB 700. The registered data DB 700 is a database that accumulates registered data registered in the registry 3 (A, B) of each carbon credit operating organization. Synchronization of the registered data DB 700 with the data in the registry 3 (A, B) of each carbon credit may be performed periodically or when an application for registration is made. Specifically, the registered data DB700 contains the following data: applicant 701 indicating the name of the applicant for each registered application; methodology 702 indicating the name of the methodology used in the project of each registered application; project implementation period 703 indicating the period during which the project was implemented; credit authentication date 704 indicating the date on which the application was authenticated as a credit; project validity period 705; project location 706 indicating the location where the project was implemented; target specific information 707 identifying the subject of the project (object, location); unique number 708 indicating the product number of the object or the like among the specific information; latitude and longitude 709 indicating the location information of the project implementation location (address or area data); project summary 710 indicating an overview of the project; and identification number 711 identifying the implementation content of the project.

[0072] If the project location has a certain range (area), the latitude and longitude 709 is the latitude and longitude of each point (vertex, etc.) on the periphery of the range (area), and if it does not have a certain range (area), it is the latitude and longitude of the address (representative point).

[0073] <Target specific information generation process> 8 is a flow diagram illustrating the details of the target identification information generation process s2. The carbon credit registration review device 1 acquires application data related to the present application by extracting the record related to the present application received in s1 from the application data DB 600 (s21).

[0074] The carbon credit registration examination device 1 determines whether or not the application data relating to the actual application extracted in s21 includes information on the unique number (product number, serial number, etc.) of the object (s22).

[0075] If the application data for this application contains information on the unique number of the object (s22: yes), the carbon credit registration review device 1 executes the process of s23, and if the application data for this application does not contain information on the unique number of the object (s22: no), the carbon credit registration review device 1 executes the process of s24.

[0076] In s23, the carbon credit registration examination device 1 acquires the information of the object related to this application by acquiring the object's unique number from the object's unique number 605 in the application data. After that, the process of s30 is performed.

[0077] In s24, the carbon credit registration examination device 1 acquires the data of the project location 604 in the application data.

[0078] If the acquired project location information includes area information such as a map or area (s25: yes), the carbon credit registration review device 1 executes the process of s27, and if the acquired project location information does not include area information such as a map or area (s25: no), the carbon credit registration review device 1 executes the process of s26.

[0079] In s26, the carbon credit registration review device 1 converts the location information of the address (point data) into latitude and longitude information based on the project location information included in the information acquired in s24, using a geocoding API, a predetermined external latitude and longitude conversion tool, a map database, or the like. Thereafter, the processing of s30 is performed. The latitude and longitude corresponding to the address is, for example, the latitude and longitude of the representative point of the address.

[0080] In s27, the carbon credit registration review device 1 acquires or converts into map data the area data (map data, area, etc.) of the project location acquired in s24. Then, the carbon credit registration review device 1 digitizes the acquired map data indicating the project location (s28). Then, the carbon credit registration review device 1 calculates the latitude and longitude of the map data acquired in s28 (s29).

[0081] For example, the carbon credit registration review device 1 identifies the position on the map of each point (e.g., corner) that constitutes the perimeter of each target area on the map. The carbon credit registration review device 1 converts the position of each identified point into latitude and longitude, and defines the area inside each point as the map area. After that, the process of s30 is performed.

[0082] In s30, the carbon credit registration and examination device 1 acquires, as the project implementation date and time, the project implementation period 603 in the application data DB 600. This completes the correspondence information generation process s2.

[0083] <Duplicate confirmation process> 9 is a flow diagram illustrating the details of the duplication confirmation process s3. The carbon credit registration review device 1 acquires information on the methodology of the present application and methodologies similar to that methodology (s31). Specifically, the carbon credit registration review device 1 acquires the methodology 602 of the application data, and then acquires, in the similar methodology DB 400, the similar methodology 402 that corresponds to the same methodology 401 as the acquired methodology 602.

[0084] The carbon credit registration review device 1 identifies, from the registered data, applications (project implementation details) whose methodology is the same as or similar to that of the present application, and extracts them as similar registered data (s32). Specifically, the carbon credit registration review device 1 identifies, from the registered data DB 700, all records in which the methodology 602 or similar methodology 402 acquired in s31 is set as the methodology 702, and extracts them as similar registered data.

[0085] The carbon credit registration and examination device 1 may acquire only registered applications in the registered data DB700 associated with the carbon credit application system 10 in a single carbon credit scheme, or may acquire registered applications from the registered data DB700 associated with the carbon credit application system 10 in multiple carbon credit schemes. This makes it possible to prevent duplicate registrations at multiple carbon credit issuing organizations, or to prevent only duplicate registrations at a single carbon credit issuing organization (for example, multiple individuals applying for and registering the same project).

[0086] The carbon credit registration and review device 1 calculates the validity period of the project in the application data (s33). Specifically, the carbon credit registration and review device 1 calculates the validity period of the project in the application data using the project implementation period of the application data acquired in s30, the methodology of the application data acquired in s31, and the project validity period DB300.

[0087] For example, if the project implementation period of the application data acquired in s30 is "20150101-20241231 (January 1, 2015 to December 31, 2024)" and the methodology of the application data acquired in s31 is "J Credit FO-001," the carbon credit registration review device 1 calculates the project validity period as "20341231 (December 31, 2034)," which is 10 years after the project implementation end date, from the methodology 301 and project validity period 302 in the project validity period DB300.

[0088] The carbon credit registration review device 1 identifies registered applications (hereinafter referred to as similar registered data) from among the registered applications that use similar and identical methodologies identified in s32, which have not yet passed the re-registration date, have an overlapping validity period with this application, and have overlapping project implementation details with this application, and extracts them as similar registered data (s34).

[0089] Specifically, the carbon credit registration review device 1 confirms whether the project validity period of the application data acquired in s33 at least partially overlaps with the project implementation period 703 and project validity period 705 of the registered data using similar and identical methodologies extracted from the registered data DB700 in s32, and whether the project summary 606 of this application matches the project summary 710 of the registered data using similar and identical methodologies extracted from the registered data DB700 in s32.

[0090] Furthermore, the carbon credit registration examination device 1 checks whether a unique number is set in the application for each similar registered data identified in s32 (s35). Specifically, the carbon credit registration examination device 1 checks the implementation details of the unique number 708 in the registered data DB 700.

[0091] If a unique number is set (s35: Y), the carbon credit registration review device 1 executes the process of s36 for the similar registered data. If a unique number is not set (s35: N), the carbon credit registration review device 1 executes the process of s37 for the similar registered data.

[0092] In s36, the carbon credit registration review device 1 checks whether there is a duplicate between the main application and the similar registered data based on the unique number, and stores the result. Specifically, the carbon credit registration review device 1 checks whether there is a match or mismatch between the unique number 605 of the record of the main application in the application data DB 600 and the unique number 708 of the target identification information 707 of the record of the similar registered data in the registered data DB 700. This completes the duplicate confirmation process s3.

[0093] In s37, the carbon credit registration review device 1 determines whether area or map data (area data) is set for each similar registered data. For example, specifically, if multiple latitudes and longitudes are registered in the latitude and longitude 709 of the record of similar registered data in the registered data DB 700, the carbon credit registration review device 1 determines that these latitudes and longitudes do not represent single location information such as an address but represent each vertex of an area, and determines that area or map area data is set.

[0094] The carbon credit registration review device 1 executes the process of s38 for similar registered data in which area or map area data is set (s37: Y). On the other hand, for similar registered data in which area data such as area or map data is not set (only single location information) (s37: N), the carbon credit registration review device 1 executes the process of area confirmation process s39 to confirm whether or not there is any overlap between the single location information of the similar registered data and the single location information such as the address in this application. This completes the overlap confirmation process s2.

[0095] In s38, the carbon credit registration examination device 1 checks whether there is any overlap between the area data of the project of the similar registered data and the area data of the project of this application (calculated in s29), and stores the result. This completes the overlap confirmation process s2.

[0096] <Area confirmation process> 10 is a flow diagram explaining the details of the area confirmation process s39. The carbon credit registration review device 1 confirms whether the project implementation area of ​​the main application is the same as the project implementation area of ​​the similar registered data, and extracts data of the same implementation area (s391). Specifically, the carbon credit registration review device 1 compares the latitude and longitude of the project implementation area of ​​the main application calculated in s29 with the contents of latitude and longitude 709 for which there are multiple latitude and longitude data in the similar registered data extracted in s32, and confirms whether the latitude and longitude are all the same.

[0097] If the location information of all vertices (nodes) in the project implementation area of ​​this application and the project implementation area of ​​the similar registered data are identical (s392: Y), the carbon credit registration review device 1 executes the processing of s393, and if the project implementation area of ​​this application and the project implementation area of ​​the similar registered data are not identical (s392: N), the carbon credit registration review device 1 executes the processing of s394.

[0098] In s393, the carbon credit registration examination device 1 stores the fact that the project implementation area of ​​this application overlaps with the area of ​​similar registered data, and the area confirmation process s39 ends.

[0099] In s394, the carbon credit registration review device 1 executes an overlap area determination process to determine whether there is an overlap (partially identical) between the area of ​​this application and the area of ​​similar registered data, and extracts the partially overlapping data (s394).

[0100] If there is some overlap between the project implementation area of ​​this application and the project implementation area of ​​similar registered data (s395: Y), the carbon credit registration review device 1 stores the fact that there is an overlap between the project implementation area of ​​this application and the project implementation area of ​​similar registered data (s396), and the area confirmation process s39 ends.

[0101] If there is no overlap between the project implementation area of ​​this application and the project implementation area of ​​the similar registered data (s395: N), the carbon credit registration review device 1 stores the fact that there is no overlap between this application and the similar registered data (s397), and the area confirmation process s39 ends.

[0102] <Overlapping area determination process s394> 11 is a flow diagram explaining the details of the overlap area determination process s394. The carbon credit registration review device 1 determines whether or not each vertex (node) of the project implementation area in this application is within the project implementation area of ​​the similar registered data (s3941-s3943). Specifically, the carbon credit registration review device 1 determines whether or not the latitude and longitude (s29) of each vertex (node) of the project implementation area in this application is within the area formed by connecting the latitude and longitude of each vertex (node) of the project implementation area of ​​the similar registered data.

[0103] If any of the vertices (nodes) of the project implementation area in this application is within the project implementation area of ​​the similar registered data (s3944:Y, an example is shown in 1202 in FIG. 12), the carbon credit registration review device 1 stores the fact that there is a partial overlap between this application and the similar registered data (s3945), and the overlap area determination process s394 ends. If any of the vertices (nodes) of the project implementation area in this application is not within the area of ​​the similar registered data (s3944:N), the carbon credit registration review device 1 executes the process of s3946.

[0104] In s3946, the carbon credit registration review device 1 extracts one of the sides (links) of the project implementation area in this application (s3946). Then, the carbon credit registration review device 1 determines whether the extracted link intersects with any of the sides (links) of the project implementation area in the similar registered data (s3947).

[0105] The carbon credit registration examination device 1 executes the processes of s3946 and s3947 for all edges (links) of the project implementation area in this application (s3948:N).

[0106] After executing the processes of s3946 and s3947 for all edges (links) of the project implementation area in this application (s3948: Y), the carbon credit registration review device 1 determines whether there are any edges (links) of the project implementation area in this application that intersect with any of the edges (links) of the project implementation area in similar registered data (s3949).

[0107] If there is a link in this application that intersects with any of the links in similar registered data (s3949:Y, an example is shown in 1203 in Figure 12), the carbon credit registration review device 1 stores the fact that there is some overlap between this application and the similar registered data (s3950), and the overlap area determination process s394 ends.

[0108] If there is no edge link of the project implementation area of ​​this application that intersects with any of the edges (links) of the project implementation area of ​​similar registered data (s3949:N), the carbon credit registration review device 1 stores the fact that the project implementation areas of this application and the similar registered data do not overlap (s3951), and the overlap area determination process s394 ends.

[0109] Fig. 12 is a diagram showing an example of an overlap determination of areas. As described above, reference numeral 1201 in Fig. 12 is an example of a case where the position information of all vertices (nodes) in the area of ​​this application and the area of ​​the similar registered data are identical (s392:Y), reference numeral 1202 in Fig. 12 is an example of a case where any vertex (node) of the area of ​​this application is inside the area of ​​the similar registered data (s3944:Y), and reference numeral 1203 in Fig. 12 is an example of a case where an edge (link) of the area of ​​this application intersects with any edge (link) of the similar registered data (s3949:Y).

[0110] (Examination results screen) 13 is a diagram showing an example of an examination result screen 1300. The examination result screen 1300 has an application data display field 1310, a duplicate presence / absence display field 1320, a duplicate data display field 1330, an examination result field 1340, and a registration status field 1350.

[0111] The application data display field 1310 displays information about this application (applicant, methodology, project implementation period, address, map, plan, etc.).

[0112] The overlap display field 1320 displays 1321 whether there is registered data that overlaps with this application (including identical and partial overlaps), and the specific details of the overlap 1322 (for example, overlap in implementation period and location).

[0113] The overlapping data display field 1330 displays project implementation details 1331 (applicant, methodology, project implementation period, address, identification number, etc.) in registered data that overlaps with this application (including identical and partial overlaps), and a map 1332 showing the overlapping areas between the project implementation location information of this application and the location information of the overlapping data.

[0114] The review result field 1340 displays the review result of this application.

[0115] The registration status field 1350 displays the registration status of this application.

[0116] Furthermore, the registration applicant terminal 4 or the carbon credit registration examination device 1 may display a carbon credit inquiry screen 1400 that displays the implementation details of the registered carbon credit, with the identification number specified as a key.

[0117] (Carbon credit inquiry screen) 14 is a diagram showing an example of a carbon credit inquiry screen 1400. The carbon credit inquiry screen 1400 has an identification number input field 1401 that accepts input of an identification number from a user such as a business operator or a person in charge of a certification body, and an information display field 1402 that displays the implementation details of the registered data in the registered data DB 700, to which the identification number input in the identification number input field 1401 is set.

[0118] As described above, when the application data includes information about an object that emits, reduces, or absorbs greenhouse gases, the carbon credit management system 100 of this embodiment determines whether the object in the application data matches the object in the registered data DB700, and if it determines that the object in the application data does not match the object in the registered data DB700, it associates the carbon credit implementation details in the application data with the information about the object and adds them to the registered data DB700. On the other hand, if the application data does not include information about the target object, and if information about the target location (address or area) is associated with the application data, the carbon credit management system 100 converts the information about the target location into latitude and longitude information, determines whether the location information (point or area) represented by the converted latitude and longitude overlaps with the location information (point or area) represented by the latitude and longitude in the registered data DB700, and if it determines that the location information (point or area) represented by the converted latitude and longitude does not overlap with the location information (point or area) represented by the latitude and longitude in the registered data DB700, it associates the carbon credit implementation details in the application data with the latitude and longitude location information and adds them to the registered data DB700.

[0119] That is, in managing carbon credits, the carbon credit management system 100 of this embodiment does not distinguish between and manage the amounts of greenhouse gas emissions, reductions, or absorptions themselves, but distinguishes between carbon credits related to greenhouse gas emissions, reductions, or absorptions based on the objects that emit, reduce, or absorb greenhouse gases or the locations where the greenhouse gas emissions, reductions, or absorptions are taking place, and determines whether or not carbon credits are registered multiple times. This makes it possible to reliably distinguish between carbon credits for each project and prevent duplicate registrations, etc.

[0120] In this way, according to the carbon credit management system 100 of this embodiment, the amount of greenhouse gas emissions, reductions, or absorptions resulting from a project can be reliably distinguished for each implementation content of the project and registered and screened.

[0121] Furthermore, the carbon credit management system 100 of this embodiment calculates the project validity period of the application data, determines whether the project validity period of the application data overlaps with the project validity period of a similar registered data DB700, and if it determines that the project period of the application data does not overlap with the project period of a similar registered data DB700, it associates the carbon credit implementation details in the application data with the target identification information (unique number or location information such as latitude and longitude) and adds them to the registered data DB700.

[0122] In this way, by checking whether the validity periods of projects related to carbon credits overlap, it is possible to prevent the carbon credits from being effectively registered twice.

[0123] Furthermore, in the carbon credit management system 100 of this embodiment, when the application data is associated with a unique number of the object of the carbon credit, it determines whether or not there is a duplication with a similar unique number in the registered data DB700, and if it determines that there is no duplication, it associates the carbon credit implementation details in the application data with the information on the unique number and adds them to the registered data DB700.

[0124] Furthermore, in the carbon credit management system 100 of this embodiment, if the application data is associated with the location of the carbon credit project (address, point location information), the carbon credit management system 100 converts the location into location information such as latitude and longitude, determines whether the converted latitude and longitude overlap with the latitude and longitude in similar registered data DB700, and if it determines that the converted latitude and longitude do not overlap with the latitude and longitude in similar registered data DB700, associates the carbon credit implementation details in the application data with the latitude and longitude information and adds them to the registered data DB700.

[0125] Furthermore, in the carbon credit management system 100 of this embodiment, if the application data is associated with area information such as map data and area as location data for the carbon credit project, the carbon credit management system 100 converts the area into latitude and longitude information, determines whether the latitude and longitude of the converted area overlap with the latitude and longitude of an area in the similar registered data DB700, and if it determines that the converted latitude and longitude do not overlap with the latitude and longitude of an area in the similar registered data DB700, associates the carbon credit implementation details in the application data with the latitude and longitude information of the area and adds them to the registered data DB700.

[0126] In this way, by converting information on the objects that are emitting, reducing, or absorbing greenhouse gases or the locations (addresses, areas) where greenhouse gases are being emitted, reduced, or absorbed into location information such as a unique number or latitude and longitude that can be used to identify each, and comparing the unique number or location information such as latitude and longitude in the application data with the unique number or location information such as latitude and longitude in the registered data to check for duplication, it is possible to more reliably prevent double registration of carbon credits where the project targets or locations overlap.

[0127] In addition, the carbon credit management system 100 of this embodiment further generates blockchain data including the implementation details of the registered data DB700 to which information on the object or latitude and longitude in the registration request has been added, and stores the generated blockchain data in each registry 3.

[0128] This allows each business operator to share their carbon credit information among themselves, and also prevents tampering with the information.

[0129] Furthermore, the carbon credit management system 100 of this embodiment sets an identification number by associating the methodology used in the carbon credit project, the project implementation period, and the target's specific information (unique number or latitude and longitude) with the content. The identification number is then added to the registered data DB 700. Thereafter, the carbon credit management system 100 accepts input of an arbitrary identification number from the user, and displays the details of the carbon credit associated with the input identification number on the screen of the registration applicant terminal 4 or the carbon credit registration review device 1 (carbon credit inquiry screen 1400).

[0130] This allows the details of registered carbon credits to be easily called up and checked using the identification number as a key.

[0131] The present invention is not limited to the above-described embodiments, and can be implemented using any components within the scope of the present invention. The above-described embodiments and modifications are merely examples, and the present invention is not limited to these implementations as long as the features of the invention are not impaired. Furthermore, although various embodiments and modifications have been described above, the present invention is not limited to these implementations. Other aspects conceivable within the scope of the technical idea of ​​the present invention are also included within the scope of the present invention.

[0132] For example, part of the hardware provided in each device of this embodiment may be provided in another device.

[0133] Furthermore, each program of each device may be provided in another device, a program may consist of multiple programs, or multiple programs may be integrated into one program.

[0134] Furthermore, although the present embodiment has been described in the case of carbon credit registration and review, the present invention is not limited to carbon credit trading, and can be applied to registration or recording of greenhouse gas emission, reduction or absorption implementation details, utilization as evidence when disclosing data on the details of projects implementing greenhouse gas emission, reduction or absorption, and other types of emissions (for example, emissions of substances that cause environmental loads other than GHGs).

[0135] The method of determining whether an area overlaps as described in this embodiment is merely an example. For example, an area may be represented as a set of many points, and each point of the area in the application data may be compared with each point of the area in the registered data DB 700.

[0136] Furthermore, in the overlapping area determination process s394, if the target area is a concave polygon, the concave polygon may be divided into a plurality of convex polygons or triangles, and overlap may be confirmed for each divided area.

[0137] Furthermore, in this embodiment, latitude and longitude information is used as the location information of the region, but any other coordinate system may be used.

[0138] Furthermore, the information about each location (address or area) may include altitude information. [Explanation of symbols]

[0139] 100 carbon credit management system, 10 carbon credit application system, 4 registration applicant terminal, 1 carbon credit registration review device

Claims

1. a storage device that stores, as registered information, the details of a project related to greenhouse gas emissions, reductions, or absorption, in association with information on objects that cause the greenhouse gas emissions, reductions, or absorption, or location information in a predetermined coordinate system that indicates the location where the greenhouse gas emissions, reductions, or absorption occurs; and receiving a registration request containing details of a project related to greenhouse gas emissions or reduction or removal; determine whether or not information on an entity that causes greenhouse gas emissions, reductions or absorption is associated with the registration request, and if it is determined that information on an entity that causes greenhouse gas emissions, reductions or absorption is associated with the registration request, determine whether or not the entity that causes greenhouse gas emissions, reductions or absorption in the registration request matches the entity that causes greenhouse gas emissions, reductions or absorption in the registration information, and if it is determined that the entity that causes greenhouse gas emissions, reductions or absorption in the registration request does not match the entity that causes greenhouse gas emissions, reductions or absorption in the registration information, associate the implementation details of the project that is related to the registration request with the information on the entity that causes greenhouse gas emissions, reductions or absorption in the registration request and add them to the registration information; a computing device that executes an overlap confirmation process in which, when it is determined that the registration request does not correspond to information on the object, it determines whether area information of a place where greenhouse gas emissions, reductions or absorptions are brought about is associated with the registration request; when it is determined that the registration request does correspond to information on the area of ​​a place where greenhouse gas emissions, reductions or absorptions are brought about, it converts the area information of the place into position information in the coordinate system, it determines whether the converted position information overlaps with the position information in the coordinate system in the registration information; and when it is determined that the converted position information of the place in the registration request does not overlap with the position information in the coordinate system in the registration information, it associates the implementation details of the project related to the registration request with the converted position information and adds it to the registration information. Registration management system.

2. The storage device further stores, in the registration information, information on a period during which the greenhouse gas emissions, reductions, or absorptions will be achieved, in association with the implementation details; The computing device further determining whether or not the registration request is associated with information on a period during which greenhouse gas emissions, reductions, or absorption will occur, and if it is determined that the registration request is associated with information on a period during which greenhouse gas emissions, reductions, or absorption will occur, determining whether or not the period related to the registration request overlaps with a period in the registration information, and if it is determined that the period related to the registration request does not overlap with a period in the registration information, correlating the implementation details of the project related to the registration request with the information on the period during which greenhouse gas emissions, reductions, or absorption will occur related to the registration request and adding them to the registration information; The registration management system of claim 1 .

3. The storage device further stores, in the registration information, information on methods for emitting, reducing, or absorbing the greenhouse gas in association with the implementation details of the project; The computing device further compares information on the method that brings about greenhouse gas emission, reduction, or absorption, which is associated with the registration request, with information on the method in the registration information, thereby determining whether the method related to the registration request is similar to the method in the registration information; if it determines that the method related to the registration request is similar to the method in the registration information, it extracts information on project implementation details from the registration information, determines whether the extracted information overlaps with the project implementation details related to the registration request; if it determines that the extracted information does not overlap with the project implementation details related to the registration request, it associates the project implementation details related to the registration request with the method that brings about greenhouse gas emission, reduction, or absorption related to the registration request and adds them to the registration information. The registration management system of claim 1 .

4. The computing device determine whether map information including the location where greenhouse gas emissions, reductions, or absorptions will occur is associated with the registration request, and if it is determined that map information including the location where greenhouse gas emissions, reductions, or absorptions will occur is associated with the registration request, convert the map information into location information in the coordinate system that represents the location, based on the map information, determine whether the converted location information overlaps with the location information in the registration information, and if it is determined that the area indicated by the converted location information does not overlap with the area indicated by the location information in the registration information, store the implementation content related to the registration request and the converted location information in the storage device in association with each other; The registration management system of claim 1 .

5. The computing device generates blockchain data including registration information to which the information on the object or the converted location information has been added, and stores the generated blockchain data in each of the information processing devices associated with the registration request and the registration information. The registration management system of claim 1 .

6. The computing device If it is determined that the entity that causes the emission, reduction or absorption of greenhouse gases in the registration request does not match the entity that causes the emission, reduction or absorption of greenhouse gases in the registration information, an identification number is added to the registration information, which is set in association with the implementation details of the project in the registration request and the information on the entity that causes the emission, reduction or absorption of greenhouse gases in the registration request; If it is determined that the converted location information of the location of the registration request does not overlap with the location information in the coordinate system in the registration information, an identification number set in association with the implementation content of the project related to the registration request and the converted location information is added to the registration information; Accepting an input of an identification number from a user, and outputting the implementation details of the project related to the input identification number to an output device; The registration management system of claim 1 .

7. A registration management method using an information processing device including a storage device that stores, as registration information, details of a project related to greenhouse gas emissions, reductions, or absorption, in association with information on objects that cause greenhouse gas emissions, reductions, or absorption, or location information in a predetermined coordinate system that indicates a location where the greenhouse gas emissions, reductions, or absorption occurs, and a calculation device, the calculation device comprising: receiving a registration request containing details of a project related to greenhouse gas emissions or reduction or removal; determine whether or not information on an entity that causes greenhouse gas emissions, reductions or absorption is associated with the registration request, and if it is determined that information on an entity that causes greenhouse gas emissions, reductions or absorption is associated with the registration request, determine whether or not the entity that causes greenhouse gas emissions, reductions or absorption in the registration request matches the entity that causes greenhouse gas emissions, reductions or absorption in the registration information, and if it is determined that the entity that causes greenhouse gas emissions, reductions or absorption in the registration request does not match the entity that causes greenhouse gas emissions, reductions or absorption in the registration information, associate the implementation details of the project that is related to the registration request with the information on the entity that causes greenhouse gas emissions, reductions or absorption in the registration request and add them to the registration information; if it is determined that the registration request does not correspond to information on the object, it determines whether area information of a location where greenhouse gas emissions, reductions, or absorptions are brought about is associated with the registration request; if it is determined that the registration request corresponds to area information of a location where greenhouse gas emissions, reductions, or absorptions are brought about, it converts the area information of the location into location information in the coordinate system, determines whether the converted location information overlaps with the location information in the coordinate system in the registration information; if it is determined that the converted location information of the location of the registration request does not overlap with the location information in the coordinate system in the registration information, it executes an overlap confirmation process of correlating the implementation details of the project related to the registration request with the converted location information and adding it to the registration information. Registration management methods.

8. The storage device further stores, in the registration information, information on a period during which the greenhouse gas emissions, reductions, or absorptions will be achieved, in association with the implementation details; The computing device further determining whether or not the registration request is associated with information on a period during which greenhouse gas emissions, reductions, or absorption will occur, and if it is determined that the registration request is associated with information on a period during which greenhouse gas emissions, reductions, or absorption will occur, determining whether or not the period related to the registration request overlaps with a period in the registration information, and if it is determined that the period related to the registration request does not overlap with a period in the registration information, correlating the implementation details of the project related to the registration request with the information on the period during which greenhouse gas emissions, reductions, or absorption will occur related to the registration request and adding them to the registration information; The registration management method according to claim 7.

9. The storage device further stores, in the registration information, information on methods for emitting, reducing, or absorbing the greenhouse gas in association with the implementation details of the project; The computing device further compares information on the method that brings about greenhouse gas emission, reduction, or absorption, which is associated with the registration request, with information on the method in the registration information, thereby determining whether the method related to the registration request is similar to the method in the registration information; if it determines that the method related to the registration request is similar to the method in the registration information, it extracts information on project implementation details from the registration information, determines whether the extracted information overlaps with the project implementation details related to the registration request; if it determines that the extracted information does not overlap with the project implementation details related to the registration request, it associates the project implementation details related to the registration request with the method that brings about greenhouse gas emission, reduction, or absorption related to the registration request and adds them to the registration information. The registration management method according to claim 7.

10. The computing device determine whether map information including the location where greenhouse gas emissions, reductions, or absorptions will occur is associated with the registration request, and if it is determined that map information including the location where greenhouse gas emissions, reductions, or absorptions will occur is associated with the registration request, convert the map information into location information in the coordinate system that represents the location, based on the map information, determine whether the converted location information overlaps with the location information in the registration information, and if it is determined that the area indicated by the converted location information does not overlap with the area indicated by the location information in the registration information, store the implementation content related to the registration request and the converted location information in the storage device in association with each other; The registration management method according to claim 7.

11. The computing device generates blockchain data including registration information to which the information on the object or the converted location information has been added, and stores the generated blockchain data in each of the information processing devices associated with the registration request and the registration information. The registration management method according to claim 7.

12. The computing device If it is determined that the entity that causes the emission, reduction or absorption of greenhouse gases in the registration request does not match the entity that causes the emission, reduction or absorption of greenhouse gases in the registration information, an identification number is added to the registration information, which is set in association with the implementation details of the project in the registration request and the information on the entity that causes the emission, reduction or absorption of greenhouse gases in the registration request; If it is determined that the converted location information of the location of the registration request does not overlap with the location information in the coordinate system in the registration information, an identification number set in association with the implementation content of the project related to the registration request and the converted location information is added to the registration information; Accepting an input of an identification number from a user, and outputting the implementation details of the project related to the input identification number to an output device; The registration management method according to claim 7.

Images