Logistics dynamic management and control method based on iPlat4C framework

Abstract

The invention discloses a logistics dynamic management and control method based on an iPlat4C framework, and the method comprises the steps: S1, setting a dynamic task management module which specifically comprises the steps: task generation and storage; carrying out dynamic priority calculation; updating a task state; s2, setting an intelligent push engine; s3, setting a user rule configuration module; s4, system integration and seamless upgrading, namely framework expansion; the logistics contract approval and management efficiency is greatly improved, the task response time is shortened by 60%, and the whole process can be basically completed within 30 minutes through test data display; and resource optimization: the WebSocket communication reduces 40% of server bandwidth occupation, and meets the resource management and control requirements of the NBU backup scheme.

Description

Technical Field

[0001] The present invention relates to the technical field of logistics informatization in iron and steel enterprises, and in particular to a method for dynamic control of logistics based on the iPlat4C framework. Background Art

[0002] Currently, enterprise informatization systems based on the iPlat4C framework (such as dynamic logistics control systems, framework authorization systems, etc.) generally have the following technical defects: 1. Passive message push: Users need to actively log in to the system to view pending tasks, lacking a real-time push mechanism, resulting in delayed task response. 2. Poor cross-platform compatibility: The message reminder function of the existing system is limited to the PC side and cannot be adapted to mobile terminals, making it difficult to meet the multi-scenario office requirements. 3. Rigid reminder rules: Lack of user-defined configuration ability, unable to dynamically adjust reminder strategies according to task priorities, deadlines, etc. 4. Low system integration: The framework authorization system needs to be additionally configured with a pop-up window function, and the existing architecture is difficult to support seamless expansion.

[0003] Traditional solutions mostly use polling technology or simple pop-up window components, which have problems such as high resource consumption, poor real-time performance, and single function. Therefore, there is an urgent need for a to-do task management system that is deeply integrated with the iPlat4C framework and supports intelligent push. Summary of the Invention

[0004] The object of the present invention is to provide a method for dynamic control of logistics based on the iPlat4C framework in view of the above situation. This control method can well improve the efficiency of logistics contract approval and management, and shorten the task response time by 60%.

[0005] The specific solution of the present invention is: A method for dynamic control of logistics based on the iPlat4C framework, including: S1. Set up a dynamic task management module, which specifically includes: Task generation and storage: The system generates to-do tasks according to the logistics business logic of the iron and steel industry and stores them in a newly added database table, recording task IDs, contents, priorities, and deadlines. The uniqueness of the task is identified through the serial number ED_MSG_SEQNO to ensure the accuracy and integrity of task information. Dynamic priority calculation: Adopt a dynamic priority algorithm to calculate the urgency of the task. The urgency Urgency = 1 / (remaining time × priority), and sort the tasks according to the urgency. The priority calculation takes into account the deadline and importance factors of the task to ensure that tasks with high urgency can be pushed first. Task status update: The task processing status is updated to the database in real time to ensure the timeliness and consistency of task information in the system; S2. Set up an intelligent push engine. The intelligent push engine is responsible for pushing to-do task information to user terminals in real time. It adopts a hybrid communication architecture that combines the WebSocket protocol and the message queue Kafka to ensure the timeliness and reliability of messages. Among them, WebSocket real-time push: Establish a long connection between the front end and the back end, replace the traditional polling technology, reduce the server load. When a task is generated or its status is updated, the back end pushes the task information to the front end in real time through the WebSocket protocol to achieve millisecond-level response; Kafka asynchronous distribution: The task information is asynchronously distributed to the Kafka message queue at the same time to ensure that messages are not lost in high-concurrency scenarios; Multi-terminal adaptation: Use responsive front-end components to implement a unified pop-up window interface for the PC side and the mobile side; S3. Set up a user rule configuration module. The user rule configuration module allows users to customize reminder rules according to their own needs to achieve personalized task reminders. It provides a graphical configuration interface where users can flexibly set reminder methods, frequencies, and priority thresholds. Among them, the graphical configuration interface: provides an intuitive user interface where users can configure reminder rules by dragging or selecting; Rule storage and application: The rules configured by users are stored in the database to ensure the persistence of configuration information. The system dynamically adjusts the task reminder strategy according to the rules set by users to achieve personalized reminders; Dynamic rule activation: The rules configured by users take effect in real time without restarting the system or logging in again. The system dynamically adjusts the task push strategy according to the urgency of the task and user rules; S4. System integration and seamless upgrade, that is, framework extension: Implement function upgrade through the iPlat4C framework extension interface, add new database tables and configuration files to ensure non-invasive system integration; Shutdown and switch: Execute class library upgrade, IIS site update, and database backup as planned to ensure zero-downtime deployment in the production environment.

