Recommended object preview method, device and electronic equipment for application program

Abstract

The application provides a recommended object preview method and device of an application program, an electronic device, a computer readable storage medium and a computer program product, and the related embodiments can be applied to various scenes such as cloud technology, artificial intelligence and intelligent transportation. The recommended object preview method of the application program comprises: in response to a binding operation on a binding entrance, collecting object identification information of a recommended object in the binding entrance; sending the binding identification information and the object identification information of the recommended object to a delivery server to establish a binding relationship; in response to a triggering operation on the application program, sending a recommendation request to the delivery server, wherein the recommendation request comprises the binding identification information; receiving object form information of the recommended object from the delivery server, and presenting the recommended object in the application program according to the object form information of the recommended object. Through the application, object preview can be realized in the actual recommendation scene, and the preview demand of a user for a specific object can be met.

Description

Technical Field

[0001] This application relates to computer technology, and more particularly to a method, apparatus, electronic device, computer-readable storage medium, and computer program product for previewing recommended objects of an application. Background Technology

[0002] With the rapid development of computer technology, object recommendation has become deeply integrated into people's daily lives. For example, electronic devices installed with applications can perform object recommendations during application operation, such as recommending news in news applications and recommending videos in video applications.

[0003] In some cases, there is a need to preview specific objects, such as when advertisers need to preview the effectiveness of their ads. In solutions provided by relevant technologies, professionals typically create mockups or videos of the specific object and send them to the previewer (e.g., for offline demonstrations). However, this preview method does not align with the actual way the object is recommended, hindering the previewer's understanding of the actual recommended effect. Summary of the Invention

[0004] This application provides a method, apparatus, electronic device, computer-readable storage medium, and computer program product for previewing recommended objects in an application. By establishing a binding relationship, the application can recommend specified objects to be recommended, thereby enabling the preview of the objects to be recommended in the actual recommendation environment.

[0005] The technical solution of this application embodiment is implemented as follows: This application provides a method for previewing recommended objects in an application, including: In response to a binding operation for a binding entry point, the object identifier information of the object to be recommended in the binding entry point is collected; wherein, the binding entry point is generated based on the object identifier information of the object to be recommended, and the object to be recommended is multimedia information to be presented in the application; The binding identifier information and the object identifier information of the object to be recommended are sent to the delivery server so that the binding relationship between the binding identifier information and the object identifier information of the object to be recommended can be established in the delivery server. In response to a triggering operation on the application, a recommendation request is sent to the delivery server, wherein the recommendation request includes the binding identification information; The application receives the object form information of the object to be recommended from the delivery server and presents the object to be recommended in the application based on the object form information. The object to be recommended is obtained by the delivery server querying the binding relationship based on the binding identifier information in the recommendation request. The object form information includes attribute information in multiple dimensions.

[0006] This application provides a method for previewing recommended objects in an application, including: The system receives binding identification information and object identification information of the object to be recommended from the terminal device, and establishes a binding relationship between the binding identification information and the object identification information of the object to be recommended; wherein, the object to be recommended is multimedia information used to be displayed in the application. A recommendation request is received from the terminal device; wherein the recommendation request is sent by the terminal device in response to a triggering operation on the application, and the recommendation request includes the binding identification information; The binding relationship is queried based on the binding identifier information in the recommendation request to obtain the object to be recommended; The object form information of the object to be recommended is sent to the terminal device, so that the terminal device can present the object to be recommended in the application according to the object form information; wherein, the object form information includes attribute information of multiple dimensions.

[0007] This application provides a method for previewing recommended objects in an application, including: Present the binding entry corresponding to the object to be recommended, wherein the object to be recommended is multimedia information used to be displayed in the application; In response to the binding operation for the binding entry, a binding relationship is established between the object to be recommended and the binding identification information; Multiple candidate applications corresponding to the binding identification information are presented, and the candidate applications are used to present the object to be recommended. In response to a selection operation for the plurality of candidate applications, the recommended object retrieved based on the binding relationship is presented in the selected candidate application.

[0008] This application provides a device for previewing recommended objects in an application, comprising: The acquisition module is used to acquire the object identification information of the object to be recommended in the binding entry in response to the binding operation; wherein the binding entry is generated based on the object identification information of the object to be recommended, and the object to be recommended is multimedia information to be displayed in the application. The binding module is used to send the binding identification information and the object identification information of the object to be recommended to the delivery server, so that the binding identification information and the object identification information of the object to be recommended can be bound together in the delivery server. The recommendation module is used to send a recommendation request to the delivery server in response to a triggering operation on the application, wherein the recommendation request includes the binding identification information; The recommendation module is further configured to receive the object form information of the object to be recommended from the delivery server, and present the object to be recommended in the application according to the object form information of the object to be recommended, wherein the object to be recommended is obtained by the delivery server querying the binding relationship according to the binding identifier information in the recommendation request; the object form information includes attribute information of multiple dimensions.

[0009] This application provides a device for previewing recommended objects in an application, comprising: The binding module is used to receive binding identification information and object identification information of the object to be recommended from the terminal device, and to establish a binding relationship between the binding identification information and the object identification information of the object to be recommended; wherein, the object to be recommended is multimedia information used to be displayed in the application. The recommendation module is used for: A recommendation request is received from the terminal device; wherein the recommendation request is sent by the terminal device in response to a triggering operation on the application, and the recommendation request includes the binding identification information; The binding relationship is queried based on the binding identifier information in the recommendation request to obtain the object to be recommended; The object form information of the object to be recommended is sent to the terminal device, so that the terminal device can present the object to be recommended in the application according to the object form information of the object to be recommended; wherein, the object form information includes attribute information of multiple dimensions.

[0010] This application provides a device for previewing recommended objects in an application, comprising: The entry presentation module is used to present the bound entry corresponding to the object to be recommended, wherein the object to be recommended is multimedia information that is displayed in the application. The binding module is used to establish a binding relationship between the object to be recommended and the binding identification information in response to the binding operation for the binding entry. The program presentation module is used to present multiple candidate applications corresponding to the binding identification information, and the candidate applications are used to present the object to be recommended. An object presentation module is used to present the object to be recommended, queried based on the binding relationship, in the selected candidate application in response to a selection operation for the plurality of candidate applications.

[0011] This application provides an electronic device, including: Memory, used to store executable instructions; The processor, when executing executable instructions stored in the memory, implements the recommended object preview method for the application provided in the embodiments of this application.

[0012] This application provides a computer-readable storage medium storing executable instructions for implementing the recommended object preview method of the application provided in this application when executed by a processor.

[0013] This application provides a computer program product, including executable instructions, which, when executed by a processor, implement the recommended object preview method for the application provided in this application.

[0014] The embodiments of this application have the following beneficial effects: By establishing a binding relationship between the object to be recommended and the binding identification information, and making targeted object recommendations in the actual recommendation environment (i.e., in the application) based on the triggered recommendation request and the binding relationship, it is possible to preview specific objects in the actual recommendation environment, fully meeting the preview needs of the previewing party. Attached Figure Description

[0015] Figure 1 This is a schematic diagram of the architecture of the application recommendation object preview system provided in the embodiments of this application; Figure 2A This is a schematic diagram of the architecture of the terminal device provided in the embodiments of this application; Figure 2B This is a schematic diagram of the architecture of the terminal device provided in the embodiments of this application; Figure 2C This is a schematic diagram of the server architecture provided in an embodiment of this application; Figure 3A This is a flowchart illustrating the method for previewing recommended objects in an application provided in this embodiment. Figure 3B This is a flowchart illustrating the method for previewing recommended objects in an application provided in this embodiment. Figure 3C This is a flowchart illustrating the method for previewing recommended objects in an application provided in this embodiment. Figure 3D This is a flowchart illustrating the method for previewing recommended objects in an application provided in this embodiment. Figure 4 This is a flowchart illustrating the method for previewing recommended objects in an application provided in this embodiment. Figure 5 This is a flowchart illustrating the method for previewing recommended objects in an application provided in this embodiment. Figure 6 This is a flowchart illustrating the method for previewing recommended objects in an application provided in this embodiment. Figure 7 This is a schematic diagram of the query interface provided in an embodiment of this application; Figure 8 This is a schematic diagram of the QR code scanning interface provided in an embodiment of this application; Figure 9 This is a schematic diagram of the selection interface provided in an embodiment of this application; Figure 10 This is a schematic diagram of the running interface of the target application provided in the embodiments of this application; Figure 11 This is a flowchart illustrating the advertising preview scheme provided in an embodiment of this application; Figure 12 This is a schematic diagram of the reading and writing process of the advertising library provided in the embodiments of this application; Figure 13 This is a schematic diagram of the device information acquisition module provided in an embodiment of this application. Detailed Implementation

[0016] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0017] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0018] In the following description, the terms "first," "second," and "third" are used merely to distinguish similar objects and do not represent a specific ordering of the objects. It is understood that "first," "second," and "third" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein. In the following description, the term "multiple" means at least two.

[0019] In the implementation of this application, the collection and processing of relevant data should strictly comply with the requirements of relevant laws and regulations, obtain the informed consent or separate consent of the personal information subject, and carry out subsequent data use and processing within the scope of laws and regulations and the authorization of the personal information subject.

[0020] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0021] Before providing a further detailed description of the embodiments of this application, the nouns and terms involved in the embodiments of this application will be explained, and the nouns and terms involved in the embodiments of this application shall be interpreted as follows.

[0022] 1) Object: This generally refers to an object that supports recommendation operations. For example, it could be multimedia information used to display within an application, such as multimedia advertisements. Objects can be described and represented through object form information, which can include the object's attributes across multiple dimensions. Taking an advertisement as an example, object form information could include the creative materials used in the advertisement, the material specifications, and the type of product advertised. Different objects can be distinguished through object identification information.

[0023] 2) Binding Target: This indicates the relevant identity for binding, and can include either a binding device or a binding account. That is, in this embodiment, an object can be bound to a binding device or a binding account. Different binding targets can be distinguished by binding identification information (or identity information).

[0024] 3) Binding Relationship: This indicates the correspondence between the object to be recommended and the binding target. Since object identification information can be used to represent objects, and binding identification information can be used to represent binding targets, a binding relationship can be established between the object identification information of an object and the binding identification information of the binding target.

