CN111832849A

CN111832849A - Business logic generation method and device, electronic equipment and computer readable medium

Info

Publication number: CN111832849A
Application number: CN201910297937.2A
Authority: CN
Inventors: 翟东波
Original assignee: Taikang Insurance Group Co Ltd
Current assignee: Taikang Insurance Group Co Ltd
Priority date: 2019-04-15
Filing date: 2019-04-15
Publication date: 2020-10-27

Abstract

The disclosure relates to a business logic generation method, a business logic generation device, an electronic device and a computer readable medium. The method comprises the following steps: acquiring at least one attribute tag of a target object from a tag library; acquiring at least one rule from a rule base based on a service scene; matching the at least one rule for each attribute tag to generate at least one service tag, wherein each service tag comprises one attribute tag; and performing combination matching on the at least one service label to generate at least one service logic. The business logic generation method, the business logic generation device, the electronic equipment and the computer readable medium can decouple the object from the business logic and quickly and accurately update the business logic when a business scene is changed.

Description

Business logic generation method and device, electronic equipment and computer readable medium

Technical Field

The present disclosure relates to the field of computer information processing, and in particular, to a method and an apparatus for generating business logic, an electronic device, and a computer-readable medium.

Background

With the development of internet technology, more and more enterprises develop services on the network, so that users can handle services at any time through the network. When transacting business for users, logical judgment is usually performed on target users through business logic written in advance, so as to realize intelligent business transaction. For example, in a business logic system of an aging institution (including an aging institution, a nursing home, a social welfare center, etc.), no matter internal business logic management is performed, and when external business logic is interacted, each region or institution defines a plurality of business logics for an object (which may be a specific client, an abstract service, or an attribute of an object) in the business logic management of the region or institution. Currently, a generation method of business logic is to define rules according to one or a combination of more specific attributes of an object, and the following defects exist in the prior art:

1. the attributes are not uniform from object to object, and the names or meanings are used confusingly.

2. Under different business scenarios, even if common attributes exist among objects, the rule definitions of the objects are still different.

3. Each business logic may contain one attribute, a combination of attributes, or a combination of attributes of an object. Therefore, when one of the attributes is changed, the combination of the attributes is simultaneously influenced, and further, the service scene to which the attribute or the attribute combination is applied is influenced.

In view of the above-mentioned drawbacks, when the service logic or the service scenario changes, the modification process of the service logic is very complicated, and the error rate is high.

Therefore, a new business logic generation method, apparatus, electronic device and computer readable medium are needed.

The above information disclosed in this background section is only for enhancement of understanding of the background of the disclosure and therefore it may contain information that does not constitute prior art that is already known to a person of ordinary skill in the art.

Disclosure of Invention

In view of this, the present disclosure provides a method and an apparatus for generating business logic, an electronic device, and a computer readable medium, which can decouple an object from the business logic and quickly and accurately update the business logic when a business scene changes.

Additional features and advantages of the disclosure will be set forth in the detailed description which follows, or in part will be obvious from the description, or may be learned by practice of the disclosure.

According to an aspect of the present disclosure, a method for generating business logic is provided, where the method includes: acquiring at least one attribute tag of a target object from a tag library; acquiring at least one rule from a rule base based on a service scene; matching the at least one rule for each attribute tag to generate at least one service tag, wherein each service tag comprises one attribute tag; and performing combination matching on the at least one service label to generate at least one service logic.

In an exemplary embodiment of the disclosure, the performing a combined match on the at least one business label to generate at least one business logic includes one or more of: performing identity matching on the at least one service label to generate at least one service logic; performing a difference matching on the at least one service label to generate at least one service logic; performing merging and matching on the at least one service label to generate at least one service logic; performing internal-exclusive matching on the at least one business label to generate at least one business logic; performing outer exclusion matching on the at least one service tag to generate at least one service logic; and mutually exclusive matching is carried out on the at least one service label so as to generate at least one service logic.

In an exemplary embodiment of the present disclosure, the method further comprises: when a service scene is changed, determining at least one attribute label needing to be deleted; and deleting at least one corresponding service label based on each attribute label needing to be deleted so as to generate at least one updated service label.

