Member joining method, device and electronic equipment

Abstract

The present application relates to the field of blockchain, and in particular to a member joining method, device and electronic device, the method comprising: when determining that a new member requesting to join a shared node meets the admission conditions, obtaining all file information required by the new member on the shared node, and adding the file information to a preset directory of the shared node corresponding to the new member, and then adding an application configuration item corresponding to the new member to the business configuration file of the back-end application of the shared node, and restarting the back-end service of the deployment device of each business node in all business nodes one by one, determining whether the deployment process of the file information and application configuration items is completed, and when the deployment process is completed, determining that the new member has successfully joined the shared node. This member joining method does not require manual operation, can save time and labor costs, is not prone to errors, and avoids risks to the business operations of other members on the shared node.

Description

Technical Field

[0001] The present application relates to the field of blockchain, and in particular to a member joining method, device and electronic device. Background Art

[0002] Blockchain is a distributed database that uses consensus and proof algorithms to ensure that each member node holds a complete record of the blockchain ledger. Blockchain maintains data consistency across all member nodes, making the blockchain's historical records extremely difficult to tamper with.

[0003] A consortium blockchain is a blockchain that targets only members of a specific group and a limited number of third parties. Within a consortium blockchain, multiple pre-selected nodes can be designated as bookkeepers. The generation of each block is determined by all pre-selected nodes, and third parties can conduct limited queries through the blockchain's open application program interface (API). Consortium blockchains have specific requirements for the configuration and network environment of consensus or verification nodes.

[0004] Typically, a consortium blockchain platform consists of multiple peer-to-peer member nodes. Each member node is a participant in the consortium blockchain platform and typically includes business nodes, computer nodes, and blockchain nodes. Depending on their deployment location, member nodes can be divided into self-built nodes and shared nodes. Self-built nodes are nodes deployed by each independently deployed participant in the consortium blockchain platform. They generally include independent business service nodes and blockchain nodes, and can deploy complete blockchain contracts. Through self-built nodes, users can initiate queries, maintenance, and other transactions on the blockchain, making them blockchain users. Shared nodes are physical nodes shared by multiple participants, providing business and blockchain access to multiple participants. All participants initiate queries, maintenance, and other transactions on the blockchain through this node.

[0005] When a new member needs to join the shared node of the alliance blockchain platform to participate in business access, the shared node of the alliance blockchain platform needs to be deployed. During the specific deployment process, a series of steps including blockchain access, activation of smart contracts, and additional configuration and restart of back-end applications need to be handled manually. This not only wastes manpower and time costs, but also has a high risk of errors, which can easily bring risks to the business operations of other members on the shared node. Summary of the Invention

[0006] The present application provides a member joining method, device and electronic device, which adds all the file information required by the new member on the shared node to the preset directory corresponding to the new member in the business node, and adds the application configuration item corresponding to the new member in the business configuration file of the business node, and restarts the back-end service to determine whether all the above file information and application configuration items are deployed, thereby determining that the new member has successfully joined the shared node. This member joining method does not require manual operation, saves time and manpower costs, is not prone to errors, and avoids risks to the business operations of other members on the shared node.

[0007] In a first aspect, the present application provides a member joining method, the method comprising:

[0008] When it is determined that the new member requesting to join the shared node meets the admission conditions, all file information required by the new member on the shared node is obtained, and the file information is added to the preset directory of the shared node corresponding to the new member;

[0009] Adding an application configuration item corresponding to the new member to the business configuration file of the shared node backend application, wherein the application configuration item is used for the new member to perform business functions on the shared node;

[0010] Determining whether the deployment process of the file information and the application configuration item is complete by restarting the backend service of the deployment device of each of all business nodes one by one;

[0011] When the deployment process is completed, it is determined that the new member has successfully joined the shared node.

[0012] By adding all the file information required by the new member on the shared node to the preset directory corresponding to the new member in the business node, and adding the application configuration items corresponding to the new member in the business configuration file of the business node, and restarting the back-end service to determine whether all the above file information and application configuration items are deployed, it is determined that the new member has successfully joined the shared node. This member joining method does not require manual operation, saves time and manpower costs, is not prone to errors, and avoids risks to the business operations of other members on the shared node.

