Information processing, display method, and electronic device

By identifying items with low purchase intent in the shopping cart as a second category of items, displaying basic information, and dynamically expanding the shopping cart capacity, the problem of a full shopping cart is solved, improving user experience and system performance.

CN122243602APending Publication Date: 2026-06-19TAOBAO CHINA SOFTWARE

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
TAOBAO CHINA SOFTWARE
Filing Date
2026-01-29
Publication Date
2026-06-19

AI Technical Summary

Technical Problem

In existing technologies, when a user's shopping cart is full and no more items can be added, a cleanup operation is required, which increases the workload and negatively impacts the user experience.

Method used

Products with a purchase intention below a threshold are identified as a second category of products and recorded differently from normal products. Only basic information is displayed, the shopping cart capacity remains unchanged, and the shopping cart capacity is dynamically expanded.

Benefits of technology

Without increasing shopping cart capacity, this reduces the number of data queries, avoids excessively long page loading times, eliminates the need for users to perform cleanup operations, and improves user experience and system service capabilities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122243602A_ABST
    Figure CN122243602A_ABST
Patent Text Reader

Abstract

This application discloses an information processing and display method and electronic device, including: identifying at least one object from a user-associated object temporary storage set whose current purchase intention is below a threshold as a second type of object, and recording it differently from other first type objects in the object temporary storage set; upon receiving a request to display an information page corresponding to the object temporary storage set, for the first type of object, obtaining information of at least one first field and at least one second field; for the second type of object, obtaining information of the at least one first field, and providing the obtained information to the client for display; wherein, the first field includes fields related to object identification, and the second field includes fields related to transaction information. Through this application embodiment, users can complete operations such as adding items to their cart with low operational burden, improving the system's service capabilities and user experience.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

[0002] In applications provided by product information service systems, a "shopping cart" function is typically offered to users. From a technical perspective, it is essentially a temporary, state-rich information aggregation that can coordinate multiple upstream and downstream businesses (products, inventory, promotions, users, etc.) and manage complex state transitions (from browsing to "adding items to reach the minimum purchase amount" and placing an order). From the user's perspective, the basic function of the "shopping cart" can be as a temporary container for selected items, allowing users to collect items of interest without the pressure of purchasing, and to view the "total price" of multiple items in real time, helping users control their total spending. The "shopping cart" can also be used as a price drop reminder or arrival reminder, or to test different coupon combinations to achieve "adding items to reach the minimum purchase amount," and so on.

[0003] As users increasingly utilize the shopping cart feature, especially active users, they often find themselves in situations where their carts are full and they cannot add more items. While the system can prompt users to remove some items from their carts before adding more, the fact that users still need to perform this action can feel burdensome, and some users may even be unwilling to do so despite receiving the reminder.

[0004] It is evident that how to enable users to complete tasks such as adding items to their cart with minimal operational burden, thereby improving the system's service capabilities and user experience, has become a technical problem that needs to be solved by those skilled in the art. Summary of the Invention

[0005] This application provides information processing, display methods, and electronic devices that enable users to complete operations such as adding items to their cart with low operational burden, thereby improving the system's service capabilities and user experience.

[0006] This application provides the following solution: An information processing method, comprising: Identify at least one object from the temporary object storage set associated with the user whose current purchase intention is below a threshold as a second type of object, and record it differently from other first type objects in the temporary object storage set; Upon receiving a request to display the information page corresponding to the object temporary storage set, for the first type of object, information of at least one first field and at least one second field is obtained; for the second type of object, information of the at least one first field is obtained, and the obtained information is provided to the client for display; wherein, the first field includes fields related to object identification, and the second field includes fields related to transaction information.

[0007] Before identifying at least one object from the temporary object storage set associated with the user whose current purchase intention is below a threshold, the method further includes: The number of objects in the object temporary storage set is determined. If the maximum capacity of the object temporary storage set has been reached or is about to be reached, the process of identifying at least one object in the user's associated object temporary storage set whose current purchase intention is below a threshold is triggered.

[0008] The step of identifying at least one object from the temporary object storage set associated with the user whose current purchase intention is below a threshold includes: If an object is added to the object temporary storage set for a period of time that reaches a first duration threshold, then the object is identified as an object whose current purchase intention of the user is lower than the threshold.

[0009] The second type of object, identified from the temporary object storage set associated with the user, includes at least one object whose current purchase intention is below a threshold. If an object has been added to the object temporary storage set for a period of time that reaches the second duration threshold, and the user has not performed any target operation on the object after it has been added to the object temporary storage set, then the object is identified as an object whose current purchase intention is lower than the threshold.

[0010] This also includes: Add an object category field to the data table corresponding to the object temporary storage set; in the default state after an object is added to the object temporary storage set, the data in the object category field is of the first category; The process of differentiating the first type of objects from other normal objects in the object temporary storage set includes: When an object in the object temporary storage set is identified as an object whose current purchase intention is below a threshold, the data of that object in the object category field of the data table is modified to the second category.

[0011] The step of differentiating the first type of objects from other normal objects in the object temporary storage set includes: The information of the second type of object is separated from the original data table and saved to a dedicated data table for the second type of object, while the first type of object is retained in the original data table.

