CN117312693A - Interface information sharing method and device, electronic equipment and storage medium - Google Patents

Abstract

The application provides an interface information sharing method and device, electronic equipment and a storage medium. The method comprises the following steps: monitoring to obtain key information on a current interactive interface, wherein the key information is used for filtering information; synchronizing the key information to a current browser route to obtain a target browser route corresponding to the current interface information, wherein the current browser route is a URL address corresponding to the current interactive interface, and the current interface information comprises the current interactive interface and the key information; determining shared object information for sharing the current interface information; and sending the shared object information and the target browser route to the server, so that the server shares the target browser route to the target object corresponding to the shared object information, and the target object displays the current interface information according to the target browser route. By the method and the device, the technical problems that interface information sharing efficiency is low, information quality is uneven and real-time synchronization cannot be achieved in the related technology are solved.

Description

Interface information sharing method and device, electronic equipment and storage medium

Technical field

The present application relates to the field of data interaction technology, and in particular to an interface information sharing method and device, electronic equipment and storage media.

Background technique

Currently, in existing interactive systems, if users need to share system interface information, this can only be achieved through screenshots, screen recordings, etc.

Using the above method to share system interface information has the following problems:

1. Low efficiency: Operations such as screenshots and screen recordings require users to perform manual operations, and post-processing of screenshots or screen recordings, such as cropping, compression, etc., consumes a lot of time and energy from users;

2. The quality of information is uneven: Since screenshots and screen recordings cannot guarantee the accuracy and completeness of the information, the quality of the shared interface information is uneven, which affects the communication effect between users;

3. Unable to synchronize in real time: Screenshots and screen recordings cannot be synchronized in real time and cannot meet the immediate needs of users during communication.

Therefore, interface information sharing in related technologies has technical problems such as low efficiency, uneven information quality, and inability to synchronize in real time.

Contents of the invention

This application provides an interface information sharing method and device, electronic equipment, and storage media to at least solve the technical problems of low efficiency, uneven information quality, and inability to synchronize in real time in interface information sharing in related technologies.

According to one aspect of the embodiments of the present application, an interface information sharing method is provided, which is applied to a terminal and includes:

Monitor and obtain key information on the current interactive interface, where the key information is used for information filtering;

Synchronize the key information to the current browser route to obtain the target browser route corresponding to the current interface information, where the current browser route is the URL address corresponding to the current interactive interface, and the current interface information includes the Describe the current interactive interface and the key information;

Determine the shared object information for sharing the current interface information;

Send the shared object information and the target browser route to the server, so that the server shares the target browser route to the target object corresponding to the shared object information, and causes the target object to follow the specified The target browser route displays the current interface information.

Optionally, as in the aforementioned method, the monitoring obtains key information on the current interface, including:

Obtain the key sub-information entered in each target control on the current interactive interface;

The key information is obtained based on the key sub-information input in each target control.

Optionally, as in the aforementioned method, the key information is synchronized to the current browser route to obtain the target browser route corresponding to the current interface information, including:

Determine the information type corresponding to each key sub-information according to the key sub-information input in each target control and the information type corresponding to each target control;

Determine the key browser route based on the information type corresponding to each key sub-information;

After splicing the key browser route to the current browser route, the target browser route corresponding to the current interface information is obtained.

Optionally, as in the aforementioned method, after determining the key browser route based on the information type corresponding to each key sub-information, the method further includes:

Filter according to the key information to obtain target information, and update the current interactive interface to obtain an updated interactive interface including the target information;

Determine the updated browser route of the updated interactive interface;

After splicing the key browser route to the updated browser route, the updated browser route corresponding to the updated interface information is obtained, wherein the updated interface information includes the updated interactive interface and all Describe key information.

According to another aspect of the embodiment of the present application, an interface information sharing method is also provided, applied to a server, including:

Obtain the shared object information and the target browser route from the client, where the target browser route means that the client obtains key information on the current interactive interface through monitoring, and synchronizes the key information to the current browser route. After that, the browser route corresponding to the current interface information is obtained. The key information is used for information filtering. The current browser route is the URL address corresponding to the current interactive interface. The current interface information includes the current interface information. Interactive interface and the key information;

The target browser route is shared to the target object corresponding to the shared object information, so that the target object displays the current interface information according to the target browser route.

Optionally, as in the aforementioned method, the target browser route is shared to the target object corresponding to the shared object information, so that the target object displays the current interface information according to the target browser route. ,include:

Generate target notification information according to the target browser route;

The target notification information is pushed to the target object according to the shared object information, so that the target object opens the current interface information by triggering the target notification information.

According to another aspect of the embodiment of the present application, an interface information sharing device is also provided, which is applied to a terminal and includes:

A listening module, used to monitor and obtain key information on the current interactive interface, where the key information is used for information filtering;

A synchronization module, used to synchronize the key information to the current browser route to obtain the target browser route corresponding to the current interface information, wherein the current browser route is the URL address corresponding to the current interactive interface, and the The current interface information includes the current interactive interface and the key information;

A sharing module, used to determine the shared object information for sharing the current interface information;

The first sending module is used to send the shared object information and the target browser route to the server, so that the server shares the target browser route to the target object corresponding to the shared object information, and The target object is caused to display the current interface information according to the target browser route.

According to another aspect of the embodiment of the present application, an interface information sharing device is also provided, which is applied to a server and includes:

The acquisition module is used to obtain the shared object information from the client and the target browser route, wherein the target browser route is for the client to obtain the key information on the current interactive interface through monitoring, and synchronize the key information to After the current browser route is completed, the browser route corresponding to the current interface information is obtained. The key information is used for information filtering. The current browser route is the URL address corresponding to the current interactive interface. The current interface The information includes the current interactive interface and the key information;

The second sending module is configured to share the target browser route to the target object corresponding to the shared object information, so that the target object displays the current interface information according to the target browser route.

According to yet another aspect of the embodiment of the present application, an electronic device is also provided, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory complete communication with each other through the communication bus; wherein, A memory is used to store a computer program; a processor is used to execute the method steps in any of the above embodiments by running the computer program stored on the memory.

According to yet another aspect of the embodiment of the present application, a computer-readable storage medium is also provided. The storage medium stores a computer program, wherein the computer program is configured to execute the method in any of the above embodiments when running. step.

In the embodiment of this application, the key information on the current interactive interface is obtained through monitoring, and the key information is synchronized to the current browser route, so that the target browser route corresponding to the current interface information can be obtained; and the current interface is processed through the server. The shared object information and the target browser route for information sharing are sent to the target object, so that the target object displays the current interface information according to the target browser route; thus achieving the purpose of sharing the current interface information to the target object; due to the sharing process , there is no need to take screenshots, screen recordings, etc., thus solving the technical problems in related technologies such as inefficiency in interface information sharing, uneven information quality, and inability to synchronize in real time.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

In order to more clearly explain the embodiments of the present application or the technical solutions in the prior art, the following will briefly introduce the drawings needed to describe the embodiments or the prior art. Obviously, for those of ordinary skill in the art, It is said that other drawings can be obtained based on these drawings without exerting creative labor.

Figure 1 is a schematic diagram of the hardware environment of an optional interface information sharing method according to an embodiment of the present application;

Figure 2 is a schematic flowchart of an optional interface information sharing method applied to a terminal according to an embodiment of the present application;

Figure 3 is a schematic flowchart of an optional interface information sharing method applied to a server according to an embodiment of the present application;

Figure 4 is a structural block diagram of an optional interface information sharing device applied to a terminal according to an embodiment of the present application;

Figure 5 is a structural block diagram of an optional interface information sharing device applied to a server according to an embodiment of the present application;

Figure 6 is a structural block diagram of an optional electronic device according to an embodiment of the present application.