[0013] In one possible design, when it is determined that a new member requesting to join a shared node meets the admission requirements, all file information required by the new member on the shared node is obtained, including:

[0014] Upon receiving the admission notification of the new member, obtaining the institution information corresponding to the new member, wherein the institution information includes the institution number, institution name, institution contact name and corresponding contact information of the institution contact;

[0015] Obtaining the public and private key configuration files corresponding to the new member and the access address files corresponding to the public and private key configuration files;

[0016] The organization information, the public and private key configuration files, and the access address file are added to the original first contract configuration file on the shared node to obtain a second contract configuration file.

[0017] Through the above method, when the shared node does not include the computing node, the organization information, public and private key configuration files, access address files and contract configuration files required for the new member to join the shared node are obtained. These file information is used for shared node information deployment.

[0018] In one possible design, after adding the organization information, the public and private key configuration files, and the access address file to the original first contract configuration file on the shared node to obtain the second contract configuration file, the method further includes:

[0019] Accessing unused account files in the user profile directory in the shared node;

[0020] The account file is renamed to obtain a computing node user file corresponding to the new member.

[0021] By using the above method, when the shared node includes a computing node, the computing node user file corresponding to the new member is obtained, and the computing node user file is used for shared node information deployment.

[0022] In one possible design, adding the file information to a preset directory of the shared node corresponding to the new member includes:

[0023] Creating or obtaining a preset directory corresponding to the new member under the configuration directory of the service node;

[0024] Add the file information to the preset directory.

[0025] Through the above method, the file information required by the new member on the shared node is added to the preset location for easy subsequent use and retrieval.

[0026] In one possible design, whether the deployment process of the file information and the application configuration item is complete is determined by restarting the backend service of the deployment device of each of all business nodes one by one, including:

[0027] Create a database and application table corresponding to the new member, and insert initialization business data into the database and application table;

[0028] Restarting backend services of deployment devices of each of all business nodes one by one according to the initialization business data and the application configuration items;

[0029] Obtaining log files of the backend service during operation;

[0030] Determine whether the deployment process of the file information and the application configuration item is completed through the log file.

[0031] Through the above method, it is determined whether the information deployment work corresponding to the new member joining the shared node is completed.

[0032] In one possible design, creating a database and application table corresponding to the new member includes:

[0033] Get the first initialization database statement corresponding to the existing member;

[0034] Adding the file information to the first initialization database statement to obtain a second initialization database statement corresponding to the new member;

[0035] The second database initialization statement is executed to obtain a database and an application table corresponding to the new member, wherein the name corresponding to the database is inconsistent with the name of the database corresponding to the existing member.

[0036] Through the above method, a database and application table are created for the new member, which are used to store initialization data and support subsequent backend service restarts.

[0037] In a possible design, before determining that a new member requesting to join a shared node meets the admission conditions, the following steps are also included:

[0038] Upon receiving a request from the new member to join the shared node, reviewing the admission qualifications of the new member;

[0039] If the review fails, the new member will be denied permission to join the shared node;

[0040] If the review is passed, the new member's request to join will be voted on through the alliance contract;

[0041] If all pre-selected nodes unanimously approve the joining request, it is determined that the new member meets the admission conditions for joining the shared node;

[0042] If there is a pre-selected node that does not agree to the joining request, the new member is denied from joining the shared node.

[0043] Through the above method, it is determined whether the new member meets the admission conditions for joining the shared node.

[0044] In a second aspect, the present application provides a member joining device, the device comprising:

[0045] An adding module, configured to, upon determining that a new member requesting to join a shared node meets admission requirements, obtain all file information required by the new member on the shared node, and add the file information to a preset directory of the shared node corresponding to the new member;

[0046] A new adding module, configured to add an application configuration item corresponding to the new member to the business configuration file of the back-end application of the shared node, wherein the application configuration item is used for the new member to execute the business function on the shared node;

[0047] A restart module, configured to determine whether the deployment process of the file information and the application configuration item is complete by restarting the backend service of the deployment device of each of all business nodes one by one;

[0048] The determination module is configured to determine whether the new member has successfully joined the shared node when the deployment process is completed.

[0049] In one possible design, the adding module is specifically used to:

[0050] Upon receiving the admission notification of the new member, obtaining the institution information corresponding to the new member, wherein the institution information includes the institution number, institution name, institution contact name and corresponding contact information of the institution contact;

[0051] Obtaining the public and private key configuration files corresponding to the new member and the access address files corresponding to the public and private key configuration files;

[0052] The organization information, the public and private key configuration files, and the access address file are added to the original first contract configuration file on the shared node to obtain a second contract configuration file.

[0053] In a possible design, the adding module is further used to:

[0054] Accessing unused account files in the user profile directory in the shared node;

[0055] The account file is renamed to obtain a computing node user file corresponding to the new member.

[0056] In one possible design, adding the file information to a preset directory of the shared node corresponding to the new member includes:

[0057] Creating or obtaining a preset directory corresponding to the new member under the configuration directory of the service node;

[0058] Add the file information to the preset directory.

[0059] In one possible design, the restart module includes:

[0060] A creation unit, configured to create a database and application table corresponding to the new member, and insert initialization service data into the database and application table;

[0061] A restart unit, configured to restart the backend service of the deployment device of each of all the service nodes one by one according to the initialization service data and the application configuration item;

[0062] An acquisition unit, configured to acquire log files of the backend service during operation;

[0063] A determination unit is configured to determine, through the log file, whether the deployment process of the file information and the application configuration item is completed.

[0064] In one possible design, the creating unit is specifically configured to:

[0065] Get the first initialization database statement corresponding to the existing member;

[0066] Adding the file information to the first initialization database statement to obtain a second initialization database statement corresponding to the new member;

[0067] The second database initialization statement is executed to obtain a database and an application table corresponding to the new member, wherein the name corresponding to the database is inconsistent with the name of the database corresponding to the existing member.

[0068] In one possible design, the device further includes:

[0069] An audit module, configured to audit the admission qualifications of a new member upon receiving a request from the new member to join the shared node;

[0070] The processing module is used to reject the new member from joining the shared node if the review fails; if the review passes, vote on the new member's joining request through the alliance contract; if all pre-selected nodes unanimously approve the joining request, it is determined that the new member meets the admission conditions for joining the shared node; if any pre-selected node disagrees with the joining request, the new member is rejected from joining the shared node.

[0071] In a third aspect, the present application provides an electronic device, comprising:

[0072] Memory for storing computer programs;

[0073] The processor is configured to implement the above-mentioned member joining method steps when executing the computer program stored in the memory.

[0074] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the above-mentioned member joining method are implemented.

[0075] In a fifth aspect, the present application provides a computer program product, which, when executed on a computer, enables the computer to execute the above-mentioned member joining method steps.

[0076] By adding all the file information required by the new member on the shared node to the preset directory corresponding to the new member in the business node, and adding the application configuration items corresponding to the new member in the business configuration file of the business node, and restarting the back-end service to determine whether all the above file information and application configuration items are deployed, it is determined that the new member has successfully joined the shared node. This member joining method does not require manual operation, saves time and manpower costs, is not prone to errors, and avoids risks to the business operations of other members on the shared node.

[0077] The technical effects that can be achieved in each of the above-mentioned aspects from the second to the fifth aspects refer to the technical effects that can be achieved in the above-mentioned first aspect or various possible solutions in the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] Figure 1 A flowchart of a member joining method provided for this application;

[0079] Figure 2 A schematic diagram of the structure of a member joining device provided in this application;

[0080] Figure 3 This is a schematic diagram of the structure of an electronic device provided in this application. DETAILED DESCRIPTION

[0081] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail with reference to the accompanying drawings. The specific operating methods in the method embodiments can also be applied to device embodiments or system embodiments. It should be noted that in the description of the present application, "multiple" is understood as "at least two". "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent the following three situations: A exists alone, A and B exist at the same time, and B exists alone. A is connected to B, which can represent the following two situations: A is directly connected to B and A is connected to B through C. In addition, in the description of the present application, words such as "first" and "second" are only used to distinguish the purpose of description, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying order.

[0082] The embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0083] When a new member needs to join the shared node of the alliance blockchain platform to participate in business access, the shared node of the alliance blockchain platform needs to be deployed. During the specific deployment process, a series of steps including blockchain access, activation of smart contracts, and additional configuration and restart of back-end applications need to be handled manually. This not only wastes manpower and time costs, but also has a high risk of errors, which can easily bring risks to the business operations of other members on the shared node.