[0012] When displaying the information page, the client will show the second type of object as non-tradable.

[0013] When the client displays information about the second type of object on the information page, it provides a restore option for the second type of object so as to restore the second type of object to the first type of object.

[0014] An information display method, comprising: Receive a request to display the information page corresponding to the temporary collection of objects associated with the target user; Obtain object information from the object temporary storage set. The object information includes information about a first type of object in at least one first field and at least one second field, and information about a second type of object in the at least one first field. The second type of object is at least one object identified from the object temporary storage set whose current purchase intention is below a threshold. The first field includes fields related to object identification, and the second field includes fields related to transaction information. The information page displays object information in the object temporary collection.

[0015] The provision that the object information in the object temporary storage set is displayed on the information page includes: A first area and a second area are created on the information page. The first area displays information about the first type of object, and the second area displays information about the second type of object. The second area is located below the first area.

[0016] In the information page, the first type of object is displayed as tradable, and the second type of object is displayed as non-tradable.

[0017] This also includes: The information page also provides functional options related to object comparison and / or object recommendation for the first type of object, while the second type of object does not have the functional options, or the functional options are displayed as inoperable.

[0018] This also includes: When displaying information about the second type of object on the information page, a recovery operation option is provided for the second type of object; After receiving a recovery operation request for one of the target objects through the operation options, the request is submitted to the server so that the target object can be restored to the first type of object, and the information of the target object on the extended field is obtained and returned. The information page will supplement the information of the target object on the extended field.

[0019] This also includes: The information page provides operation options for performing batch operations on the second type of objects; After receiving an operation request through the operation options, a batch operation interface is displayed so that batch operations can be performed on the second type of objects through the batch operation interface. The batch operations include batch recovery, batch moving to favorites and / or batch deletion.

[0020] The batch operation interface provides options for batch management of tags and batch clearing of tags. When the batch management tab option is selected, thumbnails of the second type of objects are displayed in the batch operation interface, checkboxes are provided for each object, and options for restore, move to favorites and / or delete are provided. When the batch cleanup tag option is selected, the thumbnails of the second type of objects are displayed in groups in the batch operation interface. Checkboxes are provided for each object, and a full selection box is provided for each group to facilitate batch moving of groups into favorites and / or deletion.

[0021] 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.

[0022] An electronic device, comprising: One or more processors; and 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 any of the preceding methods.

[0023] A computer program product includes a computer program / computer executable instructions that, when executed by a processor in an electronic device, implement the steps of any of the preceding methods.

[0024] According to the specific embodiments provided in this application, the following technical effects are disclosed: Through the embodiments of this application, at least one object whose current purchase intention is below a threshold can be identified from the user's associated object temporary storage set as a second type of object, and recorded differently from other first type objects in the object temporary storage set. Upon receiving a request to display the information page corresponding to the object temporary storage set, for the first type of object, information on at least one first field and at least one second field is obtained; for the second type of object, information on the at least one first field is obtained, and the obtained information is provided to the client for display. In this way, since the number of objects in the shopping cart is actually the sum of the number of first type and second type objects, the shopping cart capacity is expanded. Simultaneously, since the second type of object only needs to display information on a few fields, even if the sum of the number of first type and second type objects in the shopping cart exceeds the object capacity limit of the shopping cart in traditional solutions, it will not cause excessively long page loading or refresh times. Furthermore, since users do not need to perform operations such as clearing the shopping cart, users can complete operations such as adding items to the cart with low operational burden, thereby improving the system's service capabilities and user experience.

[0025] 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

[0026] 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.

[0027] Figure 1 This is a schematic diagram of the system architecture provided in the embodiments of this application; Figure 2 This is a flowchart of the server-side method provided in the embodiments of this application; Figure 3 This is a schematic diagram of the first interface provided in an embodiment of this application; Figure 4 This is a schematic diagram of the second interface provided in an embodiment of this application; Figure 5 This is a flowchart of the client method provided in the embodiments of this application; Figure 6 This is a schematic diagram of the electronic device provided in the embodiments of this application. Detailed Implementation

[0028] 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.

[0029] First, it's important to clarify that, regarding the situation where the shopping cart is full and no more items can be added, besides reminding users to clear the cart, another method is to expand the cart's capacity—that is, directly increasing its size to accommodate more items. However, on the one hand, each direct expansion involves significant technical modifications and resource costs; on the other hand, the shopping cart's capacity cannot be expanded indefinitely. This is mainly because displaying the user's shopping cart page typically requires expressing multiple capabilities. This necessitates fetching relevant data from multiple upstream and downstream systems, including retrieving basic information such as product images, titles, and prices from a product database, querying promotional information from relevant marketing systems, and so on. It may also involve many interconnected operations; for example, data must be fetched from one data source before other data can be fetched from another. In this scenario, if the shopping cart contains too many items, the interaction time with upstream and downstream systems will be excessively long, consequently extending the data loading or refresh time on the page, causing users to wait for extended periods. Furthermore, the shopping cart page supports user actions such as browsing, selecting, and selecting all. Especially during the selection process, the combined discount information needs to be recalculated. Therefore, if the shopping cart contains a large number of items, this operation will take a considerable amount of time, impacting the user experience. Clearly, this method of directly expanding capacity cannot fundamentally solve the problem of shopping cart capacity.

