Object management method, e-commerce platform, electronic equipment and storage medium

Abstract

The embodiment of the invention provides an object management method, an electronic commerce platform, electronic equipment and a storage medium. The object management method comprises the steps that traffic source information and candidate recall objects corresponding to a target object query request are obtained, and the traffic source information at least comprises a traffic region; based on preset management tags of the candidate recall objects, screening the candidate recall objects to obtain recall objects meeting object management conditions of the traffic region; and taking the recall object as an output object corresponding to the target object query request. According to the method, the objects can be managed based on the traffic region only by setting the management labels for the objects, so that the output objects meet the compliance requirements of the traffic region. According to the method, objects do not need to be independently published for different regions, stations do not need to be independently set for different regions, and the effects of low object and e-commerce platform maintenance cost and high maintenance efficiency are achieved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and particularly to an object management method, an e-commerce platform, an electronic device, and a storage medium. Background Art

[0002] Cross-border e-commerce platforms provide services for users in various countries. For example, users in different countries or regions can browse object pages, search for information, purchase objects, etc. on cross-border e-commerce platforms. However, different countries or regions have different market demands. At the same time, there are also differences in laws, regulations, and cultural customs. The objects displayed and sold by e-commerce platforms to users in different countries and regions need to comply with the relevant regulations of the user's country and region, such as meeting the object standards and intellectual property regulations of the target region. Given the significant differences in laws, regulations, and cultural customs among different countries or regions, the existing object management methods in the prior art are: setting up country stations for different countries or regions respectively to meet the object compliance requirements. However, this object management method in the prior art not only has the defect of high maintenance costs for objects and e-commerce platforms, but also has low maintenance efficiency.

[0003] It can be seen that the object management method in the prior art still needs to be improved. Summary of the Invention

[0004] Embodiments of the present application provide an object management method, which can manage objects based on traffic regions throughout the entire link of an e-commerce platform, and achieve the effects of low maintenance costs for objects and e-commerce platforms and high maintenance efficiency on the premise of ensuring that the objects comply with the compliance requirements of the traffic regions.

[0005] Correspondingly, embodiments of the present application also provide an e-commerce platform, an electronic device, and a storage medium to ensure the implementation and application of the above method.

[0006] To solve the above problems, embodiments of the present application disclose an object management method, and the method includes:

[0007] Obtain traffic source information and candidate recalled objects corresponding to a target object query request, where the traffic source information at least includes: traffic region;

[0008] Based on the management tags preset for the candidate recalled objects, screen out recalled objects that meet the object management conditions of the traffic region from the candidate recalled objects;

[0009] Use the recalled objects as the output objects corresponding to the target object query request.

[0010] Embodiments of the present application also disclose an e-commerce platform, and the e-commerce platform includes:

[0011] A client and a server, the server further includes: an object query module, an object management module, an object database, and a risk control module, where

[0012] The object database is used to store the objects published by merchants;

[0013] The risk control module is used to set management tags for the objects published in the object database based on the pre-established object management configuration information;

[0014] The client is used to obtain a target object query request and send the target object query request to the object query module, where the target object query request carries: traffic source information, query parameter information, and the traffic source information at least includes: traffic region;

[0015] The object query module is used to obtain candidate recalled objects based on the query parameter information carried in the target object query request, and call the object management module based on the candidate recalled objects and the traffic region carried in the target object query request;

[0016] The object management module is used to screen out recalled objects that meet the object management conditions of the traffic region from the candidate recalled objects based on the management tags of the candidate recalled objects, and return the recalled objects to the object query module;

[0017] The object query module is further used to send the recalled objects as the output objects corresponding to the target object query request to the client;

[0018] The client is further used to display the objects sent by the object query module.

[0019] An embodiment of the present application also discloses an electronic device, including: a processor, and a memory communicatively connected to the processor; the memory stores computer execution instructions; the processor executes the computer execution instructions stored in the memory to implement the method as described in the embodiment of the present application.

[0020] An embodiment of the present application also discloses a computer-readable storage medium, in which computer execution instructions are stored, and when the computer execution instructions are executed by a processor, they are used to implement the method as described in the embodiment of the present application.

[0021] Compared with the prior art, the embodiments of the present application have the following advantages: By presetting multi-dimensional management tags for an object, the accuracy of object management is improved; By obtaining the traffic source information and candidate recall objects corresponding to a target object query request, where the traffic source information at least includes: traffic region; And based on the management tags preset for the candidate recall objects, screening out recall objects that meet the object management conditions of the traffic region from the candidate recall objects; Finally, using the recall objects as the output objects corresponding to the target object query request, so that the output objects meet the compliance requirements of the traffic region. The present application only needs to set management tags for the object, and can manage the object based on the traffic region, without separately publishing objects for different regions and without separately setting up sites for different regions, achieving the effects of low maintenance cost and high maintenance efficiency for the object and the e-commerce platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 is one of the step flowcharts of an embodiment of an object management method disclosed in the present application;

[0023] Figure 2 is the second of the step flowcharts of an embodiment of an object management method disclosed in the present application;

[0024] Figure 3 is the third of the step flowcharts of an embodiment of an object management method disclosed in the present application;

[0025] Figure 4 is a schematic structural diagram of an e-commerce platform disclosed in the present application;

[0026] Figure 5 is a schematic diagram of the specific implementation architecture of the e-commerce platform disclosed in the present application;

[0027] Figure 6 is a schematic structural diagram of an exemplary device provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0028] To make the above objects, features, and advantages of the present application more obvious and understandable, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0029] The object management method disclosed in the embodiments of the present application can be applied to a cross-border e-commerce platform. For example, an object management module can be set up on the cross-border e-commerce platform for the application layer to call. The object management module filters objects by implementing the object management method disclosed in the embodiments of the present application, filters out objects that do not meet the compliance requirements of the application scenario, and only outputs objects that meet the compliance requirements of the application scenario to the clients facing users in different regions. For example, when global users query and purchase objects through the user client of the cross-border e-commerce platform, the user client responds to the user operation and sends a target object query request to the server of the cross-border e-commerce platform. In the target object query request, in addition to carrying the original request information in the prior art, it is also necessary to carry traffic source information, such as the region of the current user and the query scenario. The server recalls objects according to the target object query request sent by the client to obtain candidate recalled objects. Then, a preset object management module can be called to perform object compliance screening to display objects that meet the compliance requirements of the user's location to the user or provide them for the user to purchase. Among them, the objects include but are not limited to commodities, products, services, etc. of the e-commerce platform.

[0030] By adopting the object management method disclosed in the embodiments of the present application, the cross-border e-commerce platform realizes one-stop management of merchant objects for global users and one-stop management of global clients, effectively improving the object management efficiency, reducing the object management cost of merchants, and at the same time, enhancing the regional expansion ability of objects facing users.

[0031] The following is an example of the specific implementation of an object management method disclosed in the present application.

[0032] Refer to Figure 1 In an optional embodiment, the present application discloses an object management method, and the method includes: Step 102 to Step 106.

[0033] Step 102, obtain the traffic source information and candidate recalled objects corresponding to the target object query request, where the traffic source information at least includes: traffic region.

[0034] Among them, the target object query request can be a target object query request triggered by an object search scenario, a target object query request triggered by an object transaction scenario, a target object query request triggered by a recommendation scenario, etc. The target object query request is used to obtain object information. For example, when a user accesses the client of the cross-border e-commerce platform in country a and searches for a certain object, the client will respond to the user's search request and submit a target object query request for this object to the server.

[0035] Optionally, the cross-border e-commerce platform implementing the object management method disclosed in this application is implemented using a multi-tenant framework agreement, and the target object query request is a request sent by the client of the cross-border e-commerce platform to the server based on the multi-tenant framework agreement.

