An intelligent logistics application platform

Through the DDD multi-layer architecture and Hexagonal Architecture design, the problem of lack of clear field boundaries and unified technical standards in the logistics transaction system architecture is solved, and a high-cohesion and low-coupling logistics application platform is realized, which improves iteration efficiency and stability and reduces the Maintenance cost.

CN118656054BActive Publication Date: 2024-12-03SHENZHEN YISHIHUOLALA TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411140060.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-08-20
Publication Date
2024-12-03
Estimated Expiration
2044-08-20

AI Technical Summary

Technical Problem

The existing logistics and trading system architecture lacks clear field boundaries and unified technical standards, resulting in low cohesion and high coupling of the system, low iteration efficiency, high maintenance costs, frequent accidents, and difficulty in business expansion.

Method used

DDD (Domain-Driven Design) multi-layer architecture design is divided into presentation layer, business layer, platform layer, middle platform layer and basic layer. Through Hexagonal Architecture and CQRS+EventSourcing architecture, the system is achieved with high cohesion and low coupling. Supports business logic reuse and flexible iteration.

Benefits of technology

It improves the stability and development efficiency of the system, reduces operating costs, realizes the flexibility of business expansion and middle-end capabilities, and significantly improves the overall performance of the logistics application platform.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118656054B_ABST
    Figure CN118656054B_ABST
Patent Text Reader

Abstract

The present invention belongs to the field of intelligent logistics technology, and specifically relates to an intelligent logistics application platform, including: a presentation layer, including an order creation end and an order fulfillment end, and respectively configured for Party A users and Party B users to interact with the application platform; multiple business layers, configured with different business logics; a platform layer, configured with multiple common first domain logics; a middle platform layer, configured with multiple common second domain logics, and the general capabilities of the second domain logic exceed the first domain logic; a basic layer, used to provide common basic services for the presentation layer, business layer, platform layer, and middle platform layer; wherein the business layer is used to convert the business needs of Party A users or Party B users into corresponding business projects based on the configured business logic, and call the first domain logic of the platform layer and the second domain logic of the middle platform layer to process the business projects to generate corresponding business orders or provide corresponding business waybills.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention belongs to the technical field of intelligent logistics, and specifically relates to an intelligent logistics application platform. Background Art

[0002] At present, the system architecture of the logistics transaction model is generally a layered approach of large monomers, business + middle platform, and business + platform. For example, the architecture method of the traditional TMS (Transportation Management System) transportation management system is generally a large monomer, without a layered design, and is used to plan, execute and optimize the transportation process of goods; or the transaction system of the Internet logistics platform is generally designed in a layered manner by a large monomer business system or a platform / middle platform + business architecture.

[0003] For Internet logistics platforms, the above-mentioned layered architecture method generally has the following disadvantages:

[0004] The unclear domain boundaries lead to low cohesion and high coupling of the logistics platform.

[0005] Unclear business architecture leads to the iteration of business requirements, which accelerates the corruption of the system.

[0006] The unclear technical architecture leads to the lack of unified standards and solutions for technical solutions.

[0007] Due to the above shortcomings, with continuous iteration and maintenance, the logistics platform will have frequent accidents, poor stability, and it will be difficult to troubleshoot problems after an accident. At the same time, the iteration efficiency will become lower and lower, the maintenance cost will become higher and higher, and it will be difficult to expand business. Summary of the invention

[0008] In view of the shortcomings of the prior art mentioned above, the present invention aims to design a logistics application platform based on a multi-layer architecture of DDD (Domain-Driven Design), with lower-level capabilities being more general and higher-level capabilities being more suitable for specific businesses. It can not only reuse general capabilities, but also flexibly support business updates, thus achieving a good balance between the dilemma of business expansion and middle-end capability accumulation.

[0009] To achieve the above-mentioned purpose and other related purposes, the present invention provides an intelligent logistics application platform, including: a presentation layer, including an order creation end and an order fulfillment end, and respectively configured for Party A users and Party B users to interact with the application platform; multiple business layers, configured with different business logics; a platform layer, configured with multiple common first domain logics; a middle platform layer, configured with multiple common second domain logics, and the general capabilities of the second domain logic exceed the first domain logic; a basic layer, used to provide common basic services for the presentation layer, the business layer, the platform layer, and the middle platform layer; wherein the business layer is used to convert the business needs of Party A users or Party B users into corresponding business items based on the configured business logic, and call the first domain logic of the platform layer and the second domain logic of the middle platform layer to process the business items to generate corresponding business orders or provide corresponding business waybills.