[0025] 4) Binding Entry Point: Generated based on object identification information, used to prompt the establishment of a binding relationship. This application embodiment does not limit the type of binding entry point, such as including but not limited to QR codes and buttons.

[0026] 5) Database: A database is a collection of data stored together in a certain way, which can be shared by multiple users, has the lowest possible redundancy, and is independent of the application. It can support users to perform operations such as adding, querying, updating, and deleting data.

[0027] This application provides a method, apparatus, electronic device, computer-readable storage medium, and computer program product for previewing recommended objects in an application. It enables the recommendation of specified objects within the application, achieving object previewing in a real-world recommendation environment, while simultaneously improving the utilization of computing resources during the object preview process. The following describes exemplary applications of the electronic device provided in this application. The electronic device provided in this application can be implemented as various types of terminal devices or as a server.

[0028] See Figure 1 , Figure 1 This is a schematic diagram of the architecture of the application recommendation preview system 100 provided in this application embodiment. Terminal device 400 connects to server 200 through network 300, terminal device 500 connects to server 200 through network 300, and server 200 connects to database 600. Network 300 can be a wide area network or a local area network, or a combination of both.

[0029] In some embodiments, taking an electronic device as a terminal device as an example, the application recommendation object preview method provided in this application embodiment can be implemented by the terminal device. Taking terminal device 400 as an example, terminal device 400 can obtain query form information; match the query form information with the object form information corresponding to multiple candidate objects respectively, and take the candidate objects corresponding to the successfully matched object form information as the objects to be recommended; generate a binding entry based on the object identifier information of the objects to be recommended; in response to the binding operation for the binding entry, collect the object identifier information of the objects to be recommended in the binding entry; establish a binding relationship between the object identifier information of the objects to be recommended and the binding identifier information of the binding target; in response to a recommendation request triggered by the application, query the binding relationship based on the binding identifier information in the recommendation request, and perform a recommendation operation for the application based on the queried objects to be recommended (such as presenting the queried objects to be recommended in the application interface). The application can be an application running on terminal device 400, or an application running on an electronic device different from terminal device 400. The object form information corresponding to multiple candidate objects can be stored locally on terminal device 400, or obtained by terminal device 400 from external sources.

[0030] In some embodiments, the application recommendation object preview method provided in this application embodiment can also be implemented collaboratively by a terminal device and a server. Taking the case of collaborative implementation by a terminal device 400 and a server 200 (i.e., a delivery server) as an example, the terminal device 400 can send the acquired query form information to the server 200, so that the server 200 can match the query form information with the object form information corresponding to multiple candidate objects respectively, and take the candidate objects corresponding to the successfully matched object form information as the objects to be recommended, and send the object identification information of the objects to be recommended to the terminal device 400. The terminal device 400 generates a binding entry based on the received object identification information of the objects to be recommended, and in response to the binding operation for the binding entry, collects the object identification information of the objects to be recommended in the binding entry. The terminal device 400 notifies the server 200 based on the object identification information of the objects to be recommended and the binding identification information of the binding target, so that the server 200 establishes a binding relationship between the object identification information of the objects to be recommended and the binding identification information of the binding target. Terminal device 400 sends a recommendation request triggered by an application to server 200. Server 200 queries the binding relationship based on the binding identifier information in the recommendation request and sends the object form information of the retrieved object to be recommended to terminal device 400, so that terminal device 400 can present the object to be recommended in the application based on the received object form information. The application can run within terminal device 400.

[0031] Taking the collaborative implementation of terminal devices 400 and 500 and server 200 as an example, terminal device 400 sends the acquired query form information to server 200. Server 200 matches the received query form information with the object form information corresponding to multiple candidate objects, and selects the candidate objects corresponding to the successfully matched object form information as the objects to be recommended. Server 200 notifies terminal device 400 based on the object identifier information of the objects to be recommended, so that terminal device 400 generates a binding entry based on the object identifier information of the objects to be recommended. Terminal device 500 performs a binding operation on the binding entry presented by terminal device 400 (such as scanning a QR code) to collect the object identifier information of the objects to be recommended in the binding entry, and at the same time collects the binding identifier information of the binding target in terminal device 500. Terminal device 500 notifies server 200 based on the object identifier information of the objects to be recommended and the binding identifier information of the binding target. Upon receiving the notification, server 200 establishes a binding relationship between the object identifier information of the objects to be recommended and the binding identifier information of the binding target. Based on the established binding relationship on server 200, terminal device 500 sends a recommendation request triggered by the application to server 200. Server 200 queries the binding relationship according to the binding identifier information in the recommendation request and sends the object form information of the retrieved object to be recommended to terminal device 500, so that terminal device 500 can present the object to be recommended in the application according to the received object form information. The application can run within terminal device 500.

[0032] In some embodiments, various results involved in the preview process of recommended objects (such as object identification information, binding identification information, object morphology information, binding relationships, etc.) can be stored in the blockchain. Because the blockchain is immutable, the accuracy of the data in the blockchain can be guaranteed. Electronic devices can send query requests to the blockchain to retrieve the data stored in the blockchain.

[0033] In some embodiments, a terminal device (such as terminal device 400 or terminal device 500 described above) or a server (such as server 200 described above) can implement the application preview method provided in this application embodiment by running a computer program. For example, the computer program can be a native program or software module in an operating system; it can be a native application (APP), i.e., a program that needs to be installed in the operating system to run; it can also be a small program, i.e., a program that only needs to be downloaded to a browser environment to run; or it can be a small program that can be embedded in any APP. In short, the above-mentioned computer program can be any form of application, module, or plugin.

[0034] In some embodiments, server 200 may be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. Terminal devices (such as terminal device 400 or terminal device 500 mentioned above) may be smartphones, tablets, laptops, desktop computers, smart speakers, smartwatches, in-vehicle terminals, smart TVs, etc., but are not limited to these. Terminal devices and servers can be directly or indirectly connected via wired or wireless communication, which is not limited in this embodiment.

[0035] In some embodiments, the database 600 and the server 200 can be set up independently. In some embodiments, the database 600 and the server 200 can also be integrated together, that is, the database 600 can be regarded as existing inside the server 200 and integrated with the server 200, and the server 200 can provide the data management functions of the database 600.

[0036] Taking the electronic device provided in this application as an example, which is a terminal device, it can be understood that in the case where the electronic device is a server, Figure 2A Some parts of the structure shown (such as the user interface, presentation module, and input processing module) can be omitted. See also Figure 2A , Figure 2A This is a structural schematic diagram of the terminal device 400 provided in the embodiments of this application (the structural schematic diagram of the terminal device 500 is similar). Figure 2A The terminal device 400 shown includes at least one processor 410, a memory 450, at least one network interface 420, and a user interface 430. The various components in the terminal device 400 are coupled together via a bus system 440. It is understood that the bus system 440 is used to implement communication between these components. In addition to a data bus, the bus system 440 also includes a power bus, a control bus, and a status signal bus. However, for clarity, ... Figure 2A The general labeled all buses as Bus System 440.

[0037] Processor 410 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor can be a microprocessor or any conventional processor, etc.

[0038] User interface 430 includes one or more output devices 431 that enable the presentation of media content, including one or more speakers and / or one or more visual displays. User interface 430 also includes one or more input devices 432, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.

[0039] The memory 450 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state storage, hard disk drives, optical disk drives, etc. The memory 450 may optionally include one or more storage devices physically located away from the processor 410.

[0040] The memory 450 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), and the volatile memory may be random access memory (RAM). The memory 450 described in this application embodiment is intended to include any suitable type of memory.

[0041] In some embodiments, memory 450 is capable of storing data to support various operations, examples of which include programs, modules, and data structures or subsets or supersets thereof, as illustrated below.

[0042] Operating system 451 includes system programs for handling various basic system services and performing hardware-related tasks, such as the framework layer, core library layer, driver layer, etc., for implementing various basic business functions and handling hardware-based tasks; The network communication module 452 is used to reach other electronic devices via one or more (wired or wireless) network interfaces 420, exemplary network interfaces 420 including: Bluetooth, WiFi, and Universal Serial Bus (USB), etc. Presentation module 453 is configured to enable the presentation of information (e.g., a user interface for operating peripheral devices and displaying content and information) via one or more output devices 431 associated with user interface 430 (e.g., a display screen, a speaker, etc.). The input processing module 454 is used to detect and translate one or more user inputs or interactions from one or more input devices 432.

[0043] In some embodiments, the application recommendation preview device provided in this application can be implemented in software. Figure 2AA preview device 4551 for recommending objects of an application stored in memory 450 is shown. It may be software in the form of programs and plug-ins, including the following software modules: acquisition module 45511, binding module 45512, and recommendation module 45513. Figure 2B A preview device 4552 for a recommended object of an application stored in memory 450 is shown. It may be software in the form of programs and plug-ins, including the following software modules: entry presentation module 45521, binding module 45522, program presentation module 45523, and object presentation module 45524. Figure 2A and Figure 2B The software modules shown are logical, and therefore can be combined or further broken down arbitrarily according to their implemented functions. The functions of each module will be explained below.

[0044] Taking the electronic device provided in this application as a server as an example, see [link to relevant documentation]. Figure 2C , Figure 2C The server 200 provided in this application embodiment (for example, may be...) Figure 1 The diagram shows the architecture of server 200. Figure 2C The server 200 shown includes at least one processor 210, memory 240, and at least one network interface 220. The various components of the server 200 are coupled together via a bus system 230. The functions of the processor 210, network interface 220, bus system 230, and memory 240 can be found in [reference needed]. Figure 2A and Figure 2B The operating system 241 and network communication module 242 in the memory 240 are similarly described in the corresponding embodiments.

[0045] In some embodiments, the application recommendation preview device provided in this application can be implemented in software. Figure 2C A preview device 243 for recommending applications stored in memory 240 is shown. This device can be software in the form of programs and plugins, and includes the following software modules: a binding module 2431 and a recommendation module 2432. These modules are logically linked and can therefore be arbitrarily combined or further separated according to their implemented functions. The functions of each module will be described below.

[0046] The method for previewing recommended objects of the application provided in this application will be described in conjunction with exemplary applications and implementations of the electronic devices provided in the embodiments of this application.

