Object management method and apparatus, electronic device, and readable medium

By creating object combinations on the management page of the target entity, the main object combinations are automatically inherited to each child entity, which solves the problem of low management efficiency of chain entity child objects and achieves more efficient batch processing and management.

WO2025161513A1PCT designated stage Publication Date: 2025-08-07BEIJING YOUZHUJU NETWORK TECH CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/126406
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-01-31
Filing Date
2024-10-22
Publication Date
2025-08-07

AI Technical Summary

Technical Problem

In the instant retail scenario, the sub-entity management of chain entities is inefficient and prone to omissions or errors. The existing technology requires staff to manually operate sub-object management one by one.

Method used

Provides an object management method, by creating object combinations on the management page of the target entity, automatically inheriting the main object combinations to the management page of each child entity, and implementing batch processing of sub-object management.

Benefits of technology

Improve the efficiency of chain entity sub-object management, save manpower and material resources, reduce errors, and achieve smarter management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024126406_07082025_PF_FP_ABST
    Figure CN2024126406_07082025_PF_FP_ABST
Patent Text Reader

Abstract

Discloses in the present disclosure are an object management method and apparatus, an electronic device, and a readable medium. The method comprises: in response to creating a first object combination on a management page of a target entity, obtaining at least two main objects comprised in the first object combination, wherein the at least two main objects belong to the target entity; in each sub-entity of the target entity, obtaining a target sub-object corresponding to each main object among the at least two main objects, wherein the attribute information of the target sub-object is the same as that of the corresponding main object; for a first sub-entity among the sub-entities of the target entity which comprises at least two target sub-objects, displaying a second object combination on a management page of the first sub-entity, wherein the second object combination comprises at least two target sub-objects.
Need to check novelty before this filing date? Find Prior Art

Description

Object management method, device, electronic device and readable medium

[0001] This application claims priority to Chinese Patent Application No. 202410139333.6 filed on January 31, 2024, and the contents of the above-mentioned Chinese patent application disclosure are hereby incorporated by reference in their entirety as a part of this application. Technical Field

[0002] The present disclosure relates to an object management method, an apparatus, an electronic device, and a readable medium. Background Art

[0003] Instant retail is a high-efficiency home consumption format based on an instant delivery system. It is a common new retail format and new consumption model. Its main characteristics are: consumers place orders on online trading platforms, offline physical retailers accept orders, pick and pack the goods, and then deliver them to the address specified by the consumer, completing the order in about 30 to 60 minutes.

[0004] With the development of instant retail, many chain entities (such as chain merchants) have settled in the online trading platform of instant retail. Chain entities usually have many sub-entities (such as stores). The main object of the chain entity's headquarters will correspond to different sub-objects in different sub-entities. It is urgent to provide the staff of the chain enterprise with a technical solution for managing sub-objects in a large number of sub-entities, so as to achieve faster and more convenient management of sub-objects in the many sub-entities included in the target entity.

[0005] Summary of the Invention

[0006] The present disclosure provides an object management method, comprising:

[0007] In response to creating a first object combination on a management page of a target entity, obtaining at least two main objects included in the first object combination, where the at least two main objects belong to the target entity;

[0008] In each sub-entity of the target entity, a target sub-object corresponding to each main object of the at least two main objects is obtained, wherein the target sub-object has the same attribute information as the corresponding main object;

[0009] For a first sub-entity including at least two target sub-objects among the sub-entities of the target entity, a second object combination is displayed on the management page of the first sub-entity, where the second object combination includes the at least two target sub-objects.

[0010] In a possible implementation, the third object combination of the target entity includes a first main object and a second main object, the second sub-entity of the target entity includes only a first target sub-object corresponding to the first main object, and the method further includes:

[0011] In response to the second target sub-object corresponding to the second main object in the second sub-entity being set to the first state and a synchronization operation being performed on the third object combination, the third object combination is associated on the management page of the second sub-entity to obtain a fourth object combination, and the fourth object combination is displayed on the display page of the second sub-entity. The fourth object combination includes the first target sub-object and the second target sub-object, and the sub-object in the first state is a sub-object for display on the display page of the second sub-entity.

[0012] In a possible implementation, the method further includes:

[0013] In response to updating the first object combination on the management page of the target entity, displaying an updated second object combination on the management page of the first child entity, the updated second object combination corresponding to the update of the first object combination;

[0014] In response to performing a first operation on the first object combination on the management page of the target entity, modifying the first state of the second object combination to a second state on the management page of the first child entity, where the object combination in the second state is an object combination for hiding or deleting on the display page of the first child entity;

[0015] In response to deleting the first object combination on the management page of the target entity, deleting the second object combination on the management page of the first child entity.

[0016] In a possible implementation, the method further includes:

[0017] In response to performing a synchronization operation on the first object combination on the management page of the target entity, displaying the second object combination on the presentation page of the first child entity;

[0018] or,

[0019] In response to performing a second operation on the second object combination on the management page of the first sub-entity, the second object combination is displayed on the presentation page of the first sub-entity.

[0020] In a possible implementation, the method further includes:

[0021] In response to creating a shared content component to be displayed on a management page of the target entity and selecting a main object set to be displayed, obtaining a sub-object set corresponding to the main object set in each sub-entity of the target entity, the main object set including at least one main object, and the sub-objects included in the sub-object set corresponding one-to-one to the main objects included in the main object set;

[0022] For each of the sub-entities of the target entity, the shared content component is displayed in each sub-object included in the sub-object set.

[0023] In a possible implementation, for each of the sub-entities of the target entity, displaying the shared content component in each sub-object included in the sub-object set includes:

[0024] If the shared content component is configured with a display time, then for each of the sub-entities of the target entity, the shared content component is displayed in each sub-object included in the sub-object set according to the display time.

[0025] In a possible implementation, the method further includes:

[0026] In response to an upload operation of a material image of a third main object on a material image management tool of the target entity, obtaining a first material image of the third main object, the material image management tool being used to display a status of material image uploads of each main object in the target entity;

[0027] If the first material graph passes the review, the first material graph is applied to the sub-object corresponding to the third main object for each of the sub-entities of the target entity.

[0028] The present disclosure also provides an object management device, comprising:

[0029] a first obtaining unit, configured to, in response to creating a first object combination on a management page of a target entity, obtain at least two main objects included in the first object combination, where the at least two main objects belong to the target entity;

[0030] A second obtaining unit is configured to obtain, from each sub-entity of the target entity, a target sub-object corresponding to each of the at least two main objects, wherein the target sub-object has the same attribute information as the corresponding main object;

[0031] The first display unit is configured to display, on a management page of a first sub-entity including at least two target sub-objects among the sub-entities of the target entity, a second object combination including the at least two target sub-objects.

[0032] In a possible implementation, the third object combination of the target entity includes a first main object and a second main object, the second sub-entity of the target entity includes only a first target sub-object corresponding to the first main object, and the apparatus further includes:

[0033] An association display unit is used to respond to the second target sub-object corresponding to the second main object in the second sub-entity being set to the first state and performing a synchronization operation on the third object combination, associate the third object combination on the management page of the second sub-entity to obtain a fourth object combination, and display the fourth object combination on the display page of the second sub-entity, wherein the fourth object combination includes the first target sub-object and the second target sub-object, and the sub-object in the first state is a sub-object for display on the display page of the second sub-entity.

[0034] In a possible implementation, the apparatus further includes:

[0035] an updating unit, configured to, in response to updating the first object combination on the management page of the target entity, display an updated second object combination on the management page of the first child entity, wherein the updated second object combination corresponds to the update of the first object combination;