[0010] According to a specific embodiment of the present invention, when Party A's user interacts with the application platform through the presentation layer and triggers the corresponding business layer, the business layer is used to orchestrate the business requirements input by Party A's user based on the configured business logic, generate corresponding logistics services, and call the first domain logic of the platform layer and the second domain logic of the middle platform layer to verify the logistics service to generate a corresponding business order.

[0011] According to a specific embodiment of the present invention, when the business layer is triggered, the business layer is also used to call the first domain logic of the platform layer and / or the second domain logic of the middle platform layer to authenticate the identity of Party A users in order to distribute benefits and recommend preferential services.

[0012] According to a specific embodiment of the present invention, the first domain logic includes risk control verification, price verification, and verification of preferential services. The platform layer is used to verify the logistics service based on the configured first domain logic, and the middle platform layer is used to convert the verified logistics service into a corresponding business order based on the configured second domain logic.

[0013] According to a specific embodiment of the present invention, when the Party B user interacts with the application platform through the presentation layer and triggers the corresponding business layer, the business layer is used to call the business waybill from the middle platform layer through the platform layer based on the configured business logic to provide the Party B user with order grabbing service; wherein the middle platform layer is also used to convert the business order into the corresponding business waybill based on the configured second domain logic.

[0014] According to a specific embodiment of the present invention, when the business layer is triggered, the business layer is also used to call the first domain logic of the platform layer and / or the second domain logic of the middle platform layer to perform identity authentication on the Party B user, so as to provide an exclusive order grabbing channel and high-value business waybills.

[0015] According to a specific embodiment of the present invention, the first domain logic includes risk control verification and order quantity verification, the platform layer is used to verify the identity of the Party B user based on the configured first domain logic, and to review the business waybills snatched by the Party B user, and the middle platform layer is used to allocate corresponding business waybills to the Party B users after verification and review based on the configured second domain logic.

[0016] According to a specific embodiment of the present invention, the presentation layer includes clients corresponding to the order creation end and the order fulfillment end, and an application program interface layer; the application program interface layer is used to customize the corresponding application program interface according to the interaction characteristics of different clients; wherein, the client calls one or more of the business layers through its corresponding application program interface to process the business needs of Party A users or Party B users.

[0017] According to a specific embodiment of the present invention, the presentation layer, the business layer, the platform layer, the middle platform layer, and the basic layer adopt a Hexagonal Architecture in code implementation.

[0018] According to a specific embodiment of the present invention, the second domain logic includes order creation and waybill creation, and the order creation and waybill creation models are constructed using the CQRS (Command Query Responsibility Segregation) + Event Sourcing architecture.

[0019] The present invention provides a multi-layer intelligent logistics application platform, which adopts a five-layer structure of presentation layer, business layer, platform layer, middle platform layer and foundation layer. Compared with simple middle platform or platformization, it provides more flexibility and capability accumulation, and the system layering is more reasonable, with high cohesion and low coupling. Different business layers can quickly reuse the capabilities of the platform layer and the middle platform layer, which greatly improves the development efficiency of the application platform, significantly improves the system stability, and significantly reduces the operating cost. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 This is a structural diagram of the existing DDD layered architecture;

[0021] Figure 2 This is a structural diagram of a specific embodiment of an intelligent logistics application platform provided by the present invention;

[0022] Figure 3 This is a structural schematic diagram of another specific embodiment of an intelligent logistics application platform provided by the present invention;

[0023] Figure 4The present invention provides a structural block diagram of a specific embodiment of an electronic device. DETAILED DESCRIPTION

[0024] In order to facilitate understanding of the present application, the present application will be described more fully below with reference to the relevant drawings. Embodiments of the present application are provided in the drawings. However, the present application can be implemented in many different forms and is not limited to the embodiments described herein. On the contrary, the purpose of providing these embodiments is to make the disclosure of the present application more thorough and comprehensive.