[0030] To address the above issues, this application provides a "dynamic expansion" implementation scheme. Dynamic expansion refers not to directly increasing the shopping cart's (which can be referred to as a "temporary collection of selected items" in this application; for ease of understanding, this specification primarily uses "shopping cart" as an example) capacity, but rather, while maintaining the shopping cart's capacity limit, identifying items from the shopping cart with relatively low current purchase intent as second-category items. For example, if an item was added to the shopping cart a long time ago, possibly more than a year ago (or other thresholds), it can be considered that the user currently has a low purchase intent for that item and can be recorded as a second-category item. Alternatively, if an item was added to the shopping cart less than a year ago, but still a relatively long time ago (e.g., more than six months), and the user hasn't performed any actions on the item since adding it (including selecting it, viewing product details, etc.), then the user's purchase intent for that item may also be relatively low, and so on. In practice, the above-mentioned operation of identifying second-category items can be performed at any time, or it can be performed when the number of items in a user's shopping cart has reached or is about to reach the capacity limit, etc. After identifying the second category of goods, the other goods in the shopping cart that are in a normal state can be referred to as the first category of goods. Furthermore, the second category of goods can be recorded differently from the first category. For example, the information for the second category of goods can be separated from the original data table and stored in a separate data table; or, a relevant field can be added to the original data table, and different values ​​in this field can be used to distinguish between the first and second categories of goods, and so on.

[0031] Based on the above division of items in the shopping cart into Category 1 and Category 2, when displaying the shopping cart page, Category 1 items, being in a normal state, can be displayed according to normal shopping cart logic. This means that in addition to displaying basic fields such as product images, titles, and prices, extended fields such as available discounts and user benefits (e.g., free shipping, interest-free installments) can also be shown. Furthermore, features like "compare," selection options, and the ability to select multiple items for simultaneous ordering can be supported. However, for Category 2 items, since the user's current purchase intention is likely low, only the basic fields mentioned above can be displayed. In this way, even if only some items in the shopping cart require more detailed information as normal, while others identified as Category 2 items only need basic information, the number of queries to upstream and downstream data sources can be reduced. Therefore, even with a large number of items in the shopping cart, the overhead of querying upstream and downstream data sources will not be excessive, thus preventing excessively long page loading or refresh times. In addition, since the second category of products does not need to support the purchase function when displayed, the user will not be affected by the second category of products when performing the selection operation of the first category of products in the shopping cart, and the specific response time can still be controlled within a certain range.

[0032] Of course, during the display of information on the second category of products on the specific shopping cart page, an option to restore the second category of products can also be provided. If the quantity of the first category of products in the shopping cart has not yet reached the limit, a selected second category product can be restored to a first category product, so that the product can be combined with other first category products for ordering, and so on.

[0033] By employing the above method, since the quantity of items in the shopping cart is actually the sum of the quantities of the first and second categories of items, the cart's capacity is expanded. Furthermore, because the second category of items only needs to display a few basic fields of information, even if the combined quantity of the first and second categories exceeds the traditional cart capacity limit, it won't lead to excessively long page loading or refresh times. Additionally, since users don't need to perform actions like clearing the cart, they can easily add items to their cart with minimal effort, thus improving the system's service capabilities and user experience.

[0034] From a system architecture perspective, the embodiments of this application can provide the above-mentioned solution for "dynamically expanding" the shopping cart in a product information service system. For example... Figure 1As shown, the system can include a client and a server. The client can primarily exist as a mobile application (App), or a web page, H5 page, etc., allowing users to perform actions such as adding items to their shopping cart. The server handles the process of identifying the second category of items from the user's shopping cart, performing differential recording processing between the identified second category and the first category. After a user requests to view the shopping cart page through the client, the server can obtain information about the shopping cart items in multiple fields from multiple data sources. The amount of information required for the second category is less than that for the first category. The server can then return the specific items in the shopping cart and their corresponding first or second category information to the client, which then displays them on the shopping cart page.

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

[0036] Example 1 First, from the perspective of the aforementioned server, Embodiment 1 of this application provides an information display method, see [link to embodiment]. Figure 2 The method may specifically include: S201: Identify at least one object from the temporary object storage set associated with the user whose current purchase intention is below a threshold as a second type of object, and record it differently from other first type of objects in the temporary object storage set.

[0037] It should be noted that in a product information service system, the specific "object" can refer to a product, and correspondingly, the "object temporary storage set" can be called the "selected product temporary storage set," which is the "shopping cart" mentioned earlier. Alternatively, in other systems, the "object" can be other data objects, and the "object temporary storage set" can have other specific names; this is not limited here. For ease of description and understanding, we will mainly use products and shopping carts as examples.

[0038] In this embodiment of the application, the server can identify the products in the temporary collection of selected products associated with the user (i.e., the "shopping cart"), and identify at least one product whose current purchase intention is lower than a threshold. Such products can be called second-class products. Correspondingly, other products in the shopping cart besides the first-class products mentioned above can be called first-class products.

