Method for matching protocol data service rules and related device

Abstract

Embodiments of the present application relate to a protocol data service rule matching method and related equipment thereof. The method comprises: obtaining target protocol data information, the target protocol data information comprising a target protocol data attribute and a target attribute value corresponding to the target protocol data attribute; based on a preset mapping relationship between a protocol data attribute and a preset rule code, finding a target rule code corresponding to the target protocol data attribute in a preset storage library according to the target protocol data attribute, and taking a target rule value from a corresponding target service rule according to the target rule code, the preset storage library being used to dynamically store the mapping relationship between the preset protocol data attribute and the preset rule code; determining whether the target protocol data information matches the target service rule according to the target attribute value and the target rule value; and if so, performing service binding on the target protocol data information and the target service rule. The present application can improve system flexibility and reduce system maintenance costs.

Description

Technical Field

[0001] This application relates to the field of financial technology, and more specifically, to a method for matching protocol data service rules and related equipment. Background Technology

[0002] In recent years, more and more companies have needed to sign agreements to cooperate and develop together. These agreements can take many forms, depending on the specific agreements between the companies. Each agreement generates corresponding agreement data. Companies then match service plans to this agreement data to facilitate their mutual development. For example, in the automotive industry, after a car transaction, corresponding insurance is generated, such as non-motor vehicle insurance policies. After a non-motor vehicle insurance policy is issued, a follow-up service is required. Currently, the system can configure service plans, which are set with rule codes and rule values, such as institution codes, product codes, and package codes. After a policy is underwritten, the system searches for a service plan based on the policy information, matching the rule values ​​in the service plan with the corresponding attribute values ​​in the policy information. However, the rule codes configured in the plan are fixed and may not match the attributes in the policy information. If a rule code does not match a policy attribute, the system will not be able to find the attribute value when searching for it on the policy using the rule code, resulting in a mismatch. Therefore, the processing logic needs to first convert the inconsistent rule codes into the corresponding policy attributes. Because this conversion is hard-coded, the system must be modified every time there are inconsistent rule codes and attributes, resulting in poor flexibility and high maintenance costs for the policy service rule matching system. Summary of the Invention

[0003] The technical problem to be solved by the embodiments of this application is the poor flexibility and high maintenance cost of existing policy service rule matching systems.

[0004] To address the aforementioned technical problems, this application provides a method for matching protocol data service rules, employing the following technical solution:

[0005] The matching method for the protocol data service rules includes:

[0006] Obtain target protocol data information, which includes target protocol data attributes and target attribute values ​​corresponding to the target protocol data attributes;

[0007] Based on the preset mapping relationship between protocol data attributes and preset rule codes, the target rule code corresponding to the target protocol data attribute is searched in the preset repository according to the target protocol data attribute, and the target rule value is retrieved from the corresponding target service rule according to the target rule code. The preset repository is used to dynamically store the preset mapping relationship between the preset protocol data attributes and the preset rule codes.

[0008] Based on the target attribute value and the target rule value, determine whether the target protocol data information matches the target service rule;

[0009] If a match is found, the target protocol data information is bound to the target service rule for service binding.

[0010] Optionally, before the process of searching for the target rule code corresponding to the target protocol data attribute in a preset repository based on the preset mapping relationship between the protocol data attribute and the preset rule code, and retrieving the target rule value from the corresponding target service rule based on the target rule code, the method further includes:

[0011] Configure the default repository;

[0012] Dynamically configure the mapping relationship between preset rule codes and preset protocol data attributes.

[0013] Optionally, after configuring the preset repository, the method further includes:

[0014] Dynamically configure service rules, rule codes, and rule values, and save them in the preset repository;

[0015] The dynamic configuration service rules, rule codes, and the correspondence between rule values ​​are stored in the preset repository.

[0016] Optionally, the step of searching for the target rule code corresponding to the target protocol data attribute in a preset repository based on the preset mapping relationship between the target protocol data attribute and the preset rule code, and retrieving the target rule value from the corresponding target service rule based on the target rule code, includes:

[0017] Count the number of the target protocol data attributes and target attribute values;

[0018] If there are multiple target protocol data attributes and target attribute values, based on the preset mapping relationship between the protocol data attributes and the preset rule codes, the multiple target protocol data attributes are traversed to find multiple target rule codes that correspond one-to-one with the multiple target protocol data attributes in the preset repository, and the multiple target rule codes are traversed to extract multiple target rule values ​​from the corresponding target service rules. Each set of target attribute values ​​and target rule values ​​is uniquely matched.

