Service processing method and device for intercommunication of different service applications

Abstract

Embodiments of the present specification provide a service processing method and device when different service applications interwork. In the method, a third-party system obtains service records of at least two service types of at least two service application systems; the service records of different service types are isolated; at least two containers are constructed; a scheduling task for the service records of different service types is registered to different containers; and the service records of different service types are isolated and scheduled based on different scheduling tasks of different containers. Embodiments of the present specification can isolate the storage and scheduling of the service records of different service types, and meet regulatory requirements.

Description

TECHNICAL FIELD

[0001] One or more embodiments of the present specification relate to network information technology, and in particular, to a business processing method and device when different business applications interwork. BACKGROUND

[0002] With the development of Internet technology, more and more business applications have emerged, and various functions can be achieved through various business applications. Different business applications often need to interwork in order to interact with business data. For example, in a public transportation system, a POS machine can be used to swipe a public transportation card, which will involve the periodic settlement of transaction amounts between the public transportation system and the POS machine system, such as every day. For another example, when a user purchases a fund product, it will involve the settlement between the fund business system and the bank system where the user is located.

[0003] When different business applications interwork, in order to improve the convenience of interworking, a third-party system is often used. One business application system that needs to interwork sends business data to the third-party system, which sends it to another business application system after relevant interworking processing.

[0004] Because interworking needs to be implemented, various different types of business records will be obtained in the third-party system, and different types of business records need to be scheduled. At present, the storage and scheduling of all business records in the third-party system are not isolated, so it is impossible to meet the regulatory requirements. SUMMARY

[0005] One or more embodiments of the present specification describe a business processing method and device when different business applications interwork, which can isolate the storage and scheduling of business records of different business types to meet regulatory requirements.

[0006] According to a first aspect, a business processing method when different business applications interwork is provided, applied to a third-party system for processing interworking data between different business application systems, and the method comprises:

[0007] Obtaining business records of at least two business types of at least two business application systems;

[0008] Isolating business records of different business types;

[0009] Constructing at least two containers;

[0010] Registering scheduling tasks for business records of different business types to different containers;

[0011] Based on different scheduling tasks of different containers, the business records of different business types are isolated and scheduled.

[0012] The isolating the service records of different service types comprises:

[0013] The service records of different service types are stored in different tables respectively.

[0014] After the service records of at least two service types of at least two service application systems are obtained, and before the service records of different service types are stored in different tables respectively, the method further comprises:

[0015] The received each service record is stored in a unified storage table;

[0016] It is judged whether the isolation trigger condition is met currently, if yes, the service records of different service types are stored in different tables respectively for the unified storage table;

[0017] For each table name of the different tables, a prefix of each table name is set to identify the unified storage table, and a suffix of each table name is set to identify the service type of the service record in the table respectively.

[0018] The judging whether the isolation trigger condition is met currently comprises at least one of the following:

[0019] It is judged whether the number of the service records stored in the unified storage table is greater than a predetermined value, if yes, the isolation trigger condition is met currently;

[0020] It is judged whether the service type of any service record stored in the unified storage table belongs to a sensitive type, if yes, the isolation trigger condition is met currently;

[0021] It is judged whether a supervision instruction is received, if yes, the isolation trigger condition is met currently.

[0022] The isolating and scheduling the service records of different service types based on different scheduling tasks of different containers comprises:

[0023] When the third-party system is applied to one machine, different threads are set for different containers; the service records in the tables registered on different containers are scheduled through different threads, wherein, the service records in the tables registered on one container are scheduled by one thread;

[0024] When the third-party system is applied to N machines, different machines are set for different containers; the service records in the tables registered on different containers are scheduled through different machines applied with the third-party system, wherein, the service records in the tables registered on one container are scheduled by one machine; N is a positive integer greater than 1.

[0025] According to a second aspect, a service processing apparatus for interworking of different service applications is provided, which is applied to a third-party system for processing interworking data between different service application systems, and comprises:

[0026] a receiving module configured to obtain service records of at least two service types of at least two service application systems;

[0027] a record isolation module configured to isolate the service records of different service types;

[0028] a container construction module configured to construct at least two containers;

