Product function display method and system based on user permission management

Abstract

The application relates to the computer technical field and discloses a product function display method and system based on user permission management, which are applied to a product function display system, the system comprises a server and a terminal, and the method comprises the following steps: when a user triggers a login operation through the terminal, the terminal acquires user identification information of the user according to the login operation, and sends the user identification information and terminal identification information to the server; the server receives the terminal identification information and the user identification information, and performs authentication interaction processing on the terminal identification information and the user identification information; when the authentication is successful, target permission information of the user is determined according to the user identification information and the terminal identification information, and the target permission information is sent to the terminal; and the terminal receives the target permission information, and displays page content corresponding to the target permission information. It can be seen that the application can meet the intelligent demand of the user for learning product functions in time, and realize convenient upgrading of the product and use of extensible functions.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method and system for displaying product functions based on user permission management. Background Technology

[0002] Currently, the software development of smart terminals can be continuously iterated and upgraded to add new functions or improve performance, and can provide differentiated support based on the differences in hardware products.

[0003] In practice, to adapt to different product positioning, accommodate the rights and interests of new and old users, maximize corporate revenue, and promote new features, it is usually necessary to block certain product functions or conditionally open them to external users through authorization management.

[0004] However, practice has shown that traditional product feature authorization management only executes when a user triggers a corresponding function operation. This traditional approach has the following technical drawbacks: Firstly, if a user attempts to operate a function but the function cannot be authorized to that user, the user is only notified that the operation is impossible, resulting in low efficiency and failing to meet users' intelligent needs for timely access to product features. Secondly, once the product is finalized, it does not showcase expandable features, hindering convenient product upgrades and user access to expandable functionalities. Therefore, meeting users' intelligent needs for timely access to product features and ensuring convenient product upgrades and user access to expandable functionalities are of paramount importance. Summary of the Invention

[0005] This invention provides a product function display method and system based on user permission management, which can meet users' intelligent needs for timely access to product functions, and enable convenient product upgrades and expandable functions for users.

[0006] To address the aforementioned technical problems, the first aspect of this invention discloses a method for displaying product functions based on user permission management. The method is applied to a product function display system, which includes a server and a terminal. The method includes:

[0007] When a user triggers a login operation through the terminal, the terminal obtains the user's user identification information according to the login operation, and sends the user identification information and the terminal's terminal identification information to the server;

[0008] The server receives the terminal identification information and the user identification information, and performs authentication interaction processing on the terminal identification information and the user identification information; when authentication is successful, the server determines the user's target permission information based on the user identification information and the terminal identification information, and sends the target permission information to the terminal.

[0009] The terminal receives the target permission information and displays the page content corresponding to the target permission information;

[0010] The permission information includes at least one currently supported function of the terminal, at least one currently authorized function of the user, at least one permission type locally supported by the terminal, authorized terminal information, authorization authentication method for each authorized function, and at least one time limit data for each permission type.

[0011] As an optional implementation, in a first aspect of the present invention, the server determines the user's target permission information based on the user identification information and the terminal identification information, including:

[0012] The server determines the user's user contract information based on the user identification information, and obtains the user's first permission function pool from the user permission database corresponding to the server based on the user contract information. The first permission function pool includes at least one function whose authorization probability is greater than or equal to a preset probability.

[0013] The server determines the terminal capability information of the terminal based on the terminal identification information, and determines the second permission function pool of the terminal based on the terminal capability information. The second permission function pool includes at least one function supported by the terminal.

[0014] The server determines a third permission function pool based on a pre-established association mapping model between user and terminal identifier key and authorized functions, according to the target key between the user identifier information and the terminal identifier information. The third permission function pool includes at least one function that the terminal has authorized to the user.

[0015] The server determines the fourth permission function pool of the terminal based on the local list information sent by the terminal. The fourth permission function pool includes at least one function that the terminal can run locally.

[0016] The server performs a comprehensive analysis of the first permission function pool, the second permission function pool, the third permission function pool, and the fourth permission function pool to obtain the user's target permission information.

[0017] As an optional implementation, in a first aspect of the present invention, the server performs a comprehensive analysis of the first permission function pool, the second permission function pool, the third permission function pool, and the fourth permission function pool to obtain the user's target permission information, including:

[0018] The server determines the maximum range of functional permissions for the terminal by analyzing the overlapping functional pools between the first permission functional pool and the second permission functional pool.

[0019] The server determines the authorized function scope of the terminal based on the third permission function pool, and determines the local running function scope of the terminal based on the fourth permission function pool.

[0020] The server determines the user's first permission information based on the maximum functional permission range, the authorized functional range, and the locally running functional range. The first permission information includes at least one currently supported function of the terminal, at least one currently authorized function of the user, and one or more combinations of at least one permission type locally supported by the terminal.

[0021] The server performs binding and authorization analysis operations on the user identification information and the terminal identification information to obtain the user's second permission information. The second permission information includes at least one of the following: authorized terminal information, authorization authentication method for each authorized function, and timeliness data for each permission type.

[0022] The server determines at least one permission information from the permission information set consisting of the first permission information and the second permission information as the user's target permission information.

[0023] As an optional implementation, in a first aspect of the present invention, the server determines the user's first permission information based on the maximum functional permission range, the authorized functional range, and the local operating functional range, including:

[0024] The server analyzes the functional overlap and non-overlapping ranges among the maximum functional permission range, the authorized functional range, and the locally running functional range;

[0025] The server determines the user's first permission information based on the overlapping range of functions and the non-overlapping range of functions.

[0026] As an optional implementation, in the first aspect of the present invention, the server performs binding and authorization analysis operations on the user identification information and the terminal identification information to obtain the user's second permission information, including:

[0027] The server searches for the user's terminal binding information based on the user identification information. The terminal binding information includes at least one of the following: the number of allowed bound terminals, the number of already bound terminals, and the identifier of the bound terminals.

[0028] The server determines the authorized terminal information based on the terminal identification information and the user's terminal binding information;

[0029] The server determines the authorization and authentication method for each authorized function based on the security level field information corresponding to each authorized function contained in the first permission information.

[0030] The server calculates the expiration time parameter of each permission type based on the authorization record information obtained for each permission type, and determines the validity data of the permission type based on the expiration time parameter and the obtained current time parameter.

[0031] As an optional implementation, in the first aspect of the present invention, the method further includes:

[0032] The server performs an encoding operation on the target permission information to obtain permission encoding information;

[0033] The server performs an encoding operation on the target permission information to obtain permission encoding information, including:

[0034] The server performs structured processing on the target permission information to obtain processed target permission information;

[0035] The server performs data security encryption on the processed target permission information to obtain permission encoding information;

[0036] And, the server sends the target permission information to the terminal, including:

[0037] The server sends the permission encoding information to the terminal.

[0038] As an optional implementation, in the first aspect of the present invention, the target permission information received by the terminal is the permission encoding information;

[0039] Furthermore, the method further includes:

[0040] The terminal performs a decoding operation on the permission encoding information to obtain permission decoding information;

[0041] And, the terminal displays the page content corresponding to the target permission information, including:

[0042] The terminal displays the page content corresponding to the permission decoding information.

[0043] A second aspect of this invention discloses a product function display system based on user permission management. The system includes a server and a terminal. The server includes a user permission management module, a user access management module, and a first network module. The terminal includes a user interaction module and a second network module, wherein:

[0044] The user interaction module is used to obtain the user's user identification information according to the login operation when the user triggers a login operation through the user interaction module.

[0045] The second network module is used to send the user identification information and the terminal identification information of the terminal to the first network module;

[0046] The first network module is used to receive the terminal identification information and the user identification information;

[0047] The user access management module is used to perform authentication interaction processing on the terminal identification information and the user identification information;

[0048] The user permission management module is used to determine the user's target permission information based on the user identification information and the terminal identification information when authentication is successful.

[0049] The first network module is further configured to send the target permission information to the second network module;

[0050] The second network module is also used to receive the target permission information;

[0051] The user interaction module is used to display the page content corresponding to the target permission information;

[0052] The permission information includes at least one currently supported function of the terminal, at least one currently authorized function of the user, at least one permission type locally supported by the terminal, authorized terminal information, authorization authentication method for each authorized function, and at least one time limit data for each permission type.

[0053] As an optional implementation, in a second aspect of the present invention, the user permission management module determines the user's target permission information based on the user identification information and the terminal identification information, including:

[0054] Based on the user identification information, the user's user contract information is determined, and based on the user contract information, the user's first permission function pool is obtained from the user permission database corresponding to the server. The first permission function pool includes at least one function whose authorization probability is greater than or equal to a preset probability.

[0055] Based on the terminal identification information, the terminal capability information of the terminal is determined, and based on the terminal capability information, the second permission function pool of the terminal is determined, wherein the second permission function pool includes at least one function supported by the terminal.

[0056] Based on a pre-established association mapping model between user and terminal identifier key and authorized functions, a third permission function pool is determined according to the target key between the user identifier information and the terminal identifier information. The third permission function pool includes at least one function that the terminal has authorized to the user.

[0057] Based on the local list information sent by the terminal, the fourth permission function pool of the terminal is determined, and the fourth permission function pool includes at least one function that the terminal can run locally.

[0058] The user's target permission information is obtained by comprehensively analyzing the first permission function pool, the second permission function pool, the third permission function pool, and the fourth permission function pool.

[0059] As an optional implementation, in a second aspect of the present invention, the user permission management module performs a comprehensive analysis of the first permission function pool, the second permission function pool, the third permission function pool, and the fourth permission function pool to obtain the user's target permission information in the following specific ways:

[0060] By analyzing the overlapping function pools between the first permission function pool and the second permission function pool, the maximum range of function permissions for the terminal is determined.

[0061] Based on the third permission function pool, the authorized function scope of the terminal is determined, and based on the fourth permission function pool, the local running function scope of the terminal is determined.

[0062] Based on the maximum functional permission range, the authorized functional range, and the locally running functional range, the user's first permission information is determined. The first permission information includes at least one currently supported function of the terminal, at least one currently authorized function of the user, and one or more combinations of at least one permission type locally supported by the terminal.

[0063] Perform authentication-related operations on the user identification information and the terminal identification information to obtain the user's second permission information. The second permission information includes at least one of the following: authorized terminal information, authorization authentication method for each authorized function, and timeliness data for each permission type.

[0064] At least one permission information from the permission information set consisting of the first permission information and the second permission information is determined as the target permission information for the user.

[0065] As an optional implementation, in a second aspect of the present invention, the specific method by which the user permission management module determines the user's first permission information based on the maximum functional permission range, the authorized functional range, and the local operating functional range includes:

[0066] Analyze the functional overlap and non-overlapping ranges among the maximum functional permission range, the authorized functional range, and the locally running functional range;

[0067] The user's first permission information is determined based on the functional overlap range and the functional non-overlap range.

[0068] As an optional implementation, in the second aspect of the present invention, the user permission management module performs binding and authorization analysis operations on the user identification information and the terminal identification information to obtain the user's second permission information in the following specific ways:

[0069] Based on the user identification information, the terminal binding information of the user is retrieved. The terminal binding information includes at least one of the following: the number of allowed bound terminals, the number of bound terminals, and the identifier of the bound terminals.

[0070] The authorized terminal information is determined based on the terminal identification information and the user's terminal binding information;

[0071] Based on the security level field information corresponding to each authorized function contained in the first permission information obtained, determine the authorization and authentication method for each authorized function;

[0072] Based on the authorization record information of each permission type obtained, calculate the permission expiration time parameter for that permission type, and determine the validity period data for that permission type based on the permission expiration time parameter and the obtained current time parameter.

[0073] As an optional implementation, in a second aspect of the invention, the server further includes a permission encoding module, wherein:

[0074] The permission encoding module is used to perform an encoding operation on the target permission information to obtain permission encoding information;

[0075] The specific methods by which the permission encoding module performs an encoding operation on the target permission information to obtain the permission encoding information include:

[0076] The target permission information is structured to obtain the processed target permission information;

[0077] The processed target permission information is then subjected to data security encryption to obtain permission encoding information;

[0078] Furthermore, the specific method by which the first network module sends the target permission information to the second network module includes:

[0079] The first network module sends the permission encoding information to the second network module.

[0080] As an optional implementation, in a second aspect of the present invention, the target permission information received by the second networking module is the permission encoding information;

[0081] Furthermore, the terminal also includes a permission decoding module, wherein:

[0082] The permission decoding module is used to perform a decoding operation on the permission encoding information to obtain permission decoding information;

[0083] Furthermore, the specific methods by which the user interaction module displays the page content corresponding to the target permission information include:

[0084] Display the page content corresponding to the aforementioned permission decoding information.

[0085] A third aspect of this invention discloses another product function display system based on user permission management, the system comprising:

[0086] Memory containing executable program code;

[0087] A processor coupled to the memory;

[0088] The processor calls the executable program code stored in the memory to execute the product function display method based on user permission management disclosed in the first aspect of the present invention.

[0089] The fourth aspect of the present invention discloses a computer storage medium storing computer instructions, which, when invoked, are used to execute the product function display method based on user permission management disclosed in the first aspect of the present invention.

[0090] Compared with the prior art, the embodiments of the present invention have the following beneficial effects:

[0091] This invention provides a product function display method based on user permission management. The method is applied to a product function display system, which includes a server and a terminal. The method includes: when a user triggers a login operation through the terminal, the terminal obtains the user's user identification information based on the login operation and sends the user identification information and the terminal's terminal identification information to the server; the server receives the terminal identification information and the user identification information and performs authentication interaction processing on the terminal identification information and the user identification information; when authentication is successful, the server determines the user's target permission information based on the user identification information and the terminal identification information and sends the target permission information to the terminal; the terminal receives the target permission information and displays the page content corresponding to the target permission information; wherein the permission information includes at least one supported function of the terminal, at least one authorized function of the user, at least one permission type supported by the corresponding authorized function, authorized terminal information, authorization authentication method for each authorized function, and at least one time-limited data for each permission type. As can be seen, implementing this invention enables the terminal to obtain user identification information when the user triggers a login operation, and sends the user identification information and terminal identification information to the server together. The server then receives the dual identifiers and performs authentication interaction, achieving unified authorization from both the user and device dimensions. This provides a data foundation for subsequent matching of permission information. Upon successful authentication, the server determines the user's permission information using the dual identifiers and sends it to the terminal, triggering the terminal to receive permissions and display the corresponding page content. Through the user's login operation on the terminal combined with the linkage between the terminal and the server, product functions are automatically displayed to the user. This not only meets the user's intelligent need for timely access to product functions but also enables convenient product upgrades and the use of expandable functions, improving the user experience. Compared to the traditional passive verification method after the user accesses functions, this solution proactively reports to the server upon user login and analyzes user permissions using dual identifiers, improving the efficiency and timeliness of obtaining user permission information. Attached Figure Description

[0092] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0093] Figure 1 This is a flowchart illustrating a product function display method based on user permission management disclosed in an embodiment of the present invention;

[0094] Figure 2 This is a flowchart illustrating another product function display method based on user permission management disclosed in an embodiment of the present invention;

[0095] Figure 3 This is a schematic diagram of a product function display interface from a user's perspective, as disclosed in an embodiment of the present invention.

[0096] Figure 4 This is a schematic diagram of the system architecture of a product function display system disclosed in an embodiment of the present invention;

[0097] Figure 5 This is a schematic diagram of the structure of a core module of a server disclosed in an embodiment of the present invention;

[0098] Figure 6 This is a schematic diagram of the structure of a core module of a smart terminal disclosed in an embodiment of the present invention;

