Event handling method, device, terminal device and storage medium for a client

Abstract

The present application provides a method, apparatus, terminal device, and storage medium for event processing of a client, which can be applied to a smart hospital system. The terminal device includes a client of a first system. The method includes: listening for a trigger event of the client of the first system; when a trigger event of the client of the first system accessing a target service of the client of the second system is listened for, determining a target function included in the function library of the client of the second system according to the trigger event and the data corresponding to the trigger event, where the target function is a function for implementing the function of the target service; and calling the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event. By using the present application, the docking process between different service systems can be simplified, and the docking process is easier to implement.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular, to a method, device, terminal device, and storage medium for event processing of a client. Background Art

[0002] At present, there are various application program architectures in business systems. For example, the clients of traditional medical information systems such as Hospital Information System (HIS), Laboratory Information Management System (LIS), and Picture Archiving and Communication Systems (PACS) are developed in multiple languages. There are systems with a B / S architecture developed using HTML language, and there are also systems with a C / S architecture developed using languages such as C#, Power Builder, Visual Basic, Delphi, C++, and Android. In order to empower these business systems, it is often necessary to connect to different business systems. For example, for medical systems, it is necessary to connect third-party Artificial Intelligence (AI) or Internet medical systems with these traditional medical information systems. Here, taking third-party AI or Internet medical systems and these traditional medical information systems as an example, the method of connecting different business systems will be described.

[0003] Currently, both third-party AI or Internet medical systems and traditional medical information systems are connected through interfaces. Third-party AI or Internet medical systems provide detailed product design documents and complex interface documents, and return Json data in Representational State Transfer (RESTful) interfaces. Traditional medical information system manufacturers develop pages according to the documents to implement complex business functions. However, the client functions of third-party AI or Internet medical systems are complex. This method of connection requires developers and testers of traditional medical information system manufacturers to deeply understand the business of third-party AI or Internet medical systems before development and testing, which takes a long time and is prone to errors. Moreover, each traditional medical information system manufacturer has to repeat this process, which is extremely time-consuming and not easy to promote the implementation of third-party AI or Internet medical systems. It can be seen that the above process for connecting different business systems is relatively cumbersome and difficult to implement. Summary of the Invention

[0004] The embodiments of the present application provide a method, device, terminal device, and storage medium for event processing of a client. By introducing the function library of the client of the second system into the client of the first system, the docking of different business systems can be realized, which can simplify the docking process between different business systems and is easier to implement.

[0005] In a first aspect, the embodiments of the present application provide a method for event processing of a client, which is applied to a terminal device. The terminal device includes a client of a first system. The method includes:

[0006] Listening for trigger events of the client of the first system;

[0007] When a trigger event for accessing the target service of the client of the second system by the client of the first system is monitored, determine the target function included in the function library of the client of the second system according to the trigger event and the data corresponding to the trigger event. The target function is a function for implementing the function of the target service;

[0008] Call the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event.

[0009] Optionally, the client of the first system includes the function library. The step of calling the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event includes:

[0010] Call the target function included in the function library through the client of the first system to implement the function of the target service according to the trigger event and the data corresponding to the trigger event.

[0011] Optionally, before determining the target function included in the function library of the client of the second system according to the trigger event and the data corresponding to the trigger event when a trigger event for accessing the target service of the client of the second system by the client of the first system is monitored, the method further includes:

[0012] Send a function library acquisition request to the server of the second system;

[0013] Receive the function library of the second system returned by the server of the second system in response to the function library acquisition request, and embed the function library in the client of the first system.

[0014] Optionally, the step of calling the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event includes:

[0015] Invoke the target function included in the function library through the built-in browser embedded in the client of the first system, so as to implement the function of the target service according to the trigger event and the data corresponding to the trigger event.

[0016] Optionally, using the target function included in the function library by the built-in browser embedded in the client of the first system to implement the function of the target service according to the trigger event and the data corresponding to the trigger event includes:

[0017] Transmit the trigger event and the data corresponding to the trigger event from the client of the first system to the built-in browser embedded in the client of the first system;

