System calling method and device, equipment and storage medium

Abstract

The invention provides a system calling method and device, equipment and a storage medium, is applied to the technical field of computers, and is used for improving the calling efficiency between cross-server node systems in a distributed cluster system. The method is applied to a service system in a distributed cluster system comprising a called system and a service system, the called system is created based on an original application component in the service system, and the method comprises the following steps: in the service system, based on an inter-component calling mode between the application components, controlling to call the application components, generating an original calling request for the called system; based on an inter-system calling mode between the business system and the called system, converting the data format of the original calling request to obtain a target calling request corresponding to the inter-system calling mode; and sending the target calling request to a called system, so that the called system feeds back corresponding data information based on the service demand contained in the target calling function.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a system call method, apparatus, device and storage medium. Background Technology

[0002] With the continuous development and popularization of internet technology, the amount of data in cyberspace has exploded, making it increasingly difficult for traditional mainframe core system architectures to meet the demands of massive data storage and processing. Therefore, mainframe core architectures in various fields have gradually shifted to distributed cluster systems to utilize the computing resources of multiple servers to satisfy the needs of large-scale data storage and processing.

[0003] The host core system is a centralized computer architecture in which all core components are tightly integrated within a single host, and the data processed in this system is usually concentrated in local storage and can be directly accessed by the system through the bus; while the distributed cluster system is a decentralized computer architecture in which multiple independent computers are connected and collaborate through a network, and their data is distributed and stored on each node and managed through a distributed file system or database.

[0004] Due to the differences in the two system architectures, during the transition from a host core system to a distributed cluster system, some functions that could be called smoothly between components in the host core system may encounter certain problems in the distributed cluster system.

[0005] Therefore, there is an urgent need for a new system call method to improve the efficiency of calls between server nodes in a distributed cluster system. Summary of the Invention

[0006] This application provides a system call method, apparatus, device, and computer storage medium to improve the efficiency of calls between server node systems in a distributed cluster system.

[0007] In a first aspect, embodiments of this application provide a system invocation method. This method is applied to a business system within a distributed cluster system. The distributed cluster system includes a invoked system and the business system. The invoked system is created based on original application components within the business system. The invoked system and the business system are deployed on different server nodes within the distributed cluster system. The method includes: In the business system, based on the inter-component calling method between various application components, the calling application component is controlled to generate an original calling request for the called system; wherein, the calling application component is one of the application components currently included in the business system; Based on the inter-system call method between the business system and the called system, the data format of the original call request is converted to obtain the target call request corresponding to the inter-system call method. The target call request is sent to the called system, so that the called system can provide corresponding data information based on the business requirements contained in the target call request.

[0008] Optionally, in the business system, based on the inter-component calling method between various application components, the system controls the calling application component to generate an original calling request for the called system, including: Obtain the business requirements of the calling application component for the called system; the business requirements are used to describe: the functional and business requirements of the calling application component for the original application component. Based on the inter-component calling method between the calling application component and the original application component in each application component, and the business requirements, an original calling request is generated for the original application component; the calling request includes: parameter information of the original application component responding to the business requirements.

[0009] Optionally, the step of converting the data format of the original call request based on the inter-system call method between the business system and the called system to obtain the target call request corresponding to the inter-system call method includes: Based on the mapping relationship between the component call interface corresponding to the original application component and the system call interface corresponding to the called system, and combined with the inter-system call method between the business system and the called system, the data format of the original call request is converted to obtain the target call request corresponding to the inter-system call method.

[0010] Optionally, after sending the target invocation request to the invoked system, the method further includes: Receive data feedback results from the called system; wherein, the data feedback results include: data information determined based on the business requirements of the called application component; The data format of the data feedback result is converted to obtain the target feedback result corresponding to the called application component; The target feedback result is sent to the calling application component.

[0011] Optionally, the called system is created in the following way: Based on the business system prior to the creation of the called system, obtain the code file corresponding to the original application component; the code file is used to describe the processing function of the original application component in the business system; The code file is converted to a different language to create a called system that retains the processing functions of the original application components; Based on the called system and the inter-system calling method, a system call interface is generated for use by the business systems included in the distributed cluster system. The system call interface is used to complete the transmission of calling instructions between the called system and the business system.

[0012] Optionally, the called system is built using a different coding language than the business system, and the business system accesses a different database than the called system.