[0029] a scheduling isolation module configured to register scheduling tasks for the service records of different service types to different containers, and to isolate and schedule the service records of different service types based on different scheduling tasks of different containers.

[0030] The record isolation module is configured to store the service records of different service types in different tables respectively.

[0031] Further comprising an isolation triggering module.

[0032] The receiving module is configured to store each of the obtained service records of at least two service types of at least two service application systems in a unified storage table.

[0033] The isolation triggering module is configured to determine whether an isolation triggering condition is met, and if so, trigger the record isolation module.

[0034] The record isolation module is configured to perform:

[0035] after being triggered by the isolation triggering module, store the service records of different service types in the unified storage table in different tables respectively;

[0036] for each table name of the different tables, set a prefix of each table name to identify the unified storage table, and set a suffix of each table name to identify a service type of the service records stored in the table respectively.

[0037] The scheduling isolation module is configured to perform:

[0038] when the third-party system is applied to one machine, set different threads for different containers, and schedule the service records in the tables registered on different containers through different threads, wherein one thread schedules the service records in the tables registered on one container.

[0039] When the third-party system is applied to N machines, different machines are set for different containers; and the business records in the tables registered on different containers are scheduled by the different machines to which the third-party system is applied, wherein the same machine schedules the business records in the tables registered on the same container; N is a positive integer greater than 1.

[0040] According to a third aspect, a computing device is provided, comprising a memory and a processor, the memory having stored therein executable code which, when executed by the processor, implements the method of the first aspect.

[0041] According to the method and device provided by the embodiments of the present specification, the business records of different business types stored by the third-party system are isolated, and the scheduling of various types of business records in the third-party system is also isolated, which can meet various regulatory requirements, such as security requirements, requirements for facilitating the migration of business records, and the like, in the face of the increasingly growing amount and types of businesses currently processed by the third-party system. BRIEF DESCRIPTION OF DRAWINGS

[0042] In order to more clearly illustrate the technical solutions in the embodiments of the present specification or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description are some embodiments of the present specification, and those skilled in the art can also obtain other drawings according to these drawings without any creative effort.

[0043] Figure 1 is a schematic diagram of the system architecture to which an embodiment of the present specification is applied.

[0044] Figure 2 is a flowchart of a business processing method when different business applications interwork in an embodiment of the present specification.

[0045] Figure 3 is a structural schematic diagram of a business processing device when different business applications interwork in an embodiment of the present specification.

[0046] Figure 4 is a structural schematic diagram of a business processing device when different business applications interwork in another embodiment of the present specification. DETAILED DESCRIPTION

[0047] First of all, it should be noted that the terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit the present application. The singular forms "a", "said" and "the" used in the embodiments of the present application and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise.

[0048] For any two business applications that need to interwork, because the third-party system can complete the processing of business data in interworking based on the unified business logic and requirements required for interworking, such as protocol format conversion of complex business data, details, summary and other arrangements, and such as the processing of income calculation and distribution, therefore, more and more business application systems begin to use the third-party system to realize interworking processing, so as to simplify the processing of the business application system itself. Correspondingly, the business volume processed by the third-party system is increasing rapidly, but at present, various business records and scheduling processed by the third-party system are not isolated, so as to meet the regulatory requirements. For example, the third-party system stores the shopping records of each user in business application system A such as Taobao and the shopping records of each user in business application system B such as a live broadcast platform in a table in a day, and then schedules and sends all the shopping records in the table to business application system C after data arrangement, in this process, the shopping records on Taobao and the shopping records on the live broadcast platform are stored in a table without isolation, and the scheduling is also simultaneous without isolation, therefore, a series of problems will be caused, and the regulatory requirements cannot be met. For example, the industry and commerce supervision department needs to check all the shopping records of the live broadcast platform in the day, and the third-party system needs to migrate the above table to the system of the industry and commerce supervision department, and all the data in the table will be migrated together during the migration, which will cause unnecessary migration and data leakage of the shopping records on Taobao, and the regulatory requirements cannot be met.

[0049] The scheme provided in the present specification will be described below in combination with the drawings.

