Logistics trajectory push method and apparatus, and computer device and storage medium

Abstract

The embodiments of the present application belong to the technical field of logistics data processing. Provided are a logistics trajectory push method and apparatus, and a computer device and a storage medium. The method comprises: receiving a push rule configuration request sent by a user end, wherein the push rule configuration request comprises: a configuration object category, configuration requirement information and encryption requirement information (S101); on the basis of the configuration object category and the configuration requirement information, performing rule configuration on preset candidate push rule configuration items, so as to obtain a target push rule configuration item (S102); on the basis of the encryption requirement information, screening preset candidate encryption configuration items to obtain a selected encryption configuration item (S103); on the basis of the target push rule configuration item and the selected encryption configuration item, performing push rule construction to obtain a target push rule (S104); and on the basis of the target push rule, pushing pre-generated logistics trajectory information to the user end (S105).

Description

Logistics tracking push methods and devices, computer equipment and storage media

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411181588.5, filed on August 27, 2024, entitled "Method and Apparatus for Pushing Logistics Tracks, Computer Equipment and Storage Medium", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of logistics data processing technology, and in particular to a logistics trajectory push method and apparatus, computer equipment and storage medium. Background Technology

[0004] Logistics application services facilitate use by users across various industries, improving the efficiency of logistics operations. During the use of these applications, logistics tracking notifications are a feature that significantly impacts user experience. Traditional logistics tracking notifications follow pre-configured rules, failing to personalize tracking to meet the needs of different users and thus negatively affecting the user experience. Therefore, achieving personalized logistics tracking notifications has become a pressing technical challenge. Summary of the Invention

[0005] The main objective of this application is to propose a logistics trajectory push method and apparatus, computer equipment and storage medium, which aims to realize personalized logistics trajectory push and improve the flexibility of logistics trajectory push.

[0006] To achieve the above objectives, a first aspect of this application proposes a logistics trajectory push method, the method comprising: receiving a push rule configuration request sent by a user terminal; wherein the push rule configuration request includes: configuration object category, configuration requirement information, and encryption requirement information;

[0007] Based on the configuration object category and the configuration requirement information, the preset candidate push rule configuration items are configured to obtain the target push rule configuration items;

[0008] Selected encryption configuration items are selected from preset candidate encryption configuration items based on the encryption requirement information;

[0009] The target push rule is constructed based on the target push rule configuration item and the selected encryption configuration item;

[0010] According to the target push rules, the pre-generated logistics trajectory information is pushed to the user terminal.

[0011] To achieve the above objectives, a second aspect of this application provides a logistics trajectory tracking device, the device comprising:

[0012] The request receiving module is used to receive push rule configuration requests sent by the user terminal; wherein, the push rule configuration request includes: configuration object category, configuration requirement information and encryption requirement information;

[0013] The configuration module is used to configure the preset candidate push rule configuration items according to the configuration object category and the configuration requirement information to obtain the target push rule configuration item;

[0014] The filtering module is used to filter out the selected encryption configuration items from the preset candidate encryption configuration items based on the encryption requirement information;

[0015] The rule building module is used to build push rules based on the target push rule configuration items and the selected encryption configuration items to obtain the target push rules;

[0016] The push module is used to push pre-generated logistics trajectory information to the user terminal according to the target push rules.

[0017] To achieve the above objectives, a third aspect of the present application provides a computer device, the computer device including a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the method described in the first aspect.

[0018] To achieve the above objectives, a fourth aspect of the present application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method described in the first aspect.

[0019] The logistics trajectory push method, apparatus, computer device, and storage medium proposed in this application receive a push rule configuration request from a user terminal. This request includes a configuration object category, configuration requirement information, and encryption requirement information. Based on the configuration object category and configuration requirement information, candidate push rule configuration items are configured to obtain a target push rule configuration item, thus achieving personalized push rule configuration. Simultaneously, based on the encryption requirement information, a selected encryption configuration item is selected from the candidate encryption configuration items to achieve custom settings for logistics trajectory encryption rules. Finally, a target push rule is constructed based on the target push rule configuration item and the selected encryption configuration item, and logistics trajectory information is pushed to the user terminal according to the target push rule. This achieves personalized push of logistics trajectory information, improving not only the user experience of logistics applications but also the flexibility of logistics trajectory information push. Attached Figure Description

[0020] Figure 1 is a flowchart of the logistics trajectory push method provided in an embodiment of this application;

[0021] Figure 2 is a flowchart of step S102 in Figure 1;

[0022] Figure 3 is a flowchart of step S202 in Figure 2;

[0023] Figure 4 is a flowchart of step S302 in Figure 3;

[0024] Figure 5 is a flowchart of step S103 in Figure 1;

[0025] Figure 6 is a flowchart of a logistics trajectory push method provided in another embodiment of this application;

[0026] Figure 7 is a flowchart of a logistics trajectory push method provided in another embodiment of this application;

[0027] Figure 8 is an overall interactive flowchart of the logistics trajectory push method provided in the embodiment of this application;

[0028] Figure 9 is a schematic diagram of the logistics trajectory push device provided in an embodiment of this application;

[0029] Figure 10 is a schematic diagram of the hardware structure of the computer device provided in an embodiment of this application. Detailed Implementation

