CN114089957A

CN114089957A - Method, device and equipment for acquiring service logic code set of insurance service

Info

Publication number: CN114089957A
Application number: CN202111433467.1A
Authority: CN
Inventors: 姬小玉
Original assignee: OneConnect Financial Technology Co Ltd Shanghai
Current assignee: OneConnect Financial Technology Co Ltd Shanghai
Priority date: 2021-11-29
Filing date: 2021-11-29
Publication date: 2022-02-25

Abstract

The invention relates to a method, a device and equipment for acquiring a service logic code set of insurance service. The method comprises the following steps: acquiring a service logic based on a service application scene of an insurance service; analyzing a logic description language of the service logic, and marking an instruction chunk, an original source code and an annotation in the logic description language; for an instruction chunk, converting the instruction chunk into a target source code segment based on a conversion rule corresponding to a chunk name of the instruction chunk; and combining and splicing the annotations, the original source codes and the target source code segments to obtain a code set corresponding to the logic description language. The method can combine and match the service identification to generate the service logic aiming at different objects according to the service application scene of the insurance service, can quickly and accurately update the service logic when the service application scene is changed, realizes automatic conversion of the logic description language into codes, does not need to manually write the codes, and improves the working efficiency.

Description

Method, device and equipment for acquiring service logic code set of insurance service

Technical Field

The invention relates to the field of computers, in particular to a method and a device for acquiring a business logic code set of insurance business and computer equipment.

Background

With the economic development and social progress, the insurance industry is also developed vigorously. Insurance means that the insurance applicant pays insurance fees to the insurer according to contract agreement, and the insurer undertakes the responsibility for compensating insurance fund for property loss caused by the occurrence of the accident possibly caused by the contract agreement, or undertakes the business insurance action for paying insurance fund responsibility when the insured dies, is damaged, has diseases or reaches the conditions of the age, the deadline and the like of the contract agreement. In the insurance industry, the development of various insurance product projects is a vital work for insurance companies, and a large amount of manpower and material resources are required to be invested. In insurance business, the process of acquiring the business logic code set is very cumbersome.

In insurance business, the process of acquiring a business logic code set is very complicated, and other project models of the same type are usually applied at first, the business logic model is butted with the business of an actual application scene in a manual hard sleeve mode, and then the code logic is applied. Due to the problem of insufficient matching of various logic model templates, a great deal of modification is generally required to be carried out on service logic codes, a great deal of manpower is required to be invested in modification, the whole process is very complicated, the project development efficiency of insurance services is low, and the requirements of practical application cannot be met.

Disclosure of Invention

Therefore, it is necessary to provide a method, an apparatus and a computer device for acquiring a service logic code set of an insurance service, aiming at the problems that when the service logic code set of the insurance service is acquired, due to the insufficient matching of a logic model template, the service logic code needs to be modified greatly, a large amount of manpower is invested, the process is complicated and tedious, and the project development efficiency of the insurance service is low and the requirements of practical application cannot be met.

A method for acquiring a service logic code set of insurance service comprises the following steps:

acquiring a service logic based on the service application scene of the insurance service;

analyzing a logic description language of the business logic, and marking an instruction chunk, an original source code and an annotation in the logic description language;

for the instruction chunk, converting the instruction chunk to a target source code segment based on a conversion rule corresponding to a chunk name of the instruction chunk;

and combining and splicing the annotation, the original source code and the target source code segment to obtain a code set corresponding to the logic description language.

In one embodiment, the obtaining a service logic based on the service application scenario of the insurance service includes:

acquiring one or more feature identifiers of a target object from a preset identifier database;

acquiring at least one preset rule from a preset rule base based on a service application scene;

matching at least one preset rule for each characteristic identifier to generate one or more service identifiers; wherein, each service identifier comprises a characteristic identifier;

and performing combination matching on the one or more service identifications to generate one or more service logics.

In one embodiment, the obtaining one or more feature identifiers of the target object from a preset identifier database includes:

and determining one or more feature identifiers corresponding to the target object in the identifier database according to preset rule information and the feature information of the target object.