[0039] In practice, the operation to identify the second category of goods can be performed at any time. That is, as long as a user's shopping cart contains a product that meets the criteria, it can be identified as a second category product. Alternatively, if the number of products in a user's shopping cart is not large and will not affect the execution of new add-to-cart operations, the operation to identify the second category of goods may not be necessary. Therefore, to save resources, the number of products in the user's shopping cart can be judged first. If the shopping cart capacity limit has been reached or is about to be reached, then the step of identifying at least one product from the user's associated shopping cart that the user's current purchase intention is below a threshold can be triggered.

[0040] There are several ways to identify the second type of goods. For example, in one implementation, the time information of when a specific product is added to the user's shopping cart can be obtained. If the time a product has been added to the shopping cart reaches a first time threshold (e.g., one year, or other time length), the product can be identified as a product with a relatively low current purchase intention of the user and recorded as a second type of goods.

[0041] The above method judges a user's current purchase intention for a specific product solely based on the duration of time the product has been added to the cart. Therefore, the first duration threshold can be set relatively long to reduce the probability of misjudgment. Alternatively, other information can be combined for comprehensive judgment, such as whether the user performed any target actions on the product after adding it to the cart. In this case, the duration threshold can be set slightly shorter; for example, a second duration threshold can be set (if the first duration threshold is one year, the second duration threshold could be six months, etc.). Specifically, when identifying the second type of product, it can first be determined whether the duration of the product in the cart has reached the second duration threshold. If so, it can be further determined whether the user performed any target actions such as selecting or viewing details of the product after adding it to the cart. If no such actions were performed, the product can be identified as a product where the user's current purchase intention is below the threshold and recorded as a second type of product.

[0042] Furthermore, in practical implementation, a comprehensive judgment can be made based on factors such as whether the store to which the product belongs is one that the user frequently shops at, the user's purchase history for similar products, and whether the specific product belongs to a category with a high or low repurchase rate. For example, if a product added to the shopping cart has been removed from the shelves, it can still be classified as a second-category product. If a product belongs to a category with a low repurchase rate, including large home appliances, and the user has recently purchased another product from that category, the user's willingness to purchase other products from that category that are still in their shopping cart will generally be low, and so on.

[0043] Additionally, it's worth noting that in practical implementation, items in the shopping cart can be grouped for judgment. For example, when grouping by store, items in the same group can only be identified as second-category items if the add-to-cart duration of all items in that group exceeds a threshold. Furthermore, operation-based or type-based exclusions can be implemented. Operation-based exclusions can include excluding items that have undergone a target operation within a preset time period (e.g., 15 minutes), such as adjusting inventory structure, selecting items, switching SKUs (smallest SKU), editing quantities, or clicking to view details. Type-based exclusions can include excluding items belonging to specific business types, such as supermarket businesses, cross-border businesses, pharmaceutical businesses, fresh food businesses, travel businesses, and items with exchange or bundled purchase options, etc.

[0044] It should be noted that, in practice, expired products (e.g., products that have been removed from shelves) can also be treated as the second type of products mentioned above.

[0045] After identifying the second category of goods, a differentiated record can be created between it and the first category to highlight the distinction between the two categories in the shopping cart. Specifically, this differentiated record can be implemented in several ways. For example, one method involves separating the information for the second category of goods from the original data table and storing it in a dedicated data table for the second category, while the information for the first category can remain in the original data table. This allows for the storage of different categories of goods in different data tables, thus achieving differentiated recording between the first and second categories.

[0046] The above method can intuitively distinguish between two different categories of goods, but its drawback is that the management cost may be relatively high. New items may continuously be added to the shopping cart and become second-category items, and later, user actions may cause second-category items to revert to first-category items, etc. All of these processes involve modifying two different data tables. Therefore, in practical implementation, another method can be used. Specifically, in this method, a product category field can be added to the data table corresponding to the shopping cart. By default, when a product is added to the shopping cart, the data in the product category field for that product is in the first category. Subsequently, if a product in the shopping cart is identified as having a purchase intention below a threshold, the data in the product category field for that product can be changed to the second category. In this way, information on both first-category and second-category products can be recorded in the same data table, and the product category field can be used to differentiate between the two categories, reducing the operational costs when product categories change.

[0047] It should be noted that step S201 can be executed in real time or periodically. For example, it can be executed every day at midnight to clean recent operation records from the relevant database, process shopping cart information by user, and support retrying and monitoring alerts during the processing. Alternatively, it can be triggered by another program. For example, the aforementioned other program could be a program that detects the quantity of items in a specific user's shopping cart. If the program detects that the quantity of the first type of items in a user's shopping cart has reached or is about to reach the cart's capacity limit, then step S201 can be triggered.

[0048] S202: After receiving a request to display the information page corresponding to the object temporary storage set, for the first type of object, obtain information of at least one first field and at least one second field; for the second type of object, obtain information of the at least one first field, and provide the obtained information to the client for display; wherein, the first field includes fields related to object identification, and the second field includes fields related to transaction information.

