WO2019000996A1 - 核保信息处理的装置、方法及计算机可读存储介质 - Google Patents

核保信息处理的装置、方法及计算机可读存储介质 Download PDF

Info

Publication number
WO2019000996A1
WO2019000996A1 PCT/CN2018/077666 CN2018077666W WO2019000996A1 WO 2019000996 A1 WO2019000996 A1 WO 2019000996A1 CN 2018077666 W CN2018077666 W CN 2018077666W WO 2019000996 A1 WO2019000996 A1 WO 2019000996A1
Authority
WO
WIPO (PCT)
Prior art keywords
attachment
underwriting
page
mapping relationship
processing
Prior art date
Application number
PCT/CN2018/077666
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 WO2019000996A1 publication Critical patent/WO2019000996A1/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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/08—Insurance

Definitions

  • the present application relates to the field of communications technologies, and in particular, to an apparatus, method, and computer readable storage medium for core insurance information processing.
  • the purpose of the present application is to provide an apparatus, method and computer readable storage medium for underwriting information processing, which are intended to improve the efficiency of processing policy information.
  • the present application provides an apparatus for processing underwriting information, characterized in that the apparatus for processing underwriting information includes: a memory, a processor, and a memory stored on the processor and on the processor A system for running underwriting information processing, the system for performing the underwriting information processing being implemented by the processor to implement the following steps:
  • the present application further provides a method for processing underwriting information, and the method for processing the underwriting information includes:
  • the present application also provides a computer readable storage medium having stored on a system of underwriting information processing, the system of the underwriting information processing being executed by the processor to implement the underwriting information processing as described above The steps of the method.
  • the beneficial effects of the present application are: the application registers the component service for copying the attachment on the underwriting page and the pre-defined listening instruction for monitoring the attachment on the underwriting page, after the component service is initialized and the listening instruction is received, After listening to the attachment event on the underwriting page, the new service is copied on the underwriting page based on the component service and the drag event.
  • the user does not need to upload the same attachment repeatedly, the operation is quick and easy, and the policy information can be improved. Processing efficiency.
  • FIG. 1 is a schematic diagram of a hardware architecture of an apparatus for processing underwriting information according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of an embodiment of a method for processing underwriting information according to the present application
  • FIG. 3 is a schematic diagram of the refinement process of step S3 shown in FIG. 2.
  • first, second and the like in the present application are for the purpose of description only, and are not to be construed as indicating or implying their relative importance or implicitly indicating the number of technical features indicated. .
  • features defining “first” and “second” may include at least one of the features, either explicitly or implicitly.
  • the technical solutions between the various embodiments may be combined with each other, but must be based on the realization of those skilled in the art, and when the combination of the technical solutions is contradictory or impossible to implement, it should be considered that the combination of the technical solutions does not exist. Nor is it within the scope of protection required by this application.
  • FIG. 1 is a schematic diagram of an optional hardware architecture of the apparatus 1 for guarantee information processing in the present application.
  • the apparatus 1 for underwriting information processing may be a notebook computer, a PDA (Personal Digital Assistant), and a PAD.
  • the apparatus 1 for the underwriting information processing may include, but is not limited to, the system 10 for the underwriting information processing, the memory 11, the processor 12, and the display 13 which are communicably connected to each other through a system bus.
  • FIG. 2 only shows the device 1 with the underwriting information processing of the components 10-13, but it should be understood that not all of the illustrated components are required to be implemented, and alternative implementations may be more or less. s component.
  • the memory 11 includes at least one type of readable storage medium including a flash memory, a hard disk, a multimedia card, a card type memory (eg, SD or DX memory, etc.), and a random access memory (RAM). , static random access memory (SRAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), programmable read only memory (PROM), magnetic memory, magnetic disk, optical disk, and the like.
  • the memory 11 may be an internal storage unit of the device 1 for the underwriting information processing, such as a hard disk or memory of the device 1 for the underwriting information processing.
  • the memory 11 may also be an external storage device of the device 1 for the underwriting information processing, for example, a plug-in hard disk equipped on the device 1 for the underwriting information processing, and a smart memory card (Smart Media Card, SMC), Secure Digital (SD) card, Flash Card, etc.
  • the memory 11 can also include both the internal storage unit of the device 1 for the underwriting information processing and its external storage device.
  • the memory 11 is generally used to store various types of application software installed in the apparatus 1 for the underwriting information processing, for example, the program code of the system 10 for the underwriting information processing. Further, the memory 11 can also be used to temporarily store various types of data that have been output or are to be output.
  • the processor 12 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments.
  • the processor 12 is typically used to control the overall operation of the device 1 for the underwriting information processing.
  • the processor 12 is configured to run program code or processing data stored in the memory 11, such as the system 10 that runs the underwriting information processing, and the like.
  • the display 13 may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode) touch sensor, or the like in some embodiments.
  • the display 13 is for displaying information processed in the device 1 for underwriting information processing and a user interface for displaying visualization, such as a check-up page or the like.
  • system 10 of the above-mentioned underwriting information processing is implemented by the processor 12 to implement the following steps:
  • Step S1 pre-registering a component service for copying an attachment on the underwriting page, and predefining a listening instruction for monitoring an attachment on the underwriting page;
  • the attachment is the image on the underwriting page in the underwriting process, for example, the ID card image of the insured, the ID card image of the insured, the driving license image, etc.
  • the attachments on the underwriting page generally include multiple, underwriting
  • the page includes multiple underwriting categories.
  • the pre-registered component service is preferably an extended AngularJS (front-end framework) component service that enables the copying of attachments on the underwriting page. After the component service runs, the user operates on the underwriting page, and the component service is used to copy the attachments on the underwriting page that need to be copied.
  • AngularJS front-end framework
  • the embodiment further defines a listening instruction for monitoring an attachment on the underwriting page.
  • a shortcut key (such as a CTRL button) may be registered.
  • the monitoring instruction is triggered, and the monitoring instruction is triggered. Then listen to the attachments on the underwriting page.
  • the attachment after the attachment is uploaded to the page cache for the first time and displayed on the underwriting page, the attachment does not need to be uploaded again, and the registered component service can be used to copy the attachment displayed on the underwriting page.
  • Step S2 after the component service is initialized and receives the monitoring instruction, whether the attachment on the underwriting page is monitored for a drag event;
  • the component service when the device 1 of the underwriting information processing is started, the component service is initialized. If the component service is not initialized after the device 1 of the underwriting information processing is started, the component service may be initialized by the shortcut instruction, or View the unopened component service in the service management tool and click to initialize the component service.
  • the drag event of the attachment on the underwriting page is monitored, and specifically, the drag event of the attachment on the underwriting page may be utilized by the predetermined thread. Listening, if the attachment on the underwriting page is selected and moved, it can be determined that the attachment has a drag event.
  • Step S3 If a drag event occurs on the attachment on the underwriting page, a new attachment is copied on the underwriting page based on the component service and the drag event.
  • the component service may be used to copy the dragged accessory. Specifically, the user clicks on a core on the underwriting page. Attach the attachment in the classification and drag it to the other underwriting classification in the underwriting page. After releasing the attachment, the component service copies the attachment at the location where the attachment is released, so that a new attachment is copied at the location. .
  • the embodiment registers a component service for copying an attachment on the underwriting page and a pre-defined listening instruction for monitoring an attachment on the underwriting page, after the component service is initialized and the listening instruction is received, If a drag-and-drop event occurs on an attachment on the underwriting page, a new attachment is copied on the underwriting page based on the component service and the drag-and-drop event, and the user does not need to repeatedly upload the same attachment, which is quick and easy, and can improve the policy. Information processing efficiency.
  • the method specifically includes:
  • the page position of the dragged attachment on the underwriting page is recorded, specifically, the recorded dragged Attach the coordinates (x, y) on the underwriting page and render on the area centered on the coordinates (x, y), then copy the attachment to get the new attachment.
  • a location identifier ID of the new attachment on the underwriting page is also set in the page data corresponding to the underwriting page, wherein the location identifier ID may be, for example, a random 10-digit number, and the cache is set.
  • the location identifier ID enables the new attachment to be displayed on the underwriting page.
  • the attachment after the attachment has a drag event, the attachment is rendered at the page position at the end of the drag event to copy the new attachment, so that the same attachment in the different underwriting classification does not need to be repeatedly uploaded, but dragged ⁇ Attachment and release can be copied to get new attachments, which is quick and easy to operate.
  • the system 10 of the underwriting information processing further implements the following steps:
  • the device 1 for the underwriting information processing uploads the attachment to the image information library, establishes a mapping relationship between the uploaded attachment and the new attachment, and stores the mapping relationship.
  • the mapping relationship may be Stored in the mapping table. This way, it is not necessary to upload the new attachment to the image repository. Subsequent to the different underwriting classifications on the underwriting page, you need to use the same attachments as the attachment, and you do not need to upload the attachments to the image repository again, so that multiple identical attachments are not stored in the image repository, saving images.
  • the storage space of the information base reduces interaction with the image information base and reduces storage and maintenance costs.
  • the system 10 for the underwriting information processing when executed by the processor 12, the following steps are further implemented: when the deletion instruction for deleting the attachment is received Obtain all attachments that have a mapping relationship with the attachment, and delete the attachments and all attachments that have a mapping relationship.
  • the attachment on the underwriting page is deleted, if the attachment to be deleted has multiple attachments having a mapping relationship, the attachment and the attachment having the mapping relationship are also deleted at one time, specifically, Upon receiving the delete instruction for deleting the attachment, all the attachments having a mapping relationship with the attachment are acquired according to the attachment, the attachment is deleted, and the location identifier ID of each of the attachments in the page data corresponding to the underwriting page is deleted.
  • a deletion operation may delete the underwriting page as all the same attachments, and the operation is quick and convenient.
  • the following steps are further implemented: synchronizing the attachment information of the accessory to the location
  • the attachment has all the attachments of the mapping relationship.
  • the attachment information includes an expiration date start time, an expiration date end time, and the like, and the attachment information of the attachment on the underwriting page is synchronized with the attachment information of all the attachments in the attachment relationship.
  • the attachment information of the attachment on the underwriting page is changed or updated, the attachment letter of all attachments having a mapping relationship with the attachment is also changed or updated, and the repeated change or update operation is reduced.
  • FIG. 2 is a schematic flowchart of an embodiment of a method for processing underwriting information according to an embodiment of the present invention.
  • the method for processing the underwriting information includes the following steps:
  • Step S1 pre-registering a component service for copying an attachment on the underwriting page, and predefining a listening instruction for monitoring an attachment on the underwriting page;
  • the attachment is the image on the underwriting page in the underwriting process, for example, the ID card image of the insured, the ID card image of the insured, the driving license image, etc.
  • the attachments on the underwriting page generally include multiple, underwriting
  • the page includes multiple underwriting categories.
  • the pre-registered component service is preferably an extended AngularJS (front-end framework) component service that enables the copying of attachments on the underwriting page. After the component service runs, the user operates on the underwriting page, and the component service is used to copy the attachments on the underwriting page that need to be copied.
  • AngularJS front-end framework
  • the embodiment further defines a listening instruction for monitoring an attachment on the underwriting page.
  • a shortcut key (such as a CTRL button) may be registered.
  • the monitoring instruction is triggered, and the monitoring instruction is triggered. Then listen to the attachments on the underwriting page.
  • the attachment after the attachment is uploaded to the page cache for the first time and displayed on the underwriting page, the attachment does not need to be uploaded again, and the registered component service can be used to copy the attachment displayed on the underwriting page.
  • Step S2 after the component service is initialized and receives the monitoring instruction, whether the attachment on the underwriting page is monitored for a drag event;
  • the component service when the device 1 of the underwriting information processing is started, the component service is initialized. If the component service is not initialized after the device 1 of the underwriting information processing is started, the component service may be initialized by the shortcut instruction, or View the unopened component service in the service management tool and click to initialize the component service.
  • the drag event of the attachment on the underwriting page is monitored, and specifically, the drag event of the attachment on the underwriting page may be utilized by the predetermined thread. Listening, if the attachment on the underwriting page is selected and moved, it can be determined that the attachment has a drag event.
  • Step S3 If a drag event occurs on the attachment on the underwriting page, a new attachment is copied on the underwriting page based on the component service and the drag event.
  • the component service may be used to copy the dragged accessory. Specifically, the user clicks on a core on the underwriting page. Attach the attachment in the classification and drag it to the other underwriting classification in the underwriting page. After releasing the attachment, the component service copies the attachment at the location where the attachment is released, so that a new attachment is copied at the location. .
  • the embodiment registers a component service for copying an attachment on the underwriting page and a pre-defined listening instruction for monitoring an attachment on the underwriting page, after the component service is initialized and the listening instruction is received, If a drag-and-drop event occurs on an attachment on the underwriting page, a new attachment is copied on the underwriting page based on the component service and the drag-and-drop event, and the user does not need to repeatedly upload the same attachment, which is quick and easy, and can improve the policy. Information processing efficiency.
  • the step S3 includes:
  • the page position of the dragged attachment on the underwriting page is recorded, specifically, the recorded dragged Attach the coordinates (x, y) on the underwriting page and render on the area centered on the coordinates (x, y), then copy the attachment to get the new attachment.
  • a location identifier ID of the new attachment on the underwriting page is also set in the page data corresponding to the underwriting page, wherein the location identifier ID may be, for example, a random 10-digit number, and the cache is set.
  • the location identifier ID enables the new attachment to be displayed on the underwriting page.
  • the attachment after the attachment has a drag event, the attachment is rendered at the page position at the end of the drag event to copy the new attachment, so that the same attachment in the different underwriting classification does not need to be repeatedly uploaded, but dragged ⁇ Attachment and release can be copied to get new attachments, which is quick and easy to operate.
  • the method further includes: uploading the accessory to the image information library, and establishing the uploaded accessory and the new accessory. Mapping relationships and storing the mapping relationships.
  • the device 1 for the underwriting information processing uploads the attachment to the image information library, establishes a mapping relationship between the uploaded attachment and the new attachment, and stores the mapping relationship.
  • the mapping relationship may be Stored in the mapping table. This way, you do not need to upload the new attachment to the image repository. Subsequent to the different underwriting classifications on the underwriting page, you need to use the same attachments as the attachment, and you do not need to upload the attachments to the image repository again, so that multiple identical attachments are not stored in the image repository, saving images.
  • the storage space of the information base reduces interaction with the image information base and reduces storage and maintenance costs.
  • the method for processing the underwriting information further includes: when receiving the deletion instruction for deleting the attachment, acquiring all attachments that have a mapping relationship with the attachment. , delete the attachment and all attachments that have a mapping relationship.
  • the attachment on the underwriting page is deleted, if the attachment to be deleted has multiple attachments having a mapping relationship, the attachment and the attachment having the mapping relationship are also deleted at one time, specifically, Upon receiving the delete instruction for deleting the attachment, all the attachments having a mapping relationship with the attachment are acquired according to the attachment, the attachment is deleted, and the location identifier ID of each of the attachments in the page data corresponding to the underwriting page is deleted.
  • the one-time deletion operation can delete the underwriting page as all the same attachments, and the operation is quick and convenient.
  • the present application also provides a computer readable storage medium having stored on a system of underwriting information processing, the system of the underwriting information processing being implemented by the processor to implement the above-described underwriting information processing The steps of the method.
  • the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better.
  • Implementation Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in various embodiments of the present application.