[0018] Invoke the target function included in the function library through the built-in browser to implement the function of the target service according to the trigger event and the data corresponding to the trigger event.

[0019] Optionally, transmitting the trigger event and the data corresponding to the trigger event from the client of the first system to the built-in browser embedded in the client of the first system includes:

[0020] Invoke the data interaction function of the built-in browser embedded in the client of the first system through the client of the first system to transmit the trigger event and the data corresponding to the trigger event to the built-in browser.

[0021] Optionally, using the target function included in the function library by the built-in browser to implement the function of the target service according to the trigger event and the data corresponding to the trigger event includes:

[0022] Invoke the target function included in the function library through the built-in browser to execute the business logic corresponding to the target service according to the trigger event and the data corresponding to the trigger event, and obtain an execution result.

[0023] In a second aspect, an embodiment of the present application provides an event processing device for a client, which is applied to a terminal device. The terminal device includes a client of a first system, and the device includes:

[0024] A monitoring module, configured to monitor trigger events of the client of the first system;

[0025] A determination module, configured to, when the monitoring module monitors a trigger event of the client of the first system accessing the target service of the client of the second system, determine the target function included in the function library of the client of the second system according to the trigger event and the data corresponding to the trigger event, where the target function is a function for implementing the function of the target service;

[0026] A calling module, configured to call the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event.

[0027] In a third aspect, an embodiment of the present application provides a terminal device, including a processor and a memory, the processor and the memory are connected to each other. Wherein, the memory is used to store a computer program, the computer program includes program instructions, and the processor is configured to call the program instructions to execute the method described in the first aspect.

[0028] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the method described in the first aspect.

[0029] In summary, when the terminal device monitors a trigger event of the target service of the client of the second system accessed by the client of the first system, it can determine the target function included in the function library of the client of the second system according to the trigger event and the data corresponding to the trigger event, and call the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event. The present application realizes the docking of different service systems by introducing the function library of the client of the second system into the client of the first system. Compared with the prior art that realizes the docking of different service systems through a cumbersome docking process, the present application can simplify the docking process between different service systems, and the docking process is easier to implement. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the following drawings are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained according to these drawings.

[0031] Figure 1A is a schematic flowchart of a method for processing events of a client provided by an embodiment of the present application;

[0032] Figure 1B is a schematic diagram of a function call process provided by an embodiment of the present application;

[0033] Figure 2A is a schematic flowchart of another method for processing events of a client provided by an embodiment of the present application;

[0034] Figure 2B is a schematic diagram of another function call process provided by an embodiment of the present application;

[0035] Figure 3 It is a schematic diagram of the event processing process of a client provided by an embodiment of the present application;

[0036] Figure 4 It is a schematic structural diagram of an event processing device for a client provided by an embodiment of the present application;

[0037] Figure 5 It is a schematic structural diagram of a terminal device provided by an embodiment of the present application. Detailed implementation manners

[0038] Next, the technical solutions in the embodiments of the present application will be described in conjunction with the accompanying drawings in the embodiments of the present application.

[0039] Please refer to Figure 1A , which is a schematic flowchart of an event processing method for a client provided by an embodiment of the present application. This method can be applied to a terminal device. The terminal device includes but is not limited to intelligent terminals such as smart phones, tablet computers, laptop computers, and desktop computers. The terminal device may include a client of the first system. The method may include the following steps:

[0040] S101. Monitor the trigger event of the client of the first system.

[0041] Among them, the trigger event of the client of the first system may be monitored based on the page of the client of the first system, or may be monitored based on the page of the client of the second system displayed on the client of the first system, and the present application does not make any restrictions. The trigger event may be a page interaction event, and the page interaction event may include at least one of the following: mouse event, keyboard event, touch event, browser event, form event, etc. The data corresponding to the trigger event may refer to the event data obtained according to the trigger event.

[0042] In one embodiment, the client of the first system may refer to the client of the first system that has been launched, such as any version of the client of the first system that has been launched or the latest version of the client.

