HK1237451B - Information display method and device - Google Patents

Description

Information display method and device

Technical Field

The present application relates to the field of computer technology, and in particular to an information display method and device.

Background Art

As various types of service information on the Internet continue to increase, the service information that users pay attention to on their user terminals every day is increasing and becoming more and more dispersed. Wherein, the user terminals include but are not limited to: smartphones, tablets, smart watches, personal computers, etc.

For example, users may check headlines through information apps every day, shop through shopping apps, follow stock trends through financial apps, interact with friends through social apps, and so on.

Currently, user terminals need to obtain and display corresponding service information based on the user's gradual operation of the application. However, since the service information that the user is interested in may be large and scattered, the user may have to spend a lot of time using each corresponding application. Accordingly, the user terminal cannot quickly display the service information that the user is interested in.

Summary of the Invention

The embodiments of the present application provide an information display method and device to solve the problem in the prior art that a user terminal cannot quickly display service information that the user is concerned about.

The embodiments of the present application provide an information push method and apparatus to solve the problem in the prior art that a user terminal cannot quickly display service information of interest to the user.

An information display method provided in an embodiment of the present application includes:

Monitoring whether the user terminal is in the information push scenario according to the information of the information push scenario;

When it is monitored that the user terminal is in the information push scenario, service information obtained according to the user's first behavior data is displayed.

An information push method provided in an embodiment of the present application includes:

Get information about information push scenarios;

monitoring whether the user terminal is in the information push scenario according to the information of the information push scenario;

When it is monitored that the user terminal is in the information push scenario, service information is pushed to the user terminal.

An embodiment of the present application provides an information display device, comprising:

A monitoring module, configured to monitor whether a user terminal is in the information push scenario based on information about the information push scenario;

The display module is used to display the service information obtained according to the user's first behavior data when the monitoring module monitors that the user terminal is in the information push scenario.

An information push device provided in an embodiment of the present application includes:

The acquisition module is used to obtain information about the information push scenario;

A monitoring module, configured to monitor whether the user terminal is in the information push scenario based on the information of the information push scenario;

The push module is used to push service information to the user terminal when the monitoring module monitors that the user terminal is in the information push scenario.

Through at least one of the above-mentioned technical solutions, the embodiment of the present application can enable the user terminal to automatically obtain and display service information that the user is likely to pay attention to in the current information push scenario based on the user's application usage habits in different information push scenarios, without waiting for the user to actively use the application. Therefore, the service information that the user is interested in can be quickly displayed to the user.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

FIG1 is an information display process provided by an embodiment of the present application;

FIG2 is a display template for displaying service information in actual application, provided by an embodiment of the present application;

FIG3 is a schematic diagram of displaying service information according to the display template in FIG2 , provided in an embodiment of the present application;

FIG4 is provided in an embodiment of the present application, corresponding to the information push process of FIG1 ;

FIG5 is a diagram of the functional architecture of an application provided by an embodiment of the present application, when the information display method and information push method are implemented in an application in actual application;

FIG6 is a schematic structural diagram of an information display device provided in an embodiment of the present application;

FIG7 is a schematic diagram of the structure of the information push device provided in an embodiment of the present application.

DETAILED DESCRIPTION

To make the purpose, technical solutions, and advantages of this application more clear, the technical solutions of this application will be clearly and completely described below in conjunction with the specific embodiments of this application and the corresponding drawings. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

FIG1 is an information display process provided by an embodiment of the present application, which specifically includes the following steps:

S101: Monitoring whether a user terminal is in the information push scenario according to information of the information push scenario.

The execution subject of the information display process in Figure 1 may be the user terminal. The user terminal includes but is not limited to: a personal computer, a mobile phone, a tablet computer, a smart watch, a vehicle-mounted mobile station, etc. The execution subject does not constitute a limitation of this application.

In the embodiments of the present application, different information push scenarios may be scenarios in which the user terminal is located when different user behavior data is generated. The information push scenario described in FIG1 may be a specific information push scenario among the different information push scenarios. For ease of description, the user behavior data corresponding to the information push scenario described in FIG1 is referred to as the user's first behavior data. In other words, the information push scenario described in FIG1 may be the scenario in which the user terminal is located when the user's first behavior data is generated.

S102: When it is monitored that the user terminal is in the information push scenario, service information obtained according to the user's first behavior data is displayed.

Generally, a user can use an application on a user terminal to obtain service information provided by a server for a service corresponding to the application. The service information may refer to content data that can be displayed on the user terminal (reflecting the visual interface of the service), or an application interface that can be used by the user terminal (reflecting the business logic and functions of the service), etc.

For example, a user can use a shopping app to obtain information about various products; a user can use a travel app to check flight and hotel information and make reservations; a user can use an information app to check the latest news and comment on it; a user can use a reading app to check information about serial novels and download them, etc. The embodiments of this application are mainly elaborated based on the user's behavior of "using applications on the user terminal".

