A method, device and electronic device for collecting customer application links

Abstract

The present invention provides a method, device, electronic device and computer-readable storage medium for collecting customer application links, wherein the method includes a server receiving customer information of both the initiating customer and the receiving customer; the server verifying the customer information of both parties; and generating an encrypted string as a collection receipt code for both customers through a symmetric encryption algorithm based on the customer roles and collection application identification codes of both customers. Through the method, device, electronic device and computer-readable storage medium provided by the embodiments of the present invention, after a customer submits a collection application, a collection application identification code is assigned to its email, link, page and other modules, and the customer's tag tracking is achieved through the collection application identification code, and the real-time unique customer identity judgment is achieved; the materials and data of the customer's collection application are associated with the customer itself through the collection application identification code, realizing the data attribution function and completing the subsequent business process.

Description

Technical Field

[0001] The present invention relates to the field of e-commerce technology, and in particular to a method, device, electronic device, and computer-readable storage medium for collecting customer application links. Background Art

[0002] The e-commerce advertising delivery system (e-commerce advertising SaaS system) is a B2B system used to help cross-border e-commerce users promote e-commerce products on overseas advertising media platforms (such as Facebook, Google, Tiktok, etc.).

[0003] When clients of an e-commerce advertising system apply for account merging, they need to receive emails and receive proof of ownership. Because this presents challenges in identifying both clients and potentially misusing or misusing links, the inventors propose a method for matching client account merging application links to ensure the accuracy of the information submitted by both clients. Summary of the Invention

[0004] To solve existing technical problems, embodiments of the present invention provide a method, device, electronic device, and computer-readable storage medium for aggregating customer application links.

[0005] In a first aspect, an embodiment of the present invention provides a method for aggregating customer application links, comprising:

[0006] Upon receiving the collection application from the initiating customer at the collection application portal of the system, the server receives the customer information of both the initiating customer and the receiving customer;

[0007] The server verifies the company name, business license, and email address of both parties' customer information. If the verification is successful, it generates a collection application identification code for the collection application.

[0008] Generate an encrypted string as the collection receipt code for both customers through a symmetric encryption algorithm based on the customer roles and collection application identification codes of both customers;

[0009] The collection receipt code is combined with the page address of the corresponding returned material to generate the material receipt address of both customers;

[0010] Send the materials to the initiating customer and the receiving customer by email according to the material receipt addresses of both customers;

[0011] Call the corresponding server interface according to the collection receipt code of both customers in the material receipt address;

[0012] The server decrypts the collection receipt code to obtain the customer roles and collection application identification codes of both customers, and obtains the collection application record based on the collection application identification code;

[0013] After both parties confirm that the information on the receipt page in the collection application record is correct, they upload the collection certification materials to the server for storage based on the customer roles and collection application identification codes of both parties.

[0014] In a second aspect, an embodiment of the present invention provides a device for aggregating customer application links, including:

[0015] The server is configured to receive a collection application initiated by an initiating customer at the collection application portal of the system, receive customer information of both the initiating customer and the receiving customer; verify the company name, business license, and email address in the customer information of both parties, and generate a collection application identification code for the collection application after passing the verification; decrypt the collection receipt code to obtain the customer roles and collection application identification codes of both customers, and query the collection application record based on the collection application identification code;

[0016] An encryption generation module is used to generate an encrypted string as a collection receipt code for both customers through a symmetric encryption algorithm based on the customer roles and collection application identification codes of both customers;

[0017] An address splicing module is used to splice the collection receipt code with the page address of the corresponding return material to generate the material receipt address of both customers;

[0018] The receipt sending module is used to send the receipt to the initiating customer and the receiving customer via email according to the material receipt addresses of both customers;

[0019] A port calling module is used to call the corresponding server interface according to the collection receipt codes of both customers in the material receipt address;

[0020] The material uploading module is used to upload the collection certification materials to the server for storage according to the customer roles and collection application identification codes of both customers after both customers confirm that the receipt page information in the collection application record is correct.

[0021] In a third aspect, an embodiment of the present invention provides an electronic device comprising a bus, a transceiver, a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the transceiver, the memory, and the processor are connected via the bus, and when the computer program is executed by the processor, the steps in the method for aggregating customer application links as described above are implemented.

[0022] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps in the method for aggregating customer application links as described above.

[0023] The method, apparatus, electronic device, and computer-readable storage medium provided by the embodiments of the present invention assign a collection application identification code to modules such as emails, links, and pages after a customer submits a collection application. The collection application identification code enables tag tracking of the customer and enables real-time unique customer identity determination. The materials and data of the customer's collection application are associated with the customer itself through the collection application identification code, thereby realizing the data attribution function and completing subsequent business processes. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the background technology, the drawings required for use in the embodiments of the present invention or the background technology will be described below.

[0025] Figure 1 A flowchart of a method for aggregating customer application links provided by an embodiment of the present invention is shown;