[0019] Optionally, determining whether the target protocol data information matches the target service rule based on the target attribute value and the target rule value includes:

[0020] Iterate through each group and determine whether the target attribute value and the target rule value are the same;

[0021] If each set of target attribute values ​​is the same as the target rule values, then the target protocol data information and the target service rule are successfully matched.

[0022] If any set of target attribute values ​​and target rule values ​​are different, then the target protocol data information fails to match the target service rule.

[0023] Optionally, determining whether the target protocol data information matches the target service rule based on the target attribute value and the target rule value includes:

[0024] Determine whether the target attribute value is the same as the target rule value;

[0025] If the target attribute value is the same as the target rule value, then the target protocol data information and the target service rule are successfully matched.

[0026] If the target attribute value is not the same as the target rule value, then the target protocol data information fails to match the target service rule.

[0027] This invention also provides a matching device for protocol data service rules, the matching device for protocol data service rules comprising:

[0028] The acquisition module is used to acquire target protocol data information, which includes target protocol data attributes and target attribute values ​​corresponding to the target protocol data attributes.

[0029] The lookup module is used to search for the target rule code corresponding to the target protocol data attribute in a preset repository based on the preset mapping relationship between the target protocol data attribute and the preset rule code, and to retrieve the target rule value from the corresponding target service rule based on the target rule code. The preset repository is used to dynamically store the preset mapping relationship between the preset protocol data attribute and the preset rule code.

[0030] The matching module is used to determine whether the target protocol data information matches the target service rule based on the target attribute value and the target rule value.

[0031] The service binding module is used to bind the target protocol data information with the target service rule if a match is found.

[0032] Optionally, prior to the search module, the device further includes:

[0033] The first configuration module is used to configure the preset repository;

[0034] The second configuration module is used to dynamically configure the mapping relationship between preset rule codes and preset protocol data attributes.

[0035] This invention also provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps in the protocol data service rule matching method described in the above embodiments.

[0036] This invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in the protocol data service rule matching method described in the above embodiments.

[0037] Compared with the prior art, the embodiments of this application have the following main advantages:

[0038] By acquiring target protocol data information, which includes target protocol data attributes and corresponding target attribute values, and based on a preset mapping relationship between protocol data attributes and preset rule codes, the system searches for the target rule code corresponding to the target protocol data attribute in a preset repository, and retrieves the target rule value from the corresponding target service rule based on the target rule code. The preset repository dynamically stores the preset mapping relationship between protocol data attributes and preset rule codes. The system determines whether the target protocol data information matches the target service rule based on the target attribute value and the target rule value. If they match, the target protocol data information is service-bound to the target service rule. In this way, the mapping relationship between rule codes and protocol data attributes can be dynamically configured. If business changes occur and additions or modifications are needed, they can be made in the preset repository. If the protocol data attributes and rule codes are inconsistent, only the mapping relationship between rule codes and protocol data attributes needs to be modified in the preset repository; the system does not need to be upgraded, improving system flexibility and reducing system maintenance costs. Attached Figure Description

[0039] To more clearly illustrate the solutions in 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 some embodiments of this application. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0040] Figure 1 This is a flowchart of a method for matching protocol data service rules provided in an embodiment of the present invention;

[0041] Figure 2 This is a schematic diagram of the structure of a protocol data service rule matching device provided in an embodiment of the present invention;

[0042] Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0043] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used herein in the specification of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "comprising" and "having," and any variations thereof, in the specification, claims, and foregoing drawings of this application are intended to cover non-exclusive inclusion. The terms "first," "second," etc., in the specification, claims, or foregoing drawings of this application are used to distinguish different objects, not to describe a particular order.

[0044] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0045] like Figure 1 As shown in the figure, this application embodiment provides a method for matching protocol data service rules, which includes the following steps:

[0046] Step 101: Obtain target protocol data information, which includes target protocol data attributes and target attribute values ​​corresponding to the target protocol data attributes.