[0036] In response to performing a first operation on the first object combination on the management page of the target entity, modifying the first state of the second object combination to a second state on the management page of the first child entity, where the object combination in the second state is an object combination for hiding or deleting on the display page of the first child entity;

[0037] A deleting unit is configured to delete the second object combination on the management page of the first child entity in response to deleting the first object combination on the management page of the target entity.

[0038] In a possible implementation, the apparatus further includes:

[0039] a second display unit, configured to display the second object combination on the display page of the first sub-entity in response to performing a synchronization operation on the first object combination on the management page of the target entity;

[0040] or,

[0041] The second display unit is configured to display the second object combination on the display page of the first sub-entity in response to a second operation being performed on the second object combination on the management page of the first sub-entity.

[0042] In a possible implementation, the apparatus further includes:

[0043] a third obtaining unit configured to, in response to creating a shared content component to be displayed on the management page of the target entity and selecting a primary object set to be displayed, obtain, from each sub-entity of the target entity, a child object set corresponding to the primary object set, the primary object set including at least one primary object, and the child objects included in the child object set corresponding one-to-one to the primary objects included in the primary object set;

[0044] The third display unit is configured to display the shared content component in each sub-object included in the sub-object set for each sub-entity of the target entity.

[0045] In a possible implementation, the third display unit is specifically configured to:

[0046] If the shared content component is configured with a display time, then for each of the sub-entities of the target entity, the shared content component is displayed in each sub-object included in the sub-object set according to the display time.

[0047] In a possible implementation, the apparatus further includes:

[0048] a fourth obtaining unit, configured to obtain a first material image of the third main object in response to an upload operation of the material image of the third main object on a material image management tool of the target entity, wherein the material image management tool is configured to display the uploaded material image status of each main object in the target entity;

[0049] The fourth display unit is configured to apply the first material graph to a sub-object corresponding to a third main object for each of the sub-entities of the target entity if the first material graph passes the review.

[0050] It should be noted that the specific implementation method of the device and the technical effects achieved can be found in the relevant description of the method provided in any of the above implementation methods.

[0051] The present disclosure also provides an electronic device, the electronic device comprising: a processor and a memory;

[0052] The memory is used to store instructions or programs;

[0053] The processor is configured to execute the instructions or programs in the memory so that the electronic device executes the method provided in any one of the above implementations.

[0054] The present disclosure also provides a readable medium, in which instructions or programs are stored. When the instructions or programs are executed on a processor, the processor executes the method provided in any one of the above implementations. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments recorded in the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0056] FIG1 is a flow chart of an object management method provided by an embodiment of the present disclosure;

[0057] FIG2 is a schematic diagram of an object combination inheritance of a main object to a child entity provided by an embodiment of the present disclosure;

[0058] FIG3 is a schematic diagram of a batch application of a shared content component provided by an embodiment of the present disclosure;

[0059] FIG4 is a schematic diagram of a batch application for uploading white background images provided by an embodiment of the present disclosure;

[0060] FIG5 is a schematic structural diagram of an object management device 500 provided in an embodiment of the present disclosure; and

[0061] FIG6 is a schematic structural diagram of an electronic device 600 provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0062] With the development of instant retail, many chain entities have entered the online trading platform. Chain entities can be, for example, supermarkets, pharmaceutical companies or clothing companies. Chain entities have multiple sub-entities. For example, supermarket company A has store a1, store a2 and store a3. The online trading platform can refer to an e-commerce trading platform that can be visited by consumers to purchase goods or services. Consumers can view, purchase and other operations on the objects sold in the sub-entities under the chain entity on the online trading platform. For example, when supermarket A enters online trading platform B, supermarket company A has store a1, store a2 and store a3, then consumers can view and purchase goods sold in store a1, store a2 or store a3 through online trading platform B.

[0063] For a chain entity, the chain entity may include at least a headquarters and stores. Optionally, the chain entity may also include a management unit store, which is used to manage some stores. The management authority of the management unit store is controlled by the headquarters, and the authority of the store is jointly controlled by the headquarters and the management unit store, and the control priority of the headquarters is higher. For example, supermarket enterprise A includes headquarters 1, management unit store 1, management unit store 2, store 1, store 2, store 3, store 4 and store 5, among which store 1 and store 5 are both managed by headquarters 1 and management unit store 1, and store 2, store 3 and store 4 are managed by headquarters 1 and management unit store 2. In the embodiment of the present disclosure, an entity may refer to the headquarters or management unit store of a chain enterprise, and a sub-entity may refer to a store of the chain enterprise.

[0064] In a chain entity, the objects included in the entity are recorded as main objects, and the objects in the child entities are recorded as child objects. A child object corresponds to a main object in the entity, and the attribute information of the corresponding main object and child object is the same. The difference is that since the main object in the entity does not need to be displayed and sold to consumers, the main object does not need to have the two attributes of price and inventory. However, the child object needs to be displayed and sold to consumers. Therefore, in addition to the attribute information included in the main object (such as product name, product image, product shelf life, etc.), the child object also needs to include inventory and price. Assuming that the attribute information of main object 1 in entity A is attribute information 1, the attribute information of sub-object 1 corresponding to main object 1 in a sub-object a of entity A may include: attribute information 1, price = x, inventory = y.

[0065] It should be noted that the main object of an entity may have corresponding sub-objects in each sub-entity, or may have corresponding sub-objects in some sub-entities. The sub-objects included in the sub-entity may completely correspond to the main object included in the entity, or the sub-objects included in the sub-entity may partially correspond to the main object included in the entity. For example, the headquarters of supermarket enterprise A has main product 1, main product 2 and main product 3, and supermarket enterprise A includes store 1, store 2 and store 3. Main product 1 is distributed to store 1, store 2 and store 3, so that store 1 has sub-product 11, store 2 has sub-product 21, and store 3 has sub-product 31; main product 2 is distributed to store 2 and store 3, so that store 2 has sub-product 22, and store 3 has sub-product 32; main product 3 is distributed to store 1 and store 2, so that store 1 has sub-product 13, and store 2 has sub-product 23. In this way, main product 1 has a corresponding sub-object in each store, main products 2 and main products 3 have corresponding sub-products only in some stores, and only the sub-objects in store 2 completely correspond to the main objects of the headquarters of supermarket company A, with three in each store. The sub-objects in the other two stores only partially correspond to the main objects of the headquarters of supermarket company A.

[0066] In the instant retail scenario, more and more large-scale chain entities (i.e., including many sub-entities) are entering the online consumption platform. Currently, the management of sub-objects in the sub-entities still requires the staff of the chain entities to perform manual operations one by one. This is not only inefficient, but also prone to omissions or errors, which is not friendly to chain enterprises.

[0067] Based on this, an embodiment of the present disclosure provides an object management method, in which a function of creating an object combination of a main object is provided on the management page of the target entity. When a first object combination is created in the target entity with the help of this function, the user can see a second object combination inherited from the first object combination on the management page of the target sub-entity belonging to the target entity. In specific implementation, the method may include: in response to creating a first object combination on the management page of the target entity, obtaining at least two main objects included in the first object combination, and the at least two main objects belong to the target entity; in each sub-entity of the target entity, obtaining a target sub-object corresponding to each of the at least two main objects, and the target sub-object has the same attribute information as the corresponding main object; for a first sub-entity including at least two of the target sub-objects in each sub-entity of the target entity, displaying a second object combination on the management page of the first sub-entity, and the second object combination includes at least two target sub-objects.