In an exemplary embodiment of the present disclosure, the method further comprises: when a service scene is changed, determining at least one attribute label needing to be added; matching the at least one rule for each attribute tag that needs to be added to generate an updated at least one business tag.

In an exemplary embodiment of the present disclosure, the method further comprises: and combining and matching the at least one updated service label to generate at least one updated service logic.

In an exemplary embodiment of the present disclosure, the method further comprises: extracting a label according to the attribute information of the object; and carrying out duplication elimination processing on the extracted tags to generate the tag library.

In an exemplary embodiment of the present disclosure, obtaining at least one attribute tag of a target object from a tag library includes: and determining at least one corresponding attribute tag in the tag library according to the rule information and the attribute information of the target object.

In an exemplary embodiment of the present disclosure, the method further comprises: and classifying the labels in the label library in different dimensions.

According to an aspect of the present disclosure, a business logic generating apparatus is provided, the apparatus including: the attribute tag module is used for acquiring at least one attribute tag of the target object from the tag library; the rule module is used for acquiring at least one rule from a rule base based on a service scene; a service tag module, configured to match the at least one rule for each attribute tag to generate at least one service tag, where each service tag includes one attribute tag; and the logic generation module is used for carrying out combination and matching on the at least one service label so as to generate at least one service logic.

According to an aspect of the present disclosure, an electronic device is provided, the electronic device including: one or more processors; storage means for storing one or more programs; when executed by one or more processors, cause the one or more processors to implement a method as described above.

According to an aspect of the disclosure, a computer-readable medium is proposed, on which a computer program is stored, which program, when being executed by a processor, carries out the method as set forth above.

According to the business logic generation method, the business logic generation device, the electronic equipment and the computer readable medium provided by some embodiments of the present disclosure, the attribute tag is obtained from the tag library and matched with the rule in the rule library to generate the business tag, thereby realizing the decoupling of the object attribute and the business logic; and generating service logic according to the combination matching of the service labels, wherein each service label comprises an attribute label. The service logic can be updated quickly and accurately when the service scene is changed.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The above and other objects, features and advantages of the present disclosure will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings. The drawings described below are merely some embodiments of the present disclosure, and other drawings may be derived from those drawings by those of ordinary skill in the art without inventive effort.

Fig. 1 is a schematic diagram of a business logic generation method shown according to the prior art.

FIG. 2 is a flow diagram illustrating a business logic generation method in accordance with an exemplary embodiment.

FIG. 3 is a schematic diagram illustrating a business logic generation method in accordance with an exemplary embodiment.

FIG. 4 is a schematic diagram illustrating a business logic generation method in accordance with an exemplary embodiment.

FIG. 5 is a flow chart illustrating a business logic generation method in accordance with another exemplary embodiment.

Fig. 6 is a schematic diagram of the matching scheme according to fig. 5.

FIG. 7 is a flow chart illustrating a business logic generation method in accordance with another exemplary embodiment.

FIG. 8 is a block diagram illustrating a business logic generation apparatus in accordance with an exemplary embodiment.

FIG. 9 is a block diagram illustrating an electronic device in accordance with an example embodiment.

FIG. 10 is a schematic diagram illustrating a computer-readable storage medium according to an example embodiment.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The same reference numerals denote the same or similar parts in the drawings, and thus, a repetitive description thereof will be omitted.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and so forth. In other instances, well-known methods, devices, implementations, or operations have not been shown or described in detail to avoid obscuring aspects of the disclosure.

The block diagrams shown in the figures are functional entities only and do not necessarily correspond to physically separate entities. I.e. these functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor means and/or microcontroller means.

The flow charts shown in the drawings are merely illustrative and do not necessarily include all of the contents and operations/steps, nor do they necessarily have to be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the actual execution sequence may be changed according to the actual situation.

It will be understood that, although the terms first, second, third, etc. may be used herein to describe various components, these components should not be limited by these terms. These terms are used to distinguish one element from another. Thus, a first component discussed below may be termed a second component without departing from the teachings of the disclosed concept. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.