[0084] In order to solve the above problems, the present application provides a member joining method, which adds all the file information required by the new member on the shared node to the preset directory corresponding to the new member in the business node, and adds the application configuration item corresponding to the new member in the business configuration file of the business node, and restarts the back-end service to determine whether all the above file information and application configuration items are deployed, thereby determining whether the new member has successfully joined the shared node. This member joining method does not require manual operation, saves time and manpower costs, is not prone to errors, and avoids risks to the business operations of other members on the shared node. Among them, the method and device described in the embodiments of the present application are based on the same technical concept. Since the principles of the problems solved by the method and device are similar, the embodiments of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0085] like Figure 1 FIG. 1 is a flowchart of a member joining method provided by this application, which specifically includes the following steps:

[0086] S11, when it is determined that the new member requesting to join the shared node meets the admission conditions, all file information required by the new member on the shared node is obtained, and the file information is added to the preset directory of the shared node corresponding to the new member;

[0087] In an embodiment of the present application, when a request from a new member to join a shared node is received, the new member's admission qualifications are first reviewed. If the review fails, the new member's request to join the shared node is rejected; if the review passes, the new member's request to join is further voted on through the alliance contract.

[0088] During the voting, if all pre-selected nodes unanimously approve the new member's joining request, the new member is determined to meet the admission requirements for joining the shared node; if there is a pre-selected node that disagrees with the new member's joining request, the new member is denied from joining the shared node.

[0089] Through the above method, it is possible to determine whether the new member meets the admission conditions of the shared node. When it is determined that the new member meets the admission conditions, further, all file information required by the new member on the shared node is obtained. The specific content of the file information varies depending on the type of shared node. When the shared node does not include a computing node, the method for obtaining the file information includes:

[0090] Upon receiving a new member's admission notification, obtain the new member's corresponding institution information, which includes the institution number, institution name, institution contact name, and the corresponding contact information of the institution contact, where the contact information includes telephone number, email address, WeChat ID, etc.;

[0091] Next, obtain the public and private key configuration files corresponding to the new member and the access address files corresponding to the public and private key configuration files. The public and private key configuration files can be account.Json files, and the access address files can be address files. Of course, both the public and private key pair files and the access address files may be embodied in different file formats due to different design languages, so the file formats are not specifically limited here.

[0092] Furthermore, the public and private key configuration files and the access address file are added to the original first contract configuration file on the shared node to obtain the second contract configuration file, wherein the first contract configuration file can be the Contract / contract.yaml file, and the information in the obtained second contract configuration file includes the institution information corresponding to the new member, the institution name, the name of the institution contact, the contact information corresponding to the institution contact, accountJson, memberAddress, etc.

[0093] When the shared nodes do not include compute nodes, the above method can be used to obtain all the file information required by the new member on the shared nodes. In one possible design, when the shared nodes include compute nodes, in addition to obtaining the above file information, it is still necessary to obtain the compute node user files corresponding to the new member. The specific method for obtaining user files can be:

[0094] Access unused account files in the user profile directory of the shared node and rename them to obtain the compute node user file for the new member. For example, rename the unused *.account file in the user profile directory of the shared node to the root.account file. This root.account file will be the user file for the compute node for the new user.

[0095] Through the above method, all the file information required by the new member on the shared node can be obtained. Furthermore, this file information needs to be deployed at the preset location of the new member's corresponding shared node. The specific deployment method can be:

[0096] Create a preset directory corresponding to the new member under the configuration directory of the business node, where the preset directory can be a directory named after the new member's identity document (ID), and then add all file information to the preset directory. If a preset directory corresponding to the new member exists under the configuration directory, you can directly obtain the preset directory without recreating it.

[0097] S12, adding an application configuration item corresponding to the new member to the business configuration file of the shared node backend application;

[0098] In an embodiment of the present application, application configuration items are used for new members to execute business functions on the shared node. For example, a configuration item corresponding to the data query function is added to the new member, so that the new member can perform data query on the shared node. That is to say, in the business configuration file of the back-end application in the sharing stage, a new application configuration item corresponding to the new member is added, which is equivalent to opening the business function corresponding to the application configuration item on the shared node to the new member, so that the new member can execute the business function corresponding to the application configuration item.