[0030] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0031] It should be noted that although functional modules are divided in the device schematic diagram and a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first," "second," etc., in the specification, claims, and the aforementioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0032] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0033] First, let's analyze some of the terms used in this application:

[0034] Retry strategy: This refers to a strategy where the system automatically attempts to re-execute an operation in the face of failure or error. This strategy is used in various scenarios, such as function computation, API requests, and database connections, aiming to improve system stability and reliability. Retry strategies can include different implementations, such as linear retries, exponential backoff, and random backoff, each with its applicable scenarios and advantages.

[0035] Idempotent strategy: This focuses on ensuring that the same business operation yields consistent results and effects regardless of how many times it is executed. This strategy is particularly important in distributed systems, helping to handle duplicate or concurrent requests and preventing data inconsistencies or state errors caused by executing the same operation multiple times.

[0036] Circuit breaking is an important system design technique used to prevent a cascading failure effect when a system faces anomalies or high loads, thereby improving system stability and reliability. Based on the principle of a fuse, circuit breaking temporarily interrupts service calls when a service or system detects an anomaly or high load, preventing excessive resource consumption and request backlog. In its implementation, a circuit breaking strategy typically includes a state machine with three states: Open, Half-Open, and Closed. In the Open state, all requests are rejected; in the Half-Open state, the system attempts to reconnect or restore the service; and in the Closed state, the system processes requests normally.

[0037] MySQL is a widely used open-source relational database management system (RDBMS) based on the SQL (Structured Query Language) language. MySQL supports multiple operating systems, including various Unix and Linux variants, Windows, and macOS. MySQL provides a variety of storage engines, allowing developers to choose different data storage and indexing strategies based on application requirements.

[0038] ClickHouse is a high-performance columnar database management system for online analytical processing (OLAP) queries. ClickHouse is suitable for scenarios requiring fast, complex queries, such as web analytics, advertising technology, and e-commerce.

[0039] Hive is a data warehouse software project used to query and manage big data stored in distributed storage systems (such as Hadoop), allowing users to perform operations such as data querying, data summarization, and exploratory data analysis.

[0040] With the rapid popularization of the internet, the logistics industry plays a crucial role in the transportation of goods across various sectors, actively promoting digital transformation to improve operational efficiency. Within the logistics industry, logistics applications are developed to enhance the efficiency of logistics transactions, allowing users to handle logistics matters and track shipments. In these applications, the logistics track is pushed to users periodically, enabling them to track the current delivery progress. However, these push notifications follow fixed rules, failing to personalize the rules to meet individual user needs. This negatively impacts the user experience and reduces the flexibility of logistics track updates.

[0041] Based on this, embodiments of this application provide a logistics trajectory push method and apparatus, computer equipment and storage medium, which aim to personalize the logistics push rules according to the user's demand information for logistics push, so that when generating logistics trajectories, the logistics trajectory is pushed according to the pre-configured logistics push rules, thereby realizing personalized recommendations for logistics trajectories, which not only improves the user's experience in using logistics applications, but also improves the flexibility of logistics trajectory push.

[0042] The logistics trajectory push method, apparatus, computer equipment, and storage medium provided in this application are specifically described through the following embodiments. First, the logistics trajectory push method in this application embodiment is described.

[0043] The embodiments of this application can acquire and process relevant data based on artificial intelligence technology. Artificial intelligence (AI) refers to the theories, methods, technologies, and application systems that use digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use that knowledge to obtain optimal results.

[0044] Foundational technologies for artificial intelligence generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data processing, operating / interactive systems, and mechatronics. AI software technologies mainly encompass computer vision, robotics, biometrics, speech processing, natural language processing, and machine learning / deep learning.

[0045] The logistics trajectory push method provided in this application relates to the field of logistics data processing technology. The logistics trajectory push method provided in this application can be applied to a terminal, a server, or software running on either a terminal or a server. In some embodiments, the terminal can be a smartphone, tablet, laptop, desktop computer, etc.; the server can be configured as an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the software can be an application implementing the logistics trajectory push method, but is not limited to the above forms.

[0046] This application can be used in a wide variety of general-purpose or special-purpose computer system environments or configurations. Examples include: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer computer devices, network PCs, minicomputers, mainframe computers, and distributed computing environments including any of the above systems or devices. This application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform specific tasks or implement specific abstract data types. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0047] Figure 1 is an optional flowchart of the logistics trajectory push method provided in the embodiment of this application. The method in Figure 1 may include, but is not limited to, steps S101 to S105.

[0048] Step S101: Receive a push rule configuration request sent by the user terminal; wherein, the push rule configuration request includes: configuration object category, configuration requirement information and encryption requirement information;

[0049] Step S102: Configure the preset candidate push rule configuration items according to the configuration object category and configuration requirement information to obtain the target push rule configuration items;

[0050] Step S103: Select the encryption configuration item from the preset candidate encryption configuration items based on the encryption requirement information;

[0051] Step S104: Construct push rules based on the target push rule configuration items and the selected encryption configuration items to obtain the target push rules;

[0052] Step S105: Push the pre-generated logistics trajectory information to the user terminal according to the target push rules.

