A non-invasive auxiliary application integration method and system based on a browser kernel

Abstract

The present invention relates to a non-invasive auxiliary application integration method and system based on a browser kernel, belonging to the technical field of computer information processing. By expanding the resource request processing interface, resource response processing interface, and view rendering interface of the browser kernel, the present invention designs a monitoring module, a static data processing module, a functional script data encapsulation module, and a loading management module to monitor relevant characteristics and states of browser pages in real time, automatically perform corresponding operations on pages that meet the characteristics and states according to the configuration information provided by the extended resource and configuration management support service module, and place the entire seamless embedding and integration process inside the browser; the present invention overcomes the problems of cumbersome implementation, affecting human-computer interaction, and inadequate monitoring of necessary states in existing related technologies, and is easy to promote and apply.

Description

Technical Field

[0001] The present invention belongs to the technical field of computer information processing, and particularly relates to a non-invasive auxiliary application integration method and system based on a browser kernel. Background Art

[0002] There are many types of Web systems in operation in the power grid, and the burden on users is relatively large. If a separate independent system is built for any requirement for relevant personnel to use directly, the burden on relevant personnel will become increasingly large. Therefore, how to seamlessly embed and integrate the relevant functions of newly built Web systems due to various requirements into the functions or pages of the power grid management system has become a technical focus.

[0003] Currently, the technical methods that can achieve seamless embedding are RPA (Robotic Process Automation) technology and Selenium technology. RPA technology simulates and enhances the interaction process between humans and computers, and uses a control engine to achieve automatic processing of a large number of repetitive and regular workflow or tasks. It can take over the manual repetitive operation part in the original workflow, so as to non-invasively bridge the data interaction between two independent systems. Selenium technology is a general term for a series of tools and libraries that support Web browser automation. It provides extensions through the WebDriver core to simulate the interaction between users and browsers, is used to extend the distribution server allocated by the browser, and allows writing non-invasive interaction codes between Web systems through communication between multiple tabs of the Web browser.

[0004] RPA technology is a relatively general-purpose technology that can be used in various process operations. It can be adopted almost whenever there are repetitive and regular tasks. This technology is mainly used for process automation processing. Although using this technology can also build a bridge for the interaction between two Web systems, specific interaction process coding needs to be carried out for each pair of systems, and this technology executes the process by simulating user operations. Therefore, it is very difficult for users to obtain control of the system during the process of the process running, which affects the interaction between users and the actual business system.

[0005] The core of Selenium technology is WebDriver. This technology remotely controls various behaviors of the browser through WebDriver, and can enhance the functions of Web pages. However, when the browser page state (including: new, refreshed or closed) is modified by the user, Selenium cannot perceive it, which will cause the enhanced integrated functions not to be reloaded into the browser following the refresh of the Web page. Although this problem can be solved by designing a timer to check regularly, this not only cannot be made available in real time but also reduces the performance of the system. Therefore, how to overcome the deficiencies of the existing technology is an urgent problem to be solved in the current technical field. Summary of the Invention

[0006] The object of the present invention is to solve the deficiencies of the prior art, and provide a method for seamlessly embedding and integrating auxiliary application functions into a target Web system based on a browser kernel. A custom page function extension area is expanded from relevant interface levels according to the browser kernel interface, and then an extended resource and configuration management support service is designed based on this extension area, so as to place the entire seamless embedding and integration process inside the browser, overcoming the problems of cumbersome implementation, affecting human-computer interaction, and inadequate monitoring of necessary states in the prior related technologies.

[0007] To achieve the above object, the technical solution adopted by the present invention is as follows:

[0008] A non-intrusive auxiliary application integration method based on a browser kernel, comprising the following steps:

[0009] Step (1), expand the resource request processing interface in the browser kernel, and clone a copy of the target page request in the original interface;

[0010] Step (2), after monitoring the target page request cloning information, analyze the page-related features from this information;

[0011] Step (3), request the extended resource data corresponding to the target page from the external extended function resource and configuration management support service according to the analyzed page-related characteristic information, and then go to step (4); if there is no corresponding extended resource for the target page, do not go to step (4);

[0012] Step (4), hand over the static data in the obtained target page extended resource data to the resource response processing interface in the manner of local cache resources;

[0013] Step (5), expand the resource response processing interface in the browser kernel, and load the resources submitted in step (4) into the target page response resource list;

[0014] Step (6), package the functional script data in the obtained target page extended resource data in the format of a browser plug-in, and encapsulate it into a temporary extended function plug-in;

[0015] Step (7), perform loading management on the encapsulated extended function plug-in, and remove or load relevant extended function plug-ins from the target page according to the page rendering and display situation;

