Forest-based scrm lead pushing method and device, vehicle and storage medium

Abstract

The application relates to a Forest-based SCRM (Sales and Customer Relationship Management) lead pushing method and device, a vehicle and a storage medium, wherein the method comprises the following steps: generating system leads corresponding to each target vehicle-mounted application system in at least one target vehicle-mounted application system through the at least one target vehicle-mounted application system; acquiring interface input parameters and a unified interface of each target vehicle-mounted application system, and receiving each system lead according to the interface input parameters and the unified interface; and pushing the system lead into an SCRM platform based on a preset Forest. The application makes the lead pushing componentized through the Forest, improves the lead pushing development efficiency, can improve a log and a compensation mechanism, reduces the difficulty of troubleshooting and repairing online problems, and improves the expansibility and availability of the system.

Description

Technical Field

[0001] This application relates to the field of information processing technology, and in particular to a Forest-based SCRM lead push method, device, vehicle, and storage medium. Background Technology

[0002] Currently, information about users registering, placing orders, and participating in activities on the app is pushed to SCRM (Social Customer Relationship Management).

[0003] Existing technologies for data push first involve a message push proxy receiving push message requests from a server. Second, if the push message request is determined to be dynamic, it is parsed to identify at least one push condition. Based on these conditions, terminal data corresponding to each condition is retrieved from the terminal. Third, based on the terminal data and at least one push condition, the target push content for each tag is determined. Finally, a target push message is generated based on the target push content for each tag and sent to the message center. Because the push messages sent from the server to the terminals include dynamically adjustable content, each terminal, upon receiving the push information, can perform logical judgments based on the received push message request and determine push content tailored to its current situation, thereby improving user experience.

[0004] However, in existing technologies, the clue push code is distributed across various systems, making it difficult to expand and with poor usability. Furthermore, the lack of standardized logging and compensation mechanisms in existing technologies makes troubleshooting and repair quite difficult, which urgently needs to be addressed. Summary of the Invention

[0005] This application provides a Forest-based SCRM lead push method, device, vehicle, and storage medium to solve the problems in the prior art where lead push code is distributed across various systems, making it difficult to expand and with poor usability. Furthermore, the lack of standardized logging and compensation mechanisms in the prior art makes troubleshooting and repair difficult.

[0006] The first aspect of this application provides a Forest-based SCRM lead push method, comprising the following steps: generating system leads corresponding to each of the at least one target vehicle application systems through at least one target vehicle application system; obtaining the interface input parameters and unified interface of each target vehicle application system, and receiving each system lead according to the interface input parameters and unified interface; and pushing the system leads to the SCRM platform based on a preset Forest.

[0007] Optionally, in one embodiment of this application, after pushing the system clue to the SCRM platform, the method further includes: obtaining the status code of the SCRM platform to determine the push status of the system clue based on the status code; and, if the push status is a push failure status, performing a compensation push operation on the system clue whose push status is a push failure status based on a preset compensation mechanism and a preset compensation period.

[0008] Optionally, in one embodiment of this application, the compensation push operation for system clues in the push failure state based on a preset compensation mechanism and a preset compensation period includes: querying the push type and business ID corresponding to the system clue in the push failure state, obtaining complete push data according to the push type and the business ID, and re-pushing the complete push data to the SCRM platform.

[0009] Optionally, in one embodiment of this application, obtaining the interface input parameters and unified interface of each target vehicle application system, and receiving each system clue according to the interface input parameters and unified interface, includes: generating interface input parameters of the system clue corresponding to each target vehicle application system through each target vehicle application system; asynchronously calling the unified interface using each target vehicle application system, and sending a clue push request to a preset clue synchronization push system according to the interface input parameters and the unified interface; receiving the clue push request based on the clue synchronization push system, and storing the push type, business ID, and push status of the system clue corresponding to the clue push request in the target database according to the clue push request.

[0010] Optionally, in one embodiment of this application, the step of pushing the system clues to the SCRM platform based on a preset Forest includes: determining a token acquisition strategy corresponding to each system clue according to the push type of each system clue based on the beforeExecute method in the interceptor interface of the preset Forest, so as to control each system clue to call the corresponding token acquisition strategy to obtain the token corresponding to each system clue; constructing a retry mechanism and a unified log based on the onRetry method and afterExecute method in the interceptor interface of the preset Forest, respectively; and pushing the system clues to the SCRM platform according to the token, the retry mechanism and the unified log.