[0047] See Figure 3A , Figure 3A This is a flowchart illustrating the recommended object preview method for an application provided in this embodiment. This method can be executed by an electronic device, such as a terminal device, and will combine... Figure 3A The steps shown are explained.

[0048] In step 101, in response to the binding operation for the binding entry, the object identification information of the object to be recommended in the binding entry is collected; wherein, the binding entry is generated based on the object identification information of the object to be recommended, and the object to be recommended is multimedia information used to be presented in the application.

[0049] Here, for the object, relevant personnel may have a need to preview it. For example, before actually placing an ad, an advertiser needs to preview the ad to determine whether to modify it or whether to place it at all. To address this, in this embodiment, object preview is implemented in an actual recommendation scenario, allowing relevant personnel to experience the recommendation effect of the object in the actual recommendation scenario, thereby fully satisfying their preview needs.

[0050] To facilitate understanding, let's take the example of a candidate object to be recommended. A candidate object can be a pre-specified candidate from multiple candidate objects (e.g., the user specifies which ads from multiple candidate ads to preview), or it can be obtained by filtering multiple candidate objects in a specific way. There is no limit to the number of candidates; there can be one or more. The candidate object is multimedia information intended for presentation in the application.

[0051] Once the target object for recommendation has been identified, the terminal device can present a binding entry point. This binding entry point is generated based on the object identifier information of the target object. This application embodiment does not limit the type of binding entry point, and may include, but is not limited to, QR codes and buttons. Upon receiving a binding operation (i.e., a trigger operation) targeting the binding entry point, the object identifier information of the target object in the binding entry point is collected.

[0052] In step 102, the binding identification information and the object identification information of the object to be recommended are sent to the delivery server so that the binding relationship between the binding identification information and the object identification information of the object to be recommended can be established in the delivery server.

[0053] Here, we collect the identification information of the bound target (hereinafter referred to as binding identification information for easy distinction). The bound target includes either the bound device or the bound account. There is no limit to the number of bound targets; for example, there can be one or more. It is worth noting that the binding identification information of the bound target can be collected passively, such as by user input, or actively, such as by the terminal device calling a specific interface to collect the binding identification information of the bound target.

[0054] The terminal device sends the binding identification information and the object identification information of the object to be recommended to the delivery server. The delivery server then establishes a binding relationship between the binding identification information and the object identification information of the object to be recommended, and stores this information for later use. Essentially, this binding relationship is the binding relationship between the object to be recommended and the binding target.

[0055] It is worth noting that the binding relationship in this application is not limited and can be one-to-one, one-to-many, or many-to-one. For example, a recommended object may have a binding relationship with only one binding target, and that binding target may also have a binding relationship with only the recommended object; another example is that a recommended object may have binding relationships with multiple binding targets; yet another example is that a binding target may have binding relationships with multiple recommended objects.

[0056] In step 103, in response to the triggering operation of the application, a recommendation request is sent to the delivery server, wherein the recommendation request includes binding identification information.

[0057] Here, when the terminal device receives a trigger operation for the application, it sends a recommendation request to the delivery server, wherein the recommendation request includes binding identification information.

[0058] In step 104, the object form information of the object to be recommended is received from the delivery server, and the object to be recommended is presented in the application according to the object form information. The object to be recommended is obtained by the delivery server querying the binding relationship according to the binding identifier information in the recommendation request; the object form information includes attribute information in multiple dimensions.

[0059] When the delivery server receives a recommendation request from the terminal device, it queries the stored binding relationships based on the binding identifier information in the recommendation request. For ease of distinction, the object to be recommended corresponding to the retrieved object identifier information will be referred to as the target object, meaning that the object identifier information of the target object and the binding identifier information in the recommendation request are bound together. Then, the delivery server performs recommendation operations for the application based on the target object. For example, the delivery server sends the object form information of the target object to the terminal device, so that the terminal device can present the object to be recommended in the application based on the object form information. For example, it performs form filling processing based on the object form information of the target object to obtain the corresponding presentation form of the target object, and then presents it in the application in the corresponding presentation form of the target object. Of course, the delivery server can also directly send the presentation form corresponding to the target object to the terminal device, so that the terminal device can present it in the application.

[0060] It's worth noting that multi-dimensional attribute information is used to describe objects from different perspectives. For example, in an advertising scenario, attribute information could include the creative materials used in the advertisement, their specifications, and the type of product being advertised. Furthermore, the recommendation method for target objects is not limited to presentation; it can also be done through methods such as playing audio, depending on the media format of the target object.

[0061] In some embodiments, the above-mentioned presentation of the object to be recommended in the application based on the object form information of the object to be recommended can be achieved in the following manner: when the recommendation conditions are met, the object to be recommended is presented in the application based on the object form information of the object to be recommended; wherein, the recommendation conditions include at least one of the following: the collected real-time device parameters match the recommended device parameters; the risk detection result of the object to be recommended is no risk; the application supports the media format of the object to be recommended.

[0062] Here, when specific recommendation criteria are met, the target object can be presented in the application based on its object form information. These recommendation criteria include at least one of the following: 1) The collected real-time device parameters are consistent with the recommended device parameters. The real-time device parameters can be the device parameters of the terminal device used to run the application. The device parameters can include at least one of the device model and the operating system installed. 2) The risk detection result of the target object is no risk. Here, risk detection processing can be performed on the risk items of the target object to obtain the risk detection result of the target object; 3) The application supports the media format of the target object. For example, when the media format is audio, the application is required to support audio playback; when the media format is image, the application is required to support image rendering.

[0063] By using the above methods, we can increase the necessity of object previewing and avoid wasting computing resources caused by unnecessary object previewing.

[0064] like Figure 3A As shown, this application embodiment establishes a binding relationship, thereby enabling accurate and effective object preview for the application, which can meet the user's preview needs for specified objects to be recommended; at the same time, it can also improve the actual utilization rate of computing resources consumed by electronic devices during object preview.

[0065] In some embodiments, see Figure 3B , Figure 3B This is a flowchart illustrating the recommended object preview method for an application provided in this embodiment of the application. This method can be executed by an electronic device, such as a terminal device. Figure 3B In China, based on Figure 3ABefore step 101, in step 201, query form information can also be obtained; wherein, query form information includes attribute information of at least one dimension among multiple dimensions.

[0066] For example, a terminal device can present attribute input fields across multiple dimensions and, in response to an attribute input operation targeting at least one dimension, construct query form information based on the input attribute information of that at least one dimension. For instance, query form information can be obtained by combining the input attribute information of that at least one dimension. That is, the query form information only needs to cover at least one dimension, not all dimensions. This enhances the freedom and flexibility of object previewing; users can preview objects by inputting attribute information of some dimensions, or the query form information can cover all dimensions.

[0067] In step 202, the query form information is sent to the delivery server so that the delivery server can match the query form information with the object form information corresponding to multiple candidate objects, and use the candidate objects corresponding to the successfully matched object form information as the objects to be recommended.

[0068] For example, the terminal device sends the query form information to the delivery server. The delivery server matches the received query form information with the object form information corresponding to multiple candidate objects stored in the database, and uses the candidate objects corresponding to the successfully matched object form information as the objects to be recommended.

[0069] In step 203, the object identifier information of the object to be recommended is received from the delivery server to generate a binding entry.

[0070] After identifying the target object, the delivery server can send its object identifier information to the terminal device. The terminal device can then generate a binding entry based on this object identifier. Additionally, the delivery server can also send relevant display data for the binding entry to the terminal device, allowing the device to display the binding entry accordingly, thus reducing the workload on the terminal device.

[0071] like Figure 3B As shown, this application embodiment supports specifying the recommended objects to be previewed by querying morphological information, which can improve the freedom and flexibility of object preview and meet users' attribute needs for specific dimensions.

[0072] In some embodiments, see Figure 3C , Figure 3C This is a flowchart illustrating the recommended object preview method for an application provided in this embodiment of the application. This method can be executed by an electronic device, such as a terminal device. Figure 3C In Figure 3A While step 101 is shown, steps 301 or 302 can also be performed, which will be explained separately.

[0073] In step 301, in response to the binding operation for the binding entry, the account identifier information of the binding account corresponding to the binding operation is collected as the binding identifier information.

[0074] This application provides two methods for collecting binding identification information. The first method is that when the terminal device receives a binding operation for the binding entry, it collects the account identification information of the binding account corresponding to the binding operation as the binding identification information. At this time, the binding account is the binding target.

[0075] The binding operation can be triggered based on the binding application. For example, the binding entry can be presented in the interface of the binding application. In this case, the binding account can be an account that is logged in in the binding application.

[0076] It's worth noting that the bound application can be the same as or different from the application used to trigger the referral request (hereinafter referred to as the target application for clarity). When the bound application is different from the target application, they can share the same account. For example, the bound application and the target application can be different applications provided by the same company, and their account data can be shared.

[0077] In step 302, in response to the binding operation for the binding entry, the device identification information of the binding device corresponding to the binding operation is collected through the bridging interface as the binding identification information; wherein, the bridging interface is obtained by encapsulating the native device interface used to collect the device identification information.

[0078] The second approach is that when the terminal device receives a binding operation targeting the binding entry, it collects the device identification information of the binding device (i.e., the terminal device itself) corresponding to the binding operation through the bridging interface, using this information as the binding identification information. The binding operation can be triggered by a binding application; in this case, the bridging interface can be triggered through the binding application to collect the device identification information of the binding device.

[0079] It's worth noting that the bridging interface is a wrapper around the device's native interface used to collect device identification information. Therefore, calling the bridging interface is equivalent to calling the device's native interface, ensuring a high success rate for collecting device identification information. The implementation method of the bridging interface is not limited here; for example, it can be implemented using JSBridge technology. That is, the bridging interface can be a JSBridge interface, which can be triggered by binding to a specific interface in the application (such as an H5 interface).

[0080] This application does not limit the type of binding entry point. For example, a QR code can be generated and presented based on the object identifier information of the object to be recommended. Thus, scanning the QR code can be used as a binding operation for the binding entry point. For the terminal device, upon receiving a QR code scanning operation, it can read the object identifier information of the object to be recommended from the QR code and simultaneously trigger the collection of the binding identifier information of the binding target corresponding to the binding operation. In cases where a bridging interface needs to be triggered, a QR code can be generated based on the redirection interface address and the object identifier information of the object to be recommended. Thus, upon receiving a QR code scanning operation, the corresponding interface can be accessed based on the read redirection interface address to trigger the bridging interface of that interface, thereby achieving the collection of device identifier information.