[0016] Step (8), expand the view rendering interface in the browser kernel, and notify the relevant state information of the page rendering and presentation to step (7) in real time, so that it can make corresponding adjustments in real time in response to page changes.

[0017] In step (7), whether to remove or load is determined by the configuration of the target page stored and managed by the external extension function resource and configuration management support service and the state of the target page. Generally, the corresponding configured function is loaded after the target page is rendered, and the corresponding configured function is removed after the target page is destroyed. "Related extension function plug-in" is to combine multiple extension functions of the same target page into one according to the functional order, and the whole is called a plug-in.

[0018] In step (8), the corresponding adjustments include: removal, loading, execution of the extended function and adjustment of the extended function's own page.

[0019] Furthermore, preferably, in step (1), the target page request content includes a request address, a type, a request header, and a page status.

[0020] Furthermore, preferably, in step (2), the page-related characteristics include the target system, whether the page is newly created or refreshed, and an extension identifier corresponding to the target page.

[0021] Furthermore, preferably, in step (4), the static data includes extended resource data of basic js scripts and css styles.

[0022] The present invention also provides a non-intrusive auxiliary application integration system based on a browser kernel, comprising:

[0023] Resource request processing interface, used to request to clone the target page;

[0024] The monitoring module is connected to the resource request processing interface and the extended function resource and configuration management support service module respectively, and is used to monitor the resource request processing interface. When the target page request cloning information is monitored, the page-related features are analyzed from the information, and the handle requests the extended function resource and configuration management support service module for the extended resource data corresponding to the target page according to the analyzed page-related feature information;

[0025] The extended function resource and configuration management support service module pre-stores resource data related to the extended function of the target page;

[0026] The static data processing module is connected to the monitoring module and the resource response processing interface respectively, and is used to deliver the static data in the acquired target page extension resource data to the resource response processing interface in the form of local cache resources;

[0027] Resource response processing interface, used to load the resources sent by the static data processing module into the target page response resource list;

[0028] A functional script data encapsulation module, connected to the monitoring module, is used to package the functional script data in the obtained target page extension resource data according to the browser plugin format and encapsulate it into a temporary extension function plugin;

[0029] A loading management module, connected to the functional script data encapsulation module, is used to manage the loading of the encapsulated extension function plugin, and remove or load relevant extension function plugins from the target page according to the page rendering and display situation;

[0030] A view rendering interface, connected to the loading management module, is used to notify the loading management module of the relevant status information of the page rendering in real time.

[0031] Among them, the relevant status information includes: page creation, page refresh, page destruction, rendering start, and rendering completion. After receiving the status information, the loading management module manages the extended functions according to the category of the status and the configuration of the target page.

[0032] The present invention extends the browser kernel resource request processing interface, resource response processing interface, and view rendering interface, and designs a custom page function extension area (including a monitoring module, a static data processing module, a functional script data encapsulation module, and a loading management module) to monitor the relevant characteristics and states of the browser page in real time, automatically perform corresponding operations on the pages that meet the characteristics and states according to the configuration information provided by the extended resources and configuration management support service, such as loading custom resources and automatic management of extended functions, and embed the entire seamless integration process inside the browser. By designing an external independent extended function resource and configuration management support service, it is ensured that the addition, editing, and adjustment of the extended functions corresponding to each target page can be uniformly performed through the support service, avoiding frequent adjustment and update of the browsers of many users.

[0033] Compared with the prior art, the beneficial effects of the present invention are:

[0034] The present invention expands a custom page function extension area from the browser kernel interface level to monitor the relevant characteristics and states of the browser page in real time, automatically perform corresponding operations on the pages that meet the characteristics and states, and place this series of processes inside the browser. After the relevant extended functions are successfully enhanced to the target page, the user can perform any operations on the business functions provided by the browser according to his own habits, without affecting the user operation habits and human-computer interaction, thus solving various problems of the existing related technologies. The present invention is simple to implement, easy to maintain, and convenient to use, meeting the application requirements. Brief Description of the Drawings

[0035] Figure 1 It is a schematic flow diagram of a non-intrusive auxiliary application integration method based on a browser kernel;

[0036] Figure 2 Schematic diagram of a non-invasive auxiliary application integration system based on a browser kernel;

[0037] Figure 3 Schematic diagram of the process flow of applying the method of the present invention. Detailed implementation manners

[0038] The present invention will be further described in detail below in conjunction with embodiments.

[0039] Those skilled in the art will understand that the following embodiments are only used to illustrate the present invention and should not be construed as limiting the scope of the present invention. For those not specified in the embodiments regarding specific technologies or conditions, they shall be carried out according to the technologies or conditions described in the literature in this field or according to the product specifications. For those materials or equipment not specified as to the manufacturer, they are all conventional products that can be obtained through purchase.