[0011] A second aspect of this application provides a Forest-based SCRM lead push device, comprising: a generation module, configured to generate system leads corresponding to each of the at least one target vehicle application systems through at least one target vehicle application system; a receiving module, configured to acquire interface input parameters and a unified interface of each target vehicle application system, and receive each system lead according to the interface input parameters and the unified interface; and a push module, configured to push the system leads to an SCRM platform based on a preset Forest.

[0012] Optionally, in one embodiment of this application, it further includes: a determining module, configured to obtain the status code of the SCRM platform after pushing the system clue to the SCRM platform, so as to determine the push status of the system clue according to the status code; and a compensation module, configured to perform a compensation push operation on the system clue whose push status is a push failure state based on a preset compensation mechanism and a preset compensation period when the push status is a push failure state.

[0013] Optionally, in one embodiment of this application, the compensation module includes: a query unit, used to query the push type and business ID corresponding to the system clue of the push failure status, so as to obtain complete push data according to the push type and the business ID, and re-push the complete push data to the SCRM platform.

[0014] Optionally, in one embodiment of this application, the receiving module includes: an input parameter unit, configured to generate interface input parameters for system clues corresponding to each target vehicle application system through each target vehicle application system; a calling unit, configured to asynchronously call the unified interface using each target vehicle application system, and send a clue push request to a preset clue synchronization push system according to the interface input parameters and the unified interface; and a storage unit, configured to receive the clue push request based on the clue synchronization push system, and store the push type, business ID, and push status of the system clue corresponding to the clue push request in the target database according to the clue push request.

[0015] Optionally, in one embodiment of this application, the push module includes: a control unit, configured to determine a token acquisition strategy corresponding to each system clue based on the beforeExecute method in the interceptor interface of the preset Forest, according to the push type of each system clue, so as to control each system clue to call the corresponding token acquisition strategy to acquire the token corresponding to each system clue; a construction unit, configured to construct a retry mechanism and a unified log based on the onRetry method and the afterExecute method in the interceptor interface of the preset Forest, respectively; and a sending unit, configured to push the system clue to the SCRM platform according to the token, the retry mechanism and the unified log.

[0016] A third aspect of this application provides a vehicle, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the Forest-based SCRM lead push method as described in the above embodiments.

[0017] A fourth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described Forest-based SCRM lead push method.

[0018] Therefore, the embodiments of this application have the following beneficial effects:

[0019] Embodiments of this application can generate system clues corresponding to each of the at least one target vehicle application systems through at least one target vehicle application system; obtain the interface input parameters and unified interface of each target vehicle application system, and receive each system clue according to the interface input parameters and unified interface; and push the system clues to the SCRM platform based on a preset Forest. This application uses Forest to componentize the clue push, improving the development efficiency of clue push, and can improve the logging and compensation mechanism, reducing the difficulty of troubleshooting and fixing online problems, while improving the scalability and availability of the system. Thus, it solves the problems in the prior art where the clue push code is distributed across various systems, making it difficult to expand and with poor availability, and where the lack of standardized logging and compensation mechanisms in the prior art makes troubleshooting and fixing difficult.

[0020] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0021] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:

[0022] Figure 1 This is a flowchart illustrating a Forest-based SCRM lead push method according to an embodiment of this application.

[0023] Figure 2 This is a schematic diagram illustrating the execution logic of a Forest-based SCRM lead push method according to an embodiment of this application.

[0024] Figure 3 This is an example diagram of a Forest-based SCRM lead push device according to an embodiment of this application;

[0025] Figure 4 This is a schematic diagram of the vehicle structure provided in an embodiment of this application.

[0026] Among them, 10-Forest-based SCRM lead push device; 100-Generation module, 200-Receiving module, 300-Push module; 401-Memory, 402-Processor, 403-Communication interface. Detailed Implementation