After a user uses an application, user behavior data may be generated on the user terminal. For example, user behavior data may include at least one of the following: the name of the application used on the user terminal, the application type to which the application belongs, the start time of a particular application use, the duration of that application use, the geographic location of the user terminal when using the application, behavioral content data generated when using the content, and messages exchanged between the user terminal and the server during the user's use. Table 1 below shows a portion of the user behavior data generated by a user terminal on November 11, 2014:

Table 1

As you can see, Table 1 contains a total of 5 rows of data, each row of data is a set of user behavior data.

In an embodiment of the present application, the user's behavioral habits can be analyzed based on the generated user behavior data, and it can be inferred that in different scenarios (the scenario can be the information push scenario), the application that the user is likely to use on the user terminal.

More specifically, users use applications to obtain corresponding service information. In an embodiment of the present application, in order to realize intelligent services and improve user experience, there is no need to wait for users to actively use the application. Instead, based on the information push scenario in which the user terminal is located and the corresponding user's first behavior data, the application actively obtains and displays for the user the service information that the user may want to obtain in this information push scenario, or other information similar to the service information. In this way, the user does not have to actively use the application every time to obtain the corresponding service information, but can let the user terminal and/or server and/or other devices do it for the user.

The information push scenario and the method for determining the information push scenario are described in detail below.

Since similar applications can provide users with similar service information, the application category to which each application belongs can be used as the primary basis to analyze the user's usage habits for each category of applications. That is, for each category of applications, the time, time period, and/or geographical location at which users tend to use the application can be analyzed. In the embodiment of the present application, the information push scenario can quantitatively reflect the above user habits, and the information of the information push scenario is used to determine whether the user terminal is in the information push scenario.

For a determined information push scenario, assuming that the user frequently uses a certain application or a certain type of application in the information push scenario, the information of the information push scenario may include: the time when the user frequently uses the application or the type of application in the information push scenario (hereinafter referred to as the time), the time period during which the user uses the application or the type of application each time (hereinafter referred to as the time period), and the geographical location of the user terminal (hereinafter referred to as the geographical location).

In practical applications, the geographical location can be expressed by longitude and latitude, for example, the geographical location of 30 degrees north latitude and 120 degrees east longitude can be expressed as: (30.00, 120.00); it can also be expressed by specific place names, for example, the geographical location can be expressed by city names such as Beijing, Shanghai, Hangzhou, etc.

Continuing to use Table 1 as an example, according to each application used by the user in Table 1, the information push scenario corresponding to each application can be determined as shown in Table 2 below:

Application Name Application Category time Geographical location Shopping apps Shopping 2014-11-11 01:35 30.00, 120.00 Lottery App Lottery 2014-11-11 01:50 30.00, 120.00 Lottery App Lottery 2014-11-11 12:00 30.00, 120.00 Travel Applications Air travel 2014-11-11 14:30 30.00, 120.00 News App Information 2014-11-11 19:30 30.00, 121.00

Table 2

As you can see, Table 2 contains a total of 5 rows of data, each row of data corresponds to an information push scenario.

In the embodiment of the present application, an information push scenario can be determined based on each row of data in Table 1, corresponding to a row of data in Table 2. For example, for the information push scenario determined based on the first row of data in Table 1, the user frequently uses the "Shopping Application" application in this information push scenario. The information of this information push scenario is the time (01:35) and the geographic location (30:00, 120:00), corresponding to the first row of data in Table 2. It should be noted that generally speaking, user behavior on the user terminal is performed on a daily cycle. Accordingly, regarding the time, only the hour, minute, and second parts can be considered, without considering the year, month, and day parts. In this case, the same information push scenario also occurs on a daily cycle.

Furthermore, the information push scenario corresponding to the application category may be determined according to the application category to which each application used by the user belongs.

Specifically, for at least one application category, the information push scenarios corresponding to the applications belonging to the at least one application category may be merged to re-determine a larger information push scenario as the information push scenario corresponding to the at least one application category.

More specifically, probability statistics can be performed on the accumulated data in Table 2 (a table similar to Table 2 can be generated based on daily user behavior data, and the collection of data in multiple such tables can be referred to as the accumulated data in Table 2). After merging the information push scenarios in the accumulated data in Table 2 according to application category, the information push scenario corresponding to the application category can be determined, as shown in Table 3 below:

Application Category Time period Geographical location Shopping, lottery 00:00～02:00 30.00, 120.00 Lottery 11:00～13:00 30.00, 120.00 Air travel 2:00 PM - 3:00 PM 30.00, 120.00 Information 18:00～23:00 30.00, 120.00

Table 3

In the embodiment of the present application, each row of data in Table 3 can be used as a determined information push scenario. For example, for the information push scenario based on the first row of data in Table 3, the user frequently uses shopping and lottery applications in this information push scenario. The information of this information push scenario is the time period (00:00-02:00) and the geographical location (30:00, 120:00).

In the embodiment of the present application, whether the user terminal is in the information push scenario can be monitored based on at least one information in the information of the information push scenario.

The information push scenarios identified in Table 3 are used as examples.