[0043] S102. When monitoring the trigger event of the target service of the client of the second system accessed by the client of the first system, determine the target function included in the function library of the client of the second system according to the trigger event and the data corresponding to the trigger event, where the target function is a function for implementing the function of the target service.

[0044] Among them, the first system and the second system are different business systems. For example, for a medical system, the client of the first system can be a traditional medical informatization system, and the second system can be a third-party AI or Internet medical system. Exemplarily, multiple services can include a medical knowledge base, rational drug use, medical record quality control, auxiliary diagnosis, medication recommendation, and so on. The function library can include functions for implementing the functions of each of the multiple services of the client of the second system. The function library can encapsulate the business logic of the functions of each of the multiple services of the client of the second system. The function library, such as a JavaScript library, can include JavaScript functions for implementing the functions of each of the multiple services of the client of the second system. The function library, such as a JavaScript library, can be developed using HTML5 and CSS3 technologies. The client of the second system can be the client of any released version of the second system or the designated released version of the second system, such as the latest released version of the second system.

[0045] S103. Invoke the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event.

[0046] In the embodiment of the present application, the terminal device can invoke the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event. In the prior art, generally, it is necessary to consider the business of the client of another system and the logic of the server-side interface to develop the client of a certain system, so that the server of a certain system can access the server of another system in the way of interface call. Compared with the prior art, in the embodiment of the present application, by introducing the function library of the client of the second system into the client of the first system, the functions of the services of the client of the second system can be implemented. This process seems to the user to be completed within the same system, which can improve the user experience, and this process also makes the docking process between different business systems simple and easy to implement, can reduce the data interaction process between different systems, and improve the data interaction efficiency.

[0047] In one embodiment, when the client of the first system includes the function library, in combination with Figure 1B it can be seen that the terminal device can invoke the target function included in the function library through the client of the first system to implement the function of the target service according to the trigger event and the data corresponding to the trigger event.

[0048] In one embodiment, the function library included in the client of the first system can be obtained in the following manner: The terminal device can send a function library acquisition request to the server of the second system; the terminal device receives the function library of the client of the second system returned by the server of the second system in response to the function library acquisition request, and embeds the function library in the client of the first system. In this process, the terminal device can send a function library acquisition request to the server of the second system, the server of the second system can obtain the function library of the client of the second system in response to the function library acquisition request, and send the function library of the second system to the terminal device, and the terminal device can embed the function library in the client of the first system.

[0049] In one embodiment, the terminal device can obtain a Uniform Resource Locator (URL) input by the user for obtaining the function library of the client of the second system, generate the above-mentioned function library acquisition request according to the URL, and then send the function library acquisition request to the server of the second system. By adopting this process, the function library of the client of the second system can be dynamically added, so as to flexibly use the functions of the services of the client of the second system, such as some new functions.

[0050] In one embodiment, the process of embedding the function library in the client of the first system can occur in the scenario where the function library has not been embedded in the client of the first system, or in the scenario where the embedded function library needs to be updated. In one embodiment, whether to embed the function library in the client of the first system can be determined according to whether the development language of the client of the first system is the same as the development language of the second system. For example, if the client of the first system has the same development language as the client of the second system, the function library can be embedded in the client of the first system.

[0051] In one embodiment, the first system can be a system developed using the B / S architecture. The development language of the client of the second system is JavaScript. The function library of the client of the second system is a JavaScript library. In this case, since the client of the first system can itself be used as a browser, the JavaScript library can be directly embedded in the client of the first system without introducing a built-in browser.

[0052] It can be seen that Figure 1AIn the illustrated embodiment, when the terminal device monitors a trigger event for a target service of a client of the second system accessed by a client of the first system, it determines a target function included in the function library of the client of the second system based on the trigger event and the data corresponding to the trigger event, and invokes the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event. In this application, the docking of different service systems is realized by introducing the function library of the client of the second system into the client of the first system, which simplifies the docking process between different service systems and makes the docking process easier to implement.