[0027] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0028] The following describes an embodiment of the SCRM lead push method, apparatus, vehicle, and storage medium based on Forest, with reference to the accompanying drawings. Addressing the problems mentioned in the background section, this application provides a Forest-based SCRM lead push method. In this method, system leads corresponding to each target vehicle application system are generated through at least one target vehicle application system; interface input parameters and a unified interface for each target vehicle application system are obtained, and each system lead is received according to the interface input parameters and the unified interface; based on a preset Forest, the system leads are pushed to the SCRM platform. This application modularizes lead push through Forest, improving lead push development efficiency and enhancing logging and compensation mechanisms, reducing the difficulty of troubleshooting and fixing online issues, while also improving system scalability and availability. Therefore, it solves the problems in the prior art where lead push code is distributed across various systems, making it difficult to expand and resulting in poor availability, and the lack of standardized logging and compensation mechanisms in the prior art makes troubleshooting and repair difficult.

[0029] Specifically, Figure 1 A flowchart illustrating a Forest-based SCRM lead push method provided in this application embodiment.

[0030] like Figure 1 As shown, this Forest-based SCRM lead push method includes the following steps:

[0031] In step S101, system clues corresponding to each target vehicle application system are generated through at least one target vehicle application system.

[0032] The embodiments of this application first allow users on the App side to perform some operations using the target in-vehicle application system, generating system clues corresponding to each target in-vehicle application system.

[0033] For example, after a user registers in the registration system, registration leads can be generated; order leads can be generated through the ordering function of the marketing system; and activity leads can be generated through the activity function of the marketing system.

[0034] Therefore, the embodiments of this application generate corresponding system clues after users register, place orders, and participate in activities on the App, thereby providing guidance and basis for the execution of subsequent push operations.

[0035] In step S102, the interface input parameters and unified interface of each target vehicle application system are obtained, and each system clue is received according to the interface input parameters and unified interface.

[0036] After obtaining the system clues corresponding to each target vehicle application system, the embodiments of this application can further obtain the interface input parameters and unified interface of each target vehicle application system, thereby ensuring that the generated system clues can be effectively received.

[0037] Optionally, in one embodiment of this application, obtaining the interface input parameters and unified interface of each target vehicle application system, and receiving each system clue according to the interface input parameters and unified interface, includes: generating interface input parameters of the system clue corresponding to each target vehicle application system through each target vehicle application system; asynchronously calling the unified interface using each target vehicle application system, and sending a clue push request to a preset clue synchronous push system according to the interface input parameters and unified interface; receiving the clue push request based on the clue synchronous push system, and storing the push type, business ID and push status of the system clue corresponding to the clue push request in the target database according to the clue push request.

[0038] In practical implementation, embodiments of this application allow leads generated by different systems to pass through a unified template construction interface provided by the lead system, and different systems to asynchronously call the unified interface of the lead synchronization system. Furthermore, after receiving an asynchronous request, the lead synchronization system can save push records such as type, business ID, and push status (initialization) to a push record table in a relational database, such as... Figure 2 As shown.

[0039] Therefore, the embodiments of this application establish a general clue push template and a RESTful format-based interface, construct templated input parameters and a unified interface, making the clue push interface easy to extend and use in multiple different systems, thereby effectively reducing development costs, improving program scalability, and asynchronously improving system performance; in addition, the embodiments of this application collect clue information from different services, and improve the availability of clue synchronization through asynchronous interfaces and the introduction of multi-threading.

[0040] In step S103, based on the preset Forest, system leads are pushed to the SCRM platform.

[0041] Furthermore, embodiments of this application can also utilize Forest to push system leads to the SCRM (Social Customer Relationship Management) platform, thereby enabling lead synchronization components through Forest, improving the development efficiency and reliability of lead push, and enhancing the scalability and maintainability of the code.

[0042] Optionally, in one embodiment of this application, pushing system leads to the SCRM platform based on a preset Forest includes: determining a token acquisition strategy for each system lead based on the push type of each system lead using the beforeExecute method in the interceptor interface of the preset Forest, so as to control each system lead to call the corresponding token acquisition strategy to obtain the token corresponding to each system lead; constructing a retry mechanism and a unified log based on the onRetry method and afterExecute method in the interceptor interface of the preset Forest, respectively; and pushing the system leads to the SCRM platform based on the token, the retry mechanism, and the unified log.