Landscapes

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

Abstract

本申请涉及一种核保信息处理的装置、方法及计算机可读存储介质，所述核保信息处理的装置包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的核保信息处理的***，所述核保信息处理的***被所述处理器执行时实现如下步骤：预先注册用于复制核保页面上的附件的组件服务，并预先定义用于监听所述核保页面上的附件的监听指令；当所述组件服务初始化，并接收到监听指令后，监听在所述核保页面上的附件是否发生拖拽事件；若在所述核保页面上的附件发生拖拽事件，则基于所述组件服务及所述拖拽事件在所述核保页面上复制得到新的附件。本申请能够简化核保处理中上传附件的操作，提高处理保单信息的工作效率。

Description

核保信息处理的装置、方法及计算机可读存储介质
本申请要求于2017年6月25日提交中国专利局、申请号为201710490395.1、发明名称为“核保信息处理的装置、方法及计算机可读存储介质”的中国专利申请的优先权，其全部内容通过引用结合在申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种核保信息处理的装置、方法及计算机可读存储介质。
背景技术
近年来车险保单量和财意保单量越来愈大，同时保单的核保规则越来越严格，例如对于车险来说，需要审核更多的车辆的认证信息。用户在投保前经常需要在核保页面不同的核保分类信息中上传同一影像附件(例如被保人的身份证扫描件)，以便核保人员对不同的分类信息进行核保。现有技术中，用户在不同的核保分类信息中上传影像附件需要逐张进行上传，导致相同的影像附件需要用户重复进行上传，降低保单信息处理的工作效率。
发明内容
本申请的目的在于提供一种核保信息处理的装置、方法及计算机可读存储介质，旨在提高处理保单信息的工作效率。
为实现上述目的，本申请提供一种核保信息处理的装置，其特征在于，所述核保信息处理的装置包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的核保信息处理的***，所述核保信息处理的***被所述处理器执行时实现如下步骤：
S1，预先注册用于复制核保页面上的附件的组件服务，并预先定义用于监听所述核保页面上的附件的监听指令；
S2，当所述组件服务初始化，并接收到监听指令后，监听在所述核保页面上的附件是否发生拖拽事件；
S3，若在所述核保页面上的附件发生拖拽事件，则基于所述组件服务及所述拖拽事件在所述核保页面上复制得到新的附件。
为实现上述目的，本申请还提供一种核保信息处理的方法，所述核保信息处理的方法包括：
S1，预先注册用于复制核保页面上的附件的组件服务，并预先定义用于监听所述核保页面上的附件的监听指令；
S2，当所述组件服务初始化，并接收到监听指令后，监听在所述核保页面上的附件是否发生拖拽事件；
S3，若在所述核保页面上的附件发生拖拽事件，则基于所述组件服务及所述拖拽事件在所述核保页面上复制得到新的附件。
本申请还提供一种计算机可读存储介质，所述计算机可读存储介质上存储有核保信息处理的***，所述核保信息处理的***被处理器执行时实现如上述的核保信息处理的方法的步骤。
本申请的有益效果是：本申请注册用于复制核保页面上的附件的组件服务及预先定义用于监听核保页面上的附件的监听指令，在组件服务初始化及接收到监听指令后，如果监听到在核保页面上的附件发生拖拽事件，则基于组件服务及拖拽事件在核保页面上复制得到新的附件，不需要用户重复上传相同的附件，操作快捷简便，能够提高保单信息处理的工作效率。
附图说明
图1为本申请核保信息处理的装置一实施例的硬件架构的示意图；
图2为本申请核保信息处理的方法一实施例的流程示意图；
图3为图2所示步骤S3的细化流程示意图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅用以解释本申请，并不用于限定本申请。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
需要说明的是，在本申请中涉及“第一”、“第二”等的描述仅用于描述目的，而不能理解为指示或暗示其相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括至少一个该特征。另外，各个实施例之间的技术方案可以相互结合，但是必须是以本领域普通技术人员能够实现为基础，当技术方案的结合出现相互矛盾或无法实现时应当认为这种技术方案的结合不存在，也不在本申请要求的保护范围之内。
参阅图1，图1是本申请核保信息处理的装置1一可选的硬件架构的示意图，本实施例中，核保信息处理的装置1可以是笔记本电脑、PDA(个人数字助理)、PAD(平板电脑)等等的可移动设备，以及诸如数字TV、台式计算机、笔记本、服务器等等的固定终端。核保信息处理的装置1可包括，但不仅限于，可通过***总线相互通信连接的核保信息处理的***10、存储器11、处理器12、显示器13。需要指出的是，图2仅示出了具有组件10-13的核保信息处理的装置1，但是应理解的是，并不要求实施所有示出的组件，可以替代的实施更多或者更少的组件。
其中，所述存储器11至少包括一种类型的可读存储介质，所述可读存储介质包括闪存、硬盘、多媒体卡、卡型存储器(例如，SD或DX存储器等)、随机访问存储器(RAM)、静态随机访问存储器(SRAM)、只读存储 器(ROM)、电可擦除可编程只读存储器(EEPROM)、可编程只读存储器(PROM)、磁性存储器、磁盘、光盘等。在一些实施例中，所述存储器11可以是所述核保信息处理的装置1的内部存储单元，例如该核保信息处理的装置1的硬盘或内存。在另一些实施例中，所述存储器11也可以是所述核保信息处理的装置1的外部存储设备，例如该核保信息处理的装置1上配备的插接式硬盘，智能存储卡(Smart Media Card，SMC)，安全数字(Secure Digital,SD)卡，闪存卡(Flash Card)等。当然，所述存储器11还可以既包括所述核保信息处理的装置1的内部存储单元也包括其外部存储设备。本实施例中，所述存储器11通常用于存储安装于所述核保信息处理的装置1的各类应用软件，例如所述核保信息处理的***10的程序代码等。此外，所述存储器11还可以用于暂时地存储已经输出或者将要输出的各类数据。
所述处理器12在一些实施例中可以是中央处理器(Central Processing Unit，CPU)、控制器、微控制器、微处理器、或其他数据处理芯片。该处理器12通常用于控制所述核保信息处理的装置1的总体操作。本实施例中，所述处理器12用于运行所述存储器11中存储的程序代码或者处理数据，例如运行所述核保信息处理的***10等。
显示器13在一些实施例中可以是LED显示器、液晶显示器、触控式液晶显示器以及OLED(Organic Light-Emitting Diode，有机发光二极管)触摸器等。显示器13用于显示在核保信息处理的装置1中处理的信息以及用于显示可视化的用户界面，例如核保页面等。
其中，上述核保信息处理的***10被所述处理器12执行时实现如下步骤：
步骤S1，预先注册用于复制核保页面上的附件的组件服务，并预先定义用于监听所述核保页面上的附件的监听指令；
其中，附件为核保处理中核保页面上的影像，例如，投保人的身份证影 像、被保人的身份证影像、行驶证影像等等，核保页面上的附件一般包括多个，核保页面上包括多个核保分类。预先注册的组件服务优选为扩展的AngularJS(前端框架)组件服务，该组件服务能够实现对核保页面上的附件进行复制的功能。当组件服务运行后，用户在核保页面上操作，利用组件服务对核保页面上需要进行复制的附件进行复制。
本实施例还预先定义用于监听核保页面上的附件的监听指令，具体地，可以注册一快捷键(例如CTRL按键)，当用户按下该快捷键时，触发监听指令，在监听指令触发后对核保页面上的附件进行监听。
本实施例中，首次将附件上传至页面缓存并在核保页面上显示后，后续不需要再次上传该附件，可以利用所注册的组件服务实现对核保页面上显示的附件进行复制即可。
步骤S2，当所述组件服务初始化，并接收到监听指令后，监听在所述核保页面上的附件是否发生拖拽事件；
本实施例中，一般而言，当核保信息处理的装置1启动后组件服务初始化，若核保信息处理的装置1启动后组件服务未初始化，则可以通过快捷指令使得组件服务初始化，或者在服务管理工具中查看未开启的组件服务，并点击即可初始化该组件服务。
本实施例中，在触发监听指令后，监听在所述核保页面上的附件是否发生的拖拽事件，具体地，可以利用预定的线程对在核保页面上的附件是否发生的拖拽事件进行监听，若核保页面上的附件被选中并进行移动，则可以确定该附件发生了拖拽事件。
步骤S3，若在所述核保页面上的附件发生拖拽事件，则基于所述组件服务及所述拖拽事件在所述核保页面上复制得到新的附件。
本实施例中，组件服务初始化后如果在核保页面上的附件发生拖拽事件，则可以利用该组件服务实现对所拖拽的附件进行复制，具体地，用户点 击核保页面上某一核保分类中的附件，并拖动至核保页面中的其他核保分类中，在释放该附件后，在释放该附件的位置组件服务对附件进行复制，以在该位置上复制得到新的附件。
与现有技术相比，本实施例注册用于复制核保页面上的附件的组件服务及预先定义用于监听核保页面上的附件的监听指令，在组件服务初始化及接收到监听指令后，如果监听到在核保页面上的附件发生拖拽事件，则基于组件服务及拖拽事件在核保页面上复制得到新的附件，不需要用户重复上传相同的附件，操作快捷简便，能够提高保单信息处理的工作效率。
在一优选的实施例中，在上述图1的实施例的基础上，所述核保信息处理的***10被所述处理器12执行实现所述步骤S3时，具体包括：
S31，若在所述核保页面上的附件发生拖拽事件，记录所述附件在所述拖拽事件结束时对应的页面位置；
S32，基于所述组件服务在所述页面位置上渲染所述附件，以复制得到新的附件，设置所述新的附件在所述核保页面上的位置标识符ID，并缓存所述位置标识符ID。
本实施例中，当核保页面上的附件发生拖拽事件后，当监控到拖拽事件结束时，记录被拖拽的附件在核保页面上的页面位置，具体地，记录被拖拽的附件在核保页面上的坐标(x，y)，并在以该坐标(x，y)为中心的区域上进行渲染，然后复制该附件，得到新的附件。
此外，还在该核保页面对应的页面数据中设置该新的附件在所述核保页面上的位置标识符ID，其中，该位置标识符ID例如可以是随机的10位数，缓存所设置的该位置标识符ID，使得该新的附件能够在该核保页面上进行显示。
本实施例在附件发生拖拽事件后，在拖拽事件结束时的页面位置上渲染 附件，以复制得到新的附件，使得在不同的核保分类中相同的附件不需要重复上传，而是拖拽附件并释放即可以复制得到新的附件，操作快捷方便。
在一优选的实施例中，在上述图1的实施例的基础上，所述核保信息处理的***10被所述处理器12执行步骤S3之后，还实现如下步骤：
将所述附件上传至影像信息库中，建立上传后的附件与所述新的附件的映射关系并存储所述映射关系。
本实施例中，核保信息处理的装置1将附件上传至影像信息库中，建立上传后的附件与所述新的附件的映射关系，并存储所述映射关系，优选地，可以将映射关系存储在映射表中。这样，不需要将该新的附件也上传至影像信息库。后续在核保页面上不同的核保分类中需要使用与该附件相同的附件时，也不需要再次上传附件至影像信息库中，使得影像信息库中不会存储多个相同的附件，节省影像信息库的存储空间，减少了与影像信息库的交互，降低存储及维护成本。
在一优选的实施例中，在上述实施例的基础上，所述核保信息处理的***10被所述处理器12执行时，还实现如下步骤：当接收到删除所述附件的删除指令时，获取与所述附件存在映射关系的所有附件，删除所述附件及存在映射关系的所有附件。
本实施例中，当删除核保页面上的附件时，若所要删除的该附件存在多个具有映射关系的附件，则一次性将该附件及与其存在映射关系的附件也删除，具体地，在接收到删除附件的删除指令时，根据该附件获取与该附件存在映射关系的所有附件，删除该附件，以及将该所有附件分别在核保页面对应的页面数据中的位置标识符ID删除。
本实施例在上传错误的附件或者需要对附件进行修改时，一次删除操作 可以将核保页面当所有相同的附件进行删除，操作快捷方便。
在一优选的实施例中，在上述实施例的基础上，所述核保信息处理的***10被所述处理器12执行时，还实现如下步骤：将所述附件的附件信息同步给与所述附件存在映射关系的所有附件。
本实施例中，附件信息包括有效期限起始时间、有效期限结束时间等等，核保页面上的附件的附件信息与该附件存在映射关系的所有附件的附件信息是同步的。此外，若核保页面上的附件的附件信息变更或更新，则与该附件存在映射关系的所有附件的附件信也跟随变更或更新，减免了重复的变更或更新的操作。
如图2所示，图2为本申请核保信息处理的方法一实施例的流程示意图，该核保信息处理的方法包括以下步骤：
步骤S1，预先注册用于复制核保页面上的附件的组件服务，并预先定义用于监听所述核保页面上的附件的监听指令；
其中，附件为核保处理中核保页面上的影像，例如，投保人的身份证影像、被保人的身份证影像、行驶证影像等等，核保页面上的附件一般包括多个，核保页面上包括多个核保分类。预先注册的组件服务优选为扩展的AngularJS(前端框架)组件服务，该组件服务能够实现对核保页面上的附件进行复制的功能。当组件服务运行后，用户在核保页面上操作，利用组件服务对核保页面上需要进行复制的附件进行复制。
本实施例还预先定义用于监听核保页面上的附件的监听指令，具体地，可以注册一快捷键(例如CTRL按键)，当用户按下该快捷键时，触发监听指令，在监听指令触发后对核保页面上的附件进行监听。
本实施例中，首次将附件上传至页面缓存并在核保页面上显示后，后续 不需要再次上传该附件，可以利用所注册的组件服务实现对核保页面上显示的附件进行复制即可。
步骤S2，当所述组件服务初始化，并接收到监听指令后，监听在所述核保页面上的附件是否发生拖拽事件；
本实施例中，一般而言，当核保信息处理的装置1启动后组件服务初始化，若核保信息处理的装置1启动后组件服务未初始化，则可以通过快捷指令使得组件服务初始化，或者在服务管理工具中查看未开启的组件服务，并点击即可初始化该组件服务。
本实施例中，在触发监听指令后，监听在所述核保页面上的附件是否发生的拖拽事件，具体地，可以利用预定的线程对在核保页面上的附件是否发生的拖拽事件进行监听，若核保页面上的附件被选中并进行移动，则可以确定该附件发生了拖拽事件。
步骤S3，若在所述核保页面上的附件发生拖拽事件，则基于所述组件服务及所述拖拽事件在所述核保页面上复制得到新的附件。
本实施例中，组件服务初始化后如果在核保页面上的附件发生拖拽事件，则可以利用该组件服务实现对所拖拽的附件进行复制，具体地，用户点击核保页面上某一核保分类中的附件，并拖动至核保页面中的其他核保分类中，在释放该附件后，在释放该附件的位置组件服务对附件进行复制，以在该位置上复制得到新的附件。
与现有技术相比，本实施例注册用于复制核保页面上的附件的组件服务及预先定义用于监听核保页面上的附件的监听指令，在组件服务初始化及接收到监听指令后，如果监听到在核保页面上的附件发生拖拽事件，则基于组件服务及拖拽事件在核保页面上复制得到新的附件，不需要用户重复上传相同的附件，操作快捷简便，能够提高保单信息处理的工作效率。
在一优选的实施例中，在上述图2的实施例的基础上，所述步骤S3包括：
S31，若在所述核保页面上的附件发生拖拽事件，记录所述附件在所述拖拽事件结束时对应的页面位置；
S32，基于所述组件服务在所述页面位置上渲染所述附件，以复制得到新的附件，设置所述新的附件在所述核保页面上的位置标识符ID，并缓存所述位置标识符ID。
本实施例中，当核保页面上的附件发生拖拽事件后，当监控到拖拽事件结束时，记录被拖拽的附件在核保页面上的页面位置，具体地，记录被拖拽的附件在核保页面上的坐标(x，y)，并在以该坐标(x，y)为中心的区域上进行渲染，然后复制该附件，得到新的附件。
此外，还在该核保页面对应的页面数据中设置该新的附件在所述核保页面上的位置标识符ID，其中，该位置标识符ID例如可以是随机的10位数，缓存所设置的该位置标识符ID，使得该新的附件能够在该核保页面上进行显示。
本实施例在附件发生拖拽事件后，在拖拽事件结束时的页面位置上渲染附件，以复制得到新的附件，使得在不同的核保分类中相同的附件不需要重复上传，而是拖拽附件并释放即可以复制得到新的附件，操作快捷方便。
在一优选的实施例中，在上述图2的实施例的基础上，所述步骤S3之后还包括：将所述附件上传至影像信息库中，建立上传后的附件与所述新的附件的映射关系并存储所述映射关系。
本实施例中，核保信息处理的装置1将附件上传至影像信息库中，建立上传后的附件与所述新的附件的映射关系，并存储所述映射关系，优选地，可以将映射关系存储在映射表中。这样，不需要将该新的附件也上传至影像 信息库。后续在核保页面上不同的核保分类中需要使用与该附件相同的附件时，也不需要再次上传附件至影像信息库中，使得影像信息库中不会存储多个相同的附件，节省影像信息库的存储空间，减少了与影像信息库的交互，降低存储及维护成本。
在一优选的实施例中，在上述的实施例的基础上，该核保信息处理的方法还包括：当接收到删除所述附件的删除指令时，获取与所述附件存在映射关系的所有附件，删除所述附件及存在映射关系的所有附件。
本实施例中，当删除核保页面上的附件时，若所要删除的该附件存在多个具有映射关系的附件，则一次性将该附件及与其存在映射关系的附件也删除，具体地，在接收到删除附件的删除指令时，根据该附件获取与该附件存在映射关系的所有附件，删除该附件，以及将该所有附件分别在核保页面对应的页面数据中的位置标识符ID删除。
本实施例在上传错误的附件或者需要对附件进行修改时，一次删除操作可以将核保页面当所有相同的附件进行删除，操作快捷方便。
本申请还提供一种计算机可读存储介质，所述计算机可读存储介质上存储有核保信息处理的***，所述核保信息处理的***被处理器执行时实现上述的核保信息处理的方法的步骤。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服 务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
以上仅为本申请的优选实施例，并非因此限制本申请的专利范围，凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本申请的专利保护范围内。