[0099] Figure 7 This is a schematic diagram of the structure of a product function display system based on user permission management disclosed in an embodiment of the present invention;

[0100] Figure 8 This is a schematic diagram of another product function display system based on user permission management disclosed in an embodiment of the present invention;

[0101] Figure 9 This is a schematic diagram of the structure of another product function display system based on user permission management disclosed in an embodiment of the present invention. Detailed Implementation

[0102] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0103] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this invention are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or end that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or ends.

[0104] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of the invention. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0105] This invention discloses a product function display method and system based on user permission management. When a user initiates a login operation, the terminal can obtain user identification information and send it along with the terminal identification information to the server. The server receives the dual identifiers and performs authentication interaction, achieving unified authorization from both the user and device dimensions. This provides a data foundation for subsequent permission information matching. Upon successful authentication, the server determines the user's permission information using the dual identifiers and sends it to the terminal, triggering the terminal to receive permissions and display the corresponding page content. Through the user's login operation on the terminal combined with the interaction between the terminal and the server, product functions are automatically displayed to the user. This not only meets the user's intelligent need for timely access to product functions but also enables convenient product upgrades and the use of expandable functions, improving the user experience. Compared to the traditional passive verification method after the user accesses a function, this solution proactively reports to the server upon user login and analyzes user permissions using dual identifiers, improving the efficiency and timeliness of user permission information acquisition. Detailed explanations follow.

[0106] Example 1

[0107] Please see Figure 1 , Figure 1 This is a flowchart illustrating a product function display method based on user permission management, as disclosed in an embodiment of the present invention. Figure 1 The described product feature display method based on user permission management can be applied to a product feature display system, which includes a server (including a local server or a cloud server) and a terminal (such as a mobile phone, tablet, etc.). This embodiment of the invention does not limit the scope of the method. Figure 1 As shown, this method for displaying product features based on user permission management may include the following operations:

[0108] 101. When a user triggers a login operation through a terminal, the terminal obtains the user's user identification information based on the login operation and sends the user identification information and the terminal's terminal identification information to the server.

[0109] In this embodiment of the invention, optionally, the login operation can be an operation in which a user logs into any application within the terminal using an account. The user identification information may include at least one of the following: username, user ID, user email address, and verification credentials. The verification credentials may be a password, a dynamic code, an SMS message, or other credentials that serve an equivalent verification function; this embodiment of the invention does not impose any limitations.

[0110] In this embodiment of the invention, the terminal identification information may optionally include at least one of the following: terminal name, terminal ID, terminal model, etc., and this embodiment of the invention does not impose any limitation.

[0111] 102. The server receives terminal identification information and user identification information, and performs authentication interaction processing on the terminal identification information and user identification information.

[0112] In this embodiment of the invention, the server's authentication interaction processing is used to perform interaction processing on access terminal authentication and other related information, thereby recording information such as the unique identifier of the terminal (such as terminal ID) and the unique identifier of the user (such as user ID) after successful authentication.

[0113] 103. When authentication is successful, the server determines the user's target permission information based on the user identification information and the terminal identification information, and sends the target permission information to the terminal.

[0114] In this embodiment of the invention, optionally, the permission information includes at least one currently supported function of the terminal, at least one currently authorized function of the user, at least one permission type locally supported by the terminal, authorized terminal information, authorization authentication method for each authorized function, and at least one time-limited data for each permission type. The supported functions of the terminal may include authorized functions supported by the terminal and / or unauthorized functions supported by the terminal, and these supported functions are limited by the characteristics of the terminal device, such as being limited by the maximum range of function permissions supported by the device. Authorized functions of the user represent the function permissions already available on the device. Permission types locally supported by the terminal are determined based on whether local data files, etc., are supported; if not, they need to be downloaded and updated. Authorized terminal information represents the terminal information permitted for use, and the authorization authentication method represents a secondary authentication method using credentials such as dynamic passwords; this embodiment of the invention does not impose limitations on this.

[0115] 104. The terminal receives the target permission information and displays the page content corresponding to the target permission information.

[0116] In this embodiment of the invention, optionally, the specific content displayed on the page corresponding to the target permission information may include: directly displaying the supported and authorized functions and the usage status of the corresponding functions; further, it may also include: prompts indicating whether the function has been updated, and the usage status after the function has been updated; further, it may also include: the function being restricted, such as whether authorization needs to be obtained through purchase or other means before it can be used; further, it may also include: the user's usage of the product functions under the function display situation, which is not limited in this embodiment of the invention.

[0117] It is evident that implementation Figure 1 The described product feature display method based on user permission management enables the terminal to obtain user identification information when the user triggers a login operation. This user identification information, along with the terminal identification information, is sent to the server. The server receives the dual identifiers and performs authentication processing, achieving unified authorization from both the user and device dimensions. This provides a data foundation for subsequent permission information matching. Upon successful authentication, the server determines the user's permission information using the dual identifiers and sends it to the terminal, triggering the terminal to receive permissions and display the corresponding page content. Through the user's login operation on the terminal combined with the interaction between the terminal and the server, product features are automatically displayed to the user. This not only meets the user's intelligent need for timely access to product features but also enables convenient product upgrades and the use of expandable functions, improving the user experience. Compared to the traditional passive verification method after the user accesses a function, this solution proactively reports user permissions to the server upon user login and analyzes user permissions using dual identifiers, improving the efficiency and timeliness of user permission information acquisition.

[0118] In an optional embodiment, the method may further include:

[0119] The server performs an encoding operation on the target permission information to obtain the permission encoding information;

[0120] The server performs an encoding operation on the target permission information to obtain permission encoding information, including:

[0121] The server performs structured processing on the target permission information to obtain the processed target permission information;

[0122] The server performs data security encryption on the processed target permission information to obtain permission encoding information;

[0123] In addition, the server sends the target permission information to the terminal, including:

[0124] The server sends the permission encoding information to the terminal.

[0125] In this embodiment of the invention, optionally, the encoding operation includes at least the operation of structuring the data to be transmitted according to a preset "encoding" rule. Further optionally, the encoding operation may also include the operation of securely encrypting the data to be transmitted. This embodiment of the invention does not impose any limitations.

[0126] As can be seen, this optional embodiment can, after determining the user's target permission information, perform structured processing on the target permission information through the server to facilitate subsequent terminal identification, and then perform data security encryption processing on the processed target permission information to obtain permission encoding information and provide it to the terminal. By performing comprehensive processing such as structuring and security encryption on the permission information to be provided to the terminal, the identification efficiency and information security of permission information can be improved.

[0127] In this optional embodiment, as an optional implementation method, the target permission information received by the terminal is permission encoding information;

[0128] In addition, the method also includes:

[0129] The terminal performs a decoding operation on the authorization encoding information to obtain the authorization decoding information;

[0130] In addition, the terminal displays the page content corresponding to the target permission information, including:

[0131] The terminal displays the page content corresponding to the permission decoding information.

[0132] In this embodiment of the invention, optionally, the decoding operation includes at least decoding the data transmitted by the server according to the "encoding" rules. Further optionally, the decoding operation may also include decryption processing. Specifically, the terminal decodes the permission encoding information according to the "encoding" rules; if it detects that the permission encoding information has been encrypted, the terminal simultaneously decrypts the permission encoding information.

[0133] As can be seen, this optional implementation method can improve the accuracy, efficiency, and security of user permission information transmission by using server encoding and terminal decoding information transmission, thereby further improving the efficiency of obtaining user permission information.

[0134] Example 2

[0135] Please see Figure 2 , Figure 2 This is a flowchart illustrating a product function display method based on user permission management, as disclosed in an embodiment of the present invention. Figure 2The described product feature display method based on user permission management can be applied to a product feature display system, which includes a server (including a local server or a cloud server) and a terminal (such as a mobile phone, tablet, etc.). This embodiment of the invention does not limit the scope of the method. Figure 2 As shown, this method for displaying product features based on user permission management may include the following operations:

[0136] 201. When a user triggers a login operation through a terminal, the terminal obtains the user's user identification information based on the login operation and sends the user identification information and the terminal's terminal identification information to the server.

[0137] 202. The server receives terminal identification information and user identification information, and performs authentication interaction processing on the terminal identification information and user identification information.

[0138] In this embodiment of the invention, when authentication is successful in step 202, any one of steps 203-206 is triggered.

[0139] 203. The server determines the user's user contract information based on the user identification information, and retrieves the user's first permission function pool from the corresponding user permission database of the server based on the user contract information.

[0140] In this embodiment of the invention, optionally, the user contract information may include a user type, a list of purchased functions corresponding to the user type, and the expiration data of each function in the list of purchased functions. The user type may include one of the following: individual type, enterprise type, employee type, etc. The list of purchased functions includes at least one purchased function, the SKU, service code, version number, etc., for each function. The expiration data for each function may include the global effective time, expiration time, and freeze flag data for each function, wherein the freeze flag data is empty or indicates that the corresponding function has been frozen. The first permission function pool includes at least one function for which the user's authorization probability is greater than or equal to a preset probability level; this can be understood as a pool of functions that the user can theoretically purchase, and this embodiment of the invention does not limit this.

[0141] 204. The server determines the terminal's capability information based on the terminal identification information, and determines the terminal's second permission function pool based on the terminal capability information.

[0142] In this embodiment of the invention, the terminal capability information may include at least one of the following: the terminal's device model, the terminal's OS system, the terminal's hardware capability bitmap (e.g., whether it has a security chip, whether it has a camera, memory size, etc.), whitelist / blacklist marking information, the terminal's registration time, and last online time. The second permission function pool includes at least one function supported by the terminal, which can be understood as a pool of functions that the terminal can run; this embodiment of the invention does not impose any limitations on this.

[0143] 205. Based on the pre-established association mapping model between the user and terminal identifier key and the authorization function, the server determines the third permission function pool according to the target key between the user identifier information and the terminal identifier information.

[0144] In this embodiment of the invention, specifically, the server acquires multiple pre-stored historical combination keys and at least one authorized function corresponding to each historical combination key. The historical combination key represents a historical user and terminal identifier combination key. The server uses all historical combination keys as input parameters and all authorized functions corresponding to each historical combination key as output parameters to train a pre-built neural network model, obtaining a mapping model between the user and terminal identifier combination keys and authorized functions. Further, after determining the target combination key between user identifier information and terminal identifier information, the server inputs the target combination key into the mapping model for association analysis, obtaining all authorized functions corresponding to the target combination key, and determining all authorized functions corresponding to the target combination key as the third permission function pool. Thus, by pre-training the mapping model between the user and terminal identifier combination keys and authorized functions, accurate mapping from the currently input target combination key to the third permission function pool can be achieved.

[0145] In this embodiment of the invention, the third permission function pool includes at least one function that the terminal has authorized for the user, which can be understood as the function that the user has been authorized to use on the terminal. For example, the user identification information is denoted as UID, the terminal identification information is denoted as TID, and the combined key of the user and terminal identification can be denoted as...<UID,TID> By using the concatenation key, the system can find the list of function authorizations issued to the user by the terminal (e.g., function code, authorization mode, token status, issuance time, expiration time, remaining number of times, etc.) and the security element information bound to the terminal (e.g., certificate serial number, public key fingerprint, dynamic password seed, secondary authentication method, etc.), thereby determining the third permission function pool. This embodiment of the invention does not impose any limitations.

[0146] 206. The server determines the terminal's fourth permission function pool based on the local list information sent by the terminal.

[0147] In this embodiment of the invention, optionally, the local inventory information may include locally installed component versions, data file versions, license file hash values, etc., and may also include a list of missing components. The fourth permission function pool includes at least one function that the terminal can run locally, which can be understood as a pool of functions that can actually run locally.

[0148] In this embodiment of the invention, optionally, there is no specific order among steps 203-206. That is, each step 203-206 can occur before, after, or simultaneously with any remaining steps. This embodiment of the invention does not impose any limitations. For example, step 205 can occur before, after, or simultaneously with step 204, and step 206 can occur before, after, or simultaneously with step 203.

[0149] 207. The server performs a comprehensive analysis of the first, second, third, and fourth permission function pools to obtain the user's target permission information and sends the target permission information to the terminal.

[0150] In this embodiment of the invention, specifically, the server determines multiple permission function pools based on user identification information and terminal identification information. All permission function pools include a first permission function pool, a second permission function pool, a third permission function pool, and a fourth permission function pool. The server performs comprehensive analysis on the first permission function pool, the second permission function pool, the third permission function pool, and the fourth permission function pool to obtain the user's target permission information.

[0151] 208. The terminal receives the target permission information and displays the page content corresponding to the target permission information.

[0152] In this embodiment of the invention, for other descriptions of steps 201-208, please refer to the detailed description of steps 101-104 in Embodiment 1. This embodiment of the invention is not limited.

[0153] It is evident that implementation Figure 2The described product feature display method based on user permission management enables the terminal to obtain user identification information when the user triggers a login operation. This user identification information, along with the terminal identification information, is sent to the server. The server receives the dual identifiers and performs authentication processing, achieving unified authorization from both the user and device dimensions. This provides a data foundation for subsequent permission information matching. Upon successful authentication, the server determines the user's permission information using the dual identifiers and sends it to the terminal, triggering the terminal to receive permissions and display the corresponding page content. Through the user's login operation on the terminal combined with the interaction between the terminal and the server, product features are automatically displayed to the user. This not only meets the user's intelligent need for timely access to product features but also enables convenient product upgrades and the use of expandable functions, improving the user experience. Compared to the traditional passive verification method after the user accesses a function, this solution proactively reports user permissions to the server upon user login and analyzes user permissions using dual identifiers, improving the efficiency and timeliness of user permission information acquisition. Furthermore, the server can perform diverse processing on user identification information and terminal identification information to obtain multiple permission function pools. By comprehensively analyzing all permission function pools, the user's target permission information can be obtained, which helps to improve the accuracy and reliability of determining user permission information.

[0154] In an optional embodiment, the server in step 207 above performs a comprehensive analysis of the first permission function pool, the second permission function pool, the third permission function pool, and the fourth permission function pool to obtain the user's target permission information, including:

[0155] The server determines the maximum range of functional permissions for the terminal by analyzing the overlapping functional pools between the first and second permission functional pools.

[0156] The server determines the authorized function scope of the terminal based on the third permission function pool, and determines the local running function scope of the terminal based on the fourth permission function pool.

[0157] The server determines the user's primary permission information based on the maximum scope of functional permissions, the scope of authorized functional permissions, and the scope of locally running functional permissions.

[0158] The server performs binding and authorization analysis operations on user identification information and terminal identification information to obtain the user's secondary permission information;

[0159] The server determines at least one type of permission information from the set of permission information consisting of first permission information and second permission information as the user's target permission information.

[0160] In this embodiment of the invention, specifically, the overlapping function pool between the first and second permission function pools can be used to represent the maximum functional permission range of the terminal. This can be understood as functions that the user has purchased and the terminal can run, but whether they have been authorized and are ready locally has not yet been considered. The authorized range can be understood as functions for which the backend has already issued an authorization token to the terminal and the token is still valid. The locally running function range can be understood as functions for which the terminal-side components / data are already in place and do not need to be downloaded again.

[0161] In this embodiment of the invention, optionally, the first permission information includes one or more combinations of at least one currently supported function of the terminal, at least one currently authorized function of the user, and at least one permission type locally supported by the terminal. This embodiment of the invention does not limit the scope of the information.

[0162] In this embodiment of the invention, optionally, the second permission information includes at least one of the following: authorized terminal information, authorization authentication method for each authorized function, and timeliness data for each permission type. This embodiment of the invention does not impose any limitations on this information.

[0163] As can be seen, this optional embodiment enables the server to automatically determine the maximum functional permission range of the terminal by analyzing the overlapping functional pools between the first and second permission functional pools, determine the authorized functional range of the terminal based on the third permission functional pool, and determine the local operating functional range of the terminal based on the fourth permission functional pool. Subsequently, the user's first permission information is determined based on the maximum functional permission range, the authorized functional range, and the local operating functional range, which can improve the accuracy and efficiency of determining the first permission information. Furthermore, the server performs binding and authorization analysis operations on the user identification information and the terminal identification information to obtain the user's second permission information, which can improve the accuracy and efficiency of determining the second permission information. Finally, at least one permission information in the permission information set composed of the first permission information and the second permission information is determined as the user's target permission information, which can improve the accuracy and reliability of determining the user's target permission information.

[0164] In this optional embodiment, as an optional implementation, the server determines the user's first permission information based on the maximum functional permission scope, the authorized functional scope, and the locally running functional scope, including:

[0165] The server analyzes the overlapping and non-overlapping functional ranges among the maximum functional permission range, the authorized functional range, and the locally running functional range.

[0166] The server determines the user's primary permission information based on the overlapping and non-overlapping scope of functions.

[0167] In this embodiment of the invention, optionally, the functional overlap range includes at least the overlap range between the maximum functional permission range, the authorized functional range, and the locally running functional range, which can be referred to as a triple overlap range. Further optionally, it may also include at least one of the overlap ranges between the maximum functional permission range and the authorized functional range, the overlap range between the maximum functional permission range and the locally running functional range, and the overlap range between the authorized functional range and the locally running functional range, which can be referred to as pairwise overlap ranges. This embodiment of the invention does not impose limitations on this.

[0168] In this embodiment of the invention, optionally, the non-overlapping functional range includes at least one of the non-overlapping range of the maximum functional permission range, the non-overlapping range of the authorized functional range, and the non-overlapping range of the locally running functional range. Specifically, the non-overlapping range of the maximum functional permission range can represent a potential functional gap, which can be determined as: maximum functional permission range - (authorized functional range ∪ locally running functional range), representing a function that the terminal supports and the user may authorize, but which is neither authorized nor can be run locally (e.g., requires cloud activation). The non-overlapping range of the authorized functional range can represent authorization-dependent functions, which can be determined as: authorized functional range - (maximum functional permission range ∪ locally running functional range), representing functions that the user has authorized, but the terminal does not support or cannot run locally, and must rely on cloud services. The non-overlapping range of the locally running functional range can represent locally exclusive functions, which can be determined as: locally running functional range - (maximum functional permission range ∪ authorized functional range), representing functions that the terminal can run offline, but which are restricted by policy and are not authorized by the user or are not in the high-probability authorization pool; this embodiment of the invention does not limit this.

[0169] In this embodiment of the invention, specifically, the server extracts first-level supported functions (which can be understood as core functions) from the overlapping range between the maximum functional permission range, the authorized functional range, and the locally running functional range; and determines the functions extracted from the overlapping range between the maximum functional permission range and the authorized functional range, as well as the functions extracted from the overlapping range between the maximum functional permission range and the locally running functional range, as second-level supported functions (which can be understood as functions that need to meet preset dependency conditions, such as cloud verification or offline availability); and extracts third-level supported functions from the non-overlapping range of the maximum functional permission range (which can be understood as functions to be activated or restricted by policies); all currently supported functions of the terminal are at least one of the first-level, second-level, and third-level supported functions determined by the server.

[0170] In this embodiment of the invention, specifically, the server determines the core authorized function based on the overlap between the maximum functional permission range and the authorized function range. The core authorized function can represent a function that meets the user's expectation of a high probability of authorization. The server then determines the extended authorized function based on the non-overlapping range of the authorized function range. The extended authorized function can represent a function that belongs to special authorization or temporary permission and needs to be marked with an expiration date and restrictions. Subsequently, the server merges the core authorized function and the extended authorized function to obtain the user's currently authorized functions.