Detailed ways

In order to enable those in the technical field to better understand the solutions of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only These are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts should fall within the scope of protection of this application.

It should be noted that the terms "first", "second", etc. in the description and claims of this application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments of the application described herein can be practiced in sequences other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, e.g., a process, method, system, product, or apparatus that encompasses a series of steps or units and need not be limited to those explicitly listed. Those steps or elements may instead include other steps or elements not expressly listed or inherent to the process, method, product or apparatus.

According to one aspect of the embodiments of the present application, an interface information sharing method is provided. Optionally, in this embodiment, the above interface information sharing method can be applied to a hardware environment composed of a terminal 1402 and a server 1404 as shown in FIG. 1 . As shown in Figure 1, the server 1404 is connected to the terminal 1402 through the network and can be used to provide services (such as game services, application services, etc.) for the terminal or the client installed on the terminal. The database can be set up on the server or independently from the server. Used to provide data storage services for server 1404.

The above-mentioned network may include but is not limited to at least one of the following: wired network, wireless network. The above-mentioned wired network may include but is not limited to at least one of the following: wide area network, metropolitan area network, and local area network. The above-mentioned wireless network may include at least one of the following: WIFI (Wireless Fidelity, Wireless Fidelity), Bluetooth. The terminal may not be limited to a PC, a mobile phone, a tablet, etc.

The interface information sharing method in the embodiment of the present application can be executed by the server, the terminal, or both the server and the terminal. Wherein, the terminal executing the interface information sharing method of the embodiment of the present application may also be executed by a client installed on the terminal.

Taking the interface information sharing method in this embodiment executed by a terminal as an example, Figure 2 shows an interface information sharing method provided by an embodiment of the present application. It is applied to a terminal and includes the following steps:

Step S101: Monitor and obtain key information on the current interactive interface, where the key information is used for information filtering.

The interface information sharing method in this embodiment can be applied to scenarios where the system interface needs to be shared with other users.

Specifically, the client of the terminal can obtain the key information on the current interactive interface by monitoring the information in the specified control on the current interactive interface.

Key information may be information used for information filtering. The types that can be included are: time, type, etc., which can be selected according to the functions of the actual system or the business scenarios it is applied to.

The current interactive interface may be an interface for inputting key information. That is to say, the current interactive interface may be other interface information other than key information in the target system that needs to be interface shared.

Step S102, synchronize the key information to the current browser route to obtain the target browser route corresponding to the current interface information, where the current browser route is the URL address corresponding to the current interactive interface, and the current interface information includes the current interactive interface and key information. .

Specifically, after determining the key information, in this embodiment, the key information is synchronized to the current browser route, that is, the key information is synchronized to the URL address of the current interactive interface, and the target browser corresponding to the current interface information is obtained. routing.

Synchronizing the key information to the current browser route may be based on the key information to generate a key browser route for synchronization to the browser route, and then integrating the key browser route with the URL address of the current interactive interface to obtain the target browser route.

Step S103: Determine the sharing object information for sharing the current interface information.

Specifically, after obtaining the current interface information, the shared object information of the shared object that needs to be shared can be determined.

The shared object information may include but is not limited to: the account in the target system, the password corresponding to the account, etc.

Moreover, the shared object information can be obtained by the sharing initiator after inputting the shared object information input control.

Step S104: Send the shared object information and the target browser route to the server, so that the server shares the target browser route to the target object corresponding to the shared object information, and causes the target object to display the current interface information according to the target browser route.

Specifically, after the shared object information and the target browser route are determined, the shared object information can be sent to the server, and then the target browser route is shared to the target object corresponding to the shared object information through the server.

The target object can be a client logged in with an account indicated by the shared object information. The target object can parse the target browser route and obtain the current interface information. For example, you can first obtain the current interactive interface based on the current browser routing request in the target browser route, and then parse and obtain the key information based on the key browser route corresponding to the key information in the target browser route; thereby the interface obtains the current interface information.