[0036] In some alternative embodiments, the target object query request carries: traffic source information and query parameter information. Among them, the traffic source information at least includes: traffic region, and may also include: application scenario; the query parameter information includes but is not limited to one or more of the following information: user identifier, object information associated with the request. The object information includes but is not limited to one or more of the following information: object identifier, category, etc.; the user identifier includes but is not limited to one or more of the following information: user account number, user name, system identifier of the user account number, etc. The content and meaning of the query parameter information refer to the prior art and will not be elaborated in the embodiments of this application. The traffic region is used to describe the source region of the current target object query request, such as from which country or from which region. The traffic region can be expressed in the following form: country or region name, country or region identifier. The application scenario is used to describe the functional scenario in the cross-border e-commerce platform, where the application scenario includes but is not limited to any one of the following scenarios: search scenario, recommendation scenario, transaction scenario, live broadcast scenario, etc.

[0037] For example, for a target object query request from a client in country a, the traffic region of the target object query request can be determined through the country identifier carried in the target object query request.

[0038] The candidate recall object is an object recalled by the search or query service in the cross-border e-commerce platform based on the query parameter information in the target object query request, and is denoted as "candidate recall object" in the embodiments of this application.

[0039] In other alternative embodiments, other methods may also be used to obtain the traffic region, application scenario, and candidate recall object corresponding to the target object query request, which will not be listed one by one in the embodiments of this application.

[0040] Step 104, based on the management tags preset for the candidate recall objects, screen out the recall objects that meet the object management conditions of the traffic region from the candidate recall objects.

[0041] Among them, the object management conditions are represented by the management tags of the objects. For example, if the sale of a certain object is prohibited in country b, then set the traffic region tag, application scenario tag, and management method tag for the object in the object database to be sold, add the tag value "country b" to the traffic region tag, add the tag value "transaction scenario" to the application scenario tag, and add the tag value "invisible and non-tradable" to the management method tag. In this way, for regions not set in the traffic region tag, it can be considered that the candidate recall object meets the object management conditions of that region.

[0042] In the embodiments of the present application, the management tags are used to describe the management dimensions, management methods, management rules, etc. of the objects. The management tags include management tags for the objects in each preset dimension. Optionally, the management tags include one or more of the following management tags: management method tag, application scenario tag, risk type, management scope tag, traffic region tag.

[0043] Among them, the risk type includes one or more of the following: intellectual property risk, object authentication risk, object quality execution specification risk, object execution standard risk.

[0044] According to the object management requirements, management tags are set for each type of object, so as to perform compliance management on the objects according to the real-time query traffic conditions of each object.

[0045] Such as Figure 2 As shown, in some alternative embodiments, before obtaining the traffic source information and candidate recall objects corresponding to the target object query request, it further includes: step 100.

[0046] Step 100, based on the pre-established object management configuration information, set management tags for the objects published in the object database.

[0047] Among them, the management tags include tags in one or more of the following dimensions: traffic region tag, application scenario tag, and management method tag. The objects published to the object database include: objects published to the object database for users in multiple countries and regions.

[0048] The meanings of each management tag are introduced below.

[0049] (1) Traffic region tag

[0050] The traffic geographical area label is used to describe the geographical area where the object is subject to compliance management. In some alternative embodiments, the label value of the traffic geographical area label may be: the name or identifier of the country or region where the object is subject to compliance management. For example, different countries have different quality management standards for certain drugs or foods. An object may meet the quality management specifications of some countries but not those of all countries globally. In this case, a traffic geographical area label needs to be set for the object, and the name or identifier of the country or region with transaction risks is set in the traffic geographical area label to mark the countries or regions where the object may have the risk of not meeting the corresponding national quality management specifications when traded and is subject to compliance management.

[0051] (2) Application scenario label

[0052] The application scenario label is used to describe the scope of management scenarios where the object is managed based on the traffic geographical area. The scope of management scenarios described by the application scenario label includes, but is not limited to, one or more of the following scenario scopes: full-scenario management, transaction scenario, search scenario, advertising scenario, live broadcast scenario, store scenario, recommendation scenario, etc. Among them, the label value of the application scenario label may be the scenario name, scenario identifier, etc.

[0053] (3) Management method label

[0054] The management method label is used to describe the management method of the object. The management method includes, but is not limited to, one or both of the following: visibility, tradability. Among them, the visibility management method is used to control whether the object is visible to the user. For example, when a user queries an object that meets specified conditions, if the object meets the user's input query conditions, whether the object can be displayed to the user. The tradability management method is used to control whether the user can purchase a specified object through the client of a certain geographical area (such as a specified country). Optionally, the management method label includes two values, respectively used to indicate: invisible and non-tradable, visible and non-tradable.

[0055] In some embodiments of the present application, when setting management labels for an object, for example, when setting a traffic geographical area label, the risk types involved may be different for different geographical areas, different objects, and different scenarios. For example, for food objects and drug objects, the risks involved are not meeting the food and drug quality management specifications of different geographical areas, while for electronic objects, the risk types involved may be related to intellectual property laws and regulations. Another example is that a certain object may involve multiple risks in a certain geographical area or several geographical areas. Therefore, in order to accurately set the management label of the object, it is also necessary to store the object tagging record, which is used to record the management label and risk type of the object.

[0056] For the specific technical solution of setting management labels for the object, refer to the following description and will not be elaborated here.

[0057] For objects in the object database, not only can management tags and risk types of the objects be added, but also the management tags and risk types of the objects can be revoked as needed.

[0058] As Figure 3 shown, in some alternative embodiments, after setting management tags for the published objects in the object database based on the pre-established object management configuration information, the following is further included: Step 101.

[0059] Step 101: Perform an operation to revoke the management tags and risk types on the target object based on a preset trigger.

[0060] Wherein, the preset trigger may be: a change in the object attribute information, or an object maintenance personnel submits a request to revoke the management tags and / or risk types through the object management client of the cross-border e-commerce platform.

[0061] Optionally, performing an operation to revoke the management tags and risk types on the target object based on a preset trigger includes: obtaining the second management tag and the second risk type of the target object, wherein the target object is the object for which the management tag is to be revoked, the second management tag is the management tag to be revoked for the target object, and the second risk type is the risk type to be revoked for the target object; and performing an operation to revoke the management tag on the target object according to the second management tag, the second risk type of the target object, and the pre-established object tagging record.

[0062] For a certain object, when it is necessary to revoke the management tag corresponding to a certain risk type of the object, the object tagging record can be queried based on the matching principle of the same object, the same region, the same risk type, and the same application scenario, to find the tagging record of the target object that includes the management tag to be revoked (denoted as "the second management tag" in the embodiments of the present application) and the risk type to be revoked (denoted as "the second risk type" in the embodiments of the present application), and then, according to the type of the risk type in the found tagging record, perform the corresponding operation to revoke the management tag.

[0063] In summary, by classifying and marking the objects published by merchants in multiple dimensions such as application scenarios, management methods, risk types, and traffic regions according to the pre-configured object management configuration information, refined management of the objects can be achieved, providing a multi-dimensional and accurate object screening basis for the subsequent object recall process, and ensuring that the recalled objects meet the object management requirements of each region.

[0064] In the embodiments of the present application, the management label of an object can be stored in an object data table bound to the object as additional attribute information of the object. For example, after the object released by a merchant is stored in an object database, a risk control module of a cross-border e-commerce platform screens for risks of each object in the object database, and sets a management label for the objects already released in the object database according to pre-configured object management configuration information, where the management label can be associated with the corresponding object and stored in the object database in the form of additional attribute information of the object.

[0065] In the above text, taking the management label including: management method label, application scenario label, and traffic region label as an example, the method for setting management labels for objects is illustrated by way of example. Those skilled in the art should understand that in applications where fine-grained management of objects by region is required, the traffic region label is a necessary management label. In addition, other management labels can also be set for the objects, and the combination cases of management labels are not enumerated one by one in the embodiments of the present application. Those skilled in the art should also understand that the specific value of each of the above-mentioned labels is only an optional case, not the only or limited case for implementing this method.

[0066] In a cross-border e-commerce platform, each object has an object identifier for uniquely identifying the object. Correspondingly, according to the object identifier of the candidate recalled object, relevant information of each candidate recalled object can be further obtained. After setting management labels for each type of object, during the object recall process, the pre-set management labels of each of the candidate recalled objects can be obtained.

