CN116756087A - Private cloud file management system based on multiple mobile devices - Google Patents

Abstract

The application discloses a private cloud file management system based on a plurality of mobile devices, relates to the technical field of file management systems of mobile devices, and solves the technical problem that the memory of an idle mobile phone is not fully utilized. The method of the application comprises the following steps: the cloud service system comprises a storage unit, a cloud service unit and a user side which are sequentially connected in a communication mode; the storage unit is a storage medium formed by storage spaces of a plurality of idle mobile devices, and each idle mobile device is used as a storage node of the storage unit; the user side is a mobile device used by the user. The system meets the requirement of the user on the storage space of the mobile phone, improves the utilization efficiency of the storage space of the idle mobile phone, and provides a system for efficiently managing files for the user.

Description

Private cloud file management system based on multiple mobile devices

Technical Field

The application relates to the technical field of file management systems of mobile devices, in particular to a private cloud file management system based on a plurality of mobile devices.

Background

Smartphones are frequently used in our daily lives, and users often use smartphones to store a large number of files, such as photos, electronic books, work documents, etc. There is an increasing demand for file storage by smartphones, where the storage capacity of a single phone may not be sufficient for file storage. The memory of the smart phone is increased to solve the storage requirement, however, the hardware cost of the smart phone is increased.

Because smartphones are updated faster, a large number of idle phones are generated, and the phones often have a certain storage space ROM. How to use the storage space of these idle mobile phones to solve the insufficient storage capacity of a single mobile phone for file storage is a technical problem to be solved.

Disclosure of Invention

The application aims to provide a private cloud file management system based on a plurality of mobile devices, which aims to solve the technical problem that the storage space of the existing idle mobile phone is not fully utilized. The preferred technical solutions of the technical solutions provided by the present application can produce a plurality of technical effects described below.

In order to achieve the above purpose, the present application provides the following technical solutions:

the application provides a private cloud file management system based on a plurality of mobile devices, which comprises a storage unit, a cloud service unit and a user side which are sequentially connected in a communication mode; the storage unit is a storage medium formed by storage spaces of a plurality of idle mobile devices, and each idle mobile device is used as a storage node of the storage unit; the user side is mobile equipment used by a user; the user side transmits the file selected to be uploaded by the user to the storage unit for storage through the cloud service unit according to the file storage strategy determined by the user; and browsing or downloading the files stored on the corresponding mobile equipment of the storage unit at any time and any place according to the mapping relation between the files and the real addresses provided by the cloud service unit.

Further, the cloud service unit comprises a signaling forwarding module, a data forwarding module, an API application service interface and a database; the database is communicatively coupled to the API application service interface.

Further, each storage node comprises a signaling processing module, a first data transmission module, a file storage module and an event reporting module; the signaling processing module is in communication connection with the first data transmission module, the file storage module and the event reporting module; the signaling forwarding module, the data forwarding module and the database are respectively in communication connection with the signaling processing module, the first data transmission module and the event reporting module.

Further, the user terminal comprises a signaling sending module, a second data transmission module and a file display module; the signaling sending module, the second data transmission module and the file display module are respectively in communication connection with the signaling forwarding module, the data forwarding module and the API application service interface.

Further, the user terminal further comprises a control background which is in communication connection with the signaling sending module, the second data transmission module and the file display module.

Further, the storage unit and the user terminal transmit data through point-to-point direct connection or forward data through the cloud service unit. The transport layer protocol employs a kcp data transport protocol.

Further, the storage unit, the cloud service unit and the user terminal perform data interaction through a signaling control protocol, and the forwarding of the signaling control protocol adopts an MQTT or a WebSocket server.

Further, the cloud service unit distributes a distinguishing identifier and a p2p transmission identifier for each user side and each storage node of the storage unit corresponding to the user side; and the cloud service unit forms a mapping relation for the file and the real address of the storage node according to the distinguishing identification and the p2p transmission identification.

Further, the method further comprises a step of browsing the files stored in the storage unit by the user through the user terminal, and the step comprises the following steps:

