Multi-protocol collaborative subscription method, device, medium and program product

Abstract

The application provides a multi-protocol cooperative signing method, device, medium and program product. The method comprises the following steps: acquiring a plurality of related protocols which have a correlation relationship with each other; generating signing information according to the plurality of related protocols; and sending the signing information to a client. After confirming that the client completes the signing of the plurality of related protocols, the signing process of a supplier end is controlled, so that the loss of the client caused by the missed signing of the protocol is avoided.

Description

Technical Field

[0001] This application relates to the field of computer technology, specifically to a multi-protocol system signing method, device, medium, and program product. Background Technology

[0002] Customers can enjoy discounts on a variety of products. Taking logistics services as an example, these can be further divided into e-commerce services, dry delivery services, and express services. Each logistics service has different terms and discount criteria, stipulated through different agreements. Therefore, customers need to sign multiple agreements.

[0003] In existing technologies, when a single customer signs multiple agreements, each agreement is typically signed separately. However, these agreements may interfere with each other, leading to additional discounts when the customer ships goods, resulting in losses for the logistics service provider. Alternatively, due to missing agreements, the customer may only be able to enjoy discounts on a single logistics service, causing further losses.

[0004] For example, if a customer requires both e-commerce and dry delivery services when shipping goods, they can enjoy a discount of 0.8 for e-commerce services and 0.9 for dry delivery services. If each agreement is signed separately, the customer will receive an additional discount of 0.8 for dry delivery services on top of the existing 0.9 discount for e-commerce services. If the agreement for dry delivery services is not signed, the customer will only receive the 0.8 discount for e-commerce services, with no discount for dry delivery services. Summary of the Invention

[0005] Based on the defects and shortcomings of the existing technology, this application proposes a multi-protocol system signing method, device, medium and program product, which can generate signing information based on multiple related protocols with mutual relationships and send it to the client. After confirming that the client has completed the signing of multiple related protocols, the application controls the signing process on the supplier side to avoid the problem of the client missing the signing of the protocol and causing the client to suffer losses.

[0006] According to a first aspect of the embodiments of this application, a multi-protocol collaborative signing method is provided, including:

[0007] The system acquires multiple related agreements, which are associated with each other; generates signing information based on the multiple related agreements and sends the signing information to the client; after confirming that the client has completed the signing of the multiple related agreements, the system controls the signing process to enter the supplier's side.

[0008] According to a second aspect of the embodiments of this application, a multi-protocol collaborative signing device is provided, comprising:

[0009] The module is used to acquire multiple related protocols, which are associated with each other; the module is used to generate signing information based on the multiple related protocols; the module is used to send the signing information to the client; and the module is used to control the signing process entering the supplier's side after confirming that the client has completed the signing of the relevant protocols.

[0010] According to a third aspect of the embodiments of this application, an electronic device is provided, including a memory and a processor;

[0011] The memory is connected to the processor and is used to store programs;

[0012] The processor is used to implement the multi-protocol collaborative signing method as described in the first aspect by running a program in the memory.

[0013] According to a fourth aspect of the embodiments of this application, a storage medium is provided, on which a computer program is stored, and when the computer program is run by a processor, it implements the multi-protocol collaborative signing method as described in the first aspect.

[0014] According to a fifth aspect of the embodiments of this application, a computer program product is provided, including computer program instructions, which, when executed by a processor, cause the processor to perform the multi-protocol cooperative signing method as described in the first aspect.

[0015] The aforementioned multi-protocol collaborative signing method, equipment, media, and program products acquire multiple related protocols that are interconnected, generate signing information based on these protocols, and send the signing information to the client. After confirming that the client has completed the signing of multiple related protocols, the signing process at the supplier's end is controlled to prevent customers from missing signing agreements and incurring losses. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0017] Figure 1 This is a flowchart illustrating a multi-protocol collaborative signing method as provided in an embodiment of this application;

[0018] Figure 2 This is a schematic diagram illustrating a multi-protocol collaborative signing process as provided in an embodiment of this application;

[0019] Figure 3This is a schematic diagram of the structure of a multi-protocol collaborative signing device provided in an embodiment of this application;

[0020] Figure 4 This is a schematic diagram of the structure of an electronic device proposed in an embodiment of this application. Detailed Implementation

[0021] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0022] Overview

