System and method for rapid modification distribution of data

Abstract

The application relates to a data quick modification and distribution system in the field of old-age data processing, which comprises a function library, a data extractor and a scene library; the data extractor comprises an operation interface, the operation interface comprises application scenes and function modules, a plurality of scene systems are pre-stored in the scene library, a plurality of function systems are pre-stored in the function library, the application scenes are matched with the addresses of the scene systems, the function modules are matched with the addresses of the function systems, a plurality of the function modules and a plurality of the application scenes form a matrix in the operation interface, and a calling control is arranged at the intersection of the matrix; the calling control grabs the function system corresponding to the selected function module from the function library; after the function system is added to the application scenes in the horizontal row, all the function systems are integrated into the scene system to form the application scenes, so that the data distribution is completed, and the system is used in an old-age management system with many nodes, so that the data distribution efficiency is improved.

Description

Technical Field

[0001] This invention belongs to the field of elderly care data processing, and in particular relates to the rapid modification and distribution of data. Background Technology

[0002] In recent years, with the rapid development of high technologies such as the Internet, the Internet of Things, big data, cloud computing, and intelligent devices, and their widespread application in the field of elderly care, smart elderly care has gradually entered the public eye and become an important policy choice and development trend for solving the challenges of elderly care in China. As an innovative practice of smart elderly care services in my country, smart elderly care represents an upgrade to the traditional methods of elderly care service delivery.

[0003] To address the vast supply and demand of elderly care services in China and to organically integrate various elderly care service methods and functions, the applicant has established a smart elderly care system connecting regulatory departments, service institutions, service recipients, and service platforms. Due to the large number of events and service recipients managed, the system needs to distribute tasks to service points for regional solutions. However, the system connects to numerous service points with diverse needs. For example, regulatory departments require both data on service recipients and the processes executed by service institutions. Service institutions, as centralized platforms for service providers, handle a significant amount of service data and event processes. The service platform, in turn, needs to process large amounts of data and make corresponding decisions based on data analysis patterns. For instance, given the large number of users and their needs, if modifications and reconfigurations are required for a particular user group, the current approach is to suspend user functionality until an update is completed. Furthermore, the update method involves updating the data one by one, forcing users to download new software and wait for extended periods. Summary of the Invention

[0004] The purpose of this invention is to solve the problem of low efficiency in data updates on current elderly care service platforms. Therefore, it provides a system for rapid data modification and distribution.

[0005] The present invention provides a data rapid modification and distribution system, comprising a function library, a data extractor, and a scenario library. The data extractor includes multiple application events, each application event including an operation interface. The operation interface includes application scenarios and functional modules. The scenario library pre-stores multiple scenario systems, and the function library pre-stores multiple functional systems. The addresses of the application scenarios and scenario systems are matched, and the addresses of the functional modules and functional systems are matched. Multiple functional modules and multiple application scenarios form a matrix in the operation interface. Call controls are set at the intersections of the matrix. The addresses of the scenario systems are matched with login devices. The login devices store a routing table, and the routing table pre-stores multiple sets of accounts that can link to the scenario library addresses.

[0006] The principle of the rapid data modification and distribution system is as follows: The data extractor's interface includes multiple application events, each with added functional modules. First, an application event is selected, which then pops up a matrix operation interface. Functional modules are added to the first column, and application scenarios to the first row, forming a matrix of functional modules and application scenarios. The matrix intersections automatically generate call controls, which retrieve the corresponding functional system from the function library for the selected functional module. After adding functional systems to the application scenarios in the horizontal row, all functional systems are integrated into the scenario system to form the application scenario after data distribution, thus completing the data distribution process.

[0007] Since each application scenario has a corresponding scenario system with a login device, the login device stores a routing table. The routing table pre-stores multiple sets of accounts that can link to the scenario library address, and users can directly access the application scenario through their accounts.

[0008] The user interface is equipped with an independent modifier, which includes data editing controls. The modifier extracts elements from the functional system to form multiple data editing controls corresponding to editing elements. The multiple data editing controls are further labeled with type tags such as numerical values, keywords, checkboxes, text boxes, and attachments according to their data types.