[0053] Steps S101 to S105, as illustrated in this embodiment, involve receiving a push rule configuration request from the user terminal. This request includes a configuration object category, configuration requirement information, and encryption requirement information. Based on the configuration object category and configuration requirement information, candidate push rule configuration items are configured to obtain a target push rule configuration item, thus achieving personalized push rule configuration. Simultaneously, based on the encryption requirement information, a selected encryption configuration item is selected from the candidate encryption configuration items, enabling custom settings for logistics trajectory encryption rules. Finally, a target push rule is constructed based on the target push rule configuration item and the selected encryption configuration item, and logistics trajectory information is pushed to the user terminal according to the target push rule. This achieves personalized delivery of logistics trajectory information, improving both the user experience of logistics applications and the flexibility of logistics trajectory information delivery.

[0054] It should be noted that the logistics tracking push method is applied on the server side. The server hosts a logistics tracking system, which includes a push submodule, storage media, and a dedicated encryption machine. The logistics tracking system receives registration requests and registers the user client accordingly. Upon completion of registration, registration information is generated and stored on the storage media. After registering on the server side, the user client can configure logistics push rules. Specifically, the logistics tracking system receives push rule configuration requests and constructs the target push rules within the push submodule, enabling personalized push rule configuration.

[0055] In step S101 of some embodiments, a push rule configuration request is sent by the user terminal to configure the push rules for logistics trajectories. The push rule configuration request includes: a configuration object category, configuration requirement information, and encryption requirement information. The configuration object category represents the user category, which is determined based on the push method used by the user terminal. Push methods include standard push methods and custom push methods. The standard push method determines the configuration object category as a standard push category, while the custom push method determines it as a personalized push category. Therefore, the push method requiring push rules can be determined based on different configuration object categories. The configuration requirement information represents the user terminal's requirements for logistics push notifications and is also personalized configuration information for logistics push notifications. The encryption requirement information represents the user terminal's security requirements for pushing logistics trajectory information. The encryption requirement information determines what type of security method should be used to set up the push notification of logistics trajectory information.

[0056] Please refer to Figure 2. In some embodiments, step S102 may include, but is not limited to, steps S201 to S202:

[0057] Step S201: Filter the candidate push rule configuration items according to the configuration object category to obtain the selected push rule configuration item;

[0058] Step S202: Configure the selected push rule configuration item according to the configuration requirement information to obtain the target push rule configuration item.

[0059] In step S201 of some embodiments, the candidate push rule configuration items corresponding to different configuration object categories are different, and each candidate push rule configuration item is set with a push category label. The target category label is filtered from the push category labels according to the configuration object category, and the candidate push rule configuration item corresponding to the target category label is selected as the push rule configuration item.

[0060] Specifically, the configuration object categories include standard push categories and personalized push categories. The selected push rule configuration items for the standard push category are pre-configured standard push rule items in the logistics tracking system, while the selected push rule configuration items for the personalized push category are push rule items that can be arbitrarily combined in the logistics tracking system. It should be noted that the standard rule items only need to be set; the receiving address and track push nodes for the logistics track are configured, and the track push nodes represent which node the logistics track reaches that needs to be pushed to the user. For example, the logistics track includes multiple track nodes, including: pickup node, loading node, return node, and delivery node. The track push nodes can be selected from the track nodes, making logistics track push more flexible.

[0061] In step S202 of some embodiments, rule configuration is performed on the selected push rule configuration item according to the configuration requirement information. Different selected push rule configuration items can configure different items, and the configuration requirement information also differs for different configuration object categories. As disclosed above, for the configuration object category of the standard push category, the configuration requirement information mainly includes the receiving address and trajectory push node, changing the receiving address and trajectory push node in the selected push rule configuration item. For the configuration object category of the personalized push category, it can be a custom setting for each rule configuration item in the selected push rule configuration item, and the configuration requirement information is the configuration requirement for each rule configuration item.

[0062] It's worth noting that the logistics tracking information push settings allow you to configure different tracking notifications for users in different states. For example, when a pickup node notification is sent, the corresponding user's state is "waiting for pickup notification," and when a loading node notification is sent, the corresponding user's state is "waiting for loading notification." Therefore, you can set different tracking node notifications for different user states to achieve personalized logistics tracking settings.

[0063] In steps S201 to S202 of this embodiment, the selected push rule configuration item corresponding to the configuration object category is first selected from the candidate push rule configuration items, and then the selected push rule configuration item is configured according to the configuration requirement information to obtain the personalized target push rule configuration item, thereby realizing the custom setting of the push rule configuration item.

[0064] As previously disclosed, the configuration requirements include: push confirmation configuration information, retry configuration information, push security configuration information, and trajectory processing configuration information; the selected push rule configuration items include: original push confirmation rule configuration items, original push retry rule configuration items, original push security rule configuration items, and original logistics trajectory processing rule configuration items. The push confirmation configuration information is used to set the original push confirmation rule configuration items, that is, to set the rules for confirming the completion of the push of logistics trajectory information. The retry configuration information is used to set the original push retry rule configuration items, setting the retry rules for failed push of logistics trajectory information. The push security configuration information is used to set the original push security rule configuration items, setting the push rules for how to push logistics trajectory information without affecting the operation of the user terminal.