[0081] like Figure 3C The embodiments of this application can improve the flexibility of collecting and binding identification information, and are applicable to object preview requirements in different application scenarios, such as object preview based on account identification information or object preview based on device identification information.

[0082] In some embodiments, see Figure 3D , Figure 3D This is a flowchart illustrating the recommended object preview method for an application provided in this embodiment of the application. This method can be executed by an electronic device, such as a terminal device. Figure 3D middle, Figure 3A Before step 103 shown, multiple candidate applications corresponding to the binding identification information can also be determined in step 401.

[0083] Here, the multiple candidate applications corresponding to the binding identification information can be multiple candidate applications corresponding to the binding target. These multiple candidate applications can be configured manually or obtained through other filtering methods. For example, when the binding target is a bound account, the candidate applications corresponding to the binding target are applications that can be logged into using the bound account; when the binding target is a bound device, the candidate applications corresponding to the binding target are applications already installed on the bound device.

[0084] In step 402, in response to the selection operation for multiple candidate applications, the selected candidate application is used as the application to trigger the recommendation request.

[0085] For example, a terminal device can present multiple candidate applications. Presenting candidate applications here can refer to presenting the program identification information of the candidate applications, which may include at least one of the name and icon.

[0086] When a selection operation is received for multiple candidate applications, the selected candidate application is used as the target application. This target application is used to trigger a recommendation request at runtime. For example, the target application can trigger a recommendation request through the built-in Software Development Kit (SDK).

[0087] In some embodiments, after step 401, the method further includes: filtering multiple candidate applications based on at least one of historical trigger frequency and media format of the object to be recommended; wherein the historical trigger frequency represents the frequency at which historical recommendation requests are triggered based on the candidate applications; the above-mentioned response to the selection operation for multiple candidate applications, the selected candidate application is used as the application for triggering the recommendation request: in response to the selection operation for the filtered multiple candidate applications, the selected candidate application is used as the application for triggering the recommendation request.

[0088] Here, after identifying multiple candidate applications corresponding to the binding identification information, these candidate applications can be further filtered. For example, multiple candidate applications can be filtered based on at least one of the historical trigger frequency and the media format of the object to be recommended, where the historical trigger frequency represents the frequency at which historical recommendation requests are triggered based on the candidate applications.

[0089] In particular, when filtering multiple candidate applications based on the media format of the object to be recommended, candidate applications that support the media format can be selected. This ensures the effectiveness of the subsequent recommendation operation and avoids the object to be recommended from not being able to be correctly previewed in the target application.

[0090] When filtering multiple candidate applications based on historical trigger frequency, filtering can be implemented using specific trigger conditions. These conditions could be that the historical trigger frequency ranks among the top K of the candidate applications, where K is a positive integer; or that the historical trigger frequency exceeds a frequency threshold. This method, referencing historical experience, aligns with user habits and improves the user experience.

[0091] After filtering multiple candidate applications based on at least one of historical trigger frequency and media format of the application to be recommended, the filtered candidate applications can be presented. When a selection operation is received for the filtered candidate applications, the selected candidate application is used as the application to trigger the recommendation request.

[0092] like Figure 3D As shown, the embodiments of this application can improve the flexibility of object preview from the perspective of the application and meet various user needs. For example, users need to preview objects based on various candidate applications in order to see the preview effect of the object to be recommended in each candidate application.