[0067] Furthermore, according to the traffic source information parsed from the current target object query request, the candidate recalled objects can be further screened to obtain objects that meet the compliance management requirements of the source region.

[0068] As described above, the management label includes: traffic region label. Optionally, the method of screening the recalled objects that meet the object management conditions of the traffic region from the candidate recalled objects based on the pre-set management labels of the candidate recalled objects includes: matching the traffic region label of the candidate recalled object with the traffic region, obtaining the candidate recalled objects whose traffic region labels match the traffic region as the first objects to be filtered; obtaining the candidate recalled objects other than the first objects to be filtered as the recalled objects.

[0069] For each of the candidate recall objects, the traffic region label of the candidate recall object is respectively matched with the traffic region (i.e., the traffic source region) carried in the target object query request. If the traffic region label matches the traffic region successfully, it is considered that the candidate recall object is managed by the object management conditions of the traffic region, and the candidate recall object is used as the first object to be filtered. If the traffic region label does not match the traffic region, it is considered that the candidate recall object is not managed by the object management conditions of the traffic region.

[0070] Taking the example where the traffic source information only includes the traffic region, assume that the traffic region is: the country of traffic source, and the value is "Country A". After respectively matching the traffic region with the traffic region labels in the management labels of each candidate recall object, the candidate recall objects whose traffic region labels include "Country A" are obtained as the first objects to be filtered. As can be seen from the previous text, the first objects to be filtered are the candidate recall objects that are subject to compliance management in "Country A".

[0071] The first objects to be filtered obtained through this step are candidate recall objects that are initially judged to be managed by the object management conditions of the traffic source region based on the geographical dimension. In some alternative embodiments, if the object management label only includes the traffic region label, the candidate recall objects other than the first objects to be filtered are used as the recall objects.

[0072] By marking the regions where the objects are subject to compliance management based on the traffic region labels set for the objects, and when recalling the objects, filtering the candidate recall objects that are subject to compliance management in the traffic source region based on the traffic source region of the current target object query request, so as to output the objects that meet the requirements of compliance management in the traffic source region, in order to achieve precise management of the output objects. Specifically, for example, when a user accesses the website client of Country A to query objects, the objects whose traffic region label values set in the management label include "Country A" will be filtered out, so that the objects presented to the user all meet the object management requirements of Country A.

[0073] In the multi-dimensional object management scenario, the management label of the object also includes other dimensions, such as the application scenario label and the management method label. Correspondingly, it is also necessary to further screen the first objects to be filtered in combination with other dimension information to achieve the effect of precise object management.

[0074] Optionally, the management tags include: traffic region tags, application scenario tags, and management method tags. Screening the candidate recall objects to obtain the recall objects that meet the object management conditions of the traffic region based on the management tags preset for the candidate recall objects includes: matching the traffic region tags of the candidate recall objects with the traffic region, obtaining the candidate recall objects whose traffic region tags match the traffic region as the first objects to be filtered; filtering the first objects to be filtered based on the application scenario tags and the management method tags to obtain the second objects to be filtered; and obtaining the candidate recall objects other than the second objects to be filtered as the recall objects.

[0075] For the specific implementation manner of obtaining the first objects to be filtered, refer to the foregoing description and will not be elaborated herein.

[0076] Next, based on the application scenario tags and management method tags of the first objects to be filtered, and based on the application scenarios and management methods subject to compliance management, the first objects to be filtered are further filtered to screen out the selected recall objects that are subject to both regional compliance management and meet the application scenario management conditions and management method management conditions as the second objects to be filtered.

[0077] In the case of different contents included in the traffic source information parsed from the current target object query request, the specific implementation manner of filtering the first objects to be filtered to obtain the second objects to be filtered is different. The following will respectively describe different situations. In the following examples, it is assumed that the application scenario tags include: full-scenario management, search scenario, and transaction scenario, the management method tags of the object include: visible but not tradable, invisible and not tradable, and the traffic region tags include: country a, country b, and country c for illustration.

[0078] (1) The traffic source information only includes the traffic region

[0079] Optionally, filtering the first object to be filtered based on the application scenario tag and the management method tag to obtain a second object to be filtered includes: obtaining the first object to be filtered whose application scenario tag meets the first management scenario condition as the third object to be filtered, where the first management scenario condition is that the management scenario range indicated by the application scenario tag is full-scenario management; obtaining the third object to be filtered whose management method tag meets the first management method condition as the second object to be filtered, where the first management method condition is that the management method indicated by the management method tag is invisible. As mentioned above, the management scenario range indicated by the application scenario tag includes, but is not limited to, one or more of the following scenario ranges: full-scenario management, transaction scenario, search scenario, advertising scenario, live broadcast scenario, store scenario, recommendation scenario, etc. When the application scenario is not carried in the target object query request, only the first objects to be filtered that are all managed in the full scenario need to be selected as the third objects to be filtered. For example, by judging the application scenario tag of the first object to be filtered, the first object to be filtered with the application scenario tag of "full-scenario management" is obtained as the third object to be filtered. Then, combined with the management methods preset for each third object to be filtered, the third objects to be filtered are filtered to obtain the second objects to be filtered.

[0080] In some other embodiments of the present application, it is also possible to first filter the first object to be filtered according to the management method to obtain a filtering result, and then select the candidate recall objects whose management scenario range indicated by the application scenario tag in the obtained filtering result is full-scenario management as the second objects to be filtered.

[0081] The second objects to be filtered obtained by screening according to this method are candidate recall objects managed by the geographical dimension management condition, and the other candidate recall objects except the second objects to be filtered among the candidate recall objects are candidate recall objects not managed by the geographical dimension management condition. Finally, the candidate recall objects not managed by the geographical dimension management condition, that is, the candidate recall objects that do not need to be controlled in the source region of the target object query request, are used as the recall objects for output to the upper-layer application.

[0082] (2) The traffic source information includes: traffic region and application scenario

[0083] In some alternative embodiments, the traffic source information further includes: an application scenario. Correspondingly, filtering the first object to be filtered based on the application scenario tag and the management method tag to obtain a second object to be filtered includes: obtaining the first object to be filtered whose application scenario tag satisfies a first management scenario condition, and the first object to be filtered whose application scenario tag satisfies a second management scenario condition, as a third object to be filtered, where the first management scenario condition is that the management scenario range indicated by the application scenario tag is full-scenario management, and the second management scenario condition is that the management scenario range indicated by the application scenario tag matches the application scenario; in response to the application scenario being a transaction scenario, obtaining the third object to be filtered whose management method tag indicates that the management method is non-tradable as the second object to be filtered; or, in response to the application scenario not being a transaction scenario, obtaining the third object to be filtered whose management method tag indicates that the management method is invisible as the second object to be filtered.

[0084] As described above, the management scenario range indicated by the application scenario tag includes, but is not limited to, one or more of the following scenario ranges: full-scenario management, transaction scenario, search scenario, advertising scenario, live broadcast scenario, store scenario, recommendation scenario, etc. Among them, the application scenario can be information of any one of the following specific scenarios: transaction scenario, search scenario, advertising scenario, live broadcast scenario, store scenario, recommendation scenario, etc. After filtering out the first object to be filtered that is subject to regional management based on the regional information, the first object to be filtered that is subject to management in the full-scenario range and the scenario specified in the target object query request can be further filtered out as the third object to be filtered. For example, by determining whether the management scenario range indicated by the application scenario tag of the first object to be filtered, or indicating a specified management scenario range, if so, the first object to be filtered is used as the third object to be filtered, where the specified management scenario range is the application scenario carried in the target object query request.

[0085] After that, the third object to be filtered is filtered in combination with the management method tags of each third object to be filtered to obtain a second object to be filtered. For example, in the case where the application scenario is a transaction scenario, obtaining the third object to be filtered whose management method tag is visible but non-tradable or invisible and non-tradable as the second object to be filtered. Another example is that in the case where the application scenario is a non-transaction scenario, obtaining the third object to be filtered whose management method tag is invisible and non-tradable as the second object to be filtered.

[0086] Specifically, taking the traffic region included in the traffic source information as "Country A" and the application scenario as "transaction scenario" as an example, through traffic region label matching, candidate recall objects with traffic region labels including "Country A" are filtered out as the first objects to be filtered. Then, the first objects to be filtered with application scenario labels of "full-scenario management" and "transaction scenario" are selected as the third objects to be filtered. After that, the third objects to be filtered with management method labels of "visible but non-tradable" and "invisible and non-tradable" are selected as the second objects to be filtered.

[0087] The second objects to be filtered obtained by screening according to this method are candidate recall objects managed by multi-dimensional region management conditions and application scenario management conditions, while the other candidate recall objects among the candidate recall objects except the second objects to be filtered are candidate recall objects not managed by multi-dimensional management conditions. Finally, the candidate recall objects not managed by multi-dimensional management conditions, that is, the candidate recall objects that do not need to be controlled in the source region and the specified application scenario of the target object query request, are used as recall objects and output to the upper-layer application.

[0088] By setting multi-dimensional management labels for objects and filtering objects based on the matching relationship between the multi-dimensional management labels and the traffic region and application scenario of the current target object query request, more refined management of objects in different regions and different application scenarios is achieved. Specifically, for example, some objects need to be blocked in the advertising scenario and can be normally displayed in the search scenario and transaction scenario. After adding the application scenario label value corresponding to the advertising scenario to the management labels of these objects, when querying objects in the advertising application, the object management module can filter out the objects with full-scenario blocking and continued blocking in the advertising scenario by passing in the advertising scenario in the traffic source information. In the search scenario and transaction scenario, since the application scenario passed in the traffic source information does not match the application scenario labels of these objects, these objects will not be filtered out among the objects output for the search scenario and transaction scenario.

[0089] Step 106, use the recall object as the output object corresponding to the target object query request.

[0090] Finally, the filtered recall object is used as the object corresponding to the target object query request and output. From the method of obtaining the recall object, it can be seen that the output object is an object that meets the management requirements of the source region object of the current target object query request.

[0091] Next, the specific technical solution for setting management labels for objects will be further elaborated.

[0092] In some alternative embodiments, the object management configuration information includes the correspondence between object management conditions and the management labels and risk types. Setting management labels for the objects published in the pre-established object database is based on: according to the matching relationship between the object attribute information of the objects in the object database and the object management conditions in the correspondence, and the risk types corresponding to the object management conditions, set the management labels for the corresponding objects. Optionally, the object attribute information includes, but is not limited to, one or more of the following information: object category, object name, object picture, object detail description content, etc.

[0093] Among them, the object management configuration information is the general rules applicable to multiple countries or regions, and the special rules for specific countries or regions, formulated by relevant personnel such as object managers and legal personnel by collecting laws, regulations and regulatory guidelines of various countries or regions, including trade regulations, object safety standards, certification requirements, label and packaging regulations, etc., comparing and sorting out the requirements of different countries or regions, and identifying commonalities and differences. Then, according to the formulated general rules and special rules, sort out various management labels corresponding to object management conditions, and generate object management configuration information. Among them, the object management conditions can be described by one or more object attribute information.

[0094] For example, if certain drugs are prohibited from being sold in country a without being associated with a specified certificate, then the correspondence between the object attribute information of these drugs and the management label describing the object management condition of being prohibited from being sold in country a can be established in the object management configuration information. Among them, the object management condition includes: not being associated with a specified certificate, and the management label can be configured as follows: the traffic region label is "country a", the application scenario label is "transaction scenario", and the management method label is "invisible and non-tradable".

[0095] For another example, for a certain category of electrical appliance objects, the electrical appliance specifications they meet do not conform to the electrical appliance specifications in region S, then the correspondence between this category and a specific management label can be established in the object management configuration information. Among them, the object management condition includes: a specified category; the specific management label can be configured as follows: the traffic region label is "region S", the application scenario label is "transaction scenario", and the management method label is "invisible and non-tradable".

[0096] After establishing the above object management configuration information, for each object published by a merchant to the object database, the risk types that each object may have in different regions can be automatically identified according to the category and object detail description set by the merchant for the object, so as to determine the management label of the corresponding object.

[0097] In some alternative embodiments, setting the management label for the corresponding object according to the matching relationship between the object attribute information of the object in the object database and the object management conditions in the corresponding relationship, and the risk type corresponding to the object management conditions includes: matching the object attribute information of the object in the object database with the object management conditions to obtain the object management conditions satisfied by the object attribute information as the target object management conditions satisfied by the object; using the management label and the risk type corresponding to the target object management conditions as the first management label and the first risk type of the corresponding object; and setting the management label for the object according to the first management label, the first risk type, and the pre-established object tagging record.

[0098] Among them, the information matching method in the prior art can be used to determine whether the object attribute information of the object in the object database satisfies the object management conditions in the corresponding relationship, which will not be elaborated here.

[0099] Taking the object management condition including the object category as an example, for the electrical appliance object P1, the object category Class1 of the electrical appliance object P1 can be matched with the object categories in the object management configuration information to find one or more object management configuration information with the object category Class1 as the object management condition. Then, the management label corresponding to the object category Class1 in the object management configuration information is used as the management label matched by the electrical appliance object P1. Taking the object management condition including that the pharmaceutical object needs to be associated with the quality management certificate S2 as another example, for the pharmaceutical object P2, the quality management certificate S1 associated with the pharmaceutical recorded in the object attribute information of the pharmaceutical P2 can be matched with the quality management certificate S2 required for the pharmaceutical in the object management configuration information. If the quality management certificates S1 and S2 are different, the management label corresponding to the quality management certificate S2 in the object management configuration information is used as the management label matched by the pharmaceutical.

[0100] In some alternative embodiments, the management label for the object can also be set manually. For example, for some objects for which the management label cannot be automatically set by a computer program according to the matching relationship between the object attribute information of the object in the object database and the object management conditions in the corresponding relationship, the management label matched by the object can be configured manually.

[0101] After determining the management label matched by a certain object using the above method, the determined management label is further used to set the label for the relevant object according to the current tagging status of the object.

[0102] Optionally, based on the first management label, the first risk type, and a pre-established object tagging record, setting a management label for the object includes: querying a first tagging record of the object in the pre-established object tagging record; in response to querying the first tagging record, and when the management label in the first tagging record is the same as the first management label and the risk type in the first tagging record is the same as the first risk type, determining that the object tagging is completed; in response to querying the first tagging record, and when the management label in the first tagging record is the same as the first management label but the risk type in the first tagging record is different from the first risk type, adding the first risk type to the first tagging record; in response to querying the first tagging record, and when the management label in the first tagging record is different from the first management label and the risk type in the first tagging record is the same as the first risk type, adding the first management label as the management label of the object and creating a new tagging record in the object tagging record to describe setting the first management label for the object; in response to not querying the first tagging record, setting the first management label as the management label of the object and creating a new target tagging record in the object tagging record, where the target tagging record is used to describe that the management label corresponding to the object is the first management label and the risk type corresponding to the object is the first risk type.

[0103] Wherein, the object tagging record is used to record the current management label of the object and the existing risk types. For different objects, there may be one risk type or multiple risk types involved, that is, the risk types are superimposed during the object management process. After one type of risk disappears, other types of risks may still exist. In order to accurately manage objects based on the management label, in the embodiments of the present application, the object tagging record is used to record the current tagging status of the object and is updated in real time according to the tagging operation and untagging operation on the object. That is, the object tagging record is dynamically updated during the process of setting and canceling the management label for the object. The object tagging record is used to record the management labels that have been set for each object and the risk types involved for each object.

[0104] For a certain object, when it is necessary to set a specified management label for the object, for the object to be labeled currently and the management label to be set, first, based on the matching principle of the same object, the same region, the same risk type, and the same application scenario, query the labeling record of the object to determine whether the object to be labeled currently has set the management label to be set, and the risk types are the same. If it is found that the same management label has been set and the corresponding risk types are the same, then the setting is not repeated; if the same management label has been set, but the corresponding risk types are different, then a risk type needs to be added to the labeling record of the object to be labeled currently in the object labeling record. If the above labeling record of the object to be labeled currently is not found, then add a management label to the object to be labeled currently according to the management label to be set. At the same time, add a labeling record to the object labeling record to record that the management label to be set has been set for the object to be labeled currently.

[0105] In the embodiments of the present application, an object can be labeled multiple times. For example, for a certain object, after setting the traffic region label as country a, the traffic region label of country b can be added.

[0106] Specifically, first query the labeling record of the object to be labeled currently in the object labeling record. In the embodiments of the present application, it is recorded as the "first labeling record". If the first labeling record is found, further determine whether the management label in the first labeling record is the same as the management label to be set (recorded as the "first management label" in the embodiments of the present application), and determine whether the risk type in the first labeling record is the same as the currently set risk type (recorded as the "first risk type" in the embodiments of the present application). If both are the same, it can be determined that the object to be labeled currently has been set with the management label to be set, and there is no need to repeat the setting, and the operation of setting the management label for the object to be labeled currently ends. If the first labeling record is found, but the management label in the first labeling record is different from the management label to be set and the risk types are the same, then the management label to be set needs to be additionally set for the object to be labeled currently. If the first labeling record is found and the management label in the first labeling record is the same as the management label to be set, but the risk types are different, then a new risk type needs to be added to the first labeling record. If the labeling record of the object to be labeled currently is not found, then the management label to be set needs to be set for the object to be labeled currently. At the same time, add a labeling record of setting the management label to be set for the object to be labeled currently to the object labeling record and set the corresponding risk type.

[0107] The following specifically elaborates on the specific implementation manner of performing the revocation operation of the management label and the risk type on the target object.

[0108] Optionally, perform an operation to revoke the management label on the target object according to the second management label of the target object, the second risk type, and a pre-established object marking record, including: querying the second marking record of the target object in the pre-established object marking record; in response to querying the second marking record, and the management label in the second marking record being the same as the second management label, and the risk type in the second marking record being only the second risk type, deleting the second marking record of the target object, and deleting the management label of the target object; in response to querying the second marking record, and the management label in the second marking record being the same as the second management label, and the risk type in the second marking record including at least one third risk type and the second risk type, deleting the second risk type of the second marking record, where the third risk type is different from the second risk type; in response to querying the second marking record, and the management label in the second marking record being different from the second management label, determining that the revocation of the second management label and the second risk type is completed; in response to not querying the second marking record, determining that the revocation of the second management label and the second risk type is completed.

[0109] Specifically, for example, first query the marking record of the target object in the object marking record. In the embodiments of the present application, it is denoted as the "second marking record". If the second marking record is queried, further determine whether the management label of the second marking record is the same as the management label to be revoked (denoted as the "second management label" in the embodiments of the present application), and determine whether the risk type in the second marking record only includes the current risk type to be revoked (denoted as the "second risk type" in the embodiments of the present application). If the management label in the second marking record is the same as the second management label, and the risk type in the second marking record only includes the second risk type, it is considered that all risk types of the target object have been lifted. Delete the second management label of the target object, and at the same time, delete the second marking record of the target object from the object marking record. If the management label in the second marking record is the same as the second management label, but the risk type in the second marking record includes other risk types in addition to the second risk type, it is considered that the target object still has risks. At this time, only delete the second risk type in the second marking record of the target object from the object marking record, that is, only lift some risk types of the target object. If the marking record of the second management label of the target object is not queried in the object marking record, or the marking record of the target object is not queried in the object marking record, it can be directly considered that the revocation of the second management label and the second risk type of the target object is completed.

[0110] In summary, the object management method disclosed in the embodiments of the present application obtains the traffic source information and candidate recall objects corresponding to the target object query request, where the traffic source information at least includes: traffic region; and based on the management tags preset for the candidate recall objects, filters out the recall objects that meet the object management conditions of the traffic region from the candidate recall objects; finally, uses the recall objects as the output objects corresponding to the target object query request, realizing that only by setting management tags for the objects, the objects can be managed based on the traffic region, making the output objects meet the compliance requirements of the traffic region, without the need to separately publish objects for different regions and without the need to separately set up sites for different regions, achieving the effects of low maintenance cost and high maintenance efficiency for the objects and the e-commerce platform.

[0111] Moreover, the object management method disclosed in the embodiments of the present application realizes lightweight and low-cost full-link and multi-dimensional object management capabilities by setting multi-dimensional management tags for the objects, such as including: traffic region tags, application scenario tags, and management method tags, and transmitting the management tags transparently throughout the entire call link of the objects.

[0112] Furthermore, in this solution, the process of setting management tags for the objects is for all objects of the cross-border e-commerce platform, and the target object query request is implemented based on a multi-tenant architecture, effectively realizing geographical traffic isolation and having strong geographical scalability and universality.

[0113] Based on the above embodiments, the embodiments of the present application also disclose an e-commerce platform for implementing the above object management method.

[0114] Refer to Figure 4 , the e-commerce platform 400 includes: a client 402 and a server 404, and the server 404 further includes: an object query module 4042, an object management module 4044, an object database 4046, and a risk control module 4048, where,

[0115] The object database 4046 is used to store the objects published by the merchants;

[0116] The risk control module 4048 is used to set management tags for the objects published in the object database based on the pre-established object management configuration information, where the management tags include one or more of the following dimensions of tags: traffic region tags, application scenario tags, and management method tags;

[0117] The client 402 is used to obtain a target object query request and send the target object query request to the object query module 4042, where the target object query request carries: traffic source information, query parameter information, and the traffic source information at least includes: traffic region;

[0118] The object query module 4042 is configured to obtain candidate recalled objects based on the query parameter information carried in the target object query request, and call the object management module 4044 based on the candidate recalled objects and the traffic region carried in the target object query request;

[0119] The object management module 4044 is configured to screen out recalled objects that meet the object management conditions of the traffic region from the candidate recalled objects based on the management tags of the candidate recalled objects, and return the recalled objects to the object query module 4042;

[0120] The object query module 4042 is further configured to send the recalled objects as output objects corresponding to the target object query request to the client 402;

[0121] The client 402 is further configured to display the objects sent by the object query module 4042.

[0122] Optionally, the risk control module 4048 is further configured to obtain the second management tag and the second risk type of the target object, where the target object is an object for which the management tag is to be revoked, the second management tag is the management tag to be revoked for the target object, and the second risk type is the risk type to be revoked for the target object; and, perform the operation of revoking the management tag on the target object according to the second management tag, the second risk type of the target object, and the pre-established object tagging record.

[0123] Next, in conjunction with Figure 5 a specific implementation of the e-commerce platform 400 shown, the interaction and data processing processes of each component will be described. In Figure 5 this, each instance refers to the physical entity of the corresponding module.

[0124] As Figure 5 shown, the e-commerce platform 400 may further include a number of merchant-side instances, and merchants publish objects through the merchant-side instances to complete the configuration of object attribute information, where the object attribute information includes, but is not limited to, one or more of the following information: object category, object name, object picture, object detailed description content, etc.

[0125] The objects published by the merchants will be stored in the object database 4046. Optionally, the e-commerce platform 400 may include multiple instances of the object database 4046, that is, object database instances, and each object database instance synchronously stores the objects in real time.

[0126] In some alternative embodiments, an instance of the risk control module 4048 may set management tags for newly released objects in the object database 4046 after detecting them, or periodically. The management tags include tags in one or more of the following dimensions: traffic region tags, application scenario tags, and management method tags.

[0127] An object with management tags set has passed risk control management and can be uploaded to the object center (such as a product center) or a query database for future query use.

[0128] The e-commerce platform 400 may include several instances of clients 402, that is, client instances. Buyer users in different regions access the client instances through the network routing of their local regions. The client instances are further connected to a pre-configured instance of the server 404 (such as a server) through the local region network routing, and perform data interaction with each module set in the server instance.