[0026] Figure 2 Shown Figure 1 Flowchart of the specific method of step S105 of the embodiment;

[0027] Figure 3 Shown Figure 1 Flowchart of the specific method of step S107 of the embodiment;

[0028] Figure 4 A schematic diagram showing the structure of a device for aggregating customer application links provided by an embodiment of the present invention is shown;

[0029] Figure 5 A schematic diagram of the structure of an electronic device for aggregating customer application links provided by an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0030] Those skilled in the art will appreciate that embodiments of the present invention may be implemented as methods, apparatuses, electronic devices, and computer-readable storage media. Therefore, embodiments of the present invention may be implemented in the following forms: entirely in hardware, entirely in software (including firmware, resident software, microcode, etc.), or in a combination of hardware and software. Furthermore, in some embodiments, embodiments of the present invention may also be implemented in the form of a computer program product in one or more computer-readable storage media, wherein the computer-readable storage media contains computer program code.

[0031] The above-mentioned computer-readable storage medium may adopt any combination of one or more computer-readable storage media. Computer-readable storage media include: electrical, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or components, or any combination thereof. More specific examples of computer-readable storage media include: portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM), flash memories (Flash Memory), optical fibers, compact disc read-only memories (CD-ROMs), optical storage devices, magnetic storage devices or any combination thereof. In an embodiment of the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device, or component.

[0032] The computer program code contained in the computer-readable storage medium may be transmitted using any appropriate medium, including wireless, wire, optical cable, radio frequency (RF), or any suitable combination thereof.

[0033] The computer program code for performing the operations of the embodiments of the present invention can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as C or similar programming languages. The computer program code can be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, and entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer or to an external computer via any type of network, including a local area network (LAN) or a wide area network (WAN).

[0034] The following describes embodiments of the present invention with reference to flowcharts and / or block diagrams of methods, apparatuses, electronic devices, and computer-readable storage media according to embodiments of the present invention.

[0035] It should be understood that each block in the flowchart and / or block diagram, as well as combinations of blocks in the flowchart and / or block diagram, can be implemented by computer-readable program instructions. These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine. These computer-readable program instructions are executed by the computer or other programmable data processing device to produce a device that implements the functions / operations specified in the blocks in the flowchart and / or block diagram.

[0036] These computer-readable program instructions may also be stored in a computer-readable storage medium that enables a computer or other programmable data processing device to operate in a specific manner. In this way, the instructions stored in the computer-readable storage medium produce an instruction device product that implements the functions / operations specified in the blocks in the flowchart and / or block diagram.

[0037] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device, so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby enabling the instructions executed on the computer or other programmable data processing apparatus to provide a process that implements the functions / operations specified by the blocks in the flowchart and / or block diagram.

[0038] The embodiments of the present invention are described below with reference to the accompanying drawings.

[0039] Symmetric encryption is a type of encryption algorithm in cryptography that uses the same key for encryption and decryption, or uses two keys that can be easily deduced from each other. This key becomes a shared secret between two or more parties, allowing them to maintain a private communication link.

[0040] Symmetric encryption is characterized by low computational complexity and high encryption speed. Symmetric encryption typically involves the decryptor generating an encryption key and transmitting it to the encryptor. The encryptor then uses the encryption key to encrypt the plaintext, then sends the ciphertext to the decryptor. The decryptor then uses the encryption key to decrypt the ciphertext and obtain the plaintext. However, the key can be intercepted by attackers during transmission, so the security of symmetric encryption depends not only on the strength of the encryption algorithm itself but also on the secure transmission of the key.

[0041] Common symmetric encryption algorithms include AES, ChaCha20, 3DES, Salsa20, DES, Blowfish, IDEA, RC5, RC6, and Camellia. The Advanced Encryption Standard (AES) employed in the embodiments of the present invention is a symmetric encryption algorithm that replaces DES and 3DES and is a popular symmetric encryption algorithm. The AES data block length is uniformly 128 bits, while the key space can be configured with three different lengths: 128 bits, 192 bits, and 256 bits. Unlike most block encryption algorithms, the AES round function does not utilize a Feistel structure, but instead uses three different reversible uniform transformations.

[0042] Figure 1 FIG. 1 is a flow chart showing a method for collecting customer application links provided by an embodiment of the present invention. Figure 1 As shown, the method includes:

[0043] Step S101: Receive a collection application from a customer at the collection application portal of the system, and submit the initiating customer information (such as customer ID, nickname, company name, business license, email address, initiating customer role, etc.) and the receiving customer information (such as customer ID, nickname, company name, business license, email address, receiving customer role, etc.) to the system server;

[0044] Step S103: After receiving the aggregation application initiated by the client, the system server verifies the company name, business license, email address, and roles of both parties in the initiating and receiving client information. If the verification is successful, a unique aggregation application identification code is generated for the aggregation application, and an application expiration date is generated based on the application time. This information is then stored in the database as an aggregation application record.