[0099] S13, restarting the backend service of the deployment device of each of all business nodes one by one to determine whether the deployment process of the file information and application configuration items is complete;

[0100] In an embodiment of the present application, after configuring the corresponding application configuration items for the new member, you can restart the back-end service to verify whether the above-mentioned file information and application configuration items have been deployed. Among them, restarting the back-end service not only requires the support of the application configuration items corresponding to the new member, but also requires the support of the initialization business data corresponding to the application configuration items. For example, if you want to restart the query service function of the back-end, you not only need to configure the application configuration items corresponding to the query service function for the new member, but also configure the application data corresponding to the query service function for the new member. At this time, the application data is part of the initialization business data; if you want to restart the playback function, you not only need to configure the application configuration items corresponding to the playback function for the new member, but also configure the application data corresponding to the playback function for the new member. At this time, the application data is also part of the initialization business data.

[0101] In short, only the application configuration items corresponding to the new member cannot support the restart of the backend service. It is also necessary to configure the initial business data for the new member. The specific configuration methods include:

[0102] Obtain the first database initialization statement corresponding to the existing member, where the first database initialization statement can be a service_init.sql statement or other type of statement. The specific language type of the database initialization statement is not limited here;

[0103] Add the above file information to the first initialization database statement to obtain the second initialization database statement corresponding to the new member, and then create a preset directory corresponding to the new member under the specific directory of the second initialization database statement, where the specific directory can be the sql_init directory corresponding to the first database statement;

[0104] Next, execute the second database initialization statement to obtain the database and application table corresponding to the new member, where the name corresponding to the database is inconsistent with the name of the database corresponding to the existing member;

[0105] Finally, the initialization business data required by the new member in the shared node is inserted into the database and application table to implement the initialization business data configuration for the new member.

[0106] Through the above method, the shared node contains not only the application configuration items corresponding to the new member, but also the initialization business data corresponding to the new member. Based on the application configuration items and initialization business data, the backend service can be restarted to verify the deployment status of the above file information and application configuration items on the shared node. The specific verification method includes:

[0107] Based on the initialized business data and application configuration items, the deployment devices of each business node in all service nodes are restarted one by one to execute the business functions corresponding to the initialized business data and application configuration items. To avoid disrupting normal business operations, system operators can also manually restart the service when the system is idle. This can be done by logging into each server of the shared node using the user running the backend program. The backend service's log files are then retrieved during operation. Based on these log files, the deployment process of the file information and application configuration items is determined to be complete. If so, step S14 is executed; otherwise, the deployment of the file information and application configuration items continues.

[0108] S14: When the deployment process is completed, it is determined that the new member has successfully joined the shared node.

[0109] In this application, when it is determined that all file information and application configuration items required by the new member on the shared node are deployed, the new member can execute the business functions supported by the application configuration items on the shared node to join the shared node.

[0110] Based on the member joining method provided in this application, all the file information required by the new member on the shared node is added to the preset directory corresponding to the new member in the business node, and the application configuration items corresponding to the new member are added to the business configuration file of the business node. By restarting the back-end service to determine whether all the above file information and application configuration items are deployed, it is determined that the new member has successfully joined the shared node. This member joining method does not require manual operation, saves time and manpower costs, is not prone to errors, and avoids risks to the business operations of other members on the shared node.

[0111] Based on the same inventive concept, the embodiment of the present application also provides a member joining device, such as Figure 2 FIG. 1 is a schematic diagram of a member joining device in the present application, which includes:

[0112] The adding module 21 is configured to obtain all file information required by the new member on the shared node when it is determined that the new member requesting to join the shared node meets the admission conditions, and add the file information to a preset directory of the shared node corresponding to the new member;

[0113] A new adding module 22 is configured to add an application configuration item corresponding to the new member to the business configuration file of the back-end application of the shared node, wherein the application configuration item is used for the new member to perform business functions on the shared node;

[0114] The restart module 23 is used to determine whether the deployment process of the file information and the application configuration item is completed by restarting the backend service of the deployment device of each business node in all business nodes one by one;

[0115] The determination module 24 is configured to determine whether the new member has successfully joined the shared node when the deployment process is completed.