[0013] Secondly, embodiments of this application provide a system invocation device applied to a business system in a distributed cluster system. The distributed cluster system includes a invoked system and the business system. The invoked system is created based on the original application components of the business system. The invoked system and the business system are deployed on different server nodes in the distributed cluster system. The device includes: The generation module is used in the business system to control the calling application component based on the inter-component calling method between various application components, and generate an original calling request for the called system; wherein, the calling application component is one of the application components currently included in the business system; The conversion module is used to convert the data format of the original call request based on the inter-system call method between the business system and the called system, so as to obtain the target call request corresponding to the inter-system call method. The transmission module is used to send the target call request to the called system, so that the called system can provide corresponding data information based on the business requirements contained in the target call request.

[0014] Optionally, the generation module is used in the business system to control the calling application component and generate the original call request for the called system based on the inter-component calling method between various application components. Specifically, it is used for: Obtain the business requirements of the calling application component for the called system; the business requirements are used to describe: the functional and business requirements of the calling application component for the original application component. Based on the inter-component calling method between the calling application component and the original application component in each application component, and the business requirements, an original calling request is generated for the original application component; the calling request includes: parameter information of the original application component responding to the business requirements.

[0015] Optionally, when the conversion module is used to convert the data format of the original call request based on the inter-system call method between the business system and the called system to obtain the target call request corresponding to the inter-system call method, it is specifically used for: Based on the mapping relationship between the component call interface corresponding to the original application component and the system call interface corresponding to the called system, and combined with the inter-system call method between the business system and the called system, the data format of the original call request is converted to obtain the target call request corresponding to the inter-system call method.

[0016] Optionally, after the transmission module sends the target call request to the called system, the processing module is further configured to: Receive data feedback results from the called system; wherein, the data feedback results include: data information determined based on the business requirements of the called application component; The data format of the data feedback result is converted to obtain the target feedback result corresponding to the called application component; The target feedback result is sent to the calling application component.

[0017] Optionally, when the processing module is used to create the called system, it is specifically used for: Based on the business system prior to the creation of the called system, obtain the code file corresponding to the original application component; the code file is used to describe the processing function of the original application component in the business system; The code file is converted to a different language to create a called system that retains the processing functions of the original application components; Based on the called system and the inter-system calling method, a system call interface is generated for use by the business systems included in the distributed cluster system. The system call interface is used to complete the transmission of calling instructions between the called system and the business system.

[0018] Optionally, the called system is built using a different coding language than the business system, and the business system accesses a different database than the called system.

[0019] Thirdly, embodiments of this application provide an electronic device, including: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the at least one processor, by executing the instructions stored in the memory, causes the at least one processor to perform the method described in the first aspect or any optional embodiment of the first aspect.

[0020] Fourthly, embodiments of this application provide a computer-readable storage medium for storing instructions that, when executed, cause a method as described in the first aspect or any optional implementation thereof to be implemented.

[0021] Fifthly, embodiments of this application provide a computer program product containing instructions, wherein the computer program product stores instructions that, when run on a computer, cause the computer to perform the method described in the first aspect or any optional implementation thereof.

[0022] The beneficial effects of this application are as follows: In this solution, when application components in the business system of the distributed cluster system call the called system created based on the original application components, there is no need to make additional adaptive modifications to make the application components generate cross-system call requests. Instead, the original calling methods of each application component for the original application component are retained. In addition, the conversion process from the original call request to the target call request is performed in the business system. This can avoid the development costs required to modify each application component in the business system, and also enable the split systems to still complete the inter-system call process smoothly. Attached Figure Description

[0023] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1 This is a schematic diagram illustrating possible application scenarios provided for embodiments of this application; Figure 2A A schematic diagram illustrating the principle of the calling process between application components provided in the embodiments of this application; Figure 2B This is a schematic diagram illustrating the principle of the system call process under related technologies; Figure 3 This application provides a schematic diagram of the application scenario structure of a system call method. Figure 4 A flowchart illustrating a system call method provided in an embodiment of this application; Figure 5 A flowchart illustrating a method for generating an original call request, provided in an embodiment of this application; Figure 6 A schematic diagram illustrating the principle of a system call method provided in an embodiment of this application; Figure 7 This is a schematic diagram of the structure of a system call device provided in an embodiment of this application; Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0025] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application. Unless otherwise specified, the embodiments and features in the embodiments of this application can be arbitrarily combined with each other. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than that shown here.

[0026] The terms "first" and "second" in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the term "comprising" and any variations thereof are intended to cover non-exclusive protection. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices. The term "multiple" in this application can mean at least two, for example, two, three, or more, and the embodiments of this application do not impose limitations.

[0027] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of this application, including various details to aid understanding. These embodiments should be considered merely exemplary. Therefore, those skilled in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope of this application. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description. It should be noted that in the embodiments of this application, certain existing industry solutions such as software, components, and models may be mentioned. These should be considered exemplary, intended only to illustrate the feasibility of implementing the technical solutions of this application, and do not imply that the applicant has already used or necessarily used such solutions.