[0049] In the scenario described above, where items in the shopping cart are categorized into two types, after a user requests to display the shopping cart page, the server can treat the first and second types of items differently when retrieving their data. For the first type of items, information on at least one first field and at least one second field can be retrieved from multiple different data sources. The first field can be related to product identification, such as product images, titles, prices (typically the base price set by the merchant when publishing the product), and store information. This information can come from data sources like product databases. The second field is related to transaction information, specifically fields related to logical calculations in the transaction scenario. For example, it can include information on available coupons and supported user benefits. This information may come from data sources like marketing databases to calculate the actual transaction price. Additionally, the server can calculate the discounted price of the specific product. In other words, the first type of items can be processed like ordinary items in the shopping cart.

[0050] For the second type of product, a simplified approach can be used. Specifically, the server can retrieve only the product information in the first field mentioned above from data sources such as the product database, including product image, product title, base price, and store information, without needing to retrieve the information in the second field. This way, the time overhead for data retrieval for the second type of product will be relatively low.

[0051] After obtaining the information on the first and second fields of the first category of goods, and the information on the first field of the second category of goods, this information can be returned to the client. The client can then display the information on the first and second categories of goods on the specific shopping cart information page. For the second category of goods, they can be displayed as non-tradeable, meaning users cannot purchase them on the shopping cart page, nor can they select them or combine them with other items in a single order. Additionally, for the first category of goods, besides the information on the first and second fields, functional options related to object comparison and / or object recommendation can be provided. However, for the second category of goods, these functional options are either not provided or displayed as inoperable. In this way, for the first category of goods, users can obtain their information on the first and second fields from the shopping cart page to help them make purchasing decisions; while for the second category of goods, users can view the specific information on the first field of the second category of goods from the shopping cart page. In other words, since it is predicted that the user's current willingness to purchase this type of product is relatively low, and the probability of the user purchasing this product is relatively low, it is only necessary to let the user know which specific product it is, without needing to display the information of the second field related to the transaction to the user.

[0052] Specifically, the client can display information about the first and second categories of goods in several ways. For example, one approach is to display them together, perhaps by showing the second category in gray. Another approach is to create separate areas on the shopping cart page, divided into a first and a second area. Information about the first category of goods can be displayed in the first area, while information about the second category can be displayed in the second area. Furthermore, the second area can be located below the first area. This allows for priority display of information about the first category of goods on the shopping cart page, and this information is concentrated in the first area, avoiding interference from information about the second category of goods.

[0053] For example, such as Figure 3As shown in (A), this is a schematic diagram of the shopping cart page provided in this application embodiment. Area 301 represents the second category of goods. A title bar can be provided at the beginning of this area, displaying prompts such as "To improve space, items added to the cart more than one year ago have been moved to the bottom." Then, information about the specific second category of goods can be displayed. By comparing this with the information about the first category of goods displayed above area 31, it can be seen that the first category of goods includes not only product images, product titles, prices, and store information, but also discounted price information and tags related to user benefits, such as "Official 15% Discount" and "Use Now, Pay Later." The second category of goods, however, only displays product images, titles, store information, and basic prices.

[0054] Furthermore, when displaying information about the second type of goods on the information page, a restore option can be provided for the second type of goods to restore them to the first type of goods. For example, the above operation option can be specifically as follows: Figure 3 As shown at point 32 in (A). Of course, Figure 3 (A) The progress bar displays information on some of the second category of goods. More information on the second category of goods can be displayed by swiping the page; for example, you can see... Figure 3 As shown in (B), each of the second category of goods can have its own corresponding recovery operation options. In addition, in practice, the title bar of the specific second area can be permanently displayed at the top.

[0055] In addition to performing recovery operations on individual products, the second area also provides a batch operation option, which leads to the batch operation interface. Users can select multiple or all products in this batch operation interface (which may appear as a pop-up on the shopping cart page, etc.) and then perform batch operations such as deletion, recovery, and moving to favorites.

[0056] For example, such as Figure 4 As shown in (A), this is a schematic diagram of a batch operation overlay in an application example. It can display a list of thumbnails for multiple second-category products, along with their corresponding checkboxes. A "select all" option can also be provided for selecting all second-category products. Additionally, the overlay can offer options such as "restore to cart," "move to favorites," and "delete." Users can select multiple second-category products through this overlay and then perform batch operations such as restoring, moving to favorites, or deleting them.

[0057] Furthermore, within the specific management interface, batch management and batch cleanup can be set up as separate tabs. When displaying the batch cleanup tab, specific second-category products can be further grouped and displayed. For example, the batch management tab can be as follows: Figure 4 As shown in (A). When the batch cleanup tab is selected, as... Figure 4 As shown in (B), the second category of goods can be divided into several different groups, such as expired goods, goods added to the cart six months ago, and goods added to the cart 30 days ago. This allows users to perform grouped selections and other operations on these goods. For example, they can select all goods added to the cart six months ago with a single click, and then use options such as "move to favorites" or "delete" to perform batch moves to favorites or batch deletions.

[0058] It should be noted that for products that need to be restored, if the first and second categories of products are stored in different data tables, the product can be deleted from the data table corresponding to the second category and added to the data table corresponding to the first category. If the first and second categories of products are stored in the same data table and are distinguished by the value in the specific type field, the value in the type field of the product can be changed from the second category to the first category, and so on.