[0040] Those skilled in the art of the present technology can understand that unless specifically stated otherwise, the singular forms "a", "an", "the" and "said" used herein may also include the plural forms. It should be further understood that the term "including" used in the description of the present invention means the presence of the described features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or their groups. It should be understood that when we say that an element is "connected" to another element, it can be directly connected to other elements, or there may also be intermediate elements. The phrase "and / or" used herein includes any and all combinations of one or more of the associated listed items.

[0041] In the description of the present invention, unless otherwise specified, the meaning of "a plurality of" is two or more. The orientation or positional relationship indicated by terms such as "inside", "above", "below", etc. is based on the orientation or positional relationship shown in the drawings, and is only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be construed as a limitation to the present invention.

[0042] In the description of the present invention, it should be noted that unless otherwise clearly specified and defined, the terms "installed", "connected", "provided with" should be understood in a broad sense. For example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be directly connected or indirectly connected through an intermediate medium. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0043] Those skilled in the art can understand that, unless otherwise defined, all terms used herein (including technical terms and scientific terms) have the same meaning as the general understanding of those of ordinary skill in the art to which the present invention belongs. It should also be understood that terms such as those defined in a general dictionary should be understood to have a meaning consistent with their meaning in the context of the prior art, and will not be interpreted with idealized or overly formal meanings unless defined as such here.

[0044] As Figure 1 shown, a non-intrusive auxiliary application integration method based on a browser kernel includes the following steps:

[0045] Step (1), extend the resource request processing interface in the browser kernel, and clone a copy of the target page request in the original interface;

[0046] Step (2), after monitoring the target page request cloning information, analyze the page-related features from this information;

[0047] Step (3), according to the analyzed page-related characteristic information, request the extended resource data corresponding to the target page from the external extended function resources and configuration management support service, and then go to step (4); if there is no corresponding extended resource for the target page, do not go to step (4);

[0048] Step (4), hand over the static data in the obtained target page extended resource data to the resource response processing interface in the manner of local cache resources;

[0049] Step (5), extend the resource response processing interface in the browser kernel, and load the resources submitted in step (4) into the target page response resource list;

[0050] Step (6), package the functional script data in the obtained target page extended resource data in the format of a browser plug-in, and encapsulate it into a temporary extended function plug-in;

[0051] Step (7), perform loading management on the encapsulated extended function plug-in, and remove or load relevant extended function plug-ins from the target page according to the page rendering and display situation;

[0052] Step (8), extend the view rendering interface in the browser kernel, and notify the relevant status information of the page rendering and presentation to step (7) in real time, so that it can make corresponding adjustments in real time in response to page changes.

[0053] Among them, in step (1), the target page request content includes the request address, type, request header, and page status.

[0054] In step (2), the page-related features include the target system, whether the page is newly created or refreshed, and the extended identifier corresponding to the target page.

[0055] In step (4), the static data includes the basic js script and the extended resource data of the css style.

[0056] As Figure 2 shown, a non-intrusive auxiliary application integration system based on a browser kernel includes:

[0057] A resource request processing interface for requesting to clone a target page;

[0058] A monitoring module, connected to the resource request processing interface, the extended function resource, and the configuration management support service module respectively, for listening to the resource request processing interface. When the clone information of the target page is monitored, the page-related features are analyzed from the information, and the corresponding extended resource data of the target page is requested from the extended function resource and the configuration management support service module according to the analyzed page-related feature information;

[0059] The resource data involved in the extended functions of the target page is pre-stored in the extended function resource and configuration management support service module;

[0060] A static data processing module, connected to the monitoring module and the resource response processing interface respectively, for delivering the static data in the obtained extended resource data of the target page to the resource response processing interface in the manner of local cached resources;

[0061] A resource response processing interface for loading the resources transmitted by the static data processing module into the target page response resource list;

[0062] A functional script data encapsulation module, connected to the monitoring module, for packing the functional script data in the obtained extended resource data of the target page in the format of a browser plugin and encapsulating it into a temporary extended function plugin;

[0063] A loading management module, connected to the functional script data encapsulation module, for managing the loading of the encapsulated extended function plugin, and removing or loading relevant extended function plugins from the target page according to the page rendering and display situation;

[0064] A view rendering interface, connected to the loading management module, for notifying the loading management module of the relevant status information of the page rendering in real time.

[0065] Figure 1It is a schematic diagram of the non-invasive auxiliary application integration method based on the browser kernel. By extending the resource request processing interface, resource response processing interface, and view rendering interface of the browser kernel, a custom page function extension area is designed, which includes page feature and status detection, extended resource acquisition interaction, extended function encapsulation resource loading, dynamic function plugin management, etc.

