Multi-compatibility implementation method, device and equipment for business system based on kernel standardization

Abstract

The invention discloses a multi-compatibility implementation method, device and equipment for a business system based on kernel standardization. The method comprises the following steps: acquiring to-be-compatible service interface data of to-be-compatible service and a corresponding compatible service type; if it is determined that the compatible service type is a new service compatible type, constructing a compatible relationship between the to-be-compatible service interface data and the initial configuration data of the service system based on the standardized interface data; if it is determined that the compatible service type is the existing service compatible type, constructing a compatible relationship between the to-be-compatible service interface data and the initial configuration data of the service system based on the standardized interface data and the adaptive data; acquiring a current service system; and embedding the data into a comprehensive service system to obtain a current comprehensive service system. According to the embodiment of the invention, different types of to-be-compatible service interface data are compatible and fused based on the standardized interface data of the service system, so that the dependency coupling degree of the service system on other services is low, and more services can be more flexibly compatible.

Description

Technical Field

[0001] The present invention relates to the technical field of system development, and particularly to a method, device and equipment for multi-compatible implementation of a business system based on kernel standardization. Background Art

[0002] Currently, an enterprise's business systems (such as software systems like sales systems and marketing systems) are generally coupled with the enterprise's group architecture. For example, the group architecture also includes an event system, a tag system, an authentication system, an approval flow system, an event flow processing system, and a big data system. The coupling degree between the business system and the group architecture composed of the above systems is relatively high, and it cannot be directly privatized. Moreover, the business system generally has a high degree of dependency coupling with other services within the group, making it difficult to split from other services. Summary of the Invention

[0003] Embodiments of the present invention provide a method, device and equipment for multi-compatible implementation of a business system based on kernel standardization, aiming to solve the problem in the prior art that the coupling degree between an enterprise's business system and the corresponding large system architecture of the enterprise is relatively high, and the dependency coupling degree with other services is high, resulting in difficulty in being separately split to be compatible with more services.

[0004] In a first aspect, embodiments of the present invention provide a method for multi-compatible implementation of a business system based on kernel standardization, which includes:

[0005] In response to a business system compatibility instruction, obtain the to-be-compatible service interface data of the to-be-compatible service; wherein, the business system targeted by the business system compatibility instruction has a standardized kernel architecture including at least a system kernel, an extension point, and an adaptation layer;

[0006] Obtain the compatible service type corresponding to the to-be-compatible service interface data;

[0007] If it is determined that the compatible service type is a new service compatibility type, obtain the initial configuration data of the business system and the standardized interface data, and build a compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the business system based on the standardized interface data;

[0008] If it is determined that the compatible service type is an existing service compatibility type, obtain the initial configuration data of the business system, the standardized interface data, and the adaptation data, and build a compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the business system based on the standardized interface data and the adaptation data;

[0009] If it is determined that the compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the business system has been completed, obtain the current business system accordingly;

[0010] Embed the current business system into the integrated business system to obtain the current integrated business system.

[0011] In a second aspect, an embodiment of the present invention further provides a multi-compatible implementation device for business systems based on kernel standardization, which includes:

[0012] A unit for obtaining service data to be compatible, configured to obtain interface data of the service to be compatible in response to a business system compatibility instruction; wherein, the business system targeted by the business system compatibility instruction has a standardized kernel architecture including at least a system kernel, an extension point, and an adaptation layer;

[0013] A unit for obtaining compatible service types, configured to obtain the compatible service types corresponding to the interface data of the service to be compatible;

[0014] A first compatibility construction unit, configured to, if it is determined that the compatible service type is a new service compatibility type, obtain initial configuration data of the business system and standardized interface data, and construct a compatibility relationship between the interface data of the service to be compatible and the initial configuration data of the business system based on the standardized interface data;

[0015] A second compatibility construction unit, configured to, if it is determined that the compatible service type is an existing service compatibility type, obtain initial configuration data of the business system, standardized interface data, and adaptation data, and construct a compatibility relationship between the interface data of the service to be compatible and the initial configuration data of the business system based on the standardized interface data and the adaptation data;

[0016] A current business system processing unit, configured to, if it is determined that the compatibility relationship between the interface data of the service to be compatible and the initial configuration data of the business system has been constructed, correspondingly obtain the current business system;

[0017] A business system embedding processing unit, configured to embed the current business system into the integrated business system to obtain the current integrated business system.

[0018] In a third aspect, an embodiment of the present invention further provides a computer device, which includes a memory and a processor, and a computer program is stored on the memory. When the processor executes the computer program, the method described in the first aspect above is implemented.

[0019] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, and a computer program is stored on the computer storage medium. The computer program includes program instructions, and when the program instructions are executed by a processor, the method described in the first aspect above can be implemented.