It is to be understood by those skilled in the art that the drawings are merely schematic representations of exemplary embodiments, and that the blocks or processes shown in the drawings are not necessarily required to practice the present disclosure and are, therefore, not intended to limit the scope of the present disclosure.

In the business logic management scenario of the endowment organization, in the prior art, the business logic is mainly generated by combining one or more specific attributes as a main body, and a schematic diagram thereof is shown in fig. 1. The following disadvantages currently exist: the attributes of the objects are not uniform, and the names or meanings are disordered; when the common attributes of different objects are applied to different service scenes, the generation of service logics of the objects is different; when the business logic is updated, the updating mode is complex and is easy to make mistakes.

Taking residents who are objects in a certain endowment institution (i.e., the objects are people) as an example, the existing business logic generation method is as follows:

the attributes of the object include name, gender, household (home zone, non-home zone, home city), living care type (home care, institutional care), membership grade (VIP, class 1, class 2), payment type (bed fee, nursing fee, management fee).

Scene: the service of nursing care for the aged is enjoyed in the nursing institution, and nursing care fees (bed fees, nursing fees, management fees) need to be paid regularly.

Rule one is as follows: preferential for the person whose house mouth is the local area to enjoy the bed at the cost of 9

Rule two: the phone nursing fee aiming at the household with the local area and the VIP member enjoys 9-fold discount

Rule three: the family is the local area and is the VIP member, and when the living care type is the home care, the total cost is enjoyed by 9.5.

Rule four: … …

When the factors of the user interface are not considered in the service scene, the above rules need to be changed. When the rules are more, once the rules are omitted, errors can occur in payment, and the service progress is seriously influenced.

At present, no technical solution capable of coping with the above drawbacks exists.

In view of the defects in the prior art, the application provides a business logic generation method and a business logic generation device, and a label library is established; the concept of service labels is proposed; and generating business logic based on the combination matching mode of the business label.

FIG. 2 is a flow diagram illustrating a business logic generation method in accordance with an exemplary embodiment. The service logic generation method provided in the embodiment of the present invention may be executed by any electronic device with computing processing capability, for example, a user terminal and/or a server, which is not limited in this respect. The service logic generation method 20 provided by the embodiment of the present invention may include steps S202 to S208.

As shown in fig. 2, in step S202, at least one attribute tag of the target object is acquired from the tag library.

All tags of all objects can be stored in the tag library. For example, the objects may include a people object, a job object, an organization object, a service object, and the like. The attributes of the object may include, for example, basic information of a patient, medical record information, registered member information, payment information, name information of an organization, organization level, authority level information, and the like. Attributes with the same meaning of different objects or different attributes with the same meaning in the same object and only different expression modes can correspond to the same label in the label library. For example, the year of birth and age of the same person may correspond to the same tag in the tag library; as another example, the name of the patient and the name of the institution may correspond to the same label.

In one embodiment, at least one attribute tag corresponding to the target object in the tag library may be determined according to rule information and attribute information of the target object. The rule information is a rule related in a current service scene. For example, in the aforementioned example of paying care fees regularly for the aged, if the first to fourth rules relate to attributes such as family, member level, and living care type, the rules can be searched in the tag library according to the rule information to obtain the three tags of the residents whose objects are the aged care institutions as the attribute tags of the residents in the business scenario.

In one embodiment, when generating a tag library, a tag can be extracted according to attribute information of an object; and carrying out duplication elimination processing on the extracted tags to generate the tag library. Wherein all tags are stored in the tag library, i.e. the master data of the tags. And for a specific object, extracting partial tags from the main data of the tags according to the attributes of the specific object as attribute tags of the specific object.

By extracting and de-duplicating the attribute information of the object, the amount of tags can be reduced. For example, staff members in the a organization have 5 attributes, staff members with the same position in the B organization have 8 attributes, and staff members with the same position in the C organization have 10 attributes, and in order to meet the requirement in the prior art, 5+8+ 10-23 attributes need to be defined. In contrast, according to the method of the present embodiment, if 8 of the 10 attributes of the organization C have the same specific meaning as 8 attributes of the organization B (i.e. 8 attributes + 2 additional attributes), and 5 of the 8 attributes of the organization B have the same meaning as 5 of the organization a, 10 attributes are only needed to describe the attribute information of the staff member in the A, B, C organization. In the embodiment, the multiple attributes of different objects are extracted and deduplicated to form the tag library, so that uniform naming of the same attribute of different objects can be realized, and the tag storage capacity is reduced.

