Urban road network data resource directory generation method and system combined with business graph

Abstract

The application provides a kind of city road network data resource directory generation method and system combined with service atlas, it is related to city traffic data management technical field, first access city road network service association conduction source and road network basic data generate service data association conduction pool;Then, based on the service association conduction logic deduces the road network data association derivative relationship, forms data association derivative network;According to the dynamic adaptation of data association derivative network, the dynamic directory unit is constructed by combining road network data;Based on the service conduction attribute of dynamic directory unit, the association conduction link is generated;Finally, the dynamic directory unit and the association conduction link are integrated to form a closed-loop city road network data resource directory that can be dynamically updated, which effectively improves the management efficiency and utilization value of city road network data resources.

Description

Technical Field

[0001] This invention relates to the field of urban traffic data management technology, and more specifically, to a method and system for generating an urban road network data resource catalog that combines business maps. Background Technology

[0002] In today's increasingly complex and sophisticated urban traffic management environment, the efficient management and utilization of urban road network data resources has become crucial for improving urban traffic efficiency and optimizing traffic planning decisions. Urban road networks involve numerous functions, such as traffic flow monitoring, traffic signal control, public transportation scheduling, and road maintenance management. These functions are interconnected and mutually influential, collectively forming an organic whole for urban traffic operations.

[0003] Currently, the management of urban road network data resources mainly adopts the traditional static catalog method. This method typically categorizes and organizes data according to fixed dimensions such as data type and source, forming a relatively fixed data resource catalog. However, this static catalog has significant limitations. On the one hand, it cannot accurately reflect the complex relationships between different business operations, nor can it reflect the dynamic changes in road network data caused by the transmission of business processes. For example, changes in traffic flow monitoring data may affect traffic signal control decisions, but the traditional catalog cannot intuitively present these relationships. On the other hand, with the continuous development and innovation of urban traffic operations, new business demands are constantly emerging. The traditional static catalog struggles to adapt quickly to these changes, failing to update and adjust the data resource catalog in a timely manner. This leads to a disconnect between data management and actual business needs, reducing the efficiency of data resource utilization and impacting the effectiveness of urban traffic management. Summary of the Invention

[0004] In view of the aforementioned problems, and in conjunction with the first aspect of the present invention, embodiments of the present invention provide a method for generating a city road network data resource catalog that incorporates business maps, the method comprising:

[0005] Access the urban road network business association transmission source and road network basic data to generate a business data association transmission pool. The business association transmission source includes process association information and data request association information of various urban road network businesses.

[0006] Based on the business association transmission logic, the association and derivation relationships between road network data are derived for the business data association transmission pool, forming a data association and derivation network. The data association and derivation network reflects the dynamic association path of road network data as it is transmitted with the business.

[0007] Based on the data association and derivative network, the road network data combination corresponding to different business transmission paths is dynamically adapted to construct dynamic directory units. Each dynamic directory unit corresponds to a complete data support system for a business transmission path.

[0008] Based on the business transmission attributes of dynamic directory units, associated transmission links are generated between directory units, and the associated transmission links reflect the network data coordination relationship of different business transmission paths;

[0009] By integrating the dynamic catalog unit with the associated transmission link, a closed-loop urban road network data resource catalog is formed, which can be dynamically updated as business-related transmission changes.

[0010] Furthermore, embodiments of the present invention also provide a system for generating a city road network data resource catalog that combines business maps, including:

[0011] A processor; a machine-readable storage medium for storing machine-executable instructions of the processor; wherein the processor is configured to execute the above-described method for generating a city road network data resource catalog in conjunction with a service map by executing the machine-executable instructions.

[0012] Based on the above, by accessing the urban road network business association transmission source and generating a business data association transmission pool from basic road network data, the process association information and data demand association information of various urban road network businesses are integrated. Then, based on the business association transmission logic, the association and derivation relationships between road network data are deduced. The resulting data association derivation network can accurately reflect the dynamic association path of road network data as business transmission occurs, revealing the flow and change patterns of data under different business scenarios. Dynamic directory units are constructed based on the dynamic adaptation of road network data combinations corresponding to different business transmission paths according to the data association derivation network. Each dynamic directory unit can provide a complete data support system for a business transmission path. The association transmission links between directory units are generated based on the business transmission attributes of the dynamic directory units, reflecting the collaborative relationship of road network data in different business transmission paths and further strengthening the logical connection between data. Finally, the dynamic directory units and association transmission links are integrated to form a closed-loop urban road network data resource catalog. This urban road network data resource catalog can be dynamically updated as business association transmission changes, always maintaining a high degree of fit with actual business needs, effectively improving the management efficiency and utilization value of urban road network data resources. Attached Figure Description

[0013] Figure 1 This is a schematic diagram of the execution flow of the method for generating a city road network data resource catalog that combines business maps, provided in an embodiment of the present invention.

[0014] Figure 2 This is a schematic diagram of exemplary hardware and software components of the urban road network data resource catalog generation system that combines business maps, provided in an embodiment of the present invention. Detailed Implementation

[0015] The present invention will now be described in detail with reference to the accompanying drawings. Figure 1 This is a flowchart illustrating a method for generating an urban road network data resource catalog that combines business maps, according to an embodiment of the present invention. The following is a detailed description of this method for generating an urban road network data resource catalog that combines business maps.

[0016] Step S110: Connect the urban road network business association transmission source and road network basic data to generate a business data association transmission pool.

[0017] In the field of urban road network management, the business-related transmission sources encompass the process-related information and data request-related information of various business operations, including road network planning, traffic signal control, road maintenance, and public transport scheduling. The process-related information details the execution sequence, collaborative dependencies, and information interaction nodes between various business operations; the data request-related information clarifies the specific data requirements of each business operation during execution, such as data type, data precision, and data update frequency. Basic road network data includes physical attribute data of roads (such as road length, width, number of lanes, and pavement material), road ancillary facility data (such as traffic light locations and timing schemes, traffic sign and marking information, and street light distribution), traffic flow data (vehicle and pedestrian flow at different times on different road sections), and surrounding environmental data (such as building distribution, locations of key areas such as schools and hospitals).

[0018] During the access process, a connection must first be established with the urban traffic management department's business systems and databases through a dedicated data interface to ensure the stability and security of data transmission. For business-related transmission sources, structuring is required, converting unstructured business process documents and semi-structured collaborative rule tables into a unified, standardized data format for efficient subsequent processing and analysis. For road network infrastructure data, data cleaning is necessary to remove duplicate, abnormal, and missing values, ensuring data accuracy and completeness. After cleaning, the data is categorized and stored, and a data index is created for easy and quick querying and retrieval. Through these operations, the accessed and processed business-related transmission sources and road network infrastructure data are integrated into a unified data pool, namely the business data association transmission pool.

[0019] In the process of accessing urban road network business-related transmission sources and basic road network data, relevant laws and regulations are strictly followed. During data collection, sensitive data involving personal privacy (such as vehicle trajectory data and driver information for specific time periods and road sections) is processed using data anonymization techniques. Specifically, this includes hashing vehicle license plate information and anonymizing driver identity information to ensure that the data cannot be directly linked to any specific individual. Simultaneously, a data collection authorization mechanism is established. Formal data usage authorization agreements are signed with data providers (such as traffic management departments, road maintenance units, and third-party data service providers) to clearly define the scope, purpose, duration, and rights and obligations of both parties. The agreements specifically state that the data is only used for the construction and management of the urban road network data resource catalog and may not be used for any other unauthorized purposes. For basic road network data obtained from public channels (such as publicly available road planning documents and traffic flow statistics bulletins), the data source undergoes compliance review to ensure the legality of the data acquisition method. During data transmission, end-to-end encryption technology (such as SSL / TLS protocols) is used to encrypt the data to prevent it from being stolen or tampered with during transmission. In the data storage phase, encrypted databases are used to store sensitive data, and strict access controls are implemented. Only authorized administrators can access sensitive data through multi-factor authentication (such as password + dynamic password). Furthermore, a data security audit mechanism is established to log the entire process of data collection, transmission, storage, and use. These logs are audited regularly to promptly identify and address data security risks, ensuring that the entire data access process complies with legal and regulatory requirements, effectively protecting data privacy and security, and preventing data leaks.

[0020] Step S120: Based on the business association transmission logic, deduce the association and derivation relationships between road network data for the business data association transmission pool to form a data association and derivation network.

[0021] In this embodiment, after obtaining the business data association transmission pool, it is necessary to deduce the association and derivative relationships between road network data based on the business association transmission logic, thereby forming a data association and derivative network. The business association transmission logic refers to the inherent transmission order, data flow rules, and conditions for establishing association relationships among various business processes in urban road network operations. For example, in the daily maintenance of urban road networks, when damage to a road surface is discovered, it is necessary to first collect road surface damage data, then assess the maintenance level based on the degree of damage, then allocate appropriate maintenance resources for repair, and finally conduct acceptance testing after repair. This process involves a clear business association transmission logic. By applying this logic, various types of road network data in the business data association transmission pool are analyzed and mined to identify the implicit association relationships between data that arise with business transmission, thereby constructing a data association and derivative network that reflects the dynamic association paths of road network data.

[0022] Step S121: Access the business process transmission nodes and transmission rules in the urban road network business association transmission source, extract the associated data requests and transmission direction information of each business process transmission node, and form business transmission node characteristics.

[0023] Next, to accurately deduce the relationships between road network data, a thorough analysis of the business transmission sources within the accessed urban road network is necessary. Specifically, this involves identifying the business process transmission nodes and rules. Business process transmission nodes are key links in the business process. For example, in the road maintenance business process, nodes such as "road surface damage data collection," "maintenance level assessment," and "maintenance resource allocation" are all business process transmission nodes. Transmission rules define how business transmission occurs between nodes; for example, "maintenance level assessment can only be conducted after road surface damage data collection is completed" is a transmission rule. Then, for each business process transmission node, its associated data requirements and transmission direction information are extracted. Associated data requirements refer to the data types and specific requirements needed by the node during business processing. Taking the "maintenance level assessment" node as an example, its associated data requirements might include data such as the location, area, and depth of road surface damage. Transmission direction information indicates the direction in which the business process is transmitted from this node to the next node; for example, the transmission direction of the "maintenance level assessment" node points to the "maintenance resource allocation" node. Organizing and structuring the extracted information forms the business transmission node characteristics, which include node identifier (used to uniquely distinguish different nodes), data request type (clearly indicating what type of data is needed), transmission target node identifier (indicating the next node in the business transmission), and other content.

[0024] Step S122: Retrieve data attribute descriptions, data application scenario scope, and data association interface information from the road network basic data to generate basic road network data features.

[0025] While extracting features from business transmission nodes, it's also necessary to retrieve relevant information from the road network infrastructure data pool to generate basic road network features. Road network infrastructure data contains a wide variety of information. Data attribute descriptions explain the inherent characteristics of the data; for example, traffic flow data attributes include collection time, collection location, and vehicle type classification. Data application scenarios clarify which business scenarios the data can be applied to; for example, traffic flow data for a certain road segment can be applied to traffic signal timing optimization and road congestion warning scenarios. Data association interface information provides ways to interact and associate with other data; for example, traffic flow data can be associated with traffic event data through specific API interfaces. When generating basic road network features, it's crucial to ensure that their dimensions correspond to the data request types of the business transmission node features. In other words, if the data request types in the business transmission node features involve dimensions such as road physical attributes, traffic flow, and traffic events, then the basic road network features should also include information from these dimensions to facilitate effective matching and association analysis later.

[0026] Step S123: Access the business association transmission logic model, which includes the definition of the sequential transmission order of business process transmission nodes, the matching rules between data requests and road network data characteristics, and the triggering conditions derived from the association relationship.