[0053] The embodiments of this application can be applied to the field of intelligent healthcare for realizing the docking between different healthcare systems. For example, the client of the first system mentioned in the embodiments of this application can be a client of a traditional healthcare informatization system, and the client of the second system can be a client of a third-party AI or Internet healthcare system.

[0054] Please refer to Figure 2A , which is a schematic flowchart of another method for handling events of a client provided by the embodiments of this application. This method can be applied to the aforementioned terminal device. Specifically, this method can include the following steps:

[0055] S201. Monitor the trigger event of the client of the first system.

[0056] S202. When monitoring a trigger event for a target service of a client of the second system accessed by a client of the first system, determine a target function included in the function library of the client of the second system according to the trigger event and the data corresponding to the trigger event, where the target function is a function for implementing the function of the target service.

[0057] Among them, steps S201 and S202 can refer to Figure 1A steps S101 and S102 in the embodiments. The embodiments of this application will not elaborate here.

[0058] S203. Invoke the target function included in the function library through the built-in browser embedded in the client of the first system to implement the function of the target service according to the trigger event and the data corresponding to the trigger event.

[0059] In the embodiments of this application, Figure 2B viewed in combination, the terminal device can invoke the target function included in the function library through the built-in browser embedded in the client of the first system to implement the function of the target service according to the trigger event and the data corresponding to the trigger event.

[0060] In one embodiment, the first system may be a system developed using the C / S architecture. The development language of the client of the first system may be C#, Powerbuilder, Visual Basic, Delphi, C++, Android, etc. The development language of the client of the second system may be JavaScript. The function library of the client of the second system is a JavaScript library. In this case, since the development languages of the client of the first system and the client of the second system are different, the JavaScript library cannot be directly embedded in the client of the first system. However, in the embodiments of the present application, the JavaScript library can be introduced by embedding a built-in browser in the client of the first system. The built-in browser here may include a JavaScript engine, and the JavaScript engine can be used to interpret and execute JavaScript code.

[0061] In one embodiment, the process by which the terminal device uses the target function included in the function library through the built-in browser embedded in the client of the first system to implement the function of the target service according to the trigger event and the data corresponding to the trigger event may be: The terminal device transmits the trigger event and the data corresponding to the trigger event to the built-in browser embedded in the client of the first system through the client of the first system, and calls the target function included in the function library through the built-in browser to implement the function of the target service according to the trigger event and the data corresponding to the trigger event. This process realizes the call of the target function included in the function library of the client of the second system through the built-in browser embedded in the client of the first system. Compared with the prior art where the event processing efficiency is low due to the complex interface call methods between different business systems, the embodiments of the present application can improve the event processing rate.

[0062] In one embodiment, the process by which the terminal device transmits the trigger event and the data corresponding to the trigger event to the built-in browser embedded in the client of the first system through the client of the first system may be: The terminal device calls the data interaction function of the built-in browser embedded in the client of the first system through the client of the first system to transmit the trigger event and the data corresponding to the trigger event to the built-in browser. Refer to Figure 3 , the trigger event and the corresponding data can be transmitted between the page of the client of the first system and the page of the client of the second system through the data interaction function to implement related functions. This process seems to the user as if it is completed within the same system.

[0063] In one embodiment, the process by which the terminal device calls the target function included in the function library through the built-in browser to implement the function of the target service according to the trigger event and the data corresponding to the trigger event may be as follows: The terminal device calls the target function included in the function library through the built-in browser to execute the service logic corresponding to the target service according to the trigger event and the data corresponding to the trigger event, and obtains an execution result. The execution result may be service data obtained by executing the service logic corresponding to the target service, or the execution result may be the service data obtained when the execution is successful, or the execution result may be the result of execution failure obtained when the execution fails. In one embodiment, the way for the built-in browser to obtain the execution result may be to pass the execution result to the built-in browser by calling the interaction function of the built-in browser through the function library, and the built-in browser can receive the execution result passed by the function library. In one embodiment, the built-in browser may return the execution result to the client of the first system, thereby implementing the function of the target service.

