Method and system for supporting multi-tenant sharing of railway business service

Abstract

A method and system for supporting railway business service to perform multi-tenant sharing relates to the technical field of electronic information, and comprises seven modules of service specification, client micro-module management, menu authority control, institution personnel management, database connection management, file storage management and message center. The system seamlessly embeds the micro-module into a client interface through a micro-front-end technology, and automatically loads a corresponding configuration and permission context according to a client identifier. Each module is highly decoupled; the client and the micro module establish an authorization relationship through an identification string; the institution tree takes a client identifier as a root node to realize hierarchical organization management; a database and file storage are independently configured according to a tenant-module combination, and data isolation is guaranteed. According to the method, 'one-time development and multi-tenant reuse 'can be realized, the delivery efficiency and the resource sharing capability are remarkably improved, and meanwhile, the safety and flexibility requirements of a railway system in a multi-level and multi-department complex scene are met.

Description

Technical Field

[0001] This invention relates to the field of electronic information technology, and in particular to a method and system for supporting multi-tenant sharing of railway business services. Background Technology

[0002] With the deepening of the national railway informatization construction, the demand for business software from various units within the railway system exhibits significant characteristics of "large quantity, urgent response, and high degree of functional homogeneity." Traditional software development models typically employ a "project-based" or "siloed" architecture, where each unit or business scenario develops its own independent system. This model not only leads to extensive duplication of development, resulting in a serious waste of human, time, and hardware / software resources, but also faces challenges such as chaotic management, inconsistent interfaces, and difficulty in data interoperability during subsequent maintenance, upgrades, and function sharing.

[0003] To address these challenges, the industry has gradually introduced the concept of a "middle platform." First proposed by Alibaba, the middle platform architecture's core idea is a "large middle platform, small front-end," supporting rapid iteration and flexible innovation of front-end businesses by building reusable shared service capabilities. In recent years, large internet companies such as Tencent, JD.com, and Meituan have successively implemented middle platform strategies, achieving significant results in improving R&D efficiency, reducing system coupling, and realizing resource consolidation.

[0004] In the railway sector, China State Railway Group Co., Ltd. (China Railway) attaches great importance to the construction of a middleware platform and has already begun exploration in key business areas such as transportation scheduling. For example, it has designed a railway transportation scheduling business middleware platform and developed a prototype system for visualizing train flow management. However, existing railway middleware solutions mainly focus on providing standardized data services and unified interface specifications, emphasizing compliance with industry regulatory and data governance requirements. They suffer from significant shortcomings in multi-tenant support capabilities, rapid access mechanisms, and flexibility in custom configuration. Specifically:

[0005] Existing systems lack fine-grained control over data isolation (logical or physical) in multi-tenant scenarios, making it difficult to guarantee data security between different user units;

[0006] The access process for micro-modules (shared business function units) is complex, requires a lot of customized development, and cannot achieve "plug and play".

[0007] The lack of a unified management framework for basic resource configurations such as permissions, organizational structure, database connection, and file storage means that each new customer needs to be configured repeatedly or even have their code modified.

[0008] The lack of seamless integration with existing business systems means that users still need to switch between multiple systems when using shared services, resulting in a fragmented experience.

[0009] Therefore, there is an urgent need for a basic framework that is tailored to the characteristics of railway business, supports multi-tenant sharing, and has high configurability and rapid delivery capabilities. This framework should be able to achieve efficient reuse of micro-modules, flexible authorization, and unified operation and maintenance while ensuring data isolation and security, thereby comprehensively improving the standardization, intensification, and intelligence of railway information system construction. Summary of the Invention

[0010] To overcome the shortcomings of the prior art, the present invention discloses a method and system for supporting multi-tenant sharing of railway business services.

[0011] To achieve the above-mentioned objectives, the present invention adopts the following technical solution:

[0012] A method for supporting multi-tenant sharing of railway business services includes the following steps:

[0013] S1. In the client micro-module management module, register the client identifier for the railway business client to be accessed, and register the module identifier and access address for the micro-module to be shared, and assign the micro-module to the client;

[0014] S2. In the menu permission control module, configure the menu information and interface resources corresponding to the micro-module, and bind the menu information and interface resources to the role preset for the client;

[0015] S3. In the organization and personnel management module, maintain the organization tree and personnel tree corresponding to the client, and assign corresponding roles to the personnel;

[0016] S4. In the database connection management module, configure exclusive database connection information for the client and the micro-module to achieve logical or physical data isolation;

[0017] S5. In the file storage management module, configure independent file storage sources and access permissions for the client and the micro-module;

[0018] S6. During the operation of the micro-module, business messages are pushed to the user of the client through the message center module;

[0019] S7. In the front-end interface of the client, the access address of the micro-module is embedded in the micro-frontend and the client identifier is passed in, so that the user can call the function of the micro-module.

[0020] Preferably, the menu information includes a menu identifier, a menu component address, and a menu routing path; the interface resources include an interface identifier and an interface access address; and the role permission information includes a role identifier, the authorized menu identifier, and the interface identifier.

[0021] Preferably, the database connection information includes a client identifier, a module identifier, a database identifier, and a database connection string, which are used to dynamically switch database connections at runtime to ensure data isolation between different clients.

[0022] Preferably, the permission information configured in the file storage management module includes client identifier, module identifier, role identifier, and file storage identifier, which are used to control the access permissions of different roles to the file storage space.

[0023] Preferably, the message information pushed by the message center module includes a user identifier, a unique message identifier, message content, and a redirection address, which is used to aggregate to-do items on a unified workbench.

[0024] A system supporting multi-tenant sharing of railway business services includes:

[0025] The service specification module is used to provide common methods and dependencies of the system;

[0026] The client-side micro-module management module is used to register and manage the basic information of clients and micro-modules, and to establish the authorization relationship between clients and micro-modules.

[0027] The menu permission control module is used to manage the menu structure, interface resources, and role permission mapping of micro-modules;

[0028] The organization and personnel management module is used to maintain the organizational structure tree, personnel information, and role assignments for each client.

[0029] The database connection management module is used to configure independent database connections for different client-micro-module combinations;

[0030] The file storage management module is used to manage file storage sources, directory structure, file metadata, and access permissions.

[0031] The message center module is used to receive and distribute business messages generated by the micro-modules to the corresponding users;

[0032] The system supports seamlessly embedding micro-modules into the client's original system interface through micro-frontend technology, and automatically loading the corresponding configuration and permission context based on the passed client identifier.

[0033] Preferably, the information stored in the client micro-module management module includes: client identifier string, module identifier string, module access address, and module R&D personnel information; the authorization relationship is realized through the association between the client identifier string and the module identifier string.

[0034] Preferably, the organizational tree in the personnel management module is built with the client identifier string as the root node, forming a hierarchical organizational structure; personnel roles are bound through the mapping relationship between personnel identifier strings and role identifier strings.

[0035] Preferably, the file storage information in the file storage management module includes a file storage identifier string and a file storage connection string; the folder information includes a folder identifier string and its parent folder identifier string; and the file information includes a file identifier string, a file name, and a file size.

[0036] Preferably, the system is developed using the same programming language, and each functional module uses a unified dependency version and interface contract through a service specification module to ensure compatibility and consistency in collaborative work between modules.

[0037] By employing the technical solution described above, the present invention has the following beneficial effects:

[0038] (1) This invention provides a well-structured, configuration-driven, and highly decoupled multi-tenant sharing mechanism, which not only significantly improves the reuse efficiency and delivery speed of railway business services, but also ensures data security and operational independence between different units through modular isolation, effectively adapting to the complex needs of multi-level, multi-department, and multi-business scenarios within the railway system. The system is integrated through micro-frontend technology, and the client only needs to pass in the client_id to automatically load the tenant-specific configuration, realizing "one-time development, multi-tenant reuse", significantly shortening the delivery cycle and improving resource sharing efficiency. The overall solution has outstanding technical advantages in ensuring data security, supporting flexible configuration, and adapting to complex organizational structures.

[0039] (2) Module 1 - Service Specification of this invention serves as a unified foundation layer, centrally providing logging components, encryption tools, exception handling mechanisms, and Spring Boot Starter dependencies, ensuring consistency in technology stack and communication interfaces among all upper-layer modules, effectively reducing system integration complexity, and improving maintainability and code reusability. Module 2 - Client Micro-module Management and Module 3 - Menu Permission Control work together. The former maintains the availability relationship of (client_id, module_id) and the role scope of (client_id, role_id), while the latter implements dual control of front-end menu visibility and back-end interface calls through module menu table, interface resource table, and role permission table, supporting the presentation of differentiated functions of the same micro-module under different tenants, and accurately meeting the business needs of the railway system of "authorization by unit and use by role".

[0040] (3) Module 4 of this invention – Organization and Personnel – constructs a complete organization-user-role mapping system through the organization tree table, personnel tree table, and personnel role table. This system can accurately reflect the multi-level organizational structure of the railway system and supports multiple roles for one person, ensuring that permission allocation can be implemented to specific positions and guaranteeing operational compliance. Module 5 – Database Connection Management – ​​configures a dedicated database connection string using (client_id, module_id) as the composite key, achieving tenant isolation at the data source level. It allows for dynamic switching of data sources without modifying the micro-module code, is compatible with heterogeneous databases such as MySQL and PostgreSQL, and balances security and deployment flexibility.

[0041] (4) Module 6 - File Storage Management of this invention establishes a full-link permission control mechanism from storage bucket to specific file through file storage information table, folder information table, file information table and permission information table. The permission information table uses (client_id, module_id, role_id, storage_id) as the association key to ensure that only authorized roles can access the specified storage content. It is compatible with various storage backends such as OSS and NAS and meets the security isolation requirements of business scenarios such as document attachments and scheduling logs. Module 7 - Message Center provides a standardized push interface. The micro-module can actively send structured to-do messages containing user_id, message content and jump URL at the business trigger point to realize unified aggregation and traceable management of notifications and improve user interaction efficiency. Attached Figure Description

[0042] Figure 1 This is a diagram showing the module hierarchy of the present invention;

[0043] Figure 2 This is a software flowchart of the present invention. Detailed Implementation

[0044] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0045] In the description of this invention, it should be noted that the terms "upper" and "lower" indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings, or the orientation or positional relationship in which the product of this invention is usually placed when in use. They are only used to facilitate the description of this invention and to simplify the description, and are not intended to indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this invention.

[0046] In this application, unless otherwise expressly specified and limited, the terms "installation," "connection," "joining," and "fixing," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components. Those skilled in the art can understand the specific meaning of the above terms in this application according to the specific circumstances.

[0047] Example 1:

[0048] Combined with appendix Figures 1-2 This paper presents a method and system for supporting multi-tenant sharing of railway business services. Its core lies in achieving secure, independent, and efficient sharing of micro-modular business services among multiple railway units on a unified platform through a layered and decoupled architecture design. For example... Figure 1 The diagram shown illustrates the hierarchical relationship of the basic framework modules used in this invention. It clearly demonstrates that the system adopts a top-down seven-layer functional module structure, with each module having clearly defined responsibilities, standardized interfaces, and orderly dependencies. The bottom layer is Module 1 – Service Specification, serving as the common foundational support layer for the entire system. It provides a unified logging mechanism, encryption toolset, exception handling strategies, security verification logic, and Spring Boot Starter dependency management, ensuring that the remaining six modules have a consistent technology stack and communication compatibility at runtime.

[0049] The six functional modules above Module 1 are arranged side-by-side: Module 2 - Client Micro-module Management, Module 3 - Menu Access Control, Module 4 - Organization and Personnel Management, Module 5 - Database Connection Management, Module 6 - File Storage Management, and Module 7 - Message Center. These modules all directly rely on the common capabilities provided by Module 1 and collaborate with each other through predefined standard interfaces. For example, Module 2 passes `client_id` and `module_id` to Module 3 to establish the binding relationship between the client and the micro-module, supporting subsequent permission allocation; Module 4 outputs the mapping information of `user_id` and `role_id` to Module 3, providing user identity verification for permission checks; Modules 5 and 6 dynamically inject unique database connection strings and file storage connection strings into the runtime-loaded micro-module instances based on the combination of `(client_id, module_id)`, thereby achieving tenant isolation at the data layer. This layered design effectively separates configuration management from business execution logic, enabling the system to possess good scalability, maintainability, and security when supporting multi-tenant scenarios.

[0050] like Figure 2The diagram shown is a software flowchart of the present invention, which fully describes the entire process of a new office module from registration to integration. The process begins with: a railway office system (such as an internal OA system of a railway bureau) wanting to use an office function module (such as a document approval module) that has not yet been registered in the shared framework. Then, step 1 is performed: in module 2 - client micro-module management, a unique client identifier (such as "RAIL_A_OFFICE") is first registered for the office system, the required roles (such as "APPROVER") are defined, and a record is created for the office module, containing metadata such as module_id, access address, and module developers. Then, the module is officially assigned to the client. At the same time, in module 3 - menu permission control, the front-end menu items (including menu component address and routing path) and back-end interface resources (such as RESTful API path) corresponding to the module need to be maintained, and these resources are authorized to the aforementioned roles to ensure that the granularity of permissions covers both the interface and the API dimensions.

[0051] Step 2 is completed in Module 4 - Organization and Personnel: Initialize the complete organizational structure tree to which the client belongs (e.g., a three-level structure of "Railway Bureau → Business Department → Specific Section"), and enter all relevant personnel information. Assign one or more roles to each user (e.g., assign the "APPROVER" role to Zhang San), thereby building a complete mapping system of "Organization-User-Role". Step 3 is executed in Module 5 - Database Connection Management: Configure dedicated database connection information for this (client_id, module_id) combination, including the database identifier (db_id) and the complete JDBC connection string, ensuring that the tenant can only access its dedicated data source when using this module. Step 4 is performed in Module 6 - File Storage Management: Set the file storage source (e.g., Alibaba Cloud OSS bucket or local NAS path), generate the corresponding storage_id, and establish the association between (client_id, module_id, role_id) and storage_id through the permission information table to achieve role-level access control for file read and write operations and storage isolation between tenants.

[0052] Step 5 involves message interaction during business runtime: When the business logic in the micro-module triggers a specific event (such as document submission completion), the module calls the standard interface provided by Module 7 - Message Center to write the pending items (including fields such as target user_id, message content, and redirect URL) into the message queue for the user's workbench to retrieve and display. Finally, in step 6, the client embeds the access address of the micro-module in its front-end page using micro-frontend technology (such as Web Components or the Qiankun framework), and passes in the configured client_id (such as "RAIL_A_OFFICE") during loading; after receiving this identifier, the system... Figure 1 The module dependencies shown automatically load the corresponding permission configuration, database connection policy and file storage policy for the tenant. Users can then seamlessly use this shared function within the existing office system interface without modifying the micro-module source code or redeploying it.