[0028] The acquisition, transmission, storage, and use of data in this application all comply with the requirements of relevant national laws and regulations.

[0029] The following explanations of some terms used in the embodiments of this application are provided to facilitate understanding by those skilled in the art.

[0030] (1) Host core system: A host core system is a centralized computer architecture in which all core components are tightly integrated within a single host, and the data processed in this system is usually located in local memory and can be directly accessed by the system via a bus.

[0031] (2) Distributed cluster system: A distributed cluster system is a decentralized computer architecture in which multiple independent computers are connected and collaborate through a network, and their data is distributed and stored on each node and managed through a distributed file system or database.

[0032] (3) Application components

[0033] Application components are defined software units that perform one or more specific tasks within a system. They are the basic modules that constitute the system's functionality, and their core value lies in achieving system maintainability, scalability, and reusability through clear division of responsibilities. In this application embodiment, taking a banking system as an example, application components can be divided according to the different banking businesses they are responsible for: deposit application components, employee management application components, etc.

[0034] The application areas of the system call method provided in the embodiments of this application will be briefly introduced below.

[0035] With the continuous development and popularization of internet technology, the amount of data in cyberspace has exploded, making it increasingly difficult for traditional mainframe core system architectures to meet the demands of massive data storage and processing. Therefore, mainframe core architectures in various fields have gradually shifted to distributed cluster systems to utilize the computing resources of multiple servers to satisfy the needs of large-scale data storage and processing.

[0036] The host core system is a centralized computer architecture in which all core components are tightly integrated within a single host, and the data processed in this system is usually concentrated in local storage and can be directly accessed by the system through the bus; while the distributed cluster system is a decentralized computer architecture in which multiple independent computers are connected and collaborate through a network, and their data is distributed and stored on each node and managed through a distributed file system or database.

[0037] Due to the differences in the two system architectures, during the transition from a host core system to a distributed cluster system, some functions that could be called smoothly between components in the host core system may encounter certain problems in the distributed cluster system.

[0038] Taking the banking system as an example, during the mainframe core system era, a business system called the Inter-Bank (IB) transaction system was an application component in the mainframe core system. Since multiple application components were located in the same mainframe core system and shared a database, other application components in the mainframe core system could directly call the relevant programs of the IB transaction system, access the contents of its corresponding database, and realize related data interaction operations.

[0039] However, during the transformation of the banking system from a mainframe core system to a distributed cluster system, the IB transaction business system, with its unique advantages, was separated from the mainframe core system and independently set up as a new system occupying a dedicated server node in the distributed cluster system. At this point, other application components remaining in the mainframe core system need to communicate across nodes when calling the IB transaction business system. To achieve this cross-system call, the application components remaining in the mainframe core system need to be adapted to ensure that each application component can generate the corresponding cross-system call instructions to complete the call to the new IB system. This communication process incurs significant adaptation costs, impacting the efficiency of communication between the two systems.

[0040] In view of this, embodiments of this application provide a system call method, which is applied to a business system in a distributed cluster server. The distributed cluster system includes a business system and a called system, wherein the called system is created based on the original application components in the business system, and the called system and the business system are deployed on different server nodes in the distributed cluster system respectively.

[0041] Thus, in this distributed cluster system, when any application component in the business system needs to make a call to the called system, it can perform the following operation: In the business system, based on the inter-component calling methods between various application components, the system controls the calling application component to generate the original call request for the called system. The calling application component is one of the application components currently included in the business system. Thus, even if the original application component in the business system has been split into a new called system, other application components in the business system still do not need to generate inter-system call requests for the called system; instead, they only need to generate the original component-to-component call request.

[0042] Next, based on the inter-system call method between the business system and the called system, the data format of the original call request is converted to obtain the target call request corresponding to the inter-system call method. In this way, the business system is responsible for converting the data format of the original call requests generated by its various application components, avoiding the need for each application component to make corresponding adaptive modifications for cross-system calls, and reducing the development cost of converting from the host core system to the distributed cluster system.

[0043] Finally, after the business system sends the target call request to the called system, the called system can respond with the corresponding data information based on the business requirements contained in the call instruction, thereby completing the call operation of the application component in the business system on the called system.

[0044] In the method provided in the embodiments of this application, when application components in the business system of the distributed cluster system call the called system created based on the original application components, there is no need to make additional adaptive modifications to enable the application components to generate cross-system call requests. Instead, the original calling methods of each application component for the original application component are retained. In addition, the conversion process from the original call request to the target call request is performed in the business system. This can avoid the development costs required to modify each application component in the business system, and also enable the split systems to still complete the inter-system call process smoothly.