[0047] The aforementioned target protocol data information refers to the protocol data information of the target protocol data for which the user needs to issue a service plan. Target protocol data can be policy data in the automotive insurance industry, and the corresponding target protocol data information corresponds to target policy data information, etc. The aforementioned target protocol data attributes are the protocol data attributes contained within this target protocol data information, such as policy data attributes. Protocol data attributes can be policy data attributes, such as institution code, product code, product version number, etc. The aforementioned target attribute values ​​can be the attribute values ​​contained in the target protocol data information that correspond to the protocol data attributes. For example, when the target protocol data attribute is the product code (productCode), the target attribute value could be MP09021910. Another example is that when the target protocol data attribute is the product version number (productVersion), the target attribute value is 1.1, etc. It should be noted that the protocol data attributes and attribute values ​​can be manually configured by business personnel according to business needs. A single set of protocol data information can include multiple protocol data attributes and multiple attribute values, and the multiple attribute values ​​correspond one-to-one with the multiple protocol data attributes.

[0048] Specifically, once the protocol data is generated, corresponding protocol data information will be created.

[0049] Step 102: Based on the preset mapping relationship between protocol data attributes and preset rule codes, search for the target rule code corresponding to the target protocol data attribute in the preset repository according to the target protocol data attribute, and retrieve the target rule value from the corresponding target service rule according to the target rule code.

[0050] The aforementioned preset repository is pre-configured, and its contents can be dynamically configured, such as dynamically adding, modifying, and deleting data. Specifically, the mapping relationship between preset protocol data attributes and preset rule codes in the preset repository can also be dynamically added, modified, and deleted according to business needs. The preset repository is used to dynamically store the mapping relationship between preset protocol data attributes and preset rule codes. It should be noted that both the preset protocol data attributes and preset rule codes are pre-set. Furthermore, the representation of protocol data attributes and preset rule codes can be the same; however, protocol data attributes refer to the content within the protocol data information, while rule codes refer to the service rule. It should also be noted that a single service rule can contain multiple rule codes and multiple rule values, and there is a one-to-one correspondence between the multiple rule values ​​and multiple rule codes.

[0051] The aforementioned service rules include one or more of the following: coverage period, package code, issuing institution, insured's age range, premium range, insurance start date, product version number, and customer type. When there are multiple service rules, there are also multiple rule codes and multiple rule values.

[0052] Specifically, step 102 includes:

[0053] Count the number of target protocol data attributes and target attribute values.

[0054] If there are multiple target protocol data attributes and target attribute values, based on the preset mapping relationship between the protocol data attributes and the preset rule codes, the multiple target protocol data attributes are traversed to find multiple target rule codes that correspond one-to-one with the multiple target protocol data attributes in the preset repository, and the multiple target rule codes are traversed to retrieve multiple target rule values ​​from the corresponding target service rules. Each set of target attribute values ​​and target rule values ​​is uniquely matched.

[0055] More specifically, before searching for the target rule code corresponding to the target protocol data attribute in the preset repository, it is necessary to count the number of target protocol data attributes and target attribute values. When there is a set of protocol data attributes and attribute values ​​in the target protocol data information, it is only necessary to search for a rule code corresponding to the target service rule in the preset repository based on the set of protocol data attributes, and then retrieve the rule value based on the rule code.

[0056] When the target protocol data information contains multiple sets of target protocol data attributes and target attribute values, it is necessary to traverse each set of target protocol data attributes to find the corresponding rule codes and rule values ​​from the preset repository. For example, if there are two sets of target protocol data attributes and target attribute values, then it is necessary to find the corresponding two sets of rule codes and rule values ​​in the preset repository. This means that multiple smaller service rules can exist within the same large service solution.

[0057] Step 103: Determine whether the target protocol data information matches the target service rules based on the target attribute value and the target rule value.

[0058] Specifically, it determines whether the target attribute value is the same as the target rule value; if the target attribute value is the same as the target rule value, the target protocol data information and the target service rule are successfully matched; if the target attribute value is different from the target rule value, the target protocol data information and the target service rule are not matched.

[0059] More specifically, when there are multiple target protocol data attributes and multiple target attribute values, it means that multiple sets of rule codes and multiple sets of rule values ​​have been matched.

[0060] Then, it is necessary to iterate and determine whether each group of target attribute values ​​and target rule values ​​are the same; if each group of target attribute values ​​and target rule values ​​are the same, then the target protocol data information and the target service rule are successfully matched; if any group of target attribute values ​​and target rule values ​​are different, then the target protocol data information and the target service rule are not matched.