In one embodiment, the performing combined matching on the one or more service identifiers includes performing combined matching on the one or more service identifiers by using a combined matching method of intersection, mutual exclusion, or union.

In one embodiment, before the performing the combined matching on the one or more service identifiers, the obtaining a service logic based on a service application scenario of the insurance service further includes:

when the service application scene is changed, determining one or more feature identifiers needing to be changed;

generating one or more corresponding updated service identifications according to each feature identification needing to be changed;

and replacing the combination matching of the one or more service identifications with the combination matching of the updated one or more service identifications.

In one embodiment, the determining, when the service application scenario changes, one or more feature identifiers that need to be changed includes: when the service application scene is changed, determining one or more feature identifiers needing to be deleted;

generating one or more corresponding updated service identifiers according to each feature identifier changed as required, including: and deleting one or more corresponding service identifications based on each characteristic identification needing to be deleted to generate one or more updated service identifications.

In one embodiment, the determining, when the service application scenario changes, one or more feature identifiers that need to be changed includes: when the service application scene is changed, determining one or more feature identifiers needing to be added;

generating one or more corresponding updated service identifiers according to each feature identifier changed as required, including: and matching at least one preset rule for each feature identifier needing to be added so as to generate one or more updated service identifiers.

An apparatus for acquiring a service logic code set of an insurance service, comprising:

the acquisition module is used for acquiring service logic based on the service application scene of the insurance service;

the analysis module is used for analyzing the logic description language of the business logic and marking an instruction chunk, an original source code and an annotation in the logic description language;

a conversion module for converting the instruction chunk into a target source code segment based on a conversion rule corresponding to a chunk name of the instruction chunk for the instruction chunk;

and the splicing module is used for combining and splicing the annotation, the original source code and the target source code segment to obtain a code set corresponding to the logic description language.

A computer device comprising a memory and a processor, the memory having stored therein computer readable instructions which, when executed by the processor, cause the processor to perform the steps of the above-mentioned method for obtaining a set of business logic codes of an insurance service.

A storage medium storing computer readable instructions which, when executed by one or more processors, cause the one or more processors to perform the steps of the above method for acquiring a set of business logic codes for an insurance service.

The method, the device, the computer equipment and the storage medium for acquiring the service logic code set of the insurance service can combine and match the service identifications to generate the service logic aiming at different objects according to the service application scene of the insurance service, wherein each service identification comprises a characteristic identification, the objects and the service logic can be decoupled, the service logic can be quickly and accurately updated when the service application scene is changed, meanwhile, the logic description language is automatically converted into the codes, professional technicians do not need to manually write the codes, the labor cost is reduced, the complexity of the code generating process is reduced, the code generating efficiency is improved, the working efficiency is improved, and the requirement of practical application can be completely met.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art without creative efforts.

FIG. 1 is a flow diagram of a method for obtaining a set of business logic codes for an insurance service provided in one embodiment;

FIG. 2 is a flowchart of one embodiment of step S10 shown in FIG. 1;

FIG. 3 is a flowchart of another embodiment of step S10 shown in FIG. 1;

FIG. 4 is a block diagram of an apparatus for acquiring a service logic code set of insurance services in one embodiment;

FIG. 5 is a block diagram showing an internal configuration of a computer device in one embodiment;

FIG. 6 is a diagram of a storage medium having computer-readable instructions stored therein according to one embodiment.

The implementation, functional features and advantages of the objectives of the present application will be further explained with reference to the accompanying drawings.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

It will be understood that the terms "first," "second," "third," and the like are used merely to distinguish one description from another, and are not intended to indicate or imply relative importance. It will also be understood that, although the terms first, second, third, etc. may be used herein to describe various elements in some of the embodiments of the application, these elements should not be limited by these terms. These terms are only used to distinguish one element from another.

As shown in fig. 1, in an embodiment, a method for acquiring a service logic code set of an insurance service is provided, where the method for acquiring a service logic code set of an insurance service may specifically include the following steps:

and S10, acquiring the service logic based on the service application scene of the insurance service.