In one embodiment, the labels in the label library may be sorted in different dimensions. As shown in the above example, the name, gender and family are classified into basic information categories; the family care type (home care, institution care), the member level (VIP, type 1, type 2), and the payment type (bed fee, nursing fee, management fee) are divided into the payment type for the aged care institution; the medical insurance grade and the medical insurance payment age limit are divided into medical insurance sales classes, but the technical scheme of the application does not specially limit the division mode of the label dimension in the label library.

In step S204, at least one rule is obtained from a rule base based on the business scenario. Wherein, the rule base comprises a plurality of basic rules.

In the embodiment of the invention, various basic rules can be obtained by extracting the service scenes. Taking a business scenario of regular care fee payment in the endowment institution as an example, the rules are, for example, but not limited to, discount and discount of care fee, total fee full reduction, and the like.

In step S206, the at least one rule is matched for each attribute tag to generate at least one service tag, where each service tag includes one attribute tag.

For example, taking a business scenario of regular payment of nursing care fees in a nursing institution as an example, the attributes of the target object include a household (home zone, non-home zone, home city), a membership level (VIP, class 1, class 2), and a payment type (bed fee, nursing fee, management fee). The business scenario provides that the subject with the home zone and the VIP as the member level can enjoy the bed fee of 9. Accordingly, one rule extracted from the rule base is: the bed cost is 9 folds. Matching the rule for the family and member levels respectively based on the rule information to obtain two service labels: the family port is the subject in the local area and enjoys the bed fee of 9, and the subject with the member level of VIP enjoys the bed fee of 9.

In step S208, the at least one service label is combined and matched to generate at least one service logic.

As described in S206 by way of example, to implement the rule: the subject with the home zone and the VIP member level can enjoy the bed fee of 9 folds, and the two service tags can be matched in an identity mode, namely, only the overlapped part of the two service tags is effective when the two service tags are simultaneously applied. The combination matching method is not limited to the same matching, and may be, for example, matching methods such as exclusive or, union, inner exclusion, outer exclusion, and mutual exclusion. The specific combination matching method can be seen in fig. 2.

In one embodiment, at least one attribute tag that needs to be deleted may be determined upon a change in a business scenario; and deleting at least one corresponding service label based on each attribute label needing to be deleted so as to generate at least one updated service label. Taking a service scene of regular payment of nursing fees in the endowment institution as an example, when the service scene does not need to consider the family opening, the service label corresponding to the family opening is deleted.

In one embodiment, at least one attribute tag that needs to be added may be determined when a business scenario changes; matching the at least one rule for each attribute tag that needs to be added to generate an updated at least one business tag. Taking a business scenario of regular paying of nursing fees in a nursing institution as an example, when a subject with age greater than 70 needs to be added in the business scenario to enjoy bed fee 8 times, an attribute tag is added: age and generating a business label for the matching rule: the bed for people older than 70 years is paid 8 folds.

In one embodiment, the updated at least one business label may be subjected to combination matching to generate the updated at least one business logic. After the service tag is updated, in order to implement the change of the service scene, the updated at least one service tag needs to be combined and matched. For example, a business scenario in which a subject with an age greater than 70 is entitled to a bed fee of 8 and the attribute tag of the family is deleted is taken as an example, and the business scenario specifies a combination relationship in which a subject with an age greater than 70 is entitled to a bed fee of 8 and a subject with a member being a VIP is entitled to a bed fee of 9, i.e., when both are satisfied, only a subject with an age greater than 70 is entitled to a bed fee of 8. The two traffic labels are subject to intra-exclusive combined matching. A detailed description of the manner of combining matches is given in the embodiment described in fig. 2. Based on this, the method of the embodiment can realize the update of the service logic by adding and deleting the service tags of the designated attribute tags and recombining and matching.

