Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
FIG. 1 illustrates anexemplary system architecture 100 to which embodiments of the interface presentation methods or interface presentation apparatuses of the present application may be applied.
As shown in fig. 1, thesystem architecture 100 may includeterminals 101, 102, 103, anetwork 104, and aserver 105. Thenetwork 104 serves as a medium for providing communication links between theterminals 101, 102, 103 and theserver 105.Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may use theterminals 101, 102, 103 to interact with theserver 105 via thenetwork 104 to receive or send messages or the like. Theterminals 101, 102, 103 may have various client applications installed thereon, such as a mobile phone search application, an application market application, a map application, a web browser application, a shopping application, a search application, an instant messaging tool, a mailbox client, social platform software, and the like.
Theterminals 101, 102, 103 may be various electronic devices having a display screen and supporting information browsing, including but not limited to computers, smart phones, tablets, e-book readers, wearable smart devices, and the like.
Theserver 105 may be a server providing various services, such as a background server providing support for interface presentation of clients in theterminals 101, 102, 103. The background server can obtain request information sent by a terminal, inquire data matched with the request information in a preset data set as push data, push the push data to the terminal, enable the terminal to display the push data, obtain an operation performed by a user in an interface where the terminal displays the push data, and call a cloud plug-in or a local plug-in of the terminal, so that the cloud plug-in or the local plug-in runs and the terminal displays an interface where the operation is performed and then skips.
It should be understood that the number of terminals, networks, and servers in fig. 1 are merely illustrative. There may be any number of terminals, networks, and servers, as desired for an implementation.
With continued reference to FIG. 2, aflow 200 of one embodiment of an interface presentation method according to the present application is shown. The interface display method comprises the following steps:
step 201, acquiring request information sent by a terminal.
In this embodiment, the electronic device (for example, the server shown in fig. 1) on which the interface presentation method operates may receive request information sent by the terminal in a wired connection manner or a wireless connection manner, where the request information may include at least one of the following: the position information of the terminal, the information of a user logged in the terminal, the user information corresponding to the terminal identification and the equipment information of the terminal. The location information of the terminal may be acquired by a Global Positioning System (GPS), or may be acquired by a base station or a WI-FI signal through a network Positioning function of the terminal System itself. The terminal identifier may be Called User Identification number (CUID) or other device unique identifier, and a non-login User may use such identifier.
Step 202, querying data matched with the request information in a preset data set as push data.
In this embodiment, the electronic device (for example, the server shown in fig. 1) on which the interface presentation method operates may query, in a preset data set, data matching the request information acquired instep 201 as push data. The data in the data set is from the applications installed or not installed in the terminal. The method can be used for independently operating one application at the server side, or simultaneously operating a plurality of applications, and using the information, such as position information, included in the request information as the query condition to query the related data so as to acquire the pushed data, so that the user can simultaneously acquire the related data information of different applications through a single application. The application may be part or all of applications in an application market, for example, an application with a front download amount in a living service or shopping application in the application market may be selected to obtain data provided by the application; some applications can also be manually selected in advance to obtain data provided by the preselected applications; the data provided by all the applications can be acquired, meanwhile, the proportion of the data provided by each application viewed by the user is counted, and then the data provided by the applications with the proportion of the data viewed by the user exceeding the threshold value is acquired.
In some optional implementations of this embodiment, the request information may include location information of a terminal, and the querying, in a preset data set, data matching the request information as push data includes: and inquiring service content information of the service place as push data in a preset data set in response to the position information being within the service range of the service place acquired in advance. The service place refers to a place for providing services, and includes public institutions and some business places, such as all levels of government offices, commercial institutions, hospitals, schools, scenic spots, shopping malls, and the like. The service range of the service place may be a preset range centered on the service place, for example, the service range radiated by one hospital may be within five hundred meters of a square circle; the service scope of a service location may also be an area where many service locations are aggregated, such as a business district. The position of the service place can be obtained based on the data of the existing map software, and then the service range of the service place is determined based on the position of the service place, or the position of the service place can be obtained in a mode reported by the receiving terminal, and then the service range of the service place is determined based on the position of the service place. The receiving terminal may report information that a certain location is marked as a service location and is reported by a receiving user.
In some optional implementations of this embodiment, the request information may further include information of a user logged in the terminal or user information corresponding to the terminal identifier, and query, in a preset data set, service content information of the service location as push data, where the query may be: inquiring the service content information of the service place in a preset data set; and calculating the matching degree of the inquired service content information and the information of the user logged in the terminal or the user information corresponding to the terminal identification, and taking the service content information of which the matching degree exceeds a preset matching degree threshold value as push data. The matching degree threshold may be determined according to actual conditions, for example, when the queried service content information is more, the matching degree threshold may be higher, so as to avoid pushing too much data. The information of the user logged in the terminal or the user information corresponding to the terminal identifier usually contains information customized by the user or information of goods and services purchased by the user, so that the matching degree of the service content information and the user information can be calculated. Specifically, the matching degree of the service content information and the user information can be analyzed and calculated by establishing a machine learning model, and the parameters of the model are continuously improved along with the increase of the use condition of the user. For example, if a user buys movie tickets and the user-defined information includes that the user likes to travel, the matching degree of the service content information related to travel and movies is higher.
In some optional implementations of this embodiment, the priority of the push information itself and the matching degree may be considered in determining the order of the push information. The priority of the push information itself may be derived based on one or more of the following items of information: and the terminal recorded in the server history records requests to check the times of the push information, whether the push information is special push information or not and whether the push information is matched with the current time period or not. For example, if the current time is in the dining time period, the dining push information is matched with the current time period, and similarly, the current time period may be a afternoon tea time period or a leisure time period. The special push data refers to push data corresponding to a special service place, and the special service place comprises: scenic spot, hospital, market etc. correspond, and special propelling movement data includes: scenic spot admission tickets and evaluation information, hospital doctor introduction and registration payment related information, and market discount information. For example, if the service location is determined to be a scenic spot, the corresponding special pushed data is a scenic spot ticket and evaluation information.
Step 203, pushing the pushed data to the terminal, so that the terminal displays the pushed data.
In this embodiment, the electronic device (for example, the server shown in fig. 1) on which the interface presentation method operates pushes the pushed data queried instep 202 to the mobile terminal. The order of push can be determined according to the priority of the push information and the matching degree. Before the push data of the full version is pushed, each push data of the summary version can be pushed, and after the terminal receives the push data of the summary version, the terminal pushes the corresponding push data of the full version to the terminal when requesting the corresponding push data of the full version.
In some optional implementations of this embodiment, it may be determined whether the push data has corresponding presentation style information, and if so, the push data and the presentation style information are pushed to the terminal, so that the terminal presents the push data according to the presentation style information. The presentation style information may be obtained from a configuration file of a presentation style preset for a client on the terminal, the presentation style information includes information indicating a presentation style of the push data, and the server may control what style the client on the terminal uses to typeset the push data through the presentation style information. The push data may be sent in the form of a Hypertext Markup Language (HTML) file. If the push data does not have corresponding presentation style information, the push data can be presented through a plug-in or a WebView component.
And 204, acquiring the operation performed by the user in the interface for displaying the push data by the terminal.
In this embodiment, the electronic device (for example, the server shown in fig. 1) on which the interface presentation method operates obtains the operation performed by the user in the interface in which the terminal presents the above-mentioned pushed data instep 203. The operation performed by the user may be to acquire an operation type and position information of the operation corresponding to the operation. The user operates in the interface where the terminal presents the pushed data, which indicates that the user needs to interact, so that the interaction needs to be realized through a plug-in when the terminal does not install the application of the pushed data source.
Step 205, calling a cloud plug-in or a local plug-in of the terminal, so that the cloud plug-in or the local plug-in runs and displays an interface which skips after the operation is performed on the terminal.
In this embodiment, the server responds to the operation performed instep 204, and invokes a cloud plug-in or a local plug-in of the terminal, so that the cloud plug-in or the local plug-in runs and displays an interface to jump after the operation is performed on the terminal. And after the terminal displays the interface which skips after the operation, the terminal can also continue to acquire the operation performed by the interface which skips after the operation, displays the interface which skips after each operation, and the steps are circulated until the user closes the interface or quits the plug-in.
Cloud is a metaphor of network and internet. The cloud plug-in is based on an application/server A/S framework, adopts a technology similar to a virtual terminal, and isolates the human-computer interaction logic (an application interface, keyboard and mouse operations, touch screen operations and the like) of the application from the computing logic. The application virtualized by the server can be accessed through the cloud plug-in, the terminal only needs to transmit the operation information of the user to the server, namely the cloud, runs the virtual application, transmits the changed human-computer interaction logic (application interface) to the terminal, and renders and displays the virtual application in the terminal in real time, so that the user can obtain the access feeling as if the user runs the local application. The cloud plug-in may also be referred to as a cloud composite plug-in, because the applications of the push information sources are different, the server may virtualize a plurality of different applications, and the plurality of applications may all be accessed through the same cloud composite plug-in. The transmission of the interaction logic between the server and the terminal may be based on an Independent Computing Architecture (ICA) Protocol, a Remote Display Protocol (RDP), and the like, or may be a custom transmission Protocol when the number of interface operable elements is small. The transmission of interface data in the form of images can also be based on existing streaming protocols. Corresponding to the cloud plug-in, the local plug-in needs to be installed locally in the terminal, and most of the calculation logic of the local plug-in is still run locally in the terminal, for example, a plug-in center is arranged in part of applications, and plug-ins of other applications can be installed according to the selection of a user, so that part or all functions of other applications can be realized in one application. The plug-in may be implemented by calling an Application Programming Interface (API) or data capture technology of other applications.
In some optional implementations of this embodiment, the running environment of the local plug-in or the cloud plug-in is provided by an application installed in the terminal, and the application providing the running environment of the local plug-in or the cloud plug-in may be referred to as a host application of the local plug-in or the cloud plug-in.
In some optional implementations of this embodiment, it may be determined whether a local plug-in exists in an application from which the push data is sourced; if not, calling a cloud plug-in to enable the cloud plug-in to run and display an interface which skips after the operation on the terminal; if so, calling the local plug-in to enable the local plug-in to run and display the interface which is jumped after the operation is carried out on the terminal, or providing a download address of the local plug-in for the terminal to install the local plug-in and calling the local plug-in to enable the local plug-in to run and display the interface which is jumped after the operation is carried out on the terminal. And judging whether the application from which the push data is sourced has a local plug-in or not, and searching whether the application from which the push data is sourced has a corresponding local plug-in or not through a preset list of local plug-ins.
In some optional implementations of this embodiment, the invoking the cloud plug-in to enable the cloud plug-in to run and display the interface that jumps after the operation is performed on the terminal may include: calling a cloud plug-in; acquiring an operation type corresponding to the operation and position information of the operation; running the application from which the push data comes at the cloud end, and performing simulation operation according to the operation type and the position information to acquire an interface which skips after the operation; and sending the interface which is jumped after the operation to the terminal, so that the interface which is jumped after the operation is displayed on the terminal. The above operation types include at least one of: click, hold, drag, double click, slide, zoom. The position information of the operation may be a coordinate position of an interface where the operation is performed, or may be an operable object corresponding to the operation, and the operable object includes at least one of the following: buttons, lists, slide bars. The sending of the interface to the terminal may be sending interface display data, which is typically image data, and interface interoperable data, which is data related to an operable object in the interface, to the terminal. And the client on the subsequent terminal can carry out interactive operation processing according to the interactive operation data of the interface.
With continued reference to fig. 3, fig. 3 is a schematic diagram of an application scenario of the interface presentation method according to the present embodiment. In the application scenario of fig. 3, the server pushes data to the terminal, the terminal displays the pushed data as shown in fig. 3, and then the server obtains an operation performed by the user in an interface where the terminal displays the pushed data, and invokes a cloud plug-in or a local plug-in of the terminal, so that the cloud plug-in or the local plug-in operates and displays an interface where the operation is performed and then a jump is performed at the terminal. The operation performed may be a selection operation on a list in the figure, a click zoom-in/zoom-out operation on a picture, a click operation on a button, and a slide operation in the interface.
According to the method provided by the embodiment of the application, the cloud plug-in or the local plug-in is called, so that the cloud plug-in or the local plug-in runs and displays the interface which skips after the operation is performed on the terminal, the interface display by using a plug-in mechanism is realized, the excessive application of the terminal installation is avoided, and the resource of the terminal is saved.
With further reference to FIG. 4, aflow 400 of yet another embodiment of an interface presentation method is shown. The interfacepresentation method flow 400 includes the following steps:
step 401, sending request information to a server.
In this embodiment, the electronic device (for example, the terminal shown in fig. 1) on which the interface presentation method operates sends request information to the server. The request information may include at least one of: the position information of the terminal, the information of a user logged in the terminal, the user information corresponding to the terminal identification and the equipment information of the terminal. The location information of the terminal may be acquired by a Global Positioning System (GPS), or may be acquired by a base station or a WI-FI signal through a network Positioning function of the terminal System itself. The terminal identifier may be Called user identification number (CUID) or other device unique identifier, which may be used by a non-login user.
In some optional implementations of this embodiment, the request information may include location information of the terminal. And sending request information to the server, wherein the request information may be sent to the server in response to the position information being within a service range of a service place acquired in advance, so as to request the server to inquire and push service content information of the service place in a preset data set. The service place refers to a place for providing services, and includes public institutions and some business places, such as all levels of government offices, commercial institutions, hospitals, schools, scenic spots, shopping malls, and the like. The service range of the service place may be a preset range centered on the service place, for example, the service range radiated by one hospital may be within five hundred meters of a square circle; the service scope of a service location may also be an area where many service locations are aggregated, such as a business district. The position of the service place can be obtained based on the data of the existing map software, and then the service range of the service place is determined based on the position of the service place, or the position of the service place can be obtained in a mode reported by the receiving terminal, and then the service range of the service place is determined based on the position of the service place. The receiving terminal may report information that a certain location is marked as a service location and is reported by a receiving user.
Step 402, receiving and displaying the push data pushed by the server.
In this embodiment, the electronic device (for example, the terminal shown in fig. 1) on which the interface presentation method operates receives and presents push data returned by the server according to the request information instep 401, where the push data includes data that is matched with the request information and is queried by the server in a preset data set, and the data in the data set is derived from a locally installed or uninstalled application. The server can independently run a certain application or simultaneously run a plurality of applications, and the information, such as position information, included in the request information is used as a query condition to query the related data to acquire the pushed data, so that a user can simultaneously acquire the related data information of different applications through a single application. The application may be part or all of applications in an application market, for example, an application with a front download amount in a living service or shopping application in the application market may be selected to obtain data provided by the application; some applications can also be manually selected in advance to obtain data provided by the preselected applications; the data provided by all the applications can be acquired, meanwhile, the proportion of the data provided by each application viewed by the user is counted, and then the data provided by the applications with the proportion of the data viewed by the user exceeding the threshold value is acquired. Before the terminal receives the push data of the full version, the terminal may also receive the push data of the summary version, and after receiving the push data of the summary version, the terminal may request the server to push the corresponding push data of the full version.
In some optional implementations of this embodiment, the request information may further include information of a logged-in user or user information corresponding to a terminal identifier, and the push data includes: and the matching degree exceeds the service content information of a preset matching degree threshold value, wherein the matching degree is calculated by the server by inquiring the service content information of the service place in a preset data set and according to the inquired service content information and the information of the user logged in the terminal or the user information corresponding to the terminal identification. The matching degree threshold may be determined according to actual conditions, for example, when the queried service content information is more, the matching degree threshold may be higher, so as to avoid pushing too much data. The information of the logged-in user or the user information corresponding to the terminal identification usually contains information customized by the user or information of goods and services purchased by the user, so that the matching degree of the service content information and the user information can be calculated. Specifically, the matching degree of the service content information and the user information can be analyzed and calculated by establishing a machine learning model, and the parameters of the model are continuously improved along with the increase of the use condition of the user. For example, if a user buys movie tickets and the user-defined information includes that the user likes to travel, the matching degree of the service content information related to travel and movies is higher.
In some optional implementations of this embodiment, the determining of the order of the push information may comprehensively consider the priority of the push information itself and the matching degree. The priority of the push information itself may be derived based on one or more of the following items of information: and the terminal recorded in the server history records requests to check the times of the push information, whether the push information is special push information or not and whether the push information is matched with the current time period or not. For example, if the current time is in the dining time period, the dining push information is matched with the current time period, and similarly, the current time period may be a afternoon tea time period or a leisure time period. The special push data refers to push data corresponding to a special service place, and the special service place comprises: scenic spot, hospital, market etc. correspond, and special propelling movement data includes: scenic spot admission tickets and evaluation information, hospital doctor introduction and registration payment related information, and market discount information. For example, if the service location is determined to be a scenic spot, the corresponding special pushed data is a scenic spot ticket and evaluation information.
In some optional implementations of this embodiment, it may be determined whether the push data has corresponding presentation style information, and if so, the push data is presented according to the presentation style information. The presentation style information may be obtained from a configuration file of a presentation style preset for the client, where the presentation style information includes information indicating a presentation style of the push data, and the client on the terminal may determine which style to use to typeset the push data according to the presentation style information. The received push data may be in the form of a Hypertext markup language (HTML) file. If the push data does not have corresponding presentation style information, the push data can be presented through a plug-in or a WebView component.
And 403, collecting the operation performed by the user in the interface for displaying the push data.
In this embodiment, the terminal collects the operation performed by the user in the interface displaying the push data instep 402. The operation performed by the user may be to acquire an operation type and position information of the operation corresponding to the operation. The user operates in the interface where the terminal presents the pushed data, which indicates that the user needs to interact, so that the interaction needs to be realized through a plug-in when the terminal does not install the application of the pushed data source.
And step 404, running a local plug-in or a cloud plug-in to show an interface which skips after the operation is performed.
In this embodiment, the terminal responds to the operation collected instep 403, and runs the local plug-in or the cloud plug-in to present the interface that jumps after the operation is performed. And after the terminal displays the interface which skips after the operation, the terminal can continue to collect the operation performed by the interface which skips after the operation, displays the interface which skips after each operation, and the steps are circulated until the user closes the interface or quits the plug-in.
Cloud is a metaphor of network and internet. The cloud plug-in is based on an application/server A/S framework, adopts a technology similar to a virtual terminal, and isolates the human-computer interaction logic (an application interface, keyboard and mouse operations, touch screen operations and the like) of the application from the computing logic. The application virtualized by the server can be accessed through the cloud plug-in, the terminal only needs to transmit the operation information of the user to the server, namely the cloud, runs the virtual application, transmits the changed human-computer interaction logic (application interface) to the terminal, and renders and displays the virtual application in the terminal in real time, so that the user can obtain the access feeling as if the user runs the local application. The cloud plug-in may also be referred to as a cloud composite plug-in, because the applications of the push information sources are different, the server may virtualize a plurality of different applications, and the plurality of applications may all be accessed through the same cloud composite plug-in. The transmission of the interaction logic between the server and the terminal may be based on an Independent Computing Architecture (ICA) Protocol, a Remote Display Protocol (RDP), and the like, or may be a custom transmission Protocol when the number of interface operable elements is small. The transmission of interface data in the form of images can also be based on existing streaming protocols. Corresponding to the cloud plug-in, the local plug-in needs to be installed locally in the terminal, and most of the calculation logic of the local plug-in is still run locally in the terminal, for example, a plug-in center is arranged in part of applications, and plug-ins of other applications can be installed according to the selection of a user, so that part or all functions of other applications can be realized in one application. The plug-in may be implemented by calling an Application Programming Interface (API) or data capture technology of other applications.
In some optional implementations of this embodiment, the execution environment of the native plug-in or the cloud plug-in is provided by an installed application, and an application providing the execution environment of the native plug-in or the cloud plug-in may be referred to as a host application of the native plug-in or the cloud plug-in.
In some optional implementations of this embodiment, it may be determined whether a local plug-in exists in an application from which the push data is sourced; if not, running the cloud plug-in to show the interface which jumps after the operation is carried out; if so, operating the local plug-in to show the interface which skips after the operation, or acquiring the download address of the local plug-in, installing and operating the local plug-in to show the interface which skips after the operation. The determining whether the application from which the push data originates has the local plug-in may be that the terminal determines whether the local plug-in is installed in the locally installed application or the local plug-in of the application from which the push data originates is installable by searching a configuration file of the locally installed application.
In some optional implementations of this embodiment, running the cloud plug-in to reveal an interface that jumps after performing the operation includes: running a cloud plug-in; sending the operation type corresponding to the operation and the position information of the operation to a server; and receiving and displaying an interface which is sent by the server and skips after the operation, wherein the interface which skips after the operation is obtained by running the application from which the push data is sourced at the cloud and performing simulation operation according to the operation type and the position information. The above operation types include at least one of: click, hold, drag, double click, slide, zoom. The position information of the operation may be a coordinate position of an interface where the operation is performed, or may be an operable object corresponding to the operation, and the operable object includes at least one of the following: buttons, lists, slide bars. The interface sent by the terminal receiving server can receive interface display data and interface interoperable data, the interface display data is usually image data, and the interoperable data is data related to an operable object in the interface. And the subsequent client can carry out interactive operation processing according to the interface interactive operation data.
According to the method provided by the embodiment of the application, the interface which skips after operation is displayed by running the cloud plug-in or the local plug-in, the display of the interface by using a plug-in mechanism is realized, excessive application of the terminal installation is avoided, and the resources of the terminal are saved.
With further reference to fig. 5, as an implementation of the method shown in the above-mentioned figures, the present application provides an embodiment of an interface presentation apparatus, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 2, and the apparatus may be specifically applied to various electronic devices.
As shown in fig. 5, theinterface display apparatus 500 according to the present embodiment includes: a requestinformation obtaining unit 501, aquery unit 502, apush unit 503, anoperation obtaining unit 504, and a plug-incalling unit 505. The requestinformation acquiring unit 501 is configured to acquire request information sent by a terminal; aquery unit 502, configured to query, as push data, data in a preset data set, where the data in the data set is derived from an application installed or not installed in the terminal, and the data is matched with the request information; a pushingunit 503, configured to push the pushed data to the terminal, so that the terminal displays the pushed data; anoperation obtaining unit 504, configured to obtain an operation performed by a user in an interface where the terminal displays the push data; a plug-incalling unit 505, configured to call a cloud plug-in or a local plug-in of the terminal, so that the cloud plug-in or the local plug-in runs and displays an interface that jumps after the operation is performed on the terminal.
In some optional implementations of this embodiment, the plug-in invokingunit 505 is further configured to: judging whether the application from which the push data comes has a local plug-in or not; if not, calling a cloud plug-in to enable the cloud plug-in to run and display an interface which skips after the operation on the terminal; if so, calling the local plug-in to enable the local plug-in to run and display the interface which is jumped after the operation is carried out on the terminal, or providing a download address of the local plug-in for the terminal to install the local plug-in and calling the local plug-in to enable the local plug-in to run and display the interface which is jumped after the operation is carried out on the terminal.
In some optional implementations of this embodiment, the plug-in invokingunit 505 is further configured to: calling a cloud plug-in; acquiring an operation type corresponding to the operation and position information of the operation; running the application from which the push data comes at the cloud end, and performing simulation operation according to the operation type and the position information to acquire an interface which skips after the operation; and sending the interface which is jumped after the operation to the terminal, so that the interface which is jumped after the operation is displayed on the terminal.
In some optional implementations of this embodiment, the running environment of the local plug-in or the cloud plug-in is provided by an application installed in the terminal.
In some optional implementations of this embodiment, the pushingunit 502 is further configured to: judging whether the push data has corresponding presentation style information; if so, pushing the push data and the presentation style information to the terminal, so that the terminal presents the push data according to the presentation style information.
In some optional implementations of this embodiment, the request information may include location information of the terminal, and thequerying unit 502 is further configured to: and inquiring service content information of the service place as push data in a preset data set in response to the position information being within the service range of the service place acquired in advance.
In some optional implementations of this embodiment, the request information further includes information of a user logged in the terminal or user information corresponding to a terminal identifier, and thequerying unit 502 is further configured to: inquiring the service content information of the service place in a preset data set; and calculating the matching degree of the inquired service content information and the information of the user logged in the terminal or the user information corresponding to the terminal identification, and taking the service content information of which the matching degree exceeds a preset matching degree threshold value as push data.
With further reference to fig. 6, as an implementation of the method shown in the above-mentioned figures, the present application provides an embodiment of another interface presentation apparatus, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 4, and the apparatus may be specifically applied to various electronic devices.
As shown in fig. 6, theinterface display apparatus 600 according to the present embodiment includes: a requestinformation sending unit 601, apresentation unit 602, anoperation acquisition unit 603, and a plug-inexecution unit 604. The requestinformation sending unit 601 is configured to send request information to a server; apresentation unit 602, configured to receive and present push data pushed by the server, where the push data includes data that is queried by the server in a preset data set and matches the request information, and the data in the data set is derived from a locally installed or uninstalled application; anoperation acquisition unit 603, configured to acquire an operation performed by a user in an interface displaying the push data; the plug-inrunning unit 604 is configured to run a local plug-in or a cloud plug-in to show an interface that jumps after the operation is performed.
In some optional implementations of this embodiment, the plug-inrunning unit 604 is further configured to: running a cloud plug-in; sending the operation type corresponding to the operation and the position information of the operation to a server; and receiving and displaying an interface which is sent by the server and skips after the operation, wherein the interface which skips after the operation is obtained by running the application from which the push data is sourced at the cloud and performing simulation operation according to the operation type and the position information.
In some optional implementations of this embodiment, the plug-inrunning unit 604 is further configured to: judging whether the application from which the push data comes has a local plug-in or not; if not, running the cloud plug-in; and if so, operating the local plug-in or acquiring the download address of the local plug-in, and installing and operating the local plug-in.
In some optional implementations of this embodiment, the execution environment of the local plug-in or the cloud plug-in is provided by an installed application.
In some optional implementations of this embodiment, the presentingunit 602 is further configured to: judging whether the push data has corresponding presentation style information; and if so, receiving the push data and the presentation style information pushed by the server, and presenting the push data according to the presentation style information.
In some optional implementations of this embodiment, the request information includes location information, and the push data includes service content information of the service location, which is queried by the server in a preset data set in response to the location information being within a service range of the service location acquired in advance.
In some optional implementations of this embodiment, the request information further includes information of a logged-in user or user information corresponding to a terminal identifier, and the push data includes: and the matching degree exceeds the service content information of a preset matching degree threshold value, wherein the matching degree is calculated by the server by inquiring the service content information of the service place in a preset data set and according to the inquired service content information and the information of the user logged in the terminal or the user information corresponding to the terminal identification.
Referring now to FIG. 7, shown is a block diagram of acomputer system 700 suitable for use in implementing a server according to embodiments of the present application.
As shown in fig. 7, thecomputer system 700 includes a Central Processing Unit (CPU)701, which can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)702 or a program loaded from astorage section 708 into a Random Access Memory (RAM) 703. In theRAM 703, various programs and data necessary for the operation of thesystem 700 are also stored. TheCPU 701, theROM 702, and theRAM 703 are connected to each other via abus 704. An input/output (I/O)interface 705 is also connected tobus 704.
The following components are connected to the I/O interface 705: an input portion 706 including a keyboard, a mouse, and the like; anoutput section 707 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; astorage section 708 including a hard disk and the like; and acommunication section 709 including a network interface card such as a LAN card, a modem, or the like. Thecommunication section 709 performs communication processing via a network such as the internet. Adrive 710 is also connected to the I/O interface 705 as needed. Aremovable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on thedrive 710 as necessary, so that a computer program read out therefrom is mounted into thestorage section 708 as necessary.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through thecommunication section 709, and/or installed from theremovable medium 711. The computer program, when executed by a Central Processing Unit (CPU)701, performs the above-described functions defined in the method of the present application.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present application may be implemented by software or hardware. The described units may also be provided in a processor, and may be described as: a processor comprises a request information acquisition unit, a query unit, a push unit, an operation acquisition unit and a plug-in calling unit. The names of these units do not in some cases form a limitation on the units themselves, for example, a push unit may also be described as a "unit that pushes the push data to the terminal so that the terminal displays the push data".
As another aspect, the present application also provides a non-volatile computer storage medium, which may be the non-volatile computer storage medium included in the apparatus in the above-described embodiments; or it may be a non-volatile computer storage medium that exists separately and is not incorporated into the terminal. The non-transitory computer storage medium stores one or more programs that, when executed by a device, cause the device to: acquiring request information sent by a terminal; querying data matched with the request information in a preset data set as push data, wherein the data in the data set is sourced from an installed or uninstalled application of the terminal; pushing the pushed data to the terminal to enable the terminal to display the pushed data; acquiring operation performed by a user in an interface for displaying the pushed data by the terminal; and calling a cloud plug-in or a local plug-in of the terminal to enable the cloud plug-in or the local plug-in to run and display an interface which skips after the operation on the terminal.
The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by a person skilled in the art that the scope of the invention as referred to in the present application is not limited to the embodiments with a specific combination of the above-mentioned features, but also covers other embodiments with any combination of the above-mentioned features or their equivalents without departing from the inventive concept. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.