+

WO2018184535A1 - Procédé et dispositif de traitement de service d'assurance, serveur et support de stockage - Google Patents

Procédé et dispositif de traitement de service d'assurance, serveur et support de stockage Download PDF

Info

Publication number
WO2018184535A1
WO2018184535A1 PCT/CN2018/081779 CN2018081779W WO2018184535A1 WO 2018184535 A1 WO2018184535 A1 WO 2018184535A1 CN 2018081779 W CN2018081779 W CN 2018081779W WO 2018184535 A1 WO2018184535 A1 WO 2018184535A1
Authority
WO
WIPO (PCT)
Prior art keywords
insurance
component
item
configuration information
interface
Prior art date
Application number
PCT/CN2018/081779
Other languages
English (en)
Chinese (zh)
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 WO2018184535A1 publication Critical patent/WO2018184535A1/fr

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 application relates to a insurance service processing method, device, server and storage medium.
  • Different types of insurance have their own business processing systems. In the traditional business processing systems of various types of insurance, each system independently processes the business content involved. Since different types of insurance are the same or similar in many types of business processes, for example, many types of insurance have certain similarities in the processing rules of the user's personal information inquiry process and the insurance processing process. Therefore, these numerous types of There is a certain commonality between insurance business processing systems, and there is a possibility that resources can be shared.
  • the traditional method needs to redesign a processing system for the insurance business of the new insurance and integrate it into the existing total system.
  • an insurance service processing method apparatus, server, and storage medium are provided.
  • An insurance business processing method comprising:
  • the insurance item is processed by calling a corresponding component according to the calling address.
  • An insurance business processing device comprising:
  • a service processing request receiving module configured to receive an insurance service processing request, where the insurance service processing request includes an insurance item to be processed
  • An interface configuration information generating module configured to generate interface configuration information called by the component according to the insurance item and a preset application programming interface
  • the service processing module is configured to: when detecting the generated interface configuration information, acquire a call address of a component included in the interface configuration information; and invoke a corresponding component to process the insurance item according to the call address.
  • An insurance business processing method comprising:
  • the service component is invoked according to the calling address of the service component, the input information is processed, a processing result is generated, and sent to the user terminal.
  • An insurance service processing device comprising:
  • a service processing request receiving module configured to receive an insurance service processing request, where the insurance service processing request includes a document processing item to be processed
  • An interface configuration information generating module configured to generate interface configuration information called by the component according to the document processing item and the preset application programming interface, where the interface configuration information includes a call for processing a portlet component and a service component corresponding to the document processing item Address;
  • a service processing module configured to acquire a call address of a portlet and a service component in the interface configuration information when the interface configuration information is generated; and invoke the portlet to process the document according to the call address of the portlet Processing the item, generating an information input interface, and sending the information to the user terminal; receiving the input information returned by the user terminal through the input interface; calling the service component according to the calling address of the service component, and processing the input information
  • the processing result is generated and sent to the user terminal.
  • a server comprising a memory and one or more processors, the memory storing computer readable instructions, the computer readable instructions being executed by the processor, causing the one or more processors to execute The steps of applying the insurance service processing method provided in any one of the embodiments.
  • One or more non-volatile storage media storing computer readable instructions that, when executed by one or more processors, cause one or more processors to perform the insurance provided in any one of the embodiments herein The steps of the business processing method.
  • FIG 1 is an application environment diagram of an insurance service processing method in one or more embodiments.
  • FIG. 2 is a diagram showing the internal structure of a server in one or more embodiments.
  • FIG. 3 is a flow chart of a method of processing insurance services in one or more embodiments.
  • FIG. 4 is a flow diagram of interface configuration information for component call generation based on an insurance project and a preset application programming interface in one or more embodiments.
  • FIG. 5 is a flow chart of a method for processing insurance services in another embodiment.
  • Figure 6 is a block diagram showing the structure of an insurance service processing apparatus in one or more embodiments.
  • Figure 7 is a block diagram showing the structure of an insurance service processing apparatus in another embodiment.
  • the insurance service processing method provided by the embodiment of the present application can be applied in an application environment as shown in FIG. 1.
  • the user terminal 110 can be connected to the server 120 through a network.
  • An insurance service processing request is sent to the server 120, and the insurance service processing request includes an insurance item to be processed.
  • the server 120 After receiving the service processing request, the server 120 generates interface configuration information called by the component according to the insurance item in the service request and the preset application programming interface; and when detecting the generation of the interface configuration information, configuring information from the interface Obtaining a component identifier of the corresponding component; calling the corresponding component according to the component identifier to process the insurance item.
  • FIG. 2 is a schematic diagram showing the internal structure of a server in one embodiment.
  • the server includes a processor coupled through a system bus, a non-volatile storage medium, an internal memory, and a network interface.
  • the server's processor is used to provide computing and control capabilities that support the operation of the entire server.
  • An operating system and computer readable instructions are stored in the non-volatile storage medium.
  • the computer readable instructions are executable by a processor to implement an insurance service processing method provided by the following embodiments.
  • the internal memory provides a cached operating environment for operating systems and computer readable instructions in a non-volatile storage medium.
  • the network interface of the terminal is used for communicating with an external terminal through a network connection, for example, receiving a service processing request sent by the terminal.
  • the server can be implemented with a stand-alone server or a server cluster consisting of multiple servers.
  • FIG. 2 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the server to which the solution of the present application is applied.
  • the specific server may include a ratio. More or fewer components are shown in the figures, or some components are combined, or have different component arrangements.
  • an insurance service processing method is provided, which can be applied to an application environment as shown in FIG. 1.
  • This embodiment is described by taking the method applied to the foregoing server as an example, and includes:
  • Step S302 Receive an insurance service processing request, where the insurance service processing request includes an insurance item to be processed.
  • the server can provide various types of insurance service processing services to the user.
  • the service may be specifically for life insurance information services, property insurance information services, and pension insurance information services. More specifically, for example, policy information inquiry services for a certain type of insurance, or insurance business services such as insurance opening or surrender.
  • the server may provide a corresponding service interface to the user terminal as an entry for the service processing request.
  • the service processing request received by the server further includes a corresponding insurance item, which indicates a specific item of insurance to be processed in the request.
  • the insurance program includes but is not limited to insurance opening projects for a certain type of insurance, policy inquiry items, insurance supplementary documents, and surrender items. The insurance items included in different types of insurance are not necessarily the same.
  • Step S304 generating interface configuration information called by the component according to the insurance item and the preset application programming interface.
  • a plurality of components are preset in the server, and the components are simple encapsulations of data and methods. Every component is used to handle the business of all types of insurance with the same processing logic, and is versatile. Components can include categories such as portlets and business components. Each portlet can be used to initiate the service processing of the corresponding insurance item. Individual business components can be used to process specific insurance items.
  • the server also sets up a common Application Programming Interface (API), which is used to implement the call to the component.
  • API Application Programming Interface
  • the server may obtain the component information corresponding to the required call and the project processing logic according to the processed insurance item, encapsulate the data into a preset API, generate interface configuration information called by the component, and use the interface configuration information as a piece of information.
  • the service processing request message to be processed is stored in a preset message queue.
  • the component information includes the calling address of the component, according to which the location of the corresponding component is known, and the component can be called to process the corresponding task.
  • the server may configure information via interface generated by postMessage in HTML5.
  • the server can set a plurality of calling methods according to the postMessage, and set different calling methods corresponding to different components, and write information about the project processing logic corresponding to the insurance item and the calling address of the component to the calling method corresponding to the component to be called. And encapsulate the calling method into the API to generate interface configuration information.
  • the server may be functionally divided into component invocation modules, component frameworks, and component providing modules.
  • the component call module receives the insurance service processing request, and determines the component to be called and the corresponding project information.
  • the component framework is used to generate interface configuration information and sent to the component providing module.
  • the component providing module is configured to provide a component, and when detecting the generated interface configuration information, obtain the component and project information to be called contained therein, and call the component to process the insurance item.
  • a plurality of calling methods are set in the component framework, and different calling methods are set corresponding to different components, and information about the project processing logic corresponding to the insurance item and the calling address of the component is written in the calling method corresponding to the component to be called.
  • the method is encapsulated into an API to generate interface configuration information. Through the calling method, the component calling module and the component providing communication between the modules are implemented.
  • the calling method includes a start method, a register method, a notify method, a complete method, and an end method.
  • the start method is used to start processing the corresponding service request
  • the register method is used to register the corresponding project information
  • the notify method is used to implement communication between the component calling module and the component
  • the complete method is used to notify the called component that the corresponding component has been completed.
  • the item is processed and enters the call to the next component, which is used to indicate the end of the processing of the processed item.
  • the server can implement the call to the portlet through the start method, call the business component through the register method, the notify method, etc., end the call to the component through the end method, and return the processing result of the insurance item.
  • Step S306 when detecting the generation of the interface configuration information, acquiring the calling address of the component included in the interface configuration information.
  • the server may detect, in real time, whether there is a service processing request message to be processed in the preset message queue.
  • the interface configuration information in the message is obtained, and the calling address included in the interface configuration information is read, so that the component that needs to be called can be found according to the component identifier.
  • Step S308 the corresponding component is called according to the calling address to process the insurance item.
  • the server may query the corresponding component according to the acquired call address.
  • Different components are used to handle business transactions that correspond to different logics.
  • Components can be divided into front-end business components, public calls, database components, and associated system components. Front-end business components are used to wrap all of the business logic.
  • the public acceptance component can be provided to multiple front-end business components for processing data calculation and other services, the database component is used for data query, and the associated system interface component is used for connection with other related systems.
  • the server can obtain the project information of the insurance item to be processed, and call the component to process the project information, generate a processing result, and send the result to the user terminal.
  • the item information is information required to process the insurance item, and may include, for example, personal information of the user, and project processing logic.
  • the insurance business processing method described above is configured by pre-setting different components, each of which is used to process the business of all types of insurance having the same processing logic.
  • receiving the insurance service processing request generating interface configuration information according to the corresponding insurance item in the insurance service processing request, and when detecting that the interface configuration information is generated, acquiring the calling address of the component in the interface configuration information, according to the Call the address to call the component for the processing of the insurance project. Due to the similarity of the project processing logic between different types of insurance, the method can be applied to the insurance business processing of multiple insurance types, so that it can be applied to the business processing of multiple insurance types at the same time, thereby improving the processing efficiency of the insurance business.
  • step S304 includes:
  • Step S402 acquiring component identifiers corresponding to the insurance items.
  • the correspondence between different insurance items and component identifiers is established in advance.
  • the component identifier is used to uniquely identify the corresponding component.
  • An insurance item may correspond to multiple component identifiers. When the insurance item corresponds to multiple component identifiers, the multiple corresponding component identifiers are obtained.
  • Step S404 acquiring call address information of the corresponding component according to the component identifier.
  • the server may query the calling address information of the corresponding component according to the component identifier, and by calling the address information, the calling of the corresponding component may be implemented to perform processing on the insurance item.
  • Step S406 acquiring corresponding item processing logic according to the insurance item.
  • the server also presets project processing logic for each insurance item.
  • the project processing logic is a business processing rule and a processing flow set for realizing a business request of the corresponding insurance item. If the insurance item is a surrender item for a certain type of insurance, the processing logic includes the conditions that need to be met for the surrender of the corresponding type of insurance, and the processing procedure for surrender. The conditions include the calculation of the surrender term of the set insurance, the calculation of the surrender amount, and the like. The process of surrendering includes the surrender review process and audit rules, as well as the reconciliation of information. If the insurance item is a supplementary document item of a certain type of insurance, the corresponding item processing logic includes the conditions to be satisfied by the supplementary document and the flow of the supplementary document. The server can query the project processing logic corresponding to the insurance project, and obtain the project processing logic.
  • Step S408 the calling address information and the item processing logic are encapsulated into a preset application programming interface to generate interface configuration information.
  • the server may encapsulate the acquired call address information and corresponding item processing logic into a preset API, thereby generating interface configuration information.
  • the corresponding component can process the corresponding insurance items according to the project processing logic included in the interface configuration information, so that each component can achieve the same insurance for multiple types of insurance.
  • the processing of the project improves the reusability of the components.
  • the interface configuration information includes a plurality of call addresses and a call sequence for each component.
  • the components required for different insurance items are not necessarily the same, and the number of components to be used is not necessarily the same.
  • the server further sets the calling order of each corresponding component.
  • the number of components arranged in the same order may include a plurality.
  • the call address of each component corresponding to the component is obtained, and the corresponding calling sequence is obtained, and the multiple call addresses and the calling sequence are encapsulated into the API to generate interface configuration information.
  • the corresponding component is invoked according to the calling sequence in the interface configuration information, and the corresponding service processing is completed by the corresponding multiple components.
  • step S408 includes invoking the corresponding component to process the insurance item according to the calling address and the calling sequence.
  • the server may determine the calling sequence of each component to be called according to the calling sequence, and invoke the corresponding component according to the calling address.
  • a call notification of the component after the sorting may be generated, and the subsequent component is called to perform the processing of the insurance item.
  • the server further sets a correspondence between each project processing logic and a component, and may associate a certain project processing logic with a component identifier, and may also associate an item.
  • the processing logic is split into multiple pieces, and the project processing logic of each split branch is associated with a component.
  • the component When the corresponding component is called according to the calling address, the component is caused to process the insurance item according to the item processing logic of the corresponding all split parts.
  • each component By processing the insurance items by multiple components in accordance with the calling sequence, each component is divided into more detailed items, so that it can be applied to the processing of more types of insurance items, further improving the processing of insurance items. effectiveness.
  • FIG. 5 another insurance service processing method is provided, which is applicable to the application environment as shown in FIG. 1.
  • This embodiment is described by taking the method applied to the foregoing server as an example, and includes:
  • Step S502 Receive an insurance service processing request, where the insurance service processing request includes a document processing item to be processed.
  • the insurance service processing request includes a supplemental document request, a document information inquiry request, and the like.
  • the corresponding document processing items include document inquiry items and supplementary document items.
  • Corresponding insurance can be for life insurance, product insurance and pension insurance.
  • the component calling module of the server can receive the insurance service processing request.
  • Step S504 generating interface configuration information called by the component according to the document processing item and the preset application programming interface.
  • the interface configuration information includes a call address of a portlet and a service component corresponding to the processing document processing item.
  • the server can obtain a preset project processing logic and component identifier corresponding to the document processing item.
  • the project processing logic includes user information to be entered, and information such as document query rules.
  • the component ID includes the component ID of the portlet and business component.
  • the server may write the component identifier and the corresponding project processing logic to the set calling method, encapsulate the template into the API, and generate corresponding interface configuration information, which is stored in a preset message queue. Where the portlet is the component that was called first.
  • Step S506 when detecting the generation of the interface configuration information, acquiring the calling address of the port component and the service component in the interface configuration information.
  • the call address of the portlet and the call address of the service component in the interface configuration information may be obtained.
  • Step S508 the portal component is called according to the calling address of the portlet to process the document processing item, and the information input interface is generated and sent to the user terminal.
  • the server may invoke the corresponding portlet according to the corresponding calling sequence and the calling address of the portlet, so that the portlet processes the item processing logic according to the corresponding document, generates or extracts a preset need to process the document processing item.
  • the directory interface is sent to the user terminal, so that the user terminal can input corresponding user information.
  • Step S510 receiving the input information returned by the user terminal through the entry interface.
  • the entry information may include one or more of the name, gender, policy number, contact number, and the like of the user to be queried.
  • Step S512 the service component is invoked according to the calling address of the service component, the input information is processed, the processing result is generated, and sent to the user terminal.
  • the document processing item is described as a supplementary document item, and the server can detect whether the entered user information exists in the database corresponding to the insurance, and if yes, it can detect whether the condition of the supplementary document is satisfied, and send the detection result to the user terminal. .
  • the server may invoke the corresponding service component according to the calling sequence and the calling address of the service component, and detect the entered information according to the document processing item processing logic, and generate a processing result, and send the processing result. To the user terminal, the processing of the insurance service processing request is realized.
  • FIGS. 3-5 are sequentially displayed as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Except as explicitly stated herein, the execution of these steps is not strictly limited, and the steps may be performed in other orders. Moreover, at least some of the steps in FIGS. 3-5 may include a plurality of sub-steps or stages, which are not necessarily performed at the same time, but may be executed at different times, these sub-steps or stages The order of execution is not necessarily performed sequentially, but may be performed alternately or alternately with at least a portion of other steps or sub-steps or stages of other steps.
  • an insurance service processing apparatus comprising:
  • the service processing request receiving module 602 is configured to receive an insurance service processing request, where the insurance service processing request includes an insurance item to be processed.
  • the interface configuration information generating module 604 is configured to generate interface configuration information called by the component according to the insurance item and the preset application programming interface.
  • the service processing module 606 is configured to obtain a call address of a component included in the interface configuration information when detecting the generated interface configuration information.
  • the insurance item is processed by calling the corresponding component according to the calling address.
  • the interface configuration information generating module 604 is further configured to obtain a component identifier corresponding to the insurance service request. Get the call address information of the corresponding component according to the component identifier. Obtain the corresponding project processing logic according to the insurance project. The call address information and the project processing logic are encapsulated into a preset application programming interface to generate interface configuration information.
  • the interface configuration information includes a plurality of call addresses and a call sequence for each component.
  • the business processing module 606 is further configured to invoke the corresponding component to process the insurance item according to the calling address and the calling sequence.
  • another insurance service processing apparatus comprising:
  • the service processing request receiving module 702 is configured to receive an insurance service processing request, where the insurance service processing request includes a document processing item to be processed.
  • the interface configuration information generating module 704 generates interface configuration information that is invoked by the component according to the document processing item and the preset application programming interface.
  • the interface configuration information includes a call address of the portlet and the service component corresponding to the processing document processing item.
  • the service processing module 706 is configured to obtain a call address of the port component and the service component in the interface configuration information when the interface configuration information is generated.
  • the portal component is processed according to the calling address of the portlet to process the document processing item, and an information input interface is generated and sent to the user terminal. Receiving the input information returned by the user terminal through the entry interface.
  • the business component is called according to the calling address of the business component, the input information is processed, the processing result is generated, and sent to the user terminal.
  • the network interface may be an Ethernet card or a wireless network card.
  • the above modules may be embedded in the hardware in the processor or in the memory in the server, or may be stored in the memory in the server, so that the processor calls the corresponding operations of the above modules.
  • the processor can be a central processing unit (CPU), a microprocessor, a microcontroller, or the like.
  • a server comprising a memory and one or more processors having stored therein computer readable instructions that, when executed by a processor, cause one or more processors to perform the operations provided in any one of the embodiments herein The steps of the insurance business processing method.
  • One or more non-volatile storage media storing computer readable instructions that, when executed by one or more processors, cause one or more processors to perform the insurance provided in any one of the embodiments herein The steps of the business processing method.
  • the readable storage medium which when executed, may include the flow of an embodiment of the methods as described above.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or the like.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (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)