Claims (20)

  1. 一种核保信息处理的装置，其特征在于，所述核保信息处理的装置包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的核保信息处理的***，所述核保信息处理的***被所述处理器执行时实现如下步骤：
    S1，预先注册用于复制核保页面上的附件的组件服务，并预先定义用于监听所述核保页面上的附件的监听指令；
    S2，当所述组件服务初始化，并接收到监听指令后，监听在所述核保页面上的附件是否发生拖拽事件；
    S3，若在所述核保页面上的附件发生拖拽事件，则基于所述组件服务及所述拖拽事件在所述核保页面上复制得到新的附件。
  2. 根据权利要求1所述的核保信息处理的装置，其特征在于，所述核保信息处理的***被所述处理器执行实现所述步骤S3时，具体包括：
    S31，若在所述核保页面上的附件发生拖拽事件，记录所述附件在所述拖拽事件结束时对应的页面位置；
    S32，基于所述组件服务在所述页面位置上渲染所述附件，以复制得到新的附件，设置所述新的附件在所述核保页面上的位置标识符ID，并缓存所述位置标识符ID。
  3. 根据权利要求1所述的核保信息处理的装置，其特征在于，所述核保信息处理的***被所述处理器执行所述步骤S3之后，还实现如下步骤：
    将所述附件上传至影像信息库中，建立上传后的附件与所述新的附件的映射关系并存储所述映射关系。
  4. 根据权利要求2所述的核保信息处理的装置，其特征在于，所述核保信息处理的***被所述处理器执行所述步骤S3之后，还实现如下步骤：
    将所述附件上传至影像信息库中，建立上传后的附件与所述新的附件的映射关系并存储所述映射关系。
  5. 根据权利要求3所述的核保信息处理的装置，其特征在于，所述核保信息处理的***被所述处理器执行时，还实现如下步骤：
    当接收到删除所述附件的删除指令时，获取与所述附件存在映射关系的所有附件，删除所述附件及存在映射关系的所有附件。
  6. 根据权利要求4所述的核保信息处理的装置，其特征在于，所述核保信息处理的***被所述处理器执行时，还实现如下步骤：
    当接收到删除所述附件的删除指令时，获取与所述附件存在映射关系的所有附件，删除所述附件及存在映射关系的所有附件。
  7. 根据权利要求3或4所述的核保信息处理的装置，其特征在于，所述核保信息处理的***被所述处理器执行时，还实现如下步骤：
    将所述附件的附件信息同步给与所述附件存在映射关系的所有附件。
  8. 一种核保信息处理的方法，其特征在于，所述核保信息处理的方法包括：
    S1，预先注册用于复制核保页面上的附件的组件服务，并预先定义用于监听所述核保页面上的附件的监听指令；
    S2，当所述组件服务初始化，并接收到监听指令后，监听在所述核保页面上的附件是否发生拖拽事件；
    S3，若在所述核保页面上的附件发生拖拽事件，则基于所述组件服务及所述拖拽事件在所述核保页面上复制得到新的附件。
  9. 根据权利要求8所述的核保信息处理的方法，其特征在于，所述步骤S3具体包括：
    S31，若在所述核保页面上的附件发生拖拽事件，记录所述附件在所述拖拽事件结束时对应的页面位置；
    S32，基于所述组件服务在所述页面位置上渲染所述附件，以复制得到新的附件，设置所述新的附件在所述核保页面上的位置标识符ID，并缓存所述位置标识符ID。
  10. 根据权利要求8所述的核保信息处理的方法，其特征在于，所述步骤S3之后，还包括步骤：
    将所述附件上传至影像信息库中，建立上传后的附件与所述新的附件的映射关系并存储所述映射关系。
  11. 根据权利要求9所述的核保信息处理的方法，其特征在于，所述步骤S3之后，还包括步骤：
    将所述附件上传至影像信息库中，建立上传后的附件与所述新的附件的映射关系并存储所述映射关系。
  12. 根据权利要求10所述的核保信息处理的方法，其特征在于，还包括步骤：
    当接收到删除所述附件的删除指令时，获取与所述附件存在映射关系的所有附件，删除所述附件及存在映射关系的所有附件。
  13. 根据权利要求11所述的核保信息处理的方法，其特征在于，还包括步骤：
    当接收到删除所述附件的删除指令时，获取与所述附件存在映射关系的所有附件，删除所述附件及存在映射关系的所有附件。
  14. 根据权利要求10或11所述的核保信息处理的方法，其特征在于，还包括步骤：
    将所述附件的附件信息同步给与所述附件存在映射关系的所有附件。
  15. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有核保信息处理的***，所述核保信息处理的***被处理器执行时实现如下步骤：
    S1，预先注册用于复制核保页面上的附件的组件服务，并预先定义用于监听所述核保页面上的附件的监听指令；
    S2，当所述组件服务初始化，并接收到监听指令后，监听在所述核保页面上的附件是否发生拖拽事件；
    S3，若在所述核保页面上的附件发生拖拽事件，则基于所述组件服务及所述拖拽事件在所述核保页面上复制得到新的附件。
  16. 根据权利要求15所述的计算机可读存储介质，其特征在于，所述核保信息处理的***被所述处理器执行实现所述步骤S3时，具体包括：
    S31，若在所述核保页面上的附件发生拖拽事件，记录所述附件在所述拖拽事件结束时对应的页面位置；
    S32，基于所述组件服务在所述页面位置上渲染所述附件，以复制得到新的附件，设置所述新的附件在所述核保页面上的位置标识符ID，并缓存所述位置标识符ID。
  17. 根据权利要求15或16所述的计算机可读存储介质，其特征在于，所述核保信息处理的***被所述处理器执行所述步骤S3之后，还实现如下步骤：
    将所述附件上传至影像信息库中，建立上传后的附件与所述新的附件的映射关系并存储所述映射关系。
  18. 根据权利要求17所述的计算机可读存储介质，其特征在于，所述核保信息处理的***被所述处理器执行时，还实现如下步骤：
    当接收到删除所述附件的删除指令时，获取与所述附件存在映射关系的所有附件，删除所述附件及存在映射关系的所有附件。
  19. 根据权利要求17所述的计算机可读存储介质，其特征在于，所述核保信息处理的***被所述处理器执行时，还实现如下步骤：
    将所述附件的附件信息同步给与所述附件存在映射关系的所有附件。
  20. 根据权利要求18所述的计算机可读存储介质，其特征在于，所述核保信息处理的***被所述处理器执行时，还实现如下步骤：
    将所述附件的附件信息同步给与所述附件存在映射关系的所有附件。