[0027] In this embodiment, to derive the derivation of road network data association relationships based on business association transmission logic, a dedicated business association transmission logic model needs to be accessed. This model is constructed based on the actual situation and rules of urban road network business, and includes the definition of the sequential transmission order of business process transmission nodes. This ensures that business processes are transmitted in the correct order, avoiding logical confusion. For example, in the road construction business process, the sequential order of nodes must be "project initiation," "planning and design," "construction," and "completion and acceptance," and cannot be reversed. The matching rules between data requirements and road network data characteristics are used to determine whether the road network data meets the data requirements of the business transmission nodes. For example, when a business transmission node requires data on "traffic flow exceeding a certain value," the matching rules will specify how to determine this based on the traffic flow attribute in the road network data characteristics. The triggering conditions for the derivation of association relationships specify under what circumstances new association relationships between road network data can be derived. For example, when the traffic flow data of two adjacent roads both show abnormal growth in the same period, it may trigger the derivation of a traffic congestion transmission association relationship between them.

[0028] Step S124: Input the business transmission node features into the business association transmission logic model, and filter out the basic road network data features corresponding to the data demand type of each business transmission node through the model's built-in matching rules, and output the candidate road network data feature set corresponding to each business transmission node.

[0029] After integrating the business-related transmission logic model, the previously generated business transmission node features are input into the model. The model then uses built-in matching rules to compare and filter the data request types in the business transmission node features against the basic road network data features. For example, for the "maintenance level assessment" business transmission node, its data request types include road surface damage location, area, and depth. The model will filter the corresponding road damage detection data attribute features from the basic road network data features based on these types, such as the road surface damage location coordinates, damage area measurement, and damage depth detection features for a specific road segment. After filtering, a candidate road network data feature set can be output for each business transmission node. This candidate road network data feature set contains all the basic road network data features that may satisfy the data request of that node.

[0030] Step S125: Based on the candidate road network data feature set, extract the corresponding road network data entities, parse the attribute association items and application scenario overlap areas of the road network data entities, and determine the data association seeds.

[0031] Next, for each business transmission node, the candidate road network data feature set is used to extract the road network data entities contained therein. A road network data entity refers to a road network data unit that has practical significance and can exist independently. For example, the relevant data of a specific road can constitute a road network data entity, as can the timing data of a traffic light. After extracting the road network data entities, their attribute associations and overlapping application scenarios need to be analyzed. Attribute associations refer to the interrelationships between different road network data entities in terms of attributes. For example, there is a relationship between the road length attribute and the road travel time attribute; the longer the road, the longer the travel time. Overlapping application scenarios refer to the overlapping parts of the business scenarios in which multiple road network data entities can be applied. For example, both the road traffic flow data entity and the traffic light timing data entity can be applied to traffic congestion management scenarios; this scenario is their overlapping application scenario area. By analyzing the overlapping areas of attribute association items and application scenarios, we can determine the data association seed, which is the initial direct association between road network data entities. For example, the association between traffic flow data entities and traffic signal timing data entities in the traffic congestion management scenario can serve as a data association seed.

[0032] Step S126: Using the data association derivation algorithm, starting from the data association seed, and following the business transmission direction, deduce the adjacent road network data entities that have application scenario connections or complementary attributes with the current road network data entities, thereby expanding the scope of data association.

[0033] Step S1261: Input the road network data entity attribute information and application scenario information in the data association seed into the feature input layer of the data association derivation algorithm for structured processing. After generating identifiable feature vectors, input them into the association rule mining module of the data association derivation algorithm. Based on the preset attribute association rules and scenario connection rules, mine the potential association attributes and potential application scenarios of the current road network data entities.

[0034] When expanding the scope of data association, the information in the data association seeds must first be processed. The attribute information of the road network data entities, such as road material, number of lanes, and design speed, as well as application scenario information, such as whether it is for traffic flow monitoring or road maintenance, are input into the feature input layer of the data association derivation algorithm. The feature input layer performs structured processing on the above information, converting unstructured text descriptions into structured data formats, thereby generating a feature vector that the algorithm can recognize. This feature vector contains key information about attributes and scenarios. Next, this feature vector is input into the association rule mining module, which pre-sets various attribute association rules and scenario connection rules. For example, attribute association rules may stipulate that when the road material is asphalt, its maintenance cycle is usually different from that of concrete roads; scenario connection rules may indicate that traffic flow monitoring scenarios are often associated with traffic signal timing scenarios. Through these rules, potential association attributes that may exist in the current road network data entities are mined, such as the number of lanes on a road potentially being associated with the maximum carrying capacity of traffic flow, and potential application scenarios, such as traffic congestion warning scenarios potentially extending from traffic flow monitoring scenarios.

[0035] Step S1262: Based on potential association attributes, retrieve other road network data entities with the same or complementary attributes in the road network basic data to form a potential association data candidate set, which includes data entity identifiers and attribute matching points.

[0036] After obtaining the potential related attributes, these attributes are used as search criteria to search the basic road network data. Other road network data entities with the same or complementary attributes as the current data entities are identified. For example, roads made of asphalt material might share the same attribute; complementary attributes could be traffic flow data from one road and traffic signal timing data from another. These attributes complement each other to achieve traffic optimization. The retrieved data entities are then integrated to form a potential related data candidate set. In this candidate set, each data entity contains its unique identifier and attribute matching points with the current data entity, thus revealing which attributes each candidate entity is associated with.

[0037] Step S1263: Based on potential application scenarios, calculate the similarity or correlation between the application scenarios of other road network data entities in the road network basic data and potential application scenarios, and filter out data entities with similarity or correlation exceeding a preset threshold to supplement the potential related data candidate set.

[0038] In addition to attribute-based retrieval, the relevance of application scenarios also needs to be considered. Based on the identified potential application scenarios, the similarity or relevance between the application scenarios of other road network data entities and these potential application scenarios is calculated. For example, if the potential application scenario is traffic congestion management, then the similarity between the application scenarios of other data entities and the traffic congestion management scenario is calculated. Similarity or relevance can be calculated by analyzing keywords in the scenario description and the business processes involved. When the similarity or relevance exceeds a preset threshold, it indicates a strong relevance between the data entity and the current road network data entity in terms of application scenario. This data entity is then selected and added to the potential related data candidate set, making the candidate set more comprehensive.

[0039] Step S1264: Based on the number of attribute matching points and the scope of scene overlap, generate a close association description between each data entity in the potential associated data candidate set and the current road network data entity. Based on the close association description, sort the data entities in the potential associated data candidate set and select the data entity with more comprehensive association dimensions corresponding to the close association description as the priority association object.

[0040] For each data entity in the potential candidate set of related data, its correlation with the current road network data entities needs to be evaluated. Based on the number of attribute matching points obtained earlier (e.g., 3 attribute matching points) and the overlap range of scenarios (e.g., 50% overlap in a traffic management scenario), a strong correlation description is generated. This strong correlation description may include the number of attribute matches, the proportion of scenario overlap, and the matching status of key attributes and scenarios. Then, based on these strong correlation descriptions, the data entities in the candidate set are ranked. The ranking principle is to prioritize data entities with more comprehensive correlation dimensions; that is, data entities with more matching and overlap in attributes and scenarios are given priority and selected as priority correlation objects.

[0041] Step S1265: Extract the complete attribute information and application scenario description of the priority associated object, and verify its association with the corresponding information of the current road network data entity. The association verification process is executed based on the matching rules of the business association transmission logic model.

[0042] After selecting priority association objects, their association must be verified. Complete attribute information for these priority association objects is extracted, including all attribute items and their values, as well as a detailed description of the application scenario. This information is then compared and verified with the corresponding information of the current road network data entities. The association verification process strictly follows the matching rules in the business association transmission logic model, such as checking whether attribute values ​​meet preset matching conditions and whether the application scenarios have a logically reasonable connection. Only priority association objects that pass verification can be determined as true associated data entities.

[0043] Step S1266: Record the association basis, association attributes, and scenario connection points between the priority associated object and the current road network data entity to form a new association derivative record. The new association derivative record should maintain the same format as the original data association derivative record.

[0044] After completing the association verification, the association information needs to be recorded. This includes recording the basis for the association between the priority association object and the current road network data entity, such as which attribute matches and scenario overlaps led to the association; the specific attributes that are associated; and the scenario connection points, detailing how they are connected in the application scenario. This information forms a new association-derived record. To ensure data consistency and ease of subsequent processing, the new association-derived record must maintain the same format as the original data association-derived record, including the starting data identifier, target data identifier, and the basis for association derivation.

[0045] Step S1267: Starting from the priority associated object, repeat the process of attribute mining, scene filtering, association calculation, and record verification to continuously expand the scope of data association and form a chain-like association derivative path.

[0046] The verified priority associated objects are used as new current road network data entities, which are the new starting points. The entire process described above—from mining potential associated attributes and scenarios, to screening candidate sets, calculating close association descriptions, verifying associations, and recording association-derived records—is repeated. In this way, expansion is continuously initiated from new associated data entities, extending like a chain, thereby continuously expanding the scope of data associations and forming a chain-like association-derived path.

[0047] Step S1268: Integrate all chain-related derivative paths and corresponding derivative records to expand the scope of data association.

[0048] The expansion process stops when the chain-like derivative paths expand to a certain extent, or when there are no more matching associated data entities. Then, all formed chain-like derivative paths and their corresponding associated records are integrated. The integrated information comprehensively reflects all relationships that have expanded from the initial data association seed, thus completing the expansion of the data association scope.

[0049] Step S127: Record the business transmission basis, data attribute association points, and scenario connection logic for each association derivation, forming a data association derivation record.

[0050] During the data association derivation algorithm's association process, key information for each derivation needs to be recorded in detail, forming a data association derivation record. Each record includes a starting data identifier (identifying the starting data entity of the derivation process), a target data identifier (identifying the target data entity obtained through derivation), and the basis for association derivation. The basis for association derivation further includes business transmission basis, data attribute association points, and scenario connection logic. The business transmission basis explains which business transmission rule or process sequence this derivation is based on; the data attribute association points clarify the specific association content between the two data entities in terms of attributes; and the scenario connection logic describes how they are connected in application scenarios. For example, in the process of deriving from the maintenance resource allocation data entity to the maintenance construction progress data entity, the business transmission basis is "maintenance construction needs to be carried out and progress tracked after maintenance resource allocation is completed," the data attribute association point is "the type and quantity of allocated resources are related to the resource consumption in the construction progress," and the scenario connection logic is "the end of the maintenance resource allocation scenario is the beginning of the maintenance construction progress scenario."

[0051] Step S128: Based on all data association and derivative records, construct the basic architecture of the data association and derivative network, wherein road network data entities are defined as network nodes and filled with complete data attribute information, and association and derivative relationships are defined as network edges and filled with the basis for association derivation.

[0052] After completing multiple association and derivation derivations and forming a sufficient number of data association and derivation records, the basic architecture of the data association and derivation network can be constructed. First, each road network data entity is defined as a node in the network. The node is filled with the complete attribute information of the data entity, such as its identifier, name, detailed attribute description, and application scenario. This gives the network nodes rich information, facilitating subsequent analysis and application. Then, the association and derivation relationships reflected in the data association and derivation records are defined as edges in the network. Each edge connects two road network data entity nodes with an association relationship, and the corresponding association derivation basis is filled in the edge, namely the business transmission basis, data attribute association points, and scenario connection logic recorded earlier. Through the above method, the scattered data association and derivation records are integrated into a structured network architecture, initially forming the basic structure of the data association and derivation network.

[0053] Step S129: Add a correlation propagation strength description and a propagation direction identifier to each network edge of the data association derivative network. The correlation propagation strength description is generated based on the degree of data dependence in business propagation, and the propagation direction identifier is consistent with the business process propagation direction.

[0054] To ensure the data association network more comprehensively and accurately reflects the relationships between road network data, it is necessary to add a correlation transmission strength description and a transmission direction identifier to each network edge. The correlation transmission strength description indicates the tightness of the relationship between two road network data entities, and it is generated based on the degree of data dependence in business transmission. If a change in one data entity significantly affects another, then the correlation transmission strength between them is high. For example, in road maintenance operations, the maintenance level assessment data entity is highly dependent on the pavement damage data entity, and the accuracy of the pavement damage data directly affects the maintenance level assessment result; therefore, the correlation transmission strength description between them will be strong. The transmission direction identifier clarifies the direction of the correlation transmission. This transmission direction must be consistent with the direction of business process transmission to ensure that the network accurately reflects the flow direction of data in the business process.