and the user terminal initiates a command code for acquiring a file list, initiates a command code for acquiring a handle index of a buffer file to the storage unit after waiting for the response of the storage unit, and loads the thumbnail from the storage unit after the response of the storage unit.

Further, the method also comprises a binding flow for guaranteeing the security of the private file of the user, and the method comprises the following steps:

s1, a forwarding server of the cloud service unit initiates a binding requirement to generate a public key;

s2, whether the public key is legal or not, if so, executing a step S3; otherwise, returning an error code;

s3, each storage node returns a token and stores a unique identity of a user corresponding to the token;

s4, the user side invokes a binding interface, reports and stores a token;

s5, the forwarding server of the cloud service unit sends out whether the binding is successful or not;

s6, the user side responds that the binding is successful, and the binding is finished.

By implementing one of the technical schemes, the application has the following advantages or beneficial effects:

according to the application, a large amount of storage space ROM of the idle mobile phone is connected with a plurality of devices in series in a network mode, and then is managed through the cloud database, so that a private cloud disk system with large capacity can be formed. Furthermore, a recycling idea is provided for the use of the idle mobile phone, the requirement of a user on the storage space of the mobile phone is met, the utilization efficiency of the storage space of the idle mobile phone is improved, and a system for efficiently managing files is provided for the user.

Drawings

For a clearer description of the technical solutions of embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art, in which:

FIG. 1 is a schematic diagram of a private cloud file management system based on a plurality of mobile devices according to an embodiment of the present application;

FIG. 2 is a more detailed schematic diagram of a private cloud file management system based on multiple mobile devices according to an embodiment of the present application;

FIG. 3 is a flow chart of a private cloud file management system file browsing based on multiple mobile devices according to an embodiment of the present application;

FIG. 4 is a flow chart of a private cloud file management system file upload based on a plurality of mobile devices according to an embodiment of the present application;

FIG. 5 is a private cloud file management system file download flowchart based on a plurality of mobile devices according to an embodiment of the present application;

FIG. 6 is a binding flow chart for securing private documents of a user according to an embodiment of the present application.

In the figure: 1. a storage unit; 11. a storage node; 111. a signaling processing module; 112. a first data transmission module; 113. a file storage module; 114. an event reporting module; 2. a cloud service unit; 21. a signaling forwarding module; 22. a data forwarding module; 23. an API application service interface; 24. a database; 3. a user terminal; 31. a signaling sending module; 32. a second data transmission module; 33. a file display module; 4. and controlling the background.

Detailed Description

For a better understanding of the objects, technical solutions and advantages of the present application, reference should be made to the accompanying drawings of the response to various exemplary embodiments which form a part hereof, and in which are described various exemplary embodiments which may be employed in practicing the present application. The same reference numbers in different drawings identify the same or similar elements unless expressly stated otherwise. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. It is to be understood that they are merely examples of processes, methods, apparatuses, etc. that are consistent with certain aspects of the present disclosure as detailed in the appended claims, other embodiments may be utilized, or structural and functional modifications may be made to the embodiments set forth herein without departing from the scope and spirit of the present disclosure.

In the description of the present application, it should be understood that the terms "center," "longitudinal," "transverse," and the like are used in an orientation or positional relationship based on that shown in the drawings, and are merely for convenience in describing the present application and to simplify the description, rather than to indicate or imply that the elements referred to must have a particular orientation, be constructed and operate in a particular orientation. The terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. The term "plurality" means two or more. The terms "connected," "coupled" and "connected" are to be construed broadly and may be, for example, fixedly connected, detachably connected, integrally connected, mechanically connected, electrically connected, communicatively connected, directly connected, indirectly connected via intermediaries, or may be in communication with each other between two elements or in an interaction relationship between the two elements. The term "and/or" includes any and all combinations of one or more of the associated listed items. The specific meaning of the above terms in the present application can be understood by those of ordinary skill in the art according to the specific circumstances.

In order to illustrate the technical solutions of the present application, the following description is made by specific embodiments, only the portions related to the embodiments of the present application are shown.