[0045] After introducing the main inventive concept of the embodiments of this application, the specific implementation of the data synchronization method proposed in the embodiments of this application will be described below through some specific embodiments and accompanying drawings.

[0046] The following is a brief introduction to the application scenarios to which the technical solutions of the embodiments of this application are applicable. It should be noted that the application scenarios described below are only for illustrating the embodiments of this application and are not intended to limit the scope. In specific implementation, the technical solutions provided by the embodiments of this application can be flexibly applied according to actual needs.

[0047] See Figure 1 This is a schematic diagram of a possible application scenario provided by an embodiment of this application. In this scenario, a terminal device 101 and a server 102 may be included.

[0048] Terminal device 101 can be a mobile phone, tablet computer (PAD), personal computer (PC), wearable device, vehicle terminal, etc. Server 102 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery network (CDN), and big data and artificial intelligence platforms.

[0049] Terminal device 101 and server 102 can communicate directly or indirectly through one or more communication networks 103. The communication network 103 can be a wired network or a wireless network. For example, the wireless network can be a mobile cellular network or a Wireless-Fidelity (WIFI) network. Of course, it can also be other possible networks, and this embodiment of the invention does not limit them.

[0050] It should be noted that the system call method in this embodiment can be executed by a computer device, which can be terminal device 101 or server 102. For example, when the system call method is performed by server 102, the server can control the calling application component to generate an original call request for the called system based on the inter-component calling method between application components, and then convert the original call request into a target call request based on the inter-system calling method, so as to send the target call request to the called system, thereby completing the calling operation of the calling application component for the called system.

[0051] It should be noted that, Figure 1The examples shown are merely illustrative; in reality, the number of terminal devices and servers, as well as the communication methods, are not limited and are not specifically restricted in the embodiments of this application.

[0052] The system call method provided by the exemplary embodiments of this application will be described below with reference to the accompanying drawings and the application scenarios described above. It should be noted that the application scenarios described above are only shown to facilitate understanding of the spirit and principles of this application, and the embodiments of this application are not limited in any way in this respect.

[0053] Before introducing the system call method proposed in the embodiments of this application, it is necessary to first introduce the specific scenario in which the system call method is applied.

[0054] like Figure 2A As shown, suppose there is a host core system, which is a business system containing application component 1, application component 2, application component 3 and application component 4. During the host core system period, since each application component is deployed on the server where the host core system is located, the mutual calls between components can be carried out smoothly.

[0055] When the host core system needs to be converted into a distributed cluster system based on the needs of actual applications, and one of the application components (e.g., application component 4) has relatively independent advantages and is to be separated from the business system as an independent new system, the application components 1, 2 and 3 that originally existed in the business system can no longer use the original inter-component calling method within the system to call application component 4.

[0056] And such Figure 2B As shown, the common approach in related technologies is to modify the code of application components 1, 2, and 3 accordingly, transforming their respective calling methods from those of the original application components to those of the new system. This method requires significant development costs for creating a distributed cluster system, as each application component that will call the new system needs corresponding code modifications.

[0057] Therefore, this application proposes a new system call method, the application scenario of which is as described above: such as Figure 3 As shown, in a distributed cluster system, there are business systems and called systems. The called system is created based on an original application component of the business system. The business system contains application component 1, application component 2 and application component 3. All three application components need to call the called system.

[0058] Therefore, in this application scenario, the specific implementation method of the business invocation method provided in this application embodiment is as follows: Please refer to Figure 4 This is a flowchart illustrating a system call method provided in an embodiment of this application. The method is applied to a business system within a distributed cluster system, and its specific execution entity can be the aforementioned... Figure 1 Any computer device represented in the document (such as a client device or a server device), such as Figure 4 As shown, the specific implementation steps of this method are as follows: S401, In the business system, based on the inter-component calling method between various application components, control the calling application component to generate the original calling request for the called system; wherein, the calling application component is one of the application components currently included in the business system.

[0059] Having clarified the application scenarios of the system call method provided in this application, it can be determined that: for a business system, it contains at least one application component. These application components typically need to perform different functions within the business system, and in some cases, they also need to call the called system. Taking a banking system as an example, the application components included in the business system may include: loan application components, deposit application components, user platform application components, etc., each with its own specific function. During operation, some application components need to call the called system. The original application component corresponding to the called system can be an IB application component, which, after being split, becomes a new IB system deployed in a distributed cluster system.

[0060] In this way, when any application component in the business system needs to call the called system, it can be used as the calling application component, and then the original call request for the called system can be generated in the way of inter-component calling between application components.