[0045] Step S105: After the collection application record is successfully saved, an encrypted string is generated as the collection receipt code of the initiating customer through a symmetric encryption algorithm according to the initiating customer role and the collection application identification code;

[0046] like Figure 2 Specifically, step S105 includes:

[0047] Step S1051: Generate an initiating encryption key for the initiating customer, and encrypt the initiating customer role and the aggregated application identification code according to the initiating encryption key;

[0048] Specifically, AES requires the encryption key to be 128 bits, 192 bits, or 256 bits in length. The higher the number of bits, the greater the encryption strength. The initiating customer uses its own encryption key to encrypt a JSON string consisting of its own customer role, collection application identification code, and other information.

[0049] Step S1053: Segment the plain text of the initiating customer role and the collection application identification code to form initiating plain text segment data;

[0050] Specifically, AES cuts the plaintext into segments, each of which must be 128 bits long (16 bytes). If the last segment is less than 16 bytes, padding is used to fill it with 16 bytes. Each segment is then encrypted separately, and finally the encrypted data is concatenated to form the final ciphertext.

[0051] There are three padding modes: PKCS5, PKCS7, and NOPADDING. PKCS5 and PKCS7 require that if a packet is missing a few bytes, the end of the data is padded with a few bytes. For example, if 5 bytes are missing, 5 bytes are added to the end. NoPadding requires no padding, meaning the sender ensures that the last segment of data is exactly 16 bytes. If the last segment of data in PKCS5 mode is exactly 16 bytes, PKCS5 will automatically add 16 bytes of data after the last segment, and the padding will also be 16 bytes. This allows the decrypted segment to distinguish between valid data and padding. The decryptor must use the same padding mode as the encryptor to accurately distinguish valid data from padding. We use the PKCS7 padding mode.

[0052] Step S1055: XOR the first initiating plaintext segment data with the set initialization vector, and encrypt the data using the initiating encryption key to form the first initiating ciphertext encrypted segment data;

[0053] Step S1057: XOR the second initiating plaintext segment data with the first initiating ciphertext encrypted segment data, and encrypt the resultant data using the initiating encryption key to form the second initiating ciphertext encrypted segment data. This process is repeated in this way to form all the initiating encrypted segment data.

[0054] Specifically, in steps S1055 to S1057, the ciphertext segment data encrypted from the same plaintext segment data is different, and the structure of the plaintext and the structure of the ciphertext are also different, so the encryption security is higher.

[0055] Step S1059: concatenate the initial encryption segment data to form a final initial encryption string;

[0056] Step S107: Similarly, an encrypted string is generated as the receiving customer's receipt code through a symmetric encryption algorithm according to the receiving customer's role and the collection application identification code;

[0057] like Figure 3 Specifically, step S107 includes:

[0058] Step S1071: Generate a receiving encryption key for the receiving customer, and encrypt the receiving customer role and the aggregated application identification code according to the receiving encryption key;

[0059] Specifically, AES requires the encryption key to be 128 bits, 192 bits, or 256 bits in length. The higher the number of bits, the greater the encryption strength. The receiving customer uses its own encryption key to encrypt a JSON string consisting of its own customer role, collection application identification code, and other information.

[0060] Step S1073: Segment the plain text of the received customer role and the collected application identification code to form received plain text segment data;

[0061] Specifically, AES cuts the plaintext into segments, each of which must be 128 bits long (16 bytes). If the last segment is less than 16 bytes, padding is used to fill it with 16 bytes. Each segment is then encrypted separately, and finally the encrypted data is concatenated to form the final ciphertext.

[0062] There are three padding modes: PKCS5, PKCS7, and NOPADDING. PKCS5 and PKCS7 require that if a packet is missing a few bytes, the end of the data is padded with a few bytes. For example, if 5 bytes are missing, 5 bytes are added to the end. NoPadding requires no padding, meaning the sender ensures that the last segment of data is exactly 16 bytes. If the last segment of data in PKCS5 mode is exactly 16 bytes, PKCS5 will automatically add 16 bytes of data after the last segment, and the padding will also be 16 bytes. This allows the decrypted segment to distinguish between valid data and padding. The decryptor must use the same padding mode as the encryptor to accurately distinguish valid data from padding. We use the PKCS7 padding mode.

[0063] Step S1075: XOR the first received plaintext segment data with the set initialization vector, and encrypt the data using the received encryption key to form the first received ciphertext encrypted segment data;

[0064] Step S1077: XOR the second received plaintext segment data with the first received ciphertext encrypted segment data, and encrypt the resultant data using the received encryption key to form the second received ciphertext encrypted segment data. This process is repeated in this way to form all received encrypted segment data.

[0065] Specifically, in steps S1075 to S1077, the ciphertext segment data encrypted from the same plaintext segment data is different, and the structure of the plaintext and the structure of the ciphertext are also different, so the encryption security is higher.