According to the business logic generation method provided by the embodiment of the disclosure, different objects are abstracted into objects, and business tags are combined and matched to generate business logic, wherein each business tag comprises an attribute tag. The business logic generation method can decouple the object and the business logic, and can quickly and accurately update the business logic when the business scene is changed.

It should be clearly understood that this disclosure describes how to make and use particular examples, but the principles of this disclosure are not limited to any details of these examples. Rather, these principles can be applied to many other embodiments based on the teachings of the present disclosure.

FIG. 5 is a flow chart illustrating a business logic generation method in accordance with another exemplary embodiment. Fig. 6 is a schematic diagram of the matching scheme according to fig. 5.

As shown in fig. 5, in the embodiment of the present application, the step S208 may further include the following steps.

In step S2081, identity matching is performed on the at least one service tag to generate at least one service logic. The identity matching means that only the overlapping part of at least one service label is valid when applied simultaneously. For example, taking a service scenario in which nursing fees are paid periodically in a nursing institution as an example, the service tag includes: the household opening is the subject of the local area to enjoy the bed with 8 folds of cost; the type of care is that the subject being cared for by the institution enjoys a bed fee of 8. And if the two service tags are matched, the matching result is as follows: the family is the subject of this district and care type for the institutional care can enjoy the bed position and spend 8.

In step S2082, performing an exclusive matching on the at least one service tag to generate at least one service logic. The differential matching means that only the non-overlapping part of at least one service label is valid when applied simultaneously. For example, when two service tags listed in S141 are matched differently, the matching result is: the subject whose house is not the local area and whose care type is the institution care enjoys the bed fee of 8 folds, and the subject whose house is not the local area and whose care type is the institution care enjoys the bed fee of 8 folds.

In step S2083, the at least one service tag is subjected to merging and matching to generate at least one service logic. The matching means that at least one service label is all valid when applied simultaneously. For example, when two service tags listed in S141 are found and matched, the matching result is: the household is a subject in the local area or the care type is the nursing of the institution and enjoys the bed fee of 8.

In step S2084, performing inner-exclusion matching on the at least one service tag to generate at least one service logic. Internal exclusive matching means that at least one service tag is only partially valid when applied simultaneously. For example, when the two service tags listed in S2081 are matched with each other, the matching result is: the family is the local area and the subjects of nursing type non-institutional care enjoy the bed at a fee of 8.

In step S2085, performing outer exclusion matching on the at least one service tag to generate at least one service logic. An outer exclusion match means that at least one of the service tags is fully valid when applied simultaneously. For example, taking a service scenario in which nursing fees are paid periodically in a nursing institution as an example, the service tag includes: the house mouth is the subject in the area to enjoy nursing fee 8 times; the subject in the non-home area of the family enjoys 8 folds of the bed position fee. And if the two service tags are matched in exclusion mode, the matching result is as follows: the subject in the local area of the house enjoys 8-fold nursing fee, and the subject in the non-local area of the house does not enjoy any preference.

In step S2086, the at least one service tag is mutually exclusive matched to generate at least one service logic. Mutually exclusive matches mean that at least one service tag is invalid when applied simultaneously. For example, when two service tags listed in S2085 mutually exclusively match, the matching result is: no matter whether the mouth of the target subject is the home zone or not, the user does not enjoy 8 folds of the bed position nor 8 folds of the nursing cost. A schematic diagram of the combination matching manner mentioned in steps S2081 to S2086 is shown in fig. 6.

FIG. 7 is a flow chart illustrating a business logic generation method in accordance with another exemplary embodiment. The flow shown in fig. 7 is a description of a flow when the technical solution of the present application is applied to a scene in which nursing fees are periodically paid in a nursing institution.

Object: the label of the object of the resident of a certain endowment institution comprises name, gender, family (local area, non-local area, local city), living care type (home care, institution care), member level (VIP,1 type, 2 type), payment type (bed charge, nursing charge, management charge) and nursing grade (special level, 1 level, 2 level).