[0068] In this way, through this method, the object combination of the main object created on the chain entity can be automatically inherited to the sub-entities of the chain entity, and the object combination of the sub-objects corresponding to the object combination of the main object created by the chain entity can be automatically obtained on the management page of each sub-entity. There is no need for staff to manually configure the corresponding object combination of sub-objects one by one on the numerous sub-entities of the chain enterprise according to the object combination of the main object, which saves a lot of manpower, material resources and time costs, improves the management efficiency of the sub-objects included in the sub-entities in the chain entity, and makes the management of chain entities in instant retail scenarios more intelligent.

[0069] In addition, the disclosed embodiments also provide object management tools with other functions, each of which can implement batch processing of corresponding functions on objects in chain entities. The aforementioned tools for object combination and inheritance can be understood as tools for implementing batch collocation. Other object management tools may also include, but are not limited to, tools for batch synchronization of shared content components or tools for batch uploading of source images.

[0070] It should be noted that the subject implementing the object management method may be the object management device provided in the embodiments of the present disclosure. The object management device may be hosted in an electronic device or a functional module of the electronic device. For example, the object management device may be a functional module implementing the object management function provided in the embodiments of the present disclosure on a work website provided by an online consumption platform to staff of a chain entity, or on a server corresponding to the work website.

[0071] It should be noted that, in the embodiment of the present disclosure, online can be understood as the main object or sub-object being in the first state, and the sub-object in the first state can be displayed to consumers through the display page of the sub-entity to which the sub-object belongs; offline can be understood as the main object or sub-object being in the second state, and the sub-object in the second state is not displayed on the display page of the sub-entity to which the sub-object belongs, and is hidden or deleted.

[0072] Figure 1 is a flow chart of a batch object management method provided by an embodiment of the present disclosure. The method can be applied to an object management device, such as the object management device 500 shown in Figure 5 below.

[0073] As shown in FIG1 , the method may include, for example, the following S101 to S103:

[0074] S101: In response to creating a first object combination on a management page of a target entity, obtaining at least two main objects included in the first object combination, where the at least two main objects belong to the target entity.

[0075] The target entity may refer to the headquarters or any first-level management unit store of any chain enterprise that is stationed on the online consumption platform in the instant retail scenario. The staff of the target entity may log in to the work website provided to the staff of the target entity on the consumption platform through the account-password or account-verification code, and manage and configure the target entity through operations on the management page of the work website, wherein the management and configuration of the target entity includes the process of "creating" the first object combination mentioned in S101. Since the stores of the chain enterprise do not support the authority to independently create object combinations, the target entity cannot be a store. If the management unit store of the chain enterprise has the authority to independently publish goods, it can be considered that the management unit store has the authority to create object combinations, then the target entity can also be the management unit store, but once the management unit store does not have the authority to independently publish goods, the main object in the management unit store will be removed from the shelves, then the object combination created by the management unit store will also be removed from the shelves simultaneously.

[0076] The first object combination can refer to any combination of the main objects included in the target entity. The first object combination can include at least two main objects in the target entity. For example, if the target entity is supermarket enterprise A, and supermarket enterprise A includes main products A1, A2, ..., A100, then the first object combination can be a combination of at least two of A1, A2, ..., A100. For example, the first object combination can be A1+A3+A100, or A2+A30, or A5+A33+A89+A100.

[0077] The user may create the first object combination on the management page of the target entity manually or automatically.

[0078] For example, a target entity's management page has an action item corresponding to the automatic matching function. By clicking on this action item, a staff member can trigger the management page's backend to automatically match objects for the target entity, generating at least one first object combination. This allows the target entity's staff member to simply click on the management page, and the page automatically generates the first object combination for the target entity, greatly facilitating the target entity's staff member.

[0079] For example, for a target entity's main object, if its main object image or detail image includes other main objects within the target entity, the functional module implementing the automatic matching function on the management page can match the main objects based on the image that includes at least two main objects. In this example, the process of creating a first object combination may include: determining a matching main image from the images of the target entity's main objects, where the matching main image includes at least two main objects; and defining the at least two main objects in the matching main image as a first object combination. The first object combination generated in this example can be referred to as an object combination with a main image. The first object combination may include a matching main image, object identifiers for each main object in the matching main image, anchor points corresponding to each main object in the matching main image, and a first matching identifier. In this example, the core of the functional module implementing the automatic matching function is an image recognition algorithm. The principle of the image recognition algorithm can be understood as: searching for a matching main image from the target entity's main object, searching for other main objects included in the matching main image, marking the found main objects in the matching main image, and anchoring them at the corresponding locations.

[0080] For another example, if, among the main objects of a target entity, the main object image or the detail image of a certain main object do not include other main objects in the target entity, the functional module implementing the automatic matching function on the management page can match the main objects based on an association algorithm. In this example, the process of creating a first object combination may include: dividing the main objects included in the target entity into different categories; combining the main objects belonging to the first category with the main objects belonging to the second category to obtain candidate object combinations, where the first category and the second category belong to a preset category mapping relationship; and determining at least one first object combination from the candidate object combinations. The first object combination generated in this example can be referred to as a "no main image" object combination. The first object combination can include the object identifiers of each main object and a first matching identifier. The association algorithm can pre-set category mapping relationships. Multiple categories with category mapping relationships have strong correlations. For example, shirts, trousers, and leather shoes can be included in one category mapping relationship, while T-shirts and skirts can be included in another category mapping relationship. However, vests and cotton shoes would not be maintained in the same category mapping relationship.

[0081] As another example, on the target entity's management page, staff can manually enter at least one pre-defined object combination based on their own experience or sales data for each object. For example, the target entity's management page has an "Object Combination" function. Staff can enter the editing page through "Create New Object Combination" and create a combination by uploading a main combination image, adding products, and other operations. Once the combination passes review, it is considered a first object combination.

[0082] For example, manually creating a first object combination without a main image may include the following steps: S11, selecting at least two main objects from the target entity; S12, setting a name and recommendation for the combination; optionally, setting a discount for the combination; if no discount is set, the default setting is no discount; S13, clicking "Finish Creation" to obtain the first object combination; clicking "Previous Step" to return to modify or reselect the main object; clicking "Cancel" to exit the process of creating the first object combination. The combination name can have a preset character limit of, for example, 10 characters; the recommendation can also have a preset character limit of, for example, 40 characters.

[0083] For another example, for manually creating a first object combination with a main image, the process may include: S21, uploading a matching image, which includes at least two main objects; S22, selecting the main object corresponding to the matching image in the target entity; S23, selecting the pointing position of the main object selected in S22 on the matching image, and configuring the anchor name; S24, setting the name and recommendation of the combination, and optionally, setting a discount for the combination. If no discount is set for the combination, it can be defaulted to no discount; S25, clicking "Finish creation" to obtain the first object combination, clicking "Previous step" can return to modify or reselect the main object, and clicking "Cancel" will exit the process of creating the first object combination. Among them, the matching image can be a 1:1 image, and after uploading, the effect can be previewed in a part of the creation page (such as the left side).

[0084] In the two manual creation processes for the first object combination, you can set a character limit for the combination name, such as 10 characters; the character limit for the recommendation can also be set, such as 40 characters. After setting the combination name and recommendation, you can preview the effect in the section of the creation page (such as the left side).

[0085] It can be understood that an anchor point refers to a mark that can link to the object details page of an object. For example, when there is no operation on a certain anchor point, the anchor point can be displayed as a dot; when the staff moves the cursor to the preset area where the anchor point is located, relevant information of the object corresponding to the anchor point can be displayed near the anchor point, such as product name, price, etc.; when the staff clicks the anchor point, the display page can jump to the object details page of the object corresponding to the anchor point.

