Commodity information display method and electronic device

Abstract

Embodiments of the present application disclose a commodity information display method and an electronic device. The method comprises: receiving a browsing request for browsing detail content of a first target commodity; obtaining the detail content of the first target commodity and abstract information of a plurality of related commodities of the first target commodity; displaying a target page, the target page comprising a first container and at least one second container displayed on the same screen, wherein the first container is used to display the detail content of the first target commodity, and the second container is used to display the abstract information of the plurality of related commodities; and in response to a content switching operation, determining a second target commodity from the plurality of related commodities displayed in the second container, and switching the content displayed in the first container to detail content corresponding to the second target commodity. Through the embodiments of the present application, the commodity browsing and interaction efficiency of a user can be improved.

Description

Technical Field

[0001] This application relates to the field of information display technology, and in particular to methods and electronic devices for displaying product information. Background Technology

[0002] Product information service systems can provide users with a vast amount of product information. Typically, users need to visit the product details page to view detailed information about the product, including text, images, videos, etc., and then make purchasing decisions based on this information.

[0003] However, in the actual shopping decision-making process, users usually need to compare multiple products before making a final decision. In existing technology, if a user needs to view the details of multiple products during a single browsing session, they typically have to go through the following process: First, after discovering the first product of interest through recommendations or search results, the user clicks to jump to that product's details page; then, they return to the recommendations or search results page, find the next product, and click to jump to the next product's details page, and so on. This requires multiple back-and-forth jumps between multiple pages, making the user's operation path very long.

[0004] Therefore, how to improve the efficiency of users browsing products has become a technical problem that needs to be solved by those skilled in the art. Summary of the Invention

[0005] This application provides a method and electronic device for displaying product information, which can improve the efficiency of users' product browsing and interaction.

[0006] This application provides the following solution:

[0007] A method for displaying product information, comprising:

[0008] Receive a browsing request to view the details of the first target product;

[0009] Obtain the detailed information of the first target product, and the summary information of multiple related products of the first target product;

[0010] The target page is displayed, which includes a first container and at least one second container displayed on the same screen. The first container is used to display the details of the first target product, and the second container is used to display the summary information of the multiple related products.

[0011] In response to the content switching operation, a second target product is determined from the multiple related products displayed in the second container, and the content displayed in the first container is switched to the details content corresponding to the second target product.

[0012] The multiple related products are determined in the following way: based on the type of the source page of the browsing request, when the user has a need to browse other product details in the corresponding scenario, the relationship type between the other products and the first target product is determined, and based on the relationship type, multiple related products that have a corresponding relationship with the first target product are determined.

[0013] The relationship type is determined in the following way:

[0014] The relationship type is determined based on the type of the source page of the browsing request and the pre-saved correspondence between source page types and relationship types; or,

[0015] The relationship type is predicted based on the type of the source page of the browsing request and the user's historical browsing history in the corresponding source page type scenario.

[0016] The types of source pages include: pages containing product recommendation information streams;

[0017] The relevant products include: multiple products in the store to which the first target product belongs.

[0018] The source page includes: an information page containing multiple product search results;

[0019] The relevant products include: multiple products in the product search results that meet the similarity criteria with the first target product.

[0020] The source pages include: the user's order list page, or the page containing a collection of goods to be settled in bulk;

[0021] The related products include: multiple products that are used in combination or in the same scenario as the first target product.

[0022] This also includes:

[0023] The topic tags of the content displayed in the second container are determined according to the relationship type, and the topic tags are displayed in the second container.

[0024] Among them, the multiple related products are multiple groups: the target product and each related product group have different relationship types;

[0025] The method further includes:

[0026] Determine the topic tags based on the relationship type corresponding to each relevant product group;

[0027] The second container displays one of the related product groups and its corresponding hashtags, and provides an option to switch the content displayed in the second container to other hashtags.

[0028] Upon receiving a switching request via this operation option, the display content of the second container is switched to the summary information of each product in the relevant product group corresponding to the other topic tags.

[0029] This also includes:

[0030] When displaying product details through the first container, key information related to the theme of the content displayed in the second container is extracted and displayed in the first container.

[0031] The first container and the second container are displayed side-by-side in a vertically tiled manner.

[0032] The second container displays information about the corresponding product in the form of information cards, wherein the height of a single information card is less than the height of the screen, so that multiple information cards can be displayed within the same screen area.

[0033] The first container and the second container can respond independently to the up and down sliding operation.

[0034] This also includes:

[0035] In response to a state switching request to collapse the second container, the second container is switched to a collapsed state, and the size of the first container in the width direction is increased.

[0036] The state switching request includes: a state switching request initiated by clicking the state switching option provided on the target page, or a state switching request initiated by swiping the page left or right.

[0037] The second container is further used to add the summary information of the target product to the queue of related products;

[0038] In response to a content switching operation, determining a second target product from a plurality of related products displayed in the second container includes:

[0039] In response to a swiping operation that continues after swiping the details displayed in the first container to the top or bottom, the previous or next item of the first target item in the second container is determined as the second target item.

[0040] The step of determining the second target product from multiple related products displayed in the second container in response to a content switching operation includes:

[0041] In response to a click operation on an item in the second container, the currently clicked item in the second container is identified as the second target item.