[0023] As described in the background section, customers can enjoy discounts on various products, each with different terms and discount levels, stipulated through different agreements. Therefore, customers need to sign multiple agreements. In existing technology, when a single customer signs multiple agreements, each agreement is typically signed separately. However, the multiple agreements signed by the same customer may interfere with each other, leading to additional discounts when the customer ships goods, causing losses for the logistics service provider. Alternatively, due to missing agreements, customers may only be able to enjoy discounts on a single logistics service when shipping goods, resulting in losses for the customer.

[0024] Building upon this foundation, the inventors further discovered that having customers sign supplier agreements only after they have completed all the necessary product agreements can effectively prevent customers from missing agreements. Therefore, by first acquiring multiple related agreements and generating and sending signing information based on these agreements, and then controlling the supplier signing process only after confirming that the customer has completed all related agreements, the system can effectively prevent customers from missing agreements and thus avoid losses due to such omissions.

[0025] Based on the above concept, this specification provides a multi-protocol collaborative signing method, which will be described exemplarily below with reference to the accompanying drawings.

[0026] Exemplary methods

[0027] Please see Figure 1 In one exemplary embodiment, a multi-protocol collaborative signing method is provided, applied to any electronic device, which is a supplier-side device. This method can acquire multiple related protocols that are interconnected, communicate with a client, and control the signing process entering the supplier's side. For example... Figure 1As shown, the multi-protocol collaborative signing method includes steps S101-S103:

[0028] S101: Obtain multiple related protocols.

[0029] Among them, there are related agreements.

[0030] Specifically, these multiple related agreements are determined based on customer needs and are all agreements corresponding to the products required by the customer, including relevant terms and discount information for the required products. Among them, the relevant terms are the information provided by the supplier to the customer regarding the product, excluding discount information.

[0031] When acquiring multiple related agreements, first obtain the customer's requirements, and then, based on those requirements, acquire the corresponding related agreements. The customer's requirements must include at least the customer's desired product, i.e., the product the customer needs.

[0032] When obtaining multiple relevant agreements corresponding to customer needs, multiple agreement templates are determined based on customer needs. These templates are then adjusted, and the relevant terms and discount information of the products required by the customer are stored in these templates, resulting in multiple relevant agreements.

[0033] S102: Generate signing information based on multiple related protocols and send the signing information to the client.

[0034] The contract information can be a contract link, through which the text of multiple related agreements can be retrieved. Alternatively, the contract information can also be the text of multiple related agreements.

[0035] Depending on the specific needs, the contract information can also be information such as the identifier of the relevant agreement.

[0036] Additionally, "client" can refer to the client-side device, specifically the device itself or the software receiver installed on it. Clients can receive contract information via email address, mobile phone number, etc.

[0037] Accordingly, the client receives the signing information and displays multiple related agreements based on the signing information, so that the client can sign the agreement based on the agreement text.

[0038] The signing process includes signing and stamping. Depending on the specific needs, clients can also add necessary information when signing, such as the client's name and the person responsible for the signing.

[0039] When the signing information is a signing link, the client retrieves and displays the relevant agreements based on the signing link; when the signing information is the text of multiple related agreements, the text of these multiple related agreements is displayed directly.

[0040] Specifically, the client displays the protocol texts of multiple related agreements one by one. After signing the currently displayed related agreement, the client automatically or in response to the user's action displays the protocol text of the next related agreement, until the client has signed all related agreements.

[0041] S103: After confirming that the customer has completed the signing of multiple related agreements, control the signing process on the supplier side.

[0042] The supplier side generally refers to the equipment on the supplier's side, specifically the equipment itself or the software client installed on the equipment.

[0043] After the customer completes the signing of multiple related agreements, they send a confirmation message to the supplier. This message informs the supplier that the customer has completed the signing of multiple related agreements. The supplier can then use this confirmation to verify that the customer has completed the signing of multiple related agreements and subsequently control the signing process on their end.

[0044] After entering the supplier's contract signing process, the supplier displays the texts of multiple related agreements one by one. After completing the signing of the currently displayed related agreement, the next related agreement text is displayed automatically or in response to the supplier's operation, until the supplier has completed the signing of all related agreements.

[0045] The signing of these multiple related agreements by the supplier includes signing and stamping.

[0046] During the signing of multiple related agreements, customers can also send feedback information to the supplier after completing the signing of each related agreement. This feedback information informs the supplier that the customer has completed the signing of the relevant agreement. This feedback information includes details such as the identifier of the relevant agreement.