[0116] In a possible design, the adding module 21 is specifically used to:

[0117] Upon receiving the admission notification of the new member, obtaining the institution information corresponding to the new member, wherein the institution information includes the institution number, institution name, institution contact name and corresponding contact information of the institution contact;

[0118] Obtaining the public and private key configuration files corresponding to the new member and the access address files corresponding to the public and private key configuration files;

[0119] The organization information, the public and private key configuration files, and the access address file are added to the original first contract configuration file on the shared node to obtain a second contract configuration file.

[0120] In a possible design, the adding module 21 is further used to:

[0121] Accessing unused account files in the user profile directory in the shared node;

[0122] The account file is renamed to obtain a computing node user file corresponding to the new member.

[0123] In one possible design, adding the file information to a preset directory of the shared node corresponding to the new member includes:

[0124] Creating or obtaining a preset directory corresponding to the new member under the configuration directory of the service node;

[0125] Add the file information to the preset directory.

[0126] In one possible design, the restart module 23 includes:

[0127] A creation unit, configured to create a database and application table corresponding to the new member, and insert initialization service data into the database and application table;

[0128] A restart unit, configured to restart the backend service of the deployment device of each of all the service nodes one by one according to the initialization service data and the application configuration item;

[0129] An acquisition unit, configured to acquire log files of the backend service during operation;

[0130] A determination unit is configured to determine, through the log file, whether the deployment process of the file information and the application configuration item is completed.

[0131] In one possible design, the creating unit is specifically configured to:

[0132] Get the first initialization database statement corresponding to the existing member;

[0133] Adding the file information to the first initialization database statement to obtain a second initialization database statement corresponding to the new member;

[0134] The second database initialization statement is executed to obtain a database and an application table corresponding to the new member, wherein the name corresponding to the database is inconsistent with the name of the database corresponding to the existing member.

[0135] In one possible design, the device further includes:

[0136] An audit module, configured to audit the admission qualifications of a new member upon receiving a request from the new member to join the shared node;

[0137] The processing module is used to reject the new member from joining the shared node if the review fails; if the review passes, vote on the new member's joining request through the alliance contract; if all pre-selected nodes unanimously approve the joining request, it is determined that the new member meets the admission conditions for joining the shared node; if any pre-selected node disagrees with the joining request, the new member is rejected from joining the shared node.

[0138] Based on the member joining device provided by the present application, all the file information required by the new member on the shared node is added to the preset directory corresponding to the new member in the business node, and the application configuration items corresponding to the new member are added to the business configuration file of the business node, and the back-end service is restarted to determine whether all the above file information and application configuration items are deployed, thereby determining that the new member has successfully joined the shared node. This member joining method does not require manual operation, saves time and manpower costs, is not prone to errors, and avoids risks to the business operations of other members on the shared node.

[0139] Based on the same inventive concept, an electronic device is also provided in the embodiment of the present application, and the electronic device can realize the function of the aforementioned member joining device, referring to Figure 3 , the electronic device includes:

[0140] At least one processor 31, and a memory 32 connected to the at least one processor 31. The specific connection medium between the processor 31 and the memory 32 is not limited in the embodiment of the present application. Figure 3 In the example, the processor 31 and the memory 32 are connected via the bus 30. The bus 30 is connected to the memory 32 via the bus 30. Figure 3 The bus 30 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 3 In the figure, only one thick line is used to represent the bus, but this does not mean that there is only one bus or one type of bus. Alternatively, the processor 31 can also be called a controller, and there is no limitation on the name.

[0141] In the embodiment of the present application, the memory 32 stores instructions that can be executed by at least one processor 31. The at least one processor 31 can execute the member joining method discussed above by executing the instructions stored in the memory 32. The processor 31 can implement Figure 2 The functions of each module in the device shown.

[0142] Among them, the processor 31 is the control center of the device, which can use various interfaces and lines to connect the various parts of the entire control device, and monitor the device as a whole by running or executing instructions stored in the memory 32 and calling data stored in the memory 32, the various functions of the device and processing data.