PCT/CN2018/077666 2017-06-25 2018-02-28 核保信息处理的装置、方法及计算机可读存储介质 WO2019000996A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710490395.1A CN107918915B (zh) 2017-06-25 2017-06-25 核保信息处理的装置、方法及计算机可读存储介质
CN201710490395.1 2017-06-25

Publications (1)

Publication Number Publication Date
WO2019000996A1 true WO2019000996A1 (zh) 2019-01-03

Family

ID=61898747

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/077666 WO2019000996A1 (zh) 2017-06-25 2018-02-28 核保信息处理的装置、方法及计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN107918915B (zh)
WO (1) WO2019000996A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110647809A (zh) * 2019-08-15 2020-01-03 中国平安人寿保险股份有限公司 基于图像分析的ai核保***、方法及计算机可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106020657A (zh) * 2016-05-12 2016-10-12 山东大学 一种用于安卓***的同目录文件拖拽移动方法
CN106502498A (zh) * 2016-10-21 2017-03-15 上海与德信息技术有限公司 一种触摸屏终端上文件对象的选择方法和装置
CN106598757A (zh) * 2016-12-13 2017-04-26 珠海市魅族科技有限公司 内容粘贴方法和装置
CN106780048A (zh) * 2016-11-28 2017-05-31 中国平安财产保险股份有限公司 一种智能车险的自助理赔方法、自助理赔装置及***

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1419675A (zh) * 2000-03-22 2003-05-21 伟博麦德有限公司 用于自上而下的企业过程定义和执行的方法和***
JP4205555B2 (ja) * 2003-11-12 2009-01-07 トッパン・フォームズ株式会社 関連文書管理システム
US8712858B2 (en) * 2004-08-21 2014-04-29 Directworks, Inc. Supplier capability methods, systems, and apparatuses for extended commerce
EP1758051A1 (de) * 2005-08-22 2007-02-28 Ubs Ag System, Verfahren und Computerprogrammprodukt zur arbeitsflussbasierten Datenverarbeitung
WO2008129109A1 (es) * 2007-04-24 2008-10-30 Joan Aguado Moreno Copiador digital
JP2010250783A (ja) * 2009-04-16 2010-11-04 Studio M:Kk 迷子（ペット）発見システム付帯物・防犯機能（鈴に類する音付き機能）
MX2014004399A (es) * 2011-10-10 2015-03-05 Abbvie Biotechnology Ltd Manejo de servicios de cuidado de la salud.
CN103077673B (zh) * 2012-12-30 2015-08-26 乐视网信息技术（北京）股份有限公司 视频对应物品广告播放方法及***
CN105068815B (zh) * 2015-08-24 2018-10-19 用友网络科技股份有限公司 页面编辑器交互装置和方法
CN106610826B (zh) * 2015-10-23 2020-04-21 腾讯科技（深圳）有限公司 在线场景应用的制作方法及装置
CN105389096B (zh) * 2015-10-27 2018-10-30 深信服科技股份有限公司 基于浏览器的数据交互方法及装置
CN105809549A (zh) * 2016-02-23 2016-07-27 平安科技（深圳）有限公司 医务智能核保方法和***
CN108804483B (zh) * 2017-05-05 2020-01-07 平安科技（深圳）有限公司 单元格页面的渲染方法、服务器和计算机可读存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106020657A (zh) * 2016-05-12 2016-10-12 山东大学 一种用于安卓***的同目录文件拖拽移动方法
CN106502498A (zh) * 2016-10-21 2017-03-15 上海与德信息技术有限公司 一种触摸屏终端上文件对象的选择方法和装置
CN106780048A (zh) * 2016-11-28 2017-05-31 中国平安财产保险股份有限公司 一种智能车险的自助理赔方法、自助理赔装置及***
CN106598757A (zh) * 2016-12-13 2017-04-26 珠海市魅族科技有限公司 内容粘贴方法和装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110647809A (zh) * 2019-08-15 2020-01-03 中国平安人寿保险股份有限公司 基于图像分析的ai核保***、方法及计算机可读存储介质

