Internet-based agricultural supply chain transaction scheduling method

Abstract

The invention relates to the technical field of informatization, and provides an agricultural supply chain transaction scheduling method based on the Internet. The method aims at solving the problems of information asymmetry, low logistics efficiency, unsmooth fund flow, difficulty in quality tracing and the like in a traditional agricultural supply chain. Through integrating functions of supplier information acquisition and verification, agricultural product information acquisition and classification, intelligent matching and bidding, order generation and payment, logistics scheduling and distribution, financial service, separate account management, quality tracing and the like, efficient management and transparent operation of an agricultural supply chain are realized. The method is suitable for a large-scale agricultural supply chain platform, the transaction efficiency is remarkably improved, the operation cost is reduced, the product quality is ensured, and the modernization and sustainable development of an agricultural supply chain are promoted. Through the innovative method, all links of the agricultural supply chain are optimized, the overall competitiveness is improved, the market response speed is increased, and powerful support is provided for transformation and upgrading of the agricultural industry.

Description

Technical Field

[0001] The present invention relates to the field of information technology and provides an Internet-based agricultural supply chain transaction scheduling method. Background Art

[0002] 1. Current Situation of Traditional Agricultural Supply Chain

[0003] The agricultural supply chain is an organic connection of all links from agricultural product production to consumption, involving multiple links such as production, processing, transportation, and sales. The traditional agricultural supply chain is still the main channel for the circulation of agricultural products in China, accounting for about 80% of the total sales of agricultural products in China. However, there are many problems in this supply chain model, which affect the circulation efficiency and quality safety of agricultural products. Specific problems include:

[0004] Poor Information Communication: In the traditional supply chain, there is a lack of an effective information sharing platform, resulting in a slow response of the supply side to market demand and an increase in logistics costs. The information asymmetry between suppliers and purchasers makes the supply-demand matching efficiency of agricultural products low, further exacerbating market fluctuations.

[0005] Backward Organizational Form: Agricultural production in many regions of China is mainly based on individual households or small-scale contracting, showing the characteristics of "small scale, large group, and fragmentation". This decentralized production model leads to a variety of miscellaneous agricultural products, scattered distribution, and inconsistent production standards, making it difficult to meet the supply needs of large-scale and continuous supply such as e-commerce. At the same time, there are also easy loopholes in supervision and after-sales service, affecting the quality and market reputation of agricultural products.

[0006] Logistics Problems: The logistics link in the traditional agricultural supply chain mainly relies on self-operated logistics, with high transportation costs, low informatization level, and large losses. The particularity of agricultural products (such as perishable and vulnerable to damage) requires efficient cold chain logistics support, but the traditional logistics system is difficult to meet these needs, resulting in serious losses of agricultural products during transportation and further increasing the circulation cost.

[0007] Single Market Channel: The traditional sales of agricultural and sideline products mainly rely on offline farmers' markets, wholesalers and other channels, and the application of emerging sales channels such as e-commerce is not extensive enough. This single market channel limits the sales scope of agricultural products, making it difficult to expand the market share and resulting in low circulation efficiency of agricultural products.

[0008] 2. Deficiencies of Existing Technologies

[0009] Although the existing agricultural supply chain management technologies have been improved in terms of informatization and logistics, there are still the following deficiencies:

[0010] Information silo problem: Existing supply chain platforms often lack a unified information sharing mechanism, resulting in ineffective information circulation among suppliers, purchasers, and logistics enterprises, which affects the collaborative efficiency of the supply chain.

[0011] Low level of intelligence: Existing supply chain platforms lack intelligent support in aspects such as transaction matching and logistics scheduling, making it difficult to dynamically adjust according to changes in market demand and supply chain resources, resulting in low transaction efficiency.

[0012] Lack of financial services: Most existing supply chain platforms do not fully integrate financial services, leading to poor capital flow in the supply chain. Suppliers and purchasers face great pressure in capital turnover, which affects the stability of the supply chain.

[0013] Incomplete quality traceability system: Existing supply chain platforms lack systematic support in the quality traceability of agricultural products, making it difficult to achieve full-process quality monitoring from production to consumption, which affects the quality safety and market reputation of agricultural products. Summary of the Invention

[0014] The purpose of the present invention is to integrate the participants in each link of the supply chain, and by using intelligent matching algorithms, operations research algorithms, and blockchain technology, it can efficiently coordinate the execution of business logic and data flow among various modules, improve the overall efficiency of the supply chain, reduce transaction costs, ensure product quality, and promote the modernization and sustainable development of the agricultural supply chain.

[0015] To achieve the above purpose, the present invention adopts the following technical means:

[0016] The present invention provides an Internet-based agricultural supply chain transaction scheduling method, including the following steps:

[0017] Step 1: Collect and verify the supplier information in the agricultural supply chain to obtain the verified supplier information.

[0018] Step 2: Collect and classify the agricultural product information for the verified supplier information obtained in Step 1 to obtain the classified agricultural product information.

[0019] Step 3: Perform intelligent matching and bidding on the classified agricultural product information obtained in Step 2 to obtain the matching and bidding results.

[0020] Step 4: Generate an order and perform payment processing on the matching and bidding results obtained in Step 3 to obtain the order payment result.

[0021] Step 5: Perform logistics scheduling and distribution processing on the order payment result obtained in Step 4 to complete the agricultural supply chain transaction scheduling.

[0022] Step 6: Process the order payment result obtained in Step 4 to provide financial product services and offer financial support.

[0023] Step 7: Conduct split account management on the financial product approval result obtained in Step 6 to complete fund allocation.

[0024] Step 8: Conduct quality traceability processing on the logistics distribution result completed in Step 5 to generate a quality report.

[0025] In the above technical solution, the sub-steps of Step 1 include:

[0026] Step 1.1: Collect and process supplier information to obtain supplier information.

[0027] Step 1.2: Conduct format verification and contact information verification processing on the supplier information obtained in Step 1.1 to obtain verified supplier information.

[0028] The supplier information collection and processing in Step 1.1 includes:

[0029] Step 1.1.1: Build a supplier information collection module based on the Spring Boot framework, mark the startup class with the @SpringBootApplication annotation, and enable component scanning and automatic configuration.

[0030] Step 1.1.2: Obtain the database connection pool through dependency injection and configure the database connection parameters, including the host address, username, and password.

[0031] Step 1.1.3: Configure the JPA framework for the database connection pool to obtain the data access interface SupplierInfoRepository for supplier information. This interface inherits from JpaRepository and implements operations for creating, reading, updating, and deleting supplier information. JpaRepository is the core interface provided by Spring Data JPA, which encapsulates common database operation methods, including creating, reading, updating, and deleting.

[0032] Step 1.1.3.1: Define and process the supplier information data model, create a supplier information entity class to obtain the supplier information data model.

[0033] Step 1.1.3.2: Persist the supplier information data model obtained in Step 1.1.3.1, create the SupplierInfoRepository interface and inherit JpaRepository to obtain the supplier information persistence interface.

[0034] Step 1.1.3.3: Perform CRUD operation configuration processing on the supplier information persistence interface obtained in Step 1.1.3.2 to implement the functions of creating, reading, updating, and deleting supplier information, and obtain a fully functional supplier information persistence interface;

[0035] In the above technical solution, the sub-steps of Step 2 include:

[0036] Step 2.1: Collect and process agricultural product information to obtain agricultural product information;

[0037] Step 2.2: Classify the agricultural product information obtained in Step 2.1 to obtain classified agricultural product information.

[0038] In the above technical solution, the classification processing of agricultural product information in Step 2.2 includes:

[0039] Step 2.2.1: Build an agricultural product information search engine based on Elasticsearch and configure the index and mapping relationship;

[0040] Step 2.2.2: Perform word segmentation processing on the collected agricultural product information and establish a full-text index;