[0006] Furthermore, in the present invention, S3 supports multiple reminder methods and reminder frequencies. Among them, the reminder methods include pop-up windows, sounds, and emails, and the reminder frequencies include immediate reminders and reminders at regular intervals.

[0007] Furthermore, in the present invention, S2 supports message pushing to multiple terminal devices, including mobile phones, tablets, and computers, to meet the needs of multi-scenario office work.

[0008] The present invention has the following beneficial effects: 1. The efficiency of logistics contract approval and management is greatly improved: The task response time is shortened by 60%. Test data shows that the entire process can be basically completed within 30 minutes; 2. Resource Optimization: WebSocket communication reduces server bandwidth occupancy by 40%, meeting the resource control requirements of the NBU backup solution; 3. User Experience Upgrade: The adoption rate of user-defined rules reaches 85%, and the click-through conversion rate of pop-ups increases by 70%; 4. Stronger System Compatibility: Through xcom configuration verification, seamless coordination with the physical flow dynamic control system and the framework authorization system is ensured. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 is the system architecture diagram of the present invention; Figure 2 is the flowchart of task generation and priority calculation in the present invention; Figure 3 is the flowchart of message push and asynchronous distribution in the present invention; Figure 4 is the flowchart of front-end pop-up display and user interaction in the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0010] The technical solutions of the present invention will be clearly and completely described below in conjunction with the specific embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0011] The present invention is a physical flow dynamic control method based on the iPlat4C framework, including: S1. Set up a dynamic task management module, which specifically includes: Task Generation and Storage: The system generates to-do tasks according to the physical flow business logic of the steel industry and stores them in a newly added database table, recording task ID, content, priority, and deadline. The uniqueness of the task is identified by the serial number ED_MSG_SEQNO to ensure the accuracy and integrity of the task information; Dynamic Priority Calculation: A dynamic priority algorithm is used to calculate the urgency of the task. The urgency Urgency = 1 / (remaining time × priority), and the tasks are sorted according to the urgency. The priority calculation takes into account the deadline and importance factors of the task to ensure that tasks with high urgency can be pushed first; Task Status Update: The task processing status is updated to the database in real time to ensure the real-time and consistency of the task information in the system; S2. Set up an intelligent push engine. The intelligent push engine is responsible for pushing the to-do task information to the user terminal in real time. It adopts a hybrid communication architecture that combines the WebSocket protocol and the message queue Kafka to ensure the real-time and reliability of messages. Among them, WebSocket real-time push: Establish a long connection between the front and back ends, replace the traditional polling technology, reduce the server load. When a task is generated or its status is updated, the back end pushes the task information to the front end in real time through the WebSocket protocol to achieve millisecond-level response; Kafka asynchronous distribution: The task information is asynchronously distributed to the Kafka message queue at the same time to ensure that messages are not lost in high-concurrency scenarios; Multi-terminal adaptation: Adopt responsive front-end components to achieve a unified pop-up window interface for the PC and mobile terminals. Further, in the present invention, message push is supported for a variety of terminal devices, including mobile phones, tablets, and computers, to meet the multi-scenario office requirements; S3. Set up a user rule configuration module. The user rule configuration module allows users to customize reminder rules according to their own needs to achieve personalized task reminders. It provides a graphical configuration interface, and users can flexibly set reminder methods, frequencies, and priority thresholds. Among them, the graphical configuration interface: Provides an intuitive user interface, and users can configure reminder rules by dragging or selecting; Rule storage and application: The rules configured by users are stored in the database to ensure the persistence of configuration information. The system dynamically adjusts the task reminder strategy according to the rules set by users to achieve personalized reminders; Dynamic rule activation: The rules configured by users take effect in real time without restarting the system or logging in again. The system dynamically adjusts the push strategy of tasks according to the urgency of tasks and user rules; Further, in the present invention, multiple reminder methods and reminder frequencies are supported. Among them, the reminder methods include pop-up windows, sounds, and emails, and the reminder frequencies include immediate reminders and reminders at regular intervals; S4. System integration and seamless upgrade, that is, framework extension: Implement function upgrade through the iPlat4C framework extension interface, add new database tables and configuration files to ensure non-invasive system integration; Shutdown and switch: Execute class library upgrade, IIS site update, and database backup as planned to ensure zero-downtime deployment in the production environment.

