CN112950393A - Insurance business docking method and device, electronic equipment and readable storage medium - Google Patents
Insurance business docking method and device, electronic equipment and readable storage medium Download PDFInfo
- Publication number
- CN112950393A CN112950393A CN202110175196.8A CN202110175196A CN112950393A CN 112950393 A CN112950393 A CN 112950393A CN 202110175196 A CN202110175196 A CN 202110175196A CN 112950393 A CN112950393 A CN 112950393A
- Authority
- CN
- China
- Prior art keywords
- service
- data
- insurance
- interface
- intermediate state
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 60
- 238000003032 molecular docking Methods 0.000 title claims abstract description 52
- 238000012545 processing Methods 0.000 claims abstract description 38
- 230000008569 process Effects 0.000 claims abstract description 16
- 230000008878 coupling Effects 0.000 claims description 27
- 238000010168 coupling process Methods 0.000 claims description 27
- 238000005859 coupling reaction Methods 0.000 claims description 27
- 230000002159 abnormal effect Effects 0.000 claims description 15
- 230000015654 memory Effects 0.000 claims description 15
- 238000004590 computer program Methods 0.000 claims description 13
- 238000010586 diagram Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 6
- 238000012217 deletion Methods 0.000 description 3
- 230000037430 deletion Effects 0.000 description 3
- 238000013478 data encryption standard Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 241000208340 Araliaceae Species 0.000 description 1
- 235000005035 Panax pseudoginseng ssp. pseudoginseng Nutrition 0.000 description 1
- 235000003140 Panax quinquefolius Nutrition 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 238000009825 accumulation Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000007123 defense Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 235000008434 ginseng Nutrition 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/08—Insurance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2379—Updates performed during online database operations; commit processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
Abstract
The application is applicable to the technical field of computers, and provides an insurance service docking method and device, electronic equipment and a readable storage medium. The insurance service docking method comprises the following steps: receiving an interface calling instruction of a calling party, wherein the interface calling instruction comprises insurance company information, service information and an interface type; acquiring corresponding configuration information according to insurance company information, service information and interface types, and butting a corresponding insurance service interface according to the configuration information; acquiring service return data returned by an insurance service interface; if the intermediate state data exists in the service return data, judging whether the intermediate state data is deletable data or not according to the configuration information, wherein the intermediate state data refers to data which is generated in the logic processing process of the insurance service and represents the current state of the insurance service; and if the intermediate state data is deletable data, deleting the intermediate state data. The method provided by the application is not prone to making mistakes and can improve user experience.
Description
Technical Field
The present application belongs to the field of computer technologies, and in particular, to an insurance service docking method and apparatus, an electronic device, and a readable storage medium.
Background
With the popularization of the internet, more and more users choose to purchase insurance products on line. Therefore, the insurance brokerage company has brought on line the insurance business docking system. The insurance business docking system is also called as an insurance business gateway system and is used for receiving the business request of the user and docking the business request to the information system of the corresponding insurance company, so that the interconnection between the user and the insurance company is realized.
The insurance service docking system in the traditional technology is easy to generate errors, and the user experience is poor.
Disclosure of Invention
The application provides an insurance service docking method, an insurance service docking device, electronic equipment and a readable storage medium, which can solve the problem that an insurance service docking system is easy to generate errors.
In a first aspect, an embodiment of the present application provides an insurance service docking method, which includes:
receiving an interface calling instruction of a calling party, wherein the interface calling instruction comprises insurance company information, service information and an interface type;
acquiring corresponding configuration information according to the insurance company information, the service information and the interface type, and butting a corresponding insurance service interface according to the configuration information;
acquiring service return data returned by the insurance service interface;
if the service return data contains intermediate state data, judging whether the intermediate state data is deletable data or not according to the configuration information, wherein the intermediate state data is data which is generated in the logic processing process of the insurance service and represents the current state of the insurance service;
and if the intermediate state data is deletable data, deleting the intermediate state data.
In one embodiment, the method further comprises:
if the intermediate state data is non-deletable data, saving the intermediate state data or returning the intermediate state data to the caller.
In one embodiment, the method further comprises:
judging whether the insurance service interface has a coupling relation with other interfaces;
if yes, judging whether the coupling relation meets a release condition according to the configuration information and/or the service return data;
and if the coupling relation meets a releasing condition, releasing the coupling relation.
In one embodiment, the method further comprises:
judging whether the business return data returned by the insurance business interface is abnormal or not;
if the exception exists, processing the exception;
and if the exception handling fails, sending an alarm notice.
In one embodiment, the exception is a return data timeout, and the processing the exception includes:
acquiring unknown state data of the insurance service interface;
judging whether the unknown state data meets a deleting condition;
if the unknown state data meets the deleting condition, deleting the unknown state data;
and if the unknown state data does not meet the deleting condition, determining that the exception handling fails.
In one embodiment, the exception includes service error data in the service return data, and the processing the exception includes:
judging whether the number of the service error data exceeds a preset threshold value or not;
and if the abnormal processing fails to exceed the preset threshold, determining that the abnormal processing fails.
In one embodiment, the exception includes service error data in the service return data, and the processing the exception includes:
judging whether the service error data accords with a preset configuration rule or belongs to a white list according to the configuration information;
and if the service error data does not conform to the configuration rule and does not belong to the white list, determining that the exception handling fails.
In a second aspect, an embodiment of the present application provides an insurance service interfacing apparatus, including:
the instruction receiving module is used for receiving an interface calling instruction of a calling party, wherein the interface calling instruction comprises insurance company information, service information and an interface type;
the configuration information acquisition module is used for acquiring corresponding configuration information according to the insurance company information, the service information and the interface type and butting a corresponding insurance service interface according to the configuration information;
a return data acquisition module for acquiring the service return data returned by the insurance service interface;
the intermediate state processing module is used for judging whether the intermediate state data is deletable data or not according to the configuration information if the intermediate state data exists in the service return data, wherein the intermediate state data is data which is generated in the logic processing process of the insurance service and represents the current state of the insurance service; and if the intermediate state data is deletable data, deleting the intermediate state data.
In a third aspect, an embodiment of the present application provides an electronic device, including: a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the insurance service docking method of any one of the first aspect when executing the computer program.
In a fourth aspect, the present application provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program implements the insurance service docking method of any one of the first aspect.
According to the insurance service docking method, the insurance service docking device, the electronic equipment and the readable storage medium, when the intermediate state data exists in the service return data, whether the intermediate state data can be deleted is judged, and the intermediate state data can be deleted when the service data can be deleted, so that the independence of an insurance service interface is ensured, the coupling relation between the insurance service interface and other interfaces is reduced, the subsequent operation cannot be influenced by the error of one interface in an insurance service docking system, the service provided for a calling party is simple and reliable, the error is not easy to occur, and the user experience is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
Fig. 1 is a schematic view of an application scenario of an insurance service docking method according to an embodiment of the present application;
fig. 2 is a schematic flowchart of an insurance service docking method according to an embodiment of the present application;
fig. 3 is a schematic flow chart of an insurance service docking method according to another embodiment of the present application;
FIG. 4 is a flowchart illustrating an insurance service docking method according to another embodiment of the present application;
FIG. 5 is a schematic diagram of a software architecture of an insurance service docking system provided by an embodiment of the present application;
FIG. 6 is a schematic structural diagram of an insurance service docking device provided in an embodiment of the present application;
fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application 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 present application and are not intended to limit the present application.
It is to be understood that the terms "first," "second," "third," "fourth," and the like (if any) in the embodiments of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.
It is understood that the term "and/or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.
The insurance service docking method provided by the embodiment of the application can be applied to the application environment shown in fig. 1. The client device 102 may perform data interaction with the server 104 and the insurance broker company device 106, and the insurance broker company device 106 may also perform data interaction with the server 104. At the same time, the insurance broker 106 may interact with the insurance company equipment 108 for data. Wherein the insurance company device 106 may be provided with an insurance business docking system. The insurance company device 108 may be a plurality of devices, each of which is a device of a different insurance company. Each insurance company device 108 may be provided with an information system capable of interfacing with an insurance service interfacing system, and each information system may be provided with different insurance service interfaces (or referred to as insurance product interfaces) according to the difference of insurance services (or referred to as insurance products), such as an underwriting interface, or a status query interface.
The types of client devices 102, insurance broker equipment 106, and insurance company equipment 108 are not limited in this application, and may be, for example, portable, pocket, hand-held, computer-included, or vehicle-mounted devices. The type of the server 104 is not limited in the present application, and may be a physical server, a station group server, a high defense server, a cloud server, or the like.
The technical solution in the present application will be described in detail below with reference to the accompanying drawings. It should be noted that, in the present application, different technical features may be combined with each other without conflict.
Fig. 2 shows a schematic flow chart of an insurance service docking method provided by the present application. The embodiment of the present application is described by taking the method applied to the insurance brokerage equipment in fig. 1 as an example. As shown in fig. 2, the insurance service docking method provided in this embodiment may include:
s201, receiving an interface calling instruction of a calling party, wherein the interface calling instruction comprises insurance company information, service information and an interface type.
The caller is the device that calls the insurance service. The user selects the required insurance service through an application program or a webpage and the like, and the transmission of the interface calling instruction is realized. The insurance service docking system receives the call instruction. The call instruction may include, but is not limited to, insurance company information, business information, and interface type. The insurance company information means information of an insurance company to which the insurance service to be called belongs. The service information refers to the type of insurance service to be invoked, such as underwriting, refunding, intelligent underwriting or security, and the like. The Interface type refers to type information of an insurance service Interface to be called, and may include a docking type, for example, Application Programming Interface (API) docking or jump chain docking, etc.; interface configuration information may also be included, such as an interface key, an interface Uniform Resource Locator (URL), and the like.
S202, acquiring corresponding configuration information according to insurance company information, service information and interface types, and butting a corresponding insurance service interface according to the configuration information.
Specifically, the insurance broker company device receives the interface call instruction, and may store data such as insurance company information, service information, and interface types in a database of the Server, where the database may be a MySQL database, or a Remote Dictionary service (Redis) database. And matching the insurance company information, the service information and the interface type with the existing interface of the service docking system, and determining whether the insurance service interface to be docked is docked once. And if the insurance service interface to be butted is butted, directly reading the configuration information of the insurance service interface, generating an entry parameter according to the configuration information, and calling the corresponding insurance service interface according to the entry parameter. If the insurance service interface to be butted is not butted, the insurance service butting system is expanded firstly, information configuration is carried out, then the access parameter is generated according to the configuration information, and the insurance service interface is butted according to the access parameter. Optionally, the configuration information may include an insurance company configuration parameter (hereinafter referred to as a company configuration parameter) and an insurance service configuration parameter (hereinafter referred to as a service configuration parameter).
S203, acquiring service return data returned by the insurance service interface.
After the insurance business interface is connected, the information system of the insurance company carries out logic processing on the business and returns the business return data. The service return data includes, but is not limited to, service data required by the caller, execution result data, intermediate state data, and the like. The intermediate state data refers to data which is generated in the logic processing process of the insurance service and represents the current state of the insurance service. For example, if a calling party calls a premium service, assuming that the premium of a certain user is 100 ten thousand yuan, and after the calling party calls a premium of 20 ten thousand yuan for the first time, the user has a remaining premium of 80 ten thousand yuan, the calling premium service interface feeds back intermediate state data: the remaining balance is 80 ten thousand yuan. After the calling party calls the 30 ten thousand yuan of protection for the second time, if the user has 50 ten thousand yuan of protection, the calling and protecting business interface feeds back the intermediate state data: the remaining balance is 50 ten thousand yuan. It will be appreciated that depending on the type of service, some insurance service interfaces have intermediate status data in their return data and some do not.
And S204, if the intermediate state data exists in the service return data, judging whether the intermediate state data is deletable data or not according to the configuration information.
Also, it will be appreciated that some intermediate state interfaces may be deleted and some intermediate states may not be deleted depending on the insurance company and the particular business type. Specifically, which intermediate states are deletable and which intermediate states are not deletable may be preset according to the company configuration parameters and the service configuration parameters, and written in the configuration information of the interface. And when the intermediate state data exists in the service return data, judging whether the intermediate state data is deletable data or not according to the configuration information.
If the intermediate status data is deletable data, go to step S205;
if the intermediate state data is non-deletable data, executing step S206;
s205, deleting the intermediate state data;
and S206, saving the intermediate state data or returning the intermediate state data to the caller.
Specifically, for the intermediate state data needing to be stored, the intermediate state data can be stored in a database of a server, such as MySQL or Redis, for subsequent use; the field added by the output parameter can also be returned to the caller for storage, and the field can be carried when the subsequent interface is called.
In this embodiment, when the service return data has the intermediate state data, it is determined whether the intermediate state data can be deleted, and when the service data can be deleted, the intermediate state data is deleted, so that the independence of the insurance service interface is ensured, the coupling relationship between the insurance service interface and other interfaces is reduced, the subsequent operation of the insurance service docking system is not affected by an error of one interface, the service provided to the calling party is ensured to be simple and reliable, the error is not easy to occur, and the user experience is improved. Meanwhile, when the service data can not be deleted, the intermediate state data is stored or returned to the calling party, so that the integrity of the storage of the intermediate state data is ensured, and the normal calling of a subsequent interface is ensured.
For example, fig. 3 is a flowchart illustrating steps of acquiring corresponding configuration information according to insurance company information, service information, and an interface type, and interfacing a corresponding insurance service interface according to the configuration information in one embodiment. As shown in fig. 3, S202 may include:
s301, judging whether insurance companies to be docked are docked or not;
if the insurance companies to be docked are not already docked, executing step S302;
if the insurance companies to be docked are already docked, executing step S303;
s302, configuring insurance company parameters according to the insurance company information to obtain company configuration parameters;
s303, reading company configuration parameters of the insurance company;
s304, judging whether the insurance service to be butted is butted or not;
if the insurance service to be docked is not already docked, executing step S305;
if the insurance service to be docked is already docked, executing step S306;
s305, configuring insurance service parameters according to the service information to obtain service configuration parameters;
s306, reading the service configuration parameters of the insurance service;
s307, judging whether the insurance service interface to be butted is butted or not according to the interface type;
if the insurance service interface to be butted is not butted, executing step S308;
if the insurance service interface to be butted is butted, executing step S309;
s308, generating entry parameters according to the configured company configuration parameters and the configured service configuration parameters, and carrying out interface debugging on an insurance service interface according to the entry parameters;
s309, generating access parameters according to the read company configuration parameters and the read business configuration parameters, and connecting an insurance business interface according to the access parameters.
Optionally, the ginseng can be divided into two parts: a reference general field and a reference service field. The entry general field is general for all interfaces and can include information such as interface calling time, caller identity and the like. The participating business fields depend on company configuration information and interface configuration information, such as insurance company ID, business ID, order information, user information, applicant information, claim information, interface type, and the like. In short, the insurance service interface needing to be docked can be determined through the access parameter.
Optionally, the output parameter may include two parts: a general field for presence and a traffic field for presence. The presence fields are generic to all interfaces. The out-going services field may be determined by information returned by the insurance services interface of the insurance company, such as an insurance policy number returned by the insurance interface of the insurance company, or an insurance policy number returned by the insurance company's out-going services interface, and the like.
In one embodiment, the insurance docking system standardizes the access and the export of the parameters, receives an interface calling instruction of a calling party through a uniform interface, and uniformly acquires service return data returned by an insurance service interface. The method provided by the embodiment provides the encapsulated unified interface externally, simplifies the system complexity and improves the interface docking efficiency. Particularly, under the condition that nowadays insurance brokerage companies need to dock a large number of insurance companies and each insurance company provides multiple business interfaces, the interface docking process can be greatly simplified, and the docking efficiency is improved. In addition, the method provided by the embodiment processes details such as interface type difference, encryption and decryption mode difference and the like of an insurance company in the insurance docking system, ensures that a business side does not perceive the detail difference when calling the interface, and improves user experience. The interface type difference of the insurance companies is, for example, a difference between a HyperText Transfer Protocol (HTTP) interface and a Virtual Private Network (VPN) interface. The Encryption method difference is, for example, a difference between Data Encryption Standard (DES) Encryption and Advanced Encryption Standard (AES) Encryption.
In one embodiment, after the intermediate state data of the insurance service interface is processed, the coupling relationship of the insurance service interface can be further judged, and further decoupling is performed. Specifically, the method may further include:
judging whether the insurance service interface has a coupling relation with other interfaces; if so, judging whether the coupling relation meets the releasing condition or not according to the configuration information and/or the service return data; and if the coupling relation meets the releasing condition, releasing the coupling relation.
Whether the coupling relation can be released or not can be determined according to different service interfaces and the conditions of the interfaces coupled with the service interfaces. And judging whether the current coupling relation meets the release condition or not according to the configuration information or the service return data or the configuration information and the service return data. If the coupling relation can be removed, the coupling relation is removed, the independence of the insurance service interface is further ensured, other operations of the user are prevented from being influenced when the insurance service interface is in error, system errors are reduced, user experience is improved, and customer service pressure can be reduced.
In addition, in practical application, in the insurance service interface calling process, since the calling link is long and part of the service logic itself is complex, various problems may occur to the insurance service interface returned data, including but not limited to timeout, service error or service error, and the like, that is, an exception occurs to the returned data timeout, the service returned data includes service error data or the service returned data includes service error data. The returned data overtime exception means that no service returned data is returned within a preset time length. The service error reporting data refers to error data caused by abnormality of an information system of the insurance company. The service error reporting data refers to abnormal or error data occurring in the service logic processing process.
In view of this, the embodiments of the present application further provide a method for handling an exception in an interface call process. The method further comprises:
judging whether the returned service data of the insurance service interface is abnormal or not; if the exception exists, processing the exception; and if the exception handling fails, sending an alarm notice.
For example, fig. 4 shows a possible implementation manner of handling an insurance service interface exception in an embodiment, and as shown in fig. 4, the method may include:
s401, judging whether the returned service data returned by the insurance service interface is overtime;
if yes, executing step S402;
if not, go to step S406;
s402, acquiring unknown state data of an insurance service interface;
specifically, the unknown state data refers to data generated by an insurance service interface due to the fact that the returned data is overtime, and the state of the data is uncertain. It can be understood that the unknown state data is data generated when the returned service return data is abnormal, and does not belong to the service return data.
S403, judging whether the unknown state data meets a deleting condition;
if the unknown state data meets the deletion condition, executing step S404;
if the unknown state data does not satisfy the deletion condition, determining that the exception handling fails, and executing step S405;
s404, deleting unknown state data;
s405, sending an alarm notification;
for example, some insurance companies' underwriting interfaces take up risk guarantees. If the risk guarantee is not deleted, the user may have an over-limit error in the follow-up underwriting. And the return data is over time to cause state uncertainty, and the risk guarantee amount may be occupied at the insurance company side or not. Therefore, after the returned data of the underwriting interface is overtime, the interface for deleting the risk quota can be called for one time to delete the risk quota. However, there may be two situations for an insurance company: if the underwriting is successful, the risk quota can be deleted; if the underwriting fails, the risk quota cannot be deleted. Thus, it may be determined whether the current risk guarantee satisfies the deletion condition based on the underwriting result. If the data cannot be deleted, the abnormal processing is determined to fail, namely the unknown state data cannot be deleted, the system is in an unknown state, and an alarm notice needs to be sent in time for manual processing.
S406, judging whether the service return data comprises service error data;
if the returned data includes service error data, executing step S407;
if the returned data does not include the service error data, executing step S408;
s407, judging whether the number of the service error data exceeds a preset threshold value;
if the number of the service error data does not exceed the preset threshold, the current service error report is considered not to influence the normal service, and the service error data is ignored;
if the number of the service error data exceeds the preset threshold, determining that the exception handling fails, and executing step S405;
s408, judging whether the service return data comprises service error data or not;
if the returned data includes the service error data, executing step S409;
if the returned data does not include the service error data, determining that the insurance service interface is not abnormal;
s409, judging whether the service error data accords with a preset configuration rule or not according to the configuration information;
if the service error data conforms to the preset configuration rule, determining that the service error data is normal service data, and executing step S410;
if the service error data does not conform to the preset configuration rule, determining that exception handling fails, and executing step S405;
s410, judging whether the service error data belong to a white list;
if the service error data belong to the white list, determining the service error data as normal service data, and not processing the service error data;
if the service error data does not belong to the white list, it is determined that the exception handling fails, and step S405 is executed.
In this embodiment, by determining whether the insurance service interface returns the service return data, an exception is handled when the exception exists. Therefore, various exceptions generated in the interface docking process are subjected to internal packaging processing, the probability of exposing the exceptions to users is reduced, and user experience is improved. Meanwhile, in the exception handling process, if the exception handling fails, an alarm notice is sent, manual intervention is conducted in time, accumulation of problems is avoided, exceptions are solved in time, and user experience is further improved.
By way of example, FIG. 5 illustrates a software architecture diagram of an insurance service docking system in one embodiment. As shown in fig. 5, the insurance service docking system may include an access layer, a configuration layer, a service logic layer, and a gateway layer. The access layer comprises modules such as an underwriting module, a refunding module, an underwriting module and the like. The configuration layer may include modules for insurance company configuration, business configuration, and the like. The insurance company configuration module may be configured to implement the company configuration information obtaining function in the above embodiments, and the service configuration module may be configured to implement the service configuration information obtaining function. The business logic layer can comprise modules of rule pre-verification, default value processing, associated system calling, exception warning, coupling relation processing and the like. The gateway layer may include modules for encryption and decryption processing, interface calls, and the like. The abnormal alarm module may be configured to implement the alarm notification sending function in the foregoing embodiments. The coupling relation processing module may be configured to implement the functions of determining and releasing the coupling relation, deleting the intermediate state data, and the like in the foregoing embodiments.
The access layer of the insurance service docking system receives a calling instruction input by a calling party through a uniform internal service interface, and the internal service interface can comprise modules of underwriting, refunding, underwriting and the like. Meanwhile, the insurance business docking system docks with each insurance business interface of the insurance company information system, such as an insurance company interface a, an insurance company interface B, and the like in fig. 5.
As is apparent from fig. 5, the insurance service docking system shields differences and details between insurance companies through standardized interfaces for insurance services of different insurance companies, so that a caller only concerns the logic of the service itself, thereby significantly improving efficiency when docking the service interfaces of the insurance companies.
Fig. 6 shows a block diagram of an insurance service docking apparatus provided in an embodiment of the present application. As shown in fig. 5, the insurance service interfacing apparatus provided in this embodiment may include:
the instruction receiving module 601 is configured to receive an interface call instruction of a calling party, where the interface call instruction includes insurance company information, service information, and an interface type;
a configuration information obtaining module 602, configured to obtain corresponding configuration information according to the insurance company information, the service information, and the interface type, and interface a corresponding insurance service interface according to the configuration information;
a return data obtaining module 603, configured to obtain service return data returned by the insurance service interface;
an intermediate state processing module 604, configured to determine whether the intermediate state data is deletable data according to the configuration information if the service return data includes intermediate state data, where the intermediate state data is data that is generated by an insurance service in a logic processing process and represents a current state of the insurance service; and if the intermediate state data is deletable data, deleting the intermediate state data.
In one embodiment, the intermediate state processing module 604 is further configured to save the intermediate state data or return the intermediate state data to the caller if the intermediate state data is non-deletable data.
In one embodiment, the insurance service interfacing apparatus further includes a coupling processing module 605, configured to determine whether the insurance service interface has a coupling relationship with other interfaces; if yes, judging whether the coupling relation meets a release condition according to the configuration information and/or the service return data; and if the coupling relation meets a releasing condition, releasing the coupling relation.
In one embodiment, the insurance service interfacing apparatus further includes an exception handling module 606, configured to determine whether the service return data returned by the insurance service interface is abnormal; if the exception exists, processing the exception; and if the exception handling fails, sending an alarm notice.
In one embodiment, the exception handling module 606 is further configured to obtain unknown status data of the insurance service interface; judging whether the unknown state data meets a deleting condition; if the unknown state data meets the deleting condition, deleting the unknown state data; and if the unknown state data does not meet the deleting condition, determining that the exception handling fails.
In one embodiment, the exception handling module 606 is further configured to determine whether the number of service error data exceeds a preset threshold; and if the abnormal processing fails to exceed the preset threshold, determining that the abnormal processing fails.
In an embodiment, the exception handling module 606 is further configured to determine, according to the configuration information, whether the service error data conforms to a preset configuration rule or belongs to a white list; and if the service error data does not conform to the configuration rule and does not belong to the white list, determining that the exception handling fails.
The insurance service docking device provided in this embodiment is used to execute the insurance service docking method provided in the embodiment of the method of the present application, and the technical principle and technical effect are similar, which may be specifically referred to a part of the embodiment of the method and will not be described herein again.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
The embodiment of the application also provides the electronic equipment. For example, fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application. As shown in fig. 7, the electronic device 7 may include: a processor 70, a memory 71 and a computer program 72 stored in the memory 71 and operable on the processor 70, the steps of any of the above-described embodiments of the insurance service docking method being implemented when the computer program 72 is executed by the processor 70. The number and type of the processors 70 and the memories 71 are not limited in the embodiment of the present application.
The embodiment of the present application does not limit the type of the electronic device 7. For example, the computing device may be a desktop computer, a notebook, a palm top computer, a cloud server, and the like.
Embodiments of the present application further provide a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program can implement the steps in any of the above method embodiments.
It will be appreciated by those of ordinary skill in the art that any reference to memory, storage, databases, or other media used in the embodiments provided herein may include non-volatile and/or volatile memory. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. An insurance service docking method, comprising:
receiving an interface calling instruction of a calling party, wherein the interface calling instruction comprises insurance company information, service information and an interface type;
acquiring corresponding configuration information according to the insurance company information, the service information and the interface type, and butting a corresponding insurance service interface according to the configuration information;
acquiring service return data returned by the insurance service interface;
if the service return data contains intermediate state data, judging whether the intermediate state data is deletable data or not according to the configuration information, wherein the intermediate state data is data which is generated in the logic processing process of the insurance service and represents the current state of the insurance service;
and if the intermediate state data is deletable data, deleting the intermediate state data.
2. The method of claim 1, further comprising:
if the intermediate state data is non-deletable data, saving the intermediate state data or returning the intermediate state data to the caller.
3. The method of claim 1, further comprising:
judging whether the insurance service interface has a coupling relation with other interfaces;
if yes, judging whether the coupling relation meets a release condition according to the configuration information and/or the service return data;
and if the coupling relation meets a releasing condition, releasing the coupling relation.
4. The method according to any one of claims 1 to 3, further comprising:
judging whether the business return data returned by the insurance business interface is abnormal or not;
if the exception exists, processing the exception;
and if the exception handling fails, sending an alarm notice.
5. The method of claim 4, wherein the exception is a return data timeout, and wherein handling the exception comprises:
acquiring unknown state data of the insurance service interface;
judging whether the unknown state data meets a deleting condition;
if the unknown state data meets the deleting condition, deleting the unknown state data;
and if the unknown state data does not meet the deleting condition, determining that the exception handling fails.
6. The method of claim 4, wherein the exception includes service error data in the service return data, and wherein the processing the exception comprises:
judging whether the number of the service error data exceeds a preset threshold value or not;
and if the abnormal processing fails to exceed the preset threshold, determining that the abnormal processing fails.
7. The method of claim 4, wherein the exception includes service error data in the service return data, and wherein the processing the exception comprises:
judging whether the service error data accords with a preset configuration rule or belongs to a white list according to the configuration information;
and if the service error data does not conform to the configuration rule and does not belong to the white list, determining that the exception handling fails.
8. An insurance service docking apparatus, comprising:
the instruction receiving module is used for receiving an interface calling instruction of a calling party, wherein the interface calling instruction comprises insurance company information, service information and an interface type;
the configuration information acquisition module is used for acquiring corresponding configuration information according to the insurance company information, the service information and the interface type and butting a corresponding insurance service interface according to the configuration information;
a return data acquisition module for acquiring the service return data returned by the insurance service interface;
the intermediate state processing module is used for judging whether the intermediate state data is deletable data or not according to the configuration information if the intermediate state data exists in the service return data, wherein the intermediate state data is data which is generated in the logic processing process of the insurance service and represents the current state of the insurance service; and if the intermediate state data is deletable data, deleting the intermediate state data.
9. An electronic device, comprising: memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the method according to any of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, implements the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110175196.8A CN112950393A (en) | 2021-02-09 | 2021-02-09 | Insurance business docking method and device, electronic equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110175196.8A CN112950393A (en) | 2021-02-09 | 2021-02-09 | Insurance business docking method and device, electronic equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112950393A true CN112950393A (en) | 2021-06-11 |
Family
ID=76244424
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110175196.8A Pending CN112950393A (en) | 2021-02-09 | 2021-02-09 | Insurance business docking method and device, electronic equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112950393A (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104615759A (en) * | 2015-02-13 | 2015-05-13 | 厦门雅迅网络股份有限公司 | Data synchronization method for different business system platforms |
| CN107657538A (en) * | 2017-10-12 | 2018-02-02 | 中国平安人寿保险股份有限公司 | Insure method, terminal of insuring, insurance server and computer-readable recording medium |
| CN110187993A (en) * | 2019-05-14 | 2019-08-30 | 广州欧科信息技术股份有限公司 | A kind of processing method of misoperation, system, electronic equipment and storage medium |
| CN110351342A (en) * | 2019-06-20 | 2019-10-18 | 平安科技（深圳）有限公司 | Service order processing method, device, computer equipment and storage medium |
| CN111143087A (en) * | 2019-12-18 | 2020-05-12 | 中国平安财产保险股份有限公司 | Interface calling method and device, storage medium and server |
| CN111445344A (en) * | 2020-04-21 | 2020-07-24 | 重庆新致金服信息技术有限公司 | Insurance business list processing method, electronic equipment and storage medium |
| CN111538779A (en) * | 2020-03-25 | 2020-08-14 | 平安健康保险股份有限公司 | Incremental data synchronization method and device, computer equipment and storage medium |
| CN111626865A (en) * | 2020-05-22 | 2020-09-04 | 泰康保险集团股份有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN111651284A (en) * | 2020-05-25 | 2020-09-11 | 泰康保险集团股份有限公司 | Method, device, system and storage medium for processing service data |
-
2021
- 2021-02-09 CN CN202110175196.8A patent/CN112950393A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104615759A (en) * | 2015-02-13 | 2015-05-13 | 厦门雅迅网络股份有限公司 | Data synchronization method for different business system platforms |
| CN107657538A (en) * | 2017-10-12 | 2018-02-02 | 中国平安人寿保险股份有限公司 | Insure method, terminal of insuring, insurance server and computer-readable recording medium |
| CN110187993A (en) * | 2019-05-14 | 2019-08-30 | 广州欧科信息技术股份有限公司 | A kind of processing method of misoperation, system, electronic equipment and storage medium |
| CN110351342A (en) * | 2019-06-20 | 2019-10-18 | 平安科技（深圳）有限公司 | Service order processing method, device, computer equipment and storage medium |
| CN111143087A (en) * | 2019-12-18 | 2020-05-12 | 中国平安财产保险股份有限公司 | Interface calling method and device, storage medium and server |
| CN111538779A (en) * | 2020-03-25 | 2020-08-14 | 平安健康保险股份有限公司 | Incremental data synchronization method and device, computer equipment and storage medium |
| CN111445344A (en) * | 2020-04-21 | 2020-07-24 | 重庆新致金服信息技术有限公司 | Insurance business list processing method, electronic equipment and storage medium |
| CN111626865A (en) * | 2020-05-22 | 2020-09-04 | 泰康保险集团股份有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN111651284A (en) * | 2020-05-25 | 2020-09-11 | 泰康保险集团股份有限公司 | Method, device, system and storage medium for processing service data |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110601880B (en) | Cloud platform, service processing method, command interface and computer equipment | |
| CN110515965B (en) | Business document processing method and device, computer equipment and storage medium | |
| CN111538757B (en) | Data storage method, query method, device, server and medium | |
| CN110780870A (en) | Service execution method, device, equipment and storage medium | |
| CN111026367A (en) | Micro-service arranging method and device, terminal equipment and storage medium | |
| CN110716738A (en) | Data processing method and device, cloud platform, electronic equipment and storage medium | |
| CN108809913A (en) | The method, apparatus and equipment of data desensitization | |
| CN112288400A (en) | Multi-system data interaction method and device, computer equipment and storage medium | |
| CN115357761A (en) | Link tracking method and device, electronic equipment and storage medium | |
| CN111104556A (en) | Service processing method and device | |
| CN111127211A (en) | Block chain based transaction method, system, device and computer readable storage medium | |
| CN109299173B (en) | Data transmission method, device and storage medium | |
| US7617263B2 (en) | Method and computer-readable medium for providing an official file repository | |
| CN110008173A (en) | A kind of method and device of data storage | |
| CN114201511A (en) | Project management and control method and device, computer equipment and storage medium | |
| CN113781202A (en) | Data processing method, data processing device, computer equipment and storage medium | |
| CN111045928B (en) | Interface data testing method, device, terminal and storage medium | |
| CN112950393A (en) | Insurance business docking method and device, electronic equipment and readable storage medium | |
| CN113535439B (en) | Service request processing method, device, equipment and storage medium | |
| CN112052171B (en) | Test message processing method and device, computer equipment and storage medium | |
| CN114881739A (en) | Order event processing method and device, electronic equipment and storage medium | |
| CN111061576B (en) | Method and system for creating entity object | |
| CN111526184B (en) | Business auditing method and device | |
| CN113902415A (en) | Financial data checking method and device, computer equipment and storage medium | |
| CN110224997B (en) | Gateway-based service exposure method and device and terminal equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 518000 Room 01, 20th Floor, Cuilin Building, No. 10, Kaifeng Road, Maling Community, Meilin Street, Futian District, Shenzhen, Guangdong Applicant after: Shenzhen Handhui Technology Group Co.,Ltd. Address before: 518000 20 / F, Cuilin building, 10 Kaifeng Road, Maling community, Meilin street, Futian District, Shenzhen City, Guangdong Province Applicant before: Shenzhen muchenglin Technology Co.,Ltd. |