[0025] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein in the specification of this application are only for the purpose of describing specific embodiments and are not intended to limit this application.

[0026] The following describes the embodiments of the present invention by specific examples, and those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict.

[0027] In the following description, numerous details are discussed to provide a more thorough explanation of the embodiments of the present invention. However, it is obvious to those skilled in the art that the embodiments of the present invention can be implemented without these specific details. In other embodiments, well-known structures and devices are shown in the form of block diagrams rather than in detail to avoid making the embodiments of the present invention difficult to understand.

[0028] First of all, it should be explained that in order to enable people in this technical field to better understand the present application scheme, the technical background of this application is explained accordingly.

[0029] DDD is a software design method that takes the business domain as the core of the design to better meet business needs while improving the flexibility and adaptability of the system. For example, in industries such as finance, e-commerce, and healthcare, the DDD architecture is widely used to build systems with complex business logic. Through clear layering and component design, the system is more stable, easier to maintain, and easier to expand.

[0030] For details, please refer to Figure 1As shown in the figure, the DDD layered architecture is usually composed of the following from top to bottom: interface layer, application layer, domain layer and basic layer. Among them, the interface layer is responsible for displaying information to users and interpreting user instructions. The users here may be: users, programs, automated tests and batch scripts, etc. Application layer: a very thin layer, theoretically there should be no business rules or logic, mainly for use cases and process-related operations. However, the application layer is located above the domain layer. Because the domain layer contains multiple aggregates, it can coordinate multiple aggregated services and domain objects to complete service orchestration and combination, and collaborate to complete business operations. In addition, the application layer is also a channel for interaction between microservices. It can call application services of other microservices to complete service combination and orchestration between microservices. Domain layer: implements the core business logic of the enterprise and ensures the correctness of the business through various verification methods. The domain layer mainly reflects the business capabilities of the domain model. It is used to express business concepts, business status and business rules. The domain layer contains domain objects in the domain model such as aggregate roots, entities, value objects, and domain services. Basic layer: It runs through all layers and provides common technologies and basic services for other layers, including third-party tools, drivers, message middleware, gateways, files, caches, and databases. The most common function is to provide database persistence.

[0031] Therefore, this application is based on the multi-layer architecture of DDD. Through business analysis in the field of Internet intelligent logistics, it divides the transaction business in a layered manner of multiple businesses, large platforms, and small middle platforms. The business layer realizes a complete business process by reusing the common business capabilities of the large platform and the small middle platform, and by expanding the number of business layers, the function expansion of the logistics platform can be flexibly realized, which is conducive to the iteration and maintenance of the logistics platform.

[0032] Example 1

[0033] See also Figure 2 and Figure 3The intelligent logistics application platform shown includes: a presentation layer 10, a business layer 20, a platform layer 30, a middle platform layer 40, and a basic layer 50. Among them, the presentation layer 10 is configured for users to interact with the application platform. For example, users can enter the application platform through APP, mini-programs, web pages, etc., and can interact with the application platform after entering the application platform to obtain corresponding services. It can be understood here that the users faced by the presentation layer 10 include at least the order creation end and the order fulfillment end. For example, after entering the application platform, the user of Party A can select different services provided by the logistics platform through the presentation layer 10, including freight, moving, less-than-truckload, etc., and then create an order through the application platform and pay a certain fee to the application platform; and the user of Party B can select the waybill provided by the logistics platform through the presentation layer 10 after entering the application platform, so as to provide corresponding logistics services based on the waybill, so as to receive the salary for fulfillment from the application platform. Of course, the users faced by the presentation layer 10 are not limited to the above, for example, they may also be management users or authorized users, etc., and there are no excessive restrictions on this. However, in this embodiment, more emphasis is placed on the complete transaction process of the logistics application platform, and Party A users and Party B users are taken as examples, and there is no excessive description of management users or authorized users, etc. It can be seen that the presentation layer 10 is intended to provide an interactive channel between users and the application platform, and can display the logistics services, business functions, service items, etc. of the application platform to users.

