A design method and system for enterprise cloud platform accounts

Abstract

This application provides a design method and system for an enterprise cloud platform account, including: creating an enterprise master account in response to an enterprise's cloud platform account registration request; creating several enterprise sub-accounts corresponding to the enterprise master account based on the enterprise's demand for service functions; generating a sub-account account name and sub-account ID for the enterprise sub-account, and verifying the sub-account ID; granting at least one sub-account permission to the enterprise sub-account; matching the enterprise master account with all enterprise sub-accounts, obtaining an enterprise cloud platform account system and sending it to the enterprise. This application avoids the problem of authority conflicts and information leakage between different departments of the enterprise, and improves the user experience.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a design method and system for an enterprise cloud platform account. Background Art

[0002] With the development of science and technology, the Internet has been integrated into people's lives and work. As a new resource utilization model with unified management, flexible scheduling and convenient configuration, the cloud platform has been widely used in all walks of life for its high efficiency, rapidity and economy.

[0003] With the development and popularization of cloud platform technology, enterprises also use cloud platforms as their management centers. Storing various data on cloud platforms can solve the problem of poor information interactivity of traditional PCs as carriers for employees' office work, which is beneficial to internal information management of enterprises. At the same time, cloud platforms can also be used to achieve various service functions such as data collection and online services. Enterprises only need to purchase an account on the cloud platform to perform enterprise management and various service functions through the cloud platform.

[0004] However, for large enterprises, due to the complex hierarchy of departments, different departments face the risk of account information leakage when using cloud platform services. At the same time, for business departments and technical departments, due to their different company permissions, permission conflicts will occur when using the same account. Therefore, the existing enterprise cloud platform account system provides a poor user experience. Summary of the invention

[0005] The present application provides a design method and system for an enterprise cloud platform account to solve the above-mentioned problems existing in the prior art.

[0006] In order to solve the above technical problems, the embodiments of the present application disclose the following technical solutions:

[0007] In a first aspect, the present application provides a method for designing an enterprise cloud platform account, the method comprising:

[0008] In response to the enterprise's cloud platform account registration request, create an enterprise master account, which is used for enterprise financial management and enterprise sub-account management;

[0009] Based on the enterprise's demand for service functions, a number of enterprise sub-accounts corresponding to the enterprise master account are created, and the enterprise sub-accounts are used to use the service functions;

[0010] Generate a sub-account name and a sub-account ID for the enterprise sub-account, and verify the sub-account ID;

[0011] Granting at least one sub-account permission to the enterprise sub-account, wherein the sub-account permission includes: cloud platform console permission and programming permission;

[0012] The enterprise master account and all enterprise sub-accounts are matched to obtain the enterprise cloud platform account system, and sent to the enterprise.

[0013] Optionally, the step of creating an enterprise master account in response to the enterprise's cloud platform account registration request includes:

[0014] Based on the cloud platform account registration request, obtain enterprise information, including: enterprise needs, enterprise name, and a primary account name set by the enterprise;

[0015] Create a business master account ID associated with the enterprise;

[0016] An enterprise master account is established based on the enterprise information and the enterprise master account ID.

[0017] Optionally, establishing an enterprise master account based on the enterprise information and the enterprise master account ID includes:

[0018] Set the number of enterprise master accounts based on the enterprise needs;

[0019] A corresponding number of enterprise master accounts are established based on the master account name set by the enterprise and the enterprise master account ID, and all the enterprise master accounts are bound to the enterprise name.

[0020] Optionally, generating a sub-account ID for the enterprise sub-account includes:

[0021] Set the number of digits of the sub-account ID, which is 8 digits;

[0022] Set each digit of the sub-account ID based on the preset ID setting rules;

[0023] The preset ID setting rules include:

[0024] The first digit is the area code; the second and third digits are random numbers; the fourth digit is the check code; the fifth to eighth digits are random numbers.

[0025] Optionally, verifying the sub-account ID includes: verifying a verification code of the sub-account ID, and the verification method includes:

[0026] Obtain all the numbers in the sub-account ID except the verification code, and arrange them in order to obtain the verification code;

[0027] Process the check digit based on the sha256 algorithm and take the first and last digits of the processing result;

[0028] Convert the first digit and the last digit into decimal numbers, add the two decimal numbers to obtain a sum, divide the sum by 10 and obtain the remainder, and use the remainder as a check digit;

[0029] Determine whether the check digit and the check code are consistent.

[0030] Optionally, when the number of enterprise sub-accounts exceeds the maximum range of the sub-account ID, the enterprise sub-accounts are upgraded;