[0043] It should be noted that embodiments of this application may utilize the Interceptor provided in Forest. <object>The `beforeExecute` method in the interface obtains a token before pushing a lead. Different leads call different methods to obtain tokens based on their type, thereby obtaining tokens through the strategy pattern, which improves the extensibility and maintainability of the code. For pushing new leads, only one new strategy needs to be added.

[0044] Secondly, embodiments of this application can also utilize the Interceptor provided in Forest. <object>The onRetry method in the interface implements a retry mechanism to call the interface again; if the token expires, the token is refreshed and the interface is called again, so as to improve the reliability of clue push through the retry mechanism.

[0045] Furthermore, embodiments of this application can also utilize the Interceptor provided in Forest. <object>The afterExecute method in the interface records the http request call log in the non-relational database, including the status code, request parameter and request result, etc., so as to effectively reduce the difficulty of problem checking through the unified log recording method and log management.

[0046] Optionally, in an embodiment of the present application, after the system clue is pushed into the SCRM platform, the method further includes: obtaining a status code of the SCRM platform to determine a push state of the system clue according to the status code; and performing a compensation push operation on the system clue in the push state of the push failure state based on a preset compensation mechanism and a preset compensation period.

[0047] After the system clue is pushed, further, the embodiment of the present application can return a status code according to the SCRM interface, which records the push record state as a success or failure state.

[0048] Further, the embodiment of the present application can increase a compensation mechanism for the push failure due to network reasons, for example, a time can be set every day, and the compensation mechanism can perform compensation push on the push failure data in the last 24 hours.

[0049] Therefore, the embodiment of the present application effectively reduces the difficulty of problem checking and repairing online problems through the perfect log and compensation mechanism in the clue system, and guarantees the reliability and availability of the push.

[0050] Optionally, in an embodiment of the present application, the compensation push operation on the system clue in the push state of the push failure state based on the preset compensation mechanism and the preset compensation period includes: querying the push type and the business ID corresponding to the system clue in the push state of the push failure state to obtain complete push data according to the push type and the business ID, and re-pushing the complete push data to the SCRM platform.

[0051] In addition, in the embodiment of the present application, the compensation push can provide an abstract class through the strategy mode, add a clue to obtain the push type and the business ID to obtain complete push data, so as to call different systems to perfect the push data, specifically, query the database of each system and call the related party service to obtain complete assembled data, and then re-push in the clue push system, so as to improve the reliability of the clue push.

[0052] According to the Forest-based SCRM lead pushing method provided in the embodiment of the present application, at least one target vehicle-mounted application system is used to generate a system lead corresponding to each target vehicle-mounted application system in the at least one target vehicle-mounted application system; an interface input parameter and a unified interface of each target vehicle-mounted application system are obtained, and each system lead is received according to the interface input parameter and the unified interface; and the system lead is pushed into an SCRM platform based on a preset Forest. The Forest makes the lead pushing componentized, improves the lead pushing development efficiency, and can improve the log and compensation mechanism, reduce the difficulty of troubleshooting and repairing online problems, and improve the expansibility and usability of the system.

[0053] Secondly, the Forest-based SCRM lead pushing device provided in the embodiment of the present application is described with reference to the accompanying drawings.

[0054] Figure 3 is a block schematic diagram of the Forest-based SCRM lead pushing device in the embodiment of the present application.

[0055] As shown in Figure 3 , the Forest-based SCRM lead pushing device 10 comprises a generation module 100, a receiving module 200 and a pushing module 300.

[0056] The generation module 100 is configured to generate a system lead corresponding to each target vehicle-mounted application system in at least one target vehicle-mounted application system through the at least one target vehicle-mounted application system.

[0057] The receiving module 200 is configured to obtain an interface input parameter and a unified interface of each target vehicle-mounted application system, and receive each system lead according to the interface input parameter and the unified interface.

[0058] The pushing module 300 is configured to push the system lead into an SCRM platform based on a preset Forest.

[0059] Optionally, in an embodiment of the present application, the Forest-based SCRM lead pushing device 10 provided in the embodiment of the present application further comprises a determination module and a compensation module.