[0093] In some embodiments, see Figure 4 , Figure 4 This is a flowchart illustrating the recommended object preview method for an application provided in this embodiment of the application. This method can be implemented by a terminal device (such as...). Figure 1 The terminal device 400 or 500 shown) and the server (i.e., the delivery server, such as Figure 1 The server 200 shown will execute, combining Figure 4 The steps shown are explained.

[0094] In step 501, the terminal device sends the obtained query format information to the server.

[0095] In step 502, the server matches the query morphology information with the object morphology information corresponding to multiple candidate objects, and takes the candidate objects corresponding to the successfully matched object morphology information as the objects to be recommended.

[0096] In some embodiments, before step 502, the method further includes: the server responding to a publishing request triggered by the publishing target, querying the publishing database used by the publishing target based on the publishing object identification information corresponding to the publishing request, and obtaining attribute information of multiple dimensions created by the publishing target; wherein, the publishing target includes any one of publishing device and publishing account; constructing object form information corresponding to the candidate objects published by the publishing target based on the attribute information of multiple dimensions created by the publishing target; wherein, the candidate objects published by the publishing target correspond to the publishing object identification information; storing the publishing object identification information and the corresponding object form information in the query database; wherein, the object form information in the query database is used for matching processing with the query form information.

[0097] Here, the publishing target is used to publish to candidate targets, and the publishing target can include either the publishing device or the publishing account. For example, in an advertising scenario, the publishing target can refer to the advertiser.

[0098] When the server receives a publish request triggered by a publishing target, it can query the publishing database used by the publishing target based on the object identification information corresponding to the publish request (named "publishing object identification information" for easy distinction). This query retrieves multi-dimensional attribute information created by the publishing target. The publishing database stores data obtained through operations performed by the publishing target (i.e., multi-dimensional attribute information). During the operations performed by the publishing target, a mapping relationship between this data and the publishing object identification information is also established. It's worth noting that the publishing object identification information can exist directly within the publish request. Alternatively, considering the security and isolation of the publishing process, the publish request can include a publishing identifier that has a mapping relationship with the publishing object identification information. This mapping relationship can exist within the publishing database to facilitate the mapping of the publishing object identification information.

[0099] Then, based on the attribute information of multiple dimensions created by the publishing target, the object form information corresponding to the candidate objects published by the publishing target is constructed. For example, the attribute information of multiple dimensions created by the publishing target is combined to obtain the object form information corresponding to the candidate objects published by the publishing target. Among them, the candidate objects published by the publishing target correspond to the publishing object identification information.

[0100] Then, the published object identification information and the corresponding object form information are stored in the query database. For example, the published object identification information (object identification information) and the object form information corresponding to the candidate object are stored in the query database in key-value format, where the key is the object identification information and the value is the object form information. In this way, the publishing database and the query database provide different functions during the object preview process, which can improve I / O efficiency and thus improve the efficiency of object preview.

[0101] In some embodiments, after storing the published object identification information and the corresponding object form information in the query database, the method further includes: the server responding to a deletion request triggered by the publishing target and deleting the object identification information to be deleted and the corresponding object form information in the query database; wherein the object identification information to be deleted corresponds to the deletion request.

[0102] This application embodiment also supports deletion processing for object identifier information and corresponding object form information already stored in the query database. For example, when the server receives a deletion request triggered by a publishing target, it deletes the object identifier information to be deleted and the corresponding object form information from the query database. The deletion request may include the object identifier information to be deleted, or it may include a publishing identifier that has a mapping relationship with the object identifier information to be deleted. This method avoids invalid data occupying storage space in the query database.

[0103] In step 503, the server sends the object identification information of the object to be recommended to the terminal device, so that the terminal device can generate a binding entry based on the object identification information of the object to be recommended.

[0104] For example, the server sends the object identifier information of the object to be recommended to the terminal device, instructing the terminal device to generate a binding entry based on the received object identifier information and then display it. Alternatively, the server can directly generate a binding entry based on the object identifier information of the object to be recommended and send the relevant display data of the binding entry to the terminal device for display.

[0105] In step 504, the terminal device responds to the binding operation for the binding entry by collecting the object identification information of the object to be recommended in the binding entry.

[0106] When a terminal device receives a binding operation for a binding entry, it reads (collects) the object identifier information of the object to be recommended in the binding entry.

[0107] In step 505, the terminal device sends the binding identification information and the object identification information of the object to be recommended to the server, so that the server establishes a binding relationship between the binding identification information and the object identification information of the object to be recommended.

[0108] For example, the terminal device sends the binding identification information collected through the binding entry and the object identification information of the object to be recommended read from the binding entry to the server, so as to notify the server to establish a binding relationship between the binding identification information and the object identification information of the object to be recommended.

[0109] In some embodiments, the above-mentioned binding relationship between the binding identification information and the object identification information of the object to be recommended can be achieved in the following way: the server performs risk detection processing on the risk items of the object to be recommended and obtains the risk detection result; wherein, the risk item includes at least one of the publishing target and object form information, and the publishing target includes any one of the publishing device and the publishing account; when the risk detection result is no risk, the binding relationship between the binding identification information and the object identification information of the object to be recommended is established.

[0110] Here, the server can perform risk detection processing on the risk items of the objects to be recommended. This application embodiment does not limit the method of risk detection processing. Risk detection processing can be carried out by manual review or by combining artificial intelligence technology.

[0111] For example, if the risk item only includes the publishing target, the object form information of the historical objects published by the publishing target can be input into the machine learning model, and the output of the machine learning model can be used to determine whether the historical objects contain elements such as infringement, pornography, and violence. If they contain these elements, the output risk detection result is "risk exists"; if they do not contain these elements, the output risk detection result is "no risk".

[0112] Similarly, when the risk item only includes the object form information of the object to be recommended, the object form information of the object to be recommended can be input into the machine learning model, and the output of the machine learning model can be used to determine whether the object to be recommended contains elements such as infringement, pornography, and violence. If it contains these elements, the risk detection result is output as "risk exists"; if it does not contain these elements, the risk detection result is output as "no risk".

[0113] When the risk item includes both the target publication and the object to be recommended, a risk detection result of "no risk" is only output if neither the historical objects published by the target publication nor the objects to be recommended contain elements such as infringement, pornography, or violence. This method reduces the risk during object previewing and improves the security of object previewing.

[0114] In step 506, the terminal device sends a recommendation request to the server in response to the application's triggering operation.

[0115] For example, if a terminal device is running an application, when it receives a trigger action on the application, the terminal device will send a recommendation request generated by the application to the server.

[0116] In step 507, the server queries the binding relationship based on the binding identifier information in the recommendation request to obtain the object to be recommended, and sends the object form information of the object to be recommended to the terminal device.

[0117] Here, the server can send the object form information of the recommended object corresponding to the retrieved object identifier information to the terminal device, so that the terminal device can display it. Of course, the recommendation method for the recommended object corresponding to the retrieved object identifier information is not limited to display; it depends on its media format.

[0118] In some embodiments, after step 502, the method further includes: the server stores the object identification information and object form information of the object to be recommended in the recommendation database; the above-mentioned sending of the queried object form information of the object to be recommended to the terminal device can be achieved in the following way: the server performs query processing on the recommendation database according to the queried object identification information, and sends the queried object form information to the terminal device.

[0119] After identifying the objects to be recommended, the server can store the object identifier information and object form information of the objects from the query database into the recommendation database. For example, the object identifier information can be stored as the key, and the object form information as the value. The recommendation database is specifically responsible for responding to recommendation requests.

[0120] When the server receives a recommendation request triggered by an application, it identifies the object identifier that is bound to the binding identifier information in the recommendation request; that is, the object identifier of the target object. Then, based on the object identifier, the server queries the recommendation database to retrieve the object's physical characteristics and sends this information to the terminal device. Thus, by utilizing the collaborative functions of the publishing, query, and recommendation databases, the efficiency of object previewing can be improved, achieving low-latency object previewing.

[0121] In some embodiments, after step 505, the method further includes: when the synchronization conditions are met, synchronizing the binding relationship to the binding service; wherein the synchronization conditions include at least one of the following: the synchronization period has arrived; the number of unsynchronized binding relationships is greater than a number threshold; the pressure parameter of the binding service is less than a pressure parameter threshold; the above-mentioned query processing of the binding relationship based on the binding identifier information in the recommendation request to obtain the object to be recommended can be achieved in the following way: the binding service is called based on the binding identifier information in the recommendation request, so that the binding service queries the binding relationship based on the binding identifier information to obtain the object to be recommended.

[0122] Here, the server can support queries on binding relationships through a specific binding service. For unsynchronized binding relationships, they can be synchronized to the binding service when synchronization conditions are met, thus reducing the processing pressure on the binding service. The synchronization conditions include at least one of the following: the synchronization cycle has been reached (e.g., synchronizing once every 10 minutes); the number of unsynchronized binding relationships is greater than a quantity threshold; and the pressure parameter of the binding service (used to reflect the processing pressure of the binding service) is less than a pressure parameter threshold.

[0123] When the server receives a recommendation request, it can invoke the binding service based on the binding identifier information in the request. This allows the binding service to query and process the binding relationships based on the binding identifier information, obtaining the object to be recommended (here, the object identifier information of the object to be recommended). This method ensures the real-time nature of object preview while reducing the processing load during the object preview process.

[0124] In step 508, the terminal device presents the object to be recommended in the application based on the object form information of the object to be recommended.

[0125] like Figure 4 As shown, this application embodiment improves the applicability of object preview by coordinating the terminal device and the server.

[0126] In some embodiments, see Figure 5 , Figure 5 This is a flowchart illustrating the recommended object preview method for an application provided in this embodiment of the application. This method can be implemented by a first terminal device (such as...). Figure 1 The terminal device 400 shown), the second terminal device (such as...) Figure 1 The terminal device 500 shown) and the server (i.e., the delivery server, such as Figure 1 The server 200 shown will execute, and will combine Figure 5 The steps shown are explained.

[0127] In step 601, the first terminal device sends the obtained query pattern information to the server.

[0128] In step 602, the server matches the query morphology information with the object morphology information corresponding to multiple candidate objects, and takes the candidate objects corresponding to the successfully matched object morphology information as the objects to be recommended.

[0129] In step 603, the server sends the object identification information of the object to be recommended to the first terminal device, so that the first terminal device generates and presents a binding entry based on the object identification information of the object to be recommended.

[0130] Here, the binding entry can be generated by the first terminal device, or the server can directly generate the binding entry based on the object identifier information of the object to be recommended, and send the relevant display data of the binding entry to the first terminal device so that the first terminal device can display it.

[0131] In step 604, in response to the binding operation of the second terminal device to the binding entry presented by the first terminal device, the object identification information of the object to be recommended in the binding entry and the binding identification information corresponding to the binding operation are collected.

[0132] Here, the second terminal device can perform a binding operation on the binding entry presented by the first terminal device to collect binding identification information. The binding target can be the second terminal device itself or an account in a logged-in state within the binding application on the second terminal device. Simultaneously, the second terminal device also collects the object identification information of the object to be recommended in the binding entry.

[0133] In step 605, the second terminal device sends the binding identification information and the object identification information of the object to be recommended to the server, so that the server establishes a binding relationship between the binding identification information and the object identification information of the object to be recommended.

[0134] In step 606, the second terminal device sends a recommendation request to the server in response to the application's triggering operation.

[0135] In step 607, the server queries the binding relationship based on the binding identifier information in the recommendation request to obtain the object to be recommended, and sends the object form information of the object to be recommended to the second terminal device.

[0136] In step 608, the second terminal device presents the object to be recommended in the application based on the object form information of the object to be recommended.

[0137] like Figure 5 As shown, this application embodiment provides another architecture for object preview, which realizes object preview through three-terminal interaction, thereby improving the applicability of object preview.

[0138] See Figure 6 , Figure 6 This is a flowchart illustrating the recommended object preview method for an application provided in this embodiment. This method can be executed by an electronic device, such as a terminal device, and will combine... Figure 6 The steps shown are explained.

[0139] In step 701, the binding entry corresponding to the object to be recommended is presented. The object to be recommended is multimedia information that is used to be displayed in the application.

[0140] Here, the binding entry corresponding to the object to be recommended can be displayed. This binding entry is generated based on the object identifier information of the object to be recommended.

[0141] In some embodiments, prior to step 701, the method further includes: presenting attribute input entries for multiple dimensions; and, in response to an attribute input operation for at least one dimension of the attribute input entry, determining, from among multiple candidate objects, a candidate object that matches the attribute information of the input at least one dimension.

[0142] Here, multiple attribute input fields can be presented, each corresponding to a dimension. The type of attribute input field is not limited; for example, it could be an input box. Upon receiving an attribute input operation for at least one dimension, query form information is constructed based on the input attribute information of that dimension. For example, the input attribute information of that dimension can be combined to obtain query form information. The constructed query form information is used to match the object form information corresponding to multiple candidate objects to obtain the objects to be recommended. The object form information includes attribute information from multiple dimensions. This method improves the flexibility of object previewing and enhances the user experience, allowing users to filter recommended objects based on specific dimension requirements.

[0143] In step 702, in response to the binding operation for the binding entry, a binding relationship is established between the object to be recommended and the binding identification information.

[0144] Here, when a binding operation is received for the binding entry, a binding relationship is established between the object to be recommended and the binding identification information. The binding relationship can refer to the binding relationship between the object identification information of the object to be recommended and the binding identification information.

[0145] In step 703, multiple candidate applications corresponding to the binding identification information are presented, and the candidate applications are used to present the objects to be recommended.

[0146] Here, multiple candidate applications corresponding to the binding identification information can be presented. Presenting candidate applications can refer to presenting the program identification information of the candidate applications, which may include at least one of the name and icon.

[0147] In step 704, in response to a selection operation for multiple candidate applications, the recommended objects queried based on the binding relationship are presented in the selected candidate applications.

[0148] Here, when a selection operation is received for multiple candidate applications, the selected candidate application is taken as the target application, and the recommended object queried based on the binding relationship is displayed in the target application's interface. A recommendation request can be triggered based on the target application, and this recommendation request carries binding identification information. Thus, the binding relationship can be queried based on the binding identification information in the recommendation request.

[0149] In some embodiments, after step 702, the method further includes: presenting attribute input entries for multiple dimensions; in response to an attribute input operation for at least one dimension of the attribute input entry, determining a candidate object that matches the attribute information of at least one dimension of the input among multiple candidate objects; the above-mentioned presentation of candidate objects queried based on binding relationships in the selected candidate application can be achieved in such a way that the matching candidate objects are presented in the selected candidate application.

[0150] Here, when there are multiple objects to be recommended, the terminal device can receive attribute input operations for at least one dimension of the attribute input field, and determine the objects to be recommended that match the input attribute information of at least one dimension from among the multiple objects to be recommended. For example, query form information is constructed based on the input attribute information of at least one dimension, and the query form information is matched with the object form information corresponding to each of the multiple objects to be recommended to obtain the matched objects to be recommended (i.e., the objects to be recommended corresponding to the successfully matched object form information). Finally, the matched objects to be recommended are presented in the selected candidate applications. In this way, the targeting of object preview can be improved when there are multiple objects to be recommended, thus meeting the user's preview needs.

[0151] like Figure 6 As shown, this application embodiment establishes a binding relationship, thereby enabling accurate and effective object preview for the application, which can meet the user's preview needs for specified objects to be recommended; at the same time, it can also improve the actual utilization rate of computing resources consumed by electronic devices during object preview.

[0152] The following will illustrate exemplary applications of the embodiments of this application in real-world scenarios. For ease of understanding, examples will be provided using advertisements as the object. For advertisements, advertisers need to experience specific ads in real media scenarios and review whether the creative design meets expectations. This is a crucial part of ad placement and an important means of ad demonstration. Furthermore, product personnel or developers on advertising platforms also have a need to develop, debug, and test specific ads. Therefore, the embodiments of this application provide an ad preview solution (i.e., an object preview solution in an advertising scenario). This allows users to review whether the creative design of the ad meets expectations in a real media environment, avoiding losses caused by discrepancies between the officially launched ad and expectations. Simultaneously, for internal users of the advertising platform (such as product personnel or developers), it helps improve development iteration efficiency.

[0153] Next, the explanation will focus on product performance. The advertising preview solution provided in this application can be implemented through a first terminal device, a second terminal device, and a server. The first terminal device can be a desktop computer, and the second terminal device can be a smartphone, but it is not limited to these.

[0154] During the ad preview process, the first terminal device can receive the query format information input by the user and send the query format information to the server (delivery server). As an example, it provides... Figure 7 The diagram shown is a schematic of the query interface provided by the first terminal device. Figure 7 The query interface shown includes multiple input items (i.e., attribute input entries), each corresponding to different dimensions, such as advertising material specifications, advertising product type, and advertising product ID. When a trigger operation is received for query option 71, the first terminal device sends the input query format information to the server, so that the server matches the query format information with multiple advertising format information respectively, and selects the candidate advertisements corresponding to the successfully matched advertising format information as advertisements to be recommended. Each advertising format information corresponds to one candidate advertisement. Figure 7 This shows a portion of the attribute information from the ad format information of the ad to be recommended, such as the ad index being 430644779 and the ad aid being 3046483926.

[0155] When received targeting Figure 7 When the preview option 72 shown is triggered, the process of scanning a QR code for previewing can be initiated. As an example, it provides... Figure 8 The diagram shows a QR code scanning interface provided by the first terminal device. Figure 8 The shown QR code interface includes a QR code, which is generated based on the ad ID of the ad to be recommended (corresponding to the object identification information above).

[0156] For the user of the second terminal device, they can scan the QR code displayed on the scanning interface of the first terminal device using an application that supports QR code scanning on the second terminal device (hereinafter referred to as the "binding application" for easy distinction). The second terminal device responds to this scanning operation by displaying multiple candidate applications. As an example, the following is provided: Figure 9 The diagram shown illustrates the selection interface. Figure 9 The candidate applications shown include browser applications, news applications, video applications, and content social applications. Among them, candidate applications can share accounts with the linked applications, meaning that the same account can be logged in in the linked applications as well as in the candidate applications.

[0157] In response to a selection operation among multiple candidate applications, the second terminal device selects the chosen candidate application as the target application and runs it; that is, it navigates from the selection interface to the target application's running interface. As an example, a similar approach is provided. Figure 10 The target application's runtime interface is shown. In addition to the content provided by the target application itself, the runtime interface also includes... Figure 10 In addition to weather-related content, the presentation format of the target advertisement 101 (corresponding to the target object mentioned above) obtained by requesting the server is also shown.

[0158] Next, the explanation will focus on the underlying implementation. The ad preview solution provided in this application embodiment can include an ad information acquisition module, a device information acquisition module, a data publishing stream module, and a playback retrieval module at its underlying implementation level. Specifically, the ad information acquisition module solves the problem of users being unable to find target ads independently by establishing an inverted index of ad formats in the ad library; the device information acquisition module solves the problem of difficulty in obtaining device identification information through one-click scanning; the data publishing stream module solves the latency problem of previewing ads, enabling real-time ad preview; and the playback retrieval module is used to achieve non-intrusive ad preview. This will be combined with... Figure 11 The illustrated preview of the advertisement explains each module.

[0159] 1) Advertising information acquisition module.