In the management system of an insurance company, an object refers to an insurance beneficiary. The insurance beneficiary refers to a person who receives the benefits of an insurance contract in the life insurance. The beneficiary is designated by the insured life and loads the insurance contract. The method specifically comprises the following conditions: 1) when the insurant insurs personal insurance, the beneficiary can be the insurant, namely the insured; or a third party; 2) when the applicant insures personal insurance for others, the beneficiary may be the applicant, the insured life, or a third party. The insured life can replace the insurance beneficiary. The characteristics of the object may include, for example, basic information of the insurance beneficiary, fee payment information, and the like.

In some embodiments, as shown in fig. 2, step S10 may include the following steps:

s101, one or more feature identifications of the target object are obtained from a preset identification database.

All the identifications of all the objects can be stored in the identification database. The identification database is pre-constructed.

Taking deposit type insurance as an example, deposit type insurance is insurance designed by insurance companies which combines insurance function and deposit function, such as common double life insurance, pension and education insurance, and has deposit function besides basic guarantee function. If the insurance beneficiary does not use the insurance compensation within the insurance period, then at the appointed time, the insurance company will return a sum of money to the insurance beneficiary, as if the insurance fee is saved year by year, and the whole withdrawal is carried out after the expiration, similar to the bank's whole withdrawal for the saved part. The term of paying a deposit-type insurance may refer to, for example, paying a certain amount of insurance fee at a predetermined time every year, and continuously paying a certain period of time, and such an insurance.

Features of the same meaning of different objects or different features of the same meaning of the same object that differ only in the manner of expression may correspond to the same identifier in the identifier database.

For example, the year of birth and age of the same insurance beneficiary correspond to the same identification in the identification database.

In some embodiments, one or more feature identifiers corresponding to the preset rule information and the feature information of the target object in the identifier database may be determined according to the preset rule information and the feature information of the target object.

The preset rule information is a preset rule adopted in the current service application scene.

For example, in a business application scenario of paying deposit insurance regularly, a preset rule of the business application scenario relates to a plurality of characteristics such as gender, age, insurance type and the like, and the preset rule information can be searched in an identification database to obtain the three identifications of the insurance beneficiary as characteristic identifications of objects in the business application scenario.

In some embodiments, when the identification database is generated, the identification can be extracted according to the characteristic information of the object; and carrying out duplication elimination processing on the extracted identification to generate the identification database.

Wherein all the identifiers are stored in the identifier database. And for a specific object, extracting part of identification from the identification data as the characteristic identification of the object according to the characteristics of the object.

By extracting and de-duplicating the characteristic information of the object, the identification amount can be reduced, namely the total data amount of the identification is reduced, the problem that the storage space of the identification database is insufficient due to the fact that the total data amount is too large is solved, and the use efficiency of the identification database is improved.

For example, three families A, B and C participate in insurance application in a certain cell, family members in family a have 4 kinds of features, family members in family B in the same age group (e.g., [30,50] which is a factor generally considered in the insurance industry) have 7 kinds of features, family members in family C in the same age group (e.g., [30,50] which is a factor generally considered in the insurance industry) have 9 kinds of features, and in order to meet the requirement, the technical solution in the prior art needs to define the number of feature types to be 4+7+ 9-20. In the solution of this embodiment, if 7 of the 9 features of the family C have the same specific meaning as 7 features of the family B (i.e. the features of the family C9 include the 7 features plus two other features), and 4 of the 7 features of the family B have the same meaning as 4 features of the family a, then only 9 features are needed to describe the feature information of all family members of the family a, the family B, and the family C.

In the embodiment, repeated features of different objects are extracted and removed, so that an identification database is formed, unified naming of the same kind of features of different objects can be realized, identification storage capacity is reduced, namely, data total amount is reduced, and the problem that storage space of the identification database is insufficient due to overlarge data total amount is solved.

In some embodiments, different dimensional classification of identities in an identity database can be achieved.

For example, name, gender, and age may be classified into basic information classes; the insurance type, the insurance beneficiary level and the like can be divided into a fee payment type and the like, and the specific division mode can be set according to actual needs.

S102, acquiring at least one preset rule from a preset rule base based on a service application scene. The preset rule base comprises a plurality of basic preset rules.

