Protocol generation method and device, electronic equipment and storage medium

Abstract

The invention relates to a protocol generation method and device, electronic equipment and a storage medium, and the method comprises the steps: receiving a protocol generation request of a target account for a target product of a target product provider, and obtaining target dynamic protocol content corresponding to the target product, based on a target product identifier, a target product provider identifier and a target account identifier included in the protocol generation request, obtaining target protocol information from at least one piece of protocol information included in a preset cache, based on a target protocol template identifier in the target protocol information, obtaining a target protocol template, and based on target dynamic protocol content, obtaining a target dynamic protocol content; the preset field corresponding to the target dynamic protocol content in the target protocol template is updated, a target protocol is obtained and sent to the terminal to be displayed, personalized configuration for different payment products can be provided, the requirement for dynamic replacement is met, the adaptability and generation efficiency of the protocol are improved, and the user experience is improved. And the pertinence and the standardization of business development are improved.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a protocol generation method, device, electronic device and storage medium. Background Art

[0002] With the widespread use of mobile payment transaction technology, users need to check the relevant agreements before signing or paying at the cashier. Therefore, how to meet the customized requirements of different payment products for agreements has become the focus of ensuring the effective development of related businesses.

[0003] In the related art, when configuring protocols for different payment products, general protocols are often relied upon. However, in the related art, general protocols cannot provide personalized configurations for specific payment products, resulting in the inability to accurately adapt to different payment products, and static protocol templates are difficult to meet the needs of dynamic replacement. The customization and generation efficiency of the protocol are low, which in turn leads to low pertinence and standardization of business development. Summary of the invention

[0004] The present disclosure provides a protocol generation method, device, electronic device and storage medium to at least solve the problems in the related art that it is impossible to provide personalized configurations for different payment products, static protocol templates are difficult to meet dynamic replacement, the customization and generation efficiency of the protocol are low, and the business development is less targeted and standardized.

[0005] According to a first aspect of an embodiment of the present disclosure, a protocol generation method is provided, including:

[0006] Receive a target account's request for generating a protocol for a target product provided by a target product provider, and obtain a target dynamic protocol content corresponding to the target product; the protocol generation request includes a target product identifier corresponding to the target product, a target product provider identifier corresponding to the target product provider, and a target account identifier corresponding to the target account;

[0007] Based on the target product identifier, the target product provider identifier and the target account identifier, target protocol information is obtained from a preset cache; the preset cache includes at least one protocol information; each protocol information in the at least one protocol information is protocol information of a corresponding account for a corresponding product of a corresponding product provider; each protocol information in the at least one protocol information is stored based on a corresponding product identifier, a corresponding product provider identifier and a corresponding account identifier; each protocol information in the at least one protocol information includes a protocol template identifier of a corresponding protocol template;

[0008] Based on the target protocol template identifier in the target protocol information, a target protocol template is acquired; the target protocol template includes a preset field corresponding to the target static protocol content and the target dynamic protocol content corresponding to the target product of the target account under the target product provider, and the preset field is a replaceable field;

[0009] Based on the target dynamic protocol content, the target protocol template is updated to obtain a target protocol;

[0010] The target protocol is sent to a terminal, so that the terminal displays the target protocol.

[0011] In an optional embodiment, the method further includes:

[0012] In response to a protocol template creation instruction, acquiring the target static protocol content and the preset field;

[0013] Creating the target protocol template based on the target static protocol content and the preset fields;

[0014] In response to the protocol configuration instruction for the target protocol template, acquiring the target product provider identifier and the target protocol template identifier;

[0015] Based on the target product provider identifier and the target protocol template identifier, establishing a first association relationship between the target protocol template identifier and the target product provider identifier;

[0016] In response to the product configuration instruction for the target agreement template, acquiring the target product identifier and the target account identifier;

[0017] Based on the target protocol template identifier, the target product identifier, the target account identifier and the first association relationship, a second association relationship is established between the target protocol template identifier, the target product provider identifier, the target product identifier and the target account identifier.

[0018] In an optional embodiment, the method further includes:

[0019] Receiving a protocol cache request for the target product of the target account corresponding to the target product provider, and acquiring the target product identifier, the target product provider identifier, and the target account identifier;

[0020] Determine a target agreement template identifier based on the second association relationship, the target product identifier, the target product provider identifier, and the target account identifier;

[0021] Based on the target product identifier, the target product provider identifier and the target account identifier, the target protocol template identifier is stored in the preset cache.

[0022] In an optional embodiment, when the target protocol template identifier includes template identifiers corresponding to multiple protocol templates, the method further includes:

[0023] Receiving an agreement update request for the target product from the target product provider corresponding to the target account, and acquiring basic information corresponding to each of the multiple agreement templates; the basic information includes template expiration information and template version information;

[0024] Based on the template expiration information corresponding to each of the multiple agreement templates and the template version information corresponding to each of the multiple agreement templates, determining, from the multiple template identifiers corresponding to each of the multiple agreement templates, the agreement template identifier corresponding to the latest agreement template corresponding to the target product of the target account under the target product provider;

[0025] The storing the target protocol template identifier into the preset cache based on the target product identifier, the target product provider identifier and the target account identifier includes:

[0026] Based on the target product identifier, the target product provider identifier and the target account identifier, the protocol template identifier corresponding to the latest protocol template is stored in the preset cache.

[0027] In an optional embodiment, the preset cache also includes preset protocol information. When the target product provider identifier is a preset product provider identifier, the acquiring the target protocol information from the preset cache based on the target product identifier, the target product provider identifier, and the target account identifier includes:

[0028] Obtaining the preset protocol information in the preset cache;

[0029] Based on the preset protocol template identifier in the preset protocol information, a preset protocol template is acquired, and the preset protocol template is used as the target protocol template.

[0030] In an optional embodiment, when the target protocol template is the target static protocol content, the target protocol information further includes a target protocol link, and the method further includes:

[0031] Acquire the target protocol link from the target protocol information;

[0032] The target protocol link is sent to the terminal, so that the terminal acquires and displays the target static protocol content based on the target protocol link.

[0033] In an optional embodiment, the method further includes:

[0034] In response to the authorization instruction of the target account for the target protocol, a target authorization result is obtained; the target authorization result is used to indicate the authorization operation of the target account for the target protocol;

[0035] The target authorization result is saved in the target authorization record corresponding to the target protocol.

[0036] According to a second aspect of an embodiment of the present disclosure, a protocol generation device is provided, including:

[0037] A target dynamic protocol content acquisition module is used to receive a protocol generation request from a target account for a target product of a target product provider, and acquire the target dynamic protocol content corresponding to the target product; the protocol generation request includes a target product identifier corresponding to the target product, a target product provider identifier corresponding to the target product provider, and a target account identifier corresponding to the target account;

[0038] A target protocol information acquisition module, configured to acquire target protocol information from a preset cache based on the target product identifier, the target product provider identifier, and the target account identifier; the preset cache includes at least one protocol information; each protocol information in the at least one protocol information is protocol information of a corresponding account for a corresponding product of a corresponding product provider; each protocol information in the at least one protocol information is stored based on a corresponding product identifier, a corresponding product provider identifier, and a corresponding account identifier; each protocol information in the at least one protocol information includes a protocol template identifier of a corresponding protocol template;

[0039] A target protocol template acquisition module, configured to acquire a target protocol template based on a target protocol template identifier in the target protocol information; the target protocol template includes a preset field corresponding to a target static protocol content and a target dynamic protocol content corresponding to the target product of the target account under the target product provider, wherein the preset field is a replaceable field;

[0040] A target protocol acquisition module, used to update the target protocol template based on the target dynamic protocol content to obtain the target protocol;

[0041] The target protocol sending module is used to send the target protocol to the terminal so that the terminal displays the target protocol.

[0042] In an optional embodiment, the device further comprises:

[0043] An acquisition module, configured to acquire the target static protocol content and the preset field in response to a protocol template creation instruction;

[0044] A target protocol template creation module, used to create the target protocol template based on the target static protocol content and the preset field;

[0045] A first identification acquisition module, configured to acquire the target product provider identification and the target protocol template identification in response to a protocol configuration instruction for the target protocol template;

[0046] A first association relationship establishing module, configured to establish a first association relationship between the target protocol template identifier and the target product provider identifier based on the target product provider identifier and the target protocol template identifier;

[0047] A second identification acquisition module, configured to acquire the target product identification and the target account identification in response to a product configuration instruction for the target protocol template;

[0048] A second association relationship establishing module is used to establish a second association relationship between the target protocol template identifier, the target product identifier, the target account identifier and the first association relationship.

[0049] In an optional embodiment, the device further comprises:

[0050] A third identification acquisition module is used to receive a protocol cache request for the target product of the target account corresponding to the target product provider, and obtain the target product identification, the target product provider identification and the target account identification;

[0051] a target protocol template identifier determining module, configured to determine a target protocol template identifier based on the second association relationship, the target product identifier, the target product provider identifier, and the target account identifier;

[0052] The target protocol template identifier storage module is used to store the target protocol template identifier in the preset cache based on the target product identifier, the target product provider identifier and the target account identifier.

[0053] In an optional embodiment, when the target protocol template identifier includes template identifiers corresponding to multiple protocol templates, the device further includes:

[0054] A basic information acquisition module, configured to receive an agreement update request for the target product from the target product provider corresponding to the target account, and acquire basic information corresponding to each of the multiple agreement templates; the basic information includes template expiration information and template version information;

[0055] an agreement template identification determination module, configured to determine, from the multiple template identifications corresponding to the multiple agreement templates, the agreement template identification corresponding to the latest agreement template corresponding to the target product of the target account under the target product provider, based on the template expiration information corresponding to the multiple agreement templates and the template version information corresponding to the multiple agreement templates;

[0056] The target protocol template identification storage module includes:

[0057] The target protocol template identifier storage unit is used to store the protocol template identifier corresponding to the latest protocol template into the preset cache based on the target product identifier, the target product provider identifier and the target account identifier.

[0058] In an optional embodiment, the preset cache further includes preset protocol information. When the target product provider identifier is a preset product provider identifier, the target protocol information acquisition module includes:

[0059] A preset protocol information acquisition unit, used to acquire the preset protocol information in the preset cache;

[0060] The target protocol template determining unit is used to obtain the preset protocol template based on the preset protocol template identifier in the preset protocol information, and use the preset protocol template as the target protocol template.

[0061] In an optional embodiment, when the target protocol template is the target static protocol content, the target protocol information further includes a target protocol link, and the device further includes:

[0062] A target protocol link acquisition module, used to acquire the target protocol link from the target protocol information;

[0063] The target protocol link sending module is used to send the target protocol link to the terminal, so that the terminal obtains and displays the target static protocol content based on the target protocol link.

[0064] In an optional embodiment, the device further comprises:

[0065] A target authorization result acquisition module, used to obtain a target authorization result in response to the authorization instruction of the target account for the target protocol; the target authorization result is used to indicate the authorization operation of the target account for the target protocol;

[0066] The target authorization result saving module is used to save the target authorization result into the target authorization record corresponding to the target protocol.

[0067] According to a third aspect of an embodiment of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement a method as described in any one of the above-mentioned first aspects.

[0068] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided. When instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute any method described in the first aspect of the embodiment of the present disclosure.

[0069] The technical solution provided by the embodiments of the present disclosure brings at least the following beneficial effects:

[0070] A protocol generation request is received from a target account for a target product of a target product provider, and a target dynamic protocol content corresponding to the target product is obtained. Based on the target product identifier corresponding to the target product, the target product provider identifier corresponding to the target product provider, and the target account identifier corresponding to the target account included in the protocol generation request, target protocol information is obtained from at least one protocol information included in a preset cache, which is protocol information of the corresponding account for the corresponding product of the corresponding product provider, wherein each protocol information in the at least one protocol information is stored based on the corresponding product identifier, the corresponding product provider identifier, and the corresponding account identifier, including a protocol template identifier of the corresponding protocol template; based on the target protocol template identifier in the target protocol information, a target protocol template is obtained; based on the target dynamic protocol content, a replaceable field corresponding to the target dynamic protocol content in the target protocol template is updated to obtain a target protocol; the target protocol is sent to a terminal so that the terminal displays the target protocol; personalized configurations for different payment products can be provided to meet the needs of dynamic replacement, improve the adaptability and generation efficiency of the protocol, and thereby improve the pertinence and standardization of business development.

[0071] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0072] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.

[0073] Figure 1 is a schematic diagram of an application environment according to an exemplary embodiment;

[0074] Figure 2 is a flow chart of a protocol generation method according to an exemplary embodiment;

[0075] Figure 3 is a schematic diagram of a cache structure of protocol information according to an exemplary embodiment;

[0076] Figure 4a is a schematic diagram of a target protocol template according to an exemplary embodiment;

[0077] Figure 4b is a schematic diagram of a target protocol according to an exemplary embodiment;

[0078] Figure 5 is a flowchart showing a protocol template configuration according to an exemplary embodiment;

[0079] Figure 6a is a schematic diagram of a first association relationship configuration page according to an exemplary embodiment;

[0080] Figure 6b is a schematic diagram of a second association relationship configuration page according to an exemplary embodiment;

[0081] Figure 7 is a flow chart of another protocol generation method according to an exemplary embodiment;

[0082] Figure 8 is a schematic diagram showing a target authorization record according to an exemplary embodiment;

[0083] Fig. 9 is a block diagram of a protocol generation device according to an exemplary embodiment;

[0084] Fig.10 It is a block diagram of an electronic device for protocol generation according to an exemplary embodiment. DETAILED DESCRIPTION

[0085] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings.

[0086] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar different contents, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the attached claims.

[0087] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for display, data for analysis, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties.

[0088] See also Figure 1 , Figure 1 is a schematic diagram of an application environment according to an exemplary embodiment. Figure 1 As shown, the application environment may include a terminal 100 and a server 200 .

[0089] In an optional embodiment, the terminal 100 can be used to provide services such as protocol template configuration, product association configuration, and protocol template editing. Specifically, the terminal 100 may include but is not limited to electronic devices such as smart phones, desktop computers, tablet computers, laptops, smart speakers, digital assistants, augmented reality (AR) / virtual reality (VR) devices, and smart wearable devices, and may also be software running on the above electronic devices, such as applications. Optionally, the operating system running on the electronic device may include but is not limited to Android, IOS, Linux, Windows, etc.

[0090] In an optional embodiment, the server 200 can provide background services for the terminal 100 and generate a target protocol. Optionally, the server 200 can obtain the target dynamic protocol content corresponding to the target product. Accordingly, the target protocol template can be obtained based on the target product identifier, target product provider identifier and target account identifier included in the protocol generation request, and then the target protocol template is updated based on the target dynamic protocol content to obtain the target protocol. Specifically, the server 200 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms.

[0091] In addition, it should be noted that Figure 1 What is shown is only one application environment provided by the present disclosure. In actual application, other application environments may also be included.

[0092] In the embodiments of this specification, the terminal 100 and the server 200 may be directly or indirectly connected via wired or wireless communication, which is not limited in this disclosure.

[0093] Figure 2 is a flowchart of a protocol generation method according to an exemplary embodiment. Figure 2 As shown, the protocol generation method is used in a server and includes the following steps.

[0094] In step S201, a request for generating an agreement for a target product from a target product provider is received from a target account, and target dynamic agreement content corresponding to the target product is obtained;

[0095] In a specific embodiment, the target account may be identification information used to identify the identity of the user of the target product. For example, the user of the target product may be a business entity or an individual, and accordingly, the target account may be a merchant number or a bank card number.

[0096] In a specific embodiment, the target product provider may be an institution that provides the target product, and the target product may be a specific product or service provided by the target product provider for achieving different business objectives. Specifically, taking the target product provider as a bank or other financial institution as an example, the target product may be a quick payment product, an authentication product, a credit installment product or other financial service product.

[0097] In a specific embodiment, the protocol generation request may be a request for generating a protocol, and specifically may include a target product identifier corresponding to the target product, a target product provider identifier corresponding to the target product provider, and a target account identifier corresponding to the target account. Specifically, the target product identifier may be information used to identify the target product, such as a product code, and the target product provider identifier may be information used to identify the target product provider, such as a bank code.

[0098] In a specific embodiment, the target dynamic agreement content may be the business parameters corresponding to the target product, which are used to describe the specific indicators and settings of the various characteristics of the target product and related business rules. Taking the target product as a credit installment product as an example, the target dynamic agreement content may be the number of installments, annualized interest rate, installment amount, etc.

[0099] In step S203, based on the target product identifier, the target product provider identifier and the target account identifier, the target protocol information is obtained from the preset cache;

[0100] In a specific embodiment, the preset cache may be a storage area pre-set for storing protocol information. Specifically, the preset cache may include at least one piece of protocol information. Each piece of protocol information in the at least one piece of protocol information may be protocol information of a corresponding account for a corresponding product of a corresponding product provider. Accordingly, each piece of protocol information in the at least one piece of protocol information may be stored based on a corresponding product identifier, a corresponding product provider identifier and a corresponding account identifier. Each piece of protocol information in the at least one piece of protocol information may include a protocol template identifier of a corresponding protocol template.

[0101] In a specific embodiment, the target protocol information may be protocol information of the target product corresponding to the target account under the target product provider.