[0086] Assuming that the first object combination includes a first primary object and a second primary object within the target entity, S101 may, for example, include: in response to creating the first object combination on the management page of the target entity, obtaining relevant information about the first primary object and relevant information about the second primary object. The relevant information about the first primary object may include at least an object identifier of the first primary object, and the relevant information about the second primary object may include at least an object identifier of the second primary object. The object identifier may be, for example, information that uniquely identifies the object, such as the object's name, serial number, or ID.

[0087] It should be noted that only main objects belonging to the same target entity can create the first object combination, and main objects belonging to different entities cannot be combined to create the first object combination.

[0088] It should be noted that an upper limit on the number of first object combinations can be set for the target entity, such as 500. Then, the number of first object combinations created in the target entity cannot exceed 500. If 500 first object combinations already exist in the target entity, then when a new first object combination is created on the management page of the target entity, the creation of the new first object combination will fail because the number of first object combinations in the target entity exceeds the upper limit.

[0089] It should be noted that, when the number of primary objects in the shelf state in the first object combination is less than 2, it can be considered that the creation of the first object combination has failed, or the created first object combination is automatically offline.

[0090] It should be noted that, in order to provide a safer and healthier environment for online consumption platforms, after the first object combination is created, the images, text, and other contents in the first object combination may be subject to compliance review. If the review passes, the following steps S102 to S103 may be triggered to automatically create an object combination of sub-objects in the sub-entities of the target entity.

[0091] S102: Obtain a target sub-object corresponding to each of at least two main objects in each sub-entity of the target entity, wherein the target sub-object has the same attribute information as the corresponding main object.

[0092] The sub-entities of the target entity can refer to several subordinate entities of the target entity. For example, if the target entity is the headquarters of chain enterprise A, the sub-entities of the target entity are any store belonging to chain enterprise A; or if the target entity is any management unit store a of chain enterprise A, the sub-entities of the target entity are several stores belonging to management unit store a of chain enterprise A.

[0093] The objects within a sub-entity are called sub-objects within that sub-entity. The "master" and "sub-object" before an object are names defined to distinguish the entity level at which the object resides. Master objects only exist within entities, and sub-objects only exist within sub-entities. Master objects cannot be displayed or sold to consumers, but sub-objects can be displayed and sold to consumers. For example, if chain enterprise A is the target entity, its headquarters includes ten different types of milk: milk 1 to milk 10. Milk 1 to milk 10 can be understood as the 10 master objects of the target entity; if milk 1 to milk 8 are sold to store 1 of chain enterprise A, and store 1 is a sub-entity of the target entity, then milk 1 to milk 8 can be understood as the 8 sub-objects of the sub-entity.

[0094] As an example, S102 may include: for each main object in the first object combination, obtaining a sub-object corresponding to the main object from the sub-entity of the target entity, denoted as a target sub-object. Assuming that the first object combination includes a first main object and a second main object, and the target entity includes sub-entity 1 and sub-entity 2, then S102 may include: in sub-entity 1, obtaining sub-object 11 corresponding to the first main object, and obtaining sub-object 12 corresponding to the second main object; in sub-entity 2, obtaining sub-object 21 corresponding to the first main object, and obtaining sub-object 22 corresponding to the second main object. If the target entity also includes sub-entity 3, and sub-object 32 corresponding to the second main object in sub-entity 3 is not available, then S102 may include: in sub-entity 3, obtaining sub-object 31 corresponding to the first main object. The target sub-objects obtained in sub-entity 1 include sub-objects 11 and 12, the target sub-objects obtained in sub-entity 2 include sub-objects 21 and 22, and the target sub-objects obtained in sub-entity 3 include only sub-object 31.

[0095] It can be seen that the execution of S102 prepares for the object combination of the main object to be inherited to the child object in S103 to obtain the object combination of the child object.

[0096] S103 : For a first sub-entity including at least two target sub-objects among the sub-entities of the target entity, display a second object combination on a management page of the first sub-entity, where the second object combination includes at least two target sub-objects.

[0097] The first sub-entity can be considered as any sub-entity in the target entity that meets the following conditions: at least two target sub-objects are obtained after S102. In the example of the target entity including sub-entity 1, sub-entity 2, and sub-entity, sub-entity 1 and sub-entity 2 can both be considered as a first sub-entity, while sub-entity 3 cannot be considered as a first sub-entity.

[0098] As an example, S103 may include: S1031, based on the number of target sub-objects of each sub-entity in the target entity obtained in S102, determining at least one first sub-entity including at least two target sub-objects; S1032, for each first sub-entity in the at least one first sub-entity, creating the at least two target sub-objects in the first sub-entity as a second object combination; S1033, displaying the corresponding second object combination on the management page of each first sub-entity in the at least one first sub-entity. In this way, by inheriting the first object combination of the main object in the target entity, the second object combination of the sub-objects is automatically created in the first sub-entity of the target entity.

[0099] It should be noted that the object combination of the sub-object can be linked through some operations of the object combination of the main object (such as offline, update or delete), but other operations of the object combination of the main object (such as online) may not be automatically linked. Therefore, in the embodiment of the present disclosure, for the object combination of each sub-object that inherits the object combination of a main object, the collocation identifiers can be different and different from the collocation identifier of the object combination of the main object. For example, the collocation identifier of the first object combination of the target entity is 123, the collocation identifier of the second object combination 1 that inherits the first object combination in the sub-entity 1 of the target entity can be 456, and the collocation identifier of the second object combination 2 that inherits the first object combination in the sub-entity 2 of the target entity can be 789.

[0100] For example, as shown in Figure 2, assuming that the first object combination created in the target entity includes a first main object and a second main object, and the target entity includes sub-entity 1, sub-entity 2 and sub-entity 3, after the embodiment of the present disclosure, on the management page of sub-entity 1, the second object combination 1 can be displayed, and the second object combination 1 can include a sub-object 11 corresponding to the first main object and a sub-object 12 corresponding to the second main object; on the management page of sub-entity 2, the second object combination 2 can be displayed, and the second object combination 2 can include a sub-object 21 corresponding to the first main object and a sub-object 22 corresponding to the second main object; on the management page of sub-entity 3, since there is only one target sub-object (i.e., sub-object 31), the object combination of sub-objects inherited from the first object combination is not displayed, and is indicated by light gray font and dotted lines in Figure 2 as not existing.

[0101] After S103, it can be considered that the second object combination has been created on the management page of the first sub-entity. The online methods for the second object combination may include but are not limited to: Method 1, manual online, that is, after S103, the method may further include: in response to performing an online operation on the second object combination on the management page of the first sub-entity, the second object combination is online on the first sub-entity; Method 2, automatic online of the second object combination is achieved through a synchronization operation of the first object combination, that is, after S103, the method may further include: in response to performing a synchronization operation on the first object combination on the management page of the target entity, the second object combination is online on the first sub-entity. By onlineizing the second object combination, users can view the second object combination included in the first sub-entity on the online consumption platform, so that they can make purchases according to the second object combination.

[0102] After S103, the state of the second object group may be linked to certain operations of the first object group. The linked operations may include: update operation, offline operation or delete operation.

[0103] As an example, for the update of the first object combination, the method may also include: in response to updating the first object combination on the management page of the target entity, displaying the updated second object combination on the management page of the first child entity, the updated second object combination corresponding to the update of the first object combination.

[0104] As an example, for taking the first object combination offline, the method may further include: in response to performing a first operation on the first object combination on the management page of the target entity, modifying the first state of the second object combination to the second state on the management page of the first child entity. After the second object combination is taken offline on the management page of the first child entity, the user cannot view the second object combination on the first child entity on the online consumption platform. The first operation may refer to an operation to take the first object combination offline, such as modifying the first state of the first object combination to the second state. The object combination in the second state is an object combination used to be hidden or deleted on the display page of the first child entity.