The method in this embodiment obtains key information on the current interactive interface through monitoring, and synchronizes the key information to the current browser route, so that the target browser route corresponding to the current interface information can be obtained; and the server will process the current interface The shared object information and the target browser route for information sharing are sent to the target object, so that the target object displays the current interface information according to the target browser route; thereby achieving the purpose of sharing the current interface information to the target object; due to the sharing process , there is no need to take screenshots, screen recordings, etc., thus solving the technical problems in related technologies such as inefficiency in interface information sharing, uneven information quality, and inability to synchronize in real time.

As an optional embodiment, as in the aforementioned method, step S101 monitors and obtains key information on the current interface, including the following steps:

Step 1201: Obtain key sub-information entered in each target control on the current interactive interface.

Step 1202: Obtain key information based on the key sub-information input in each target control.

Specifically, in order to obtain the key information input by the user, there are multiple target controls on the current interactive interface that can be used to input key sub-information.

The target control can input key sub-information through a drop-down box or typing input. Each key sub-information can be composed of one or more characters.

After determining the key sub-information input in each target control, the key information can be obtained based on the key sub-information input in each target control. That is to say, the key information includes all key sub-information.

Through the method of this embodiment, key information on the current interactive interface can be extracted.

As an optional embodiment, as in the aforementioned method, step S102 synchronizes key information to the current browser route to obtain the target browser route corresponding to the current interface information, including the following steps:

Step 1301: Determine the information type corresponding to each key sub-information according to the key sub-information input in each target control and the information type corresponding to each target control.

Specifically, the type of information used to input information for each target control is different, such as time, resource type, etc.

Therefore, for different key sub-information, the information type corresponding to each key self-information is also different from each other.

Step 1302: Determine the key browser route based on the information type corresponding to each key sub-information.

Specifically, after determining the information type corresponding to each key sub-information, a preset correspondence relationship can be followed, for example, the URL information corresponding to each information type, and the URL information corresponding to each key sub-information. Generate critical browser routes.

Step S1303: After splicing key browser routes to the current browser route, the target browser route corresponding to the current interface information is obtained.

After determining the key browser route, the key browser route can be spliced to the current browser route to obtain the target browser route corresponding to the current interface information; further, the first N characters of the key browser route can be obtained Use preset characters for identification to distinguish it from the current browser route of the current interactive interface, so as to facilitate later analysis to obtain the current interactive interface and key information.

As an optional embodiment, as in the aforementioned method, after step S1302 determines the key browser route based on the information type corresponding to each key sub-information, the method further includes the following steps:

Step 1401, filter the target information according to the key information, and update the current interactive interface to obtain an updated interactive interface including the target information;

Step 1402, determine the updated browser route of the updated interactive interface;

Step 1403: After splicing the key browser routes to the updated browser routes, the updated browser routes corresponding to the updated interface information are obtained, where the updated interface information includes the updated interactive interface and key information.

That is to say, after the key information is determined, the target information can be obtained by filtering first, that is, the target information is the information used for filtering the key information.

For example, after entering key information in all target controls, you can click a button such as "Query" to start a query, obtain the target information from the server, and update the current interactive interface to obtain an updated interactive interface including the target information.

After the target updated interactive interface is determined, the updated browser route corresponding to the updated interactive interface can be obtained. Then, the key browser routes can be spliced to the updated browser routes to obtain the updated browser routes corresponding to the updated interface information.

As shown in Figure 3, according to another aspect of the embodiment of the present application, an interface information sharing method is also provided, which is applied to a server and includes the following steps:

Step S201, obtain the shared object information from the client and the target browser route. The target browser route is that the client obtains the key information on the current interactive interface through monitoring, and synchronizes the key information to the current browser route to obtain The browser route corresponding to the current interface information. The key information is used for information filtering. The current browser route is the URL address corresponding to the current interactive interface. The current interface information includes the current interactive interface and key information;