[0034] The business layer 20 is configured with independent business logic to process the business needs of users. For example, Party A user needs to move within the same city, so the corresponding business layer 20 is triggered when the presentation layer 10 interacts with the application platform. Accordingly, the business layer 20 compiles the business needs input by Party A user based on the configured business logic, such as the old home address and the new home address, the selected moving vehicle model, and the contact information and other related information to generate the corresponding electronic order.

[0035] It can be understood here that the business functions of the logistics application platform are not limited to one type, for example, including large truck transportation, small car transportation, same-city transportation, cross-city transportation, etc., and the business logic corresponding to different business functions is different. Therefore, under normal circumstances, one business layer 20 corresponds to one business function, and multiple business layers 20 can be configured according to the logistics services that the logistics application platform can provide to handle different business needs of users. Of course, if the business functions are relatively similar, it can also be configured that one business layer 20 corresponds to multiple business functions. Without making too many restrictions on this, the modifications and embellishments made to the embodiments of the present invention by those skilled in the art without departing from the spirit of the present invention still fall within the scope of the invention application patent of the present invention.

[0036] The platform layer 30 is configured with multiple first domain logics, and the middle platform layer 40 is configured with multiple second domain logics. It should be noted here that the first domain logic and the second domain logic are different from the business logic. They are common logical processing methods that the logistics application platform can use when processing user needs. For example, the business logic can be intra-city transportation or inter-city transportation, but after the corresponding process is arranged based on the business logic, both the intra-city transportation business and the inter-city transportation business need to verify the corresponding business expenses, so the verification of the expenses here can be used as a common logical processing method. In addition, the general capabilities of the second domain logic at least exceed the first domain logic, thus forming a hierarchical architecture that is more specific as it goes up and more general as it goes down. Of course, there is no restriction on the specific functions of the first domain logic and the second domain logic. Specifically, they can be allocated to the platform layer 30 and the middle platform layer 40 according to the common capabilities according to the common logical processing methods that can be shared in actual applications, and the common capabilities of the middle platform layer 40 are kept greater than the platform layer 30. The modifications and embellishments made to the embodiments of the present invention by those skilled in the art without departing from the spirit of the present invention still fall within the scope of the invention patent application of the present invention.

[0037] Therefore, after the business layer 20 has preliminarily processed the user's business needs, it can obtain the corresponding business items, and then further process and verify the business items by calling the first domain logic of the platform layer 30 and the second domain logic of the middle platform layer 40, thereby completing the transaction process.

[0038] The basic layer 50 is used to provide more general basic services for the presentation layer 10, the business layer 20, the platform layer 30, and the middle platform layer 40, such as some basic components that need to be called by the presentation layer 10 / business layer 20 / platform layer 30 / middle platform layer 40 when performing corresponding functions. There are no excessive restrictions on this. Without departing from the spirit of the present invention, modifications and improvements made to the embodiments of the present invention by those skilled in the art still fall within the scope of the invention patent application of the present invention.

[0039] It can be seen that different business layers 20 in the multi-layer architecture are configured with different business logics to target specific business needs, while the platform layer 30 and the middle platform layer 40 are general capability layers that can be called by the business layer 20 when needed. It can be understood here that multiple first-domain logics are configured in the platform layer 30, corresponding to multiple different functional roles or business capabilities, and the same is true for the middle platform layer 40. However, due to different business needs of users, the corresponding business layer 20 does not utilize all the functional roles or business capabilities of the platform layer 30 and / or the middle platform layer 40 when calling it, and usually only part of the first-domain logic / second-domain logic in the platform layer 30 or the middle platform layer 40.

[0040] Therefore, when a certain business function of the logistics application platform needs to be maintained or updated, the corresponding business layer 20 can be temporarily removed accordingly, and other business functions in the logistics application platform, that is, the corresponding business layer 20, will not be affected, and can still be arranged according to the business logic, and call the general capabilities of the platform layer and the middle platform layer to maintain normal operation; or when the logistics application platform needs to expand certain business functions, the business layer 20 corresponding to the business logic can be added accordingly, and it can work normally by reusing the capabilities of the platform layer 30 and the middle platform layer 40. In this way, even if the business layer 20 is added or removed, it will not affect the normal operation of the logistics platform, thereby greatly improving the flexibility of iterative upgrades and update maintenance of the logistics application platform. If it still follows an overall system architecture, the entire system architecture needs to be rewritten when expanding or maintaining the logistics application platform, which seriously affects the development efficiency of the logistics application platform.