Embodiment one:

as shown in fig. 1, the application provides a private cloud file management system based on a plurality of mobile devices, which comprises a storage unit 1, a cloud service unit 2 and a user terminal 3 which are sequentially connected in a communication manner. The storage unit 1 is a storage medium formed by storage spaces of a plurality of idle mobile devices, and each idle mobile device is used as one storage node 11 of the storage unit 1; the user terminal 3 is a mobile device used by a user. Further, the user side 3 transmits the file selected to be uploaded by the user to the storage unit 1 for storage through the cloud service unit 2 according to the file storage strategy determined by the user; and browsing or downloading the files stored on the corresponding mobile equipment of the storage unit 1 at any time and any place according to the mapping relation between the files and the real addresses provided by the cloud service unit 2. In the application, the storage unit 1 has the functions of signaling processing, data uploading and downloading and file storage, and can also report events; the cloud service unit 2 is used as a bridge for connecting the entity storage unit 1 and the user terminal 3, mainly has the functions of a file database, communication signaling protocol forwarding and API interface (such as an API application service interface), and simultaneously can not directly provide data forwarding for the data transmission process of the user terminal 3 and the storage node 11; in addition, the user can maintain the corresponding relation of the files and the storage addresses through the cloud service unit 2; the user terminal 3 provides a mobile phone terminal application program for a file manager, and mainly provides operations such as uploading files, downloading files, browsing files and other deleting, moving, copying, renaming and the like for a user.

It should be noted that, the file storage policy is provided by the user side 3 (such as APP, mobile phone application program) so that the user can select which idle mobile device of the storage unit 1 to store the file to be stored preferentially, or uniformly store the file on each idle mobile device. The mobile device of the application is a mobile phone or a smart phone. It should be further noted that the file index database may be used to cache the node position where the file is located, so that the user can conveniently query at the user side.

According to the application, a large amount of storage space ROM of the idle mobile phone is connected with a plurality of devices in series in a network mode, and then is managed through the cloud database, so that a private cloud disk system with large capacity can be formed. Furthermore, a recycling idea is provided for the use of the idle mobile phone, the requirement of a user on the storage space of the mobile phone is met, the utilization efficiency of the storage space of the idle mobile phone is improved, and a system for efficiently managing files is provided for the user.

As shown in fig. 2, as an example, the cloud service unit 2 includes a signaling forwarding module 21, a data forwarding module 22, an API application service interface 23, and a database 24; the database 24 is communicatively connected to the API application service interface 23.

As an example, each storage node 11 includes a signaling processing module 111, a first data transmission module 112, a file storage module 113, and an event reporting module 114. The signaling processing module 111 is in communication connection with the first data transmission module 112, the file storage module 113 and the event reporting module 114; the signaling forwarding module 21, the data forwarding module 22 and the database 24 are respectively in communication connection with the signaling processing module 111, the first data transmission module 112 and the event reporting module 114. Specifically, when the signaling processing module 111 receives the operation command code forwarded by the signaling forwarding module 21 of the cloud service unit 2, if the operation command code is a storage user file, the first data transmission module 112 is started to receive the file forwarded by the data forwarding module 22 or receive the file directly transmitted by the second data transmission module 32 (as described below) of the user terminal 3, and the received file is written into the file storage module 113 under the control of the signaling processing module 111; the operation command code is a download user file, and the signaling processing module 111 extracts the response file from the file storage module 113, and forwards or directly sends the response file to the second data transmission module 32 of the user terminal 3 through the first data transmission module 112. After each operation command code is executed, an event is formed and reported to the database 24 of the cloud service unit 2, and data interaction is formed with the user terminal 3 through the API application service interface 23. Of course, the signaling forwarding module in the cloud service unit 2 may record the protocol without reporting the signaling forwarding module separately.

It should be noted that, the time reporting of the storage module may be reported through a signaling protocol module, or may be reported through a cloud API service. The signaling processing module is a control module for file data transmission.