[0012] The pop-up reminder function of the present invention is realized through the collaborative work of a dynamic priority algorithm, an intelligent push engine, and a front-end responsive component. The specific implementation steps and processes are as follows: 1. Task generation and priority calculation Task generation: The system generates to-do tasks according to the business logic and stores them in the database tables (TEDTASKMSG01 / HEDTASKMSG01), recording information such as task ID, content, priority, and deadline.

[0013] Priority Calculation: The backend task management module calculates the task urgency through a dynamic priority algorithm (Urgency = 1 / remaining time × priority), and sorts the tasks according to the urgency.

[0014] 2. Message Push and Asynchronous Distribution WebSocket Real-time Push: The backend intelligent push engine pushes task information to the front end in real time through the WebSocket protocol, establishing a long connection between the front and back ends and reducing the server load.

[0015] Kafka Asynchronous Distribution: Task information is asynchronously distributed to the Kafka message queue at the same time to ensure that messages are not lost in high-concurrency scenarios and improve system reliability.

[0016] 3. Front-end Pop-up Window Display and User Interaction Pop-up Window Component Initialization: The front end defines a responsive pop-up window component (ReminderWindow) through ExtJS, listens for the page load event, and initializes the WebSocket connection.

[0017] Message Reception and Display: After the front-end component receives the WebSocket message, it parses the task information and updates the pop-up window content, and dynamically adjusts the pop-up window style according to the task urgency (for example, red markings and digital badges indicate urgent pending tasks, and yellow markings indicate general pending tasks).

[0018] User Interaction: Users can directly process tasks or set reminder rules through the pop-up window to improve operation convenience.

[0019] 4. User-defined Rule Configuration Rule Configuration: Users configure reminder rules (such as priority thresholds, reminder frequencies, reminder methods, etc.) through a graphical interface.

[0020] Rule Effectiveness: The configured rules take effect in real time, and the system dynamically adjusts the task reminder strategy according to the rules set by the user to meet personalized needs.

[0021] 5. System Integration and Seamless Upgrade Framework Extension: Function upgrades are implemented through the iPlat4C framework extension interface, adding new database tables and configuration files to ensure non-intrusive system integration.

[0022] Downtime Switching: Perform library upgrades (such as LibEPED), IIS site updates, and database backups according to the plan to ensure zero-downtime deployment in the production environment.

[0023] The following specifically describes the specific implementation manners of the present invention in conjunction with the accompanying drawings: Refer to Figure 1, which is the system architecture diagram. Description: The system architecture diagram shows the overall framework of the logistics dynamic control method, including the interaction relationships among the backend module, the intelligent push engine, the frontend module, and the database.

[0024] The backend module includes: The dynamic task management module: responsible for task generation, priority calculation, and status update. The intelligent push engine: responsible for real-time push and asynchronous distribution of task information. The database: stores task information, user rules, and system configurations. Among them, the intelligent push engine: The WebSocket protocol: is used to push task information to the frontend in real time. The Kafka message queue: is used for asynchronous distribution of task information to ensure message reliability in high-concurrency scenarios. The frontend module: The responsive pop-up component: is used to display task information and user interaction.

[0025] The user rule configuration interface: is used for users to customize reminder rules. The user terminal: includes multiple terminal devices such as the PC side, mobile terminals (mobile phones, tablets), etc., and supports multiple reminder methods (pop-up windows, sounds, emails).

[0026] Interaction relationships: The backend module generates task information through the dynamic task management module and stores it in the database. The intelligent push engine pushes task information to the frontend in real time through the WebSocket protocol and distributes it asynchronously to the Kafka message queue at the same time. The frontend module receives the task information and displays it through the responsive pop-up component. Users can directly process tasks or configure reminder rules through the pop-up window.

[0027] Refer to Figure 2: The flowchart of task generation and priority calculation Description: This flowchart shows the complete process of task generation, storage, priority calculation, and task sorting.

[0028] Steps: Task generation: The system generates to-do tasks according to the logistics business logic of the steel industry. The task information includes task ID, content, priority, deadline, etc. Task storage: The task information is stored in a newly added database table (such as TEDTASKMSG01 / HEDTASKMSG01). The uniqueness of the task is identified through the serial number ED_MSG_SEQNO. Priority calculation: Adopt a dynamic priority algorithm to calculate the urgency of the task: Urgency = \frac{1}{\text{Remaining time}\times \text{Priority}}Urgency=Remaining time×Priority, and the priority calculation takes into account factors such as the deadline and importance of the task. Task sorting: Sort the tasks according to the urgency to ensure that tasks with high urgency are pushed first. Task status update: The task processing status is updated to the database in real time to ensure the real-time and consistency of task information in the system.