[0055] Step S1210: Integrate network nodes, network edges, descriptions of association transmission strength, and transmission direction identifiers to form a data association derivative network. This data association derivative network is used to dynamically present the association derivative paths and dependencies of road network data as it is transmitted with services.

[0056] Finally, the previously constructed network nodes, network edges, and added association transmission strength descriptions and transmission direction identifiers are integrated to form a data association derivation network. This data association derivation network can dynamically present the association derivation paths and dependencies of road network data as business transmission occurs. Through this data association derivation network, users can see how road network data entities are associated and derived along the business transmission direction, starting from the initial data association seed, as well as the degree of dependency and transmission direction between different data entities.

[0057] Step S130: Based on the data association and derived network, dynamically adapt the road network data combination corresponding to different business transmission paths and construct dynamic directory units.

[0058] After forming a data association and derivation network, this network can be used to dynamically adapt road network data combinations corresponding to different business transmission paths, thereby constructing dynamic catalog units. Different urban road network services have different business transmission paths; for example, road maintenance services have their specific transmission paths, and traffic signal optimization services also have their unique transmission paths. Each business transmission path requires specific road network data combinations for support. The data association and derivation network demonstrates the relationships and transmission paths between road network data, thus allowing for the selection of matching road network data for each business transmission path based on this network. Through dynamic adaptation, it is ensured that the selected data combinations accurately reflect the changing needs of the business transmission path, and the data combinations can be updated accordingly when the business transmission path is adjusted. Organizing the adapted road network data combinations according to a certain structure and rules constructs dynamic catalog units, with each dynamic catalog unit corresponding to a complete data support system for a business transmission path.

[0059] Step S131: Parse the transmission direction identifier and service transmission node association information in the data association derivative network, extract all independent service transmission paths, and each service transmission path contains continuous service transmission nodes and corresponding road network data nodes.

[0060] In this embodiment, the first step in constructing the dynamic directory unit is to parse the data association derivative network to extract all independent business transmission paths. The transmission direction identifiers in the data association derivative network clearly define the transmission direction of data and business, while the business transmission node association information illustrates the connection relationships between various business transmission nodes. By analyzing the above information, different business transmission paths can be identified. An independent business transmission path refers to a complete business process chain that exists relatively independently in the business process and does not intersect or overlap with other paths. For example, in urban road network management, there may be an independent business transmission path such as "road planning and design -> road construction -> road completion acceptance -> road routine maintenance," and another independent business transmission path such as "traffic flow monitoring -> traffic signal timing optimization -> traffic operation effect evaluation." When extracting each business transmission path, it is necessary to include its continuous business transmission nodes and corresponding road network data nodes. Business transmission nodes are key links in the business process, such as the "road planning and design" node and the "traffic flow monitoring" node in the above path; road network data nodes are the specific road network data entities that support these business transmission nodes. For example, the road network data nodes corresponding to the road planning and design node may include topographic data nodes and land use data nodes of the planning area.

[0061] Step S132: Based on the business objective description of each business transmission path, extract the core business demand features of that business transmission path. The core business demand features include the key data types for business implementation, data usage order requirements, and data association strength thresholds.

[0062] For each extracted independent business transmission path, its business objective description needs to be clearly defined. This description clarifies the ultimate business purpose the path aims to achieve. For example, the business objective description for the path "traffic flow monitoring -> traffic signal timing optimization -> traffic operation effect evaluation" might be "to improve road traffic efficiency and reduce traffic congestion by optimizing traffic signal timing." Based on this business objective description, core business demand characteristics are extracted. Key data types refer to the types of data necessary to achieve the business objective. For the aforementioned traffic signal timing optimization path, key data types might include real-time traffic flow data at each intersection, average vehicle speed data, and traffic signal cycle duration data. The data usage order requirement specifies the order in which these key data are used in the business process. For example, real-time traffic flow data must be acquired first, then traffic signal timing optimization can be performed based on this data, and finally, the traffic operation effect can be evaluated based on the optimized timing scheme. The data correlation strength threshold sets the minimum strength requirement for the correlation between different data. Only data with a correlation strength reaching or exceeding this threshold can be included in the data combination of the business transmission path to ensure that the correlation between data is sufficient to support the achievement of the business objective.

[0063] Step S133: Traverse the road network data nodes corresponding to the business transmission path in the data association derivative network, extract the complete attribute information and association transmission strength description of each road network data node, and form a path data feature set.

[0064] After clarifying the core business requirements, it is necessary to traverse the road network data nodes corresponding to the current business transmission path in the data association derivative network. The data association derivative network contains a large number of road network data nodes. By using transmission direction identifiers and business transmission node association information, those road network data nodes related to a specific business transmission path can be located. For each located road network data node, its complete attribute information needs to be extracted. This information includes the data name, source, collection time, data format, and accuracy. For example, the complete attribute information of a traffic flow data node might include "traffic flow data on main roads during morning peak hours," "collected by traffic monitoring equipment," "collection time is 7:00-9:00 daily," "data format is CSV," and "accuracy is ±5%." Simultaneously, a correlation transmission strength description for each road network data node needs to be extracted. This description reflects the tightness of the relationship between the node and other nodes. Integrating the extracted complete attribute information and correlation transmission strength descriptions of all road network data nodes forms the path data feature set.

[0065] Step S134: Based on the key data types in the core business requirements, select road network data nodes that meet the requirements from the path data feature set to form an initial data combination candidate set.

[0066] The path data feature set contains a large amount of road network data node information related to the business transmission path. Next, it needs to be filtered based on the key data types in the core business requirements. The filtering process, according to the definition of key data types, checks each road network data node in the path data feature set to see if it belongs to the required key data type. For example, if the key data types include "real-time traffic flow data" and "traffic signal cycle duration data," then only road network data nodes whose attribute information indicates they belong to these two types will be selected in the path data feature set. Through the above filtering, an initial data combination candidate set is formed, which contains all data nodes that may meet the key data requirements of the business transmission path.

[0067] Step S135: Based on the data usage order requirements in the core business demand characteristics and combined with the transmission direction identifier of the data association derivative network, the road network data nodes in the initial data combination candidate set are arranged in order to generate an ordered data sequence.

[0068] Step S1351: Extract the data usage sequence requirements from the core business requirements features, break down the data usage sequence requirements into multiple data usage stages, each data usage stage corresponds to a key business link in the business transmission path, and determine the core data requirements for each data usage stage.

[0069] When sequentially arranging road network data nodes in the initial data combination candidate set, the order of data usage requirements must first be clearly defined. These requirements are extracted from the core business needs and then broken down into multiple data usage stages. Each stage corresponds to a key business link in the business transmission path. For example, in the road maintenance business transmission path, the data usage order requirements might be broken down into stages such as "road surface data collection," "maintenance plan formulation," "maintenance construction," and "maintenance acceptance," each a key link in the business path. Simultaneously, core data requirements are determined for each data usage stage. For instance, the core data requirements for the "road surface data collection stage" might be data such as the location, area, and degree of road surface damage.

[0070] Step S1352: Parse the transmission direction identifier of the road network data node corresponding to the initial data combination candidate set in the data association derivative network, and determine the transmission order of each road network data node in the business transmission path.

[0071] In the data association and derivative network, each road network data node has a transmission direction identifier, which indicates the direction of data flow during the business transmission process. The transmission direction identifier of each road network data node in the initial data combination candidate set is parsed, and the transmission sequence of each node in the business transmission path is determined based on the direction indicated by the identifier. For example, in the transmission direction of "road surface data acquisition node → maintenance plan formulation node → maintenance construction node", the transmission sequence of the road surface data acquisition node is 1, the maintenance plan formulation node is 2, the maintenance construction node is 3, and so on, to determine the position of each node.

[0072] Step S1353: Establish the correspondence between the data usage stage and the sequence of transmission, so that each data usage stage can be matched with the road network data node corresponding to the transmission direction identifier.

[0073] Each data usage stage after decomposition is mapped to a predetermined transmission sequence. Based on the sequence of key business processes in the business transmission path, each data usage stage is matched to a corresponding transmission sequence range, ensuring that all road network data nodes belonging to that data usage stage are positioned within their respective transmission sequence positions. For example, if the "road surface data collection stage" corresponds to transmission sequence positions 1-5, then all road network data nodes belonging to this stage should be positioned within the range of 1-5.

[0074] Step S1354: Based on the correspondence, the road network data nodes in the initial data combination candidate set are initially sorted according to the order of data usage stages to form an initial ordered sequence. The correlation transmission strength description of each road network data node in the initial ordered sequence is extracted, the close correlation description between adjacent road network data nodes is analyzed, and the arrangement order of nodes in the initial ordered sequence is adjusted so that the nodes with more comprehensive correlation dimensions corresponding to the close correlation description are arranged adjacently.

[0075] Based on the established correspondence between data usage stages and transmission sequence, the road network data nodes in the initial data combination candidate set are initially sorted according to the chronological order of data usage stages, forming an initial ordered sequence. Next, the correlation transmission strength description of each road network data node in this sequence is extracted, such as strong correlation, medium correlation, and weak correlation. The close correlation descriptions between adjacent nodes are analyzed to understand their comprehensiveness in correlation dimensions such as attributes and application scenarios. If the close correlation descriptions of two adjacent nodes show that their correlation dimensions are not comprehensive enough, but their correlation dimensions with other non-adjacent nodes are more comprehensive, the arrangement order of these nodes is adjusted so that nodes with more comprehensive correlation dimensions are arranged adjacently to enhance the correlation between data nodes in the sequence.

[0076] Step S1355: Analyze the data application scenario activation conditions of each road network data node to ensure that the application scenario activation conditions of the sorted road network data nodes are consistent with the process advancement logic of the business transmission path.

[0077] Each road network data node has its own data application scenario initiation conditions, that is, under what circumstances will the data from that node be applied. These initiation conditions are analyzed, and then the initiation conditions of the sorted road network data nodes' application scenarios are checked to ensure they conform to the workflow logic of the business transmission path. For example, if the business transmission path requires that maintenance plan formulation can only begin after road surface data collection is completed, then the initiation conditions of the data nodes related to maintenance plan formulation should be set to occur after road surface data collection is completed, ensuring that the node initiation order aligns with the business workflow logic.

[0078] Step S1356: Extract the data access dependencies of road network data nodes. Access to some road network data nodes requires the output of other road network data nodes as a prerequisite. Further adjust the sequence order based on the data access dependencies.

[0079] Data access dependencies exist between road network data nodes; some nodes require the output of other nodes for data access. For example, the data access of the maintenance plan evaluation node may require the maintenance plan content output by the maintenance plan formulation node as a prerequisite. These data access dependencies are extracted, and the sequence order is further adjusted accordingly. The nodes that are depended upon are placed before the dependent nodes to ensure that the necessary prerequisite data exists when accessing the dependent nodes, thus ensuring smooth data access.

[0080] Step S1357: Compare and verify the adjusted sequence with the data usage order requirements in the core business requirements. If there is any inconsistency, adjust the sequence again according to the data usage order requirements until the sequence order is consistent with the data usage order requirements.

[0081] After the above adjustments, the resulting sequence will be compared and verified in detail with the data usage order requirements in the core business requirements. The order of data nodes in the sequence will be checked to ensure it fully conforms to the specified order in the data usage order requirements. If any inconsistencies are found, such as a reversed node order in a certain data usage stage, the sequence will be readjusted according to the data usage order requirements. This process may need to be repeated multiple times until the sequence order is completely consistent with the data usage order requirements.

[0082] Step S1358: Record all the basis for adjustments during the sequence arrangement process, including the basis for initial sorting, adjustments based on closely related descriptions, adjustments based on application scenario initiation conditions, adjustments based on data access dependencies, and further adjustments based on comparative verification, to form a sequence arrangement description.