In the embodiment of the application, various basic preset rules are obtained by extracting the service application scenes. In the business application scenario of the insurance company for paying the savings insurance periodically, the preset rules of the business application scenario may include, but are not limited to, preset rules of discount for the fee, full reduction of the insurance year fee, different payment fees corresponding to different age groups of the insurance beneficiary, and the like.

S103, matching at least one preset rule for each feature identifier to generate one or more service identifiers, wherein each service identifier comprises one feature identifier.

For example, in a business application scenario of a deposit-type insurance company, characteristics of a target object of the business application scenario include age (the age is divided into different age groups), insurance type (four types of type a, type B, type C, and type D), and insurance service life. An example of a table of characteristic data of the target object is shown in the following table, for example.

Table object characteristics data

Object	Age (age)	Type of insurance	Life of insuring
				Safety beneficiary armor	18	Type B	8
Insurance beneficiary B	15	Type C	12
				Insurance beneficiary third	28	Type A	10
Insurance benefitting man	10	Type D	7

The business application scenario specifies that an object with the age of the insurance beneficiary within the interval of [18,20], the insurance type of D and the insurance service life of five years can enjoy eight-fold discount benefits of one-year insurance service cost. Accordingly, one preset rule extracted from the preset rule base is as follows: the insurance cost is eight folds for one year. Matching the preset rule for the age, the insurance type and the insurance service life respectively based on the preset rule information to obtain three service identifications: the object in the age range of [18,20] can enjoy the eight-fold discount of the one-year insurance expense, the object with the insurance type D can enjoy the eight-fold discount of the one-year insurance expense, and the object with the insurance service life reaching five years can enjoy the eight-fold discount of the one-year insurance expense.

And S104, combining and matching the one or more service identifications to generate one or more service logics.

As described in the example given in step S103, to implement the preset rule: the object with the age in the range of [18,20], the insurance type D and the insurable life reaching five years can enjoy the eight-fold discount of the insurable cost of one year, and the three service identifications can be subjected to identity matching, namely, under the condition of simultaneously adopting the three service identifications, only the intersection part of the three service identifications is valid. The combination matching mode can be set according to actual needs, and besides the matching mode of intersection, combination matching modes such as mutual exclusion and union can be adopted.

In some embodiments, step S10 may further include, before step S104, the steps of:

s103', when the service application scene is changed, determining one or more feature identifiers needing to be changed;

s103', generating one or more corresponding updated service identifications according to each feature identification needing to be changed.

Replacing the combination matching of the one or more service identifiers in the step S104 with the combination matching of the one or more updated service identifiers, that is, replacing the step S104 with:

s104', the updated one or more service identifications are combined and matched to generate one or more service logics.

The one or more feature identifiers to be changed may be, for example, one or more feature identifiers to be deleted, or one or more feature identifiers to be added.

In some embodiments, when a business application scene changes, one or more feature identifiers that need to be deleted may be determined; and deleting one or more corresponding service identifications based on each characteristic identification needing to be deleted to generate one or more updated service identifications. Taking a business application scenario of a regular deposit-type insurance payment of an insurance company as an example, when the business application scenario does not need to consider the insurance type of the insurance beneficiary, deleting the business identifier corresponding to the insurance type of the insurance beneficiary.

In some embodiments, one or more feature identifiers that need to be added may be determined when a business application scenario changes; and matching the at least one preset rule for each feature identifier needing to be added to generate one or more updated service identifiers.

Taking a business application scenario of a insurance company for paying a deposit-type insurance regularly as an example, when an object needing to increase the body weight index in the business application scenario is in a standard range and enjoys nine discount benefits on one-year insurance cost, a feature identifier is added: and matching the body weight index with a preset rule to generate a service identifier: the object whose body weight index falls within the standard range enjoys nine discount benefits on one-year insurance cost.

In some embodiments, the updated one or more business identifications may be recombined and matched to generate updated one or more business logics. After the service identifier is updated, in order to implement the change of the service application scenario, the updated one or more service identifiers need to be combined and matched.