[0059] Additionally, during the product restoration process, users can observe the corresponding changes on the front-end interface. For example, restored products may move from the area containing Category 2 products back to the area containing Category 1 products, and so on. Furthermore, in practical applications, there may be situations where insufficient shopping cart capacity prevents the restoration of some products. In such cases, a partial restoration strategy can be adopted, which prioritizes restoring some products and returns the IDs of the unrestored products to the client, prompting the user to clear the shopping cart before attempting to restore them again.

[0060] In summary, through the embodiments of this application, at least one item whose current purchase intention is below a threshold can be identified from the user's associated temporary shopping list as a second category of items, and this is differentiated from other items in the temporary shopping list that are in a normal state (first category of items). Upon receiving a request to display the information page corresponding to the temporary shopping list, for the first category of items, information on the basic and extended fields is obtained; for the second category of items, information on the basic fields is obtained, and the obtained information is provided to the client for display. In this way, since the number of items in the shopping cart is actually the sum of the number of items in the first and second categories, the shopping cart capacity is expanded. Simultaneously, since only a few basic fields of information need to be displayed for the second category of items, even if the sum of the number of items in the first and second categories exceeds the traditional shopping cart capacity limit, it will not cause excessively long page loading or refresh times. Furthermore, since users do not need to perform operations such as clearing the shopping cart, they can complete operations such as adding items to their cart with minimal burden, thereby improving the system's service capabilities and user experience.

[0061] Example 2 This second embodiment corresponds to the first embodiment and provides an information display method from the client's perspective. See [link / reference] Figure 5 The method may include: S501: Receive a request to display the information page corresponding to the temporary collection of objects associated with the target user.

[0062] S502: Obtain object information from the object temporary storage set. The object information includes information about a first type of object in at least one first field and at least one second field, and information about a second type of object in the at least one first field. The second type of object is at least one object identified from the object temporary storage set whose current purchase intention is below a threshold. The first field includes fields related to object identification, and the second field includes fields related to transaction information.

[0063] The product information in the aforementioned temporary collection of selected products can be obtained from the server, or it can be obtained from the local cache if the shopping cart information recently obtained from the server exists in the local cache of the client's terminal device.

[0064] S502: Display the object information in the object temporary storage set on the information page.

[0065] Specifically, when displaying object information in the object temporary collection on the information page, a first area and a second area can be created on the information page. The first area displays information about the first type of object, and the second area displays information about the second type of object. The first area is located above the second area.

[0066] Specifically, on the information page, the first type of object can be displayed as tradable, and the second type of object can be displayed as non-tradable.

[0067] In addition, the information page may provide functional options related to object comparison and / or object recommendation for the first type of object, while the second type of object may not have such functional options, or the functional options may be displayed as inoperable.

[0068] When displaying information about the second type of object on the information page, a restore operation option is provided for the second type of object. After receiving a restore operation request for one of the target objects through the operation option, the request can be submitted to the server to restore the target object to the first type of object, and the information of the target object in the extended field is retrieved and returned. Afterwards, the client can supplement the display of the target object's information in the extended field on the information page.

[0069] Additionally, the shopping cart information page can provide operation options for batch operations on the second type of objects. Upon receiving an operation request via these options, a batch operation interface can be displayed, allowing for batch operations on the second type of objects, including batch restore, batch move to favorites, and / or batch deletion.

[0070] Specifically, the batch operation interface can also provide batch management tag options and batch cleanup tag options; wherein, when the batch management tag option is selected, the batch operation interface displays thumbnails of the second type of objects, provides checkboxes for each object, and provides restore, move to favorites and / or delete operation options; when the batch cleanup tag option is selected, the thumbnails of the second type of objects can be grouped and displayed in the batch operation interface, providing checkboxes for each object, and providing a select all box for each group, so as to perform batch move to favorites and / or delete operations for the groups.

[0071] For the parts of Embodiment 2 that are not detailed above, please refer to Embodiment 1 above and other parts of this specification. They will not be repeated here.

[0072] 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.).

[0073] Corresponding to the aforementioned Embodiment 1, this application also provides an information processing apparatus, which may include: The object identification unit is used to identify at least one object from the object temporary storage set associated with the user whose current purchase intention is lower than a threshold as a second type of object, and to make a differential record with other first type objects in the object temporary storage set. An information providing unit is configured to, upon receiving a request to display an information page corresponding to the object temporary storage set, obtain information of at least one first field and at least one second field for the first type of object, and obtain information of the at least one first field for the second type of object, and provide the obtained information to the client for display; wherein, the first field includes fields related to object identification, and the second field includes fields related to transaction information.

[0074] The device may further include: The judgment unit is used to judge the number of objects in the object temporary storage set before identifying at least one object in the user's associated object temporary storage set where the user's current purchase intention is lower than the threshold. If the upper limit of the capacity of the object temporary storage set has been reached or is about to be reached, the process of identifying at least one object in the user's associated object temporary storage set where the user's current purchase intention is lower than the threshold is triggered.

[0075] Specifically, the object recognition unit can be used for: If an object is added to the object temporary storage set for a period of time that reaches a first duration threshold, then the object is identified as an object whose current purchase intention of the user is lower than the threshold.

[0076] Alternatively, the object recognition unit may be specifically used for: If an object has been added to the object temporary storage set for a period of time that reaches the second duration threshold, and the user has not performed any target operation on the object after it has been added to the object temporary storage set, then the object is identified as an object whose current purchase intention is lower than the threshold.

