CN112995200A

CN112995200A - Resource value evaluation user management method based on cloud platform and related product

Info

Publication number: CN112995200A
Application number: CN202110354688.3A
Authority: CN
Inventors: 苑文佳
Original assignee: Shenzhen United Assets And Equity Exchange Co ltd
Current assignee: Shenzhen United Assets And Equity Exchange Co ltd
Priority date: 2019-01-11
Filing date: 2020-01-11
Publication date: 2021-06-18
Anticipated expiration: 2040-01-11
Also published as: CN112995201A; CN111212082B; CN111212082A; CN112995200B; CN112995201B

Abstract

The embodiment of the application discloses a resource value evaluation user management method based on a cloud platform and a related product, wherein the method comprises the following steps: the cloud platform receives a user account registration request Reg-rq1 from a Client 1; confirming account registration type C1 carried in the user account registration request Reg-rq1 and K1 account information parameters required by the account registration type C1; sending an account information parameter acquisition request Get-rq1 to a Client1 to acquire K1 account information parameters input by a user; determining the belonged user level L1 according to K1 account information parameters input by the user; the K1 account information parameters are correlated and then imported into a signed user database matched with the user level L1 for storage; and sending a prompt that the account registration is successful to the Client 1. By implementing the embodiment of the application, the users to be registered can be classified and registered according to the grades, so that the hierarchical management of the users on the platform is facilitated.

Description

Resource value evaluation user management method based on cloud platform and related product

Technical Field

The application relates to the technical field of networks and computers, in particular to a resource value evaluation user management method based on a cloud platform and a related product.

Background

Currently, resource (physical resource or non-physical resource) value assessment is an important technical requirement. Due to the fact that the resource types are all five-door, different types of resources need to use different value evaluation models; even homogeneous resources, in many cases, different individuals or businesses may use different value assessment models for value assessment. In addition, with the increasing demand, more and more users are required to perform resource value evaluation, and the users are also required to be more and more complicated, which causes great troubles to the user management.

Disclosure of Invention

The embodiment of the application provides a resource value evaluation user management method based on a cloud platform and a related product, which can classify and register users to be registered according to grades, so that hierarchical management of the users on the platform is facilitated.

In a first aspect, an embodiment of the present application provides a resource value assessment user management method based on a cloud platform, including:

the cloud platform receives a user account registration request Reg-rq1 from a Client 1;

the cloud platform analyzes the user account registration request Reg-rq1, and confirms an account registration type C1 carried in the user account registration request Reg-rq 1;

the cloud platform searches an account category registry matched with the account registration category C1 in a local standard registry set, and determines K1 account information parameters required for account registration according to the account category registry;

the cloud platform sends an account information parameter acquisition request Get-rq1 to the Client1, where the account information parameter acquisition request Get-rq1 carries an account information parameter demand page P1 to be input, where the account information parameter demand page P1 to be input includes K1 information input areas, the K1 information input areas are used to input the K1 account information parameters required for user account registration, respectively, where K1 is an integer greater than 1;

the cloud platform receives an account information parameter acquisition response Get-res1 which is sent by the Client1 and used for responding to the account information parameter acquisition request Get-rq1, wherein the account information parameter acquisition response Get-res1 carries an input account information parameter demand page P1;

the cloud platform extracts the K1 account information parameters from the input account information parameter demand page P1, and determines the user level L1 according to the K1 account information parameters;

the cloud platform associates the K1 account information parameters and then guides the associated account information parameters into a signed user database matched with the user level L1 for storage;

the cloud platform sends a user account registration response Reg-res1 for responding to the user account registration request Reg-rq1 to the Client1, wherein the user account registration response Reg-res1 carries a prompt that account registration is successful.

As an optional implementation manner, the cloud platform parsing the user account registration request Reg-rq1 and confirming the account registration category C1 carried in the user account registration request Reg-rq1 includes:

the cloud platform analyzes the user account registration request Reg-rq1, and sends an account registration category confirmation request Con-rq1 to the Client1, where the account registration category confirmation request Con-rq1 carries a registration category confirmation page P2 to be input, where the registration category confirmation page P2 to be input includes M1 account registration category options, where the M1 account registration category options only allow one account registration category option to be checked at the same time, and the M1 is an integer greater than 1;

the cloud platform receives an account registration category confirmation response Con-res1 which is sent by the Client1 and used for responding to the account registration category confirmation request Con-rq1, wherein the account registration category confirmation response Con-res1 carries an input registration category confirmation page P2, and an account registration category C1 option in the input registration category confirmation page P2 is selected by a user;

and the cloud platform analyzes the account registration type confirmation response Con-res1 to obtain the account registration type C1.

As an optional implementation manner, the cloud platform extracts the K1 account information parameters from the input account information parameter demand page P1, and determines the user level L1 according to the K1 account information parameters, including:

the cloud platform extracts the K1 account information parameters from the input account information parameter demand page P1, and searches whether the K1 account information parameters are the same as at least one account information parameter of one of the signed users in a local all-signed user database;

if the K1 account information parameters are different from the account information parameters of all the signed users, the cloud platform determines the level L1 of the user according to the K1 account information parameters;

if at least one item of account information parameters of the K1 account information parameters is the same as that of one signed user, but the signed user is in a failure state, the cloud platform determines the level L1 of the user according to the K1 account information parameters.

As an optional implementation, the method further comprises:

if at least one item of account information parameters of the K1 users is the same as that of one of the signed users, and the signed user is in an effective state, the cloud platform sends an account information parameter acquisition request Get-rq2 to the Client1, the account information parameter acquisition request Get-rq2 carries the input account information parameter demand page P1, the account information parameters in the input account information parameter demand page P1, which are the same as those of the signed user, are marked to mark that the account information parameters exist, and the user needs to change the account information parameters.

As an optional implementation, the method further comprises:

the cloud platform receives a resource value evaluation request Val-rq1 aiming at a resource R1, which is sent by the Client 1;

the cloud platform determines the access right corresponding to the user level L1 according to the user level L1;

the cloud platform determines a value evaluation report of the resource R1 according to the access right;