[0061] In one possible implementation, the original call request can be generated in the following manner: See Figure 5 This is a flowchart illustrating a method for generating an original call request according to an embodiment of this application. Figure 5 As shown, the specific implementation steps of this method are as follows: S501: Obtain the business requirements of the calling application component for the called system; wherein, the business requirements are used to describe: the requirements information of the calling application component for the functions and services provided by the original application component.

[0062] For calling application components, the triggering condition is that the calling application component has certain requirements for the functions and business provided by the called system.

[0063] Therefore, when generating the original call request, the first step is to obtain the business requirements of the calling application component for the called system. These business requirements may include: extracting some data from the called system, updating some data contained in the called system, or requesting the called system to assist in collecting certain statistical information, etc. This application does not impose any restrictions on these requirements.

[0064] S502: Based on the inter-component calling method between the calling application component and the original application component in each application component, and the obtained business requirements, generate the original calling request for the original application component; wherein, the original calling request includes: parameter information of the calling original application component in response to the business requirements.

[0065] In this process, whenever the calling component needs to make a call to the called system (i.e. the original application component), it can adopt the calling method between the two when the original application component was not split, and generate the corresponding original call request, which contains the parameter information required for the original application component to respond to business needs.

[0066] In this way, for each application component in the business system, each time a call operation is performed on the called system, only the original call request between the two application components before splitting can be generated, without modifying the application components in the business system to generate the corresponding inter-system call request. This avoids the process of modifying the application components and improves the efficiency of creating a distributed cluster system.

[0067] After generating the original call request, the server can continue to perform the following operations: S402, based on the inter-system call method between the business system and the called system, converts the data format of the original call request to obtain the target call request corresponding to the inter-system call method.

[0068] The original call request is generated using the inter-component call method. However, for the called system, which has become an independent new system, such an original call request cannot successfully call the called system to perform the corresponding operation.

[0069] Therefore, for the business system, after the control calling system generates the original call request, it is also necessary to perform corresponding conversion processing on the original call request based on the inter-system calling method between the business system and the called system, so as to ensure that the target call request obtained after conversion can successfully realize the call operation for the called system.

[0070] In one possible implementation, the process of transforming the original invocation request to obtain the corresponding target invocation request can be performed as follows: Specifically, the business system can convert the data format of the original call request based on the mapping relationship between the component call interface corresponding to the original application component and the system call interface corresponding to the called system, combined with the inter-system call method between the business system and the called system, to obtain the target call request corresponding to the inter-system call method.

[0071] For a business system, once the original call request is determined, it can perform corresponding transformation processing on the original call request to generate the target call request. In this process, it can utilize the inter-system call method between the business system and the called system, as well as the mapping relationship between the component call interfaces of the original application components and the system call interfaces of the called system, to convert the data format of the original call request into the corresponding data format of the target call request. This allows the target call request to be successfully received by the called system, thereby completing the corresponding call operation.

[0072] For example, such as Figure 6 As shown, in a business system, when converting raw call requests generated by different application components, a target encapsulation function can be set up to handle this conversion process. This target encapsulation function can be set to the same program name as the original application component. This allows other application components to assume it's the original application component based on this program name, generate raw call requests, and send these requests to the target encapsulation function. The target encapsulation function, based on the mapping relationship between the component call interface of the original application component and the system call interface of the called system, and considering the inter-system call method between the business system and the called system, converts the data format of the raw call request. While ensuring the transmitted content remains unchanged, it transforms the raw call request corresponding to the original inter-component call method into the target call request corresponding to the inter-system call method.

[0073] Thus, after receiving the target call request, the server can continue to perform the following operations: S403, the target call request is sent to the called system so that the called system can provide corresponding data information based on the business requirements contained in the target call request.

[0074] Once the target call request has been successfully retrieved, it needs to be sent to the called system.

[0075] For the called system, an external calling command interface is provided during its creation process. Through this interface, the called system can receive calling commands from other systems and then complete the corresponding operations. In the system calling method provided in this application embodiment, after receiving the target calling request, the called system can feed back the corresponding data information to the business system based on the business requirements contained in the target calling request.

[0076] In this way, the business system can complete the operation of calling the application component to call the called system.

[0077] In the system call method provided in this application embodiment, when the application components of the business system in the distributed cluster system call the called system created based on the original application components, there is no need to make additional adaptive modifications to enable the application components to generate cross-system call requests. Instead, the original calling methods of each application component for the original application component are retained. In addition, the conversion process from the original call request to the target call request is performed in the business system. This can avoid the development costs required to modify each application component in the business system, and also enable the split systems to still complete the inter-system call process smoothly.