[0050] In order to facilitate the understanding of the method provided in the present specification, the system architecture involved and applicable to the present specification will be described first. As shown in Figure 1 The system architecture mainly includes two network nodes: business application systems and third-party systems, wherein the business application systems include: business application system 1, business application system 2, business application system 3, business application system 4.

[0051] The four business application systems complete different business functions respectively. The business application system 1 and the business application system 2 need to be communicated, the business application system 3 and the business application system 4 need to be communicated, and the third-party system is used to complete the processing of the communicated data. For example, for the pouring type communication business, the business application system 1 can be a payment system, the business application system 2 can be a fund product system, a user purchases a fund of the fund product system through the payment system, the third-party system converts the massive purchase data of the payment system into a protocol format and processes the amount, type and the like, and then sends the processed communicated data to the fund product system. Meanwhile, when the fund product system distributes the income of the fund, the third-party system also processes the massive income data into a protocol format and processes the amount, the user account and the like, and then sends the processed communicated data to the payment system. For example, for the clearing type communication business, the third-party system generates an execution file between the business application system 3 and the business application system 4, such as processing the data format, forming the details of the transaction, and the like.

[0052] It should be understood that Figure 1 The number of the business application systems and the third-party system in the above embodiment is only illustrative. According to the implementation needs, any number can be selected and arranged. For example, generally, the third-party system is connected with a large number of business application systems, and processes the communicated data between various different business application systems.

[0053] Figure 2 is a business processing method flowchart when different business applications are communicated in an embodiment of the present specification. The execution subject of the method is the third-party system as shown in Figure 1 It can be understood that the method can also be executed by any device, equipment, platform, equipment cluster with computing and processing capabilities. Referring to Figure 2 The method comprises the following steps.

[0054] Step 201: obtaining business records of at least two business types of at least two business application systems.

[0055] Step 203: isolating the business records of different business types.

[0056] Step 205: constructing at least two containers.

[0057] Step 207: registering the scheduling tasks for the business records of different business types to different containers.

[0058] Step 209: isolating and scheduling the business records of different business types based on different scheduling tasks of different containers.

[0059] It can be seen that the above-mentioned Figure 2In the shown flow, the business records of different business types stored in the third-party system are isolated, and the dispatching of the business records of various types in the third-party system is also isolated. In the face of the increasingly growing business volume and business types handled by the third-party system, various regulatory requirements such as security requirements, requirements for facilitating the migration of business records, etc. can be met.

[0060] Each of the steps in the method 1000 will be described below in conjunction with specific embodiments. Figure 2

[0061] First, for step 201, the third-party system obtains business records of at least two business types of at least two business application systems.

[0062] Referring to Figure 1 For example, the business application system 1 is the Alipay system, the business application system 2 is a fund product purchase system, the business application system 3 is an automatic vending system, and the business application system 4 is a product merchant settlement system. Therefore, in this step 201, the third-party system will receive the business records sent by the business application system 1 (such as various purchase records of fund products purchased through the Alipay account within an hour), and the third-party system will also receive the business records sent by the business application system 3 (such as the sales records of the products sold by the automatic vending system to the merchants within this month).

[0063] Next, in step 203, the third-party system isolates the business records of different business types.

[0064] The third-party system continuously receives various interworking data between various business application systems. In this step, the third-party system can store the business records of different business types in different tables respectively to achieve isolation.

[0065] In the embodiments of the present disclosure, the implementation of the step 203 can include:

[0066] Method one, isolated storage from the start of the third-party system running.

[0067] In this method one, when the third-party system just starts running and receives the business records of various business application systems, the business records can be stored in tables according to the business types of the business records. For example, the business records of the business application system 1 are stored in table 1 from the beginning of receiving the business records of the business application system 1, and the business records of the business application system 3 are stored in table 2 from the beginning of receiving the business records of the business application system 3.

[0068] Method two, isolated storage when the isolation trigger condition is met.

[0069] ​In the second mode, when the third-party system just starts to run and receives the business records of various business application systems, the business records are not stored in different tables according to the business types of the business records, but are first stored in a table as in the prior art, that is, after step 201, the third-party system stores each received business record in a unified storage table; then, it is determined in real time whether the isolation trigger condition is met, and if yes, the business records of different business types are stored in different tables in step 203; if not, no isolated storage in different tables is performed.

