WO2025036016A1 - Benefit information display method and electronic device - Google Patents

Abstract

Disclosed in embodiments of the present application are a benefit information display method and an electronic device. The method comprises: acquiring a benefit data definition template, wherein the benefit data definition template comprises a plurality of data fields; acquiring data display rule information respectively corresponding to a plurality of benefit items; on the basis of the benefit data definition template, storing data of a user respectively on the plurality of data fields of the plurality of benefit items; and in response to a benefit information viewing request initiated by a target user, reading, from the stored information, data of the target user on the plurality of data fields of the plurality of benefit items, and assembling the data into display content respectively corresponding to the plurality of benefit items, so as to display, in a target page, the display content respectively corresponding to the plurality of benefit items. By means of the embodiments of the present application, information of a plurality of different benefit items can be displayed in an aggregated manner by means of a same page, and low development cost and high expandability are achieved.

Description

Method and electronic device for displaying equity information

This application claims the priority of the Chinese patent application filed with the China Patent Office on August 14, 2023, with application number 202311015911.7 and application name “Method and electronic device for displaying rights and interests information”, all contents of which are incorporated by reference in this application.

Technical Field

The present application relates to the field of information technology, and in particular to a method and electronic device for displaying equity information.

Background Art

In many application systems, there is a membership system, and users can obtain more membership benefits by becoming a higher level member. For example, in the commodity information service system, a variety of different membership types can be provided for merchant users. At a higher membership level, merchants can obtain multiple membership benefits such as industry management guidance, priority for high-quality logistics services, and so on.

In the prior art, customer service staff usually introduces information such as the rights and interests that can be enjoyed under various membership levels to users. However, after the user becomes a member of the corresponding level, information about the rights and interests that can be used is usually revealed in multiple different scenarios. For example, when a merchant ships goods to overseas users, the user may be prompted that the merchant enjoys "sea shipping priority", etc. It can be seen that in this way, the user's perception and use of various rights and interests are in a relatively passive state. Therefore, many rights and interests may be difficult for users to use, or the frequency of use is very low, so that it is difficult to reflect the value that the corresponding membership level can actually bring to the user.

Summary of the invention

The present application provides a method and electronic device for displaying rights and interests information, which can aggregate and display information of multiple different rights and interests items on the same page, and has low development cost and high scalability.

This application provides the following solutions:

A method for displaying equity information, comprising:

Acquire a rights and interests data definition template, wherein the rights and interests data definition template includes a plurality of data fields, wherein the plurality of data fields include a data field related to basic information and a data field related to user usage;

Obtain data display rule information on data fields related to user usage corresponding to multiple benefit items under different user usage conditions;

According to the rights and interests data definition template, the data of the user in multiple data fields of multiple rights and interests items are saved, wherein the data in the data fields related to the user's usage is determined according to the user's rights and interests item usage information and the data display rule information;

In response to a request initiated by a target user to view rights and interests information, the data of the target user on multiple data fields of the multiple rights and interests items are read from the saved information and assembled into display contents corresponding to the multiple rights and interests items respectively, so as to display the display contents corresponding to the multiple rights and interests items respectively in the target page.

Among them, for fields related to user usage, different benefit items correspond to different candidate values on the same field;

The data display rule information specifically includes: the correspondence between the candidate values of the same benefit item in the same field and the user's usage, so as to determine the data to be displayed for the corresponding benefit item in the corresponding field from the candidate values of the corresponding benefit item in the corresponding field according to the usage information of the specific user.

The fields related to user usage include: description text and/or action items to be displayed when displaying benefit items;

The obtaining of data display rule information on data fields related to user usage corresponding to the plurality of rights and interests items under different user usage situations includes:

Obtaining description texts and/or action item display rule information corresponding to a plurality of benefit items under different user usage situations; wherein each benefit item corresponds to a different candidate text and/or candidate action item, and the data display rule information includes: a correspondence between each candidate text and/or candidate action item of the same benefit item and the user usage situation;

The step of saving data of multiple users in multiple data fields of multiple rights and interests items according to the rights and interests data definition template includes:

Obtain usage information of the multiple benefit items by multiple users respectively, and determine the corresponding description text and/or action items to be displayed when displaying the benefit items to each user based on the usage information and the data display rules, and save them as data in the corresponding data fields.

The action item information includes the name of the action item and a jump address, so as to jump to a corresponding page according to the jump address to obtain detailed information related to the benefit item, or to perform processing related to the benefit item.

If the target user has used the benefit item, the description text includes: the number of times the target user has used the benefit item, the remaining number of times and/or the information on the use effect obtained.

If the target user has not used the benefit item, the description text includes: functional description summary information about the benefit item.

Among them, by executing the scheduled task, the usage information of the multiple rights and interests items of multiple users is obtained, and according to the usage information and the data display rules, the data on the data field related to the user's usage is determined when the rights and interests items are displayed to each user.

The rights and interests data definition template includes: a first template and a second template, wherein the first template is used to define data fields related to the rights and interests items and basic information, and the second template is used to define data fields related to multiple rights and interests items and user usage conditions;

The step of saving data of multiple users in multiple data fields of multiple rights and interests items according to the rights and interests data definition template includes:

According to the first template, data on the data fields of the plurality of equity items and the basic information are saved as equity configuration information;

According to the second template, data on the data fields related to the plurality of benefit items and user usage are saved as benefit usage related data information;

When responding to the request for viewing the rights and interests information initiated by the target user, it includes:

Acquire data of the plurality of equity items in data fields related to the basic information from the equity configuration information;

Acquire data of the target user on data fields related to user usage of the plurality of benefit items from the benefit usage related data;

The data of the multiple rights and interests items in the data fields related to the basic information and the data of the data fields related to the user usage are assembled to generate display contents corresponding to the multiple rights and interests items respectively.

The step of obtaining data of the plurality of equity items in data fields related to basic information from the equity configuration information includes:

Determine the membership type information corresponding to the target user;

The data of the multiple rights and interests items corresponding to the member type in the data fields related to the basic information are obtained from the rights and interests configuration information.

Among them, different membership types correspond to different processor modules;

After determining the membership type information corresponding to the target user, the following further includes:

The corresponding processor module is determined according to the member type information, so that the processor module can read and assemble the data.

Wherein, the equity configuration information includes a sorting index field corresponding to the equity item;

The method further comprises:

According to the data on the sorting index field, the display contents corresponding to the multiple rights and interests items are sorted so as to be displayed in the target page in a corresponding order.

When a benefit item is added, deleted, or the information is updated, the benefit configuration information and/or benefit usage related data information are updated to update the displayed benefit item and/or the corresponding displayed content.

A method for displaying equity information, comprising:

Receive a request from a target user to view rights information;

Displaying a target page, wherein the target page includes display contents corresponding to a plurality of rights and interests items, respectively, and the display contents are generated by reading and assembling the data of the target user on a plurality of data fields of the plurality of rights and interests items by the same processor module;

The data of the target user on the multiple data fields of the multiple rights and interests items are determined according to the rights and interests data definition template, including data fields related to basic information and data fields related to user usage. The data in the data field related to the user's usage is determined based on the user's benefit item usage information and the data display rules.

The display contents corresponding to the multiple rights and interests items include:

The action item information corresponding to the equity item, the action item information including the name of the action item and the jump address, so as to jump to the corresponding page according to the jump address to obtain detailed information related to the equity item, or perform processing related to the equity item;

Among them, different benefit items correspond to different action items under the same user usage situation.

A device for displaying equity information, comprising:

A template acquisition unit, used to acquire a rights and interests data definition template, wherein the rights and interests data definition template includes a plurality of data fields, wherein the plurality of data fields include a data field related to basic information and a data field related to user usage;

A data display rule acquisition unit, used to acquire data display rule information on data fields related to user usage conditions corresponding to a plurality of benefit items under different user usage conditions;

A data acquisition unit, configured to save the data of the user in multiple data fields of multiple benefit items according to the benefit data definition template, wherein the data in the data field related to the user's usage is determined according to the user's benefit item usage information and the data display rule;

A display content construction unit is used to respond to a request for viewing rights information initiated by a target user, read the data of the target user on multiple data fields of the multiple rights items from the saved information, and assemble them into display contents corresponding to the multiple rights items respectively, so as to display the display contents corresponding to the multiple rights items respectively in the target page.

A device for displaying equity information, comprising:

A request receiving unit, used to receive a request initiated by a target user to view rights and interests information;

A page display unit, used for displaying a target page, wherein the target page includes display contents corresponding to a plurality of rights and interests items, respectively, and the display contents are generated by reading and assembling the data of the target user on a plurality of data fields of the plurality of rights and interests items by the same processor module;

Among them, the data of the target user in multiple data fields of the multiple rights and interests items are determined according to the rights and interests data definition template, including data fields related to basic information and data fields related to user usage. The data in the data fields related to user usage is determined based on the user's rights and interests item usage information and the data display rules.

A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of any of the methods described above.

An electronic device, comprising:

one or more processors; and

A memory associated with the one or more processors, the memory being used to store program instructions, wherein the program instructions, when read and executed by the one or more processors, execute the steps of any of the methods described above.

According to the specific embodiments provided in this application, this application discloses the following technical effects:

Through the embodiment of the present application, the display information of multiple different rights and interests items can be standardized and disassembled and extracted into a standardized template. In the template, the data that needs to be displayed corresponding to the rights and interests items can be split into data fields related to basic information and data fields related to user usage. At the same time, the data display rules on the fields related to user usage corresponding to multiple rights and interests items under different user usage conditions can also be configured. Afterwards, the data of the user on multiple data fields of multiple rights and interests items can be saved according to the rights and interests data definition template. Among them, the data on the fields related to user usage can be determined based on the user's usage information of the multiple rights and interests items and the aforementioned data display rules. In this way, after the target user initiates a request to view the rights and interests information, the data of the target user on multiple data fields of the multiple rights and interests items can be read from the saved information, and assembled into the display content corresponding to the multiple rights and interests items, so as to be displayed on the target page. In this way, the information of multiple different rights and interests items can be aggregated and displayed on the same page, and information related to user usage can be displayed. During the implementation process, although the information that needs to be conveyed in the same field for each benefit item may be different and related to the specific user's use of the corresponding benefit item, since the data fields corresponding to each benefit item are uniformly defined and the data to be displayed for different users in multiple fields of each benefit item can be obtained in advance, when it is necessary to display it to the user, it can be processed by the same processing logic to complete the data assembly. Accordingly, only the same set of processing logic needs to be developed to complete the display of multiple different benefit items, thereby achieving the purpose of reducing development costs.

In addition, when rights items are added, deleted, or information is updated, only the specific configuration information needs to be updated. For example, for newly added rights items, it is only necessary to configure the data on each field according to the aforementioned template. There is no need to develop new processing logic separately. Therefore, this solution has stronger scalability.

In a preferred implementation, the data related to the rights and interests item can also be split into two parts, namely, the data on the fields related to the basic information and the data on the fields related to the user's usage, and the first template and the second template are provided respectively. In this way, only the data on the fields related to the user's usage needs to be saved in the user dimension and dynamically updated, while the data on the fields related to the basic information only needs to be saved for each rights and interests item, and there is no need to save a copy for each user, thereby saving storage space.

Of course, any product implementing the present application does not necessarily need to achieve all of the advantages described above at the same time.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

FIG1 is a schematic diagram of a system architecture provided in an embodiment of the present application;

FIG2 is a flow chart of a first method provided in an embodiment of the present application;

FIG3 is a schematic diagram of a first interface provided in an embodiment of the present application;

FIG4 is a schematic diagram of a second interface provided in an embodiment of the present application;

FIG5 is a schematic diagram of a third interface provided in an embodiment of the present application;

FIG6 is a flow chart of a second method provided in an embodiment of the present application;

FIG7 is a schematic diagram of a first device provided in an embodiment of the present application;

FIG8 is a schematic diagram of a second device provided in an embodiment of the present application;

FIG. 9 is a schematic diagram of an electronic device provided in an embodiment of the present application.

DETAILED DESCRIPTION

The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the present application belong to the scope of protection of this application.

First of all, it should be explained that the inventors of the present application found in the process of implementing the embodiments of the present application that in the prior art, a special page is usually not provided to display what rights and interests can be enjoyed under a specific membership type, but are scattered on different pages. If a user (specifically a merchant user) needs to use or enable (including activation, configuration, authentication, etc.) a certain right or interest, it is necessary to find the entry for the use or activation of the corresponding right or interest through a multi-level directory before the corresponding operation can be performed.

In view of the above situation, in order to better provide users with information about rights and interests, and facilitate users to use specific rights and interests, in an embodiment of the present application, a specific page can be provided for users, in which information on a variety of rights and interests that can be enjoyed under a specific membership type can be aggregated and displayed. In addition, not only can basic information such as the name and introduction of each right and interest be displayed, but also corresponding description text (for example, whether it has been used, if it has been used, how the use effect is, etc.), related action item information and other information related to user usage can be provided according to the specific user's use of each right and interest. In this way, users can understand which rights and interests they have, whether they have been used, if they have been used, the corresponding use effect and other information through the same page. In addition, specific actions can be taken directly through the page, for example, including using, activating, and registering for a certain right and interest item, etc., without having to go to different pages to find the corresponding action entry.

However, in the process of implementing the above solution, the inventors of the present application discovered that for different users, due to the different usage of each benefit item, the corresponding copywriting, action items, etc. that need to be displayed will also be different. For example, if a user has used a benefit item, it means that the previous activation, authentication, and other processes have been completed and it can be used directly. Therefore, action items such as "go to use" can be directly provided; and if the user has not used a benefit item, it may be necessary to activate, authenticate, and other processes first. Therefore, options such as "deactivate" and "deauthenticate" can be displayed. On the other hand For different rights and interests, even if the user's usage status is the same, the specific copy and action items that need to be displayed to the user may be different. For example, for rights and interests A and B, a user has used these two rights and interests. However, for right and interest A, the copy that needs to be displayed may be "X goals to be completed", and for right and interest B, the copy that needs to be displayed may be "X have been reported this month", etc., where "X" needs to be determined according to the specific user's usage; or, for the two rights and interests C and D, a user has not used these two rights and interests, but the action item that needs to be displayed to the user for right and interest C may be "Go to register", and the action item that needs to be displayed to the user for right and interest D may be "Go to verify", etc.

In other words, if you need to display multiple different rights and interests items and corresponding data/action items related to user usage through a unified page, then since each rights and interests item needs to convey different information/action points to the user, the specific descriptions and action items may also be different. Therefore, the situation is more complicated and you need to consider how to implement it.

For example, a specific implementation method may be to define a processing class (also called a processor module) for each equity item to undertake the processing logic of each equity, including acquiring and processing the data of each equity item. However, since it is necessary to define processors for a variety of different equity items, each processor needs to output descriptions such as the equity item name, icon, whether it meets the standard, equity description text, and the remaining N equity items. In addition, it is also necessary to output different action items. Therefore, when the number of equity items is relatively large, the development cost will be relatively high; in addition, each new equity item requires a redefinition of a equity processing class, so the scalability of the solution will be relatively poor.

In order to reduce development costs and improve the scalability of the solution, a specific solution is also provided in an embodiment of the present application. In this solution, a unified processing class can be developed for multiple different rights and interests items, and the differentiated needs of different rights and interests items in display copy and action items can be met through the same processing logic. In order to achieve this goal, an embodiment of the present application can first provide a standardized rights and interests data definition template, in which multiple specific data fields can be defined, and different rights and interests items can share the unified template when being displayed. That is, the specific display content of each rights and interests item can be assembled from the data on each field in the specific template.

After configuring the data definition template, the data of each benefit item in each field can be configured in the user dimension according to the template for assembling specific display content. Among them, as mentioned above, since different benefit items may have different requirements when revealing descriptive text, action items and other information related to user usage even under the same user usage status, it is also possible to configure each benefit item with its own display rule. The display rule mainly refers to the data display rule information on the data field related to user usage corresponding to multiple benefit items under different user usage conditions. For example, since different benefit items correspond to different candidate values on the same field for the fields related to user usage, the specific data display rule information can be the correspondence between the candidate values of the same benefit item on the same field and the user usage. In this way, the data to be displayed for the corresponding benefit item on the corresponding field can be determined from the candidate values of the corresponding benefit item on the corresponding field according to the usage information of the specific user, and so on.

After configuring the specific rights data definition template and the aforementioned data display rule information, since it includes data fields related to the user's use of rights items, and these data may change continuously, therefore, under the preferred implementation, it is possible to obtain data related to the use of user-dimensional rights items from the corresponding data source (for example, a data base table that maintains user-dimensional feature data, such as the number of times a certain rights item is used, etc.) by executing a scheduled task, including whether a certain user has used a certain rights item, the specific effect of use, etc. After obtaining these data, it is possible to determine what kind of text needs to be displayed when displaying a specific rights item to the user, and which specific action item, etc., based on the display rule information corresponding to the specific rights item. These data can be saved in the form of a vertical table, etc., and updated regularly by the aforementioned scheduled tasks.

Since the data of each benefit item in multiple fields is maintained in the user dimension, when a specific target user needs to access a specific benefit center or other pages, the basic information of the specific benefit item and the data in the fields related to the user's usage can be read from the pre-saved data, and assembled into specific display content for display on the page. Since the various data fields in the above template are uniformly defined, although the content displayed on each field of each benefit item may be different, when it needs to be displayed to the user, it can be processed by the same processing logic to complete the data assembly. Therefore, only a unified processor module needs to be developed to complete the display of each different benefit item, so as to achieve the purpose of reducing development costs. In addition, when adding new benefit items, it is only necessary to configure or obtain the data on each field according to the above template, and there is no need to develop new processing logic separately. Therefore, this solution has stronger scalability. Of course, in actual applications, different processor modules can also be developed according to different member types, so that the same processor module can process the relevant data of multiple different benefit items corresponding to the same member type and perform assembly and other processing.

Among them, under the preferred implementation, since the specific rights and interests data may include some fields whose specific data is relatively fixed and will not change due to different users or different user usage, such as the name, icon and other basic information of the rights and interests item, the specific rights and interests data definition template can also be split into two parts, which are used to standardize the fields related to the basic information of the rights and interests items and the fields related to the user's usage. In this way, multiple users can share the same basic information about each rights and interests item, and only the data related to the user's usage needs to be dynamically constructed and saved separately by user. In this way, it is possible to avoid storing the basic information of each right and interest item separately for each user, thereby saving storage space.

From the perspective of system architecture, referring to Figure 1, the embodiments of the present application may involve the client and server of a specific application system, wherein, on the server side, specific rights and interests data definition templates may be mainly saved (specifically, a first template corresponding to the basic information field and a second template corresponding to the field related to user usage) and data display rule information on fields related to user usage corresponding to multiple rights and interests items under different user usage conditions may also be saved. Afterwards, the data of each rights and interests item in the basic information field may be obtained and saved, and the data of the user-dimensional rights and interests items in the fields related to user usage may be constructed by executing scheduled tasks and the like, and may be updated regularly. After a specific user initiates a request to view the rights and interests information through the client, the server may also By reading the data corresponding to each right item of the target user, and assembling it into specific display content, the content is provided to the client for display.

The specific implementation scheme provided in the embodiments of the present application is described in detail below.

Embodiment 1

First, from the perspective of the server, this embodiment 1 provides a method for displaying rights and interests information. Referring to FIG. 2 , the method may specifically include:

S201: Acquire a rights and interests data definition template, wherein the rights and interests data definition template includes a plurality of data fields, wherein the plurality of data fields include a data field related to basic information and a data field related to user usage.

The specific rights and interests data definition template can be used to define multiple data fields. The data on these data fields can be the relevant data used to construct the display content of the specific rights and interests item. For example, the specific data fields can include the name, icon, text, action item information, etc. of the rights and interests item.

Among them, as mentioned above, regarding the multiple data fields in the specific template, some fields may include some specific data that are relatively fixed and usually do not change due to different users or different user usage. These fields are usually used to define some basic information of specific rights and interests items, for example, the name and icon of the rights and interests item; in addition, some fields are also included, which are related to user usage, that is, what kind of data needs to be displayed in the corresponding fields, which changes dynamically according to the user's usage of the specific rights and interests item, for example, the copywriting to be displayed, the name of the action item, etc.

Therefore, in order to save storage space during specific implementation, the specific rights and interests data definition template can also be standardized and disassembled into a first template and a second template, wherein the first template is mainly used to define some relatively fixed basic information-related fields, and the second template is mainly used to define some fields related to user usage. In this way, the first template can be universal for different users, that is, for each rights and interests item, it is only necessary to maintain a unified configuration data according to the first template, including the name and icon of the rights and interests item (since the data on these fields will not change due to different users or different user usage, there is no need to configure a separate copy for each user). As for the fields related to user usage, that is, the fields whose specific data may change due to different user usage, a separate copy of the rights and interests data can be maintained for each user and saved by constructing a vertical table or other means.

For example, in a specific implementation, the first template may specifically include the fields shown in the following Table 1:

Table 1

Regarding the second template, the specific defined data fields may be as shown in Table 2:

Table 2

It should be noted here that in cross-border application systems, specific users may come from multiple different countries/regions. Therefore, when obtaining the name, grouping, description text and other information of each benefit item, the problem of multi-language display may be involved. Specifically, for this basic information, the data of each benefit item under each field can be saved in multiple different languages. When displaying to a specific user, the benefit item name in the corresponding language can be selected for display based on the user's country/region.

S202: Obtaining data display rule information on data fields related to user usage conditions corresponding to a plurality of benefit items in different user usage conditions.

Since different rights items may correspond to different candidate values on the same field related to user usage, even in the same user usage, the specific data that needs to be displayed for different rights items may be different. For example, when different rights items are for the same user usage status, the specific data that needs to be displayed on the fields related to user usage, such as copywriting or action items, may also be different. Therefore, specific data display rule information can also be configured for each rights item. For example, this data display rule can be used to describe the specific relationship between each rights item and the user. What candidate values are there in the fields related to user usage, and what kind of data is required to be revealed in the specific fields in various user usage situations, for example, including what kind of descriptive copy and/or what kind of action items are revealed, etc. Among them, the specific candidate copy, action items, and corresponding disclosure rules for each benefit item can be different.

For example, the candidate action items corresponding to a certain benefit item A include "stop using" and "stop activating", while the candidate action items corresponding to another benefit item B include "stop using" and "stop authenticating", etc.; accordingly, the corresponding rules can be set as follows:

Equity Item A:

If the user has used benefit item A, the displayed action item is "deactivate"; if the user has not used benefit item A, since benefit item A needs to be activated before use, the displayed action item may be "deactivate";

Equity Item B:

If the user has used benefit item B, the action item displayed is "stop using"; if the user has not used benefit item B, since benefit item B requires the user to be authenticated before use, the action item displayed may be "stop authenticating".

It should be noted that in the specific display rules, regarding action items, in addition to configuring the name of the action item, you can also configure information such as the jump address corresponding to the specific action item. In this way, after the specific action item is displayed, if the user clicks on the specific action item, the jump address can be used to jump to the corresponding page for display, so that the user can complete the corresponding "action".

Regarding specific descriptions, they can also be configured differently according to different user usage situations. For example, if the target user has used the benefit item, the description includes: the number of times the target user has used the benefit item, the remaining number of times and/or the usage effect information obtained, etc. If the target user has not used the benefit item, the description includes: summary information about the function description of the benefit item, etc. In addition, under the same user usage situation, the descriptions that need to be displayed for different benefit items may be different. For example, if a user has used two benefit items, the text that needs to be displayed for one of the benefit items may be "X goals to be completed", and the text that needs to be displayed for the other benefit item may be "X reported this month", etc. These can all be configured in a rule-based manner, where the specific quantity information can be dynamically determined based on the actual usage of the specific user.

S203: According to the rights and interests data definition template, the user's data on multiple data fields of multiple rights and interests items are saved, wherein the data on the data fields related to the user's usage is determined based on the user's rights and interests item usage information and the data display rules.

Since the rights data definition template and data display rules are configured, the data of multiple users in multiple data fields of multiple rights items can be saved according to the template and data display rules. If the first template and the second template are used, the data on each data field can be configured for each equity item for the first template. These data usually do not need to be updated unless the name, icon, etc. of a certain equity item changes. In other words, the data on the fields related to the basic information of the equity item can be constructed by manual configuration and other methods. For example, the specific equity configuration item definition can be configured and designed in the format of JSON (JavaScript Object Notation). After the data configuration on the fields related to the basic information of each equity item is completed, it can be saved on the server side, for example, it can be saved through the configuration center server of the server side, and so on.

The data on the fields related to user usage can be specifically determined based on the user's rights and interests item usage information and the data display rules. In a specific implementation, since each user's usage of the rights and interests items may change dynamically, the data on the fields related to the user's usage may also change dynamically. To this end, in a preferred implementation, the data on the fields related to user usage can be acquired and regularly updated by executing scheduled tasks. In a specific implementation, the user's usage data for each right can be obtained from a data source such as a data base table that maintains user-dimensional feature data. The above-mentioned data base table can be maintained by a log system, etc.

Among them, the obtained user usage data of various rights and interests may specifically include whether the user has used a certain right item, the specific usage amount of a certain right item, etc. These data can be directly obtained from the aforementioned data base table, or they can be obtained by processing the data in the data base table, etc. In other words, if there are processed data indicators in the data base table, they can be used directly. If not, the aforementioned scheduled task can also process the data in the base table to obtain the user usage data indicators of the rights and interests items. For example, for a certain right item, it is necessary to obtain whether the user has participated in a certain activity. However, the data does not directly exist in the data base table. In this case, the scheduled task can use the existing data in the data base table to count whether the user has participated in the activity, etc. Among them, the specific scheduled task can implement the logic of processing the data in the base table through SQL (Structured Query Language) statements and other methods.

After determining the user's usage data for the benefit items, it is possible to determine what information needs to be displayed in the fields related to the user's usage when displaying the specific benefit item to the user based on the aforementioned display rule information corresponding to the specific benefit item, for example, including specific descriptive text, action items, etc. For example, assuming that a user has used benefit item A, and benefit item A is related to quotation and has a limit on the number of uses, the text displayed can be "Quoted X times this month", and the action item can be "Go to quote", etc. Among them, the specific number of quotations "X" can also be obtained by the aforementioned scheduled task from the specific data base table (directly or after processing).

After obtaining the data related to the user's use of specific rights and interests items, and determining the information that needs to be displayed on the specific fields related to the user's use of the rights and interests items according to the data display rules corresponding to each right and interest item, a user-dimensional rights and interests item data table can be constructed (for example, it can be saved in the form of a vertical table). The data table can include the rights and interests item data constructed for each user, for example, including the description text determined based on each user's use of each right and interest item (whether it has been used, how effective it is, etc.), and can also include the action item information that needs to be displayed based on each user's use of each right and interest item, etc.

S204: In response to a request for viewing rights information initiated by a target user, the data of the target user on multiple data fields of the multiple rights items are read from the saved information, and assembled into display contents corresponding to the multiple rights items respectively, so as to display the display contents corresponding to the multiple rights in the target page.

Since the data required to be displayed in each field of the rights and interests items in the user dimension have been acquired in advance, when it is necessary to display the rights and interests information to a specific target user, the data of the target user in multiple data fields of the multiple rights and interests items can be read from the saved data and assembled into display content corresponding to the multiple rights and interests items.

Among them, if it is disassembled into two parts according to the aforementioned first template and the second template, the data of multiple rights items in the data fields related to the basic information can be first obtained from the rights configuration information, and the data of the target user on the data fields related to the user usage of the multiple rights items can be obtained from the rights usage related data; then, the data of the multiple rights items in the data fields related to the basic information and the data in the data fields related to the user usage are assembled to generate the display content corresponding to the multiple rights items respectively.

It should be noted that the specific equity configuration information may also include a sorting index field corresponding to the equity item, and the data on the field may include the sorting position number of the specific equity item. At this time, the display content corresponding to the multiple equity items may also be sorted according to the data on the sorting index field, so as to be displayed in the corresponding order on the target page.