[0105] As an example, for deleting the first object combination, the method may further include: in response to deleting the first object combination on the management page of the target entity, deleting the second object combination on the management page of the first child entity. Unlike going offline, if the first object combination is deleted on the management page of the target entity, then after deletion, the first object combination will no longer exist on the management page of the target entity; however, if the first object combination is taken offline on the management page of the target entity, then after going offline, the first object combination can still be displayed on the management page of the target entity, except that the status of the first object combination is offline. Similarly, if the second object combination is deleted on the management page of the first child entity, then after deletion, the second object combination will no longer exist on the management page of the first child entity; however, if the second object combination is taken offline on the management page of the first child entity, then after going offline, the second object combination can still be displayed on the management page of the first child entity, except that the status of the second object combination is offline.

[0106] In some implementations, for a second sub-entity that includes only one target sub-object within the target entity, a second object combination corresponding to the first object combination may not be created within the second sub-entity. After the second sub-entity includes two or more target sub-objects, a synchronization operation is performed on the first object combination within the target entity to create the second object combination corresponding to the first object combination within the second sub-entity.

[0107] As an example, assuming that the third object combination of the target entity can include a first main object and a second main object, and the second sub-entity of the target entity only includes the first target sub-object corresponding to the first main object, then the method may further include: in response to the second target sub-object corresponding to the second main object in the second sub-entity being set to the first state, and performing a synchronization operation on the third object combination, associating the third object combination on the management page of the second sub-entity to obtain a fourth object combination, and displaying the fourth object combination on the display page of the second sub-entity, wherein the fourth object combination includes the first target sub-object and the second target sub-object, and the sub-objects in the first state are sub-objects for display on the display page of the second sub-entity. The second sub-entity may be, for example, sub-entity 3 shown in FIG2 . In the object management process shown in FIG2 , sub-object 32 corresponding to the first main object in sub-entity 3 may be considered to be in a delisted state. This example can be understood as follows: after sub-object 32 is listed, the first object combination (i.e., the third object combination) can be synchronized on the management page of the target entity to achieve inheritance of the first object combination in sub-entity 3, and sub-entity 3 may include second object combination 3 (i.e., the fourth object combination). Moreover, based on the synchronization operation, the second object combination 3 can be automatically online when the first object combination is online.

[0108] It should be noted that there can only be one effective task at the same time. For example, when the task of inheriting the first object combination of the target entity to the first child entity is being executed, operations such as editing the first object combination of the target entity cannot be performed. The above-mentioned creation, synchronization, update and other functions are mutually exclusive, and the user can only operate one function of an object combination at the same time. Each function belongs to an executable operation of an object, and each function can correspond to an independent button or other control. After the user clicks on the control corresponding to an operation, it is necessary to first determine whether there are other tasks in progress. If so, a pop-up window or other method will prompt the user to try again later. The title of the pop-up window can be "Operation failed", and the text of the pop-up window can be "There is an ongoing task, the operation cannot be performed, please try again later", and the pop-up window has an "OK" button.

[0109] If a create, update, or sync operation fails, you can add a "View Batch Operation History" button to the pop-up window. Clicking this button takes you to the corresponding page for the batch operation history and allows you to view the details of the failure. Each row in the batch operation history page displays the details of one batch task.

[0110] In the batch operation record, in the case of batch processing failure of the object combination of the main object or the object combination of the sub-object, the operations that can be performed include: (1) View the main combination, which can view the name and / or object combination ID of the object combination of the main object corresponding to the task, and can also include the picture corresponding to the object combination of the main object; (2) Operation type, which can include the operations that can be performed on the object combination of all sub-objects; (3) Download failure details, when the task fails, a "Download Failure Details" button appears, and click it to download the relevant information of the failed object combination of the sub-object. The download table can include the following columns: the ID of the object combination of the main object, the ID of the sub-entity, the ID of the sub-object, and the reason for failure. The download table can include the following rows: the ID of the sub-object. It should be noted that the sub-objects in the object combination of a sub-entity need to be included in the download table of the failure record.

[0111] For example, if a target entity contains a primary object a, a primary object b, and a primary object c, and the ID of this object combination is 123, and the target entity contains sub-entities 1, 2, and 3, where sub-entity 1 includes sub-objects a1, b1, and c1, sub-entity 2 includes sub-objects a2 and b2, and sub-entity 3 includes sub-objects a3, b3, and c3, but sub-object a3 is no longer available, then the download table in the failure record can be shown in Table 1 below.

[0112] Table 1

[0113] It can be seen that through this method, the object combination of the main object created on the chain entity can be automatically inherited to the sub-entities of the chain entity, and the object combination of the sub-objects corresponding to the object combination of the main object created by the chain entity can be automatically obtained on the management page of each sub-entity. There is no need for the staff to manually configure the corresponding object combination of sub-objects one by one on the numerous sub-entities of the chain enterprise according to the object combination of the main object, which saves a lot of manpower, material resources and time costs, improves the management efficiency of the sub-objects included in the sub-entities in the chain entity, and makes the management of chain entities in instant retail scenarios more intelligent.

[0114] In some possible implementations, some shared content of the target entity needs to be configured into multiple sub-entities of the target entity. In this case, the method may further include a process of batch displaying (or also referred to as delivery) these shared content components. As an example, the method may further include: S201, in response to creating a shared content component to be displayed on the management page of the target entity and selecting a main object set to be displayed, obtaining a sub-object set corresponding to the main object set in each sub-entity of the target entity, the main object set including at least one main object, and the sub-objects included in the sub-object set corresponding to the main object included in the main object set; S202, for each sub-entity of each sub-entity of the target entity, displaying the shared content component in each sub-object included in the sub-object set.

[0115] The shared content component may refer to a component such as an image or text that can be reused by multiple object detail pages. For example, it may be an image corresponding to the instructions for use, brewing instructions, event descriptions, etc. that need to be displayed on the object detail page. Displaying the shared content component in the child object in S202 may refer to adding the shared content component to a preset location on the child object detail page.

[0116] The functional module corresponding to this implementation method can batch apply the shared content components edited for the primary object in the target entity to the detail pages of the sub-objects corresponding to the primary object in the target entity's sub-entities. It should be noted that if the sub-entities have permission, they can customize the display time of the shared content components on their own detail pages.

[0117] The presentation of the shared content component in the embodiments of the present disclosure may include timed presentation and real-time presentation.

[0118] For real-time display, the implementation process may include: (1) creating a shared content component to be displayed on the management page of the target entity, (2) selecting the main object to be displayed, (3) submitting, (4) reviewing, and (5) after passing the review, the shared content component will be effective on the details page of the sub-object corresponding to the main object to be displayed in each sub-entity of the target entity.

[0119] For timed display, the implementation process may include: (1) creating a shared content component to be displayed on the management page of the target entity, (2) configuring the display time of the shared content component, (3) selecting the main object to be displayed, (4) submitting, (5) reviewing, and (6) after the review is passed, the shared content component is effective on the details page of the sub-object corresponding to the main object to be displayed in each sub-entity of the target entity according to the configured display time. It should be noted that during the period when the shared content component is effective on the details page of the sub-object, if you want to delete the shared content component, you can first stop the task of displaying the shared content component and then delete the shared content component. In this case, S202 may include, for example: if the shared content component is configured with a display time, then for each sub-entity of each sub-entity of the target entity, the shared content component is displayed in each sub-object included in the sub-object set according to the display time.