For example, taking a business application scenario in which an object with a body weight index within a standard range is added to enjoy nine-fold benefits of one-year insurance cost and the feature identifier of the insurance type is deleted as an example, and the business application scenario specifies that the object with the body weight index within the standard range enjoys the nine-fold benefits of one-year insurance cost, the object with the age within the [18,20] interval can enjoy eight-fold benefits of one-year insurance cost, and the object with the insurance year duration up to five years can enjoy the eight-fold benefits of one-year insurance cost, only the object with the insurance year duration up to five years can enjoy the eight-fold benefits of one-year insurance cost. The combination and matching mode can be specifically set according to actual needs.

Based on this, the method of this embodiment can update the service logic by adding or deleting the service identifier of the specified feature identifier and then performing the combination matching again.

S20, analyzing the logic description language of the business logic, and marking out the instruction chunk, the original source code and the annotation in the logic description language.

The instruction chunks, original source code, and annotations may be referred to as description units. The logical description language includes a plurality of description units that include instruction chunks, original source code, and annotations.

The logic description language of the business logic may be a logic language for converting into computer programming language codes such as JAVA language, C + + language, etc., and the logic description language is used to describe the business logic that needs to be processed by the functional body. For example, the logic description language may contain relevant information for describing the business implementation process, the business execution steps involved in the business implementation process, and the like. The logic description language may be, for example, pseudo code.

The logical description language may be in various forms, such as an XML format file or a txt format file. XML, short for Extensible Markup Language, is a Markup Language for marking electronic documents to have structure. The TXT format is a text document.

In some embodiments, the logic description language may also employ custom file resources.

The description unit may be a comment, or an original code segment described in a computer programming language, and may also be one of instruction blocks for describing each service execution step.

Comments are explanations and illustrations of the code, the purpose of which is to make it easier for people to understand the function or use of the code. When the annotation is used for writing a program, a person who writes the program can explain or prompt a sentence, a program segment, a function and the like, so that the readability of the program code can be improved. The annotations are only for improved readability and are not compiled by the computer.

Annotations generally include prologue annotations and functional annotations. The main contents of the introductory note include the interfaces of the modules, the description of the data and the functionality of the modules. The main contents of the functional annotations of the module include the functions of the program segments, the functions of the statements, and the states of the data. For example, in a business application scenario where savings-type insurance is paid on a regular basis, functional annotation of a piece of code in a logic description language: and searching in the identification database according to preset rule information to obtain three identifications of the insurance beneficiary as characteristic identifications of the object in the business application scene.

A service logic typically comprises a plurality of service execution steps, so a logic description language may be composed of at least one instruction block for describing the respective service execution steps. Each instruction chunk is the basic unit of a logic description language. An instruction chunk is a series of instructions organized together for use as one independent command. For example, if the logical description language employed is pseudo code, then the chunks of instructions are macros in the pseudo code.

There may also be some comments between different instruction blocks. For example, "//" is used for row annotation, "///" is used for block annotation; a line annotation is an annotation that has only one line, and a block annotation is an annotation that includes multiple lines. "/" is the beginning of the note, the line note has only one line; "/", contains multiple lines of annotation statements, and block annotations contain multiple lines of annotation statements.

There may also be a code segment between the instruction chunks or annotations, the code segment comprising at least one line of code. The code segment directly parsed from the logic description language is referred to as an original code segment for distinguishing from a code segment subsequently converted from the instruction chunk.

Because the original code segment is formed by the code, the conversion is not needed; and the comments in the logic description language can also be used for explaining the purpose or meaning of the code, so that the original code segment and the comments can not be converted any more, but can be directly determined as the code and directly output for being combined with the code converted by the instruction block later.

In some embodiments, the logic description language can distinguish and mark each description unit by a specified identifier, so that the logic description language can be resolved into a plurality of description units distinguished and marked by the specified identifier according to the specified identifier contained in the logic description language.

There may be at least one specified identity, for example, the annotation may be a plurality of lines of pseudo code within "//", or may be a single line of pseudo code beginning with "//"; while instruction chunks (i.e., macros in the pseudo-code) may be marked with a particular identification different from the comments, for example, may be marked with brackets "[ ]", such that a pseudo-code line within a bracket "[ ]" corresponds to an instruction chunk.