[0047] The aforementioned feedback information and contract completion information can be automatically sent to the supplier in response to the customer's contract status, or they can be sent to the supplier by the client in response to the supplier's contract status confirmation request.

[0048] Specifically, when the client responds to the supplier's contract status confirmation request by sending feedback information and contract completion information to the supplier, this contract status request can be sent periodically by the supplier. The contract status confirmation request is used to confirm whether the client has completed signing the various relevant agreements.

[0049] It should also be noted that if it is confirmed that the customer has not completed the signing of multiple related agreements, the process of signing agreements with the supplier will not be initiated.

[0050] In this embodiment, multiple related agreements with interrelationships are obtained, signing information is generated based on the multiple related agreements, and the signing information is sent to the client. After confirming that the client has completed the signing of multiple related agreements, the signing process entering the supplier's side is controlled to achieve collaborative signing, avoid customer losses due to missed, incorrect, or insufficient signing of agreements, and avoid accounts receivable issues in the later pricing of products.

[0051] To avoid losses for suppliers due to additional discounts offered by customers when using products provided by suppliers, in some embodiments, discount information can be stored in a single file, while other product information can be stored separately.

[0052] Specifically, the multiple related agreements include a target discount agreement and multiple target product agreements. The target discount agreement includes discount information for the target products corresponding to the multiple target product agreements, and the target product agreements include other information for their corresponding target products.

[0053] The target product is the product awaiting a customer contract. Other information is the aforementioned relevant regulations, which are explained above and will not be repeated here.

[0054] Correspondingly, when obtaining multiple related agreements, it is necessary to first determine the agreement template corresponding to the product to be signed by the customer, i.e. the target product, and the agreement template for storing discount information based on customer needs. Based on the target product and the corresponding discount information, the agreement template corresponding to the target product is adjusted to obtain multiple target product agreements. The agreement template for storing the discount information of the target product is then adjusted, and the discount information of the target product is stored in the agreement template to obtain the target discount agreement.

[0055] In this embodiment, the target discount agreement among multiple related agreements stores discount information for all products required by the customer. After the signing of multiple related agreements is completed, the discount that the customer can enjoy is uniformly calculated based on the target discount agreement when the customer needs the supplier to provide services for shipment. This can effectively avoid the situation of discounts on top of discounts, avoid losses on the supplier side, and also avoid the situation where a single product is effective but the corresponding discount information for that product is not effective, thereby reducing the accounts receivable problems that may arise in the later pricing of the product.

[0056] To avoid customer losses due to under-signing, omission, or incorrect signing of agreements, in some embodiments, before obtaining multiple related agreements, the association between the protocol templates of multiple related agreements is established first. When obtaining multiple related agreements, based on the association between the protocol templates of multiple related agreements, the protocol templates of multiple related agreements are obtained first, and then the protocol templates of multiple related agreements are adjusted to obtain multiple related agreements.

[0057] Since each customer's actual needs, i.e., the products they require, may be different, the agreement templates corresponding to the multiple related agreements that the customer needs to sign will also be different. Therefore, when establishing the relationship between the agreement templates of multiple related agreements, it is usually to directly establish the relationship between the agreement templates of all agreements provided by the supplier. When obtaining multiple agreement templates, based on the relationship between the agreement templates of all related agreements provided by the supplier, the agreement templates of multiple related agreements are first obtained, and then the multiple related agreement templates are adjusted to obtain multiple related agreements.

[0058] Specifically, before acquiring multiple related protocols, different protocol templates are associated with business process codes to establish the relationship between different protocol templates.

[0059] Among them, the different agreement templates are the agreement templates and preferential agreement templates for all products that the supplier can provide.

[0060] For each agreement template, select a business process code to associate that business process code with the agreement template, until all agreement templates are associated with business process codes. For example, for a discount agreement, select the process code "300047" to associate the discount agreement with the process code "300047".

[0061] Based on actual needs, when a supplier adds a new business / product, a corresponding agreement template is added, and a business process code is selected for the newly added agreement template to associate the business process code with the newly added agreement template.

[0062] When a supplier reduces its business / product offerings, delete the corresponding agreement template and remove the association between the agreement template and the business process code.