[0065] Specifically, the original push confirmation rule configuration item is used to determine the rules for successful pushes, the original push retry rule configuration item is used to set the rules for retrying after a push fails, the original push security rule configuration item is used to set the security rules for the push process, and the original logistics trajectory processing rule configuration item is used to set the rules for processing logistics trajectories.

[0066] Please refer to Figure 3. In some embodiments, step S202 may include, but is not limited to, steps S301 to S305:

[0067] Step S301: Configure the original push confirmation rule configuration item according to the push confirmation configuration information to obtain the selected push confirmation rule configuration item;

[0068] Step S302: Configure the original push retry rule configuration item according to the retry configuration information to obtain the selected push retry rule configuration item;

[0069] Step S303: Configure the original push security rule configuration items according to the push security configuration information to obtain the selected push security rule configuration items;

[0070] Step S304: Configure the original logistics trajectory processing rule configuration items according to the trajectory processing configuration information to obtain the selected logistics trajectory processing rule configuration items;

[0071] Step S305: Construct the target push rule configuration item based on the selected push confirmation rule configuration item, the selected push retry rule configuration item, the selected push security rule configuration item, and the selected logistics trajectory processing rule configuration item.

[0072] In step S301 of some embodiments, the original push confirmation rule configuration item is also called an idempotent policy, and the idempotent policy is a policy for confirming the successful push of logistics trajectory information. The push confirmation configuration information is used to set the configuration information for the idempotent policy. Specifically, rules are set for the original push confirmation rule configuration item, that is, the idempotent policy is set according to the push confirmation configuration information. If the push confirmation configuration information indicates that an idempotent policy does not need to be set, the idempotent policy is turned off. If the push confirmation configuration information indicates that an idempotent policy needs to be set and provides idempotent policy setting rules, the idempotent policy is turned on, and the idempotent policy is set according to the idempotent setting rules.

[0073] Specifically, the idempotent strategy involves setting up middleware. After a logistics trajectory information push is completed, the time of the logistics trajectory generation and the logistics trajectory node are used as the push value, which is then stored in a cache space in the storage medium. When pushing logistics trajectory information again, the push value is first searched in the cache space. If a push value corresponding to the logistics trajectory information exists, the push is not performed again; otherwise, the logistics trajectory information is pushed to the user's end. Therefore, by pre-setting an idempotent strategy, accurate pushes of logistics trajectory information can be achieved, reducing duplicate pushes of logistics trajectory information.

[0074] In step S302 of some embodiments, the original push retry rule configuration item is also called the retry strategy. The retry strategy is the strategy for re-pushing logistics trajectory information after the push fails. The retry configuration information is used to set the retry strategy, that is, to set how to re-push logistics trajectory information to the user terminal after the push fails.

[0075] Specifically, the retry strategy configuration is implemented by the push submodule, which performs time-step retry push based on the MySQL statements in the retry configuration information to complete the retry strategy settings, so as to maximize the successful push of logistics trajectory information to the user end.

[0076] In step S303 of some embodiments, the original push security rule configuration is also called a circuit breaker policy, and the circuit breaker policy is used to ensure that the push of logistics trajectory information to the user terminal does not affect the normal operation of the user terminal. The push security configuration information is also called the circuit breaker policy configuration information, which is used to configure and set the circuit breaker policy.

[0077] Specifically, circuit breaker policies prevent client systems within the user terminal from being overwhelmed, and different user terminals require different circuit breaker policies. For example, if the circuit breaker policy uses a time window algorithm to count the proportion of slow calls within 5 seconds, and the slow call proportion exceeds 60%, the client system on the user terminal is circuit-broken, meaning the connection is stopped, and an anomaly assessment is performed again after 5 seconds. It should be noted that slow calls refer to an increased response time for logistics tracking information push notifications. For example, if feedback is received from the user terminal 3 seconds after logistics tracking information is pushed, and a slow call occurs—meaning feedback is received after 3 seconds, and the proportion of feedback received after 3 seconds reaches 60%—it is considered a slow call in logistics tracking information push notifications, requiring the generation of an alarm message to prompt maintenance personnel to repair the logistics application. It should be noted that the feedback time varies among different user terminals, so the feedback time and the proportion of slow call occurrences are set according to the push security configuration information of different user terminals to achieve targeted circuit breaker policy settings, thereby improving the applicability to different types of user terminals.

[0078] In step S304 of some embodiments, the original logistics trajectory processing rule configuration item is also called the logistics trajectory processing logic. The logistics trajectory processing logic is used to set the processing order of logistics trajectory information. The trajectory processing configuration information is used to configure the logistics trajectory processing logic, that is, to set the processing logic of logistics trajectory information.

[0079] In step S305 of some embodiments, the target push rule configuration item is obtained by combining the selected push confirmation rule configuration item, the selected push retry rule configuration item, the selected push security rule configuration item, and the selected logistics trajectory processing rule configuration item. This involves combining the configured logistics trajectory processing logic, retry strategy, idempotent strategy, and circuit breaker strategy. Therefore, by integrating the processing logic and strategies involved in the logistics push process into the target push rule configuration item, the custom setting of logistics push rules can be achieved, improving the flexibility of logistics trajectory information push.