Step S202: Share the target browser route to the target object corresponding to the shared object information, so that the target object displays the current interface information according to the target browser route.

Specifically, the client of the terminal can obtain the key information on the current interactive interface by monitoring the information in the specified control on the current interactive interface.

Key information may be information used for information filtering. The types that can be included are: time, type, etc., which can be selected according to the functions of the actual system or the business scenarios it is applied to.

The current interactive interface may be an interface for inputting key information. That is to say, the current interactive interface may be other interface information other than key information in the target system that needs to be interface shared.

After determining the key information, the client of the terminal synchronizes the key information to the current browser route, that is, synchronizes the key information to the URL address of the current interactive interface, and obtains the target browser route corresponding to the current interface information.

Synchronizing the key information to the current browser route may be based on the key information to generate a key browser route for synchronization to the browser route, and then integrating the key browser route with the URL address of the current interactive interface to obtain the target browser route.

After obtaining the current interface information, the shared object information of the shared object that needs to be shared can be determined.

The shared object information may include but is not limited to: the account in the target system, the password corresponding to the account, etc.

Moreover, the shared object information can be obtained by the sharing initiator after inputting the shared object information input control.

Specifically, after determining the shared object information and the target browser route, the terminal can send the shared object information and the target browser route to the server.

After the server obtains the shared object information and the target browser route, it can share the target browser route to the target object corresponding to the shared object information according to the shared object information.

The target object can be a client logged in with an account indicated by the shared object information. The target object can parse the target browser route and obtain the current interface information. For example, you can first obtain the current interactive interface based on the current browser routing request in the target browser route, and then parse and obtain the key information based on the key browser route corresponding to the key information in the target browser route; thereby the interface obtains the current interface information.

As an optional embodiment, as in the aforementioned method, step S202 shares the target browser route to the target object corresponding to the shared object information, so that the target object displays the current interface information according to the target browser route, including the following The steps described:

Step 2101: Generate target notification information according to the target browser route.

Specifically, after acquiring the shared object information and the target browser route, the server can first generate target notification information for notifying the target object based on the target browser route.

The target notification information can be encapsulated with the target browser route, and the target notification information can be encapsulated in the form of a card notification.

Step 2102: Push the target notification information to the target object according to the shared object information, so that the target object opens the current interface information by triggering the target notification information.

Specifically, after the target notification information is generated, the target notification information can be pushed to the target object according to the shared object information.

For example, according to the target account information in the shared object information, the target notification information can be pushed to the target client (that is, the target object) currently logged in with the target account corresponding to the target account information, and the target notification information in the target object After being triggered (for example, clicked), the current interface information can be opened.

As described below, an application example using any of the foregoing embodiments is provided:

Open the visual interface of the system (i.e., the current interactive interface), and you can see the keyword screening (i.e., target control) of the filtering information module.

Users can select keywords to filter data by themselves in the target control of the client (i.e., key sub-information entered in each target control). The client monitors the keywords selected by the user and synchronizes all keywords (i.e., key information). Go to the current browser route and get the target browser route.

In the selected keyword filtering out required information interface, click the share button on the visual interface, fill in the login ID of the designated sharing person (i.e., the shared object information), and send the target browser route to the server, which will then send the target browser The router route is pushed to the shared information interface of the specified user system (i.e., the target object).

On the designated push user system interface (i.e., the interface of the target object), the card notification received from the server push (i.e., the target notification information) is displayed. The user clicks the notification card notification to jump to the current shared interface information.

The implementation principle can be:

The user selects the interface information that needs to be shared through the client (ie, terminal) application program, and the interface information is digitized to generate a shared data package (ie, including the target browser route).

The client application sends the shared data package to the server, and at the same time, the client application requests the server to match other users who are allowed to be shared with the shared data package.

