TWI898244B - System for controlling signature sequence according to sequence codes to complete the online insurance application and method thereof - Google Patents

Abstract

A system for controlling signature sequence according to sequence codes to complete the online insurance application and a method thereof are provided. By generating an insurance agreement based on a product identification of an insurance product and signatory data transmitted by a business client by an insurance server, generating guidance data containing an insurance identification and sequence codes by the insurance server, transmitting the insurance identification, one of the sequence codes and an identification data to a platform server according to the connection message by a signature client after the signature client obtains the guidance data, and transmitting the insurance agreement from the platform server to the signature client for signature when the received sequence code matches a signature sequence and the identification data matches signer’s identification corresponding to the received sequence code, the system and the method can provide multiple people to sign the same document online, and can achieve the effect of reducing time cost of paper delivery and signature.

Description

System and method for completing online insurance by controlling signature sequence according to sequence code

An online insurance application system and method, particularly a system and method for completing online insurance application by controlling the signature sequence according to a sequential code.

In response to regulatory authorities' inclusive finance policies, the financial industry has developed numerous digital processes and systems in the hope of addressing issues such as recommending financial products, streamlining the purchase process, and confirming purchase intent. However, in order to meet existing regulations for online financial product purchases, the current process has become less intuitive and inconvenient for consumers. Furthermore, current regulations impose numerous restrictions on consumers purchasing financial products online. For example, detailed product information is required before purchasing a financial product, and most financial products require a signature before the purchase can be completed. Therefore, despite numerous inconveniences and restrictions, consumers still prefer face-to-face product introductions and signature services from sales representatives to complete the purchase of financial products.

In certain situations, such as when sales representatives are far away from consumers or during a major infectious disease outbreak, they are often unable to provide face-to-face service. To meet the sales representative's need for product introduction services, sales representatives can introduce products to consumers through online communication. However, simply introducing products via voice or video does not allow consumers to sign. To this end, most financial institutions offer online document signing services. This involves verifying the signatory's identity online and then providing the signatory with a digital certificate to sign the electronic document. However, current online document signing services typically only allow a single signatory to sign a document, and cannot accommodate multiple signatories signing the same document. Therefore, for certain financial products (such as insurance policies), which may require multiple signatories to complete the purchase, existing document signing services are unable to meet this demand.

In summary, it can be seen that the existing technology has long been unable to provide online document signing services with the problem of multiple people signing the same document. Therefore, it is necessary to propose improved technical means to solve this problem.

In view of the problem that the prior art online document signing service cannot provide multiple people with the same document, the present invention discloses a system and method for completing online insurance application by controlling the signature sequence based on sequence codes, wherein:

The system disclosed in the present invention for completing online insurance application by controlling the signature sequence according to the sequence code includes at least: a business client for inputting product identification data and signatory data; an insurance server for receiving the product identification data and signatory data, and generating an insurance consent form and corresponding policy identification data according to the product identification data and signatory data, and generating a sequence code corresponding to the signatory data, and generating guidance data, wherein the guidance data includes a connection message, policy identification data, and sequence code; a signature client for obtaining the guidance data through the insurance server, and for obtaining the guidance data. The platform server receives the policy identification data and sequence code sent by the signing client. When the sequence code matches the signing sequence corresponding to the policy identification data, the insurance server obtains the signatory identification data corresponding to the sequence code. The platform server receives the identity identification data sent by the signing client, and when it determines that the identity identification data matches the signatory identification data, obtains the insurance agreement corresponding to the policy identification data and transmits the insurance agreement to the signing client. The signing client signs the insurance agreement and returns the signed insurance agreement to the platform server.

The method disclosed in the present invention for completing online insurance application by controlling the signature sequence according to the sequence code includes at least the following steps: the business client inputs the product identification data and the signatory data, and transmits the product identification data and the signatory data to the insurance server; the insurance server generates the insurance consent form and the corresponding policy identification data according to the product identification data and the signatory data; the insurance server generates the sequence code corresponding to the signatory data and generates the guidance data, which includes the connection information of the platform server, the policy identification data, and the sequence code; the signature client obtains the guidance data through the insurance server, and The policy identification data and sequence code are transmitted to the platform server based on the connection message. When the sequence code matches the signing sequence corresponding to the policy identification data, the platform server obtains the signatory identification data corresponding to the sequence code from the insurance server. The signing client obtains the identity identification data and transmits it to the platform server. When the platform server determines that the identity identification data matches the signatory identification data, it obtains the insurance agreement corresponding to the policy identification data and transmits the insurance agreement to the signing client. The signing client signs the insurance agreement and transmits the signed insurance agreement to the platform server.

The system and method disclosed in the present invention are as described above. The difference between the present invention and the prior art is that the present invention generates an insurance consent form and corresponding policy identification data based on the product identification data and signatory data sent by the business client through the insurance server, and then generates a guidance data containing the policy identification data and the sequence code corresponding to the signatory. After the signing client obtains the guidance data, it transmits the policy identification data in the guidance data according to the connection message in the guidance data. The platform server sends the sequence code and identity information to the platform server. When the sequence code matches the signing sequence and the identity information matches the signatory identification information corresponding to the sequence code, the platform server sends the insurance consent form to the signing client for signature. This process continues until all signatories have completed signing the insurance consent form. This solves the problems of previous technologies and can achieve the technical effect of reducing the time cost of sending paper signatures.

The following will be used in conjunction with drawings and embodiments to describe in detail the features and implementation methods of the present invention. The content is sufficient to enable anyone familiar with the relevant technology to easily and fully understand the technical means used by the present invention to solve the technical problems and implement them accordingly, thereby achieving the effects that can be achieved by the present invention.

This invention allows different signatories who need to sign the insurance consent form to use the same or different signature clients to connect to the platform server to sign the form. These signatories may include, but are not limited to, the proposer, the insured, legal representatives, and insurance agents.

This invention also mentions a computing device. The computing device mentioned herein includes, but is not limited to, hardware components such as one or more processing modules, one or more memory modules, and a bus that connects the various hardware components (including the memory modules and processing modules). Through these hardware components, the computing device can load and execute an operating system, allowing the operating system to run on the computing device, and can also execute software or programs. The computing device also includes a housing, within which the aforementioned hardware components are housed.

