CN110442825B - Method and apparatus for presenting information - Google Patents

Method and apparatus for presenting information Download PDF

Info

Publication number
CN110442825B
CN110442825B CN201910742698.7A CN201910742698A CN110442825B CN 110442825 B CN110442825 B CN 110442825B CN 201910742698 A CN201910742698 A CN 201910742698A CN 110442825 B CN110442825 B CN 110442825B
Authority
CN
China
Prior art keywords
type
information
acquisition request
information acquisition
indicated
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201910742698.7A
Other languages
Chinese (zh)
Other versions
CN110442825A (en
Inventor
吴培希
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lianshang Xinchang Network Technology Co Ltd
Original Assignee
Lianshang Xinchang Network Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lianshang Xinchang Network Technology Co Ltd filed Critical Lianshang Xinchang Network Technology Co Ltd
Priority to CN201910742698.7A priority Critical patent/CN110442825B/en
Publication of CN110442825A publication Critical patent/CN110442825A/en
Application granted granted Critical
Publication of CN110442825B publication Critical patent/CN110442825B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/957—Browsing optimisation, e.g. caching or content distillation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

Embodiments of the present disclosure disclose methods and apparatus for presenting information. The method for presenting information comprises the following steps: under the condition that the information acquisition operation executed by a user through a target application is detected, sending a first type of information acquisition request to a first server and sending a second type of information acquisition request to a second server; under the condition of acquiring the second type of information indicated by the second type of information acquisition request, determining whether the first type of information indicated by the first type of information acquisition request is acquired; and under the condition that the first type information indicated by the first type information acquisition request is not acquired, presenting the second type information indicated by the second type information acquisition request and the first type information stored in the local storage through the target application. The embodiment improves the presenting speed of the first type information and the second type information on the premise of ensuring that the first type information and the second type information are both presented.

Description

Method and apparatus for presenting information
Technical Field
Embodiments of the present disclosure relate to the field of computer technologies, and in particular, to a method and apparatus for presenting information.
Background
Currently, presentation schemes for a first type of information (e.g., advertisements) and a second type of information (e.g., other information besides advertisements) generally include the following three types:
the first scheme is as follows: the terminal equipment requests the first type information and the second type information from the same server, and the server directly returns the combined first type information and the second type information for the terminal equipment to present.
Scheme II: the terminal equipment simultaneously and respectively requests the first type information from the server in which the first type information is stored and requests the second type information from the server in which the second type information is stored. Then, the terminal device first presents the second type of information and then inserts the first type of information between the second type of information.
The third scheme is as follows: the terminal equipment requests the first type information from the server storing the first type information in advance and then stores the first type information locally. When the terminal equipment needs to present the information, the second type information is requested from the server stored with the second type information, and then the first type information stored in the local is inserted between the second type information.
Disclosure of Invention
The present disclosure presents methods and apparatus for presenting information.
In a first aspect, an embodiment of the present disclosure provides a method for presenting information, which is applied to a terminal device, where the terminal device is installed with a target application, and the terminal device includes a local storage for storing a first type of information, and the method includes: in response to detecting that a user executes information acquisition operation through a target application, sending a first-class information acquisition request to a first server and sending a second-class information acquisition request to a second server, wherein the first server stores first-class information indicated by the first-class information acquisition request, and the second server stores second-class information indicated by the second-class information acquisition request; in response to the second type of information indicated by the second type of information acquisition request, determining whether the first type of information indicated by the first type of information acquisition request is acquired; and in response to the first type information indicated by the first type information acquisition request is not acquired, presenting the second type information indicated by the second type information acquisition request and the first type information stored in the local storage through the target application.
In some embodiments, the method further comprises: in response to a predetermined update condition being met, a predetermined update step is performed to update the first type of information in the local storage.
In some embodiments, the update condition includes any one of: the number of the first type information currently stored in the local memory is less than or equal to a preset number threshold; the local memory stores first type information with the storage time length exceeding a first preset time length; detecting running operation executed by a user on a target application, and storing first type information with the storage duration exceeding a first preset duration in a local memory; the time when the first type of information is obtained from the first server last time exceeds a second preset time length, and the first type of information with the storage time length exceeding the first preset time length is stored in the local storage.
In some embodiments, each first type of information stored in the local memory has a first preset duration corresponding to the first type of information.
In some embodiments, the updating step comprises at least one of: the first type information is obtained from the first server again, and the obtained first type information is stored in the local storage; and deleting the first type information meeting the predetermined deleting condition from the local storage.
In some embodiments, the deletion condition includes any one of: the first type information is the first type information with the longest storage time in the first type information stored in the local memory; the current time is later than the latest presentation time set for the first type of information.
In some embodiments, after determining whether the first type information indicated by the first type information acquisition request has been acquired in response to acquiring the second type information indicated by the second type information acquisition request, the method further comprises: and in response to the first type of information indicated by the first type of information acquisition request, presenting the first type of information indicated by the first type of information acquisition request and the second type of information indicated by the second type of information acquisition request through the target application.
In some embodiments, the method further comprises: and in response to that the first type information indicated by the first type information acquisition request is not acquired within a preset time period, re-sending the first type information acquisition request to the first server, wherein the preset time period takes the moment of acquiring the second type information indicated by the second type information acquisition request as a starting point.
In some embodiments, the method further comprises: and in response to the first-class information indicated by the first-class information acquisition request acquired within a preset time period, storing the first-class information indicated by the first-class information acquisition request in a local memory, wherein the preset time period takes the time of acquiring the second-class information indicated by the second-class information acquisition request as a starting point.
In some embodiments, the local memory is a local cache.
In some embodiments, the target application presents the first type of information and the second type of information in an information flow manner.
In some embodiments, a time difference between a time when the terminal device acquires the first type of information and a time when the terminal device presents the first type of information is smaller than a preset time difference threshold.
In a second aspect, an embodiment of the present disclosure provides an apparatus for presenting information, which is disposed in a terminal device, where the terminal device has a target application installed thereon, and the terminal device includes a local storage for storing a first type of information, and the apparatus includes: a first transmission unit: the system comprises a first server and a second server, wherein the first server stores first information indicated by a first information acquisition request, and the second server stores second information indicated by a second information acquisition request; a determination unit configured to determine whether the first type information indicated by the first type information acquisition request has been acquired, in response to acquisition of the second type information indicated by the second type information acquisition request; and the first presenting unit is configured to present the second type information indicated by the second type information acquisition request and the first type information stored in the local memory through the target application in response to the first type information indicated by the first type information acquisition request not being acquired.
In some embodiments, the apparatus further comprises: and the updating unit is configured to execute a predetermined updating step to update the first type information in the local storage in response to the condition that the predetermined updating condition is met.
In some embodiments, the update condition includes any one of: the number of the first type information currently stored in the local memory is less than or equal to a preset number threshold; the local memory stores first type information with the storage time length exceeding a first preset time length; detecting running operation executed by a user on a target application, and storing first type information with the storage duration exceeding a first preset duration in a local memory; the time when the first type of information is obtained from the first server last time exceeds a second preset time length, and the first type of information with the storage time length exceeding the first preset time length is stored in the local storage.
In some embodiments, each first type of information stored in the local memory has a first preset duration corresponding to the first type of information.
In some embodiments, the updating step comprises at least one of: the first type information is re-acquired from the first server, and the re-acquired first type information is stored in a local memory; and deleting the first type information meeting the predetermined deleting condition from the local storage.
In some embodiments, the deletion condition includes any one of: the first type information is the first type information with the longest storage time in the first type information stored in the local memory; the current time is later than the latest presentation time set for the first type of information.
In some embodiments, the apparatus further comprises: and the second presentation unit is configured to present the first type information indicated by the first type information acquisition request and the second type information indicated by the second type information acquisition request through the target application in response to the acquisition of the first type information indicated by the first type information acquisition request.
In some embodiments, the apparatus further comprises: and a second sending unit configured to resend the first-type information acquisition request to the first server in response to not acquiring the first-type information indicated by the first-type information acquisition request within a preset time period, wherein the preset time period starts from a time when the second-type information indicated by the second-type information acquisition request is acquired.
In some embodiments, the apparatus further comprises: and a storage unit configured to store the first type information indicated by the first type information acquisition request in the local storage in response to acquisition of the first type information indicated by the first type information acquisition request within a preset time period, wherein the preset time period starts from a time when the second type information indicated by the second type information acquisition request is acquired.
In some embodiments, the local memory is a local cache.
In some embodiments, the target application presents the first type of information and the second type of information in an information flow manner.
In some embodiments, a time difference between a time when the terminal device acquires the first type of information and a time when the terminal device presents the first type of information is smaller than a preset time difference threshold.
In a third aspect, an embodiment of the present disclosure provides a terminal device, where the terminal device includes: one or more processors; a storage device having one or more programs stored thereon; when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the method as described in any implementation of the first aspect.
In a fourth aspect, the disclosed embodiments provide a computer-readable medium on which a computer program is stored, which computer program, when executed by a processor, implements the method as described in any of the implementations of the first aspect.
The method and the device for presenting information provided by the embodiments of the present disclosure send a first type information acquisition request to a first server and a second type information acquisition request to a second server in a case where an information acquisition operation performed by a user through a target application is detected, where the first server stores first type information indicated by the first type information acquisition request, the second server stores second type information indicated by the second type information acquisition request, then, in a case where the second type information indicated by the second type information acquisition request is acquired, determine whether the first type information indicated by the first type information acquisition request has been acquired, and finally, in a case where the first type information indicated by the first type information acquisition request has not been acquired, present the second type information indicated by the second type information acquisition request and the first type information stored in a local storage through the target application, therefore, on the premise of ensuring that the first type information and the second type information are both presented, the presenting speed of the first type information and the second type information is improved.
Drawings
Other features, objects and advantages of the disclosure will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
FIG. 1 is an exemplary system architecture diagram in which one embodiment of the present disclosure may be applied;
FIG. 2 is a flow diagram of one embodiment of a method for presenting information, according to the present disclosure;
3A-3C are schematic diagrams of one application scenario of a method for presenting information according to the present disclosure;
FIG. 4 is a flow diagram of yet another embodiment of a method for presenting information in accordance with the present disclosure;
FIG. 5 is a flow diagram of yet another embodiment of a method for presenting information in accordance with the present disclosure;
FIG. 6 is a block diagram of a computer system suitable for use with a terminal device implementing an embodiment of the disclosure.
Detailed Description
The present disclosure is described in further detail below with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not to be construed as limiting 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, in the present disclosure, the embodiments and features of the embodiments may be combined with each other without conflict. The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Fig. 1 illustrates an exemplary system architecture 100 to which embodiments of methods for presenting information may be applied, according to embodiments of the present disclosure.
As shown in fig. 1, system architecture 100 may include terminal device 101, network 102, and servers 103, 104. Network 102 is the medium used to provide communication links between terminal equipment 101 and servers 103, 104. Network 102 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may use the terminal device 101 to interact with the servers 103, 104 via the network 102 to receive or transmit data (e.g., to transmit the first type information acquisition request and the second type information acquisition request to the servers 103, 104, respectively), and so on. Various client applications, such as news information applications, video playing software, image processing applications, web browser applications, shopping applications, search applications, instant messaging tools, mailbox clients, social platform software, and the like, may be installed on the terminal device 101.
The terminal apparatus 101 may be hardware or software. When the terminal device 101 is hardware, it may be various electronic devices having a display screen and supporting page browsing, including but not limited to a smart phone, a tablet computer, an e-book reader, an MP3 player (Moving Picture Experts Group Audio Layer III, motion Picture Experts Group Audio Layer 3), an MP4 player (Moving Picture Experts Group Audio Layer IV, motion Picture Experts Group Audio Layer 4), a laptop computer, a desktop computer, and the like. When the terminal apparatus 101 is software, it can be installed in the electronic apparatuses listed above. It may be implemented as a plurality of software or software modules (e.g., software or software modules used to provide distributed services) or as a single software or software module. And is not particularly limited herein.
The servers 103 and 104 may be servers that provide various services, for example, the server 103 may be a server that stores first type information indicated by a first type information acquisition request, and the server 104 may be a server that stores second type information indicated by a second type information acquisition request. After the terminal device 101 sends the first-type information acquisition request to the server 103, the server 103 may return the first-type information indicated by the first-type information acquisition request to the terminal device 101. After the terminal device 101 sends the second type information acquisition request to the server 104, the server 104 may return the second type information indicated by the second type information acquisition request to the terminal device 101. As an example, the servers 103 and 104 may be cloud servers, or may be physical servers.
The server may be hardware or software. When the server is hardware, it may be implemented as a distributed server cluster composed of multiple servers, or may be implemented as a single server. When the server is software, it may be implemented as multiple pieces of software or software modules (e.g., software or software modules used to provide distributed services), or as a single piece of software or software module. And is not particularly limited herein.
It should also be noted that the method for presenting information provided by the embodiments of the present disclosure is generally performed by a terminal device.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation. When the electronic device on which the method for presenting information operates does not require data transmission with other electronic devices in performing the method, the system architecture may include only the electronic device (e.g., terminal device) on which the method for presenting information operates.
With continued reference to FIG. 2, a flow 200 of one embodiment of a method for presenting information in accordance with the present disclosure is shown. The method for presenting the information is applied to the terminal equipment, wherein the terminal equipment is provided with a target application, and the terminal equipment comprises a local memory for storing the first type of information. The method for presenting information comprises the following steps:
step 201, in response to detecting that the user performs an information obtaining operation through the target application, sending a first type information obtaining request to the first server, and sending a second type information obtaining request to the second server.
In this embodiment, an executing subject (e.g., a terminal device shown in fig. 1) of the method for presenting information may send a first type information acquisition request to a first server and a second type information acquisition request to a second server in a case where an information acquisition operation performed by a user through a target application is detected. The first server stores first type information indicated by the first type information acquisition request, and the second server stores second type information indicated by the second type information acquisition request.
The first type of information and the second type of information may be stored in a first server and a second server, respectively. Typically, the first type of information and the second type of information each represent different types of information. The first type information and the second type information may be managed by different managers, respectively. By way of example, the first type of information may be advertisements and the second type of information may be other information (e.g., news information) in addition to advertisements. The first type of information is typically managed by a provider of the first type of information (e.g., an advertiser). The second type of information is typically managed by a provider of the second type of information (e.g., the person who operates the second type of information). In addition, in general, after a user of a target application clicks on first-type information presented on the target application, a provider of the first-type information needs to pay a certain fee (e.g., an advertisement fee) to a provider of second-type information.
Here, the target application may be an application for presenting the first type of information and the second type of information. The local storage may be a removable hard disk, an optical disk, or the like. The information acquisition operation may be an operation for instructing the execution main body to acquire information as described above.
As an example, when a user performs a refresh operation (i.e., the information acquisition operation) on a target application (e.g., an information-based application), the execution subject may send a first-type information acquisition request (e.g., an advertisement acquisition request) to a first server (e.g., a server storing advertisements), and send a second-type information acquisition request (e.g., an information acquisition request) to a second server (e.g., a server storing information).
It is to be understood that, after the first server receives the first-type information acquisition request, the first-type information indicated by the first-type information acquisition request may be returned to the execution main body. Similarly, after the second server receives the second type information acquisition request, the second type information indicated by the second type information acquisition request may be returned to the execution main body.
Here, the administrator of the first server may update the first type of information stored in the first server. For example, the administrator may delete all or part of the first type information stored in the first server every first preset time period (e.g., 1 hour, 8 hours), and/or store new first type information in the first server. Similarly, the administrator of the second server may update the second type of information stored in the second server. For example, the administrator may delete all or part of the second type information stored in the second server every second preset time period (e.g., 2 hours, 5 hours), and/or store new second type information in the second server.
In step 202, in response to acquiring the second type of information indicated by the second type of information acquisition request, it is determined whether the first type of information indicated by the first type of information acquisition request has been acquired.
In this embodiment, in a case where the execution main body acquires the second type information indicated by the second type information acquisition request, the execution main body may determine whether the first type information indicated by the first type information acquisition request has been acquired.
Here, the execution body may first obtain the first type of information and then obtain the second type of information; or first obtaining the first type of information and then obtaining the second type of information; the first type of information and the second type of information may also be obtained simultaneously.
And step 203, in response to the first type information indicated by the first type information acquisition request is not acquired, presenting the second type information indicated by the second type information acquisition request and the first type information stored in the local storage through the target application.
In this embodiment, when the execution main body does not acquire the first type of information indicated by the first type of information acquisition request (that is, the execution main body does not acquire the first type of information temporarily when the execution main body has acquired the second type of information), the execution main body may present the second type of information indicated by the second type of information acquisition request and the first type of information stored in the local storage through the target application.
With continuing reference to fig. 3A-3C, fig. 3A-3C are schematic diagrams of an application scenario of a method for presenting information according to the present embodiment. In the application scenario of fig. 3A, the terminal device 301 has a target application installed (in fig. 3A, the target application is an information-class application), and the terminal device 301 includes a local storage (e.g., a cache) for storing the first-class information. As shown in fig. 3A, the terminal device 301 detects an information acquisition operation (refresh operation in the drawing) performed by the user through the target application. Then, with continued reference to fig. 3B, the terminal apparatus 301 sends a first-type information acquisition request 304 to the first server 302, and sends a second-type information acquisition request 305 to the second server 303. The first server 302 stores the first type of information indicated by the first type of information obtaining request, and the second server 303 stores the second type of information indicated by the second type of information obtaining request. After that, the terminal device 301 receives the second type information 306 returned by the second server 303. Referring next to fig. 3C, in a case where the terminal device 301 acquires the second type information 306 indicated by the second type information acquisition request 305, the terminal device 301 temporarily does not acquire the first type information indicated by the first type information acquisition request 304, and thereafter, the terminal device 301 presents the second type information 306 indicated by the second type information acquisition request 305 and the first type information 307 stored in the local storage through the target application.
The method provided by the above embodiment of the present disclosure is implemented by sending a first type information acquisition request to a first server and sending a second type information acquisition request to a second server in a case where an information acquisition operation performed by a user through a target application is detected, where the first server stores first type information indicated by the first type information acquisition request, the second server stores second type information indicated by the second type information acquisition request, then, in a case where the second type information indicated by the second type information acquisition request is obtained, determining whether the first type information indicated by the first type information acquisition request has been obtained, and finally, in a case where the first type information indicated by the first type information acquisition request has not been obtained, presenting, through the target application, the second type information indicated by the second type information acquisition request and the first type information stored in the local storage, therefore, on the premise of ensuring that the first type information and the second type information are both presented, the presenting speed of the first type information and the second type information is improved.
In some optional implementations of this embodiment, in a case that it is determined that the predetermined update condition is met, the execution main body may further perform a predetermined update step to update the first type information in the local storage.
Here, the above-mentioned update condition may be a condition for updating the first type information in the local storage. The updating step may be a step for updating the first type information in the local storage.
It can be understood that, in this alternative implementation manner, in the case that it is determined that the update condition is met, the first type of information in the local storage is updated, and the first type of information stored in the local storage can be updated in time, so that the first type of information that is not met with the specification is prevented from being presented to the user. For example, if there is provision to: if the time difference between the time when the first server sends the first type of information to the execution main body and the time when the execution main body presents the first type of information is greater than or equal to a preset time difference threshold value (for example, 1 hour), determining that the execution main body presents the operation of the first type of information as abnormal behavior. Thus, the update condition may be "a time difference between a time when the first server sends the first type information to the execution main body and a time when the execution main body presents the first type information is equal to or greater than a preset time difference threshold", and the update step may be "reacquire the first type information from the first server, store the reacquired first type information in the local storage, and delete the first type information whose storage time is equal to or greater than the time difference threshold from the local storage". In this way, it is possible to avoid determining the operation in which the execution subject presents the first type of information as an abnormal behavior. Here, the operation determined as the abnormal behavior is usually futile for the provider of the second type of information. In some cases, providers of the first type of information will not pay a fee (e.g., an advertising fee) to the second type of information providers for operations determined to be anomalous behavior.
In practice, managers of the first type of information (e.g., advertisements) usually need to push the first type of information to users of various information pushing platforms (e.g., the target applications), so as to achieve the purposes of promoting products, issuing promotional information, and the like. However, in some cases, the first type of information is time sensitive. For example, the first type of information is "XX product five fold on 11/2019", then the first type of information should be presented before 11/2019 (including the current day), and the first type of information should not be presented after 11/2019 (not including the current day). Thus, the optional implementation manner can determine whether to present the first type information according to the timeliness of the first type information. Further, a first type of information is obtained that can be used for presentation.
In addition, the information push platform (such as the target application) needs to stream to the website indicated by the first type of information (such as the advertisement). Thus, the manager of the first kind of information (e.g., advertisement) usually defines some indicators (e.g., browsing times, purchasing times, browsing duration, clicking times, etc.) for evaluating the diversion effect, and determines users meeting certain characteristics as non-valid users and operations meeting certain characteristics as abnormal behavior. For example, if a time difference between a time when the first server sends the first type of information to the execution main body and a time when the execution main body presents the first type of information is greater than or equal to a preset time difference threshold (e.g., 1 hour), the user of the target application flow guide is determined to be a non-valid user. The updating condition may be "a time difference between a time when the first server sends the first type of information to the execution main body and a time when the execution main body presents the first type of information is greater than or equal to a preset time difference threshold", and the updating step may be "reacquire the first type of information from the first server, store the reacquired first type of information in the local storage, and delete the first type of information whose storage time is greater than or equal to the time difference threshold from the local storage". Therefore, the situation that the user of the target application flow guide is judged to be a non-effective user can be avoided to a certain extent, the situation that the operation executed by the execution main body is judged to be abnormal behavior is avoided to a certain extent, and further the reduction of the cost paid by the provider of the first type of information to the provider of the second type of information is avoided to a certain extent.
In some optional implementations of this embodiment, the update condition includes any one of:
in the first item, the amount of the first type information currently stored in the local memory is less than or equal to a preset amount threshold.
It is to be understood that, in some cases, the execution main body may present a plurality of pieces of first-type information at a time, and thus, when the number of pieces of first-type information currently stored in the local storage is smaller than or equal to a preset number threshold (for example, the number of pieces of first-type information currently presented by the execution main body at a time), by performing the updating step, the number of pieces of first-type information currently stored in the local storage may be made larger than the preset threshold, so that in a case where the first-type information to be presented is obtained from the local storage, the first-type information presented at a time by the execution main body may be obtained from the local storage, thereby avoiding a time delay problem of presenting the first-type information due to the fact that the number of pieces of first-type information presented is larger than the number of pieces of first-type information stored in the local storage.
And in the second item, the local memory stores first type information with the storage time length exceeding a first preset time length.
Here, each of the first type information stored in the local storage may have the same first preset time duration, and each of the first type information stored in the local storage may also have a different first preset time duration. For example, each first type of information may have a first preset duration corresponding to the first type of information. The first preset time duration may be predetermined and used for indicating the time duration of the validity period of the first type of information.
It can be understood that, for the first type of information whose storage duration exceeds the first preset duration, the interval between the time when the execution main body acquires the first type of information and the time when the execution main body presents the first type of information is often long, and if the first type of information whose storage duration exceeds the first preset duration is presented, it is easy for the provider of the first type of information to determine that the first type of information is abnormal. It should be understood that deleting the first type of information whose storage time duration exceeds the first preset time duration from the local storage and retrieving the first type of information from the first server may avoid determining the user of the target application flow guide as a non-valid user.
And thirdly, detecting the running operation executed by the user on the target application, and storing the first type of information with the storage time length exceeding the first preset time length in the local memory.
It can be understood that, with the third item as the update condition, the number of times of executing the update step can be reduced on the premise of reducing the probability that the behavior of the execution subject presenting the first type of information and the behavior of the user clicking the first type of information are determined as abnormal behavior, as compared with the second item as the update condition. In addition, the third item is used as an update condition, and whether the first type of information stored in the local storage needs to be updated or not can be detected after the target application runs.
And fourthly, the time from the last time when the first type of information is acquired from the first server exceeds a second preset time length, and the first type of information of which the storage time length exceeds the first preset time length is stored in the local memory.
It can be understood that, with the fourth item as the update condition, the number of times of executing the update step can be reduced on the premise of reducing the probability that the behavior of the execution subject presenting the first type of information and the behavior of the user clicking the first type of information are determined as abnormal behavior, as compared with the second item as the update condition. In addition, with the fourth item as an update condition, it can also be periodically detected whether the first type information stored in the local storage needs to be updated.
In some optional implementation manners of this embodiment, each piece of first-type information stored in the local storage has a first preset duration corresponding to the piece of first-type information.
It can be understood that, in the alternative implementation manner, a different first preset duration may be set for each first type of information, so that flexibility of managing (for example, deleting the first type of information and presenting the first type of information) the first type of information is improved.
In some optional implementations of this embodiment, the updating step includes at least one of:
the first item is to retrieve the first type of information from the first server and store the retrieved first type of information to the local storage.
It is understood that, in general, the first type information retrieved from the first server is the first type information within the valid period, and thus, the first type information within the non-valid period can be prevented from being presented to some extent.
And a second item for deleting the first type of information, which meets a predetermined deletion condition, from the local storage.
It can be understood that, in order to avoid excessive first-type information stored in the local storage, part of the stored first-type information may be deleted, thereby reducing the occupation of storage space.
In some optional implementations of this embodiment, the deletion condition includes any one of:
the first item, the first type information is the first type information with the longest storage time in the first type information stored in the local memory.
It can be understood that the first type of information with the longest storage time has the highest probability of being the first type of information within the non-validity period, and therefore, the first type of information within the non-validity period can be prevented from being presented to some extent.
And the second item, wherein the current time is later than the latest presentation time set for the first type of information.
It will be appreciated that a latest presentation time may be set for each of the first type of information, after which the first type of information is not typically required to be presented (e.g., when the first type of information is an advertisement, a user clicking on the first type of information after the latest presentation time may not obtain an advertising fee).
In some optional implementations of this embodiment, after performing step 202, the execution main body may further perform the following steps: and under the condition of acquiring the first type of information indicated by the first type of information acquisition request, presenting the first type of information indicated by the first type of information acquisition request and the second type of information indicated by the second type of information acquisition request through the target application.
It can be understood that, in the case of acquiring the first type of information indicated by the first type of information acquisition request, the optional implementation manner may present the first type of information indicated by the first type of information acquisition request and the second type of information indicated by the second type of information acquisition request through the target application, so as to present the first type of information more timely, thereby ensuring timeliness of presentation of the first type of information.
In some optional implementation manners of this embodiment, the executing main body may further send the first-type information obtaining request to the first server again when the first-type information indicated by the first-type information obtaining request is not obtained within a preset time period. The preset time period takes the moment of acquiring the second type of information indicated by the second type of information acquisition request as a starting point.
It can be understood that, in this alternative implementation manner, when the first type of information indicated by the first type of information acquisition request is not acquired within a preset time period, the first type of information may be automatically acquired from the first server again until the first type of information is acquired.
In some optional implementation manners of this embodiment, the execution main body may further store the first type information indicated by the first type information acquisition request in the local storage when the first type information indicated by the first type information acquisition request is acquired within a preset time period. The preset time period takes the moment of acquiring the second type of information indicated by the second type of information acquisition request as a starting point.
It is to be understood that, since the executing entity usually presents the first type of information stored in the local storage before performing the step, the alternative implementation may store the first type of information returned by the first server in the local storage after presenting the first type of information, so as to obtain the first type of information within the validity period from the local storage when the first type of information needs to be presented later.
In some optional implementations of this embodiment, the local memory is a local cache.
It can be understood that, when the local storage is a local cache, the executing body may obtain the first type of information from the local storage more quickly, thereby increasing the speed of presenting, by the target application, the second type of information indicated by the second type of information obtaining request and the first type of information stored in the local storage.
In some optional implementation manners of this embodiment, the target application presents the first type of information and the second type of information in an information flow manner.
In the prior art, presentation schemes for a first type of information (e.g. advertisements) and a second type of information (e.g. other information than advertisements) generally include the following three types:
the first scheme is as follows: the terminal equipment requests the first type information and the second type information from the same server, and the server directly returns the combined first type information and the second type information for the terminal equipment to present.
Scheme II: the terminal equipment simultaneously and respectively requests the second type information from the server stored with the second type information and requests the first type information from the server stored with the first type information. Then, the terminal device first presents the second type of information and then inserts the first type of information between the second type of information.
The third scheme is as follows: the terminal equipment requests the first type information from the server storing the first type information in advance and then stores the first type information locally. When the terminal equipment needs to present the information, the second type information is requested from the server stored with the second type information, and then the first type information stored in the local is inserted between the second type information.
Wherein, the above-mentioned scheme has the following drawback separately:
the first scheme has the following disadvantages: with the use of a service where the first type of information (e.g. advertisements) and the second type of information are stored in the same address indication, there is a lack of flexibility in managing the first type of information. Also, the first type of information (e.g., advertisements) that is more expensive cannot be used.
The second scheme has the following disadvantages: sometimes, the first type information is returned slowly, so that the user has browsed the whole information flow, and the first type information is not inserted; in some cases, the first server for storing the first type of information considers the user as an invalid user and does not return the first type of information directly.
The third scheme has the disadvantages that: the time when the first type of information is returned and the time when the first type of information is displayed and clicked are often separated by a long time and are considered to be abnormal behaviors.
Here, the optional implementation manner may insert the first type of information into the second type of information in time on the basis of improving the flexibility of managing the first type of information, and may avoid determining a behavior of presenting the first type of information to a user or clicking the first type of information by the user as an abnormal behavior to a certain extent.
In some optional implementation manners of this embodiment, a time difference between a time when the terminal device acquires the first type of information and a time when the terminal device presents the first type of information is smaller than a preset time difference threshold.
It can be understood that, in the optional implementation manner, the time difference between the time when the terminal device acquires the first type of information and the time when the terminal device presents the first type of information is controlled to be smaller than the preset time difference threshold, so that the situation that the user of the target application flow guide is judged to be a non-effective user is avoided to a certain extent.
With further reference to fig. 4, a flow 400 of yet another embodiment of a method for presenting information is shown. The method for presenting the information is applied to terminal equipment, wherein the terminal equipment is provided with a target application and comprises a local memory for storing the first type of information. The method for presenting information comprises the following steps:
step 401, in response to detecting that the user executes the operation on the target application and in response to that the local storage stores the first type of information whose storage duration exceeds a first preset duration, obtaining the first type of information from the first server, and storing the obtained first type of information in the local storage. Thereafter, step 402 is performed.
In this embodiment, an execution main body (for example, the terminal device shown in fig. 1) of the method for presenting information may obtain, when detecting that a running operation performed on a target application by a user is performed and when first type information whose storage duration exceeds a first preset duration is stored in a local storage, the first type information from a first server, and store the obtained first type information in the local storage.
Here, the target application may be an application for presenting the first type of information and the second type of information. The local storage may be a removable hard disk, an optical disk, or the like. The information acquisition operation may be an operation for instructing the execution main body to acquire information as described above.
Here, each of the first type information stored in the local storage may have the same first preset time duration, and each of the first type information stored in the local storage may also have a different first preset time duration, for example, each of the first type information may have a first preset time duration corresponding to the first type information. The first preset time period may be predetermined and used for indicating the time period of the validity period of the first type of information.
The first type of information and the second type of information may be stored in a first server and a second server, respectively. Typically, the first type of information and the second type of information each represent different types of information. The first type of information and the second type of information may be managed by different managers, respectively. By way of example, the first type of information may be advertisements and the second type of information may be other information (e.g., news information) in addition to advertisements. The first type of information is typically managed by a provider of the first type of information (e.g., an advertiser). The second type of information is typically managed by a provider of the second type of information (e.g., the person who operates the second type of information). In addition, in general, after a user of a target application clicks on or otherwise manipulates a first type of information presented on the target application, a provider of the first type of information needs to pay a certain fee (e.g., an advertisement fee) to a provider of a second type of information.
Step 402, in response to detecting that the user performs an information obtaining operation through the target application, sending a first type information obtaining request to the first server, and sending a second type information obtaining request to the second server. Thereafter, step 403 is performed.
In this embodiment, step 402 is substantially the same as step 201 in the corresponding embodiment of fig. 2, and is not described here again.
In step 403, in response to acquiring the second type information indicated by the second type information acquisition request, it is determined whether the first type information indicated by the first type information acquisition request has been acquired. Then, if yes, go to step 404; if not, go to step 405.
In this embodiment, step 403 is substantially the same as step 202 in the corresponding embodiment of fig. 2, and is not described herein again.
Step 404, presenting the first type information indicated by the first type information acquisition request and the second type information indicated by the second type information acquisition request through the target application.
In this embodiment, the execution main body may present, through the target application, the first type information indicated by the first type information acquisition request and the second type information indicated by the second type information acquisition request.
And step 405, presenting the second type information indicated by the second type information acquisition request and the first type information stored in the local storage through the target application.
In this embodiment, step 405 is substantially the same as step 203 in the corresponding embodiment of fig. 2, and is not described herein again.
It should be noted that, in addition to the above-mentioned contents, the present embodiment may further include the same or similar features and effects as those of the embodiment corresponding to fig. 2, and details are not repeated herein.
As can be seen from fig. 4, compared with the embodiment corresponding to fig. 2, the flow 400 of the method for presenting information in the present embodiment highlights a step of updating the first type of information stored in the local storage, and a step of presenting, by the target application, the first type of information indicated by the first type of information acquisition request and the second type of information indicated by the second type of information acquisition request in the case where the first type of information indicated by the first type of information acquisition request has been acquired. Therefore, the scheme described in this embodiment may detect whether the first type of information stored in the local storage needs to be updated after the target application runs, so as to reduce the number of times of executing the update step on the premise of reducing the probability of determining the behavior of the execution main body presenting the first type of information and the behavior of the user clicking the first type of information as the abnormal behavior. In addition, according to the scheme described in this embodiment, when the first type of information indicated by the first type of information acquisition request is acquired, the first type of information indicated by the first type of information acquisition request and the second type of information indicated by the second type of information acquisition request can be presented through the target application, so that the first type of information can be presented more timely, and thus, timeliness of presentation of the first type of information is ensured.
Continuing to refer to FIG. 5, a flow 500 of yet another embodiment of a method for presenting information is illustrated. The method for presenting the information is applied to the terminal equipment, wherein the terminal equipment is provided with a target application, and the terminal equipment comprises a local memory for storing the first type of information. The method for presenting information comprises the following steps:
step 501, in response to detecting that a user executes an operation on a target application and in response to that first type information with a storage time length exceeding a first preset time length is stored in a local storage, obtaining the first type information from a first server, and storing the obtained first type information to the local storage. Thereafter, step 502 is performed.
In this embodiment, step 501 is substantially the same as step 401 in the embodiment corresponding to fig. 4, and is not described here again.
Step 502, in response to detecting that the user performs the information obtaining operation through the target application, sending a first type information obtaining request to the first server, and sending a second type information obtaining request to the second server. Thereafter, step 503 is performed.
In this embodiment, step 502 is substantially the same as step 402 in the embodiment corresponding to fig. 4, and is not described here again.
Step 503, in response to acquiring the second type information indicated by the second type information acquisition request, determining whether the first type information indicated by the first type information acquisition request has been acquired. If yes, go to step 504; if not, go to step 505.
In this embodiment, step 503 is substantially the same as step 403 in the embodiment corresponding to fig. 4, and is not described here again.
Step 504, presenting the first type information indicated by the first type information obtaining request and the second type information indicated by the second type information obtaining request through the target application.
In this embodiment, step 504 is substantially the same as step 404 in the embodiment corresponding to fig. 4, and is not described here again.
And 505, presenting the second type information indicated by the second type information acquisition request and the first type information stored in the local storage through the target application. Thereafter, step 506 is performed.
In this embodiment, step 505 is substantially the same as step 405 in the embodiment corresponding to fig. 4, and is not described here again.
Step 506, it is determined whether the first type information indicated by the first type information obtaining request is obtained within a preset time period. If yes, go to step 507, otherwise go to step 508.
In this embodiment, the execution main body may further determine whether the first type information indicated by the first type information acquisition request is acquired within a preset time period. The preset time period takes the moment of acquiring the second type of information indicated by the second type of information acquisition request as a starting point. The duration corresponding to the preset time period is predetermined.
Step 507, storing the first type information indicated by the first type information obtaining request in a local memory.
In this embodiment, the execution main body may further store the first type information indicated by the first type information acquisition request in the local memory.
And step 508, re-sending the first-type information acquisition request to the first server.
In this embodiment, the execution main body may further resend the first type information acquisition request to the first server.
It should be noted that, in addition to the above-mentioned contents, the present embodiment may further include the same or similar features and effects as those of the embodiment corresponding to fig. 2, and details are not repeated herein.
As can be seen from fig. 5, compared with the embodiment corresponding to fig. 4, the flow 500 of the method for presenting information in the present embodiment highlights the steps performed in the case where the first type information indicated by the first type information acquisition request is acquired within the preset time period, and the steps performed in the case where the first type information indicated by the first type information acquisition request is not acquired within the preset time period. Therefore, the scheme described in this embodiment may automatically send the first type information acquisition request to the first server multiple times, so as to acquire the first type information returned by the first type server. In addition, after the first type of information is presented, the first type of information returned by the first server is stored in the local storage, and when the first type of information needs to be presented, the first type of information within the validity period can be obtained from the local storage for presentation, so that the speed of presenting the first type of information is improved on the premise that the presentation time of the first type of information is within the validity period.
Referring now to fig. 6, a block diagram of a terminal device (e.g., terminal device in fig. 1) 600 suitable for use in implementing embodiments of the present disclosure is shown. The terminal device shown in fig. 6 is only an example, and should not bring any limitation to the functions and the use range of the embodiments of the present disclosure.
As shown in fig. 6, the terminal device 600 may include a processing means (e.g., a central processing unit, a graphic processor, etc.) 601 that may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage means 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the terminal apparatus 600 are also stored. The processing device 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
Generally, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; includes a storage device 608; and a communication device 609. The communication means 609 may allow the terminal device 600 to perform wireless or wired communication with other devices to exchange data. While fig. 6 illustrates a terminal apparatus 600 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided. Each block shown in fig. 6 may represent one device or may represent multiple devices as desired.
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 embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication means 609, or installed from the storage means 608, or installed from the ROM 602. The computer program, when executed by the processing device 601, performs the above-described functions defined in the methods of embodiments of the present disclosure.
It should be noted that the computer readable medium described in the embodiments of the present disclosure may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In embodiments of the disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In embodiments of the present disclosure, however, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
The computer readable medium may be contained in the terminal device; or may exist separately without being assembled into the terminal device. The computer readable medium carries one or more programs which, when executed by the terminal device, cause the terminal device to: in response to detecting that a user executes information acquisition operation through a target application, sending a first-class information acquisition request to a first server and sending a second-class information acquisition request to a second server, wherein the first server stores first-class information indicated by the first-class information acquisition request, and the second server stores second-class information indicated by the second-class information acquisition request; responding to the second type information indicated by the acquired second type information acquisition request, and determining whether the first type information indicated by the first type information acquisition request is acquired; and in response to the first type of information indicated by the first type of information acquisition request is not acquired, presenting the second type of information indicated by the second type of information acquisition request and the first type of information stored in the local memory through the target application.
Computer program code for carrying out operations for embodiments of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
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 disclosure. 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 foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention in the present disclosure is not limited to the specific combination of the above-mentioned features, but also encompasses other embodiments in which any combination of the above-mentioned features or their equivalents is possible without departing from the inventive concept as defined above. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.

Claims (14)

1. A method for presenting information, applied to a terminal device, wherein the terminal device is installed with a target application, the terminal device comprises a local storage for storing a first type of information, the method comprising:
in response to detecting that a user performs information acquisition operation through the target application, sending a first-class information acquisition request to a first server and sending a second-class information acquisition request to a second server, wherein the first server stores first-class information indicated by the first-class information acquisition request, and the second server stores second-class information indicated by the second-class information acquisition request;
in response to the second type of information indicated by the second type of information acquisition request, determining whether the first type of information indicated by the first type of information acquisition request is acquired;
and in response to not acquiring the first type of information indicated by the first type of information acquisition request, presenting the second type of information indicated by the second type of information acquisition request and the first type of information stored in the local memory through the target application.
2. The method of claim 1, wherein the method further comprises:
in response to a predetermined update condition being met, a predetermined update step is performed to update the first type of information in the local storage.
3. The method of claim 2, wherein the update condition comprises any one of:
the number of the first type information currently stored in the local memory is less than or equal to a preset number threshold;
the local memory stores first type information with the storage time length exceeding a first preset time length;
detecting running operation executed by a user on the target application, wherein first type information with the storage duration exceeding the first preset duration is stored in the local storage;
the time when the first type of information is obtained from the first server last time exceeds a second preset time length, and the first type of information with the storage time length exceeding the first preset time length is stored in the local storage.
4. The method according to claim 3, wherein each first type of information stored in the local memory has a first preset duration corresponding to the first type of information.
5. The method of claim 2, wherein the updating step comprises at least one of:
the first type information is obtained from the first server again, and the obtained first type information is stored in the local storage;
and deleting the first type information meeting the predetermined deleting condition from the local storage.
6. The method of claim 5, wherein the deletion condition comprises any one of:
the first type information is the first type information with the longest storage time length in the first type information stored in the local memory;
the current time is later than the latest presentation time set for the first type of information.
7. The method according to claim 1, wherein after determining whether the first type information indicated by the first type information acquisition request has been acquired in response to acquiring the second type information indicated by the second type information acquisition request, the method further comprises:
and responding to the first type of information indicated by the first type of information acquisition request, and presenting the first type of information indicated by the first type of information acquisition request and the second type of information indicated by the second type of information acquisition request through the target application.
8. The method of claim 1, wherein the method further comprises:
and in response to that the first type information indicated by the first type information acquisition request is not acquired within a preset time period, re-sending the first type information acquisition request to the first server, wherein the preset time period takes the moment of acquiring the second type information indicated by the second type information acquisition request as a starting point.
9. The method of claim 1, wherein the method further comprises:
and in response to the first type of information indicated by the first type of information acquisition request acquired within a preset time period, storing the first type of information indicated by the first type of information acquisition request in the local memory, wherein the preset time period takes the time when the second type of information indicated by the second type of information acquisition request is acquired as a starting point.
10. The method of any of claims 1-9, wherein the local memory is a local cache.
11. The method according to one of claims 1 to 9, wherein the target application presents the first type of information and the second type of information in an information flow.
12. The method according to one of claims 1 to 9, wherein a time difference between a time when the terminal device acquires the first type of information and a time when the terminal device presents the first type of information is smaller than a preset time difference threshold.
13. A terminal device, comprising:
one or more processors;
a storage device having one or more programs stored thereon,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-12.
14. A computer-readable medium, on which a computer program is stored, wherein the computer program, when being executed by a processor, carries out the method according to any one of claims 1-12.
CN201910742698.7A 2019-08-13 2019-08-13 Method and apparatus for presenting information Active CN110442825B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910742698.7A CN110442825B (en) 2019-08-13 2019-08-13 Method and apparatus for presenting information

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910742698.7A CN110442825B (en) 2019-08-13 2019-08-13 Method and apparatus for presenting information

Publications (2)

Publication Number Publication Date
CN110442825A CN110442825A (en) 2019-11-12
CN110442825B true CN110442825B (en) 2022-07-12

Family

ID=68434998

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910742698.7A Active CN110442825B (en) 2019-08-13 2019-08-13 Method and apparatus for presenting information

Country Status (1)

Country Link
CN (1) CN110442825B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106874460A (en) * 2017-02-14 2017-06-20 腾讯科技（深圳）有限公司 Information recommendation method, apparatus and system
CN108965389A (en) * 2018-06-13 2018-12-07 连尚（新昌）网络科技有限公司 Method for showing information
CN109471695A (en) * 2018-10-31 2019-03-15 北京字节跳动网络技术有限公司 Method and apparatus for more new data
CN109725784A (en) * 2017-10-30 2019-05-07 华为技术有限公司 Information display method and terminal device

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101551888A (en) * 2008-04-02 2009-10-07 上海亿动信息技术有限公司 Advertisement information publishing system and corresponding advertisement publishing control method
CN102930037B (en) * 2012-11-09 2017-04-05 北京奇虎科技有限公司 page loading method and device
CN105897833A (en) * 2015-12-01 2016-08-24 乐视网信息技术（北京）股份有限公司 Advertisement data processing method and router
CN106600343B (en) * 2016-12-30 2020-02-14 中广热点云科技有限公司 Video content associated online video advertisement management method and system
CN106940729A (en) * 2017-03-24 2017-07-11 北京金山安全软件有限公司 Advertisement display method and device and electronic equipment
CN110061900B (en) * 2018-01-18 2021-11-02 腾讯科技（深圳）有限公司 Message display method, device, terminal and computer readable storage medium
CN109816198A (en) * 2018-12-12 2019-05-28 平安科技（深圳）有限公司 Method, apparatus, computer equipment and the storage medium of data processing
CN110011907B (en) * 2019-04-16 2021-05-07 腾讯科技（深圳）有限公司 Message display method, message processing method and device

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106874460A (en) * 2017-02-14 2017-06-20 腾讯科技（深圳）有限公司 Information recommendation method, apparatus and system
CN109725784A (en) * 2017-10-30 2019-05-07 华为技术有限公司 Information display method and terminal device
CN108965389A (en) * 2018-06-13 2018-12-07 连尚（新昌）网络科技有限公司 Method for showing information
CN109471695A (en) * 2018-10-31 2019-03-15 北京字节跳动网络技术有限公司 Method and apparatus for more new data

Also Published As

Publication number Publication date
CN110442825A (en) 2019-11-12

Similar Documents

Publication Publication Date Title
AU2018200833B2 (en) Providing content to a user across multiple devices
JP6306187B2 (en) Dynamic telephone number assignment
CN108965389B (en) Method for displaying information
US8775554B2 (en) Cloud-based web page applications for extending functionality
CN108540508B (en) Method, device and equipment for pushing information
CN109992719B (en) Method and apparatus for determining push priority information
US10242102B2 (en) Network crawling prioritization
CN106897202B (en) Method and apparatus for outputting data
CN111694629A (en) Information display method and device and electronic equipment
US20150154659A1 (en) System and method for displaying transitional mobile ads during network page download latency time
US11146860B2 (en) Service processing method, device, and intelligent terminal for obtaining and displaying data based on texture data corresponding to a target service
CN111698365A (en) Information display method and device
CN111143662A (en) Content recommendation method, device and computer storage medium
CN110442825B (en) Method and apparatus for presenting information
WO2015096791A1 (en) Method and system for releasing media content
CN107480269B (en) Object display method and system, medium and computing equipment
CN110619101A (en) Method and apparatus for processing information
WO2018205642A1 (en) Video revenue calculation modeling device and method, video recommendation device and method, server, and storage medium
JP2024500300A (en) Information interaction methods, devices, and equipment
CN107666497B (en) Data access method and device
CN113449230A (en) Method and system for determining exposure element, client and server
CN113450170A (en) Information display method and device
US20150100920A1 (en) Companion content presented along with invitational content item
US9047627B1 (en) Publisher side file support for expandable content items
US20240257179A1 (en) User interest detection for content generation

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant