CN112101992B

CN112101992B - Object management method and device based on multiple object sides

Info

Publication number: CN112101992B
Application number: CN202010946132.9A
Authority: CN
Inventors: 张约晟; 王侃譞
Original assignee: Rajax Network Technology Co Ltd
Current assignee: Rajax Network Technology Co Ltd
Priority date: 2020-09-10
Filing date: 2020-09-10
Publication date: 2021-09-07
Anticipated expiration: 2040-09-10
Also published as: CN112101992A

Abstract

The invention discloses an object management method and device based on a plurality of object sides, wherein the method comprises the following steps: in response to the received principal creation request, creating an object principal and generating a primary account corresponding to the object principal; acquiring configuration dimensions contained in a received set configuration request, creating an object dimension set which is subordinate to an object main body and corresponds to the configuration dimensions, and generating set sub-accounts which are subordinate to a primary account and correspond to the object dimension set; configuring a plurality of object ends which are subordinate to an object dimension set according to a received object configuration request, and respectively generating object sub-account numbers which are subordinate to a primary account number and correspond to the object ends; and managing an object main body, an object dimension set and each object terminal belonging to the object dimension set through the primary account number, the set sub-account number and the object sub-account number respectively. The method can manage a plurality of similar object ends based on the object dimension set, and achieves the purposes of managing the similar object ends in batch and improving the management efficiency.

Description

Object management method and device based on multiple object sides

Technical Field

The invention relates to the technical field of data management, in particular to an object management method and device based on a plurality of object sides.

Background

At present, with the increasing popularity of the internet, more and more entity objects can provide services by means of the internet. These entity objects include: libraries, cinemas, parks, and the like. For example, on the basis of traditional offline stores, a large number of store ends relying on internet operation are derived. These store ends provide store services to users via the internet, and accordingly, users can access the store ends via the internet.

The inventor finds that the number of the online object ends is huge in the process of implementing the invention, but the management is loose, the object ends are independent from each other, different administrators are required to manage the object ends respectively, and the clustering and unified management cannot be performed on the types of the online object ends. Therefore, an efficient management method is needed in the prior art to realize batch management of multiple homogeneous object terminals.

Disclosure of Invention

In view of the above problems, embodiments of the present invention are proposed to provide a method and apparatus for object management based on multiple object sides, which overcome or at least partially solve the above problems.

According to an aspect of the embodiments of the present invention, there is provided an object management method based on multiple object sides, including:

in response to a received principal creation request, creating an object principal and generating a primary account corresponding to the object principal;

acquiring configuration dimensions contained in a received set configuration request, creating an object dimension set which is subordinate to the object main body and corresponds to the configuration dimensions, and generating set sub-accounts which are subordinate to the primary account and correspond to the object dimension set;

configuring a plurality of object ends which are subordinate to the object dimension set according to a received object configuration request, and respectively generating object sub-account numbers which are subordinate to the primary account number and correspond to the object ends;

and managing the object main body, the object dimension set and each object terminal belonging to the object dimension set through the primary account number, the set sub-account number and the object sub-account number respectively.

Optionally, the managing the object subject, the object dimension set, and each object terminal belonging to the object dimension set through the primary account number, the set sub-account number, and the object sub-account number respectively includes:

the method comprises the steps of obtaining an account identification contained in a received account management request, determining a data range corresponding to the account identification, carrying out aggregation processing on data content matched with the data range to obtain an account data set corresponding to the account identification, and executing management operation according to the account data set.

Optionally, when the account id included in the account management request corresponds to the primary account, the data range corresponding to the account id includes: a subject data range matching a subject corresponding to a primary account number, and an account number data set corresponding to the account number identification includes: a subject account data set corresponding to the subject;

when the account id contained in the account management request corresponds to a set sub-account, the data range corresponding to the account id includes: a set data range that matches the set of object dimensions corresponding to the set sub-account, and the account data set corresponding to the account identification includes: a set account data set corresponding to the set of object dimensions;

when the account id contained in the account management request corresponds to the object sub-account, the data range corresponding to the account id includes: and the object data range is matched with the object end corresponding to the object sub-account, and the account data set corresponding to the account identification comprises: and the object account data set corresponds to the object terminal.

Optionally, the executing the management operation according to the account data set includes:

acquiring a management type identifier contained in the account management request;

and executing the management operation matched with the management type identification aiming at the account data set.

Optionally, the management type identifier includes: a data processing type identifier, an electronic ticket issuance type identifier, and/or an activity creation type identifier.

Optionally, after generating the set sub-account which is subordinate to the primary account and corresponds to the set of object dimensions, the method further includes:

configuring the integrated account role information of the integrated sub-accounts and the integrated account authority data corresponding to the integrated account role information;

and after the object sub-account numbers which belong to the primary account number and correspond to the object terminals are respectively generated, the method further comprises the following steps: and configuring object account role information of each object sub-account and object account authority data corresponding to the object account role information.

Optionally, the data range corresponding to the account id is further determined according to account role information corresponding to the account id; the account role information comprises: the aggregate account role information and/or the object account role information.

Optionally, the set sub-accounts corresponding to the object dimension set are multiple, and the multiple set sub-accounts correspond to different set account role information and set account permission data respectively; and the object sub-accounts corresponding to the object terminals are multiple, and the multiple object sub-accounts correspond to different object account role information and different object account permission data respectively.

Optionally, the configuration dimensions included in the set configuration request include a plurality of dimensions, and the creating an object dimension set that is subordinate to the object subject and corresponds to the configuration dimensions, and the generating a set sub-account that is subordinate to the primary account and corresponds to the object dimension set includes:

and creating a plurality of object dimension sets which are subordinate to the object main body and respectively correspond to the configuration dimensions, and generating a plurality of set sub-account numbers which are subordinate to the primary account number and respectively correspond to the object dimension sets of the configuration dimensions.

Optionally, the object main body is a store main body, and the object end is a store end; the configuration dimensions contained in the set configuration request include at least one of: a brand store configuration dimension, a chain store configuration dimension, a group store configuration dimension, and a regional store configuration dimension;

and the set of object dimensions corresponding to the configuration dimensions comprises at least one of: a brand dimension set, a linkage dimension set, a clique dimension set, and a region dimension set.

Optionally, after generating the set sub-account which is subordinate to the primary account and corresponds to the set of object dimensions, the method further includes: storing the mapping relation between the set sub-account and the object dimension set into a preset account mapping table;

after the generating the object sub-account numbers which belong to the primary account number and correspond to the object terminals respectively, the method further includes: storing the mapping relation between the object sub-account and the object end into the account mapping table;

and, the method further comprises: and changing the set sub-account and/or the object sub-account, and updating the account mapping table.

Optionally, the creating an object body in response to the received body creation request includes:

and acquiring and verifying the main body data information contained in the main body creating request, and if the verification is passed, creating an object main body corresponding to the main body data information.

According to another aspect of the embodiments of the present invention, there is provided an object management apparatus based on multiple object sides, including:

the subject creating module is suitable for responding to a received subject creating request, creating an object subject and generating a primary account number corresponding to the object subject;

the set configuration module is suitable for acquiring configuration dimensions contained in a received set configuration request, creating an object dimension set which is subordinate to the object main body and corresponds to the configuration dimensions, and generating a set sub-account which is subordinate to the primary account and corresponds to the object dimension set;

the object configuration module is suitable for configuring a plurality of object ends which are subordinate to the object dimension set according to a received object configuration request, and respectively generating object sub-account numbers which are subordinate to the primary account number and correspond to the object ends;

and the management module is suitable for managing the object main body, the object dimension set and each object terminal belonging to the object dimension set through the primary account number, the set sub-account number and the object sub-account number respectively.

Optionally, the management module is specifically adapted to:

Optionally, the set configuration module is further adapted to:

and the object configuration module is further adapted to: and configuring object account role information of each object sub-account and object account authority data corresponding to the object account role information.

Optionally, the configuration dimensions included in the set configuration request include a plurality of dimensions, and the set configuration module is specifically adapted to:

Optionally, the set configuration module is further adapted to: storing the mapping relation between the set sub-account and the object dimension set into a preset account mapping table;

the object configuration module is further adapted to: storing the mapping relation between the object sub-account and the object end into the account mapping table;

and, the apparatus further comprises:

and the changing module is suitable for changing the set sub-account and/or the object sub-account and updating the account mapping table.

Optionally, the subject creation module is specifically adapted to:

According to still another aspect of an embodiment of the present invention, there is provided an electronic apparatus including: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;

the memory is used for storing at least one executable instruction, and the executable instruction enables the processor to execute the operation corresponding to the object management method based on the plurality of object sides.

According to a further aspect of the embodiments of the present invention, there is provided a computer storage medium, where at least one executable instruction is stored, and the executable instruction causes a processor to perform operations corresponding to the object management method based on multiple object sides as described above.

In the object management method and device based on multiple object sides provided by the embodiment of the invention, firstly, an object main body is created and a primary account corresponding to the object main body is generated; then, according to the configuration dimension contained in the received set configuration request, an object dimension set which is subordinate to the object main body and corresponds to the configuration dimension is created, and a set sub-account which is subordinate to the primary account and corresponds to the object dimension set is generated; and finally, configuring a plurality of object terminals which are subordinate to the object dimension set according to the received object configuration request, and respectively generating object sub-account numbers which are subordinate to the primary account number and correspond to the object terminals, so that the object main body, the object dimension set and the object terminals which are subordinate to the object dimension set are managed through the primary account number, the set sub-account number and the object sub-account number respectively. Therefore, the method can generate the object dimension set corresponding to the configuration dimension based on the object main body, so that a plurality of homogeneous object terminals are managed based on the object dimension set. The configuration dimensions can be flexibly set according to the characteristics of the object main body, and the specific content and the specific number of the configuration dimensions can be flexibly adjusted by technicians in the field according to actual scenes, so that the purposes of managing similar object terminals in batches and improving the management efficiency can be achieved through the set sub-accounts corresponding to the configuration dimensions, wherein the types of the similar object terminals are different along with the different configuration dimensions, so that the similar object terminals can be conveniently aggregated according to the different dimensions, and the management is more flexible and diversified.

The foregoing description is only an overview of the technical solutions of the embodiments of the present invention, and the embodiments of the present invention can be implemented according to the content of the description in order to make the technical means of the embodiments of the present invention more clearly understood, and the detailed description of the embodiments of the present invention is provided below in order to make the foregoing and other objects, features, and advantages of the embodiments of the present invention more clearly understandable.

Drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the embodiments of the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:

fig. 1 is a flowchart illustrating an object management method based on multiple object sides according to an embodiment of the present invention;

FIG. 2 is a flowchart illustrating a method for managing objects based on multiple object sides according to another embodiment of the present invention;

fig. 3 is a schematic structural diagram of an object management apparatus based on multiple object sides according to an embodiment of the present invention;

fig. 4 is a schematic structural diagram of an electronic device provided in an embodiment of the present invention;

FIG. 5 shows a schematic diagram of the relationship between an object body, a plurality of sets of object dimensions, and an object end.

Detailed Description

Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

Fig. 1 shows a flowchart of an object management method based on multiple object sides according to an embodiment of the present invention. As shown in fig. 1, the method comprises the steps of:

step S110: and in response to the received main body creating request, creating an object main body and generating a primary account number corresponding to the object main body.

Specifically, the execution agent in this embodiment may be a server, and accordingly, the agent creation request is triggered by a client corresponding to the server. The main body creating request contains various data information related to the main body, and correspondingly, the server side creates an object main body according to the data information contained in the main body creating request. Wherein, the object subject means: an online virtual subject corresponding to the physical object. In this step, a primary account number corresponding to the subject is further generated. The primary account is used for realizing management operation aiming at the object subject.

Step S120: the method comprises the steps of obtaining configuration dimensions contained in a received set configuration request, creating an object dimension set which is subordinate to an object main body and corresponds to the configuration dimensions, and generating set sub-accounts which are subordinate to a primary account and correspond to the object dimension set.

Wherein the set configuration request is typically triggered by the client for creating a set of object dimensions corresponding to the specified configuration dimensions. The configuration dimension included in the set configuration request is used to represent a generation dimension of the object dimension set, and specifically may be a region dimension, an object identification dimension, a time interval dimension, and other dimensions. Accordingly, the set of object dimensions refers to: and generating a set matched with the configuration dimension according to the corresponding configuration dimension. The object dimension set is used for storing a plurality of homogeneous object ends in the same dimension. For example, if the configuration dimension is a region dimension, the set of object dimensions is used to store each object side in the same region.

In addition, in this step, a set sub-account which is subordinate to the primary account and corresponds to the object dimension set is further generated, and the set sub-account is used for implementing a management operation for the object dimension set.

Step S130: and configuring a plurality of object terminals affiliated to the object dimension set according to the received object configuration request, and respectively generating object sub-account numbers affiliated to the primary account number and corresponding to the object terminals.

And the object configuration request is used for configuring each object end belonging to the object dimension set. Specifically, a pre-generated object end may be added to a corresponding object dimension set, so as to implement unified management of multiple homogeneous object ends through the object dimension set.

In addition, an object sub-account belonging to the primary account and corresponding to each object is generated for each object. The object sub account is used for realizing management operation aiming at an object end.

Step S140: and managing an object main body, an object dimension set and each object terminal belonging to the object dimension set through the primary account number, the set sub-account number and the object sub-account number respectively.

Specifically, different account numbers correspond to different entity contents, so that different entities can be managed through different account numbers. For example, the management can be performed for the object subject through the primary account number; the object dimension set can be managed through the set sub-account, and then all object ends under the object dimension set are managed in a unified mode; the management can be carried out aiming at a specific object side through the object sub account. Therefore, management operations with different granularities can be realized through different accounts.

Therefore, the object management method based on the plurality of object ends provided by the embodiment of the invention can generate the object dimension set corresponding to the configuration dimension based on the object main body, so that the plurality of similar object ends are uniformly managed based on the object dimension set. The configuration dimensions can be flexibly set according to the characteristics of the object main body, and the specific content and the specific number of the configuration dimensions can be flexibly adjusted by technicians in the field according to actual scenes, so that the purposes of managing similar object terminals in batches and improving the management efficiency can be achieved through the set sub-accounts corresponding to the configuration dimensions, wherein the types of the similar object terminals are different along with the different configuration dimensions, so that the similar object terminals can be conveniently aggregated according to the different dimensions, and the management is more flexible and diversified.

Fig. 2 is a flowchart illustrating a method for object management based on multiple object sides according to another embodiment of the present invention. As shown in fig. 2, the method comprises the steps of:

step S210: and in response to the received main body creating request, creating an object main body and generating a primary account number corresponding to the object main body.

Specifically, the execution main body in this embodiment is a server, and the main body creation request is triggered by a client corresponding to the server. The main body creating request contains various data information related to the main body, and correspondingly, the server side creates an object main body according to the data information contained in the main body creating request. Wherein, the object subject means: an online virtual subject corresponding to the physical object.

In specific implementation, in order to ensure the compliance of the object body, the object body data information contained in the body creation request is further acquired and verified, and if the verification is passed, the object body corresponding to the body data information is created; and if the verification fails, returning a prompt message. The main data information may be various forms such as main qualification data information, main description data information, and the like.

In this step, a primary account number corresponding to the subject is further generated. The primary account is used for realizing management operation aiming at the object subject. The object body is a core for realizing unified management of a plurality of object ends.

Step S220: the method comprises the steps of obtaining configuration dimensions contained in a received set configuration request, creating an object dimension set which is subordinate to an object main body and corresponds to the configuration dimensions, and generating set sub-accounts which are subordinate to a primary account and correspond to the object dimension set.

Wherein the set configuration request is typically triggered by the client for creating a set of object dimensions corresponding to the specified configuration dimensions. The configuration dimension included in the set configuration request is used to represent a generation dimension of the object dimension set, and specifically may be a region dimension, an object identification dimension, a time interval dimension, and other dimensions. Accordingly, the set of object dimensions refers to: and generating a set matched with the configuration dimension according to the corresponding configuration dimension. The object dimension set is used for storing a plurality of homogeneous object ends in the same dimension. In addition, in this step, a set sub-account which is subordinate to the primary account and corresponds to the object dimension set is further generated, and the set sub-account is used for implementing a management operation for the object dimension set.

Optionally, in order to facilitate the user to configure different sets from multiple dimensions, in this embodiment, the configuration dimensions included in the set configuration request may be multiple, and accordingly, when an object dimension set that is subordinate to the object subject and corresponds to the configuration dimensions is created, and set sub-accounts that are subordinate to the primary account and correspond to the object dimension set are generated, multiple object dimension sets that are subordinate to the object subject and correspond to respective configuration dimensions are created, and multiple set sub-accounts that are subordinate to the primary account and correspond to the object dimension sets of respective configuration dimensions are generated.

For example, the configuration dimensions contained in the aggregate configuration request include: a time period dimension, and a territorial dimension. Correspondingly, a time interval object dimension set which is subordinate to the primary account and corresponds to the time interval dimension is created, and a time interval set sub-account is generated; and creating a region object dimension set which belongs to the primary account and corresponds to the region dimension, and generating a region set sub-account. The time interval object dimension set is used for uniformly managing a plurality of object ends corresponding to the same time interval, the region object dimension set is used for uniformly managing a plurality of object ends corresponding to the same region, and different sets are respectively managed through different set sub-accounts.

Optionally, in a specific example, the object subject is a store subject (specifically, a registered merchant may be used), the object terminal is a store terminal, and the store terminal mainly refers to a network terminal for managing data information in a store; accordingly, the configuration dimensions contained in the aggregate configuration request include at least one of: a brand store configuration dimension, a chain store configuration dimension, a group store configuration dimension, and a regional store configuration dimension; and the set of object dimensions corresponding to the configuration dimensions includes at least one of: a brand dimension set, a linkage dimension set, a clique dimension set, and a region dimension set. The system comprises a brand dimension set, a chain dimension set, a group dimension set and a region dimension set, wherein the brand dimension set is used for uniformly managing a plurality of object ends corresponding to the same store brand, the chain dimension set is used for uniformly managing a plurality of object ends corresponding to the same chain store, the group dimension set is used for uniformly managing a plurality of object ends corresponding to the same group, and the region dimension set is used for uniformly managing a plurality of object ends corresponding to the same region. Correspondingly, the brand dimension set has corresponding brand set sub-accounts, the chain dimension set has corresponding chain set sub-accounts, the group dimension set has corresponding group set sub-accounts, and the region dimension set has corresponding region set sub-accounts.

Step S230: and configuring a plurality of object terminals affiliated to the object dimension set according to the received object configuration request, and respectively generating object sub-account numbers affiliated to the primary account number and corresponding to the object terminals.

And the object configuration request is used for configuring each object end belonging to the object dimension set. Specifically, a pre-generated object end may be added to a corresponding object dimension set, so as to implement unified management of multiple homogeneous object ends through the object dimension set. In addition, an object sub-account belonging to the primary account and corresponding to each object is generated for each object. The object sub account is used for realizing management operation aiming at an object end.

Specifically, the object configuration request is used to add the generated object ends to the object dimension sets, where when the number of the object dimension sets is multiple, the object ends included in different object dimension sets may intersect. For example, for object end one, it may belong to both the first set of object dimensions and the second set of object dimensions.

In addition, the object configuration request can be further subdivided into two types, namely an object initial configuration request and an object change configuration request. Wherein the object initial configuration request is used for adding an isolated object end which is not contained in any object dimension set into at least one object dimension set. The object change configuration request is used for removing the object end which is already contained in at least one object dimension set from the at least one object dimension set or further moving the object end to another object dimension set. In specific implementation, the corresponding relationship between each object end and the corresponding object dimension set needs to be recorded in a background database.

For ease of understanding, FIG. 5 shows a schematic diagram of the relationship between the subject of an object, a plurality of sets of object dimensions, and the ends of an object. As shown in fig. 5, the object body includes: a first set of object dimensions, a second set of object dimensions, and a third set of object dimensions. Wherein the first set of object dimensions comprises: an object end A, an object end B and an object end C; the second set of object dimensions includes: an object side D and an object side E; the third set of object dimensions includes: an object side F, and an object side G.

Step S240: the method comprises the steps of obtaining an account identification contained in a received account management request, determining a data range corresponding to the account identification, carrying out aggregation processing on data content matched with the data range to obtain an account data set corresponding to the account identification, and executing management operation according to the account data set.

Specifically, a user triggers an account management request by logging in an account, and accordingly, the account management request includes an account identifier. The account management request may be triggered by a primary account, a set sub-account, or an object sub-account, and accordingly, the account identifier may be an account identifier of the primary account, an account identifier of the set sub-account, or an account identifier of the object sub-account, which is described below for each possible case:

in a possible implementation manner, if the account management request is triggered by a primary account, an account identifier included in the account management request corresponds to the primary account, and accordingly, a data range corresponding to the account identifier includes: a subject data range matching a subject corresponding to the primary account number, and an account number data set corresponding to the account number identification includes: a subject account data set corresponding to the subject. Wherein, the main data range refers to: and aggregating the data content matched with the main body data range in the data range corresponding to the data content corresponding to the object main body to obtain the full data content corresponding to the object main body, and using the full data content as a main account data set corresponding to the account identification of the primary account, thereby realizing various management operations on the object main body based on the main account data set. The main body data range usually covers the object main body and each object dimension set subordinate thereto and data of each object end in each object dimension set, so that the main body data range is wide, the main body data range covers the object main body and each set subordinate thereto and corresponding data of the object end, and accordingly, the primary account number can realize unified management for the object main body and each set subordinate thereto and the object end. Wherein the polymerization treatment means: gathering the same kind of data scattered in different storage positions. In this embodiment, data contents matching with a data range corresponding to an account id are mainly aggregated together to form an account data set corresponding to the account id. Therefore, the meaning of "aggregation" in this embodiment mainly refers to aggregating multiple data in a data range into the same data set, so as to facilitate the unified management of data. Of course, it will be understood by those skilled in the art that in the aggregation process, no additional processing may be performed on the data, but only the scattered data is aggregated into the same dataset; or, various additional processing such as deduplication, statistics, merging and/or analysis may be performed on the data, and then the processed data is gathered into the same data set, where the processing mode of the additional processing may be flexibly set by a person skilled in the art, redundant data can be removed by the additional processing, and even contents such as intermediate results of common operations can be added, so as to provide convenience for subsequent management operations. In summary, the embodiment of the present invention does not limit the specific meaning of the aggregation process, and may be a simple data aggregation operation, or may add some necessary processing procedures.