[0031] The lifting process includes:

[0032] The number of digits of the sub-account ID is expanded from 8 to 12; wherein: the first digit is the area code and is the same as the original area code; the second and third digits are random numbers and are the same as the original second and third digits; the fourth digit is the check code; the fifth to eighth digits are random numbers; the ninth to twelfth digits are random numbers and are the same as the original fifth to eighth digits.

[0033] Optionally, if the enterprise sub-account has cloud platform console permissions, the cloud platform sub-account can log in to the front-end web page of the cloud platform;

[0034] If the enterprise sub-account has programming permissions, the cloud platform sub-account has a Secret ID, and the Secret ID is used for background programming of the cloud platform.

[0035] Optionally, also include:

[0036] All enterprise sub-accounts are isolated from each other to ensure that the data between each enterprise sub-account is not interoperable.

[0037] In a second aspect, the present application provides a system for designing an enterprise cloud platform account, the system comprising:

[0038] A master account creation module, configured to create an enterprise master account in response to an enterprise's cloud platform account registration request, wherein the enterprise master account is used for enterprise financial management and enterprise sub-account management;

[0039] A sub-account creation module, configured to create a number of enterprise sub-accounts corresponding to the enterprise master account based on the enterprise's demand for service functions, and the enterprise sub-accounts are used to use the service functions;

[0040] A sub-account name and ID module is configured to generate a sub-account name and a sub-account ID for the enterprise sub-account, and verify the sub-account ID;

[0041] A sub-account permission module, configured to grant at least one sub-account permission to the enterprise sub-account, wherein the sub-account permission includes: cloud platform console permission and programming permission;

[0042] The account system module is configured to match the enterprise master account with all enterprise sub-accounts, obtain the enterprise cloud platform account system, and send it to the enterprise.

[0043] Optionally, generating a sub-account ID for the enterprise sub-account includes:

[0044] Set the number of digits of the sub-account ID, which is 8 digits;

[0045] Set each digit of the sub-account ID based on the preset ID setting rules;

[0046] The preset ID setting rules include:

[0047] The first digit is the area code; the second and third digits are random numbers; the fourth digit is the check code; the fifth to eighth digits are random numbers.

[0048] Compared with the prior art, the beneficial effects of this application are:

[0049] The present application provides a design method and system for an enterprise cloud platform account, including: creating an enterprise master account in response to an enterprise's cloud platform account registration request, the enterprise master account is used for enterprise financial management and enterprise sub-account management; creating several enterprise sub-accounts corresponding to the enterprise master account based on the enterprise's demand for service functions, and the enterprise sub-accounts are used to use service functions; generating a sub-account account name and sub-account ID for the enterprise sub-account, and verifying the sub-account ID; granting at least one sub-account permission to the enterprise sub-account, and the sub-account permissions include: cloud platform console permissions and programming permissions; matching the enterprise master account with all enterprise sub-accounts to obtain an enterprise cloud platform account system, and sending it to the enterprise. The present application takes into account the different permission requirements between different departments of the enterprise, and creates multiple sub-accounts so that each sub-account can correspond to one or more departments, so that each department can use the corresponding sub-account, avoiding the problem of permission conflicts and information leakage, and improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] In order to more clearly illustrate the technical solution of the present application, the drawings required for use in the embodiments are briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0051] Figure 1 An overall flow chart of the method for designing an enterprise cloud platform account provided in an embodiment of the present application. DETAILED DESCRIPTION

[0052] In order to enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.

[0053] See also Figure 1 , is an overall flow chart of the design method of the enterprise cloud platform account provided in the embodiment of the present application. Figure 1 As shown, the method comprises the following steps:

[0054] S1. In response to the enterprise's cloud platform account registration request, create an enterprise master account, which is used for enterprise financial management and enterprise sub-account management;

[0055] S2. Create several enterprise sub-accounts corresponding to the enterprise master account based on the enterprise's demand for service functions. The enterprise sub-accounts are used to use the service functions.

[0056] S3. Generate a sub-account name and sub-account ID for the enterprise sub-account, and verify the sub-account ID

[0057] S4. Grant at least one sub-account permission to the enterprise sub-account, wherein the sub-account permission includes: cloud platform console permission and programming permission

[0058] S5. Match the enterprise master account with all enterprise sub-accounts to obtain the enterprise cloud platform account system, and send it to the enterprise.

[0059] The following is a detailed description of each step:

[0060] In step S1, in response to the enterprise's cloud platform account registration request, an enterprise master account is created.

[0061] Specifically, the cloud platform master account is the default account after registration, which can be understood as a parent account or a super-managed account. The cloud platform sub-account belongs to the cloud platform master account, and there is a one-to-many relationship between the master account and the sub-account. The sub-account cannot exist independently, and one master account can correspond to one or more sub-accounts.

[0062] The business master account can manage the business finances, the business operations, and each business sub-account.

[0063] In some embodiments, the method for creating an enterprise master account specifically includes:

[0064] S11. Obtain enterprise information based on the cloud platform account registration request, including: enterprise requirements, enterprise name, and the name of the primary account set by the enterprise.

[0065] S12. Create an enterprise master account ID associated with the enterprise.

[0066] S13, establishing an enterprise master account based on the enterprise information and the enterprise master account ID. Specifically including:

[0067] The number of enterprise master accounts is set based on the enterprise's needs. Specifically, customers can decide whether to use the same cloud platform master account between subsidiaries or different departments based on the company's own characteristics and needs. For example, a cross-border financial institution has credit business in multiple countries and regions and needs to use the corporate credit report service in the cloud platform, but the service content, service frequency, and service cycle used in different countries are different. At this time, a master account can be set up in each branch in each country to independently manage the sub-accounts in the region.

[0068] A corresponding number of enterprise master accounts are established based on the master account name set by the enterprise and the enterprise master account ID, and all the enterprise master accounts are bound to the enterprise name.

[0069] Specifically, the business owner account ID is unique and associated with the business. When logging in to the business owner account, it can be set to enter the company name, main account name, business owner account ID and password at the same time. Only when all are entered correctly can the login be allowed to ensure the security of the account.

[0070] In step S2, a number of enterprise sub-accounts corresponding to the enterprise master account are created based on the enterprise's demand for service functions.

[0071] Specifically, each main account will correspond to multiple enterprise sub-accounts. According to the different needs of different departments for service functions, each department can be set to have a sub-account, or it can be set that multiple highly related departments share one account. It can also be set that each group or each employee in the department has a sub-account according to the various positions in the department. The specific sub-account settings can be set by the enterprise itself, and the embodiments of this application are not limited.

[0072] Enterprise sub-accounts only support the use of services and do not have the right to perform operations such as financial management and account management.

[0073] Taking the corporate credit report service as an example, you can set up a development sub-account and an operation sub-account. The development sub-account has programming permissions and can recompile the report returned by the service. The operation sub-account can log in to the cloud platform to perform business activities such as report query and report download.

[0074] In step S3, a sub-account name and a sub-account ID are generated for the enterprise sub-account, and the sub-account ID is verified.

[0075] Specifically, the sub-account name can be named by the holder of each sub-account, and there is no limitation here. Each sub-account ID is unique and corresponds to a sub-account one by one.

[0076] The methods for generating a sub-account ID include:

[0077] Set the number of digits of the sub-account ID, which is 8 digits;

[0078] Each digit of the sub-account ID is set based on the preset ID setting rules.

[0079] The preset ID setting rules include:

[0080] The first digit is the area code, which indicates the internal area of ​​the enterprise and is set by the enterprise. The second and third digits are random numbers, which can be generated from 00 to 99. The fourth digit is the check code. The fifth to eighth digits are random numbers, which can be generated from 0000 to 9999. That is: area code (1 digit) + random number (2 digits) + check code (1 digit) + random number (4 digits).

[0081] For example: 15457538.

[0082] Verifying the sub-account ID specifically includes: verifying a verification code of the sub-account ID.

[0083] Verification methods include:

[0084] Get all the numbers in the sub-account ID except the verification code, and arrange them in order to obtain the verification digit. Specifically, taking the sub-account 15457538 as an example, the verification digit is (1547538).

[0085] The check digit is processed based on the sha256 algorithm, and the first and last digits of the processing result are taken. Specifically, SHA256 (1547538) =

[0086] a9da61ceeea2f2714263cb2baf 9985b856f7c9ce77a025c5815de59aa4aa609f

[0087] The first digit and the last digit are converted into decimal numbers, and the two decimal numbers are added to obtain a sum, and the sum is divided by 10 to obtain a remainder, which is used as a check digit.

[0088] Specifically, the first digit and the last digit are a and f respectively, which are converted to decimal system as 10 and 15. The sum 10+15=25, modulo 10, 25mod10=5. Therefore, the check digit is 5.

[0089] Determine whether the check digit and the check code are consistent. If they are consistent, the check code is correct.