[0060] The determination module is configured to obtain a state code of the SCRM platform after the system lead is pushed into the SCRM platform, so as to determine a pushing state of the system lead according to the state code.

[0061] The compensation module is configured to perform a compensation pushing operation on the system lead in the pushing state of the pushing failure state based on a preset compensation mechanism and a preset compensation period in the case that the pushing state is the pushing failure state.

[0062] Optionally, in one embodiment of this application, the compensation module includes: a query unit, used to query the push type and business ID corresponding to the system clue in the push failure state, so as to obtain complete push data according to the push type and business ID, and re-push the complete push data to the SCRM platform.

[0063] Optionally, in one embodiment of this application, the receiving module 200 includes: an input parameter unit, a calling unit, and a storage unit.

[0064] The input parameter unit is used to generate the interface input parameters for the system clues corresponding to each target vehicle application system through each target vehicle application system.

[0065] The calling unit is used to asynchronously call the unified interface for each target vehicle application system, and send the clue push request to the preset clue synchronization push system according to the interface input parameters and the unified interface.

[0066] The storage unit is used to receive clue push requests based on the clue synchronous push system, and store the push type, business ID and push status of the system clue corresponding to the clue push request in the target database according to the clue push request.

[0067] Optionally, in one embodiment of this application, the push module 300 includes: a control unit, a construction unit, and a sending unit.

[0068] The control unit is used to determine the token acquisition strategy corresponding to each system clue based on the push type of each system clue according to the beforeExecute method in the interceptor interface of the preset Forest, so as to control each system clue to call the corresponding token acquisition strategy to obtain the token corresponding to each system clue.

[0069] The building unit is used to construct a retry mechanism and a unified log based on the onRetry and afterExecute methods in the interceptor interface of the pre-defined Forest.

[0070] The sending unit is used to push system clues to the SCRM platform based on the token, retry mechanism, and unified log.

[0071] It should be noted that the foregoing explanation of the Forest-based SCRM lead push method embodiment also applies to the Forest-based SCRM lead push device of this embodiment, and will not be repeated here.

[0072] The SCRM lead push device based on Forest proposed in this application includes a generation module for generating system leads corresponding to each of the at least one target vehicle application system; a receiving module for acquiring the interface input parameters and unified interface of each target vehicle application system, and receiving each system lead according to the interface input parameters and unified interface; and a push module for pushing the system leads to the SCRM platform based on a preset Forest. This application modularizes lead push through Forest, improving lead push development efficiency, enhancing logging and compensation mechanisms, reducing the difficulty of troubleshooting and fixing online issues, and simultaneously improving system scalability and availability.

[0073] Figure 4 A schematic diagram of the structure of a vehicle provided in an embodiment of this application. The vehicle may include:

[0074] The memory 401, the processor 402, and the computer program stored on the memory 401 and capable of running on the processor 402.

[0075] When the processor 402 executes the program, it implements the Forest-based SCRM lead push method provided in the above embodiments.

[0076] Furthermore, the vehicle also includes:

[0077] Communication interface 403 is used for communication between memory 401 and processor 402.

[0078] The memory 401 is used to store computer programs that can run on the processor 402.

[0079] The memory 401 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0080] If the memory 401, processor 402, and communication interface 403 are implemented independently, then the communication interface 403, memory 401, and processor 402 can be interconnected via a bus to complete communication between them. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be divided into address buses, data buses, control buses, etc. For ease of representation, Figure 4 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0081] Optionally, in a specific implementation, if the memory 401, processor 402, and communication interface 403 are integrated on a single chip, then the memory 401, processor 402, and communication interface 403 can communicate with each other through an internal interface.

[0082] Processor 402 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.

[0083] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described Forest-based SCRM lead push method.

[0084] In the description of this specification, the references to "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0085] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0086] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or N executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0087] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0088] It should be understood that the various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. If implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0089] Those skilled in the art will understand that all or part of the steps of the methods described in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it includes one or a combination of the steps of the method embodiments.

[0090] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0091] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of this application.< / object> < / object> < / object>

Claims