[0063] Specifically, the agreement templates for products and preferential agreements provided by suppliers can be saved in a table for unified management. The table also records product information corresponding to the agreement templates, such as product identifiers, business process codes associated with each agreement template, and information such as identifiers of other agreement templates associated with each agreement template.

[0064] Furthermore, the business process code serves as an identifier for the business process. A business process represents the relevant operational procedures when a supplier provides a product to a customer, and different business processes are interconnected. Therefore, by associating different protocol templates with business process codes, the relationships between different protocol templates can be established, thus revealing the relationships between the aforementioned related protocols.

[0065] For example, the relationships between different business processes include preceding relationships, parallel relationships, and following relationships. A preceding relationship means that one business process must be executed before another business process can be executed. A parallel relationship means that two business processes must be executed simultaneously. A following relationship means that one business process must be executed after another business process can be executed.

[0066] For example, the process of the supplier providing product A is bound to the process of calculating the discount for product A. The protocol template of the product agreement corresponding to product A is associated with the process of the supplier providing product A, and the discount calculation process of product A is associated with the protocol template of the discount agreement. In this way, the association between the protocol template of the product agreement corresponding to product A and the protocol template of the discount agreement can be established.

[0067] Therefore, by associating different protocol templates with business process codes, the relationships between these related protocols can be established based on the relationships between the business process codes.

[0068] When obtaining multiple related protocols, calculations are performed based on the relationships between different protocol templates and the required products to obtain multiple target protocol templates. Then, multiple related protocols are generated based on these multiple target protocol templates.

[0069] Among them, the multiple target agreement templates are all agreement templates associated with the agreement template of the required product, including the discount agreement template and the agreement template of the target product. In addition, the multiple target agreement templates correspond one-to-one with multiple related agreements.

[0070] Specifically, the demand product is the product that the customer needs based on the customer's requirements, and the target product is the agreement to be signed by the customer, including the demand product and other products related to the demand product.

[0071] More specifically, the customer's desired product is determined based on user input, where the user input indicates the customer's desired product.

[0072] Among them, the products in demand can be added, deleted, or modified based on customer needs.

[0073] Generally, the above calculation operations are performed by the upstream system.

[0074] Specifically, during the calculation, information about the required product, such as its identifier and the association between different protocol templates, is uploaded to the upstream system. The upstream system then determines multiple protocol templates associated with the required product based on the association between the different protocol templates, including the discount protocol template and the target product's protocol template, as the target protocol templates, thus obtaining multiple target protocol templates.

[0075] The relationships between different protocol templates can be stored by the supplier after determining / updating the relationships, or they can be sent to the upstream system in real time when there is a measurement requirement. Depending on the actual needs, the relationships between different protocol templates can also be determined by the upstream system. The relationships between different protocol templates are updated as the protocol templates change.

[0076] After obtaining the required product, based on the relationship between different agreement templates, determine the agreement templates of other products associated with the agreement template of the required product, as well as the preferential agreement template. Take the required product and the determined other products as the target product, and then take the agreement template of the required product and the agreement template of the determined other products as the agreement template of the target product. After that, take the preferential agreement template and the agreement template of the target product as the target agreement template.

[0077] Specifically, for each required product, based on the association between its protocol template and different protocol templates, other protocol templates associated with the protocol template of the required product are determined. In this way, by traversing each of the multiple related protocols, all protocols in the multiple related protocols corresponding to the target product can be obtained.

[0078] When generating multiple related agreements based on multiple target agreement templates, the discount information of the target product is added to the discount agreement template to obtain the target discount agreement among multiple related agreements. Then, the corresponding target product agreement template is adjusted based on other information of the target product to obtain multiple target product agreements among multiple related agreements.

[0079] Based on varying customer needs and agreements between customers and suppliers, when calculating multiple target-related agreements, the customer's demand discounts for each required product can also be considered. These demand discounts are the discounts offered by the supplier to that customer, and may differ from the discounts enjoyed by other customers. In other words, by combining the required products and their demand discounts with the relationships between different agreement templates, calculations can be performed to obtain the agreement template and discount information for the target products.

[0080] Specifically, based on the association between the required product and different agreement templates, the agreement template for the target product is determined. For details on the implementation of this step, please refer to the above content. Additionally, based on the required discount for the required product and the discount information for other products associated with the required product, the discount information for the target product is summarized and generated.