[0080] In steps S301 to S305 of this embodiment, the idempotency strategy, retry strategy, circuit breaker strategy and logistics trajectory processing logic are customized. Then, the customized idempotency strategy, retry strategy, circuit breaker strategy and logistics trajectory processing logic are combined into a target push rule configuration item to realize the customized configuration of logistics trajectory push rules. The configuration process involves multiple strategies and processing logics of the push process, so as to realize a more comprehensive personalized push rule configuration.

[0081] Referring to Figure 4, in some embodiments, the original push retry rule configuration item includes: original retry time interval, original number of retries, and original single retry duration. The original push retry rule configuration item is a retry strategy, and the retry strategy needs to configure the duration and interval of each retry and set the number of retries. Therefore, the retry strategy includes the original retry time interval, the original number of retries, and the original single retry duration. The original retry time interval is the time interval between each retry of pushing logistics trajectory information, the original number of retries is the number of times the logistics trajectory information needs to be retried, and the original single retry duration is the duration of each retried push of logistics trajectory information.

[0082] Please refer to Figure 4. In some embodiments, step S302 may include, but is not limited to, steps S401 to S404:

[0083] Step S401: Set the original retry time interval according to the retry configuration information to obtain the selected retry time interval;

[0084] Step S402: Set the original number of retries according to the retry configuration information to obtain the selected number of retries;

[0085] Step S403: Set the original single retry duration according to the retry configuration information to obtain the selected single retry duration;

[0086] Step S404: Construct the selected push retry rule configuration item based on the selected retry time interval, selected number of retries, and selected single retry duration.

[0087] In step S401 of some embodiments, the retry configuration information includes retry time interval configuration information, retry count configuration information, and retry duration configuration information. The original retry time interval is configured according to the retry time interval configuration information to set a selected retry time interval corresponding to the retry time interval configuration information. For example, the retry time interval for a standard push rule is 2 minutes. In personalized push rule configuration, the retry time interval for logistics trajectory information can be set according to requirements. The selected retry time interval can be the same or set as a stepped time interval based on the number of retries. It should be noted that a stepped time interval means that the retry time interval increases continuously with the number of retries. For example, the time interval for the first retry is 2 minutes, the time interval for the second retry is 5 minutes, the time interval for the third retry is 8 minutes, and so on, setting the selected retry time interval to achieve personalized setting of the retry time interval.

[0088] In step S402 of some embodiments, the original number of retries is configured according to the retry count configuration information to set a retries number that matches the retry count configuration information as the selected retries number. For example, the standard push rule has 2 retries, and the selected retries number can be set to 3 or 4, realizing personalized settings for the number of retries.

[0089] In step S403 of some embodiments, the original single retry duration is set according to the retry duration configuration information, that is, the retry duration corresponding to the retry duration configuration information is set as the selected single retry duration. For example, if the original single retry duration is 10 seconds, and it is necessary to modify the original single retry duration from 10 seconds to 15 seconds as the selected single retry duration, the custom setting of the single retry duration can be realized.

[0090] In step S404 of some embodiments, the custom selected retry time interval, selected number of retries, and selected single retry duration are concatenated to obtain a retry strategy, thereby realizing the custom setting of the retry strategy and making the retry operation more flexible after the failure of logistics trajectory information push.

[0091] In steps S401 to S404 of this embodiment, the selected push retry rule configuration item is obtained by custom setting the retry time interval, retry count, and single retry duration in the retry strategy, thereby realizing the custom setting of the retry strategy.

[0092] In some embodiments, candidate encryption configuration items include: candidate encryption rule configuration items and candidate encryption object configuration items; the candidate encryption rule configuration items represent the encryption method of logistics trajectory information, and the candidate encryption object configuration items represent which part of the logistics trajectory information needs to be encrypted.

[0093] Please refer to Figure 5. In some embodiments, step S103 may include, but is not limited to, steps S501 to S503:

[0094] Step S501: Select the encryption rule configuration item from the candidate encryption rule configuration items based on the encryption requirement information;

[0095] Step S502: Select the chosen encryption object configuration item from the candidate encryption object configuration items based on the encryption requirement information;

[0096] Step S503: Generate the selected encryption configuration item based on the selected encryption rule configuration item and the selected encryption object configuration item.

[0097] In step S501 of some embodiments, the encryption requirement information represents the encryption requirement for pushing logistics trajectory information, and the encryption requirement information includes: encryption method configuration information and encryption object configuration information. The selected encryption rule configuration item is selected from the candidate encryption rule configuration items according to the encryption method configuration information, so as to select an encryption method that meets the user's encryption requirements.

[0098] In step S502 of some embodiments, selected encryption object configuration items are selected from candidate encryption object configuration items based on encryption object configuration information, so as to select which contents in the logistics trajectory information need to be encrypted.

[0099] For example, if the encryption rule configuration item is selected as ciphertext encryption algorithm and the encryption object configuration item is selected as contact information and contact address, then the ciphertext encryption algorithm will be used to encrypt the contact information and contact address in the logistics trajectory information.

[0100] In step S503 of some embodiments, the selected encryption configuration item is obtained by combining the selected encryption rule configuration item and the selected encryption object configuration item.

[0101] In steps S501 to S503 of this embodiment, by setting the selected encryption rule configuration item and the selected encryption object configuration item, the encryption method and encryption object of the logistics trajectory information are personalized, so as to complete the encrypted push of the logistics trajectory information according to the user's needs.