Pseudo-code format of the function, for example:

search (F, name)// parameter type may not be given, but must be accounted for in the notation.

S30, aiming at the instruction chunk, converting the instruction chunk into a target source code segment based on a conversion rule corresponding to the chunk name of the instruction chunk; the target source code fragment is described in a computer programming language. The target source code section may include a target code section and an annotation.

Different types of instruction chunks may respectively correspond to different conversion rules, and based on the conversion rules corresponding to the instruction chunks, the instruction chunks may be converted into corresponding code segments.

Comments and/or codes can also be included in one instruction block, and the comments and/or codes in the instruction block can be directly output, that is, conversion rules corresponding to the comments or codes in the instruction block can be directly output without conversion, and for other parameters except the codes and comments, the parameters can be converted into codes according to the conversion rules corresponding to the parameters.

The pseudo code may include macros, original source code, and annotations, while the original source code may include plain text and/or character strings. The macros may include user macros and system macros.

According to a preset pseudo code specification, the structure relation of a functional module, a pseudo code operator, a special character and a data structure in the pseudo code specification are respectively and correspondingly converted into a function call, a reloadable operator, the special character and the data structure of a computer programming language.

The pseudo-code specification may include, for example: variable declaration rules, instruction representation rules, expression forms, assignment statement formats, sequential structure forms, selection structure forms, loop structure forms, and the like.

In the pseudo code specification, the expression can comprise an arithmetic expression and a logic expression; the arithmetic expression may use the usual arithmetic operators (+, -, +,/, and ^ indicating the power). The logical expression may use the relational operators ═ ≠, < >, ≦ and ≧ and, or (or), not (not).

And S40, combining and splicing the annotation, the original source code and the target source code segment to obtain a code set corresponding to the logic description language.

Specifically, when the annotations, the original code segments, and the target source code segments are combined and spliced, the annotations, the original source code, and the target source code segments may be sequentially spliced to obtain a code set according to an order of the annotations, the original code, and the instruction chunks converted into the annotations or the target source code in the logic description language. For example, the original source code or target source code segments corresponding to the service execution steps are spliced according to the sequence of the service execution steps, and comments for explaining each line code or each code segment are placed behind the corresponding code or code segment to explain the corresponding code or code segment, so as to obtain the code set corresponding to the logic description language.

In some embodiments, the obtaining method may further include: and saving the code set obtained by the conversion of the logic description language into a file to obtain a source file.

According to the method for acquiring the service logic code set of the insurance service, the service identifications can be combined and matched aiming at different objects according to the service application scene of the insurance service to generate the service logic, wherein each service identification comprises a characteristic identification, the objects and the service logic can be decoupled, the service logic can be quickly and accurately updated when the service application scene is changed, meanwhile, the logic description language is automatically converted into the codes, professional technicians do not need to manually write the codes, the labor cost is reduced, the complexity of the code generating process is also reduced, the code generating efficiency is improved, the working efficiency is improved, and the requirements of practical application can be completely met.

As shown in fig. 4, another embodiment of the present application provides an apparatus for acquiring a service logic code set of an insurance service, including:

In one embodiment, the obtaining module obtains service logic based on the service application scenario of the insurance service, and includes:

In an embodiment, the performing combined matching on the one or more service identifiers includes performing combined matching on the one or more service identifiers by using a combined matching manner of intersection, mutual exclusion, or union.

In an embodiment, the determining, when the service application scenario changes, one or more feature identifiers that need to be changed includes: when the service application scene is changed, determining one or more feature identifiers needing to be deleted;

In an embodiment, the determining, when the service application scenario changes, one or more feature identifiers that need to be changed includes: when the service application scene is changed, determining one or more feature identifiers needing to be added;

In one embodiment, a computer device is proposed, the computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:

In one embodiment, the obtaining of the service logic based on the service application scenario of the insurance service executed by the processor includes:

In one embodiment, the obtaining, by the processor, one or more feature identifiers of the target object from a preset identifier database includes:

In one embodiment, the performing, by the processor, a combined matching on the one or more service identities includes performing a combined matching on the one or more service identities by using an intersection, mutual exclusion, or union combined matching manner.

