A private cloud device control method, domain, computer device and readable storage medium
By building a domain in a private cloud device and utilizing the master control device and command data communication, autonomous authentication and data synchronization are achieved. This solves the problem of identity verification for private cloud devices without network or third-party authentication services, ensuring data security and privacy, and improving user experience.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- YICI NETCOM (HANGZHOU) TECH CO LTD
- Filing Date
- 2023-05-31
- Publication Date
- 2026-04-28
AI Technical Summary
Private cloud devices cannot authenticate users when they are unable to connect to the network or when third-party authentication services cease operation, resulting in a lack of data security and privacy.
By selecting a master control device in the private cloud device and building a domain, the master control device forms a temporary device group with other devices, communicates using command data, and independently stores the master control account and private cloud account in each device to achieve self-authentication and data synchronization, ensuring the security and privacy of the private cloud device.
Without the need for third-party authentication services, it enables self-authentication and data security for private cloud devices, ensuring data security and privacy and improving user experience.
Smart Images

Figure CN116723012B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of cloud computing technology, specifically to a private cloud device control method, domain, computer device, and readable storage medium. Background Technology
[0002] The development of cloud computing has been rapid, and its unique elastic scaling, flexible business expansion, and deployment capabilities have gained widespread recognition. Personal private cloud products, as an important supplement to public clouds, help solve the problems of high-speed, private business scenarios without internet access. When using personal private cloud devices, accessing services requires authentication, and users may own multiple private cloud devices. For personal private cloud devices, the following requirements are typically needed: privacy—users do not want others to know they are using a particular personal private cloud device; and offline usability—that is, authentication is performed independently by the personal cloud device, without relying on third-party service providers.
[0003] However, in some use cases, private cloud devices cannot connect to the network and therefore cannot use third-party authentication services; in other use cases, third-party authentication service providers have stopped providing services, but access to private cloud devices is still required. Summary of the Invention
[0004] This invention aims to address one of the technical problems in related technologies to a certain extent. To this end, this invention provides a private cloud device control method that eliminates the need for third-party authentication and does not overwrite existing private cloud login accounts.
[0005] To achieve the above objectives, the present invention adopts the following technical solution:
[0006] A private cloud device control method is provided for controlling a private cloud device to join a group formed by the private cloud device or to access a group that the private cloud device has already joined. The private cloud device control method includes the following steps:
[0007] Two or more controlled private cloud devices log in to their respective private cloud accounts, select any one of the devices as the master control device, and its account as the master control account. The domain is composed of the two or more controlled private cloud devices.
[0008] The master control device distributes the master control account to other private cloud devices in the domain. In the other private cloud devices in the domain, the master control account and its own private cloud account are stored in two different data tables.
[0009] Other private cloud devices in the domain can join other groups consisting of private cloud devices through the master control account;
[0010] When a private cloud device in a domain accesses a group of private cloud devices that other private cloud devices have joined, the private cloud devices that have joined the group act as proxies for the other private cloud devices to access the group.
[0011] Optionally, constituting a domain from controlled private cloud devices includes the following steps:
[0012] A temporary equipment group consisting of controlled private cloud devices;
[0013] In the temporary device group, the master control device communicates with other private cloud devices in the domain using command data as the communication content;
[0014] After receiving the command data, other private cloud devices in the temporary device group execute the command data and synchronize with the main control device.
[0015] Optionally, the command data includes:
[0016] Key, used to identify data;
[0017] Actions are used to record operations performed on data, including adding, deleting, and modifying.
[0018] Value is used to record the value of data after it has been processed.
[0019] Optionally, when a private cloud device in the domain, other than a device of the master control device, synchronizes data with other private cloud devices, the device first sends the command data to the master control device, and then the master control device sends it to other private cloud devices for synchronization.
[0020] Optionally, after other private cloud devices in the domain, excluding the master control device, join other groups consisting of private cloud devices through the master control account, the information of the joined groups is synchronized among the various private cloud devices in the domain.
[0021] Optionally, in two separate data tables—the storage master account and the storage's own private cloud account—the master account and its own private cloud account have a corresponding relationship, including:
[0022] Your private cloud account ID corresponds to your domain ID; your private cloud account password corresponds to your domain password.
[0023] The technical solution provided by this invention does not rely on third-party authentication services. Even when private cloud devices cannot connect to the internet or third-party authentication service providers cease providing services, authentication can still be provided through the master control device, ensuring the data security and privacy of the private cloud. Furthermore, the technical solution provided by this invention ensures that the master control account of other private cloud devices in the domain, excluding the master control device, is stored separately and independently in different data tables. Therefore, the master control account will not overwrite the accounts of other private cloud devices, facilitating user access. Thanks to the domain comprised of private cloud devices, when other private cloud devices in the domain join a group composed of other private cloud devices, they join using the master control account. Moreover, all devices within the domain will synchronize data, allowing other private cloud devices in the domain to access information about the groups they join, further guaranteeing the privacy of the private cloud.
[0024] Furthermore, the present invention also provides a domain composed of private cloud devices, used to control the private cloud devices to join a group formed by the private cloud devices. The formation of a domain composed of private cloud devices includes the following steps:
[0025] Choose any one of two or more private cloud devices as the master control device;
[0026] A temporary equipment group consisting of private cloud devices;
[0027] In the temporary device group, the master control device communicates with other private cloud devices in the domain using command data as the communication content;
[0028] After receiving the command data, other private cloud devices in the temporary device group execute the command data and synchronize with the main control device.
[0029] Optionally, the command data includes:
[0030] Key, used to identify data;
[0031] Actions are used to record operations performed on data, including adding, deleting, and modifying.
[0032] Value is used to record the value of data after it has been processed.
[0033] Optionally, when a non-master device in the domain synchronizes data with other private cloud devices, the device first sends the command data to the master device, and then the master device sends it to other private cloud devices for synchronization.
[0034] Optionally, when any device in a domain composed of private cloud devices joins another group composed of private cloud devices, the master control device distributes its login account as the master control account to the other private cloud devices. In the other private cloud devices, the master control account and its own private cloud account are stored in two different data tables.
[0035] Other private cloud devices in the domain can join other groups consisting of private cloud devices through the master account.
[0036] Optionally, when a private cloud device in a domain accesses a group of private cloud devices that other private cloud devices have joined, the private cloud devices that have joined the group act as proxies for the other private cloud devices to access the group.
[0037] Optionally, in two separate data tables—the storage master account and the storage's own private cloud account—the master account and its own private cloud account have a corresponding relationship, including:
[0038] Your private cloud account ID corresponds to your domain ID; your private cloud account password corresponds to your domain password.
[0039] Optionally, after other private cloud devices in the domain join other groups consisting of private cloud devices through the master account, the information of the joined groups is synchronized among the various private cloud devices in the domain.
[0040] The domain composed of private cloud devices provided by this invention is similar to the reasoning process of the beneficial effects of the aforementioned private cloud device control method, and will not be repeated here.
[0041] Furthermore, the present invention also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement any of the above-described private cloud device control methods.
[0042] In addition, the present invention also provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the private cloud device control method described in any of the above claims.
[0043] These features and advantages of the present invention will be disclosed in detail in the following specific embodiments and accompanying drawings. The preferred embodiments or means of the present invention will be shown in detail in conjunction with the accompanying drawings, but are not intended to limit the technical solutions of the present invention. In addition, each of these features, elements and components appearing in the following text and drawings is a plurality of, and different symbols or numbers are used for convenience of representation, but all represent parts with the same or similar construction or function. Attached Figure Description
[0044] The present invention will be further described below with reference to the accompanying drawings:
[0045] Figure 1 This is a schematic diagram of an embodiment of the present invention. Detailed Implementation
[0046] The embodiments of the present invention are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described are intended to explain the present invention and should not be construed as limiting the invention.
[0047] The terms "an embodiment," "example," or "trademark" used in this specification refer to a particular feature, structure, or characteristic described in connection with the embodiment itself that may be included in at least one embodiment disclosed in this patent. The phrase "in an embodiment" appearing in various places throughout the specification does not necessarily refer to the same embodiment.
[0048] Example:
[0049] like Figure 1 As shown, this embodiment provides a private cloud device control method for controlling a private cloud device to join a group formed by the private cloud device or to access a group that the private cloud device has already joined.
[0050] The private cloud device control method provided in this embodiment includes the following steps:
[0051] Private cloud device 1 and private cloud device 2 log in to their respective private cloud accounts. In other embodiments, the number of private cloud devices can be increased according to actual needs. A single private cloud device can directly join a group formed by private cloud devices. Therefore, the method provided in this embodiment is applicable to the control of two or more private cloud devices. Any one of the devices is selected as the master control device, and its account is selected as the master control account. In this embodiment, private cloud device 1 is selected as the master control device, forming a domain with private cloud device 2.
[0052] The sub-steps for constructing a domain for a private cloud device are as follows:
[0053] A temporary device group is formed by private cloud device 1 and private cloud device 2. The underlying devices and logic used in this step are similar to those in ordinary QQ groups and WeChat groups, and will not be described in detail here.
[0054] In the temporary device group, the master device communicates with other private cloud devices in the domain, namely private cloud device 2, using command data as the communication content. Unlike QQ groups and WeChat groups, which have visible dialog boxes and whose communication content includes conversations and content sharing between group members, this temporary device group lacks visible dialog boxes. The communication content between the various devices that are group members is not conversations or content sharing, but rather command data. The command data includes:
[0055] Key, used to identify data;
[0056] Actions are used to record operations performed on data, including adding, deleting, and modifying.
[0057] Value is used to record the value of data after it has been processed.
[0058] After receiving the command data, private cloud device 2 executes it. That is, according to the content of the command data, the receiving device performs operations such as adding, deleting, and modifying relevant data. After the operation is completed, the value of the modified data matches the value in the command data. This is how it synchronizes with the main control device.
[0059] It should be noted that in this embodiment, each device constituting the domain can only synchronize data with other private cloud devices through the master control device. When a non-master control device in the domain synchronizes data with other private cloud devices, the device first sends the command data to the master control device, and then the master control device sends it to other private cloud devices for synchronization.
[0060] After a domain is established, the master control device distributes the master control account to other private cloud devices within the domain. Along with the master control account, the master control device's friend list, group list, and other information are also distributed. In other private cloud devices, the master control account and its own private cloud account are stored in two separate data tables. Specifically, in these two separate data tables, the master control account and its own private cloud account have a corresponding relationship: the private cloud account ID corresponds to the domain ID; the private cloud account password corresponds to the domain password. Therefore, private cloud device 2 can log in using both its own account 2 and the master control account (i.e., account 1). It is evident that the master control account does not overwrite the accounts on other private cloud devices. After the domain is established, the original control data and accounts are retained and can be used normally on other private cloud devices without switching to a specific device, achieving a seamless user experience.
[0061] Other private cloud devices within the domain join other groups composed of private cloud devices using the master control account. Information from these groups is then synchronized across all private cloud devices within the domain. When multiple private cloud devices belonging to a user form a domain and join a new group, they join the new group using the master control account. When a user accesses group 3 using private cloud device 2, since a master control account has been assigned to private cloud device 2, it can directly request data from group 3. Therefore, other private cloud devices within the domain can also access information about the groups they have joined, further ensuring the privacy of the private cloud.
[0062] When a private cloud device in a domain accesses a group of private cloud devices that other private cloud devices have joined, the private cloud devices already in the group act as proxies for the other private cloud devices accessing the group. For example... Figure 1 As shown, when a user accesses group 2 on private cloud device 1, private cloud device 1 will find that group 2 was joined by account 2 of private cloud device 1. Therefore, private cloud device 1 will forward the request to private cloud device 2, which will act as a proxy for private cloud device 1 to access group 2, and finally return the result to device 1.
[0063] As can be seen, the technical solution provided in this embodiment does not rely on third-party authentication services. Even when the private cloud device cannot connect to the Internet or the third-party authentication service provider stops providing services, it can still provide authentication through the main control device, thus ensuring the data security of the private cloud device and the privacy of the private cloud.
[0064] This embodiment also provides a domain composed of private cloud devices, used to control the private cloud devices to join a group formed by the private cloud devices. The steps to form a domain composed of private cloud devices are as follows:
[0065] Choose any one of two or more private cloud devices as the master control device;
[0066] A temporary device group is formed by private cloud devices. The underlying devices and logic used to form this temporary device group are similar to those in ordinary QQ groups and WeChat groups, and will not be described in detail here. In the temporary device group, the master device communicates with other private cloud devices in the domain using command data as the communication content. Unlike QQ groups and WeChat groups, which have visual dialog boxes and whose communication content includes conversations and content sharing between group members, this temporary device group does not have visual dialog boxes. The communication content between the various devices that are group members is not conversations or content sharing, but command data. The command data includes:
[0067] Key, used to identify data;
[0068] Actions are used to record operations performed on data, including adding, deleting, and modifying.
[0069] Value is used to record the value of data after it has been processed.
[0070] After receiving the command data, other private cloud devices in the temporary device group execute the command data and synchronize with the master control device. It should be noted that in this embodiment, each device constituting the domain can only synchronize data with other private cloud devices through the master control device. When a non-master control device in the domain synchronizes data with other private cloud devices, the device first sends the command data to the master control device, and then the master control device distributes it to the other private cloud devices for synchronization.
[0071] As described in the aforementioned private cloud device control method, when any device in a domain composed of private cloud devices joins another group composed of private cloud devices, the master control device distributes its login account as the master control account to the other private cloud devices. In the other private cloud devices, the master control account and its own private cloud account are stored in two different data tables. The master control account and its own private cloud account have a corresponding relationship, including: the ID of its own private cloud account corresponds to the domain ID; and the password of its own private cloud account corresponds to the domain password. Other private cloud devices in the domain join other groups composed of private cloud devices through the master control account, and the information of the joined groups is then synchronized among the various private cloud devices in the domain.
[0072] The beneficial effects of the domain composed of private cloud devices provided in this embodiment are similar to the beneficial effects of the aforementioned private cloud device control method, and will not be repeated here.
[0073] Meanwhile, this embodiment also provides a computer device, including a memory and a processor. The memory stores a computer program, and when the computer program is executed by the processor, it causes the processor to perform the above-described... private The steps of the cloud device control method are described above. The steps of the private cloud device control method here can be the steps in the memory analysis methods of the various embodiments described above.
[0074] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. Accordingly, the computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can implement the methods of any of the above embodiments. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
[0075] The above are merely specific embodiments of the present invention, but the scope of protection of the present invention is not limited thereto. Those skilled in the art should understand that the present invention includes, but is not limited to, the contents described in the accompanying drawings and the specific embodiments above. Any modifications that do not depart from the functional and structural principles of the present invention will be included within the scope of the claims.
Claims
1. A private cloud device control method for controlling a private cloud device to join a group formed by private cloud devices or to access a group to which the private cloud device has already joined, characterized by, The private cloud device control method includes the following steps: Two or more controlled private cloud devices log in to their respective private cloud accounts and select any one of the devices as the master device, with its account serving as the master account. In the event that the device cannot connect to the Internet or the third-party authentication service provider stops providing services, the two or more controlled private cloud devices constitute a domain. The master control device distributes the master control account to other private cloud devices in the domain. In the other private cloud devices in the domain, the master control account and its own private cloud account are stored in two different data tables. Other private cloud devices in the domain can join other groups consisting of private cloud devices through the master control account; When a private cloud device in a domain accesses a group of private cloud devices that other private cloud devices have joined, the private cloud devices that have joined the group act as proxies for the other private cloud devices to access the group.
2. The private cloud device control method according to claim 1, characterized by, The process of constructing a domain from controlled private cloud devices includes the following steps: A temporary equipment group consisting of controlled private cloud devices; In the temporary device group, the master control device communicates with other private cloud devices in the domain using command data as the communication content; After receiving the command data, other private cloud devices in the temporary device group execute the command data and synchronize with the main control device.
3. The private cloud device control method according to claim 2, wherein The command data includes: Key, used to identify data; Actions are used to record operations performed on data, including adding, deleting, and modifying. Value is used to record the value of data after it has been processed.
4. The private cloud device control method according to claim 2, characterized by, When a private cloud device in the domain, other than the master control device, synchronizes data with other private cloud devices, the device first sends the command data to the master control device, and then the master control device sends it to the other private cloud devices for synchronization.
5. The private cloud device control method according to claim 4, wherein After other private cloud devices in the domain, excluding the master control device, join other groups consisting of private cloud devices through the master control account, the information of the joined groups is synchronized among the various private cloud devices in the domain.
6. The private cloud device control method according to any one of claims 1 to 4, characterized by, In the two separate data tables—the storage master account and the storage's own private cloud account—there is a corresponding relationship between the master account and its own private cloud account, including: Your private cloud account ID corresponds to your domain ID; your private cloud account password corresponds to your domain password.
7. A domain consisting of private cloud devices for controlling the joining of private cloud devices to a swarm of private cloud devices, characterized in that, In the event of an inability to connect to the internet or the cessation of service provision by a third-party authentication service provider, establishing a domain comprised of private cloud devices involves the following steps: Choose any one of two or more private cloud devices as the master control device; A temporary equipment group consisting of private cloud devices; In the temporary device group, the master control device communicates with other private cloud devices in the domain using command data as the communication content; After receiving the command data, other private cloud devices in the temporary device group execute the command data and synchronize with the main control device.
8. The domain of private cloud devices of claim 7, wherein, The command data includes: Key, used to identify data; Actions are used to record operations performed on data, including adding, deleting, and modifying. Value is used to record the value of data after it has been processed.
9. The domain of private cloud devices of claim 7, wherein, When a non-master device in the domain synchronizes data with other private cloud devices, the device first sends the command data to the master device, and then the master device sends it to the other private cloud devices for synchronization.
10. The domain of private cloud devices according to any of claims 7 to 9, characterized in that, When any device in a domain composed of private cloud devices joins another group composed of private cloud devices, the master control device distributes its login account as the master control account to other private cloud devices. In other private cloud devices, the master control account and its own private cloud account are stored in two different data tables. Other private cloud devices in the domain can join other groups consisting of private cloud devices through the master account.
11. The domain of private cloud devices according to any of claims 7 to 9, characterized in that, When a private cloud device in a domain accesses a group of private cloud devices that other private cloud devices have joined, the private cloud devices that have joined the group act as proxies for the other private cloud devices to access the group.
12. The domain comprised of private cloud devices according to claim 10, characterized in that, In the two separate data tables—the storage master account and the storage's own private cloud account—there is a corresponding relationship between the master account and its own private cloud account, including: Your private cloud account ID corresponds to your domain ID; your private cloud account password corresponds to your domain password.
13. The domain comprised of private cloud devices as described in claim 10, characterized in that, After other private cloud devices in the domain join other groups consisting of private cloud devices through the master control account, the information of the groups they join is synchronized among the various private cloud devices in the domain.
14. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the private cloud device control method according to any one of claims 1 to 6.
15. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the private cloud device control method according to any one of claims 1 to 6.
Citation Information
Patent Citations
Data communication method, device and equipment, readable storage medium and server
CN115801861A