In Example 1, assuming monitoring is performed based on time periods, if the current time falls within the time period of a certain information push scenario, then it can be considered that the user terminal is currently in that information push scenario. For example, assuming the current time is 01:00, then it can be considered that the user terminal is currently in the information push scenario corresponding to the first row of data in Table 3.

Example 2: Assuming that monitoring is performed based on time period and geographic location, if the current time is monitored to fall within the time period of a certain information push scenario, it can be considered that the user terminal is currently in that information push scenario. For example, assuming that the current time is monitored to be 01:00 and the current geographic location of the user terminal is (40:00, 120:00), although the current time falls within the time period of 00:00-02:00 in Table 3, since the current geographic location of the user terminal is different from the geographic location (30:00, 120:00) corresponding to the time period of 00:00-02:00, it can be considered that the user terminal is not currently in the information push scenario corresponding to the first row of data in Table 3.

In addition, for the information push scenarios identified in Table 2, since the information of the information push scenarios includes time, monitoring can also be performed based on time. If the current time is monitored to be the time of a certain information push scenario, it can be considered that the user terminal is currently in that information push scenario. For example, if the current time is monitored to be 01:35, it can be considered that the user terminal is currently in the information push scenario corresponding to the first row of data in Table 2.

In an embodiment of the present application, based on the user's first behavior data, it can be inferred that when the user terminal is in the information push scenario, the user may want to obtain service information, and then the service information can be obtained and displayed.

Through the above method, the user terminal can automatically obtain and display the service information that the user is likely to pay attention to in the current information push scenario based on the user's application usage habits in different information push scenarios, without waiting for the user to actively use the application. Therefore, the service information that the user is interested in can be quickly displayed to the user.

The following describes a method for obtaining service information based on the user's first behavior data and displaying the obtained service information.

In an embodiment of the present application, the service information may be obtained from a server of an application on the user terminal. Specifically, the user terminal may send relevant information of the user's first behavior data to the server, and receive service information pushed by the server based on the relevant information.

When the user terminal is detected to be in the information push scenario, the user terminal can obtain service information from the server and display the obtained service information. This method is more suitable for scenarios where real-time requirements are not high. The user terminal can also obtain service information from the server in advance and save the obtained service information locally. Then, when the user terminal is detected to be in the information push scenario, it can not interact with the server, but instead search for the locally saved service information and display the service information. This method has high real-time performance. The service information can be determined based on the relevant information of the user's first behavior data.

Furthermore, the relevant information of the user's first behavior data includes at least one of the following: information of the information push scenario; behavior content data contained in the user's first behavior data; and application category corresponding to the user's first behavior data.

When the relevant information includes information about the information push scenario, the service information may include service information mapped to the information about the information push scenario. The mapping relationship between each information push scenario and each service information may be specified by the server or the user terminal and is not limited in this application.

When the relevant information includes behavior content data included in the user's first behavior data, the service information may include service information related to the behavior content data.

For example, when the behavior content data is "booking a flight ticket", since the user may also book a hotel after booking a flight ticket, and may pay attention to the weather conditions on the day of the flight, the service information related to "booking a flight ticket" may be hotel information, weather forecast information and other service information.

When the relevant information includes the application category corresponding to the first user behavior data, the service information may include: service information whose application category is the same as or related to the application category corresponding to the first user behavior data.

Still using the above example to illustrate, the application category corresponding to "booking air tickets" may be the air travel category, and the service information may be service information belonging to the air travel category, or service information belonging to the weather category, and so on.

For another example, when it is monitored that the current user terminal is in the information push scenario corresponding to the second row of data in Table 3, the user's first behavior data can be the third row of data in Table 1, and the information of the information push scenario can be the time period (11:00-13:00) and/or the geographical location (30.00, 120.00). The behavior content data contained in the user's first behavior data can be "browsing the lottery results of the Double Color Ball", and the application category corresponding to the user's first behavior data can be "lottery category". Then, when the user terminal is monitored to be in the information push scenario, the service information displayed can be: service information belonging to the "lottery category" or to application categories related to the "lottery category" (such as "financial management category", etc.).

For another example, when it is monitored that the current user terminal is in the information push scenario corresponding to the fourth row of data in Table 3, the corresponding user behavior data may be the last row of data in Table 1, the information of the information push scenario may be the time period (18:00-23:00) and/or the geographic location (30.00, 120.00), the behavior content data contained in the user behavior data may be "browsing headlines", and the application category corresponding to the user behavior data may be "information category", then the service information displayed on the user terminal when it is monitored that the user terminal is in the information push scenario may be: service information belonging to the "information category" or to an application category related to the "information category" (such as "stock category", etc.).

It should be noted that the service information described in this application may be obtained by the server from at least one third-party server based on the relevant information, or may be generated by the server itself. The third-party server may be a server provided by a third-party service provider.

Furthermore, receiving the service information pushed by the server according to the relevant information specifically includes: receiving the service information in the service information format pushed by the server according to the relevant information and the service information format.