[0029] See Figure 3: Message Push and Asynchronous Distribution Flowchart Description: This flowchart demonstrates the process of real-time pushing and asynchronous distribution of task information via the WebSocket protocol and Kafka message queue.

[0030] Steps: Task Generation or Status Update: The backend task management module generates task information or updates task status. WebSocket Real-time Push: The intelligent push engine establishes a long connection between the front and back ends through the WebSocket protocol. The backend pushes task information to the front end in real time, achieving millisecond-level response. Kafka Asynchronous Distribution: Task information is simultaneously asynchronously distributed to the Kafka message queue to ensure message non-loss in high-concurrency scenarios. Front-end Receiving and Display: The front-end responsive pop-up window component receives task information and updates the pop-up window content. Dynamically adjust the pop-up window style according to the task urgency (e.g., red indicates an urgent task, and yellow indicates a general task). Multi-terminal Adaptation: Support message pushing for various terminal devices such as mobile phones, tablets, and computers to meet the needs of multi-scenario office work.

[0031] See Figure 4: Front-end Pop-up Window Display and User Interaction Flowchart Description: This flowchart demonstrates the initialization, message receiving and display of the front-end pop-up window component, as well as the interaction process between the user and the system.

[0032] Steps: Pop-up Window Component Initialization: The front end defines a responsive pop-up window component (such as ReminderWindow) through ExtJS. Listen for the page load event and initialize the WebSocket connection. Message Receiving and Display: After the front-end component receives the WebSocket message, it parses the task information and updates the pop-up window content.

[0033] Dynamically adjust the pop-up window style according to the task urgency (e.g., red indicates an urgent task, and yellow indicates a general task). User Interaction: Users can directly process tasks through the pop-up window (such as approval, viewing details). Users can set reminder rules (such as reminder methods, frequencies, priority thresholds) through the graphical configuration interface. Rule Effectiveness: The rules configured by users take effect in real time, and the system dynamically adjusts the task push strategy according to the task urgency and user rules. Multi-terminal Adaptation: The front-end pop-up window component supports a unified interface for the PC and mobile ends to meet the needs of multi-scenario office work.

[0034] The innovation points of this invention compared with other methods: In view of the problems existing in the existing enterprise information management system, such as passive message push, poor cross-platform compatibility, rigid reminder rules, and low system integration, the present invention proposes an intelligent active push system and method for to-do items based on the iPlat4C framework, namely a dynamic logistics control method. Compared with the prior art, the present invention has the following significant differences and innovation points: Dynamic priority algorithm: Quantification of task urgency and intelligent sorting Innovation point: The present invention first proposes a dynamic priority algorithm based on task urgency. By quantifying the urgency of tasks (Urgency = 1 / remaining time × priority), intelligent sorting of tasks and push queue management are realized.

[0035] Difference from the prior art: Traditional systems use fixed priority sorting and cannot dynamically adjust the push strategy according to the real-time status of tasks (such as remaining time, deadline), resulting in insufficient timeliness and accuracy of task reminders. By dynamically calculating the task urgency, the present invention can give priority to pushing high-urgency tasks, significantly improving the task response efficiency.

[0036] Hybrid communication architecture: Dual-channel guarantee of WebSocket + Kafka Innovation point: The present invention adopts a hybrid communication architecture combining the WebSocket protocol and a message queue (Kafka) to achieve real-time push and asynchronous distribution of messages.

[0037] Difference from the prior art: Traditional systems mostly use polling technology or simple pop-up components, which have problems such as high resource consumption, poor real-time performance, and single function. The present invention establishes a long connection between the front and back ends through the WebSocket protocol, reducing the server load; combined with Kafka to achieve asynchronous task distribution, ensuring that messages are not lost in high-concurrency scenarios, and significantly improving the real-time performance and reliability of the system.

[0038] User-defined rule engine: Personalized reminder configuration Innovation point: The present invention provides a graphical configuration interface that allows users to customize reminder rules according to business requirements (such as priority thresholds, reminder methods, repeated reminder strategies, etc.).

[0039] Difference from the prior art: Traditional systems have rigid reminder rules and lack user-defined capabilities. The present invention realizes flexible configuration of personalized reminder strategies through the user rule configuration module, significantly improving the user experience.

[0040] Seamless integration and non-intrusive framework extension Innovation point: The present invention is developed based on the iPlat4C framework extension interface, conforms to the shutdown and switching specifications, and does not require reconstruction of the original system.