[0081] After obtaining multiple relevant agreements, the basic information of the target product agreements within these agreements, including agreement codes, customer names, product names, and associated process codes, can be adjusted. Similarly, the basic information of the target discount agreements within these agreements, including agreement codes, customer names, discount information for each target product involved, and associated process codes, can also be adjusted.

[0082] After obtaining multiple related protocols, a list of these protocols is displayed, including their names. Selecting a specific related protocol will display all its associated protocols in the list.

[0083] For example, a discount agreement is selected and its basic information is displayed, along with related agreements such as the e-commerce small parcel product agreement, dry goods product agreement, and express parcel product agreement - discount version.

[0084] In addition, after obtaining multiple related agreements, you can also perform operations on the list displaying these multiple related agreements. For example, you can click the signing trigger button, such as the "Initiate Signing" text button, to send multiple related agreements to the client for signing.

[0085] Specifically, it can be either sending multiple related protocols directly to the client for signing, or sending the client a link that can retrieve multiple related protocols for signing.

[0086] After the relevant agreements are sent to the client for signing, the client's signing status is displayed in a list showing multiple relevant agreements. The client's signing status can be either "Client Confirmed" or "Client Confirming," or simply "Client Signed" or "Client Not Yet Completed Signing."

[0087] After sending the relevant agreements to the client for signing, a notification message can also be sent to the client to inform them that they have received multiple relevant agreements to be signed or links to multiple relevant agreements to be signed.

[0088] Furthermore, after sending the relevant agreements to the client for signing, multiple related agreements can be withdrawn simultaneously. For example, by clicking the "Cancel Agreement" button, multiple related agreements or their links can be withdrawn at once, terminating the client's signing process. This allows for the coordinated operation of multiple related agreements.

[0089] In this embodiment, different protocol templates are associated with business process codes to establish relationships between them. When acquiring multiple related protocols, calculations are performed based on these relationships and the protocol templates for the customer's desired product to obtain multiple target protocol templates, including discount agreement templates and target product agreement templates. Based on these target protocol templates, multiple related protocols corresponding to each target protocol template are generated. This way, when acquiring multiple related protocols, all protocol templates related to the customer's desired product can be obtained, thereby generating all protocols within the multiple related protocols. This prevents customers from missing, under-signing, or signing the wrong agreements, and avoids situations such as signing a discount agreement but not a product agreement, or signing a product agreement but not a discount agreement containing the corresponding discount information.

[0090] To ensure that signed agreements take effect simultaneously and to avoid losses to customers or suppliers due to the effectiveness of a single agreement, in some embodiments, after entering the signing process on the supplier's side, if it is detected that both the client and the supplier have completed the signing of multiple related agreements, the signing and effectiveness of multiple related agreements are controlled.

[0091] Accordingly, after entering the supplier's contract signing process, if it is detected that the customer or supplier has not completed the signing of any relevant agreement, the signing of the already signed relevant agreements will be temporarily suspended.

[0092] Thus, in this embodiment, after entering the supplier's signing process, when it is detected that the client and the supplier have completed the signing of multiple related agreements, the activation logic is automatically triggered to control the signing and activation of multiple related agreements, thereby ensuring that multiple related agreements take effect simultaneously after signing, and avoiding the situation where only some of the related agreements take effect.

[0093] In order to control the simultaneous effectiveness of multiple related agreements signed, in some embodiments, when it is detected that both the client and the supplier have completed the signing of multiple related agreements, the signing and effectiveness of multiple related agreements are controlled based on user input.

[0094] Specifically, a first input is received, which is used to trigger the signing and activation operation. Then, in response to the first input, the signing and activation of multiple related agreements are controlled.

[0095] The first input can be a click operation. For example, after a customer and supplier have signed multiple related agreements, clicking a button such as "Activate" can trigger the activation logic of these multiple related agreements, thus controlling the activation of multiple related agreements.

[0096] Thus, in this embodiment, when it is detected that both the client and the supplier have completed the signing of multiple related agreements, a first input for triggering the signing to take effect is received, and in response to the first input, the signing of multiple related agreements is controlled to take effect, so as to realize the simultaneous effect of multiple related agreements and avoid the situation where some related agreements take effect only individually, thereby avoiding losses for both the client and the supplier.

[0097] In some embodiments, after a customer completes the signing of multiple related agreements, the supplier automatically controls the activation of the multiple related agreements based on the signing feedback.

[0098] In some embodiments, the supplier provides a query interface for downstream systems to perform real-time queries on multiple related protocols and their effectiveness.