The bus of the computing device provided in the present invention may include one or more types of buses, such as a data bus, an address bus, a control bus, an expansion bus, and/or a local bus. Buses used in computing devices include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Peripheral Component Interconnect (PCI) bus, the Video Electronics Standards Association (VESA) local bus, the Universal Serial Bus (USB) bus, and the PCI Express (PCI-E/PCIe) bus.

The processing module of the computing device proposed in the present invention is coupled to a bus. The processing module includes a register group or register space, which can be completely set on the processing chip of the processing module, or completely or partially set outside the processing chip and coupled to the processing chip via a dedicated electrical connection and/or via a bus. The processing module can be a central processing unit, a microprocessor, or any suitable processing element. If the computing device is a multi-processor device, that is, the computing device includes multiple processing modules, then the processing modules included in the computing device are the same or similar, and are coupled and communicated through a bus. In some embodiments, the processing module can interpret a computer instruction or a series of multiple computer instructions to perform specific calculations or operations, such as mathematical operations, logical operations, data comparison, copying/moving data, etc., to drive other hardware components in the computing device or run an operating system or execute various programs and/or modules. The computer instructions can be assembly language instructions, instruction set architecture instructions, machine instructions, machine-related instructions, microinstructions, firmware instructions, or source code or object code written in any combination of one or more programming languages, and the computer instructions can be executed entirely on a single computing device, partially on a single computing device, or partially on one computing device and partially on another connected computing device. The above-mentioned programming languages include object-oriented programming languages such as Common Lisp, Python, C++, Objective-C, Smalltalk, Delphi, Java, Swift, C#, Perl, Ruby, etc., and conventional procedural programming languages such as C or other similar programming languages.

Computing devices usually also include one or more chipsets. The processing module of the computing device can be coupled to the chipset or electrically connected to the chipset through a bus. The chipset is composed of one or more integrated circuits (ICs), including a memory controller and a peripheral input/output (I/O) controller, etc. In other words, the memory controller and the peripheral input/output (I/O) controller can be included in one IC, or can be implemented using two or more ICs. The chipset usually provides input/output and memory management functions, as well as multiple general-purpose and/or dedicated registers, timers, etc., wherein the above-mentioned general-purpose and/or dedicated registers and timers can be accessed or used by one or more processing modules coupled or electrically connected to the chipset. In some embodiments, the chipset may also be part of the processing module.

The processing module of a computing device can also access data from memory modules and mass storage areas installed on the computing device through a memory controller. The aforementioned memory modules include any type of volatile memory and/or non-volatile memory (NVRAM), such as static random access memory (SRAM), dynamic random access memory (DRAM), read-only memory (ROM), and flash memory. The aforementioned mass storage area can include any type of storage device or storage media, such as a hard drive, optical disc, flash drive, memory card, solid-state drive (SSD), or any other storage device. In other words, the memory controller can access data in static random access memory (SRAM), dynamic random access memory (DRAM), flash memory, hard drives, and SSDs.

The processing module of a computing device can also connect to and communicate with peripheral devices or interfaces, such as peripheral output devices, peripheral input devices, communication interfaces, and various data or signal receiving devices, through a peripheral input/output controller via a peripheral input/output bus. A peripheral input device can be any type of input device, such as a keyboard, mouse, trackball, touchpad, or joystick. A peripheral output device can be any type of output device, such as a monitor or printer. The peripheral input device and peripheral output device can also be the same device, such as a touchscreen. The communication interface may include a wireless communication interface and/or a wired communication interface. The wireless communication interface may include an interface supporting wireless local area networks (such as Wi-Fi, Zigbee, etc.), Bluetooth, infrared, near-field communication (NFC), 3G/4G/5G mobile communication networks (cellular networks), or other wireless data transmission protocols. The wired communication interface may be an Ethernet device, a DSL modem, a cable modem, an asynchronous transfer mode (ATM) device, or an optical fiber communication interface and/or component. The data or signal receiving device may include a GPS receiver or a physiological signal receiver. The physiological signals received by the physiological signal receiver include, but are not limited to, heart rate and blood oxygen levels. The processing module can periodically poll various peripheral devices and interfaces, allowing the computing device to input and output data through various peripheral devices and interfaces, and also to communicate with another computing device having the hardware components described above.

The following first uses "Figure 1" as a system architecture diagram of the present invention, which is a system that uses sequential codes to control the signature sequence to complete online insurance applications, to illustrate the system operation of the present invention. As shown in "Figure 1", the system of the present invention includes a business client 110, an insurance server 120, a signature client 130, and a platform server 150. Among them, the business client 110, the insurance server 120, the signature client 130, and the platform server 150 can all be computing devices. It should be noted that the business client 110, the insurance server 120, the signature client 130, and the platform server 150 can use a wired or wireless network through a communication interface to transmit data or signals to other connected devices or equipment.

The business client 110 is typically a mobile phone, tablet computer, or laptop computer, but the present invention is not limited thereto. The business client 110 can be connected to the insurance server 120. In some embodiments, the business client 110 can also be connected to one or more signing clients 130, but the present invention is not limited thereto.

The business client 110 is responsible for inputting product identification data and signatory data, and for transmitting the input product identification data and signatory data to the insurance server 120. The product identification data input by the business client 110 corresponds to an insurance product, such as a product name, product number, etc., and can be generated by any number of words, letters, numbers, and symbols in any arrangement, but the product identification data is not limited to this; the signatory data input by the business client 110 includes one or more signatory identification data, and the input signatory data can be sent via voice calls, video calls, instant messaging, or emails. The signatory information may be obtained by an insurance agent using the business client 110 in one or more ways. In some embodiments, the signatory information also includes the signatory basic information corresponding to the signatory identification information. The signatory identification information may represent a specific signatory and include, but is not limited to, an ID number, passport number, mobile phone number, email account, etc. The signatory basic information may include the signatory's name, gender, date of birth, residential address, correspondence address, etc.

Generally speaking, the business client 110 can execute a specific application and display a data input interface through the executed application for inputting product identification data and signatory information. In some embodiments, upon receiving a guidance message from the platform server 150, the business client 110 can execute the application corresponding to the received guidance message. The guidance message includes, but is not limited to, a push message or a browser redirect command.