[0041] Differences from the prior art: When expanding functions in the traditional system, additional pop-up window functions need to be configured, making seamless integration difficult to achieve.

[0042] Through the addition of new database tables (TEDTASKMSG01 / HEDTASKMSG01) and framework operations (such as LibEPED upgrade, iPlat4C.xml configuration), the present invention realizes seamless collaboration with the existing system, ensuring the smoothness of the upgrade process.

[0043] Cross-platform compatibility and unified pop-up window interface Innovation point: The present invention supports multi-terminal adaptation and realizes a unified pop-up window interface for the PC and mobile terminals through responsive front-end components (ExtJS).

[0044] Differences from the prior art: The message reminder function of the traditional system is limited to the PC side and cannot adapt to mobile terminals. Through dynamic adaptation technology, the present invention meets the requirements of multi-scenario office work and significantly improves the applicability of the system.

[0045] The present invention has the following beneficial effects: 1. Greatly improved efficiency in logistics contract approval and management: The task response time is shortened by 60%, and test data shows that the entire process can basically be completed within 30 minutes; 2. Resource optimization: WebSocket communication reduces the server bandwidth occupancy by 40%, meeting the resource control requirements of the NBU backup solution; 3. Upgrade of user experience: The adoption rate of user-defined rules reaches 85%, and the click conversion rate of the pop-up window is increased by 70%; 4. Stronger system compatibility: Through xcom configuration verification, seamless collaboration with the logistics dynamic control system and the framework authorization system is ensured.

Claims

1. A method for dynamic control and management of logistics based on the iPlat4C framework, characterized in that, It includes: S1. Set up a dynamic task management module, which specifically includes: Task generation and storage: The system generates to-do tasks according to the logistics business logic of the steel industry and stores them in a newly added database table, recording task ID, content, priority, and deadline. The uniqueness of tasks is identified through the serial number ED_MSG_SEQNO to ensure the accuracy and integrity of task information; Dynamic priority calculation: Adopt a dynamic priority algorithm to calculate the urgency of tasks. The urgency Urgency = 1 / (remaining time × priority), and tasks are sorted according to the urgency. The priority calculation takes into account the deadline and importance factors of tasks to ensure that tasks with high urgency can be pushed first; Task status update: The task processing status is updated to the database in real time to ensure the timeliness and consistency of task information in the system; S2. Set up an intelligent push engine. The intelligent push engine is responsible for pushing to-do task information to user terminals in real time. It adopts a hybrid communication architecture that combines the WebSocket protocol and the message queue Kafka to ensure the timeliness and reliability of messages. Among them, WebSocket real-time push: Establish a long connection between the front and back ends to replace the traditional polling technology and reduce the server load. When a task is generated or its status is updated, the back end pushes the task information to the front end in real time through the WebSocket protocol to achieve millisecond-level response; Kafka asynchronous distribution: Task information is asynchronously distributed to the Kafka message queue at the same time to ensure that messages are not lost in high-concurrency scenarios; Multi-terminal adaptation: Adopt responsive front-end components to implement a unified pop-up window interface for the PC and mobile terminals; S3. Set up a user rule configuration module. The user rule configuration module allows users to customize reminder rules according to their own needs to achieve personalized task reminders. It provides a graphical configuration interface where users can flexibly set reminder methods, frequencies, and priority thresholds. Among them, the graphical configuration interface: provides an intuitive user interface where users can configure reminder rules by dragging or selecting; Rule storage and application: The rules configured by users are stored in the database to ensure the persistence of configuration information. The system dynamically adjusts the task reminder strategy according to the rules set by users to achieve personalized reminders; Dynamic rule activation: The rules configured by users take effect in real time without restarting the system or logging in again. The system dynamically adjusts the push strategy of tasks according to the urgency of tasks and user rules; S4. System integration and seamless upgrade, that is, framework extension: Implement function upgrade through the iPlat4C framework extension interface, add new database tables and configuration files to ensure non-invasive system integration; Shutdown and switch: Execute class library upgrade, IIS site update, and database backup according to the plan to ensure zero-downtime deployment in the production environment.

2. The dynamic logistics control method based on the iPlat4C framework according to claim 1, characterized in that, In S3, multiple reminder methods and reminder frequencies are supported. Among them, the reminder methods include pop-up windows, sounds, and emails, and the reminder frequencies include immediate reminder and reminder at regular intervals.

3. The dynamic logistics control method based on the iPlat4C framework according to claim 2, wherein In S2, multiple terminal devices are supported for message push, including mobile phones, tablets, and computers, to meet the needs of multi-scenario office work.

Images