[0053] In the specific implementation of this invention, the data structure design of each module is as follows: Module 1 - Service Specification: This module centrally encapsulates common utility classes, logging components, encryption algorithms, and Spring Boot auto-configuration classes to ensure the consistency of the underlying system. Module 2 - Client Micro-module Management and Maintenance: This module maintains three core data tables: First, a basic information table for the client and micro-modules, with fields including client_id, module_id, module access address, and module developer; second, a list of available modules, recording (client_id, module_id) tuples to indicate which modules a client can use; and third, a list of client roles, recording (client_id, role_id) mappings to define the scope of roles. Module 3 - Menu Permission Control: This module contains three sub-tables: a module menu table (fields: module_id, menu_id, menu component address, menu route path), an interface resource table (fields: api_id, interface access address), and a role permission table (fields: role_id, menu_id, api_id), which together implement a dual control mechanism for menu visibility and interface call permissions. Module 4 - Organizational Personnel: A complete organizational structure and user role binding relationship are constructed through the organizational tree table (fields: client_id, org_id, parent_org_id), the personnel tree table (fields: user_id, personnel name), and the personnel role table (fields: user_id, role_id). Module 5 - Database Connection Management: The configuration information table includes fields: client_id, module_id, db_id, and database connection string, supporting dynamic switching of data sources by both tenant and module dimensions. Module 6 - File Storage Management: Maintains four types of information tables: file storage information table (storage_id, file storage connection string), folder information table (storage_id, folder_id, parent_folder_id), file information table (storage_id, folder_id, file_id, file name, file size), and permission information table (client_id, module_id, role_id, storage_id), achieving fine-grained permission control from buckets to folders to specific files. The message information table in Module 7 - Message Center contains fields: user_id, msg_id, message content, and access address, supporting business systems to proactively push structured pending messages to the workbench of specified users.

[0054] When the office system of a certain railway bureau (Unit A) needs to integrate a corresponding functional module, such as the "Document Approval" module, the specific operation process is as follows:

[0055] Step 1: Register the client identifier "RAIL_A_OFFICE" in module 2, create the role "APPROVER", and establish a registration record for module "DOC_APPROVAL_V2" and assign it to the client; at the same time, configure all menu items and API resources of this module in module 3 and authorize these resources to the "APPROVER" role.

[0056] Step 2: Import the complete organizational tree of Unit A into Module 4 (e.g., org_id are “RAIL_A_HEAD”, “RAIL_A_DEPT”, and “RAIL_A_SECTION” respectively), enter all relevant personnel (e.g., user U1001 “Zhang San”), and assign the “APPROVER” role to them.

[0057] Step 3: Configure a dedicated database connection for this module in Module 5, set db_id to "DB_DOC_A", and point the connection string to the independent MySQL instance of Unit A.

[0058] Step 4: Configure the storage source in module 6, set storage_id to "OSS_BUCKET_A", and authorize the storage source to the "APPROVER" role through the permission table to ensure that upload / download operations can only be performed by authorized users.

[0059] Step 5: Integrate the message push call of module 7 into the business logic of the micro-module, and automatically send a notification message to the relevant users when the document status changes.

[0060] Step 6: On the front-end page of Unit A's office system, load the URL of this module through the micro-front-end container and pass in client_id = "RAIL_A_OFFICE"; the system will automatically load the tenant's exclusive permissions, data source and storage policy accordingly, and the user can directly use this function in the original system to achieve zero-intrusion integration.

[0061] Through the above standardized process, this invention provides a multi-tenant sharing mechanism that is structurally clear, configuration-driven, and highly decoupled. It not only significantly improves the reuse efficiency and delivery speed of railway business services, but also ensures data security and operational independence between different units through modular isolation, effectively adapting to the complex needs of multi-level, multi-department, and multi-business scenarios within the railway system.

[0062] Example 2:

[0063] Combined with appendix Figures 1-2This document describes a method and system for supporting multi-tenant sharing of railway business services. Unlike Embodiment 1, it focuses on the complete implementation process of a specific application scenario. A railway bureau (Unit A) needs to integrate a "process approval" micro-module into its existing office system. (Refer to...) Figure 2 The process is as follows: First, in Module 2 - Client Micro-Module Management, register client_id = “RAIL_A_OFFICE”, create the role “APPROVER”, and assign module_id = “DOC_APPROVAL_V2” to this client. Next, in Module 3 - Menu Permission Control, configure specific menu items, such as menu_id = “MENU_DOC_LIST”, whose corresponding front-end component address is “ / views / doc / List.vue”, and the route path is “ / doc / list”; at the same time, define the interface resource API_SUBMIT_DOC, whose access address is “ / api / v1 / docs / submit”, and authorize both this menu and the interface to the “APPROVER” role.

[0064] In Module 4 - Organization and Personnel, import the three-level organizational structure of Unit A, with org_ids as "RAIL_A_HEAD" (Railway Bureau Headquarters), "RAIL_A_DEPT" (Business Department), and "RAIL_A_SECTION" (Grassroots Department), respectively. Enter user U1001 (Name: Zhang San) and bind them to the "APPROVER" role. In Module 5 - Database Connection Management, configure db_id = "DB_DOC_A", with its JDBC connection string pointing to Unit A's dedicated MySQL database instance, ensuring that process data is stored and queried only within this tenant's scope. In Module 6 - File Storage Management, set storage_id = "OSS_BUCKET_A", representing an independent OSS bucket, and authorize this storage source to the "APPROVER" role through the permission information table, allowing users with this role to upload or download attachments.

[0065] When Zhang San submits a process in the system, the internal business logic of the micro-module is triggered, calling the push interface of module 7 - message center, and sending a structured message to the user U1002: "You have a process document to review," along with a redirect URL (such as " / doc / detail?id=123"). Finally, the front-end of Unit A's office system embeds the access address of this micro-module in the form of an iframe or Web Components using micro-front-end technology (such as the qiankun framework), and passes client_id="RAIL_A_OFFICE" during loading; the system then... Figure 1The module dependencies and data flow shown automatically load the corresponding permission context, database connection configuration and file storage strategy for the tenant, realizing seamless integration and plug-and-play functionality of the modules.

[0066] Example 3:

[0067] Combined with appendix Figures 1-2 This document describes a method and system for supporting multi-tenant sharing of railway business services. Based on Embodiment 1, it is applied to a dispatching business scenario. A dispatching center B needs to connect to a "vehicle flow management visualization" micro-module to achieve real-time monitoring of train operation status. Similarly, based on... Figure 2 The process involves registering client_id = “DISPATCH_CENTER_B” in Module 2 - Client Micro-Module Management and registering module_id = “TRAIN_FLOW_VIS_V1” for this center; configuring the “Real-time Monitoring” menu item and its corresponding front-end components and routing paths in Module 3 - Menu Permission Control, registering the / api / v1 / flow / realtime interface resource, creating the “DISPATCHER” role, and authorizing the above resources to this role; constructing the three-level organizational structure of the dispatch center (e.g., dispatching station → dispatching console → duty group) in Module 4 - Organization and Personnel, and assigning the “DISPATCHER” role to dispatcher D2001; configuring the PostgreSQL database instance PG_FLOW_B in Module 5 - Database Connection Management as the dedicated data source for this module; and binding the local NAS storage path NAS_FLOW_B in Module 6 - File Storage Management to store historical traffic logs or screenshot files, and authorizing this storage source to the “DISPATCHER” role through the permission table.

[0068] When the system detects a train delay, the micro-module automatically calls the Module 7 - Message Center interface to push an alarm message to the relevant dispatcher. The message includes the train number, estimated delay time, and a link to suggested handling procedures. When the dispatch platform frontend loads this visualization module, it passes `client_id = “DISPATCH_CENTER_B”`; the system then... Figure 1 The architecture shown dynamically injects the tenant's database connection, file storage path, and permission context, allowing dispatchers to directly view train flow dynamics in a unified dispatch interface without switching systems or logging in repeatedly. This process fully demonstrates the versatility and adaptability of this invention in non-office-related business scenarios, achieving rapid reuse and secure sharing of core railway business functions.

[0069] The parts of this invention not described in detail are prior art. It will be apparent to those skilled in the art that this invention is not limited to the details of the above exemplary embodiments, and that the invention can be implemented in other specific forms without departing from the spirit or essential characteristics of the invention. Therefore, the embodiments should be regarded as exemplary and non-limiting in all respects, and are intended to encompass all changes falling within the meaning and scope of equivalents within this invention.