Abstract

L'invention concerne un procédé de traitement de service d'assurance qui comprend : la réception d'une demande de traitement de service d'assurance, la demande de traitement de service d'assurance comprenant un article d'assurance à traiter; la génération, en fonction de l'article d'assurance et d'une interface de programmation d'application prédéfinie, d'informations de configuration d'interface pour appeler un composant; l'acquisition, lors de la détection de la génération des informations de configuration d'interface, d'une adresse d'appel du composant contenu dans les informations de configuration d'interface; et l'appel, selon l'adresse d'appel, du composant correspondant pour traiter l'article d'assurance.
PCT/CN2018/081779 2017-04-07 2018-04-03 Procédé et dispositif de traitement de service d'assurance, serveur et support de stockage WO2018184535A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710225327.2A CN107798617B (zh) 2017-04-07 2017-04-07 保险业务处理方法和装置
CN201710225327.2 2017-04-07

Publications (1)

Publication Number Publication Date
WO2018184535A1 true WO2018184535A1 (fr) 2018-10-11

Family

ID=61530239

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/081779 WO2018184535A1 (fr) 2017-04-07 2018-04-03 Procédé et dispositif de traitement de service d'assurance, serveur et support de stockage

Country Status (2)

Country Link
CN (1) CN107798617B (fr)
WO (1) WO2018184535A1 (fr)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107798617B (zh) * 2017-04-07 2021-04-13 平安科技（深圳）有限公司 保险业务处理方法和装置
CN108924185A (zh) * 2018-06-01 2018-11-30 中铁程科技有限责任公司 接口生成方法及装置
CN109214668A (zh) * 2018-08-24 2019-01-15 平安科技（深圳）有限公司 保险业务处理方法及系统、终端和计算机可读存储介质
CN111105314A (zh) * 2018-10-29 2020-05-05 中国人民财产保险股份有限公司 一种保险数据清分系统
CN109582303B (zh) * 2018-10-31 2024-05-03 平安科技（深圳）有限公司 通用组件调用方法、装置、计算机设备及存储介质
CN111580892B (zh) * 2019-02-19 2023-09-19 杭州海康威视系统技术有限公司 一种业务组件调用的方法、装置、终端和存储介质
CN110543327B (zh) * 2019-09-06 2023-08-01 深圳前海环融联易信息科技服务有限公司 业务组件复用方法、装置、计算机设备及存储介质
CN111091468B (zh) * 2019-11-14 2023-08-22 泰康保险集团股份有限公司 保单数据处理方法及装置、存储介质、电子设备
CN111371702B (zh) * 2020-02-28 2024-04-05 中国平安人寿保险股份有限公司 数据转发的方法、装置、电子设备及存储介质
CN112465653A (zh) * 2020-11-26 2021-03-09 中国人寿保险股份有限公司 一种保险业务处理方法、装置、设备及存储介质
CN113793224A (zh) * 2021-01-21 2021-12-14 京东安联财产保险有限公司 电子保单业务的处理方法、装置、电子设备和存储介质
CN114003414B (zh) * 2021-12-30 2022-04-01 太平金融科技服务(上海)有限公司深圳分公司 业务回访处理方法、装置、计算机设备和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090240798A1 (en) * 2008-03-18 2009-09-24 Microsoft Corporation Resource Equalization for Inter- and Intra- Data Center Operations
CN101976189A (zh) * 2010-09-26 2011-02-16 用友软件股份有限公司 组件展现方法和装置
CN103095479A (zh) * 2011-11-04 2013-05-08 华为技术有限公司 业务配置的方法及装置
CN107798617A (zh) * 2017-04-07 2018-03-13 平安科技（深圳）有限公司 保险业务处理方法和装置

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101388089A (zh) * 2005-08-09 2009-03-18 金蝶软件（中国）有限公司 一种工作流中业务逻辑处理的方法和装置
CN101237333B (zh) * 2007-01-31 2011-06-29 北京邮电大学 一种基于多网络融合的支持多种业务的通用业务平台
CN100583783C (zh) * 2007-11-06 2010-01-20 北京航空航天大学 基于配置策略的电信领域遗留系统集成工具
US8458656B1 (en) * 2008-08-25 2013-06-04 United Services Automobile Association (Usaa) Systems and methods for providing mobile browser access to mobile device functionalities
CN101383845B (zh) * 2008-10-15 2011-12-21 北京邮电大学 综合业务接入装置、系统及其控制方法
US8856079B1 (en) * 2012-09-28 2014-10-07 Emc Corporation Application programming interface for efficient object information gathering and listing
CN105607895B (zh) * 2014-11-21 2021-03-02 阿里巴巴集团控股有限公司 一种基于应用程序编程接口的应用程序的运行方法和装置
CN104572091B (zh) * 2014-12-25 2017-11-03 百度在线网络技术（北京）有限公司 应用软件实现方法、装置以及计算机设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090240798A1 (en) * 2008-03-18 2009-09-24 Microsoft Corporation Resource Equalization for Inter- and Intra- Data Center Operations
CN101976189A (zh) * 2010-09-26 2011-02-16 用友软件股份有限公司 组件展现方法和装置
CN103095479A (zh) * 2011-11-04 2013-05-08 华为技术有限公司 业务配置的方法及装置
CN107798617A (zh) * 2017-04-07 2018-03-13 平安科技（深圳）有限公司 保险业务处理方法和装置