and the cloud platform sends a resource value evaluation response Val-res1 for responding to the resource value evaluation request Val-rq1 to the Client1, wherein the resource value evaluation response Val-res1 carries the value evaluation report.

In a second aspect, an embodiment of the present application provides a cloud platform, including:

a processor and a memory coupled to each other;

the processor is used for receiving a user account registration request Reg-rq1 from a Client 1;

analyzing the user account registration request Reg-rq1, and confirming an account registration type C1 carried in the user account registration request Reg-rq 1;

searching an account category registry matched with the account registration category C1 in a local standard registry set stored in the memory, and determining K1 account information parameters required for account registration according to the account category registry;

sending an account information parameter acquisition request Get-rq1 to the Client1, where the account information parameter acquisition request Get-rq1 carries an account information parameter demand page P1 to be input, where the account information parameter demand page P1 to be input includes K1 information input areas, the K1 information input areas are used to input the K1 account information parameters required for user account registration, respectively, where the K1 is an integer greater than 1;

receiving an account information parameter acquisition response Get-res1 sent by the Client1 and used for responding to the account information parameter acquisition request Get-rq1, wherein the account information parameter acquisition response Get-res1 carries an input account information parameter demand page P1;

extracting the K1 account information parameters from the input account information parameter demand page P1, and determining the affiliated user level L1 according to the K1 account information parameters;

the K1 account information parameters are correlated and then imported into a signed user database matched with the user level L1 for storage;

and sending a user account registration response Reg-res1 for responding to the user account registration request Reg-rq1 to the Client1, wherein the user account registration response Reg-res1 carries a prompt that account registration is successful.

As an optional implementation manner, the processor analyzes the user account registration request Reg-rq1, and confirms the account registration category C1 carried in the user account registration request Reg-rq1 in a specific manner:

the processor analyzes the user account registration request Reg-rq1, and sends an account registration category confirmation request Con-rq1 to the Client1, where the account registration category confirmation request Con-rq1 carries a registration category confirmation page P2 to be input, where the registration category confirmation page P2 to be input includes M1 account registration category options, the M1 account registration category options only allow one account registration category option to be checked at the same time, and the M1 is an integer greater than 1;

receiving an account registration type confirmation response Con-res1 sent by the Client1 and used for responding to the account registration type confirmation request Con-rq1, wherein the account registration type confirmation response Con-res1 carries an input registration type confirmation page P2, and an account registration type C1 option in the input registration type confirmation page P2 is selected by a user;

and analyzing the account registration type confirmation response Con-res1 to obtain the account registration type C1.

As an optional implementation manner, the manner in which the processor extracts the K1 account information parameters from the input account information parameter demand page P1 and determines the corresponding user level L1 according to the K1 account information parameters is specifically as follows:

the processor extracts the K1 account information parameters from the input account information parameter demand page P1, and searches whether the K1 account information parameters are the same as at least one account information parameter of one of the signed users in a local all-signed user database;

if the K1 account information parameters are different from the account information parameters of all the signed users, determining the level L1 of the user according to the K1 account information parameters;

and if at least one item of account information parameters of the K1 account information parameters is the same as the account information parameters of one of the signed users, and the signed user is in a failure state, determining the level L1 of the user according to the K1 account information parameters.

As an optional implementation manner, if at least one item of account information parameters of the K1 account information parameters is the same as that of one of the signed users, and the signed user is in an active state, the processor is further configured to send an account information parameter obtaining request Get-rq2 to the Client1, where the account information parameter obtaining request Get-rq2 carries the input account information parameter demand page P1, and the account information parameter that is the same as that of the signed user in the input account information parameter demand page P1 is provided with a flag to flag that the account information parameter already exists, and the user needs to change the account information parameter.

As an optional implementation manner, the processor is further configured to receive a resource value evaluation request Val-rq1 sent by the Client1 for the resource R1;

according to the user level L1, determining the access right corresponding to the user level L1;

determining a value evaluation report of the resource R1 according to the access authority;

and sending a resource value evaluation response Val-res1 for responding to the resource value evaluation request Val-rq1 to the Client1, wherein the resource value evaluation response Val-res1 carries the value evaluation report.

In a third aspect, embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored, where the computer program is executed by hardware (for example, a processor, and the like) to implement part or all of steps of any one of the methods performed by the cloud platform in the embodiments of the present application.

In a fourth aspect, embodiments of the present application provide a computer program product comprising instructions that, when run on a cloud platform, cause the cloud platform to perform some or all of the steps of the method of the above aspects.

In the embodiment of the application, when a user wants to evaluate resource value on a cloud platform, account registration can be performed on the cloud platform, specifically, the cloud platform can receive a user account registration request Reg-rq1 from a Client1, and analyze the user account registration request Reg-rq1 to obtain an account registration category C1 carried by the user account registration request Reg-rq 1; searching an account category registry matched with the account registration category C1 in the local standard registry set, and determining K1 account information parameters required for account registration according to the account category registry; sending an account information parameter acquisition request Get-rq1 to a Client1 to request a user to input the K1 account information parameters; the cloud platform receives an account information parameter acquisition response Get-res1 which is sent by a Client1 and used for responding to an account information parameter acquisition request Get-rq1, wherein the account information parameter acquisition response Get-res1 carries the input K1 account information parameters; the user level L1 can be determined according to the K1 account information parameters; the K1 account information parameters are correlated and then imported into a signed user database matched with the user level L1 for storage; the cloud platform sends a user account registration response Reg-res1 for responding to the user account registration request Reg-rq1 to the Client1, wherein the prompt that the account registration is successful is carried. Therefore, by implementing the embodiment of the application, the users to be registered can be classified and registered according to the grades, so that the hierarchical management of the users on the platform is facilitated.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.

Fig. 1 is a schematic structural diagram of a communication system according to an embodiment of the present application;

fig. 2 is a schematic flowchart of a resource value assessment user management method based on a cloud platform according to an embodiment of the present application;

fig. 3 is a layout diagram of an account registration category confirmation page P2 according to an embodiment of the present application;

fig. 4 is a layout schematic diagram of an account information parameter requirement page P1 provided in the embodiment of the present application;