[0066] Step S1079: splicing the received encrypted segment data to form a final received encrypted string;

[0067] Step S109: Concatenate the initiating collection receipt code, the receiving collection receipt code, and the page address of the returned material to generate the material receipt addresses of the initiating customer and the receiving customer;

[0068] Step S111: Send the generated material receipt address to the mailboxes of the initiating customer and the receiving customer respectively by email;

[0069] Step S113: After receiving the email, the initiating / receiving customer opens the material receipt address link. The browser will display the customer's collection material return page. After the system front-end captures the collection receipt code in the address bar, it calls the system server interface.

[0070] Step S115: After receiving the collection receipt code, the server decrypts the code to obtain a unique collection application identification code and the customer roles of both parties. The collection application record table is searched based on the collection application identification code to obtain the collection application record.

[0071] Step S117: If the collection status in the collection application record table is "Submission pending", the current customer information of both parties (such as customer nickname, mobile phone number, company name, expiration date, etc.) is returned to the system front end according to the customer role, and the system front end page is displayed to the customer;

[0072] Step S119: If the collection status in the collection application record table is abnormal, such as expired, an error message indicating that the application record has expired is returned to the front end, prompting the customer to re-submit the collection application. For example, if the customer has already submitted the collection materials, a message will be displayed indicating that the materials have been submitted and that the customer does not need to submit them again.

[0073] Step S121: After the client confirms that the information displayed on the collection material receipt page is correct, the client uploads the collection material to the server as an attachment;

[0074] Step S123: After the server obtains the uploaded collection material file link and collection receipt code, it decrypts the collection receipt code to obtain the collection application identification code and the customer roles of both parties. Based on the customer role and collection application identification code, the collection material file link is saved to the corresponding customer information; after the material is successfully saved, the status in the collection application record table is changed to pending review.

[0075] The method for collecting customer application links in an embodiment of the present invention assigns a collection application identification code to its email, link, page and other modules after the customer submits the collection application. The collection application identification code is used to track the customer's tags and realize the real-time unique customer identity judgment; the materials and data of the customer's collection application are associated with the customer himself through the collection application identification code, realizing the data attribution function and completing the subsequent business process.

[0076] The customer application link aggregation method of the embodiment of the present invention only exposes the encrypted customer-specific aggregation receipt code to the outside world. The customer role and aggregation application identification code contained therein can only be decrypted on the server side. The method is simple and easy to implement, ensuring the security of the aggregation process.

[0077] It should be understood that in the embodiments of the present invention, the term "first initiating plaintext segment data / first received plaintext segment data" or "second initiating plaintext segment data / second received plaintext segment data" represents any one plaintext segment data among multiple initiating plaintext segment data / receiving plaintext segment data. The embodiments of the present invention describe the first or second initiating plaintext segment data / receiving plaintext segment data with universal significance, making it easier for those skilled in the art to understand how to perform each initiating plaintext segment data / receiving plaintext segment data, thereby making it easier to understand the embodiments of the present invention, but the embodiments of the present invention are not limited to this.

[0078] Combined with the above Figures 1 to 3 , describes in detail the method for collecting customer application links according to an embodiment of the present invention, and will now combine Figure 4 , a detailed description of the client application link aggregation device according to an embodiment of the present invention.

[0079] Figure 4 FIG. 1 shows a schematic diagram of a structure of a client application link collection device provided by an embodiment of the present invention. Figure 4 As shown, the collection device of the customer application link includes:

[0080] The server 10 is configured to receive a collection application initiated by an initiating customer at the system collection application portal, receive customer information of both the initiating customer and the receiving customer, verify the company name, business license, and email address in the customer information of both parties, and generate a collection application identification code for the collection application upon passing the verification, decrypt the collection receipt code, obtain the customer roles and collection application identification codes of both customers, and retrieve the collection application record based on the collection application identification code.

[0081] The encryption generation module 20 is used to generate an encrypted string as the collection receipt code of the two customers through a symmetric encryption algorithm based on the customer roles and collection application identification codes of the two customers;

[0082] The address splicing module 30 is used to splice the collection receipt code with the page address of the corresponding return material to generate the material receipt address of both customers;

[0083] The receipt sending module 40 is used to send the receipt to the initiating customer and the receiving customer respectively via email according to the material receipt addresses of both customers;

[0084] The port calling module 50 is used to call the corresponding server interface according to the collection receipt code of both customers in the material receipt address;

[0085] The material uploading module 60 is used to upload the collection certification materials to the server for storage according to the customer roles and collection application identification codes of both parties after both parties confirm that the receipt page information in the collection application record is correct.

[0086] Optionally, in an embodiment of the present invention, the encryption generation module 20 includes a key generation submodule 21, a data segmentation submodule 22, an XOR encryption submodule 23, and a data splicing submodule 24:

[0087] The key generation submodule 21 is used to generate an encryption key for both customers and encrypt the customer roles and aggregation application identification codes of both customers according to the encryption key;

[0088] The data segmentation submodule 22 is used to segment the plain text data of the customer role and the collection application identification code into plain text segment data;

[0089] The XOR encryption submodule 23 is used to perform XOR encryption on the plaintext segment data according to the set initial vector and key offset to form encrypted segment data;

[0090] The data splicing submodule 24 is used to splice the encrypted segment data into a final encrypted string.

[0091] Optionally, in an embodiment of the present invention, the XOR encryption submodule 23 is specifically used to perform XOR processing on the first plaintext segment data and the initial vector, and form the first ciphertext encrypted segment data after encryption processing with the encryption key; perform XOR processing on the second plaintext segment data and the first ciphertext encrypted segment data, and form the second ciphertext encrypted segment data after encryption processing with the encryption key; and so on, to form all the encrypted segment data.

[0092] Optionally, in this embodiment of the present invention, a collection status module 70 is further included:

[0093] The collection status module 70 is configured to return the customer information of both parties to the system according to the customer role if the collection status in the collection application record indicates that materials are pending submission; and to remind the customer to re-initiate the collection application if the collection status in the collection application record indicates that there is an abnormality.

[0094] Therefore, the collection device of the customer application link in the embodiment of the present invention assigns a collection application identification code to the customer's email, link, page and other modules after the customer submits the collection application. The collection application identification code is used to track the customer's tags and realize the real-time unique customer identity judgment; the materials and data of the customer's collection application are associated with the customer himself through the collection application identification code, realizing the data attribution function and completing the subsequent business process.

[0095] Therefore, the collection device of the customer application link in the embodiment of the present invention only exposes the encrypted customer-specific collection receipt code to the outside world, and the customer role and collection application identification code contained therein can only be decrypted on the server side. The method is simple and easy to implement, ensuring the security of the collection process.

[0096] In addition, an embodiment of the present invention also provides an electronic device, including a bus, a transceiver, a memory, a processor, and a computer program stored in the memory and runnable on the processor. The transceiver, the memory, and the processor are respectively connected via a bus. When the computer program is executed by the processor, each process of the above-mentioned embodiment of the method for aggregating customer application links is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0097] For details, see Figure 5 As shown, an embodiment of the present invention further provides an electronic device, which includes a bus 51 , a processor 52 , a transceiver 53 , a bus interface 54 , a memory 55 and a user interface 56 .

[0098] In an embodiment of the present invention, the electronic device further includes: a computer program stored in the memory 55 and executable on the processor 52, wherein when the computer program is executed by the processor 52, the following steps are implemented:

[0099] Upon receiving the collection application from the initiating customer at the collection application portal of the system, the server receives the customer information of both the initiating customer and the receiving customer;

[0100] The server verifies the company name, business license, and email address of both parties' customer information. If the verification is successful, it generates a collection application identification code for the collection application.

[0101] Generate an encrypted string as the collection receipt code for both customers through a symmetric encryption algorithm based on the customer roles and collection application identification codes of both customers;

[0102] The collection receipt code is combined with the page address of the corresponding returned material to generate the material receipt address of both customers;

[0103] Send the materials to the initiating customer and the receiving customer by email according to the material receipt addresses of both customers;

[0104] Call the corresponding server interface according to the collection receipt code of both customers in the material receipt address;

[0105] The server decrypts the collection receipt code to obtain the customer roles and collection application identification codes of both customers, and obtains the collection application record based on the collection application identification code;

[0106] After both parties confirm that the information on the receipt page in the collection application record is correct, they upload the collection certification materials to the server for storage based on the customer roles and collection application identification codes of both parties.

[0107] Optionally, when the computer program is executed by the processor 52, the following steps may be further implemented:

[0108] Generate an encryption key for both customers, and encrypt the customer roles and aggregation application identification codes of both customers according to the encryption key;

[0109] Segmenting the plaintext data of the customer role and the aggregated application identification code into plaintext segment data;

[0110] According to the set initial vector and key offset, the plaintext segment data is XOR-encrypted to form encrypted segment data;

[0111] The encrypted segment data are concatenated to form a final encrypted string.

[0112] Optionally, when the computer program is executed by the processor 52, the following steps may be further implemented:

[0113] Performing an XOR operation on the first plaintext segment data and the initial vector, and encrypting the resultant data with the encryption key to form a first ciphertext encrypted segment data;

[0114] Performing an XOR operation on the second plaintext segment data and the first ciphertext encrypted segment data, and encrypting the resultant data with the encryption key to form the second ciphertext encrypted segment data;

[0115] And so on, forming all the encrypted segment data.

[0116] Optionally, when the computer program is executed by the processor 52, the following steps may be further implemented:

[0117] If the collection status in the collection application record is "Submission pending", the customer information of both parties is returned to the system according to the customer role;

[0118] If the collection status in the collection application record is abnormal, remind the customer to re-initiate the collection application.

[0119] The transceiver 53 is configured to receive and send data under the control of the processor 52 .

[0120] exist Figure 5 In the figure, a bus architecture (represented by bus 51) is shown, which may include any number of interconnected buses and bridges, connecting various circuits including one or more processors represented by processor 52 and memory represented by memory 55.

[0121] Bus 51 represents one or more of any of several types of bus structures, including a memory bus and memory controller, a peripheral bus, an Accelerated Graphical Port (AGP), a processor, or a local bus using any of a variety of bus architectures. By way of example and not limitation, such architectures include: an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, a Video Electronics Standards Association (VESA), and a Peripheral Component Interconnect (PCI) bus.

[0122] The processor 52 can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by an integrated logic circuit of the hardware in the processor or by instructions in the form of software. The above processors include: a general-purpose processor, a central processing unit (CPU), a network processor (NP), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), a complex programmable logic device (CPLD), a programmable logic array (PLA), a microcontroller unit (MCU) or other programmable logic devices, discrete gates, transistor logic devices, discrete hardware components. The various methods, steps and logic block diagrams disclosed in the embodiments of the present invention can be implemented or executed. For example, the processor can be a single-core processor or a multi-core processor, and the processor can be integrated into a single chip or located on multiple different chips.

[0123] The processor 52 can be a microprocessor or any conventional processor. The method steps disclosed in conjunction with the embodiments of the present invention can be directly executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a readable storage medium known in the art, such as a random access memory (RAM), a flash memory (Flash Memory), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), or a register. The readable storage medium is located in a memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method.

[0124] The bus 51 may also connect various other circuits, such as peripheral devices, voltage regulators, or power management circuits, and the bus interface 54 provides an interface between the bus 51 and the transceiver 53. These are all well known in the art and are therefore not further described in this embodiment of the present invention.

[0125] The transceiver 53 can be a single component or multiple components, such as multiple receivers and transmitters, providing a means for communicating with various other devices over a transmission medium. For example, the transceiver 53 receives external data from other devices and transmits data processed by the processor 52 to other devices. Depending on the nature of the computer system, a user interface 56 may also be provided, such as a touch screen, physical keyboard, display, mouse, speaker, microphone, trackball, joystick, or stylus.

[0126] It should be understood that in an embodiment of the present invention, the memory 55 may further include a memory remotely located relative to the processor 52, and these remotely located memories may be connected to the server via a network. One or more parts of the aforementioned network may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless local area network (WLAN), a wide area network (WAN), a wireless wide area network (WWAN), a metropolitan area network (MAN), the Internet, a public switched telephone network (PSTN), a plain old telephone service network (POTS), a cellular telephone network, a wireless network, a wireless fidelity (Wi-Fi) network, and a combination of two or more of the aforementioned networks. For example, the cellular telephone network and the wireless network can be a Global System for Mobile Communications (GSM) system, a Code Division Multiple Access (CDMA) system, a Worldwide Interoperability for Microwave Access (WiMAX) system, a General Packet Radio Service (GPRS) system, a Wideband Code Division Multiple Access (WCDMA) system, a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD) system, an Advanced Long Term Evolution (LTE-A) system, a Universal Mobile Telecommunications (UMTS) system, an Enhanced Mobile Broadband (eMBB) system, a Massive Machine Type of Communication (mMTC) system, an Ultra Reliable Low Latency Communications (uRLLC) system, and the like.

[0127] It should be understood that the memory 55 in the embodiment of the present invention may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, non-volatile memories include: read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory.

[0128] Volatile memory includes random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 55 of the electronic device described in the embodiments of the present invention includes, but is not limited to, the above and any other suitable types of memory.

[0129] In the embodiment of the present invention, the memory 55 stores the following elements of the operating system 551 and the application program 552: executable modules, data structures, or subsets thereof, or extended sets thereof.

[0130] Specifically, the operating system 551 includes various system programs, such as a framework layer, a core library layer, and a driver layer, which are used to implement various basic services and process hardware-based tasks. The application 552 includes various application programs, such as a media player and a browser, which are used to implement various application services. The program that implements the method of the embodiment of the present invention can be included in the application 552. The application 552 includes applets, objects, components, logic, data structures, and other computer system executable instructions that perform specific tasks or implement specific abstract data types.

[0131] In addition, an embodiment of the present invention also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, it implements the various processes of the above-mentioned customer application link collection method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0132] Specifically, when the computer program is executed by a processor, the following steps can be implemented:

[0133] Upon receiving the collection application from the initiating customer at the collection application portal of the system, the server receives the customer information of both the initiating customer and the receiving customer;

[0134] The server verifies the company name, business license, and email address of both parties' customer information. If the verification is successful, it generates a collection application identification code for the collection application.