Claims

1. A method and system for supporting multi-tenant sharing of railway business services, characterized in that, Includes the following steps: S1. In the client micro-module management module, register the client identifier for the railway business client to be accessed, and register the module identifier and access address for the micro-module to be shared, and assign the micro-module to the client; S2. In the menu permission control module, configure the menu information and interface resources corresponding to the micro-module, and bind the menu information and interface resources to the role preset for the client; S3. In the organization and personnel management module, maintain the organization tree and personnel tree corresponding to the client, and assign corresponding roles to the personnel; S4. In the database connection management module, configure exclusive database connection information for the client and the micro-module to achieve logical or physical data isolation; S5. In the file storage management module, configure independent file storage sources and access permissions for the client and the micro-module; S6. During the operation of the micro-module, business messages are pushed to the user of the client through the message center module; S7. In the front-end interface of the client, the access address of the micro-module is embedded in the micro-frontend and the client identifier is passed in, so that the user can call the function of the micro-module.

2. The method for supporting multi-tenant sharing of railway business services as described in claim 1, characterized in that: The menu information includes a menu identifier, a menu component address, and a menu routing path; the interface resources include an interface identifier and an interface access address; the role permission information includes a role identifier, the authorized menu identifier, and an interface identifier.

3. The method for supporting multi-tenant sharing of railway business services as described in claim 1, characterized in that: The database connection information includes client identifier, module identifier, database identifier, and database connection string, which are used to dynamically switch database connections at runtime to ensure data isolation between different clients.

4. The method for supporting multi-tenant sharing of railway business services as described in claim 1, characterized in that: The permission information configured in the file storage management module includes client identifier, module identifier, role identifier, and file storage identifier, which are used to control the access permissions of different roles to the file storage space.

5. The method for supporting multi-tenant sharing of railway business services as described in claim 1, characterized in that: The message information pushed by the message center module includes user identifier, unique message identifier, message content, and redirection address, which is used to aggregate to-do items on a unified workbench.

6. A system for supporting multi-tenant sharing of railway business services, characterized in that, include: The service specification module is used to provide common methods and dependencies of the system; The client-side micro-module management module is used to register and manage the basic information of clients and micro-modules, and to establish the authorization relationship between clients and micro-modules. The menu permission control module is used to manage the menu structure, interface resources, and role permission mapping of micro-modules; The organization and personnel management module is used to maintain the organizational structure tree, personnel information, and role assignments for each client. The database connection management module is used to configure independent database connections for different client-micro-module combinations; The file storage management module is used to manage file storage sources, directory structure, file metadata, and access permissions. The message center module is used to receive and distribute business messages generated by the micro-modules to the corresponding users; The system supports seamlessly embedding micro-modules into the client's original system interface through micro-frontend technology, and automatically loading the corresponding configuration and permission context based on the passed client identifier.

7. The system for supporting multi-tenant sharing of railway business services as described in claim 6, characterized in that: The client micro-module management module stores the following information: client identifier string, module identifier string, module access address, and module R&D personnel information; the authorization relationship is achieved through the association between the client identifier string and the module identifier string.

8. The system for supporting multi-tenant sharing of railway business services as described in claim 6, characterized in that: The organizational tree in the personnel management module is a hierarchical organizational structure with the client identifier string as the root node; personnel roles are bound through the mapping relationship between personnel identifier strings and role identifier strings.

9. The system for supporting multi-tenant sharing of railway business services as described in claim 6, characterized in that: The file storage information in the file storage management module includes a file storage identifier string and a file storage connection string; the folder information includes a folder identifier string and its parent folder identifier string; and the file information includes a file identifier string, file name, and file size.

10. The system for supporting multi-tenant sharing of railway business services as described in claim 6, characterized in that: The system is developed using the same programming language, and each functional module uses a unified dependency version and interface contract through the service specification module to ensure compatibility and consistency in collaborative work between modules.

Images