Service scene: in order to enjoy the care and care service in an institution, it is necessary to periodically pay care fees (80 yuan for bed, 100 yuan for care, and 10 yuan for management). The service scenario specifies: rule I, the subject whose house mouth is the local zone enjoys the preferential of 8 folds of the bed cost; rule two, the special preference of the household mouth of the local area is only limited to the type of institution care; rule three, VIP members enjoy the total cost by 8.5 points; rule four: when the living care type is home care, the care cost is 1.1 fold.

When the endowment institution A executes the payment calculation logic of endowment nursing fees, only rules one, three and four are supported according to the actual situation, and only rule four is effective when rule three is matched with rule four, and rule one is solved and matched with rule three.

In step S702, according to the business scenario specification, the attribute tags of the target residents are extracted: family, type of care of living, membership level.

In step S704, a plurality of rules are extracted according to the business scenario: the bed cost is 8 folds; the total cost is 8.5 folds; the nursing cost is 1.1.

In step S706, at least one rule is matched for each extracted attribute tag to generate a plurality of service tags. The service labels are as follows:

a first service label: the expense for the subject bed in the home zone is 8;

and a second service label: the total cost of the VIP member is 8.5 points;

and a third service label: the residential care type is subject care cost 1.1 fold for home care.

In step S740, the plurality of service tags are combined and matched to generate a service logic. According to the service scene, solving and matching the service label I and the service label III; and the business label three is rejected from the business label two.

According to the service logic in step S708, the attribute tag of the client a1 takes the following values: the family mouth, the family nursing, VIP member of this district. When the customer A1 pays, the nursing fee (the bed fee 80 Yuan 8 Yuan + the nursing fee 100 Yuan 1.1 Yuan + the management fee 10 Yuan)

The client a2 attribute label takes the values: the family mouth, the institution nursing, the VIP member of this district. Then the customer a2 pays, and the care fee for the aged (bed fee 80 yuan +8 yuan + 100 yuan +10 yuan + management fee) 8.5.

In another endowment institution B, the supporting rule I, the rule II, the rule III and the rule IV are determined according to specific conditions. And matching the rule I and the rule II. And only rule three is effective if rule one and rule three match.

The attribute tags are: family, type of care of living, membership level.

The various rules are: the bed cost is 8 folds; the total cost is 8.5 folds; the nursing cost is 1.1.

The service label generated according to the service scene is as follows:

a first service label: the expense for the subject bed in the home zone is 8;

and a second service label: the bed cost of the subject of the institution nursing is 8 folds;

and a third service label: the total cost of the VIP member is 8.5 points;

and a service label four: the residential care type is subject care cost 1.1 fold for home care.

According to the service scene, the identity matching is carried out on the service label I and the service label II; the business label three is internally exclusive of the business label one.

According to the above service logic, the attribute tag of the client B1 takes the following values: family, institution care, class 1 members in this area. Then the customer B1 pays the fee, which is the care fee for the aged (bed fee 80 x 8 x + care fee 100 x + management fee 10 x).

The client B2 attribute tag takes the values: family mouth, family nursing, class 1 member.

When the customer B2 pays, the nursing fee for old people is equal to (bed fee 80 Yuan + nursing fee 100 Yuan 1.1 discount + management fee 10 Yuan)

The client B3 attribute tag takes the values: the family mouth, the family nursing, VIP member of this district.

Then customer B3 pays, and the nursing fee for old people is (bed fee 80 yuan + nursing fee 100 yuan + 1.1 yuan + management fee 10 yuan) 8.5 yuan.

The client B4 attribute tag takes the values: the family mouth, the institution nursing, the VIP member of this district.

Then the customer B4 pays the fee, which is the aged care fee (bed fee 80 yuan + nursing fee 100 yuan + management fee 10 yuan) × 8.5.

In one embodiment, when the service scene of the endowment organization B does not consider the attribute tag account, the attribute tag account and the corresponding service tag one are deleted. And then the rest service labels are combined and matched to generate the updated service logic.

Those skilled in the art will appreciate that all or part of the steps implementing the above-described embodiments are implemented as computer programs executed by a central processing unit CPU. When executed by the CPU, performs the functions defined by the above-described methods provided by the present disclosure. The program may be stored in a computer readable storage medium, which may be a read-only memory, a magnetic or optical disk, or the like.