[0083] Throughout the sequence arrangement process, the basis for each adjustment must be recorded. This includes the correspondence between the data usage stage and the order of transmission during the initial sorting; the specific correlation dimension analysis results when adjusting based on close associations; the correspondence between the start conditions and business process logic when adjusting based on application scenario start conditions; the details of dependencies when adjusting based on data access dependencies; and inconsistencies discovered and adjustment methods when making further adjustments based on comparison and verification. These bases are compiled into a sequence arrangement description to facilitate subsequent understanding and tracing of the sequence order.

[0084] Step S1359: Integrate the adjusted road network data node sequence and sequence arrangement description to generate an ordered data sequence. The ordered data sequence is used to meet the order requirements and association requirements of data use in the business transmission path.

[0085] Finally, the road network data node sequence, which has undergone multiple adjustments and comparative verifications, is integrated with the sequence arrangement description to form the final ordered data sequence. The data nodes in this ordered data sequence are arranged according to the order in which data is used in the business transmission path, and the relationships between the nodes are close and reasonable, meeting the requirements for the order and association of data use during business transmission.

[0086] Step S136: Based on the data association strength threshold in the core business demand characteristics, filter out road network data nodes in the ordered data sequence whose association transmission strength description does not meet the requirements, optimize the integrity and association of the ordered data sequence, and extract the unique identifier, data access address, data update cycle and data format description of each road network data node in the optimized ordered data sequence to form a set of data element information.

[0087] After generating the ordered data sequence, it needs to be optimized to further improve the quality of the data combination. The optimization is based on the data association strength threshold in the core business requirement characteristics. The data association strength threshold specifies the minimum strength standard of the association relationship between data nodes. For each road network data node in the ordered data sequence, it is checked whether the association transmission strength description with the preceding and following nodes reaches the threshold. If the association transmission strength description of a node does not meet the requirements, it means that the node has a weak association with other nodes, which may affect the smooth progress of the business transmission path, so it needs to be filtered out. Through the filtering operation, the integrity and association of the ordered data sequence are optimized to ensure that there is a strong association between the data nodes in the sequence. After optimization, the key meta-information of each road network data node is extracted, including unique identifier (used to uniquely identify the node), data access address (indicating how to obtain the data), data update cycle (indicating the frequency of data updates), data format description (describing the data storage format), etc. The above meta-information is integrated together to form a data meta-information set.

[0088] Step S137: Based on the data element information set, add a business transmission path identifier, a node location identifier in the path, and a data association dependency identifier to each road network data node in the ordered data sequence. The business transmission path identifier, node location identifier in the path, and data association dependency identifier are consistent with the characteristics of the business transmission path.

[0089] After obtaining the set of data metadata, additional identification information needs to be added to each road network data node in the ordered data sequence to better manage and apply the data nodes. This identification information includes business transmission path identifiers, node location identifiers within the path, and data dependency identifiers. The business transmission path identifier indicates the business transmission path to which the data node belongs, avoiding confusion between data nodes on different paths. The node location identifier within the path clarifies the specific position of the data node in the ordered data sequence, such as the first node, the second node, etc. The data dependency identifier indicates which other data nodes the data node depends on, and which data nodes depend on the data node. The settings of these identifiers must be consistent with the characteristics of the business transmission path; for example, the business transmission path identifier should correspond to the unique name or number of the path, and the location identifier should reflect the order in which the data is used.

[0090] Step S138: Integrate the ordered data sequence, data element information set, business transmission path identifier, node position identifier in the path, and data association dependency identifier to form a path-specific data combination.

[0091] Next, the previously obtained ordered data sequence, data element information set, and various added identifiers are integrated to form a path-specific data assembly. The integration process organizes this information according to a specific structure, ensuring that the path-specific data assembly reflects the data required for the business transmission path. For example, the ordered data sequence can serve as the main framework, with corresponding data element information and various identifiers attached to each data node, thus forming a data assembly specifically designed to serve a particular business transmission path.

[0092] Step S139: Encapsulate the path-specific data combination according to a unified directory unit structure, supplement the business transmission adaptation instructions and associated data calling rules of the path-specific data combination, and form a dynamic directory unit. The dynamic directory unit is used to achieve adaptive adjustment of the data combination as the business transmission path changes.

[0093] Finally, the path-specific data assembly is encapsulated to form a dynamic directory unit. The encapsulation uses a unified directory unit structure to ensure that all dynamic directory units have a consistent format and organization, facilitating management and use. During the encapsulation process, it is also necessary to supplement the business transmission adaptation specifications and associated data retrieval rules for the path-specific data assembly. The business transmission adaptation specifications explain how the data assembly adapts to the corresponding business transmission path, including the correspondence between data and business steps, and the role of data in the business process; the associated data retrieval rules specify how to call the data in the data assembly and how the data interacts with each other. Through encapsulation and supplementary specifications, a complete dynamic directory unit is formed, which can automatically adjust the data composition within it according to changes in the business transmission path.

[0094] Step S140: Based on the business transmission attributes of dynamic directory units, generate the associated transmission links between directory units. The associated transmission links reflect the network data collaboration relationship of different business transmission paths.

[0095] After constructing the dynamic directory units, it is necessary to generate the interconnected transmission links between these units based on their business transmission attributes. The business transmission attributes of a dynamic directory unit reflect the characteristics of its respective business transmission path, data requirements, and its association with other businesses. Different dynamic directory units may correspond to different business transmission paths, but these paths often have collaborative relationships. For example, the road maintenance business transmission path and the traffic management business transmission path need to work together during road construction to reduce the impact of construction on traffic. The interconnected transmission links between directory units are used to embody these collaborative relationships. They connect different dynamic directory units, enabling the sharing and interaction of road network data and ensuring that various businesses can operate collaboratively and efficiently.

[0096] Step S141: Extract the business transmission path identifier, core business demand characteristics, and road network data node identifier in the data combination of each dynamic catalog unit to form a catalog unit transmission feature set.

[0097] To generate the interconnected transmission links between directory units, it is first necessary to extract key information from each dynamic directory unit, forming a directory unit transmission feature set. This key information includes: a business transmission path identifier, which uniquely identifies the business transmission path to which the dynamic directory unit belongs; core business demand characteristics, reflecting the core data requirements and objectives of the business transmission path; and road network data node identifiers within the data assembly, clarifying the specific road network data nodes included in the dynamic directory unit. By extracting this information, the characteristics and requirements of each dynamic directory unit can be comprehensively understood. Integrating this information together constitutes the directory unit transmission feature set.

[0098] Step S142: Based on the set of transmission features of directory units, analyze the overlapping areas of core business demand features of different dynamic directory units, identify the directory unit groups with business collaboration needs, and determine the business collaboration needs based on the connection relationship of business processes or data sharing needs.

[0099] After obtaining the set of transmission characteristics for directory units, the core business demand characteristics of different dynamic directory units are analyzed to identify overlapping areas. Overlapping areas of core business demand characteristics mean that different business transmission paths share common data requirements, which often forms the basis for business collaboration. For example, the core business demand characteristics of road maintenance and traffic management transmission paths may overlap in terms of "traffic flow data for construction sections," because road maintenance construction affects traffic flow, while traffic management requires developing plans based on traffic flow data. Based on these overlapping areas, directory unit groups with business collaboration needs can be identified. The determination of business collaboration needs is mainly based on the connection relationship of business processes (such as the need for traffic restoration and diversion after maintenance construction) or data sharing needs (such as both businesses needing to use the same traffic flow data).

[0100] Step S143: Extract the road network data node identifiers from the data combination of all dynamic directory units in each directory unit group, and find the road network data node identifiers that are common to different directory units.

[0101] For identified directory unit groups with business collaboration needs, it is necessary to further extract the road network data node identifiers from the data combination of each dynamic directory unit. These identifiers represent the specific road network data nodes contained in the directory unit. By comparing the road network data node identifiers of different directory units, common road network data node identifiers can be identified. These common road network data node identifiers are key connection points for data sharing and association between different directory units. For example, two dynamic directory units may both contain "traffic flow data node identifiers for a certain road segment." The road network data nodes corresponding to this identifier are common to them and can serve as an important data bridge for collaboration between them.

[0102] Step S144: Based on the shared road network data node identifiers, extract the association transmission strength description and transmission direction identifier of the corresponding road network data entities, and determine the data transmission direction and close association description between different directory units.

[0103] After identifying common road network data node identifiers, it is necessary to extract the association transmission strength description and transmission direction identifier of the corresponding road network data entities from the data association derivative network. The association transmission strength description reflects the tightness of the association between the road network data entity and other data entities, while the transmission direction identifier indicates the direction of data transmission. Based on this information, the data transmission direction between different directory units can be determined, i.e., from which directory unit the data flows to which directory unit. For example, construction progress data from the maintenance business directory unit may flow to the traffic management business directory unit to support the formulation of traffic management plans. Simultaneously, based on the association transmission strength description, a description of the tightness of association between different directory units can be generated, indicating the degree of their collaborative relationship, such as "highly collaborative" or "moderately collaborative."

[0104] Step S145: Analyze the business transmission path identifier of the dynamic directory unit in each directory unit group, extract the sequential connection order or parallel collaboration relationship between the business transmission paths, and form the business transmission collaboration logic.

[0105] Beyond data-level correlations, it's also necessary to analyze the collaborative relationships of dynamic directory units within the directory unit group from a business perspective. By analyzing the business transmission path identifiers of dynamic directory units, we can identify the business transmission paths they belong to. Further research into the relationships between these business transmission paths allows us to extract their sequential connection order or parallel collaboration relationships. A sequential connection order means that one business transmission path can only begin after another is completed; for example, the "road construction" business transmission path must be completed before the "road completion acceptance" business transmission path can be initiated. A parallel collaboration relationship means that multiple business transmission paths occur simultaneously and cooperate with each other; for example, the "traffic signal optimization" business transmission path and the "public transportation dispatching" business transmission path may collaborate in parallel during morning rush hour to jointly ensure smooth traffic flow. After organizing these relationships, a business transmission collaboration logic is formed to guide the collaborative work between directory units.

[0106] Step S146: Using the shared road network data node identifier as the connection hub, and combining the data transmission direction, closely related description and business transmission collaboration logic, establish the initial association link between directory units. The initial association link includes the link start point identifier, the link end point identifier, and the connection basis.

[0107] Step S1461: Extract the complete attribute information, associated transmission strength description and transmission direction identifier of the road network data entity corresponding to the common road network data node identifier to form a hub data feature set.

[0108] When establishing initial connection links using shared road network data node identifiers as connecting hubs, it is first necessary to extract detailed information about the road network data entities corresponding to these shared node identifiers to form a hub data feature set. Complete attribute information includes the name, data type, collection method, and storage location of the road network data entity; the correlation transmission strength description indicates the degree of association between this entity and other data entities; and the transmission direction identifier indicates the direction of data transmission. For example, if a shared road network data node identifier corresponds to "traffic flow data entity of a certain arterial road," its complete attribute information might include data collection interval, number of covered lanes, etc., the correlation transmission strength description might be "strongly correlated with surrounding road network capacity data entities," and the transmission direction identifier might be "transmitted from traffic flow monitoring nodes to signal timing optimization nodes." Integrating the above information constitutes the hub data feature set.

[0109] Step S1462: Based on the hub data feature set, determine the associated dynamic directory unit corresponding to each shared road network data node identifier, and clarify the role of each associated dynamic directory unit in the link. The role is divided into data provider or data receiver.

[0110] Once the hub data feature set is obtained, the associated dynamic directory unit corresponding to each shared road network data node identifier is determined based on the road network data entity information within it. Each shared node identifier may be associated with multiple dynamic directory units; for example, "traffic flow data entity of a certain arterial road" may be associated with both "traffic signal optimization dynamic directory unit" and "road congestion warning dynamic directory unit." Then, the role of each associated dynamic directory unit in the link is clarified, i.e., data provider or data receiver. A data provider is a directory unit that provides data to the link, while a data receiver is a directory unit that obtains data from the link. For example, "traffic signal optimization dynamic directory unit" may be the data receiver of "traffic flow data entity of a certain arterial road," while "traffic flow monitoring dynamic directory unit" is the data provider for that data entity.