Continuing with the previous example, the server retrieves information categorized as "news" based on the relevant information. It can also further filter headlines from this information and push them to the user terminal as service information for display. Based on the user's first action data, this service information is likely what the user is currently looking for. The user does not need to actively use the app to access this service information, thereby improving the efficiency of obtaining service information on the user terminal and enhancing the user experience.

It should be noted that the service information format can be defined on the server side or on the user terminal side. The embodiments of the present application do not limit the specific content of the service information format. In practical applications, data formats such as Card Model Language (CML), Extensible Markup Language (XML), or Document Object Model (DOM) can be used as the service information format.

Let's take CML as an example of the service information format. CML is a data format similar to XML. The server can format the service information according to the CML format specification. After the user terminal obtains the processed service information, it can display it in a corresponding user interface (UI) or view. The displayed interface effect is mainly based on various card styles. The current CML format specification is shown below for reference (content in curly brackets):

In an embodiment of the present application, the user terminal may filter the obtained service information before displaying it. Then, in step S102, displaying the service information may specifically include: filtering the service information obtained based on the user's first behavior data according to the information filtering rule and then displaying it.

For example, if the application category corresponding to the user's first action data is "information," the user terminal may obtain service information belonging to "information" and/or "stock" from the server. However, in actual application, the user may not be interested in "stock" service information. In this case, the user terminal can filter out the "information" service information from the obtained service information and display it. This can further improve the user experience.

In actual applications, the above-mentioned service information filtering step can be performed by the server, the user terminal, or both. Furthermore, since the more service information a user terminal receives, the higher the data traffic charges incurred by the user, the above-mentioned service information filtering step can preferably be performed by the server. In this way, the user terminal only needs to receive the filtered service information, which can reduce the user's data traffic charges.

Furthermore, the information filtering rules may be automatically set by the server or the user terminal according to each information push scenario, or may be manually set by the user for the server or the user terminal, so that the user can obtain desired service information.

The information filtering rule may include: filtering service information whose corresponding application category is consistent with a set application category from the service information obtained according to the user's first behavior data.

The information filtering rules may specifically include one or more groups of information filtering conditions, wherein each group of information filtering conditions may correspond to an information push scenario. For example, Table 4 shows a group of information filtering conditions that have been set in actual applications:

Table 4

It can be seen that the information filtering conditions in Table 4 can be determined based on the user behavior data corresponding to the first row of data in Table 1, or can also be determined based on the information push scenario corresponding to the first row of data in Table 3. In this application scenario, the user is likely to use shopping applications. Therefore, service information related to shopping and/or whose time intervals match the time periods in Table 4 and/or whose geographic locations match the geographic locations in Table 4 can be filtered out and displayed to the user terminal. In this way, the user can directly use the service information without using the shopping application, thereby increasing the channels for obtaining service information on the user terminal.

In addition, according to the above description, the information filtering conditions in Table 4 can also be manually set by the user. For this information push scenario, assuming that the user does not want to obtain shopping-related service information in this information push scenario in the future, but wants to obtain information-related service information, the user can also change the data content corresponding to the "Application Category" in Table 4 from "Shopping" to "Info" through the user terminal.

In the embodiments of the present application, generally, the user terminal can display the service recommendation information after the above-mentioned screening operation to the user. Of course, in actual applications, since users may have different preferences for different service information, such a function can also be provided: the user can set in advance or in real time through the user terminal whether to allow the server to push the service information and whether to allow the user terminal to display the service information for different service information. The user terminal can then save the user's settings as display setting information and associate the display setting information with the information of the information push scenario corresponding to the service information.

Correspondingly, for the above step S102, displaying the service information may specifically include: acquiring and parsing display setting information corresponding to the information of the information push scenario, and displaying the service information when it is parsed that the display setting information indicates that the service information is allowed to be displayed.

For example, assuming that the user does not want to see travel-related service information in the near future, the user can make settings on the user terminal so that even if the user terminal obtains travel-related service information from the server, the service information will not be displayed. This increases the applicable scenarios of the information display method provided in the embodiment of the present application and improves the user experience.

In the embodiment of the present application, as mentioned above, the user terminal obtains service information in a service information format from the server. Accordingly, the user terminal can display the service information according to a display template applicable to the service information format.

Furthermore, when there are multiple applicable display templates, each display template can be distinguished based on a "display template identifier." In this case, in addition to obtaining service information from the server, the user terminal can also receive a display template identifier sent by the server. Displaying the service information can include displaying the service information based on the display template indicated by the display template identifier.

It should be noted that the display template identifier can be defined in the service information format or defined separately and then associated with the service information. For example, when CML is used as the service information format, the "CML Type" field in the CML format specification can be used to store the display template identifier. Each value set in the "CML Type" field can represent a display template identifier.

In actual applications, the display template may be a UI or View predefined by a server or user terminal, and the user terminal may display service information by rendering the service information using the display template.

Figure 2 shows a display template for displaying service information in actual application. It can be seen that the display template mainly includes four areas, namely:

Logo text, which can be used to display the title and introduction of service information;