[0020] The embodiments of the present invention provide a method, apparatus, and device for multi-compatible implementation of a service system based on kernel standardization. The method includes: in response to a service system compatibility instruction, obtaining the data of the service interface to be compatible of the service to be compatible; obtaining the compatible service type corresponding to the data of the service interface to be compatible; if it is determined that the compatible service type is a newly created service compatibility type, obtaining the initial configuration data of the service system and the standardized interface data, and constructing a compatibility relationship between the data of the service interface to be compatible of the service to be compatible and the initial configuration data of the service system based on the standardized interface data; if it is determined that the compatible service type is an existing service compatibility type, obtaining the initial configuration data of the service system, the standardized interface data, and the adaptation data, and constructing a compatibility relationship between the data of the service interface to be compatible of the service to be compatible and the initial configuration data of the service system based on the standardized interface data and the adaptation data; if it is determined that the compatibility relationship between the data of the service interface to be compatible of the service to be compatible and the initial configuration data of the service system has been constructed, correspondingly obtaining the current service system; and embedding the current service system into the integrated service system to obtain the current integrated service system. The embodiments of the present invention are compatible with and integrate different types of service interface data to be compatible based on the standardized interface data of the service system, so that the service system has a low degree of dependency coupling on other services and can be more flexible in being compatible with more services. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the following drawings are some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0022] Figure 1 It is a schematic diagram of the application scenario of the method for multi-compatible implementation of a service system based on kernel standardization provided by the embodiments of the present invention;

[0023] Figure 2 It is a schematic flowchart of the method for multi-compatible implementation of a service system based on kernel standardization provided by the embodiments of the present invention;

[0024] Figure 3 It is a schematic block diagram of the device for multi-compatible implementation of a service system based on kernel standardization provided by the embodiments of the present invention;

[0025] Figure 4 It is a schematic block diagram of the computer device provided by the embodiments of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0026] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0027] It should be understood that when used in this specification and the appended claims, the terms "comprises" and "comprising" indicate the presence of the described features, wholes, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or their combinations.

[0028] It should also be understood that the terms used in this specification of the present invention are merely for the purpose of describing specific embodiments and are not intended to limit the present invention. As used in this specification of the present invention and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an", and "the" are intended to include the plural forms.

[0029] It should be further understood that the term " / and / " used in this specification of the present invention and the appended claims refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0030] Please refer to Figure 1 and Figure 2 simultaneously, where Figure 1 is a schematic diagram of the scenario of the method for realizing multi-compatibility of the business system based on kernel standardization in the embodiments of the present invention, Figure 2 is a schematic flowchart of the method for realizing multi-compatibility of the business system based on kernel standardization provided in the embodiments of the present invention. As Figure 1 shown, the method for realizing multi-compatibility of the business system based on kernel standardization provided in the embodiments of the present invention is applied to the server 10, and the server 10 can also be communicatively connected to other servers 20.

[0031] As Figure 2 shown, the method includes the following steps S110-S160.

[0032] S110. In response to the business system compatibility instruction, obtain the data of the to-be-compatible service interface of the to-be-compatible service.

[0033] Among them, the business system targeted by the business system compatibility instruction has a standardized kernel architecture including at least a system kernel, an extension point, and an adaptation layer.

[0034] In this embodiment, the technical solution is described with the server as the execution entity. A business system (such as a sales system, a marketing system, etc.) is pre-deployed in the server. In order to enable the above business system to be compatible with a variety of other functional systems, the business system can have a standardized kernel architecture, such as a standardized kernel architecture form with at least a system kernel, an extension point, and an adaptation layer. After the kernel architecture of the business system is improved in the above manner, when there is a need for other services to be compatible with the business system, when the maintenance personnel of the business system operate the corresponding user interface of the server and select the service compatibility operation button of the business system, a business system compatibility instruction is generated accordingly. After that, the interface data of the service to be compatible corresponding to the business system compatibility instruction can also be obtained. At this time, the obtained interface data of the service to be compatible has not yet established a compatibility relationship with the business system and needs to be processed subsequently.

[0035] S120. Obtain the compatibility service type corresponding to the interface data of the service to be compatible.

[0036] In this embodiment, after the interface data of the service to be compatible is obtained, it is also necessary to further obtain the corresponding compatibility service type. In this application, it is set that the compatibility service type at least includes a new service compatibility type and an existing service compatibility type, where the new service compatibility type is used to indicate that the service to be compatible is a newly created service, and the existing service compatibility type is used to indicate that the service to be compatible is a service that has existed in history. By determining the compatibility service type corresponding to the interface data of the service to be compatible, it is convenient to adopt the corresponding compatibility relationship construction method subsequently.

[0037] S130. If it is determined that the compatibility service type is the new service compatibility type, obtain the initial configuration data of the business system and the standardized interface data, and build a compatibility relationship between the interface data of the service to be compatible and the initial configuration data of the business system based on the standardized interface data.

[0038] In this embodiment, when the compatibility service type is the new service compatibility type, the initial configuration data of the business system and the standardized interface data of the business system can be obtained first. At this time, no data related to the service to be compatible has been added to the initial configuration data of the business system. After that, the business system and the service to be compatible can be docked through the standardized interface corresponding to the standardized interface data, so that the compatibility relationship between the interface data of the service to be compatible and the initial configuration data of the business system can be quickly established. For example, the interface data of the service to be compatible is correspondingly added to the initial configuration data of the business system, so that after the business system is compatible with the compatibility service corresponding to the compatibility service interface data, at least the compatibility of the function, input and output parameters, data type, call method, etc. of the service to be compatible is completed.

[0039] Among them, when configuring standardized interface data for the business system, specifically, interface standardization and interaction standardization transformations are carried out, which can realize the kernel upgrade without chain and the subsystem with configuration dependencies of the business system, meeting the personalized requirements of the business and the requirement of kernel reuse for private deployment.