[0135] Generate an encrypted string as the collection receipt code for both customers through a symmetric encryption algorithm based on the customer roles and collection application identification codes of both customers;

[0136] The collection receipt code is combined with the page address of the corresponding returned material to generate the material receipt address of both customers;

[0137] Send the materials to the initiating customer and the receiving customer by email according to the material receipt addresses of both customers;

[0138] Call the corresponding server interface according to the collection receipt code of both customers in the material receipt address;

[0139] The server decrypts the collection receipt code to obtain the customer roles and collection application identification codes of both customers, and obtains the collection application record based on the collection application identification code;

[0140] After both parties confirm that the information on the receipt page in the collection application record is correct, they upload the collection certification materials to the server for storage based on the customer roles and collection application identification codes of both parties.

[0141] Optionally, when the computer program is executed by a processor, the following steps may be further implemented:

[0142] Generate an encryption key for both customers, and encrypt the customer roles and aggregation application identification codes of both customers according to the encryption key;

[0143] Segmenting the plaintext data of the customer role and the aggregated application identification code into plaintext segment data;

[0144] According to the set initial vector and key offset, the plaintext segment data is XOR-encrypted to form encrypted segment data;

[0145] The encrypted segment data are concatenated to form a final encrypted string.

[0146] Optionally, when the computer program is executed by a processor, the following steps may be further implemented:

[0147] Performing an XOR operation on the first plaintext segment data and the initial vector, and encrypting the resultant data with the encryption key to form a first ciphertext encrypted segment data;

[0148] Performing an XOR operation on the second plaintext segment data and the first ciphertext encrypted segment data, and encrypting the resultant data with the encryption key to form the second ciphertext encrypted segment data;

[0149] And so on, forming all the encrypted segment data.

[0150] Optionally, when the computer program is executed by a processor, the following steps may be further implemented:

[0151] If the collection status in the collection application record is "Submission pending", the customer information of both parties is returned to the system according to the customer role;

[0152] If the collection status in the collection application record is abnormal, remind the customer to re-initiate the collection application.

[0153] Computer-readable storage media include: permanent and non-permanent, removable and non-removable media, which are tangible devices that can retain and store instructions for use by instruction execution devices. Computer-readable storage media include: electronic storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, and any suitable combination of the above. Computer-readable storage media include: phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette storage, magnetic disk storage or other magnetic storage devices, memory sticks, mechanical encoding devices (such as punched cards or raised structures with grooves in which instructions are recorded), or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined in the embodiments of the present invention, computer-readable storage media does not include temporary signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (such as light pulses passing through fiber optic cables), or electrical signals transmitted through wires.

[0154] The serial numbers of the above embodiments of the present invention are for description only and do not represent the advantages or disadvantages of the embodiments.

[0155] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in the embodiments of the present invention can be implemented by electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the components and steps of each example have been generally described in terms of function in the above description. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer program instructions. The computer program instructions include: assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, integrated circuit configuration data, or source code or object code written in any combination of one or more programming languages, the programming language including object-oriented programming languages, such as Smalltalk, C++, and procedural programming languages, such as C or similar programming languages.

[0156] When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in accordance with the embodiments of the present invention are generated. The computer may be a computer, a dedicated computer, a computer network, or other editable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, twisted pair, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave) method. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media. The available medium may be a magnetic medium (e.g., a floppy disk, magnetic disk, tape), an optical medium (e.g., an optical disk), or a semiconductor medium (e.g., a solid-state drive (SSD)). Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of the present invention.

[0157] Those skilled in the art will clearly understand that, for the sake of convenience and brevity of description, the specific working processes of the above-described systems, devices and units can refer to the corresponding processes in the aforementioned embodiments of the method of the present invention and will not be repeated here.

[0158] In the several embodiments provided in this application, it should be understood that the disclosed devices, electronic devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or can be an electrical, mechanical or other form of connection.

[0159] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, and may be located in a single location or distributed across multiple network units. Some or all of these units may be selected based on actual needs to address the issues addressed by the embodiments of the present invention.

[0160] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0161] If the integrated unit is implemented in the form of 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 the embodiment of the present invention is essentially 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, which is stored in a storage medium and includes several instructions for enabling a computer device (including: a personal computer, a server, a data center or other network device) to perform all or part of the steps of the method described in each embodiment of the present invention. The above-mentioned storage medium includes the various media that can store program codes as listed above.

[0162] The above description is merely a specific implementation of the embodiments of the present invention, but the scope of protection of the embodiments of the present invention is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the embodiments of the present invention should be included in the scope of protection of the embodiments of the present invention. Therefore, the scope of protection of the embodiments of the present invention should be based on the scope of protection of the claims.

Claims