The business client 110 may also receive the guidance data transmitted by the insurance server 120 and provide the received guidance data to the signing client 130. For example, the business client 110 may display the guidance data for the signing client 130 to scan or identify. Alternatively, the guidance data may be transmitted to the signing client 130 via near-field communication (NFC), Bluetooth, a wireless local area network (e.g., Wi-Fi), a mobile communication network (e.g., 4G, 5G, etc.), etc., but the present invention is not limited thereto. The guidance data may be in the form of a URL or a two-dimensional barcode, but the present invention is not limited thereto.

The insurance server 120 can be connected to the platform server 150. Generally speaking, the insurance server 120 can be connected to the platform server 150 via an API, but the present invention is not limited thereto. In some embodiments, the insurance server 120 can also provide a connection to the business client 110 or can be connected to the signing client 130.

Insurance server 120 is responsible for receiving the product identification data and signatory information transmitted by business client 110 and generating an insurance agreement based on the received product identification data and signatory information. Generally speaking, insurance server 120 may store templates for insurance agreement forms for various insurance products and may add the signatory information to the insurance agreement form template for the insurance product corresponding to the product identification data. Specifically, the signatory identification data and the signatory's basic information are added to the corresponding locations in the template to generate the insurance agreement form. The insurance agreement form is typically in PDF format, but the present invention is not limited thereto.

The insurance server 120 is also responsible for generating policy identification data corresponding to the generated insurance application form. For example, the insurance server 120 may obtain the current time and generate policy identification data including the current time and product identification data. For example, the current time and product identification data may be combined into the policy identification data. However, the present invention is not limited to this. For example, the insurance server 120 may also generate policy identification data including the company identification data of the insurance company. In some embodiments, the insurance server 120 may also include the generated policy identification data in the insurance application form.

The insurance server 120 is also responsible for generating navigation data corresponding to each signing client 130. The navigation data generated by the insurance server 120 may include connection information, policy identification data, and a sequence code. In some embodiments, the navigation data generated by the insurance server 120 may also include company identification data of the insurance company. More specifically, the connection message may include the network address or domain name of the platform server 150, or may include an API path provided by the platform server 150, but the present invention is not limited thereto. The sequence code may represent the signing sequence of the signatories corresponding to the signatory identification information in the received signatory data, for example, using Arabic numerals such as 1, 2, 3, etc. or English letters such as A, B, C, etc. to represent the signing sequence of the signatories corresponding to the signatory identification information. It should be noted that the insurance server 120 can determine the signing order of the signatories based on the signatory's identity as indicated in the signatory data. For example, the insurance server 120 can pre-define the signing order of signatories with different identities in each insurance product and read the signing order of signatories with different identities in the corresponding insurance product based on the product identification data. Alternatively, the insurance server 120 can obtain the signing order of signatories with different identities from a template for generating an insurance agreement.

The insurance server 120 may also transmit the generated guidance data to the business client 110, or may transmit the guidance data to the signing client 130. For example, it should be noted that the insurance server 120 may first obtain the salesperson information corresponding to the business client 110 and the signatory information of each signatory in the received signatory information, and then transmit the guidance data to the business client 110 and/or the signing client 130 via text message, email, instant messaging, push notification, etc. based on the mobile phone number, email account, instant messaging account, and insurance company application identification information in the salesperson information or each signatory information.

In some embodiments, the insurance server 120 may also receive the policy identification data and sequence code transmitted by the platform server 150, and may determine whether the received sequence code matches the signature sequence corresponding to the received policy identification data to generate a corresponding judgment result, and may return the generated judgment result to the platform server 150. The insurance server 120 may establish a signature sequence corresponding to the generated policy identification data when generating the policy identification data, and may check whether the received sequence code is consistent with the signature sequence corresponding to the policy identification data when receiving the policy identification data. If so, it means that the sequence code is consistent with the signature sequence, and the insurance server 120 may update the signature sequence (for example, update the signature sequence to the order of the signature sequence). The order code of the next signatory is obtained, and the signatory identification data corresponding to the order code can be obtained. The obtained signatory identification data can be added to the judgment result, thereby returning the signatory identification data to the platform server 150. Conversely, if the received order code does not match the signing order, the insurance server 120 can determine that the order code does not conform to the signing order. The signing order generally indicates the order in which the signatories corresponding to the policy identification data are currently or next to sign the insurance consent form.

The insurance server 120 may also receive a request for an insurance consent form from the platform server 150 and transmit the requested insurance consent form to the platform server 150. The insurance server 120 may also receive an insurance consent form signed by all signatories from the platform server 150 and store the received insurance consent form. Alternatively, the storage path of the received insurance consent form and the corresponding policy identification data may be stored as a single piece of data in a file or database. The insurance server 120 may store the insurance consent form in a storage medium installed in the insurance server 120, or in a storage device or data server connected to the insurance server 120 via a network or physical line, or may encrypt the insurance consent form and publish it to the blockchain 190 or other private blockchain. Similarly, a file or database storing the storage path and policy identification data may be included in the insurance server 120, or in a storage device or data server connected to the insurance server 120 via a network or physical line.

The insurance server 120 may also receive the notification message sent by the platform server 150 , generate a corresponding guidance message according to the notification message, and provide the generated guidance message to the signature client 130 . In some embodiments, the notification message may include policy identification data and a notification code. The insurance server 120 may obtain the signing order based on the policy identification data and may send a guidance message to the corresponding signatory based on the notification code. For example, when the notification code indicates re-signing, the insurance server 120 may send the guidance message to the signatory ranked first in the signing order, and may delete the policy identification data and the insurance consent form corresponding to the policy identification data. The insurance server 120 may also regenerate the policy identification data and retain the corresponding signing order. When the notification code indicates re-signing, the insurance server 120 may send the guidance message to the signatory in the signing order corresponding to the sequence code in the notification code, etc.

The signing client 130 can be a mobile phone, laptop, desktop computer, smart TV, game console, etc., but the present invention is not limited thereto. The signing client 130 can be connected to the platform server 150. In some embodiments, the signing client 130 can also be connected to the insurance server 120.

Signature client 130 is responsible for obtaining navigation data generated by insurance server 120. For example, signature client 130 can scan navigation data displayed by business client 110 using an image capture module within signature client 130. It can also receive navigation data sent by business client 110 or insurance server 120 via a communication interface, or download navigation data from an email server or instant messaging server.

Signing client 130 can decode the received navigation data to obtain the connection information, policy identification information, and sequence code. Signing client 130 is also responsible for establishing a connection with platform server 150 based on the connection information in the received navigation data and transmitting the policy identification information and sequence code in the navigation data to platform server 150. Signing client 130 is also responsible for entering identification information and transmitting the input identification information to platform server 150.