[0040] In one embodiment, the initial configuration data of the business system at least includes system kernel data and system extension point data;

[0041] Building the compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the business system based on the standardized interface data includes:

[0042] Adding the to-be-compatible service interface data to the system extension point data in the initial configuration of the business system based on the standardized interface data to build the compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the business system, and updating the initial configuration data of the business system.

[0043] In this embodiment, when the business system has a standardized kernel architecture and at least has a standardized kernel architecture form of a system kernel, extension points, and an adaptation layer, the initial configuration data of the business system can at least include system kernel data and system extension point data. When building the compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the business system, specifically, the to-be-compatible service interface data is added to the system extension point data in the initial configuration of the business system based on the standardized interface data, and the update of the initial configuration data of the business system is realized by the above method of adding and updating the system extension point data.

[0044] S140. If it is determined that the compatible service type is an existing service compatibility type, obtain the initial configuration data of the business system, the standardized interface data, and the adaptation data, and build the compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the business system based on the standardized interface data and the adaptation data.

[0045] In this embodiment, when the compatible service type is an existing service compatibility type, the initial configuration data of the business system, the standardized interface data, and the adaptation data of the business system can be obtained first (in this case, compared with creating a new service compatibility type, the adaptation data needs to be obtained additionally). At this time, no data related to the to-be-compatible service has been added to the initial configuration data of the business system. Then, the business system and the to-be-compatible service are docked with the standardized interface corresponding to the standardized interface data and the adaptation layer (or adaptation service) corresponding to the adaptation data, so that the compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the business system can be quickly established, such as correspondingly adding the to-be-compatible service interface data and the adaptation data to the initial configuration data of the business system.

[0046] In one embodiment, the initial configuration data of the service system at least includes system kernel data, system extension point data, and system adaptation layer data;

[0047] Constructing the compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the service system based on the standardized interface data and the adaptation data includes:

[0048] Based on the standardized interface data, adding the to-be-compatible service interface data to the system extension point data in the initial configuration of the service system, and adding the adaptation data to the system adaptation layer data in the initial configuration of the service system, so as to construct the compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the service system, and update the initial configuration data of the service system; wherein, the adaptation data is adaptation layer data or adaptation service data.

[0049] In this embodiment, when the service system has a standardized kernel architecture and at least has a standardized kernel architecture form of a system kernel, extension points, and an adaptation layer, it can be ensured that the initial configuration data of the service system at least includes system kernel data, system extension point data, and system adaptation layer data. When constructing the compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the service system, specifically, based on the standardized interface data, adding the to-be-compatible service interface data to the system extension point data in the initial configuration of the service system, and adding the adaptation data to the system adaptation layer data in the initial configuration of the service system, and updating the initial configuration data of the service system by the above-mentioned method of adding and updating the system extension point data and the system adaptation layer data. Among them, when the adaptation data includes adaptation layer data, it is mainly used for data processing and conversion in the system adaptation layer; when the adaptation data includes adaptation service data, it is mainly used for data involved and processed during the operation of services in the system adaptation layer, including input data, output data, and intermediate data generated and used inside the service, and is a specific execution unit for implementing the functions of the system adaptation layer, taking data as the processing object and completing various adaptation operations.

[0050] S150. If it is determined that the compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the service system has been constructed, then obtain the current service system correspondingly, and embed the current service system into the integrated service system to obtain the current integrated service system.

[0051] In this embodiment, after the compatibility relationship between the data of the service interface to be compatible and the initial configuration data of the business system is completed, it means that the business system has achieved compatibility with the service to be compatible. At this time, a coupling relationship is established between the two, and the obtained current business system can be regarded as a complete new business system. If this new business system and the integrated business system to be embedded later belong to the same enterprise, the new business system can also be embedded in the integrated business system of the enterprise to realize the compatible application of business systems within the same enterprise.

[0052] S160. Embed the current business system into the integrated business system to obtain the current integrated business system.

[0053] In this embodiment, after embedding the current business system into the integrated business system to obtain the current integrated business system, still referring to the above example, the compatible application of business systems within the same enterprise is realized. For example, there are also a label system, a big data system, a reach system, a rights and interests system, etc. in the integrated business system. Embedding the current business system into the integrated business system can quickly obtain the current integrated business system. It can be seen that through the above method, the integration of the current business system and the integrated business system can be quickly realized.

[0054] In one embodiment, as the first specific embodiment of the current integrated business system applied to user data processing, after step S160, it further includes:

[0055] If the current user data is detected, input the current user data into the current integrated business system for data processing to obtain the corresponding current user data processing result;

[0056] Obtain the target data receiving subsystem corresponding to the current user data processing result in the current integrated business system, and send the current user data processing result to the target data receiving subsystem.

[0057] In this embodiment, since the business system has been made compatible with the service to be compatible and embedded in the current integrated business system, based on the data processing logic corresponding to the business system and the service to be compatible, as well as the data processing logic of other systems included in the current integrated business system, and the overall data processing process, it can be used as the basic data for the current integrated business system to perform data processing. For example, the current integrated business system is still used by the business system within the enterprise to process user data. At this time, the current integrated business system detects the current user data (such as including user face images, user basic information, user business requirements, etc.). After inputting the current user data into the current integrated business system for processing, the current user data processing result can be obtained.