As an example, the client 3 includes a signaling module 31, a second data transmission module 32, and a file presentation module 33; the signaling sending module 31, the second data transmission module 32 and the file displaying module 33 are respectively in communication connection with the signaling forwarding module 21, the data forwarding module 22 and the API application service interface 23. Further, the client 3 further includes a control background 4 communicatively connected to the signaling sending module 31, the second data transmission module 32, and the file presentation module 33. The control background 4 can control the user terminal 3 to upload the user files in the mobile phone to the storage unit 1, browse and download related files from the storage unit 1, and perform other operations such as deleting, moving, copying, renaming and the like on the files.

As an example, the storage unit 1 and the user terminal directly transmit data through point-to-point connection or forward data through the cloud service unit 2. The transport layer protocol employs a kcp data transport protocol. In this example, the data transmission layer uses udp+kcp (direct connection or forwarding) for data transmission, where udp is a transmission layer protocol, and kcp is analogous to tcp in that bandwidth is sacrificed to trade off transmission speed, that is, fast data transmission is achieved. The transport protocol packet format is as follows:

/**

*Header

*|1byte|1byte|2byte|4byte|4byte|4byte|4byte|

*|version|type|data-len|handle|seqNo|total packet|reserved|

*<p>

*<p>

*type:0undefine,1sync-1,2sync-ack-1,5fi le-segment-data

* data-len: file-data size, type=5, and the value is not 0

* handle: file handle index for distinguishing transmission files

* seqNo: file fragment sequence number, so a single file small MTU (1400) lnterger. Max (4G) =5600G is maximally supported

* total packet: total number of packets

* reserved field

*/

As an example, the storage unit 1, the cloud service unit 2, and the client 3 perform data interaction through a signaling control protocol, and the forwarding of the signaling control protocol adopts an MQTT or WebSocket server. Further, the categories of the signaling control protocol include file transmission, file operation and event reporting.

It should be noted that, interaction such as data transmission and control needs a set of signaling control protocol as assistance, and the control protocol is received by a message communication server, and may be forwarded by adopting the MQTT or WebSocket service. The signaling protocol class includes file transfer, file manipulation, event reporting, etc. The format content of the signaling control protocol is shown in the following tables 1-2:

table 1 format of signaling control protocol

key	value	desc
			version	int	Protocol version
type	int	Protocol type
			zction	int	Command code
uid	string	Message source p2pid
			info	object	Additional messages

Table 2 type definition in signaling control protocol

value	desc
		1	Downlink execution operation message
2	Uplink operation reply message
		3	Uplink event notification message
4	p2p information interaction command

As an example, the cloud service unit 2 further allocates a distinguishing identifier and a p2p transmission identifier to each user end 3 and each storage node 11 of the corresponding storage unit 1; and the cloud service unit forms a mapping relation according to the distinguishing identification and the p2p transmission identification as the file and the real address of the storage node. And P2pId (shown in table 2) is allocated to each user terminal 3 and the corresponding file storage mobile phone node according to the rule and is used as a distinguishing identifier between the nodes and an identifier of P2P transmission. Specifically, the storage node 11 and the user terminal 3 can obtain the identification through the algorithm rule operation of the cloud service unit 2 through the equipment identification (such as a serial number, deviceId, etc.) of the mobile phone. The user terminal 3 introduces an account system, and can also use telephone numbers and the like to generate the unique p2p identification. It should be noted that the allocated p2p identifier must be unique, so a cloud service unit is required for allocation.

After the identifier is established, the cloud service unit 2 forms a mapping relationship for the file and the real address of the storage node 11 according to each p2pId, and through the mapping relationship, the user can intuitively see which storage node 11 the file is stored in, what the files are, which storable nodes exist, the result of each event, and the like at the file display module 33 of the user side 3.

The command code action in table 1 is used to distinguish between different operations, including: browsing files, uploading files, and downloading files. The specific flow is as follows:

as shown in fig. 3, the steps of browsing the files stored in the storage unit 1 by the user terminal 3 are as follows:

the user terminal 3 initiates a command code for acquiring a file list, initiates a command code for acquiring a handle index of a buffer file to the storage unit 1 after waiting for the response of the storage unit 1, and loads the thumbnail from the storage unit 1 after the response of the storage unit 1. Specifically, the user sends a command code (GetFileList) for obtaining a file list to the signaling forwarding module 21 (e.g., MQTT) of the cloud service unit 2 through the signaling sending module 31 of the user terminal 3, and forwards the command code to the signaling processing module 111 of each storage node 11 through the signaling forwarding module 21 of the cloud service unit 2; the user 3 receives the acquired file list response command codes of the signaling processing module 111 of each storage node 11 through the signaling forwarding module 21 of the cloud service unit 2 (GetFileList response);

the user side 3 sends a command code getThumb (n-handleli) for loading the file list thumbnail from the buffer system to each storage node 11 through the cloud service unit 2, and receives each storage node 11 response command code getThumb (n-handleli) response forwarded by the cloud service unit 2;

the user terminal 3 loads the thumbnail from the file storage module 113 of each storage node 11 through the data forwarding module 22 of the cloud service unit 2 until the loading is completed.

As shown in fig. 4, the step of uploading the file to the storage unit 1 by the user is:

the user terminal 3 initiates a file uploading command code to the storage unit 1 through the cloud service unit 2 and waits for the response of the storage unit 1; after the response, the client 3 starts uploading to the storage node 11 corresponding to the storage unit 1 through the cloud service unit 2 or directly, and after the uploading is completed, the uploading event of the storage unit 1 is received through the cloud service unit 2. It should be noted that, when uploading, the user needs to determine the file storage policy, specifically according to the user's own choice.

As shown in fig. 5, the steps of the user downloading a file from the storage unit 1 are:

the user terminal 3 initiates a file downloading command code to the storage unit 1 through the cloud service unit 2 and waits for the response of the storage unit 1; after the response, the user terminal 3 starts to download the corresponding file through the cloud service unit 2 or directly from the storage node 11 corresponding to the storage unit 1, and after the verification is completed, the download event is reported to the storage unit 1 through the cloud service unit 2; if the downloading is not completed, the cloud service unit 2 reports the downloading event to the storage unit 1 after the downloading is continued to be completed.

It should be noted that the above-mentioned file browsing, uploading and downloading involve communication between the signaling modules of the command code, transmission by the data modules involved in data transmission, and communication between the event reporting module 114, the database 24 module and the file display module 33 involved in the event.

As shown in fig. 6, for the security of the private file, the user end 3 that can first enter the private storage system must go through a binding procedure, and the binding procedure needs to use an authentication algorithm. As an example, the present application further includes a binding process for guaranteeing security of the private document of the user, including the steps of:

s1, a forwarding server (such as MQTT) of a cloud service unit 2 initiates a binding requirement to generate a public key;

s2, whether the public key is legal or not, if so, executing a step S3; otherwise, an error code is returned. If not, the connection with the storage unit is refused for the user;

s3, each storage node 11 returns a token and stores a unique identity of a user corresponding to the token;

s4, the user terminal 3 calls a binding interface, reports and stores the token; here, the control background 4 described above is reported. It should be noted that, the binding interface is called to bind the relationship between the storage node and the user, i.e. confirm the attribution relationship;

s5, a forwarding server of the cloud service unit 2 sends out whether binding is successful or not;

s6, the user side 3 responds to successful binding, and the binding is finished.

The token is a token, is a string of character strings generated by the server, is used as an identifier of the request by the user side 3, and comprises a unique identity identifier uid of the user, a timestamp time of the current time and a signature sign.

It should be noted that the system must also be rights controlled for security. The rights control first classifies users, such as administrator, general user, temporary user (disposable user), and assigns different rights to different user classes. These rights include, but are not limited to, file viewing, file downloading, file uploading, file transferring, sharing users, file deletion, file modification, file movement, and the like.