[0041] In a specific embodiment, the first domain logic of the platform layer may include risk control verification, price verification, verification of preferential services, order review and quantity verification, etc., and the second domain logic of the middle platform layer may include identity authentication, order creation, waybill creation, bill generation, etc.

[0042] When the user of Party A interacts with the application platform through the presentation layer 10 and triggers the corresponding business layer 20, that is, the user enters the logistics application platform through the APP or applet, and further selects the corresponding business needs, such as freight, moving, etc., thereby triggering the corresponding business layer 20. First, the business layer 20 will call the middle platform layer 40 through the platform layer 30 to authenticate the identity of the user of Party A, for example, the user needs to log in to the account and enter the password, and further verify the user's membership information. If the user subscribes to VIP membership, coupons can be issued accordingly, or some preferential services corresponding to the current business layer 20 can be pushed, etc. If the user is just an ordinary identity, then the user's business needs can continue to be obtained. Secondly, the business layer 20 arranges the business needs entered by the user of Party A based on the business logic configured by it, and generates corresponding logistics services, such as arranging the relevant information such as the location, time, and goods entered by the user into a specific logistics service, that is, delivering a certain cargo from where to where within a specified time and similar situations. Furthermore, the business layer 20 calls the platform layer 30 to verify the logistics service. For example, the risk control verification can be to review whether the logistics service is prohibited, whether the safety factor is high, etc., the price verification can be to identify the theoretical fees that need to be paid for the logistics service, and the discount service verification can be based on the theoretical fees that need to be paid after deducting the corresponding red envelope or fee reduction. Finally, the middle platform layer 40 creates the corresponding business order based on the audited and verified logistics service, and generates the corresponding bill and feeds it back to the user through the presentation layer 10 for payment.

[0043] It can be seen here that the above specific content is the transaction process of the order creation end in actual application. At the same time, the middle platform layer 40 is also used to create corresponding business waybills according to the business order, and the freight driver or the transporter performs the fulfillment. The transaction process of the order fulfillment end is as follows:

[0044] When the user of Party B interacts with the application platform through the presentation layer 10 and triggers the corresponding business layer 20, that is, the user enters the logistics application platform through the APP or applet, and further selects the corresponding business needs, such as the order grabbing service, that is, receiving the waybill and completing the performance, so as to obtain the salary from the logistics application platform, thereby triggering the corresponding business layer 20. First, the business layer 20 will call the middle platform layer 40 through the platform layer 30 to authenticate the identity of the user of Party B, for example, the user needs to log in to the account and enter the password, and further verify the user's membership information. If the user subscribes to VIP membership, it can provide an exclusive order grabbing channel or provide some hidden high-value waybill and other special services to obtain a higher salary. If the user is just an ordinary identity, then the above-mentioned special services are not included. Secondly, the business layer 20 retrieves the corresponding business waybill from the middle platform layer 40 through the platform layer 30 based on the business logic configured by it. Here, if the user of Party B is a VIP member, some high-value waybills can be directly provided to the user of Party B for selection. If the user of Party B is an ordinary identity, multiple business waybills are provided for multiple users of Party B to grab. Furthermore, the business layer 20 calls the platform layer 30 to perform risk control verification on the Party B user, for example, it can be to review the Party B user's credibility, performance completion, etc., and at the same time review whether the Party B user can accept the business waybill that he has snatched / accepted, such as quantity restrictions, or membership restrictions, or credibility or performance completion restrictions, etc. Finally, the middle platform layer 40 allocates the corresponding business waybill based on the audited and verified Party B user. In addition, the middle platform layer 40 is also used to pay the corresponding salary and other things after the Party B user completes the corresponding business waybill.

[0045] In summary, this embodiment utilizes the layered architecture design and model modeling method of DDD to form a logistics application platform with a multi-layer architecture that includes a presentation layer, a business layer, a platform layer, a middle platform layer, and a basic layer, and ensures that the lower layers are more general and the higher layers are closer to specific businesses. This can achieve maximum reuse and is conducive to flexible iterative upgrades and update maintenance of the logistics application platform.