[0064] In one embodiment, a dynamic link library (DLL) of the built-in browser may be added to the client of the first system. Specifically, the built-in browser may be embedded in the client of the first system in the following manner: The terminal device calls the interface provided by the DLL through the client of the first system to embed the built-in browser within the client of the first system. In the case where the development languages of the client of the first system and the client of the second system are different, this process can achieve the purpose of using the functions of the client of the second system by embedding the built-in browser within the client of the first system.

[0065] It can be seen that Figure 2A In the embodiment shown, the electronic device can implement the call of the target function in the function library of the client of the second system through the built-in browser embedded in the client of the first system, thereby implementing the function of the target service. Using this method can make the docking process between different service systems more simple and easy to implement.

[0066] In an auxiliary diagnosis scenario, the terminal device can obtain the URL for accessing the auxiliary diagnosis service input by the user on the client side of the traditional medical informatization system. The terminal device can access the URL of the auxiliary diagnosis service through the built-in browser of the traditional medical informatization system client, and the server of the system where the auxiliary diagnosis service is located can return a JavaScript library. The terminal device calls the JavaScript functions in the JavaScript library for implementing the functions of the auxiliary diagnosis service through the built-in browser to obtain the auxiliary diagnosis interface according to the URL and display the auxiliary diagnosis interface in the built-in browser. The user inputs the chief complaint information of the patient in the traditional medical informatization system client, and the terminal device calls the data interaction function of the built-in browser through the traditional medical informatization system client to transmit the diagnosis event and the chief complaint information of the patient to the built-in browser. The terminal device calls the JavaScript functions of the AI diagnosis service in the JavaScript library through the built-in browser, executes the business logic of the AI diagnosis service according to the diagnosis event and the chief complaint information, obtains a list of diagnosis results, and displays the list of diagnosis results in the built-in browser. After the user selects a diagnosis result, the JavaScript library calls the data interaction function of the built-in browser to transmit the selected diagnosis result to the built-in browser, and the built-in browser then returns the diagnosis result to the traditional medical informatization system client, thus completing the auxiliary diagnosis process.

[0067] Please refer to Figure 4 , an event processing device for a client provided by an embodiment of the present application. This event processing device can be applied to the aforementioned terminal device, and the terminal device includes a client of a first system. Specifically, the device may include:

[0068] A monitoring module 401, configured to monitor trigger events of the client of the first system.

[0069] A determination module 402, configured to, when the monitoring module 401 monitors a trigger event that the client of the first system accesses a target service of the client of the second system, determine a target function included in the function library of the client of the second system according to the trigger event and the data corresponding to the trigger event, where the target function is a function for implementing the function of the target service.

[0070] A calling module 403, configured to call the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event.

[0071] In an alternative embodiment, the client of the first system includes the function library, and the calling module 403 calls the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event. Specifically, the target function included in the function library is called through the client of the first system to implement the function of the target service according to the trigger event and the data corresponding to the trigger event.

[0072] In an alternative embodiment, the event processing device further includes a communication module 404 and an embedding module 405.

[0073] In an alternative embodiment, when a trigger event for accessing the target service of the client of the second system by the client of the first system is monitored, the communication module 404 is configured to send a function library acquisition request to the server of the second system and receive the function library of the client of the second system returned by the server of the second system in response to the function library acquisition request before determining the target function included in the function library of the client of the second system according to the trigger event and the data corresponding to the trigger event.

[0074] In an alternative embodiment, the embedding module 405 is configured to embed the function library in the client of the first system.

[0075] In an alternative embodiment, the calling module 403 calls the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event. Specifically, the target function included in the function library is called through the built-in browser embedded in the client of the first system to implement the function of the target service according to the trigger event and the data corresponding to the trigger event.

[0076] In an alternative embodiment, the calling module 403 uses the target function included in the function library through the built-in browser embedded in the client of the first system to implement the function of the target service according to the trigger event and the data corresponding to the trigger event. Specifically, the trigger event and the data corresponding to the trigger event are passed from the client of the first system to the built-in browser embedded in the client of the first system; the target function included in the function library is called through the built-in browser to implement the function of the target service according to the trigger event and the data corresponding to the trigger event.