[0058] Moreover, the obtained current user data processing result needs to be output or saved in the business system within the enterprise. At this time, it is also necessary to obtain the target data receiving subsystem corresponding to the current user data processing result in the current integrated business system, and send the current user data processing result to the target data receiving subsystem. Finally, the target data receiving subsystem outputs or saves the current user data processing result.

[0059] In one embodiment, obtaining the target data receiving subsystem corresponding to the current user data processing result in the current integrated business system includes:

[0060] Obtain the system adaptation layer data corresponding to the current business system in the current integrated business system, and determine the target data receiving subsystem based on the system adaptation layer data.

[0061] In this embodiment, in order to more quickly determine the target data receiving subsystem in the current integrated business system, the system adaptation layer data corresponding to the current business system can be obtained in the current integrated business system first. Then, by parsing the system adaptation layer data, the object to be compatible with the service, which can be used as the data receiving subsystem, can be determined. Finally, the target data receiving subsystem is determined based on the system adaptation layer data. It can be seen that by parsing the system adaptation layer data, the target data receiving subsystem can be quickly determined in the scenario where the current user data processing result needs to be output or saved in the business system within the enterprise.

[0062] In one embodiment, as the second specific embodiment of the current integrated business system applied to user data processing, after step S160, it further includes:

[0063] If the current user data is detected, input the current user data into the current integrated business system for data processing to obtain the corresponding current user data processing result;

[0064] Obtain the third-party system communicatively connected to the current integrated business system based on the adaptation layer, and send the current user data processing result to the third-party system.

[0065] In this embodiment, since the business system has been made compatible with the service to be compatible and embedded in the current integrated business system, it can also be used as the basic data for data processing in the current integrated business system based on the data processing logics corresponding to the business system and the service to be compatible, as well as the data processing logics of other systems included in the current integrated business system, and the overall data processing flow. Moreover, the current integrated business system can also be connected to an external third-party system. When the current integrated business system detects the current user data (such as including user face images, user basic information, user business requirements, etc.), after inputting the current user data into the current integrated business system for processing, the current user data processing result can be obtained.

[0066] Moreover, the obtained current user data processing result needs to be output to an external system. At this time, it is also necessary to determine the third-party system communicatively connected to the current integrated business system based on the adaptation layer in the current integrated business system, and send the current user data processing result to the third-party system.

[0067] In one embodiment, as a scenario where the current business system is reused and called by other systems within an enterprise, after step S150, it further includes:

[0068] If a business system call instruction is detected, the current business system is correspondingly system-packaged to obtain a packaged business system, and the packaged business system is sent to the receiving system corresponding to the business system call instruction.

[0069] In this embodiment, in order to achieve the flexible call and deployment of the current business system, it is also possible to receive the business system calls of other business teams within the group. That is, when the server detects a business system call instruction sent by another business server (which can be within the same intranet of the group as the server), at this time, the server can first correspondingly system-package the current business system to obtain a packaged business system. Then, the server sends the packaged business system to the receiving system corresponding to the business system call instruction (such as the other business server in the above example). After the receiving system receives the packaged new business system, it installs and deploys it, and can also be integrated with other business systems in the receiving system to achieve the flexible compatibility and coupling between other business systems and the current business system.

[0070] It can be seen that the embodiments implementing this method can be compatible with and integrate different types of service interface data to be compatible based on the standardized interface data of the business system, so that the degree of dependency coupling of the business system on other services is low, and it can be more flexible in being compatible with more services.

[0071] Figure 3 It is a schematic block diagram of a device for realizing multi-compatibility of a business system based on kernel standardization provided by an embodiment of the present invention. AsFigure 3 As shown, corresponding to the above multi-compatible implementation method of the business system based on kernel standardization, the present invention also provides a multi-compatible implementation device 100 for the business system based on kernel standardization. The multi-compatible implementation device 100 for the business system based on kernel standardization includes units for executing the above multi-compatible implementation method of the business system based on kernel standardization. Please refer to Figure 3 , the multi-compatible implementation device 100 for the business system based on kernel standardization includes: a to-be-compatible service data acquisition unit 110, a compatible service type acquisition unit 120, a first compatible construction unit 130, a second compatible construction unit 140, a current business system processing unit 150, and a business system embedding processing unit 160.

[0072] The to-be-compatible service data acquisition unit 110 is configured to acquire to-be-compatible service interface data of the to-be-compatible service in response to a business system compatibility instruction.

[0073] Wherein, the business system targeted by the business system compatibility instruction has a standardized kernel architecture including at least a system kernel, an extension point, and an adaptation layer.

[0074] In this embodiment, the technical solution is described with the server as the execution subject. In the server, a business system (such as a sales system, a marketing system, etc.) is pre-deployed. In order to enable the above business system to be compatible with multiple other functional systems, the business system can be made to have a standardized kernel architecture, such as a standardized kernel architecture form with at least a system kernel, an extension point, and an adaptation layer. After the kernel architecture of the business system is improved in the above manner, when there is a need for other to-be-compatible services to be compatible with the business system, it can be when the maintenance personnel of the business system operate the corresponding user interface of the server and select the business system service compatibility operation button, then a business system compatibility instruction is generated accordingly. After that, the to-be-compatible service interface data corresponding to the business system compatibility instruction can also be obtained. At this time, the obtained to-be-compatible service interface data has not yet established a compatibility relationship with the business system and needs to be processed subsequently.