[0077] Additionally, an object category field can be added to the data table corresponding to the object temporary storage set. In the default state after an object is added to the object temporary storage set, the data in the object category field is of the first category. At this time, when an object in the object temporary storage set is identified as an object whose current purchase intention is lower than the threshold, the data in the object category field of the object in the data table can be modified to the second category.

[0078] Alternatively, the information of the second type of object can be separated from the original data table and saved to a dedicated data table for the second type of object, while the first type of object remains in the original data table.

[0079] Specifically, when displaying the information page, the client can show the second type of object as non-tradable.

[0080] When the client displays information about the second type of object on the information page, it provides a restore option for the second type of object so as to restore the second type of object to the first type of object.

[0081] Corresponding to Embodiment 2, this application also provides an information display device, which may include: The request receiving unit is used to receive requests to display information pages corresponding to the temporary collection of objects associated with the target user; An information acquisition unit is used to acquire object information in the object temporary storage set. The object information includes information of a first type of object in at least one first field and at least one second field, and information of a second type of object in the at least one first field. The second type of object is at least one object identified from the object temporary storage set whose current purchase intention is below a threshold. The first field includes fields related to object identification, and the second field includes fields related to transaction information. An information display unit is used to display object information in the object temporary storage set on the information page.

[0082] Specifically, the information display unit can be used for: A first area and a second area are created on the information page. The first area displays information about the first type of object, and the second area displays information about the second type of object. The second area is located below the first area.

[0083] In the information page, the first type of object is displayed as tradable, and the second type of object is displayed as non-tradable.

[0084] In addition, the information page may provide the first type of object with functional options related to object comparison and / or object recommendation, but the second type of object does not have the functional options, or the functional options are displayed as inoperable.

[0085] Additionally, the device may also include: A recovery operation option providing unit is used to provide recovery operation options for the second type of object when the information of the second type of object is displayed on the information page; The recovery request submission unit is used to receive a recovery operation request for one of the target objects through the operation options, submit the request to the server so as to restore the target object to the first type of object, and return the information of the target object in the extended field. A supplementary display unit is used to supplement the information of the target object on the extended field in the information page.

[0086] Furthermore, it may also include: A batch operation option providing unit is used to provide operation options for performing batch operations on the second type of objects in the information page; A batch operation interface display unit is used to display a batch operation interface after receiving an operation request through the operation options, so that batch operations can be performed on the second type of objects through the batch operation interface. The batch operations include batch recovery, batch moving to favorites and / or batch deletion.

[0087] The batch operation interface can provide options for batch management of tags and batch clearing of tags. When the batch management tab option is selected, thumbnails of the second type of objects are displayed in the batch operation interface, checkboxes are provided for each object, and options for restore, move to favorites and / or delete are provided. When the batch cleanup tag option is selected, the thumbnails of the second type of objects are displayed in groups in the batch operation interface. Checkboxes are provided for each object, and a full selection box is provided for each group to facilitate batch moving of groups into favorites and / or deletion.

[0088] 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.

[0089] And an electronic device, comprising: One or more processors; and 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.

[0090] A computer program product includes a computer program / computer executable instructions that, when executed by a processor in an electronic device, implement the steps of the method described in the foregoing method embodiments.

[0091] in, Figure 6 An exemplary architecture of an electronic device is shown, which may include a processor 610, a video display adapter 611, a disk drive 612, an input / output interface 613, a network interface 614, and a memory 620. The processor 610, video display adapter 611, disk drive 612, input / output interface 613, network interface 614, and memory 620 can communicate with each other via a communication bus 630.

[0092] The processor 610 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to achieve the technical solution provided in this application.

[0093] The memory 620 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 620 can store the operating system 621 for controlling the operation of the electronic device 600, and the basic input / output system (BIOS) for controlling the low-level operations of the electronic device 600. Additionally, it can store a web browser 623, a data storage management system 624, and an icon font processing system 625, etc. The aforementioned icon font processing system 625 can be the application program that specifically implements the aforementioned steps in this embodiment. In summary, when implementing the technical solution provided in this application through software or firmware, the relevant program code is stored in the memory 620 and executed by the processor 610.

[0094] Input / output interface 613 is used to connect input / output modules to realize information input and output. Input / output modules can be configured as components in the device (not shown in the figure) or externally connected to the device to provide corresponding functions. Input devices may include keyboards, mice, touch screens, microphones, various sensors, etc., and output devices may include displays, speakers, vibrators, indicator lights, etc.

[0095] Network interface 614 is used to connect a communication module (not shown in the figure) to enable communication between this device and other devices. The communication module can communicate via wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).

[0096] Bus 630 includes a pathway for transmitting information between various components of the device, such as processor 610, video display adapter 611, disk drive 612, input / output interface 613, network interface 614, and memory 620.

[0097] It should be noted that although the above-described device only shows the processor 610, video display adapter 611, disk drive 612, input / output interface 613, network interface 614, memory 620, bus 630, etc., in specific implementations, the device may also include other components necessary for normal operation. Furthermore, those skilled in the art will understand that the above-described device may only include the components necessary for implementing the solution of this application, and does not necessarily include all the components shown in the figures.