[0046] At the same time, the entire logistics application platform adopts the Hexagonal Architecture in code implementation. Through the principle of dependency inversion, the business logic code is separated and decoupled from the underlying class library and external interface conversion logic, which can ensure the sedimentation of the core business domain logic.

[0047] In addition, the CQRS + EventSourcing architecture design method is adopted in the order creation and waybill creation areas of the middle platform layer. Through the CQRS architecture method, the read logic and write logic of the order and waybill can be separated, which solves the contradictory problems of low QPS (Queries-per-second) but complex logic in the write logic, and high QPS and simple logic in the read logic but the need to read data across multiple fields. By drawing on the design method of EventSourcing, the decoupling of the core processing logic of the order and waybill and the peripheral dependency logic is completed in an event-driven manner, ensuring high cohesion of the core logic.

[0048] In addition, the Saga design method is adopted in terms of distributed consistency. The business process is split into multiple sub-transactions through long transactions, and the workflow is used to ensure that all sub-transactions are successfully submitted to achieve distributed eventual consistency.

[0049] Finally, it should be added that the presentation layer 10 in this embodiment includes clients corresponding to the order creation end and the order fulfillment end, as well as an application interface layer, and the application interface layer adopts the BFF architecture. It can be understood that the application interface layer in the application interface layer can customize the interface form according to the interactive characteristics of different clients, so that when the user triggers the corresponding business needs through the client, the business layer is called by calling the corresponding application interface layer to process the user's business needs. In addition, an application interface can correspond to calling one or more business layers 20, without making too many restrictions on this. Without departing from the spirit of the present invention, the modifications and embellishments made to the embodiments of the present invention by those skilled in the art still fall within the scope of the invention patent application of the present invention.

[0050] Example 2

[0051] See also Figure 4 As shown, an embodiment of the present application further provides an electronic device, including a memory 2, a processor 1, and a program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned intelligent logistics application platform when executing the program.

[0052] Among them, the memory includes at least one type of readable storage medium, and the readable storage medium includes flash memory, mobile hard disk, multimedia card, card-type memory (for example: SD or DX memory, etc.), magnetic memory, disk, optical disk, etc. In some embodiments, the memory can be an internal storage unit of the electronic device, such as a mobile hard disk of the electronic device. In other embodiments, the memory can also be an external storage device of the electronic device, such as a plug-in mobile hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the electronic device. Further, the memory can also include both an internal storage unit of the electronic device and an external storage device. The memory can not only be used to store application software and various types of data installed in the electronic device, but also can be used to temporarily store data that has been output or is to be output.

[0053] In some embodiments, the processor may be composed of an integrated circuit, for example, a single packaged integrated circuit, or a plurality of packaged integrated circuits with the same or different functions, including one or more central processing units (CPUs), microprocessors, digital processing chips, graphics processors, and a combination of various control chips. The processor is the control core (Control Unit) of the electronic device, which connects the various components of the entire electronic device using various interfaces and lines, and executes various functions of the electronic device and processes data by running or executing programs or modules stored in the memory, and calling data stored in the memory.

[0054] The processor executes the operating system of the electronic device and various installed application programs. The processor executes the application programs to implement the above-mentioned intelligent logistics application platform.

[0055] Exemplarily, the program may be divided into one or more modules, which are stored in the memory and executed by the processor to complete the present invention. The one or more modules may be a series of program instruction segments capable of completing specific functions, which are used to describe the execution process of the program in the electronic device.

[0056] The above-mentioned integrated unit implemented in the form of software function modules can be stored in a computer-readable storage medium. The above-mentioned software function modules are stored in a storage medium and include several instructions for enabling a computer device (which can be a personal computer, a computer device, or a network device, etc.) or a processor to perform part of the functions of various embodiments of the present invention.

[0057] In summary, the present invention provides a multi-layer intelligent logistics application platform, which adopts a five-layer structure of presentation layer, business layer, platform layer, middle platform layer, and foundation layer. Compared with simple middle platform or platformization, it provides more flexibility and capability accumulation, and the system layering is more reasonable, with high cohesion and low coupling. Different business layers can quickly reuse the capabilities of the platform layer and the middle platform layer, which greatly improves the development efficiency of the application platform, significantly improves the system stability, and significantly reduces the operating cost.