[0160] In the solutions provided by related technologies, users in the advertising and marketing business line will encounter the following two problems when trying to find a suitable target advertisement: the advertisement library is built according to the advertiser as the primary key, while the user's need is to find the target advertisement according to its format, such as wanting to find a mini-program advertisement that leads directly to the application in three images. Existing components and services cannot meet this need; if the user applies to be an advertiser and creates an advertisement, they need to go through a cumbersome approval process to apply for virtual funds (creating an advertisement requires virtual funds), and the created advertisement is difficult to share. Every user who needs to view the advertisement has to go through this process, which is time-consuming and laborious.

[0161] To address this issue, this application embodiment utilizes an advertising information acquisition module. This module includes an advertising database (corresponding to the query database mentioned above), which supports querying for specific advertising formats using an inverted index based on advertising format. Within the advertising database, the attributes of each advertisement can be set according to the needs of the actual application scenario; for example, the designed attribute fields are shown in Table 1.

[0162] Table 1

[0163] It's worth noting that the direct access types in Table 1 refer to how the ad is presented after being triggered. Non-direct access means that after triggering the ad, a redirect is made based on a specific Uniform Resource Locator (URL), i.e., redirecting to the browser instead of the application. Application direct access means that after triggering the ad, the ad redirects to the application. Dual-link direct access means that the external link ad supports redirecting to a specific product page within the application. UL direct access is a unique redirection method in iOS, which is a redirection via the Hypertext Transfer Protocol (HTTP). Dual-link direct access and UL direct access mean that both dual-link direct access and UL direct access are supported simultaneously, and the rest are similar.

[0164] After designing the attribute fields in the ad library, the next step is to design how the data in the ad library is generated. In this embodiment, the data in the ad library can be constructed based on the data in the publishing database. For example, the publishing database can include relational databases and non-relational databases. Relational databases include MySQL databases, and non-relational databases include key-value (KV) databases, cloud key-value (CKV) databases, etc. The non-relational database stores ad-related attribute information. The primary key is the ad ID, and the values ​​include ad creative specifications, ad product type, landing page type, direct access type, contract ad tag, mini-program type, native ad tag, promotion application package name, ad type, UL direct access address, video duration, and other attribute information. It is worth noting that the ad ID used as the primary key here is specifically used for ad queries during the ad preview process and is different from the aforementioned ad short ID, advertiser ID, and ad long ID. Relational databases store mappings between media sites, ad placements, and ad IDs. The ad ID mapping is specifically the mapping between ad IDs and publishing IDs (corresponding to the publishing identifier mentioned above). The publishing ID is used by the advertiser (corresponding to the publishing account mentioned above). For example... Figure 12 As shown, when an advertiser creates or changes an ad, they notify the publishing service based on the publishing ID. The publishing service updates the ad status based on the publishing ID, for example, by determining the ad ID that has a mapping relationship with the publishing ID. Then, based on the ad ID, it retrieves attribute information of different dimensions from non-relational databases and relational databases, constructs ad format information based on these attribute information, and stores the ad ID and the constructed ad format information in the ad library in the form of key-value pairs.

[0165] exist Figure 12In this system, the advertising information acquisition module can be divided into two parts: reading and writing. The reading part provides user-facing query services, allowing users to search for advertisements of a specific format by querying format information. The writing part is responsible for building the advertising database by monitoring changes to advertisements, such as views for adding / changing advertisements and deleting advertisements. When a view for adding / changing an advertisement is detected, the system retrieves the corresponding data from both non-relational and relational databases through a publishing service, constructs the advertisement format information, and stores it in the advertising database. When a view for deleting an advertisement is detected, the system directly deletes the corresponding advertisement format information from the advertising database, thereby saving storage resources.

[0166] 2) Equipment information acquisition module.

[0167] In the solutions provided by related technologies, non-technical personnel cannot obtain the device ID (i.e., device identification information) on their own. The process for professionals to obtain the device ID is also very complicated and requires the following steps: ① Configure a proxy in the browser to intercept requests; ② Obtain the advertising request through the proxy; ③ Parse the device ID carried in the advertising request; ④ Manually bind the device ID and the advertising ID.

[0168] To address this, this application provides a device information acquisition module, which enables users to obtain device IDs with a single click by scanning a code. Users can scan the code with a single click by binding an application and jump to the selected target application to preview the advertisement, greatly improving the efficiency of the advertisement preview.

[0169] The device information acquisition module may include a web module, a terminal H5 module, and a backend module. H5 is short for HyperText Markup Language (HTML) 5, which will combine... Figure 13The following describes each module. The Web module, located on the first terminal device, generates a QR code for users on the second terminal device to scan. This QR code contains a redirect to an H5 page and the ad ID of the advertisement to be recommended. The terminal H5 module, located on the second terminal device, scans the QR code presented on the first terminal device via a bound application. During scanning, it opens the corresponding H5 interface (corresponding to the selection interface mentioned above) based on the redirect to the H5 page in the QR code. It collects the device ID of the second terminal device using the JSBridge interface (corresponding to the bridging interface mentioned above) in the H5 interface and sends the device ID and the ad ID of the advertisement to be recommended in the QR code to the server for binding. Finally, it presents the candidate applications returned by the server in the H5 interface (which can display at least one of the candidate application's name and icon). The backend module, located on the server, performs risk detection on the risk items of the advertisement to be recommended upon receiving the device ID and the ad ID of the advertisement to be recommended. If no risk is detected, it saves the corresponding binding relationship to the database, determines the candidate applications that can present the advertisement, and returns the schema information (i.e., application identification information) of the determined candidate applications to the terminal H5 module. Thus, for users of the second terminal device, only two operations are required: scanning the code and selecting a candidate application, which is very convenient. It's worth noting that the background module is independent of... Figure 11 The data publishing stream module and playback retrieval module shown are, for example, located between the device information acquisition module and the data publishing stream module.

[0170] 3) Data publishing flow module.

[0171] The data publishing module resides on the server. When it receives a device ID and an ad ID (e.g., a device ID and ad ID detected as risk-free by the backend module), it establishes a binding relationship between the device ID and the ad ID and stores the binding relationship in the binding relationship database (i.e., the database used to store binding relationships). Simultaneously, a transaction is generated to trigger the subscription module within the data publishing module. The subscription module performs the following operations: ① It stores the ad ID and its corresponding ad format information in a key-value format in the recommendation database, where the recommendation database can be a non-relational database; ② It stores the basic targeting conditions corresponding to the ad ID (corresponding to the recommendation conditions mentioned above) in the preview service of the playback retrieval module. The basic targeting conditions can be configured according to the actual application scenario, such as specifying which operating systems the ad can be displayed on; ③ It synchronizes the binding relationships in the binding relationship database to the binding service in batches, for example, through periodic synchronization, thus reducing the processing pressure on the binding service.

[0172] 4) Playback search module.

[0173] When the second terminal device runs the target application, it initiates an advertising request (corresponding to the recommendation request mentioned above) based on the target application. This advertising request carries the device ID of the second terminal device. The playback retrieval module includes a playback service (Display service), a retrieval service, and a preview service. When the playback service receives an advertising request, it forwards the advertising request to the retrieval service. The retrieval service accesses the binding service based on the device ID in the advertising request to determine the advertising ID of the target advertisement that is bound to that device ID. Then, it sends the advertising ID to the preview service. The preview service checks whether the advertising request meets the recommendation conditions corresponding to the advertising ID and sends the check result to the retrieval service. When the check result is passed (i.e., the recommendation conditions are met), the retrieval service queries the recommendation database based on the advertising ID to obtain the advertising format information corresponding to the advertising ID. It then fills in the presentation format based on the advertising format information and sends the presentation format to the playback service, which plays the advertisement in the target application on the second terminal device, for example, by presenting it in the target application's running interface according to the presentation format. The target application can access the playback service through a Software Development Kit (SDK). The SDK access method is a black box access on the application side, which can greatly improve access efficiency and accurately and effectively retrieve target advertisements.