[0098] 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.

[0099] 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.

[0100] The information processing, display methods, and electronic devices 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 embodiments above are only for the purpose of helping to understand the methods and core ideas of this application. 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. An information processing method characterized by comprising: include: Identify at least one object from the temporary object storage set associated with the user whose current purchase intention is below a threshold as a second type of object, and record it differently from other first type objects in the temporary object storage set; Upon receiving a request to display the information page corresponding to the object temporary storage set, for the first type of object, information of at least one first field and at least one second field is obtained; for the second type of object, information of the at least one first field is obtained, and the obtained information is provided to the client for display; wherein, the first field includes fields related to object identification, and the second field includes fields related to transaction information.

2. The method according to claim 1, characterized in that, Before identifying at least one object from the temporary object storage set associated with the user whose current purchase intention is below a threshold, the method further includes: The number of objects in the object temporary storage set is determined. If the maximum capacity of the object temporary storage set has been reached or is about to be reached, the process of identifying at least one object in the user's associated object temporary storage set whose current purchase intention is below a threshold is triggered.

3. The method according to claim 1, characterized in that, The step of identifying at least one object from the temporary object storage set associated with the user whose current purchase intention is below a threshold includes: If an object is added to the object temporary storage set for a period of time that reaches a first duration threshold, then the object is identified as an object whose current purchase intention of the user is lower than the threshold.

4. The method according to claim 1, characterized in that, The second type of object is identified from the temporary object storage set associated with the user, where at least one object whose current purchase intention is below a threshold is identified as such, including: If an object has been added to the object temporary storage set for a period of time that reaches the second duration threshold, and the user has not performed any target operation on the object after it has been added to the object temporary storage set, then the object is identified as an object whose current purchase intention is lower than the threshold.

5. The method of claim 1, wherein, Also includes: Add an object category field to the data table corresponding to the object temporary storage set; in the default state after an object is added to the object temporary storage set, the data in the object category field is of the first category; The process of differentiating the first type of objects from other normal objects in the object temporary storage set includes: When an object in the object temporary storage set is identified as an object whose current purchase intention is below a threshold, the data of that object in the object category field of the data table is modified to the second category.

6. The method according to claim 1, characterized in that, The process of differentiating the first type of objects from other normal objects in the object temporary storage set includes: The information of the second type of object is separated from the original data table and saved to a dedicated data table for the second type of object, while the first type of object is retained in the original data table.

7. The method according to any one of claims 1 to 6, characterized in that, When displaying the information page, the client shows the second type of object as non-tradable.

8. The method according to any one of claims 1 to 6, characterized in that, When the client displays information about the second type of object on the information page, it provides a restore option for the second type of object so that the second type of object can be restored to the first type of object.

9. An information presentation method, characterized by, include: Receive a request to display the information page corresponding to the temporary collection of objects associated with the target user; Obtain object information from the object temporary storage set. The object information includes information about a first type of object in at least one first field and at least one second field, and information about a second type of object in the at least one first field. The second type of object is at least one object identified from the object temporary storage set whose current purchase intention is below a threshold. The first field includes fields related to object identification, and the second field includes fields related to transaction information. The information page displays object information in the object temporary collection.

10. The method according to claim 9, characterized in that, The display of object information in the object temporary storage set on the information page includes: A first area and a second area are created on the information page. The first area displays information about the first type of object, and the second area displays information about the second type of object. The second area is located below the first area.

11. The method according to claim 9, characterized in that, On the information page, the first type of object is displayed as tradable, and the second type of object is displayed as non-tradable.

12. The method of claim 9, wherein, Also includes: The information page also provides functional options related to object comparison and / or object recommendation for the first type of object, while the second type of object does not have the functional options, or the functional options are displayed as inoperable.

13. The method of claim 9, wherein, Also includes: When displaying information about the second type of object on the information page, a recovery operation option is provided for the second type of object; After receiving a recovery operation request for one of the target objects through the operation options, the request is submitted to the server so that the target object can be restored to the first type of object, and the information of the target object on the extended field is obtained and returned. The information page will supplement the information of the target object on the extended field.

14. The method of claim 9, wherein, Also includes: The information page provides operation options for performing batch operations on the second type of objects; After receiving an operation request through the operation options, a batch operation interface is displayed so that batch operations can be performed on the second type of objects through the batch operation interface. The batch operations include batch recovery, batch moving to favorites and / or batch deletion.

15. The method according to claim 14, characterized in that, The batch operation interface provides options for batch management of tags and batch clearing of tags; When the batch management tab option is selected, thumbnails of the second type of objects are displayed in the batch operation interface, checkboxes are provided for each object, and options for restore, move to favorites and / or delete are provided. When the batch cleanup tag option is selected, the thumbnails of the second type of objects are displayed in groups in the batch operation interface. Checkboxes are provided for each object, and a full selection box is provided for each group to facilitate batch moving of groups into favorites and / or deletion.

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

17. An electronic device, comprising: 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 15.

18. A computer program product comprising computer program / computer executable instructions, characterized in that, When the computer program / computer-executable instructions are executed by a processor in an electronic device, they implement the steps of the method according to any one of claims 1 to 15.