[0075] The compatible service type acquisition unit 120 is configured to acquire the compatible service type corresponding to the to-be-compatible service interface data.

[0076] In this embodiment, after the to-be-compatible service interface data is acquired, it is also necessary to further acquire the corresponding compatible service type. In this application, the compatible service type is set to include at least a new service compatible type and an existing service compatible type, where the new service compatible type is used to indicate that the to-be-compatible service is a newly created service, and the existing service compatible type is used to indicate that the to-be-compatible service is a historical existing service. By determining the compatible service type corresponding to the to-be-compatible interface service data, it is convenient to adopt corresponding compatibility relationship construction methods subsequently.

[0077] The first compatible construction unit 130 is configured to, if it is determined that the compatible service type is a new service compatible type, obtain the initial configuration data of the business system and the standardized interface data, and build a compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the business system based on the standardized interface data.

[0078] In this embodiment, when the compatible service type is a new service compatible type, the initial configuration data of the business system and the standardized interface data of the business system can be obtained first. At this time, no data related to the to-be-compatible service has been added to the initial configuration data of the business system. Then, the standardized interface corresponding to the standardized interface data can be used to dock the business system with the to-be-compatible service, so that the compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the business system can be quickly established. For example, the to-be-compatible service interface data can be correspondingly added to the initial configuration data of the business system, so that after the business system is compatible with the compatible service corresponding to the compatible service interface data, at least the compatibility of the to-be-compatible interface in terms of function, input and output parameters, data type, call method, etc. is completed.

[0079] In one embodiment, the initial configuration data of the business system at least includes system kernel data and system extension point data;

[0080] The building of the compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the business system based on the standardized interface data includes:

[0081] Based on the standardized interface data, add the to-be-compatible service interface data to the system extension point data in the initial configuration of the business system to build the compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the business system, and update the initial configuration data of the business system.

[0082] In this embodiment, when the business system has a standardized kernel architecture and at least has a standardized kernel architecture form of a system kernel, an extension point, and an adaptation layer, the initial configuration data of the business system can at least include system kernel data and system extension point data. When building the compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the business system, specifically, based on the standardized interface data, the to-be-compatible service interface data is added to the system extension point data in the initial configuration of the business system, and the update of the initial configuration data of the business system is realized by the above method of adding and updating the system extension point data.

[0083] The second compatibility building unit 140 is configured to, if it is determined that the compatible service type is an existing service compatible type, obtain the initial configuration data of the business system, the standardized interface data, and the adaptation data, and build a compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the business system based on the standardized interface data and the adaptation data.

[0084] In this embodiment, when the compatible service type is an existing service compatible type, the initial configuration data of the business system, the standardized interface data, and the adaptation data of the business system can be obtained first (in this case, compared with creating a new service compatible type, the adaptation data also needs to be obtained). At this time, no data related to the to-be-compatible service has been added to the initial configuration data of the business system. Then, the business system and the to-be-compatible service are docked with the standardized interface corresponding to the standardized interface data and the adaptation layer (or adaptation service) corresponding to the adaptation data, so that the compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the business system can be quickly established, such as correspondingly adding the to-be-compatible service interface data and the adaptation data to the initial configuration data of the business system.

[0085] In one embodiment, the initial configuration data of the business system at least includes system kernel data, system extension point data, and system adaptation layer data;

[0086] The building of the compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the business system based on the standardized interface data and the adaptation data includes:

[0087] Adding the to-be-compatible service interface data to the system extension point data in the initial configuration of the business system based on the standardized interface data, and adding the adaptation data to the system adaptation layer data in the initial configuration of the business system to build the compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the business system, and updating the initial configuration data of the business system; wherein, the adaptation data is adaptation layer data or adaptation service data.

[0088] In this embodiment, when the business system has a standardized kernel architecture, and at least has the form of a standardized kernel architecture including a system kernel, an extension point, and an adaptation layer, at least the system kernel data, system extension point data, and system adaptation layer data can be included in the initial configuration data of the business system. When constructing the compatibility relationship between the data of the service interface to be compatible and the initial configuration data of the business system, specifically, based on the standardized interface data, the data of the service interface to be compatible is added to the system extension point data in the initial configuration of the business system, and the adaptation data is added to the system adaptation layer data in the initial configuration of the business system. The update of the initial configuration data of the business system is achieved by the above method of adding and updating the system extension point data and the system adaptation layer data. Among them, when the adaptation data includes adaptation layer data, it is mainly used for data processing and conversion in the system adaptation layer; when the adaptation data includes adaptation service data, it is mainly used for data involved and processed during the operation of services in the system adaptation layer, including input data, output data, and intermediate data generated and used inside the service. It is the specific execution unit for implementing the functions of the system adaptation layer, taking data as the processing object to complete various adaptation operations.

[0089] The current business system processing unit 150 is configured to, if it is determined that the compatibility relationship between the data of the service interface to be compatible and the initial configuration data of the business system has been completed, correspondingly obtain the current business system and embed the current business system into the integrated business system to obtain the current integrated business system.