The primary fields can be used to display the main content of the service information;

Secondary fields and auxiliary fields can be used to display non-primary content of service information;

The operation area can be used to place space for operating service information, such as buttons, barcodes, QR codes, etc.

To further illustrate, for example, a news-related service in an actual application, Figure 3 shows a schematic diagram of the display template in Figure 2. For ease of understanding, each area is marked with a dashed box and arrow. It can be seen that the logo text, main area, secondary area, additional area, and operation area all display corresponding content.

It should be noted that this application does not limit the specific style of the display template and the specific method of displaying service information based on the display template. Figures 2 and 3 are just examples and are not limiting.

In the embodiment of the present application, the user's habit of using applications on the user terminal may also change.

For example, suppose a user is accustomed to using a lottery app to view the lottery results for the Double Color Ball lottery at 12:00 PM every day. According to the method provided in this application, the user terminal can display the obtained lottery service information at 12:00 PM every day for the user to view. However, the user has recently used a video app to watch online videos at 12:00 PM every day. In this case, if the user terminal continues to display lottery service information at 12:00 PM every day, it may not meet the user's current needs.

To address the issue in the above example, after determining the information push scenario, the user terminal can also update the user's first behavior data corresponding to the information push scenario based on recently accumulated user behavior data. Specifically, if the behavior content data previously included in the user's first behavior data may be "viewing the lottery results for the Double Color Ball lottery," this behavior content data can be updated to "watching online videos." In this way, the service information subsequently displayed by the user terminal based on the updated user's first behavior data can be service information related to video applications, which is more in line with the user's current habits.

For example, if a user is accustomed to using the lottery app at 12:00 PM every day, then according to the method provided in this application, the user terminal can display the obtained lottery service information at 12:00 PM every day for the user to view. However, the user has recently used the lottery app at 10:00 AM every day. In this case, if the user terminal continues to display the lottery service information at 12:00 PM every day, it may not meet the user's current needs.

To address the above example, after determining the information push scenario (as previously described, the information push scenario may include "12:00"), the user terminal can also update the information push scenario based on recently accumulated user behavior data. Specifically, the "12:00" included in the information push scenario can be updated to "10:00." In this way, the user terminal will then display lottery service information at 10:00 every day, which is more in line with the user's current habits.

According to the description of the above two examples, in order to facilitate the update operation, the mapping relationship between the information push scenario and the user's first behavior data can be pre-established. In this case, for the above step S102, when the user terminal is monitored to be in the information push scenario, the service information obtained based on the user behavior data is displayed. Specifically, it may include: when the user terminal is monitored to be in the information push scenario, based on the mapping relationship between the information of the information push scenario and the user's first behavior data, determining the user's first behavior data of the information mapping of the information push scenario; and displaying the service information obtained based on the user's first behavior data.

Furthermore, after displaying the service information obtained based on the user's first behavior data, the method also includes: using the user's second behavior data to update the first behavior data in the mapping relationship; or using information of other information push scenarios in which the user's first behavior data is generated to update the information of the information push scenario in the mapping relationship.

The second user behavior data may be user behavior data selected according to a preset strategy from all existing user behavior data or the "recently accumulated user behavior data" mentioned in the above two examples.

The above is an information display method provided by the embodiment of the present application, which is executed by the user terminal. Based on the same idea, the information push process corresponding to the information display process in Figure 1 is executed by the server in the embodiment of the present application, as shown in Figure 4, and specifically includes the following steps:

S401: Acquire information about information push scenarios.

The execution subject of the information display process in Figure 4 may be a server, wherein the server includes but is not limited to: a server corresponding to the application on the user terminal, a third-party device, etc.

S402: Monitoring whether the user terminal is in the information push scenario according to the information of the information push scenario.

S403: When it is monitored that the user terminal is in the information push scenario, service information is pushed to the user terminal.

In an embodiment of the present application, the user terminal may also monitor whether it is in the information push scenario. In this case, the server may not actively push service information to the user terminal, but may wait for the user terminal to request the server for service information when it monitors that it is in the information push scenario, and then the server sends the service information to the user terminal.

Through the above method, the server can automatically push service information that the user is likely to pay attention to in the current information push scenario to the user terminal based on the user's application usage habits in different information push scenarios, without waiting for the user to actively use the application, thereby allowing the user terminal to quickly display the service information that the user is interested in.

In an embodiment of the present application, for the above-mentioned step S401, obtaining information about the information push scenario may specifically include: receiving information about the information push scenario sent by the user terminal, or determining information about the information push scenario based on the user's first behavior data.

Obviously, the former method of obtaining information about the information push scenario is determined by the user terminal, while the latter method is determined by the server. In comparison, the information about the information push scenario obtained through the former method better reflects the user's actual needs, and the service information subsequently pushed by the server is accordingly more in line with the user's actual needs. The latter method of obtaining information about the information push scenario can reduce the processing burden on the user terminal. In actual applications, the method of obtaining information about the information push scenario can be selected based on the specific application scenario.