[0174] The advertising preview solution provided by this application can improve the convenience of querying, binding and previewing each step, enabling users to examine whether the creative design of the advertisement meets expectations in a real media environment, avoiding losses caused by the discrepancy between the real scenario and expectations. At the same time, internal users of the advertising platform (such as product personnel / developers) can use this solution to improve the efficiency of development iteration.

[0175] The following continues to describe an exemplary structure of the application recommendation preview device 4551 provided in the embodiments of this application, implemented as a software module. In some embodiments, such as Figure 2AAs shown, the software modules in the application's recommended object preview device 4551 stored in the memory 450 may include: a collection module 45511, used to collect object identification information of the object to be recommended in the binding entry in response to a binding operation for the binding entry; wherein the binding entry is generated based on the object identification information of the object to be recommended, and the object to be recommended is multimedia information to be presented in the application; a binding module 45512, used to collect the object to be recommended, which is multimedia information to be presented in the application; a recommendation module 45513, used to send a recommendation request to the delivery server in response to a trigger operation for the application, wherein the recommendation request includes binding identification information; the recommendation module 45513 is also used to receive object form information of the object to be recommended from the delivery server, and present the object to be recommended in the application based on the object form information of the object to be recommended, wherein the object to be recommended is obtained by the delivery server querying the binding relationship based on the binding identification information in the recommendation request; the object form information includes attribute information of multiple dimensions.

[0176] In some embodiments, the application's recommended object preview device 4551 further includes a matching module, configured to: obtain query form information; wherein the query form information includes attribute information of at least one dimension among multiple dimensions; send the query form information to a delivery server, so that the delivery server can perform matching processing between the query form information and the object form information corresponding to multiple candidate objects respectively, and take the candidate objects corresponding to the successfully matched object form information as the objects to be recommended; receive the object identifier information of the objects to be recommended from the delivery server to generate the binding entry.

[0177] In some embodiments, the acquisition module 45511 is further configured to perform any of the following processes: acquire account identifier information of the account corresponding to the binding operation as binding identifier information; acquire device identifier information of the device corresponding to the binding operation through a bridging interface as binding identifier information; wherein the bridging interface is obtained by encapsulating the native device interface used for acquiring device identifier information.

[0178] In some embodiments, the application recommendation object preview device 4551 further includes a selection module, configured to: determine multiple candidate applications corresponding to the binding identification information; and, in response to a selection operation for the multiple candidate applications, use the selected candidate application as the application for triggering the recommendation request.

[0179] In some embodiments, the selection module is further configured to: filter a plurality of candidate applications based on at least one of historical trigger frequency and media format of the object to be recommended; wherein the historical trigger frequency represents the frequency at which historical recommendation requests are triggered based on the candidate applications; and in response to the selection operation for the filtered plurality of candidate applications, the selected candidate application is used as the application for triggering the recommendation request.

[0180] In some embodiments, the recommendation module 45513 is further configured to present the object to be recommended in the application based on the object form information of the object to be recommended when the recommendation conditions are met; wherein the recommendation conditions include at least one of the following: the collected real-time device parameters match the recommended device parameters; the risk detection result of the object to be recommended is no risk; the application supports the media format of the object to be recommended.

[0181] The following continues to describe an exemplary structure of the application recommendation preview device 4552 provided in the embodiments of this application, implemented as a software module. In some embodiments, such as Figure 2B As shown, the software modules in the application recommendation preview device 4552 stored in the memory 450 may include: an entry presentation module 45521, used to present the binding entry corresponding to the object to be recommended, wherein the object to be recommended is multimedia information to be displayed in the application; a binding module 45522, used to establish a binding relationship between the object to be recommended and the binding identification information in response to a binding operation for the binding entry; an application presentation module 45523, used to present multiple candidate applications corresponding to the binding identification information, wherein the candidate applications are used to present the object to be recommended; and an object presentation module 45524, used to present the object to be recommended queried according to the binding relationship in the selected candidate application in response to a selection operation for multiple candidate applications.

[0182] In some embodiments, the recommended object preview device 4552 further includes a matching module for: presenting attribute input entries for multiple dimensions; and, in response to an attribute input operation for at least one dimension of the attribute input entry, determining, from multiple candidate objects, an object to be recommended that matches the attribute information of the input at least one dimension.

[0183] In some embodiments, the recommended object preview device 4552 further includes a matching module, configured to: present attribute input entries for multiple dimensions; in response to an attribute input operation for at least one dimension of the attribute input entry, determine among multiple objects to be recommended that match the attribute information of at least one dimension of the input; the object presentation module 45524 is further configured to: present the matching objects to be recommended in the selected candidate application.

[0184] The following continues to describe the exemplary structure of the application recommendation preview device 243 provided in the embodiments of this application as a software module. In some embodiments, such as Figure 2C As shown, the software modules in the application's recommended object preview device 243 stored in the memory 240 may include: a binding module 2431, used to receive binding identification information and object identification information of the object to be recommended from the terminal device, and establish a binding relationship between the binding identification information and the object identification information of the object to be recommended; wherein, the object to be recommended is multimedia information to be displayed in the application; and a recommendation module 2432, used to: receive a recommendation request from the terminal device; wherein, the recommendation request is sent by the terminal device in response to a trigger operation on the application, and the recommendation request includes binding identification information; query the binding relationship according to the binding identification information in the recommendation request to obtain the object to be recommended; and send the object form information of the object to be recommended to the terminal device so that the terminal device can display the object to be recommended in the application according to the object form information of the object to be recommended; wherein, the object form information includes attribute information of multiple dimensions.

[0185] In some embodiments, the recommended object preview device 243 further includes a matching module, configured to: receive query form information from a terminal device; wherein the query form information includes attribute information of at least one dimension among multiple dimensions; perform matching processing on the query form information and the object form information corresponding to multiple candidate objects respectively, and take the candidate object corresponding to the successfully matched object form information as the object to be recommended; and send the object identification information of the object to be recommended to the terminal device.

[0186] In some embodiments, the recommended object preview device 243 further includes a publishing module, configured to: respond to a publishing request triggered by a publishing target, query the publishing database used by the publishing target based on the publishing object identification information corresponding to the publishing request, and obtain attribute information of multiple dimensions created by the publishing target; wherein the publishing target includes any one of a publishing device and a publishing account; construct object form information corresponding to the candidate objects published by the publishing target based on the attribute information of multiple dimensions created by the publishing target; wherein the candidate objects published by the publishing target correspond to the publishing object identification information; and store the publishing object identification information and the corresponding object form information in a query database; wherein the object form information in the query database is used for matching processing with the query form information.

[0187] In some embodiments, the recommended object preview device 243 further includes a deletion module, configured to: in response to a deletion request triggered by the publishing target, perform deletion processing on the object identification information to be deleted and the corresponding object form information in the query database; wherein the object identification information to be deleted corresponds to the deletion request.

[0188] In some embodiments, the recommended object preview device 243 further includes a storage module for storing the object identification information and object form information of the object to be recommended into a recommendation database; the recommendation module 2432 is further configured to: query the recommendation database according to the object identification information of the object to be recommended to obtain the object form information of the object to be recommended.

[0189] In some embodiments, the recommended object preview device 243 further includes a synchronization module, used to synchronize the binding relationship to the binding service when the synchronization conditions are met; wherein, the synchronization conditions include at least one of the following: the synchronization period has arrived; the number of unsynchronized binding relationships is greater than a number threshold; the pressure parameter of the binding service is less than a pressure parameter threshold; the recommendation module 2432 is further used to: call the binding service according to the binding identification information in the recommendation request, so that the binding service performs query processing on the binding relationship according to the binding identification information to obtain the object to be recommended.

[0190] In some embodiments, the recommended object preview device 243 further includes a risk detection module, configured to: perform risk detection processing on the risk items of the object to be recommended, and obtain a risk detection result; wherein, the risk item includes at least one of the publishing target and object form information, and the publishing target includes any one of the publishing device and the publishing account; when the risk detection result is no risk, establish a binding relationship between the binding identification information and the object identification information of the object to be recommended.

[0191] This application provides a computer program product or computer program that includes computer instructions (i.e., executable instructions) stored in a computer-readable storage medium. An electronic device's processor reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform the application preview method described in this application embodiment.

[0192] This application provides a computer-readable storage medium storing executable instructions that, when executed by a processor, cause the processor to execute the recommended object preview method of the application provided in this application.

[0193] In some embodiments, the computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or it may be a variety of devices including one or any combination of the above-mentioned memories.

[0194] In some embodiments, executable instructions may take the form of a program, software, software module, script, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

[0195] As an example, executable instructions may, but do not necessarily, correspond to files in a file system. They may be stored as part of a file that holds other programs or data, for example, in one or more scripts in a Hyper Text Markup Language (HTML) document, in a single file dedicated to the program in question, or in multiple collaborating files (e.g., a file that stores one or more modules, subroutines, or code sections).

[0196] As an example, executable instructions can be deployed to execute on a single electronic device, or on multiple electronic devices located in one location, or on multiple electronic devices distributed across multiple locations and interconnected via a communication network.

[0197] The above are merely embodiments of this application and are not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, and improvements made within the spirit and scope of this application are included within the scope of protection of this application.

Claims