In another possible implementation manner, if the account management request is triggered by a set sub-account, an account identifier included in the account management request corresponds to the set sub-account, and accordingly, a data range corresponding to the account identifier includes: a set data range that matches the set of object dimensions corresponding to the set sub-accounts, and the set of account data corresponding to the account identification includes: a set account dataset corresponding to the set of object dimensions. Wherein, the aggregate data range refers to: and aggregating the data content matched with the set data range in the data range corresponding to the data content corresponding to the object dimension set to obtain the full data content corresponding to the object dimension set, and using the full data content as a set account data set corresponding to the account identification of the set sub-account, thereby realizing various management operations on the object dimension set based on the set account data set. The set data range usually covers the object dimension set and the data of each object end contained in the set data range. Therefore, although the set data range is smaller than the main data range, the set data range still covers the object dimension set and the corresponding data of each object terminal included in the object dimension set, and accordingly, the set sub-account can achieve unified management on the object dimension set and each object terminal included in the object dimension set.

In another possible implementation manner, if the account management request is triggered by the object sub-account, the account identifier included in the account management request corresponds to the object sub-account, and accordingly, the data range corresponding to the account identifier includes: the object data range matched with the object end corresponding to the object sub-account, and the account data set corresponding to the account identification comprises: and the object account data set corresponds to the object end. Wherein, the object data range refers to: and aggregating the data content matched with the target data range in the data range corresponding to the data content corresponding to the target end to obtain the full data content corresponding to the target end, and using the full data content as a target account data set corresponding to the account identification of the target sub-account, thereby realizing various management operations on the target end based on the target account data set. The object data range usually covers the data of the object end, so that the object data range is smaller than the set data range and only covers the corresponding data of the current object end, and accordingly, the object sub-account can achieve unified management for the current object end.

Therefore, by the method, data aggregation operation with different granularities can be realized according to the data ranges corresponding to different types of user accounts. The data range corresponding to the primary account number is wide, and data aggregation operation with the largest granularity can be achieved; the data range corresponding to the target sub-account is narrow, and the data aggregation operation with the minimum granularity can be realized; the data range corresponding to the set sub-account is between the first two, and data aggregation operation with moderate granularity can be achieved, so that unified management of all object ends contained in the object dimension set can be achieved through the set sub-account.

In the present embodiment, the operation type of the management operation may be various, thereby implementing different types of management. Correspondingly, when the management operation is executed according to the account data set, the method is realized by the following steps: acquiring a management type identifier contained in an account management request; and executing the management operation matched with the management type identification aiming at the account data set. The user can trigger account management requests of different types through different management operation entries, and accordingly the management type identifier includes: a data processing type identifier, an electronic ticket issuance type identifier, and/or an activity creation type identifier. The account management request containing the data processing type identifier is used for realizing data processing operations, such as data modification, deletion, updating and the like, aiming at the account data set; the account management request containing the electronic ticket issuing type identifier is used for achieving the purpose of issuing the electronic tickets in the range corresponding to the account data set, for example, when the account data set is a set account data set, the electronic tickets can be issued uniformly for all object terminals in the object dimension set; the account management request containing the activity creation type identifier is used for achieving the purpose of creating the activity in the range corresponding to the account dataset, for example, when the account dataset is a set account dataset, the activity can be uniformly created for each object terminal in the object dimension set.

In addition, in order to facilitate flexible configuration of roles and permissions of user accounts, in the embodiment, after a set sub-account which is subordinate to the primary account and corresponds to the object dimension set is generated, set account role information of the set sub-accounts and set account permission data corresponding to the set account role information are further configured; correspondingly, after object sub-accounts which are subordinate to the primary account and correspond to the object terminals are respectively generated, object account role information of the object sub-accounts and object account permission data corresponding to the object account role information are further configured. In a similar way, the primary account role information of the primary account and the primary account permission data corresponding to the primary account role information can be further configured for the primary account. Therefore, the account role information in the embodiment includes: the primary account role information, the aggregate account role information and the object account role information are described above. Accordingly, the account rights data includes: primary account permission data, aggregate account permission data, and object account permission data. The account role information is used to indicate a user role of a management user corresponding to the account, and for example, the account role information may include: the method comprises the following steps that a plurality of role types such as a service role, an operation role, an accounting role and the like are adopted, and account number authority data corresponding to each role type are different. For example, account permission data corresponding to an account of a service role mainly refers to various permissions associated with providing services, including: access rights of the service, etc.; for another example, the account authority data corresponding to the account of the accounting role mainly refers to various authorities associated with accounting, including: account access rights, etc. In a word, different account roles and account permissions are allocated, so that different permissions can be allocated to users with different roles, and the purpose of flexible management is achieved.