[0041] Step 2.2.3: Classify according to agricultural product category, specification, and origin information and store it in the database.

[0042] In the above technical solution, the sub-steps of Step 3 include:

[0043] Step 3.1: Search and match agricultural product information based on Elasticsearch and sort it in combination with price and inventory factors;

[0044] Step 3.1.1: Initialize the intelligent matching product selection module to obtain an intelligent matching product selection module object;

[0045] Step 3.1.2: Search and match the agricultural product information to obtain a matching result;

[0046] Step 3.1.2.1: After the backend receives the product selection request submitted by the frontend, create a matchProducts method in the SmartMatchService class for processing;

[0047] Step 3.1.2.2: The matchProducts method uses Elasticsearch for full-text search based on the keywords, categories, and specification information input by the user to obtain agricultural product information that meets the conditions;

[0048] Step 3.1.2.3: Match and sort the search results, and sort them in combination with the relevance, price, and inventory factors of the products, including:

[0049] Agricultural products with lower prices are preferentially displayed;

[0050] Agricultural products with sufficient inventory are preferentially displayed;

[0051] Agricultural products with higher relevance are preferentially displayed.

[0052] Step 3.1.3: Return the matching results to the front end for the user to select;

[0053] Step 3.2: Build an auction module based on the RabbitMQ message queue to process the auction requests submitted by users;

[0054] Step 3.2.1: Perform initialization processing on the auction product selection module to obtain the auction product selection module object;

[0055] Step 3.2.1.1: Build the "Product Auction Selection Module" based on the Spring Boot framework, and create the ProductAuctionService class as the core control class;

[0056] Step 3.2.1.2: Obtain the database connection pool, message queue service, and user authentication service through dependency injection;

[0057] Step 3.2.1.3: Configure the relevant parameters of RabbitMQ in the application.yml file, including the address spring.rabbitmq.host of the RabbitMQ server, the port spring.rabbitmq.port of the RabbitMQ server, the login name spring.rabbitmq.username, and the password spring.rabbitmq.password.

[0058] Step 3.2.2: Verify and process the auction requests submitted by users to obtain the verified auction requests;

[0059] Step 3.2.2.1: After the back end receives the auction request submitted by the front end, create a processBid method in the ProductAuctionService class for processing;

[0060] Step 3.2.2.2: The processBid method verifies the user identity and bid information, including:

[0061] Check whether the user exists;

[0062] Check whether the user balance is sufficient to pay the auction amount;

[0063] Check whether the bidding amount meets the range specified by the platform.

[0064] Step 3.2.3: Send the verified bidding request to the message queue and update the bidding status;

[0065] Step 3.2.3.1: Package the bidding information into a message object, including product ID, bidding amount, and bidding time;

[0066] Step 3.2.3.2: Send the message to the specified message queue through RabbitMQ;

[0067] Step 3.2.3.3: Listen to the message queue in real time and update the bid information and bidding status of each product;

[0068] Step 3.3: Determine the winner according to the bidding algorithm and generate the bidding result.

[0069] Step 3.3.1: Initialize the bidding algorithm to obtain the bidding algorithm object;

[0070] Step 3.3.1.1: Define the core logic of the bidding algorithm, for example:

[0071] The basic supplier of the seller is A j , and the price of a certain commodity is X j yuan / ton, and the inventory is Y i tons;

[0072] The buyer and purchaser is B i , and the quantity of the commodity with the purchase intention is S i tons;

[0073] The platform adjusts the price to ε j yuan / ton according to purchasers of different levels. Therefore, the price of the commodity for this purchaser is:

[0074]

[0075] Step 3.3.2: Calculate the final price of each purchaser according to the bidding algorithm and determine the winner;

[0076] Step 3.3.2.1: Traverse all bidding requests and calculate the final price of each purchaser according to the bidding algorithm;

[0077] Step 3.3.2.2: Compare the final prices of each purchaser and determine the winner;

[0078] Step 3.3.3: Generate the bidding result and notify the relevant users;

[0079] Step 3.3.3.1: Store the information of the winning bidder in the database and update the bidding status to "Won the bid".

[0080] Step 3.3.3.2: Notify the winning bidder and other participants via in-site message or SMS.

[0081] Step 3.3.3.3: Display the bidding result after the front-end receives the notification.

[0082] In the above technical solution, the sub-steps of Step 4 include:

[0083] Step 4.1: Process the bidding result to generate order information.

[0084] Step 4.1.1: Generate order information based on the bidding result, including order number, commodity information, price, and quantity.

[0085] Step 4.1.2: Store the order information in the database and generate a unique order ID.

[0086] Step 4.1.3: Display the order information through the front-end page for the user to confirm.

[0087] Step 4.2: Process the payment for the order information obtained in Step 4.1 to obtain the order payment result.

[0088] Step 4.2.1: Integrate third-party payment interfaces, including Alipay and WeChat Pay, and configure payment parameters.

[0089] Step 4.2.2: Receive the user's payment request and verify the payment information.

[0090] Step 4.2.3: Call the third-party payment interface to complete the payment and update the order status to "Paid".

[0091] In the above technical solution, the sub-steps of Step 5 include:

[0092] Step 5.1: Process the order payment result for logistics scheduling to obtain logistics scheduling information.

[0093] Step 5.11: Generate a logistics scheduling task based on the order information, including delivery address, delivery method, and delivery time.

[0094] Step 5.1.2: Call the logistics management system interface to allocate delivery resources.

[0095] Step 5.1.3: Real-time track the logistics status and update the order logistics information.

[0096] Step 5.2: Process the logistics scheduling information obtained in Step 5.1 for delivery to complete the agricultural supply chain transaction scheduling.

[0097] Step 5.2.1: Arrange delivery vehicles and personnel according to the logistics scheduling tasks;

[0098] Step 5.2.2: Monitor the delivery process in real time to ensure timely delivery;

[0099] After the delivery is completed, update the order status to completed and notify the user.

[0100] In the above technical solution, Step 6 includes the following steps:

[0101] Step 6.1: Build the "Financial Product Service" module based on the Spring Cloud microservice architecture and complete the module initialization;

[0102] Step 6.2: Receive loan applications and verify the application information, including amount range, basic enterprise information, verification code, etc.;

[0103] Step 6.3: Obtain multi-dimensional risk control data through the risk control data interface and calculate the risk score;

[0104] Step 6.4: Conduct manual review, generate loan contracts and determine the loan amount, term, and interest rate;

[0105] Step 6.5: Execute the loan disbursement operation to complete the financial transaction.

[0106] In the above technical solution, Step 7 includes the following steps:

[0107] Step 7.1: Build the "Profit Distribution Management Module" based on the Spring Boot framework and configure the database connection and third-party payment interface.

[0108] Step 7.2: Calculate the profit distribution amounts for the suppliers and the platform according to the financial product approval results and the order amount.

[0109] Step 7.3: Record the profit distribution information in the database and complete the profit distribution payment.

[0110] Step 7.4: Update the profit distribution status and notify the relevant parties.

[0111] In the above technical solution, Step 8 includes the following steps:

[0112] Step 8.1: Build the "Quality Traceability Module" based on the Spring Boot framework and configure the database connection and quality information collection service.

[0113] Step 8.2: Collect quality information during the production process of agricultural products, including production date, production process, raw material sources, etc.

[0114] Step 8.3: Associate the quality information with the order information and supplier information to generate a quality traceability report.

[0115] Step 8.4: Use the AES encryption algorithm to encrypt and store the quality traceability data to ensure data security;

[0116] Step 8.5: Generate a quality report and store it in the database for users to query and download.

[0117] Since the present invention adopts the above technical means, it has the following beneficial effects:

[0118] 1. Supplier information collection and verification