[0111] Step S1463: Based on the data transmission direction identifier, determine the data transmission direction between the associated dynamic directory units to form the transmission direction framework of the initial association link. The transmission direction framework includes the starting directory unit, the ending directory unit, and the transmission path direction.

[0112] Based on the transmission direction identifiers in the hub data feature set, the data transmission direction between associated dynamic directory units is determined. The transmission direction identifiers indicate from which entity the data is transmitted to which entity, thus determining the transmission path between associated dynamic directory units. For example, if the transmission direction identifier for "traffic flow data entity of a certain main road" is "transmission from traffic flow monitoring node to signal timing optimization node," then in the corresponding associated dynamic directory units, the "traffic flow monitoring dynamic directory unit" is the starting directory unit, and the "traffic signal optimization dynamic directory unit" is the ending directory unit. The transmission path direction is from the starting directory unit to the ending directory unit, thus forming the transmission direction framework of the initial associated link.

[0113] Step S1464: Based on the tightly associated description, add a connection strength attribute to the propagation direction frame of the initial associated link. The connection strength attribute directly corresponds to the tightly associated description.

[0114] The tightness of association description reflects the degree of association between road network data entities. Based on this, a connection strength attribute is added to the transmission direction frame of the initial association link. The connection strength attribute directly corresponds to the tightness of association description. If the tightness of association description is "strong association," the connection strength attribute value is high; if it is "weak association," the connection strength attribute value is low. For example, if the tightness of association description for "traffic flow data entity of a certain arterial road" and "signal timing optimization data entity" is "strong association," then in their corresponding initial association link transmission direction frame, the connection strength attribute is set to high to indicate that the data transmission of this link is of high importance.

[0115] Step S1465: Analyze the business transmission and collaboration logic, extract the key business nodes and data interaction requirements in the collaboration process, and transform the key business nodes and data interaction requirements into connection rules for the initial association link. The connection rules include the timing, content, and format of data interaction.

[0116] The business transmission and collaboration logic defines the methods and rules for collaboration between businesses. Analyzing this logic can extract key business nodes and data interaction requirements in the collaboration process. Key business nodes are important links in the collaboration process, such as the "signal timing scheme generation node"; data interaction requirements include the specific content and timing requirements of data interaction. These key business nodes and data interaction requirements are transformed into connection rules for the initial associated links. For example, if the "signal timing scheme generation node" requires traffic flow data, then the connection rules will stipulate that the data interaction time is before the start of the business at that node, the content is the latest traffic flow data, and the format is a specific structured data format.

[0117] Step S1466: Based on the transmission direction framework, connection strength attribute and connection rules of the initial association link, build the basic structure of the initial association link. The basic structure includes link identifier, participating directory unit identifier, transmission direction, connection strength and connection rules.

[0118] The basic structure of an initial association link is built by integrating its transmission direction framework (including start point, end point, and transmission path direction), connection strength attribute, and connection rules. The link identifier uniquely identifies the link; the participating directory unit identifier lists the start and end directory units in the link; the transmission direction specifies the data transmission direction; the connection strength reflects the link's importance; and the connection rules define the details of data interaction. For example, the basic structure of an initial association link might be: the link identifier is "L001," the participating directory unit identifiers are "Traffic Flow Monitoring Directory Unit (Start Point)" and "Traffic Signal Optimization Directory Unit (End Point)," the transmission direction is from the start point to the end point, the connection strength is high, and the connection rule is "Transmit traffic flow data for the past 24 hours in JSON format before the morning rush hour every day."

[0119] Step S1467: Extract the associated data retrieval rules of the participating directory units, integrate the associated data retrieval rules of the participating directory units into the basic structure of the initial association link, and clarify the permission scope, transmission method, and format requirements for data retrieval in the initial association link.

[0120] Each participating directory unit (starting and ending directory units) has its own associated data retrieval rules, which cover data retrieval permissions, methods, and formats. Extracting these rules and integrating them into the basic structure of the initial association link ensures that the link not only knows what data needs to be transmitted and when, but also how to transmit it and who has the authority to transmit and receive it. For example, the associated data retrieval rules for the "traffic flow monitoring directory unit" might stipulate that "only the traffic management department's system is authorized to access the data, and the transmission method is HTTPS encrypted transmission." Integrating this into the basic link structure clarifies that the initial association link specifies the scope of data retrieval permissions as the traffic management department's system, the transmission method as HTTPS, and the format requirement as JSON.

[0121] Step S1468: Analyze the overlapping area of ​​the initial associated link and other potential associated links. If a connection conflict is found, adjust the connection rules of the conflicting links according to the transmission priority information or business transmission coordination logic to eliminate the conflict.

[0122] In urban road network operations, there may be more than one associated link. Newly established initial associated links may overlap with other potential associated links, such as using the same data nodes or participating in the same directory unit. This can lead to connection conflicts, for example, if two links both require to retrieve data from the same data provider at the same time, causing excessive load on the data provider. In this case, it is necessary to adjust the connection rules of the conflicting links based on transmission priority information (core business links have higher priority than general business links) or business transmission coordination logic (such as the order of business processes). For example, modifying the data transmission time of one of the links can eliminate the conflict and ensure that all links can function normally.

[0123] Step S1469: Record the basis for establishing the initial association link. The basis for establishing the link includes the hub data feature set, transmission direction, close association description, and business transmission and collaboration logic, forming a link establishment description.

[0124] The link establishment description is a detailed record of the initial link construction process. It systematically organizes the key information used in the establishment process to facilitate subsequent link maintenance, optimization, and traceability. When recording the basis for establishment, it is necessary to list in detail the specific content related to link establishment in the hub data feature set, such as the complete attribute information of the road network data entities corresponding to the shared road network data node identifiers, the description of association transmission strength, and the transmission direction identifier. This information is the basic data support for link establishment. The transmission direction, as the core guide for link data transmission, also needs to be clearly recorded in its determination process and final result. This includes how the data transmission direction between associated dynamic directory units is determined based on the transmission direction identifier in the hub data feature set, as well as the specific content such as the resulting starting directory unit, ending directory unit, and transmission path direction. The association tightness description reflects the tightness of the link connection. The record should explain how this description is generated based on the number of attribute matching points and the scope of scene overlap, and how this description affects the setting of the link connection strength attribute. The business transmission and collaboration logic serves as the business-level guide for link construction. It requires detailed documentation of how this logic is extracted by analyzing the sequential connection order or parallel collaboration relationships between business transmission paths, and how this logic is transformed into connection rules for the initial associated links, ensuring that the link construction meets actual business needs. By systematically integrating the above information, a link construction specification is formed.

[0125] Step S14610: Integrate the basic structure of the initial association link, the association data calling rules of the participating directory units, and the link construction instructions to form the initial association link. The initial association link is used to clarify the association method and collaborative logic between directory units based on the shared road network data node identifier.

[0126] Having completed the preceding steps, we have obtained the basic structure of the initial association link, the association data retrieval rules for participating directory units, and the link construction instructions. Now, these three parts need to be organically integrated to form a complete initial association link. During integration, it is crucial to ensure consistency and coherence between the various parts. Elements in the basic structure, such as link identifiers, participating directory unit identifiers, transmission direction, connection strength, and connection rules, must match the permissions, transmission methods, and format requirements in the association data retrieval rules of the participating directory units. Simultaneously, the link construction instructions must provide a reasonable and detailed explanation of the formation process of the basic structure and association data retrieval rules. For example, if the basic structure specifies JSON as the data transmission format, then the association data retrieval rules of the participating directory units should also explicitly support JSON data transmission. The link construction instructions should explain why JSON was chosen, possibly based on requirements for data compatibility and parsing efficiency in the business transmission and collaboration logic. Through the above integration, the final initial association link can clearly and accurately define the association method and collaboration logic established between different catalog units based on the shared road network data node identifier, providing a specific and operable implementation path for business collaboration and data association transmission between dynamic catalog units in urban road network business.

[0127] Step S147: Add a collaboration type identifier and transmission priority information to the initial association link. The collaboration type identifier distinguishes between data sharing collaboration, business connection collaboration, and scenario complementarity collaboration. The transmission priority information is generated based on business attributes.

[0128] To make the initial linkage more complete and operational, it's necessary to add collaboration type identifiers and transmission priority information. Collaboration type identifiers distinguish different types of collaboration relationships. Common collaboration types include data-sharing collaboration (primarily for sharing data), business-connecting collaboration (based on the sequential connection of business processes), and scenario-complementary collaboration (different business scenarios complement each other to achieve a common goal). Transmission priority information is determined based on business attributes; for example, core business transmission priority is higher than general business, and urgent business transmission priority is higher than routine business. Adding this information makes the collaboration methods and importance of the linkage clearer.

[0129] Step S148: Extract the associated data retrieval rules for each dynamic directory unit, integrate the associated data retrieval rules into the corresponding initial association link, and determine the permission scope, transmission method, and format requirements for data retrieval in the initial association link.

[0130] Each dynamic directory unit has its associated data retrieval rules, which specify how to access data within that directory unit. When establishing the initial association link, these associated data retrieval rules need to be integrated into the link to ensure smooth data access between different directory units. Specifically, the permission scope for data retrieval in the initial association link (which users or systems can access the data), transmission method (e.g., data transmission via HTTP, FTP, etc.), and format requirements (the format in which the data is transmitted and exchanged, such as JSON, XML, etc.) need to be determined based on the associated data retrieval rules.

[0131] Step S149: Based on all initial associated links, collaboration type identifiers, transmission priority information and associated data calling rules, build the basic structure of the associated transmission link network. This basic structure includes link nodes, link connection relationships, and link attributes. Link nodes are dynamic directory units.

[0132] All initial association links, along with added collaboration type identifiers, transmission priority information, and associated data retrieval rules, are integrated to build the basic structure of the association transmission link network. In this basic structure, link nodes are dynamic directory units, and each node represents a data support system for a business transmission path. Link connections are represented by the initial association links, describing the association methods between dynamic directory units. Link attributes include collaboration type identifiers, transmission priority information, and associated data retrieval rules. By building this basic structure, a preliminary network structure is formed, demonstrating the association transmission relationships between dynamic directory units.

[0133] Step S1410: Integrate link nodes, link connection relationships and all link attributes to form an association transmission link between directory units. This association transmission link is used to realize business collaboration and data association transmission between different dynamic directory units.

[0134] After establishing all initial association links, these links need to be integrated to form the association transmission links between directory units. First, the link nodes are identified as the dynamic directory units. Each dynamic directory unit exists as an independent node in the association transmission link network, possessing a unique identifier and specific business transmission attributes. Then, all initial association links are reviewed to determine the link connections, i.e., which dynamic directory units are interconnected through initial association links to form a complex network structure. Simultaneously, attribute information for all links is collected, including collaboration type identifiers, transmission priority information, associated data retrieval rules, connection strength, and connection rules. During the integration process, link connections need to be checked and optimized to ensure there are no redundant or conflicting connections. For overlapping or conflicting links, adjustments and trade-offs are made based on transmission priority information and business transmission collaboration logic to ensure the rationality and efficiency of the entire association transmission link network. Finally, link nodes, link connections, and all link attributes are organized and stored according to a specific logical structure, ultimately forming the association transmission links between directory units. This interconnected transmission link can organically connect various dynamic directory units in urban road network management, enabling efficient business collaboration and data transmission between different dynamic directory units according to business needs, realizing data resource sharing and smooth business process connection, and improving the overall efficiency and intelligence level of urban road network management.

[0135] Step S150: Integrate dynamic catalog units and associated transmission links to form a closed-loop urban road network data resource catalog, which can be dynamically updated as business-related transmission changes.

[0136] After constructing the dynamic catalog units and generating the associated transmission links, these two parts need to be integrated to form a closed-loop urban road network data resource catalog. The dynamic catalog units are the basic building blocks of the urban road network data resource catalog, each unit corresponding to a complete data support system for a business transmission path. The associated transmission links are the ties connecting these basic units, enabling business collaboration and data association transmission between different units. Through integration, the dynamic catalog units are organized according to the connection relationships and collaborative logic defined by the associated transmission links, forming a hierarchical, clearly structured, and self-updating and optimizing closed-loop system. This urban road network data resource catalog can comprehensively and accurately reflect the data resource status of urban road network business, and can be dynamically updated as the business association transmission sources change, always maintaining its timeliness and accuracy.

[0137] Step S151: Collect all completed dynamic directory units, extract the complete data combination, business transmission adaptation instructions, related data calling rules and unique identifier of each dynamic directory unit, and form a core information database of the directory unit.

[0138] To effectively integrate dynamic directory units with associated transmission links, it is first necessary to collect and manage all completed dynamic directory units in a unified manner. During the collection process, the core information of each dynamic directory unit needs to be comprehensively extracted, including: a complete data assembly containing all road network data nodes supporting the business transmission path, along with their related identifiers and metadata; a business transmission adaptation specification detailing how the data assembly adapts to the corresponding business transmission path, including the correspondence between data and business processes, and the role of data in the business workflow; associated data retrieval rules specifying how to call data within the data assembly and how data interacts with each other; and a unique directory unit identifier used to uniquely distinguish different dynamic directory units, ensuring no confusion occurs during subsequent integration and management. The extracted core information is then stored and organized according to a unified data format and structure to form a directory unit core information database. The establishment of this database enables the rapid and accurate acquisition of key information for each dynamic directory unit, facilitating operations such as association mapping and hierarchical division.

[0139] Step S152: Retrieve the associated transmission links between directory units, extract the link node identifiers, connection relationships, collaboration type identifiers, transmission priority information, and associated data call rules in the associated transmission links, and form a core information database of the links.

[0140] While collecting the core information of dynamic directory units, it is also necessary to retrieve the associated transmission links between the previously generated directory units and extract their core information. The core information in the associated transmission links includes: link node identifiers, which indicate the dynamic directory units connected to the link; connection relationships, which describe the connection method and transmission path between link nodes; collaboration type identifiers, which distinguish the collaboration type of the link, such as data sharing collaboration, business integration collaboration, and scenario complementarity collaboration; transmission priority information, which determines the priority level of the link in data transmission and business collaboration based on business attributes; and associated data retrieval rules, which clarify the scope of permissions, transmission methods, and format requirements for data retrieval on the link. The extracted core information of the associated transmission links is then organized and structured to form a link core information database. This link core information database corresponds to the directory unit core information database, together constituting the basic data resources for integrating dynamic directory units and associated transmission links.

[0141] Step S153: Based on the unique identifier of the directory unit, establish an association mapping between the core information database of the directory unit and the core information database of the link, thereby associating each association transmission link with the core information of the dynamic directory unit participating in the collaboration.

[0142] The unique identifier of a directory unit is the key link connecting the core information database of a directory unit and the core information database of a link. By matching the link node identifier in the core information database of a link with the unique identifier of a directory unit in the core information database of a directory unit, an association mapping relationship can be established between the two databases. For example, if the link node identifiers are "Dynamic Directory Unit A" and "Dynamic Directory Unit B", by looking up the corresponding unique identifier of the directory unit in the core information database of a directory unit, the link can be associated with the complete data combination, business transmission adaptation instructions, and related data call rules of "Dynamic Directory Unit A" and "Dynamic Directory Unit B". This association mapping ensures that each associated transmission link is no longer isolated, but corresponds to a specific dynamic directory unit and its core information participating in the collaboration, ensuring that the relationship between dynamic directory units and associated transmission links is clear and logically sound in the integrated urban road network data resource directory.

[0143] Step S154: Based on the transmission priority information of the associated transmission link, the dynamic directory units in the core information database of the directory unit are hierarchically divided to form the main directory level and the collaborative directory level. The main directory level corresponds to the directory units of the core business transmission path.

[0144] After establishing the association mapping between the core information database of directory units and the core information database of links, all dynamic directory units in the core information database of directory units are hierarchically divided according to the transmission priority information of the associated transmission links. Transmission priority information reflects the importance of different associated transmission links in business collaboration and data transmission. Dynamic directory units connected by high-priority links typically correspond to core business transmission paths in urban road network management. Therefore, dynamic directory units associated with high-priority associated transmission links are classified into the main directory level. These directory units support the core businesses of urban road network management, such as dynamic directory units corresponding to core business transmission paths like daily road maintenance, real-time traffic signal optimization, and main road traffic flow monitoring. Dynamic directory units associated with other priority associated transmission links are classified into the directory collaboration level. These directory units are mainly used to support collaborative work of core businesses or handle some secondary, auxiliary business transmission paths. This hierarchical division makes the structure of the urban road network data resource directory clearer, highlights the importance of core business data resources, and facilitates users' quick location and access to key data.

[0145] Step S155: Within the main directory level and the collaborative directory level, build a horizontal association structure for directory units based on the connection relationship of the association transmission link. The horizontal association structure reflects the collaborative logic between directory units at the same level.

[0146] After completing the division of the main directory level and the directory collaboration level, it is necessary to build a horizontal association structure for directory units within each level. The construction of the horizontal association structure is based on the connection relationship of the association transmission links; that is, dynamic directory units within the same level are interconnected through association transmission links to form a collaborative network. For example, in the main directory level, the "Main Road Traffic Flow Monitoring Dynamic Directory Unit" and the "Traffic Signal Real-time Optimization Dynamic Directory Unit" are connected through a high-priority association transmission link. Simultaneously, the "Traffic Signal Real-time Optimization Dynamic Directory Unit" is also connected to the "Traffic Congestion Early Warning Dynamic Directory Unit." These connections together constitute the horizontal association structure within the main directory level. This horizontal association structure within the main directory level reflects the collaborative logic between directory units at the same level, such as data sharing, business process integration, and complementary scenarios, enabling dynamic directory units at the same level to work efficiently together according to business needs and jointly achieve core business objectives.

[0147] Step S156: A vertical association structure for directory units is built across the main directory level and the directory collaboration level, based on the business connection relationship of the association transmission link. The vertical association structure reflects the business transmission path between directory units at different levels.

[0148] In addition to building horizontal association structures within a hierarchy, it is also necessary to build vertical association structures for directory units across the main directory level and the directory collaboration level. The construction of vertical association structures is based on the business connection relationships of the association transmission links; that is, dynamic directory units at different levels have sequential business connections or data dependencies through these links. For example, the "Secondary Arterial Road Traffic Flow Data Collection Dynamic Directory Unit" in the directory collaboration level needs to transmit the collected data to the "Traffic Flow Data Analysis Dynamic Directory Unit" in the main directory level for processing and analysis. This business connection relationship constitutes part of the vertical association structure. The vertical association structure reflects the business transmission paths between directory units at different levels, enabling core business transmission paths to extend from the main directory level to the directory collaboration level, or for the directory collaboration level to support the business operations of the main directory level, thus achieving smooth data flow and collaborative business advancement between different levels.

[0149] Step S157: Integrate the horizontal and vertical association structures to build an overall association framework for the urban road network data resource catalog. The overall association framework includes three core elements: hierarchical division, association path, and collaboration rules.

[0150] After establishing the horizontal and vertical association structures, these two structures need to be integrated to build the overall association framework of the urban road network data resource catalog. During the integration process, hierarchical division should be used as the foundation of the overall association framework, clearly defining the scope and boundaries of the main catalog level and the catalog collaboration level. The association paths contained in the horizontal and vertical association structures should be sorted and integrated to form a complete association path network covering all dynamic catalog units. Simultaneously, the collaboration rules of all association transmission links should be collected and organized, including collaboration type identifiers, association data retrieval rules, and connection rules, serving as the collaboration rule elements of the overall association framework. Through integration, the overall association framework possesses the characteristics of clear hierarchical division, well-defined association paths, and comprehensive collaboration rules. These three core elements support and cooperate with each other, jointly forming the basic skeleton of the urban road network data resource catalog.

[0151] Step S158: Fill all dynamic directory unit information in the core information database of the directory unit into the corresponding positions of the overall association framework, and supplement the association transmission description and data interaction process between directory units.

[0152] After the overall association framework is built, all dynamic directory unit information stored in the core information database of the directory units needs to be populated into the corresponding positions in the framework. Based on the hierarchical division of the dynamic directory units, dynamic directory unit information belonging to the main directory level is populated into the main level area of ​​the overall association framework, and dynamic directory unit information belonging to the collaborative directory level is populated into the collaborative level area. During the population process, not only must the complete data combination of the dynamic directory unit, business transmission adaptation instructions, association data calling rules, and unique identifiers of the directory unit be entered, but also the association transmission instructions and data interaction processes between directory units must be supplemented according to the association paths in the overall association framework. The association transmission instructions explain in detail the association transmission links between two dynamic directory units, as well as the basis and purpose of the association; the data interaction process describes the specific steps of how data is transmitted, processed, and fed back between two dynamic directory units. By populating and supplementing this information, the overall association framework becomes more comprehensive and concrete, intuitively displaying the entire content and internal relationships of the urban road network data resource catalog.

[0153] Step S159: Establish a dynamic directory update triggering mechanism. The dynamic directory update triggering mechanism takes the change of the business-related transmission source as the triggering condition. When the business process transmission node or transmission rule changes, the dynamic directory unit and the associated transmission link are automatically updated.

[0154] Step S1591: Access the real-time monitoring interface of the business-related transmission source to obtain the real-time status information of the business process transmission nodes and transmission rules. The real-time status information includes the change types of nodes added, nodes deleted, rules modified, and rules added.

[0155] The first step in establishing a dynamic directory update trigger mechanism is to achieve real-time monitoring of business-related transmission sources. This involves connecting to a real-time monitoring interface for business-related transmission sources. This interface continuously acquires real-time status information of business process transmission nodes and rules. This real-time status information records various changes to the business-related transmission sources, including node additions (new business process transmission nodes are added), node deletions (existing business process transmission nodes are removed), rule modifications (existing transmission rules are adjusted or updated), and rule additions (new transmission rules are added). By acquiring this status information in real time, the dynamic changes of business-related transmission sources can be promptly grasped.

[0156] Step S1592: Based on real-time status information, access the change recognition module. The change recognition module is used to automatically identify the changes in the content, scope, and impact dimensions of the changes in the business process transmission nodes and transmission rules.

[0157] After acquiring real-time status information, it is input into the change identification module. This module has the capability to analyze and process this information, automatically identifying specific changes in business process transmission nodes and rules, such as newly added node names and functions, and modified rule clauses; the scope of the change, i.e., which business processes, transmission nodes, or rules are affected; and the dimensions of the change's impact, such as its potential influence on data requirements, business collaboration, and transmission paths. Through the processing by the change identification module, the specific circumstances of changes in business-related transmission sources can be accurately grasped.

[0158] Step S1593: Connect to the change impact assessment model. Input the change content and scope into the change impact assessment model. The change impact assessment model outputs a description of the dimensions and degree of impact of the change on the existing dynamic directory units and related transmission links.

[0159] To assess the impact of changes in business-related transmission sources on the existing system, a change impact assessment model is integrated. The changes identified by the change identification module and their scope are input into this model. Based on a pre-defined assessment algorithm and business rules, the change impact assessment model analyzes the input changes and their scope, evaluating the potential impact dimensions of these changes on existing dynamic directory units and related transmission links. These impact dimensions include factors such as the affected data combinations, business transmission adaptation specifications, and related data retrieval rules; as well as a description of the degree of impact, such as severe impact, moderate impact, or minor impact.

[0160] Step S1594: Based on the description of the impact dimension and the degree of impact, determine the scope of dynamic catalog units and the scope of associated transmission links that need to be updated, and form a list of update objects. The list of update objects includes object identifiers and update priorities.

[0161] Based on the impact dimensions and severity descriptions output by the change impact assessment model, the specific scope of dynamic directory units and related transmission links that need to be updated is further determined. Dynamic directory units and related transmission links that are severely affected are included in the update scope; for those with minor impact, it can be decided whether to update or postpone the update based on the actual situation. Then, object identifiers are assigned to these objects that need updating for unique identification, and update priorities are determined based on factors such as the severity of impact and business importance, resulting in a detailed list of update objects.