In an embodiment of the present application, when a user terminal requests service information from a server, the relevant information of the user's first behavior data may be sent to the server. Accordingly, the server may receive the relevant information of the user's first behavior data sent by the user terminal. Furthermore, in step S403 above, pushing service information to the user terminal may specifically include: based on the relevant information, pushing service information obtained from at least one third-party server to the user terminal. This improves the effectiveness of the service information pushed by the server to the user terminal.

Furthermore, pushing service information to the user terminal based on the relevant information may specifically include: pushing the service information in the information format to the user terminal based on the relevant information and information format. The relevant information about the user's first behavior data includes at least one of the following: behavior content data contained in the user's first behavior data, and an application category corresponding to the user's first behavior data.

It should be noted that if the server adopts the second acquisition method mentioned above to obtain information about the information push scenario, since the server can determine the information about the information push scenario by itself, the relevant information of the user behavior data sent by the user terminal may not include: information about the information push scenario.

Similarly, if the server adopts the first acquisition method mentioned above to obtain information about the information push scenario, since the server does not determine the information about the information push scenario by itself, it can obtain information about the information push scenario from the user terminal, then the relevant information of the user behavior data may include: information about the information push scenario.

In an embodiment of the present application, when the relevant information includes the application category, pushing service information to the user terminal may include: obtaining service information corresponding to the application category based on the application category, and pushing the obtained service information corresponding to the application category to the user terminal.

In an embodiment of the present application, when the relevant information includes the behavioral content data, pushing service information to the user terminal may include: obtaining data required for behaviors similar to the behavior represented by the behavioral content data, and pushing the required data to the user terminal as the service information. For example, when the behavioral content data included in the relevant information is "querying top product information," it can be inferred that the user may have a need to purchase clothing, and new top product information and other clothing product information can be pushed to the user as service information. This not only makes it easier for the user to choose tops, but also makes it easier for the user to choose other clothing that matches the top, thereby improving the user experience.

The above are the information display method and information push method provided in the embodiments of the present application. In actual applications, the information display method and information push method can be implemented on different applications respectively, or on the same application.

FIG5 shows the overall functional architecture of an application when the information display method and the information push method are implemented as one application.