One account corresponds to one role, and correspondingly, for the same object subject, a plurality of primary accounts respectively corresponding to different account roles can be provided; similarly, for the same object dimension set, there may be a plurality of set sub-accounts respectively corresponding to different account roles; and, for the same object side, there may be a plurality of object sub-accounts respectively corresponding to different account roles. Therefore, in an optional implementation manner, a plurality of set sub-accounts corresponding to the object dimension set are provided, and the plurality of set sub-accounts correspond to different set account role information and set account permission data respectively; and the object sub-accounts corresponding to the object terminals are multiple, and the multiple object sub-accounts correspond to different object account role information and different object account permission data respectively.

Correspondingly, in the above process, the data range corresponding to the account id is further determined according to the account role information corresponding to the account id. For example, if the role of the account is accounting, the corresponding data range mainly refers to the data range related to the accounting operation; for example, if the role of the account is a service role, the corresponding data range mainly refers to a data range related to providing a service. For example, for a subject data range matching a subject corresponding to a primary account number, if the role of the primary account number is an accounting role, the corresponding subject data range mainly refers to a data range related to an accounting operation.

In addition, in this embodiment, the account and the entities such as the subject object, the set, or the object side do not have a strong binding relationship, and accordingly, a person skilled in the art can flexibly adjust the account information of each entity. Specifically, after generating a set sub-account which is subordinate to the primary account and corresponds to the set of object dimensions, the method further includes: storing the mapping relation between the set sub-account and the object dimension set into a preset account mapping table; and after object sub-accounts which are subordinate to the primary account and correspond to the object terminals are respectively generated, the mapping relation between the object sub-accounts and the object terminals is further stored in an account mapping table. Accordingly, in this embodiment, the set sub-account and/or the object sub-account can be changed, and the account mapping table can be updated. For example, set sub-accounts corresponding to a plurality of roles can be newly added for a certain object dimension set, only the account mapping table needs to be modified, and the system does not need to be adjusted greatly, so that convenience is provided for flexible configuration of the accounts.

Finally, the above embodiments are described taking a specific example as an example for ease of understanding. In this example, the object side is a store side, the object subject is a merchant, and the configuration dimensions include: brand dimensions, linkage dimensions, and group dimensions. Correspondingly, for the registered target merchants, a brand dimension set, a chain dimension set and a group dimension set correspond to each other. The brand dimension set comprises a plurality of store ends belonging to the same brand, the chain dimension set comprises a plurality of store ends belonging to the same chain organization, and the group dimension set comprises a plurality of store ends belonging to the same group. Accordingly, each dimension set can be managed in terms of the corresponding dimension. The account permission data of various accounts comprises at least one of the following data: daily operation management authority, signing authority, settlement authority, fund authority, batch operation authority, offline visiting authority and the like. The user can log in a background database corresponding to the set through a set sub-account corresponding to the brand dimension set, so that the related data of each object terminal subordinate to the brand dimension set is accessed. It can be seen that in this example, the set of brand dimensions corresponds to a virtual organization through which multiple store ends affiliated with the same brand are grouped together and managed uniformly. Accordingly, unified management for a plurality of store ends can be achieved through the set sub-accounts corresponding to the brand dimension set, and moreover, roles and permissions of different accounts can be flexibly configured according to actual needs. And, store related data corresponding to the brand dimension set are aggregated together, so that the data content of each store in the same brand dimension set is conveniently and uniformly viewed.

In a traditional mode, a plurality of stores are independent from one another or managed according to regional positions, so that stores of the same brand cannot be managed in a unified mode through unified accounts. Further, the chain hierarchy between stores determined by the regional position is often disordered, and cannot be associated with information such as the brand of the store, thereby causing confusion in store management. In addition, a strong binding relationship exists between the account system and the chain hierarchy of the existing store, so that the purpose of flexibly allocating accounts cannot be realized, the cost of modifying the account system is high, and the account modification is inconvenient. However, in this example, a virtual organization is constructed by a set of object dimensions, the dimensional configuration of which can be flexibly specified by a user, e.g., the set of object dimensions can be flexibly constructed from a variety of dimensions, such as brands, chains, and the like. Correspondingly, on the basis of the object dimension set, flexible allocation of accounts is achieved through a main account system and a sub account system, and corresponding store data can be aggregated according to the setting of the object dimension set. As can be seen from this, since both the account and the data can be flexibly arranged based on the object dimension set, store resources such as electronic tickets can be arranged in units of the object dimension set. For example, an electronic ticket can be sent to each store end subordinate to the electronic ticket through a set sub-account corresponding to the brand dimension set, so that the electronic ticket can be uniformly verified and sold at each store end subordinate to the same brand dimension set.

In order to facilitate management, store IDs of the store ends in the e-commerce platform can be bound with object sub-accounts created for the store ends, so that unified management of stores in the e-commerce platform can be achieved through the object sub-accounts of the store ends, the store management efficiency is improved, and especially the management cost can be greatly reduced when a chain of stores is numerous or a brand belongs to multiple stores.

In addition, as mentioned above, each account has corresponding account role information and account authority information, for example, the primary account has primary account role information and primary account authority information for defining the role and authority content of the primary account; the set sub-account has set account role information and set account permission information and is used for limiting roles and permission contents of the set account; the object sub-account has object account role information and object account authority information, and is used for limiting the role and authority content of the object account. In order to facilitate flexible management, the authority data configured for the account can be further changed through an account authority change request. For example, the upper-level account can send an authority change instruction to at least one corresponding lower-level account, so that the authority of the lower-level account is changed; for another example, the lower-level account can send an authority change request to the corresponding upper-level account to request the upper-level account to assign a new authority or cancel part of the authority.

In one embodiment, the higher-level account may directly grant permission to one or more subordinate accounts. The primary account number can temporarily authorize all or part of authority content contained in the authority data of the primary account number to one or two subordinate collective sub-account numbers, so that the collective sub-account number with authority authorization has all or part of authority content of the primary account number, and further can replace the primary account number to perform part of management operations.