[0042] A method for displaying product information, comprising:

[0043] Receive browsing requests to view the details of the target product;

[0044] Obtain the detailed information of the target product, as well as the summary information of multiple related products of the target product;

[0045] The target page is displayed, which includes a first container and at least one second container displayed on the same screen. The first container is used to display the details of the target product, and the second container is used to display summary information of the multiple related products.

[0046] A product information display device, comprising:

[0047] A browsing request receiving unit is used to receive browsing requests for browsing the details of the first target product;

[0048] The information acquisition unit is used to acquire the details of the first target product and the summary information of multiple related products of the first target product;

[0049] A page display unit is used to display a target page, which includes a first container and at least one second container displayed on the same screen. The first container is used to display the details of the first target product, and the second container is used to display the summary information of the multiple related products.

[0050] An interactive unit is used to respond to a content switching operation by determining a second target product from multiple related products displayed in the second container and switching the content displayed in the first container to the details content corresponding to the second target product.

[0051] A product information display device, comprising:

[0052] A browsing request receiving unit is used to receive browsing requests for viewing the details of a target product.

[0053] An information acquisition unit is used to acquire the detailed content of the target product and the summary information of multiple related products of the target product;

[0054] A page display unit is used to display a target page, which includes a first container and at least one second container displayed on the same screen. The first container is used to display the details of the target product, and the second container is used to display summary information of the multiple related products.

[0055] A computer-readable storage medium having a computer program stored thereon that, when executed by a processor, implements the steps of any of the preceding methods.

[0056] An electronic device, comprising:

[0057] One or more processors; and

[0058] A memory associated with the one or more processors, the memory being used to store program instructions that, when read and executed by the one or more processors, perform the steps of the method described in any of the preceding descriptions.

[0059] According to the specific embodiments provided in this application, the following technical effects are disclosed:

[0060] Through the embodiments of this application, upon receiving a user's request to browse the details of a first target product, not only can the details of the first target product be obtained, but also summary information of multiple related products can be obtained, and the above content can be displayed on the target page. The target page may include a first container and at least one second container displayed simultaneously. The first container displays the details of the first target product, and the second container displays the summary information of the multiple related products. Furthermore, when the user performs a content switching operation, a second target product can be determined from the multiple related products displayed in the second container, and the content displayed in the first container can be switched to the details of the second target product. In this way, users can compare the details of multiple different products on the same page without having to switch back and forth between multiple different pages, thus improving the user's product browsing and interaction efficiency.

[0061] In an optional implementation, the specific related products can be determined based on the type of the source page of the browsing request. That is, different source page types can reflect, to some extent, the relationship between other products and the current first target product when a user has a need to browse other products. Correspondingly, multiple related products of the current first target product can be determined based on this relationship type. In this way, different product recommendations can be made based on various browsing scenarios to improve the click-through rate or purchase conversion rate of related products displayed in the second container.

[0062] Of course, any product implementing this application does not necessarily need to achieve all of the advantages described above at the same time. Attached Figure Description

[0063] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0064] Figure 1 This is a schematic diagram of the system architecture provided in the embodiments of this application;

[0065] Figure 2 This is a flowchart of the first method provided in the embodiments of this application;

[0066] Figure 3 This is a schematic diagram of the page structure provided in an embodiment of this application;

[0067] Figure 4 This is a schematic diagram of a page example provided in an embodiment of this application;

[0068] Figure 5 This is a flowchart of the second method provided in the embodiments of this application;

[0069] Figure 6 This is a schematic diagram of the first device provided in the embodiments of this application;

[0070] Figure 7 This is a schematic diagram of the second device provided in the embodiments of this application;

[0071] Figure 8 This is a schematic diagram of the electronic device provided in the embodiments of this application. Detailed Implementation

[0072] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0073] First, it's important to clarify that in existing technologies, to facilitate user switching between different product detail pages, a "Recommended" product display area can be provided on the product detail page (e.g., the product A detail page). This area can display links to other products from the same store, or links to similar products from other stores, and so on. However, this recommendation information is usually displayed at the end of the current product A's detail page. Users need to scroll to the bottom of the current product A's detail page to see these recommended product links; alternatively, even if a quick-access anchor is provided at the top of the detail page, users still need to actively click on this anchor to locate the recommended content display area. In other words, the recommended product information on the detail page relies on user actions such as scrolling or clicking to be exposed. Furthermore, even if a user browses this recommended product information and selects another product B to view its details page, if the user wants to return to the details page of product A, they still need to go back through the initial homepage recommendations or search results, find product A, and then click the link for product A again to be redirected to its details page. Clearly, this existing technology still suffers from a lengthy user operation path.

[0074] To address the above situation, this application provides a new solution. In this solution, when a user needs to browse the details of a target product (for ease of description, it can be referred to as the first target product), summary information of multiple related products can be obtained, and then this information can be displayed on the target page. The target page may include a first container and at least one second container displayed simultaneously. The first container can be used to display the details of the target product, while the second container can be used to display the summary information (e.g., main image thumbnail, price, tags, etc.) of the aforementioned multiple related products.