1. A method for previewing recommended objects in an application, characterized in that, Applied to a first terminal device and a second terminal device, the method includes: The first terminal device sends the query form information to the delivery server, so that the delivery server uses a pre-established object form inverted index to query the query form information in the query database, selects the candidate objects whose object form information matches the query form information as the objects to be recommended, and stores the object identification information and object form information of the objects to be recommended in the recommendation database. The objects to be recommended are multimedia information that is to be delivered to the application for presentation. The first terminal device receives the object identification information of the object to be recommended from the delivery server, and presents a QR code generated based on the object identification information of the object to be recommended and the jump interface address; In response to the scanning operation of the QR code, the second terminal device reads the object identification information of the recommended object and the jump interface address in the QR code, and accesses the interface corresponding to the jump interface address through the jump interface address; by triggering the bridging interface in the interface, it collects the device identification information of the bound device corresponding to the scanning operation as the binding identification information; wherein, the bridging interface is the JSBridge interface, which is obtained by encapsulating the native device interface used to collect the device identification information; The second terminal device sends the binding identification information and the object identification information of the object to be recommended to the delivery server, so that the delivery server can perform risk detection processing on the risk items of the object to be recommended, and establish a binding relationship between the binding identification information and the object identification information of the object to be recommended when the result of the risk detection processing is no risk. The risk items include at least one of the publishing target and object form information, and the publishing target includes any one of the publishing device and the publishing account. The second terminal device determines multiple candidate applications corresponding to the binding identification information, and the candidate applications are used to present the object to be recommended; In response to the selection operation for the plurality of candidate applications, the second terminal device selects the candidate application as the application used to trigger the recommendation request; In response to a triggering operation on the application, the second terminal device sends the recommendation request to the delivery server, wherein the recommendation request includes the binding identification information; The second terminal device receives the object form information of the object to be recommended from the delivery server, and presents the object to be recommended in the application according to the object form information. The object form information is obtained by the delivery server calling the binding service according to the binding identifier information in the recommendation request, the binding service querying the binding relationship to obtain the object identifier information of the object to be recommended, and then querying the recommendation database according to the object identifier information. The object form information includes attribute information of multiple dimensions.

2. The method according to claim 1, characterized in that, Before the first terminal device sends the queried morphological information to the delivery server, the method further includes: The first terminal device acquires query pattern information; wherein, the query pattern information includes attribute information of at least one of the multiple dimensions.

3. The method according to claim 1, characterized in that, The method further includes: The second terminal device collects the account identifier information of the bound account corresponding to the scanning operation as the binding identifier information.

4. The method according to claim 1, characterized in that, After determining the multiple candidate applications corresponding to the binding identifier information, the method further includes: The second terminal device filters the plurality of candidate applications based on at least one of the historical trigger frequency and the media format of the objects to be recommended; wherein, the historical trigger frequency represents the frequency at which historical recommendation requests are triggered based on the candidate applications; In response to a selection operation for the plurality of candidate applications, the second terminal device selects the candidate application as the application used to trigger the recommendation request, including: In response to a selection operation among a plurality of candidate applications, the second terminal device selects the candidate application as the application used to trigger the recommendation request.

5. The method according to any one of claims 1 to 4, characterized in that, The step of presenting the object to be recommended in the application based on the object form information of the object to be recommended includes: When the recommendation criteria are met, the second terminal device presents the object to be recommended in the application based on the object form information of the object to be recommended. The recommended conditions include at least one of the following: The collected real-time device parameters match the recommended device parameters; The risk detection result of the object to be recommended is no risk; The application supports the media formats of the objects to be recommended.

6. A method for previewing recommended objects in an application, characterized in that, Applied to a delivery server, the method includes: The system receives query format information from a first terminal device and queries the query format information in a query database using a pre-established object format inverted index. Candidate objects whose object format information matches the query format information are selected as recommended objects. The object identifier information and object format information of the recommended objects are stored in a recommendation database, and the object identifier information of the recommended objects is sent to the first terminal device. The recommended objects are multimedia information intended for presentation in the application. The first terminal device presents a QR code generated based on the object identifier information of the object to be recommended and the redirection interface address, so that the second terminal device responds to the scanning operation of the QR code, reads the object identifier information of the object to be recommended and the redirection interface address in the QR code, and accesses the interface corresponding to the redirection interface address through the redirection interface address; by triggering the bridging interface in the interface, the device identifier information of the bound device corresponding to the scanning operation is collected as the binding identifier information; wherein, the bridging interface is the JSBridge interface, which is obtained by encapsulating the native device interface used to collect the device identifier information; The device receives binding identification information and object identification information of the object to be recommended from the second terminal device, performs risk detection processing on the risk items of the object to be recommended, and establishes a binding relationship between the binding identification information and the object identification information of the object to be recommended when the result of the risk detection processing is no risk. The risk items include at least one of the publishing target and object form information, and the publishing target includes any one of the publishing device and the publishing account. The second terminal device is invoked to determine multiple candidate applications corresponding to the binding identification information. The candidate applications are used to present the object to be recommended, and in response to the selection operation for the multiple candidate applications, the selected candidate application is used as the application to trigger the recommendation request. A recommendation request is received from the second terminal device; wherein the recommendation request is sent by the second terminal device in response to a triggering operation on the application, and the recommendation request includes the binding identification information; The binding service is invoked based on the binding identifier information in the recommendation request. The binding service queries the binding relationship to obtain the object identifier information of the object to be recommended. Then, the object identifier information is used to query the recommendation database to obtain the object form information of the object to be recommended. The object form information of the object to be recommended is sent to the second terminal device, so that the second terminal device can present the object to be recommended in the application according to the object form information of the object to be recommended; wherein, the object form information includes attribute information of multiple dimensions.

7. The method according to claim 6, characterized in that, The query format information includes attribute information of at least one of the multiple dimensions.

8. The method according to claim 7, characterized in that, Before selecting candidate objects whose object morphology information matches the query morphology information as recommended objects, the method further includes: In response to a publishing request triggered by a publishing target, the publishing database used by the publishing target is queried based on the publishing object identification information corresponding to the publishing request to obtain attribute information of multiple dimensions created by the publishing target; wherein, the publishing target includes either a publishing device or a publishing account; Based on the attribute information of multiple dimensions created by the publishing target, construct the object form information corresponding to the candidate objects published by the publishing target; wherein, the candidate objects published by the publishing target correspond to the publishing object identification information; The object identification information and the corresponding object form information are stored in the query database; wherein, the object form information in the query database is used for matching with the query form information.

9. The method according to any one of claims 6 to 8, characterized in that, After establishing the binding relationship between the binding identifier information and the object identifier information of the object to be recommended, the method further includes: When the synchronization conditions are met, the binding relationship is synchronized to the binding service; The synchronization conditions include at least one of the following: the synchronization period arrives; the number of unsynchronized binding relationships is greater than a number threshold; the pressure parameter of the binding service is less than a pressure parameter threshold.

10. A method for previewing recommended objects in an application, characterized in that, Applied to a first terminal device and a second terminal device, the method includes: The first terminal device sends the query form information to the delivery server, so that the delivery server uses a pre-established object form inverted index to query the query form information in the query database, selects the candidate objects whose object form information matches the query form information as the objects to be recommended, and stores the object identification information and object form information of the objects to be recommended in the recommendation database. The objects to be recommended are multimedia information that is to be delivered to the application for presentation. The first terminal device receives the object identification information of the object to be recommended from the delivery server, and presents a QR code generated based on the object identification information of the object to be recommended and the jump interface address; In response to the scanning operation of the QR code, the second terminal device reads the object identification information of the recommended object and the jump interface address in the QR code, and accesses the interface corresponding to the jump interface address through the jump interface address; by triggering the bridging interface in the interface, it collects the device identification information of the bound device corresponding to the scanning operation as the binding identification information; wherein, the bridging interface is the JSBridge interface, which is obtained by encapsulating the native device interface used to collect the device identification information; The second terminal device sends the binding identification information and the object identification information of the object to be recommended to the delivery server, so as to establish a binding relationship between the object identification information and the binding identification information of the object to be recommended in the delivery server; The second terminal device presents multiple candidate applications corresponding to the binding identification information. The candidate applications are used to present the object to be recommended. The object form information is obtained by the delivery server calling the binding service according to the binding identification information in the recommendation request, the binding service querying the binding relationship to obtain the object identification information of the object to be recommended, and then querying the recommendation database according to the object identification information. In response to a selection operation for the plurality of candidate applications, the second terminal device presents the recommended object retrieved based on the binding relationship among the selected candidate applications.

11. The method according to claim 10, characterized in that, Before presenting the QR code generated based on the object identifier information of the object to be recommended and the redirection interface address, the method further includes: The first terminal device presents attribute input entries in multiple dimensions; The first terminal device responds to an attribute input operation for at least one dimension of attribute input entry, generates query form information based on the input attribute information of the at least one dimension, and sends the query form information to the delivery server, so that the delivery server determines the recommended object that matches the input attribute information of the at least one dimension among multiple candidate objects.

12. The method according to claim 10, characterized in that, After establishing the binding relationship between the object identifier information and the binding identifier information of the object to be recommended, the method further includes: The first terminal device presents attribute input entries in multiple dimensions; The first terminal device responds to an attribute input operation for at least one dimension of attribute input entry, generates query form information based on the input attribute information of the at least one dimension, and sends the query form information to the delivery server, so that the delivery server determines the recommended object that matches the input attribute information of the at least one dimension among a plurality of recommended objects; Presenting the recommended object retrieved based on the binding relationship in the selected candidate applications includes: The second terminal device presents the matching recommended object in the selected candidate application.

13. A device for previewing recommended objects in an application, characterized in that, The apparatus is used to perform the method according to any one of claims 1-3.

14. A device for previewing recommended objects in an application, characterized in that, The apparatus is used to perform the method of claim 6.

15. A device for previewing recommended objects in an application, characterized in that, The apparatus is used to perform the method according to any one of claims 10 to 12.

16. An electronic device, characterized in that, The electronic device includes: Memory, used to store executable instructions; A processor, when executing executable instructions stored in the memory, implements the application recommendation preview method according to any one of claims 1 to 5, or the application recommendation preview method according to any one of claims 6 to 9, or the application recommendation preview method according to any one of claims 10 to 12.

17. A computer-readable storage medium storing executable instructions, characterized in that, When the executable instructions are executed by the processor, they implement the application recommendation object preview method according to any one of claims 1 to 5, or the application recommendation object preview method according to any one of claims 6 to 9, or the application recommendation object preview method according to any one of claims 10 to 12.

18. A computer program product comprising executable instructions, characterized in that, When the executable instructions are executed by the processor, they implement the application recommendation object preview method according to any one of claims 1 to 5, or the application recommendation object preview method according to any one of claims 6 to 9, or the application recommendation object preview method according to any one of claims 10 to 12.

Images