[0102] In a specific embodiment, Figure 3 As shown, Figure 3: is a schematic diagram of a cache structure of protocol information according to an exemplary embodiment, wherein the cache type used by each protocol information in the preset cache is Redis cache. Exemplarily, Redis cache adopts a key-value storage method, and identifies the corresponding data value (such as hash<protocol type_card type, protocol information>) through a specific key (such as AGREEMENT_RESULT_{productCode}_00000000, etc.). Specifically, "{productCode}" is a placeholder, which will be replaced by the corresponding specific product name in actual application to identify different products, and "00000000" indicates a general situation not related to the bank or an identification for non-bank business, "protocol type" can refer to different types of protocols, such as payment agreement, cooperation agreement, etc., "card type" can refer to various bank card types such as debit card, credit card, etc., and optionally, the key (AGREMENT_RESULT_{productCode}_00000000, etc.) EMENT_RESULT_{productCode}_{bankCode}) is used to identify data values ​​({"mchList":["mchId1","mchId2"],"agreementList":[{agreement 1 information},{agreement 2 information}]}). Specifically, "{productCode}" represents the product code, which is used to clarify which product the agreement information is related to. "{bankCode}" is a placeholder for the bank code, which will be replaced by the corresponding specific bank name in actual use. The agreement information includes the agreement template id (used for dynamic template query), agreement type, agreement template link (static template has value), agreement name (used for cash register display), version number, bank code, card type, merchant number (merchant customized agreement has value), etc.

[0103] In a specific embodiment, Figure 3 As shown, when receiving a protocol generation request for a target product from a target account and a target product provider, the protocol generation request includes a target product identifier (product code) corresponding to the target product, a target product provider identifier (bank code) corresponding to the target product provider, and a target account identifier (merchant number) corresponding to the target account. The corresponding cache key is first queried based on the target product identifier and the target product provider identifier, and then compared with the target account identifier in the protocol information corresponding to the cache key to determine the target protocol information. For the case where the protocol information does not have a target account identifier (non-merchant customized protocol), the target protocol information can be determined only based on the target product identifier and the target product provider identifier.

[0104] In the above embodiment, through the cache key, the required protocol information cache data can be quickly located according to key identifiers such as product code and bank code, without traversing and searching in a large amount of data, which greatly improves the query efficiency. The cache key contains the product code and bank code respectively, so that the protocol information can be cached and managed separately for different products and different banks. Inside the hash structure, the protocol information is stored with "protocol type_card type" as the key, so that highly targeted protocol information can be quickly obtained, and refined data management is achieved. The protocol information includes the detailed attributes of the merchants involved and the protocol itself, which ensures the integrity of the data and avoids the situation where some data is missing or inconsistent due to decentralized data storage.

[0105] In an optional embodiment, the preset cache also includes preset protocol information. When the target product provider identifier is the preset product provider identifier, the above-mentioned obtaining the target protocol information from the preset cache based on the target product identifier, the target product provider identifier and the target account identifier includes:

[0106] Get the preset protocol information in the preset cache;

[0107] Based on the preset protocol template identifier in the preset protocol information, the preset protocol template is acquired, and the preset protocol template is used as the target protocol template.

[0108] In a specific embodiment, the preset protocol information may be protocol information corresponding to the preset protocol, and the preset product provider identifier may be information used to identify the preset product provider. Taking the product provider as a bank as an example, the preset protocol may be a general situation unrelated to the bank or a preset protocol for non-banking services, such as a privacy-related protocol. The preset product provider identifier (bank code) may be 00000000.

[0109] In a specific embodiment, the preset protocol template may be a protocol template corresponding to a preset protocol.

[0110] In the above embodiment, preset protocol information is stored in the preset cache. When no bank is specified or the protocol information corresponding to a bank is not separately configured, the general protocol information can be directly obtained, which can ensure that the business is carried out according to a relatively unified standard and process, thereby maintaining the consistency of business logic in different scenarios.

[0111] In step S205, based on the target protocol template identifier in the target protocol information, the target protocol template is obtained;

[0112] In a specific embodiment, the target agreement template identifier may be information used to identify the target agreement template, specifically, such as an agreement template ID or an agreement template link. The target agreement template may be an agreement template corresponding to the target agreement template identifier. Specifically, the target agreement template includes preset fields corresponding to the target static agreement content and the target dynamic agreement content corresponding to the target product of the target account under the target product provider. The preset fields may be replaceable fields.

[0113] In a specific embodiment, the target static agreement content may be the static agreement content corresponding to the target product of the target account under the target product provider. Specifically, the target static agreement content may be the basic and general part of the agreement content corresponding to the target product of the target account under the target product provider, which is relatively fixed and does not change easily with the normal situation during the business operation process. The target dynamic agreement content may be the dynamic agreement content corresponding to the target product of the target account under the target product provider. Specifically, the target dynamic agreement content may be the part of the agreement content corresponding to the target product of the target account under the target product provider that may change with factors such as changes in the external environment during the business operation process, the specific behavior or demand changes of the target account, etc.

[0114] In a specific embodiment, Figure 4a As shown, Figure 4a is a schematic diagram of a target protocol template according to an exemplary embodiment. The preset field may be ${stageNum!} or ${annualRate!}, etc. The target static protocol content may be protocol content other than ${stageNum!} and ${annualRate!}.

[0115] In an optional embodiment, the above method may further include: a step of configuring a protocol template, specifically, Figure 5 As shown, the following steps may be included:

[0116] In step S501, in response to a protocol template creation instruction, target static protocol content and preset fields are acquired;

[0117] In a specific embodiment, the protocol template creation instruction may be an instruction that triggers the creation of a target protocol template.

[0118] In step S503, a target protocol template is created based on the target static protocol content and preset fields;

[0119] In a specific embodiment, Figure 4a As shown, the target static protocol content and preset fields in the target protocol template can be edited through a rich text editor.

[0120] In step S505, in response to the protocol configuration instruction for the target protocol template, the target product provider identifier and the target protocol template identifier are obtained;

[0121] In a specific embodiment, the protocol configuration instruction may be an instruction for configuring a protocol template identifier, such as Figure 6a As shown, the bank name of the target product provider may be Xiao A Bank, and the target agreement template identifier may be the template number (24080822265155XXXX).

[0122] In step S507, based on the target product provider identifier and the target protocol template identifier, a first association relationship is established between the target protocol template identifier and the target product provider identifier;

[0123] In a specific embodiment, the first association relationship can be an association relationship between the target agreement template and the target product provider. Specifically, the first association relationship can be established by identifying the target agreement template (template number) and the target product provider identifier (bank code), thereby associating the target agreement template with Bank A.

[0124] In step S509, in response to the product configuration instruction for the target agreement template, a target product identifier and a target account identifier are obtained;

[0125] In a specific embodiment, the product configuration instruction may be an instruction for performing product association configuration, such as Figure 6b As shown, the target product identifier can be the product code (online payment | quick payment), and the target account identifier can be the merchant number (20200030900000XXXX).

[0126] In step S5011, based on the target protocol template identifier, the target product identifier, the target account identifier and the first association relationship, a second association relationship is established between the target protocol template identifier, the target product provider identifier, the target product identifier and the target account identifier. Specifically, Figure 6b As shown, the target protocol template identifier can be the template number (24080822265155XXXX), the target product provider identifier can be the bank name (Small A Bank), the target product identifier can be the product name (Online Payment | Quick Payment), and the target account identifier can be the merchant number (20200030900000XXXX).

[0127] In a specific embodiment, the second association relationship can be an association relationship between the target agreement template, the target product provider, the target product and the target account, which is established based on the first association relationship. Specifically, on the basis of establishing the first association relationship between the above-mentioned target agreement template identifier (template number) and the target product provider identifier (bank code), a second association relationship can be established between the target product provider identifier (bank name), the target product identifier (product name) and the target agreement template identifier (template number) and the target product provider identifier (bank code).

[0128] In the above embodiment, the target agreement template is obtained by creating preset fields corresponding to the target static agreement content and the target dynamic agreement content, and a first association relationship is established between the target agreement template identifier and the target product provider identifier through the configuration page. Then, based on the first association relationship, a second association relationship is established between the target agreement template identifier, the target product provider identifier, the target product identifier and the target account identifier, so as to achieve comprehensive and accurate positioning from the merchant level to the product, product provider and agreement. When it is necessary to find a certain agreement template, the relevant agreement template can be quickly located based on the association relationship.

[0129] In an optional embodiment, the above method may further include:

[0130] Receive a protocol cache request for a target product of a target product provider corresponding to a target account, and obtain a target product identifier, a target product provider identifier, and a target account identifier;

[0131] Determine a target protocol template identifier based on the second association relationship, the target product identifier, the target product provider identifier, and the target account identifier;

[0132] Based on the target product identifier, the target product provider identifier and the target account identifier, the target protocol template identifier is stored in a preset cache.

[0133] In a specific embodiment, the protocol cache request may be a request to cache a target protocol template.

[0134] In a specific embodiment, taking the target product as online payment|fast payment, the target product provider as Xiao A Bank, and the merchant number of the target account identifier as 20200030900000XXXX as an example, based on Figure 6b The second association relationship shown can determine that the template number of the target protocol template identifier is 24080822265155XXXX.

[0135] In a specific embodiment, based on the above-mentioned target product identifier (online payment | quick payment), the above-mentioned target product provider identifier (Small A Bank) and the above-mentioned target account identifier (20200030900000XXXX), the target protocol template identifier (24080822265155XXXX) can be stored in the corresponding protocol information in the preset cache.

[0136] In the above embodiment, based on the second association relationship, the target product identifier, the target product provider identifier and the target account identifier, the target protocol template identifier is determined and stored in the protocol information corresponding to the preset cache. When the protocol template needs to be called subsequently, there is no need to conduct a large-scale search and investigation among all protocol templates. It can be directly obtained from the preset cache based on the determined target protocol template identifier and the second association relationship, which greatly shortens the time for obtaining the protocol template and improves the response speed of business processing. Moreover, all target protocol template identifiers are stored in the preset cache based on the second association relationship, which can ensure the consistency and accuracy of the protocol.

[0137] In an optional embodiment, when the target protocol template identifier includes template identifiers corresponding to multiple protocol templates, the above method may further include:

[0138] Receive an agreement update request for a target product of a target product provider corresponding to a target account, and obtain basic information corresponding to each of multiple agreement templates;

[0139] Based on the template validity information corresponding to each of the multiple agreement templates and the template version information corresponding to each of the multiple agreement templates, determine, from the multiple template identifiers corresponding to each of the multiple agreement templates, the agreement template identifier corresponding to the latest agreement template corresponding to the target product under the target product provider of the target account;

[0140] The above-mentioned storing the target protocol template identifier in the preset cache based on the target product identifier, the target product provider identifier and the target account identifier includes:

[0141] Based on the target product identifier, the target product provider identifier and the target account identifier, the protocol template identifier corresponding to the latest protocol template is stored in a preset cache.

[0142] In a specific embodiment, multiple protocol templates may be multiple versions of protocol templates corresponding to a target protocol template. Exemplarily, the current version numbers corresponding to the multiple protocol templates may be v1.0, v2.0, v3.0, etc. Specifically, multiple protocol templates correspond to the same protocol template identifier and correspond to different primary key IDs.

[0143] In a specific embodiment, the protocol update request may be an update request for a target protocol template. The basic information may include template validity information and template version information. Specifically, the template validity information may include the effective time and expiration time of the template, and the template version information may be the current version number mentioned above.

[0144] In a specific embodiment, the latest protocol template may be a protocol template with the latest current version number and within the validity period among the multiple protocol templates.