[0090] In this embodiment, after the compatibility relationship between the data of the service interface to be compatible and the initial configuration data of the business system is completed, it means that the business system has achieved compatibility with the service to be compatible. At this time, a coupling relationship is constructed between the two, and the obtained current business system can be regarded as a complete new business system. If this new business system and the integrated business system to be embedded later belong to the same enterprise, the new business system can also be embedded in the integrated business system of the enterprise to realize the compatibility application of business systems within the same enterprise.

[0091] The business system embedding processing unit 160 is configured to embed the current business system into the integrated business system to obtain the current integrated business system.

[0092] In this embodiment, after the current business system is embedded into the integrated business system to obtain the current integrated business system, still referring to the above example, the compatibility application of business systems within the same enterprise is realized. For example, there are also a label system, a big data system, a reach system, a rights and interests system, etc. in the integrated business system. Embedding the current business system into the integrated business system can quickly obtain the current integrated business system. It can be seen that through the above method, the integration of the current business system and the integrated business system can be quickly realized.

[0093] In one embodiment, as the first specific embodiment of the current integrated service system applied to user data processing, the multi-compatible implementation device 100 of the service system based on kernel standardization further includes:

[0094] A first user data processing unit, configured to input the current user data into the current integrated service system for data processing if the current user data is detected, so as to obtain a corresponding current user data processing result;

[0095] A first user data sending unit, configured to obtain a target data receiving subsystem corresponding to the current user data processing result in the current integrated service system, and send the current user data processing result to the target data receiving subsystem.

[0096] In this embodiment, since the service system has been made compatible with the service to be compatible and embedded in the current integrated service system, based on the data processing logics corresponding to the service system and the service to be compatible, as well as the data processing logics of other systems included in the current integrated service system, and the overall data processing flow, it can be used as the basic data for data processing by the current integrated service system. For example, when the current integrated service system is still a service system used within an enterprise to process user data, and at this time the current integrated service system detects current user data (such as including user face images, user basic information, user service requirements, etc.), after inputting the current user data into the current integrated service system for processing, a current user data processing result can be obtained.

[0097] Moreover, the obtained current user data processing result needs to be output or saved in the service system within the enterprise. At this time, it is also necessary to obtain a target data receiving subsystem corresponding to the current user data processing result in the current integrated service system, and send the current user data processing result to the target data receiving subsystem. Finally, the target data receiving subsystem outputs or saves the current user data processing result.

[0098] In one embodiment, obtaining the target data receiving subsystem corresponding to the current user data processing result in the current integrated service system includes:

[0099] Obtaining the system adaptation layer data corresponding to the current service system in the current integrated service system, and determining the target data receiving subsystem based on the system adaptation layer data.

[0100] In this embodiment, in order to more quickly determine the target data receiving subsystem in the current integrated service system, system adaptation layer data corresponding to the current service system may first be obtained in the current integrated service system, and then the object to be compatible service, which can be used as the data receiving subsystem, can be determined by parsing the system adaptation layer data. Finally, the target data receiving subsystem is determined based on the system adaptation layer data. It can be seen that by parsing the system adaptation layer data, the target data receiving subsystem can be quickly determined in the scenario where the current user data processing result needs to be output or saved in the business system within the enterprise.

[0101] In one embodiment, as the second specific embodiment of the current integrated service system applied to user data processing, the business system multi-compatibility implementation device 100 based on kernel standardization further includes:

[0102] A second user data processing unit, configured to input the current user data into the current integrated service system for data processing to obtain a corresponding current user data processing result if the current user data is detected;

[0103] A second user data sending unit, configured to obtain a third-party system communicatively connected to the current integrated service system based on the adaptation layer, and send the current user data processing result to the third-party system.

[0104] In this embodiment, since the business system has been made compatible with the service to be compatible and embedded in the current integrated service system, it can also be used as the basic data for data processing in the current integrated service system based on the data processing logics corresponding to the business system and the service to be compatible, as well as the data processing logics of other systems included in the current integrated service system, and the overall data processing flow. Moreover, the current integrated service system can also be docked with an external third-party system. When the current integrated service system detects current user data (such as including user face images, user basic information, user service requirements, etc.), after inputting the current user data into the current integrated service system for processing, a current user data processing result can be obtained.

[0105] Moreover, if the obtained current user data processing result needs to be output to an external system, at this time, it is also necessary to determine a third-party system communicatively connected to the current integrated service system based on the adaptation layer in the current integrated service system, and send the current user data processing result to the third-party system.

[0106] In one embodiment, as the scenario where the current business system is reused and called by other systems within the enterprise, the business system multi-compatibility implementation device 100 based on kernel standardization further includes:

[0107] A service system call processing unit, which is configured to, if a service system call instruction is detected, encapsulate the current service system to obtain an encapsulated service system, and send the encapsulated service system to a receiving system corresponding to the service system call instruction.

[0108] In this embodiment, in order to flexibly call and deploy the current service system, it is also possible to receive service system calls from other business teams within the group. That is, when the server detects a service system call instruction sent by another service server (which may be within the same intranet of the group as the server), the server can first encapsulate the current service system to obtain an encapsulated service system. Then, the server sends the encapsulated service system to a receiving system corresponding to the service system call instruction (such as another service server in the above example). After receiving the encapsulated new service system, the receiving system installs and deploys it, and can also integrate it with other service systems in the receiving system to achieve flexible compatibility and coupling between other service systems and the current service system.