In one embodiment, before the performing, by the processor, the combined matching on the one or more service identifiers, the obtaining a service logic based on a service application scenario of the insurance service further includes:

In one embodiment, the determining, by the processor, one or more feature identifiers that need to be changed when the business application scenario is changed includes: when the service application scene is changed, determining one or more feature identifiers needing to be deleted;

In one embodiment, the determining, by the processor, one or more feature identifiers that need to be changed when the business application scenario is changed includes: when the service application scene is changed, determining one or more feature identifiers needing to be added;

Fig. 5 is a schematic diagram showing an internal structure of the computer device in one embodiment. As shown in fig. 5, the computer device includes a processor, a non-volatile storage medium, a memory, and a network interface connected through a system bus. The non-volatile storage medium of the computer device stores an operating system, a database and computer readable instructions, the database may store control information sequences, and the computer readable instructions, when executed by the processor, may cause the processor to implement the above method for acquiring a service logic code set of an insurance service. The processor of the computer device is used for providing calculation and control capability and supporting the operation of the whole computer device. The memory of the computer device may have stored therein computer readable instructions which, when executed by the processor, may cause the processor to perform a method of acquiring a set of business logic codes for an insurance service. The network interface of the computer device is used for connecting and communicating with the terminal. Those skilled in the art will appreciate that the architecture shown in fig. 5 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

The computer device provided by the embodiment of the present application and the method for acquiring the service logic code set of the insurance service provided by the embodiment of the present application have the same inventive concept and have the same beneficial effects as the method adopted, operated or implemented by the computer device.

In one embodiment, a storage medium is provided that stores computer-readable instructions that, when executed by one or more processors, cause the one or more processors to perform the steps of:

As shown in fig. 6, the storage medium is an optical disc 20, on which computer readable instructions are stored, and when the computer readable instructions are executed by a processor, the method for acquiring the service logic code set of the insurance service provided by any of the foregoing embodiments is executed.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the computer program is executed. The storage medium may be a non-volatile storage medium such as a magnetic disk, an optical disk, a Read-Only Memory (ROM), or a Random Access Memory (RAM).

The storage medium storing the computer readable instructions provided by the above embodiments of the present application and the method provided by the embodiments of the present application have the same advantages as the method adopted, executed or implemented by the application program stored in the storage medium.

The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. A method for acquiring a service logic code set of insurance service is characterized by comprising the following steps:

2. The method for acquiring a service logic code set of an insurance service according to claim 1, wherein the acquiring a service logic based on a service application scenario of the insurance service includes:

3. The method for obtaining the set of business logic codes of insurance service according to claim 2, wherein said obtaining one or more feature identifiers of the target object from a preset identifier database comprises:

4. The method for acquiring a service logic code set of an insurance service according to claim 2, wherein the performing a combined matching on the one or more service identities includes performing a combined matching on the one or more service identities by using a combined matching method of intersection, mutual exclusion, or union.

5. The method for acquiring a service logic code set of an insurance service according to claim 2, wherein before the step of performing the combination matching on the one or more service identifiers, the step of acquiring a service logic based on a service application scenario of the insurance service further comprises:

6. The method for acquiring a service logic code set of an insurance service according to claim 5, wherein the determining one or more feature identifiers that need to be changed when the service application scenario changes includes: when the service application scene is changed, determining one or more feature identifiers needing to be deleted;

7. The method for acquiring a service logic code set of an insurance service according to claim 5, wherein the determining one or more feature identifiers that need to be changed when the service application scenario changes includes: when the service application scene is changed, determining one or more feature identifiers needing to be added;

8. An apparatus for acquiring a service logic code set of an insurance service, comprising:

9. A computer device comprising a memory and a processor, the memory having stored therein computer readable instructions which, when executed by the processor, cause the processor to perform the steps of the method of obtaining a set of business logic codes for an insurance service according to any one of claims 1 to 7.

10. A storage medium storing computer readable instructions which, when executed by one or more processors, cause the one or more processors to perform the steps of the method of obtaining a set of business logic codes for an insurance service according to any one of claims 1 to 7.