[0119] Build a supplier information collection module through the Spring Boot framework, and combine it with the Vue.js front-end framework to achieve two-way data binding, solving the problem of information asymmetry in the traditional agricultural supply chain. Through format verification and contact information verification, the accuracy and reliability of supplier information are ensured, achieving the effect of improving the transparency and trust of supply chain information.

[0120] 2. Agricultural product information collection and classification

[0121] Build an agricultural product information search engine based on Elasticsearch, and combine word segmentation processing and full-text indexing technology to solve the problem of chaotic and difficult-to-rapidly retrieve agricultural product information. By classifying and storing agricultural product information, rapid retrieval and accurate matching of agricultural product information are realized, improving the efficiency of information processing in the supply chain.

[0122] 3. Intelligent matching and bidding processing

[0123] Search and match agricultural product information through Elasticsearch, and sort it in combination with factors such as price and inventory, solving the problem of low efficiency in supply and demand matching in the traditional supply chain. Combine the RabbitMQ message queue to process bidding requests, realizing an efficient bidding process, achieving the effect of improving transaction efficiency and fairness.

[0124] 4. Order generation and payment processing

[0125] Build a payment settlement module based on the Spring Boot framework, and integrate third-party payment interfaces such as Alipay and WeChat Pay to solve the problems of complex payment processes and low efficiency in the traditional supply chain. Through automated order generation and payment processing, the rapid completion of the transaction process is realized, improving the user experience and transaction efficiency.

[0126] 5. Logistics scheduling and distribution processing

[0127] The logistics distribution service module is built through the Spring Boot framework, and the distribution resources are scheduled in combination with the logistics management system, solving the problems of high cost and low efficiency in traditional logistics. By tracking the logistics status in real time, the quality and timeliness of agricultural products during transportation are ensured, achieving the effects of reducing logistics costs and improving distribution efficiency.

[0128] 6. Financial Product Service Processing

[0129] The financial product service module is built based on the Spring Cloud microservice architecture, and in combination with the risk control data interface and the SMS verification code service, the problem of unsmooth capital flow in the supply chain is solved. By providing convenient financial services such as loan approval and loan disbursement operations, the capital flow in the supply chain is promoted, and the stability of the supply chain is enhanced.

[0130] 7. Revenue Sharing Management Processing

[0131] The revenue sharing management module is built through the Spring Boot framework, and in combination with the third-party payment interface and the message queue service, the problem of complex capital allocation in the supply chain is solved. Through automated revenue sharing calculation and payment, the fairness and transparency of the capital allocation between suppliers and the platform are ensured, achieving the effect of improving the efficiency of capital management.

[0132] 8. Quality Traceability Processing

[0133] The quality traceability module is built based on the Spring Boot framework, and in combination with the AES encryption algorithm, the quality traceability data is encrypted and stored, solving the problem of difficult quality traceability of agricultural products. By collecting and associating the quality information in production, logistics and other links, the whole-process quality monitoring from production to consumption is realized, achieving the effect of ensuring the quality and safety of agricultural products.

[0134] 9. Improvement of the Overall Efficiency of the Supply Chain

[0135] By integrating information flow, logistics and capital flow, and in combination with intelligent matching algorithms, operations research algorithms and blockchain technology, the problems of information silos and low degree of intelligence in traditional supply chains are solved. Through one-stop services, the overall efficiency of the supply chain is significantly improved, transaction costs are reduced, product quality is guaranteed, and the modernization and sustainable development of the agricultural supply chain are promoted. Brief Description of the Drawings

[0136] Figure 1 This is a simple flowchart of the present invention. Detailed Embodiments

[0137] A detailed description of the embodiments of the present invention will be given below. Although the present invention will be described and illustrated in conjunction with some specific embodiments, it should be noted that the present invention is not limited to these embodiments only. On the contrary, any modifications or equivalent replacements made to the present invention shall be covered within the scope of the claims of the present invention.

[0138] In addition, in order to better illustrate the present invention, numerous specific details are given in the following specific embodiments. Those skilled in the art will understand that the present invention can be implemented without these specific details.

[0139] Aiming at the problems studied above, the object of the present invention is to provide a platform that covers multiple key links of supply chain management. Through this platform, upstream suppliers can publish agricultural product information, downstream purchasers can compare and select the required agricultural products, financial institutions can enter the platform to provide financial services for suppliers and purchasers with financial service needs. At the same time, the platform also provides one-stop services such as information release, intelligent trading matching and matchmaking mechanism, group buying and distribution, call auction, payment settlement, logistics distribution, and quality traceability.

[0140] The present invention provides an Internet-based agricultural supply chain transaction scheduling method, including the following steps:

[0141] Step 1: Supplier registration: The platform invites suppliers to register on the platform and provides technical support for suppliers, including data interfaces, API access, etc., to facilitate suppliers to perform operations such as product addition, product management, product query, employee management in the background, purchaser invitation, and construction of a private domain supplier mall.

[0142] As an implementation, the present invention further describes the detailed steps of Step 1 as follows:

[0143] Step 1.1: Build a "Supplier Invitation Module" based on the Spring Boot framework, mark the startup class with the @SpringBootApplication annotation to enable component scanning and automatic configuration, create a class named SupplierInvitationModule as the core control class, obtain the required service components through dependency injection, such as database connection pool, email sending service, SMS sending service, etc., complete the initialization of the module to obtain the supplier invitation module object, which is responsible for coordinating the execution of the business logic and data flow of the entire invitation process. Introduce Spring Security for security authentication and authorization to ensure that only users with specific permissions (such as platform administrators or procurement leaders) can access and use the supplier invitation function. By configuring user roles and permissions, unauthorized operations are prevented to ensure system security.