FIG. 5 is a schematic flow chart of resource value evaluation provided in the embodiments of the present application;

fig. 6 is a schematic structural diagram of a cloud platform provided in an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

It should be noted that the terms "comprises" and "comprising," and any variations thereof, in the embodiments of the present application, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

The embodiment of the application discloses a resource value evaluation user management method based on a cloud platform and a related product, which can classify and register users to be registered according to grades, so that hierarchical management of the users on the platform is facilitated. The following detailed description is made with reference to the accompanying drawings.

Referring to fig. 1, an embodiment of the present application provides a communication system. As shown in fig. 1, the communication system may include at least a cloud platform 110 and a client 120 interconnected by a network. The technical solution of the embodiment of the present application may be implemented based on the communication system with the architecture illustrated in fig. 1 by way of example or a modified architecture thereof.

Referring to fig. 2, an embodiment of the present application provides a resource value evaluation user management method based on a cloud platform. As shown in fig. 2, the method may include, but is not limited to, the following steps:

210. the cloud platform receives a user account registration request Reg-rq1 from a Client 1.

220. The cloud platform parses the user account registration request Reg-rq1, and confirms the account registration category C1 carried in the user account registration request Reg-rq 1.

In the embodiment of the application, the user account registration request Reg-rq1 may directly carry an account registration category C1, and at this time, the user has selected an account category to be registered before sending the user account registration request Reg-rq1 to the cloud platform through the Client 1.

Optionally, the user account registration request Reg-rq1 may not carry the account registration category C1, but actively send an account registration category confirmation request Con-rq1 to the Client1 after the cloud platform receives the user account registration request Reg-rq1, so that the user selects an account category to be registered. Specifically, the step 220 of analyzing the user account registration request Reg-rq1 by the cloud platform, and confirming the account registration category C1 carried in the user account registration request Reg-rq1 may include the following steps:

the cloud platform analyzes a user account registration request Reg-rq1, and sends an account registration category confirmation request Con-rq1 to a Client1, wherein the account registration category confirmation request Con-rq1 carries a registration category confirmation page P2 to be input, the registration category confirmation page P2 to be input comprises M1 account registration category options, the M1 account registration category options only allow one account registration category option to be checked at the same time, and M1 is an integer greater than 1;

the cloud platform receives an account registration category confirmation response Con-res1 sent by the Client1 and used for responding to the account registration category confirmation request Con-rq1, the account registration category confirmation response Con-res1 carries an input registration category confirmation page P2, and an account registration category C1 option in the input registration category confirmation page P2 is selected by a user;

the cloud platform analyzes the account registration type confirmation response Con-res1 to obtain an account registration type C1.

Specifically, after receiving a user account registration request Reg-rq1 sent by a Client1, the cloud platform may send an account registration category confirmation request Con-rq1 to the Client1, where the account registration category confirmation request Con-rq1 carries a registration category confirmation page P2 to be input, and displays the registration category confirmation page P2 on a display interface of the Client1, so that the user selects an account category to be registered from the registration category confirmation page P2 to be input. At least two account registration category options may be included on the registration category confirmation page P2 to be input, and a user may select only one of the account registration categories at the same time for checking. As shown in fig. 3 by way of example, the registration category confirmation page P2 to be entered may include two account registration categories, one of which may be selected by the personal account and enterprise account users, respectively. When the user wants to register the personal account, the user can manually check the personal account, and after the user confirms that the personal account is submitted, the user feeds back the personal account to the cloud platform through the Client 1. The cloud platform analyzes the input registration type confirmation page P2 to acquire that the account type to be registered by the user is a personal account, that is, confirms that the personal account is the account registration type C1. It is to be understood that although only two account registration category options are shown in fig. 3, this is exemplary and not limiting, and one or more other options may be added, such as adding an organization account, or an enterprise account may be further subdivided into a private account, a national enterprise account, a business account, and so on. In addition, the account registration category may also be classified into other categories, such as temporary accounts and formal accounts, general accounts and advanced accounts, member accounts and non-member accounts, and the like, which are not limited herein.

230. The cloud platform searches an account type registry matched with the account registration type C1 in the local standard registry set, and determines K1 account information parameters required for account registration according to the account type registry.

240. The cloud platform sends an account information parameter acquisition request Get-rq1 to a Client1, where the account information parameter acquisition request Get-rq1 carries an account information parameter demand page P1 to be input, where the account information parameter demand page P1 to be input includes K1 information input areas, the K1 information input areas are used to input the K1 account information parameters required for user account registration, respectively, where K1 is an integer greater than 1.

In the embodiment of the application, different account category registration tables are stored in the cloud platform according to different account registration categories, and the account category registration tables corresponding to the different account registration categories may be different. When the account type which the user wants to register is a personal account, an account type registry matched with the personal account can be searched from a registry set pre-stored in the cloud platform, K1 account information parameters correspondingly required by the user can be obtained through the account type registry, and the account information parameters are fed back to the Client1 in the form of an account information parameter demand page P1 to be input for display, so that the user fills in the K1 account information parameters.

Specifically, the account information parameter demand page P1 to be input may be as shown in fig. 4 by way of example, where the account information parameter demand page P1 to be input includes K1 information input areas corresponding to K1 account information parameters to be input. The K1 information input areas may include, but are not limited to, account name (i.e. the user names his account), account password (i.e. the user sets up a password for his account), contact address, personal identification information collection entry, payment condition, payment entry, age, gender, country, city, area, etc. The contact way can be a mobile phone number or a mailbox number, and information receiving and password retrieving are facilitated. The user identity information can be acquired by clicking a button under the 'personal identity information acquisition inlet' to connect to a corresponding window, for example, a camera on the Client1 can be opened to acquire face information of a registered user, or the front and back of an identity card of the user can be scanned, or a fingerprint acquisition device on the Client1 can be started to acquire fingerprint information of the registered user, and the like, which is not limited herein. When the cloud platform is a pay use platform, the user can pay during registration, wherein the payment condition can be selected by the registered user, such as payment according to the monthly, quarterly, annually and the like, and then the user enters a corresponding payment inlet to pay according to the payment condition selected by the registered user.