[0102] In step S104 of some embodiments, the target push rule configuration item is used to set the push rules for logistics trajectory information, and the selected encryption configuration item is used to set the encryption settings for the logistics trajectory information push process. Therefore, the logistics trajectory processing logic, retry strategy, idempotent strategy, circuit breaker strategy and selected encryption configuration item in the target push rule configuration item are used to construct push rules to obtain the target push rule corresponding to the push rule configuration request.

[0103] Please refer to Figure 6. In some embodiments, after step S104, the logistics trajectory push method further includes, but is not limited to, steps S601 to S603:

[0104] Step S601: Select the push failure repair rule from the preset candidate push failure repair rules according to the configuration object category;

[0105] Step S602: Update the target push rule according to the selected push failure repair rule to obtain the updated push rule;

[0106] Step S603: Push the logistics trajectory information to the user terminal according to the update push rules.

[0107] In step S601 of some embodiments, the candidate push failure modification rule is also called the logistics re-push rule. This means that when the customer system on the user's end is unavailable, the push of logistics trajectory information will be paused; that is, the rule will be re-push after the logistics trajectory information has not been pushed. It should be noted that different user categories require different re-push rules. Therefore, a selected push failure rule is selected from the candidate push failure repair rules based on the configured object category to obtain a re-push rule that satisfies the user category. Specifically, each candidate push failure repair rule is set with an applicable object tag. A target object tag is selected from the applicable object tags based on the configured object category, and the candidate push failure repair rule corresponding to the target object tag is then used as the selected push failure repair rule.

[0108] For example, if the selected push failure repair rule is to store the suspended logistics trajectory information in the storage medium, and the client system on the user end is repaired, the logistics trajectory information can be re-pushed to the designated user end through the Kafka data supplement consumer group by resetting the offset without interfering with the normal business of the client system, thus realizing the logistics trajectory re-push.

[0109] In step S602 of some embodiments, the selected push failure rule is added to the target push rule to obtain a new push rule as the updated push rule. It should be noted that the updated push rule is a logistics push rule with added logistics supplementary push rules, as a more complete logistics push rule.

[0110] In step S603 of some embodiments, the logistics trajectory information is pushed to the user terminal by updating the logistics push rules, so as to achieve more accurate logistics trajectory information push. The push is personalized according to the user's needs, which can improve the applicability of logistics trajectory information push.

[0111] In steps S601 to S603 of this embodiment, a selected push failure repair rule that meets the user's re-push requirement is selected, and then the selected push failure repair rule is added to the target push rule to obtain an updated push rule. Logistics trajectory information is pushed according to the updated push rule, making the personalized settings of logistics trajectory information push more comprehensive.

[0112] Please refer to Figure 7. In some embodiments, after step S105, the logistics trajectory push method may also include, but is not limited to, steps S701 to S703:

[0113] Step S701: Obtain the successful push time information of logistics trajectory information;

[0114] Step S702: Based on the successful push time information and the preset time threshold, the logistics trajectory information is classified by time to obtain the time category;

[0115] Step S703: Store the logistics trajectory information into a preset storage database according to the time category.

[0116] In step S701 of some embodiments, the successful push time information is the time when the logistics trajectory information is successfully pushed to the user terminal. It should be noted that after the logistics trajectory information is pushed to the user terminal, feedback information is received from the user terminal, and the feedback information includes the logistics trajectory reception time, so as to determine the successful push time based on the logistics trajectory reception information.

[0117] In step S702 of some embodiments, a time threshold is preset to distinguish the time category of successfully pushed logistics trajectory information. It should be noted that the time category includes a long time category and a short time category. The long time category indicates that the time when the logistics trajectory information has been successfully pushed exceeds the preset time threshold, while the short time category indicates that the time when the logistics trajectory information has been successfully pushed does not exceed the preset time threshold, and it may still need to be pushed again.

[0118] In step S703 of some embodiments, the successfully pushed logistics trajectory information is stored in different storage databases according to time category, and the storage databases are set in the storage medium to realize the classified storage of logistics trajectory information. This makes it convenient to quickly retrieve the logistics trajectory information by selecting the corresponding storage database according to the time category of the logistics trajectory information when retrieving it later.

[0119] For example, the storage databases include ClickHouse and Hive. ClickHouse is a high-performance columnar database management system, while Hive is a data warehouse software project used for querying and managing big data stored in distributed storage systems (such as Hadoop). In this embodiment, long-term logistics trajectory information is stored in Hive, while short-term logistics trajectory information is stored in ClickHouse. It should be noted that ClickHouse offers fast query speeds, and its keys can be easily integrated into application systems, facilitating page-based query functionality. Hive can be used for operations and data reporting. Therefore, storing short-term logistics trajectory information in ClickHouse allows for quick retrieval, while storing long-term logistics trajectory information in Hive facilitates centralized use during subsequent data analysis.

[0120] In steps S701 to S703 of this embodiment, the logistics trajectory information is classified and stored in different storage databases according to the successful push time information, so as to realize the classified storage of logistics trajectory data.