[0144] Step 1.2 After the backend receives the invitation information submitted by the frontend, create a validateSupplierData method in the SupplierInvitationService class. Use regular expressions to validate the format of the supplier name (Pattern.compile(″^[a-zA-Z0-9\\s]+$").matcher(supplier.getName()).matches(), ensuring it only contains letters, numbers, and spaces), and use PhoneNumberUtil.getInstance0.isValidNumber(phoneNumber) (Google's libphonenumber library) to validate the phone number in the contact information. If any validation fails, return the error information to the frontend in JSON format through the @ResponseBody annotation of Spring MVC, prompting the user to modify the corresponding field; if the validation passes, continue with the subsequent invitation process.

[0145] Step 1.3 Build the framework of the supplier product management system. Based on the microservices architecture, build the "supplier product management system". In the product management microservice, use the MySQL database to store product-related information, and configure the database connection parameters in the application.yml file, similar to the module for inviting suppliers. Use JPA to define the product entity classes Product (including attributes such as product ID, name, description, price, picture URL, category ID, supplier ID, stock quantity, status, etc.), Category (including attributes such as category ID, category name, parent category ID, etc.), and Stock (including attributes such as stock ID, product ID, stock quantity, stock warning threshold, etc.). Configure the relationships between entity classes through annotations such as @Entity, @OneToMany, @ManyToOne, etc. For example, a product belongs to a category (@ManyToOne), a category contains multiple products (@OneToMany), and a product corresponds to a stock record (@OneToOne), etc. Create the ProductRepository, CategoryRepository, and StockRepository interfaces that inherit from JpaRepository to implement basic CRUD operations on product, category, and stock data. At the same time, use the query method naming convention of JPA or the @Query annotation to write complex query statements to meet the data query requirements in various product management scenarios, such as querying products by category, querying products by supplier, etc., to ensure efficient data storage and fast retrieval.

[0146] Step 2. Conduct agricultural product information collection and classification processing on the verified supplier information obtained in Step 1 to obtain classified agricultural product information;

[0147] Step 2.2.1. Build an agricultural product information search engine based on Elasticsearch and configure the index and mapping relationship;

[0148] Step 2.2.2. Perform word segmentation processing on the collected agricultural product information and establish a full-text index;

[0149] Step 2.2.3. Classify according to the agricultural product category, specification, and origin information and store it in the database.

[0150] As an embodiment, the following further explanations are made:

[0151] Intelligent matching product selection method

[0152] Backend architecture setup: Build the "Intelligent Matching Product Selection Module" based on the Spring Boot framework. Use the `@SpringBootApplication` annotation to mark the startup class and enable component scanning and auto-configuration. Create a class named `SmartMatchService` as the core control class and obtain the required service components through dependency injection. This includes a database connection pool (using HikariCP, configuring parameters such as the connection pool size, maximum connection number, and minimum idle connection number to ensure stable and efficient database connections), a search engine service (such as Elasticsearch, used for full-text search and indexing of product information to achieve fast and accurate product matching), and a data caching service (such as Redis, caching product data and search results to improve system response speed). Configure the database connection parameters in the applicaion.yml file, including spring.datasource.url, spring.datasource.username, spring.datasource.password, etc. At the same time, configure the relevant parameters of Elasticsearch

[0153] Data processing and matching: After the backend receives the product selection request submitted by the frontend, the matchProducts method in the SmartMatchService class processes it. First, use Elasticsearch to search according to the information such as keywords, categories, and specifications entered by the user. Then, perform matching and sorting based on the search results. A custom matching algorithm can be used to sort by combining factors such as product relevance, price, and inventory. For example

[0154]

[0155] Finally, return the matching results to the front end. After receiving the data, the front end displays it on the page for users to select.

[0156] Step 3: Perform intelligent matching and bidding processing on the classified agricultural product information obtained in Step 2 to obtain matching and bidding results;

[0157] Step 3.1: Search and match the agricultural product information based on Elasticsearch, and sort it in combination with price and inventory factors;

[0158] Step 3.1.1: Initialize the intelligent matching product selection module to obtain an object of the intelligent matching product selection module;

[0159] Step 3.1.1.1: Build the "intelligent matching product selection module" based on the Spring Boot framework, mark the startup class with the @SpringBootApplication annotation, and enable component scanning and automatic configuration;

[0160] Step 3.1.1.2: Create a class named SmartMatchService as the core control class, and obtain the required service components through dependency injection, including a database connection pool, an Elasticsearch search engine service for full-text search and indexing of product information to achieve fast and accurate product matching, and a data caching service;

[0161] Step 3.1.1.3: Configure the database connection parameters in the application.yml file, and at the same time configure the relevant parameters of Elasticsearch;

[0162] Step 3.1.2: Search and match the agricultural product information to obtain matching results;

[0163] Step 3.1.2.1: After the back end receives the product selection request submitted by the front end, create a matchProducts method in the SmartMatchService class for processing;

[0164] Step 3.1.2.2: The matchProducts method uses Elasticsearch for full-text search based on the keywords, categories, and specification information input by the user to obtain agricultural product information that meets the conditions;

[0165] Step 3.1.2.3: Match and sort the search results, and sort them in combination with the relevance, price, and inventory factors of the products, including:

[0166] Agricultural products with lower prices are displayed first;

[0167] Agricultural products with sufficient inventory are preferentially displayed;

[0168] Agricultural products with higher relevance are preferentially displayed.

[0169] Step 3.1.3: Return the matching results to the front end for users to select;

[0170] Step 3.2: Build an auction module based on the RabbitMQ message queue to process the auction requests submitted by users;

[0171] Step 3.2.1: Perform initialization processing on the auction product selection module to obtain the object of the auction product selection module;

[0172] Step 3.2.1.1: Build the "Product Auction Product Selection Module" based on the Spring Boot framework, and create the ProductAuctionService class as the core control class;

[0173] Step 3.2.1.2: Obtain the database connection pool, message queue service, and user authentication service through dependency injection;

[0174] Step 3.2.1.3: Configure the relevant parameters of RabbitMQ in the application.yml file, including the address of the RabbitMQ server spring.rabbitmq.host, the port of the RabbitMQ server spring.rabbitmq.port, the login name spring.rabbitmq.usemame, and the password spring.rabbitmq.password.

[0175] Step 3.2.2: Perform verification processing on the auction requests submitted by users to obtain the verified auction requests;

[0176] Step 3.2.2.1: After the back end receives the auction request submitted by the front end, create a processBid method in the ProductAuctionService class for processing;

[0177] Step 3.2.2.2: The processBid method verifies the user identity and bid information, including:

[0178] Check whether the user exists;

[0179] Check whether the user balance is sufficient to pay the auction amount;

[0180] Check whether the auction amount meets the range specified by the platform.

[0181] Step 3.2.3: Send the verified auction requests to the message queue and update the auction status;

[0182] Step 3.2.3.1: Package the bidding information into a message object, including product ID, bidding amount, and bidding time;

[0183] Step 3.2.3.2: Send the message to the specified message queue through RabbitMQ;

[0184] Step 3.2.3.3: Monitor the message queue in real time and update the bid information and bidding status of each product;

[0185] Step 3.3: Determine the winner according to the bidding algorithm and generate the bidding result.

[0186] Step 3.3.1: Initialize the bidding algorithm to obtain the bidding algorithm object;

[0187] Step 3.3.1.1: Define the core logic of the bidding algorithm, for example:

[0188] The basic supplier of the seller is A i , and the price of a certain commodity of it is X i yuan / ton, and the inventory is Y i tons;

[0189] The purchaser of the buyer is B i , and the quantity of the commodity with the purchase intention is S i tons;

[0190] The platform adjusts the price to ε j yuan / ton according to purchasers of different levels. Therefore, the price of the commodity for this purchaser is:

[0191]

[0192] Step 3.3.2: Calculate the final price of each purchaser according to the bidding algorithm and determine the winner;

[0193] Step 3.3.2.1: Traverse all bidding requests and calculate the final price of each purchaser according to the bidding algorithm;

[0194] Step 3.3.2.2: Compare the final prices of each purchaser and determine the winner;

[0195] Step 3.3.3: Generate the bidding result and notify the relevant users;

[0196] Step 3.3.3.1: Store the information of the winner in the database and update the bidding status to "awarded";

[0197] Step 3.3.3.2: Notify the winner and other participants through in-site messages or text messages;

[0198] Step 3.3.3.3: After the front end receives the notification, it displays the bidding result.

[0199] As an implementation, the following further explanations are made:

[0200] Build the "Product Bidding and Product Selection Module" based on the Spring Boot framework, and create the ProductAuctionService class as the core control class. Obtain the database connection pool (the same as the intelligent matching module), the message queue service (such as RabbitMQ, used to send and receive bidding messages), and the user authentication service (such as Spring Security, to ensure the legal identity of users) through dependency injection. Configure the relevant parameters of RabbitMQ in the application.yml file, such as spring.rabbitmq.host, spring.rabbitmq.port, spring.rabbitmq.username, and spring.rabbitmq.password.

[0201] Bidding algorithm: The basic supplier of the seller is A i , and the price of a certain commodity is X i yuan / ton, and the inventory is Y i tons;

[0202] The buyer and purchaser is B i , and the quantity of the commodity with the purchase intention is S i tons;

[0203] The platform adjusts the price to ε j yuan / ton according to purchasers of different levels. Therefore, the price of the commodity for this purchaser is:

[0204]

[0205] After the bidding process processing backend receives the bidding request submitted by the front end,

[0206] it is processed by the processBid method in the ProductAuctionService class. First, verify the user identity and bid information. For example:

[0207]

[0208]

[0209] Then, send the bid information to the RabbitMQ message queue. For example

[0210] Message message = new Message();

[0211] message.setProductId(productId);

[0212] message.setBidAmount(bidAmount);

[0213] message.setBidTime(new Date());

[0214] rabbitTemplate.send("product_auction", message);

[0215] During the bidding process, the platform continuously monitors the message queue and updates the bid information and bidding status of each product. When the bidding deadline arrives, the winner is determined, and finally, the winner and other participants are notified. After receiving the notification, the front end displays the bidding results.

[0216] Group-buying and distribution product selection method

[0217] Subsequently, based on the Spring Boot framework, a "group-buying and distribution product selection module" is built, and the GroupBuyService class is created as the core control class. Obtain the database connection pool (the same as the intelligent matching module), email sending service (used to send group-buying invitations and notifications), and user authentication service (such as Spring Security) through dependency injection. Configure the database connection parameters and related parameters of the email sending service in the `application.yml` file, such as `spring.mail.host`, `spring.mail.port`, `spring.mail.username`, `spring.mail.password`.

[0218] After the group-buying process handling backend receives the group-buying request submitted by the front end, the `processGroupBuy` method in the GroupBuyService class processes it. First, the user identity and group-buying information are verified.

[0219] During the group-buying process, the backend continuously updates the group-buying progress and participant information. When the group-buying deadline arrives, the group-buying result is determined.

[0220] Finally, the group-buying participants are notified. After receiving the notification, the front end displays the group-buying results.

[0221] Step 4: Generate an order and process the payment for the matching and bidding results obtained in Step 3 to obtain the order payment result;

[0222] Step 4.1: Build a payment and settlement module based on the Spring Boot framework and create a PaymentService class. Obtain the database connection pool (using HikariCP to ensure stable and efficient database connections) and third-party payment interfaces (such as Alipay, WeChat Pay, etc.) through dependency injection. Configure the relevant parameters for third-party payments in the application.yml file, such as alipay.gatewayUrl, alipay.appId, alipay.privateKey for Alipay, and wxpay.appId, wxpay.partnerKey, wxpay.notifyUrl for WeChat Pay, etc.

[0223] Step 4.2: On the front-end page, use the Vue.js framework to create a payment page. The user selects a payment method (such as Alipay, WeChat Pay), fills in the payment amount, order information, etc. Implement two-way data binding through Vue's v-model directive and call the back-end interface to initiate a payment request. After the back-end receives the front-end payment request, it verifies the payment information. For example, check whether the order amount is consistent with the user input and whether the user balance is sufficient for payment. If the verification passes, call the third-party payment interface for payment.

[0224] Step 4.3: After the third-party payment is successful, the back-end receives the payment result notification, updates the order status, and records the payment information in the database.

[0225] Step 5: Perform logistics scheduling and distribution processing on the order payment result obtained in Step 4 to complete the agricultural supply chain transaction scheduling;

[0226] Step 5.1: Build a logistics distribution service module based on the Spring Boot framework and create a `LogisticsService` class as the core control class. Obtain a database connection pool through dependency injection (using HikariCP, configure parameters such as the connection pool size, maximum number of connections, and minimum number of idle connections to ensure stable and efficient database connections), and a logistics information management system (such as a warehousing management system, transportation management system, etc.). Configure database connection parameters in the `application.yml` file, including `spring.datasource.url`, `spring.datasource.username`, and `spring.datasource.password`. Use Spring Data JPA for database operations, create a `LogisticsRepository` interface, and inherit from `JpaRepository` to implement CRUD operations on logistics-related data. For example, query order information `@Query("SELECT o FROM Order o WHERE o.orderId = :orderId")`, and query inventory information `@Query("SELECT s FROM Stock s WHERE s.productId = :productId")`.

[0227] Step 5.2: Order processing: The `LogisticsService` class receives the order ID submitted by the front end, queries the order details from the database, including order amount, product types, quantity, customer information, etc. Inject `LogisticsRepository` through `@Autowired` and call the `findById` method to obtain the order object `Order order = logisticsRepository.findById(orderId).orElse(null)`.

[0228] Step 6: Perform financial product service processing on the order payment result obtained in Step 4 to provide financial support.

[0229] Step 6.1: Build the "Financial Product Service" module based on the Spring Cloud microservices architecture. Create a startup class named `LoanServiceApplication` and use the @SpringCloudApplication annotation to enable functions such as service registration and discovery, component scanning, and configuration loading. This annotation integrates @EnableDiscoveryClient (used to register services into service discovery components such as Consul and Eureka, enabling mutual location and invocation between services, facilitating collaboration with other microservices on the platform, for example, interacting with the order management microservice to obtain enterprise transaction flow information for auxiliary evaluation) and @SpringBootApplication (completing the basic configuration of the Spring Boot framework, enabling automatic configuration and component scanning, and introducing basic dependencies such as database connection pools and logging components).Introduce a series of key components through dependency injection: Select HikariCP as the database connection pool and finely configure its parameters in the application.yml file. For example, spring.datasource.hikari.minimum-idle=5 ensures that the number of idle connections maintains a basic level, avoiding performance overhead caused by frequent creation and destruction of connections. spring.datasource.hikari.maximum-pool-size=20 limits the maximum number of connections to prevent resource exhaustion. At the same time, configure the connection timeout: spring.datasource.hikari.connection-timeout=30000 (in milliseconds) to ensure that connection requests are responded to within a reasonable duration; the risk control data interface service, which interfaces with professional risk control data providers based on the HTTP protocol. By configuring the API key (such as riskDataApiKey: your_api_key), request headers (setting specific Content-Type, Authorization, etc.), and call frequency limits (using Guava's RateLimiter class, such as RateLimiter.create(5) indicating a maximum of 5 requests per second), prevent being blocked by the risk control data source due to excessive requests, while ensuring the timeliness and stability of data, and obtain external risk control data in real time for accurate risk assessment; the SMS verification code service, which integrates Tencent Cloud SMS or Alibaba Cloud SMS services, etc. Configure the SMS signature (such as "[Supply Chain Platform Name 1") and template ID (corresponding to different business scenarios, such as the application verification code template, loan notice template, etc.) for identity verification in links such as user application and key information modification to ensure operation safety; the electronic contract signing service interface, introduce the SDKs of well-known third-party electronic contract platforms such as Fadada and Shangshangqian, add dependencies and configure relevant account information (such as appId: your_app_id, secretKey: your_secret_key of the Fadada platform) in the pom.xml file, and use it to efficiently generate and sign contracts after subsequent approval. Complete the module initialization to obtain a financial service object, which overall manages the business process and coordinates each component to complete a series of operations from application to loan disbursement. At the same time, use Spring CloudConfig to achieve centralized management of configurations, create a configuration repository (which can be based on Git, store configuration files such as application.yml in it, and set different branches corresponding to development, testing, production, etc. environments), facilitating quick switching of configuration parameters in different environments and ensuring system flexibility.Introduce Spring Security OAuth2 for user authentication and authorization. Combine with the platform's user system to allocate different quota permission scopes for different roles (such as ordinary suppliers, high-quality suppliers, large platform customers, etc.). For example, the initial quota ceiling for ordinary suppliers is 100,000, and for high-quality suppliers it is 500,000. By configuring the relevant rules of the OAuth2 client, resource server, and authorization server, define the authorization policies for different roles in the authorization server configuration. For example, use the Role-Based Access Control (RBAC) model to assign specific permission sets to each role (permissions are marked on relevant methods through the @PreAuthorize annotation, such as `@PreAuthorize("hasRole('ROLE_SUPPLIER_NORMAL')")` to restrict access for the ordinary supplier role), ensuring that only legitimate users within the quota permissions can initiate and operate the process, safeguarding the security of financial transactions.

[0230] Step 6.2: After the back-end receives the application submitted by the front-end, create a validateLoanApplication method in the LoanApplicationService class. First, perform a range check on the amount. Combine the quota permissions corresponding to the user role to determine whether the applied amount is within the allowed range (for example, if an ordinary supplier applies for an amount greater than 100,000, an error will be returned), and use the logic `if(loanApplication.getLoanAmount()>user.getLoanLimit()){return false;}` for judgment; perform format verification on the basic enterprise information. For example, check whether the enterprise name conforms to the specification (`Pattern.compile(″^[a-zA-Z0-9\\s]+$″).matcher(enterpriseName).matches()`), and whether the registered address is valid (verify the authenticity of the address by calling the map service API in reverse. For example, use the Baidu Map API `BaiduMapClient.getInstance().geocoding(enterpriseAddress).getResult().isValid()` to determine whether the address is resolvable and valid); use the SMS verification code service to verify whether the verification code submitted by the user is correct (`smsVerificationService.verifyCode(userId, enteredCode)`). If any one of the validations fails, return the error information to the front-end in JSON format through the `@ResponseBody` annotation of Spring MVC, prompting the user to modify the corresponding fields. If the validation passes, encapsulate the application data into a `LoanApplication` entity object and use the `LoanApplicationRepository.save(loanApplication)` method to persistently store it in the application record table of the database, and enter the subsequent approval process. During the data verification process, if it is found that the user submits applications frequently (for example, submits more than 3 times within 1 hour, judged by querying the recent application records in the database and counting the number of times), a risk control warning will be triggered, the user's application process will be suspended, and at the same time, the artificial customer service will be notified to intervene and verify the situation to prevent malicious applications or misoperations, and ensure the reasonable utilization of system resources and controllable financial risks.

[0231] Step 6.3: When the application data is successfully stored in the database, the risk control review process is automatically triggered. In the `RiskControlService` class, first, multi-dimensional risk control data of the applicant is obtained in real-time through the risk control data interface service, including but not limited to the frequency of enterprise industrial and commercial information changes (obtained from the industrial and commercial data platform. If there are frequent changes recently, it may imply unstable operation. By setting a scheduled task to call the industrial and commercial data interface to query the change records every 1 day, implemented using the `@Scheduled(cron=″0 0 0 * * *″)` annotation. If the number of changes exceeds 3 times in the past 3 months, a risk factor is marked), judicial litigation records (querying the court public information system, the risk of outstanding litigation is relatively high. By docking with the public API of the Supreme People's Court's Judgment Documents Network, retrieving litigation information based on the enterprise name or unified social credit code. If there are outstanding cases, details such as the case type, involved amount, plaintiff and defendant are recorded as key bases for risk assessment), tax payment situation (docking with the tax department data interface, the tax arrears situation affects credit. Using the e-tax bureau interface provided by the State Taxation Administration, querying the enterprise's tax declaration and payment records in the past 1 year. If the tax arrears amount exceeds a certain threshold, such as 50,000 yuan, it is regarded as a high-risk signal), industry credit rating (calling data from professional industry credit institutions, such as China Chengxin International Credit Rating Co., Ltd. and Dagong Global Credit Rating Co., Ltd., obtaining the relative credit ranking and score of the enterprise's industry by industry classification through their open APIs, setting industry credit weights in combination with the platform's own risk preferences, and integrating them into the comprehensive risk assessment system), etc. Based on this data, combined with the internally preset risk control model (for example, a scoring model constructed based on logistic regression or decision tree algorithms, and the model training data comes from past successful and failed cases, continuously optimizing and adjusting parameters.The training process is carried out on a dedicated big data processing platform such as Hadoop or Spark, leveraging a vast amount of historical data to improve the model's accuracy. By retraining regularly, such as once a quarter, the model is ensured to adapt to market changes. Calculate the applicant's risk score, such as `riskScore = riskModel.calculateScore(creditData)`. If the risk score is lower than the set threshold (e.g., 60 points, and the threshold is dynamically adjusted based on historical default rate data. By continuously monitoring historical default situations and statistically analyzing the default probabilities in different risk score segments, when it is found that the default rate in a certain risk score segment rises by more than 10%, the threshold is adjusted in a timely manner), then update the review status of the application to `REJECTED`, and record the detailed rejection reason (such as "The enterprise has outstanding lawsuits and a high risk") in the review remarks field of the database, and update the database record through `LoanApplicationRepository.save(updatedLoanApplication)`. If the risk score meets the standard, it enters the manual review process. Send a review notice to the platform reviewers (through the in-site message system, insert an in-site message record in the database, mark the reviewer ID, message content, and sending time, and the reviewers can view it when they log in). At the same time, push the application materials to the review workbench to facilitate the reviewers to review the materials and make judgments. In the risk control review process, key information such as the source of risk control data acquisition, model calculation process and results, and review status changes is recorded throughout the process in an independent risk control log table for subsequent traceability, auditing, and model optimization, ensuring the transparency and reliability of the risk control process.

[0232] Step 6.4: During the manual review stage, the auditor logs in to the audit workbench of the platform (an independent front-end page developed based on Vue.is, which interacts with the back-end through Axios) to view the detailed information of the application, including company introduction, financial statements (if any, through the file upload component, the back-end uses Apache POI and other tools to parse Excel format financial statement data and store relevant indicators, such as total assets, total liabilities, and owner's equity in the balance sheet, operating income and net profit in the income statement, etc. These indicators are used to build a financial ratio analysis system to assist in judging the company's debt-paying ability, profitability, and operating ability, such as debt-paying ability ratio = total liabilities / total assets. If the ratio is too high, it may indicate that the company has a greater financial risk), explanation of the purpose of the application amount, etc. The auditor makes a comprehensive judgment based on these materials and the risk control audit results, combined with his own experience. If he thinks the application is reasonable, he can enter the recommended amount on the audit page (it must be within the user role's amount authority) and click the audit pass button. After the back-end `LoanApprovalService` receives the audit result, it first updates the application's audit status to `APPROVED`, and then creates a `Loan` entity object based on the recommended amount, sets the amount, term, annual interest rate and other attributes. The annual interest rate is determined based on factors such as market interest rate level, corporate risk rating and platform funding cost (such as 8% annual interest rate for low-risk high-quality enterprises and 12% annual interest rate for high-risk ordinary enterprises. The specific calculation method can refer to the industry benchmark interest rate and the risk adjustment coefficient. The risk adjustment coefficient is obtained by mapping the risk score output by the risk control model. For example, a risk score of 80-100 points corresponds to a risk adjustment coefficient of 0.8, 60-80 points corresponds to 1.2, etc.), and stores the information in the database through `LoanRepository.save(loan)`, and generates a repayment plan at the same time (based on the amount, term, and annual interest rate, using financial computing libraries such as `Apache Commons Math` calculates the principal, interest, and repayment date of each repayment period, etc., and encapsulates them into the RepaymentPlan entity class, which is associated with the Loan entity class through @OneToMany`. The calculation formula is as follows: principal of each repayment period = amount / term (month), interest of each repayment period = balance × annual interest rate / 12, and the repayment date is a fixed date of each month or as agreed in the contract to ensure that the repayment plan is accurate and reasonable), and sends an approval notification to the applicant (via SMS notification, using third-party SMS gateways such as Alibaba Cloud SMS Service or Tencent Cloud SMS Service, configuring notification templates, and sending SMS messages containing key information such as amount, term, and repayment plan; at the same time, sending an internal message, inserting a record in the internal message table to facilitate the applicant to log in and view detailed information). The approval process ends here and enters the loan release stage.During the manual review process, if the reviewer has questions about the application materials, they can use the built-in instant messaging tool on the platform (implemented based on WebRTC or a third-party instant messaging SDK) to communicate with the applicant in real time, obtain further explanations or supplementary materials, improve the review efficiency and accuracy, and at the same time record the communication content in the review remarks field for subsequent traceability).

[0233] Step 6.5: The loan disbursement link is responsible for the `LoanDisbursementService`. After the approval is passed and the repayment plan is generated, this service first cooperates with financial institutions on the platform (such as banks or third-party payment platforms) through docking.

[0234] Step 7: Conduct ledger management on the financial product approval results obtained in Step 6 to complete the fund allocation.

[0235] Step 7.1: Build an "accounting management module" based on the Spring Boot framework, and create the AccountingService class as the core control class. Obtain the database connection pool (using HikariCP to ensure stable and efficient database connections), third-party payment interfaces (such as Alipay, WeChat Pay, etc.), and message queue services (such as RabbitMQ for processing accounting-related information) through dependency injection. Configure the database connection parameters in the application.yml file, including `spring.datasource.url`, `spring.datasource.username`, `spring.datasource.password`, and third-party payment-related parameters, such as Alipay's `alipay.gatewayUrl`, `alipay.appId`, `alipay.privateKey`, and WeChat Pay's `wxpay.appId`, `wxpay.partnerKey`, `wxpay.notifyUrl`.

[0236] Step 7.2: Implement CRUD operations on accounting-related data by inheriting `JpaRepository`. For example, query order information `@Query(″SELECT o FROM Order o WHERE o.orderId=:orderId")`, and query supplier account information `@Query(″SELECT s FROM Suppliers WHERE s.supplierId=:supplierId")`.

[0237] Step 7.3, Security authentication: Introduce Spring Security for user identity authentication and authorization. Configure user roles and permissions in the `SecurityConfig` class to ensure that only users with specific permissions (such as platform administrators and procurement leaders) can access the profit sharing function. For example, set the user role to `ROLE_ADMIN` and the permission to ` / accounting / `, and only users with this role can perform profit sharing operations.

[0238] Step 7.4, Profit sharing calculation: Determine the profit sharing amounts for the supplier and the platform based on the profit sharing ratio of the order.

[0239] Step 7.5, Record profit sharing information: Record the profit sharing information into the database.

[0240] Step 7.6, Profit sharing payment: Pay the supplier's profit sharing amount to the supplier `paymentService.payToSupplier(supplierId, supplierAmount);`.

[0241] Step 8, Conduct quality traceability processing on the logistics distribution results completed in Step 5 and generate a quality report.

[0242] Step 8.1, Product information collection: During the product production process, collect relevant information about the product, including product ID, product batch number, production date, production process, raw material source, etc. Store this information in the database.

[0243] Step 8.2, Supplier information collection: Collect relevant information about the supplier, including supplier name, supplier address, supplier contact information, quality standards of the supplied products, etc. Store this information in the database.

[0244] Step 8.3, Storage and association of traceability information: Associate the product quality inspection results with the product information and supplier information, and store the quality traceability information in the database.

[0245] Step 8.4, Generate a quality report, store the report, and at the same time encrypt the quality traceability data using the AES encryption algorithm.

[0246] In view of the above problems, the present invention proposes an Internet-based agricultural supply chain transaction scheduling method, aiming to improve the circulation efficiency of agricultural products, reduce transaction costs, and ensure product quality by integrating all links in the supply chain. The specific improvement directions include:

[0247] Information sharing and intelligent matching: Integrate the information of suppliers, purchasers and logistics enterprises through an Internet platform, and use intelligent matching algorithms to quickly recommend the best matching partners for both buyers and sellers based on multi-dimensional factors such as transaction history, credit evaluation, and price requirements, improving the efficiency and accuracy of transaction completion.

[0248] Logistics scheduling optimization: Conduct logistics path planning and transportation resource scheduling through operations research algorithms, comprehensively consider factors such as transportation cost, timeliness, and cold chain requirements, and select the optimal logistics transportation method and route to ensure that agricultural products can be delivered to the destination in the shortest time, at the lowest cost, and with guaranteed quality.

[0249] Financial service integration: Provide convenient financial services such as special product funds for purchasers in the supply chain through the platform, solve the problem of capital shortage, and promote the stable operation of the supply chain and the activity of transactions.

[0250] Quality traceability and safety guarantee: Build an immutable agricultural product traceability system through blockchain technology, record the full life cycle information from production to consumption, realize the whole process quality monitoring and traceability from farm to table, and guarantee the quality and safety of agricultural products.

[0251] In summary, the present invention integrates the information flow, logistics flow and capital flow in the supply chain, provides one-stop procurement, sales, supply chain financial services and other related services, significantly improves the overall efficiency of the agricultural and sideline products supply chain, reduces transaction costs, guarantees product quality, and promotes the modernization and sustainable development of the agricultural product supply chain industry.

Claims

1. A method for scheduling agricultural supply chain transactions based on the Internet, characterized in that: The following steps are involved: Step 1: Collect and verify supplier information in the agricultural supply chain to obtain verified supplier information; Step 2: Collect and classify the agricultural product information of the supplier information that has passed the verification obtained in step 1 to obtain classified agricultural product information; Step 3: Perform intelligent matching and bidding processing on the classified agricultural product information obtained in step 2 to obtain matching and bidding results; Step 4: Generate an order and process payment for the matching and bidding results obtained in step 3 to obtain an order payment result; Step 5: Perform logistics scheduling and distribution processing on the order payment result obtained in step 4 to complete the agricultural supply chain transaction scheduling; Step 6: Perform financial product service processing on the order payment result obtained in step 4 and provide financial product support; Step 7: Perform account management on the financial product approval results obtained in step 6 to complete fund allocation; Step 8: Conduct quality traceability processing on the logistics distribution results completed in step 5 and generate a quality report.

2. The method for scheduling agricultural supply chain transactions based on the Internet according to claim 1, characterized in that: The sub-steps of step 1 include: Step 1.1, collect and process supplier information to obtain supplier information; Step 1.2: Perform format verification and contact verification on the supplier information obtained in step 1.1 to obtain the verified supplier information; The supplier information collection process in step 1.1 includes: Step 1.1.

1. Build a supplier information collection module based on the Spring Boot framework, use the @SpringBootApplication annotation to mark the startup class, and enable component scanning and automatic configuration; Step 1.1.1.1, initialize the Spring Boot framework, create a startup class and mark it with @SpringBootApplication annotation, enable component scanning and automatic configuration functions, and obtain the initialized SpringBoot application; Step 1.1.1.2, divide the initialized Spring Boot application obtained in step 1.1.1.1 into modules, create a supplier information collection module, and obtain a supplier information collection module framework; Step 1.1.1.3, perform dependency injection configuration processing on the supplier information collection module framework obtained in step 1.1.1.2, introduce the required dependent components, and obtain the configured supplier information collection module; Step 1.1.2, obtain the database connection pool through dependency injection, and configure the database connection parameters, including host address, user name, and password; Step 1.1.3, configure the JPA framework for the database connection pool to obtain the data access interface SupplierInfoRepository for supplier information. This interface inherits from JpaRepository and implements the creation, reading, updating and deletion operations of supplier information. JpaRepository is the core interface provided by Spring Data JPA, which encapsulates common database operation methods, including creation, reading, updating and deletion; Step 1.1.3.1, define the supplier information data model, create the supplier information entity class, and obtain the supplier information data model; Step 1.1.3.2: Persist the supplier information data model obtained in step 1.1.3.1, create a SupplierInfoRepository interface and inherit JpaRepository to obtain the supplier information persistence interface; Step 1.1.3.3: Perform CRUD operation configuration processing on the supplier information persistence interface obtained in step 1.1.3.2 to implement the functions of creating, reading, updating and deleting supplier information, and obtain a fully functional supplier information persistence interface.

3. The method for scheduling agricultural supply chain transactions based on the Internet according to claim 1, characterized in that: The sub-steps of step 2 include: Step 2.1, collecting and processing agricultural product information to obtain agricultural product information; Step 2.2: Classify the agricultural product information obtained in step 2.1 to obtain classified agricultural product information.

4. The method for scheduling agricultural supply chain transactions based on the Internet according to claim 3 is characterized in that: The agricultural product information classification processing in step 2.2 includes: Step 2.2.1: Build an agricultural product information search engine based on Elasticsearch and configure indexes and mapping relationships; Step 2.2.2, perform word segmentation on the collected agricultural product information and establish a full-text index; Step 2.2.3: Classify agricultural products according to their categories, specifications, and origin information, and store them in the database.

5. The method for scheduling agricultural supply chain transactions based on the Internet according to claim 1, characterized in that: The sub-steps of step 3 include: Step 3.1: Search and match agricultural product information based on Elasticsearch, and sort by price and inventory factors; Step 3.1.1, initialize the intelligent matching product selection module to obtain the intelligent matching product selection module object; Step 3.1.1.1, build the "intelligent matching product selection module" based on the Spring Boot framework, use the @SpringBootApplication annotation to mark the startup class, and enable component scanning and automatic configuration; Step 3.1.1.2, create a class named SmartMatchService as the core control class, and obtain the required service components through dependency injection, including the database connection pool, the search engine service Elasticsearch for full-text search and indexing of product information to achieve fast and accurate product matching, and the data cache service; Step 3.1.1.

3. Configure the database connection parameters in the application.yml file and configure the relevant parameters of Elasticsearch; Step 3.1.2, searching and matching agricultural product information to obtain matching results; Step 3.1.2.1: After the backend receives the product selection request submitted by the frontend, it creates the matchProducts method in the SmartMatchService class for processing; Step 3.1.2.2, the matchProducts method uses Elasticsearch to perform a full-text search based on the keywords, categories, and specifications entered by the user to obtain the agricultural product information that meets the conditions; Step 3.1.2.3: Match and sort the search results, combining product relevance, price, and inventory factors to sort, including: Agricultural products with lower prices are displayed first; Agricultural products with sufficient stocks will be displayed first; Agricultural products with higher relevance will be displayed first; Step 3.1.3, return the matching results to the front end for user selection; Step 3.1.3.1, encapsulate the sorted agricultural product information into JSON format and return it to the front end; Step 3.1.3.2: After the front end receives the data, it is displayed on the page for the user to select; Step 3.2: Build a bidding module based on the RabbitMQ message queue to process bidding requests submitted by users; Step 3.2.1: Initialize the bidding and product selection module to obtain the bidding and product selection module object; Step 3.2.1.

1. Build the "Product Bidding and Selection Module" based on the Spring Boot framework and create the ProductAuctionService class as the core control class; Step 3.2.1.2, obtain the database connection pool, message queue service, and user authentication service through dependency injection; Step 3.2.1.3, configure the relevant parameters of RabbitMQ in the application.yml file, including the address of the RabbitMQ server spring.rabbitmq.host, the port of the RabbitMQ server spring.rabbitmq.port, the login name spring.rabbitmq.username, and the password spring.rabbitmq.password; Step 3.2.2: Verify the bidding request submitted by the user and obtain the bidding request that has passed the verification; Step 3.2.2.1: After the backend receives the bidding request submitted by the frontend, it creates the processBid method in the ProductAuctionService class for processing; Step 3.2.2.2, the processBid method verifies the user identity and bid information, including: Check if the user exists; Check whether the user's balance is sufficient to pay the bid amount; Check whether the bid amount is within the range specified by the platform; Step 3.2.3: Send the verified bidding request to the message queue and update the bidding status; Step 3.2.3.1, encapsulate the bidding information into a message object, including product ID, bidding amount, and bidding time; Step 3.2.3.2, send the message to the specified message queue through RabbitMQ; Step 3.2.3.3, monitor the message queue in real time and update the bidding information and bidding status of each product; Step 3.3: Determine the winning bidder based on the bidding algorithm and generate the bidding results; Step 3.3.1, initialize the bidding algorithm and obtain the bidding algorithm object; Step 3.3.1.

1. Define the core logic of the bidding algorithm, for example: Seller Basic Supplier Indicates A j , the price of a certain commodity is Xi yuan / ton, and the inventory is Y i ton; Buyer Purchaser indicates B i , the quantity of intended goods to be purchased is S i ton; The platform adjusts the price to ε according to different levels of buyers j Yuan / ton, so the buyer's commodity price is: Step 3.3.2: Calculate the final price of each buyer based on the bidding algorithm and determine the winning bidder; Step 3.3.2.1, traverse all bidding requests and calculate the final price of each buyer according to the bidding algorithm; Step 3.3.2.2: Compare the final prices of each buyer and determine the winning bidder; Step 3.3.3, generate bidding results and notify relevant users; Step 3.3.3.1, store the information of the successful bidder in the database, and update the bidding status to "successful bid"; Step 3.3.3.2: Notify the successful bidder and other participants via in-site message or SMS; Step 3.3.3.3: After receiving the notification, the front end displays the bidding results.

6. The method for scheduling agricultural supply chain transactions based on the Internet according to claim 1, characterized in that: The sub-steps of step 4 include: Step 4.1: Perform order generation processing on the bidding results to obtain order information; Step 4.2: Perform payment processing on the order information obtained in step 4.1 to obtain the order payment result; Step 4.2.1, integrate third-party payment interfaces, including Alipay and WeChat Pay, and configure payment parameters; Step 4.2.2: Receive payment request from user and verify payment information; Step 4.2.3: Call the third-party payment interface to complete the payment and update the order status to paid.

7. The method for scheduling agricultural supply chain transactions based on the Internet according to claim 1, characterized in that: The sub-steps of step 5 include: Step 5.1: Perform logistics scheduling on the order payment result to obtain logistics scheduling information; Step 5.1.1, generate logistics scheduling tasks based on order information, including delivery address, delivery method, and delivery time; Step 5.1.2: Call the logistics management system interface to allocate distribution resources; Step 5.1.3, track the logistics status in real time and update the order logistics information; Step 5.2: Distribute and process the logistics dispatch information obtained in step 5.1 to complete the agricultural supply chain transaction dispatch; Step 5.2.1: Arrange delivery vehicles and personnel according to logistics dispatch tasks; Step 5.2.2: Monitor the delivery process in real time to ensure on-time delivery; Step 5.2.3: After delivery is completed, update the order status to completed and notify the user.

8. The method for scheduling agricultural supply chain transactions based on the Internet according to claim 1, characterized in that: Step 6 includes the following steps: Step 6.1: Build the "Financial Product Service" module based on the Spring Cloud microservice architecture and complete module initialization; Step 6.2: Receive the loan application and verify the application information, including the amount range, basic company information, and verification code; Step 6.3: Obtain multi-dimensional risk control data through the risk control data interface and calculate the risk score; Step 6.4: Conduct manual review, generate a loan contract and determine the loan amount, term and interest rate; Step 6.5: Execute the loan operation and complete the financial transaction.

9. The method for scheduling agricultural supply chain transactions based on the Internet according to claim 1, characterized in that: Step 7 includes the following steps: Step 7.1: Build the "account management module" based on the Spring Boot framework, and configure the database connection and third-party payment interface; Step 7.2: Calculate the supplier and platform's share of the account based on the financial product approval result and order amount; Step 7.3: Record the split account information into the database and complete the split account payment; Step 7.4: Update the account splitting status and notify relevant parties.

10. The method for scheduling agricultural supply chain transactions based on the Internet according to claim 1, characterized in that: Step 8 includes the following steps: Step 8.1: Build the "quality traceability module" based on the Spring Boot framework, and configure the database connection and quality information collection service; Step 8.2: Collect quality information of agricultural products during production, including production date, production process, source of raw materials, etc.; Step 8.3: Associate the quality information with the order information and supplier information to generate a quality traceability report; Step 8.4: Use the AES encryption algorithm to encrypt and store the quality traceability data to ensure data security; Step 8.5: Generate a quality report and store it in the database for users to query and download.

Images