[0075] In other words, on the same page, two or more different containers can be used. The first container displays the details of the current target product, while at least one second container displays summary information of multiple related products. The first and second containers can be displayed simultaneously, meaning multiple containers can appear within the screen's visible range at the same time. For example, taking a single second container as an example, in one specific implementation, the first and second containers can be displayed vertically, meaning the second container can be located to the side of the first container (either to the right or left, etc.), or the two containers can be arranged side-by-side along the page's height. Since pages are typically displayed from top to bottom, simply displaying the target page allows the first and second containers to be displayed simultaneously, enabling users to view information about multiple related products while browsing the details of the current target product without any user intervention.

[0076] Furthermore, the first container in the target page of this application embodiment can also switch between displaying the details of multiple different products. That is, the first container can not only display the details of the current first target product, but also display the details of other products displayed in the second container. This allows for switching between the details of multiple different products within the same target page, eliminating the need to jump between different product detail pages, thus improving interaction efficiency and reducing waste of system resources. Specifically, the first and second containers can also be linked. For example, after sliding the details of the current first target product to the top or bottom in the first container, if the user continues to slide up or down, the previous or next product in the second container can be identified as the second target product, and its corresponding details can be displayed in the first container. Alternatively, while browsing multiple related products displayed in the second container, the user can click on any product. In this case, the clicked product in the second container can be identified as the second target product, and its corresponding details can be displayed in the first container, and so on.

[0077] The specific related products corresponding to the primary target product can be identified in various ways. One optional method is to identify them separately based on the different types of the source page from which the browsing request originates. This will be discussed in detail later.

[0078] From a system architecture perspective, see Figure 1This application embodiment can provide corresponding functions in a product information service system. Specifically, it can interact with the user through a client. After receiving a user's request to browse the details of a first target product, it can obtain the details of the first target product and the summary information of multiple related products from the server or local cache, so as to load them into the first container and the second container of the target page for display. In addition, the client can also respond to the user's interactive operations based on the target page, which may include switching the content displayed in the first container. After determining the second target product from the multiple related products displayed in the second container, the content displayed in the first container is switched to the details of the second target product.

[0079] The specific implementation schemes provided in the embodiments of this application will be described in detail below.

[0080] Example 1

[0081] First, according to Embodiment 1 of this application, from the perspective of the aforementioned client, a method for displaying product information is provided. Referring to Figure 2, this method may specifically include:

[0082] S201: Receive a browsing request to view the details of the first target product.

[0083] Specifically, as mentioned earlier, users can initiate requests to view the details of their primary target product through various channels. For example, when a recommended product feed is displayed on the client's homepage, users can click on links to their primary target products while browsing this feed, thus initiating a request to view the details of those products. Alternatively, after initiating a product search through search entry points provided on the client's homepage or other pages, users can click on links to their primary target products in the search results, thus initiating a request to view the details of those products. Or, when browsing an order list page, users can also click on a link to a primary target product they have already purchased, thus initiating a request to view the details of that product, and so on.

[0084] S202: Obtain the details of the first target product and the summary information of multiple related products of the first target product.

[0085] Upon receiving the aforementioned browsing request, the client can obtain the detailed content of the target product. Additionally, in this embodiment, it can also obtain summary information of multiple related products. The client can obtain this information from the server, or, if it is not the first time accessing the target product, it can obtain the information from its local cache.

[0086] Of course, the summary information of related products does not need to be cached locally. This is because the identified related products and their order can change in real time. Therefore, the client can request the server to determine the specific related products and their corresponding summary information. The server can then determine multiple related products associated with the first target product based on a specific algorithm and extract the corresponding summary information from the product information database.

[0087] There are several ways to determine specific related products. One preferred approach is to identify multiple related products based on the type of page from which the browsing request originates. In other words, after browsing the details of a primary target product, a user often needs to view more product details. These additional products may have some kind of relationship with the primary target product, but this relationship type may differ depending on the scenario (as can be seen from the aforementioned page from which the browsing request originates). For example, if a user selects a product as their primary target product from the recommended product feed on the client's homepage, they may need to compare this primary target product with other products in the same store, such as style. If a user selects a product as their primary target product through a search results page, they may need to compare it with other similar products in the search results, such as price. If a user selects a product as their primary target product through an order list page, they may need to select other products that can be paired with this primary target product, and so on.

[0088] Therefore, in an optional implementation, for a browsing request to view details of the first target product, the type of the source page for the browsing request can be determined first. Then, based on the specific source page type, multiple related products with corresponding relationship types to the first target product can be determined. The correspondence between the source page type and the product relationship type can be pre-saved, so that after determining the source page type, the specific product relationship type can be determined by viewing this correspondence. Alternatively, based on the source page type and the user's browsing history, the relationship type between other products the user needs to view in the corresponding source page scenario and the first target product can be predicted, thus obtaining personalized prediction results based on different users. Then, based on this queried or predicted product relationship type information, multiple related products of the first target product can be determined.