[0129] For example, the client instance may send a target object query request to an instance of the corresponding object query module 4042 through regional routing. Specifically, when a buyer user logs in to the client instance of the cross-border e-commerce platform 400 in country b to access the seller's mall and performs an object query operation, the client instance will generate a target object query request based on the query conditions input by the current user and the traffic region information corresponding to country b. After that, the client instance will send the generated target object query request to an instance of the object query module 4042. Similarly, when a buyer user logs in to the client instance of the cross-border e-commerce platform 400 in country a to access the seller's mall and performs an object query operation, the client instance will generate a target object query request based on the query conditions input by the current user and the traffic region information corresponding to country a. After that, the client instance will send the generated target object query request to an instance of the object query module 4042.

[0130] Optionally, the target object query request may come from different application scenarios of the cross-border e-commerce platform, such as advertising scenarios, recommendation scenarios, transaction scenarios, and other scenarios in the prior art that can trigger the cross-border e-commerce platform to execute the target object query request. Correspondingly, the object query module 4042 may include multiple query services, which can be respectively used to query different data sources generated according to an instance of the object database 4046. For example, the object query module 4042 may include a search service for querying the query database. For another example, the object query module 4042 may further include a store object query service for querying the object center.

[0131] In an embodiment of the present application, the e-commerce platform is implemented based on a multi-tenant framework, and all buyer users and stores share the object database 4046. At the same time, traffic isolation is achieved for buyer users and stores. The corresponding traffic source information of the buyer users is transmitted throughout the entire link of object query based on the multi-tenant framework. In this way, an instance of the client 402 can transparently transmit the traffic source information (such as traffic region) to an instance of the object query module 4042 and an instance of the object management module 4044.

[0132] The instance of the object query module 4042 performs object query using the query strategy in the prior art to obtain candidate recalled objects. Then, using the candidate recalled objects and the traffic source information (such as traffic region) carried in the target object query request as input parameters, it calls an instance of the object management module 4044.

[0133] The instance of the object management module 4044 filters out recalled objects that meet the object management conditions of the traffic region from the candidate recalled objects based on the management tags of the candidate recalled objects, and returns the recalled objects to the instance of the object query module 4042.

[0134] Finally, the instance of the object query module 4042 sends the recalled objects as the output objects corresponding to the target object query request to the instance of the client 402.

[0135] In some alternative embodiments, the management tags include: traffic region tags. Filtering out recalled objects that meet the object management conditions of the traffic region from the candidate recalled objects based on the management tags of the candidate recalled objects includes: matching the traffic region tags of the candidate recalled objects with the traffic region to obtain the candidate recalled objects whose traffic region tags match the traffic region as the first objects to be filtered; obtaining the candidate recalled objects other than the first objects to be filtered as the recalled objects.

[0136] In some alternative embodiments, the management tags include: traffic region tags, application scenario tags, and management method tags. Filtering out recalled objects that meet the object management conditions of the traffic region from the candidate recalled objects based on the management tags of the candidate recalled objects includes: matching the traffic region tags of the candidate recalled objects with the traffic region to obtain the candidate recalled objects whose traffic region tags match the traffic region as the first objects to be filtered; filtering the first objects to be filtered based on the application scenario tags and the management method tags to obtain the second objects to be filtered; obtaining the candidate recalled objects other than the second objects to be filtered as the recalled objects.

[0137] For the specific implementation manners of the above modules, please refer to the descriptions of the relevant steps in the method embodiments above, and details are not described herein again.

[0138] In summary, for the e-commerce platform disclosed in the embodiments of the present application, by setting one or more dimensions of management tags for the objects published in the object database based on the pre-established object management configuration information, when a target object query request is sent by a client in different regions, the server can obtain candidate recalled objects based on the query parameter information carried in the target object query request, and based on the candidate recalled objects, the traffic region carried in the target object query request, and the management tags of the candidate recalled objects, screen and obtain recalled objects that meet the object management conditions of the traffic region from the candidate recalled objects. Then, the recalled objects are used as the output objects corresponding to the target object query request and sent to the client, realizing that only by setting management tags for the objects, the objects can be managed based on the traffic region, so that the output objects meet the compliance requirements of the traffic region. The e-commerce platform disclosed in the embodiments of the present application does not need to separately publish objects for different regions and does not need to separately set up sites for different regions, achieving the effects of low maintenance cost and high maintenance efficiency of the objects and the e-commerce platform.

[0139] Moreover, for the e-commerce platform disclosed in the embodiments of the present application, by setting multi-dimensional management tags for the objects, such as including: traffic region tags, application scenario tags, management method tags, and transmitting the management tags transparently in the entire call link of the objects, the ability of lightweight, low-cost, full-link, multi-dimensional object management is realized.

[0140] Furthermore, in this solution, the process of setting the management tags of the objects is for all objects of the cross-border e-commerce platform, and the target object query request is implemented based on a multi-tenant architecture, effectively realizing geographical traffic isolation and having strong geographical scalability and universality.

[0141] It should be noted that for the method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the embodiments of the present application are not limited by the described action sequences, because according to the embodiments of the present application, some steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily essential for the embodiments of the present application.

[0142] Based on the above embodiments, the present embodiment further provides an object management device, and the device includes:

[0143] Traffic source information and candidate recall object acquisition module, used to acquire traffic source information and candidate recall objects corresponding to a target object query request, where the traffic source information at least includes: traffic region;

[0144] Candidate recall object filtering module, used to screen out recall objects that meet the object management conditions of the traffic region from the candidate recall objects based on the preset management tags of the candidate recall objects;

[0145] Object output module, used to use the recall objects as the output objects corresponding to the target object query request.

[0146] Optionally, the management tags include: traffic region tags, and the candidate recall object filtering module is further used for:

[0147] Match the traffic region tags of the candidate recall objects with the traffic region, and obtain the candidate recall objects with the traffic region tags matching the traffic region as the first objects to be filtered;

[0148] Obtain the candidate recall objects other than the first objects to be filtered as recall objects.

[0149] Optionally, the management tags include: traffic region tags, application scenario tags, and management method tags, and the candidate recall object filtering module is further used for:

[0150] Match the traffic region tags of the candidate recall objects with the traffic region, and obtain the candidate recall objects with the traffic region tags matching the traffic region as the first objects to be filtered;

[0151] Filter the first objects to be filtered based on the application scenario tags and the management method tags to obtain second objects to be filtered;

[0152] Obtain the candidate recall objects other than the second objects to be filtered as recall objects.

[0153] Optionally, the filtering the first objects to be filtered based on the application scenario tags and the management method tags to obtain second objects to be filtered includes:

[0154] Obtain the first objects to be filtered whose application scenario tags meet the first management scenario condition as the third objects to be filtered, where the first management scenario condition is: the management scenario range indicated by the application scenario tag is full-scenario management;

[0155] Obtain the third object to be filtered whose management method label meets the first management method condition as the second object to be filtered, where the first management method condition is that the management method indicated by the management method label is invisible.

[0156] Optionally, the traffic source information further includes: an application scenario. Filtering the first object to be filtered based on the application scenario label and the management method label to obtain a second object to be filtered includes:

[0157] Obtain the first object to be filtered whose application scenario label meets the first management scenario condition and the first object to be filtered whose application scenario label meets the second management scenario condition as the third object to be filtered, where the first management scenario condition is that the management scenario range indicated by the application scenario label is full-scenario management, and the second management scenario condition is that the management scenario range indicated by the application scenario label matches the application scenario;

[0158] In response to the application scenario being a transaction scenario, obtain the third object to be filtered whose management method label indicates that the management method is non-tradable as the second object to be filtered; or,

[0159] In response to the application scenario not being a transaction scenario, obtain the third object to be filtered whose management method label indicates that the management method is invisible as the second object to be filtered.

[0160] Optionally, before obtaining the traffic source information and the candidate recall object corresponding to the target object query request, the device further includes:

[0161] A first label setting module, configured to set management labels for the objects published in the object database based on the pre-established object management configuration information, where the management labels include labels in one or more of the following dimensions: traffic region label, application scenario label, and management method label.