[0171] In this embodiment of the invention, all permission types supported locally by the terminal may include at least one of the following types: fully local permissions (representing permissions that do not require an internet connection and are permanently valid), conditional local permissions (representing permissions that require periodic verification or can only be used offline when specific conditions are met), and independent local permissions (representing permissions for system-level functions that are not affected by the user's authorization status, such as basic settings, offline mode, etc.). Specifically, the server classifies each function within the overlapping range of the maximum functional permission range, the authorized functional range, and the locally running functional range as fully local permissions; the server merges the maximum functional permission range and the authorized functional range to obtain a merged functional range, and classifies each function within the overlapping range between the locally running functional range and the merged functional range as conditional local permissions; the server classifies each function within the non-overlapping range of the locally running functional range as independent local permissions.

[0172] As can be seen, this optional implementation can analyze the functional overlap and non-overlapping ranges between the maximum functional permission range, the authorized functional range, and the locally running functional range through the server, and determine the user's first permission information based on the functional overlap and non-overlapping ranges. It can achieve a precise mapping from the permission range of the original permission function pool to the first permission information through the server, which not only ensures the legality of function authorization, but also takes into account the consistency between terminal execution capabilities and user experience.

[0173] In this optional embodiment, as another optional implementation, the server performs binding and authorization analysis operations on the user identification information and terminal identification information to obtain the user's second permission information, including:

[0174] The server uses the user's identifier information to locate the user's terminal binding information;

[0175] The server determines the authorized terminal information based on the terminal identification information and the user's terminal binding information;

[0176] The server determines the authorization and authentication method for each authorized function based on the security level field information corresponding to each authorized function contained in the first permission information.

[0177] The server calculates the expiration time parameter for each permission type based on the authorization record information obtained for each permission type, and determines the validity period data for that permission type based on the expiration time parameter and the obtained current time parameter.

[0178] In this embodiment of the invention, optionally, the terminal binding related information includes at least one of the following: the number of allowed bound terminals (which can be understood as the maximum number of terminals a user can bind), the number of bound terminals (which can be understood as the number of terminals a user has bound), and the identifier of the bound terminals. This embodiment of the invention does not limit the information.

[0179] In this embodiment of the invention, specifically, the terminal binding information is searched through user identification information. Then, by judging whether the terminal identification information is in the binding list, the binding time, the binding method (scanning code, SMS, email, administrator import), and whether the number of unbinding / rebinding attempts has exceeded the limit, the authorized terminal list and whether the current terminal is allowed to continue binding are determined, thus obtaining the authorized terminal information.

[0180] In this embodiment of the invention, optionally, the security level field information may include one of the following: low security level, medium security level, high security level, and highest security level. The low security level indicates a security level that includes a static license file, the medium security level indicates a security level that includes a dynamic password / one-time activation code, the high security level indicates a security level that includes a two-way TLS certificate and can respond to challenges in real time, and the highest security level indicates a security level that includes a certificate and a secondary authentication method using face / fingerprint. This embodiment of the invention does not impose any limitations on this.

[0181] In this embodiment of the invention, optionally, the validity period data for each permission type can be calculated through each authorization record. Each authorization record includes a time-based authorization record and / or a count-based authorization record (e.g., remaining authorization counts), and also includes an offline grace period (which can be understood as the number of hours the terminal is allowed to remain usable offline). The time-based authorization record can include an absolute expiration time (which can be understood as the user contract expiration time, the authorization token's own expiration time, the terminal registration validity period, etc.) and a relative remaining duration. The relative remaining duration can be obtained by subtracting the current time from the absolute expiration time; this embodiment of the invention does not impose limitations on this.

[0182] As can be seen, this optional implementation can use the server to find the user's terminal binding information based on the user's identification information, thereby determining the authorized terminal information based on the terminal identification information and the user's terminal binding information, which can improve the accuracy and efficiency of determining the authorized terminal information. Furthermore, based on the security level field information corresponding to each authorized function included in the obtained first permission information, the authorization authentication method for each authorized function can be determined, which can improve the accuracy and efficiency of determining the authorization authentication method for authorized functions. Moreover, based on the authorization record information of each permission type obtained, the permission expiration time parameter for that permission type can be calculated, and based on the permission expiration time parameter and the obtained current time parameter, the validity data for that permission type can be determined, which can improve the accuracy and reliability of determining the validity data for each permission type. By determining the authorized terminal information, the authorization authentication method, and the validity data for various permissions, the accuracy and reliability of determining the second permission information can be improved.

[0183] For example, such as Figure 3 As shown, Figure 3 This is a schematic diagram of a product function display interface from a user's perspective, as disclosed in an embodiment of the present invention. This product function display interface can showcase popular functions of the terminal (such as...). Figure 3 The Hotfunctions shown may include airbag repositioning functions (such as...). Figure 3 The Airbag Reset and BMS reset functions shown are as follows. Figure 3 The BMS Reset and ADAS calibration functions shown are as follows: Figure 3 The ADAS calibration shown), anti-theft key function (such as...) Figure 3 IMMO keys shown), smart key matching (such as...) Figure 3 The Smart key matching and PIN code reading functions shown are illustrated. Figure 3 At least one of the following (PINCode reading) is allowed: if a function displays a locked icon, it means that the function is not currently authorized to the user / terminal.

[0184] In embodiments of the present invention, such as Figure 4 As shown, Figure 4 This is a schematic diagram of the system architecture of a product function demonstration system disclosed in an embodiment of the present invention. The system architecture includes a server and a smart terminal, and the server and the smart terminal can communicate bidirectionally. Figure 5 As shown, Figure 5 This is a structural diagram of a core module of a server disclosed in an embodiment of the present invention. The server may include a user permission management module, a user access management module, a networking module, a permission encoding module, a user permission database, and other modules. Figure 6 As shown, Figure 6 This is a structural diagram of a core module of a smart terminal disclosed in an embodiment of the present invention. The smart terminal may include a user interaction module, a network module, a permission decoding module, and other modules. (Combined with...) Figures 3-6 The function of each module in the server and smart terminal is as follows:

[0185] Both the network module of the server and the network module of the smart terminal are used to realize the function of network access, which is the basic infrastructure of the standard;

[0186] The user access management module provides API interfaces to meet the access needs of smart terminals and performs authentication and other related information interaction processing. If authentication is successful, it records the unique identifier of the terminal (terminal ID) and the unique identifier of the user (user ID) for this login.

[0187] The permission encoding module is used to encrypt the corresponding permissions (including but not limited to): currently supported functions (including unauthorized functions), currently authorized functions, and the validity period of various permissions obtained from the user permission database based on the user's login information, and to encrypt them together with the terminal's unique identifier (terminal ID) and the user's unique identifier (user ID).

[0188] The user permission management module is used to manage the permissions of users and their devices, such as reading, storing, and changing permissions.

[0189] The user permission database is used to store information related to the permissions of a username and the devices under that username, such as (including but not limited to): currently supported functions (including unauthorized functions), currently authorized functions, locally supported permissions, authorized terminal information, authorization authentication methods, validity data of various permissions, and at least one other auxiliary information;

[0190] The permission decoding module is used to decode the data transmitted by the server according to the "encoding" rules. If the permission encoding module has performed encryption, the permission decoding module will also perform decryption.

[0191] The user interaction module is used to display the interactive interface for users to operate the software.

[0192] Combination Figures 3-6 The specific steps for implementing the product function display method based on user permission management through the above system include:

[0193] When a user triggers a login operation through the user interaction module, the user interaction module obtains the user's user identification information based on the login operation.

[0194] The second networking module sends the user identification information and the terminal identification information of the terminal to the first networking module;

[0195] The first networking module receives terminal identification information and user identification information;

[0196] The user access management module performs authentication and interaction processing on terminal identification information and user identification information.

[0197] When authentication is successful, the user permission management module determines the user's target permission information based on the user identification information and the terminal identification information;

[0198] The permission encoding module performs an encoding operation on the target permission information to obtain the permission encoding information;

[0199] The first network module sends the permission encoding information to the second network module;

[0200] The second network module receives the authorization code information;

[0201] The permission decoding module performs a decoding operation on the permission encoding information to obtain the permission decoding information;

[0202] The user interaction module displays the page content corresponding to the permission decoding information.

[0203] For example, when a user launches an App (application), the login process is completed based on the network module, which uses the user's account (such as username, user ID, email, etc.) and verification credentials (such as password, dynamic code, SMS, etc.).

[0204] Users complete corresponding interactive operations (such as information display, function operation, etc.) based on the user interaction module.

[0205] During interactive operations, including the display of related functions, the terminal connects to the server through its network module and reports the current terminal identification information to the server. The terminal identification information includes (but is not limited to): user ID, terminal ID, etc.

[0206] The user permission management module retrieves the corresponding permissions from the user permission database based on user identification information and terminal identification information;

[0207] The permission encoding module performs structured processing on the transmitted data (including permissions) (to facilitate terminal recognition) and performs data security encryption.

[0208] The server sends the information processed by the permission encoding module to the terminal via the network module.

[0209] After receiving the corresponding information, the terminal completes the decoding and decryption process through the permission decoding module. After decryption, relevant information is obtained, such as (including but not limited to): currently supported functions (including unauthorized functions), currently authorized functions, locally supported permissions, authorized terminal information, authorization authentication method, validity data of various permissions, and at least one other auxiliary information.

[0210] The user interaction module displays different functional sections differently based on the decoded permission information, such as (including but not limited to): directly displaying the function and its usage, function update prompts and usage after the function update, function restrictions (such as whether authorization is required through purchase or other means), and at least one of the following: the user's completion of product usage as indicated by the function display.

[0211] Example 3

[0212] Please see Figure 7 , Figure 7 This is a schematic diagram of the structure of a product function display system based on user permission management, as disclosed in an embodiment of the present invention. Figure 7 The described product function display system based on user permission management includes a server 30 (including a local server or a cloud server) and a terminal 40 (such as a mobile phone, tablet, etc.), which are not limited in this embodiment of the invention. Figure 7 As shown, server 30 includes user access management module 301, user access management module 302, and first networking module 303; terminal 40 includes user interaction module 401 and second networking module 402, wherein:

[0213] User interaction module 401 is used to obtain the user's user identification information based on the login operation when the user triggers the login operation through user interaction module 401.

[0214] The second networking module 402 is used to send user identification information and terminal 40 identification information of terminal 40 to the first networking module 303;

[0215] The first networking module 303 is used to receive terminal 40 identification information and user identification information;

[0216] User access management module 302 is used to perform authentication interaction processing on terminal 40 identification information and user identification information;

[0217] The user permission management module 301 is used to determine the user's target permission information based on the user identification information and the terminal 40 identification information when authentication is successful.

[0218] The first network module 303 is also used to send the target permission information to the second network module 402;

[0219] The second network module 402 is also used to receive target permission information;

[0220] User interaction module 401 is used to display the page content corresponding to the target permission information;

[0221] The permission information includes at least one currently supported function of the terminal 40, at least one currently authorized function of the user, at least one permission type locally supported by the terminal 40, authorization terminal 40 information, authorization authentication method for each authorized function, and at least one time limit data for each permission type.

[0222] It is evident that implementation Figure 7 The described product function display system based on user permission management enables terminal 40 to obtain user identification information when a user triggers a login operation. This user identification information, along with terminal 40 identification information, is then sent to server 30. Server 30 receives the dual identifiers and performs authentication processing, achieving unified authorization from both human and device dimensions. This provides a data foundation for subsequent permission information matching. Upon successful authentication, server 30 determines the user's permission information using the dual identifiers and sends it to terminal 40, triggering terminal 40 to receive permissions and display the corresponding page content. Through the user's login operation on terminal 40, combined with the linkage between terminal 40 and server 30, product functions are automatically displayed to the user. This not only meets the user's intelligent need for timely access to product functions but also allows for convenient product upgrades and the use of expandable functions, improving the user experience. Compared to the traditional passive verification method after user access to functions, this solution proactively reports user permissions to server 30 upon user login to terminal 40 and analyzes user permissions using dual identifiers, improving the efficiency and timeliness of user permission information acquisition.

[0223] In an optional embodiment, the user permission management module 301 determines the user's target permission information based on the user identification information and the terminal 40 identification information, including:

[0224] Based on the user identification information, determine the user's user contract information, and based on the user contract information, retrieve the user's first permission function pool from the user permission database corresponding to server 30. The first permission function pool includes at least one function whose authorization probability is greater than or equal to a preset probability.

[0225] Based on the terminal 40 identification information, the terminal 40 capability information is determined, and based on the terminal 40 capability information, the second permission function pool of the terminal 40 is determined. The second permission function pool includes at least one function supported by the terminal 40.

[0226] Based on the pre-established association mapping model between the user and terminal 40 identifier joint key and the authorization function, the third permission function pool is determined according to the target joint key between the user identifier information and the terminal 40 identifier information. The third permission function pool includes at least one function of the authorized user of the terminal 40.

[0227] Based on the local list information sent by the terminal 40, the fourth permission function pool of the terminal 40 is determined. The fourth permission function pool includes at least one function that the terminal 40 can run locally.

[0228] A comprehensive analysis of the first, second, third, and fourth permission function pools is conducted to obtain the user's target permission information.

[0229] As can be seen, this optional embodiment can perform diversified processing on user identification information and terminal identification information through server 30 to obtain multiple permission function pools. Thus, the user's target permission information can be obtained through comprehensive analysis of all permission function pools, which helps to improve the accuracy and reliability of user permission information determination.

[0230] In this optional embodiment, as an optional implementation method, the user permission management module 301 performs comprehensive analysis on the first permission function pool, the second permission function pool, the third permission function pool, and the fourth permission function pool to obtain the user's target permission information in the following specific ways:

[0231] By analyzing the overlapping function pools between the first and second permission function pools, the maximum range of function permissions for terminal 40 is determined.

[0232] Based on the third permission function pool, the authorized function scope of terminal 40 is determined, and based on the fourth permission function pool, the local operation function scope of terminal 40 is determined.

[0233] Based on the maximum functional permission range, the authorized functional range, and the locally running functional range, the user's first permission information is determined. The first permission information includes at least one currently supported function of terminal 40, at least one currently authorized function of the user, and one or more combinations of at least one permission type locally supported by terminal 40.

[0234] Perform authentication-related operations on user identification information and terminal 40 identification information to obtain the user's second permission information. The second permission information includes at least one of the following: authorized terminal 40 information, authorization authentication method for each authorized function, and timeliness data for each permission type.

[0235] Determine at least one permission information from the set of permission information consisting of first permission information and second permission information as the user's target permission information.

[0236] As can be seen, this optional implementation allows the server 30 to automatically determine the maximum functional permission range of the terminal 40 by analyzing the overlapping functional pools between the first and second permission functional pools, determine the authorized functional range of the terminal 40 based on the third permission functional pool, and determine the local operating functional range of the terminal 40 based on the fourth permission functional pool. Subsequently, the user's first permission information is determined based on the maximum functional permission range, the authorized functional range, and the local operating functional range, which can improve the accuracy and efficiency of determining the first permission information. Furthermore, the server 30 performs binding and authorization analysis operations on the user identification information and the terminal 40 identification information to obtain the user's second permission information, which can improve the accuracy and efficiency of determining the second permission information. Finally, at least one permission information in the permission information set composed of the first permission information and the second permission information is determined as the user's target permission information, which can improve the accuracy and reliability of determining the user's target permission information.

[0237] In this optional implementation, the user permission management module 301 may determine the user's first permission information based on the maximum functional permission range, the authorized functional range, and the locally running functional range in the following ways:

[0238] Analyze the overlapping and non-overlapping functional ranges among the maximum functional permission range, the authorized functional range, and the locally running functional range;

[0239] Determine the user's first permission information based on the overlapping and non-overlapping scope of functions.

[0240] As can be seen, this optional implementation can also analyze the functional overlap and non-overlapping ranges between the maximum functional permission range, the authorized functional range, and the locally running functional range through the server 30. Based on the functional overlap and non-overlapping ranges, the user's first permission information can be determined. The server 30 can achieve a precise mapping from the permission range of the original permission function pool to the first permission information, which not only ensures the legality of function authorization, but also takes into account the consistency between the execution capability of the terminal 40 and the user experience.

[0241] In this optional implementation, the user permission management module 301 may optionally perform binding and authorization analysis operations on the user identification information and the terminal 40 identification information to obtain the user's second permission information in the following specific ways:

[0242] Based on the user identification information, find the user's terminal 40 binding information. The terminal 40 binding information includes at least one of the following: the number of allowed bound terminals 40, the number of bound terminals 40, and the identifier of the bound terminal 40.

[0243] The authorized terminal 40 information is determined based on the terminal 40 identification information and the user's terminal 40 binding information;

[0244] Based on the security level field information corresponding to each authorized function contained in the first permission information, determine the authorization and authentication method for each authorized function.

[0245] Based on the authorization record information of each permission type, calculate the permission expiration time parameter for that permission type, and determine the validity period data for that permission type based on the permission expiration time parameter and the obtained current time parameter.

[0246] As can be seen, this optional implementation can also use the server 30 to find the user's terminal 40 binding information based on the user identification information, thereby determining the authorized terminal 40 information based on the terminal 40 identification information and the user's terminal 40 binding information, which can improve the accuracy and efficiency of determining the authorized terminal 40 information. Furthermore, based on the security level field information corresponding to each authorized function included in the obtained first permission information, the authorization authentication method for each authorized function can be determined, which can improve the accuracy and efficiency of determining the authorization authentication method for authorized functions. Moreover, based on the obtained authorization record information for each permission type, the permission expiration time parameter for that permission type can be calculated, and based on the permission expiration time parameter and the obtained current time parameter, the validity data for that permission type can be determined, which can improve the accuracy and reliability of determining the validity data for each permission type. By determining the authorized terminal 40 information, the authorization authentication method, and the validity data for various permissions, the accuracy and reliability of determining the second permission information can be improved.

[0247] In another alternative embodiment, such as Figure 8 As shown, Figure 8 This is a schematic diagram of another product function display system based on user permission management disclosed in an embodiment of the present invention, wherein the server 30 further includes a permission encoding module 304, wherein:

[0248] The permission encoding module 304 is used to perform encoding operations on the target permission information to obtain permission encoding information;

[0249] The permission encoding module 304 performs an encoding operation on the target permission information, and the specific methods for obtaining the permission encoding information include:

[0250] The target permission information is structured to obtain the processed target permission information;

[0251] The processed target permission information is then encrypted to obtain permission encoding information.

[0252] Furthermore, the specific methods by which the first network module 303 sends the target permission information to the second network module 402 include:

[0253] The first network module 303 sends the permission encoding information to the second network module 402.

[0254] As can be seen, this optional embodiment can, after determining the user's target permission information, perform structured processing on the target permission information by the server 30 to facilitate subsequent identification by the terminal 40, and then perform data security encryption processing on the processed target permission information to obtain permission encoding information and provide it to the terminal 40. By performing comprehensive processing such as structuring and security encryption on the permission information to be provided to the terminal 40, the recognition efficiency and information security of permission information can be improved.

[0255] In this optional embodiment, as an optional implementation, the target permission information received by the second networking module 402 is permission encoding information;

[0256] And, such as Figure 8 As shown, terminal 40 also includes a permission decoding module 403, wherein:

[0257] The permission decoding module 403 is used to perform a decoding operation on the permission encoded information to obtain the permission decoded information;

[0258] Furthermore, the specific methods by which the user interaction module 401 displays the page content corresponding to the target permission information include:

[0259] Display the page content corresponding to the permission decoding information.

[0260] As can be seen, this optional implementation can improve the accuracy, efficiency and security of user permission information transmission by using the information transmission method of encoding by server 30 and decoding by terminal 40, thereby further improving the efficiency of obtaining user permission information.

[0261] Example 4

[0262] Please see Figure 9 , Figure 9 This is a schematic diagram of the structure of another product function display system based on user permission management disclosed in an embodiment of the present invention. For example... Figure 9 As shown, this product function display system based on user permission management may include:

[0263] Memory 401 storing executable program code;

[0264] Processor 402 coupled to memory 401;

[0265] The processor 402 calls the executable program code stored in the memory 401 to execute the steps in the product function display method based on user permission management described in Embodiment 1 or Embodiment 2 of the present invention.

[0266] Example 5

[0267] This invention discloses a computer storage medium storing computer instructions. When these computer instructions are invoked, they are used to execute the steps in the product function display method based on user permission management described in Embodiment 1 or Embodiment 2 of this invention.

[0268] Example 6

[0269] This invention discloses a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to perform the steps in the product function display method based on user permission management described in Embodiment 1 or Embodiment 2.

[0270] The system embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0271] Through the detailed description of the above embodiments, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, including read-only memory (ROM), random access memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), one-time programmable read-only memory (OTPROM), electrically-Erasable Programmable Read-Only Memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, disk storage, magnetic tape storage, or any other computer-readable medium that can be used to carry or store data.

[0272] Finally, it should be noted that the product function display method and system based on user permission management disclosed in the embodiments of the present invention are merely preferred embodiments of the present invention, and are only used to illustrate the technical solutions of the present invention, and not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for displaying product functions based on user permission management, characterized in that, The method is applied to a product function demonstration system, which includes a server and a terminal, and the method includes: When a user triggers a login operation through the terminal, the terminal obtains the user's user identification information according to the login operation, and sends the user identification information and the terminal's terminal identification information to the server; The server receives the terminal identification information and the user identification information, and performs authentication interaction processing on the terminal identification information and the user identification information; when authentication is successful, the server determines the user's target permission information based on the user identification information and the terminal identification information, and sends the target permission information to the terminal. The terminal receives the target permission information and displays the page content corresponding to the target permission information; The permission information includes at least one currently supported function of the terminal, at least one currently authorized function of the user, at least one permission type locally supported by the terminal, authorized terminal information, authorization authentication method for each authorized function, and at least one time-limited data for each permission type. The server determines the user's target permission information based on the user identification information and the terminal identification information, including: The server determines the user's user contract information based on the user identification information, and obtains the user's first permission function pool from the user permission database corresponding to the server based on the user contract information. The first permission function pool includes at least one function whose authorization probability is greater than or equal to a preset probability. The server determines the terminal capability information of the terminal based on the terminal identification information, and determines the second permission function pool of the terminal based on the terminal capability information. The second permission function pool includes at least one function supported by the terminal. The server determines a third permission function pool based on a pre-established association mapping model between user and terminal identifier key and authorized functions, according to the target key between the user identifier information and the terminal identifier information. The third permission function pool includes at least one function that the terminal has authorized to the user. The server determines the fourth permission function pool of the terminal based on the local list information sent by the terminal. The fourth permission function pool includes at least one function that the terminal can run locally. The server performs a comprehensive analysis of the first permission function pool, the second permission function pool, the third permission function pool, and the fourth permission function pool to obtain the user's target permission information.