[0070] The second mode can more flexibly control the starting time of the isolated storage of the business records through the isolation trigger condition, and the implementation is more flexible and configurable.

[0071] In the second mode, when the business records of different business types are stored in different tables, in order to be traceable, that is, to show through the table name that the data in each table of the isolated storage comes from which table, the prefixes of the table names of different tables used for isolated storage are the same, and all identify the unified storage table, and the suffixes identify the business types of the business records stored in the tables, respectively. For example, when the isolation trigger condition is not met, 1 billion business records of various business types of various business application systems are stored in a unified storage table, and the table name of the unified storage table is “record”. When the isolation trigger condition is met, for example, the 1 billion business records come from 4 business application systems, corresponding to 4 business types, then 4 tables used for isolated storage can be established, the table name of table 1 is “record_typeA”, all business records of the business type “typeA” from the business application system 1 in the 1 billion business records are routed to table 1 for storage; similarly, the table name of table 2 is “record_typeB”, all business records of the business type “typeB” from the business application system 2 in the 1 billion business records are routed to table 2 for storage; the table name of table 3 is “record_typeC”, all business records of the business type “typeC” from the business application system 3 in the 1 billion business records are routed to table 3 for storage; and the table name of table 4 is “record_typeD”, all business records of the business type “typeD” from the business application system 4 in the 1 billion business records are routed to table 4 for storage. As can be seen, the table names of table 1 to table 4 have the same prefix, all of which identify that the business records come from the unified storage table with the name “record”, and have different suffixes, which identify the business types of the business records stored in the tables, respectively.

[0072] For the second mode, in an embodiment of the present disclosure, determining whether the current satisfies the isolation triggering condition includes at least one of the following:

[0073] 1. Determining whether the number of business records stored in the unified storage table is greater than a predetermined value, and if yes, the current satisfies the isolation triggering condition. Through the determination method, the size of the predetermined value can be determined in advance according to the processing capacity of the third-party system and the interworking data volume of the business application system, so as to flexibly and configurable control the timing of the isolation storage of the business records.

[0074] 2. Determining whether the business type of any business record stored in the unified storage table belongs to a sensitive type, and if yes, the current satisfies the isolation triggering condition. Through the determination method, the sensitive type can be set in advance, such as which business type data belongs to the sensitive type that should be kept secret. When the unified storage table does not include the business records of the sensitive type, such as no sensitive type business record has ever appeared, there is no need to perform isolation storage. If the business records of the sensitive type are added to the unified storage table, the isolation storage can be started, so as to isolate the business records of the sensitive type from other business records in different tables, thereby improving the security.

[0075] 3. Determining whether a supervision instruction is received, and if yes, the current satisfies the isolation triggering condition. Through the determination method, the supervision instruction can be processed, such as the supervision instruction is to call out all the transaction records on the live platform. Then, the business records of different business types in the unified storage table can be stored in different tables of the third-party system, and then the data in the table storing the transaction records on the live platform can be migrated to the supervision department sending the supervision instruction.

[0076] Through the above processing, the isolation storage of the business records is realized through the separate table storage, and a business isolation mode in the interworking of different business applications is provided from the table dimension.

[0077] The isolation scheduling of the business records can also be realized through the container, and another business isolation mode in the interworking of different business applications is provided from the container dimension. See steps 205 to 209 below.

[0078] Step 205: Construct at least two containers.

[0079] Here, the number of constructed containers can be determined according to the capacity of the third-party system, such as a total of 3 containers are constructed. Alternatively, the number of constructed containers can be determined according to the number of tables used in the isolation storage, such as 10 tables are used in the isolation storage, and then 10 containers can be constructed.

[0080] In an embodiment of the present disclosure, the building container can form different memory areas corresponding to different containers in the memory of the third-party system.

[0081] Step 207: Register the scheduling tasks of the service records of different service types to different containers.