In summary, in this embodiment, a large amount of storage space ROM of the idle mobile phone connects a plurality of devices in series through a network, and then is managed through the cloud database, so as to form a private cloud disk system with large capacity. And the unused storage space of the idle mobile phone is reused, so that the requirement of a user on the storage space of the mobile phone is met, and the utilization efficiency of the storage space of the idle mobile phone is improved. The embodiment also provides a system for efficiently managing files for users.

The foregoing is only illustrative of the preferred embodiments of the application, and it will be appreciated by those skilled in the art that various changes in the features and embodiments may be made and equivalents may be substituted without departing from the spirit and scope of the application. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the application without departing from the essential scope thereof. Therefore, it is intended that the application not be limited to the particular embodiment disclosed, but that the application will include all embodiments falling within the scope of the appended claims.

Claims (10)

1. The private cloud file management system based on the plurality of mobile devices is characterized by comprising a storage unit, a cloud service unit and a user side which are sequentially connected in a communication mode; the storage unit is a storage medium formed by storage spaces of a plurality of idle mobile devices, and each idle mobile device is used as a storage node of the storage unit; the user side is mobile equipment used by a user;

the user side transmits the file selected to be uploaded by the user to the storage unit for storage through the cloud service unit according to the file storage strategy determined by the user; and browsing or downloading the files stored on the corresponding mobile equipment of the storage unit at any time and any place according to the mapping relation between the files and the real addresses provided by the cloud service unit.

2. The private cloud file management system based on a plurality of mobile devices of claim 1, wherein said cloud service unit comprises a signaling forwarding module, a data forwarding module, an API application service interface and a database; the database is communicatively coupled to the API application service interface.

3. The private cloud file management system based on a plurality of mobile devices according to claim 2, wherein each of said storage nodes comprises a signaling processing module, a first data transmission module, a file storage module and an event reporting module; the signaling processing module is in communication connection with the first data transmission module, the file storage module and the event reporting module;

the signaling forwarding module, the data forwarding module and the database are respectively in communication connection with the signaling processing module, the first data transmission module and the event reporting module.

4. The private cloud file management system based on a plurality of mobile devices according to claim 2, wherein the user side comprises a signaling sending module, a second data transmission module and a file presentation module; the signaling sending module, the second data transmission module and the file display module are respectively in communication connection with the signaling forwarding module, the data forwarding module and the API application service interface.

5. The private cloud file management system of claim 4, wherein said client further comprises a control background communicatively coupled to said signaling module, said second data transmission module, and said file presentation module.

6. The private cloud file management system based on a plurality of mobile devices according to claim 1, wherein the storage unit and the user terminal directly transmit data through point-to-point connection or forward data through the cloud service unit; the transport layer protocol employs a kcp data transport protocol.

7. The private cloud file management system based on a plurality of mobile devices according to claim 1, wherein the storage unit, the cloud service unit and the user side perform data interaction through a signaling control protocol, and the forwarding of the signaling control protocol adopts an MQTT or WebSocket server.

8. The private cloud file management system based on a plurality of mobile devices according to claim 1, further comprising the cloud service unit distributing a distinguishing identifier and a p2p transmission identifier for each user side and each storage node of the storage unit corresponding to the user side; and the cloud service unit forms a mapping relation for the file and the real address of the storage node according to the distinguishing identification and the p2p transmission identification.

9. The private cloud file management system of claim 1, further comprising a step of a user browsing files stored in said storage unit via said user side, comprising:

and the user terminal initiates a command code for acquiring a file list, initiates a command code for acquiring a handle index of a buffer file to the storage unit after waiting for the response of the storage unit, and loads the thumbnail from the storage unit after the response of the storage unit.

10. The private cloud file management system of claim 9, further comprising a binding process for securing a private file of a user, comprising the steps of:

s1, a forwarding server of the cloud service unit initiates a binding requirement to generate a public key;

s2, whether the public key is legal or not, if so, executing a step S3; otherwise, returning an error code;

s3, each storage node returns a token and stores a unique identity of a user corresponding to the token;

s4, the user side invokes a binding interface, reports and stores a token;

s5, the forwarding server of the cloud service unit sends out whether the binding is successful or not;

s6, the user side responds that the binding is successful, and the binding is finished.