Store commodity operation authority updating method and device, terminal and medium
By employing automated feature extraction and rule association mechanisms, the problem of low efficiency in traditional access control has been solved. This enables precise matching and dynamic adjustment of access control rules for a massive number of store products, thereby improving the efficiency and accuracy of access control.
Patent Information
- Application Number
- CN202510966685.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-07-14
- Publication Date
- 2025-10-17
Smart Images

Figure CN120807102A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of computers, and in particular to a store commodity management permission updating method and device, a terminal and a medium. BACKGROUND
[0002] In the operation process of a retail enterprise, there is an important task of fine management of the saleable range of a large number of SKUs in each store. These SKUs are large in number and diverse in attributes, covering different categories, specifications, brands and batches, etc. The stores are widely distributed, and the consumer habits, commercial district positioning and target customer groups in different regions differ. Meanwhile, market strategies are adjusted according to market dynamics, and there may be differences in regulatory requirements in different regions or different commodity categories. Promotion activities also show the characteristics of diversification and high frequency. Under this background, the enterprise needs to ensure that each SKU can be sold in the appropriate store at the appropriate time to adapt to the flexible adjustment of market strategies, meet the strict requirements of local regulations, and efficiently carry out various promotion activities.
[0003] However, traditional management methods, such as manual list management relying on manual operation and simple "commodity forbidden combination" mode, mainly rely on manual data entry, updating and checking. With the increase in the number of stores and the number of commodity SKUs, the inefficiency of traditional management methods is continuously magnified, which has become a technical problem that needs to be solved by technical personnel in the field. SUMMARY
[0004] The present application provides a store commodity management permission updating method, device, terminal and medium, which is used to solve the technical problem of low efficiency of existing store commodity management permission management methods.
[0005] To solve the above technical problems, the first aspect of the present application provides a store commodity management permission updating method, comprising:
[0006] receiving permission rule updating information;
[0007] performing feature extraction based on the permission rule updating information to obtain rule updating features, wherein the rule updating features include store features, commodity features and permission features;
[0008] determining a store ID corresponding to the store features and a commodity ID corresponding to the commodity features according to the store features and the commodity features, in combination with preset store information and commodity information;
[0009] generating store commodity rule association information corresponding to the permission rule updating information according to the store ID and the commodity ID, in combination with a permission rule ID corresponding to the permission features;
[0010] According to the comparison between the store commodity rule association information and the core rule information, a target store commodity combination affected in the core rule information is determined, and a permission rule of the target store commodity combination is updated based on the store commodity rule association information, to obtain an updated store commodity operation permission list, wherein the core rule information records the permission rule of each store commodity combination.
[0011] Preferably, the rule updating feature further comprises a rule level feature and / or a rule effective condition feature.
[0012] The rule level feature is used to determine the permission rule with the highest level as the effective rule when multiple permission rules conflict.
[0013] The rule effective condition feature is used to indicate the effective condition of the permission rule.
[0014] Preferably, the store commodity rule association information corresponding to the permission rule update information is generated according to the store ID and the commodity ID, in combination with the permission rule ID corresponding to the permission feature, and comprises:
[0015] The store ID and the commodity ID are associated with the permission rule ID corresponding to the permission feature respectively, to obtain store rule association information and commodity rule association information respectively.
[0016] The store ID and the commodity ID corresponding to the same permission rule ID are subjected to Cartesian product processing, to obtain the store commodity rule association information corresponding to the permission rule update information.
[0017] Preferably, before the permission rule of the target combination is updated based on the store commodity rule association information, the method further comprises:
[0018] According to the comparison result of the store commodity rule association information and the core rule information, an update operation mode corresponding to each target store commodity combination is determined, so as to update the permission rule of the target store commodity combination based on the store commodity rule association information and in combination with the update operation mode corresponding to the target store commodity combination, to obtain the updated store commodity operation permission list.
[0019] Preferably, the update operation mode comprises initialization rule, added rule application, deleted rule application, and deleted rule association.
[0020] Preferably, the determination of the update operation mode corresponding to each target store commodity combination according to the comparison result of the store commodity rule association information and the core rule information comprises:
[0021] When the rule for the target store commodity combination does not exist in the core rule information, it is determined that the update operation mode corresponding to the target store commodity combination is initialization of the rule, so as to create the permission rule of the target store commodity combination in the core rule information;
[0022] When the rule for the target store commodity combination already exists in the core rule information, and the permission rule of the target store commodity combination is added through the update of the store commodity rule association information, it is determined that the update operation mode corresponding to the target store commodity combination is addition of the rule, so as to add the permission rule of the target store commodity combination in the core rule information;
[0023] When the rule for the target store commodity combination already exists in the core rule information, and part or all of the permission rules of the target store commodity combination are removed through the update of the store commodity rule association information, it is determined that the update operation mode corresponding to the target store commodity combination is deletion of the rule or deletion of the rule association, so as to delete part or all of the permission rules of the target store commodity combination in the core rule information.
[0024] Preferably, the obtained updated store commodity operation permission list comprises:
[0025] Based on the updated core rule information, a store commodity operation permission list is generated according to the to-be-activated rule corresponding to each store commodity combination, wherein the to-be-activated rule is the permission rule with the highest level and meeting the activation condition among all the permission rules corresponding to the store commodity combination.
[0026] Meanwhile, the second aspect of the present application provides a store commodity operation permission updating device, comprising:
[0027] A permission rule update information receiving unit is configured to receive permission rule update information.
[0028] A feature extraction unit is configured to perform feature extraction based on the permission rule update information to obtain rule update features, wherein the rule update features comprise store features, commodity features and permission features.
[0029] A store commodity information matching unit is configured to determine a store ID corresponding to the store features and a commodity ID corresponding to the commodity features according to the store features and the commodity features, and in combination with preset store information and commodity information.
[0030] An information association unit is configured to generate store commodity rule association information corresponding to the permission rule update information according to the store ID and the commodity ID, and in combination with a permission rule ID corresponding to the permission features.
[0031] The permission list generation unit is configured to compare the store commodity rule association information with core rule information, determine an affected target store commodity combination in the core rule information, update a permission rule of the target store commodity combination based on the store commodity rule association information, and obtain an updated store commodity operation permission list, wherein the core rule information records the permission rule of each store commodity combination.
[0032] The third aspect of the present application provides a store commodity operation permission management terminal, comprising a memory and a processor.
[0033] The memory is configured to store program code for implementing the store commodity operation permission updating method according to the first aspect of the present application.
[0034] The processor is configured to read and execute the program code.
[0035] The fourth aspect of the present application provides a computer readable storage medium, which stores program code for being read and executed by a processor to implement the store commodity operation permission updating method according to the first aspect of the present application.
[0036] From the above technical solutions, the present application has the following advantages:
[0037] The scheme provided by the present application first receives permission rule updating information, then extracts features from the permission rule updating information to obtain rule updating features including store features, commodity features and permission features, and then realizes accurate matching and dynamic adjustment of massive store commodity permission rules through automatic feature extraction, rule association and intelligent updating mechanism, thereby solving the problems of low efficiency and easy errors in traditional manual management and improving the efficiency and accuracy of permission management. BRIEF DESCRIPTION OF DRAWINGS
[0038] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed in the embodiments or prior art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.
[0039] Figure 1 The flowchart of the store commodity operation permission updating method provided by the present application is shown in the figure.
[0040] Figure 2 The structure diagram of the store commodity operation permission updating device provided by the present application is shown in the figure.
[0041] Figure 3 A structural schematic diagram of an embodiment of a store commodity management permission terminal provided by the present application is provided. DETAILED DESCRIPTION
[0042] In the prior art, retail enterprises need to finely manage the saleable range of a large number of commodities in each store. The number of commodities is large and the attributes are diverse, the stores are widely distributed and there are regional differences, and the market strategy needs to be frequently adjusted. The traditional management mode relies on manual operation and simple forbidden matching mode. With the growth of the number of stores and commodities, manual updating is inefficient and prone to data errors, and cannot adapt to the dynamic changes in business needs. For example, when a certain chain supermarket needs to adjust the range of promotional commodities, it needs to manually check the matching relationship between hundreds of stores and thousands of commodities, resulting in a long update cycle and the risk of omissions.
[0043] To solve the above problems, the researchers found that the core defect of the traditional method is the lack of automatic feature analysis and rule association mechanism. By analyzing the permission update scene, it is found that each rule change involves multi-dimensional matching of store attributes, commodity attributes and permission attributes, from which the idea of decomposing rule update information into computable features is generated. In view of this, the embodiments of the present application provide a store commodity management permission update method, device, terminal and medium, for realizing the automatic processing of permission update and solving the technical problem of low efficiency of the existing store commodity management permission management mode.
[0044] To make the purposes, features and advantages of the present application more obvious and easy to understand, the technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. Obviously, the embodiments described below are only a part of the embodiments of the present application, not all. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative labor are within the scope of protection of the present application.
[0045] First, a detailed description of an embodiment of a store commodity management permission update method provided by the present application is provided as follows:
[0046] Please refer to Figure 1 The store commodity management permission update method provided by the embodiments of the present application comprises:
[0047] Step 101, receiving permission rule update information;
[0048] Step 102, feature extraction based on the permission rule update information to obtain rule update features;
[0049] Among them, the rule update features include: store features, commodity features and permission features;
[0050] Step 103, according to the store features and the commodity features, combining the pre-set store information and commodity information, determine the store ID corresponding to the store features, and the commodity ID corresponding to the commodity features;
[0051] Step 104, according to the store ID and the commodity ID, combining the permission rule ID corresponding to the permission feature, generate the store commodity rule association information corresponding to the permission rule update information;
[0052] Step 105, according to the comparison between the store commodity rule association information and the core rule information, determine the target store commodity combination affected in the core rule information, update the permission rule of the target store commodity combination based on the store commodity rule association information, and obtain the updated store commodity operation permission list;
[0053] Among them, the core rule information records the permission rule of each store commodity combination.
[0054] It should be noted that the permission rule update information refers to structured data containing permission adjustment instructions, which can be implemented in JSON or XML format, and is used to carry data elements such as store screening conditions, commodity classification identifiers, and permission change types. Rule update features refer to computable data units extracted from update information, which can be implemented using natural language processing techniques, such as extracting store area features through named entity recognition and extracting commodity category features through classification models. Store information refers to a pre-established standardized store database, which can store the mapping relationship between store ID and address, area, level, etc. attributes using a relational database. Commodity information refers to standardized commodity master data, which can store the association relationship between commodity ID and attributes such as category, brand, and specification using a distributed database. Core rule information refers to the current effective permission rule set, which can store the multi-dimensional association relationship between stores, commodities, and permission rules using a graph database.
[0055] Specifically, when the system receives a permission rule update request, first parse the request content to extract key feature elements. For example, a certain update requires "all A-level flagship stores in Guangdong Province to add sales permission for commodity X", the system extracts "Guangdong Province" "A-level" "flagship store" as store features, "commodity X" as commodity features, and "add sales permission" as permission features. Then, through the store database matching, obtain the store ID set of all A-level flagship stores in Guangdong Province, and through the commodity database matching, obtain the commodity ID set of commodity X, wherein if "commodity X" refers to a specific commodity, the matching is the commodity ID of the commodity, and if "commodity X" refers to a certain commodity category, the matching is all commodity IDs under the commodity category. Then, after associating the matching results with the permission rule ID, a new rule association information is generated, which is compared and analyzed with the existing core rules to automatically identify the store commodity combinations that need to add permissions. Finally, update the core rule database to generate a store commodity operation permission list containing the latest permission status, which can be used to distribute the data in the store commodity operation permission list to each downstream business system (such as POS system, e-commerce platform, etc.) through a data interface for use.
[0056] The above technical scheme realizes the automatic processing of permission rule updating, effectively reduces the error rate of manual operation, and shortens the rule updating period to minutes. The system can accurately identify the store commodity combinations affected by rule changes, avoiding the possible problems of missed or mismatched allocation in traditional methods. Through the standardized feature extraction and matching mechanism, it ensures that the permission update operations in different business scenarios have unified processing logic, and improves the adaptability of the system to complex rule changes.
[0057] On the basis of the above basic embodiment, the scheme of the present application further proposes that the rule update features can also include: rule level features and rule effective condition features, the rule level features are used to give priority to the permission rule with the highest rule level when multiple permission rules conflict, and the rule effective condition features are used to indicate the effective conditions of the permission rules.
[0058] Among them, the rule level feature refers to the attribute of setting the priority value of the permission rule. Specifically, it can be implemented by numerical coding or alphabetical grading, for example, dividing the rules into first level, second level, third level, etc. This feature enables automatic selection of the highest priority rule in the case of rule conflict, avoiding manual intervention. The rule effective condition feature refers to the logical judgment condition that triggers the effectiveness of the permission rule. Specifically, it can be implemented by time range, inventory threshold or sales area restriction parameters, for example, setting the rule to take effect only during the promotion period or when the inventory is below a preset value. This feature ensures that the permission rule is automatically activated or deactivated in a specific scenario through dynamic condition judgment.
[0059] Specifically, after receiving the permission rule update information, the system extracts the rule level feature and the rule effective condition feature. When there are multiple permission rules for the same store commodity combination, the system automatically filters the highest level rule as the final effective rule according to the rule level feature. For example, if a new rule 1 "Guangdong Province all A-level flagship stores add new commodity B1 sales permission" is added, but there is also a blacklist rule "Guangdong Province all A-level stores stop B-class commodities (including commodity B1) sales permission", at this time, if the priority of rule 1 is higher than that of the blacklist rule, rule 1 can break through the restriction of the blacklist rule and take effect. At the same time, the system performs real-time condition detection based on the rule effective condition feature, for example, it judges whether the current time is within the promotion period. If the condition is not met, the corresponding rule is temporarily disabled. In this way, the conflict processing and dynamic activation process of the permission rule are automatically executed.
[0060] The rule level feature is used to automatically resolve conflicts. In addition, the rule effective condition in the prior art is usually described in fixed text, which cannot be linked with real-time business data. The rule effective condition feature in the present scheme parameterizes the condition, so that the system can dynamically monitor and trigger rule state changes. Through the above technical scheme, the problem of low efficiency caused by relying on manual decision in the case of permission rule conflict is solved, and the automatic matching of rule effective condition and business data is realized. For example, during the promotion activity, the system automatically enables the high-priority promotion rule and overrides the original sales restriction rule, and automatically restores the original rule after the promotion ends, without the need for manual adjustment one by one.
[0061] Regarding step 104 mentioned in the above basic embodiment, the step process can be further refined as:
[0062] According to the store ID and the commodity ID, in combination with the permission rule ID corresponding to the permission feature, the store commodity rule association information corresponding to the permission rule update information is generated, including: associating the store ID and the commodity ID with the permission rule ID corresponding to the permission feature respectively to obtain store rule association information and commodity rule association information respectively; performing Cartesian product processing on the store ID and the commodity ID corresponding to the same permission rule ID to obtain the store commodity rule association information corresponding to the permission rule update information.
[0063] The store rule association information refers to a data structure for establishing a corresponding relationship between the store ID and the permission rule ID, which can be implemented in the form of a key-value pair or an association table, and is used to record a set of permission rules applicable to each store. The commodity rule association information refers to a data structure for establishing a corresponding relationship between the commodity ID and the permission rule ID, which can be implemented in the form of a two-dimensional relationship matrix, and is used to identify the permission rule range applicable to each commodity. The Cartesian product processing refers to an operation method for full combination traversal of all store IDs and commodity IDs under the same permission rule ID, which can be implemented by using database joint query or set operation algorithm, and is used to generate a complete mapping relationship between the store and the commodity in the permission rule dimension.
[0064] Specifically, in the permission rule update process, first, the store features and the commodity features in the permission rule update information are parsed, and the pre-set store information library and the commodity information library are matched to obtain the corresponding store ID and commodity ID respectively. Then, the store ID is associated with the permission rule ID to form a store rule association information table, and at the same time, the commodity ID is associated with the same permission rule ID to form a commodity rule association information table. Further, for all store IDs and commodity IDs under the same permission rule ID, Cartesian product operation is performed to generate a three-tuple set containing the store ID, the commodity ID and the permission rule ID, thereby constructing complete store commodity rule association information. For example, when the permission rule ID is R001, if the associated store ID contains S001 and S002, and the commodity ID contains P100 and P200, four association records {S001, P100, R001}, {S001, P200, R001}, {S002, P100, R001}, and {S002, P200, R001} will be generated through Cartesian product processing.
[0065] The application can automatically generate the association relationship between all possible store commodity combinations and permission rules by introducing a Cartesian product processing mechanism, avoiding the efficiency bottleneck and data consistency errors caused by manual operation. Through the above technical solutions, the application solves the problem of incomplete rule coverage caused by low efficiency of manual operation in traditional permission management, realizes the automatic batch generation of the association relationship between store and commodity permission rules, ensures that all related store commodity combinations are accurately identified and processed when the rules are updated, and effectively supports the business needs of high-frequency and large-scale permission rule updates.
[0066] Further, the application further proposes that before updating the permission rules of the target combination based on the store commodity rule association information, it can also include:
[0067] According to the comparison result of the store commodity rule association information and the core rule information, the update operation mode corresponding to each target store commodity combination is determined, so as to update the permission rules of the target store commodity combination based on the store commodity rule association information and the update operation mode corresponding to the target store commodity combination, and obtain the updated store commodity operation permission list.
[0068] Among them, the update operation mode refers to the specific operation type of changing the permission rules, and these operation modes are used to distinguish the rule change requirements in different scenarios. By presetting multiple operation types and automatically matching the operation mode based on the rule comparison result, different granularity permission change requirements can be accurately processed, and fine operation control of permission rule update is realized, for example, quickly removing specific rules after the promotion activity ends without affecting other associated permissions, or batch updating the affected store commodity combinations when the regulations change, for example, in the scene that needs to handle the addition and deletion operations at the same time, the system can automatically identify and execute the corresponding operations respectively, avoiding errors that may be caused by manual intervention, and improving the processing efficiency of large-scale rule update.
[0069] More specifically, the application further proposes that the update operation mode includes initializing rules, adding rule application, deleting rule application, and deleting rule association.
[0070] Among them, the initialization rule refers to creating a permission rule for the target store commodity combination in the core rule information for the first time, which can be implemented by inserting a new record in the database, and is suitable for the scene of configuring permission for the first time; the new rule application refers to adding new rules for the target store commodity combination on the basis of the existing permission rules, which can be implemented by adding an association identifier in the existing rule set, and is suitable for the scene of expanding the coverage range of permission; the rule application deletion refers to removing part of the permission rules of the target store commodity combination, which can be implemented by marking the invalid state or physically deleting in the rule set, and is suitable for the scene of adjusting the permission application condition or range; the rule association deletion refers to removing the binding relationship between the target store commodity combination and the specific permission rule, which can be implemented by deleting the corresponding record in the association table, and is suitable for the scene of rule invalidation or reconfiguration.
[0071] Specifically, when the permission rule update information triggers the core rule information adjustment, first, the specific operation type to be performed is identified by comparing the differences between the store commodity rule association information and the core rule information. For example, if the target store commodity combination has no corresponding record in the core rule information, the initialization rule operation is performed to create a basic permission rule; if a new rule needs to be added on the basis of the existing rule, the new rule application operation is performed to expand the rule set through the association identifier; if part of the redundant or conflicting rules need to be removed, the rule application deletion operation is performed to retain only the valid rules; if the association between the rule and the combination needs to be completely removed, the rule association deletion operation is performed to clear all the binding relationships. Thus, through the combination of the four operation types, dynamic and fine adjustment of the permission rule is realized.
[0072] In addition, through the above four operation modes, the following operation scenarios can be further derived: 1) after the "rule application deletion" operation is performed, if the highest priority rule that was previously effective is deleted, a rule that has existed before but has a lower priority will automatically become the new effective rule for the store commodity combination, thereby achieving the effect of "the 'original' rule invalidation and the'substitute' rule promotion"; 2) after the "new rule application" operation is performed, if a newly added or newly applied rule in this batch has a higher priority than the originally effective rule, it replaces the old rule, thereby achieving the effect of "the'stronger' new rule replacing the effective position of the old rule".
[0073] The scheme can automatically match different update scenarios through the preset four operation types, for example, support incremental update instead of full coverage, avoid repeated operation, and ensure the accuracy and traceability of rule changes. Through the above technical scheme, the corresponding update operation type can be quickly matched for the permission rule change requirement of a large number of store commodity combinations, and the complexity of manual intervention is reduced. For example, after the promotion activity ends, the temporary permission can be removed by batch executing the delete rule application operation without the need to reconfigure all rules, which significantly improves the rule update efficiency and system response flexibility.
[0074] Based on the above proposed update operation mode, the application further proposes to determine the update operation mode corresponding to each target store commodity combination according to the comparison result of the store commodity rule association information and the core rule information, including:
[0075] When there is no rule for the target store commodity combination in the core rule information, the update operation mode corresponding to the target store commodity combination is determined as initializing rules to create the permission rules of the target store commodity combination in the core rule information; when there is a rule for the target store commodity combination in the core rule information, and the permission rules of the target store commodity combination are increased through the update of the store commodity rule association information, the update operation mode corresponding to the target store commodity combination is determined as adding rule application to add the permission rules of the target store commodity combination in the core rule information; when there is a rule for the target store commodity combination in the core rule information, and part or all of the permission rules of the target store commodity combination are removed through the update of the store commodity rule association information, the update operation mode corresponding to the target store commodity combination is determined as deleting rule application or deleting rule association to delete part or all of the permission rules of the target store commodity combination in the core rule information.
[0076] Specifically, in the permission rule update process, the system automatically identifies the rule change state of each store commodity combination by comparing the current core rule information with the updated association information. For example, when it is detected that a combination has no corresponding record in the core rule library, an initialization process is triggered to generate an initial permission configuration; if it is found that there is an existing record but there is a new permission item, an incremental update operation is performed; for the scenario where the permission needs to be removed, partial deletion or complete unbinding operation is selected according to the removal range. Thus, a complete closed-loop process from rule matching, state determination to operation execution is realized, and the efficiency bottleneck caused by manual intervention is avoided.
[0077] The scheme can identify the rule change type in real time and trigger the corresponding operation process through the automatic state judgment and classification processing mechanism, greatly shortens the processing period and ensures the operation accuracy. Through the above technical scheme, the problem of low efficiency of manual operation in the case of massive store commodity combination permission update is solved. Through the rule state automatic judgment and classification processing mechanism, accurate update of permission rules is realized, rule conflicts or data omissions caused by manual misjudgment are avoided, and the processing efficiency of large-scale data update is further improved.
[0078] Further, the application also provides an updated store commodity operation permission list, which includes: based on the updated core rule information, generating a store commodity operation permission list according to the to-be-effective rule corresponding to each store commodity combination, wherein the to-be-effective rule is the permission rule with the highest level and meeting the effective condition among all the permission rules corresponding to the store commodity combination.
[0079] Specifically, when generating the store commodity operation permission list, first, all the permission rules associated with each store commodity combination are extracted from the updated core rule information, and then the permission rules are sorted in descending order according to the rule level characteristics, and the rule set with the highest level is selected. Further, the rule set selected is verified for the effective condition, such as checking whether the current time is within the rule validity period, whether the target area meets the sales permission range, whether the promotion activity is in the active state, etc. If there is a rule that meets the conditions of the highest level and the effective condition, it is written into the list as the to-be-effective rule; if there is no rule that meets the conditions, the store commodity combination is marked as an unsalable state. Therefore, the list generation process ensures the accuracy and real-time performance of the permission rules through automatic rule screening and condition verification.
[0080] The scheme can quickly identify the highest priority rule and dynamically verify its effective condition through the automatic processing of rule level characteristics and effective condition characteristics, avoiding the inefficiency and uncertainty of manual intervention. Through the above technical scheme, the permission effectiveness problem in the case of multi-rule conflict can be automatically solved, ensuring that the generation process of the store commodity operation permission list is efficient and accurate under complex market strategies and dynamic regulatory requirements, while reducing the business risks caused by rule priority misjudgment or effective condition omission, and adapting to the business needs of high-frequency and multi-dimensional rule update.
[0081] The above is a detailed description of an embodiment of a store commodity operation permission update method provided by the application, and the following is a detailed description of an embodiment of a store commodity operation permission update device provided by the application.
[0082] Please refer to Figure 2 The store commodity operation permission update device provided by the embodiment of the application includes:
[0083] The permission update information receiving unit 201 is configured to receive permission rule update information.
[0084] The feature extraction unit 202 is configured to perform feature extraction based on the permission rule update information to obtain rule update features, wherein the rule update features include store features, commodity features, and permission features.
[0085] The store commodity information matching unit 203 is configured to determine a store ID corresponding to the store features and a commodity ID corresponding to the commodity features according to the store features and the commodity features, and in combination with preset store information and commodity information.
[0086] The information association unit 204 is configured to generate store commodity rule association information corresponding to the permission rule update information according to the store ID and the commodity ID, in combination with a permission rule ID corresponding to the permission features, wherein the store commodity rule association information.
[0087] The permission list generation unit 205 is configured to compare the store commodity rule association information with core rule information to determine a target store commodity combination affected in the core rule information, to update the permission rule of the target store commodity combination based on the store commodity rule association information, and to obtain an updated store commodity operation permission list, wherein the core rule information records the permission rule of each store commodity combination.
[0088] Specifically, when the permission update information receiving unit captures a rule change request, the feature extraction unit parses key elements in the request, for example, which may include a store area code, a commodity classification code, and a permission type code. The store commodity information matching unit converts the area code into a specific store number and the classification code into a standard commodity code by querying a preset store information database and a commodity information database. The information association unit then binds these entity codes with rule identifiers to form an association data set containing a three-dimensional relationship of store-commodity-rule. The permission list generation unit automatically identifies permission items that need to be adjusted by comparing with an existing core rule library, for example, when a store adds sales permission for a certain type of commodity, the unit detects whether there are conflicting clauses in the original rule set, and automatically updates the permission state according to the preset priority rule.
[0089] Through the above technical solution, the problem of low efficiency of permission rule update in large-scale retail networks is solved, and automatic identification and accurate pushing of rule change impact are realized. The cooperative operation of the units of the device reduces the manual intervention link, avoids permission configuration errors caused by human operation errors, supports real-time processing of high-frequency rule updates, and meets the needs of rapid iteration of modern retail business.
[0090] In addition, the application also provides detailed descriptions of a store commodity operation permission management terminal embodiment and a computer readable storage medium embodiment, as follows:
[0091] Please refer to Figure 3 The application provides a store commodity operation permission management terminal. The terminal implementation carrier can be a personal computer, a server, an embedded electronic device, or the like. The main components of the terminal include a memory 33 and a processor 31. The memory 33 and the processor 31 can be connected through a communication bus 34.
[0092] The memory 33 is configured to store program code. The program code is configured to implement the store commodity operation permission update method mentioned in the above embodiments. The processor 31 is configured to read and execute the program code.
[0093] The memory refers to a physical device for saving program code and data. The memory can be implemented by a solid state disk, a mechanical hard disk, or a cloud storage medium. The memory is configured to persistently store permission rule update logic and core rule information, and ensure that the data is not lost after power failure or system restart. The processor refers to an operation unit for executing program code. The processor can be implemented by a multi-core central processing unit or a distributed computing chip. The processor is configured to analyze program instructions, perform feature extraction, rule matching, and permission list generation operations, and improve the efficiency of massive data processing through parallel computing.
[0094] Specifically, the terminal implements the permission rule update process through the program code stored in the memory. After the permission rule update information is received, the processor performs feature extraction operations to separate the store features, commodity features, and permission features from the update information. Then, the processor calls the preset store information and commodity database to map the features to specific store IDs and commodity IDs, and associates them with the corresponding permission rule IDs. Subsequently, the processor compares the associated information with the core rule library, identifies the target store commodity combination that needs to be updated, and generates the final permission list according to the conflict resolution strategy. For example, in the rule conflict scenario, the processor automatically selects the rule with the highest priority and updates the list.
[0095] In some specific embodiments, the memory can be configured as a distributed database cluster to support high concurrency access, and the processor can be deployed as a multi-node computing architecture to accelerate rule matching for large-scale store commodity combinations. The program code can be packaged using containerization technology to facilitate dynamic expansion of computing resources on the cloud or local servers.
[0096] Further, the computer readable storage medium proposed by the application stores program code. The program code is configured to be read and executed by the processor to implement the store commodity operation permission update method mentioned in the above embodiments.
[0097] The computer-readable storage medium refers to a physical carrier or an electronic carrier capable of persistently storing program code, and can be implemented by a solid state disk, a mechanical hard disk or a cloud storage server. The storage of the program code ensures the repeatability of the permission rule updating logic.
[0098] Specifically, when the program code is executed by the processor, first, the permission rule updating information is received, which can include store identification, commodity classification or permission effective condition elements. Then, the program code extracts features from the updating information, such as store features, commodity features and permission features obtained by regular expression matching or keyword recognition. Next, the program code matches the extracted features with the preset store information library and commodity information library, such as through hash table query or database index retrieval, to determine the corresponding store ID and commodity ID. Then, the program code performs an association operation on the store ID, the commodity ID and the permission rule ID, such as generating all possible store commodity combination rule association information through Cartesian product. Finally, the program code compares the generated association information with the core rule library, identifies the target combination that needs to be updated, and completes the permission rule updating operation according to the preset conflict resolution strategy, to generate a store commodity operation permission list containing the latest effective rules.
[0099] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the terminal, the device and the unit described above can refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.
[0100] In several embodiments provided in the present application, it should be understood that the disclosed terminal, device and method can be implemented by other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units or components shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or other forms.
[0101] The terms "first", "second", "third", "fourth" and the like in the description of this application and in the claims, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the use of these terms herein is to be construed to cover the embodiments of this application, unless otherwise expressly specified and set forth in a claim attached hereto. Furthermore, terms "comprise", "have" and "include" and their conjugates, as used herein, are used to specify the presence of an stated feature, integer, step, operation, element, component, or the like but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or groups thereof.
[0102] It should be understood that, in this application, "at least one" means one or more, "multiple" means two or more. "And / or" is used to describe the relationship between associated objects, which means that there can be three relationships, for example, "A and / or B" can mean: only A, only B, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects. "At least one of the following" or the like means any combination of these items, including any combination of single or multiple items. For example, at least one of a, b or c, can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.
[0103] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or they can be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.
[0104] In addition, the functional units in each embodiment of the application can be integrated into one processing unit, or each unit can exist physically, or two or more units can be integrated into one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.
[0105] The integrated unit, if implemented in the form of a software function unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application essentially or say the part that contributes to the prior art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media that can store program codes.
[0106] The above-described embodiments are only used to illustrate the technical solutions of the present application, rather than limit them; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacements for some technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application.
Claims
1. A method for updating store merchandise management authority, characterized in that: include: Receive permission rule update information; Performing feature extraction based on the authority rule update information to obtain rule update features, wherein the rule update features include: store features, product features, and authority features; According to the store characteristics and product characteristics, combined with preset store information and product information, determine the store ID corresponding to the store characteristics and the product ID corresponding to the product characteristics; Generate store-product rule association information corresponding to the permission rule update information based on the store ID and the product ID and the permission rule ID corresponding to the permission feature; By comparing the store product rule association information with the core rule information, the target store product combination affected in the core rule information is determined, and the permission rules of the target store product combination are updated based on the store product rule association information to obtain an updated store product operating permission list, wherein the core rule information records the permission rules for each store product combination.
2. A method for updating store merchandise management authority according to claim 1, characterized in that: The rule update characteristics also include: rule level characteristics and / or rule effectiveness condition characteristics; The rule level feature is used to take effect the permission rule with the highest rule level when multiple permission rules conflict; The rule effectiveness condition feature is used to indicate the effectiveness condition of the permission rule.
3. A method for updating store merchandise management authority according to claim 1, characterized in that: According to the store ID and the product ID, combined with the permission rule ID corresponding to the permission feature, the store product rule association information corresponding to the permission rule update information is generated, including: Associating the store ID and the product ID with the permission rule ID corresponding to the permission feature, respectively, to obtain store rule association information and product rule association information; Cartesian product processing is performed on the store ID and product ID corresponding to the same authority rule ID to obtain store-product rule association information corresponding to the authority rule update information.
4. A method for updating store merchandise management authority according to claim 2, characterized in that: Before updating the permission rules of the target combination based on the store product rule association information, the method further includes: Based on the comparison results of the store product rule association information and the core rule information, the update operation method corresponding to each target store product combination is determined, so that the permission rules of the target store product combination are updated based on the store product rule association information and combined with the update operation method corresponding to the target store product combination to obtain an updated store product operating permission list.
5. A method for updating store merchandise management authority according to claim 4, characterized in that: The update operation methods include: initializing rules, adding new rule applications, deleting rule applications, and deleting rule associations.
6. A method for updating store merchandise management authority according to claim 5, characterized in that: The determining of the update operation mode corresponding to each target store product combination according to the comparison result of the store product rule association information and the core rule information includes: When there is no rule for the target store product combination in the core rule information, determining that the update operation mode corresponding to the target store product combination is an initialization rule, so as to create an authority rule for the target store product combination in the core rule information; When a rule for the target store product combination already exists in the core rule information, and a permission rule for the target store product combination is added by updating the store product rule association information, determining that the update operation mode corresponding to the target store product combination is applicable to the new rule, so as to add the permission rule for the target store product combination to the core rule information; When there are already rules for the target store product combination in the core rule information, and part or all of the permission rules of the target store product combination are removed by updating the store product rule association information, the update operation mode corresponding to the target store product combination is determined to be deletion of rule application or deletion of rule association, so as to delete part or all of the permission rules of the target store product combination in the core rule information.
7. A method for updating store merchandise management authority according to claim 6, characterized in that: The updated store merchandise management authority list includes: Based on the updated core rule information, a store merchandise management authority list is generated according to the pending rules corresponding to each store merchandise combination, wherein the pending rules are the authority rules with the highest level and meeting the effectiveness conditions among all the authority rules corresponding to the store merchandise combination.
8. A device for updating store merchandise management authority, characterized in that: include: A permission update information receiving unit, configured to receive permission rule update information; a feature extraction unit, configured to extract features based on the authority rule update information to obtain rule update features, wherein the rule update features include: store features, product features, and authority features; A store product information matching unit, configured to determine, based on the store characteristics and product characteristics, the store ID corresponding to the store characteristics and the product ID corresponding to the product characteristics in combination with preset store information and product information; An information association unit, configured to generate store-product rule association information corresponding to the permission rule update information based on the store ID and the product ID and the permission rule ID corresponding to the permission feature; The permission list generating unit is used to compare the store product rule association information with the core rule information, determine the target store product combination affected in the core rule information, and update the permission rules of the target store product combination based on the store product rule association information to obtain an updated store product operation permission list, wherein the core rule information records the permission rules for each store product combination.
9. A store merchandise management authority management terminal, characterized in that: include: memory and processor; The memory is used to store program code, and the program code is used to implement the method for updating store merchandise management authority according to any one of claims 1 to 7; The processor is configured to read and execute the program code.
10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores program code, which is used to be read and executed by a processor to implement a method for updating store merchandise management permissions as described in any one of claims 1 to 7.