[0082] Here, in order to isolate and schedule the service records stored in different tables, the scheduling tasks of the service records in different tables can be registered to different containers in advance. For example, there are totally 10 tables, and if there are 3 containers, 3 tables with similar service types among the 10 tables can be registered to container 1, and subsequent storage and scheduling can be performed in container 1; another 3 tables among the 10 tables can be registered to container 2, and subsequent storage and scheduling can be performed in container 2; the remaining 4 tables among the 10 tables can be registered to container 3, and subsequent storage and scheduling can be performed in container 3, so as to realize container-level scheduling and storage isolation.

[0083] Step 209: Isolating and scheduling the service records of different service types based on different scheduling tasks of different containers.

[0084] In an embodiment of the present disclosure, one implementation process of the step 209 includes:

[0085] When the third-party system is applied to one machine, different threads are set for different containers; the service records in the tables registered on different containers are scheduled by different threads, wherein the service records in the tables registered on the same container are scheduled by the same thread;

[0086] When the third-party system is applied to N machines, that is, the functions of the third-party system are completed by the N machines together, different machines are set for different containers; the service records in the tables registered on different containers are scheduled by different machines applied with the third-party system, wherein the service records in the tables registered on the same container are scheduled by the same machine; N is a positive integer greater than 1.

[0087] An embodiment of the present disclosure provides a service processing device when different service applications interwork, which is applied to a third-party system for processing interworking data between different service application systems, wherein referring to Figure 3 The device includes:

[0088] The receiving module 301 is configured to obtain service records of at least two service types of at least two service application systems;

[0089] The record isolation module 302 is configured to isolate the service records of different service types;

[0090] The container building module 303 is configured to build at least two containers;

[0091] The scheduling isolation module 304 is configured to register scheduling tasks of the business records of different service types to different containers; and perform isolated scheduling on the business records of different service types based on different scheduling tasks of the different containers.

[0092] In one embodiment of the device of the present specification, the record isolation module 302 is configured to store the business records of different service types in different tables respectively.

[0093] In one embodiment of the device of the present specification, referring to Figure 4 The device further comprises an isolation triggering module 401.

[0094] The receiving module 301 is configured to, after obtaining the business records of at least two service types of at least two service application systems, store each of the received business records in a unified storage table.

[0095] The isolation triggering module 401 is configured to determine whether the isolation triggering condition is met at present, and if so, trigger the record isolation module 302.

[0096] The record isolation module 302, after being triggered by the isolation triggering module 401, performs the processing of storing the business records of different service types in different tables respectively on the unified storage table, and sets a prefix of each table name to identify the unified storage table and sets a suffix to identify the service type of the business records stored in the table respectively for each table name of the different tables.

[0097] In one embodiment of the device of the present specification, the scheduling isolation module 304 is configured to perform:

[0098] When the third-party system is applied to one machine, different threads are set for different containers; and the business records in the tables registered on the different containers are scheduled by different threads, wherein the same thread schedules the business records in the tables registered on the same container;

[0099] When the third-party system is applied to N machines, different machines are set for different containers; and the business records in the tables registered on the different containers are scheduled by different machines to which the third-party system is applied, wherein the same machine schedules the business records in the tables registered on the same container; N is a positive integer greater than 1.

[0100] One embodiment of the present specification provides a computer readable storage medium having a computer program stored thereon, when the computer program is executed in a computer, the computer program causes the computer to execute the method in any one of the embodiments of the present specification.

[0101] One embodiment of the present specification provides a computing device comprising a memory and a processor, the memory having stored therein executable code which, when executed by the processor, implements a method in any one of the embodiments of the present specification.

[0102] It can be understood that the structures shown in the embodiments of the present specification do not constitute a specific limitation on the devices of the embodiments of the present specification. In other embodiments of the present specification, the above-described devices can include more or fewer components than shown, or combine certain components, or split certain components, or different arrangement of components. The components shown can be implemented in hardware, software, or a combination of software and hardware.

[0103] The information interaction between the modules in the above-described devices and systems, the execution process, and the like, are based on the same concept as the method embodiments of the present specification, and the specific content can be referred to the description in the method embodiments of the present specification, which will not be described here.

[0104] Each of the embodiments of the present specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the device embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the part of the description of the method embodiments.

[0105] Those skilled in the art should realize that the functions described in the present specification can be implemented in hardware, software, a plug-in, or any combination thereof. When implemented in software, these functions can be stored in a computer readable medium or transmitted as one or more instructions or codes on a computer readable medium.