[0077] In an alternative embodiment, the calling module 403 transmits a trigger event and data corresponding to the trigger event to a built-in browser of the client embedded in the first system through the client of the first system. Specifically, the data interaction function of the built-in browser embedded in the client of the first system is called through the client of the first system to transmit the trigger event and the data corresponding to the trigger event to the built-in browser.

[0078] In an alternative embodiment, the calling module 403 calls the target function included in the function library through the built-in browser to implement the function of the target service according to the trigger event and the data corresponding to the trigger event. Specifically, the target function included in the function library is called through the built-in browser to execute the service logic corresponding to the target service according to the trigger event and the data corresponding to the trigger event, and an execution result is obtained.

[0079] It can be seen that Figure 4 In the illustrated embodiment, when the event processing device monitors a trigger event of the target service of the client of the second system accessed by the client of the first system, it determines the target function included in the function library of the client of the second system according to the trigger event and the data corresponding to the trigger event, and calls the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event. This process simplifies the docking process between different service systems and makes the docking process easier to implement.

[0080] Please refer to Figure 5 , which is a schematic structural diagram of a terminal device provided by an embodiment of the present application. Among them, the terminal device described in this embodiment may include: a processor 1000, an input device 2000, an output device 3000, and a memory 4000. The processor 1000, the input device 2000, the output device 3000, and the memory 4000 may be connected through a bus or other means. In one embodiment, the input device 2000 and the output device are optional devices. In one embodiment, the input device 2000 and the output device 3000 may include standard wired or wireless communication interfaces. In one embodiment, the input device 2000 may further include a touch screen or a touch display screen and other devices. The output device 3000 may further include a display screen or a touch display screen and other devices.

[0081] The processor 1000 may be a Central Processing Unit (CPU), and this processor 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. The general-purpose processor may be a microprocessor or this processor may also be any conventional processor, etc.

[0082] The memory 4000 may be a high-speed RAM memory or a non-volatile memory, such as a disk memory. The memory 4000 is used to store a set of program codes, and the processor 1000, the input device 2000, and the output device 3000 can call the program codes stored in the memory 4000. Specifically:

[0083] The processor 1000 is configured to monitor trigger events of clients of the first system; when a trigger event of a client of the first system accessing a target service of a client of the second system is monitored, determine a target function included in the function library of the client of the second system according to the trigger event and the data corresponding to the trigger event, where the target function is a function for implementing the function of the target service; and call the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event.

[0084] In one embodiment, the client of the first system includes the function library, and the processor 1000 calls the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event, specifically by the client of the first system calling the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event.

[0085] In one embodiment, the processor 1000 is further configured to, when detecting a trigger event that a client of the first system accesses a target service of a client of the second system, before determining a target function included in the function library of the client of the second system according to the trigger event and the data corresponding to the trigger event, send a function library acquisition request to the server of the second system through the output device 3000; receive, through the input device 2000, the function library of the client of the second system returned by the server of the second system in response to the function library acquisition request, and embed the function library in the client of the first system.

[0086] In one embodiment, the processor 1000 calls the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event. Specifically, the built-in browser embedded in the client of the first system is used to call the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event.

[0087] In one embodiment, the processor 1000 uses the target function included in the function library through the built-in browser embedded in the client of the first system to implement the function of the target service according to the trigger event and the data corresponding to the trigger event. Specifically, the trigger event and the data corresponding to the trigger event are passed from the client of the first system to the built-in browser embedded in the client of the first system; the built-in browser is used to call the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event.

[0088] In one embodiment, the processor 1000 passes the trigger event and the data corresponding to the trigger event from the client of the first system to the built-in browser embedded in the client of the first system. Specifically, the data interaction function of the built-in browser embedded in the client of the first system is called through the client of the first system to pass the trigger event and the data corresponding to the trigger event to the built-in browser.

[0089] In one embodiment, the processor 1000 uses the built-in browser to call the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event. Specifically, the built-in browser is used to call the target function included in the function library to execute the service logic corresponding to the target service according to the trigger event and the data corresponding to the trigger event, and obtain an execution result.