It can be understood that, the account registration categories selected by the registered user are different, and the number and the content of the account information parameters required for registration may also be different. For example, when the account registration category C1 selected by the registered user is a business account, the K1 account information parameters included in the account information parameter requirement page P1 to be input may include, but are not limited to, an account name, an account password, a business name, a business code, a business type (e.g., private enterprise, national enterprise, etc.), a business registration address or business address, a business contact manner, a payment condition, a payment entrance, and the like.

250. The cloud platform receives an account information parameter acquisition response Get-res1 which is sent by the Client1 and used for responding to the account information parameter acquisition request Get-rq1, and the account information parameter acquisition response Get-res1 carries the input account information parameter demand page P1.

260. The cloud platform extracts the K1 account information parameters from the input account information parameter demand page P1, and determines the user level L1 according to the K1 account information parameters.

270. And the cloud platform associates the K1 account information parameters and then imports the account information parameters into a signed user database matched with the user level L1 for storage.

280. The cloud platform sends a user account registration response Reg-res1 for responding to the user account registration request Reg-rq1 to the Client1, and the user account registration response Reg-res1 carries a prompt that the account registration is successful.

In the embodiment of the application, when the registered user fills in the K1 account information parameters on the account information parameter demand page P1, the filled account information parameter demand page P1 is fed back to the cloud platform through the Client1, the cloud platform extracts the parameters filled by the user from the page P1, and the user level of the registered user is determined according to the parameters. The cloud platform can divide registered users into a plurality of levels to facilitate hierarchical management, for example, the user levels can be divided into individual users, enterprise users, temporary users, formal users, common users, advanced users, paid users, non-paid users and the like, and for example, the user levels can be divided into public members, gold members, platinum members, diamond members and the like, and the division can be performed according to other modes, which is not limited in the embodiment of the application.

The rights and interests of users in different levels can be different, and the higher the rights and interests are, the lower the rights and interests are. The priority of users in different levels may also be different, such as individual users having a lower priority than enterprise users, temporary users having a lower priority than regular users, general users having a lower priority than advanced users, and so on. Optionally, the user level may be determined by extracting payment conditions in the K1 account information parameters, where the more the payment is higher, the less the payment is lower, such as the popular member is lower in level than the golden member, the golden member is lower in level than the platinum member, the platinum member is lower in level than the diamond member, and so on.

After the user level is determined, the cloud platform may associate the K1 account information parameters into a whole, and store the whole in a subscriber database corresponding to the user level. For example, a public member belonging to a personal account is stored in the subscriber database 1, a gold member belonging to a personal account is stored in the subscriber database 2, a platinum member belonging to a personal account is stored in the subscriber database 3, a diamond member belonging to a personal account is stored in the subscriber database 4, and so on.

Optionally, the step 260 of extracting, by the cloud platform, the K1 account information parameters from the input account information parameter requirement page P1, and determining the user level L1 according to the K1 account information parameters may include the following steps:

the cloud platform extracts the K1 account information parameters from an input account information parameter demand page P1, and searches whether the K1 account information parameters are the same as at least one account information parameter of one of the signing users in a local all-signing-user database;

if at least one item of account information parameters of the K1 account information parameters is the same as that of one signed user, but the signed user is in a failure state, the cloud platform determines the user level L1 to which the cloud platform belongs according to the K1 account information parameters.

Specifically, after the account information parameter demand page P1 filled by the user is acquired and the above account information parameters are extracted, the account information parameters may be compared with account information parameters of all the subscribers in the cloud platform. If the user name, the contact address or the identity information established by the registered user is different from the user name, the contact address or the identity information established by the registered user before the registration, and the user name, the contact address or the identity information can be used for the registration operation. If at least one item of the account number information parameter is the same as that of a certain signed user, but the signed user is in a failure state, the account number information parameter can still be used for the registration operation. The subscriber may be in a failure state, which includes but is not limited to one of the following cases: the account of the subscriber has been logged off, the subscriber's fee has expired and not been renewed, the trial period of the subscriber (e.g., temporary user) has expired and not been paid, etc. Optionally, after the registration operation is completed, the cloud platform may delete all account information parameters of the failed subscriber.

Further, if at least one item of the K1 account information parameters is the same as that of one of the signed users, and the signed user is in an effective state, the cloud platform sends an account information parameter obtaining request Get-rq2 to the Client1, where the account information parameter obtaining request Get-rq2 carries an input account information parameter demand page P1, and the account information parameter which is the same as that of the signed user in the input account information parameter demand page P1 is marked to mark that the account information parameter exists, and the user needs to change the account information parameter.

For example, when the account name is the same as the account name of one of the subscribers in the valid state, the cloud platform returns the submitted account information parameter demand page P1 to the Client1, marks the account name to indicate that the account name is registered by another person, and requests to replace the account name for registration, so as to avoid confusion caused by the same account name. For another example, when the individual identity information is the same as the individual identity information of one of the subscribers in an effective state, the cloud platform returns the submitted account information parameter demand page P1 to the Client1, marks the individual identity information collection location to mark that the individual identity information is registered, and can replace the individual identity information for registration again or directly log in with the individual identity information, so that the situation that the same person performs repeated registration can be avoided. The signed user is in an effective state and can be a user who has not been logged off and normally pays the fee.

Optionally, as shown in fig. 5, after the account registration is successful, the user may perform resource value evaluation on the cloud platform, and the resource value evaluation method may include the following steps:

510. the cloud platform receives a resource value evaluation request Val-rq1 aiming at the resource R1 and sent by a Client 1;

520. the cloud platform determines the access right corresponding to the user level L1 according to the user level L1;

530. the cloud platform determines a value evaluation report of the resource R1 according to the access right;

540. and the cloud platform sends a resource value evaluation response Val-res1 for responding to the resource value evaluation request Val-rq1 to the Client1, wherein the resource value evaluation response Val-res1 carries the value evaluation report.