Furthermore, it should be noted that the above-mentioned figures are only schematic illustrations of the processes involved in the methods according to exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.

The following are embodiments of the disclosed apparatus that may be used to perform embodiments of the disclosed methods. For details not disclosed in the embodiments of the apparatus of the present disclosure, refer to the embodiments of the method of the present disclosure.

FIG. 8 is a block diagram illustrating a business logic generation apparatus in accordance with an exemplary embodiment. The business logic generating apparatus 80 may include: attribute tagging module 802, rules module 804, business tagging module 806, and logic generation module 808.

The attribute tag module 802 may be configured to retrieve at least one attribute tag of a target object from a tag library. In one embodiment, the attribute tag module 510 is configured to determine at least one attribute tag corresponding to the target object in the tag library according to the rule information and the attribute information of the target object.

The rules module 804 is configured to obtain at least one rule from a rule base based on a business scenario.

The service label module 806 is configured to match the at least one rule for each attribute label to generate at least one service label, where each service label includes one of the attribute labels.

The logic generating module 808 is configured to perform combination matching on the at least one service tag to generate at least one service logic.

In one embodiment, the logic generation module 808 is configured to perform identity matching on the at least one service tag to generate at least one service logic; performing a difference matching on the at least one service label to generate at least one service logic; performing merging and matching on the at least one service label to generate at least one service logic; performing internal-exclusive matching on the at least one business label to generate at least one business logic; performing outer exclusion matching on the at least one service tag to generate at least one service logic; and mutually exclusive matching is carried out on the at least one service label so as to generate at least one service logic.

In one embodiment, the service logic generating apparatus 80 further includes a service change module, configured to determine at least one attribute tag that needs to be deleted when a service scenario changes; and deleting at least one corresponding service label based on each attribute label needing to be deleted so as to generate at least one updated service label.

In one embodiment, the service change module is configured to determine at least one attribute tag that needs to be added when a service scenario changes; matching the at least one rule for each attribute tag that needs to be added to generate an updated at least one business tag.

In one embodiment, the logic generating module 808 is further configured to perform combination matching on the updated at least one service label to generate the updated at least one service logic.

In one embodiment, the business logic generating apparatus 80 further includes a tag generating module, configured to extract a tag according to the attribute information of the object; and carrying out duplication elimination processing on the extracted tags to generate the tag library.

In one embodiment, the tag generation module is further configured to classify the tags in the tag library in different dimensions.

According to the business logic generating device provided by the embodiment of the disclosure, different objects are abstracted into objects, and business tags are combined and matched to generate business logic, wherein each business tag comprises an attribute tag. The business logic generation method can decouple the object and the business logic, and can quickly and accurately update the business logic when the business scene is changed.

An electronic device 200 according to this embodiment of the present disclosure is described below with reference to fig. 9. The electronic device 200 shown in fig. 9 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 9, the electronic device 200 is embodied in the form of a general purpose computing device. The components of the electronic device 200 may include, but are not limited to: at least one processing unit 210, at least one memory unit 220, a bus 230 connecting different system components (including the memory unit 220 and the processing unit 210), a display unit 240, and the like.

Wherein the storage unit stores program code executable by the processing unit 210 to cause the processing unit 210 to perform the steps according to various exemplary embodiments of the present disclosure described in the above-mentioned electronic prescription flow processing method section of the present specification. For example, the processing unit 210 may perform the steps as shown in fig. 2, 5, 7.

The memory unit 220 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM)2201 and/or a cache memory unit 2202, and may further include a read only memory unit (ROM) 2203.

The storage unit 220 may also include a program/utility 2204 having a set (at least one) of program modules 2205, such program modules 2205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.

Bus 230 may be one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

The electronic device 200 may also communicate with one or more external devices 300 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 200, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 200 to communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 250. Also, the electronic device 200 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network such as the Internet) via the network adapter 260. The network adapter 260 may communicate with other modules of the electronic device 200 via the bus 230. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 200, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, or a network device, etc.) to execute the above method according to the embodiments of the present disclosure.