[0145] In a specific embodiment, based on the template validity information (effective date and expiration date) corresponding to each of the multiple agreement templates, at least one agreement template that is within the validity period can be determined, and then based on the template version information (current version number) corresponding to the above at least one agreement template, the agreement template identifier (template number) corresponding to the latest agreement template corresponding to the target product of the target account under the target product provider can be determined from the template identifier corresponding to each of the above at least one agreement template.

[0146] In a specific embodiment, based on the above-mentioned target product identifier (online payment | quick payment), the above-mentioned target product provider identifier (Small A Bank) and the above-mentioned target account identifier (20200030900000XXXX), the protocol template identifier corresponding to the latest protocol template of the target product under the target product provider and the corresponding primary key id can be stored in the corresponding protocol information in the preset cache.

[0147] In the above embodiment, based on the template timeliness information and template version information corresponding to each of the multiple protocol templates corresponding to the target protocol template, the protocol template identifier and the primary key id are determined and stored in the preset cache, which can ensure that the protocol template subsequently selected from the preset cache based on the target protocol template identifier is the latest and available, avoiding problems such as the agreement terms not being in line with the actual situation and business operation risks caused by the use of expired protocol templates. When a new protocol template is updated or the old template becomes invalid, the protocol template identifier and the primary key id in the preset cache are updated, which can ensure that the information in the cache always matches the latest business needs and protocol template status, thereby ensuring the timeliness and accuracy of the protocol.

[0148] In an optional embodiment, when the target protocol template is a target static protocol content, the target protocol information may further include a target protocol link, and the method may further include:

[0149] Get the target protocol link from the target protocol information;

[0150] The target protocol link is sent to the terminal, so that the terminal obtains and displays the target static protocol content based on the target protocol link.

[0151] In a specific embodiment, the target protocol link may be information used to identify the target static protocol content. Specifically, the target protocol link may be a link used to indicate the storage location of the target static protocol content in OSS. Specifically, the format and composition of the target protocol link may be https: / / oss-mpay-static.XXX.com (oss domain name) / tps (bucket name, storage space name for storing objects) / service-agreement-user-230424.html (path / target static protocol content file name).

[0152] In a specific embodiment, the target protocol link obtained from the target protocol information is sent to the terminal, and the terminal can directly obtain the corresponding target static protocol content through the target protocol link and display it on the terminal.

[0153] In the above embodiment, when the target protocol template is a static protocol, the target protocol link can be directly obtained from the target protocol information and sent to the terminal, so that the terminal obtains and displays the target protocol template based on the target protocol link, which can quickly obtain the protocol content, simplify the operation process, and greatly shorten the time to obtain the protocol.

[0154] In step S207, based on the target dynamic protocol content, the target protocol template is updated to obtain the target protocol;

[0155] In a specific embodiment, the target protocol may be a protocol corresponding to the target protocol template, such as Figure 4b As shown in the following example, by referencing the variable stageNum as ${stageNum!}, you can replace ${stageNum!} in the template with the actual value corresponding to stageNum, and get the following: Figure 4b Schematic diagram of the target protocol shown.

[0156] In step S209, the target protocol is sent to the terminal so that the terminal displays the target protocol.

[0157] In a specific embodiment, the following is sent to the terminal: Figure 4b The target protocol shown in the figure is displayed on the terminal.

[0158] In step S2011, in response to the authorization instruction of the target account for the target protocol, a target authorization result is obtained;

[0159] In a specific embodiment, the authorization instruction may be an instruction triggered by the target account to grant the target protocol authority, and the target authorization result may be used to indicate the authorization operation of the target account for the target protocol.

[0160] In step S2013, the target authorization result is saved in the target authorization record corresponding to the target protocol.

[0161] In a specific embodiment, the target authorization record may be a user authorization record for each account for the target protocol, such as Figure 8 As shown, it may include the authorization date (creation date) of each account, each account information (merchant name, merchant number, external user number, etc.), associated business primary key, etc.

[0162] In the above embodiment, the target authorization result of the target account for the target protocol is saved in the target authorization record, which can realize subsequent evidence and ensure the legality and compliance of the transaction. The target authorization record can serve as an important basis for risk assessment. By analyzing the authorization records, enterprises can discover potential risk points. At the same time, when security incidents occur (such as account theft, data leakage, etc.), the authorization records can help enterprises quickly determine the affected protocols and account scopes. By viewing the target authorization records, the security team can understand which accounts have access rights to which protocols, so as to take timely measures, such as revoking authorization, freezing accounts, etc., to reduce the losses caused by security incidents.

[0163] It can be seen from the technical solutions provided by the above embodiments of this specification that this specification receives a protocol generation request for a target product of a target product provider from a target account, obtains a target dynamic protocol content corresponding to the target product, and based on the target product identifier corresponding to the target product, the target product provider identifier corresponding to the target product provider and the target account identifier corresponding to the target account included in the protocol generation request, obtains the target protocol information from at least one protocol information of the corresponding account for the corresponding product of the corresponding product provider included in each protocol information included in the preset cache, wherein each protocol information in the at least one protocol information is stored based on the corresponding product identifier, the corresponding product provider identifier and the corresponding account identifier, including the protocol template identifier of the corresponding protocol template, obtains the target protocol template based on the target protocol template identifier in the target protocol information, updates the replaceable fields corresponding to the target dynamic protocol content in the target protocol template based on the target dynamic protocol content, obtains the target protocol, and sends the target protocol to the terminal so that the terminal displays the target protocol, which can provide personalized configurations for different payment products, meet the needs of dynamic replacement, improve the adaptability and generation efficiency of the protocol, and thus improve the pertinence and standardization of business development.

[0164] Fig. 9 is a block diagram of a protocol generation device according to an exemplary embodiment. Fig. 9 , the device comprises:

[0165] The target dynamic protocol content acquisition module 910 is used to receive a protocol generation request from a target account for a target product of a target product provider, and obtain the target dynamic protocol content corresponding to the target product; the protocol generation request includes a target product identifier corresponding to the target product, a target product provider identifier corresponding to the target product provider, and a target account identifier corresponding to the target account;

[0166] The target protocol information acquisition module 930 is used to acquire the target protocol information from the preset cache based on the target product identifier, the target product provider identifier and the target account identifier; the preset cache includes at least one protocol information; each protocol information in the at least one protocol information is the protocol information of the corresponding account for the corresponding product of the corresponding product provider; each protocol information in the at least one protocol information is stored based on the corresponding product identifier, the corresponding product provider identifier and the corresponding account identifier; each protocol information in the at least one protocol information includes the protocol template identifier of the corresponding protocol template;

[0167] The target agreement template acquisition module 950 is used to acquire the target agreement template based on the target agreement template identifier in the target agreement information; the target agreement template includes preset fields corresponding to the target static agreement content and the target dynamic agreement content of the target account under the target product provider, and the preset fields are replaceable fields;

[0168] A target protocol acquisition module 970 is used to update the target protocol template based on the target dynamic protocol content to obtain the target protocol;

[0169] The target protocol sending module 990 is used to send the target protocol to the terminal so that the terminal displays the target protocol.

[0170] In an optional embodiment, the above device further includes:

[0171] An acquisition module, used to acquire target static protocol content and preset fields in response to a protocol template creation instruction;

[0172] A target protocol template creation module, used to create a target protocol template based on the target static protocol content and preset fields;

[0173] A first identification acquisition module, configured to acquire a target product provider identification and a target protocol template identification in response to a protocol configuration instruction for a target protocol template;

[0174] A first association relationship establishing module, configured to establish a first association relationship between the target protocol template identifier and the target product provider identifier based on the target product provider identifier and the target protocol template identifier;

[0175] A second identification acquisition module, configured to acquire a target product identification and a target account identification in response to a product configuration instruction for a target protocol template;

[0176] The second association relationship establishment module is used to establish a second association relationship between the target protocol template identifier, the target product identifier, the target account identifier and the first association relationship.

[0177] In an optional embodiment, the above device further includes:

[0178] A third identification acquisition module is used to receive a protocol cache request for a target product of a target product provider corresponding to a target account, and obtain a target product identification, a target product provider identification, and a target account identification;

[0179] A target protocol template identifier determination module, configured to determine a target protocol template identifier based on the second association relationship, a target product identifier, a target product provider identifier, and a target account identifier;

[0180] The target protocol template identifier storage module is used to store the target protocol template identifier in a preset cache based on the target product identifier, the target product provider identifier and the target account identifier.

[0181] In an optional embodiment, when the target protocol template identifier includes template identifiers corresponding to multiple protocol templates, the apparatus further includes:

[0182] A basic information acquisition module is used to receive an agreement update request for a target product of a target product provider corresponding to a target account, and obtain basic information corresponding to each of a plurality of agreement templates; the basic information includes template validity information and template version information;

[0183] An agreement template identification determination module, used to determine, from the multiple template identifications corresponding to the multiple agreement templates, the agreement template identification corresponding to the latest agreement template corresponding to the target product of the target account under the target product provider, based on the template validity information corresponding to the multiple agreement templates and the template version information corresponding to the multiple agreement templates;

[0184] The target protocol template identification storage module includes:

[0185] The target protocol template identifier storage unit is used to store the protocol template identifier corresponding to the latest protocol template into a preset cache based on the target product identifier, the target product provider identifier and the target account identifier.

[0186] In an optional embodiment, the preset cache also includes preset protocol information. When the target product provider identifier is a preset product provider identifier, the target protocol information acquisition module 930 includes:

[0187] A preset protocol information acquisition unit, used to acquire the preset protocol information in the preset cache;

[0188] The target protocol template determining unit is used to obtain the preset protocol template based on the preset protocol template identifier in the preset protocol information, and use the preset protocol template as the target protocol template.

[0189] In an optional embodiment, when the target protocol template is the target static protocol content, the target protocol information further includes a target protocol link, and the above-mentioned apparatus further includes:

[0190] A target protocol link acquisition module, used to acquire a target protocol link from target protocol information;

[0191] The target protocol link sending module is used to send the target protocol link to the terminal, so that the terminal obtains and displays the target static protocol content based on the target protocol link.

[0192] In an optional embodiment, the above device further includes:

[0193] A target authorization result acquisition module is used to obtain a target authorization result in response to an authorization instruction of a target account for a target protocol; the target authorization result is used to indicate the authorization operation of the target account for the target protocol;

[0194] The target authorization result saving module is used to save the target authorization result to the target authorization record corresponding to the target protocol.

[0195] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0196] Fig.10 is a block diagram of an electronic device for protocol generation according to an exemplary embodiment. The electronic device may be a terminal, and its internal structure diagram may be as shown in FIG. Fig.10As shown. The electronic device includes a processor, a memory, a network interface, a display screen and an input device connected via a system bus. Among them, the processor of the electronic device is used to provide computing and control capabilities. The memory of the electronic device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the electronic device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a protocol generation method is implemented. The display screen of the electronic device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the electronic device can be a touch layer covering the display screen, or a key, trackball or touchpad provided on the housing of the electronic device, or an external keyboard, touchpad or mouse, etc.

[0197] Those skilled in the art will understand that Fig.10 The structure shown in the figure is merely a block diagram of a partial structure related to the scheme of the present disclosure, and does not constitute a limitation on the electronic device to which the scheme of the present disclosure is applied. The specific electronic device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0198] In an exemplary embodiment, an electronic device is also provided, including: a processor; and a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement the protocol generation method in the embodiment of the present disclosure.

