WO2019127773A1 - 保险产品的销售处理方法、装置、存储介质及终端 - Google Patents

保险产品的销售处理方法、装置、存储介质及终端 Download PDF

Info

Publication number
WO2019127773A1
WO2019127773A1 PCT/CN2018/073813 CN2018073813W WO2019127773A1 WO 2019127773 A1 WO2019127773 A1 WO 2019127773A1 CN 2018073813 W CN2018073813 W CN 2018073813W WO 2019127773 A1 WO2019127773 A1 WO 2019127773A1
Authority
WO
WIPO (PCT)
Prior art keywords
insurance
product
information
insurance product
request message
Prior art date
Application number
PCT/CN2018/073813
Other languages
English (en)
French (fr)
Inventor
付舒婷
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019127773A1 publication Critical patent/WO2019127773A1/zh

Links

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
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0613—Third-party assisted
    • 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

Definitions

  • the present application belongs to the field of communications technologies, and in particular, to a method, an apparatus, a storage medium, and a terminal for selling and selling insurance products.
  • the embodiment of the present application provides a method, a device, a storage medium and a terminal for selling insurance products, so as to solve the complicated way for the channel to access the insurance product, the cumbersome interaction process with the insurance system, the labor cost, and the slow effect. problem.
  • the embodiment of the present application provides a sales processing method for an insurance product, where the sales processing method includes:
  • the request message includes coded information of the combined insurance product to be processed
  • the querying the database according to the request message, obtaining the combined insurance product to be processed and the insurance products included therein, and the insurance system to which each insurance product belongs includes:
  • the request message includes identification information of a function to be requested
  • obtaining the product information, and transmitting the product information and the request message to the insurance system to which the insurance system belongs includes:
  • one processing thread corresponds to an insurance product
  • the request interface corresponding to the insurance product is invoked and the product information is transmitted.
  • the request interface includes an inquiry request interface, a verification service request interface, and a coverage request interface;
  • the product information includes a insurance code, a security information, a policy number, and an applicant information
  • the product information includes the policyholder information, the insured person information, the insurance coverage and the number of copies requested;
  • the product information includes an insurance policy number and a payment method.
  • the embodiment of the present application further provides a sales processing device for an insurance product, where the sales processing device includes:
  • An association module configured to acquire a business operation instruction, and associate an insurance product formulated by a different insurance system based on the business operation instruction to obtain a combined insurance product
  • a sending module configured to send the combined insurance product to a channel side system, so that the channel side system displays the combined insurance product on a sales interface
  • An obtaining module configured to acquire a request message sent by the channel side system
  • a query module configured to query the database according to the request message, obtain the combined insurance product to be processed, the insurance products included therein, and the insurance system to which each insurance product belongs;
  • a processing module configured to acquire, for each insurance product, product information thereof, and send the product information and the request message to an insurance system to which it belongs;
  • the result obtaining module is configured to obtain the processing result returned by the insurance system according to the product information and the request message, and send the processing result to the channel side system.
  • the request message includes coded information of the combined insurance product to be processed, and identification information of the function to be requested;
  • the query module includes:
  • a parsing unit configured to parse the request message to obtain encoded information
  • a first query unit configured to query a database based on the encoded information, obtain an insurance product associated with each other in the combined insurance product to be processed, and an insurance system to which each insurance product belongs;
  • the second query unit is configured to query the database based on the identification information of the to-be-requested function, and determine a request interface corresponding to the insurance system to which each insurance product belongs.
  • processing module includes:
  • a startup unit configured to start a processing thread of the same number as the insurance product, and allocate the insurance product to each processing thread
  • a calling unit configured to acquire, by the processing thread, product information of the processed insurance product, and invoke a request interface corresponding to the insurance system to which the insurance product belongs;
  • a sending unit configured to send the product information and the request message to the insurance system to which the insurance product belongs by using the request interface
  • one processing thread corresponds to an insurance product
  • the request interface corresponding to the insurance product is invoked and the product information is transmitted.
  • the embodiment of the present application further provides a computer readable storage medium, where the computer readable instructions are stored, and when the computer readable instructions are executed by the processor, the following steps are implemented:
  • the embodiment of the present application further provides a terminal, where the terminal includes a memory, a processor, and computer readable instructions stored on the memory and executable on the processor, when the processor executes the computer readable instructions.
  • the embodiment of the present application develops a unified sales interaction process, obtains business operation instructions through the insurance cloud server, associates insurance products formulated by different insurance systems, and obtains a combined insurance product;
  • the product is sent to the channel side system, so that the channel side system displays the combined insurance product on the sales interface, so that the channel party is not familiar with and accesses the product plans of different insurance companies;
  • when interacting with the channel side system obtaining the a request message sent by the channel side system; querying the database according to the request message, obtaining the combined insurance product to be processed and the insurance products included therein, and the insurance system to which each type of insurance product belongs; obtaining each type of insurance product Product information, the product information and the request message are separately sent to the insurance system to which they belong;
  • the insurance system obtains the processing result returned by the insurance system according to the product information and the request message, and finally sends the processing result to the office Channel-side system, which simplifies the channel-side system in selling insurance products
  • the interaction mode of the time avoids the direct connection
  • FIG. 1 is a first implementation flowchart of a method for processing sales of an insurance product according to an embodiment of the present application
  • FIG. 2 is a second implementation flowchart of a method for processing sales of an insurance product according to an embodiment of the present application
  • FIG. 3 is a third implementation flowchart of a method for processing sales of an insurance product according to an embodiment of the present application
  • FIG. 4 is a structural diagram of a sales processing apparatus for an insurance product according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a terminal provided by an embodiment of the present application.
  • FIG. 1 shows a first implementation flow of a method for processing sales of an insurance product according to an embodiment of the present application.
  • the sales processing method of the insurance product provided by the embodiment of the present application is applied to the insurance cloud server, and the insurance cloud server is integrated with the insurance system and the channel side system to realize the combined sales of the insurance product.
  • the insurance system is a product management system of an insurance company, including but not limited to Ping An Insurance and Pacific Insurance;
  • the channel side system is a management system of an insurance sales intermediary company, and the insurance sales intermediary company includes Not limited to Tuniu, Tongcheng, and Bank of China.
  • the sales processing method includes:
  • step S101 a business operation instruction is acquired, and an insurance product formulated by a different insurance system is associated based on the business operation instruction to obtain a combined insurance product.
  • the insurance cloud server interacts with business people by providing tools like "product factories.”
  • Business personnel can configure insurance products on the “product factory” and enter or select the associated insurance products on the management page for combination.
  • the insurance products in the insurance system corresponding to the same insurance company may be associated or combined, or the insurance products in the insurance system corresponding to different insurance companies may be associated and combined. For example, suppose there is an A1 product in the insurance system A, and a B1 product exists in the insurance system B. Through the management page, the business personnel can configure the A1 product and the B1 product to be sold together as a packaged product or a combined product.
  • the insurance cloud server obtains a business operation instruction of the business personnel, and associates the insurance products formulated by the different insurance systems according to the business operation instruction, specifically storing the coded information of the insurance product, and generating the combined product based on the coded information of the insurance product.
  • the encoded information is given to the combined insurance product.
  • step S102 the combined insurance product is sent to the channel side system such that the channel side system displays the combined insurance product on the sales interface.
  • the insurance cloud server sends the related information of the configured combined insurance product to the channel side system for the channel side system to display the sales, or to the portal website for the channel side to view.
  • the insurance company does interface docking, which helps the channel to save R&D costs and facilitate the channel to access insurance products.
  • step S103 a request message sent by the channel side system is acquired.
  • the sales interface or the portal provides a plurality of function identifiers related to the insurance sales process
  • the business personnel can trigger the function identification according to the customer's needs
  • the channel side system generates a request message according to the input operation of the business personnel. And sending the request message to the insurance cloud server.
  • the request message is a function request related to an insurance sales process.
  • the function identifier includes but is not limited to the inquiry identifier, the underwriting identifier, and the underwriting identifier.
  • the request message includes but is not limited to the inquiry request, the underwriting request, and the underwriting request.
  • step S104 the database is inquired according to the request message, and the combined insurance product to be processed and the insurance products included therein, and the insurance system to which each insurance product belongs are obtained.
  • the insurance cloud server records, by using a database, a combination insurance product and each insurance product constituting the combined insurance product.
  • the insurance cloud server After receiving the request message, the insurance cloud server queries the database based on the request message, obtains the combined insurance product to be processed, the insurance products included therein, and the insurance system to which each insurance product belongs, to determine the insurance that needs to be interacted. system.
  • step S105 for each insurance product, its product information is obtained, and the product information and the request message are transmitted to the insurance system to which it belongs.
  • the insurance cloud server acquires the product corresponding to the A1 product and the B1 product from the database. Information, and then send the product information and request message of the A1 product to the insurance system A to which it belongs, and send the product information and request message of the B1 product to the insurance system B to which it belongs to request the insurance system separately.
  • a and insurance system B perform the corresponding operations in the insurance sales process.
  • the product information is detailed information of the insurance product, including but not limited to the product code, the insurance company to which it belongs, the age of insurance, the amount of insurance, the payment method, the payment period, and the guarantee period.
  • the insurance cloud server sends the product information of the insurance product and the request message of the channel party to the corresponding insurance system, in place of the channel party interacting with the insurance system, requesting the insurance system to execute the insurance sales process and the The operation corresponding to the request message, such as inquiry, underwriting or underwriting.
  • the interaction between the channel side system and the insurance cloud server may be based on a set of standard interfaces provided by the insurance cloud server, and the channel side system uses the set of standard interfaces to access the insurance cloud.
  • the server can be used without developing interfaces for different insurance companies, effectively reducing the development cost of the channel side, simplifying the access process of the channel side to the insurance product and the interaction process with the insurance system.
  • step S106 the insurance system acquires the processing result according to the product information and the processing result returned by the request message, and sends the processing result to the channel side system.
  • the processing result is returned to the insurance cloud server, such as the inquiry result, the underwriting result, and the underwriting result, thereby completing the function related to the insurance sales process, and the process is performed by the insurance cloud server.
  • the channel party receives the processing result returned by the insurance cloud server, and does not need to be handed over to the insurance system.
  • the Https request response mode may be adopted between the channel side system and the insurance cloud server, and the JSON data format is used in the message transmission, wherein the JSON data format is an optimized xml format, and for the same amount of data, JSON The format is simpler, the bandwidth occupied during transmission is small, and the system is easy to read and write.
  • the embodiment of the present application obtains a business operation instruction based on the insurance sales platform, associates the insurance products formulated by different insurance systems, and obtains a combined insurance product; and then sends the combined insurance product to the channel side system to make the
  • the channel side system displays the combined insurance product on the sales interface, so that the channel party is not familiar with and accesses the product plans of different insurance companies; when interacting with the channel side system, obtaining the request message sent by the channel side system;
  • the request message queries a database, obtains a combined insurance product to be processed, an insurance product included therein, and an insurance system to which each insurance product belongs; acquires product information of each insurance product, and uses the product information and the
  • the request message is sent to the insurance system to which it belongs, and the insurance system obtains the processing result returned by the insurance system according to the product information and the request message, and finally sends the processing result to the channel side system, thereby simplifying the channel side.
  • the way the system interacts when selling insurance products, avoiding direct channel The insurance system is docked, and the channel side is not required to develop the interface standards for different insurance systems, which effectively reduces the labor cost of the channel side, simplifies the sales process of the channel side, and solves the difficulty in developing the channel side system in the prior art and the high research and development cost.
  • the problem The problem.
  • FIG. 2 it is a schematic diagram of a second implementation flow of the sales processing method of the insurance product provided by the embodiment of the present application.
  • the request message includes coded information of the combined insurance product to be processed.
  • the step S104 queries the database according to the request message, and obtains the combined insurance product to be processed and the insurance products included therein, and the insurance system to which each insurance product belongs, including:
  • step S104 parsing the request message to obtain encoded information
  • step S1042 based on the encoded information query database, the insurance products associated with each other in the combined insurance product to be processed and the insurance system to which each insurance product belongs are acquired.
  • the first correspondence is maintained on the database of the insurance cloud server, and the combined insurance products and each insurance product constituting the combined insurance products are recorded.
  • the first correspondence may be displayed by coding information, that is, the correspondence between the coded information is maintained in the database. For example, if the A1 product in the insurance system A and the B1 product in the insurance system B are configured as a packaged C1 product for sale, the coded information of the C1 product and the coded information of the A1 product and the coded information of the B1 product are performed. Associated and stored in the first correspondence.
  • the insurance cloud server After receiving the request message, the insurance cloud server obtains the encoded information from the request message, queries the first correspondence relationship based on the encoded information, acquires the combined insurance product to be processed, and the insurance product included in the combined insurance product to be processed,
  • the related functions in the account improve the timeliness of insurance billing and sales.
  • the request message further includes identifier information of the function to be requested.
  • the step S1042 is based on the encoded information query database, and obtains the insurance products associated with each other in the combined insurance product to be processed, and the insurance system to which each insurance product belongs, and then includes:
  • step S1043 the database is searched based on the identification information of the function to be requested, and the request interface corresponding to the insurance system to which each insurance product belongs is determined.
  • the insurance cloud server can interact with the insurance system through a standard interface provided by the insurance system.
  • the standard interfaces provided by different insurance systems are usually different. Some insurance systems use the http interface, and some insurance systems use the web interface.
  • the insurance cloud server maintains a second correspondence relationship on the database of the insurance cloud server, and records the identification information of the function to be requested and the interface information of each insurance system to implement the function to be requested.
  • the insurance cloud server After receiving the request message and querying the insurance system to which each of the insurance products belongs to the insurance system, the insurance cloud server queries the second corresponding relationship in the database again based on the identification information of the to-be-requested function, and acquires the The request interface used by the insurance system.
  • the step S105 is to obtain the product information of each insurance product, and send the product information and the request message to the insurance system to which the insurance system belongs, and further includes:
  • step S1051 a processing thread of the same number as the insurance product is started, and the insurance product is allocated to each processing thread.
  • one processing thread corresponds to an insurance product
  • the request interface corresponding to the insurance product is invoked and the product information is transmitted.
  • the insurance cloud server counts the number of insurance products included in the combined insurance product to be processed, and starts multiple processing threads according to the quantity.
  • a combination insurance product includes two insurance products A1 and B1, and then starts two processing threads a and b.
  • the insurance products are respectively allocated to the processing threads a and b, one processing thread serves the insurance product A1, and the other processing thread serves the insurance product B1.
  • step S1052 the processing thread acquires the product information of the processed insurance product, and invokes the request interface corresponding to the insurance system to which the insurance product belongs.
  • the same combination insurance product includes multiple insurance products
  • the pending functions faced by the processing thread may be different, the requested interface may be different; on the other hand, the request interface used by different insurance systems
  • the types are not exactly the same, so the product information of the incoming request interface is not exactly the same.
  • the product information is related to the to-be-requested function.
  • Each processing thread operates independently to obtain product information of the assigned insurance products.
  • the request interface includes but is not limited to an inquiry request interface, a verification request interface, and a coverage request interface.
  • the product information includes but is not limited to the insurance code, the insurance amount information, the policy number of copies, and the policyholder information; when the underwriting request interface is invoked, the product information includes but is not limited to the policyholder information.
  • step S1053 the product information and the request message are sent to the insurance system to which the insurance product belongs through the request interface.
  • the request interface provided by the insurance system to which the processed insurance product belongs is invoked, and the product information of the insurance product is transmitted to the request interface, thereby implementing parallel interaction with multiple insurance systems.
  • the channel side system adopts single-thread processing, and the product interface information of each insurance system is called one by one in a serial manner, and the waiting time of the client is long.
  • the embodiment of the present application interacts with the insurance system corresponding to each insurance product in parallel by simultaneously starting multiple processing threads, thereby greatly improving the response speed of the request message, shortening the waiting time of the customer, and improving the insurance billing and underwriting. Timeliness.
  • step S106 the processing results returned by different calling interfaces are also different.
  • the insurance system if the inquiry interface is invoked, the insurance system returns the quotation information of the insurance product to the insurance cloud server.
  • the insurance system returns a message indicating whether the insurance product can be insured to the insurance cloud server, returns the insurance policy number if it can be insured, and returns a specific error message if the insurance cannot be insured. If the underwriting interface is invoked, the insurance system returns the policy number of the insurance product to the insurance cloud server.
  • the size of the serial number of each step does not mean the order of execution order, and the order of execution of each step should be determined by its function and internal logic, and should not constitute any implementation process of the embodiment of the present application. limited.
  • FIG. 4 is a structural diagram showing the structure of a sales processing apparatus for an insurance product according to an embodiment of the present application. For the convenience of description, only parts related to the embodiment of the present application are shown.
  • the sales processing device of the insurance product is used to implement the sales processing method of the insurance product described in the foregoing embodiments of FIG. 1 , FIG. 2 , and FIG. 3 , and may be a software unit and hardware built in the server. Unit or combination of hardware and software,
  • the sales processing device of the insurance product includes:
  • the association module 41 is configured to acquire a business operation instruction, and associate the insurance products formulated by different insurance systems according to the business operation instruction to obtain a combined insurance product;
  • a sending module 42 configured to send the combined insurance product to a channel side system, so that the channel side system displays the combined insurance product on a sales interface;
  • the obtaining module 43 is configured to acquire a request message sent by the channel side system
  • the querying module 44 is configured to query the database according to the request message, obtain the combined insurance product to be processed, the insurance products included therein, and the insurance system to which each insurance product belongs;
  • the processing module 45 is configured to acquire, for each insurance product, product information thereof, and send the product information and the request message to an insurance system to which the insurance system belongs;
  • the result obtaining module 46 is configured to obtain the processing result returned by the insurance system according to the product information and the request message, and send the processing result to the channel side system.
  • the request message includes coded information of the combined insurance product to be processed, and identifier information of the function to be requested;
  • the query module 44 includes:
  • the parsing unit 441 is configured to parse the request message to obtain encoded information.
  • the first query unit 442 is configured to query the database based on the encoded information, obtain the insurance products associated with each other in the combined insurance product to be processed, and the insurance system to which each insurance product belongs;
  • the second query unit 443 is configured to query the database based on the identification information of the to-be-requested function, and determine a request interface corresponding to the insurance system to which each insurance product belongs.
  • the processing module 45 includes:
  • the startup unit 451 is configured to start a processing thread of the same number as the insurance product, and allocate the insurance product to each processing thread;
  • the calling unit 452 is configured to acquire, by the processing thread, product information of the processed insurance product, and invoke a request interface corresponding to the insurance system to which the insurance product belongs;
  • the sending unit 453 is configured to send the product information and the request message to the insurance system to which the insurance product belongs by using the request interface;
  • one processing thread corresponds to an insurance product
  • the request interface corresponding to the insurance product is invoked and the product information is transmitted.
  • the request interface includes, but is not limited to, an inquiry request interface, a verification service request interface, and a coverage request interface;
  • the product information includes, but is not limited to, insurance code, insurance amount information, policy number of copies, and policyholder information;
  • the product information includes, but is not limited to, the policyholder information, the insured person information, the insurance coverage and the number of copies requested;
  • the product information includes, but is not limited to, an insurance policy number and a payment method.
  • each module/unit in the embodiment of the present application may be used to implement all the technical solutions in the foregoing method embodiments, and the specific working process may refer to the corresponding process in the foregoing method embodiments, and details are not described herein again. .
  • the embodiment provides a computer readable storage medium, where the computer readable storage medium is stored with the computer readable instructions, and when the computer readable instructions are executed by the processor, the sales processing method of the insurance product in Embodiment 1 is implemented, in order to avoid duplication , no longer repeat them here.
  • the computer readable instructions are executed by the processor, the functions of the modules/units in the sales processing device of the insurance product in Embodiment 2 are implemented. To avoid repetition, details are not described herein again.
  • FIG. 5 is a schematic diagram of a terminal according to an embodiment of the present disclosure, where the terminal includes but is not limited to a server and a mobile terminal.
  • the terminal 5 of this embodiment includes a processor 50, a memory 51, and computer readable instructions 52 stored in the memory 51 and executable on the processor 50.
  • the steps in the embodiment of the sales processing method of the insurance product are implemented, for example, steps S101 to S106 shown in FIG. 1 and steps S1041 described in the embodiment of FIG. S1042, steps S1043 to S1053 described in the embodiment of FIG. 3; or, when the processor 50 executes the computer readable instructions 52, implement the functions of each module/unit in the embodiment of the sales processing device of the insurance product, for example The functions of the modules 41 to 46 shown in Fig. 4.
  • the computer readable instructions 52 may be partitioned into one or more modules/units that are stored in the memory 51 and executed by the processor 50, To complete this application.
  • the one or more modules/units may be a series of computer readable instruction segments capable of performing a particular function for describing the execution of the computer readable instructions 52 in the terminal 5.
  • the computer readable instructions 52 may be divided into an association module, a sending module, an obtaining module, a query module, a processing module, and a result obtaining module.
  • the specific functions of each module are as follows:
  • An association module configured to acquire a business operation instruction, and associate an insurance product formulated by a different insurance system based on the business operation instruction to obtain a combined insurance product
  • a sending module configured to send the combined insurance product to a channel side system, so that the channel side system displays the combined insurance product on a sales interface
  • An obtaining module configured to acquire a request message sent by the channel side system
  • a query module configured to query the database according to the request message, obtain the combined insurance product to be processed, the insurance products included therein, and the insurance system to which each insurance product belongs;
  • a processing module configured to acquire, for each insurance product, product information thereof, and send the product information and the request message to an insurance system to which it belongs;
  • the result obtaining module is configured to obtain the processing result returned by the insurance system according to the product information and the request message, and send the processing result to the channel side system.
  • the terminal 5 can be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server.
  • the terminal may include, but is not limited to, a processor 50, a memory 51. It will be understood by those skilled in the art that FIG. 5 is only an example of the terminal 5 and does not constitute a limitation of the terminal 5, and may include more or less components than those illustrated, or combine some components, or different components, such as
  • the terminal may also include an input/output device, a network access device, a bus, and the like.
  • the processor 50 may be a central processing unit (CPU), or may be other general-purpose processors, a digital signal processor (DSP), an application specific integrated circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like, which is a control center of the terminal, and connects various parts of the entire terminal using various interfaces and lines.
  • the memory 51 can be used to store the computer readable instructions and/or modules by running or executing computer readable instructions and/or modules stored in the memory, and recalling data stored in the memory Implementing various functions of the terminal.
  • the memory may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may be stored. Data created based on the use of the terminal, etc.
  • the memory may include a high-speed random access memory, and may also include non-volatile memory such as a hard disk, a memory, a plug-in hard disk, a smart memory card (SMC), and a secure digital card (Secure Digital, SD). , Flash Card, at least one disk storage device, flash memory device, or other volatile solid-state storage device.
  • non-volatile memory such as a hard disk, a memory, a plug-in hard disk, a smart memory card (SMC), and a secure digital card (Secure Digital, SD).
  • SD Secure Digital
  • Flash Card at least one disk storage device, flash memory device, or other volatile solid-state storage device.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated modules/units if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium.
  • the present application implements all or part of the processes in the foregoing embodiments, and may also be implemented by computer readable instructions, which may be stored in a computer readable storage medium.
  • the computer readable instructions when executed by a processor, may implement the steps of the various method embodiments described above.
  • the computer readable instructions comprise computer readable instruction code, which may be in the form of source code, an object code form, an executable file or some intermediate form or the like.
  • the computer readable storage medium may include any entity or device capable of carrying the computer readable instruction code, a recording medium, a USB flash drive, a removable hard disk, a magnetic disk, an optical disk, a computer memory, a read only memory (ROM, Read- Only Memory), Random Access Memory (RAM), electrical carrier signals, telecommunications signals, and software distribution media. It should be noted that the content contained in the computer readable storage medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in a jurisdiction, for example, in some jurisdictions, according to legislation and patent practice, computer readable The storage medium does not include an electrical carrier signal and a telecommunication signal.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Development Economics (AREA)
  • Theoretical Computer Science (AREA)
  • Technology Law (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

本申请适用于通信技术领域，提供了一种保险产品的销售处理方法，所述方法包括：获取业务操作指令，关联不同保险系统制定的保险产品得到组合保险产品；将所述组合保险产品发送至渠道方系统，以使得所述渠道方系统在销售界面上展示所述组合保险产品；根据所述渠道方系统发送的请求消息查询数据库，获取待处理的组合保险产品及其所包括的保险产品、每一种保险产品所归属的保险系统；将每一种保险产品的产品信息和请求消息发送至其所归属的保险系统；获取所述保险系统根据所述产品信息及请求消息返回的处理结果，并转发至所述渠道方系统。本申请解决了现有技术中保险销售的渠道方接入保险产品的方式复杂、与保险系统的交互流程繁琐的问题。

Description

保险产品的销售处理方法、装置、存储介质及终端
本专利申请以2017年12月26日提交的申请号为201711430438.3，名称为“保险产品的销售处理方法、装置、存储介质及终端”的中国发明专利申请为基础，并要求其优先权。
技术领域
本申请属于通信技术领域，尤其涉及一种保险产品的销售处理方法、装置、存储介质及终端。
背景技术
在保险业务领域，经常遇到对不同保险公司推出的保险产品同时销售的场景，比如航空延误险和航空意外险。规模较大的保险销售中介(即渠道方)通常具备销售系统。现有技术需要渠道方在销售系统上分别配置不同保险公司的产品，并针对不同保险公司的调用接口分别做开发。在同时出售相互关联的产品A和产品B时，现有技术根据客户在销售系统的销售界面上的勾选操作，即同时勾选产品A和产品B，才能够依次调用产品A所属的保险系统和产品B所属的保险系统进行承保，交互过程繁琐。
可见，在对保险产品进行同时销售时，现有技术中渠道方的接入方式复杂，需要较大的人力成本来完成开发，与保险系统的交互流程繁琐，严重影响到了出单、承保的时效性。
发明内容
本申请实施例提供了一种保险产品的销售处理方法、装置、存储介质及终端，以解决渠道方接入保险产品的方式复杂、与保险系统的交互流程繁琐、人力成本大、效性慢的问题。
本申请实施例提供了一种保险产品的销售处理方法，所述销售处理方法包括：
获取业务操作指令，基于所述业务操作指令关联不同保险系统制定的保险产品，得到组合保险产品；
将所述组合保险产品发送至渠道方系统，以使得所述渠道方系统在销售界面上展示所述组合保险产品；
获取所述渠道方系统发送的请求消息；
根据所述请求消息查询数据库，获取待处理的组合保险产品及其所包括的保险产品、每一种保险产品所归属的保险系统；
对于每一种保险产品，获取其产品信息，将所述产品信息和所述请求消息发送至其所归属的保险系统；
获取所述保险系统根据所述产品信息及请求消息返回的处理结果，将所述处理结果发送至所述渠道方系统。
进一步地，所述请求消息中包括待处理的组合保险产品的编码信息；
所述根据所述请求消息查询数据库，获取待处理的组合保险产品及其所包括的保险产品、每一种保险产品所归属的保险系统包括：
解析所述请求消息得到编码信息；
基于所述编码信息查询数据库，获取该待处理的组合保险产品中相互关联的保险产品、每一种保险产品所归属的保险系统。
进一步地，所述请求消息中包括待请求功能的标识信息；
所述基于所述编码信息查询数据库，获取该待处理的组合保险产品中相互关联的保险产品、每一种保险产品所归属的保险系统，之后还包括：
基于所述待请求功能的标识信息查询数据库，确定每一种保险产品所归属的保险系统对应的请求接口。
进一步地，所述对于每一种保险产品，获取其产品信息，将所述产品信息和所述请求消息发送至其所归属的保险系统包括：
启动与所述保险产品数量相同的处理线程，将所述保险产品分配至每一条处理线程；
通过所述处理线程获取所处理的保险产品的产品信息，并调用所述保险产品所归属的保险系统对应的请求接口；
将所述产品信息和所述请求消息通过所述请求接口发送至所述保险产品所归属的保险系统；
其中，一个处理线程对应一种保险产品，调用所述保险产品对应的请求接口并传入产品信息。
进一步地，所述请求接口包括询价请求接口、核保请求接口、承保请求接口；
当调用询价请求接口时，所述产品信息包括险种代码、保额信息、保单份数、投保人信息；
当调用核保请求接口时，所述产品信息包括投保人信息、被投保人信息、请求保障的险种保额及份数；
当调用承保请求接口时，所述产品信息包括投保单号、支付方式。
本申请实施例还提供了一种保险产品的销售处理装置，所述销售处理装置包括：
关联模块，用于获取业务操作指令，基于所述业务操作指令关联不同保险系统制定的保险产品，得到组合保险产品；
发送模块，用于将所述组合保险产品发送至渠道方系统，以使得所述渠道方系统在销售界面上展示所述组合保险产品；
获取模块，用于获取所述渠道方系统发送的请求消息；
查询模块，用于根据所述请求消息查询数据库，获取待处理的组合保险产品及其所包括的保险产品、每一种保险产品所归属的保险系统；
处理模块，用于对于每一种保险产品，获取其产品信息，将所述产品信息和所述请求消息发送至其所归属的保险系统；
结果获取模块，用于获取所述保险系统根据所述产品信息及请求消息返回的处理结果，将所述处理结果发送至所述渠道方系统。
进一步地，所述请求消息中包括待处理的组合保险产品的编码信息、待请求功能的标识信息；
所述查询模块包括：
解析单元，用于解析所述请求消息得到编码信息；
第一查询单元，用于基于所述编码信息查询数据库，获取该待处理的组合保险产品中相互关联的保险产品、每一种保险产品所归属的保险系统；
第二查询单元，用于基于所述待请求功能的标识信息查询数据库，确定每一种保险产品所归属的保险系统对应的请求接口。
进一步地，所述处理模块包括：
启动单元，用于启动与所述保险产品数量相同的处理线程，将所述保险产品分配至每一条处理线程；
调用单元，用于通过所述处理线程获取所处理的保险产品的产品信息，并调用所述保险产品所归属的保险系统对应的请求接口；
发送单元，用于将所述产品信息和所述请求消息通过所述请求接口发送至所述保险产品所归属的保险系统；
其中，一个处理线程对应一种保险产品，调用所述保险产品对应的请求接口并传入产品信息。
本申请实施例还提供了一种计算机可读存储介质，其上存储有计算机可读指令，该计算机可读指令被处理器执行时实现如下步骤：
获取业务操作指令，基于所述业务操作指令关联不同保险系统制定的保险产品，得到 组合保险产品；
将所述组合保险产品发送至渠道方系统，以使得所述渠道方系统在销售界面上展示所述组合保险产品；
获取所述渠道方系统发送的请求消息；
根据所述请求消息查询数据库，获取待处理的组合保险产品及其所包括的保险产品、每一种保险产品所归属的保险系统；
对于每一种保险产品，获取其产品信息，将所述产品信息和所述请求消息发送至其所归属的保险系统；
获取所述保险系统根据所述产品信息及请求消息返回的处理结果，将所述处理结果发送至所述渠道方系统。
本申请实施例还提供了一种终端，所述终端包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机可读指令，所述处理器执行所述计算机可读指令时实现如下步骤：
获取业务操作指令，基于所述业务操作指令关联不同保险系统制定的保险产品，得到组合保险产品；
将所述组合保险产品发送至渠道方系统，以使得所述渠道方系统在销售界面上展示所述组合保险产品；
获取所述渠道方系统发送的请求消息；
根据所述请求消息查询数据库，获取待处理的组合保险产品及其所包括的保险产品、每一种保险产品所归属的保险系统；
对于每一种保险产品，获取其产品信息，将所述产品信息和所述请求消息发送至其所归属的保险系统；
获取所述保险系统根据所述产品信息及请求消息返回的处理结果，将所述处理结果发送至所述渠道方系统。
与现有技术相比，本申请实施例开发了一套统一的销售交互流程，通过保险云服务器获取业务操作指令，关联不同保险系统制定的保险产品，得到组合保险产品；然后将所述组合保险产品发送至渠道方系统，以使得所述渠道方系统在销售界面上展示所述组合保险产品，从而无需渠道方熟悉及接入不同保险公司的产品方案；在与渠道方系统交互时，获取所述渠道方系统发送的请求消息；根据所述请求消息查询数据库，获取待处理的组合保险产品及其所包括的保险产品、每一种保险产品所归属的保险系统；获取每一种保险产品的产品信息，将所述产品信息及所述请求消息分别发送至其所归属的保险系统；获取所述保险系统根据所 述产品信息及请求消息返回的处理结果，最后将所述处理结果发送至所述渠道方系统，从而简化了渠道方系统在销售保险产品时的交互方式，避免了渠道方直接与保险系统对接，无需渠道方针对不同保险系统的接口标准进行开发，有效地降低了渠道方的人力成本、简化了渠道方的销售流程。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他附图。
图1是本申请实施例提供的保险产品的销售处理方法的第一实现流程图；
图2是本申请实施例提供的保险产品的销售处理方法的第二实现流程图；
图3是本申请实施例提供的保险产品的销售处理方法的第三实现流程图；
图4是本申请实施例提供的保险产品的销售处理装置的组成结构图；
图5是本申请实施例提供的终端的示意图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
图1示出了本申请实施例提供的保险产品的销售处理方法的第一实现流程。本申请实施例提供的所述保险产品的销售处理方法应用于所述保险云服务器，通过构建保险云服务器与保险系统、渠道方系统进行交互，实现了保险产品的组合销售。其中，所述保险系统为保险公司的产品管理系统，所述保险公司包括但不限于平安保险、太平洋保险；所述渠道方系统为保险销售中介公司的管理系统，所述保险销售中介公司包括但不限于途牛、同城、中银。
参阅图1，所述销售处理方法包括：
在步骤S101中，获取业务操作指令，基于所述业务操作指令关联不同保险系统制定的保险产品，得到组合保险产品。
在这里，所述保险云服务器通过提供类似“产品工厂”的工具与业务人员交互。业务人员可以在所述“产品工厂”上配置保险产品，并在管理页面上输入或者选取相互关联的保险 产品进行组合。示例性地，可以是将同一保险公司对应的保险系统中的保险产品进行关联、组合，也可以是将不同保险公司对应的保险系统中的保险产品进行关联、组合。比如，假设保险系统A中存在A1产品，保险系统B中存在B1产品，通过所述管理页面，业务人员可以将A1产品和B1产品配置成一个打包的产品或者组合的产品一同销售。
应当理解，组合销售的产品应当是相似或相同场景下相互关联的，比如购买机票场景下的航延险和航意险，参加旅行团场景下的意外险和门诊险。
保险云服务器获取业务人员的业务操作指令，基于所述业务操作指令关联不同保险系统制定的保险产品，具体为将保险产品的编码信息进行关联存储，且基于该保险产品的编码信息，生成组合产品的编码信息，赋予所述组合保险产品。
在步骤S102中，将所述组合保险产品发送至渠道方系统，以使得所述渠道方系统在销售界面上展示所述组合保险产品。
在本申请实施例中，保险云服务器将配置好的组合保险产品的相关信息发送至渠道方系统，以供所述渠道方系统展示销售，或者上挂到门户网站供渠道方查看。作为渠道方，只需要将销售界面或者门户网站上的组合保险产品展示给客户即可，与现有技术需要在渠道方系统中对所销售的产品进行定义和配置相比，渠道方无需再与保险公司做接口对接，有利于渠道方节省研发成本，方便渠道方接入保险产品。
在步骤S103中，获取所述渠道方系统发送的请求消息。
在这里，所述销售界面或者门户网站上提供了多种与保险销售流程相关的功能标识，业务人员可以根据客户的需求触发所述功能标识，渠道方系统根据业务人员的输入操作生成请求消息，并将所述请求消息发送至保险云服务器。
其中，所述请求消息为与保险销售流程相关的功能请求。可选地，所述功能标识包括但不限于询价标识、核保标识、承保标识，相应地，所述请求消息包括但不限于询价请求、核保请求、承保请求。
在步骤S104中，根据所述请求消息查询数据库，获取待处理的组合保险产品及其所包括的保险产品、每一种保险产品所归属的保险系统。
在本申请实施例中，所述保险云服务器通过数据库上记录着组合保险产品以及构成所述组合保险产品的每一种保险产品。
保险云服务器接收到请求消息后，基于所述请求消息查询数据库，获取待处理的组合保险产品及其所包括的保险产品、每一种保险产品所归属的保险系统，以确定需要进行交互的保险系统。
在步骤S105中，对于每一种保险产品，获取其产品信息，将所述产品信息和所述请求 消息发送至其所归属的保险系统。
示例性地，假设组合保险产品C1包括保险系统A中的A1产品和保险系统B中的B1产品，基于所述请求消息，所述保险云服务器从数据库中获取到A1产品和B1产品对应的产品信息，然后将所述A1产品的产品信息和请求消息发送至其所归属的保险系统A，将所述B1产品的产品信息和请求消息发送至其所归属的保险系统B，以分别请求保险系统A和保险系统B执行保险销售流程中的对应操作。
可选地，所述产品信息为保险产品的明细信息，包括但不限于产品编码、所归属的保险公司、投保年龄、保额、缴费方式、缴费期、保障期。
在这里，本申请实施例由保险云服务器将保险产品的产品信息和渠道方的请求消息发送至对应的保险系统，以代替渠道方与保险系统交互，请求保险系统执行保险销售流程中与所述请求消息对应的操作，比如询价、核保或者承保。
可选地，所述渠道方系统与所述保险云服务器之间的交互可以基于所述保险云服务器提供的一套标准接口展开，所述渠道方系统采用所述的套标准接口接入保险云服务器即可，无需针对不同的保险公司提供的接口进行开发，有效地降低了渠道方的开发成本，简化了渠道方对保险产品的接入过程以及与保险系统的交互过程。
在步骤S106中，获取所述保险系统根据所述产品信息及请求消息返回的处理结果，将所述处理结果发送至所述渠道方系统。
保险系统根据请求消息执行相应功能后，会将处理结果返回至所述保险云服务器，比如询价结果、核保结果、承保结果，从而完成与保险销售流程相关的功能，此过程由保险云服务器代理完成，渠道方接收保险云服务器返回的处理结果，无需与保险系统进行交接。
可选地，所述渠道方系统和保险云服务器之间可以采用Https请求响应模式，在报文传输上使用JSON数据格式，其中，JSON数据格式是优化的xml格式，对于同等的数据量，JSON格式更简单，传输时占用的带宽小，且易于系统的读写。
综上所述，本申请实施例基于所述保险销售平台获取业务操作指令，关联不同保险系统制定的保险产品，得到组合保险产品；然后将所述组合保险产品发送至渠道方系统，以使得所述渠道方系统在销售界面上展示所述组合保险产品，从而无需渠道方熟悉及接入不同保险公司的产品方案；在与渠道方系统交互时，获取所述渠道方系统发送的请求消息；根据所述请求消息查询数据库，获取待处理的组合保险产品及其所包括的保险产品、每一种保险产品所归属的保险系统；获取每一种保险产品的产品信息，将所述产品信息及所述请求消息分别发送至其所归属的保险系统；获取所述保险系统根据所述产品信息及请求消息返回的处理结果，最后将所述处理结果发送至所述渠道方系统，从而简化了渠道方系统在销售保险产品时 的交互方式，避免了渠道方直接与保险系统对接，无需渠道方针对不同保险系统的接口标准进行开发，有效地降低了渠道方的人力成本、简化了渠道方的销售流程，解决了现有技术中渠道方系统开发困难、研发成本高的问题。
进一步地，基于图1提供的保险产品的销售处理方法的第一实现流程的基础上，提出本申请实施例提供的保险产品的销售处理方法的第二实现流程。
如图2所示，是本申请实施例提供的保险产品的销售处理方法的第二实现流程示意图。在本申请实施例中，所述请求消息中包括待处理的组合保险产品的编码信息。
所述步骤S104根据所述请求消息查询数据库，获取待处理的组合保险产品及其所包括的保险产品、每一种保险产品所归属的保险系统，包括：
在步骤S1041中，解析所述请求消息得到编码信息；
在步骤S1042中，基于所述编码信息查询数据库，获取该待处理的组合保险产品中相互关联的保险产品、每一种保险产品所归属的保险系统。
在这里，所述保险云服务器的数据库上维护着第一对应关系，记录了组合保险产品以及组成所述组合保险产品的每一种保险产品。所述第一对应关系可以通过编码信息展示，即数据库中维护着编码信息之间的对应关系。比如，假设保险系统A中的A1产品和保险系统B中的B1产品配置成一个打包的C1产品进行销售时，将C1产品的编码信息与所述A1产品的编码信息、B1产品的编码信息进行关联，并存储至所述第一对应关系中。
保险云服务器接收到请求消息后，从所述请求消息获取编码信息，基于所述编码信息查询第一对应关系，获取待处理的组合保险产品，以及待处理的组合保险产品所包括的保险产品、每一种保险产品所归属的保险系统，从而规范了保险云服务器对保险产品的管理，渠道方也无需在系统上配置保险产品的相关信息，传入组合保险产品的编码信息即可请求销售流程中的相关功能，提高了保险出单及销售的时效性。
进一步地，基于图2提供的保险产品的销售处理方法的第二实现流程的基础上，提出本申请实施例提供的保险产品的销售处理方法的第三实现流程。
如图3所示，是本申请实施例提供的保险产品的销售处理方法的第三实现流程示意图。在本申请实施例中，所述请求消息中还包括待请求功能的标识信息。
所述步骤S1042基于所述编码信息查询数据库，获取该待处理的组合保险产品中相互关联的保险产品、每一种保险产品所归属的保险系统，之后还包括：
在步骤S1043中，基于所述待请求功能的标识信息查询数据库，确定每一种保险产品所 归属的保险系统对应的请求接口。
在这里，保险云服务器可以通过保险系统提供的标准接口与所述保险系统交互。其中，不同保险系统提供的标准接口通常是不相同的，有的保险系统使用http接口，有的保险系统使用web接口。所述保险云服务器的数据库上还维护着第二对应关系，记录了待请求功能的标识信息与每一个保险系统实现该待请求功能的接口信息。
保险云服务器接收到请求消息并查询到待处理的组合保险产品中每一种保险产品所归属的保险系统后，基于所述待请求功能的标识信息再次查询数据库中的第二对应关系，获取所述保险系统所使用的请求接口。
所述步骤S105对于每一种保险产品，获取其产品信息，将所述产品信息和所述请求消息发送至其所归属的保险系统，还包括：
在步骤S1051中，启动与所述保险产品数量相同的处理线程，将所述保险产品分配至每一条处理线程。
其中，一个处理线程对应一种保险产品，调用所述保险产品对应的请求接口并传入产品信息。保险云服务器统计待处理的组合保险产品所包含的保险产品数量，根据所述数量同步启动多个处理线程，比如一个组合保险产品包括两种保险产品A1和B1，则启动两条处理线程a和b，将所述保险产品分别分配至所述处理线程a和b，一条处理线程为保险产品A1服务，另一条处理线程为保险产品B1服务。
在步骤S1052中，通过所述处理线程获取所处理的保险产品的产品信息，并调用所述保险产品所归属的保险系统对应的请求接口。
在这里，尽管同一个组合保险产品包括多种保险产品，但是处理线程面对的待请求功能可能不相同，所调用的请求接口可能不相同；另一方面，由于不同保险系统所使用的请求接口的类型也不完全相同，因此传入请求接口的产品信息也不完全相同。在本申请实施例中，所述产品信息与所述待请求功能相关。每一条处理线程独立运作，获取所分配的保险产品的产品信息。
可选地，所述请求接口包括但不限于询价请求接口、核保请求接口、承保请求接口。当调用询价请求接口时，所述产品信息包括但不限于险种代码、保额信息、保单份数、投保人信息；当调用核保请求接口时，所述产品信息包括但不限于投保人信息、被投保人信息、请求保障的险种保额及份数；当调用承保请求接口时，所述产品信息但不限于包括投保单号、支付方式。
在步骤S1053中，将所述产品信息和所述请求消息通过所述请求接口发送至所述保险产品所归属的保险系统。
通过所述处理线程，调用所处理的保险产品所归属的保险系统提供的请求接口，将所述保险产品的产品信息传入所述请求接口，从而实现了与多个保险系统的并行交互。而现有技术中，渠道方系统采用单线程处理，按照串行的方式逐一调用每一个保险系统的请求接口传入产品信息，客户的等待时间长。本申请实施例通过同步启动多条处理线程来并行与每一个保险产品对应的保险系统进行交互，大大地提高了对请求消息的响应速度，缩短了客户的等待时间，提高了保险出单、承保的时效性。
进一步地，在步骤S106中，不同调用接口返回的处理结果也不相同。可选地，若调用询价接口时，保险系统向所述保险云服务器返回保险产品的报价信息。若调用核保接口时，保险系统向所述保险云服务器返回保险产品是否能够投保的消息，在能够投保的情况下返回投保单号，在不能投保的情况下返回具体的错误信息。若调用承保接口时，保险系统向所述保险云服务器返回保险产品的保单号。
应理解，在上述实施例中，各步骤的序号的大小并不意味着执行顺序的先后，各步骤的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
实施例2
图4示出了本申请实施例提供的保险产品的销售处理装置的组成结构图，为了便于说明，仅示出了与本申请实施例相关的部分。
在本申请实施例中，所述保险产品的销售处理装置用于实现上述图1、图2、图3实施例中所述的保险产品的销售处理方法，可以是内置于服务器的软件单元、硬件单元或者软硬件结合的单元、
参阅图4，所述保险产品的销售处理装置包括：
关联模块41，用于获取业务操作指令，基于所述业务操作指令关联不同保险系统制定的保险产品，得到组合保险产品；
发送模块42，用于将所述组合保险产品发送至渠道方系统，以使得所述渠道方系统在销售界面上展示所述组合保险产品；
获取模块43，用于获取所述渠道方系统发送的请求消息；
查询模块44，用于根据所述请求消息查询数据库，获取待处理的组合保险产品及其所包括的保险产品、每一种保险产品所归属的保险系统；
处理模块45，用于对于每一种保险产品，获取其产品信息，将所述产品信息和所述请求消息发送至其所归属的保险系统；
结果获取模块46，用于获取所述保险系统根据所述产品信息及请求消息返回的处理结果，将所述处理结果发送至所述渠道方系统。
可选地，所述请求消息中包括待处理的组合保险产品的编码信息、待请求功能的标识信息；
所述查询模块44包括：
解析单元441，用于解析所述请求消息得到编码信息；
第一查询单元442，用于基于所述编码信息查询数据库，获取该待处理的组合保险产品中相互关联的保险产品、每一种保险产品所归属的保险系统；
第二查询单元443，用于基于所述待请求功能的标识信息查询数据库，确定每一种保险产品所归属的保险系统对应的请求接口。
可选地，所述处理模块45包括：
启动单元451，用于启动与所述保险产品数量相同的处理线程，将所述保险产品分配至每一条处理线程；
调用单元452，用于通过所述处理线程获取所处理的保险产品的产品信息，并调用所述保险产品所归属的保险系统对应的请求接口；
发送单元453，用于将所述产品信息和所述请求消息通过所述请求接口发送至所述保险产品所归属的保险系统；
其中，一个处理线程对应一种保险产品，调用所述保险产品对应的请求接口并传入产品信息。
可选地，所述请求接口包括但不限于询价请求接口、核保请求接口、承保请求接口；
当调用询价请求接口时，所述产品信息包括但不限于险种代码、保额信息、保单份数、投保人信息；
当调用核保请求接口时，所述产品信息包括但不限于投保人信息、被投保人信息、请求保障的险种保额及份数；
当调用承保请求接口时，所述产品信息包括但不限于投保单号、支付方式。
需要说明的是，本申请实施例中的各模块/单元可以用于实现上述方法实施例中的全部技术方案，其具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述或记载的部分，可以参见其它实施例的相关描述。
实施例3
本实施例提供一计算机可读存储介质，该计算机可读存储介质上存储有计算机可读指令，该计算机可读指令被处理器执行时实现实施例1中保险产品的销售处理方法，为避免重复，这里不再赘述。或者，该计算机可读指令被处理器执行时实现实施例2中保险产品的销售处理装置中各模块/单元的功能，为避免重复，这里不再赘述。
实施例4
图5是本申请实施例提供的一种终端的示意图，所述终端包括但不限于服务器、移动终端。如图5所示，该实施例的终端5包括：处理器50、存储器51以及存储在所述存储器51中并可在所述处理器50上运行的计算机可读指令52。所述处理器50执行所述计算机可读指令52时实现上述保险产品的销售处理方法实施例中的步骤，例如图1所示的步骤S101至S106，图2实施例中所述的步骤S1041至S1042，图3实施例中所述的步骤S1043至S1053；或者，所述处理器50执行所述计算机可读指令52时实现上述保险产品的销售处理装置实施例中各模块/单元的功能，例如图4所示模块41至46的功能。
示例性的，所述计算机可读指令52可以被分割成一个或多个模块/单元，所述一个或者多个模块/单元被存储在所述存储器51中，并由所述处理器50执行，以完成本申请。所述一个或多个模块/单元可以是能够完成特定功能的一系列计算机可读指令段，该指令段用于描述所述计算机可读指令52在所述终端5中的执行过程。例如，所述计算机可读指令52可以被分割成关联模块、发送模块、获取模块、查询模块、处理模块、结果获取模块，各模块具体功能如下：
关联模块，用于获取业务操作指令，基于所述业务操作指令关联不同保险系统制定的保险产品，得到组合保险产品；
发送模块，用于将所述组合保险产品发送至渠道方系统，以使得所述渠道方系统在销售界面上展示所述组合保险产品；
获取模块，用于获取所述渠道方系统发送的请求消息；
查询模块，用于根据所述请求消息查询数据库，获取待处理的组合保险产品及其所包括的保险产品、每一种保险产品所归属的保险系统；
处理模块，用于对于每一种保险产品，获取其产品信息，将所述产品信息和所述请求消息发送至其所归属的保险系统；
结果获取模块，用于获取所述保险系统根据所述产品信息及请求消息返回的处理结果，将所述处理结果发送至所述渠道方系统。
所述终端5可以是桌上型计算机、笔记本、掌上电脑及云端服务器等计算设备。所述 终端可包括，但不仅限于，处理器50、存储器51。本领域技术人员可以理解，图5仅仅是终端5的示例，并不构成对终端5的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件，例如所述终端还可以包括输入输出设备、网络接入设备、总线等。
所称处理器50可以是中央处理单元(Central Processing Unit，CPU)，还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等，所述处理器是所述终端的控制中心，利用各种接口和线路连接整个终端的各个部分。
所述存储器51可用于存储所述计算机可读指令和/或模块，所述处理器通过运行或执行存储在所述存储器内的计算机可读指令和/或模块，以及调用存储在存储器内的数据，实现所述终端的各种功能。所述存储器可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等；存储数据区可存储根据终端的使用所创建的数据等。此外，存储器可以包括高速随机存取存储器，还可以包括非易失性存储器，例如硬盘、内存、插接式硬盘、智能存储卡(Smart Media Card，SMC)、安全数字卡(Secure Digital，SD)、闪存卡(Flash Card)，至少一个磁盘存储器件、闪存器件或其他易失性固态存储器件。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的模块/单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读存储介质中。基于这样的理解，本申请实现上述实施例方法中的全部或部分流程，也可以通过计算机可读指令来指令相关的硬件来完成，所述的计算机可读指令可存储于一计算机可读存储介质中，该计算机可读指令在被处理器执行时，可实现上述各个方法实施例的步骤。其中，所述计算机可读指令包括计算机可读指令代码，所述计算机可读指令代码可以为源代码形式、对象代码形式、可执行文件或某些中间形式等。所述计算机可读存储介质可以包括：能够携带所述计算机可读指令代码的任何实体或装置、记录介质、U盘、移动硬盘、磁碟、光盘、计算机存储器、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、电载波信号、电信信号以及软件分发介质等。需要说明的是，所述计算机可读存储介质包含的内容可以根据司法管辖区内立法和专利实践的要求进行适当的增减，例如在某些司法管辖区，根据立法和专利实践，计算机可 读存储介质不包括是电载波信号和电信信号。
以上所述实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围，均应包含在本申请的保护范围之内。

Claims (20)

  1. 一种保险产品的销售处理方法，其特征在于，所述销售处理方法包括：
    获取业务操作指令，基于所述业务操作指令关联不同保险系统制定的保险产品，得到组合保险产品；
    将所述组合保险产品发送至渠道方系统，以使得所述渠道方系统在销售界面上展示所述组合保险产品；
    获取所述渠道方系统发送的请求消息；
    根据所述请求消息查询数据库，获取待处理的组合保险产品及其所包括的保险产品、每一种保险产品所归属的保险系统；
    对于每一种保险产品，获取其产品信息，将所述产品信息和所述请求消息发送至其所归属的保险系统；
    获取所述保险系统根据所述产品信息及请求消息返回的处理结果，将所述处理结果发送至所述渠道方系统。
  2. 如权利要求1所述的保险产品的销售处理方法，其特征在于，所述请求消息中包括待处理的组合保险产品的编码信息；
    所述根据所述请求消息查询数据库，获取待处理的组合保险产品及其所包括的保险产品、每一种保险产品所归属的保险系统包括：
    解析所述请求消息得到编码信息；
    基于所述编码信息查询数据库，获取该待处理的组合保险产品中相互关联的保险产品、每一种保险产品所归属的保险系统。
  3. 如权利要求2所述的保险产品的销售处理方法，其特征在于，所述请求消息中包括待请求功能的标识信息；
    所述基于所述编码信息查询数据库，获取该待处理的组合保险产品中相互关联的保险产品、每一种保险产品所归属的保险系统，之后还包括：
    基于所述待请求功能的标识信息查询数据库，确定每一种保险产品所归属的保险系统对应的请求接口。
  4. 如权利要求3所述的保险产品的销售处理方法，其特征在于，所述对于每一种保险产品，获取其产品信息，将所述产品信息和所述请求消息发送至其所归属的保险系统包括：
    启动与所述保险产品数量相同的处理线程，将所述保险产品分配至每一条处理线程；
    通过所述处理线程获取所处理的保险产品的产品信息，并调用所述保险产品所归属的保 险系统对应的请求接口；
    将所述产品信息和所述请求消息通过所述请求接口发送至所述保险产品所归属的保险系统；
    其中，一个处理线程对应一种保险产品，调用所述保险产品对应的请求接口并传入产品信息。
  5. 如权利要求3或4所述的保险产品的销售处理方法，其特征在于，所述请求接口包括询价请求接口、核保请求接口、承保请求接口；
    当调用询价请求接口时，所述产品信息包括险种代码、保额信息、保单份数、投保人信息；
    当调用核保请求接口时，所述产品信息包括投保人信息、被投保人信息、请求保障的险种保额及份数；
    当调用承保请求接口时，所述产品信息包括投保单号、支付方式。
  6. 一种保险产品的销售处理装置，其特征在于，所述销售处理装置包括：
    关联模块，用于获取业务操作指令，基于所述业务操作指令关联不同保险系统制定的保险产品，得到组合保险产品；
    发送模块，用于将所述组合保险产品发送至渠道方系统，以使得所述渠道方系统在销售界面上展示所述组合保险产品；
    获取模块，用于获取所述渠道方系统发送的请求消息；
    查询模块，用于根据所述请求消息查询数据库，获取待处理的组合保险产品及其所包括的保险产品、每一种保险产品所归属的保险系统；
    处理模块，用于对于每一种保险产品，获取其产品信息，将所述产品信息和所述请求消息发送至其所归属的保险系统；
    结果获取模块，用于获取所述保险系统根据所述产品信息及请求消息返回的处理结果，将所述处理结果发送至所述渠道方系统。
  7. 如权利要求6所述的保险产品的销售处理装置，其特征在于，所述请求消息中包括待处理的组合保险产品的编码信息；
    所述查询模块包括：
    解析单元，用于解析所述请求消息得到编码信息；
    第一查询单元，用于基于所述编码信息查询数据库，获取该待处理的组合保险产品中相互关联的保险产品、每一种保险产品所归属的保险系统。
  8. 如权利要求7所述的保险产品的销售处理装置，其特征在于，所述请求消息中包括 待请求功能的标识信息；所述查询模块还包括：
    第二查询单元，用于基于所述待请求功能的标识信息查询数据库，确定每一种保险产品所归属的保险系统对应的请求接口。
  9. 如权利要求8所述的保险产品的销售处理装置，其特征在于，所述处理模块包括：
    启动单元，用于启动与所述保险产品数量相同的处理线程，将所述保险产品分配至每一条处理线程；
    调用单元，用于通过所述处理线程获取所处理的保险产品的产品信息，并调用所述保险产品所归属的保险系统对应的请求接口；
    发送单元，用于将所述产品信息和所述请求消息通过所述请求接口发送至所述保险产品所归属的保险系统；
    其中，一个处理线程对应一种保险产品，调用所述保险产品对应的请求接口并传入产品信息。
  10. 如权利要求8或9所述的保险产品的销售处理装置，其特征在于，所述请求接口包括询价请求接口、核保请求接口、承保请求接口；
    当调用询价请求接口时，所述产品信息包括险种代码、保额信息、保单份数、投保人信息；
    当调用核保请求接口时，所述产品信息包括投保人信息、被投保人信息、请求保障的险种保额及份数；
    当调用承保请求接口时，所述产品信息包括投保单号、支付方式。
  11. 一种计算机可读存储介质，其上存储有计算机可读指令，其特征在于，该计算机可读指令被处理器执行时实现如下步骤：
    获取业务操作指令，基于所述业务操作指令关联不同保险系统制定的保险产品，得到组合保险产品；
    将所述组合保险产品发送至渠道方系统，以使得所述渠道方系统在销售界面上展示所述组合保险产品；
    获取所述渠道方系统发送的请求消息；
    根据所述请求消息查询数据库，获取待处理的组合保险产品及其所包括的保险产品、每一种保险产品所归属的保险系统；
    对于每一种保险产品，获取其产品信息，将所述产品信息和所述请求消息发送至其所归属的保险系统；
    获取所述保险系统根据所述产品信息及请求消息返回的处理结果，将所述处理结果发送 至所述渠道方系统。
  12. 如权利要求11所述的计算机可读存储介质，其特征在于，所述请求消息中包括待处理的组合保险产品的编码信息；
    所述根据所述请求消息查询数据库，获取待处理的组合保险产品及其所包括的保险产品、每一种保险产品所归属的保险系统包括：
    解析所述请求消息得到编码信息；
    基于所述编码信息查询数据库，获取该待处理的组合保险产品中相互关联的保险产品、每一种保险产品所归属的保险系统。
  13. 如权利要求12所述的计算机可读存储介质，其特征在于，所述请求消息中包括待请求功能的标识信息；
    所述基于所述编码信息查询数据库，获取该待处理的组合保险产品中相互关联的保险产品、每一种保险产品所归属的保险系统，之后还包括：
    基于所述待请求功能的标识信息查询数据库，确定每一种保险产品所归属的保险系统对应的请求接口。
  14. 如权利要求13所述的计算机可读存储介质，其特征在于，所述对于每一种保险产品，获取其产品信息，将所述产品信息和所述请求消息发送至其所归属的保险系统包括：
    启动与所述保险产品数量相同的处理线程，将所述保险产品分配至每一条处理线程；
    通过所述处理线程获取所处理的保险产品的产品信息，并调用所述保险产品所归属的保险系统对应的请求接口；
    将所述产品信息和所述请求消息通过所述请求接口发送至所述保险产品所归属的保险系统；
    其中，一个处理线程对应一种保险产品，调用所述保险产品对应的请求接口并传入产品信息。
  15. 如权利要求13或14所述的计算机可读存储介质，其特征在于，所述请求接口包括询价请求接口、核保请求接口、承保请求接口；
    当调用询价请求接口时，所述产品信息包括险种代码、保额信息、保单份数、投保人信息；
    当调用核保请求接口时，所述产品信息包括投保人信息、被投保人信息、请求保障的险种保额及份数；
    当调用承保请求接口时，所述产品信息包括投保单号、支付方式。
  16. 一种终端，所述终端包括存储器、处理器及存储在存储器上并可在处理器上运行的 计算机可读指令，其特征在于，所述处理器执行所述计算机可读指令时实现如下步骤：
    获取业务操作指令，基于所述业务操作指令关联不同保险系统制定的保险产品，得到组合保险产品；
    将所述组合保险产品发送至渠道方系统，以使得所述渠道方系统在销售界面上展示所述组合保险产品；
    获取所述渠道方系统发送的请求消息；
    根据所述请求消息查询数据库，获取待处理的组合保险产品及其所包括的保险产品、每一种保险产品所归属的保险系统；
    对于每一种保险产品，获取其产品信息，将所述产品信息和所述请求消息发送至其所归属的保险系统；
    获取所述保险系统根据所述产品信息及请求消息返回的处理结果，将所述处理结果发送至所述渠道方系统。
  17. 如权利要求16所述的终端，其特征在于，所述请求消息中包括待处理的组合保险产品的编码信息；
    所述根据所述请求消息查询数据库，获取待处理的组合保险产品及其所包括的保险产品、每一种保险产品所归属的保险系统包括：
    解析所述请求消息得到编码信息；
    基于所述编码信息查询数据库，获取该待处理的组合保险产品中相互关联的保险产品、每一种保险产品所归属的保险系统。
  18. 如权利要求17所述的终端，其特征在于，所述请求消息中包括待请求功能的标识信息；
    所述基于所述编码信息查询数据库，获取该待处理的组合保险产品中相互关联的保险产品、每一种保险产品所归属的保险系统，之后还包括：
    基于所述待请求功能的标识信息查询数据库，确定每一种保险产品所归属的保险系统对应的请求接口。
  19. 如权利要求18所述的终端，其特征在于，所述对于每一种保险产品，获取其产品信息，将所述产品信息和所述请求消息发送至其所归属的保险系统包括：
    启动与所述保险产品数量相同的处理线程，将所述保险产品分配至每一条处理线程；
    通过所述处理线程获取所处理的保险产品的产品信息，并调用所述保险产品所归属的保险系统对应的请求接口；
    将所述产品信息和所述请求消息通过所述请求接口发送至所述保险产品所归属的保险 系统；
    其中，一个处理线程对应一种保险产品，调用所述保险产品对应的请求接口并传入产品信息。
  20. 如权利要求18或19所述的终端，其特征在于，所述请求接口包括询价请求接口、核保请求接口、承保请求接口；
    当调用询价请求接口时，所述产品信息包括险种代码、保额信息、保单份数、投保人信息；
    当调用核保请求接口时，所述产品信息包括投保人信息、被投保人信息、请求保障的险种保额及份数；
    当调用承保请求接口时，所述产品信息包括投保单号、支付方式。
PCT/CN2018/073813 2017-12-26 2018-01-23 保险产品的销售处理方法、装置、存储介质及终端 WO2019127773A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711430438.3A CN108242014A (zh) 2017-12-26 2017-12-26 保险产品的销售处理方法、装置、存储介质及终端
CN201711430438.3 2017-12-26

Publications (1)

Publication Number Publication Date
WO2019127773A1 true WO2019127773A1 (zh) 2019-07-04

Family

ID=62701105

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/073813 WO2019127773A1 (zh) 2017-12-26 2018-01-23 保险产品的销售处理方法、装置、存储介质及终端

Country Status (2)

Country Link
CN (1) CN108242014A (zh)
WO (1) WO2019127773A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109377381A (zh) * 2018-08-21 2019-02-22 中国平安人寿保险股份有限公司 基于数据分析的保险配置方法、装置、计算机设备及存储介质
CN110287406A (zh) * 2019-05-21 2019-09-27 深圳壹账通智能科技有限公司 渠道用户推荐方法、服务器及计算机可读存储介质
CN113313588A (zh) * 2020-02-26 2021-08-27 京东数字科技控股股份有限公司 请求的响应方法、装置及系统、存储介质、电子装置
CN112508643A (zh) * 2020-12-03 2021-03-16 海腾保险代理有限公司 用于报价的信息处理方法和装置
CN112862362A (zh) * 2021-03-12 2021-05-28 智显互联(深圳)股份有限公司 商显产业链的交易系统、方法、装置、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106127587A (zh) * 2016-06-24 2016-11-16 焦文华 自助保险方法及适用于该方法的保险自助柜员机
CN106548404A (zh) * 2016-11-10 2017-03-29 上海最会保网络科技有限公司 一种基于互联网的车险比价交易方法及装置
CN106952163A (zh) * 2016-01-07 2017-07-14 平安科技（深圳）有限公司 保险数据处理方法及系统
CN107016027A (zh) * 2016-12-08 2017-08-04 阿里巴巴集团控股有限公司 实现业务信息快速搜索的方法和装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004157980A (ja) * 2002-07-04 2004-06-03 Tokio Marine & Fire Insurance Co Ltd 事業活動包括保険のための情報処理方法及び装置
CN101783006A (zh) * 2009-01-19 2010-07-21 乔美国际网路股份有限公司 自主利率投资型终身寿险的方法与保险平台
CN106844372B (zh) * 2015-12-04 2021-09-24 菜鸟智能物流控股有限公司 一种物流信息查询方法和装置
CN107239326A (zh) * 2016-03-28 2017-10-10 平安科技（深圳）有限公司 承保多线程批处理方法和系统
CN112927090A (zh) * 2016-12-19 2021-06-08 创新先进技术有限公司 业务订单数据的生成方法及装置
CN106649845A (zh) * 2016-12-30 2017-05-10 上海富聪金融信息服务有限公司 一种交易信息服务平台及其信息处理方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106952163A (zh) * 2016-01-07 2017-07-14 平安科技（深圳）有限公司 保险数据处理方法及系统
CN106127587A (zh) * 2016-06-24 2016-11-16 焦文华 自助保险方法及适用于该方法的保险自助柜员机
CN106548404A (zh) * 2016-11-10 2017-03-29 上海最会保网络科技有限公司 一种基于互联网的车险比价交易方法及装置
CN107016027A (zh) * 2016-12-08 2017-08-04 阿里巴巴集团控股有限公司 实现业务信息快速搜索的方法和装置

Also Published As

Publication number Publication date
CN108242014A (zh) 2018-07-03

Similar Documents

Publication Publication Date Title
WO2019127773A1 (zh) 保险产品的销售处理方法、装置、存储介质及终端
US20200050608A1 (en) Multi-tenant data isolation method, apparatus, and system
US9460138B2 (en) Managing an index of a table of a database
US8572023B2 (en) Data services framework workflow processing
US8346747B2 (en) Extending database tables in a multi-tenant environment
WO2018201887A1 (zh) 数据响应方法、装置、终端设备及介质
US10331669B2 (en) Fast query processing in columnar databases with GPUs
WO2016011886A1 (zh) 对图像进行解码的方法及装置
WO2020000720A1 (zh) 服务器、报文处理方法、程序和计算机可读存储介质
CN108536778A (zh) 一种数据应用共享平台及方法
WO2021042849A1 (zh) 一种云平台、业务处理方法、命令接口及计算机设备
WO2021208762A1 (zh) 数据存储、查询
US20200143323A1 (en) Linked blockchain structures for accelerated multi-chain verification
US20230030856A1 (en) Distributed table storage processing method, device and system
CN108363741B (zh) 大数据统一接口方法、装置、设备及存储介质
US11886941B2 (en) Systems and methods for providing uniform access in a multi-tenant system
US9204175B2 (en) Providing partial file stream for generating thumbnail
US8406401B2 (en) Interactive voice response system to business application interface
CN110378680A (zh) 一种数据处理方法、装置、存储介质和服务器
US10628416B2 (en) Enhanced database query processing
CN109271564A (zh) 保单查询方法及设备
US20190163830A1 (en) Customer service advocacy on social networking sites using natural language query response from site-level search results
CN111176588B (zh) 业务单据出单方法、装置、介质及电子设备
WO2019001271A1 (zh) 开发平台装置、获取保单号的方法及计算机可读存储介质
US8453166B2 (en) Data services framework visibility component

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18894509

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 05.10.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18894509

Country of ref document: EP

Kind code of ref document: A1