[0009] The modifier uses the type tag to find the data type to be modified. When you need to modify the data in a functional module, simply call the modifier and select the data type control. This will allow you to directly put data of the same data type from all functional modules into the modification table. After completing the data modification, simply click "Confirm," and the data will be quickly fed back to the functional system from its original address, achieving the purpose of batch modification.

[0010] The user interface includes a function module search bar to check if the function module matches the application scenario. It also includes an "Add" button to add an application scenario, which is assigned an IP address. Adding the application scenario's IP address to the login device allows access to the application scenario's content through the login device.

[0011] To facilitate data modification on terminals that have already been matched with application scenarios, this solution also includes a method for rapid data modification and distribution, the steps of which include:

[0012] Step 1: Start the distribution system and modify the data mode to upload the terminal data to the temporary storage server. At this time, the terminal can access the application scenario through the login device, but cannot modify the data in the application scenario.

[0013] Step 2: The distribution system extracts modifiable data from the functional system using the modifier;

[0014] Step 3: After completing the batch modifications, populate the modification interface with the data from the temporary server, and then submit the modifications in the editor.

[0015] Step 4: At this point, the gateway data communication link is restored, enabling the modification and distribution of data for all application scenarios in the system.

[0016] Furthermore, after the data modification and distribution are completed, return to the desktop of the modification scope, click the check button to view the information of the modified function modules, and highlight the modification information or display a floating window prompt so that technical personnel can check whether any modifications have been missed.

[0017] In step four, after the data modification and distribution are completed, a modification announcement board is created for each scenario, and the announcement board information contains the content of this modification.

[0018] In step two, if the same data is extracted from multiple functional modules, the data is merged, and the merged data is marked by its address to indicate which functional system the merged data belongs to.

[0019] In step two, a monitoring guard is added to the modifier to filter the distributed data. Specifically: First, the monitoring guard reads the scene system address and checks if it matches the scene system address logged in by the terminal. If there is a discrepancy, the terminal's scene data will be erased and login will be restricted. Then, the number of functional modules in the scene system is compared. If the number of functional modules matches, the terminal's login address is extracted and stored in the work log. If the login address matches more than 5 times in the work log, it is defined as a frequently used tag; if the login address matches less than 5 times, it is marked as an abnormal login. Finally, the routing monitoring guard compares the data editing control with the data in the functional system to see if they match. If the data does not match, an alert message is sent.

[0020] By using monitoring guards, we can prevent data from not being synchronized to the terminal after it has been modified. Monitoring guards can also monitor account logins on infrequently used terminals, providing early warnings and ensuring data security. Attached Figure Description

[0021] Figure 1 This is a schematic diagram of the data rapid modification and distribution system in Embodiment 1.

[0022] Figure 2 This is a schematic diagram illustrating the relationship between the called controls and the scene library in Example 1;

[0023] Figure 3 This is a schematic diagram of the modifier principle of the data rapid modification and distribution system in Example 2;

[0024] Figure 4 This is a flowchart illustrating a method for rapid data modification and distribution, as shown in Example 3. Detailed Implementation

[0025] The following detailed description illustrates the specific implementation method:

[0026] Example 1

[0027] like Figure 1 and Figure 2 The data rapid modification and distribution system shown includes a function library 9, a data extractor 1, and a scenario library 10. The data extractor 1 includes multiple application events 2, each application event 2 includes an operation interface 4, and the operation interface 4 includes application scenarios 7 and functional modules 3. The scenario library 10 pre-stores multiple scenario systems 71, and the function library 9 pre-stores multiple functional systems 31. The addresses of the application scenarios 7 and scenario systems 71 are matched, and the addresses of the functional modules 3 and functional systems 31 are matched. The multiple functional modules 3 and multiple application scenarios 7 form a matrix in the operation interface 4.