[0089] For example, if the source page is the homepage of a client containing a product recommendation feed, users may be more inclined to explore the details of other products in the same store as the first target product (i.e., the relationship type described above is: products with a store relationship to the first target product). Therefore, the specific identified multiple related products can include multiple products in the store to which the first target product belongs. In other words, multiple products can be retrieved from the store to which the first target product belongs. These products can be products in the store that are related to the current first target product, such as products belonging to the same series as the first target product, or products with similar styles, or even all products in the store, etc. Of course, whether some or all products in the store are considered as the above multiple related products, these products can be sorted according to certain rules. The factors influencing the sorting can be varied, including the product's own attributes (such as whether it is newly listed, whether it has tags like "high sales" or "low price"), its similarity to the current target product (e.g., whether it belongs to the same series as the current target product), and the user's personalized preference information, etc. (The specific sorting algorithm will not be detailed here).

[0090] If the source page of the browsing request is an information page containing multiple product search results, the user may need to view details of other products similar to the first target product, and may also need to compare prices with the current first target product. That is, the relationship type with the first target product could be: products that have some similarity to the first target product, etc. In this case, the specifically identified multiple related products can include: multiple products in the product search results that meet the similarity criteria with the first target product. The calculation of product similarity can be determined by comparing information about specific products across multiple dimensions, etc., which will not be detailed here.

[0091] If the source page of the browsing request is the user's order list page or a page of items awaiting bulk checkout (e.g., a shopping cart page), meaning the user has already purchased or is about to purchase the first target product, then the user may need to view details of products that are paired with the first target product. Therefore, the multiple related products identified at this time can include: multiple products that are paired with the first target product (e.g., a top and pants) or used in the same scenario. The pairing or same-scenario relationships between products can be determined in various ways. For example, one approach is to pre-store the pairing or same-scenario relationships between product categories using a database. Of course, to improve recommendation accuracy, these pairing or same-scenario relationships can be further refined; for example, which styles of shoes, hats, accessories, etc., can be paired with a certain style of skirt, etc. In this way, for the current primary target product, based on information such as the category to which the primary target product belongs, other categories that have a matching relationship or the same usage scenario relationship with the primary target product can be found by querying this database. Then, multiple specific products under these other categories can be selected as multiple related products, and so on.

[0092] It's important to note that when identifying related products that have a pairing relationship or are used in the same scenario, the selection can also be based on the order status associated with the current target product. For example, if the order status of the current target product is "pending shipment," or if the target product is still in the "shopping cart" and has not yet been ordered, then related products that can be paired with it can be prioritized from the same store as the target product. This allows users to prioritize pairing with products from the same store, thus helping both users and merchants save on logistics costs. Of course, if there are no related products that can be paired with it in the same store, or if the quantity is relatively small, then the selection of products to pair with it from across the entire network can be considered, and so on.

[0093] The above describes several types of source pages and the corresponding methods for determining related products. It is understood that in practical applications, there may be other methods for determining related products for other types of source pages, which will not be listed here, but all of them fall within the scope of protection of this application.

[0094] It should be noted that in practical applications, multiple sets of related products can be generated for the same primary target product. Each set of related products can correspond to a different relationship type with the primary target product. For example, it can include related product groups with same store relationship, related product groups with similar relationship, related product groups with matching relationship or same scenario relationship, and so on.

[0095] After identifying multiple related products, the summary information for these products in this embodiment can be pre-defined using required information fields. These fields may include the product's main image (which can be a thumbnail), price, and tags. The server can then provide the client with the information for each related product in these fields, which the client then organizes and displays according to the structure of the target page. Specific tag information can be used to showcase the advantages of the corresponding product. These tags can be pre-added by the server through data statistical analysis, and may include, for example, low price, high sales volume, many positive reviews, etc.

[0096] S203: Display the target page, which includes a first container and at least one second container displayed on the same screen, wherein the first container is used to display the details of the first target product, and the second container is used to display the summary information of the plurality of related products.

[0097] After obtaining the details of the specific first target product and the summary information of multiple related products, a target page can be displayed. This target page may include a first container and at least one second container displayed simultaneously. The first container can be used to display the details of the target product, while the second container can be used to display the summary information of the multiple related products. There can be one or more second containers. In the case of multiple second containers, for example, they can be used to display the summary information of related products with different associations to the current first target product, and so on.

[0098] In one specific implementation, the second container can display summary information of the multiple related products in the form of a feed, and users can browse the information displayed in the second container by scrolling up and down. Furthermore, when multiple products from the same store are related to the current first target product, this second container can also display all products in the store. In this way, users can access all products in a store through the target page provided in this embodiment without needing to navigate to a dedicated store page.

[0099] Specifically, "screen-on-screen display" refers to the simultaneous display of a first container and at least one second container within the same visible area of ​​the screen. In practice, this screen-on-screen display can be achieved in various ways. For example, the second container can be displayed as a floating layer, and its position relative to the outer frame window can be fixed. This way, even if the content in the first container is scrolled up or down, the second container will not be scrolled out of the visible area. With this floating layer display method, the second container can be displayed in any position relative to the first container; for example, it can be displayed horizontally at the top or bottom of the first container, or vertically to the left or right of the first container, and so on.