[0199] In an exemplary embodiment, a computer-readable storage medium is also provided. When instructions in the storage medium are executed by a processor of an electronic device, the electronic device can execute the protocol generation method in the embodiment of the present disclosure.

[0200] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

[0201] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A protocol generation method, characterized in that: include: Receive a target account's request for generating a protocol for a target product from a target product provider, and obtain target dynamic protocol content corresponding to the target product; The protocol generation request includes a target product identifier corresponding to the target product, a target product provider identifier corresponding to the target product provider, and a target account identifier corresponding to the target account; Based on the target product identifier, the target product provider identifier and the target account identifier, obtaining target protocol information from a preset cache; The preset cache includes at least one piece of protocol information; Each of the at least one piece of agreement information is agreement information of a corresponding account for a corresponding product of a corresponding product provider; Each of the at least one piece of protocol information is stored based on a corresponding product identifier, a corresponding product provider identifier, and a corresponding account identifier; each of the at least one piece of protocol information includes a protocol template identifier of a corresponding protocol template; Based on the target protocol template identifier in the target protocol information, a target protocol template is acquired; the target protocol template includes a preset field corresponding to the target static protocol content and the target dynamic protocol content corresponding to the target product of the target account under the target product provider, and the preset field is a replaceable field; Based on the target dynamic protocol content, the target protocol template is updated to obtain a target protocol; The target protocol is sent to a terminal, so that the terminal displays the target protocol.

2. A protocol generation method according to claim 1, characterized in that: The method further comprises: In response to a protocol template creation instruction, acquiring the target static protocol content and the preset field; Creating the target protocol template based on the target static protocol content and the preset fields; In response to the protocol configuration instruction for the target protocol template, acquiring the target product provider identifier and the target protocol template identifier; Based on the target product provider identifier and the target protocol template identifier, establishing a first association relationship between the target protocol template identifier and the target product provider identifier; In response to the product configuration instruction for the target agreement template, acquiring the target product identifier and the target account identifier; Based on the target protocol template identifier, the target product identifier, the target account identifier and the first association relationship, a second association relationship is established between the target protocol template identifier, the target product provider identifier, the target product identifier and the target account identifier.

3. A protocol generation method according to claim 2, characterized in that: The method further comprises: Receiving a protocol cache request for the target product of the target account corresponding to the target product provider, and acquiring the target product identifier, the target product provider identifier, and the target account identifier; Determine a target agreement template identifier based on the second association relationship, the target product identifier, the target product provider identifier, and the target account identifier; Based on the target product identifier, the target product provider identifier and the target account identifier, the target protocol template identifier is stored in the preset cache.

4. A protocol generation method according to claim 3, characterized in that: In a case where the target protocol template identifier includes template identifiers corresponding to respective protocol templates, the method further includes: Receiving an agreement update request for the target product from the target product provider corresponding to the target account, and acquiring basic information corresponding to each of the multiple agreement templates; the basic information includes template expiration information and template version information; Based on the template expiration information corresponding to each of the multiple agreement templates and the template version information corresponding to each of the multiple agreement templates, determining, from the multiple template identifiers corresponding to each of the multiple agreement templates, the agreement template identifier corresponding to the latest agreement template corresponding to the target product of the target account under the target product provider; The storing the target protocol template identifier into the preset cache based on the target product identifier, the target product provider identifier and the target account identifier includes: Based on the target product identifier, the target product provider identifier and the target account identifier, the protocol template identifier corresponding to the latest protocol template is stored in the preset cache.

5. A protocol generation method according to claim 1, characterized in that: The preset cache also includes preset protocol information. When the target product provider identifier is a preset product provider identifier, obtaining the target protocol information from the preset cache based on the target product identifier, the target product provider identifier, and the target account identifier includes: Obtaining the preset protocol information in the preset cache; Based on the preset protocol template identifier in the preset protocol information, a preset protocol template is acquired, and the preset protocol template is used as the target protocol template.

6. A protocol generation method according to claim 1, characterized in that: In the case where the target protocol template is the target static protocol content, the target protocol information further includes a target protocol link, and the method further includes: Acquire the target protocol link from the target protocol information; The target protocol link is sent to the terminal, so that the terminal acquires and displays the target static protocol content based on the target protocol link.

7. A protocol generation method according to claim 1, characterized in that: The method further comprises: In response to the authorization instruction of the target account for the target protocol, a target authorization result is obtained; the target authorization result is used to indicate the authorization operation of the target account for the target protocol; The target authorization result is saved in the target authorization record corresponding to the target protocol.

8. A protocol generation device, characterized in that: include: A target dynamic protocol content acquisition module is used to receive a protocol generation request from a target account for a target product of a target product provider, and acquire the target dynamic protocol content corresponding to the target product; the protocol generation request includes a target product identifier corresponding to the target product, a target product provider identifier corresponding to the target product provider, and a target account identifier corresponding to the target account; A target protocol information acquisition module, configured to acquire target protocol information from a preset cache based on the target product identifier, the target product provider identifier, and the target account identifier; The preset cache includes at least one piece of protocol information; Each of the at least one piece of agreement information is agreement information of a corresponding account for a corresponding product of a corresponding product provider; Each of the at least one piece of protocol information is stored based on a corresponding product identifier, a corresponding product provider identifier, and a corresponding account identifier; each of the at least one piece of protocol information includes a protocol template identifier of a corresponding protocol template; A target protocol template acquisition module, configured to acquire a target protocol template based on a target protocol template identifier in the target protocol information; the target protocol template includes a preset field corresponding to a target static protocol content and a target dynamic protocol content corresponding to the target product of the target account under the target product provider, wherein the preset field is a replaceable field; A target protocol acquisition module, used to update the target protocol template based on the target dynamic protocol content to obtain the target protocol; The target protocol sending module is used to send the target protocol to the terminal so that the terminal displays the target protocol.

9. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the protocol generation method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: When the instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the protocol generation method as claimed in any one of claims 1 to 7.

Images