[0078] In one possible implementation, after the business system sends the target call request to the called system, the business system may continue to perform the following operations: Receive data feedback results from the called system; wherein, the data feedback results include: data information determined based on the business requirements of the called application component.

[0079] After receiving the target call request, the called system will perform corresponding operations based on the business requirements contained therein, thereby obtaining the corresponding data feedback result. This data feedback result then needs to be fed back to the business system for use by the calling application components.

[0080] Therefore, the business system will receive data feedback results from the called system.

[0081] After receiving the data feedback result, the business system can also convert the data format of the data feedback result to obtain the target feedback result corresponding to the called application component, thereby ensuring that the called application component obtains the target feedback result that it can directly process.

[0082] Finally, the business system can send the target feedback result to the calling application component, thereby achieving a closed loop in the system call process.

[0083] In this way, the data feedback results from the called system can also be processed by the business system through data format conversion before being sent to the calling application component. This ensures that the calling application component can directly process the target feedback results, avoiding additional data processing work by the calling application component and ensuring the stable operation of the system call process.

[0084] Furthermore, as mentioned above, when the business system encapsulates a target encapsulation function, the data format conversion operation for performing data feedback results can also be performed by the target encapsulation function.

[0085] The above describes the operations performed by the business system during the system call process. However, in this application scenario, a prerequisite for this is that the called system is a new system created based on the original application components. Therefore, the creation of the called system can be done in the following way: Based on the business system prior to the creation of the called system, obtain the code file corresponding to the original application component; the code file describes the processing function of the original application component in the business system; then, perform code language conversion processing on the code file to create the called system that retains the processing function of the original application component.

[0086] In this process, the creation of the called system mainly adopted the code files of the original application components, which were adapted to include the various functions of the original application components, so as to ensure that the new called system can accurately complete the relevant content in the original application components.

[0087] For example, the various IB application components in the banking system have relatively independent functions and data. During the distributed transformation of the original host core system, the distributed deployment of servers and data will be completed. Therefore, the advantage of the relative independence of IB application components makes it easier to maintain a new IB system, and it can be upgraded and changed independently, reducing the impact on business systems.

[0088] Optionally, the created called system can be built using a different coding language than the business system, and the databases accessed by the business system and the called system can be different.

[0089] For example, the creation of a business system can be accomplished using a coding language or a corresponding operating system. For instance, the development language could be COBOL, and the database could be DB2. As for the called system, its corresponding development language could be Java, and the database used could be GoldenDB, etc.

[0090] Based on the called system and the inter-system calling method, a system call interface is generated for use by the business systems included in the distributed cluster system. The system call interface is used to complete the transmission of calling instructions between the called system and the business system.

[0091] In the process of creating the called system, in addition to creating the internal functions of the system, it is also necessary to create a system call interface that can be called by other systems.

[0092] For example, in the host core system phase, the application component CS001 program is assigned to the input interface of the original application component IB001 (i.e., generating a raw call request to invoke the original application component) to call the original application component's program IB001. In the distributed cluster system phase, the application component CS001 program is still assigned to the input interface of the original application component IB001. At this point, the target encapsulation function in the business system needs to complete the mapping relationship between the input interface of the original IB001 and the standard service interface (such as NEWIB001) corresponding to the system call interface published by the called system, then complete the transformation processing of the raw call request, and finally send it to the called system.

[0093] Based on the same inventive concept, embodiments of this application also provide a system call device.

[0094] See Figure 7 This is a schematic diagram of the structure of a system call device provided in an embodiment of this application. The device may be the aforementioned server or a chip or integrated circuit in the device. The device includes modules / units / technical means for executing the method executed by the server in the above method embodiment.

[0095] For example, the device 700 includes: The generation module 701 is used to control the calling application component and generate an original call request for the called system based on the inter-component calling method between various application components in the business system; wherein, the calling application component is one of the application components currently included in the business system; The conversion module 702 is used to convert the data format of the original call request based on the inter-system call method between the business system and the called system, so as to obtain the target call request corresponding to the inter-system call method. The transmission module 703 is used to send the target call request to the called system, so that the called system can provide corresponding data information based on the business requirements contained in the target call request.

[0096] Optionally, the generation module 701 is used in the business system to control the calling application component and generate the original call request for the called system based on the inter-component calling method between various application components. Specifically, it is used for: Obtain the business requirements of the calling application component for the called system; the business requirements are used to describe: the functional and business requirements of the calling application component for the original application component. Based on the inter-component calling method between the calling application component and the original application component in each application component, and the business requirements, an original calling request is generated for the original application component; the calling request includes: parameter information of the original application component responding to the business requirements.