[0100] Alternatively, in a more preferred embodiment, the first and second containers can be displayed side-by-side in a vertically tiled manner (within the same application's frame window). Since the target page is typically displayed vertically from top to bottom, this vertically tiled display method naturally allows the two containers to be displayed simultaneously without relying on user interaction with the target page. For example, as... Figure 3 As shown, 31 represents the first container, and 32 represents the second container. Thus, when the target page is displayed, both the first and second containers can be shown simultaneously. Of course, in practical applications, only the first container can be displayed by default. Users can then expand the second container by clicking relevant operation options or swiping left or right within the first container, resulting in a vertically tiled display of the first and second containers on the same screen. Furthermore, in specific implementations, user browsing preferences can be statistically analyzed based on historical operation records. This allows for different display methods for the first and second containers depending on the user's preferences. For example, some users might directly display both containers on the same screen, while others might only display the first container by default, with the second container appearing only after user interaction.

[0101] Among them, such as Figure 3As shown, the first container can be larger than the second container in width to more clearly display the details of the target product. Regarding the product information displayed in the second container, since it typically only requires displaying a thumbnail of the product's main image, price, and other summary information, this information can be carried using smaller information cards. Therefore, the width of the second container is sufficient to accommodate these information cards displayed in a single column. Furthermore, precisely because the information cards displayed in the second container are smaller—at least in height than the screen height—N (where N is an integer greater than 1) of the information cards can be displayed within the same screen area. For example, as... Figure 3 In the example shown at point 32, the second container can display information for N=6 products within the same screen area (of course, the 6 products on the first screen can also include the target product currently being displayed for details in the first container). Thus, by having a user click on a target product, at least 6 products can be exposed. For example, in a practical application, the page display could be as follows: Figure 4 As shown in (A), assuming a user clicks on a product from the search results page on the homepage, the displayed target page may include the product details displayed in the first container, and may also display summary information of multiple related products in the second container, etc.

[0102] Furthermore, in practical implementation, the theme tags of the content displayed in the second container can be determined based on the relationship type between the aforementioned related products and the current first target product. The content theme can also be displayed in the second container to allow users to more intuitively understand the relationship between the content displayed in the two containers. For example, when the source page is a search results page, the specific theme displayed could be "Compare Prices for You"; when the source page is a homepage recommendation feed, the specific theme displayed could be "Good Finds in the Same Store"; when the source page is an order list page or shopping cart page, the specific theme displayed could be "Matching Out Your Choices," and so on.

[0103] If multiple related products have various relationship types with the target product, they can be divided into multiple related product groups, each corresponding to a relationship type and, correspondingly, a aforementioned topic tag. In this case, during the actual display, one of the related product groups and its corresponding topic tag can be displayed in the second container, and options can be provided to switch the display content of the second container to other topic tags. For example, as... Figure 4As shown at point 41 in (A), the topic tag corresponding to the relevant product group currently displayed in the second container is "Compare Prices for You". Additionally, as shown at point 42 in the figure, an option is provided to switch to displaying the relevant product group corresponding to "Same Store Best Deals". Upon receiving a switching request via this option, the display content of the second container can be switched to summary information of each product in the relevant product group corresponding to the other topic tag.

[0104] Furthermore, when displaying the details of a specific product through the first container, all details can be displayed directly in the first container. Alternatively, in an optional implementation, the details of the specific product can be filtered based on the content themes of related products in the second container before being displayed in the first container. For example, for the theme "Compare Prices for You," when displaying the product details through the first container, key information related to price comparison is extracted and displayed in the first container, while other content unrelated to price comparison can be omitted to avoid interfering with the user's browsing experience and further improve browsing efficiency.

[0105] It should be noted that, in the scenario where the first and second containers are displayed side-by-side in a vertically tiled manner, both containers can independently respond to vertical swiping operations. In other words, users can swipe up and down on the first and second containers separately. For example, if a user wants to view more details about the current target product, they can swipe up or down within the area of ​​the first container to bring other details into the visible range of the first container's window, while the content in the second container remains unchanged. Similarly, if a user wants to view more summary information about related products, they can swipe up or down within the area of ​​the second container to bring summary information about other products into the visible range of the second container's window, while the content in the first container remains unchanged, and so on.

[0106] S204: In response to the content switching operation, determine the second target product from the multiple related products displayed in the second container, and switch the content displayed in the first container to the details content corresponding to the second target product.

[0107] During the display process using the aforementioned first and second containers, the first container can also be used to switch the display of details for multiple related products shown in the second container. There are several specific switching methods. For example, in one method, after the user scrolls the details of the current target product displayed in the first container to the top or bottom, if they continue to scroll up or down, the previous or next product in the second container is identified as the second target product, and its details are retrieved. Then, the content displayed in the first container can be switched to the details of the previous or next product. For example, in a specific implementation, it can be as follows: Figure 4 As shown at point 43 in (B), when the user scrolls to the bottom (or top) of the current product details, a prompt can be provided. This prompt may include graphic elements such as arrows encouraging the user to continue scrolling, or text prompts such as "Continue scrolling to view the next item," etc. In other words, if the target product displayed in the first container is product A, and product B is displayed after product A in the second container, then if the user scrolls down in the area of ​​the first container until reaching the bottom of product A's details and continues scrolling down, the content displayed in the first container can be switched to product B's details.

[0108] Furthermore, after switching the content displayed in the first container to the details of the previous or next product, the display focus in the second container can be simultaneously moved to the previous or next product. That is, in the initial state, since the first container displays the details of the target product requested by the user, the display focus in the second container can be on that target product, meaning the summary information of that target product is displayed as selected. For example, it can be distinguished from other product information through highlighting. In this state, if the user has already scrolled to the top or bottom of the target product's details in the first container and continues scrolling, the details of the previous or next product can be loaded into the first container for display based on the product's order in the second container. Simultaneously, the display focus in the second container can be moved to the previous or next product, meaning the summary information of the previous or next product is displayed as selected.

[0109] Alternatively, while browsing the product summary information displayed in the second container, users can click on the summary information of any product. In this case, the clicked product in the second container will be designated as the second target product, and its corresponding details will be displayed in the first container. That is, assuming the first container currently displays the details of product A, and the second container displays summary information of multiple products from the same store as product A, users can click on the summary information of products of interest at any time while swiping up and down in the area of ​​the second container to view the products in the store. For example, clicking on product D will display the details of product D in the first container.

[0110] It should be noted that, in practical implementation, to meet the different access needs of various users, the second container can also include an expanded state and a collapsed state. Under normal circumstances, the second container can be in the expanded state by default. In this case, after receiving a request to collapse the second container, the client can switch the second container to the collapsed state and also expand the width of the first container, that is, display it as a normal product details page. The specific state switching request can be initiated in various ways, such as through state switching options provided on the target page, such as... Figure 4 As shown at point 44 in (A), a "Collapse" button can be provided. Users can then initiate a state transition request by clicking this option. After the second container is collapsed, the "Collapse" button can be displayed as "Expand," and users can click this button again to switch the second container back to the expanded state. Alternatively, if the first and second containers are tiled vertically, a state transition request can be initiated by swiping left or right on the page. For example, if the second container is to the right of the first container, a swipe to the right within the first container's area will collapse the second container. After collapsing, a swipe to the left will switch the second container back to the expanded state.

[0111] In summary, through the embodiments of this application, upon receiving a user's request to browse the details of a first target product, not only can the details of the first target product be obtained, but also summary information of multiple related products can be obtained, and the above content can be displayed on the target page. The target page can include a first container and at least one second container displayed simultaneously. The first container displays the details of the first target product, and the second container displays the summary information of the multiple related products. Furthermore, when the user performs a content switching operation, a second target product can be determined from the multiple related products displayed in the second container, and the content displayed in the first container can be switched to the details of the second target product. In this way, users can compare the details of multiple different products on the same page without having to switch back and forth between multiple different pages, thus improving the user's product browsing and interaction efficiency.

[0112] In an optional implementation, the specific related products can be determined based on the type of the source page of the browsing request. That is, different source page types can reflect, to some extent, the relationship between other products and the current first target product when a user has a need to browse other products. Correspondingly, multiple related products of the current first target product can be determined based on this relationship type. In this way, different product recommendations can be made based on various browsing scenarios to improve the click-through rate or purchase conversion rate of related products displayed in the second container.

[0113] Example 2

[0114] In the aforementioned Embodiment 1, the introduction mainly focused on facilitating users' comparison of details for multiple different products. In Embodiment 2, another method for displaying product information is also provided, see [link to Embodiment 1]. Figure 5 The method may include:

[0115] S501: Receive a browsing request to view the details of the target product;

[0116] S502: Obtain the detailed content of the target product and the summary information of multiple related products of the target product;

[0117] S503: Display the target page, which includes a first container and at least one second container displayed on the same screen, wherein the first container is used to display the details of the target product, and the second container is used to display the summary information of the multiple related products.

[0118] Through this second embodiment, when a user accesses the details of a target product, while the details of the target product are displayed in the first container, summary information of more related products can be displayed in the second container on the same screen. In this way, the traffic generated by a user's access to a target product can bring exposure opportunities to multiple products. Therefore, the limited user traffic can be utilized more fully to improve the product exposure rate in the system.

[0119] Regarding the arrangement of the first and second containers, please refer to Embodiment 1 and other parts of this application specification, which will not be repeated here.

[0120] It should be noted that the embodiments of this application may involve the use of user data. In practical applications, user-specific personal data may be used in the scheme described herein within the scope permitted by applicable laws and regulations, provided that it complies with the applicable laws and regulations of the country (e.g., with the user's explicit consent, with the user being properly notified, etc.).

[0121] Corresponding to Embodiment 1, this application also provides a product information display device, see [link to embodiment]. Figure 6 The device may include:

[0122] The browsing request receiving unit 601 is used to receive a browsing request to browse the details of the first target product;

[0123] The information acquisition unit 602 is used to acquire the details of the first target product and the summary information of multiple related products of the first target product;

[0124] The page display unit 603 is used to display a target page, which includes a first container and at least one second container displayed on the same screen. The first container is used to display the details of the first target product, and the second container is used to display the summary information of the multiple related products.

[0125] The interaction unit 604 is used to respond to a content switching operation, determine a second target product from a plurality of related products displayed in the second container, and switch the content displayed in the first container to the details content corresponding to the second target product.

[0126] The multiple related products are determined in the following way: based on the type of the source page of the browsing request, when the user has a need to browse other product details in the corresponding scenario, the relationship type between the other products and the first target product is determined, and based on the relationship type, multiple related products that have a corresponding relationship with the first target product are determined.

[0127] The specific type of relationship can be determined in the following ways:

[0128] The relationship type is determined based on the type of the source page of the browsing request and the pre-saved correspondence between source page types and relationship types; or,

[0129] The relationship type is predicted based on the type of the source page of the browsing request and the user's historical browsing history in the corresponding source page type scenario.

[0130] Specifically, the source page includes: the client homepage containing a product recommendation information stream; at this time, the related products include: multiple products in the store to which the first target product belongs.

[0131] Alternatively, the source page may include an information page containing multiple product search results; in this case, the related products may include multiple products in the product search results that meet the similarity criteria with the first target product.

[0132] Alternatively, the source page may include: the user's order list page, or a collection page of goods to be settled in bulk; in this case, the related goods may include: multiple goods that are used in combination or in the same scenario as the first target goods.

[0133] In a specific implementation, the device may further include:

[0134] The topic tag display unit is used to determine the topic tags of the content displayed in the second container according to the relationship type, and display the topic tags in the second container.

[0135] Among them, the multiple related products are multiple groups: the target product and each related product group have different relationship types;

[0136] The device may further include:

[0137] The topic tag determination unit is used to determine topic tags based on the relationship type corresponding to each relevant product group;

[0138] The theme switching operation option providing unit is used to display one of the related product groups and the corresponding theme tags in the second container, and to provide operation options for switching the display content of the second container to other theme tags;

[0139] The theme switching unit is used to switch the display content of the second container to the summary information of each product in the relevant product group corresponding to the other theme tags after receiving a switching request through the operation option.

[0140] Additionally, the device may also include:

[0141] The key information extraction unit is used to extract key information related to the theme of the content displayed in the second container when displaying product details through the first container, and then display it in the first container.

[0142] In practice, the first container and the second container are displayed side-by-side in a vertically tiled manner.

[0143] The second container can display information about the corresponding product in the form of information cards, wherein the height of a single information card is less than the height of the screen, so that multiple information cards can be displayed within the same screen area.

[0144] The first container and the second container can respond to the up and down sliding operations independently.

[0145] In a specific implementation, the device may further include:

[0146] A container state switching unit is used to switch the second container to a collapsed state and expand the size of the first container in the width direction in response to a state switching request for collapsing the second container.

[0147] The state switching request includes: a state switching request initiated by clicking the state switching option provided on the target page, or a state switching request initiated by swiping the page left or right.

[0148] Specifically, the second container is also used to add the summary information of the target product to the queue of related products;

[0149] At this point, the interaction unit can specifically be used for:

[0150] In response to a swiping operation that continues after swiping the details displayed in the first container to the top or bottom, the previous or next item of the first target item in the second container is determined as the second target item.

[0151] Alternatively, the interaction unit can also be specifically used for:

[0152] In response to a click operation on an item in the second container, the currently clicked item in the second container is identified as the second target item.

[0153] Corresponding to Embodiment 2, this application also provides a product information display device, see [link to embodiment]. Figure 7 The device may include:

[0154] The browsing request receiving unit 701 is used to receive browsing requests for browsing the details of a target product;

[0155] The information acquisition unit 702 is used to acquire the detailed content of the target product and the summary information of multiple related products of the target product;

[0156] The page display unit 703 is used to display a target page, which includes a first container and at least one second container displayed on the same screen. The first container is used to display the details of the target product, and the second container is used to display the summary information of the multiple related products.

[0157] In addition, embodiments of this application also provide a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the method described in any of the foregoing method embodiments.

[0158] And an electronic device, comprising:

[0159] One or more processors; and

[0160] A memory associated with the one or more processors, the memory being used to store program instructions that, when read and executed by the one or more processors, perform the steps of the method described in any of the foregoing method embodiments.

[0161] in, Figure 8 The architecture of an electronic device is illustrated by example. For example, device 800 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, aircraft, etc.

[0162] Reference Figure 8 The device 800 may include one or more of the following components: a processing component 802, a memory 804, a power supply component 806, a multimedia component 808, an audio component 810, an input / output (I / O) interface 812, a sensor component 814, and a communication component 816.

[0163] Processing component 802 typically controls the overall operation of device 800, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 802 may include one or more processors 820 to execute instructions to perform all or part of the steps of the methods provided in this disclosure. Furthermore, processing component 802 may include one or more modules to facilitate interaction between processing component 802 and other components. For example, processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.

[0164] Memory 804 is configured to store various types of data to support the operation of device 800. Examples of this data include instructions for any application or method operating on device 800, contact data, phonebook data, messages, pictures, videos, etc. Memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0165] Power supply component 806 provides power to various components of device 800. Power supply component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to device 800.

[0166] Multimedia component 808 includes a screen that provides an output interface between device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 808 includes a front-facing camera and / or a rear-facing camera. When device 800 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0167] Audio component 810 is configured to output and / or input audio signals. For example, audio component 810 includes a microphone (MIC) configured to receive external audio signals when device 800 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 804 or transmitted via communication component 816. In some embodiments, audio component 810 also includes a speaker for outputting audio signals.