For example, when displaying, as shown in Figure 3, the information of various rights and interests items corresponding to the current target user can be displayed, among which the rights and interests item shown at 31 is named "Industry Business Guidance". Since the current target user has used this rights and interests item, the displayed text is "2 goals to be completed" (wherein the number "2" can change dynamically to prompt the user's use of the rights and interests item), and the action item is "Go to check"; the rights and interests item shown at 32 is named "Management Certificate". Since the current target user has not used this rights and interests item, the displayed text is "Management System Certificate", and the action item can be "Go to verify", and so on.

Among them, the icons of specific rights and interests items can also be in an interactive state. When performing interactive operations such as clicking, some detailed description information of the rights and interests items can be displayed through pop-up windows/floating layers. For example, when clicking the icon of the rights and interests item "L2+Self-Marketing", a pop-up window as shown in Figure 4 can be displayed, which can display more detailed information about the rights and interests item; when clicking the rights and interests item "RFQ", a pop-up window as shown in Figure 5 can be displayed, which can display relevant information such as detailed introduction of the rights and interests item, etc.

In addition, when a new benefit item is added, deleted, or the data is updated, only the configuration information needs to be updated. For example, in the case of a new benefit item, the data on each field of the new benefit item can be configured according to the above template, without the need to develop new processing logic separately. Therefore, this solution has stronger scalability.

It should also be noted that in the embodiment of the present application, multiple rights and interests items can share the same processing logic for display. However, in a specific application system, there may be multiple different types of members, and different types of members may have different rights and interests items available. In addition, some rights and interests items may have some special requirements when being displayed, etc. Therefore, in the specific implementation, different processing logics can be implemented for different types of members. In this way, when displaying the rights and interests items for the target user, it is possible to first determine which membership type the current target user belongs to, and then call the processing logic corresponding to the type for processing.

In summary, through the embodiment of the present application, the display information of multiple different rights and interests items can be standardized and disassembled and extracted into a standardized template. In the template, the data that needs to be displayed corresponding to the rights and interests items can be split into data fields related to basic information and data fields related to user usage. At the same time, the data display rules on the fields related to user usage corresponding to multiple rights and interests items under different user usage conditions can also be configured. Afterwards, the data of the user on multiple data fields of multiple rights and interests items can be saved according to the rights and interests data definition template. Among them, the data on the fields related to user usage can be determined based on the user's usage information of the multiple rights and interests items and the aforementioned data display rules. In this way, after the target user initiates a request to view the rights and interests information, the data of the target user on multiple data fields of the multiple rights and interests items can be read from the saved information, and assembled into the display content corresponding to the multiple rights and interests items, so as to be displayed on the target page. In this way, the information of multiple different rights and interests items can be aggregated and displayed on the same page, and information related to user usage can be displayed. During the implementation process, although the information that needs to be conveyed in the same field for each benefit item may be different and related to the specific user's use of the corresponding benefit item, since the data fields corresponding to each benefit item are uniformly defined and the data to be displayed for different users in multiple fields of each benefit item can be obtained in advance, when it is necessary to display it to the user, it can be processed by the same processing logic to complete the data assembly. Accordingly, only the same set of processing logic needs to be developed to complete the display of multiple different benefit items, thereby achieving the purpose of reducing development costs.

In addition, when rights items are added, deleted, or information is updated, only the specific configuration information needs to be updated. For example, for newly added rights items, it is only necessary to configure the data on each field according to the aforementioned template. There is no need to develop new processing logic separately. Therefore, this solution has stronger scalability.

In a preferred implementation, not only can the data related to the rights and interests item be split into two parts, namely, the data on the fields related to the basic information and the data on the fields related to the user's usage, but also the first template and the second template can be provided respectively. In this way, only the data on the fields related to the user's usage needs to be saved in the user dimension and dynamically updated, while the data on the fields related to the basic information only needs to be saved for each rights and interests item, and there is no need to save a copy for each user, thereby saving storage space.

Embodiment 2

The second embodiment corresponds to the first embodiment and provides a method for displaying rights and interests information from the perspective of the client. Referring to FIG. 6 , the method may include:

S601: receiving a request from a target user to view rights and interests information;

S602: Display a target page, wherein the target page includes display contents corresponding to a plurality of rights and interests items, and the display contents are generated by reading and assembling the data of the target user on a plurality of data fields of the plurality of rights and interests items by the same processor module;

The data of the target user on the multiple data fields of the multiple rights and interests items are determined according to the rights and interests data definition template, including data fields related to basic information and data fields related to user usage. The data in the data field related to the user's usage is determined based on the user's benefit item usage information and the data display rules.

Specifically, the display content corresponding to the multiple rights and interests items respectively includes: action item information corresponding to the rights and interests items, the action item information including the name of the action item and the jump address, so as to jump to the corresponding page according to the jump address to obtain detailed information related to the rights and interests item, or perform processing related to the rights and interests item; wherein different rights and interests items correspond to different action items under the same user usage situation.

For the contents not described in detail in the second embodiment, please refer to the records in the first embodiment and other parts of this specification, which will not be repeated here.

It should be noted that the embodiments of the present application may involve the use of user data. In actual applications, user-specific personal data can be used in the scheme described herein within the scope permitted by applicable laws and regulations, subject to the requirements of applicable laws and regulations of the country where the user is located (for example, with the user's explicit consent, effective notification to the user, etc.).

Corresponding to the first embodiment, the embodiment of the present application further provides a device for displaying rights and interests information. Referring to FIG. 7 , the device may include:

The template acquisition unit 701 is used to acquire a rights and interests data definition template, wherein the rights and interests data definition template includes a plurality of data fields, wherein the plurality of data fields include a data field related to basic information and a data field related to user usage;

A data display rule acquisition unit 702 is used to acquire data display rule information on data fields related to user usage conditions corresponding to multiple benefit items under different user usage conditions;

The data acquisition unit 703 is used to save the data of the user in multiple data fields of multiple benefit items according to the benefit data definition template, wherein the data in the data field related to the user's usage is determined according to the user's benefit item usage information and the data display rule;

The display content construction unit 704 is used to respond to a request for viewing rights information initiated by a target user, read the data of the target user on multiple data fields of the multiple rights items from the saved information, and assemble them into display contents corresponding to the multiple rights items respectively, so as to display the display contents corresponding to the multiple rights items respectively in the target page.

The fields related to user usage include: description text and/or action items to be displayed when displaying benefit items;

At this time, the data display rule acquisition unit can be specifically used to: obtain the description copy and/or action item display rule information corresponding to multiple rights and interests items under different user usage situations; wherein each rights and interests item corresponds to a different candidate copy and/or candidate action item, and the data display rule information includes: the correspondence between each candidate copy and/or candidate action item of the same rights and interests item and the user usage situation;

The data acquisition unit can be specifically used to: obtain usage information of the multiple rights and interests items by multiple users respectively, and determine the corresponding description text and/or action items to be displayed when displaying the rights and interests items to each user based on the usage information and the data display rules, and save them as data in the corresponding data fields.

The action item information includes the name of the action item and a jump address, so as to jump to a corresponding page according to the jump address to obtain detailed information related to the benefit item, or to perform processing related to the benefit item.

If the target user has used the benefit item, the description text includes: the number of times the target user has used the benefit item, the remaining number of times and/or information on the use effect obtained.

If the target user has not used the benefit item, the description text includes: functional description summary information about the benefit item.

Among them, the data acquisition unit can specifically obtain the usage information of the multiple rights and interests items by multiple users by executing a scheduled task, and determine the data on the data field related to the user's usage when displaying the rights and interests items to each user based on the usage information and the data display rules.

The rights and interests data definition template includes: a first template and a second template, wherein the first template is used to define data fields related to the rights and interests items and basic information, and the second template is used to define data fields related to multiple rights and interests items and user usage conditions;

At this time, the data acquisition unit can be specifically used for:

According to the first template, data on the data fields of the plurality of equity items and the basic information are saved as equity configuration information;

According to the second template, data on the data fields related to the plurality of benefit items and user usage are saved as benefit usage related data information;

The display content assembly unit can be specifically used for:

In response to a request for viewing rights information initiated by the target user, obtaining data of the plurality of rights items in data fields related to basic information from the rights configuration information;

Acquire data of the target user on data fields related to user usage of the plurality of benefit items from the benefit usage related data;

The data of the multiple rights and interests items in the data fields related to the basic information and the data of the data fields related to the user usage are assembled to generate display contents corresponding to the multiple rights and interests items respectively.

Specifically, if there are multiple different membership types, the display content assembly unit can be specifically used to: determine the membership type information corresponding to the target user; obtain data on multiple rights and interests items corresponding to the membership type in data fields related to basic information from the rights and interests configuration information.

In addition, different membership types may correspond to different processor modules. In this case, the display content assembly unit may be specifically used to: after determining the membership type information corresponding to the target user, determine the corresponding processor module according to the membership type information, so that the processor module can read and assemble the data.

The equity configuration information may further include a sorting index field corresponding to the equity item;

At this time, the device may further include:

The sorting unit is used to sort the display contents corresponding to the multiple rights and interests items according to the data on the sorting index field, so as to display them in the corresponding order on the target page.

When a benefit item is added, deleted, or the information is updated, the benefit configuration information and/or benefit usage related data information are updated to update the displayed benefit item and/or the corresponding displayed content.

Corresponding to the second embodiment, the embodiment of the present application further provides a device for displaying rights and interests information. Referring to FIG. 8 , the device may include:

The request receiving unit 801 is used to receive a request initiated by a target user to view rights and interests information;

The page display unit 802 is used to display a target page, wherein the target page includes display contents corresponding to a plurality of rights and interests items, and the display contents are generated by reading and assembling the data of the target user in a plurality of data fields of the plurality of rights and interests items by the same processor module;

Among them, the data of the target user in multiple data fields of the multiple rights and interests items are determined according to the rights and interests data definition template, including data fields related to basic information and data fields related to user usage. The data in the data fields related to user usage is determined based on the user's rights and interests item usage information and the data display rules.

Among them, the display contents corresponding to the multiple rights and interests items include:

The action item information corresponding to the benefit item includes the name of the action item and a jump address, so as to jump to the corresponding page according to the jump address to obtain detailed information related to the benefit item, or perform processing related to the benefit item; wherein different benefit items correspond to different action items under the same user usage situation.

In addition, an embodiment of the present application further provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the steps of any one of the methods in the aforementioned method embodiments are implemented.

And an electronic device, comprising:

one or more processors; and

A memory associated with the one or more processors, the memory being used to store program instructions, wherein the program instructions, when read and executed by the one or more processors, execute the steps of the method described in any one of the aforementioned method embodiments.

9 exemplarily shows the architecture of the electronic device, which may include a processor 910, a video display adapter 911, a disk drive 912, an input/output interface 913, a network interface 914, and a memory 920. The processor 910, the video display adapter 911, the disk drive 912, the input/output interface 913, the network interface 914, and the memory 920 may be communicatively connected via a communication bus 930.

Among them, the processor 910 can be implemented by a general-purpose CPU (Central Processing Unit, processor), a microprocessor, an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solution provided in this application.

The memory 920 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 920 can store an operating system 921 for controlling the operation of the electronic device 900, and a basic input and output system (BIOS) for controlling the low-level operation of the electronic device 900. In addition, a web browser 923, a data storage management system 924, and a rights and interests information display processing system 925, etc. can also be stored. The above-mentioned rights and interests information display processing system 925 can be an application program that specifically implements the operations of the aforementioned steps in the embodiment of the present application. In short, when the technical solution provided by the present application is implemented by software or firmware, the relevant program code is stored in the memory 920 and is called and executed by the processor 910.

The input/output interface 913 is used to connect the input/output module to realize information input and output. The input/output module can be configured in the device as a component (not shown in the figure), or it can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.

The network interface 914 is used to connect to a communication module (not shown) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB, network cable, etc.) or a wireless mode (such as mobile network, WIFI, Bluetooth, etc.).

The bus 930 comprises a pathway for transmitting information between the various components of the device (eg, the processor 910, the video display adapter 911, the disk drive 912, the input/output interface 913, the network interface 914, and the memory 920).

It should be noted that, although the above device only shows a processor 910, a video display adapter 911, a disk drive 912, an input/output interface 913, a network interface 914, a memory 920, a bus 930, etc., in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include components necessary for implementing the solution of the present application, and does not necessarily include all the components shown in the figure.

It can be known from the description of the above implementation methods that those skilled in the art can clearly understand that the present application can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution of the present application can be essentially or partly contributed to the prior art in the form of a software product, which can be stored in a storage medium such as ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in the various embodiments of the present application or certain parts of the embodiments.

Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for systems or system embodiments, since they are basically similar to method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments. The systems and system embodiments described above are merely illustrative, in which the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physically separated. The physical unit may not be a physical unit, that is, it may be located in one place, or it may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Ordinary technicians in this field can understand and implement it without creative work.

The above is a detailed introduction to the method and electronic device for displaying rights and interests information provided by the present application. This article uses specific examples to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method and its core idea of the present application. At the same time, for those skilled in the art, according to the idea of the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as limiting the present application.

Claims (14)

A method for displaying equity information, characterized by comprising: Acquire a rights and interests data definition template, wherein the rights and interests data definition template includes a plurality of data fields, wherein the plurality of data fields include a data field related to basic information and a data field related to user usage; Obtain data display rule information on data fields related to user usage corresponding to multiple benefit items under different user usage conditions; According to the rights and interests data definition template, the data of the user in multiple data fields of multiple rights and interests items are saved, wherein the data in the data fields related to the user's usage is determined according to the user's rights and interests item usage information and the data display rule information; In response to a request initiated by a target user to view rights and interests information, the data of the target user on multiple data fields of the multiple rights and interests items are read from the saved information and assembled into display contents corresponding to the multiple rights and interests items respectively, so as to display the display contents corresponding to the multiple rights and interests items respectively in the target page. The method according to claim 1, characterized in that For fields related to user usage, different benefit items correspond to different candidate values for the same field; The data display rule information specifically includes: the correspondence between the candidate values of the same benefit item in the same field and the user's usage, so as to determine the data to be displayed for the corresponding benefit item in the corresponding field from the candidate values of the corresponding benefit item in the corresponding field according to the usage information of the specific user. The method according to claim 2, characterized in that The fields related to user usage include: description text and/or action items to be displayed when displaying benefit items; The obtaining of data display rule information on data fields related to user usage corresponding to the plurality of rights and interests items under different user usage situations includes: Obtaining description texts and/or action item display rule information corresponding to a plurality of benefit items under different user usage situations; wherein each benefit item corresponds to a different candidate text and/or candidate action item, and the data display rule information includes: a correspondence between each candidate text and/or candidate action item of the same benefit item and the user usage situation; The step of saving data of multiple users in multiple data fields of multiple rights and interests items according to the rights and interests data definition template includes: Obtain usage information of the multiple benefit items by multiple users respectively, and determine the corresponding description text and/or action items to be displayed when displaying the benefit items to each user based on the usage information and the data display rules, and save them as data in the corresponding data fields. The method according to claim 3, characterized in that The action item information includes the name of the action item and a jump address, so as to jump to a corresponding page according to the jump address to obtain detailed information related to the benefit item, or perform processing related to the benefit item. The method according to claim 3, characterized in that If the target user has used the benefit item, the description text includes: the number of times the target user has used the benefit item, the remaining number of times and/or information on the use effect obtained. The method according to claim 3, characterized in that If the target user has not used the benefit item, the description text includes: functional description summary information about the benefit item. The method according to claim 1, characterized in that By executing scheduled tasks, the usage information of the multiple benefit items by multiple users is obtained, and based on the usage information and the data display rules, the data corresponding to the data field related to the user's usage is determined when the benefit items are displayed to each user. The method according to any one of claims 1 to 7, characterized in that The rights and interests data definition template includes: a first template and a second template, wherein the first template is used to define data fields related to the rights and interests items and basic information, and the second template is used to define data fields related to multiple rights and interests items and user usage conditions; The step of saving data of multiple users in multiple data fields of multiple rights and interests items according to the rights and interests data definition template includes: According to the first template, data on the data fields of the plurality of equity items and the basic information are saved as equity configuration information; According to the second template, data on the data fields related to the plurality of benefit items and user usage are saved as benefit usage related data information; When responding to the request for viewing the rights and interests information initiated by the target user, it includes: Acquire data of the plurality of equity items in data fields related to the basic information from the equity configuration information; Acquire data of the target user on data fields related to user usage of the plurality of benefit items from the benefit usage related data; The data of the multiple rights and interests items in the data fields related to the basic information and the data of the data fields related to the user usage are assembled to generate display contents corresponding to the multiple rights and interests items respectively. The method according to claim 8, characterized in that The acquiring data of the plurality of equity items in data fields related to basic information from the equity configuration information includes: Determine the membership type information corresponding to the target user; The data of the multiple rights and interests items corresponding to the member type in the data fields related to the basic information are obtained from the rights and interests configuration information. The method according to claim 9, characterized in that Different membership types correspond to different processor modules; After determining the membership type information corresponding to the target user, the following further includes: The corresponding processor module is determined according to the member type information, so that the processor module can read and assemble the data. The method according to claim 8, characterized in that The equity configuration information includes a sorting index field corresponding to the equity item; The method further comprises: According to the data on the sorting index field, the display contents corresponding to the multiple rights and interests items are sorted so as to be displayed in the target page in a corresponding order. A method for displaying equity information, characterized by comprising: Receive a request from a target user to view rights information; Displaying a target page, wherein the target page includes display contents corresponding to a plurality of rights and interests items, respectively, and the display contents are generated by reading and assembling the data of the target user on a plurality of data fields of the plurality of rights and interests items by the same processor module; Among them, the data of the target user in multiple data fields of the multiple rights and interests items are determined according to the rights and interests data definition template, including data fields related to basic information and data fields related to user usage. The data in the data fields related to user usage is determined based on the user's rights and interests item usage information and the data display rules. A computer-readable storage medium having a computer program stored thereon, characterized in that when the program is executed by a processor, the steps of the method described in any one of claims 1 to 12 are implemented. An electronic device, comprising: one or more processors; and A memory associated with the one or more processors, the memory being used to store program instructions, wherein the program instructions, when read and executed by the one or more processors, execute the steps of the method described in any one of claims 1 to 12.