[0162] Optionally, the object management configuration information includes the correspondence between object management conditions and the management labels and risk types. Setting management labels for the objects published in the object database based on the pre-established object management configuration information includes:

[0163] According to the matching relationship between the object attribute information of the object in the object database and the object management conditions in the correspondence, and the risk type corresponding to the object management conditions, set the management labels for the corresponding objects.

[0164] Optionally, setting the management label for the corresponding object according to the matching relationship between the object attribute information of the object in the object database and the object management condition in the corresponding relationship, and the risk type corresponding to the object management condition includes:

[0165] Matching the object attribute information of the object in the object database with the object management condition, and obtaining the object management condition satisfied by the object attribute information as the target object management condition satisfied by the object;

[0166] Taking the management label corresponding to the target object management condition and the risk type as the first management label and the first risk type of the corresponding object;

[0167] Setting the management label for the object according to the first management label, the first risk type, and the pre-established object tagging record.

[0168] Optionally, after setting the management label for the objects published in the object database based on the pre-established object management configuration information, the apparatus further includes:

[0169] A second label setting module, configured to obtain a second management label and a second risk type of a target object, where the target object is an object for which the management label is to be revoked, the second management label is the management label to be revoked of the target object, and the second risk type is the risk type to be revoked of the target object; and performing an operation of revoking the management label on the target object according to the second management label, the second risk type of the target object, and the pre-established object tagging record.

[0170] Optionally, the objects published to the object database include: objects published to the object database for users in multiple countries and regions.

[0171] In summary, the object management apparatus disclosed in the embodiments of the present application obtains the traffic source information and candidate recall objects corresponding to the target object query request, where the traffic source information at least includes: traffic region; and based on the management labels preset for the candidate recall objects, screening out recall objects that meet the object management conditions of the traffic region from the candidate recall objects; finally, using the recall objects as the output objects corresponding to the target object query request, realizes that only by setting management labels for objects, objects can be managed based on the traffic region, so that the output objects meet the compliance requirements of the traffic region, and there is no need to separately publish objects for different regions and no need to separately set up sites for different regions, achieving the effects of low maintenance cost and high maintenance efficiency of objects and e-commerce platforms.

[0172] Moreover, the object management device disclosed in the embodiments of the present application realizes lightweight and low-cost full-link and multi-dimensional object management capabilities by setting multi-dimensional management tags for objects, such as including: traffic region tags, application scenario tags, and management method tags, and transparently transmitting management tags throughout the entire call link of the object.

[0173] Furthermore, in this solution, the process of setting management tags for objects is oriented to all objects of the cross-border e-commerce platform, and the target object query request is implemented based on a multi-tenant architecture, effectively achieving geographical traffic isolation and having strong geographical scalability and universality.

[0174] The embodiments of the present application also provide a non-volatile readable storage medium, in which one or more modules (programs) are stored. When the one or more modules are applied to a device, the device can be caused to execute instructions (instructions) for each method step in the embodiments of the present application.

[0175] The embodiments of the present application also provide a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the method as described in the embodiments of the present application.

[0176] The embodiments of the present application also provide an electronic device, including: a processor, and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the method as described in the embodiments of the present application. In the embodiments of the present application, the electronic device includes devices such as servers and terminal devices.

[0177] The embodiments of the present disclosure can be implemented as a device configured as desired using any suitable hardware, firmware, software, or any combination thereof. The device can include electronic devices such as servers (clusters) and terminals. Figure 6 Exemplary device 600 that can be used to implement the various embodiments described in the present application is schematically shown.

[0178] For one embodiment, Figure 6 Exemplary device 600 is shown, which has one or more processors 602, a control module (chipset) 604 coupled to at least one of the (one or more) processors 602, a memory 606 coupled to the control module 604, a non-volatile memory (NVM) / storage device 608 coupled to the control module 604, one or more input / output devices 610 coupled to the control module 604, and a network interface 612 coupled to the control module 604.

[0179] The processor 602 may include one or more single-core or multi-core processors, and the processor 602 may include any combination of general-purpose processors or dedicated processors (such as graphics processors, application processors, baseband processors, etc.). In some embodiments, the device 600 can act as devices such as the server, terminal, etc. described in the embodiments of the present application.

[0180] In some embodiments, the device 600 may include one or more computer-readable media (such as the memory 606 or the NVM / storage device 608) having instructions 614, and one or more processors 602 combined with the one or more computer-readable media and configured to execute the instructions 614 to implement modules so as to perform the actions described in the present disclosure.

[0181] For one embodiment, the control module 604 may include any suitable interface controller to provide any suitable interface to at least one of the (one or more) processors 602 and / or any suitable device or component communicating with the control module 604.

[0182] The control module 604 may include a memory controller module to provide an interface to the memory 606. The memory controller module may be a hardware module, a software module, and / or a firmware module.

[0183] The memory 606 may be used, for example, to load and store data and / or instructions 614 for the device 600. For one embodiment, the memory 606 may include any suitable volatile memory, such as suitable DRAM. In some embodiments, the memory 606 may include double data rate type four synchronous dynamic random access memory (DDR4 SDRAM).

[0184] For one embodiment, the control module 604 may include one or more input / output controllers to provide an interface to the NVM / storage device 608 and the (one or more) input / output devices 610.

[0185] For example, the NVM / storage device 608 may be used to store data and / or instructions 614. The NVM / storage device 608 may include any suitable non-volatile memory (such as flash memory) and / or may include any suitable (one or more) non-volatile storage devices (such as one or more hard disk drives (HDDs), one or more optical disc (CD) drives, and / or one or more digital versatile disc (DVD) drives).

[0186] The NVM / storage device 608 may include storage resources that are part of the device on which the device 600 is installed, or it may be accessible by the device without being part of the device. For example, the NVM / storage device 608 may be accessed via the (one or more) input / output devices 610 through a network.

[0187] (One or more) input / output devices 610 may provide an interface for device 600 to communicate with any other suitable device. The input / output devices 610 may include communication components, audio components, sensor components, etc. The network interface 612 may provide an interface for device 600 to communicate via one or more networks. Device 600 may wirelessly communicate with one or more components of a wireless network according to any standard and / or protocol among one or more wireless network standards and / or protocols. For example, it may access a wireless network based on a communication standard, such as Bluetooth, WiFi, 2G, 3G, 4G, 5G, etc., or a combination thereof for wireless communication.

[0188] For one embodiment, at least one of the (one or more) processors 602 may be logically encapsulated with one or more controllers of the control module 604 (e.g., a memory controller module). For one embodiment, at least one of the (one or more) processors 602 may be logically encapsulated with one or more controllers of the control module 604 to form a system-in-package (SiP). For one embodiment, at least one of the (one or more) processors 602 may be logically integrated with one or more controllers of the control module 604 on the same die. For one embodiment, at least one of the (one or more) processors 602 may be logically integrated with one or more controllers of the control module 604 on the same die to form a system-on-chip (SoC).

[0189] In various embodiments, device 600 may be, but is not limited to: a server, a desktop computing device, or a mobile computing device (e.g., a laptop computing device, a handheld computing device, a tablet computer, a netbook, etc.), etc., terminal devices. In various embodiments, device 600 may have more or fewer components and / or a different architecture. For example, in some embodiments, device 600 includes one or more cameras, a keyboard, a liquid crystal display (LCD) screen (including a touchscreen display), a non-volatile memory port, multiple antennas, a graphics chip, an application-specific integrated circuit (ASIC), and a speaker.

[0190] Among them, a main control chip may be used as the processor or control module in the detection device. Sensor data, location information, etc. are stored in the memory or NVM / storage device. The sensor group may be used as an input / output device, and the communication interface may include a network interface.

[0191] Embodiments of the present application also provide an electronic device, including: a processor; and a memory storing executable code thereon, which, when executed, causes the processor to execute one or more of the methods as in the embodiments of the present application. In the embodiments of the present application, various data can be stored in the memory, such as target files, file-application association data, and other various data, and can also include user behavior data, etc., thus providing a data basis for various processes.