[0097] Optionally, the conversion module 702 is used to convert the data format of the original call request based on the inter-system call method between the business system and the called system, and to obtain the target call request corresponding to the inter-system call method. Specifically, it is used for: Based on the mapping relationship between the component call interface corresponding to the original application component and the system call interface corresponding to the called system, and combined with the inter-system call method between the business system and the called system, the data format of the original call request is converted to obtain the target call request corresponding to the inter-system call method.

[0098] Optionally, after the transmission module 703 sends the target call request to the called system, the processing module is further configured to: Receive data feedback results from the called system; wherein, the data feedback results include: data information determined based on the business requirements of the called application component; The data format of the data feedback result is converted to obtain the target feedback result corresponding to the called application component; The target feedback result is sent to the calling application component.

[0099] Optionally, when the processing module 703 creates the called system, it is specifically used for: Based on the business system prior to the creation of the called system, obtain the code file corresponding to the original application component; the code file is used to describe the processing function of the original application component in the business system; The code file is converted to a different language to create a called system that retains the processing functions of the original application components; Based on the called system and the inter-system calling method, a system call interface is generated for use by the business systems included in the distributed cluster system. The system call interface is used to complete the transmission of calling instructions between the called system and the business system.

[0100] Optionally, the called system is built using a different coding language than the business system, and the business system accesses a different database than the called system.

[0101] As one example, Figure 7 The device described can be used to perform Figure 4 The method described in the illustrated embodiment is therefore relevant to the functions that each functional module of the device can achieve. Figure 4 The description of the embodiments shown will not be repeated here.

[0102] It should be noted that although several modules or sub-modules of the device have been mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to embodiments of the present invention, the features and functions of two or more units described above can be embodied in a single module. Conversely, the features and functions of a module described above can be further divided and embodied by multiple modules.

[0103] As one possible product form of the aforementioned device, see [link to product description]. Figure 8 This application also provides an electronic device 800, comprising: At least one processor 801; and a communication interface 803 communicatively connected to the at least one processor 801; the at least one processor 801 causes the electronic device 800 to execute the method steps performed by any device in the above method embodiments through the communication interface 803 by executing instructions stored in the memory 802.

[0104] Optionally, the memory 802 is located outside the electronic device 800.

[0105] Optionally, the electronic device 800 includes the memory 802, which is connected to the at least one processor 801, and stores instructions executable by the at least one processor 801. (Appendix) Figure 8 The dashed line indicates that memory 802 is optional for electronic device 800.

[0106] The processor 801 and the memory 802 can be coupled through an interface circuit or integrated together; no restriction is imposed here.

[0107] This application embodiment does not limit the specific connection medium between the processor 801, memory 802, and communication interface 803. This application embodiment... Figure 8 The processor 801, memory 802, and communication interface 803 are connected via a bus 804. Figure 8 The connections between other components are shown in bold and are for illustrative purposes only, not as limiting information. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 8 The text uses only a single thick line to represent a bus, but this does not imply that there is only one bus or one type of bus. It should be understood that the processor mentioned in the embodiments of this application can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor, implemented by reading software code stored in memory.

[0108] For example, the processor can be a Central Processing Unit (CPU), or 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. A general-purpose processor can be a microprocessor or any conventional processor.

[0109] It should be understood that the memory mentioned in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate Synchronous DRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct RAM (DR RAM).

[0110] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0111] It should be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

[0112] As another possible product form, embodiments of this application also provide a computer-readable storage medium for storing instructions that, when executed, cause a computer to perform the method steps performed by any of the devices in the above method examples.

[0113] As another possible product form, this application embodiment also provides a computer program product containing instructions, wherein the computer program product stores instructions that, when run on a computer, cause the computer to execute the method steps performed by any device in the above method embodiments.

[0114] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0115] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0116] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0117] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0118] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A system call method, characterized in that, A business system applied in a distributed cluster system, wherein the distributed cluster system includes a called system and the business system, the called system is created based on the original application components of the business system, and the called system and the business system are deployed on different server nodes in the distributed cluster system, the method comprising: In the business system, based on the inter-component calling method between various application components, the calling application component is controlled to generate an original calling request for the called system; wherein, the calling application component is one of the application components currently included in the business system; Based on the inter-system call method between the business system and the called system, the data format of the original call request is converted to obtain the target call request corresponding to the inter-system call method. The target call request is sent to the called system, so that the called system can provide corresponding data information based on the business requirements contained in the target call function.

2. The method as described in claim 1, characterized in that, In the aforementioned business system, based on the inter-component calling method between various application components, the system controls the calling application components to generate an original calling request for the called system, including: Obtain the business requirements of the calling application component for the called system; the business requirements are used to describe: the functional and business requirements of the calling application component for the original application component. Based on the inter-component calling method between the calling application component and the original application component in each application component, and the business requirements, an original calling request is generated for the original application component; the calling request includes: parameter information of the original application component responding to the business requirements.