[0162] Step S1595: Configure an update process for each dynamic directory unit in the update object list. The update process includes operation steps such as adjusting the data combination, modifying the business transmission adaptation instructions, and updating the associated data calling rules.

[0163] For each dynamic directory unit in the update object list, a dedicated update process needs to be configured. This update process should clearly define the specific operational steps, including: adjusting data combinations, i.e., adding, deleting, or modifying data combinations in the dynamic directory unit according to changes; modifying business transmission adaptation specifications, updating the specification document to reflect the changed business transmission adaptation status; and updating associated data retrieval rules, adjusting rules such as permissions, methods, and formats for data retrieval to ensure that the dynamic directory unit can adapt to changes in business transmission sources.

[0164] Step S1596: Configure an update process for each associated transmission link in the update object list. The update process includes operation steps such as adjusting link connection relationships, modifying collaboration type identifiers, and updating transmission priority information.

[0165] For each associated transmission link in the updated object list, an update process also needs to be configured. This process includes adjusting the link connection relationship, adjusting the start point, end point, or intermediate connection nodes of the link according to changes in business transmission nodes and rules; modifying the collaboration type identifier, updating the collaboration type of the link, such as changing from data sharing collaboration to business connection collaboration; and updating the transmission priority information, redetermining the transmission priority of the link according to the changed business importance to ensure the accuracy and effectiveness of associated transmission links.

[0166] Step S1597: Connect to the update execution module. The update execution module is configured to automatically execute update operations of dynamic directory units and associated transmission links according to the update process and update priority.

[0167] An update execution module is integrated, pre-configured to automatically perform update operations on dynamic directory units and associated transmission links according to the previously defined update process and update priorities in the update object list. During the update process, the update execution module strictly follows the operation steps to adjust data assemblies, modify adaptation specifications, and update rules, ensuring the accuracy and efficiency of the update and reducing manual intervention.

[0168] Step S1598: Access the update verification module. After the update operation is executed, the update verification module can verify the fit between the updated dynamic directory unit and the associated transmission link and the new state of the business associated transmission source. The verification process is executed based on the business associated transmission logic model.

[0169] After the update operation is completed, the update verification module needs to be invoked. The function of the update verification module is to verify whether the updated dynamic directory units and associated transmission links are consistent with the new state of the business-related transmission source. The verification process is based on the business-related transmission logic model, checking whether the updated objects meet the requirements of the new business-related transmission source in terms of data combination, transmission rules, and collaborative relationships, ensuring that the updated system can operate normally.

[0170] Step S1599: Record all operation logs during the update process. The operation logs include the update object, update time, update content, update basis, and verification results, forming a complete update file.

[0171] Throughout the update process, detailed logging of all operations is required. Operation logs should include the identifier of the object being updated, the time the update operation was executed, the specific update content, the basis for the update (such as the impact assessment results), and the verification results output by the update verification module. These logs should be compiled and archived to form a complete update file for subsequent auditing, tracing, and troubleshooting of the update process.

[0172] Step S15910: Integrate the change identification module, change impact assessment model, update process, update execution module, update verification module, and update archive to form a dynamic update trigger mechanism for the catalog.

[0173] Finally, the various components, including the change identification module, change impact assessment model, update process configured for dynamic catalog units and related transmission links, update execution module, update verification module, and update archives, are integrated to form a dynamic catalog update triggering mechanism. When the business-related transmission source changes, this dynamic catalog update triggering mechanism can automatically complete the entire process from change identification, impact assessment, update execution to result verification, ensuring that the urban road network data resource catalog can be dynamically updated in a timely and accurate manner to follow the changes in the business-related transmission source.

[0174] Step S1510: Integrate the overall association framework, directory unit information, association transmission instructions, data interaction process, and dynamic update triggering mechanism of the directory to form a closed-loop urban road network data resource directory. The urban road network data resource directory can be dynamically updated as business association transmission changes.

[0175] Having completed the preceding steps, we have constructed the overall relational framework, populated the directory unit information, supplemented the relational transmission instructions and data interaction processes, and established a dynamic update trigger mechanism for the directory. Now, we need to integrate these components to form the final closed-loop urban road network data resource directory. During integration, we must ensure smooth interfaces, normal data interaction, and consistent logical relationships between the components. The overall relational framework, as the skeleton of the directory, supports the organization and display of directory unit information, relational transmission instructions, and data interaction processes; the dynamic update trigger mechanism monitors changes in business relational transmission sources in real time and drives corresponding updates to the directory. Through integration, the urban road network data resource directory possesses the characteristics of comprehensive data resources, clear relational relationships, efficient business collaboration, and timely and accurate updates. It can achieve self-circulation and dynamic optimization, forming a closed-loop system that provides comprehensive, high-quality data services for urban road network management, and can continuously evolve and improve as the business develops and changes.

[0176] Based on the same inventive concept, please refer to Figure 2 This paper illustrates a schematic block diagram of a system 100 for generating urban road network data resource catalogs in conjunction with service maps, provided in an embodiment of this application, for executing the above-described method for generating urban road network data resource catalogs in conjunction with service maps. The system 100 may include a communication unit 110, a machine-readable storage medium 120, and a processor 130.

[0177] In this embodiment, both the machine-readable storage medium 120 and the processor 130 are located in the urban road network data resource catalog generation system 100 that incorporates service maps, and they are separately configured. Alternatively, the machine-readable storage medium 120 can also be integrated into the processor 130 and can communicate and interact with external systems through the communication unit 110. The machine-readable storage medium 120 is used to store machine-executable instructions for executing the scheme of this application, and the processor 130 is used to execute the machine-executable instructions stored in the machine-readable storage medium 120 to implement the urban road network data resource catalog generation method incorporating service maps provided in the aforementioned method embodiments.

[0178] It should be noted that, in order to simplify the description of the present invention and thus help to understand one or more embodiments of the invention, multiple features may sometimes be grouped into one embodiment, drawing or description thereof in the foregoing description of the embodiments of the present invention.

Claims

1. A method for generating a city road network data resource catalog that combines business maps, characterized in that, The method includes: Access the urban road network business association transmission source and road network basic data to generate a business data association transmission pool. The business association transmission source includes process association information and data request association information of various urban road network businesses. Based on the business association transmission logic, the association and derivation relationships between road network data are derived for the business data association transmission pool, forming a data association and derivation network. The data association and derivation network reflects the dynamic association path of road network data as it is transmitted with the business. Based on the data association and derivative network, the road network data combination corresponding to different business transmission paths is dynamically adapted to construct dynamic directory units. Each dynamic directory unit corresponds to a complete data support system for a business transmission path. Based on the business transmission attributes of dynamic directory units, associated transmission links are generated between directory units, and the associated transmission links reflect the network data coordination relationship of different business transmission paths; By integrating the dynamic catalog unit with the associated transmission link, a closed-loop urban road network data resource catalog is formed, which can be dynamically updated as business-related transmission changes.

2. The method for generating a city road network data resource catalog combining business maps according to claim 1, characterized in that, The process of deriving the correlation and derivation relationships between road network data based on the business association transmission logic, forming a data association and derivation network, includes: Access the business process transmission nodes and transmission rules in the urban road network business association transmission source, extract the associated data requests and transmission direction information of each business process transmission node, and form business transmission node features. The business transmission node features include node identifier, data request type, and transmission target node identifier. The data attribute descriptions, data application scenario scopes, and data association interface information in the road network basic data are retrieved to generate basic road network data features. The dimensions of the basic road network data features correspond to the data request type dimensions of the business transmission node features. Access business association transmission logic model, which includes the definition of the sequential transmission order of business process transmission nodes, the matching rules between data requests and road network data characteristics, and the triggering conditions derived from the association relationship; The business transmission node features are input into the business association transmission logic model. Through the matching rules built into the business association transmission logic model, the basic features of road network data corresponding to the data demand type of each business transmission node are filtered out, and the candidate road network data feature set corresponding to each business transmission node is output. Based on the candidate road network data feature set, the corresponding road network data entities are extracted, the attribute association items and application scenario overlap areas of the road network data entities are analyzed, and data association seeds are determined. The data association seeds are the initial direct association relationships between road network data entities. Using the data association derivation algorithm, starting from the data association seed, and following the business transmission direction, we can deduce adjacent road network data entities that have application scenario connections or complementary attributes with the current road network data entities, thereby expanding the scope of data association. Record the business transmission basis, data attribute association points, and scenario connection logic for each association derivation, forming a data association derivation record. Each data association derivation record includes the starting data identifier, the target data identifier, and the basis for association derivation. Based on all data-related derived records, the basic architecture of the data-related derived network is constructed. In this architecture, road network data entities are defined as network nodes and their complete attribute information is filled in. The related derived relationships are defined as network edges and their derivation basis is filled in. Add a correlation propagation strength description and a propagation direction identifier to each network edge of the data association derivative network. The correlation propagation strength description is generated based on the degree of data dependence in business propagation, and the propagation direction identifier is consistent with the business process propagation direction. By integrating network nodes, network edges, descriptions of correlation transmission strength, and transmission direction identifiers, the data correlation derivative network is formed. The data correlation derivative network is used to dynamically present the correlation derivative paths and dependencies of road network data as it is transmitted with services.

3. The method for generating a city road network data resource catalog combining business maps according to claim 1, characterized in that, The step of dynamically adapting road network data combinations corresponding to different service transmission paths based on the data association derivative network and constructing dynamic directory units includes: The transmission direction identifier and service transmission node association information in the data association derivative network are parsed to extract all independent service transmission paths. Each service transmission path contains continuous service transmission nodes and corresponding road network data nodes. Based on the business objective description of each business transmission path, the core business demand features of the business transmission path are extracted. The core business demand features include the key data types for business implementation, data usage order requirements, and data association strength thresholds. Traverse the road network data nodes corresponding to the business transmission path in the data association derivative network, extract the complete attribute information and association transmission strength description of each road network data node, and form a path data feature set; Based on the key data types in the core business requirements, select road network data nodes that meet the requirements from the path data feature set to form an initial data combination candidate set; Based on the data usage order requirements in the core business demand characteristics, and combined with the transmission direction identifier of the data association derivative network, the road network data nodes in the initial data combination candidate set are arranged sequentially to generate an ordered data sequence; Based on the data association strength threshold in the core business demand characteristics, road network data nodes in the ordered data sequence that do not meet the requirements of association transmission strength description are filtered out, the integrity and association of the ordered data sequence are optimized, and the unique identifier, data access address, data update cycle and data format description of each road network data node in the optimized ordered data sequence are extracted to form a set of data element information. Based on the data element information set, a business transmission path identifier, a node position identifier in the path, and a data association dependency identifier are added to each road network data node in the ordered data sequence. The business transmission path identifier, node position identifier in the path, and data association dependency identifier are consistent with the characteristics of the business transmission path. Integrate ordered data sequences, data element information sets, business transmission path identifiers, node location identifiers in the path, and data association dependency identifiers to form a path-specific data combination; The path-specific data combination is encapsulated according to a unified directory unit structure. The business transmission adaptation instructions and associated data calling rules of the path-specific data combination are supplemented to form a dynamic directory unit. The dynamic directory unit is used to achieve adaptive adjustment of the data combination as the business transmission path changes.