[0099] Information regarding multiple protocols and their validity can be sent to downstream systems via Topic communication and a query interface.

[0100] For example, downstream systems include product platforms and pricing systems, etc.

[0101] This makes it easier for downstream systems to understand the content of the relevant protocols and whether the protocols are effective.

[0102] For example, a multi-protocol collaborative signing process can be as follows: Figure 2 As shown, after receiving multiple agreements, including Agreement A and Agreement B, the customer first selects Agreement A and signs it, i.e., signs Agreement A. Then, the customer selects Agreement B and signs it, i.e., signs Agreement B. After that, the customer enters the supplier's signing process, which can follow the same process as signing with the customer: first, select Agreement A and sign it, i.e., signs Agreement A. Then, select Agreement B and sign it, i.e., signs Agreement B. After that, the customer controls Agreement A and Agreement B to take effect. Finally, the multiple agreements are integrated and distributed to other systems, i.e., downstream systems can receive and query the Agreement A and Agreement B signed between the customer and the supplier.

[0103] In some embodiments, after multiple related agreements are signed and become effective, the status of each agreement signed by the customer is adjusted, that is, the status of each agreement that has never been effective is adjusted to the status that has been effective.

[0104] Information on all relevant agreements signed by the client can be displayed in tabular form, including the agreement number, the associated business process code, the agreement name, whether the agreement is in effect, and the client's name. When an agreement is in effect, the table also stores the agreement's start and end dates.

[0105] In this way, relevant personnel can quickly understand whether multiple related agreements of the client are in effect, when they started taking effect, and when they ended.

[0106] To avoid blockages in the signing process, which could lead to prolonged signing times or difficulty in completing the signing, some embodiments may monitor the status of each node in the signing process of multiple related agreements, and output an error alert when the status of a certain node is abnormal.

[0107] Specifically, during the signing process of multiple related agreements, the status of each node in the signing process is recorded. Based on the status of each node in the signing process of multiple related agreements, it is determined whether the signing process is abnormal. If the signing process is abnormal, an abnormality alert message is output, including the reason for the abnormality.

[0108] The signing process includes stages such as agreement generation, customer signing, and supplier signing.

[0109] In other words, during the signing of multiple related agreements, the entire lifecycle of the signing process is recorded, that is, the time from the generation of the relevant agreement to the supplier completing the signing of the relevant agreement.

[0110] In the status of each node, the status of protocol generation is either "protocol has been generated" or "protocol has not been fully generated", the status of customer signing is either "customer has completed signing multiple related protocols" or "customer has not completed signing multiple related protocols", and the status of supplier signing is "supplier has completed signing multiple related protocols".

[0111] In addition, abnormal reasons such as incomplete agreement generation, customer failure to sign multiple related agreements, and supplier failure to sign related agreements can all be considered as abnormal reasons.

[0112] Of course, depending on the actual needs, the reasons for the anomaly can be further refined, such as the failure to complete the signing of a certain related agreement for a long time.

[0113] Before outputting abnormal alerts, the status of each node can be re-checked to determine whether each node is abnormal, and an alert can be issued if an abnormality is found.

[0114] Thus, in this embodiment, by recording the status of each node in the signing process and outputting an error reminder message including the reason for the error when the signing process is abnormal, the error reason can be reminded in a timely manner, so that the supplier or customer can take corresponding measures to resolve the error in a timely manner.

[0115] To prevent customers from missing, missigning, or undersigning agreements, in some implementations, the signing process on the supplier's side is manually triggered, and the signing process on the supplier's side only begins after the customer has completed the signing.

[0116] Specifically, the system receives a second input, which triggers the supplier's contract signing process. In response to the second input, it determines whether the client has completed the signing of multiple related agreements. If the client has completed the signing of multiple related agreements, the system proceeds to the supplier's contract signing process. If the client has not completed the signing of multiple related agreements, it outputs a notification message explaining why the supplier's contract signing process could not proceed.

[0117] In this way, after receiving the second input, the process can be completed only after confirming that the client has signed multiple related agreements before proceeding to the supplier's signing process. This can effectively prevent situations where the client misses, missigns, or undersigns agreements.

[0118] Of course, depending on the actual needs, the supplier can automatically enter the signing process on the supplier side after the client has completed the signing of multiple related agreements.

[0119] Exemplary device