[0028] A call control 8 is set at the intersection of the matrix. The address of the scene system 71 is matched with a login device 11. The login device 11 stores a routing table. The routing table pre-stores multiple sets of accounts that can link to the scene library address. Each set of accounts corresponds to a terminal 12.

[0029] The operation interface 4 of the data extractor 1 includes multiple application events 2, and functional modules 3 are added to each application event 2. First, an application event 2 is selected. After selection, a matrix operation interface 4 pops up. Functional modules 3 are added to the first column of the pop-up matrix operation interface 4, and application scenarios 7 are added to the first row, thus forming a matrix composed of functional modules 3 and application scenarios 7. The intersections of the matrix will automatically generate call controls 8, which will retrieve the corresponding functional system 31 from the function library 9. After adding functional systems to the application scenarios in the horizontal row, all functional systems are then integrated into the scenario system 71 to form the application scenario after data distribution, thus completing the data distribution.

[0030] In the operation interface 4, there is a function module search bar 5, which is used to check whether the function module and the application scenario are in a matching state. In the operation interface 4, there is an add button 5, which is used to add application scenario 7. The application scenario is assigned an IP address. Add the IP address of the application scenario to the login device 11, so that the content of application scenario 7 can be accessed through the login device 11.

[0031] Example 2

[0032] like Figure 3The operation interface shown is equipped with an independent modifier 13, which includes a data editing control 32. The modifier extracts the elements in the functional system 31 to form the modification elements corresponding to multiple data editing controls 32. The multiple data editing controls 32 are further labeled with type tags 14 such as numerical values, keywords, checkboxes, text boxes and attachments according to the data type.

[0033] Modifier 13 calls type tag 14 to find the data type to be modified. When it is necessary to modify the data in function module 3, modifier 13 is called directly. In modifier 13, the data type control is selected. This way, all data of the same data type in function module 3 can be put into the modification table. After the data modification is completed, just click confirm, and the data will be quickly fed back to the function system according to the original address, so as to achieve the purpose of batch modification.

[0034] Example 3:

[0035] like Figure 4 One method shown is for rapid data modification and distribution, and the steps include:

[0036] Step 1 S1: Start the distribution system and modify the data mode to upload the terminal data to the temporary storage server. At this time, the terminal can access the application scenario through the login device, but cannot modify the data in the application scenario.

[0037] Step 2 S2: The distribution system extracts modifiable data from the functional systems through the modifier; if the same data is extracted from multiple functional modules, the data is merged, and the addresses are used to mark which functional systems the merged data belongs to.

[0038] Step 3 S3: After completing the batch modifications, populate the modification interface with the data from the temporary server and submit the modification interface in the modifier;

[0039] Step 4 (S4): At this point, the gateway data communication link is restored, enabling the modification and distribution of data for all application scenarios in the system.

[0040] Supplementary Step S5: After the data modification and distribution are completed, return to the desktop of the modification scope, click the check button, view the information of the modified function modules, and highlight the modification information or display a floating window prompt so that technical personnel can check whether any modifications have been missed.

[0041] Supplementary Step S6: After the data modification and distribution are completed, create a modification announcement board for each scenario, with the announcement board information stating the content of this modification.

[0042] like Figure 1 , Figure 2 and Figure 3The modifier 13 shown includes a listening guard 16. The listening guard 15 filters the distributed data. Specifically: First, the listening guard 15 reads the scene system address and checks if it matches the scene system address of the login device 11. If there is a discrepancy, the scene data of the terminal 12 is erased and login is restricted. Then, the number of functional modules 3 in the scene system 7 is compared. If the number of functional modules 3 matches, the login address of the terminal 12 is extracted and stored in the work log. If the login address matches more than 5 times in the work log, it is defined as a common tag. If the login address matches less than 5 times, it is marked as an abnormal login. Finally, the routing listening guard 15 compares the data in the data editing control 32 and the data in the functional system 31 to see if they match. If the data does not match, a warning message is sent.

[0043] By using monitoring guards, we can prevent data from not being synchronized to the terminal after it has been modified. Monitoring guards can also monitor account logins on infrequently used terminals, providing early warnings and ensuring data security.

[0044] The above descriptions are merely embodiments of the present invention. Commonly known structures and characteristics are not described in detail here. Those skilled in the art are aware of all common technical knowledge in the field prior to the application date or priority date, are aware of all existing technologies in that field, and have the ability to apply conventional experimental methods prior to that date. Those skilled in the art can, under the guidance of this application, improve and implement this solution in combination with their own capabilities. Some typical known structures or methods should not be obstacles for those skilled in the art to implement this application. It should be noted that those skilled in the art can make several modifications and improvements without departing from the structure of the present invention. These should also be considered within the scope of protection of the present invention, and will not affect the effectiveness of the implementation of the present invention or the practicality of the patent. The scope of protection claimed in this application should be determined by the content of its claims, and the specific embodiments described in the specification can be used to interpret the content of the claims.

Claims

1. A data quick modification distribution method based on a data quick modification distribution system, characterized in that: the data quick modification distribution system comprises a function library, a data extractor and a scene library; the data extractor comprises a plurality of application events, each application event comprises an operation interface, the operation interface comprises an application scene and a function module, the scene library pre-stores a plurality of scene systems, the function library pre-stores a plurality of function systems, the application scene matches the address of the scene system, the function module matches the address of the function system, a plurality of the function modules and a plurality of the application scenes form a matrix in the operation interface, a calling control is arranged at the intersection of the matrix, the address of the scene system matches a login device, the login device stores a routing table, and the routing table pre-stores a plurality of groups of accounts capable of linking the address of the scene library; the data quick modification distribution method comprises the following steps: Step one: starting the distribution system to modify data mode, uploading terminal data to a temporary storage server, at this time, the terminal can access the application scene through the login device, but cannot modify the data in the application scene; Step two: the distribution system extracts the data that can be modified in the function system through a modifier; Step three: after batch completion of modification, filling the data in the temporary storage server into a modification interface, submitting the modification interface in the modifier, Step four: at this time, the gateway data communication link is restored, and the data of all application scenes of the system are modified and distributed. The operation interface is provided with an independent modifier, the modifier comprises data editing controls, elements in the function system are extracted to form a plurality of modification elements corresponding to the data editing controls, and a plurality of the data editing controls add value, keyword, check box, text box and attachment type tags according to the data type.

2. The method of claim 1, wherein: In the operation interface, a function module search bar is arranged, which is used to check whether the function module and the application scene are in a matching state, and an increase button is arranged in the operation interface, which is used to increase the application scene, and the application scene is assigned with an IP address; the IP address of the application scene is added to the login device to form a data channel for accessing the application scene through the login device.

3. The method of claim 2, wherein: In the step two: the scene in the login state is used as the scene in the modification state, the data filled by the terminal is temporarily stored in the local database, and a data verification state is prompted.

4. The method of claim 1, wherein: In step two, if the same data is extracted from a plurality of function modules, the data is merged, and the merged data is marked as belonging to which function system data through the address.

5. The method of claim 4, wherein: After the step three, when the data modification and distribution are completed, return to the modification range desktop, click the check button, check the modified information of the function module, and highlight the modified information or perform floating window prompting.

6. The method of claim 5, wherein: After step three, when the data modification and distribution are completed, a modification bulletin board is created for each scene, and the modification bulletin board information indicates the content of this modification.

7. The method of claim 6, wherein: ​ 8. The method of claim 1, wherein: In step two; the modifier is added with a listening guard, which filters the distributed data through the listening guard, specifically: first, the listening guard reads the scene system address to check whether the scene system address is consistent with the terminal login scene system address, if there is inconsistency, the terminal scene data will be erased and the login will be restricted; Then, compare the number of function modules in the scene system, when the number of function modules matches, extract the login address of the terminal, and store the login address in the work log table, if the login address in the work log table matches more than 5 times, it is defined as a common label; If the login address is less than 5 times, mark the login address as an abnormal login; Finally, through the route listening guard, compare whether the data in the data editing control and the function system match, if the data does not match, send a warning message.

Images