And when the user is successfully registered, resource value evaluation operation can be initiated on the cloud platform. Specifically, a user initiates a resource value evaluation request Val-rq1 for a resource R1 to the cloud platform through the Client1, where the resource value evaluation request Val-rq1 may carry a resource identifier and a resource type identifier, where the resource identifier may be used to indicate a specific resource, and the resource type identifier may be used to indicate a resource of which type the specific resource belongs to. Resource R1 may be a physical resource, such as an electronic device (e.g., a cell phone, a computer, a watch, etc.), a building (e.g., a house, a sculpture, etc.), land, table, chair, furniture, etc.; resource R1 may also be a non-physical resource such as a patent, trademark, application, etc. If the resource R1 is an electronic device, the resource identifier is a mobile phone, and the resource type identifier is an electronic device; if resource R1 is a patent, that resource is identified as a patent number and the resource type is identified as a patent. The cloud platform can determine the access authority corresponding to the user level according to the user level of the user, wherein the access authority corresponding to the users of different user levels can be different, and the higher the user level is, the larger the access authority is, and the lower the user level is, the smaller the access authority is. Further, after the access right of the user is obtained, a value evaluation report can be determined according to the access right, and the value evaluation report is fed back to the Client1, so that the user can conveniently review the value evaluation report. The value evaluation report obtained by the user with higher access right is more detailed, and the value evaluation report obtained by the user with lower access right is more brief, for example, the value evaluation report obtained by the paying user is more detailed than the value evaluation report obtained by the non-paying user.

Optionally, the step 530 specific implementation of the cloud platform determining the value evaluation report of the resource R1 according to the access right may include the following steps:

the cloud platform searches a value evaluation model matched with the resource type identifier under the access authority in a local standard model library according to the access authority;

under the condition that a value evaluation model V1 matched with the resource type identifier under the access right is searched from a local standard model library by the cloud platform, determining N1 dimensional parameters required by the value evaluation model V1 for value evaluation;

the cloud platform sends a dimensional parameter value acquisition request Get-rq3 to a Client1, wherein the dimensional parameter value acquisition request Get-rq3 carries a dimensional parameter requirement page P3 to be filled, the dimensional parameter requirement page P3 to be filled includes N1 value filling areas, the N1 value filling areas are used for respectively filling standardized values of the resource R1 in N1 dimensional parameters, and N1 is an integer greater than 1;

the cloud platform receives a dimensional parameter value acquisition response Get-res3 which is sent by a Client1 and used for responding to a dimensional parameter value acquisition request Get-rq3, wherein the dimensional parameter value acquisition response Get-res3 carries a filled dimensional parameter demand page P3, and N1 value filling areas of the filled dimensional parameter demand page P3 fill standardized values of the N1 dimensional parameters; the standardized values of the N1 dimensional parameters are obtained by carrying out standardized numerical processing on the original values of the N1 dimensional parameters filled in by the user through the Client 1;

the cloud platform extracts the standardized values of the resource R1 in the N1 dimensional parameters from the filled-in dimensional parameter demand page P3; and importing the standardized values of the N1 dimensional parameters into a value evaluation model V1 to obtain a value evaluation report of the resource R1 output by the value evaluation model V1.

Optionally, the method further includes:

under the condition that any value evaluation model matched with the resource type identifier is not searched in the local standard model library by the cloud platform, the cloud platform sends a model acquisition request to a shared standard model library, wherein the model acquisition request carries the resource type identifier;

if a model acquisition response which is sent by the shared standard model library and used for responding to the model acquisition request is received, and the model acquisition response carries a value evaluation model M2 which is searched from the shared standard model library and matched with the resource type identifier, K2 dimension parameters required by the value evaluation model M2 for value evaluation are determined;

the cloud platform sends a dimensional parameter value obtaining request get-rq2 to the Client1, where the dimensional parameter value obtaining request get-rq2 carries a dimensional parameter requirement page P2 to be filled, where the dimensional parameter requirement page P2 to be filled includes K2 value-taking filling areas, the K2 value-taking filling areas are used to respectively fill standardized values of the resource R1 represented by the resource identifier at the K2 dimensional parameters, and the K2 is an integer greater than 1;

the cloud platform receives a dimensional parameter value acquisition response get-res2 which is sent by the Client terminal 1 and used for responding to the dimensional parameter value acquisition request get-rq2, wherein the dimensional parameter value acquisition response get-res2 carries a filled dimensional parameter demand page P2, and K2 filling value areas of the filled dimensional parameter demand page P2 fill standardized values of the K2 dimensional parameters; the standardized values of the K2 dimensional parameters are obtained by carrying out standardized numerical processing on the original values of the K2 dimensional parameters filled in by the user through the Client 1;

the cloud platform extracts the standardized values of the resource R1 in the K2 dimensional parameters from the filled-in dimensional parameter demand page P2; importing the standardized values of the K2 dimensional parameters into the value evaluation model M2 to obtain a value evaluation report of the resource R1 output by the value evaluation model M2;

and the cloud platform sends a resource value evaluation response Res4 for responding to the resource value evaluation request to the Client1, wherein the resource value evaluation response carries the value evaluation report.

Optionally, before the cloud platform sends the model obtaining request to the shared standard model library, the method further includes: determining that the importance rating of the user account flagged in the subscription record CR1 is above a preset rating threshold T1.

In addition, before the cloud platform sends the model acquisition request to the shared standard model library, if it is determined that the importance level of the user account marked in the subscription record CR1 is not higher than the preset level threshold T1, the cloud platform sends friend assistance requests to Client1, the better assistance requests carry three friend accounts having friend relationship with the user account marked in the subscription record CR1, wherein the importance levels of the three friend accounts are higher than a preset level threshold T1, when receiving the friend assistance response sent by the Client1, the friend assistance response carries prestored assistance codes corresponding to at least 2 friend accounts in the three friend accounts, then it is determined that the Client1 obtains effective assistance from friends, the cloud platform performs the step of sending a model acquisition request to the shared standard model library.

In addition, before the resource value evaluation request is sent out, the Client1 may perform authentication on the user to improve security, for example, the Client1 may pop up a fingerprint collection prompt box to prompt the user to input a fingerprint image; the Client1 can acquire a fingerprint image of a user, compare the fingerprint image with a pre-stored fingerprint image template, send a resource value evaluation request to the cloud platform if the comparison is successful, pop up a fingerprint comparison failure if the comparison is failed, and request to re-input a prompt of the fingerprint image.