[0168] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0169] Sensor assembly 814 includes one or more sensors for providing status assessments of various aspects of device 800. For example, sensor assembly 814 may detect the on / off state of device 800, the relative positioning of components such as the display and keypad of device 800, changes in the position of device 800 or a component of device 800, the presence or absence of user contact with device 800, the orientation or acceleration / deceleration of device 800, and temperature changes of device 800. Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 814 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0170] Communication component 816 is configured to facilitate wired or wireless communication between device 800 and other devices. Device 800 can access wireless networks based on communication standards, such as WiFi, or mobile communication networks such as 2G, 3G, 4G / LTE, and 5G. In one exemplary embodiment, communication component 816 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 816 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0171] In an exemplary embodiment, device 800 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0172] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, which can be executed by a processor 820 of device 800 to perform the method provided by the present disclosure. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0173] As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in various embodiments or some parts of the embodiments of this application.

[0174] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, for system or system embodiments, since they are basically similar to method embodiments, the description is relatively simple, and relevant parts can be referred to the descriptions in the method embodiments. The systems and system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0175] The product information display method and electronic device provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and its core ideas. Furthermore, those skilled in the art will recognize that, based on the ideas of this application, there will be changes in the specific implementation methods and application scope. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A method for displaying product information, characterized in that, include: Receive a browsing request to view the details of the first target product; The process involves obtaining detailed information about the first target product and summary information about multiple related products. The determination of these related products includes: determining the type of the source page corresponding to the browsing request; and determining multiple related products with a corresponding relationship type based on the source page type. The relationship type includes having a same-store relationship with the first target product, a similarity relationship with the first target product, or a combination or same-scenario usage relationship with the first target product. The multiple related products are grouped, with each group corresponding to a different relationship type. The target page is displayed, comprising a first container and at least one second container displayed simultaneously. The first container displays the details of the first target product, and the second container displays summary information and corresponding hashtags for each product in a related product group. An option is provided to switch the display content of the second container to the content corresponding to other hashtags. Upon receiving a switching request via the option, the display content of the second container is switched to the summary information of each product in the related product group corresponding to other hashtags. The hashtags are determined based on the relationship type corresponding to each related product group. In response to the content switching operation, a second target product is determined from the multiple related products displayed in the second container, and the content displayed in the first container is switched to the details content corresponding to the second target product.