[0120] like Figure 3 As shown in the figure, this application embodiment also provides a multi-protocol collaborative signing device, including an acquisition module 201, a generation module 202, a sending module 203, and a control module 204.

[0121] in,

[0122] Module 201 is used to acquire multiple related protocols;

[0123] Generation module 202 is used to generate contract information based on multiple related agreements;

[0124] Sending module 203 is used to send contract information to the client;

[0125] The control module 204 is used to control the signing process at the supplier's end after confirming that the customer has completed the signing of multiple related agreements.

[0126] The multi-protocol collaborative signing device provided in this embodiment belongs to the same application concept as the multi-protocol collaborative signing method provided in the above embodiments of this application. It can execute the method provided in any of the above embodiments of this application and has the corresponding functional modules and beneficial effects of the method. Technical details not described in detail in this embodiment can be found in the specific processing content of the multi-protocol collaborative signing method provided in the above embodiments of this application, and will not be repeated here.

[0127] The functions implemented by the acquisition module 201, generation module 202, sending module 203 and control module 204 can be implemented by the same or different processors calling software, and this application embodiment does not limit this.

[0128] Exemplary electronic devices

[0129] Another embodiment of this application also provides an electronic device, see [link to relevant documentation] Figure 4 As shown, the electronic device includes a memory 300 and a processor 310.

[0130] The memory 300 is connected to the processor 310 and is used to store programs;

[0131] The processor 310 is used to implement the multi-protocol collaborative signing method disclosed in any of the above embodiments by running the program stored in the memory 300.

[0132] Specifically, the electronic device may also include: a bus, a communication interface 320, an input device 330, and an output device 340.

[0133] The processor 310, memory 300, communication interface 320, input device 330, and output device 340 are interconnected via a bus. Among them:

[0134] A bus can include a pathway for transmitting information between various components of a computer system.

[0135] The processor 310 can be a general-purpose processor, such as a general-purpose central processing unit (CPU), a microprocessor, etc., or an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present application. It can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0136] Processor 310 may include a main processor, as well as a baseband chip, modem, etc.

[0137] The memory 300 stores a program for executing the technical solution of this application, and may also store an operating system and other critical business functions. Specifically, the program may include program code, which includes computer operation instructions. More specifically, the memory 300 may include read-only memory (ROM), other types of static storage devices capable of storing static information and instructions, random access memory (RAM), other types of dynamic storage devices capable of storing information and instructions, disk storage, flash memory, etc.

[0138] Input device 330 may include a device for receiving user input data and information, such as a keyboard, mouse, camera, scanner, light pen, voice input device, touch screen, pedometer, or gravity sensor.

[0139] Output device 340 may include devices that allow information to be output to a user, such as a display screen, printer, speaker, etc.

[0140] The communication interface 320 may include a device that uses any transceiver to communicate with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Network (WLAN), etc.

[0141] The processor 310 executes the program stored in the memory 300 and calls other devices, which can be used to implement any of the steps of the multi-protocol collaborative signing method provided in the above embodiments of this application.

[0142] Those skilled in the art will understand that Figure 4 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the electronic device to which the present application is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0143] This application also proposes a chip, which includes a processor and a data interface. The processor reads and runs a program stored in a memory through the data interface to execute the multi-protocol collaborative signing method described in any of the above embodiments. For details of the processing and its beneficial effects, please refer to the above embodiments of the multi-protocol collaborative signing method.

[0144] In addition to the methods and devices described above, embodiments of this application propose a computer program product comprising computer program instructions that, when executed by a processor, cause the processor to perform the steps of the multi-protocol cooperative signing method according to various embodiments of this application as described in the "Exemplary Methods" section of this specification.

[0145] The computer program product can be written in any combination of one or more programming languages ​​to perform the operations of the embodiments of this application. The programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0146] Furthermore, embodiments of this application also propose a storage medium storing a computer program, which is executed by a processor in the steps of the multi-protocol collaborative signing method according to various embodiments of this application described in the "Exemplary Methods" section above.

[0147] The basic principles of the present invention have been described above with reference to specific embodiments. However, it should be noted that the advantages, benefits, and effects mentioned in the present invention are merely examples and not limitations, and should not be considered as essential features of each embodiment of the present invention. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the present invention to the necessity of employing the aforementioned specific details.