[0061] When comparing multiple sets of target attribute values ​​and target rule values, first check if the first set of target attribute values ​​and target rule values ​​are the same (or equal; same or equal can refer to the same or equal representation symbols, text, numbers, etc.). If they are the same, the service rule is valid. Continue processing the next target attribute value and target rule value. After all service rules have been compared, if all corresponding target attribute values ​​and target rule values ​​are the same, the service rule matches. If any target attribute value and target rule value are different, the service rule does not match.

[0062] Step 104: If a match is found, bind the target protocol data information with the target service rules.

[0063] Specifically, once it is confirmed that the target protocol data information and the target service rule are successfully matched, the target protocol data information and the target service rule can be bound together. This allows users to easily find the corresponding target service rule when searching for the target protocol data information, thus intuitively understanding the service plan content of the target service rule corresponding to the target protocol data information. Users can effectively maintain and follow up on the target protocol data information, thereby improving service quality.

[0064] In this embodiment, target protocol data information is obtained, including target protocol data attributes and corresponding target attribute values. Based on a preset mapping relationship between protocol data attributes and preset rule codes, the target rule code corresponding to the target protocol data attribute is searched in a preset repository according to the target protocol data attribute, and the target rule value is retrieved from the corresponding target service rule according to the target rule code. The preset repository is used to dynamically store the preset mapping relationship between protocol data attributes and preset rule codes. The target protocol data information and the target service rule are judged to match based on the target attribute value and the target rule value. If they match, the target protocol data information and the target service rule are bound together. In this way, the mapping relationship from rule code to protocol data attribute can be dynamically configured. If business changes occur and additions or modifications are needed, they can be made in the preset repository. If the protocol data attribute and rule code are inconsistent, only the mapping relationship from rule code to protocol data attribute needs to be modified in the preset repository. The system does not need to be upgraded or modified, which improves flexibility and reduces system maintenance costs.

[0065] In this embodiment of the application, before step 102, the matching method for the protocol data service rules further includes:

[0066] Configure the default repository;

[0067] Dynamically configure the mapping relationship between preset rule codes and preset protocol data attributes.

[0068] Of course, the matching methods for the protocol's data service rules also include:

[0069] Dynamically configure service rules, rule codes, and rule values, and save them in a preset repository;

[0070] The system dynamically configures the correspondence between service rules, rule codes, and rule values, and stores them in a preset repository.

[0071] Specifically, a repository needs to be set up in advance. This repository can be used to dynamically store the mapping relationship between rule codes and protocol data attributes. The mapping relationship between rule codes and protocol data attributes can be dynamically added, modified, or deleted according to business needs. Of course, the pre-set repository can also be used to dynamically store the correspondence between rule codes, service rules, and rule values. The correspondence between rule codes, service rules, and rule values ​​can be dynamically added, modified, or deleted according to business needs. Rule codes can also be dynamically added, modified, or deleted.

[0072] In this embodiment, the rule encoding and its mapping to protocol data attributes can be dynamically configured and stored in a preset repository. If business needs change subsequently, requiring additions or modifications, these can be done in the preset repository. If the protocol data attributes and rule encodings are inconsistent, only the mapping relationship between the rule encodings and protocol data attributes needs to be modified in the preset repository; the system does not require upgrades or modifications, thus improving flexibility and reducing system maintenance costs.

[0073] like Figure 2 As shown, this embodiment of the invention also provides a protocol data service rule matching device, the protocol data service rule matching device 200 comprising:

[0074] The acquisition module 201 is used to acquire target protocol data information, which includes target protocol data attributes and target attribute values ​​corresponding to the target protocol data attributes.

[0075] The lookup module 202 is used to search for the target rule code corresponding to the target protocol data attribute in the preset repository based on the preset mapping relationship between the preset protocol data attributes and the preset rule codes, and to retrieve the target rule value from the corresponding target service rule based on the target rule code. The preset repository is used to dynamically store the preset mapping relationship between the preset protocol data attributes and the preset rule codes.

[0076] Matching module 203 is used to determine whether the target protocol data information matches the target service rule based on the target attribute value and the target rule value;

[0077] The service binding module is used to bind the target protocol data information with the target service rules if a match is found.

[0078] Optionally, prior to the lookup module 202, the protocol data service rule matching device 200 further includes:

[0079] The first configuration module is used to configure the preset repository;

[0080] The second configuration module is used to dynamically configure the mapping relationship between preset rule codes and preset protocol data attributes.

[0081] Optionally, after the first configuration module, the protocol data service rule matching device 200 further includes:

[0082] The third configuration module is used to dynamically configure service rules, rule codes, and rule values, and save them in a preset repository.

[0083] The fourth configuration module is used to dynamically configure the correspondence between service rules, rule codes, and rule values, and stores them in a preset repository.

[0084] Optionally, the lookup module 202 also includes:

[0085] The statistical unit is used to count the number of target protocol data attributes and target attribute values.

[0086] The lookup unit is used to search for multiple target rule codes that correspond one-to-one with multiple target protocol data attributes in a preset repository based on the mapping relationship between preset protocol data attributes and preset rule codes, and to retrieve multiple target rule values ​​from the corresponding target service rules by traversing multiple target rule codes. Each set of target attribute values ​​and target rule values ​​is uniquely matched.

[0087] Optionally, the matching module 203 includes:

[0088] The first judgment unit is used to determine whether the target attribute value is the same as the target rule value;

[0089] The first matching unit is used to determine if the target attribute value is the same as the target rule value, in which case the target protocol data information and the target service rule are successfully matched.

[0090] The second matching unit is used to determine if the target protocol data information fails to match the target service rule if the target attribute value is different from the target rule value.

[0091] Optionally, the matching module 203 includes:

[0092] The second judgment unit is used to iterate and judge whether the target attribute value and the target rule value of each group are the same;

[0093] The third matching unit is used to ensure that if each set of target attribute values ​​is the same as the target rule values, then the target protocol data information and the target service rule are successfully matched.

[0094] The fourth matching unit is used to determine if the target protocol data information fails to match the target service rule if any set of target attribute values ​​and target rule values ​​are different.

[0095] like Figure 3 As shown, this embodiment of the invention also provides an electronic device 300, which includes: a memory 302, a processor 301, a network interface 303, and a computer program stored in the memory 302 and executable on the processor 301, wherein:

[0096] The processor 301 is used to call the computer program stored in the memory 302 and perform the following steps:

[0097] Obtain target protocol data information, which includes target protocol data attributes and target attribute values ​​corresponding to the target protocol data attributes;

[0098] Based on the preset mapping relationship between protocol data attributes and preset rule codes, the system searches for the target rule code corresponding to the target protocol data attribute in the preset repository according to the target protocol data attribute, and retrieves the target rule value from the corresponding target service rule according to the target rule code. The preset repository is used to dynamically store the preset mapping relationship between the preset protocol data attributes and preset rule codes.

[0099] Determine whether the target protocol data information matches the target service rules based on the target attribute values ​​and target rule values;

[0100] If a match is found, the target protocol data information will be bound to the target service rules.

[0101] Optionally, before the processor 301 executes the process of matching protocol data service rules based on the mapping relationship between preset protocol data attributes and preset rule codes, searching for the target rule code corresponding to the target protocol data attribute in a preset repository according to the target protocol data attribute, and retrieving the target rule value from the corresponding target service rule according to the target rule code, the matching method for protocol data service rules further includes:

[0102] Configure the default repository;

[0103] Dynamically configure the mapping relationship between preset rule codes and preset protocol data attributes.

[0104] Optionally, the matching method for protocol data service rules executed by processor 301 after configuring the preset repository also includes:

[0105] Dynamically configure service rules, rule codes, and rule values, and save them in a preset repository;

[0106] The system dynamically configures the correspondence between service rules, rule codes, and rule values, and stores them in a preset repository.

[0107] Optionally, the processor 301 executes a mapping relationship based on a preset protocol data attribute and a preset rule code, searches for the target rule code corresponding to the target protocol data attribute in a preset repository according to the target protocol data attribute, and retrieves the target rule value from the corresponding target service rule according to the target rule code, including:

[0108] Count the number of target protocol data attributes and target attribute values;

[0109] If there are multiple target protocol data attributes and target attribute values, based on the preset mapping relationship between the protocol data attributes and the preset rule codes, the multiple target protocol data attributes are traversed to find multiple target rule codes that correspond one-to-one with the multiple target protocol data attributes in the preset repository, and the multiple target rule codes are traversed to retrieve multiple target rule values ​​from the corresponding target service rules. Each set of target attribute values ​​and target rule values ​​is uniquely matched.