[0058] The above embodiments are merely illustrative of the principles and effects of the present invention, and are not intended to limit the present invention. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present invention. Therefore, all equivalent modifications or changes made by a person of ordinary skill in the art without departing from the spirit and technical ideas disclosed by the present invention shall still be covered by the claims of the present invention.

Claims

1. An intelligent logistics application platform, It is characterized in that include: The presentation layer includes the order creation end and the order fulfillment end, and is configured to allow Party A users and Party B users to interact with the application platform respectively; Multiple business layers, configured with different business logics; The platform layer is configured with common multiple first domain logics; The middle platform layer is configured with multiple common second domain logics, and the common capabilities of the second domain logics exceed those of the first domain logics; The basic layer is used to provide common basic services for the presentation layer, the business layer, the platform layer, and the middle platform layer; The business logic is the business function corresponding to the intelligent logistics application platform in the process of realizing the business needs of Party A users / Party B users, and the first domain logic and the second domain logic are the service functions that can be used universally by the intelligent logistics application platform in the process of realizing the business needs of different Party A users / Party B users; The business layer is used to convert the business needs of Party A users or Party B users into corresponding business items based on the configured business logic, and call the first domain logic of the platform layer and the second domain logic of the middle platform layer to process the business items to generate corresponding business orders or provide corresponding business waybills; When the user of Party A interacts with the application platform through the presentation layer and triggers the corresponding business layer, the business layer is used to orchestrate the business requirements input by the user of Party A based on the configured business logic, generate corresponding logistics services, and call the first domain logic of the platform layer and the second domain logic of the middle platform layer to verify the logistics services to generate corresponding business orders; When the user of Party B interacts with the application platform through the presentation layer and triggers the corresponding business layer, the business layer is used to call the business waybill from the middle platform layer through the platform layer based on the configured business logic to provide the user of Party B with order grabbing service; The middle platform layer is also used to convert the business order into the corresponding business waybill based on the configured second domain logic; When the intelligent logistics application platform adds a business function, the business needs of Party A users or Party B users are realized by configuring the business layer of the corresponding business logic and reusing the first domain logic of the platform layer and / or the second domain logic of the middle platform layer.

2. The intelligent logistics application platform according to claim 1, It is characterized in that When the business layer is triggered, the business layer is also used to call the first domain logic of the platform layer and / or the second domain logic of the middle platform layer to authenticate the identity of Party A users in order to distribute benefits and recommend preferential services.

3. The intelligent logistics application platform according to claim 1, It is characterized in that The first area of ​​logic includes risk control verification, price verification, and discount service verification. The platform layer is used to verify the logistics service based on the configured first domain logic, and the middle platform layer is used to convert the verified logistics service into a corresponding business order based on the configured second domain logic.

4. The intelligent logistics application platform according to claim 1, It is characterized in that When the business layer is triggered, the business layer is also used to call the first domain logic of the platform layer and / or the second domain logic of the middle platform layer to authenticate the identity of the Party B user, so as to provide an exclusive order grabbing channel and high-value business waybills.

5. The intelligent logistics application platform according to claim 4, It is characterized in that The first domain logic includes risk control verification and order quantity verification. The platform layer is used to verify the identity of the Party B user based on the configured first domain logic, and to review the business waybills snatched by the Party B user, and the middle platform layer is used to assign corresponding business waybills to the Party B users who have passed the verification and review based on the configured second domain logic.

6. The intelligent logistics application platform according to claim 1, It is characterized in that The presentation layer includes clients corresponding to the order creation end and the order fulfillment end, as well as an application program interface layer; The application program interface layer is used to customize corresponding application program interfaces according to the interactive characteristics of different clients; The client calls one or more of the business layers through its corresponding application program interface to process the business needs of Party A users or Party B users.

7. The intelligent logistics application platform according to claim 1, It is characterized in that The presentation layer, the business layer, the platform layer, the middle platform layer, and the basic layer adopt the Hexagonal Architecture in code implementation.

8. The intelligent logistics application platform according to claim 1, It is characterized in that The second domain logic includes order creation and waybill creation, and the CQRS+EventSourcing architecture is used to build the order creation and waybill creation models.