Also Published As

Publication number Publication date
CN107918915A (zh) 2018-04-17
CN107918915B (zh) 2022-02-08

Similar Documents

Publication Publication Date Title
US10380103B2 (en) Object data updating method and apparatus in an object storage system
US8681994B2 (en) Systems and methods for document control using public key encryption
US8407185B2 (en) Computer, its processing method, and computer system
WO2019062189A1 (zh) 电子装置、数据表归档处理的方法、***及存储介质
WO2018223941A1 (zh) 多保险产品出单的装置、方法及计算机可读存储介质
US20180253440A1 (en) User initiated and automatic conditional deletion
WO2019047508A1 (zh) 电子书评论信息的处理方法、电子设备以及存储介质
US10075490B2 (en) Information processing apparatus, electronic meeting system, and program
WO2019071898A1 (zh) 电子装置、数据库查询脚本生成方法及存储介质
US20160041972A1 (en) System and method for dynamic document retention
JP2014178784A (ja) 情報処理装置、情報処理システム及び情報処理プログラム
US10803093B2 (en) Systems and methods for enabling a file management label to persist on a data file
US9021389B1 (en) Systems and methods for end-user initiated data-loss-prevention content analysis
WO2019000996A1 (zh) 核保信息处理的装置、方法及计算机可读存储介质
US20220083507A1 (en) Trust chain for official data and documents
CN107111633B (zh) 基于背景的保存位置的推断
WO2017016139A1 (zh) 一种***还原方法与装置
US20150339030A1 (en) Method, apparatus, and system for data transfer across applications
WO2019085354A1 (zh) 基于Excel***界面的数据库联动方法、电子装置及存储介质
CN111753141A (zh) 一种数据管理方法及相关设备
US20140092435A1 (en) Applying individual preferences to printed documents
US10042859B1 (en) Chronological based retention for objects archived through a web-based storage interface for ILM
CN112988663A (zh) 文件存储方法和电子设备
WO2019169762A1 (zh) 电子装置、zk节点信息通知方法、***及存储介质
US20220300457A1 (en) Information processing apparatus and non-transitory computer readable medium storing information processing program

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: 18824331

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 25.05.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18824331

Country of ref document: EP

Kind code of ref document: A1