[0110] Optionally, the processor 301 performs the following: determining whether the target protocol data information matches the target service rule based on the target attribute value and the target rule value, including:

[0111] Determine whether the target attribute value is the same as the target rule value;

[0112] If the target attribute value is the same as the target rule value, then the target protocol data information and the target service rule are successfully matched.

[0113] If the target attribute value is different from the target rule value, then the target protocol data information fails to match the target service rule.

[0114] Optionally, the processor 301 performs the following: determining whether the target protocol data information matches the target service rule based on the target attribute value and the target rule value, including:

[0115] Iterate through each group and determine whether the target attribute value and the target rule value are the same;

[0116] If each set of target attribute values ​​is the same as the target rule values, then the target protocol data information and the target service rule are successfully matched.

[0117] If any set of target attribute values ​​and target rule values ​​are different, the target protocol data information will fail to match the target service rule.

[0118] The electronic device 300 provided in this embodiment of the invention can realize the various implementation methods in the protocol data service rule matching method embodiment, as well as the corresponding beneficial effects. To avoid repetition, these will not be described again here.

[0119] It should be noted that only the processor 301, memory 302, and network interface 303 with components are shown in the figure. However, it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Those skilled in the art will understand that the electronic device described here is a device capable of automatically performing numerical calculations and / or information processing according to pre-set or stored instructions. Its hardware includes, but is not limited to, microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0120] Electronic devices can be computing devices such as desktop computers, laptops, PDAs, and cloud servers. Human-computer interaction can be achieved through methods such as keyboards, mice, remote controls, touchpads, or voice-activated devices.

[0121] The memory 302 includes at least one type of readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 302 may be an internal storage unit of an electronic device, such as the hard disk or memory of the electronic device. In other embodiments, the memory 302 may also be an external storage device of the electronic device, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the electronic device. Of course, the memory 302 may include both internal storage units and external storage devices of the electronic device. In this embodiment, the memory 302 is typically used to store the operating system and various application software installed on the electronic device, such as program code for matching methods of protocol data service rules. In addition, the memory 302 may also be used to temporarily store various types of data that have been output or will be output.

[0122] In some embodiments, processor 301 may be a central processing unit (CPU), controller, microcontroller, microprocessor, or other data processing chip. This processor 301 is typically used to control the overall operation of the electronic device. In this embodiment, processor 301 is used to run program code stored in memory 302 or process data, such as program code for running a matching method for protocol data service rules.

[0123] The network interface 303 may include a wireless network interface or a wired network interface, which is typically used to establish a communication connection between the electronic device 300 and other electronic devices.

[0124] This invention also provides a computer-readable storage medium storing a computer program. When the computer program is executed by the processor 301, it implements the various processes of the protocol data service rule matching method embodiment provided by this invention and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0125] Those skilled in the art will understand that all or part of the process in the matching method of the protocol data service rules of the embodiments can be implemented by a computer program instructing related hardware. The program of the matching method of the protocol data service rules can be stored in a computer-readable storage medium. When the program is executed, it can include the process of the embodiments of the various methods.

[0126] Obviously, the embodiments described above are only some embodiments of this application, not all embodiments. The accompanying drawings show preferred embodiments of this application, but do not limit the patent scope of this application. This application can be implemented in many different forms; rather, the purpose of providing these embodiments is to provide a more thorough and comprehensive understanding of the disclosure of this application. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing specific embodiments, or make equivalent substitutions for some of the technical features. Any equivalent structures made using the content of this application's specification and drawings, directly or indirectly applied to other related technical fields, are similarly within the scope of patent protection of this application.

Claims