[0121] In summary, please refer to Figure 8. This application embodiment will provide a detailed description of the modules involved in the logistics trajectory push method. It should be noted that the logistics trajectory push method in this embodiment is applied to the server side, and the server side is equipped with a logistics trajectory system, a push submodule, a storage medium, and a dedicated encryption machine. The server side communicates with the user side, and the user side generates and configures a platform and a client system.

[0122] Before configuring the logistics push rules, users send a registration request from the customer system to the logistics tracking system. The logistics tracking system then registers the user based on the registration request, obtains the registration information, and stores the registration information in the Redis cache in the storage medium.

[0123] After the logistics tracking system generates logistics tracking information, the user configures logistics push rules on the configuration platform to generate a logistics rule configuration request. The configuration platform sends the logistics rule configuration request to the push submodule. The push submodule parses the logistics rule configuration request to obtain push confirmation configuration information, retry configuration information, push security configuration information, and tracking processing configuration information. Based on the push confirmation configuration information, an idempotent policy is configured; based on the retry configuration information, a retry policy is configured; based on the push security configuration information, a circuit breaker policy is configured; and based on the tracking processing configuration information, the logistics tracking processing logic is configured to obtain the target push rule configuration item. Then, a dedicated encryption machine encrypts the information in the logistics tracking information based on the candidate encryption rule configuration item and the candidate encryption object configuration item to obtain the selected encryption configuration item. The dedicated encryption machine then sends the selected encryption configuration item to the push submodule. Finally, the push submodule constructs the target push rule from the selected encryption configuration item and the target push rule configuration item. Simultaneously, the push submodule adds a selected push failure repair rule to the target push rule to obtain an updated push rule. Finally, the push submodule pushes the logistics tracking information to the user's client system using the updated push rule.

[0124] Once the logistics tracking information is pushed out, it will be stored in the storage database of the storage medium.

[0125] Please refer to Figure 9. This application embodiment also provides a logistics trajectory push device, which can implement the above-described logistics trajectory push method. The device includes:

[0126] The request receiving module 901 is used to receive push rule configuration requests sent by the user terminal; wherein, the push rule configuration request includes: configuration object category, configuration requirement information and encryption requirement information;

[0127] The configuration module 902 is used to configure the preset candidate push rule configuration items according to the configuration object category and configuration requirement information to obtain the target push rule configuration item;

[0128] The filtering module 903 is used to filter the selected encryption configuration items from the preset candidate encryption configuration items based on the encryption requirement information;

[0129] The rule building module 904 is used to build push rules based on the target push rule configuration items and the selected encryption configuration items to obtain the target push rules;

[0130] The push module 905 is used to push pre-generated logistics trajectory information to the user terminal according to the target push rules.

[0131] The specific implementation method of the logistics trajectory push device is basically the same as the specific implementation method of the logistics trajectory push method described above, and will not be repeated here.

[0132] This application also provides a computer device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the above-described logistics trajectory push method. This computer device can be any smart terminal, including tablet computers, in-vehicle computers, etc.

[0133] Please refer to Figure 10, which illustrates the hardware structure of a computer device according to another embodiment. The computer device includes:

[0134] The processor 1001 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application.

[0135] The memory 1002 can be implemented as a read-only memory (ROM), static storage device, dynamic storage device, or random access memory (RAM). The memory 1002 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 1002 and is called and executed by the processor 1001 using the logistics trajectory push method of the embodiments of this application.

[0136] Input / output interface 1003 is used to implement information input and output;

[0137] The communication interface 1004 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).

[0138] Bus 1005 transmits information between various components of the device (e.g., processor 1001, memory 1002, input / output interface 1003, and communication interface 1004);

[0139] The processor 1001, memory 1002, input / output interface 1003 and communication interface 1004 are connected to each other within the device via bus 1005.

[0140] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described logistics trajectory push method.

[0141] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory may optionally include memory remotely located relative to the processor, and these remote memories can be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0142] The logistics trajectory push method, apparatus, computer device, and storage medium provided in this application embodiment receive a push rule configuration request from a user terminal. The push rule configuration request includes: configuration object category, configuration requirement information, and encryption requirement information. Based on the configuration object category and configuration requirement information, the method configures candidate push rule configuration items to obtain a target push rule configuration item, thereby achieving personalized configuration of push rules. Simultaneously, based on the encryption requirement information, the method selects a encryption configuration item from the candidate encryption configuration items, thereby achieving custom settings for logistics trajectory encryption rules. Finally, the method constructs a target push rule based on the target push rule configuration item and the selected encryption configuration item, and pushes logistics trajectory information to the user terminal according to the target push rule, thereby achieving personalized push of logistics trajectory information. This not only improves the user experience of using logistics applications but also enhances the flexibility of logistics trajectory information push.

[0143] The embodiments described in this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. As those skilled in the art will know, with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0144] Those skilled in the art will understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of this application, and may include more or fewer steps than shown, or combine certain steps, or different steps.

[0145] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0146] Those skilled in the art will understand that all or some of the steps in the methods disclosed above, as well as the functional modules / units in the systems and devices, can be implemented as software, firmware, hardware, or suitable combinations thereof.