[0120] To create a shared content component to display, on the target entity's management page, you can select the Create Shared Content Component function. Upon accessing this function, you can first select a real-time or scheduled display mode. Next, you can set the shared content component to display. Once this is complete, you can navigate to the Decoration module to edit the display mode for the shared content component on the detail page. For example, you can set the name of the shared content component and select its position on the detail page. A character limit for the shared content component name can be preset, such as 20 characters. The position of the shared content component on the detail page can be set to Pin, Bottom, or Other. Pin can be placed at the top of the current detail page, Bottom at the bottom, or Other. When multiple shared content components are displayed on a detail page simultaneously, the most recently displayed content indicates the position of the most recently displayed shared content component among the other shared content components. For example, Other - Pin can place the most recently displayed shared content component at the top of the detail page, moving the previously displayed shared content components downward. It should be noted that after creating the shared content component to be displayed, you can preview the effect in a part of the creation page (such as the left side).

[0121] It should be noted that when the target entity is a chain enterprise, the headquarters and management unit stores are supported to set shared content components for the main products, and the sub-products can automatically inherit the shared content components; stores are usually not allowed to set shared content components separately for their own sub-products.

[0122] It should be noted that when editing a shared content component for a main product, the sub-products corresponding to the main product will automatically inherit the modified shared content component. You are not allowed to select only some of the sub-entities displaying the shared content component for the modified shared content component to take effect. Instead, you are required to select all of the sub-entities displaying the shared content component for the modified shared content component to take effect, ensuring that the information on the shared content component in the sub-products and the main product is consistent. If the shared content component information between the main product and sub-products is inconsistent, and certain detail fields on the detail page can be set differently, you can select only some of the sub-entities to take effect for the modified shared content component, while the other sub-entities take effect for the shared content component before the modification.

[0123] The real-time display feature can be set directly for all detail pages. Once set, both the main product and sub-products can modify the shared content components when editing the object's detail page. It should be noted that editing the shared content components of a sub-product requires that the sub-product and its sub-entity are on the whitelist. The whitelist can include sub-products or sub-entities that support differentiated editing of product details.

[0124] For the real-time display function, after setting the details page, neither the main product nor the sub-product can edit the shared content component. If you need to modify the shared content component, you must first end the display task of the shared content component.

[0125] It should be noted that there may be multiple shared content components that are pinned to the top and bottom at the same time, and these multiple shared content components may be displayed in an upward or downward manner.

[0126] Regarding the selection of the main object to be displayed, in one case, if the sub-entity cannot operate the shared content component by itself, then the main object to be displayed can be directly selected, and these main objects can be displayed on the sub-objects corresponding to all sub-entities. The selection of the main object to be displayed can support filtering based on the ID of the main object, the code of the target entity, the name of the main object, the category name or the status of the main object, and the selection of the main object to be displayed can be achieved by checking. In another case, if the sub-entity can operate the shared content component by itself, then after selecting the main object to be displayed, the sub-entity to be displayed can be selected; or the sub-entity to be displayed and the sub-object to be displayed in the sub-entity can be selected. In this way, the shared content component can be effective on the selected sub-object, and the shared content component will not be displayed on the unselected sub-object. Since multiple main objects may have different sub-entities, if the selected sub-entity does not have a corresponding sub-object in a main object of the sub-entity, batch display processing will not be performed.

[0127] After the presentation is complete, the review process begins. You can choose to continue the presentation or view the presentation history. Within the presentation history, real-time presentations and scheduled presentations can be categorized into two categories. The presentation task list within each category displays the shared content component being presented (such as an image describing the activity), the name of the shared content component, the number of associated objects, the presentation status, or actions. The presentation status can include: presentation completed or presentation failed. The reason for a presentation failure could be a system error or a failed review. Hovering the cursor over the "Presentation Failed" area displays the reason. Actions include ending the presentation, deleting the presentation, or viewing details. Only shared content components whose presentation has ended can be deleted. Clicking "View Details" displays details of the sub-objects being presented, including but not limited to their ID, price, sales volume, and presentation status, via a side-sliding pop-up window. If a presentation task displays some sub-entities, the number of sub-entities displayed can also be displayed. Actions displayed can also include viewing sub-entity presentation details. For sub-entity display details, you can display the sub-entity details displayed by the display task under the main object, which can include the sub-entity name, sub-entity ID and display status, and support filtering by sub-entity name and / or sub-entity ID.

[0128] For example, as shown in Figure 3, assume that an activity description picture of "30 off for purchases over 200" is created on the management page of the target entity and is applied to the first main object and the second main object of the target entity. The target entity includes sub-entity 1 and sub-entity 2. The sub-object 11 in sub-entity 1 corresponds to the first main object, the sub-object 12 in sub-entity 1 corresponds to the second main object, the sub-object 21 in sub-entity 2 corresponds to the first main object, and the sub-object 22 in sub-entity 2 corresponds to the second main object. Then, after the real-time display of the activity description picture is achieved through batch display in an embodiment of the present disclosure, the detail pages of sub-objects 11, 12, 21, and 22 all include the activity description picture of "30 off for purchases over 200".

[0129] It can be seen that in the embodiment of the present disclosure, the shared content components created on the chain entity can be automatically inherited to the sub-objects of each sub-entity of the chain entity, and the shared content components created by the chain entity can be automatically obtained on the details page of each sub-object. There is no need for staff to repeatedly configure the shared content that needs to be configured on each sub-object one by one, which saves a lot of manpower, material resources and time costs, improves the management efficiency of the sub-objects included in the sub-entities in the chain entity, and makes the management of chain entities in instant retail scenarios more intelligent.

[0130] In some possible implementations, the target entity also needs to apply the material images uploaded by some main objects without material images in batches to the sub-objects corresponding to each sub-entity, so that each sub-object can be conveniently configured with material images. The sub-objects with material images will provide users with a better viewing experience, thereby improving the user's consumption experience of the sub-objects. Then, the method can also include a process of quickly uploading material images and batching them to sub-objects. As an example, the method can also include: S301, in response to the upload operation of the material image of the third main object on the material image management tool of the target entity, obtaining the first material image of the third main object, the material image management tool is used to display the material image upload status of each main object in the target entity; S302, if the first material image is approved, then for each sub-entity in each sub-entity of the target entity, apply the first material image in the sub-object corresponding to the third main object.

[0131] The stock image can be any image displayed on the object's details page, for example, a white-background image of the object. The following description uses a stock image with a white background as an example; the white-background image can be replaced with any other stock image.

[0132] Although the publishing and / or editing page of an object already has a function entry for uploading white background images, supporting staff to upload white background images for a single sub-object, it is relatively inconvenient for staff at the headquarters or management unit stores of a chain enterprise to view the white background image upload status of multiple main objects. In the embodiment of the present disclosure, a function module for viewing the white background image status of each main object is also opened on the management page of the target entity, and an entry for uploading white background images is added to the operation items of main objects that have not uploaded white background images. This makes it easier for staff to understand the white background image status of all main objects, conduct timely omission detection and online preview editing, and upload white background images for main objects that do not have white background images.

[0133] The functionality provided by the disclosed embodiment is only accessible to the target entity. This means that only the headquarters or management unit stores of a chain enterprise can use this functionality, not the storefronts. The store's sub-products automatically inherit the approved white background image of the main product. The white background image has an independent review status and can be independently appealed. This functionality can be accessed through a separate entry in the target entity's management page, or by modifying the entry for uploading a white background image on the current object's publish and / or edit page.

[0134] When a staff member clicks the white background image management function on the target entity's management page, all main objects under the target entity will be displayed, along with the corresponding white background images of the main objects. The displayed information may include, for example: the main image of the main object, the main object's name, the main object's category, the main object's ID, the main object's status (e.g., on sale, removed from shelves, etc.), the main object's white background image, or its review status. For main objects with white background images, the displayed information includes the main object's white background image. For main objects without white background images, the upload entry for the main object's white background image is displayed.