1. A method for matching protocol data service rules, characterized in that, The method includes: Obtain target protocol data information, which includes target protocol data attributes and target attribute values ​​corresponding to the target protocol data attributes; Based on the mapping relationship between preset protocol data attributes and preset rule codes, the system searches for the target rule code corresponding to the target protocol data attribute in a preset repository according to the target protocol data attribute, and retrieves the target rule value from the corresponding target service rule according to the target rule code. The preset repository is used to dynamically store the mapping relationship between preset protocol data attributes and preset rule codes. Service rules include one or more of the following: coverage period, package code, issuing agency, insured age range, premium range, insurance start date, product version number, and customer type. The preset protocol data attributes and preset rule codes have the same representation. Protocol data attributes are relative to the content in the protocol data information, and rule codes are relative to the service rules. The system counts the number of target protocol data attributes and target attribute values. If there are multiple target protocol data attributes and target attribute values, based on the mapping relationship between preset protocol data attributes and preset rule codes, the system traverses multiple target protocol data attributes to search for multiple target rule codes that correspond one-to-one with the multiple target protocol data attributes in the preset repository, and traverses the multiple target rule codes to retrieve multiple target rule values ​​from the corresponding target service rules. Each set of target attribute values ​​and target rule values ​​is uniquely matched. Based on the target attribute value and the target rule value, determine whether the target protocol data information matches the target service rule; If a match is found, the target protocol data information is bound to the target service rule for service binding.

2. The matching method for protocol data service rules according to claim 1, characterized in that, Before the mapping relationship between the preset protocol data attributes and preset rule codes, the method further includes: searching for the target rule code corresponding to the target protocol data attribute in a preset repository based on the target protocol data attribute, and retrieving the target rule value from the corresponding target service rule based on the target rule code; Configure the default repository; Dynamically configure the mapping relationship between preset rule codes and preset protocol data attributes.

3. The matching method for protocol data service rules according to claim 2, characterized in that, After configuring the preset repository, the method further includes: Dynamically configure service rules, rule codes, and rule values, and save them in the preset repository; The dynamic configuration service rules, rule codes, and the correspondence between rule values ​​are stored in the preset repository.

4. The matching method for protocol data service rules according to claim 1, characterized in that, The step of determining whether the target protocol data information matches the target service rule based on the target attribute value and the target rule value includes: Iterate through each group and determine whether the target attribute value and the target rule value are the same; If each set of target attribute values ​​is the same as the target rule values, then the target protocol data information and the target service rule are successfully matched. If any set of target attribute values ​​and target rule values ​​are different, then the target protocol data information fails to match the target service rule.

5. The matching method for protocol data service rules according to claim 1, characterized in that, The step of determining whether the target protocol data information matches the target service rule based on the target attribute value and the target rule value includes: Determine whether the target attribute value is the same as the target rule value; If the target attribute value is the same as the target rule value, then the target protocol data information and the target service rule are successfully matched. If the target attribute value is not the same as the target rule value, then the target protocol data information fails to match the target service rule.

6. A matching device for protocol data service rules, characterized in that, The device includes: The acquisition module is used to acquire target protocol data information, which includes target protocol data attributes and target attribute values ​​corresponding to the target protocol data attributes. The lookup module is used to search for the target rule code corresponding to the target protocol data attribute in a preset repository based on the preset mapping relationship between the target protocol data attribute and the preset rule code. Then, it retrieves the target rule value from the corresponding target service rule based on the target rule code. The preset repository dynamically stores the mapping relationship between the preset protocol data attributes and the preset rule codes. Service rules include one or more of the following: coverage period, package code, issuing agency, insured age range, premium range, insurance start date, product version number, and customer type. The preset protocol data attributes and preset rule code table... The same format is used, but the protocol data attributes are relative to the content in the protocol data information, and the rule codes are relative to the service rules. The number of target protocol data attributes and target attribute values ​​is counted. If there are multiple target protocol data attributes and target attribute values, based on the preset mapping relationship between the protocol data attributes and the preset rule codes, multiple target protocol data attributes are traversed to find multiple target rule codes that correspond one-to-one with the multiple target protocol data attributes in the preset repository, and multiple target rule values ​​are extracted from the corresponding target service rules by traversing the multiple target rule codes. Each set of target attribute values ​​and target rule values ​​is uniquely matched. The matching module is used to determine whether the target protocol data information matches the target service rule based on the target attribute value and the target rule value. The service binding module is used to bind the target protocol data information with the target service rule if a match is found.

7. The matching device for protocol data service rules as described in claim 6, characterized in that, Prior to the search module, the device further includes: The first configuration module is used to configure the preset repository; The second configuration module is used to dynamically configure the mapping relationship between preset rule codes and preset protocol data attributes.

8. An electronic device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the steps in the matching method of protocol data service rules as described in any one of claims 1-5.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps in the matching method for protocol data service rules as described in any one of claims 1-5.

Images