[0192] Embodiments of the present application also provide one or more machine-readable media storing executable code thereon, which, when executed, causes a processor to execute one or more of the methods as in the embodiments of the present application.

[0193] For the apparatus embodiments, since they are basically similar to the method embodiments, the description is relatively simple. For the relevant parts, refer to the partial description of the method embodiments.

[0194] Each embodiment in this specification is described in a progressive manner. The key point of each embodiment is to illustrate the differences from other embodiments. For the same or similar parts among the embodiments, refer to each other.

[0195] Embodiments of the present application are described with reference to the flowcharts and / or block diagrams of methods, terminal devices (systems), and computer program objects according to the embodiments of the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, and the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing terminal devices generate an apparatus for implementing the functions specified in Figure 1 one process or multiple processes and / or blocks Figure 1 one block or multiple blocks.

[0196] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal device to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including an instruction apparatus that implements the functions specified in Figure 1 one process or multiple processes and / or blocks Figure 1 one block or multiple blocks.

[0197] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device, so that a series of operation steps are executed on the computer or other programmable terminal device to generate a computer-implemented process. Thus, the instructions executed on the computer or other programmable terminal device provide steps for implementing the functions specified in one process or multiple processes and / or blocks. Figure 1 One process or multiple processes and / or blocks Figure 1 Steps for implementing the functions specified in one block or multiple blocks.

[0198] Although the preferred embodiments of the embodiments of the present application have been described, those skilled in the art can make additional changes and modifications once they learn the basic creative concepts. Therefore, the appended claims are intended to be construed as including the preferred embodiments and all changes and modifications falling within the scope of the embodiments of the present application.

[0199] Finally, it should also be noted that in this article, relational terms such as first and second are only used 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 term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or terminal device comprising a series of elements not only includes those elements, but also includes other elements not expressly listed, or elements inherent to such process, method, article or terminal device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the existence of additional identical elements in the process, method, article or terminal device comprising the said element.

[0200] The above has introduced in detail an object management method, an e-commerce platform, an electronic device and a storage medium provided by the present application. Specific examples are used in this article to elaborate on the principle and implementation manner of the present application. The description of the above embodiments is only used to help understand the method and its core idea of the present application; at the same time, for those of ordinary skill in the art, according to the idea of the present application, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation to the present application.

Claims

1. An object management method, characterized in that, The method includes: Obtaining traffic source information and candidate recall objects corresponding to a target object query request, where the traffic source information at least includes: traffic region; Based on the management tags preset for the candidate recall objects, screening out recall objects that meet the object management conditions of the traffic region from the candidate recall objects; Using the recall objects as the output objects corresponding to the target object query request.

2. The method according to claim 1, wherein The management tags include: traffic region tags. The screening out recall objects that meet the object management conditions of the traffic region from the candidate recall objects based on the management tags preset for the candidate recall objects includes: Matching the traffic region tags of the candidate recall objects with the traffic region, and obtaining the candidate recall objects whose traffic region tags match the traffic region as the first objects to be filtered; Obtaining the candidate recall objects other than the first objects to be filtered as recall objects.

3. The method according to claim 1, wherein The management tags include: traffic region tags, application scenario tags, and management method tags. The screening out recall objects that meet the object management conditions of the traffic region from the candidate recall objects based on the management tags preset for the candidate recall objects includes: Matching the traffic region tags of the candidate recall objects with the traffic region, and obtaining the candidate recall objects whose traffic region tags match the traffic region as the first objects to be filtered; Filtering the first objects to be filtered based on the application scenario tags and the management method tags to obtain second objects to be filtered; Obtaining the candidate recall objects other than the second objects to be filtered as recall objects.

4. The method according to claim 3, characterized in that, The filtering the first objects to be filtered based on the application scenario tags and the management method tags to obtain second objects to be filtered includes: Obtaining the first objects to be filtered whose application scenario tags meet the first management scenario condition as the third objects to be filtered, where the first management scenario condition is: the management scenario range indicated by the application scenario tag is full-scenario management; Obtaining the third objects to be filtered whose management method tags meet the first management method condition as the second objects to be filtered, where the first management method condition is: the management method indicated by the management method tag is invisible.

5. The method according to claim 3, wherein The traffic source information further includes: application scenario. The filtering the first objects to be filtered based on the application scenario tags and the management method tags to obtain second objects to be filtered includes: Obtaining the first objects to be filtered whose application scenario tags meet the first management scenario condition and the first objects to be filtered whose application scenario tags meet the second management scenario condition as the third objects to be filtered, where the first management scenario condition is: the management scenario range indicated by the application scenario tag is full-scenario management, and the second management scenario condition is: the management scenario range indicated by the application scenario tag matches the application scenario; In response to the application scenario being a transaction scenario, obtain the third object to be filtered whose management method tag indicates that the management method is non-tradable as the second object to be filtered; or, In response to the application scenario not being a transaction scenario, obtain the third object to be filtered whose management method tag indicates that the management method is invisible as the second object to be filtered.

6. The method according to claim 1, wherein Before obtaining the traffic source information and candidate recall objects corresponding to the target object query request, it further includes: Based on the pre-established object management configuration information, set management tags for the objects published in the object database, where the management tags include tags in one or more of the following dimensions: traffic region tags, application scenario tags, and management method tags.

7. The method according to claim 6, wherein The object management configuration information includes the correspondence between object management conditions and the management tags and risk types. Based on the pre-established object management configuration information, setting management tags for the objects published in the object database includes: According to the matching relationship between the object attribute information of the objects in the object database and the object management conditions in the correspondence, and the risk types corresponding to the object management conditions, set the management tags for the corresponding objects.

8. The method according to claim 7, wherein The setting of the management tags for the corresponding objects according to the matching relationship between the object attribute information of the objects in the object database and the object management conditions in the correspondence, and the risk types corresponding to the object management conditions includes: Match the object attribute information of the objects in the object database with the object management conditions to obtain the object management conditions satisfied by the object attribute information as the target object management conditions satisfied by the object; Use the management tags and risk types corresponding to the target object management conditions as the first management tags and the first risk types of the corresponding objects; Set the management tags for the object according to the first management tags, the first risk types, and the pre-established object tagging records.

9. The method according to claim 6, wherein After setting the management tags for the objects published in the object database based on the pre-established object management configuration information, it further includes: Obtain the second management tags and the second risk types of the target object, where the target object is the object for which the management tags are to be revoked, the second management tags are the management tags to be revoked for the target object, and the second risk types are the risk types to be revoked for the target object; Perform the operation of revoking the management tags on the target object according to the second management tags, the second risk types of the target object, and the pre-established object tagging records.

10. The method according to claim 6, wherein The objects published in the object database include: objects published in the object database for users in multiple countries and regions.

11. An e-commerce platform, characterized in that, It includes: A client and a server, where the server further includes: an object query module, an object management module, an object database, and a risk control module, where The object database is used to store the objects published by merchants; The risk control module is used to set management tags for the objects published in the object database based on the pre-established object management configuration information; The client is used to obtain a target object query request and send the target object query request to the object query module. Among them, the target object query request carries: traffic source information and query parameter information. The traffic source information at least includes: traffic region; The object query module is used to obtain candidate recalled objects based on the query parameter information carried in the target object query request, and call the object management module based on the candidate recalled objects and the traffic region carried in the target object query request; The object management module is used to screen out recalled objects that meet the object management conditions of the traffic region from the candidate recalled objects based on the management tags of the candidate recalled objects, and return the recalled objects to the object query module; The object query module is further used to send the recalled objects as output objects corresponding to the target object query request to the client; The client is further used to display the objects sent by the object query module.

12. An electronic device, characterized in that, It includes: A processor and a memory communicatively connected to the processor; The memory stores computer execution instructions; The processor executes the computer execution instructions stored in the memory to implement the method according to any one of claims 1-10.

13. A computer-readable storage medium, characterized in that, Computer execution instructions are stored in the computer-readable storage medium, and when the computer execution instructions are executed by the processor, they are used to implement the method according to any one of claims 1-10.

Images