Optionally, the above specific implementation of the Client1 acquiring the fingerprint image may include: acquiring F1 normal bottom layer data values through F1 normal sensing electrodes of a fingerprint identification module, and acquiring F2 abnormal bottom layer data values through F2 abnormal sensing electrodes of the fingerprint identification module, wherein a sensing electrode array of the fingerprint module comprises the F1 normal sensing electrodes and the F2 abnormal sensing electrodes, and the F1 and the F2 are positive integers;

the Client1 determines F2 normal bottom layer data corresponding to the F2 abnormal sensing electrodes according to the F1 normal bottom layer data values; the Client1 generates the fingerprint image according to the F1 normal underlying data values and the F2 normal underlying data values.

In addition, in the above example process, the specific implementation manner of determining, by the Client1, the F2 normal bottom layer data corresponding to the F2 abnormal sensing electrodes according to the F1 normal bottom layer data values is as follows:

the Client1 determines the average of the F1 normal underlying data values; and the Client1 changes all the F2 abnormal bottom layer data values into the average value to obtain F2 normal bottom layer data corresponding to the F2 abnormal induction electrodes.

In addition, in the above example process, the specific implementation manner of determining, by the Client1, the F2 normal bottom layer data corresponding to the F2 abnormal sensing electrodes according to the F1 normal bottom layer data values is as follows: the Client1 acquires coordinate values of each abnormal induction electrode in F2 abnormal induction electrodes; the Client1 performs mean processing on each abnormal sensing electrode according to the coordinate value of each abnormal sensing electrode and the F1 bottom layer data values to obtain F2 normal bottom layer data corresponding to the F2 abnormal sensing electrodes;

the averaging process includes: determining x sensing electrodes of which the distance from the coordinate value of the abnormal sensing electrode processed by the current mean value is smaller than a preset distance in the F1 normal sensing electrodes, calculating the mean value of x bottom layer data values corresponding to the x sensing electrodes, and determining that the mean value is the reference bottom layer data value of the abnormal sensing electrode processed by the current mean value, wherein x is a positive integer.

The underlying data values may include capacitance values and/or voltage values, etc. The abnormal induction electrode is an induction electrode with abnormality in the fingerprint acquisition area. The induction electrode of fingerprint identification module can be detected by the little the control unit of fingerprint identification module.

It should be noted that, along with the increase of fingerprint identification module live time, the response electrode of fingerprint identification module has some response electrode to appear unusually, and the bottom data that these unusual response electrode obtained are unusual, can lead to Client1 to appear the noise point with the fingerprint image that the bottom data that normal response electrode and unusual response electrode obtained generated, and then influence the contrast of follow-up fingerprint contrast, therefore, before generating the fingerprint image, can revise these unusual bottom data earlier, with the noise point that reduces the fingerprint image, and then can improve the contrast of fingerprint contrast.

In addition, for a scene in which a fingerprint image is acquired by shooting, a specific implementation of the client ClieAt1 acquiring the fingerprint image may include: shooting through a camera module to obtain a fingerprint image, and acquiring an image area to be corrected in the fingerprint image, wherein the distortion degree parameter of the image area to be corrected is greater than or equal to a preset distortion degree parameter; acquiring a central pixel grid of the image according to a preset size; dividing the image area to be corrected into A pixel grids with the same size as the central pixel grid, wherein A is an integer larger than 2; and correcting the A pixel grids by taking the central pixel grid as a distortion correction reference to obtain a corrected fingerprint image.

Wherein correcting the A pixel meshes with the central pixel mesh as a distortion correction reference comprises: acquiring the transverse distance and the longitudinal distance from the A pixel grids to the central pixel grid; according to the transverse distance and the longitudinal distance from the A pixel grids to the central pixel grid, converting transverse distortion degree parameters and longitudinal distortion degrees corresponding to the A pixel grids; and carrying out distortion correction on the A pixel grids according to the distortion degree parameters corresponding to the A pixel grids.

For example, the acquiring an image region to be corrected in the image comprises: analyzing the fingerprint image to obtain an image area with a distortion degree parameter greater than or equal to a preset distortion degree parameter; displaying the image area with the distortion degree parameter larger than or equal to the preset distortion degree parameter on a display interface of the mobile terminal, and prompting a user to select the image area to be corrected; if a selection instruction input by a user is received, acquiring an image area to be corrected corresponding to the selection instruction to obtain the image area to be corrected.

By way of further example, the acquiring an image region to be corrected in the image comprises: analyzing the image to obtain all image areas of which the distortion degree parameters are greater than or equal to preset distortion degree parameters in the image, wherein all the image areas are image areas to be corrected.

For example, the dividing the image area to be corrected into a pixel grids of the same size as the central pixel grid comprises: and gridding the image area to be corrected according to a preset size to obtain A pixel grids with the same size as the central pixel grid.

In addition, before comparing the fingerprint image with the pre-stored fingerprint image template, the method can also comprise the step of carrying out image precision enhancement processing on the fingerprint image. Comparing the fingerprint image with a pre-stored fingerprint image template comprises: and comparing the fingerprint image subjected to the image precision enhancement processing with a pre-stored fingerprint image template.

The image precision enhancement processing on the acquired fingerprint image may include: acquiring a target image area to be enhanced in a fingerprint image, wherein the target image area comprises a plurality of sub-area images; performing image quality evaluation on each subarea image in the plurality of subarea images to obtain a plurality of image quality evaluation values; selecting at least one target image quality evaluation value smaller than a preset image quality evaluation threshold value from the plurality of image quality evaluation values; acquiring at least one target sub-area image corresponding to the at least one target image quality evaluation value; and performing image precision enhancement processing on the at least one target subregion image to obtain the enhanced target image region. The image quality evaluation index may include, but is not limited to: mean gray, mean square error, entropy, edge preservation, and the like. It is considered that the larger the obtained image quality evaluation value is, the better the image quality is. Alternatively, in the case where the requirement on the accuracy of the image quality evaluation is not high, the evaluation may be performed by using one image quality evaluation index, for example, the image quality evaluation value may be performed on the image to be processed by using entropy, and it may be considered that the larger the entropy, the better the image quality is, and conversely, the smaller the entropy, the worse the image quality is.