2. The method according to claim 1, characterized in that, The relationship type is determined in the following way: The relationship type is determined based on the type of the source page of the browsing request and the pre-saved correspondence between the source page type and the relationship type; or, The relationship type is predicted based on the type of the source page of the browsing request and the user's historical browsing history in the corresponding source page type scenario.

3. The method according to claim 1, characterized in that, The source page includes: a page containing a product recommendation information stream; the determined relevant product group is: a related product group within the same store, including: multiple products in the store to which the first target product belongs; or, The source page includes: an information page containing multiple product search results; the determined related product groups are related product groups with similar relationships, including: multiple products in the product search results that meet the similarity criteria with the first target product; or... The source page includes: the user's order list page, or the collection page of goods to be settled in batches; the determined related product group is a related product group with a matching or same usage scenario, including: multiple products that have a matching or same usage scenario with the first target product.

4. The method according to any one of claims 1 to 3, characterized in that, The first container and the second container are displayed side-by-side in a vertically tiled manner.

5. The method according to claim 4, characterized in that, Also includes: In response to a state switching request to collapse the second container, the second container is switched to a collapsed state, and the size of the first container in the width direction is increased.

6. The method according to claim 5, characterized in that, The state switching request includes: a state switching request initiated by clicking the state switching option provided on the target page, or a state switching request initiated by swiping the page left or right.