[0135] The display area corresponding to the white background image management function can be categorized, displayed, and filtered by white background image status. White background image status can include: All, To Be Uploaded, Published, and Rejected. The main object in the display area can be filtered based on the main object's ID, name, or status.

[0136] The review and status in the displayed information may refer to the review status of the uploaded white background image, which may include: under review, passed review, rejected by machine review, or rejected by human review.

[0137] For main objects that do not have a white background image, the upload entrance for the white background image of the main object will be displayed. The text of the upload entrance can be "Upload Image". When the area where the "Upload Image" is located is clicked, three methods of uploading white background images can be supported: Method 1, automatic filling. When the main image or any image in the details page of the main object contains a white background image or an image that can be cut out to obtain a white background image, the upload method can include the "Auto Fill" option. After clicking "Auto Fill", the white background image will be automatically obtained; Method 2, local upload. After clicking "Local Upload", the upload tool will be called up, and the local folder will be entered, from which a white background image can be selected; Method 3, gallery selection. An existing image can be selected from the material image library of the online consumption platform's work website for the target entity to obtain a white background image.

[0138] After uploading the white background image, submit it for review directly. Once the review is passed, the white background image will be determined as the white background image of the main object.

[0139] For a main object that already has a white background image, when the cursor hovers over the white background image, the available operations include but are not limited to: Operation 1, Preview, which displays a larger version of the white background image; Operation 2, Crop, which launches the image editor, crops the white background image, uploads it for review, and applies the cropped white background image after review; Operation 3, Delete, which deletes the white background image.

[0140] The white background image management list can enter an independent material review queue, and only the compliance of the image is reviewed. There is no need to review other information of the main object. Therefore, the review link is clear and brief, and faster than the review link of other products. The review of white background images can be divided into manual review and automatic machine review. For rejected white background images, if it is rejected after manual review, appeals are not allowed; if it is rejected after automatic machine review, appeals are allowed, and the reasons are expressed before entering the review queue for manual review. It should be noted that in the embodiment of the present disclosure, the function of batch appeal and batch deletion of rejected white background images is also supported to improve the efficiency of uploading and batch application of white background images.

[0141] For example, as shown in Figure 4, assume that on the management page of the target entity, the target entity includes sub-entity 1 and sub-entity 2, sub-entity 1 includes sub-object 11 corresponding to the main object 1, and sub-entity 2 includes sub-object 21 corresponding to the main object 1. For the main object 1 that does not include a white background image, click "Upload Image" and select "Local Upload" to select Picture 1 in the local map library and upload it as the white background image of the main object 1; then, review Picture 1; after the review is passed, on the management page of the target entity, the white background image column in the main object 1 displays Picture 1, and sub-objects 11 and sub-objects 21 have white background images and the white background image is Picture 1.

[0142] It can be seen that in the embodiment of the present disclosure, the material image of each main object can be displayed on the chain entity, which is convenient for the staff to understand the main objects that do not have material images or have unreasonable material images; for the main objects that have not uploaded material images, the material images of the main objects can be uploaded on the management page of the chain entity, and the material images can be automatically inherited to the sub-objects of each sub-entity of the chain entity. The material images can be automatically included on the details page of each sub-object, and the staff does not need to repeatedly perform the operation of uploading material images for the sub-objects that need to be configured with material images one by one, which saves a lot of manpower, material resources and time costs, improves the management efficiency of the sub-objects included in the sub-entities in the chain entity, and makes the management of chain entities in instant retail scenarios more intelligent.

[0143] Accordingly, the embodiment of the present disclosure further provides an object management device 500, as shown in FIG5 . The device 500 may include:

[0144] A first obtaining unit 501 is configured to, in response to creating a first object combination on a management page of a target entity, obtain at least two primary objects included in the first object combination, where the at least two primary objects belong to the target entity;

[0145] A second obtaining unit 502 is configured to obtain, from each sub-entity of the target entity, a target sub-object corresponding to each of the at least two main objects, wherein the target sub-object has the same attribute information as the corresponding main object;

[0146] The first display unit 503 is configured to display a second object combination including the at least two target sub-objects on a management page of a first sub-entity among the sub-entities of the target entity. The second object combination includes the at least two target sub-objects.

[0147] In a possible implementation, the third object combination of the target entity includes a first main object and a second main object, and the second sub-entity of the target entity includes only a first target sub-object corresponding to the first main object. The apparatus 500 further includes:

[0148] An association display unit is used to respond to the second target sub-object corresponding to the second main object in the second sub-entity being set to the first state and performing a synchronization operation on the third object combination, associate the third object combination on the management page of the second sub-entity to obtain a fourth object combination, and display the fourth object combination on the display page of the second sub-entity, wherein the fourth object combination includes the first target sub-object and the second target sub-object, and the sub-object in the first state is a sub-object for display on the display page of the second sub-entity.

[0149] In a possible implementation, the apparatus 500 further includes:

[0150] an updating unit, configured to, in response to updating the first object combination on the management page of the target entity, display an updated second object combination on the management page of the first child entity, wherein the updated second object combination corresponds to the update of the first object combination;

[0151] In response to performing a first operation on the first object combination on the management page of the target entity, modifying the second object combination from a first state to a second state on the management page of the first child entity, wherein the object combination in the second state is an object combination for hiding or deleting on the display page of the first child entity;

[0152] A deleting unit is configured to delete the second object combination on the management page of the first child entity in response to deleting the first object combination on the management page of the target entity.

[0153] In a possible implementation, the apparatus 500 further includes:

[0154] a second display unit, configured to display the second object combination on the display page of the first sub-entity in response to performing a synchronization operation on the first object combination on the management page of the target entity;

[0155] or,

[0156] The second display unit is configured to display the second object combination on the display page of the first sub-entity in response to a second operation being performed on the second object combination on the management page of the first sub-entity.

[0157] In a possible implementation, the apparatus 500 further includes:

[0158] a third obtaining unit configured to, in response to creating a shared content component to be displayed on the management page of the target entity and selecting a primary object set to be displayed, obtain, from each sub-entity of the target entity, a child object set corresponding to the primary object set, the primary object set including at least one primary object, and the child objects included in the child object set corresponding one-to-one to the primary objects included in the primary object set;

[0159] The third display unit is configured to display the shared content component in each sub-object included in the sub-object set for each sub-entity of the target entity.

[0160] In a possible implementation, the third display unit is specifically configured to:

[0161] If the shared content component is configured with a display time, then for each of the sub-entities of the target entity, the shared content component is displayed in each sub-object included in the sub-object set according to the display time.

[0162] In a possible implementation, the apparatus 500 further includes:

[0163] a fourth obtaining unit, configured to obtain a first material image of the third main object in response to an upload operation of the material image of the third main object on a material image management tool of the target entity, wherein the material image management tool is configured to display the uploaded material image status of each main object in the target entity;

[0164] The fourth display unit is configured to apply the first material graph to a sub-object corresponding to a third main object for each of the sub-entities of the target entity if the first material graph passes the review.

[0165] It should be noted that the specific implementation of the device 500 and the technical effects achieved can be found in the relevant description of the method shown in FIG1 .

[0166] In addition, an embodiment of the present disclosure also provides an electronic device, which includes a processor and a memory: the memory is used to store instructions or computer programs; the processor is used to execute the instructions or computer programs in the memory, so that the electronic device executes any implementation of the method provided in the embodiment of the present disclosure.