Wherein, the image precision enhancement processing is carried out on the at least one target subregion image, and comprises the following steps: dividing a target subregion image i into a plurality of region blocks, wherein the target subregion image i is any one target subregion image in the at least one target subregion image; respectively extracting the features of each of the plurality of region blocks to obtain a plurality of feature point sets, wherein each region block corresponds to one feature point set; determining the feature point distribution density corresponding to each of the plurality of region blocks according to the plurality of feature point sets to obtain a plurality of feature point distribution densities; determining a target image enhancement control coefficient corresponding to each feature point distribution density in the plurality of feature point distribution densities according to a preset mapping relation between the feature point distribution densities and the image enhancement control coefficients to obtain a plurality of target image enhancement control coefficients; respectively carrying out image enhancement processing on each of the plurality of area blocks according to the plurality of target image enhancement control coefficients to obtain an enhanced target subregion image i; and smoothing the target subregion image i to obtain a final target subregion image i.

Each type of image enhancement algorithm can correspond to an image enhancement control coefficient, and the size of the image enhancement control coefficient controls the image enhancement effect. The embodiment of the application can carry out pertinence enhancement according to the characteristics of each region block, so that the details of each region are clearer, in addition, in order to ensure the transition between different regions to be natural, the smooth processing is adopted, the enhancement effect is achieved, the difference enhancement feeling between each region is optimized, and the fingerprint image quality is better.

For example, when the resource R1 is a patent, the N1 value filling areas in the dimension parameter requirement page P3 to be filled may include, but are not limited to, an application date, a patent name, a key field, a patent category, a patent status, a payment status, a technical field, and the like of the patent. The key field may input key technical points of the patent, some keywords with strong correlation, or may input abstract or beneficial effect, etc., which is not limited herein. The patent category may be one of invention, reality, or appearance. The patent status may include one of underwriting, authorized or failed, and may be further subdivided, such as in preliminary examination, in actual examination, authorized, withdrawn, rejected, etc., without limitation. When the value of an authorized patent is evaluated, the remaining effective period of the patent can be calculated through the patent application date and the patent category input by a user, the technical field, the technical means and the technical novelty degree of the patent can be roughly known according to the patent name and the key field, and then the value of the patent is evaluated according to a value evaluation model. For example, a patent with a high degree of novelty in general technology has a higher value than a patent with a low degree of novelty, and a patent with a long remaining life is higher than a patent with a short remaining life.

As another example, when the resource R1 is an electronic device, the N1 value filling areas in the dimension parameter requirement page P3 to be filled may include, but are not limited to, a device model, a processor (CPU), a computing rate of the device, a purchase date or production date of the device, a price when the device is purchased, an age of the device, a memory size, and the like. The method comprises the steps of carrying out value evaluation on a computer, calculating the remaining service life of the computer according to the purchase date (or production date) input by a user, the current time and the service life of equipment, calculating the operating efficiency of the computer according to the model number, CPU and calculation rate of the computer input by the user to roughly estimate the loss degree of the computer, using the purchase price of the computer as a reference value, and then estimating the value of the computer according to a value evaluation model. For example, a computer with a long remaining lifetime is more valuable than a computer with a short remaining lifetime, a computer with a high operating efficiency and a low loss is more valuable than a computer with a low operating efficiency and a low loss, and so on.

As another example, when the resource R1 is a building, the N1 value filling areas in the dimension parameter requirement page P3 to be filled may include, but are not limited to, a house attribute, an area size, a seating position, a purchase date or a land use right acquisition date, a purchase unit price or total price, a service life, a cell to which the resource belongs, a cell greening area, traffic near the cell, and the like. The property of the house may include commercial, civil or industrial use, and may be further subdivided, such as self-building, commercial, apartment, talent accommodation, and the like, without limitation. The seating location may include urban or suburban areas, or may be further subdivided, such as civic rings, bi-rings, tri-rings, and the like, without limitation. The method comprises the steps of carrying out value evaluation on a house, calculating the remaining service life of the house according to the purchase date or the land use right acquisition date, the current time and the service life input by a user, calculating the overall value of the house according to the house attribute, the area size, the sitting position and the purchase unit price or total price input by the user, and then combining a value evaluation model to estimate the current value of the house. For example, houses with long remaining life span have higher value than houses with short remaining life span, houses with large areas and good locations have higher value than houses with small areas and poor locations, and so on.

It can be seen that in the embodiment of the application, when a user wants to perform resource value evaluation on a cloud platform, account registration may be performed on the cloud platform first, specifically, the cloud platform may receive a user account registration request Reg-rq1 from a Client1, and analyze the user account registration request Reg-rq1 to obtain an account registration category C1 carried by the user account registration request Reg-rq 1; searching an account category registry matched with the account registration category C1 in the local standard registry set, and determining K1 account information parameters required for account registration according to the account category registry; sending an account information parameter acquisition request Get-rq1 to a Client1 to request a user to input the K1 account information parameters; the cloud platform receives an account information parameter acquisition response Get-res1 which is sent by a Client1 and used for responding to an account information parameter acquisition request Get-rq1, wherein the account information parameter acquisition response Get-res1 carries the input K1 account information parameters; the user level L1 can be determined according to the K1 account information parameters; the K1 account information parameters are correlated and then imported into a signed user database matched with the user level L1 for storage; the cloud platform sends a user account registration response Reg-res1 for responding to the user account registration request Reg-rq1 to the Client1, wherein the prompt that the account registration is successful is carried. By implementing the embodiment of the application, the users to be registered can be classified and registered according to the grades, so that the hierarchical management of the users on the platform is facilitated.

Referring to fig. 6, an embodiment of the present application provides a cloud platform 600, which at least may include: a processor 620 and a memory 610 coupled to each other; for example, the processor 620 and the memory 610 may be coupled by a bus 630.

The Memory 610 may include, but is not limited to, a Random Access Memory (RAM), an Erasable Programmable Read Only Memory (EPROM), a Read-Only Memory (ROM), or a portable Read-Only Memory (CD-ROM), and the like, and the Memory 610 is used for storing relevant instructions and data.