In some embodiments, the signing client 130 may also select an authentication method and transmit the selected authentication method to the platform server 150. Generally speaking, upon receiving a redirect message from the platform server 150, the signing client 130 may display an authentication method selection interface according to the received redirect message, allowing the user to select an authentication method, such as selecting a web page, mobile phone, or application for authentication.

The signing client 130 can also receive the first guidance message sent by the platform server 150, and can open the application corresponding to the selected authentication method according to the received first guidance message, and can obtain the identity identification data corresponding to the authentication method through the application. For example, if the signing client 130 chooses to authenticate with the application, then when the received guidance message indicates that the application that can communicate with the platform server 150 is to be opened, the signing client 130 can first determine whether the signing client 130 has installed the application. If not, the signing client 130 can open the browser program or the application installation program and provide the browser program or the application installation program with the identity information. The user of the signing client 130 (i.e., the signatory) is prompted to install the application on the signing client 130. If the signing client 130 has already installed the application, the signing client 130 can activate the application, allowing the application to log in to the application using a pre-registered account by entering an account number and password or biometrics. After the signatory logs in to the application, the application reads the configured identity information.

The signing client 130 may also receive a second guidance message sent by the platform server 150. The application executed by the signing client 130 may use the identity information obtained according to the second guidance message to perform identity authentication via the mobile communication network. When the identity information passes the authentication, the application may transmit the authenticated identity information to the platform server 150 to complete the registration of the identity information.

The signing client 130 is also responsible for receiving the insurance agreement sent by the platform server 150 , signing the received insurance agreement, and returning the signed insurance agreement to the platform server 150 . It should be noted that, as the signing order of the signatories is different, the number of times the insurance consent form received by the signature client 130 used by each signatory is signed will also be different. That is to say, if the signatory's signing order is the first signature, the insurance consent form received by the signature client 130 will not be signed by anyone. If the signatory's signing order is the second signature, the insurance consent form received by the signature client 130 will be signed by the signatory with the first signature order. If the signatory's signing order is the third signature, the insurance consent form received by the signature client 130 will be signed by the signatory with the first and second signature orders, and so on.

The signing client 130 may also receive the redirect message sent by the platform server 150 and connect to the insurance server 120 according to the received redirect message.

The platform server 150 can be connected to the insurance server 120 and can provide a connection to the signing client 130. Generally speaking, the platform server 150 can provide a connection to the signing client 130 via an API, but the present invention is not limited thereto.

The platform server 150 is responsible for receiving the policy identification data and sequence code transmitted by the signature client 130, and is responsible for determining whether the received sequence code matches the signature sequence corresponding to the received policy identification data. The platform server 150 can establish a signature sequence corresponding to the policy identification data when it first receives the policy identification data, and can compare the received sequence code with the signature sequence when it subsequently receives the same policy identification data to see if they are the same. If so, it means that the sequence code is consistent with the signature sequence, and the platform server 150 can update the signature sequence corresponding to the policy identification data to a sequence code with the next arrangement sequence. Otherwise, the platform server 150 can determine that the sequence code does not meet the signature sequence.

The platform server 150 may also transmit the received policy identification data and sequence code to the insurance server 120, and may receive a determination result returned by the insurance server 120, thereby allowing the insurance server 120 to determine whether the received sequence code matches the signature sequence corresponding to the received policy identification data.

The platform server 150 is also responsible for obtaining the signatory identification data corresponding to the sequence code from the insurance server 120 when determining that the received sequence code matches the signature sequence corresponding to the received policy identification data. More specifically, if the platform server 150 does not determine whether the sequence code matches the signature sequence through the insurance server 120, and the platform server 150 determines that the sequence code matches the signature sequence, it connects to the insurance server 120 and requests the signatory identification data corresponding to the sequence code from the insurance server 120. If the platform server 150 determines whether the sequence code complies with the signing sequence through the insurance server 120, and if the sequence code complies with the signing sequence, the platform server 150 can directly obtain the signatory identification data corresponding to the sequence code from the determination result returned by the insurance server 120. The platform server 150 can also generate a corresponding prompt message (such as a prompt message indicating that the signing sequence does not comply) when it determines that the received sequence code does not comply with the signing sequence, and can return the generated prompt message to the signature client 130.

The platform server 150 may also generate a redirect message displaying an identity verification method selection interface when determining that the received sequence code matches the signing sequence corresponding to the received policy identification data, and may transmit the generated redirect message to the signing client 130; the platform server 150 may also receive the identity verification method selected by the signing client 130, and may generate a corresponding first guidance message based on the received identity verification method, and may transmit the generated first guidance message to the signing client 130.

The platform server 150 may also receive identification data transmitted by the signing client 130 and, based on the received identification data, may generate a second guidance message when determining that the signing client 130 is not registered, and transmit the generated second guidance message to the signing client 130. The platform server 150 may also receive identification data transmitted by an application executed by the signing client 130 and use the received identification data to complete the registration process.