[0167] Referring to FIG6 , a schematic diagram of the structure of an electronic device 600 suitable for implementing embodiments of the present disclosure is shown. Terminal devices in embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. The electronic device shown in FIG6 is merely an example and should not limit the functionality or scope of use of embodiments of the present disclosure.

[0168] As shown in Figure 6, electronic device 600 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage device 608 into a random access memory (RAM) 603. Various programs and data required for the operation of electronic device 600 are also stored in RAM 603. Processing device 601, ROM 602, and RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to bus 604.

[0169] Typically, the following devices may be connected to the I / O interface 605: an input device 606 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 607 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 608 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 609. The communication device 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. Although FIG. 6 shows the electronic device 600 with various devices, it should be understood that not all of the devices shown are required to be implemented or present. More or fewer devices may alternatively be implemented or present.

[0170] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication device 609, or installed from the storage device 608, or installed from the ROM 602. When the computer program is executed by the processing device 601, the above-mentioned functions defined in the method of the embodiment of the present disclosure are performed.

[0171] The electronic device provided by the embodiment of the present disclosure and the method provided by the above embodiment belong to the same inventive concept. For technical details not fully described in this embodiment, please refer to the above embodiment, and this embodiment has the same beneficial effects as the above embodiment.

[0172] The embodiments of the present disclosure further provide a computer-readable medium, in which instructions or computer programs are stored. When the instructions or computer programs are executed on a device, the device executes any implementation of the method provided in the embodiments of the present disclosure.

[0173] It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or component, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, device, or component. In the present disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to wires, optical cables, RF (radio frequency), etc., or any suitable combination thereof.

[0174] In some embodiments, the client and server can communicate using any currently known or later developed network protocol, such as HTTP (Hypertext Transfer Protocol), and can be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or later developed network.

[0175] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0176] The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device can perform the method.

[0177] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages, or a combination thereof, including, but not limited to, object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0178] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the module, program segment, or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of the boxes in the block diagram and / or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0179] The units involved in the embodiments described in this disclosure may be implemented in software or hardware, wherein the name of a unit / module does not, in some cases, limit the unit itself.

[0180] The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, and without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chip (SOCs), complex programmable logic devices (CPLDs), and the like.

[0181] In the context of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium can include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0182] It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Reference can be made to the common and similar parts between the various embodiments. For the systems or devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple, and the relevant parts can be referred to the method description.

[0183] It should be understood that in the present disclosure, "at least one (item)" refers to one or more, and "plurality" refers to two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0184] It should also be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or device comprising the element.

[0185] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0186] It should be noted that in the embodiments of the present disclosure, user sensitive information is not involved, and user-related information is obtained, used and determined after user authorization. In one example, before obtaining user-related information, the corresponding interface displays prompt information related to obtaining data use authorization. This prompt information is based on relevant laws and regulations and informs the user of the type, scope of use, usage scenarios, etc. of the personal information involved in this disclosure in an appropriate manner, so that the user can determine whether to agree to the authorization based on the prompt information. It can be understood that the above-mentioned notification and the process of obtaining user authorization are only illustrative and do not constitute a limitation on the implementation method of the present disclosure. Other methods that meet relevant laws and regulations can also be applied to the implementation method of the present disclosure.

[0187] The above description of the disclosed embodiments is intended to enable one skilled in the art to implement or use the present disclosure. Various modifications to these embodiments will be readily apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is not limited to the embodiments shown herein, but is intended to be construed in the widest manner consistent with the principles and novel features disclosed herein.

Claims

1. An object management method, comprising: In response to creating a first object combination on a management page of a target entity, obtaining at least two primary objects included in the first object combination, wherein the at least two primary objects belong to the target entity; In each sub-entity of the target entity, a target sub-object corresponding to each of the at least two main objects is obtained, wherein the target sub-object has the same attribute information as the corresponding main object; and For a first sub-entity including at least two target sub-objects among the sub-entities of the target entity, a second object combination is displayed on the management page of the first sub-entity, wherein the second object combination includes the at least two target sub-objects.

2. The method according to claim 1, wherein The third object combination of the target entity includes a first main object and a second main object, the second sub-entity of the target entity includes only a first target sub-object corresponding to the first main object, and the method further includes: In response to the second target sub-object corresponding to the second main object in the second sub-entity being set to the first state and a synchronization operation being performed on the third object combination, the third object combination is associated on the management page of the second sub-entity to obtain a fourth object combination, and the fourth object combination is displayed on the display page of the second sub-entity, wherein the fourth object combination includes the first target sub-object and the second target sub-object, and the sub-object in the first state is a sub-object for display on the display page of the second sub-entity.

3. The method according to claim 1 or 2, further comprising: In response to updating the first object combination on the management page of the target entity, displaying an updated second object combination on the management page of the first child entity, wherein the updated second object combination corresponds to the update of the first object combination; In response to performing a first operation on the first object combination on the management page of the target entity, modifying the first state of the second object combination to a second state on the management page of the first child entity, wherein the object combination in the second state is an object combination for hiding or deleting on the display page of the first child entity; and In response to deleting the first object combination on the management page of the target entity, deleting the second object combination on the management page of the first child entity.

4. The method according to claim 1 or 2, further comprising: In response to performing a synchronization operation on the first object combination on the management page of the target entity, displaying the second object combination on the presentation page of the first child entity; or, In response to performing a second operation on the second object combination on the management page of the first sub-entity, the second object combination is displayed on the presentation page of the first sub-entity.

5. The method according to any one of claims 1 to 4, further comprising: In response to creating a shared content component to be displayed on a management page of the target entity and selecting a main object set to be displayed, obtaining a sub-object set corresponding to the main object set in each sub-entity of the target entity, wherein the main object set includes at least one main object, and the sub-objects included in the sub-object set have a one-to-one correspondence with the main objects included in the main object set; For each of the sub-entities of the target entity, the shared content component is displayed in each sub-object included in the sub-object set.

6. The method according to claim 5, wherein: For each of the sub-entities of the target entity, displaying the shared content component in each sub-object included in the sub-object set includes: If the shared content component is configured with a display time, then for each of the sub-entities of the target entity, the shared content component is displayed in each sub-object included in the sub-object set according to the display time.

7. The method according to any one of claims 1 to 6, further comprising: In response to an upload operation of a material image of a third main object on a material image management tool of the target entity, obtaining a first material image of the third main object, wherein the material image management tool is used to display the material image upload status of each main object in the target entity; and If the first material graph passes the review, the first material graph is applied to the sub-object corresponding to the third main object for each of the sub-entities of the target entity.

8. An object management device, comprising: a first obtaining unit configured to, in response to creating a first object combination on a management page of a target entity, obtain at least two primary objects included in the first object combination, wherein the at least two primary objects belong to the target entity; a second obtaining unit configured to obtain, from each sub-entity of the target entity, a target sub-object corresponding to each of the at least two main objects, wherein the target sub-object has the same attribute information as the corresponding main object; and The display unit is configured to display a second object combination on a management page of a first sub-entity including at least two target sub-objects among the sub-entities of the target entity, wherein the second object combination includes the at least two target sub-objects.

9. An electronic device comprising: processor and memory; Wherein, the memory is configured to store instructions or programs; The processor is configured to execute the instructions or programs in the memory, so that the electronic device performs the method according to any one of claims 1 to 7.

10. A readable medium, wherein: The readable medium stores instructions or programs, and when the instructions or programs are executed on a processor, the processor is caused to execute the method according to any one of claims 1 to 7.

Citation Information

Patent Citations

  • Information display method, electronic equipment and computer readable storage medium

    CN116542729A

  • SAAS-based WeChat store integrated platform

    CN117314577A

  • Information processing device, information processing method and program

    JP6195642B1