[0143] In one possible design, processor 31 may include one or more processing units. Processor 31 may integrate an application processor and a modem processor. The application processor primarily processes the operating system, user interface, and application programs, while the modem processor primarily handles wireless communications. It is understood that the modem processor may not be integrated into processor 31. In some embodiments, processor 31 and memory 32 may be implemented on the same chip. In some embodiments, they may also be implemented on separate chips.

[0144] The processor 31 can be a general-purpose processor, such as a central processing unit (CPU), a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the member joining method disclosed in the embodiments of this application can be directly implemented as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor.

[0145] The memory 32 is a non-volatile computer-readable storage medium that can be used to store non-volatile software programs, non-volatile computer executable programs and modules. The memory 32 may include at least one type of storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory, a random access memory (RAM), a static random access memory (SRAM), a programmable read-only memory (PROM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic memory, a magnetic disk, an optical disk, etc. The memory 32 is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 32 in the embodiment of the present application can also be a circuit or any other device that can realize a storage function, for storing program instructions and / or data.

[0146] By designing and programming the processor 31, the code corresponding to the member adding method described in the above embodiment can be fixed into the chip, so that the chip can execute the code when running. Figure 1 The steps of the member joining method of the embodiment shown are as follows: How to design and program the processor 31 is a technique well known to those skilled in the art and will not be described in detail here.

[0147] Based on the same inventive concept, an embodiment of the present application further provides a storage medium storing computer instructions. When the computer instructions are executed on a computer, the computer executes the member joining method discussed above.

[0148] In some possible implementations, various aspects of the member joining method provided in the present application can also be implemented in the form of a program product, which includes program code. When the program product is run on the device, the program code is used to enable the control device to execute the steps of the member joining method according to various exemplary embodiments of the present application described above in this specification.

[0149] The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or component, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0150] The program product of the member joining method provided in the embodiments of the present invention may be a portable compact disc read-only memory (CD-ROM) and include program code, and may be run on a computing device. However, the program product of the present invention is not limited thereto. In this document, a readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0151] A readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries readable program code. Such propagated data signals may take a variety of forms, including, but not limited to, electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium that can transmit, propagate, or transfer a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0152] Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0153] The program code for performing the operations of the present invention may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, and the like, as well as conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a stand-alone software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving a remote computing device, the remote computing device may be connected to the user computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0154] It should be noted that although several units or subunits of the device are mentioned in the above detailed description, this division is merely exemplary and not mandatory. In fact, according to embodiments of the present invention, the features and functions of two or more units described above may be embodied in a single unit. Conversely, the features and functions of a single unit described above may be further divided and embodied by multiple units.

[0155] Furthermore, although the operations of the method of the present invention are described in a particular order in the accompanying drawings, this does not require or imply that these operations must be performed in this particular order, or that all illustrated operations must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.

[0156] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0157] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0158] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0159] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0160] Obviously, those skilled in the art may make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application is intended to include these modifications and variations.

Claims

1. A member joining method, characterized in that: The method comprises: When it is determined that the new member requesting to join the shared node meets the admission conditions, all file information required by the new member on the shared node is obtained, and the file information is added to the preset directory of the shared node corresponding to the new member; Adding an application configuration item corresponding to the new member to the business configuration file of the shared node backend application, wherein the application configuration item is used for the new member to perform business functions on the shared node; Create a database and application table corresponding to the new member, and insert initialization business data into the database and application table; Restarting backend services of deployment devices of each of all business nodes one by one according to the initialization business data and the application configuration items; Obtaining log files of the backend service during operation; Determining whether the deployment process of the file information and the application configuration item is completed through the log file; When the deployment process is completed, it is determined that the new member has successfully joined the shared node.

2. The method according to claim 1, wherein When it is determined that the new member requesting to join the shared node meets the admission conditions, all file information required by the new member on the shared node is obtained, including: Upon receiving the admission notification of the new member, obtaining the institution information corresponding to the new member, wherein the institution information includes the institution number, institution name, institution contact name and corresponding contact information of the institution contact; Obtaining the public and private key configuration files corresponding to the new member and the access address files corresponding to the public and private key configuration files; The organization information, the public and private key configuration files, and the access address file are added to the original first contract configuration file on the shared node to obtain a second contract configuration file.