FIG. 10 schematically illustrates a computer-readable storage medium in an exemplary embodiment of the disclosure.

Referring to fig. 10, a program product 400 for implementing the above method according to an embodiment of the present disclosure is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present disclosure is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The computer readable storage medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable storage medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

The computer readable medium carries one or more programs which, when executed by a device, cause the computer readable medium to perform the functions of: acquiring at least one attribute tag of a target object from a tag library; acquiring at least one rule from a rule base based on a service scene; matching the at least one rule for each attribute tag to generate at least one service tag, wherein each service tag comprises one attribute tag; and performing combination matching on the at least one service label to generate at least one service logic.

Those skilled in the art will appreciate that the modules described above may be distributed in the apparatus according to the description of the embodiments, or may be modified accordingly in one or more apparatuses unique from the embodiments. The modules of the above embodiments may be combined into one module, or further split into multiple sub-modules.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.

Exemplary embodiments of the present disclosure are specifically illustrated and described above. It is to be understood that the present disclosure is not limited to the precise arrangements, instrumentalities, or instrumentalities described herein; on the contrary, the disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

In addition, the structures, the proportions, the sizes, and the like shown in the drawings of the present specification are only used for matching with the contents disclosed in the specification, so as to be understood and read by those skilled in the art, and are not used for limiting the limit conditions which the present disclosure can implement, so that the present disclosure has no technical essence, and any modification of the structures, the change of the proportion relation, or the adjustment of the sizes, should still fall within the scope which the technical contents disclosed in the present disclosure can cover without affecting the technical effects which the present disclosure can produce and the purposes which can be achieved. In addition, the terms "above", "first", "second" and "a" as used in the present specification are for the sake of clarity only, and are not intended to limit the scope of the present disclosure, and changes or modifications of the relative relationship may be made without substantial changes in the technical content.

Claims

1. A business logic generation method, comprising:

acquiring at least one attribute tag of a target object from a tag library;

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

matching the at least one rule for each attribute tag to generate at least one service tag, wherein each service tag comprises one attribute tag;

and performing combination matching on the at least one service label to generate at least one service logic.

2. The method of claim 1, wherein combinatorially matching the at least one business label to generate at least one business logic comprises one or more of:

performing identity matching on the at least one service label to generate at least one service logic;

performing a difference matching on the at least one service label to generate at least one service logic;

performing merging and matching on the at least one service label to generate at least one service logic;

performing internal-exclusive matching on the at least one business label to generate at least one business logic;

performing outer exclusion matching on the at least one service tag to generate at least one service logic;

and mutually exclusive matching is carried out on the at least one service label so as to generate at least one service logic.

3. The method of claim 1, further comprising:

when a service scene is changed, determining at least one attribute label needing to be deleted;

and deleting at least one corresponding service label based on each attribute label needing to be deleted so as to generate at least one updated service label.

4. The method of claim 1, further comprising:

when a service scene is changed, determining at least one attribute label needing to be added;

matching the at least one rule for each attribute tag that needs to be added to generate an updated at least one business tag.

5. The method of any of claims 3 or 4, further comprising:

and combining and matching the at least one updated service label to generate at least one updated service logic.

6. The method of claim 1, further comprising:

extracting a label according to the attribute information of the object;

and carrying out duplication elimination processing on the extracted tags to generate the tag library.

7. The method of claim 1, wherein obtaining at least one attribute tag of a target object from a tag library comprises:

and determining at least one corresponding attribute tag in the tag library according to the rule information and the attribute information of the target object.

8. The method of claim 6, further comprising:

and classifying the labels in the label library in different dimensions.

9. A business logic generation apparatus, comprising:

the attribute tag module is used for acquiring at least one attribute tag of the target object from the tag library;

the rule module is used for acquiring at least one rule from a rule base based on a service scene;

a service tag module, configured to match the at least one rule for each attribute tag to generate at least one service tag, where each service tag includes one attribute tag;

and the logic generation module is used for carrying out combination and matching on the at least one service label so as to generate at least one service logic.

10. An electronic device, comprising:

one or more processors;

storage means for storing one or more programs;

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-8.

11. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-8.