The application can be installed on the user terminal. On the user terminal side, the application is mainly used to collect user behavior data from the user terminal itself or from a third-party device, and based on the analysis of the user behavior data, determine the user's behavior habits and preferences in different information push scenarios, and then monitor the current information push scenario, and obtain and display the service information corresponding to the current information push scenario from the server side. The service information is determined based on the user's behavior habits and preferences (which can be reflected by the user's first behavior data) in the current information push scenario.

Accordingly, the server corresponding to the application may include at least the service information data center on the server side shown in FIG5 . The service information data center may generate service information itself or obtain service information from a third-party server. The service information data center may determine the service information that the user is likely to be interested in from the existing service information based on the information push scenario of the user terminal, and push it to the user terminal as the service information for display.

The above are the information display method and information push method provided in the embodiments of the present application. Based on the same idea, the embodiments of the present application also provide corresponding information display devices and information push devices, as shown in Figures 6 and 7.

FIG6 is a schematic diagram of the structure of an information display device provided in an embodiment of the present application, specifically comprising:

A monitoring module 601 is configured to monitor whether a user terminal is in an information push scenario based on information about the information push scenario;

The display module 602 is configured to display service information obtained based on the user's first behavior data when the monitoring module 601 monitors that the user terminal is in the information push scenario.

The information push scenario is the scenario in which the user terminal is located when the user's first behavior data is generated.

The device further comprises:

A service information module 603 is configured to obtain service information based on the user's first behavior data before the display module 602 displays the service information obtained based on the user's first behavior data;

The service information module 603 is specifically used to: send relevant information of the user's first behavior data to the server before the display module 602 displays the service information obtained according to the user's first behavior data, and receive service information pushed by the server based on the relevant information; or, search for locally stored service information before the display module 602 displays the service information obtained according to the user's first behavior data, wherein the service information is determined based on the relevant information of the user's first behavior data.

The service information module 603 is specifically configured to receive service information in the service information format that is pushed by the server according to the relevant information and the service information format.

The device further comprises:

The display template module 604 is configured to receive the display template identifier sent by the server;

The display module 602 is specifically configured to display the service information according to the display template indicated by the display template identifier.

The relevant information of the user's first behavior data includes at least one of the following:

Information about the information push scenario;

Behavior content data included in the user's first behavior data;

The application category corresponding to the user's first behavior data.

When the relevant information includes information about the information push scenario, the service information includes service information mapped to the information of the information push scenario; or when the relevant information includes behavior content data contained in the user's first behavior data, the service information includes service information related to the behavior content data; or when the relevant information includes an application category corresponding to the user's first behavior data, the service information includes: service information whose application category is the same as the application category corresponding to the user's first behavior data.

The display module 602 is specifically configured to: acquire and parse display setting information corresponding to the information of the information push scenario; and display the service information when it is parsed that the display setting information indicates that the service information is allowed to be displayed.

The service information is obtained by the server from at least one third-party server according to the relevant information.

The display module 602 is specifically used to: when the monitoring module monitors that the user terminal is in the information push scenario, determine the user first behavior data of the information mapping of the information push scenario according to the mapping relationship between the information of the information push scenario and the user's first behavior data; and display the service information obtained according to the user's first behavior data.

The device further comprises:

Update module 605 is used to update the first behavior data in the mapping relationship using the user's second behavior data after the display module displays the service information obtained based on the user's first behavior data, or to update the information of the information push scenario in the mapping relationship using the information of other information push scenarios in which the user's first behavior data is generated.

Specifically, the device shown in FIG. 6 may be located on a terminal.

FIG7 is a schematic diagram of the structure of an information push device provided in an embodiment of the present application, specifically comprising:

Acquisition module 701, used to acquire information of information push scenario;

A monitoring module 702 is configured to monitor whether the user terminal is in the information push scenario based on the information of the information push scenario;

The push module 703 is configured to push service information to the user terminal when the monitoring module detects that the user terminal is in the information push scenario.

The push module 703 is specifically configured to: receive relevant information about the user's first behavior data sent by the user terminal; and push service information obtained from at least one third-party server to the user terminal based on the relevant information.

The relevant information of the user behavior data includes at least one of the following:

Behavior content data included in the user's first behavior data;

The application category corresponding to the user's first behavior data.

Specifically, the device shown in FIG. 7 may be located on a server.

Embodiments of the present application provide an information display method and apparatus. This method monitors whether a user terminal is in an information push scenario based on information about the information push scenario. When the user terminal is detected to be in the information push scenario, service information obtained based on the user's first behavior data is displayed. Through this method, the user's first behavior data can reflect the user's application usage habits when the user terminal was previously in the information push scenario. The terminal can then obtain and display service information that the user is likely to be interested in in the information push scenario without having to wait for the user to actively use the application. Therefore, the service information that the user is interested in can be quickly displayed to the user.

It will be understood by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

The present invention is described with reference to the flowcharts and/or block diagrams of the methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and/or box in the flowchart and/or block diagram, as well as the combination of processes and/or boxes in the flowchart and/or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and/or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

The foregoing is merely an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should all be included within the scope of the claims of the present application.

Claims (26)

1. An information display method, characterized in that it includes: Based on the information push scenario, monitor whether the user terminal is in the information push scenario; When a user terminal is detected to be in the information push scenario, service information obtained based on the user's first behavior data is displayed. Different information push scenarios correspond to different applications or application categories on the user terminal. The user's first behavior data is user behavior data generated based on the user's behavior when the user terminal was previously in the information push scenario and the user used the application or application category on the user terminal that corresponds to the information push scenario. 2. The method as described in claim 1, wherein the information push scenario is the scenario in which the user terminal is located when the user's first behavior data is generated. 3. The method as described in claim 2, characterized in that, before displaying the service information obtained based on the user's first behavior data, the method further includes: obtaining service information based on the user's first behavior data; the step of obtaining service information based on the user's first behavior data includes: Send relevant information about the user's first behavior data to the server, and receive service information pushed by the server based on the relevant information; or, Locate locally stored service information, wherein the service information is determined based on relevant information of the user's first behavior data. 4. The method as described in claim 3, characterized in that receiving service information pushed by the server based on the relevant information specifically includes: Receive service information that is pushed by the server according to the relevant information and service information format, and that has the service information format. 5. The method as described in claim 3 or 4, characterized in that the method further comprises: Receive the display template identifier sent by the server; then Display service information, including: The service information is displayed according to the display template indicated by the display template identifier. 6. The method as described in claim 3 or 4, wherein the relevant information of the user's first behavior data includes at least one of the following: Information from the information push scenario; The user's first behavior data includes behavioral content data; The application category corresponding to the user's first behavior data. 7. The method as described in claim 6, characterized in that: When the relevant information includes information from the information push scenario, the service information includes service information mapped to the information from the information push scenario; or When the relevant information includes behavioral content data contained in the user's first behavioral data, the service information includes service information related to the behavioral content data; or When the relevant information includes the application category corresponding to the user's first behavior data, the service information includes: service information whose application category is the same as the application category corresponding to the user's first behavior data. 8. The method as described in claim 3 or 4, characterized in that displaying service information includes: Obtain and parse the display settings information corresponding to the information push scenario; When the display settings information indicates that displaying service information is allowed, the service information is displayed. 9. The method as described in claim 3 or 4, wherein the service information is obtained by the server from at least one third-party server based on the relevant information. 10. The method as described in claim 2, characterized in that, when monitoring that the user terminal is in the information push scenario, displaying service information obtained based on user behavior data includes: When a user terminal is detected to be in the information push scenario, the user's first behavior data mapped to the information push scenario is determined based on the mapping relationship between the information in the information push scenario and the user's first behavior data. Display service information obtained based on the user's first behavior data. 11. The method as described in claim 10, characterized in that, after displaying the service information obtained based on the user's first behavior data, the method further includes: Update the first behavior data in the mapping relationship using the user's second behavior data; or The information of the information push scenario in the mapping relationship is updated using information from other information push scenarios in which the user's first behavior data was generated. 12. An information push method, characterized in that it includes: Obtain information from information push scenarios; Based on the information of the information push scenario, monitor whether the user terminal is in the information push scenario; When the user terminal is detected to be in the information push scenario, service information is pushed to the user terminal; Pushing service information to user terminals, specifically including: The system receives information related to the user's first behavior data sent by the user terminal. Different information push scenarios correspond to different applications or application categories on the user terminal. The user's first behavior data is generated based on the user's behavior when the user terminal was previously in the information push scenario, and the user's behavior when using the application or application category on the user terminal that corresponds to the information push scenario. Based on the aforementioned information, service information obtained from at least one third-party server is pushed to the user terminal. 13. The method as described in claim 12, wherein the relevant information of the user behavior data includes at least one of the following: The user's first behavior data includes behavioral content data; The application category corresponding to the user's first behavior data. 14. An information display device, characterized in that it comprises: The monitoring module is used to monitor whether the user terminal is in the information push scenario based on the information push scenario. The display module is used to display service information obtained based on the user's first behavior data when the monitoring module detects that the user terminal is in the information push scenario. Different information push scenarios correspond to different applications or application categories on the user terminal. The user's first behavior data is user behavior data generated based on the user's behavior when the user terminal was previously in the information push scenario and the user used the application or application category on the user terminal that corresponds to the information push scenario. 15. The apparatus as described in claim 14, wherein the information push scenario is the scenario in which the user terminal is located when the user's first behavior data is generated. 16. The apparatus of claim 15, wherein the apparatus further comprises: The service information module is used to obtain service information based on the user's first behavior data before the display module displays the service information obtained based on the user's first behavior data. The service information module is specifically used to: send relevant information of the user's first behavior data to the server before the display module displays the service information obtained based on the user's first behavior data, and receive service information pushed by the server based on the relevant information; or, it is used to search for locally stored service information before the display module displays the service information obtained based on the user's first behavior data, wherein the service information is determined based on the relevant information of the user's first behavior data. 17. The apparatus of claim 16, wherein the service information module is specifically configured to: receive service information having the service information format pushed by the server according to the relevant information and service information format. 18. The apparatus of claim 16 or 17, wherein the apparatus further comprises: The display template module is used to receive a display template identifier sent by the server; then The display module is specifically used to display service information according to the display template represented by the display template identifier. 19. The apparatus of claim 16 or 17, wherein the relevant information of the user's first behavior data includes at least one of the following: Information from the information push scenario; The user's first behavior data includes behavioral content data; The application category corresponding to the user's first behavior data. 20. The apparatus of claim 19, wherein when the relevant information includes information of the information push scenario, the service information includes service information mapped to the information of the information push scenario; or when the relevant information includes behavioral content data contained in the user's first behavioral data, the service information includes service information related to the behavioral content data; or when the relevant information includes the application category corresponding to the user's first behavioral data, the service information includes: service information whose application category is the same as the application category corresponding to the user's first behavioral data. 21. The apparatus as described in claim 16 or 17, wherein the display module is specifically configured to: acquire and parse display setting information corresponding to the information in the information push scenario; and display the service information when the parsed display setting information indicates that displaying service information is allowed. 22. The apparatus of claim 16 or 17, wherein the service information is obtained by the server from at least one third-party server based on the relevant information. 23. The apparatus of claim 15, wherein the display module is specifically configured to: when the monitoring module detects that the user terminal is in the information push scenario, determine the user's first behavior data mapped by the information in the information push scenario according to the mapping relationship between the information in the information push scenario and the user's first behavior data; and display the service information obtained based on the user's first behavior data. 24. The apparatus of claim 23, wherein the apparatus further comprises: An update module is used to update the first behavior data in the mapping relationship using the second behavior data of the user after the display module displays the service information obtained based on the first behavior data of the user, or to update the information of the information push scenario in the mapping relationship using the information of other information push scenarios in which the first behavior data of the user was generated. 25. An information push device, characterized in that it comprises: The acquisition module is used to acquire information for information push scenarios; The monitoring module is used to monitor whether the user terminal is in the information push scenario based on the information push scenario information; The push module is used to push service information to the user terminal when the monitoring module detects that the user terminal is in the information push scenario; The push module is specifically used for: receiving information related to user first behavior data sent by the user terminal, wherein different information push scenarios correspond to different applications or application categories on the user terminal, and the user first behavior data is user behavior data generated based on the user's behavior of using the application or application category corresponding to the information push scenario when the user terminal was previously in the information push scenario; and pushing service information obtained from at least one third-party server to the user terminal according to the relevant information. 26. The apparatus of claim 25, wherein the relevant information of the user behavior data includes at least one of the following: The user's first behavior data includes behavioral content data; The application category corresponding to the user's first behavior data.