7. The method according to any one of claims 1 to 3, characterized in that, The second container is also used to add the summary information of the target product to the queue of related products; In response to a content switching operation, determining a second target product from a plurality of related products displayed in the second container includes: In response to a swiping operation that continues after swiping the details displayed in the first container to the top or bottom, the previous or next item of the first target item in the second container is determined as the second target item.

8. The method according to any one of claims 1 to 3, characterized in that, In response to a content switching operation, determining a second target product from a plurality of related products displayed in the second container includes: In response to a click operation on an item in the second container, the currently clicked item in the second container is identified as the second target item.

9. A method for displaying product information, characterized in that, include: Receive browsing requests to view the details of the target product; The system obtains the detailed content of the target product and summary information of multiple related products. The determination of the multiple related products includes: determining the type of the source page corresponding to the browsing request, and determining multiple related products with corresponding relationship types to the target product based on the source page type. The relationship types include having a same-store relationship with the target product, a similarity relationship with the target product, or a combination or same-scenario usage relationship with the first target product. The multiple related products are in multiple groups, with each group corresponding to a different relationship type. The target page is displayed, comprising a first container and at least one second container displayed simultaneously. The first container displays the details of the target product, and the second container displays summary information and corresponding hashtags for each product in a related product group. An option is provided to switch the content displayed in the second container to the content displayed for other hashtags. Upon receiving a switching request via the option, the content displayed in the second container is switched to the summary information of each product in the related product group corresponding to another hashtag. The hashtags are determined based on the relationship type of each related product group.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the program implements the steps of the method described in any one of claims 1 to 9.

11. An electronic device, characterized in that, include: One or more processors; as well as A memory associated with the one or more processors, the memory being used to store program instructions that, when read and executed by the one or more processors, perform the steps of the method according to any one of claims 1 to 9.

Images