1. A method for collecting customer application links, characterized in that: include: Upon receiving the collection application from the initiating customer at the collection application portal of the system, the server receives the customer information of both the initiating customer and the receiving customer; The server verifies the company name, business license, and email address of both parties' customer information. If the verification is successful, it generates a collection application identification code for the collection application. Generate an encrypted string as the collection receipt code for both customers through a symmetric encryption algorithm based on the customer roles and collection application identification codes of both customers; The collection receipt code is combined with the page address of the corresponding returned material to generate the material receipt address of both customers; Send the materials to the initiating customer and the receiving customer by email according to the material receipt addresses of both customers; Call the corresponding server interface according to the collection receipt code of both customers in the material receipt address; The server decrypts the collection receipt code to obtain the customer roles and collection application identification codes of both customers, and obtains the collection application record based on the collection application identification code; After both parties confirm that the information on the receipt page in the collection application record is correct, they upload the collection certification materials to the server for storage based on the customer roles and collection application identification codes of both parties.

2. The method according to claim 1, characterized in that The step of generating an encrypted string as the collection receipt code of both customers through a symmetric encryption algorithm based on the customer roles and collection application identification codes of both customers specifically includes: Generate an encryption key for both customers, and encrypt the customer roles and aggregation application identification codes of both customers according to the encryption key; Segmenting the plaintext data of the customer role and the aggregated application identification code into plaintext segment data; According to the set initial vector and key offset, the plaintext segment data is XOR-encrypted to form encrypted segment data; The encrypted segment data are concatenated to form a final encrypted string.

3. The method according to claim 2, characterized in that The step of performing XOR encryption on the plaintext segment data to form encrypted segment data according to the set initial vector and key offset specifically includes: Performing an XOR operation on the first plaintext segment data and the initial vector, and encrypting the resultant data with the encryption key to form a first ciphertext encrypted segment data; Performing an XOR operation on the second plaintext segment data and the first ciphertext encrypted segment data, and encrypting the resultant data with the encryption key to form the second ciphertext encrypted segment data; And so on, forming all the encrypted segment data.

4. The method according to claim 1, wherein Also includes: If the collection status in the collection application record is "Submission pending", the customer information of both parties is returned to the system according to the customer role; If the collection status in the collection application record is abnormal, remind the customer to re-initiate the collection application.

5. A device for collecting customer application links, characterized in that: include: The server is used to receive the collection application initiated by the initiating customer at the system collection application portal, and receive the customer information of both the initiating customer and the receiving customer; Verify the company name, business license, and email address in the customer information of both parties. If the verification is successful, generate a collection application identification code for the collection application; decrypt the collection receipt code to obtain the customer role and collection application identification code of both parties, and query the collection application record based on the collection application identification code; An encryption generation module is used to generate an encrypted string as a collection receipt code for both customers through a symmetric encryption algorithm based on the customer roles and collection application identification codes of both customers; An address splicing module is used to splice the collection receipt code with the page address of the corresponding return material to generate the material receipt address of both customers; The receipt sending module is used to send the receipt to the initiating customer and the receiving customer via email according to the material receipt addresses of both customers; A port calling module is used to call the corresponding server interface according to the collection receipt codes of both customers in the material receipt address; The material uploading module is used to upload the collection certification materials to the server for storage according to the customer roles and collection application identification codes of both customers after both customers confirm that the receipt page information in the collection application record is correct.

6. The device according to claim 5, characterized in that The encryption generation module includes a key generation submodule, a data segmentation submodule, an XOR encryption submodule and a data splicing submodule: The key generation submodule is used to generate an encryption key for both customers, and encrypt the customer roles and aggregation application identification codes of both customers according to the encryption key; The data segmentation submodule is used to segment the plaintext data of the customer role and the aggregated application identification code into plaintext segment data; The XOR encryption submodule is used to perform XOR encryption processing on the plaintext segment data to form encrypted segment data according to the set initial vector and key offset; The data splicing submodule is used to splice the encrypted segment data to form a final encrypted string.

7. The device according to claim 6, characterized in that The XOR encryption submodule is specifically configured to perform an XOR process on the first plaintext segment data and the initialization vector, and encrypt the data using the encryption key to form a first ciphertext encrypted segment data; and perform an XOR process on the second plaintext segment data and the first ciphertext encrypted segment data, and encrypt the data using the encryption key to form a second ciphertext encrypted segment data; And so on, forming all the encrypted segment data.

8. The device according to claim 5, characterized in that Also includes the collection status module: The collection status module is configured to return the customer information of both parties to the system according to the customer role if the collection status in the collection application record is "materials to be submitted"; and to remind the customer to re-initiate the collection application if the collection status in the collection application record is "abnormal".

9. An electronic device comprising a bus, a transceiver, a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the transceiver, the memory, and the processor are connected via the bus, wherein: When the computer program is executed by the processor, the steps of the method for aggregating customer application links according to any one of claims 1 to 4 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method for aggregating customer application links according to any one of claims 1 to 4 are implemented.

Images