[0109] It can be seen that implementing the embodiments of this device can be compatible and integrate different types of service interface data to be compatible based on the standardized interface data of the service system, resulting in a low degree of dependency coupling of the service system on other services and enabling more flexible compatibility with more services.

[0110] The above service system multi-compatibility implementation device based on kernel standardization can be implemented in the form of a computer program, and this computer program can run on a computer device as Figure 4 shown.

[0111] Please refer to Figure 4 , Figure 4 which is a schematic block diagram of a computer device provided by an embodiment of the present invention. This computer device integrates any one of the service system multi-compatibility implementation devices based on kernel standardization provided by the embodiments of the present invention.

[0112] Refer to Figure 4 , this computer device 400 includes a processor 402, a memory, and a network interface 405 connected through a system bus 401. Among them, the memory may include a storage medium 403 and an internal memory 404.

[0113] The storage medium 403 can store an operating system 4031 and a computer program 4032. This computer program 4032 includes program instructions, and when these program instructions are executed, the processor 402 can be made to execute a service system multi-compatibility implementation method based on kernel standardization.

[0114] The processor 402 is used to provide computing and control capabilities to support the operation of the entire computer device.

[0115] The internal memory 404 provides an environment for the operation of the computer program 4032 in the storage medium 403. When the computer program 4032 is executed by the processor 402, the processor 402 can be caused to execute the above-mentioned method for realizing multi-compatibility of the service system based on kernel standardization.

[0116] The network interface 405 is used for network communication with other devices. Those skilled in the art can understand that Figure 4 the structure shown in is only a block diagram of some structures related to the solution of the present invention, and does not constitute a limitation on the computer device to which the solution of the present invention is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine some components, or have different component arrangements.

[0117] Among them, the processor 402 is used to run the computer program 4032 stored in the memory to implement the following steps:

[0118] In response to a service system compatibility instruction, obtain the interface data of the service to be compatible of the service to be compatible; wherein, the service system targeted by the service system compatibility instruction has a standardized kernel architecture including at least a system kernel, an extension point, and an adaptation layer;

[0119] Obtain the compatible service type corresponding to the interface data of the service to be compatible;

[0120] If it is determined that the compatible service type is a new service compatible type, obtain the initial configuration data of the service system and the standardized interface data, and build a compatibility relationship between the interface data of the service to be compatible and the initial configuration data of the service system based on the standardized interface data;

[0121] If it is determined that the compatible service type is an existing service compatible type, obtain the initial configuration data of the service system, the standardized interface data, and the adaptation data, and build a compatibility relationship between the interface data of the service to be compatible and the initial configuration data of the service system based on the standardized interface data and the adaptation data;

[0122] If it is determined that the compatibility relationship between the interface data of the service to be compatible and the initial configuration data of the service system has been completed, obtain the current service system accordingly;

[0123] Embed the current service system into the integrated service system to obtain the current integrated service system.

[0124] It should be understood that in the embodiments of the present invention, the processor 402 may be a central processing unit (CPU), and the processor 402 may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0125] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program includes program instructions, and the computer program can be stored in a storage medium, and the storage medium is a computer-readable storage medium. The program instructions are executed by at least one processor in the computer system to implement the process steps of the embodiments of the above methods.

[0126] Therefore, the present invention also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and the computer program includes program instructions. When the program instructions are executed by a processor, the processor performs the following steps:

[0127] In response to a service system compatibility instruction, obtain the compatibility service interface data of the service to be compatible; wherein, the service system targeted by the service system compatibility instruction has a standardized kernel architecture including at least a system kernel, an extension point, and an adaptation layer;

[0128] Obtain the compatible service type corresponding to the compatibility service interface data;

[0129] If it is determined that the compatible service type is a new service compatibility type, obtain the initial configuration data of the service system and the standardized interface data, and build a compatibility relationship between the compatibility service interface data and the initial configuration data of the service system based on the standardized interface data;

[0130] If it is determined that the compatible service type is an existing service compatibility type, obtain the initial configuration data of the service system, the standardized interface data, and the adaptation data, and build a compatibility relationship between the compatibility service interface data and the initial configuration data of the service system based on the standardized interface data and the adaptation data;

[0131] If it is determined that the compatibility relationship between the to-be-compatible service interface data and the initial configuration data of the service system has been completed, the current service system is correspondingly obtained;

[0132] The current service system is embedded into the integrated service system to obtain the current integrated service system.

[0133] The storage medium can be various computer-readable storage media such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a magnetic disk, or an optical disc, etc., which can store program codes.

[0134] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present invention.

[0135] In several embodiments provided by the present invention, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of each unit is only a logical function division, and there can be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.

[0136] The steps in the method embodiments of the present invention can be adjusted, combined, and deleted according to actual needs. The units in the device embodiments of the present invention can be combined, divided, and deleted according to actual needs. In addition, the functional units in each embodiment of the present invention can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit.

[0137] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a terminal, or a network device, etc.) to execute all or part of the steps of the methods described in each embodiment of the present invention.