In yet another case, the lower-level account may send a permission application request to the upper-level account or other lower-level accounts with permission to expand the permission range of the lower-level account. For example, the first set sub-account can send a permission application request to the second set sub-account, so that the second set sub-account grants all or part of the permissions to the first set sub-account (the first set sub-account and the second set sub-account are mutually flat accounts). Specifically, when the first set sub-account needs to be combined with the second set sub-account to jointly create a coupon sending activity or other types of activities, the first set sub-account and the second set sub-account can temporarily have a common management authority in an authority expansion mode, so that various activities can be created in a customized range conveniently.

In addition, the primary account number can also copy the active content created in the first set of sub-account numbers to the second set of sub-account numbers, so that the same active content can be implemented in each store under the first set of sub-account numbers and each store under the second set of sub-account numbers at the same time. In addition, the first set sub-account may also send an activity sharing request to the second set sub-account, so that the activities created in the first set sub-account are shared to the second set sub-account, and the same activity content can be implemented in each store under the first set sub-account and each store under the second set sub-account at the same time.

The primary account is a superior account of a set sub-account and an object sub-account, and the set sub-account is a superior account of the object sub-account; similarly, the set sub-account and the target sub-account are subordinate accounts of the primary account, and the target sub-account is a subordinate account of the set sub-account. In addition, the first set of sub-accounts is any set of sub-accounts, and the second set of sub-accounts is any set of sub-accounts different from the first set of sub-accounts.

Therefore, the embodiment can flexibly create activities in stores in various ranges in a temporary authority authorization mode, and accordingly unified management can be conveniently carried out according to the self-defined store range.

In summary, in this embodiment, the purpose of configuring the object sets from the configuration dimensions can be flexibly achieved through a virtual organization of the object dimension sets, so that the data of the object ends can be uniformly aggregated through the object dimension sets. Moreover, through the main and sub account systems, each object dimension set and each object terminal can flexibly create a plurality of accounts with different roles and configure different permissions for the accounts of the roles respectively, so that flexible management of different organizational structures is realized. In addition, the embodiment can verify the data information of the object subject to prevent the problem that the object subject which is not in compliance enters the system, thereby improving the management and control of the object subject.

Fig. 3 is a schematic structural diagram illustrating an object management apparatus based on multiple object sides according to an embodiment of the present invention. As shown in fig. 3, the apparatus includes:

a subject creation module 31 adapted to create an object subject in response to a received subject creation request, and generate a primary account number corresponding to the object subject;

a set configuration module 32, adapted to obtain a configuration dimension included in the received set configuration request, create an object dimension set that is subordinate to the object subject and corresponds to the configuration dimension, and generate a set sub-account that is subordinate to the primary account and corresponds to the object dimension set;

the object configuration module 33 is adapted to configure a plurality of object terminals affiliated to the object dimension set according to the received object configuration request, and respectively generate object sub-account numbers affiliated to the primary account number and corresponding to the object terminals;

and the management module 34 is adapted to manage the object subject, the object dimension set, and each object terminal belonging to the object dimension set through the primary account number, the set sub-account number, and the object sub-account number, respectively.

Optionally, the management module is specifically adapted to:

Optionally, the set configuration module is further adapted to:

and, the apparatus further comprises:

Optionally, the subject creation module is specifically adapted to:

The specific structure and the working principle of each module may refer to the description of the corresponding part of the method embodiment, and are not described herein again.

Therefore, the object management device based on the plurality of object ends provided by the embodiment of the invention can generate the object dimension set corresponding to the configuration dimension based on the object main body, so that the plurality of similar object ends are uniformly managed based on the object dimension set, and the aims of managing the similar object ends in batch and improving the management efficiency are fulfilled.

An embodiment of the present invention provides a non-volatile computer storage medium, where the computer storage medium stores at least one executable instruction, and the computer executable instruction may execute an object management method based on multiple object ends in any method embodiment described above.

The executable instructions may be specifically configured to cause a processor to perform the operations in the above-described method embodiments.

Fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present invention, and the specific embodiment of the present invention does not limit the specific implementation of the electronic device.

As shown in fig. 4, the electronic device may include: a processor (processor)402, a Communications Interface 404, a memory 406, and a Communications bus 408.

Wherein: the processor 402, communication interface 404, and memory 406 communicate with each other via a communication bus 408. A communication interface 404 for communicating with network elements of other devices, such as clients or other servers. The processor 402 is configured to execute the program 410, and may specifically perform the relevant steps in the embodiment of the object management method based on multiple object sides.

In particular, program 410 may include program code comprising computer operating instructions.

The processor 402 may be a central processing unit CPU or an application Specific Integrated circuit asic or one or more Integrated circuits configured to implement embodiments of the present invention. The electronic device comprises one or more processors, which can be the same type of processor, such as one or more CPUs; or may be different types of processors such as one or more CPUs and one or more ASICs.

And a memory 406 for storing a program 410. Memory 406 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.

The program 410 may be specifically configured to cause the processor 402 to perform the operations in the above-described method embodiments.

The algorithms or displays presented herein are not inherently related to any particular computer, virtual system, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. In addition, embodiments of the present invention are not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of embodiments of the present invention as described herein, and any descriptions of specific languages are provided above to disclose preferred embodiments of the invention.

In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the embodiments of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that is, the claimed embodiments of the invention require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will appreciate that while some embodiments herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.

The various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functionality of some or all of the components according to embodiments of the present invention. Embodiments of the invention may also be implemented as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing embodiments of the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.