[0090] In specific implementation, the processor 1000, the input device 2000, and the output device 3000 described in the embodiments of the present application may be executableFigure 1A and Figure 2A The implementation described in the embodiment can also execute the implementation described in the embodiment of the present application, which will not be repeated here.

[0091] In each embodiment of the present application, each functional unit can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

[0092] 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 program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above methods. Among them, the computer-readable storage medium can be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM), etc.

[0093] The above disclosure is only a preferred embodiment of the present application. Of course, the scope of the rights of the present application cannot be limited by this. Those of ordinary skill in the art can understand all or part of the processes of the above embodiments, and the equivalent changes made according to the claims of the present application still fall within the scope covered by the present application.

Claims

1. A method for event processing of a client, characterized in that, Applied to a terminal device, the terminal device includes a client of a first system, and the method includes: Listening for trigger events of the client of the first system; When a trigger event for the client of the first system to access the target service of the client of the second system is listened, determining, according to the trigger event and the data corresponding to the trigger event, the target function included in the function library of the client of the second system, where the target function is a function for implementing the function of the target service; the first system and the second system are different business systems, and the function library includes functions for implementing the functions of each service in multiple services of the client of the second system; Invoking, through the client of the first system, the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event; Before determining, according to the trigger event and the data corresponding to the trigger event, the target function included in the function library of the client of the second system, the method further includes: Sending a function library acquisition request to the server of the second system; Receiving the function library of the client of the second system returned by the server of the second system in response to the function library acquisition request, and embedding the function library in the client of the first system.

2. The method according to claim 1, characterized in that, The invoking the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event includes: Invoking, through the built-in browser embedded in the client of the first system, the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event.

3. The method according to claim 2, characterized in that, The invoking, through the built-in browser embedded in the client of the first system, the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event includes: Transmitting the trigger event and the data corresponding to the trigger event from the client of the first system to the built-in browser embedded in the client of the first system; Invoking, through the built-in browser, the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event.

4. The method according to claim 3, characterized in that, The transmitting the trigger event and the data corresponding to the trigger event from the client of the first system to the built-in browser embedded in the client of the first system includes: Invoking, through the client of the first system, the data interaction function of the built-in browser embedded in the client of the first system to transmit the trigger event and the data corresponding to the trigger event to the built-in browser.

5. The method according to claim 3, characterized in that, The invoking, through the built-in browser, the target function included in the function library to implement the function of the target service according to the trigger event and the data corresponding to the trigger event includes: Invoking, through the built-in browser, the target function included in the function library to execute the business logic corresponding to the target service according to the trigger event and the data corresponding to the trigger event, and obtaining an execution result.

6. An event processing device for a client, characterized in that, Applied to a terminal device, the terminal device includes a client of a first system, and the apparatus includes: A monitoring module, configured to monitor a trigger event of the client of the first system; A determining module, configured to, when the monitoring module monitors a trigger event that the client of the first system accesses a target service of the client of the second system, determine a target function included in the function library of the client of the second system according to the trigger event and data corresponding to the trigger event, where the target function is a function for implementing the function of the target service; the first system and the second system are different service systems, and the function library includes functions for implementing the functions of each of multiple services of the client of the second system; An invocation module, configured to invoke the target function included in the function library through the client of the first system, so as to implement the function of the target service according to the trigger event and the data corresponding to the trigger event; A communication module, configured to send a function library acquisition request to the server of the second system and receive the function library of the client of the second system returned by the server of the second system in response to the function library acquisition request before determining the target function included in the function library of the client of the second system according to the trigger event and the data corresponding to the trigger event; An embedding module, configured to embed the function library in the client of the first system.

7. A terminal device, characterized in that, Including a processor and a memory, the processor and the memory are connected to each other, where the memory is configured to store a computer program, the computer program includes program instructions, and the processor is configured to invoke the program instructions to execute the method according to any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, and the computer program is executed by a processor to implement the method according to any one of claims 1-5.

Images