[0138] As described above, it is only the specific implementation manner of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present invention can easily think of various equivalent modifications or substitutions, and these modifications or substitutions should all be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A method for realizing multi-compatibility of a business system based on kernel standardization, characterized in that: include: In response to the business system compatibility instruction, obtaining compatible service interface data of the compatible service; wherein the business system targeted by the business system compatibility instruction has a standardized kernel architecture including at least a system kernel, an extension point and an adaptation layer; Obtaining the compatible service type corresponding to the to-be-compatible service interface data; If it is determined that the compatible service type is a newly created service compatible type, then obtaining the business system initial configuration data and standardized interface data, and building a compatible relationship between the to-be-compatible service interface data and the business system initial configuration data based on the standardized interface data; If it is determined that the compatible service type is an existing service compatible type, then obtaining the business system initial configuration data, standardized interface data and adaptation data, and building a compatibility relationship between the to-be-compatible service interface data and the business system initial configuration data based on the standardized interface data and the adaptation data; If it is determined that the compatibility relationship between the to-be-compatible service interface data and the business system initial configuration data has been completed, then the current business system is correspondingly acquired; The current business system is embedded into the integrated business system to obtain the current integrated business system.

2. The method according to claim 1, characterized in that The business system initial configuration data at least includes system kernel data and system extension point data; The constructing a compatibility relationship between the to-be-compatible service interface data and the business system initial configuration data based on the standardized interface data includes: Based on the standardized interface data, the service interface data to be compatible is added to the system extension point data in the initial configuration of the business system to build a compatible relationship between the service interface data to be compatible and the initial configuration data of the business system, and the initial configuration data of the business system is updated.

3. The method according to claim 1, characterized in that The business system initial configuration data at least includes system kernel data, system extension point data and system adaptation layer data; The constructing a compatible relationship between the to-be-compatible service interface data and the business system initial configuration data based on the standardized interface data and the adaptation data includes: Based on the standardized interface data, the service interface data to be compatible is added to the system extension point data in the initial configuration of the business system, and the adaptation data is added to the system adaptation layer data in the initial configuration of the business system to build a compatible relationship between the service interface data to be compatible and the initial configuration data of the business system, and update the initial configuration data of the business system; wherein the adaptation data is adaptation layer data or adaptation service data.

4. The method according to claim 1, characterized in that After the step of embedding the current business system into the integrated business system to obtain the current integrated business system, the method further includes: If current user data is detected, the current user data is input into the current integrated service system for data processing to obtain a corresponding current user data processing result; A target data receiving subsystem corresponding to the current user data processing result is obtained in the current integrated service system, and the current user data processing result is sent to the target data receiving subsystem.

5. The method according to claim 4, characterized in that The target data receiving subsystem for acquiring the target data corresponding to the current user data processing result in the current integrated service system includes: The system adaptation layer data corresponding to the current service system in the current integrated service system is acquired, and the target data receiving subsystem is determined based on the system adaptation layer data.

6. The method according to claim 1, characterized in that After the step of embedding the current business system into the integrated business system to obtain the current integrated business system, the method further includes: If current user data is detected, the current user data is input into the current integrated service system for data processing to obtain a corresponding current user data processing result; A third-party system connected to the current integrated service system based on the adaptation layer communication is obtained, and the current user data processing result is sent to the third-party system.

7. The method according to claim 1, characterized in that If it is determined that the compatibility relationship between the to-be-compatible service interface data and the business system initial configuration data has been completed, then after the step of obtaining the current business system, the method further includes: If a business system calling instruction is detected, the current business system is correspondingly packaged to obtain a packaged business system, and the packaged business system is sent to a receiving system corresponding to the business system calling instruction.

8. A device for realizing multi-compatibility of a business system based on kernel standardization, characterized in that: include: A to-be-compatible service data acquisition unit, used to acquire to-be-compatible service interface data of the to-be-compatible service in response to the business system compatible instruction; wherein the business system targeted by the business system compatible instruction has a standardized kernel architecture including at least a system kernel, an extension point and an adaptation layer; A compatible service type acquisition unit, used to acquire the compatible service type corresponding to the to-be-compatible service interface data; A first compatibility building unit is used to obtain the business system initial configuration data and the standardized interface data if it is determined that the compatible service type is a newly created service compatible type, and to build a compatibility relationship between the interface data of the service to be compatible and the initial configuration data of the business system based on the standardized interface data; A second compatibility construction unit is used to obtain the business system initial configuration data, standardized interface data and adaptation data if it is determined that the compatible service type is an existing service compatible type, and to construct a compatibility relationship between the to-be-compatible service interface data and the business system initial configuration data based on the standardized interface data and the adaptation data; A current business system processing unit, configured to correspondingly acquire the current business system if it is determined that the compatibility relationship between the to-be-compatible service interface data and the business system initial configuration data has been completed; The business system embedding processing unit is used to embed the current business system into the integrated business system to obtain the current integrated business system.

9. A computer device, characterized in that: The computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the multi-compatibility implementation method of the business system based on kernel standardization as described in any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which includes program instructions. When the program instructions are executed by a processor, the method for realizing multi-compatibility of a business system based on kernel standardization according to any one of claims 1 to 7 can be realized.

Images