[0106] The above specific embodiments further detail the purpose, technical solutions, and beneficial effects of the present application. It should be understood that the above description is only a specific embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made on the basis of the technical solutions of the present application shall be included in the protection scope of the present application.

Claims

1. A service processing method for intercommunication between different service applications, applied to a third-party system for processing intercommunication data between different service application systems, wherein, The method comprises the following steps: obtaining business records of at least two business types of at least two business application systems; isolating the business records of different business types; constructing at least two containers; registering scheduling tasks of the business records in different tables of different business types to different containers; the scheduling tasks of the business records in the first number of tables are registered to the same container; the first number is an integer greater than 1; isolating and scheduling the business records of different business types based on different scheduling tasks of different containers; wherein the isolation of the business records of different business types comprises: storing the business records of different business types in different tables respectively; wherein the isolation and scheduling of the business records of different business types based on different scheduling tasks of different containers comprises: when the third-party system is applied to one machine, setting different threads for different containers; scheduling the business records in the tables registered on different containers through different threads, wherein the same thread schedules the business records in the tables registered on the same container; when the third-party system is applied to N machines, setting different machines for different containers; scheduling the business records in the tables registered on different containers through different machines applied with the third-party system, wherein the same machine schedules the business records in the tables registered on the same container; N is a positive integer greater than 1.

2. The method of claim 1, wherein, After the obtaining of the business records of at least two business types of at least two business application systems, and before the storing of the business records of different business types in different tables respectively, the method further comprises: storing each received business record in a unified storage table; determining whether the isolation trigger condition is met currently, and if yes, executing the storing of the business records of different business types in different tables for the unified storage table; for each table name of the different tables, setting a prefix of each table name to identify the unified storage table, and setting a suffix of each table name to identify the business type of the business record in the table respectively.

3. The method of claim 2, wherein, The determination of whether the isolation trigger condition is met currently comprises at least one of the following: determining whether the number of the business records stored in the unified storage table is greater than a predetermined value, and if yes, the isolation trigger condition is met currently; determining whether the business type of any business record stored in the unified storage table belongs to a sensitive type, and if yes, the isolation trigger condition is met currently; determining whether a supervision instruction is received, and if yes, the isolation trigger condition is met currently.

4. The service processing device for intercommunication between different service applications, applied to a third-party system for processing intercommunication data between different service application systems, wherein, The method comprises the following steps: a receiving module configured to obtain business records of at least two business types of at least two business application systems; a record isolation module configured to isolate the business records of different business types; a container construction module configured to construct at least two containers; The scheduling isolation module is configured to register scheduling tasks of service records in different tables of different service types to different containers, and to perform isolated scheduling on the service records of the different service types based on different scheduling tasks of the different containers; wherein the scheduling tasks of the service records in the first number of tables are registered to the same container; the first number is an integer greater than 1. The record isolation module is configured to store the service records of different service types in different tables respectively. The scheduling isolation module is configured to perform: When the third-party system is applied to one machine, different threads are set for different containers, and the service records in the tables registered on the different containers are scheduled through different threads, wherein the same thread schedules the service records in the tables registered on the same container. When the third-party system is applied to N machines, different machines are set for different containers, and the service records in the tables registered on the different containers are scheduled through different machines applied with the third-party system, wherein the same machine schedules the service records in the tables registered on the same container; N is a positive integer greater than 1.

5. The apparatus of claim 4, further comprising: An isolation triggering module; The receiving module is configured to store each received service record in a unified storage table after obtaining service records of at least two service types of at least two service application systems; The isolation triggering module is configured to determine whether the isolation triggering condition is met, and to trigger the record isolation module if the isolation triggering condition is met. The record isolation module is configured to perform: After being triggered by the isolation triggering module, the record isolation module stores the service records of different service types in the unified storage table in different tables respectively. For each table name of the different tables, a prefix of each table name is set to identify the unified storage table, and a suffix of each table name is set to identify the service type of the service records stored in the table respectively.

6. A computing device comprising a memory and a processor, the memory storing executable code, and the processor implementing the method of any one of claims 1-3 when executing the executable code.

Images