[0090] It should be noted that the generation method and verification method of the verification code are the same. When a sub-account is obtained, it is only necessary to verify the verification code to determine whether the sub-account is correct.

[0091] In some embodiments, when the number of enterprise sub-accounts exceeds the maximum range of the sub-account IDs, the enterprise sub-accounts are upgraded.

[0092] The promotion process specifically includes:

[0093] The number of digits of the sub-account ID is extended from 8 to 12; among which: the first digit is the area code and is the same as the original area code; the second and third digits are random numbers and are the same as the original second and third digits; the fourth digit is the check code; the fifth to eighth digits are random numbers; the ninth to twelfth digits are random numbers and are the same as the original fifth to eighth digits. That is: area code (old, 1 digit) + random number (old, 2 digits) + check code (new, 1 digit) + random number (new, 4 digits) + random number (old, 4 digits).

[0094] When logging in to an enterprise sub-account, you can set it to enter the sub-account name, sub-account ID and password at the same time. Login is allowed only when all are entered correctly to ensure account security.

[0095] In step S4, at least one sub-account permission is granted to the enterprise sub-account. Specifically, the sub-account permission includes: cloud platform console permission and programming permission.

[0096] If the enterprise sub-account has cloud platform console permissions, the cloud platform sub-account can log in to the front-end web page of the cloud platform.

[0097] If the enterprise sub-account has programming permissions, the cloud platform sub-account has a Secret ID, and the Secret ID is used for background programming of the cloud platform.

[0098] Enterprises can set their own sub-accounts to have cloud platform console permissions or programming permissions or both permissions, and there is no limitation here.

[0099] In step S5, the enterprise master account and all enterprise sub-accounts are matched to obtain the enterprise cloud platform account system, and sent to the enterprise.

[0100] In some embodiments, it also includes:

[0101] All enterprise sub-accounts are isolated from each other to ensure that the data between each enterprise sub-account is not interoperable.

[0102] The cloud platform master account can view the operation records and data of all accounts, and the cloud platform sub-account can only view the operation records and data of this account.

[0103] The present application embodiment also provides a system for designing an enterprise cloud platform account, including:

[0104] A master account creation module, configured to create an enterprise master account in response to an enterprise's cloud platform account registration request, wherein the enterprise master account is used for enterprise financial management and enterprise sub-account management;

[0105] A sub-account creation module, configured to create a number of enterprise sub-accounts corresponding to the enterprise master account based on the enterprise's demand for service functions, and the enterprise sub-accounts are used to use the service functions;

[0106] A sub-account name and ID module is configured to generate a sub-account name and a sub-account ID for the enterprise sub-account, and verify the sub-account ID;

[0107] A sub-account permission module, configured to grant at least one sub-account permission to the enterprise sub-account, wherein the sub-account permission includes: cloud platform console permission and programming permission;

[0108] The account system module is configured to match the enterprise master account with all enterprise sub-accounts, obtain the enterprise cloud platform account system, and send it to the enterprise.

[0109] Since the above embodiments are all described by citing and combining with other embodiments, different embodiments have the same parts, and the same and similar parts between the embodiments in this specification can be referred to each other. No further detailed description is given here.

[0110] In summary, compared with the prior art, the present invention has the following beneficial effects:

[0111] The embodiment of the present application provides a design method and system for an enterprise cloud platform account, including: creating an enterprise master account in response to an enterprise's cloud platform account registration request, the enterprise master account is used for enterprise financial management and enterprise sub-account management; creating several enterprise sub-accounts corresponding to the enterprise master account based on the enterprise's demand for service functions, and the enterprise sub-accounts are used to use service functions; generating a sub-account account name and sub-account ID for the enterprise sub-account, and verifying the sub-account ID; granting at least one sub-account permission to the enterprise sub-account, and the sub-account permissions include: cloud platform console permissions and programming permissions; matching the enterprise master account with all enterprise sub-accounts to obtain an enterprise cloud platform account system, and sending it to the enterprise. This application takes into account the different permission requirements between different departments of the enterprise, and creates multiple sub-accounts so that each sub-account can correspond to one or more departments, so that each department can use the corresponding sub-account, avoiding the problem of permission conflicts and information leakage, and improving the user experience.

[0112] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

[0113] Those skilled in the art can clearly understand that the technology in the embodiments of the present application can be implemented by means of software plus a necessary general hardware platform. Based on this understanding, the technical solution in the embodiments of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which can be stored in a storage medium such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application or some parts of the embodiments.