It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. Embodiments of the invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names. The steps in the above embodiments should not be construed as limiting the order of execution unless specified otherwise.

Claims

1. An object management method based on a plurality of object sides comprises the following steps:

managing the object main body, the object dimension set and each object terminal belonging to the object dimension set through the primary account number, the set sub-account number and the object sub-account number respectively; managing different entities through different accounts, realizing data aggregation operation with different granularities according to data ranges corresponding to different types of user accounts, and executing management operation based on the obtained account data set corresponding to the account identification; the method comprises the steps of obtaining an account identification contained in a received account management request, determining a data range corresponding to the account identification, carrying out aggregation processing on data content matched with the data range to obtain an account data set corresponding to the account identification, and executing management operation according to the account data set.

2. The method according to claim 1, wherein when the account id included in the account management request corresponds to the primary account, the data range corresponding to the account id includes: a subject data range matching a subject corresponding to a primary account number, and an account number data set corresponding to the account number identification includes: a subject account data set corresponding to the subject;

3. The method of claim 1, wherein the performing management operations according to the account data set comprises:

4. The method of claim 3, wherein the management type identification comprises: a data processing type identifier, an electronic ticket issuance type identifier, and/or an activity creation type identifier.

5. The method of any one of claims 1 to 4, wherein after generating a set sub-account number belonging to the primary account number and corresponding to the set of object dimensions, the method further comprises:

6. The method of claim 5, wherein the data range corresponding to the account identifier is further determined according to account role information corresponding to the account identifier; the account role information comprises: the aggregate account role information and/or the object account role information.

7. The method of claim 5, wherein the set sub-accounts corresponding to the set of object dimensions are multiple, and the multiple set sub-accounts correspond to different set account role information and set account permission data respectively; and the object sub-accounts corresponding to the object terminals are multiple, and the multiple object sub-accounts correspond to different object account role information and different object account permission data respectively.

8. The method according to any one of claims 1 to 4, wherein the configuration dimensions included in the set configuration request include a plurality of configuration dimensions, and the creating a set of object dimensions belonging to the subject of the object and corresponding to the configuration dimensions, and the generating a set sub-account belonging to the primary account and corresponding to the set of object dimensions includes:

9. The method of any of claims 1-4, wherein the subject entity is a store entity and the subject end is a store end; the configuration dimensions contained in the set configuration request include at least one of: a brand store configuration dimension, a chain store configuration dimension, a group store configuration dimension, and a regional store configuration dimension;

10. The method of any one of claims 1 to 4, wherein after generating a set sub-account number belonging to the primary account number and corresponding to the set of object dimensions, the method further comprises: storing the mapping relation between the set sub-account and the object dimension set into a preset account mapping table;

11. The method of any of claims 1-4, wherein creating an object body in response to a received body creation request comprises:

12. An object management device based on a plurality of object sides comprises:

the management module is suitable for managing the object main body, the object dimension set and each object terminal belonging to the object dimension set through the primary account number, the set sub-account number and the object sub-account number respectively; managing different entities through different accounts, realizing data aggregation operation with different granularities according to data ranges corresponding to different types of user accounts, and executing management operation based on the obtained account data set corresponding to the account identification; the method comprises the steps of obtaining an account identification contained in a received account management request, determining a data range corresponding to the account identification, carrying out aggregation processing on data content matched with the data range to obtain an account data set corresponding to the account identification, and executing management operation according to the account data set.

13. The apparatus according to claim 12, wherein when the account id included in the account management request corresponds to the primary account, the data range corresponding to the account id includes: a subject data range matching a subject corresponding to a primary account number, and an account number data set corresponding to the account number identification includes: a subject account data set corresponding to the subject;

14. The apparatus of claim 12, wherein the management module is specifically adapted to:

15. The apparatus of claim 14, wherein the management type identification comprises: a data processing type identifier, an electronic ticket issuance type identifier, and/or an activity creation type identifier.

16. The apparatus of any of claims 12-15, wherein the set configuration module is further adapted to:

17. The apparatus of claim 16, wherein the data range corresponding to the account identifier is further determined according to account role information corresponding to the account identifier; the account role information comprises: the aggregate account role information and/or the object account role information.

18. The device of claim 16, wherein the set sub-accounts corresponding to the set of object dimensions are multiple, and the multiple set sub-accounts correspond to different set account role information and set account permission data, respectively; and the object sub-accounts corresponding to the object terminals are multiple, and the multiple object sub-accounts correspond to different object account role information and different object account permission data respectively.

19. The apparatus according to any of claims 12-15, wherein the configuration dimensions included in the aggregate configuration request include a plurality, and the aggregate configuration module is specifically adapted to:

20. The apparatus according to any one of claims 12-15, wherein the subject entity is a store entity and the subject end is a store end; the configuration dimensions contained in the set configuration request include at least one of: a brand store configuration dimension, a chain store configuration dimension, a group store configuration dimension, and a regional store configuration dimension;

21. The apparatus of any of claims 12-15, wherein the set configuration module is further adapted to: storing the mapping relation between the set sub-account and the object dimension set into a preset account mapping table;

and, the apparatus further comprises:

22. The apparatus according to any of claims 12-15, wherein the subject creation module is specifically adapted to:

23. An electronic device, comprising: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;

the memory is used for storing at least one executable instruction, and the executable instruction causes the processor to execute the operation corresponding to the object management method based on multiple object ends in any one of claims 1-11.

24. A computer storage medium having at least one executable instruction stored therein, the executable instruction causing a processor to perform operations corresponding to the multiple object side based object management method according to any one of claims 1-11.