[0148] The block diagrams of devices, apparatuses, devices, and systems involved in this invention are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to,” and are used interchangeably with them. The terms “or” and “and” as used herein refer to the terms “and / or,” and are used interchangeably with them unless the context clearly indicates otherwise. The term “such as” as used herein refers to the phrase “such as but not limited to,” and is used interchangeably with it.

[0149] It should also be noted that in the apparatus, device, and method of the present invention, the components or steps can be disassembled and / or recombined. These disassemblies and / or recombinations should be considered as equivalent solutions of the present invention.

[0150] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use the invention. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects without departing from the scope of the invention. Therefore, the invention is not intended to be limited to the aspects shown herein, but rather to be carried out within the widest scope consistent with the principles and novel features disclosed herein.

[0151] It should be understood that the qualifying terms "first", "second", "third", "fourth", "fifth" and "sixth" used in the description of the embodiments of the present invention are only used to more clearly illustrate the technical solutions and are not intended to limit the scope of protection of the present invention.

[0152] The above description has been given for purposes of illustration and description. Furthermore, this description is not intended to limit the embodiments of the invention to the forms disclosed herein. Although numerous exemplary aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations therein.

Claims

1. A multi-protocol collaborative signing method, characterized in that, The method includes: Obtain multiple related protocols, which are associated with each other; Generate signing information based on the multiple related protocols, and send the signing information to the client; After confirming that the customer has completed the signing of the aforementioned multiple related agreements, control the signing process to the supplier.

2. The multi-protocol collaborative signing method according to claim 1, characterized in that, The multiple related agreements include a target discount agreement and multiple target product agreements. The target discount agreement includes discount information of the target products corresponding to the multiple target product agreements. The target product agreements include other information of the target products corresponding to them. The target products are products to be signed by the customer.

3. The multi-protocol collaborative signing method according to claim 2, characterized in that, Prior to acquiring multiple related protocols, the method further includes: Associate different protocol templates with business process codes to establish the relationship between the different protocol templates; The acquisition of multiple related protocols includes: Based on the relationship between different protocol templates and the customer's required products, multiple target protocol templates are obtained. The multiple target protocol templates are all protocol templates associated with the protocol template of the required products, including the discount protocol template and the protocol template of the target products. Based on the multiple target protocol templates, the multiple related protocols are generated, and the multiple target protocol templates correspond one-to-one with the multiple related protocols.

4. The multi-protocol collaborative signing method according to claim 1, characterized in that, After entering the supplier-side contract signing process, the method further includes: If it is detected that both the client and the supplier have completed the signing of the multiple related agreements, the signing of the multiple related agreements shall be controlled to take effect.

5. The multi-protocol collaborative signing method according to claim 1, characterized in that, The method further includes: When it is detected that both the client and the supplier have completed the signing of the multiple related agreements, a first input is received, which is used to trigger the signing to take effect. In response to the first input, control the signing and activation of the multiple related protocols.

6. The multi-protocol collaborative signing method according to any one of claims 1 to 5, characterized in that, During the signing process of the multiple related agreements, the method further includes: Record the status of each node in the signing process of the multiple related agreements, where the nodes in the signing process include agreement generation, customer signing, and supplier signing; Based on the status of each node in the signing process of the multiple related protocols, determine whether the signing process is abnormal; If the signing process is abnormal, an error notification message will be output, which includes the reason for the error.

7. The multi-protocol collaborative signing method according to claim 6, characterized in that, The method further includes: Receive a second input, which is used to trigger the signing process on the supplier's side; In response to the second input, it is determined whether the client has completed the signing of the plurality of related protocols; Once it is determined that the client has completed the signing of the multiple related agreements, the signing process on the supplier's side will commence. If it is determined that the client has not completed the signing of the multiple related agreements, a reminder message is output, which is used to remind the client of the reason why the signing process cannot be entered into the supplier's end.

8. An electronic device, characterized in that, Including memory and processor; The memory is connected to the processor and is used to store programs; The processor is used to implement the multi-protocol collaborative signing method as described in any one of claims 1 to 7 by running the program in the memory.

9. A storage medium, characterized in that, The storage medium stores a computer program, which, when executed by a processor, implements the multi-protocol collaborative signing method as described in any one of claims 1 to 7.

10. A computer program product, characterized in that, The computer program product includes computer program instructions that, when executed by a processor, cause the processor to perform the multi-protocol collaborative signing method as described in any one of claims 1 to 7.

Images