1. A Forest-based SCRM lead push method, characterized in that, Includes the following steps: Generate system clues corresponding to each target vehicle application system within the at least one target vehicle application system; Obtain the interface input parameters and unified interface of each target vehicle application system, and receive each system clue according to the interface input parameters and unified interface; Based on the preset Forest, the system leads are pushed to the SCRM platform; The step of obtaining the interface input parameters and unified interface of each target vehicle application system, and receiving each system clue according to the interface input parameters and unified interface, includes: The interface input parameters for generating system clues corresponding to each target vehicle application system are obtained through each target vehicle application system. The unified interface is called asynchronously using each target vehicle application system, and a clue push request is sent to the preset clue synchronization push system according to the interface input parameters and the unified interface. Based on the aforementioned clue synchronization push system, the system receives the clue push request and stores the push type, business ID, and push status of the system clue corresponding to the clue push request in the target database according to the clue push request. The process of pushing system leads to the SCRM platform based on a preset Forest includes: Based on the beforeExecute method in the interceptor interface of the preset Forest, the token acquisition strategy corresponding to each system clue is determined according to the push type of each system clue, so as to control each system clue to call the corresponding token acquisition strategy to obtain the token corresponding to each system clue; Based on the onRetry and afterExecute methods in the interceptor interface of the preset Forest, a retry mechanism and a unified log are constructed respectively. The system clues are pushed to the SCRM platform based on the token, the retry mechanism, and the unified log.

2. The method according to claim 1, characterized in that, After pushing the system leads to the SCRM platform, the process also includes: Obtain the status code of the SCRM platform to determine the push status of the system clues based on the status code; When the push status is in the push failure state, a compensation push operation is performed on the system clues in the push failure state based on a preset compensation mechanism and a preset compensation period.

3. The method according to claim 2, characterized in that, The compensation push operation for system clues in the push failure state based on a preset compensation mechanism and a preset compensation period includes: Query the system clues corresponding to the failed push status and their corresponding push type and business ID, obtain complete push data based on the push type and business ID, and then re-push the complete push data to the SCRM platform.

4. A Forest-based SCRM lead push device, characterized in that, include: A generation module is used to generate system clues corresponding to each target vehicle application system in the at least one target vehicle application system. The receiving module is used to acquire the interface input parameters and unified interface of each target vehicle application system, and to receive each system clue according to the interface input parameters and unified interface. The push module is used to push the system leads to the SCRM platform based on the preset Forest. The step of obtaining the interface input parameters and unified interface of each target vehicle application system, and receiving each system clue according to the interface input parameters and unified interface, includes: The interface input parameters for generating system clues corresponding to each target vehicle application system are obtained through each target vehicle application system. The unified interface is called asynchronously using each target vehicle application system, and a clue push request is sent to the preset clue synchronization push system according to the interface input parameters and the unified interface. Based on the aforementioned clue synchronization push system, the system receives the clue push request and stores the push type, business ID, and push status of the system clue corresponding to the clue push request in the target database according to the clue push request. The process of pushing system leads to the SCRM platform based on a preset Forest includes: Based on the beforeExecute method in the interceptor interface of the preset Forest, the token acquisition strategy corresponding to each system clue is determined according to the push type of each system clue, so as to control each system clue to call the corresponding token acquisition strategy to obtain the token corresponding to each system clue; Based on the onRetry and afterExecute methods in the interceptor interface of the preset Forest, a retry mechanism and a unified log are constructed respectively. The system clues are pushed to the SCRM platform based on the token, the retry mechanism, and the unified log.

5. The apparatus according to claim 4, characterized in that, Also includes: The determination module is used to obtain the status code of the SCRM platform after the system clue is pushed to the SCRM platform, so as to determine the push status of the system clue based on the status code; The compensation module is used to perform compensation push operations on system clues in the push failure state based on a preset compensation mechanism and a preset compensation period when the push status is in the push failure state.

6. The apparatus according to claim 5, characterized in that, The compensation module includes: The query unit is used to query the push type and business ID corresponding to the system clues in the push failure state, so as to obtain complete push data according to the push type and the business ID, and re-push the complete push data to the SCRM platform.

7. A vehicle, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, the processor executing the program to implement the Forest-based SCRM lead push method as described in any one of claims 1-3.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, The program is executed by the processor to implement the Forest-based SCRM lead push method as described in any one of claims 1-3.

Images