[0066] In order to better manage extended functions, resource reuse, and facilitate implementation, according to the technical requirements of the page function extension area, an external independent extended function resource and configuration management support service is designed and constructed to ensure that the extended functions of each target page can be uniformly adjusted through the support service, avoiding frequent adjustments and updates to the browsers of numerous users.

[0067] Application Example

[0068] Figure 3 It is a schematic diagram of the application process of the present invention, including three parts: a self-made browser, an extended function resource and configuration management support service, and an intelligent auxiliary application service. The basic application process of the present invention is as follows:

[0069] First, the relevant resource data involved in the extended functions of the target page are entered into the extended function resource and configuration management support service, and the target page feature information is used as the unique identifier of the extended function resource. Then, the user uses the self-made browser to open and use the business system, and when the page is requested to be loaded, the steps of the page function extension area will be synchronously executed. Finally, after the extended function is loaded onto the target page, the user can freely perform any operation. Of course, each type of extended function can have its own corresponding backend intelligent auxiliary application service, which can be used to complete more complex auxiliary functions, such as image recognition, semantic analysis, etc.

[0070] The above shows and describes the basic principles, main features, and advantages of the present invention. Those skilled in the art of this industry should understand that the present invention is not limited by the above embodiments. What is described in the above embodiments and the specification only illustrates the principles of the present invention. Without departing from the spirit and scope of the present invention, the present invention will have various changes and improvements, and these changes and improvements all fall within the scope of the present invention claimed. The scope of protection claimed by the present invention is defined by the appended claims and their equivalents.

Claims

1. A non-invasive auxiliary application integration method based on a browser kernel, characterized in that It includes the following steps: Step (1), expand the resource request processing interface in the browser kernel, and clone a copy of the target page request in the original interface; Step (2), after listening to the target page request cloning information, analyze the page-related features from this information; Step (3), according to the analyzed page-related feature information, request the extended resource data corresponding to the target page from the external extended function resource and configuration management support service, and then go to Step (4); if there is no corresponding extended resource for the target page, do not go to Step (4); Step (4), hand over the static data in the obtained target page extended resource data to the resource response processing interface in the form of local cached resources; Step (5), expand the resource response processing interface in the browser kernel, and load the resources submitted in Step (4) into the target page response resource list; Step (6), package the functional script data in the obtained target page extended resource data in the browser plug-in format, and encapsulate it into a temporary extended function plug-in; Step (7), perform loading management on the encapsulated extended function plug-in, and remove or load relevant extended function plug-ins from the target page according to the page rendering display situation; Step (8), expand the view rendering interface in the browser kernel, and notify the relevant status information of the page presentation rendering to Step (7) in real time, so that it can respond to page changes in real time and make corresponding adjustments.

2. The non-invasive auxiliary application integration method based on a browser kernel according to claim 1, wherein In Step (1), the target page request content includes the request address, type, request header, and page status.

3. The non-invasive auxiliary application integration method based on a browser kernel according to claim 1, characterized in that In Step (2), the page-related features include the target system, whether the page is newly created or refreshed, and the extended identifier corresponding to the target page.

4. The non-intrusive auxiliary application integration method based on a browser kernel according to claim 1, wherein In Step (4), the static data includes the extended resource data of the basic js script and css style.

5. A non-invasive auxiliary application integration system based on a browser kernel, characterized in that, It includes: A resource request processing interface for requesting to clone the target page; A monitoring module, connected to the resource request processing interface, the extended function resource, and the configuration management support service module respectively, for monitoring the resource request processing interface. When it listens to the target page request cloning information, it analyzes the page-related features from this information, and requests the extended resource data corresponding to the target page from the extended function resource and the configuration management support service module according to the analyzed page-related feature information; The extended function resource and configuration management support service module pre-stores the resource data involved in the extended function of the target page; A static data processing module, connected to the monitoring module and the resource response processing interface respectively, for handing over the static data in the obtained target page extended resource data to the resource response processing interface in the form of local cached resources; A resource response processing interface for loading the resources transmitted by the static data processing module into the target page response resource list; A functional script data encapsulation module, connected to the monitoring module, for packaging the functional script data in the obtained target page extended resource data in the browser plug-in format and encapsulating it into a temporary extended function plug-in; The loading management module is connected to the functional script data encapsulation module and is used to manage the loading of the encapsulated extended function plug-ins, and remove or load relevant extended function plug-ins from the target page according to the page rendering display situation; The view rendering interface is connected to the loading management module and is used to notify the loading management module of the relevant status information of the page rendering in real time.

Images