2. The product function display method based on user permission management according to claim 1, characterized in that, The server performs a comprehensive analysis of the first permission function pool, the second permission function pool, the third permission function pool, and the fourth permission function pool to obtain the user's target permission information, including: The server determines the maximum range of functional permissions for the terminal by analyzing the overlapping functional pools between the first permission functional pool and the second permission functional pool. The server determines the authorized function scope of the terminal based on the third permission function pool, and determines the local running function scope of the terminal based on the fourth permission function pool. The server determines the user's first permission information based on the maximum functional permission range, the authorized functional range, and the locally running functional range. The first permission information includes at least one currently supported function of the terminal, at least one currently authorized function of the user, and one or more combinations of at least one permission type locally supported by the terminal. The server performs binding and authorization analysis operations on the user identification information and the terminal identification information to obtain the user's second permission information. The second permission information includes at least one of the following: authorized terminal information, authorization authentication method for each authorized function, and timeliness data for each permission type. The server determines at least one permission information from the permission information set consisting of the first permission information and the second permission information as the user's target permission information.

3. The product function display method based on user permission management according to claim 2, characterized in that, The server determines the user's first permission information based on the maximum functional permission range, the authorized functional range, and the local operating functional range, including: The server analyzes the functional overlap and non-overlapping ranges among the maximum functional permission range, the authorized functional range, and the locally running functional range; The server determines the user's first permission information based on the overlapping range of functions and the non-overlapping range of functions.

4. The product function display method based on user permission management according to claim 3, characterized in that, The server performs binding and authorization analysis operations on the user identification information and the terminal identification information to obtain the user's second permission information, including: The server searches for the user's terminal binding information based on the user identification information. The terminal binding information includes at least one of the following: the number of allowed bound terminals, the number of already bound terminals, and the identifier of the bound terminals. The server determines the authorized terminal information based on the terminal identification information and the user's terminal binding information; The server determines the authorization and authentication method for each authorized function based on the security level field information corresponding to each authorized function contained in the first permission information. The server calculates the expiration time parameter of each permission type based on the authorization record information obtained for each permission type, and determines the validity data of the permission type based on the expiration time parameter and the obtained current time parameter.

5. The product function display method based on user permission management according to any one of claims 1-4, characterized in that, The method further includes: The server performs an encoding operation on the target permission information to obtain permission encoding information; The server performs an encoding operation on the target permission information to obtain permission encoding information, including: The server performs structured processing on the target permission information to obtain processed target permission information; The server performs data security encryption on the processed target permission information to obtain permission encoding information; And, the server sends the target permission information to the terminal, including: The server sends the permission encoding information to the terminal.

6. The product function display method based on user permission management according to claim 5, characterized in that, The target permission information received by the terminal is the permission encoding information; Furthermore, the method further includes: The terminal performs a decoding operation on the permission encoding information to obtain permission decoding information; And, the terminal displays the page content corresponding to the target permission information, including: The terminal displays the page content corresponding to the permission decoding information.

7. A product function display system based on user permission management, characterized in that, The system includes a server and a terminal. The server includes a user permission management module, a user access management module, and a first networking module. The terminal includes a user interaction module and a second networking module. The system is used to execute the product function display method based on user permission management as described in any one of claims 1-6, wherein: The user interaction module is used to obtain the user's user identification information according to the login operation when the user triggers the login operation through the user interaction module. The second network module is used to send the user identification information and the terminal identification information of the terminal to the first network module; The first network module is used to receive the terminal identification information and the user identification information; The user access management module is used to perform authentication interaction processing on the terminal identification information and the user identification information. The user permission management module is used to determine the user's target permission information based on the user identification information and the terminal identification information when authentication is successful. The first network module is further configured to send the target permission information to the second network module; The second network module is also used to receive the target permission information; The user interaction module is used to display the page content corresponding to the target permission information; The permission information includes at least one currently supported function of the terminal, at least one currently authorized function of the user, at least one permission type locally supported by the terminal, authorized terminal information, authorization authentication method for each authorized function, and at least one time limit data for each permission type.

8. A product function display system based on user permission management, characterized in that, The system includes: Memory containing executable program code; A processor coupled to the memory; The processor calls the executable program code stored in the memory to execute the product function display method based on user permission management as described in any one of claims 1-6.

9. A computer storage medium, characterized in that, The computer storage medium stores computer instructions, which, when invoked, are used to execute the product function display method based on user permission management as described in any one of claims 1-6.

Images