3. The method according to claim 2, wherein After adding the organization information, the public and private key configuration files, and the access address file to the original first contract configuration file on the shared node to obtain the second contract configuration file, the method further includes: Accessing unused account files in the user profile directory in the shared node; The account file is renamed to obtain a computing node user file corresponding to the new member.

4. The method according to claim 1, wherein The step of adding the file information to a preset directory of a shared node corresponding to the new member includes: Creating or obtaining a preset directory corresponding to the new member under the configuration directory of the service node; Add the file information to the preset directory.

5. The method according to claim 1, wherein The step of creating a database and application table corresponding to the new member includes: Get the first initialization database statement corresponding to the existing member; Adding the file information to the first initialization database statement to obtain a second initialization database statement corresponding to the new member; The second database initialization statement is executed to obtain a database and an application table corresponding to the new member, wherein the name corresponding to the database is inconsistent with the name of the database corresponding to the existing member.

6. The method according to claim 1, wherein Before determining that a new member requesting to join a shared node meets the admission criteria, it also includes: Upon receiving a request from the new member to join the shared node, reviewing the admission qualifications of the new member; If the review fails, the new member will be denied permission to join the shared node; If the review is passed, the new member's request to join will be voted on through the alliance contract; If all pre-selected nodes unanimously approve the joining request, it is determined that the new member meets the admission conditions for joining the shared node; If there is a pre-selected node that does not agree to the joining request, the new member is denied from joining the shared node.

7. A member joining device, characterized in that: The device comprises: An adding module, configured to, upon determining that a new member requesting to join a shared node meets admission requirements, obtain all file information required by the new member on the shared node, and add the file information to a preset directory of the shared node corresponding to the new member; A new adding module, configured to add an application configuration item corresponding to the new member to the business configuration file of the back-end application of the shared node, wherein the application configuration item is used for the new member to execute the business function on the shared node; a restart module, configured to create a database and application table corresponding to the new member and insert initialization business data into the database and application table; restart the backend service of the deployment device of each of all business nodes one by one based on the initialization business data and the application configuration items; obtain the log file of the backend service during operation; and determine whether the deployment process of the file information and the application configuration items is complete based on the log file; The determination module is configured to determine whether the new member has successfully joined the shared node when the deployment process is completed.

8. The device according to claim 7, wherein The adding module is specifically used for: Upon receiving the admission notification of the new member, obtaining the institution information corresponding to the new member, wherein the institution information includes the institution number, institution name, institution contact name and corresponding contact information of the institution contact; Obtaining the public and private key configuration files corresponding to the new member and the access address files corresponding to the public and private key configuration files; The organization information, the public and private key configuration files, and the access address file are added to the original first contract configuration file on the shared node to obtain a second contract configuration file.

9. The device according to claim 8, wherein The adding module is also used for: Accessing unused account files in the user profile directory in the shared node; The account file is renamed to obtain a computing node user file corresponding to the new member.

10. The device according to claim 7, wherein The step of adding the file information to a preset directory of a shared node corresponding to the new member includes: Creating or obtaining a preset directory corresponding to the new member under the configuration directory of the service node; Add the file information to the preset directory.

11. The device according to claim 7, wherein The creation unit is specifically used for: Get the first initialization database statement corresponding to the existing member; Adding the file information to the first initialization database statement to obtain a second initialization database statement corresponding to the new member; The second database initialization statement is executed to obtain a database and an application table corresponding to the new member, wherein the name corresponding to the database is inconsistent with the name of the database corresponding to the existing member.

12. The device according to claim 7, wherein The device further comprises: An audit module, configured to audit the admission qualifications of a new member upon receiving a request from the new member to join the shared node; The processing module is used to reject the new member from joining the shared node if the review fails; if the review passes, vote on the new member's joining request through the alliance contract; if all pre-selected nodes unanimously approve the joining request, it is determined that the new member meets the admission conditions for joining the shared node; if any pre-selected node disagrees with the joining request, the new member is rejected from joining the shared node.

13. An electronic device, characterized in that: include: Memory for storing computer programs; A processor, configured to implement the method steps of any one of claims 1 to 6 when executing the computer program stored in the memory.

14. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method steps according to any one of claims 1 to 6 are implemented.

15. A computer program product, characterized in that When the computer program product is run on a computer, the computer is caused to perform the method according to any one of claims 1 to 6.

Images