[0114] It should be noted that, in this specification, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a circuit structure, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such circuit structure, article or device. In the absence of further restrictions, the existence of an element defined by the sentence "includes a..." does not exclude the existence of other identical elements in the circuit structure, article or device including the element.

[0115] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the disclosure of the invention herein. The present application is intended to cover any modification, use or adaptation of the present invention, which follows the general principles of the present application and includes common knowledge or customary technical means in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the content of the claims. The above-described embodiments of the present application do not constitute a limitation on the scope of protection of the present application.

Claims

1. A method for designing an enterprise cloud platform account, characterized in that: The method comprises: In response to the enterprise's cloud platform account registration request, create an enterprise master account, which is used for enterprise financial management and enterprise sub-account management; Based on the enterprise's demand for service functions, a number of enterprise sub-accounts corresponding to the enterprise master account are created, and the enterprise sub-accounts are used to use the service functions; Generate a sub-account name and a sub-account ID for the enterprise sub-account, and verify the sub-account ID; Granting at least one sub-account permission to the enterprise sub-account, the sub-account permission including: cloud platform console permission and programming permission. If the enterprise sub-account has cloud platform console permission, the cloud platform sub-account can log in to the front-end web page of the cloud platform; If the enterprise sub-account has programming permissions, the cloud platform sub-account has a Secret ID, which is used for backend programming of the cloud platform; Match the enterprise master account with all enterprise sub-accounts to obtain the enterprise cloud platform account system, and send it to the enterprise; All enterprise sub-accounts are isolated from each other to ensure that the data between each enterprise sub-account is not interoperable; The step of generating a sub-account ID for the enterprise sub-account includes: Set the number of digits of the sub-account ID, which is 8 digits; Set each digit of the sub-account ID based on the preset ID setting rules; The preset ID setting rules include: The first digit is the area code; the second and third digits are random numbers; the fourth digit is the check code; the fifth to eighth digits are random numbers; Verifying the sub-account ID includes: verifying the verification code of the sub-account ID, and the verification method includes: Obtain all the numbers in the sub-account ID except the verification code, and arrange them in order to obtain the verification code; Process the check digit based on the sha256 algorithm and take the first and last digits of the processing result; Convert the first digit and the last digit into decimal numbers, add the two decimal numbers to obtain a sum, divide the sum by 10 and obtain the remainder, and use the remainder as a check digit; Determining whether the check digit and the check code are consistent; When the number of enterprise sub-accounts exceeds the maximum range of the sub-account ID, the enterprise sub-accounts are upgraded; The lifting process includes: The number of digits of the sub-account ID is expanded from 8 to 12; wherein: the first digit is the area code and is the same as the original area code; the second and third digits are random numbers and are the same as the original second and third digits; the fourth digit is the check code; the fifth to eighth digits are random numbers; the ninth to twelfth digits are random numbers and are the same as the original fifth to eighth digits.

2. The method for designing an enterprise cloud platform account according to claim 1, characterized in that: The step of creating an enterprise master account in response to the enterprise's cloud platform account registration request includes: Based on the cloud platform account registration request, obtain enterprise information, including: enterprise needs, enterprise name, and a primary account name set by the enterprise; Create a business master account ID associated with the enterprise; An enterprise master account is established based on the enterprise information and the enterprise master account ID.

3. The method for designing an enterprise cloud platform account according to claim 2, characterized in that: The establishing of the business owner account based on the business information and the business owner account ID includes: Set the number of enterprise master accounts based on the enterprise needs; A corresponding number of enterprise master accounts are established based on the master account name set by the enterprise and the enterprise master account ID, and all the enterprise master accounts are bound to the enterprise name.

4. A system for designing an enterprise cloud platform account, used to execute the method for designing an enterprise cloud platform account according to any one of claims 1 to 3, characterized in that: The system comprises: A master account creation module, configured to create an enterprise master account in response to an enterprise's cloud platform account registration request, wherein the enterprise master account is used for enterprise financial management and enterprise sub-account management; A sub-account creation module, configured to create a number of enterprise sub-accounts corresponding to the enterprise master account based on the enterprise's demand for service functions, and the enterprise sub-accounts are used to use the service functions; A sub-account name and ID module is configured to generate a sub-account name and a sub-account ID for the enterprise sub-account, and verify the sub-account ID; A sub-account permission module, configured to grant at least one sub-account permission to the enterprise sub-account, wherein the sub-account permission includes: cloud platform console permission and programming permission; The account system module is configured to match the enterprise master account with all enterprise sub-accounts, obtain the enterprise cloud platform account system, and send it to the enterprise.

Images