[0147] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of the units described above is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0148] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0149] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0150] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes multiple instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing programs, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0151] The preferred embodiments of the present application have been described above with reference to the accompanying drawings, but this does not limit the scope of the claims of the present application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and substance of the embodiments of the present application shall be within the scope of the claims of the present application.

Claims

1. A method for pushing logistics tracking information, characterized in that, The method includes: Receive a push rule configuration request sent by the user client; wherein the push rule configuration request includes: configuration object category, configuration requirement information and encryption requirement information; Based on the configuration object category and the configuration requirement information, the preset candidate push rule configuration items are configured to obtain the target push rule configuration items; Selected encryption configuration items are selected from preset candidate encryption configuration items based on the encryption requirement information; The target push rule is constructed based on the target push rule configuration item and the selected encryption configuration item; According to the target push rules, the pre-generated logistics trajectory information is pushed to the user terminal.

2. The method according to claim 1, characterized in that, The step of configuring preset candidate push rule configuration items according to the configuration object category and the configuration requirement information to obtain target push rule configuration items includes: The selected push rule configuration item is obtained by filtering the candidate push rule configuration items according to the configuration object category; The selected push rule configuration item is configured according to the configuration requirement information to obtain the target push rule configuration item.

3. The method according to claim 2, characterized in that, The configuration requirement information includes: push confirmation configuration information, retry configuration information, push security configuration information, and trajectory processing configuration information; the selected push rule configuration items include: original push confirmation rule configuration items, original push retry rule configuration items, original push security rule configuration items, and original logistics trajectory processing rule configuration items. The original push confirmation rule configuration items are used to determine the rules for successful pushes; the original push retry rule configuration items are used to set the rules for retrying after a push failure; the original push security rule configuration items are used to set the security rules for the push process; and the original logistics trajectory processing rule configuration items are used to set the rules for processing logistics trajectories. The step of configuring the selected push rule configuration items according to the configuration requirement information to obtain the target push rule configuration items includes: Based on the push confirmation configuration information, the original push confirmation rule configuration item is configured to obtain the selected push confirmation rule configuration item; The original push retry rule configuration item is configured according to the retry configuration information to obtain the selected push retry rule configuration item. Based on the push security configuration information, the original push security rule configuration item is configured to obtain the selected push security rule configuration item; Based on the trajectory processing configuration information, the original logistics trajectory processing rule configuration item is configured to obtain the selected logistics trajectory processing rule configuration item; The target push rule configuration item is constructed based on the selected push confirmation rule configuration item, the selected push retry rule configuration item, the selected push security rule configuration item, and the selected logistics trajectory processing rule configuration item.

4. The method according to claim 3, characterized in that, The original push retry rule configuration items include: original retry time interval, original number of retries, and original single retry duration; the step of configuring the original push retry rule configuration items according to the retry configuration information to obtain the selected push retry rule configuration items includes: The original retry time interval is set according to the retry configuration information to obtain the selected retry time interval; The original number of retries is set according to the retry configuration information to obtain the selected number of retries; The original single retry duration is set according to the retry configuration information to obtain the selected single retry duration; The selected push retry rule configuration item is constructed based on the selected retry time interval, the selected number of retries, and the selected single retry duration.

5. The method according to any one of claims 1 to 4, characterized in that, The candidate encryption configuration items include: candidate encryption rule configuration items and candidate encryption object configuration items; the step of selecting the selected encryption configuration item from the preset candidate encryption configuration items based on the encryption requirement information includes: Select the encryption rule configuration item from the candidate encryption rule configuration items based on the encryption requirement information; Selected encryption object configuration items are selected from the candidate encryption object configuration items based on the encryption requirement information; The selected encryption configuration item is generated based on the selected encryption rule configuration item and the selected encryption object configuration item.

6. The method according to any one of claims 1 to 4, characterized in that, After constructing the push rule based on the target push rule configuration item and the selected encryption configuration item to obtain the target push rule, the method further includes: Select the push failure repair rule from the preset candidate push failure repair rules according to the configured object category; The target push rule is updated according to the selected push failure repair rule to obtain the updated push rule; The logistics trajectory information is pushed to the user terminal according to the update push rules.

7. The method according to any one of claims 1 to 4, characterized in that, After pushing the pre-generated logistics trajectory information to the user terminal according to the target push rule, the method further includes: Obtain the successful push time information of the logistics trajectory information; The logistics trajectory information is classified by time based on the successful push time information and a preset time threshold to obtain the time category. The logistics trajectory information is stored in a preset storage database according to the time category.

8. A logistics trajectory tracking device, characterized in that, The device includes: The request receiving module is used to receive push rule configuration requests sent by the user terminal; wherein, the push rule configuration request includes: configuration object category, configuration requirement information and encryption requirement information; The configuration module is used to configure the preset candidate push rule configuration items according to the configuration object category and the configuration requirement information to obtain the target push rule configuration item; The filtering module is used to filter out the selected encryption configuration items from the preset candidate encryption configuration items based on the encryption requirement information; The rule building module is used to build push rules based on the target push rule configuration items and the selected encryption configuration items to obtain the target push rules; The push module is used to push pre-generated logistics trajectory information to the user terminal according to the target push rules.

9. A computer device, characterized in that, The computer device includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the logistics trajectory push method according to any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the logistics trajectory push method according to any one of claims 1 to 7.

Images