4. The method for generating a city road network data resource catalog combining business maps according to claim 1, characterized in that, The generation of association transmission links between directory units based on the business transmission attributes of dynamic directory units includes: Extract the business transmission path identifier, core business demand characteristics, and road network data node identifiers in the data assembly of each dynamic catalog unit to form a catalog unit transmission characteristic set; Based on the set of transmission features of the directory unit, the overlapping areas of the core business demand features of different dynamic directory units are analyzed, and the directory unit groups with business collaboration needs are identified. The business collaboration needs are determined based on the connection relationship of business processes or data sharing needs. Extract the road network data node identifiers from the data combination of all dynamic directory units in each directory unit group, and find the road network data node identifiers that are common to different directory units. Based on the shared road network data node identifiers, the association transmission strength description and transmission direction identifier of the corresponding road network data entities are extracted to determine the data transmission direction and close association description between different directory units. Analyze the business transmission path identifiers of dynamic directory units in each directory unit group, extract the sequential connection order or parallel collaboration relationship between business transmission paths, and form business transmission collaboration logic; Using the shared road network data node identifier as the connection hub, and combining the data transmission direction, closely related description, and business transmission collaboration logic, an initial association link is established between directory units. The initial association link includes the link start point identifier, the link end point identifier, and the connection basis. Add a collaboration type identifier and transmission priority information to the initial association link. The collaboration type identifier distinguishes between data sharing collaboration, business connection collaboration, and scenario complementarity collaboration. The transmission priority information is generated based on business attributes. Extract the associated data retrieval rules for each dynamic directory unit, integrate the associated data retrieval rules into the corresponding initial association link, and determine the permission scope, transmission method, and format requirements for data retrieval in the initial association link; Based on all initial associated links, collaboration type identifiers, transmission priority information, and associated data retrieval rules, the basic structure of the associated transmission link network is built. The basic structure of the associated transmission link network includes link nodes, link connection relationships, and link attributes. Link nodes are dynamic directory units. By integrating link nodes, link connection relationships, and all link attributes, an association transmission link between directory units is formed. The association transmission link between directory units is used to realize business collaboration and data association transmission between different dynamic directory units.

5. The method for generating a city road network data resource catalog combining business maps according to claim 1, characterized in that, The urban road network data resource catalog that integrates the dynamic catalog unit and the associated transmission link to form a closed loop includes: Collect all completed dynamic directory units, extract the complete data combination, business transmission adaptation instructions, related data calling rules and unique identifier of each dynamic directory unit, and form a core information database of the directory unit. Retrieve the associated transmission links between directory units, extract the link node identifiers, connection relationships, collaboration type identifiers, transmission priority information, and associated data retrieval rules from the associated transmission links, and form a core information database of the links; Based on the unique identifier of the directory unit, an association mapping is established between the core information database of the directory unit and the core information database of the link, thereby associating each association transmission link with the core information of the dynamic directory unit participating in the collaboration. Based on the transmission priority information of the associated transmission link, the dynamic directory units in the core information database of the directory unit are hierarchically divided to form the main directory level and the directory collaboration level. The main directory level corresponds to the directory units of the core business transmission path. Within the main directory level and the collaborative directory level, a horizontal association structure for directory units is built based on the connection relationship of the association transmission link. The horizontal association structure reflects the collaborative logic between directory units at the same level. A vertical association structure for directory units is built across the main directory level and the directory collaboration level, based on the business connection relationship of the association transmission link. The vertical association structure reflects the business transmission path between directory units at different levels. By integrating horizontal and vertical association structures, an overall association framework for the urban road network data resource catalog is built. The overall association framework includes three core elements: hierarchical division, association path, and collaborative rules. Fill the corresponding positions in the overall association framework with all dynamic directory unit information from the core information database of the directory unit, and supplement the association transmission description and data interaction process between directory units; Establish a dynamic directory update triggering mechanism. The dynamic directory update triggering mechanism takes the change of the business-related transmission source as the triggering condition. When the business process transmission node or transmission rule changes, the dynamic directory unit and the associated transmission link are automatically updated. The overall association framework, directory unit information, association transmission instructions, data interaction process and directory dynamic update triggering mechanism are integrated to form a closed-loop urban road network data resource directory. The urban road network data resource directory can be dynamically updated as business association transmission changes.

6. The method for generating a city road network data resource catalog combining business maps according to claim 2, characterized in that, The data association derivation algorithm, starting from the data association seed, deduces adjacent road network data entities that have application scenario connections or complementary attributes with the current road network data entities along the business transmission direction, thereby expanding the scope of data association, including: The road network data entity attribute information and application scenario information in the data association seed are input into the feature input layer of the data association derivation algorithm for structured processing. After generating identifiable feature vectors, they are input into the association rule mining module of the data association derivation algorithm. Based on preset attribute association rules and scenario connection rules, the potential association attributes and potential application scenarios of the current road network data entities are mined. Based on the potential association attributes, other road network data entities with the same or complementary attributes are retrieved from the road network basic data to form a potential association data candidate set, which includes data entity identifiers and attribute matching points. Based on the potential application scenarios, the similarity or correlation between the application scenarios of other road network data entities in the road network basic data and the potential application scenarios is calculated. Data entities with similarity or correlation exceeding a preset threshold are filtered out and added to the potential related data candidate set. Based on the number of attribute matching points and the scope of scene overlap, a close association description between each data entity in the potential associated data candidate set and the current road network data entity is generated. Based on the close association description, the data entities in the potential associated data candidate set are sorted, and the data entity with more comprehensive association dimensions corresponding to the close association description is selected as the priority association object. Extract the complete attribute information and application scenario description of the priority associated objects, and verify their association with the corresponding information of the current road network data entities. The association verification process is executed based on the matching rules of the business association transmission logic model. Record the basis for association, association attributes, and scenario connection points between the priority associated object and the current road network data entity, forming a new association derivative record. The new association derivative record maintains the same format as the original data association derivative record. Starting with the priority associated objects as a new starting point, repeat the process of attribute mining, scenario filtering, association calculation, and record verification to continuously expand the scope of data association and form a chain-like association derivative path; Integrate all chain-related derivative paths and corresponding derivative records to expand the scope of data association.

7. The method for generating a city road network data resource catalog combining business maps according to claim 3, characterized in that, Based on the data usage order requirements in the core business requirements and combined with the transmission direction identifier of the data association derivative network, the road network data nodes in the initial data combination candidate set are sequentially arranged to generate an ordered data sequence, including: Extract the data usage sequence requirements from the core business requirements features, break down the data usage sequence requirements into multiple data usage stages, each data usage stage corresponds to a key business link in the business transmission path, and determine the core data requirements of each data usage stage; The transmission direction identifiers of the road network data nodes corresponding to the initial data combination candidate set in the data association derivative network are analyzed to determine the transmission order of each road network data node in the business transmission path; Establish a correspondence between the data usage stage and the sequence of transmission, so that each data usage stage can be matched with the road network data node corresponding to the transmission direction identifier; Based on the aforementioned correspondence, the road network data nodes in the initial data combination candidate set are initially sorted according to the order of data usage stages to form an initial ordered sequence. The correlation transmission strength description of each road network data node in the initial ordered sequence is extracted, the close correlation description between adjacent road network data nodes is analyzed, and the arrangement order of nodes in the initial ordered sequence is adjusted so that nodes with more comprehensive correlation dimensions corresponding to the close correlation description are arranged adjacently. Analyze the data application scenario activation conditions of each road network data node to ensure that the application scenario activation conditions of the sorted road network data nodes are consistent with the process advancement logic of the business transmission path; Extract the data access dependencies of road network data nodes. Access to some road network data nodes requires the output of other road network data nodes as a prerequisite. Further adjust the sequence order based on the data access dependencies. The adjusted sequence is compared and verified with the data usage order requirements in the core business requirements. If there is any inconsistency, the sequence is adjusted again according to the data usage order requirements until the sequence order is consistent with the data usage order requirements. Record the basis for all adjustments during the sequence arrangement process, including the initial sorting, adjustments based on closely related descriptions, adjustments based on application scenario initiation conditions, adjustments based on data access dependencies, and the basis for further adjustments based on comparative verification, to form a sequence arrangement description; The integrated and adjusted road network data node sequence and sequence arrangement description are used to generate the ordered data sequence, which is used to meet the order requirements and association requirements of data use in the business transmission path.

8. The method for generating a city road network data resource catalog combining business maps according to claim 4, characterized in that, The initial association link between directory units is established by using shared road network data node identifiers as connection hubs, combining data transmission direction, closely related descriptions, and business transmission collaboration logic, including: Extract the complete attribute information, associated transmission strength description and transmission direction identifier of the road network data entity corresponding to the common road network data node identifier to form a hub data feature set; Based on the hub data feature set, the associated dynamic directory unit corresponding to each shared road network data node identifier is determined, and the role of each associated dynamic directory unit in the link is clarified. The role is divided into data provider or data receiver. Based on the data transmission direction identifier, the data transmission direction between associated dynamic directory units is determined, forming the transmission direction framework of the initial association link. The transmission direction framework of the initial association link includes the starting directory unit, the ending directory unit, and the transmission path direction. Based on the tightly associated description, a connection strength attribute is added to the propagation direction frame of the initial associated link. The connection strength attribute directly corresponds to the tightly associated description. The business transmission and collaboration logic is analyzed, key business nodes and data interaction requirements in the collaboration process are extracted, and the key business nodes and data interaction requirements are transformed into connection rules for the initial association link. The connection rules for the initial association link include the timing, content, and format of data interaction. Based on the transmission direction framework, connection strength attribute, and connection rules of the initial association link, the basic structure of the initial association link is constructed. The basic structure of the initial association link includes link identifier, participating directory unit identifier, transmission direction, connection strength, and connection rules. Extract the associated data retrieval rules of the participating directory units, integrate the associated data retrieval rules of the participating directory units into the basic structure of the initial association link, and clarify the permissions, methods, and restrictions of data retrieval in the initial association link; The overlapping areas of the initial associated links and other potential associated links are analyzed. If a connection conflict is found, the connection rules of the conflicting links are adjusted according to the transmission priority information or the business transmission coordination logic to eliminate the conflict. Record the basis for establishing the initial connection links, including the hub data feature set, transmission direction, close association description, and business transmission and collaboration logic, to form a link establishment description; The initial association link is formed by integrating the basic structure of the initial association link, the association data calling rules of the participating directory units, and the link building instructions. The initial association link is used to clarify the association method and collaborative logic between directory units based on the shared road network data node identifier.

9. The method for generating a city road network data resource catalog combining business maps according to claim 5, characterized in that, The aforementioned dynamic directory update triggering mechanism uses changes in business-related transmission sources as triggering conditions. When business process transmission nodes or transmission rules change, it automatically triggers updates to dynamic directory units and related transmission links, including: Access the real-time monitoring interface of the business-related transmission source to obtain real-time status information of business process transmission nodes and transmission rules. The real-time status information includes the change types of nodes being added, nodes being deleted, rules being modified, and rules being added. Based on real-time status information, a change recognition module is accessed. The change recognition module is used to automatically identify the changes in the content, scope, and impact dimensions of the business process transmission nodes and transmission rules. The change impact assessment model is accessed by inputting the content and scope of the change into the model. The model then outputs the dimensions and descriptions of the impact of the change on the existing dynamic directory units and related transmission links. Based on the impact dimensions and impact descriptions, the scope of dynamic directory units and associated transmission links that need to be updated are determined, forming an update object list, which includes object identifiers and update priorities; Configure an update process for each dynamic directory unit in the list of updated objects. The update process includes operation steps such as adjusting the data assembly, modifying the business transmission adaptation instructions, and updating the associated data calling rules. Configure an update process for each associated transmission link in the list of updated objects. The update process includes operation steps such as adjusting link connection relationship, modifying collaboration type identifier, and updating transmission priority information. An update execution module is connected, which is configured to automatically execute update operations of dynamic directory units and associated transmission links according to the update process and update priority; The update verification module is connected. After the update operation is executed, the update verification module can verify the fit between the updated dynamic directory unit and the associated transmission link and the new state of the business associated transmission source. The verification process is executed based on the business associated transmission logic model. Record all operation logs during the update process. The operation logs include the update object, update time, update content, update basis, and verification results, forming a complete update archive. The change identification module, change impact assessment model, update process, update execution module, update verification module, and update archive are integrated to form the dynamic update trigger mechanism for the aforementioned directory.

10. A system for generating a city road network data resource catalog that combines business maps, characterized in that, include: processor; A machine-readable storage medium for storing machine-executable instructions of the processor; The processor is configured to execute the urban road network data resource catalog generation method combining service maps as described in any one of claims 1 to 9 by executing the machine-executable instructions.

Images