Basic data management and control system and method based on star structure
Through the star-structured basic data management and control system, unified management of basic data across the province and local autonomous coordination are achieved, solving the data consistency and business adaptation problems in multi-finance and multi-unit collaboration scenarios, and meeting the needs of financial informatization construction.
Patent Information
- Application Number
- CN202211661758.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-12-23
- Publication Date
- 2025-10-03
- Estimated Expiration
- 2042-12-23
AI Technical Summary
In a multi-finance and multi-unit collaborative scenario, basic data management is difficult and cannot simultaneously meet the needs of strengthening management and control and adapting to business needs.
A basic data management and control system based on a star structure is adopted, including a first-level module centrally deployed throughout the province, a second-level module for finance departments at all levels within the province, and a third-level module for public institutions under the jurisdiction of finance departments at all levels. Through control instructions, unified management and local updates of data are achieved to ensure data consistency and business adaptability.
It has achieved the coordination of unified management of basic data across the province and local autonomy, solved the problems of data consistency and business adaptation, and met the needs of financial informatization construction.
Smart Images

Figure CN116109427B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of information construction, and in particular to a basic data management and control system and method based on a star structure. Background Art
[0002] With the development of cloud computing, big data, and large-scale interconnected industry network technologies, the integration of fiscal budget management, with provinces as the central unit, has accelerated. The fiscal industry's application development model has completely overturned the previous system construction model of building a first-level system based on a first-level fiscal system. This model, which adheres to unified business specifications, unified technical standards, and a unified technical approach, has gained widespread recognition. Financial application systems with integrated business operations, ultra-large-scale computing power, storage capacity, and interconnectivity have become mainstream.
[0003] Due to the high degree of convergence of budget management operations at all levels, extremely high requirements are placed on the management of basic data. It is necessary to realize unified management, unified distribution, unified updating and other business needs of basic data in a large range of multiple fiscal regions to ensure that fiscal data is generated according to the same caliber and rules under the same information framework, and to ensure that the data granularity and statistical caliber of national fiscal business data are highly unified, laying the foundation for giving full play to the key basic support role of finance in the national governance system.
[0004] At present, the Ministry of Finance has developed a national budget data aggregation system, and through this system, it has realized data exchange between the central and local levels, ensuring the issuance and management of unified central data at the national level. However, below the provincial level, how to ensure that the basic data issued by the central government is conveyed to the finance departments at all levels, how to ensure that the unified basic data added and maintained in the province reaches the finance departments at all levels smoothly, and how to ensure that the basic information required for unification in each business module reaches the finance departments at all levels smoothly, ensure the consistency of basic data, and achieve the construction and operation goals of the province's financial informatization construction have become urgent issues that need to be solved. Summary of the Invention
[0005] In view of this, the purpose of the present invention is to provide a basic data management and control system, method and electronic equipment based on a star structure to solve the current difficulties in basic data management in multi-finance and multi-unit collaboration scenarios, and the problem of being unable to simultaneously meet the needs of strengthening management and control and adapting to business needs.
[0006] To achieve the above objectives, the present invention adopts the following technical solutions:
[0007] In the first aspect, the present application provides a basic data management and control system based on a star structure, comprising: a first-level module centrally deployed for the entire province, multiple second-level modules deployed at various levels of finance within the province, and multiple third-level modules deployed at the institutions under the jurisdiction of the finance at various levels;
[0008] The first-level module is used to store and manage basic data and send the basic data to all the second-level modules; the second-level module is used to generate local basic data based on the basic data sent by the first-level module, and send the basic data generated by the second-level module to the corresponding third-level module; the third-level module is used to generate local basic data based on the basic data sent by the second-level module;
[0009] When the primary module modifies its basic data based on a control instruction, the primary module is further configured to issue the control instruction to all the secondary modules, so that the secondary modules can update their local basic data based on the control instruction after their managers adjust their local businesses or confirm the changes.
[0010] When the secondary module changes the basic data therein based on the control instruction, the secondary module is also used to issue the control instruction to the corresponding tertiary module, so that the tertiary module can update its local basic data based on the control instruction after its management personnel adjust the local business or confirm it.
[0011] Optionally, the secondary module generates local basic data based on the basic data sent by the primary module, including: generating a basic data copy based on the basic data sent by the primary module as the local basic data;
[0012] The third-level module generates local basic data based on the basic data sent by the second-level module, including: generating a basic data copy based on the basic data sent by the second-level module as the local basic data.
[0013] Optionally, the basic data copy of the secondary module is also used for applications at this level;
[0014] The third-level module is also used to directly obtain at least part of the basic data in the second-level module for use by local applications.
[0015] Optionally, local basic data is generated based on the basic data sent by the upper-level module, including:
[0016] Directly use the basic data sent by the upper module as the local basic data;
[0017] Or based on business needs, select some of the basic data issued by the upper-level module as local basic data;
[0018] Or based on business needs and preset extension rules, at least part of the basic data sent by the upper-level module is expanded to generate local basic data;
[0019] Among them, the first-level module is the upper-level module of the second-level module, and the second-level module is the upper-level module of the third-level module.
[0020] Optionally, the basic data includes first basic data and second basic data, the first basic data is the basic data that the lower-level module is not allowed to modify after being issued, and the second basic data is the basic data that the lower-level module is allowed to modify after being issued; the control instruction includes a new instruction; the secondary module is the lower-level module of the primary module, and the tertiary module is the lower-level module of the secondary module
[0021] If the adding instruction is used to add the first basic data, the lower-level module is further used to directly execute the adding instruction to add the corresponding basic data to the local basic data;
[0022] If the new instruction is used to add the second basic data, then after the manager adjusts the local business or confirms it, the local basic data is updated based on the control instruction, including:
[0023] Execute the new instruction to perform the operation of adding new basic data in the local basic data, and after the administrator confirms it, the data obtained by the operation will take effect.
[0024] Optionally, the control instruction further includes a delete instruction;
[0025] After the management personnel adjust the local business or confirm it, based on the control instruction, the local basic data is updated, including:
[0026] After the administrator adjusts the local business, the deletion instruction is executed to delete the corresponding basic data in the local basic data.
[0027] Optionally, the control instruction further includes a modification instruction;
[0028] After the management personnel adjust the local business or confirm it, based on the control instruction, the local basic data is updated, including:
[0029] Execute the modification instruction to generate a new copy of the basic data and set it to a disabled state;
[0030] After its managers adjust local business or confirm, the newly generated basic data copy is activated and the original local basic data is deactivated.
[0031] Optionally, the first-level module, the second-level module and the third-level module each include at least one of a basic data submodule, a metadata submodule, a log submodule and a change history submodule;
[0032] The basic data submodule is used to manage the basic data in this module;
[0033] The metadata submodule is used to manage the attributes of the basic data in this module, including the name, publishing method, and whether other modules are allowed to extend it after it is issued;
[0034] The log submodule is used to record operation events on the basic data in this module;
[0035] The change history submodule is used to record the historical data of the basic data in this module at various stages.
[0036] Optionally, the primary module and the secondary module both further include a registration submodule;
[0037] The registration submodule in the primary module is used to register the secondary module and establish a communication connection with the registered secondary module to issue basic data and control instructions to the registered secondary module;
[0038] The registration submodule in the secondary module is used to register the tertiary module and establish a communication connection with the registered tertiary module to send basic data and control instructions to the registered tertiary module.
[0039] In a second aspect, the present application further provides a basic data management and control method based on a star structure, which is applied to the lower-level modules in the above-mentioned system, including:
[0040] Obtaining basic data and control instructions from a superior module, wherein the control instructions are used to change the basic data;
[0041] Generate local basic data based on the basic data obtained from the upper-level module;
[0042] After the administrator of the lower-level module adjusts the local business or confirms it, the local basic data is changed based on the control instruction.
[0043] The star-structured basic data management and control system provided in this application realizes the release and sharing of basic data from the province to finance at all levels and then to the units under the jurisdiction of each finance through three levels of modules. In addition, the control instructions executed in the modules at this level are issued to the lower-level modules, so that the lower-level modules can update the local basic data based on the control instructions after adjusting the business. While strengthening data management and control and ensuring data consistency, it can also avoid the problem of being unable to adapt to the finances at all levels and the business of each unit. BRIEF DESCRIPTION OF THE DRAWINGS
[0044] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0045] Figure 1 This is a schematic diagram of the structure of a basic data management and control system based on a star structure provided in an embodiment of the present application;
[0046] Figure 2 A schematic diagram of a process for adding basic data based on a new instruction in a basic data control system based on a star structure provided by an embodiment of the present application;
[0047] Figure 3 A schematic diagram of a process for deleting basic data based on a delete instruction in a basic data management and control system based on a star structure provided by an embodiment of the present application;
[0048] Figure 4 A schematic diagram of a process for lower-level modules to modify basic data based on modification instructions in a basic data management and control system based on a star structure provided in an embodiment of the present application;
[0049] Figure 5 A schematic diagram of the structure of a first-level module in a basic data management and control system based on a star structure provided in an embodiment of the present application;
[0050] Figure 6 A schematic diagram of data interaction between modules at all levels in a basic data management and control system based on a star structure provided in an embodiment of the present application;
[0051] Figure 7 A flow chart of a basic data management method based on a star structure provided in an embodiment of the present application. DETAILED DESCRIPTION
[0052] To make the objectives, technical solutions, and advantages of the present invention more apparent, the technical solutions of the present invention will be described in detail below. Obviously, the embodiments described are only some of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other implementations obtained by those of ordinary skill in the art without inventive effort are within the scope of protection of the present invention.
[0053] Application Overview:
[0054] In order to meet the needs of information construction, there are generally two models in the existing technology, namely, the technical solution that pursues full sharing and use of basic data and the technical solution that basic data at all levels are maintained independently according to standards, but neither can meet the needs of information construction.
[0055] Specifically, the technical solution for fully sharing and utilizing basic data primarily seeks to maximize the sharing of basic data, pursuing a near-zero-redundancy solution. Through a control mechanism, basic data is maintained once and shared across all regions, attempting to resolve the issue of basic data consistency through technical means. However, this solution fails to unify the operational pace of local finances, making the strong consistency it seeks difficult to achieve. Ultimately, this solution is overly idealistic and faces numerous difficulties in practical application. Various problems arise from conflicts and mutual constraints between business and technology, further rendering this solution unsuitable for large-scale financial system development.
[0056] Second, the technical solution for finance departments at all levels to maintain data by themselves in accordance with standards acknowledges that the problem of business coordination and consistency under multiple finance situations cannot be solved through technology. The solution of self-maintenance of basic data by all levels successfully avoids the problems of mutual restraint and mutual influence in the first solution. However, it also greatly weakens the demand for unified management, updating, and publishing of basic data across the province, abandons the use of technical means to solve the problem of data consistency, lacks control at the corresponding demand points, and lacks the necessary control capabilities overall.
[0057] In addition, since the above two methods are both rooted in the integrated budget management construction scenario, for the larger-scale application construction of fiscal and financial integration, which incorporates the construction factor of unit finance as the fund management center, the first technical solution that pursues full sharing and use of basic data needs to extend its control capabilities to budget units, which makes its control model face more stringent requirements and challenges; the second solution that lacks control capabilities performs poorly in meeting the requirements for greater consistency of basic data, and lacks support for meeting the unified requirements of common basic data for multiple units.
[0058] On the premise of fully understanding the financial basic data management business, this application sets up a unified basic data management center and basic data sharing and use centers at the financial and administrative unit levels to build a star-shaped basic data center management and use system that has both unified management and control capabilities and retains the autonomy of each financial district and unit. It well meets the basic data management and control problems of unified management, release, sharing and partial autonomy of basic data among the province, finance at all levels, and budget units under finance at all levels under the large centralized application model. The specific plan is introduced in detail through the following embodiments.
[0059] System Example:
[0060] Figure 1 This is a structural diagram of a basic data management and control system based on a star structure provided in an embodiment of the present application. The system provided in an embodiment of the present application includes a first-level module, a second-level module and a third-level module.
[0061] The first-level module 1 is used to store and manage basic data, and distribute the basic data to all second-level modules 2; the second-level module 2 is used to generate local basic data based on the basic data distributed by the first-level module 1, and distribute the generated basic data to the corresponding third-level module 3; the third-level module 3 is used to generate local basic data based on the basic data distributed by the second-level module 2.
[0062] Specifically, Level 1 Module 1 is centrally and uniformly deployed across the province, serving as the province's unified basic data management, maintenance, and release center. It stores basic data required for province-wide application, including basic data acquired from the central government and newly added basic data shared across the province. That is, the basic data in Level 1 Module 1 is shared across the province, including various code tables, expenditure function classifications, accounting subjects, and economic classifications of departmental budget expenditures. Level 1 Module 1 is used to provide basic data services to Level 2 Module 2, including distributing its basic data to Level 2 Module 2.
[0063] Secondary Module 2 is deployed in provincial finance departments at all levels. After acquiring the basic data from Primary Module 1, it generates local basic data based on the acquired basic data, such as by creating a local copy of the basic data. Secondary Module 2 is used to distribute local basic data to the institutions and applications under its jurisdiction, providing basic data sharing services to meet the basic data usage requirements of the business applications at this level and the institutions under its jurisdiction.
[0064] The third-level module 3 is arranged in the public institutions under the jurisdiction of finance at all levels. After obtaining the basic data in the second-level module 2, it generates local basic data, including establishing a local copy of the basic data, or directly obtaining the basic data in the second-level module 2 for use by the unit and corresponding applications.
[0065] It's important to note that because Level 3 Module 3 is connected only to Level 2 Module 2, obtaining basic data services from Level 2 Module 2 also reflects the management principle that institutions at this level adhere to the unified basic data requirements of the local finance department. Furthermore, because the local basic data in Level 2 Module 2 is generated based on the basic data in Level 1 Module 1, Level 1 Module 1 also has a certain degree of control over the basic data in Level 3 Module 3 on a larger scale.
[0066] Thus, by centrally deploying Level 1 Module 1, Level 2 Module 2 at each finance department, and Level 3 Module 3 at each public institution, one Level 1 Module 1, multiple Level 2 Modules 2, and multiple Level 3 Module 3 deployment points form a star-shaped structure centered on Level 1 Module 1. Each public institution deployment point obtains corresponding data, services, and instructions from its own level of finance; each finance deployment point obtains corresponding data, services, and instructions from the province-wide deployment point, ensuring efficient data interoperability across departments.
[0067] Furthermore, when the first-level module 1 changes the basic data therein based on a control instruction, the first-level module 1 is also used to issue the control instruction to all second-level modules 2, so that the second-level modules can update and change their local basic data based on the control instruction after their managers adjust local business or confirm; and when the second-level module 2 changes the basic data therein based on a control instruction, the second-level module 2 is also used to issue the control instruction to the corresponding third-level module 3, so that the third-level module 3 can change and update its local basic data based on the control instruction after its managers adjust local business or confirm.
[0068] Specifically, when the first-level module 1 changes the basic data therein based on the control instructions, such as adding, modifying and deleting basic data, in order to ensure that the basic data of the second-level module 2 remains consistent with the basic data modified by the first-level module 1, the first-level module 1 will also send the control instructions to the second-level module 2, for example, by issuing the corresponding control instructions through a message mechanism.
[0069] After receiving the control instruction from the primary module 1, the secondary module 2 modifies and updates the local basic data based on the control instruction after the administrator of the secondary module 2 adjusts the business and business data or confirms it. For example, this may include executing the control instruction first to modify the local basic data, but setting the modified basic data to the inactive state. After the administrator adjusts the business and confirms it, the modified basic data is activated; or directly executing the control instruction after adjusting the business data to ensure that the basic data change does not conflict with the business.
[0070] Similarly, the third-level module 3 can also obtain control instructions from the second-level module 2 to modify local basic data. It should be noted that in this case, the control instructions in the second-level module 2 can be control instructions obtained by the second-level module 2 from the first-level module 1, or they can be input and generated by the second-level module administrator himself. The subsequent modification and update principles are the same as the principles for updating basic data by the second-level module 2 described above, and will not be repeated here.
[0071] The basic data control system based on the star structure provided by this application realizes the release and sharing of basic data from the province to the finance departments at all levels and then to the units under the jurisdiction of each finance department by setting up a first-level module for basic data management that is unified across the province, a second-level module for basic data sharing corresponding to the finance departments at all levels, and a third-level module for basic data sharing corresponding to the administrative and public institutions under the finance departments at all levels. Moreover, by simultaneously issuing control instructions executed within this module to the lower-level modules, the lower-level modules can update the local basic data based on the control instructions after adjusting the business or confirming it. While strengthening data control and ensuring data consistency, it can also avoid the problem of being unable to adapt to the finance departments at all levels and the business of each unit, thereby meeting the construction needs and operation and maintenance needs of the province's financial informatization construction.
[0072] In some embodiments, the upper module in the above modules (for example, for the third-level module 3, its upper module is the second-level module 2, and for the second-level module 2, its upper module is the first-level module 1) sends basic data to the lower module (for example, for the first-level module 1, its lower module is the second-level module 2, and for the second-level module 2, its lower module is the third-level module 3) in a manner that can be directly pushing the basic data to the lower module, or receiving and responding to the download request of the lower module, and achieving the sending by downloading the lower module. The control instructions can be sent through a message mechanism.
[0073] In some embodiments, the above-mentioned secondary module 2 and tertiary module 3 generate local basic data based on the acquired superior basic data, and may generate a local basic data copy so that the local basic data copy can be subsequently adjusted based on preset rules and business needs, and used by the application system of this level or this unit without affecting the superior basic data.
[0074] In addition, the first-level module 1 can also construct control metadata for its basic data through internal preset sub-modules, such as the metadata sub-module, to maintain and manage the corresponding basic data, and establish a basic data benchmark shared by the entire province. Similarly, the second-level module 2 can also construct control metadata for its acquired, newly added, or modified basic data according to preset rules, and establish a basic data benchmark shared by the public institutions under the financial jurisdiction of the same level.
[0075] In some embodiments of the present application, local basic data is generated based on the basic data sent by the upper module, including various methods, such as:
[0076] First: Directly use the basic data sent by the upper-level module as the local basic data. That is, do not make any adjustments to the basic data sent by all upper-level modules, and directly generate a local basic data copy for use by the current level application and lower-level modules.
[0077] Second: Based on business needs, select some basic data sent by the upper-level module as local basic data; when some basic data sent by the upper-level module are not used at this level, you can select some of them and generate a local copy of the basic data for use by applications at this level and lower-level modules.
[0078] Third: Based on business needs and preset extension rules, expand at least part of the basic data issued by the upper-level module to generate local basic data; wherein, the preset extension rules can be formulated by the upper-level module or globally (for all modules). At this time, the local basic data copy can include directly obtained and unexpanded basic data and expanded basic data.
[0079] In this way, we can ensure the unified management, maintenance, release and use of basic data, while also ensuring the partial autonomy of lower-level modules and ensuring the smooth progress of business.
[0080] Furthermore, in some embodiments of the present application, the control instructions for changing the basic data mentioned above may include adding instructions, deleting instructions, and modifying instructions, etc.
[0081] Specifically, a new instruction is added for adding new basic data. It should be noted that the basic data sent by the upper module includes the first basic data and the second basic data. Taking the first-level module 1 as an example, the first basic data is the basic data that is not allowed to be modified by the second-level module 2 after being sent to the second-level module 2, and the second basic data is the basic data that is allowed to be modified by the second-level module 2 after being sent to the second-level module 2.
[0082] like Figure 2 As shown, when a new instruction is used to add the first basic data (for example, unified basic data for the entire province), after obtaining the instruction, the secondary module 2 can directly execute the instruction in the secondary module 2 and take effect on the newly added basic data without the intervention of the administrator of the secondary module 2, so as to add the corresponding basic data in the local basic data copy and complete the update.
[0083] When a new instruction is used to add a second basic data, after the secondary module 2 obtains the instruction, it needs the intervention of the administrator of the secondary module 2 to take effect. For example, after the execution of the new instruction, the corresponding basic data is added, but its status is not enabled or not effective. It will only be enabled or effective after the administrator of the secondary module 2 agrees, thereby avoiding the problem of confusion between basic data and business in the secondary module 2 after it is directly enabled or effective.
[0084] Figure 3 A schematic diagram of a process for deleting basic data based on a delete instruction in a basic data management system based on a star structure provided by an embodiment of the present application is shown in FIG. Figure 3 As shown, including:
[0085] After the lower-level module receives the deletion instruction executed in the upper-level module, it first waits for the administrator to sort out the corresponding business. After the sorting is completed (the administrator can enter a confirmation instruction), the deletion instruction is executed to delete the corresponding basic data in the local basic data of this module to complete the update.
[0086] Figure 4 A schematic diagram of a process in which a lower-level module deletes basic data based on a modification instruction in a basic data management and control system based on a star structure according to an embodiment of the present application is provided. Figure 4 As shown, including:
[0087] After the lower-level module receives the modification instruction executed in the upper-level module, it can first execute the modification instruction and build a modified basic data copy locally, but its status is not enabled. At this time, the basic data used in this module is still the original basic data; after the module manager adjusts the corresponding business data according to the modification instruction, the status of the modified data copy is set to enabled, and the original basic data is disabled to achieve replacement and update.
[0088] In this way, based on the above method, the local basic data of modules at all levels are changed and updated, which solves the problem of unified addition, modification and deletion of basic data of modules at all levels, ensures the integrity of business data and the consistency of the final state of basic data, and at the same time reflects the partial autonomy of lower-level modules.
[0089] Furthermore, in the basic data management and control system based on the star structure provided by this application, each module can be composed of multiple sub-modules. Taking the first-level module 1 as an example, Figure 5 The submodules include: a basic data submodule 11 , a metadata submodule 12 , a log submodule 13 , a change history submodule 14 and a registration submodule 15 .
[0090] Specifically, the basic data submodule 11 is used to manage the basic data in this module, including providing business operations such as input, modification, deletion, activation, and deactivation for the basic data in this module.
[0091] The metadata submodule 12 is used to manage the properties of the basic data described in this module, including describing the control properties of the basic data in this module to control the release method of the basic data (including downloading or pushing), whether the basic data allows the extension of lower-level modules, and the name of the basic data, etc.
[0092] The log submodule 13 is used to generate an operation log of the basic data, and record operation events on the basic data in this module.
[0093] The change history sub-module 14 is used to record the historical data of the basic data in this module at each stage of its life cycle.
[0094] The registration submodule 15 is used to register the lower-level module in the upper-level module to realize the link between the upper and lower modules, and form an organic basic data management system with the linked modules, thereby realizing the transmission of basic data and control instructions.
[0095] It should be noted that the above-mentioned sub-modules can all be equipped in the secondary module 2 to realize the same functions mentioned above in the secondary module 2, and other sub-modules except the registration sub-module 15 can all be set in the tertiary module 3 to realize the same functions.
[0096] It should be noted that the registration sub-module is set in the upper-level module. For example, a registration sub-module 15 is set in the first-level module 1, which is used to register the second-level module 2, realize the link between the first-level module 1 and the registered second-level module 2, and thus send basic data and control instructions to the registered second-level module 2; and is set in the second-level module 2, which is used to register the third-level module 3, realize the link with the registered third-level module 3, and send basic data and control instructions to the registered third-level module 3.
[0097] So, like Figure 6 As shown, each administrative and public institution deployment point (corresponding to the third-level module 3) registers to obtain corresponding data, services and instructions from the finance at the same level (corresponding to the second-level module 2), and each financial deployment point registers to obtain corresponding data, services and instructions from the provincial deployment point (corresponding to the first-level module 1) to ensure efficient and orderly data transmission.
[0098] The basic data control system based on the star structure provided by this application has a clear structure, covers comprehensive business, has a clear and concise way to solve problems, is easy to implement, convenient to maintain, and has strong scalability. It is suitable for the management requirements of complex basic data in the integrated business of fiscal budget management and the integrated financial and financial scenarios; by uniformly managing basic data and publishing data to finance at all levels, redundant copies of financial data at all levels (local basic data copies) are formed, and data maintenance is achieved by receiving maintenance information (the above-mentioned control instructions for changing basic data) issued by the control mechanism. The control mechanism is simple and clear, covering finance at all levels and their subordinate budget units, and meeting the requirements of unified basic data and financial and financial integration across the province; for the basic data obtained by finance at all levels and units, because their data status is not enabled, finance at all levels and units are allowed to independently control the data activation status according to their own business rhythm and data status. This completely avoids the problem that the first solution in the existing technology cannot adapt to the inconsistent business rhythm of finance at all levels and units; at the same time, the existence of redundant copies of finance at all levels (units can choose whether to use financial shared services or unit copies according to their needs) eliminates the risk of single point failure under the sharing mode and improves the robustness of the system. And because of the existence of local copies, finance departments and units at all levels can easily maintain their own extended information, reducing the communication costs and maintenance difficulties caused by conflicts between extended information.
[0099] Method Example:
[0100] Based on the same inventive concept, the present application also provides a basic data management method based on a star structure, which is applied to the system provided by the above system embodiment, such as Figure 7 Shown, including:
[0101] S701. Obtain basic data and control instructions from the upper-level module.
[0102] Among them, control instructions are used to change basic data;
[0103] S702: Generate local basic data based on the basic data obtained from the upper-level module;
[0104] S703. After the administrator of the lower-level module adjusts the local business or confirms it, the local basic data is changed based on the control instruction.
[0105] This application is based on a full understanding of financial business needs, and organizes the basic data management and maintenance business to form a solution specifically for the financial and financial integration application field under the multi-finance centralized application model.
[0106] Specifically, as described in the above system embodiment, in the system and method of the present application, basic data management is generally divided into three modules, namely, a basic data maintenance and management module for province-wide data sharing and use, a basic data management and maintenance module for finance at all levels, and a basic data management module for specific units. On the basis of the division of the three modules, the basic data publishing mechanism, sharing mechanism, redundant storage mechanism, duplicate data control rules, data change notification mechanism and other means are combined to form an overall solution for basic data management and maintenance, which effectively meets various needs in the following application scenarios:
[0107] ① It meets the needs of basic data control scenarios with unified management and release, shared use and partial autonomy of basic data among the province, finance departments at all levels, and budget units under finance departments at all levels under the province's large-scale centralized application model.
[0108] ② It meets the needs of pushing change information to all levels when basic data is added, changed, or deactivated.
[0109] ③ It meets the needs of finance at all levels to build local redundant copies of basic data, expand basic data according to rules, accept change information, and adjust local basic data according to the change information.
[0110] ④ It meets the needs of finance at all levels to independently control the status of basic data due to inconsistent business rhythms.
[0111] ⑤ It meets the needs of finance at all levels to provide basic data sharing services to the budget units under their jurisdiction based on redundant copies.
[0112] ⑥ It meets the needs of scenarios where finance departments at all levels release information on data addition, modification, deactivation, etc. to their subordinate units.
[0113] ⑦ It meets the needs of budget units under the jurisdiction of finance at all levels to obtain data from the finance at the same level to form local redundant copies, expand basic data according to rules, accept change information, and adjust local basic data according to the change information.
[0114] ⑧It meets the needs of financial units at all levels to independently control the status of basic data due to inconsistent business rhythms, and ultimately solves the problem of basic data consistency.
[0115] ⑨ It meets the needs of finance departments at all levels and subordinate units to independently obtain basic data in batches.
[0116] In addition, it should be noted that due to the similar scenarios and needs, the system and method provided in this application can also be applied to scenarios where other government departments build large-scale centralized application systems, such as the Ministry of Civil Affairs, Public Security, Industry and Commerce, Education, and the Ministry of Agriculture and Rural Affairs, etc. to build large-scale centralized application scenarios. The only difference is the basic data, and the management and control principles are the same. You can refer to the above-mentioned control principles of financial basic data for understanding, and will not go into details here.
[0117] It can be understood that the same or similar parts of the above embodiments can be referenced to each other, and the contents not described in detail in some embodiments can refer to the same or similar contents in other embodiments.
[0118] It should be noted that, in the description of the present invention, the terms "first", "second", etc. are used for descriptive purposes only and should not be understood as indicating or implying relative importance. In addition, in the description of the present invention, unless otherwise specified, the meaning of "plurality" is at least two.
[0119] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code comprising one or more executable instructions for implementing the steps of a specific logical function or process, and the scope of the preferred embodiments of the present invention includes alternative implementations in which functions may be performed out of the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present invention pertain.
[0120] It should be understood that various parts of the present invention can be implemented using hardware, software, firmware, or a combination thereof. In the above-described embodiments, multiple steps or methods can be implemented using software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented using hardware, as in another embodiment, any one of the following technologies known in the art or a combination thereof can be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application-specific integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.
[0121] Those skilled in the art will understand that all or part of the steps in the method of the above embodiment can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiment.
[0122] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing module, or each unit may exist physically separately, or two or more units may be integrated into a single module. The aforementioned integrated modules may be implemented in the form of hardware or in the form of software functional modules. If the integrated modules are implemented in the form of software functional modules and sold or used as independent products, they may also be stored in a computer-readable storage medium.
[0123] The storage medium mentioned above can be a read-only memory, a magnetic disk or an optical disk, etc.
[0124] Throughout this specification, reference to terms such as "one embodiment," "some embodiments," "examples," "specific examples," or "some examples" means that a specific feature, structure, material, or characteristic described in conjunction with that embodiment or example is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
[0125] Although the embodiments of the present invention have been shown and described above, it will be understood that the above embodiments are illustrative and are not to be construed as limitations on the present invention. A person skilled in the art may change, modify, replace and modify the above embodiments within the scope of the present invention.
Claims
1. A basic data management and control system based on a star structure, characterized by: include: One first-level module deployed centrally across the province, multiple second-level modules deployed at all levels of finance within the province, and multiple third-level modules deployed at all levels of finance under the jurisdiction of the public institutions; The primary module is used to store and manage basic data, and distribute the basic data to all the secondary modules; The secondary module is used to generate local basic data based on the basic data sent by the primary module, and send the basic data generated by the secondary module to the corresponding tertiary module; The third-level module is used to generate local basic data based on the basic data issued by the second-level module; When the primary module modifies its basic data based on a control instruction, the primary module is further configured to issue the control instruction to all the secondary modules, so that the secondary modules can update their local basic data based on the control instruction after their managers adjust their local businesses or confirm the changes. When the secondary module modifies its basic data based on the control instruction, the secondary module is further configured to issue the control instruction to the corresponding tertiary module, so that the tertiary module can update its local basic data based on the control instruction after its management personnel adjust the local business or confirm it; The generating of local basic data based on the basic data issued by the upper-level module includes: directly using the basic data issued by the upper-level module as the local basic data; or selecting part of the basic data issued by the upper-level module as the local basic data based on business needs; or expanding at least part of the basic data issued by the upper-level module based on business needs and preset expansion rules to generate local basic data; wherein the first-level module is the upper-level module of the second-level module, and the second-level module is the upper-level module of the third-level module; Among them, the basic data includes first basic data and second basic data, the first basic data is the basic data that the lower-level module is not allowed to modify after it is issued, and the second basic data is the basic data that the lower-level module is allowed to modify after it is issued; the control instruction includes a new instruction; the secondary module is the lower-level module of the primary module, and the tertiary module is the lower-level module of the secondary module; if the new instruction is used to add the first basic data, the lower-level module is also used to directly execute the new instruction to add the corresponding basic data in the local basic data; if the new instruction is used to add the second basic data, then after its management personnel adjusts the local business or confirms, based on the control instruction, update its local basic data, including: executing the new instruction, making the operation of adding new basic data in the local basic data, and after its management personnel confirms, taking into account the data obtained by the operation.
2. The system according to claim 1, wherein: The basic data copy of the secondary module is also used for applications at this level; The third-level module is also used to directly obtain at least part of the basic data in the second-level module for use by local applications.
3. The system according to claim 1, wherein: The control instructions also include deletion instructions; After the management personnel adjust the local business or confirm it, based on the control instruction, the local basic data is updated, including: After the administrator adjusts the local business, the deletion instruction is executed to delete the corresponding basic data in the local basic data.
4. The system according to claim 1, wherein: The control instructions also include modification instructions; After the management personnel adjust the local business or confirm it, based on the control instruction, the local basic data is updated, including: Execute the modification instruction to generate a new copy of the basic data and set it to a disabled state; After its managers adjust local business or confirm, the newly generated basic data copy is activated and the original local basic data is deactivated.
5. The system according to claim 1, wherein: The first-level module, the second-level module and the third-level module each include at least one of a basic data submodule, a metadata submodule, a log submodule and a change history submodule; The basic data submodule is used to manage the basic data in this module; The metadata submodule is used to manage the attributes of the basic data in this module, including the name, publishing method, and whether other modules are allowed to extend it after it is issued; The log submodule is used to record operation events on the basic data in this module; The change history submodule is used to record the historical data of the basic data in this module at various stages.
6. The system according to claim 1, wherein: The primary module and the secondary module also include a registration submodule; The registration submodule in the primary module is used to register the secondary module and establish a communication connection with the registered secondary module to issue basic data and control instructions to the registered secondary module; The registration submodule in the secondary module is used to register the tertiary module and establish a communication connection with the registered tertiary module to send basic data and control instructions to the registered tertiary module.
7. A basic data management and control method based on a star structure, characterized in that: Applicable to a lower-level module in the system according to any one of claims 1 to 6, comprising: Obtaining basic data and control instructions from a superior module, wherein the control instructions are used to change the basic data; Generate local basic data based on the basic data obtained from the upper-level module; After the administrator of the lower-level module adjusts the local business or confirms it, the local basic data is changed based on the control instruction.
Citation Information
Patent Citations
Basic data sharing system and method thereof
CN104796389A