File synchronization method, electronic device and storage medium
By using the file synchronization method to synchronize resource files between the master server node and the slave server node in the distributed file storage system, the problem of out-of-synchronization after resource files is solved, synchronization efficiency is improved and resource utilization is optimized.
Patent Information
- Application Number
- CN202410258364.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-03-07
- Publication Date
- 2024-12-10
- Estimated Expiration
- 2044-03-07
AI Technical Summary
In distributed file storage mode, resource files are prone to be out of synchronization between server nodes after resource files are updated, resulting in inefficiency.
Provide a file synchronization method, by determining the list of files to be synchronized on the master server node, sending resource synchronization prompt messages to the target slave server node according to preset synchronization rules, ensuring that resource files are synchronized between the master server node and the slave server node. , use preset filtering and sorting rules to select the appropriate slave node for synchronization, and monitor the modification and call of resource files for synchronization management.
It effectively solves the problem of low efficiency in resource file synchronization, ensures timely synchronization of resource files in distributed file storage systems between different server nodes, and avoids bandwidth competition and resource waste during synchronization.
Smart Images

Figure CN118233475B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of Internet technology, and in particular to a file synchronization method, an electronic device and a storage medium. Background Art
[0002] The file storage methods on the server side are mainly divided into centralized file storage and distributed file storage. Among them, centralized file storage mainly stores resource files in a certain server, so as to provide services to the client through the server, but this method is prone to single point failure. Relatively speaking, distributed file storage uses multiple server nodes to store resource files, so the possibility of single point failure is lower, so the server currently mainly uses distributed file storage to store resource files.
[0003] However, for the distributed file storage method, since the resource files are stored through multiple server nodes, if the resource files are updated, it is easy for the resource files between the server nodes to be out of sync. Summary of the invention
[0004] The purpose of the embodiments of the present application is to provide a file processing method, device, electronic device and storage medium based on a knowledge base, so as to solve the problem of low efficiency in modifying files stored in a knowledge base in the prior art.
[0005] A first aspect of an embodiment of the present application provides a file synchronization method, which is used for a master server node, and includes:
[0006] Determine whether there are resource files to be synchronized in the list of files to be synchronized;
[0007] If so, a resource synchronization prompt message is sent to the target slave server node according to a preset synchronization rule, so that the target slave server node obtains the resource file to be synchronized from the master server node according to the resource synchronization prompt message.
[0008] Preferably, the method further comprises:
[0009] Monitoring whether there is a resource file that meets a synchronization condition, wherein the synchronization condition specifically includes that the resource file is a modified resource file or the resource file is a newly uploaded resource file;
[0010] If so, the resource file is added to the list of files to be synchronized.
[0011] Preferably, according to a preset synchronization rule, sending a resource synchronization prompt message to the target slave server node specifically includes:
[0012] According to a preset screening rule, at least one target slave server node is screened out from a plurality of slave server nodes;
[0013] Sort each target slave server node according to the preset sorting rules;
[0014] The resource synchronization prompt message is sent to each sorted target slave server node in turn.
[0015] Preferably, at least one target slave server node is selected from a plurality of slave server nodes according to a preset screening rule, specifically including:
[0016] Determine the demand score of each slave server node for the resource file to be synchronized according to the importance level of each slave server node and the number of times the historical version of the resource file to be synchronized in each slave server node has been called;
[0017] At least one target slave server node is selected based on the demand score of each slave server node.
[0018] Preferably, the method further comprises:
[0019] Obtaining a notification message sent by a slave server node when the historical version of the resource file to be synchronized is called, indicating that the historical version of the resource file to be synchronized is called;
[0020] The number of times the historical version of the resource file to be synchronized in the slave server node is called is updated according to the notification message.
[0021] A second aspect of an embodiment of the present application provides a file synchronization method, the method being used for a target slave server node, the method comprising:
[0022] Get the resource synchronization prompt message sent by the master server node;
[0023] According to the resource synchronization prompt message, the resource file to be synchronized is obtained from the main server node.
[0024] Preferably, obtaining the resource file to be synchronized from the master server node according to the resource synchronization prompt message specifically includes:
[0025] Parsing the resource synchronization prompt message to obtain the file name and synchronization start time of the resource file to be synchronized;
[0026] At the synchronization start time, the resource file to be synchronized is obtained from the main server node according to the file name.
[0027] Preferably, after obtaining the resource file to be synchronized from the master server node according to the resource synchronization prompt message, the method further includes:
[0028] In the case where the resource file to be synchronized is called, a notification message of the calling of the resource file to be synchronized is sent to the main server node.
[0029] A third aspect of the embodiments of the present application provides an electronic device, including:
[0030] Memory for storing computer programs;
[0031] A processor is used to execute any one of the methods described in the method embodiments of the present application.
[0032] A fourth aspect of an embodiment of the present application provides a storage medium, including: a program, which, when executed on an electronic device, enables the electronic device to execute any one of the methods in the method embodiments of the present application.
[0033] The file synchronization method provided by the embodiment of the present application includes first determining whether there are resource files to be synchronized recorded in the list of files to be synchronized, and if so, sending a resource synchronization prompt message to the target slave server node according to the preset synchronization rule, so that the target slave server node can obtain the resource file to be synchronized from the master server node according to the resource synchronization prompt message. Therefore, the method can synchronize the resource files in the master server node to the slave server node, thereby solving the problems in the prior art. BRIEF DESCRIPTION OF THE DRAWINGS
[0034] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.
[0035] Figure 1 A schematic diagram of the structure of an electronic device provided in one embodiment of the present application.
[0036] Figure 2 A schematic diagram of the specific structure of a distributed file storage system provided in one embodiment of the present application;
[0037] Figure 3 A schematic diagram of a specific process of a file synchronization method provided in an embodiment of the present application;
[0038] Figure 4 A specific flowchart of a file synchronization method provided in another embodiment of the present application;
[0039] Figure 5 A schematic diagram of the specific structure of a file synchronization device provided in an embodiment of the present application;
[0040] Figure 6 A specific structural diagram of a file synchronization device provided in accordance with another embodiment of the present application. DETAILED DESCRIPTION
[0041] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings in the embodiments of the present application. In the description of the present application, terms such as "first", "second", "third", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance or sequence.
[0042] As mentioned above, for the distributed file storage method, since resource files are stored through multiple server nodes, if the resource files are updated, it is easy for the resource files between the server nodes to be out of sync. For example, if a user updates the resource files of a server node, the other server nodes usually still do not have the updated resource files, which easily leads to the resource files between the server nodes being out of sync.
[0043] In view of this, the embodiments of the present application provide a file synchronization method, device, electronic device and storage medium, which can be used to solve the technical problem. Figure 1 FIG. 1 is a schematic diagram of a specific structure of an electronic device provided in this embodiment. The electronic device 1 includes: at least one processor 11 and a memory 12. Figure 1 A processor is used as an example. The processor 11 and the memory 12 may be connected via a bus 10, and the memory 12 stores instructions that can be executed by the processor 11, and the instructions are executed by the processor 11, so that the electronic device 1 can execute all or part of the process of the method in the embodiment of the present application.
[0044] The electronic device 1 can be used as a master server node in a distributed file storage system, or as a slave server node in a distributed file storage system. Figure 2 The figure shows a specific structural diagram of the distributed file storage system provided by an embodiment of the present application. The distributed file storage system includes a master server node 21 and multiple slave server nodes 22. Each slave server node 22 is connected to the master server node 21 respectively, so as to be able to communicate with the master server node 21.
[0045] like Figure 3 The figure shows a specific flow chart of the file synchronization method provided by the embodiment of the present application. The method can be performed by Figure 1 The electronic device 1 shown is used as Figure 2The method is performed by a master server node in the distributed file storage system shown in the figure, and comprises the following steps:
[0046] Step S31: Determine whether there are resource files to be synchronized recorded in the list of files to be synchronized. If so, execute step S32.
[0047] The to-be-synchronized file list is used to record the to-be-synchronized resource files. For example, when a resource file needs to be synchronized to a slave server node, the resource file can be recorded in the to-be-synchronized file list as a to-be-synchronized resource file. In this way, the to-be-synchronized file list can be queried to determine whether the to-be-synchronized resource file is recorded in the to-be-synchronized file list. For example, if a resource file is recorded in the to-be-synchronized file list, the resource file is the to-be-synchronized resource file. On the contrary, if the to-be-synchronized file list does not record a resource file, it means that the to-be-synchronized file list does not record a resource file to be synchronized.
[0048] Among them, for the resource files in the main server, when the resource files are modified, it is usually necessary to synchronize the modified resource files to the slave server nodes. Of course, if the main server node receives a new resource file uploaded by the user, it is usually necessary to synchronize the newly uploaded resource files to the slave server nodes. Therefore, the method can also include monitoring whether there are resource files that meet the synchronization conditions, wherein the synchronization conditions specifically include that the resource file is a modified resource file or that the resource file is a newly uploaded resource file. If so, it means that the resource file is a modified resource file or a newly uploaded resource file, and therefore meets the synchronization conditions, then the resource file can be added to the list of files to be synchronized, so that it can be synchronized by the method provided in the embodiment of the present application.
[0049] In practical applications, resource files can usually be synchronized periodically, so step S31 needs to be executed periodically to periodically determine whether there are resource files to be synchronized recorded in the list of files to be synchronized, wherein the period can be 1 hour, half an hour, 24 hours or 1 week, etc.
[0050] Step S32: Send a resource synchronization prompt message to the target slave server node according to the preset synchronization rule.
[0051] By sending a resource synchronization prompt message to the target slave server node, the target slave server node can obtain the resource file to be synchronized from the master server node according to the resource synchronization prompt message.
[0052] For example, when there are resource files to be synchronized recorded in the list of files to be synchronized, a resource synchronization prompt message can be sent to the target slave server node according to the preset synchronization rules, so that after receiving the resource synchronization prompt message, the target slave server node can obtain the resource files to be synchronized from the master server node according to the resource synchronization prompt message.
[0053] In actual applications, in order to enable the target slave server node to obtain the resource file to be synchronized from the master server node according to the resource synchronization prompt message, the resource synchronization prompt message usually needs to carry the file name of the resource file to be synchronized; in addition, considering that the master server node is connected to multiple slave server nodes, there may be multiple slave server nodes that need to obtain the resource file to be synchronized. At this time, in order to avoid the situation where multiple slave server nodes compete for bandwidth, these different slave server nodes can usually be controlled to download the resource file to be synchronized at different times. Therefore, the synchronization prompt message can usually also carry the synchronization start time, so that the target slave server node can download the resource file to be synchronized at the synchronization start time.
[0054] Therefore, after receiving the synchronization prompt message, the target slave server node can parse the file name of the resource file to be synchronized and the synchronization start time from the synchronization prompt message, and then obtain the resource file to be synchronized from the target slave server node according to the file name at the synchronization start time.
[0055] The file synchronization method provided by the embodiment of the present application includes first determining whether there are resource files to be synchronized recorded in the list of files to be synchronized, and if so, sending a resource synchronization prompt message to the target slave server node according to the preset synchronization rule, so that the target slave server node can obtain the resource file to be synchronized from the master server node according to the resource synchronization prompt message. Therefore, the method can synchronize the resource files in the master server node to the slave server node, thereby solving the problems in the prior art.
[0056] For example, if a resource file in the master server node is updated, the resource file can be added to the list of files to be synchronized as a resource file to be synchronized, and then synchronized to the target slave server node through the method provided in the embodiment of the present application.
[0057] It should be further explained that, since the master server node is usually connected to multiple slave server nodes, only some of these slave server nodes may need to synchronize the resource file to be synchronized, and in order to avoid competition for bandwidth resources, these slave server nodes need to sort the resource synchronization time. Therefore, in the above step S32, according to the preset synchronization rule, a resource synchronization prompt message is sent to the target slave server node. On the one hand, it is necessary to filter out the target slave server node from multiple slave server nodes, and on the other hand, it is also necessary to sort the order of sending the resource synchronization prompt message. Therefore, the preset synchronization rule may include a preset filtering rule and a preset sorting rule, wherein at least one target slave server node can be filtered out according to the preset filtering rule, and these target slave server nodes can be sorted according to the preset sorting rule.
[0058] Therefore, the specific implementation method of step S32 can be to first filter out at least one target slave server node from multiple slave server nodes according to a preset filtering rule, then sort each target slave server node according to a preset sorting rule, and then send the resource synchronization prompt message to each sorted target slave server node in turn.
[0059] Among them, the specific implementation method of filtering out at least one target slave server node from multiple slave server nodes according to preset filtering rules can be to determine the demand score of each slave server node for the resource file to be synchronized according to the importance level of each slave server node and the number of times the historical version of the resource file to be synchronized in each slave server node is called, and then filter out at least one target slave server node according to the demand score of each slave server node.
[0060] Among them, for determining the demand score of each slave server node for the resource file to be synchronized according to the importance level of each slave server node and the number of times the historical version of the resource file to be synchronized in each slave server node is called, the specific implementation method may be, first obtaining the importance level of each slave server node, which reflects the importance of the corresponding slave server node, and then obtaining the importance score corresponding to the importance level by querying the importance level scoring rule table, thereby obtaining the importance score of each slave server node.
[0061] On the other hand, after obtaining the number of times the historical version of the resource file to be synchronized is called in each slave server node, the number of times each slave server node is called can be further calculated, and the proportion of the total number of times called. For example, the number of times each slave server node is called can be summed to obtain the total number of times called, and then the number of times each slave server node is called can be calculated respectively, and the proportion of the total number of times called. In addition, after obtaining the number of times each slave server node is called and the proportion of the total number of times called, the proportion can be multiplied by the magnification factor to obtain the number of times called score, wherein the magnification factor can be a piecewise function of the proportion, such as, when the proportion is in the interval of [X1, X2), the magnification factor can be 10, when the proportion is in the interval of [X2, X3), the magnification factor can be 15, when the proportion is in the interval of [X3, X4], the magnification factor can be 20, wherein X1, X2, X3 and X4 are constants greater than 0 and less than 1, respectively, so that the higher the proportion, the greater the corresponding magnification factor.
[0062] In this way, after obtaining the importance score of each slave server node and the score of the number of calls of the historical version of the resource file to be synchronized in each slave server node in the above manner, the demand score of each slave server node can be calculated by the following formula 1:
[0063] P=a*M+b*NFormula 1
[0064] Among them, a and b are weights respectively; M is the importance score of the slave server node; N is the number of times the historical version of the resource file to be synchronized is called in the slave server node.
[0065] After obtaining the demand scores of each slave server node, the slave server node with the highest demand score can be directly used as the target slave server node, or the nodes can be arranged in descending order according to the demand scores, and then the three or five slave server nodes with the largest demand scores can be used as the target slave server nodes. Of course, a threshold can also be set, and the slave server nodes with demand scores greater than the threshold can be used as the target slave server nodes.
[0066] For the resource files to be synchronized, the master server node and each slave server node may store the historical version of the resource files to be synchronized. The historical version of the resource files to be synchronized is often called by the client and the slave server node itself, and the number of times the historical version of the resource files to be synchronized is called can reflect the demand of the slave server node for the historical version of the resource files to be synchronized. For example, the higher the number of calls, the greater the demand, and conversely, the lower the number of calls, the smaller the demand.
[0067] In actual applications, the master server node can obtain the notification message sent by the slave server node when the historical version of the resource file to be synchronized is called, and then update the number of times the historical version of the resource file to be synchronized in the slave server node is called according to the notification message. For example, in a slave server node, when the historical version of the resource file to be synchronized is called, the slave server node will send a notification message to the master server node that the historical version of the resource file to be synchronized is called, thereby notifying the master server node that the historical version of the resource file to be synchronized is called, so that the master server node will update the number of times the historical version of the resource file to be synchronized in the slave server node is called according to the notification message.
[0068] Based on the same inventive concept as the above-mentioned file synchronization method, Figure 4 As shown, the embodiment of the present application also provides a file synchronization method, which can be Figure 1 The electronic device 1 shown is used as Figure 2 The method is executed from a server node in the distributed file storage system shown in the figure, and comprises the following steps:
[0069] Step S41: Obtain a resource synchronization prompt message sent by the main server node.
[0070] Since the target slave server node is connected to the master server node, in step S41, the target slave server node can obtain the resource synchronization prompt message sent by the master server node.
[0071] Step S42: According to the resource synchronization prompt message, the resource file to be synchronized is obtained from the main server node.
[0072] After receiving the resource synchronization prompt message, the target slave server node can obtain the resource file to be synchronized from the master server node according to the resource synchronization prompt message. Specifically, the resource synchronization prompt message can be parsed first to obtain the file name and synchronization start time of the resource file to be synchronized, and then at the synchronization start time, the resource file to be synchronized can be obtained from the master server node according to the file name.
[0073] In addition, after executing the above step S42, the method may further include: when the resource file to be synchronized is called, the target slave server node may also send a notification message that the resource file to be synchronized is called to the master server node.
[0074] Of course, in the case where the historical version of the resource file to be synchronized is called, the target slave server node may also send a notification message to the master server node that the historical version of the resource file to be synchronized is called.
[0075] In addition, after the target slave server node obtains the resource file to be synchronized from the master server node, it can also send a synchronization completion receipt to the master server node, so that the master server can know from the receipt that the target slave server has completed the synchronization of the resource file to be synchronized.
[0076] It should be noted that, during the process of synchronizing the resource files to be synchronized, the target slave server node can also set up a synchronization monitoring page on the master server node, and then display parameters such as the file size of the resource files to be synchronized, the proportion of synchronized resources, the synchronization start time, and the synchronization duration on the synchronization monitoring page, so as to monitor the synchronization process.
[0077] Because of the Figure 4 The method shown is similar to Figure 3 The method shown is based on the same inventive concept, and therefore can also solve the problems in the prior art, which will not be described in detail here.
[0078] Based on the same inventive concept as the file synchronization method provided in the embodiment of the present application, the embodiment of the present application also provides a file synchronization device. If there is any unclear point, please refer to the corresponding content of the method embodiment. Figure 5 FIG. 5 is a schematic diagram of a specific structure of the device 50. The device 50 can be applied to a main server node. The device 50 includes a determining unit 501 and a sending unit 502, wherein:
[0079] A determination unit 501 is used to determine whether a resource file to be synchronized is recorded in the list of files to be synchronized;
[0080] The sending unit 502 is used to send a resource synchronization prompt message to the target slave server node according to a preset synchronization rule when it is determined that the list of files to be synchronized records resource files to be synchronized, so that the target slave server node obtains the resource files to be synchronized from the master server node according to the resource synchronization prompt message.
[0081] The device 50 provided in the embodiment of the present application is adopted. Since the device 50 adopts the same inventive concept as the method provided in the embodiment of the present application, on the premise that the method can solve the technical problem, the device 50 can also solve the technical problem, which will not be repeated here.
[0082] The device 50 may also include a monitoring adding unit for monitoring whether there are resource files that meet the synchronization conditions, wherein the synchronization conditions specifically include that the resource file is a modified resource file or the resource file is a newly uploaded resource file; if so, the resource file is added to the list of files to be synchronized.
[0083] Among them, sending a resource synchronization prompt message to a target slave server node according to a preset synchronization rule may specifically include:
[0084] According to a preset screening rule, at least one target slave server node is screened out from a plurality of slave server nodes;
[0085] Sort each target slave server node according to the preset sorting rules;
[0086] The resource synchronization prompt message is sent to each sorted target slave server node in turn.
[0087] The step of selecting at least one target slave server node from a plurality of slave server nodes according to a preset screening rule may specifically include:
[0088] Determine the demand score of each slave server node for the resource file to be synchronized according to the importance level of each slave server node and the number of times the historical version of the resource file to be synchronized in each slave server node has been called;
[0089] At least one target slave server node is selected based on the demand score of each slave server node.
[0090] The device 50 may also include a call count recording unit, which is used to obtain a notification message sent by the slave server node when the historical version of the resource file to be synchronized is called; and update the call count of the historical version of the resource file to be synchronized in the slave server node according to the notification message.
[0091] Based on the same inventive concept as the file synchronization method provided in the embodiment of the present application, the embodiment of the present application also provides a file synchronization device. If there is any unclear point, please refer to the corresponding content of the method embodiment. Figure 6 FIG. 6 is a schematic diagram of a specific structure of the device 60. The device 60 can be applied to a slave server node. The device 60 includes a prompt message acquisition unit 601 and a synchronization unit 602, wherein:
[0092] The prompt message acquisition unit 601 is used to acquire the resource synchronization prompt message sent by the main server node;
[0093] The synchronization unit 602 is used to obtain the resource file to be synchronized from the main server node according to the resource synchronization prompt message.
[0094] Since the device 60 adopts the same inventive concept as the method provided in the embodiment of the present application, it can also solve the problems in the prior art, which will not be described in detail here.
[0095] Wherein, obtaining the resource file to be synchronized from the master server node according to the resource synchronization prompt message may specifically include:
[0096] Parsing the resource synchronization prompt message to obtain the file name and synchronization start time of the resource file to be synchronized;
[0097] At the synchronization start time, the resource file to be synchronized is obtained from the main server node according to the file name.
[0098] Among them, the device 60 can also include a notification message sending unit, which is used to send a notification message to the main server node that the resource file to be synchronized is called after obtaining the resource file to be synchronized from the main server node according to the resource synchronization prompt message, when the resource file to be synchronized is called.
[0099] The embodiment of the present invention further provides a storage medium, including: a program, which, when running on an electronic device, enables the electronic device to execute all or part of the process of the method in the above embodiment. The storage medium may be a disk, an optical disk, a read-only memory (ROM), a random access memory (RAM), a flash memory, a hard disk (HDD) or a solid-state drive (SSD). The storage medium may also include a combination of the above types of memories.
[0100] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.
Claims
1. A file synchronization method, characterized in that: The method is used for a master server node, and the method comprises: Determine whether there are resource files to be synchronized in the list of files to be synchronized; If yes, sending a resource synchronization prompt message to the target slave server node according to a preset synchronization rule, so that the target slave server node obtains the resource file to be synchronized from the master server node according to the resource synchronization prompt message; Among them, according to the preset synchronization rules, sending a resource synchronization prompt message to the target slave server node specifically includes: According to a preset screening rule, at least one target slave server node is screened out from a plurality of slave server nodes; Sort each target slave server node according to the preset sorting rules; Sending the resource synchronization prompt message to each sorted target slave server node in turn; Among them, according to the preset screening rule, screening out at least one target slave server node from the plurality of slave server nodes specifically includes: Determine the demand score of each slave server node for the resource file to be synchronized according to the importance level of each slave server node and the number of times the historical version of the resource file to be synchronized in each slave server node has been called; According to the demand score of each slave server node, at least one target slave server node is selected; According to the importance level of each slave server node and the number of times the historical version of the resource file to be synchronized in each slave server node is called, the demand score of each slave server node for the resource file to be synchronized is determined, specifically including: Get the importance level of each slave server node; By querying the importance level scoring rule table, the importance scores corresponding to the importance levels of each slave server node are obtained; Calculate the number of calls for each slave server node and its proportion in the total number of calls; The proportions are multiplied by the magnification coefficients to obtain the call count scores of the historical versions of the resource files to be synchronized in each slave server node; The requirement score of each slave server node is calculated using the following formula: P = a*M+b*N; Among them, a and b are weights respectively; M is the importance score of the slave server node; N is the number of times the historical version of the resource file to be synchronized is called in the slave server node.
2. The method according to claim 1, characterized in that The method further comprises: Monitoring whether there is a resource file that meets a synchronization condition, wherein the synchronization condition specifically includes that the resource file is a modified resource file or the resource file is a newly uploaded resource file; If so, the resource file is added to the list of files to be synchronized.
3. The method according to claim 1, characterized in that The method further comprises: Obtaining a notification message sent by a slave server node when the historical version of the resource file to be synchronized is called, indicating that the historical version of the resource file to be synchronized is called; The number of times the historical version of the resource file to be synchronized in the slave server node is called is updated according to the notification message.
4. An electronic device, characterized in that: include: Memory for storing computer programs; A processor, configured to execute the method according to any one of claims 1 to 3.
5. A storage medium, characterized in that: The invention comprises: a program, which, when running on an electronic device, enables the electronic device to execute the method as claimed in any one of claims 1 to 3.