The processor 620 may be one or more Central Processing Units (CPUs), and in the case that the processor 620 is one CPU, the CPU may be a single-core CPU or a multi-core CPU.

The processor 620 is configured to read the program codes stored in the memory 610 and execute some or all of the steps of the method executed by the cloud platform 600 in the above-described embodiment of the present application.

Specifically, the processor 620 is configured to receive a user account registration request Reg-rq1 from the Client 1;

searching an account category registry matched with the account registration category C1 in a local standard registry set stored in the memory 610, and determining K1 account information parameters required for account registration according to the account category registry;

sending an account information parameter acquisition request Get-rq1 to a Client1, where the account information parameter acquisition request Get-rq1 carries an account information parameter demand page P1 to be input, where the account information parameter demand page P1 to be input includes K1 information input regions, the K1 information input regions are used to input the K1 account information parameters required for user account registration, where K1 is an integer greater than 1;

receiving an account information parameter acquisition response Get-res1 sent by a Client1 and used for responding to the account information parameter acquisition request Get-rq1, wherein the account information parameter acquisition response Get-res1 carries an input account information parameter demand page P1;

extracting the K1 account information parameters from an input account information parameter demand page P1, and determining the user level L1 according to the K1 account information parameters;

and sending a user account registration response Reg-res1 for responding to the user account registration request Reg-rq1 to the Client1, wherein the user account registration response Reg-res1 carries a prompt that the account registration is successful.

Optionally, the manner in which the processor 620 analyzes the user account registration request Reg-rq1 and confirms the account registration category C1 carried in the user account registration request Reg-rq1 may specifically be:

the processor 620 analyzes the user account registration request Reg-rq1, and sends an account registration category confirmation request Con-rq1 to the Client1, where the account registration category confirmation request Con-rq1 carries a registration category confirmation page P2 to be input, where the registration category confirmation page P2 to be input includes M1 account registration category options, where the M1 account registration category options only allow one account registration category option to be checked at the same time, and M1 is an integer greater than 1;

receiving an account registration category confirmation response Con-res1 sent by the Client1 and used for responding to the account registration category confirmation request Con-rq1, wherein the account registration category confirmation response Con-res1 carries an input registration category confirmation page P2, and an account registration category C1 option in the input registration category confirmation page P2 is selected by a user;

the account registration type confirmation response Con-res1 is parsed to obtain an account registration type C1.

Optionally, the manner in which the processor 620 extracts the K1 account information parameters from the input account information parameter demand page P1, and determines the user level L1 according to the K1 account information parameters may specifically be:

the processor 620 extracts the K1 account information parameters from the input account information parameter demand page P1, and searches all local subscriber databases to see whether the K1 account information parameters are the same as at least one of the account information parameters of one subscriber;

if the K1 account information parameters are different from the account information parameters of all the signed users, determining the user level L1 to which the user belongs according to the K1 account information parameters;

and if at least one item of account information parameters of the K1 account information parameters is the same as that of one signed user, and the signed user is in a failure state, determining the user level L1 to which the signed user belongs according to the K1 account information parameters.

Optionally, the processor 620 may be further configured to, if at least one item of the K1 account information parameters is the same as one of the account information parameters of one of the contracting users, and the contracting user is in an active state, send an account information parameter obtaining request Get-rq2 to the Client1, where the account information parameter obtaining request Get-rq2 carries an input account information parameter requirement page P1, and the account information parameter that is the same as the contracting user in the input account information parameter requirement page P1 is provided with a flag to flag that the account information parameter exists, and the user needs to change the account information parameter.

Optionally, the processor 620 may be further configured to receive a resource value evaluation request Val-rq1 for the resource R1 sent by the Client 1;

determining a value evaluation report of the resource R1 according to the access right;

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., coaxial cable, fiber optic, digital subscriber line) or wirelessly (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., compact disk), or a semiconductor medium (e.g., solid state disk), among others.

It should be noted that, for simplicity of description, the above-mentioned embodiments of the method are described as a series of acts or combinations, but those skilled in the art should understand that the present application is not limited by the order of acts described, as some steps may be performed in other orders or simultaneously according to the present application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

The steps in the method of the embodiment of the application can be sequentially adjusted, combined and deleted according to actual needs.

The composition structure in the cloud platform can be merged, divided and deleted according to actual needs.

The cloud platform-based resource value assessment user management method and the related products disclosed in the embodiment of the application are introduced in detail, a specific example is applied in the method to explain the principle and the implementation mode of the application, and the description of the embodiment is only used for helping to understand the method and the core idea of the application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims

1. A resource value evaluation user management method based on a cloud platform is characterized by comprising the following steps:

2. The method of claim 1, wherein the cloud platform parses the user account registration request Reg-rq1, validates the account registration category C1 carried in the user account registration request Reg-rq1, and comprises:

3. The method as claimed in claim 1, wherein the cloud platform extracts the K1 account information parameters from the inputted account information parameters requirement page P1, and determines the user level L1 according to the K1 account information parameters, including:

4. The method of claim 3, further comprising:

5. The method according to any one of claims 1-4, further comprising:

6. A cloud platform, comprising:

a processor and a memory coupled to each other;

7. The cloud platform of claim 6, wherein the processor parses the user account registration request Reg-rq1 to confirm that the account registration category C1 carried in the user account registration request Reg-rq1 is specifically:

8. The cloud platform of claim 6, wherein the processor extracts the K1 account information parameters from the entered account information parameters requirements page P1, and determines the user level L1 according to the K1 account information parameters by:

9. The cloud platform of claim 8, wherein the processor is further configured to, if at least one of the K1 account information parameters is the same as one of the account information parameters of a subscriber and the subscriber is in an active state, send an account information parameter obtaining request Get-rq2 to the Client1, where the account information parameter obtaining request Get-rq2 carries the input account information parameter demand page P1, and the account information parameter in the input account information parameter demand page P1 that is the same as the subscriber is provided with a flag to flag that the account information parameter already exists and that the subscriber needs to change the account information parameter.

10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a computer device, implements the method of any one of claims 1 to 5.