Also Published As

Publication number Publication date
CN107798617B (zh) 2021-04-13
CN107798617A (zh) 2018-03-13

Similar Documents

Publication Publication Date Title
WO2018184535A1 (fr) Procédé et dispositif de traitement de service d'assurance, serveur et support de stockage
US11243704B2 (en) Data pipeline architecture for analytics processing stack
CN108737325A (zh) 一种多租户数据隔离方法、装置及系统
WO2020192134A1 (fr) Procédé et appareil de gestion d'exceptions basés sur spring mvc, et dispositif informatique et support de stockage
WO2019104973A1 (fr) Procédé d'invocation de langage croisé, serveur et support d'informations
CN110765187A (zh) 一种数据源路由管理方法和装置
CN114153626A (zh) 一种服务集成过程抽象的方法、装置和计算机设备
CN112948272A (zh) 基于生产环境的数据测试系统功能方法、装置及相关设备
CN111736923A (zh) 数据处理方法、装置、电子设备及可读存储介质
US20180359317A1 (en) System and method for non-intrusive context correlation across cloud services
CN111538651B (zh) 接口测试方法、装置、服务器及存储介质
CN111008254B (zh) 一种对象创建方法、装置、计算机设备和存储介质
CN105516250A (zh) 物联网服务调用平台和系统
CN110795741A (zh) 对数据进行安全性处理的方法和装置
CN114020689B (zh) 数据处理方法、数据处理装置、电子设备及存储介质
US11023527B2 (en) Using observable data object to unmarshal graph data
CN114625458A (zh) 页面数据的处理方法、装置、电子设备和存储介质
CN114675982A (zh) 一种业务集成系统的数据获取通用方法及系统
CN111722994A (zh) 一种任务请求的响应方法及设备
CN116366724A (zh) 业务流程的处理方法、装置、计算机设备、存储介质
CN113779021B (zh) 数据处理方法、装置、计算机系统及可读存储介质
CN110389966B (zh) 一种信息处理方法及装置
CN113986995A (zh) 请求分发方法、装置、存储介质及电子设备
CN115048411B (zh) 数据处理方法、装置、系统、介质及程序产品
CN113556370A (zh) 一种服务调用方法和装置

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

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 16.01.2020.

122 Ep: pct application non-entry in european phase

Ref document number: 18781297

Country of ref document: EP

Kind code of ref document: A1

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载