The platform server 150 is also responsible for receiving the identity information transmitted by the signing client 130 and determining whether the received identity information matches the signatory identification information received from the insurance server 120. If the identity information does not match the signatory identification information, the platform server 150 may generate a corresponding prompt message (e.g., a prompt message indicating that the signatory's identity is incorrect) and may return the generated prompt message to the signing client 130.

The platform server 150 is also responsible for obtaining the insurance consent form corresponding to the received policy identification data when it determines that the received identity identification data matches the signatory identification data. If the platform server 150 is receiving the policy identification data for the first time or does not have an insurance consent form corresponding to the policy identification data stored, the platform server 150 may transmit the policy identification data to the insurance server 120 and receive the insurance consent form returned by the insurance server 120. If the platform server 150 already has an insurance consent form stored, the platform server 150 may read the stored insurance consent form corresponding to the policy identification data. Generally speaking, the insurance agreement stored in the platform server 150 has usually been signed by one or more signing clients 130.

The platform server 150 is also responsible for transmitting the obtained insurance agreement to the signing client 130. Before transmitting the insurance agreement to the signing client 130, the platform server 150 may also verify that the signatures of the signatories listed in the previous signing order have been completed. For example, before transmitting the insurance agreement to the signing client 130 used by the second signatory, the platform server 150 will verify that the insurance agreement includes the signature of the first signatory; before transmitting the insurance agreement to the signing client 130 used by the third signatory, the platform server 150 will verify that the insurance agreement includes the signatures of the first and second signatories, and so on.

The platform server 150 is also responsible for receiving the signed insurance agreement form returned by the signing client 130. After receiving the insurance agreement form returned by the signing client 130, the platform server 150 can also check whether the signatures of the signatories ranked before the current signatory have been completed. For example, when receiving the insurance agreement form returned by the signing client 130 used by the signatory with the first signing order, the platform server 150 can confirm whether the insurance agreement form contains the signature of the signatory with the first signing order; when receiving the insurance agreement form returned by the signing client 130 used by the signatory with the second signing order, the platform server 150 can confirm whether the insurance agreement form contains the signatures of the signatories with the first and second signing orders, and so on.

The platform server 150 may also generate a redirect message to connect to the insurance server 120 upon receiving the signed insurance agreement form returned by the signing client 130 , and may transmit the generated redirect message to the signing client 130 .

Upon receiving the signed insurance application agreement from the signing client 130, the platform server 150 may perform a specific operation on the policy identification data corresponding to the insurance application agreement and the sequence code corresponding to the user of the signing client 130 to generate operation result data. The generated operation result data may then be published to the blockchain 190 for storage. The specific operation described above includes, but is not limited to, a hash operation.

The platform server 150 may also determine whether the validity period corresponding to the received policy identification data has expired. Among them, the validity time mentioned in the present invention includes but is not limited to the case validity time, identity verification time, and document signing time. More specifically, the platform server 150 can generate the corresponding case validity time when the policy identification data is first received, generate the identity verification time each time the policy identification data is received, and generate the document signing time when it is determined that the received identity identification data matches the signatory identification data. Generally speaking, the case validity time, identity verification time, and document signing time can be the current time plus the corresponding predetermined time length, and the case validity time, identity verification time, and document signing time are not necessarily the same. For example, the case validity time can be one day or 12 hours, the identity verification time can be 10 minutes or 300 seconds, and the document signing time can be 1 hour or 30 minutes, etc., but the present invention is not limited to this. Generally speaking, the platform server 150 can check whether various validity periods have expired each time it receives policy identification data, but the present invention is not limited to this. For example, the platform server 150 can also check whether the validity period has expired at regular intervals or at a predetermined time after generating various validity periods.

The platform server 150 may also generate a corresponding notification message when determining that the validity period has expired and transmit the generated notification message to the insurance server 120. In some embodiments, the platform server 150 may generate a notification message including the policy identification data and a re-signing request when the validity period of a case expires. It may also generate a notification message including the policy identification data and a re-signing request when the identity verification time or document signing time expires. The re-signing notification message typically also includes a sequence code.

When receiving the signed insurance agreement form returned by the signing client 130, the platform server 150 can also determine whether the sequence code corresponding to the user of the signing client 130 is the last in the signing sequence. If the sequence code is the last in the signing sequence, the platform server 150 can sign the received insurance agreement form and transmit the re-signed insurance agreement form to the insurance server 120.

The platform server 150 may also update the signatory membership data corresponding to the signatory identification data when determining that the received identity identification data matches the signatory identification data. For example, it may determine whether the signatory's membership level has reached a predetermined level or is higher than the predetermined level. If so, the signatory's membership level will not be adjusted. If not, the platform server 150 may adjust the signatory's membership level to the predetermined level, etc., but the present invention is not limited to this.

Next, we will use an example to illustrate the operating system and method of the present invention. Please refer to Figure 2A for a flowchart of the method for completing online insurance applications by controlling the signature sequence according to a sequential code. In this example, it is assumed that the business client 110 is a tablet computer and the signing client 130 is a smartphone, but the present invention is not limited to this.

When the insurance agent uses the business client 110 to communicate with the customer via the Internet, if the customer confirms the insurance application, the insurance agent can use the present invention to provide the customer (insured person) with the online insurance application.

First, the business client 110 can input the product identification data of the insurance product and the signatory data of the signatory who needs to sign to complete the insurance application, and can transmit the input product identification data and signatory data to the insurance server 120 (step 201). In this embodiment, it is assumed that the insurance agent can open the application supporting the present invention, and after the customer (insured) confirms the insurance product to be insured, the insurance agent can ask the customer (insured) for the information of the insurer and the insured through one or more methods such as voice call, video call, instant messaging, or email, and operate the business client 110 to select in the application The proposer enters the insurance product they wish to purchase and their respective signatory identification information, such as their ID number and mobile phone number, as well as their basic information, such as their name, birthday, and address. After the insurance agent completes the input, the application transmits the signatory information, including the signatory identification information and basic information, and the product identification information of the insurance product to the insurance server 120.

After the insurance server 120 receives the product identification data and the signatory data transmitted by the business client 110, the insurance server 120 may generate an insurance consent form and corresponding policy identification data based on the received product identification data and the signatory data (step 210). In this embodiment, it is assumed that the insurance server 120 can obtain the current time including year, month, day, hour, minute, and second, and can combine the current date with product identification data as policy identification data, for example, 20230208092403-A0013004, where 20230208092403 is the current time and A0013004 is the product identification data of the insurance product; the insurance server 120 can read the corresponding consent form template based on the product identification data, and add the signatory identification data of the proposer and the insured included in the signatory data, the signatory basic information, and the generated policy identification data to the relative positions of the read consent form template, thereby generating an insurance consent form.

After the insurance server 120 generates the policy identification data, the insurance server 120 may also generate a sequence code corresponding to each signatory and a navigation message including a connection message to the platform server 150 and the generated policy identification data and sequence code (step 220). In this embodiment, assuming that the signatories are the proposer and the insured, and the signing order defined by the insurance server 120 is the proposer and the insured, the insurance server 120 can generate corresponding sequence codes for the proposer and the insured, such as A1 and B2, respectively. The insurance server 120 can also generate a multi-level message including a connection message of the platform server 150, the company code of the insurance company providing the insurance server 120, the generated policy identification data, and the sequence code corresponding to the proposer or the insured. The system may generate a URL for the policyholder containing the URL of the platform server 150 and the URI "comId=company code&caseId=policy identification data&actionId=A1", and generate a URL for the insured containing the URL of the platform server 150 and the URI "comId=company code&caseId=policy identification data&actionId=B2", or generate a QR code for each policyholder or insured to obtain the URL of the policyholder or insured.

After the insurance server 120 generates the corresponding navigation data for each signatory, the signing client 130 used by each signatory can obtain the corresponding navigation data generated by the insurance server 120 and transmit the policy identification data and sequence code in the navigation data to the platform server 150 based on the connection information in the navigation data (step 230). In this embodiment, it is assumed that the insurance server 120 can transmit the two generated guidance data corresponding to the policyholder and the insured to the business client 110. After the insurance agent receives the guidance data generated by the insurance server 120, the insurance agent can operate the business client 110 to first display the guidance data corresponding to the policyholder, so that the policyholder communicating with the insurance agent can operate the signature client 130 to intercept or scan the guidance data corresponding to the policyholder and can connect to the platform server according to the guidance data. The insurance server 120 may also transmit the guidance data to the signature client 130 used by the policyholder directly or indirectly via SMS, email, instant messaging, or push message, so that the policyholder can operate the signature client 130 (such as clicking on a URL or decoding a QR code) to connect the signature client 130 to the platform server 150 according to the guidance data and transmit the policy identification data and sequence code to the platform server 150.

After the platform server 150 receives the policy identification data and sequence code transmitted by the signature client 130, when it is determined that the sequence code received matches the signature sequence corresponding to the received policy identification data, the insurance server 120 obtains the signatory data corresponding to the received sequence code (step 250). In this embodiment, it is assumed that the platform server 150 can first read the signature sequence corresponding to the received policy identification data (i.e., A1), and compare the read signature sequence with the received sequence code. If not, the platform server 150 can determine that the sequence code does not match the signature sequence corresponding to the policy identification data, and the platform server 150 can generate a A prompt message indicating that the signature sequence does not match is generated and sent to the signature client 130 for display; if so, the platform server 150 can determine that the sequence code matches the signature sequence corresponding to the policy identification data, and the platform server 150 can transmit the policy identification data and the sequence code to the insurance server 120 through the API provided by the insurance server 120. The insurance server 1 20 can also read the signature sequence (A1) corresponding to the received policy identification data and compare whether the read signature sequence is the same as the received sequence code. If not, the insurance server 120 can generate a judgment result indicating that the sequence code does not match the signature sequence and can return the generated judgment result to the platform server 150. If so, the insurance server Server 120 may update the signature sequence corresponding to the policy identification data to B2, and may read the signatory data whose signature sequence matches the sequence code from the signatory data corresponding to the policy identification data, and generate a judgment result indicating that the sequence code matches the signature sequence and includes the read signatory data, and transmit the generated judgment result back to the platform server 150. After receiving the judgment result transmitted by the insurance server 120, if the judgment result indicates that the sequence code does not match the signature sequence, the platform server 150 can also generate a prompt message indicating that the signature sequence does not match and transmit it to the signature client 130 for display. If the judgment result indicates that the sequence code does match the signature sequence, the platform server 150 can also update the signature sequence corresponding to the policy identification data to B2 and obtain the signatory data that matches the sequence code from the judgment result.

After the signing client 130 transmits the policy identification data and sequence code in the guidance data to the platform server 150 according to the connection message in the guidance data (step 230), the signing client 130 can obtain the identity identification data of the user using the signing client 140 and transmit the obtained identity identification data to the platform server 150 (step 260). In this embodiment, assuming that as shown in the process of FIG. 2B , after the platform server 150 receives the policy identification data and sequence code transmitted by the signing client 130, it can generate a redirect message and transmit the generated redirect message to the signing client 130. After receiving the redirect message, the signing client 130 can provide the insurer (signer) with the authentication method selection interface according to the display. If the proposer chooses to use the application for identity verification, the signing client 130 may transmit the selected identity verification method to the platform server 150 (step 261). After receiving the identity verification method transmitted by the signing client 130, the platform server 150 may generate a first guidance message corresponding to the received identity verification method, such as a webpage or instruction to open the application or The generated first guidance message can be sent to the signing client 130 (step 262). After receiving the first guidance message sent by the platform server 150, the signing client 130 can open the corresponding application according to the received first guidance message (step 263). If the signing client 130 determines that the application is not installed, it can prompt the signatory to download and install the application. If the signing client 130 has the application installed, the signing client 130 can open the application. After the application is executed by the signing client 130, the signatory can be prompted to enter the account password or biometrics. After the account password or biometrics are verified, the signatory can obtain the identity identification data corresponding to the identity verification method (step 264) and transmit the obtained identity identification data to the platform server 150.

After the platform server 150 receives the identification data sent by the signature client 130, the platform server 150 can determine whether the received identification data has been registered (step 265). If so, the platform server 150 can skip the registration process. If not, the platform server 150 can perform the registration process, that is, the platform server 150 can generate a second boot message and can send the generated The second guidance message is sent to the signing client 130 (step 266). After receiving the second guidance message, the application executed by the signing client 130 can prompt the signatory to turn off WiFi to switch the network used to the mobile communication network, and use the obtained identity information to transmit it to the telecommunications server via the mobile communication network for identity authentication (step 267). The application executed by the signing client 130 may generate a corresponding verification result after identity authentication and may transmit the generated verification result to the platform server 150 (step 268). The platform server 150 may register the identity identification data when it determines that the received verification result message indicates that the identity identification data has passed identity authentication (step 269).

Returning to FIG. 2A , after the platform server 150 receives the identity identification data transmitted by the signing client 130 (step 260 ), the platform server 150 can determine whether the received identity identification data matches the obtained signatory identification data. If the received identity identification data matches the obtained signatory identification data, the platform server 150 can obtain the insurance consent form corresponding to the policy identification data previously transmitted by the signing client 130 and transmit the obtained insurance consent form to the signing client 130 (step 270 ). In this embodiment, it is assumed that the platform server 150 can determine whether an insurance consent form corresponding to the policy identification data is stored. If not, the platform server 150 can connect to the insurance server 120 to obtain the insurance consent form. If so, the platform server 150 can read the insurance consent form that has been signed at least once.

After the signing client 130 receives the insurance agreement sent by the platform server 150 , the signing client 130 may sign the received insurance agreement and return the signed insurance agreement to the platform server 150 (step 280 ).

Afterwards, the platform server 150 can generate a redirect message and transmit the generated redirect message to the signing client 130 (step 291) as shown in the process of "Figure 2C", so that after receiving the redirect message sent by the platform server 150, the signing client 130 connects to the insurance server 120 according to the received redirect message (step 292), so that the insurance server 120 can confirm that the signing client 130 has completed the signing of the insurance consent form; alternatively, the platform server 150 can also directly generate a signing completion message and transmit the generated signing completion message to the insurance server 120, so that the insurance server 120 can confirm that the signing client 130 has completed the signing of the insurance consent form after receiving the signing completion message.

After confirming that the signing client 130 has completed signing the insurance agreement, the insurance server 120 may send a guidance message corresponding to the next signatory to the signing client 130 used by the next signatory, so that the next signatory repeats the above steps 230 to 292 until all signatories have completed signing.

Thus, through the present invention, insurance agents can guide all signatories who need to sign the insurance policy to complete the signing of the insurance policy through the Internet.

In the above embodiment, after the signing client 130 returns the signed insurance agreement to the platform server 150 (step 280), the platform server 150 may also perform a specific operation such as a hash operation on the policy identification data and the sequence code to generate operation result data (step 295), as shown in the process of "Figure 2D", and may publish the generated operation result data to the blockchain 190 (step 296).

As shown in the process of "Figure 2E", the platform server 150 can also re-sign the insurance consent form signed and returned by the signature client 130 used by the last signatory (step 298) when the sequence code is determined to be the last in the signing sequence, and can transmit the re-signed insurance consent form to the insurance server 120 (step 299), so that the insurance server 120 stores the insurance consent form and records the policy identification information and the storage path of the insurance consent form.

In summary, the difference between the present invention and the prior art is that the insurance server generates the insurance consent form and the corresponding policy identification data based on the product identification data and the signatory data sent by the business client, and then generates the guidance data containing the policy identification data and the sequence code corresponding to the signatory. After the signature client obtains the guidance data, it transmits the policy identification data and the sequence code in the guidance data to the platform server according to the connection message in the guidance data, and transmits the identity identification data. The data is sent to the platform server. When the sequence code matches the signing sequence and the identity information matches the signatory identification information corresponding to the sequence code, the platform server transmits the insurance consent form to the signing client for signature. This technical means continues until all signatories have completed signing the insurance consent form. This technical means can solve the problem of previous technologies that online document signing services cannot provide multiple people with the same signature, thereby achieving the technical effect of reducing the time cost of sending paper signatures.

Furthermore, the method of the present invention for completing online insurance by controlling the signature sequence according to the sequence code can be implemented in hardware, software, or a combination of hardware and software. It can also be implemented in a centralized manner in a computer system or in a distributed manner with different components distributed across several interconnected computer systems.

While the embodiments disclosed above are limited to the present invention, these descriptions are not intended to directly limit the scope of patent protection for this invention. Any modifications or alterations in the form and details of the present invention made by a person skilled in the art without departing from the spirit and scope of this invention are within the scope of patent protection for this invention. The scope of patent protection for this invention shall remain subject to the scope of the attached patent application.

110: Business Client 120: Insurance Server 130: Signature Client 150: Platform Server 190: Blockchain Step 201: The business client enters product identification data and signatory information, and transmits the product identification data and signatory information to the insurance server. Step 210: The insurance server generates the insurance agreement and the corresponding policy identification data based on the product identification data and signatory information. Step 220: The insurance server generates a sequence code and guidance data. The guidance data includes a connection message, policy identification data, and sequence code. Step 230: The signing client obtains the guidance data from the insurance server and transmits the policy identification data and sequence code to the platform server according to the connection message. Step 250: When the sequence code matches the signing sequence corresponding to the policy identification data, the platform server obtains the signatory identification data corresponding to the sequence code from the insurance server. Step 260: The signing client obtains the identity identification data and transmits the identity identification data to the platform server. Step 261: The signing client selects the identity verification method and transmits it to the platform server. Step 262: The platform server generates a first guidance message corresponding to the identity verification method and transmits the first guidance message to the signing client. Step 263: The signing client opens the corresponding application based on the first guidance message. Step 264: The application obtains the identity identification data corresponding to the authentication method. Step 265: The platform server determines whether the identity identification data is registered. Step 266: The platform server generates a second guidance message and sends the second guidance message to the signing client. Step 267: The application uses the identity identification data to perform identity authentication via the mobile communication network based on the second guidance message. Step 268: The application generates and sends the corresponding authentication result to the platform server. Step 269: The platform server registers the identity identification data when the identity identification data passes the authentication. Step 270: When the platform server determines that the identity information matches the signatory identification information, it obtains the insurance consent form corresponding to the policy identification information and sends the insurance consent form to the signing client. Step 280: The signing client signs the insurance consent form and returns it to the platform server. Step 291: The platform server generates a redirect message and sends it to the signing client. Step 292: The signing client connects to the insurance server based on the redirect message. Step 295: The platform server performs a specific operation on the policy identification data and sequence code to generate the operation result data. Step 296: The platform server publishes the operation result data to the blockchain. Step 298: When the platform server determines that the sequence code is the last one in the signing sequence, it signs the insurance agreement. Step 299: The platform server sends the insurance agreement after the second signature to the insurance server.

Figure 1 is a system architecture diagram for completing online insurance applications by controlling the signature sequence according to a sequence code as proposed in the present invention. Figure 2A is a flow chart of the method for completing online insurance applications by controlling the signature sequence according to a sequence code as proposed in the present invention. Figure 2B is a flow chart of the method for the signature client to obtain identity identification information as proposed in the present invention. Figure 2C is a flow chart of the method for the platform server as proposed in the present invention to guide the signature client to connect to the insurance server. Figure 2D is a flow chart of the method for the platform server as proposed in the present invention to publish data to the blockchain. Figure 2E is a flow chart of the method for the platform server as proposed in the present invention to sign the insurance consent form.

Step 201: The business client enters product identification information and signatory information, and transmits the product identification information and signatory information to the insurance server.

Step 210: The insurance server generates the insurance agreement and corresponding policy identification data based on the product identification data and signatory information.

Step 220: The insurance server generates a sequence code and navigation data. The navigation data includes connection information, policy identification data, and sequence code.

Step 230: The signing client obtains the guidance data from the insurance server and sends the policy identification data and sequence code to the platform server based on the connection message.

Step 250: When the sequence code matches the signing sequence corresponding to the policy identification data, the platform server obtains the signatory identification data corresponding to the sequence code from the insurance server.

Step 260: The signing client obtains the identification information and sends it to the platform server.

Step 270: When the platform server determines that the identity information matches the signatory's identification information, it obtains the insurance consent form corresponding to the policy identification information and transmits the insurance consent form to the signing client.

Step 280: The signing client signs the insurance agreement and sends it back to the platform server.

Claims (10)

A system for completing online insurance applications by controlling the signature sequence using sequence codes. The system comprises at least: A business client for inputting product identification information and the signatory information of at least one signatory; An insurance server, configured to receive the product identification data and the at least one signatory's information, generate an insurance application and corresponding policy identification data based on the product identification data and the at least one signatory's information, obtain a signing sequence based on the at least one signatory's identity based on the product identification data, determine a sequence code based on the signing sequence and the at least one signatory's identity, and generate a navigation data, wherein the navigation data includes a connection message, policy identification data, and the sequence code; At least one signing client, corresponding to the at least one signatory, obtains the navigation data and the identity identification data of the at least one signatory through the insurance server; and A platform server is used to provide the at least one signature client with a connection according to the connection information in the guide data, and receive the policy identification data and the sequence code in the guide data sent by the at least one signature client, and when the sequence code matches the signature sequence corresponding to the policy identification data, the insurance server obtains a signatory identification data corresponding to the sequence code, and receives the signature sequence sent by the at least one signature client. The identity identification data is obtained, and when it is determined that the identity identification data matches the signatory identification data, the insurance agreement corresponding to the policy identification data is obtained and transmitted to the at least one signing client. The at least one signing client signs the insurance agreement and returns the signed insurance agreement to the platform server. The insurance server or the platform server then updates the signature sequence to the sequence code of the next signatory. A system for completing online insurance applications by controlling a signature sequence according to a sequential code as described in claim 1, wherein the at least one signing client is further configured to select an identity verification method and transmit the selected authentication method to the platform server, and to open an application corresponding to the authentication method in response to a first guidance message corresponding to the authentication method transmitted by the platform server, and to obtain identity identification data corresponding to the authentication method through the application. A system for completing online insurance applications by controlling the signature sequence according to a sequential code as described in claim 2, wherein the platform server is further configured to generate a second guidance message and transmit the second guidance message to the at least one signing client when determining that the identity identification data is not registered. The application then uses the identity identification data to perform identity verification via a mobile communication network based on the second guidance message, and transmits the identity identification data to the platform server to complete the registration of the identity identification data when the identity identification data passes the identity verification. A system for completing online insurance applications by controlling the signature sequence according to a sequence code as described in claim 1, wherein the platform server is further configured to generate a redirect message and transmit it to the at least one signing client upon receiving the signed insurance agreement form sent by the at least one signing client, and the at least one signing client is further configured to connect to the insurance server based on the redirect message. A system for completing online insurance applications by controlling the signature sequence according to a sequential code as described in claim 1, wherein the platform server is further configured to send a notification message to the insurance server when determining that an effective time corresponding to the policy identification data has expired, and the insurance server is further configured to regenerate the guidance data based on the notification message and provide it to the at least one signing client. A system for completing online insurance applications by controlling the sequence of signatures according to a sequence code as described in claim 1, wherein the platform server is further configured to, upon receiving the signed insurance application consent form, perform a specific operation on the policy identification data and the sequence code to generate an operation result data, and publish the operation result data to a blockchain, and/or, when determining that the sequence code is the last in the signature sequence, sign the signed insurance application consent form and transmit the re-signed insurance application consent form to the insurance server. A method for completing online insurance applications by controlling the signature sequence using sequence codes, the method comprising at least the following steps: A business client inputs product identification data and the signatory information of at least one signatory, and transmits the product identification data and the at least one signatory information to an insurance server; The insurance server generates an insurance application agreement and corresponding policy identification data based on the product identification data and the at least one signatory information; The insurance server obtains a signing sequence for the at least one signatory based on the product identification data, determines a sequence code based on the signing sequence and the at least one signatory's identity, and generates a navigation data comprising a connection message from a platform server, the policy identification data, and the sequence code. At least one signing client obtains the navigation data from the insurance server and transmits the policy identification data and the sequence code in the navigation data to the platform server based on the connection message in the navigation data. The at least one signing client corresponds to the at least one signatory. When the sequence code matches the signing sequence corresponding to the policy identification data, the platform server obtains the signatory identification data corresponding to the sequence code from the insurance server. The at least one signing client obtains identity identification data and transmits the identity identification data to the platform server. When the platform server determines that the identity identification data matches the signatory identification data, it obtains the insurance agreement corresponding to the policy identification data and transmits the insurance agreement to the at least one signing client. The at least one signing client signs the insurance agreement and transmits the signed insurance agreement to the platform server, causing the insurance server or the platform server to update the signature sequence to the next sequence code following the sequence code. A method for completing online insurance application by controlling the signature sequence according to a sequential code as described in claim 7, wherein the step of the at least one signing client obtaining the identity identification data comprises the step of the at least one signing client selecting an identity verification method and transmitting the identity verification method to the platform server, the platform server generating a first guidance message corresponding to the identity verification method and transmitting the first guidance message to the at least one signing client, and the step of the at least one signing client opening an application corresponding to the identity verification method according to the first guidance message to obtain the identity identification data corresponding to the identity verification method through the application. A method for completing online insurance application by controlling the signature sequence according to a sequential code as described in claim 8, wherein after the at least one signing client transmits the identity identification data to the platform server, the platform server generates a second guidance message when determining that the identity identification data is not registered based on the identity identification data and transmits the second guidance message to the at least one signing client, the application uses the identity identification data to perform identity verification via a mobile communication network based on the second guidance message, and transmits the identity identification data to the platform server to complete the registration of the identity identification data when the identity identification data passes the identity verification. A method for completing online insurance applications by controlling the signature sequence according to a sequence code as described in claim 7, wherein, after the at least one signing client transmits the signed insurance agreement to the platform server, the method further includes the platform server performing a specific operation on the policy identification data and the sequence code to generate an operation result data, storing the operation result data via a blockchain, and, when determining that the sequence code is the last in the signature sequence, signing the signed insurance agreement and transmitting the re-signed insurance agreement to the insurance server.