3. The method as described in claim 1, characterized in that, The step of converting the data format of the original call request based on the inter-system call method between the business system and the called system to obtain the target call request corresponding to the inter-system call method includes: Based on the mapping relationship between the component call interface corresponding to the original application component and the system call interface corresponding to the called system, and combined with the inter-system call method between the business system and the called system, the data format of the original call request is converted to obtain the target call request corresponding to the inter-system call method.

4. The method as described in claim 3, characterized in that, After sending the target invocation request to the invoked system, the method further includes: Receive data feedback results from the called system; wherein, the data feedback results include: data information determined based on the business requirements of the called application component; The data format of the data feedback result is converted to obtain the target feedback result corresponding to the called application component; The target feedback result is sent to the calling application component.

5. The method according to any one of claims 1-4, characterized in that, The called system is created in the following way: Based on the business system prior to the creation of the called system, obtain the code file corresponding to the original application component; the code file is used to describe the processing function of the original application component in the business system; The code file is converted to a different language to create a called system that retains the processing functions of the original application components; Based on the called system and the inter-system calling method, a system call interface is generated for use by the business systems included in the distributed cluster system. The system call interface is used to complete the transmission of calling instructions between the called system and the business system.

6. The method as described in claim 5, characterized in that, The called system is built using a different coding language than the business system, and the business system accesses a different database than the called system.

7. A system call device, characterized in that, A business system applied in a distributed cluster system, wherein the distributed cluster system includes a called system and the business system, the called system is created based on the original application components of the business system, and the called system and the business system are deployed on different server nodes in the distributed cluster system, the device comprising: The generation module is used in the business system to control the calling application component based on the inter-component calling method between various application components, and generate an original calling request for the called system; wherein, the calling application component is one of the application components currently included in the business system; The conversion module is used to convert the data format of the original call request based on the inter-system call method between the business system and the called system, so as to obtain the target call request corresponding to the inter-system call method. The transmission module is used to send the target call request to the called system, so that the called system can provide corresponding data information based on the business requirements contained in the target call request.

8. The apparatus as claimed in claim 7, characterized in that, The generation module is used in the business system to control the calling application component and generate the original call request for the called system based on the inter-component calling method between various application components. Specifically, it is used for: Obtain the business requirements of the calling application component for the called system; the business requirements are used to describe: the functional and business requirements of the calling application component for the original application component. Based on the inter-component calling method between the calling application component and the original application component in each application component, and the business requirements, the original calling request for the original application component is generated; The call request includes: parameter information that the original application component responds to in response to the business requirement.

9. The apparatus as claimed in claim 7, characterized in that, The conversion module is used to convert the data format of the original call request based on the inter-system call method between the business system and the called system, and to obtain the target call request corresponding to the inter-system call method. Specifically, it is used for: Based on the mapping relationship between the component call interface corresponding to the original application component and the system call interface corresponding to the called system, and combined with the inter-system call method between the business system and the called system, the data format of the original call request is converted to obtain the target call request corresponding to the inter-system call method.

10. The apparatus as claimed in claim 9, characterized in that, After the transmission module sends the target call request to the called system, the processing module is further configured to: Receive data feedback results from the called system; wherein, the data feedback results include: data information determined based on the business requirements of the called application component; The data format of the data feedback result is converted to obtain the target feedback result corresponding to the called application component; The target feedback result is sent to the calling application component.

11. The apparatus according to any one of claims 7-9, characterized in that, The processing module is used to create the called system, specifically for: Based on the business system prior to the creation of the called system, obtain the code file corresponding to the original application component; the code file is used to describe the processing function of the original application component in the business system; The code file is converted to a different language to create a called system that retains the processing functions of the original application components; Based on the called system and the inter-system calling method, a system call interface is generated for use by the business systems included in the distributed cluster system. The system call interface is used to complete the transmission of calling instructions between the called system and the business system.

12. The apparatus as claimed in claim 11, characterized in that, The called system is built using a different coding language than the business system, and the business system accesses a different database than the called system.

13. An electronic device, characterized in that, include: At least one processor; and a memory communicatively connected to the at least one processor; The memory stores instructions executable by the at least one processor, which executes the instructions stored in the memory to perform the method as described in any one of claims 1-6.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store instructions that, when executed, cause the method as described in any one of claims 1-6 to be implemented.

15. A computer program product containing instructions, characterized in that, The computer program product stores instructions that, when run on a computer, cause the computer to perform the method as described in any one of claims 1-6.

Images