The server receives the shared data package and stores it in the shared database. At the same time, according to the request of the client application (ie, the shared object information sent), it matches other user systems (ie, target objects) that are allowed to share the shared data package.

The server sends the matching results to the client application, and the client application establishes communication channels with other users based on the matching results to realize real-time sharing of system interface information between users.

It should be noted that for the sake of simple description, the foregoing method embodiments are expressed as a series of action combinations. However, those skilled in the art should know that the present application is not limited by the described action sequence. Because in accordance with this application, certain steps may be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily necessary for this application.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is Better implementation. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence or that contributes to the existing technology. The computer software product is stored in a storage medium (such as ROM (Read-Only Memory, Read-only memory)/RAM (Random Access Memory, disk, optical disk), including a number of instructions to make a terminal device (can be a mobile phone, computer, server, or network device, etc.) to execute this Apply the methods described in the various examples.

According to another aspect of the embodiments of the present application, an interface information sharing device for implementing the above interface information sharing method applied to a terminal is also provided. Figure 4 is a structural block diagram of an optional interface information sharing device according to an embodiment of the present application. The device is applied to a terminal. As shown in Figure 4, the device may include:

The monitoring module 11 is used to monitor and obtain key information on the current interactive interface, where the key information is used for information filtering;

Synchronization module 12 is used to synchronize key information to the current browser route to obtain the target browser route corresponding to the current interface information, where the current browser route is the URL address corresponding to the current interactive interface, and the current interface information includes the current interactive interface and key information;

Sharing module 13, used to determine the shared object information for sharing the current interface information;

The first sending module 14 is used to send the shared object information and the target browser route to the server, so that the server shares the target browser route to the target object corresponding to the shared object information, and causes the target object to be displayed according to the target browser route. Current interface information.

It should be noted that the listening module 11 in this embodiment can be used to perform the above step S101, the synchronization module 12 in this embodiment can be used to perform the above step S102, and the sharing module 13 in this embodiment can be used to perform the above step S101. Step S103, the first sending module 14 in this embodiment can be used to perform the above step S104.

In addition to the above-mentioned modules, the device in this embodiment may also include a module that performs any method in any of the foregoing embodiments of the interface information sharing method applied to the terminal.

According to another aspect of the embodiment of the present application, an interface information sharing device for implementing the above interface information sharing method applied to a server is also provided. Figure 5 is a structural block diagram of an optional interface information sharing device according to an embodiment of the present application. The device is applied to a server. As shown in Figure 5, the device may include:

According to another aspect of the embodiment of the present application, an interface information sharing device is also provided, which is applied to a server and includes:

The acquisition module 21 is used to obtain the shared object information from the client and the target browser route. The target browser route is for the client to obtain the key information on the current interactive interface through monitoring, and synchronize the key information to the current browser route. After that, the browser route corresponding to the current interface information is obtained, and the key information is used for information filtering. The current browser route is the URL address corresponding to the current interactive interface. The current interface information includes the current interactive interface and key information;

The second sending module 22 is used to share the target browser route to the target object corresponding to the shared object information, so that the target object displays the current interface information according to the target browser route.

It should be noted that the acquisition module 21 in this embodiment can be used to perform the above step S201, and the second sending module 22 in this embodiment can be used to perform the above step S202.

In addition to the above-mentioned modules, the device in this embodiment may also include a module that performs any method in any of the foregoing embodiments of the interface information sharing method applied to the server.

It should be noted here that the examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the contents disclosed in the above embodiments. It should be noted that the above module, as part of the device, can run in the hardware environment as shown in Figure 1, and can be implemented by software or hardware, where the hardware environment includes a network environment.

According to yet another aspect of the embodiment of the present application, an electronic device for implementing the above system interface information method is also provided. The electronic device may be a server, a terminal, or a combination thereof.

According to another embodiment of the present application, an electronic device is also provided, including: As shown in Figure 6, the electronic device may include: a processor 1501, a communication interface 1502, a memory 1503, and a communication bus 1504, wherein the processor 1501, The communication interface 1502 and the memory 1503 complete communication with each other through the communication bus 1504.

Memory 1503, used to store computer programs;

The processor 1501 is used to implement the following steps when executing the program stored in the memory 1503:

Interface information sharing method applied to terminals:

Step S101: Monitor and obtain key information on the current interactive interface, where the key information is used for information filtering.

Step S102, synchronize the key information to the current browser route to obtain the target browser route corresponding to the current interface information, where the current browser route is the URL address corresponding to the current interactive interface, and the current interface information includes the current interactive interface and key information. .

Step S103: Determine the sharing object information for sharing the current interface information.

Step S104: Send the shared object information and the target browser route to the server, so that the server shares the target browser route to the target object corresponding to the shared object information, and causes the target object to display the current interface information according to the target browser route.

And, the interface information sharing method applied to the server:

Step S201, obtain the shared object information from the client and the target browser route. The target browser route is that the client obtains the key information on the current interactive interface through monitoring, and synchronizes the key information to the current browser route to obtain The browser route corresponding to the current interface information. The key information is used for information filtering. The current browser route is the URL address corresponding to the current interactive interface. The current interface information includes the current interactive interface and key information;

Step S202: Share the target browser route to the target object corresponding to the shared object information, so that the target object displays the current interface information according to the target browser route.

Optionally, in this embodiment, the above-mentioned communication bus may be a PCI (Peripheral Component Interconnect, Peripheral Component Interconnect Standard) bus, or an EISA (Extended Industry Standard Architecture, Extended Industry Standard Architecture) bus, etc. The communication bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus. The communication interface is used for communication between the above-mentioned electronic devices and other devices.

The memory may include random access memory (Random Access Memory, RAM) or non-volatile memory (Non-Volatile Memory, NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located far away from the aforementioned processor.

As an example, the above-mentioned memory 1503 may include, but is not limited to, the listening module 11, the synchronization module 12, the sharing module 13 and the first sending module 14 in the above-mentioned interface information sharing device applied to the terminal, as well as the interface information applied to the server. The acquisition module 21 and the second sending module 22 in the shared device. In addition, it may also include but is not limited to other module units in the above-mentioned interface information sharing device for terminals and the interface information sharing device applied to servers, which will not be described again in this example.

The above-mentioned processor may be a general-purpose processor, which may include but is not limited to: CPU (Central Processing Unit, central processing unit), NP (Network Processor, network processor), etc.; it may also be a DSP (Digital Signal Processor, digital signal processor), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array, field programmable gate array) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components.

An embodiment of the present application also provides a computer-readable storage medium. The storage medium includes a stored program, wherein the method steps of the above method embodiment are executed when the program is run.

Optionally, in this embodiment, the above-mentioned storage medium may include but is not limited to: U disk, ROM, RAM, mobile hard disk, magnetic disk or optical disk and other various media that can store program codes.

The above serial numbers of the embodiments of the present application are only for description and do not represent the advantages or disadvantages of the embodiments.

If the integrated units in the above embodiments are implemented in the form of software functional units and sold or used as independent products, they can be stored in the above computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, It includes several instructions to cause one or more computer devices (which can be personal computers, servers or network devices, etc.) to execute all or part of the steps of the methods described in various embodiments of this application.

In the above-mentioned embodiments of the present application, each embodiment is described with its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

In the several embodiments provided in this application, it should be understood that the disclosed client can be implemented in other ways. Among them, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or may be Integrated into another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the units or modules may be in electrical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution provided in this embodiment.

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

The above are only the preferred embodiments of the present application. It should be pointed out that for those of ordinary skill in the art, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications can also be made. should be regarded as the scope of protection of this application.

Claims (10)

1. The interface information sharing method is characterized by being applied to a terminal and comprising the following steps:

monitoring to obtain key information on a current interactive interface, wherein the key information is used for filtering information;

synchronizing the key information to a current browser route to obtain a target browser route corresponding to current interface information, wherein the current browser route is a URL address corresponding to the current interactive interface, and the current interface information comprises the current interactive interface and the key information;

Determining shared object information for sharing the current interface information;

and sending the shared object information and the target browser route to a server, so that the server shares the target browser route to a target object corresponding to the shared object information, and the target object displays the current interface information according to the target browser route.

2. The method of claim 1, wherein the monitoring obtains key information on the current interface, comprising:

acquiring key sub-information input in each target control on the current interactive interface;

and obtaining the key information based on the key sub-information input in each target control.

3. The method of claim 2, wherein synchronizing the key information to the current browser route to obtain the target browser route corresponding to the current interface information comprises:

determining the information type corresponding to each piece of key sub-information according to the key sub-information input in each piece of target control and the information type corresponding to each piece of target control;

determining a key browser route based on the information type corresponding to each key sub-information;

And splicing the key browser route to the current browser route to obtain the target browser route corresponding to the current interface information.

4. The method of claim 3, wherein after determining the critical browser route based on the information type corresponding to each critical sub-information, the method further comprises:

filtering according to the key information to obtain target information, and updating the current interactive interface to obtain an updated interactive interface comprising the target information;

determining an updated browser route of the updated interactive interface;

and splicing the key browser route to the updated browser route to obtain the updated browser route corresponding to the updated interface information, wherein the updated interface information comprises the updated interactive interface and the key information.

5. An interface information sharing method, which is applied to a server, comprises the following steps:

obtaining shared object information from a client and a target browser route, wherein the target browser route is a browser route corresponding to current interface information after the client monitors to obtain key information on a current interactive interface, the key information is synchronized to the current browser route, the key information is used for information filtering, the current browser route is a URL address corresponding to the current interactive interface, and the current interface information comprises the current interactive interface and the key information;

And sharing the target browser route to a target object corresponding to the shared object information, so that the target object displays the current interface information according to the target browser route.

6. The method of claim 5, wherein sharing the target browser route to the target object corresponding to the shared object information, so that the target object displays the current interface information according to the target browser route, comprises:

generating target notification information according to the target browser route;

pushing the target notification information to the target object according to the shared object information, so that the target object opens the current interface information by triggering the target notification information.

7. An interface information sharing apparatus, applied to a terminal, comprising:

the monitoring module is used for monitoring and obtaining key information on the current interactive interface, wherein the key information is used for filtering information;

the synchronization module is used for synchronizing the key information into a current browser route to obtain a target browser route corresponding to current interface information, wherein the current browser route is a URL address corresponding to the current interactive interface, and the current interface information comprises the current interactive interface and the key information;

The sharing module is used for determining shared object information for sharing the current interface information;

and the first sending module is used for sending the shared object information and the target browser route to a server so that the server shares the target browser route to a target object corresponding to the shared object information, and the target object displays the current interface information according to the target browser route.

8. An interface information sharing apparatus, applied to a server, comprising:

the system comprises an acquisition module, a target browser route and a search module, wherein the acquisition module is used for acquiring shared object information from a client and the target browser route, wherein the target browser route is a browser route corresponding to current interface information after the client acquires key information on a current interactive interface through monitoring and synchronizes the key information to the current browser route, the key information is used for information filtering, the current browser route is a URL address corresponding to the current interactive interface, and the current interface information comprises the current interactive interface and the key information;

and the second sending module is used for sharing the target browser route to a target object corresponding to the shared object information, so that the target object displays the current interface information according to the target browser route.

9. An electronic device comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus, characterized in that,

the memory is used for storing a computer program;

the processor is configured to perform the method steps of any of claims 1 to 6 by running the computer program stored on the memory.

10. A computer-readable storage medium, characterized in that the storage medium has stored therein a computer program, wherein the computer program is arranged to perform the method steps of any of claims 1 to 6 when run.