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

Abstract

The invention provides an urban road network data resource directory generation method and system combined with a business atlas, and relates to the technical field of urban traffic data management.The method comprises the steps that firstly, an urban road network business association conduction source and road network basic data are accessed to generate a business data association conduction pool; deducing a road network data association derivative relationship based on the business association conduction logic to form a data association derivative network; according to the data association derivative data network dynamic adaptive road network data combination, constructing a dynamic directory unit; generating an associated conduction link based on the dynamic directory unit service conduction attribute; and finally, the dynamic directory unit and the associated conduction link are integrated to form a closed-loop urban road network data resource directory which can be dynamically updated, so that the management efficiency and the utilization value of urban road network data resources are effectively improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of urban traffic data management, in particular to a method and system for generating an urban road network data resource directory in combination with a business graph. BACKGROUND

[0002] In the context of increasingly complex and refined urban traffic management, efficient management and utilization of urban road network data resources have become critical to improving urban traffic operation efficiency and optimizing traffic planning decisions. Urban road networks involve numerous businesses, such as traffic flow monitoring, traffic signal control, public transportation scheduling, road maintenance management, etc. These businesses are interconnected and influence each other, forming an organic whole of urban traffic operation.

[0003] Currently, the management of urban road network data resources mainly adopts the traditional static directory method. The above method usually classifies and organizes data according to fixed dimensions such as data type and source, forming a relatively fixed data resource directory. However, the above static directory has obvious limitations. On the one hand, it cannot accurately reflect the complex relationship between different businesses, and it is difficult to reflect the dynamic changes of road network data as the business is transmitted. For example, changes in traffic flow monitoring data may affect traffic signal control decisions, but the traditional directory cannot intuitively present the above association. On the other hand, with the continuous development and innovation of urban traffic businesses, new business demands are constantly emerging, and the traditional static directory is difficult to quickly adapt to these changes, making it difficult to update and adjust the data resource directory in a timely manner, leading to a disconnect between data management and actual business needs, reducing the efficiency of data resources, and affecting the effectiveness of urban traffic management. SUMMARY

[0004] In view of the above-mentioned problems, in combination with the first aspect of the present application, the embodiments of the present application provide a method for generating an urban road network data resource directory in combination with a business graph, which comprises: Accessing urban road network business association transmission sources and road network basic data to generate a business data association transmission pool, the business association transmission sources containing process association information and data demand association information of various businesses of the urban road network; Based on the business association transmission logic, the association derivation relationship between road network data is deduced for the business data association transmission pool to form a data association derivation network, which reflects the dynamic association path of road network data as the business is transmitted; According to the data association derivation network, dynamically adapt the road network data combination corresponding to different business transmission paths to build a dynamic directory unit, each dynamic directory unit corresponding to a complete data support system of a business transmission path; Based on the service conduction attribute of the dynamic directory unit, an associated conduction link between the directory units is generated, and the associated conduction link reflects the road network data cooperation relationship of different service conduction paths. The dynamic directory unit and the associated conduction link are integrated to form a closed-loop urban road network data resource directory, and the urban road network data resource directory can be dynamically updated with changes in service associated conduction.

[0005] In another aspect, the embodiment of the present application also provides a city road network data resource directory generation system combined with a service graph, comprising: A processor; a machine readable storage medium for storing machine executable instructions of the processor; wherein the processor is configured to execute the machine executable instructions to perform the above-mentioned city road network data resource directory generation method combined with a service graph.

[0006] Based on the above aspects, by accessing the city road network service associated conduction source and the road network basic data to generate the service data associated conduction pool, the process associated information and data demand associated information of various services of the city road network are integrated, and then the associated derivative relationship between the road network data is deduced based on the service associated conduction logic to form a data associated derivative network. The data associated derivative network can accurately reflect the dynamic association path of the road network data with the service conduction, and reveal the flow and change rule of the data in different service scenarios. According to the data associated derivative network, a dynamic directory unit is dynamically adapted to the road network data combination corresponding to different service conduction paths. Each dynamic directory unit can provide a complete data support system for a service conduction path. Based on the service conduction attribute of the dynamic directory unit, the associated conduction link between the directory units is generated, which reflects the road network data cooperation relationship of different service conduction paths, and further strengthens the logical relationship between the data. Finally, the dynamic directory unit and the associated conduction link are integrated to form a closed-loop urban road network data resource directory. The urban road network data resource directory can be dynamically updated with changes in service associated conduction, always maintains a high degree of fit with actual service needs, and effectively improves the management efficiency and utilization value of the urban road network data resources. BRIEF DESCRIPTION OF DRAWINGS

[0007] Figure 1 is the execution flow diagram of the city road network data resource directory generation method combined with a service graph provided by the embodiment of the present application.

[0008] Figure 2 is the schematic diagram of the exemplary hardware and software components of the city road network data resource directory generation system combined with a service graph provided by the embodiment of the present application. DETAILED DESCRIPTION

[0009] The present application will be specifically described below in conjunction with the drawings of the specification, Figure 1is a flowchart of a method for generating a city road network data resource directory combined with a business graph according to an embodiment of the present application. The method for generating a city road network data resource directory combined with a business graph will be described in detail below.

[0010] Step S110: Access the city road network business association conduction source and the road network basic data to generate a business data association conduction pool.

[0011] In the field of city road network management, the business association conduction source covers the process association information and data demand association information of various businesses such as road network planning, traffic signal control, road maintenance, and public transportation scheduling. The process association information describes the execution order, cooperative dependency relationship, and information interaction nodes between various businesses in detail. The data demand association information clearly defines the specific requirements of each business for various data during execution, such as data type, data precision, data update frequency, etc. The road network basic data includes physical property data of roads (such as road length, width, number of lanes, road surface material, etc.), road auxiliary facility data (such as traffic signal lamp position and timing scheme, traffic sign and marking information, street light distribution, etc.), traffic flow data (vehicle flow and pedestrian flow of each road section at different times, etc.), and road surrounding environment data (such as building distribution, school, hospital, and other key area positions, etc.).

[0012] In the access process, first, a dedicated data interface is needed to establish a connection with the business system and database of the city traffic management department to ensure the stability and security of data transmission. For the business association conduction source, it needs to be structured, converting unstructured business process documents and semi-structured cooperative rule tables into a unified standardized data format for efficient processing and analysis. For the road network basic data, data cleaning operations are needed to remove duplicate data, abnormal data, and missing values to ensure data accuracy and integrity. After cleaning, the above data is classified and stored, and data indexes are established to facilitate fast query and call. Through the above operations, the accessed and processed business association conduction source and road network basic data are integrated into a unified data pool, i.e., a business data association conduction pool.

[0013] In the process of associating the conduction source of the city road network service with the road network basic data, the relevant legal regulations are strictly followed. In the data collection link, sensitive data related to personal privacy (such as vehicle trajectory data of a specific road at a specific time, driver information, etc.) is processed using data desensitization technology, including hash operation on vehicle license plate information and anonymization replacement of driver identity information, to ensure that the data cannot be directly linked to a specific individual. At the same time, a data collection authorization mechanism is established by signing a formal data use authorization agreement with data providers (such as traffic management departments, road maintenance units, and third-party data service providers), which clearly defines the scope, purpose, and duration of data collection, as well as the rights and obligations of both parties. The agreement specifically states that the data is only used for the construction and management of the city road network data resource directory and cannot be used for other unauthorized purposes. For road network basic data obtained from public channels (such as road planning public documents and traffic flow statistics bulletins), the data source must be reviewed for compliance to ensure that the data acquisition method is legal. In the data transmission process, end-to-end encryption technology (such as SSL / TLS protocol) is used to encrypt the data to prevent data from being stolen or tampered with during transmission. In the data storage link, sensitive data is stored using an encrypted database, and strict access permission control is set up, allowing only authorized management personnel to access sensitive data through multi-factor authentication (such as password + dynamic password). In addition, a data security audit mechanism is established to log data collection, transmission, storage, and use throughout the entire process, and the logs are audited regularly to promptly identify and address data security risks, ensuring that the entire data access process complies with legal regulations, effectively protecting data privacy and security, and preventing data leakage.

[0014] Step S120: Based on the service association conduction logic, the association and derivation relationship between the road network data is derived for the service data association conduction pool, and a data association and derivation network is formed.

[0015] In this embodiment, after obtaining the service data association conduction pool, the association and derivation relationship between the road network data needs to be derived based on the service association conduction logic, and then a data association and derivation network is formed. The service association conduction logic refers to the inherent conduction order, data flow rule, and condition for establishing the association relationship between the various business processes in the city road network service. For example, in the daily maintenance business of the city road network, when a road surface damage is found, the road surface damage data needs to be collected first, then the maintenance level is evaluated according to the damage degree, and then the corresponding maintenance resources are allocated for repair, and finally the acceptance of the repaired road is carried out. There is a clear business association conduction logic in this process. By applying this logic, various road network data in the service data association conduction pool is analyzed and mined to find the implicit association relationship between the data generated during the business conduction, thereby constructing a data association and derivation network that can reflect the dynamic association path of the road network data.

[0016] Step S121: Access the business flow conduction nodes and conduction rules in the city road network business association conduction source, extract the associated data requirements and conduction direction information of each business flow conduction node, and form the business conduction node characteristics.

[0017] Next, in order to accurately derive the association derivation relationship between the road network data, first, the accessed city road network business association conduction source needs to be deeply analyzed. Specifically, it is to access the business flow conduction nodes and conduction rules therein. The business flow conduction node is the key link in the business flow, such as the "road surface damage data collection" node, the "maintenance level evaluation" node, the "maintenance resource allocation" node, etc. all belong to the business flow conduction node. The conduction rule specifies how the nodes conduct business, for example, "only after the road surface damage data collection is completed, the maintenance level evaluation can be carried out" is a conduction rule. Then, for each business flow conduction node, extract its associated data requirements and conduction direction information. The associated data requirements refer to the data types and specific requirements needed by the node in the business processing process. Taking the "maintenance level evaluation" node as an example, its associated data requirements may include road surface damage location, area, depth, etc. The conduction direction information indicates the direction of the business flow from the node to the next node, for example, the conduction direction of the "maintenance level evaluation" node is to the "maintenance resource allocation" node. After organizing and structuring these extracted information, the business conduction node characteristics are formed, which include node identification (used to uniquely distinguish different nodes), data requirement type (clearly need what type of data), conduction target node identification (indicates the next node of business conduction) and other contents.

[0018] Step S122: Retrieve the data attribute description, data application scenario range, and data association interface information in the road network basic data to generate the road network data basic characteristics.

[0019] While extracting the service conduction node features, the relevant information of the road network basic data from the service data association conduction pool also needs to be called to generate the road network data basic features. The information of the road network basic data is diverse, among which the data attribute description is used to describe the intrinsic characteristics of the data, such as the attribute description of the traffic flow data including the collection time, collection location, vehicle type classification, etc.; the data application scene range clearly shows which business scenarios the data can be applied to, for example, the traffic flow data of a road section can be applied to the traffic signal timing optimization scene and the road congestion early warning scene; the data association interface information provides the way of interaction and association with other data, such as the traffic flow data can be associated with the traffic event data through a specific API interface. When generating the road network data basic features, it is necessary to ensure that the dimensions thereof correspond to the data demand type dimensions of the business conduction node features. That is, if the data demand type in the business conduction node features involves the road physical attribute, traffic flow, traffic event, etc., the road network data basic features should also contain the information of these dimensions, so as to facilitate subsequent effective matching and association analysis.

[0020] Step S123: accessing the service association conduction logic model, which contains the definition of the conduction sequence of the business process conduction nodes, the matching rules of the data demand and the road network data features, and the association relationship derivation trigger conditions.

[0021] In this embodiment, in order to realize the derivation of the road network data association relationship based on the business association conduction logic, a special business association conduction logic model needs to be accessed. The business association conduction logic model is constructed according to the actual situation and rules of the urban road network business, which contains the definition of the conduction sequence of the business process conduction nodes, which ensures that the business process is conducted in the correct order and avoids logical confusion. For example, in the road construction business process, the sequence of the nodes must be “project approval”, “planning and design”, “construction”, “completion and acceptance”, etc., and cannot be reversed. The matching rules of the data demand and the road network data features are used to judge whether the road network data meets the data demand of the business conduction node, for example, when a certain business conduction node needs “vehicle flow greater than a certain value” data, the matching rules will clearly show how to judge according to the vehicle flow attribute in the road network data features. The association relationship derivation trigger condition specifies under what circumstances the new association relationship between the 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 the traffic congestion conduction association relationship between them.

[0022] Step S124: input the service conduction node features into the service association conduction logic model, filter out the road network data basic features corresponding to the data demand type of each service conduction node through the matching rules built in the model, and output the candidate road network data feature set corresponding to each service conduction node.

[0023] After accessing the service association conduction logic model, the service conduction node features generated in the foregoing are input into the model. The model will compare and filter the data demand types in the service conduction node features and the road network data basic features one by one according to the built-in matching rules. For example, for the "maintenance level evaluation" service conduction node, the data demand types include road surface damage location, area, depth, etc. The model will filter out the attribute features of the road damage detection data corresponding to these types in the road network data basic features, such as the road surface damage location coordinate data feature, damage area measurement data feature, and damage depth detection data feature of a road section. After filtering, a candidate road network data feature set can be output for each service conduction node, which contains all road network data basic features that can meet the data demand of the node.

[0024] Step S125: based on the candidate road network data feature set, extract the corresponding road network data entity, analyze the attribute association items and application scenario overlap area of the road network data entity, and determine the data association seed.

[0025] Then, for each candidate road network data feature set corresponding to a service conduction node, the road network data entity contained therein is extracted. The road network data entity refers to a road network data unit that has actual meaning and can exist independently, such as the data related to a specific road, which can constitute a road network data entity, or the timing data of a traffic signal, which can also constitute a road network data entity. After extracting the road network data entity, its attribute association items and application scenario overlap area need to be analyzed. The attribute association items refer to the parts that are associated with each other in attributes between different road network data entities, for example, the length attribute of a road and the travel time attribute of a road are associated, and the longer the length, the longer the travel time. The application scenario overlap area refers to the part that is overlapped in the application scenarios of multiple road network data entities, for example, the traffic flow data entity of a road and the timing data entity of a traffic signal can be applied to the traffic congestion governance scenario, which is their application scenario overlap area. Through the analysis of the attribute association items and the application scenario overlap area, the data association seed, i.e., the initial direct association relationship between road network data entities, can be determined, for example, the association between the traffic flow data entity and the timing data entity of a traffic signal in the traffic congestion governance scenario can be used as a data association seed.

[0026] Step S126: Deriving, by a data association derivation algorithm, adjacent road network data entities that have application scenario connection or attribute complementarity with the current road network data entity along the service conduction direction, starting from the data association seed, to expand the data association range.

[0027] Step S1261: Inputting the attribute information and application scenario information of the road network data entity in the data association seed into the feature input layer of the data association derivation algorithm for structured processing, generating a recognizable feature vector, and then inputting the feature vector into the association rule mining module of the data association derivation algorithm to mine the potential associated attributes and potential application scenarios of the current road network data entity based on the preset attribute association rules and scenario connection rules.

[0028] When expanding the data association range, the information in the data association seed needs to be processed first. The attribute information of the road network data entity, such as the material of the road, the number of lanes, the design speed, etc., and the application scenario information, such as whether it is used for traffic flow monitoring or road maintenance, etc., are input into the feature input layer of the data association derivation algorithm. The feature input layer will perform structured processing on the above information, converting unstructured text descriptions into structured data formats, and then generating an algorithm-recognizable feature vector. This feature vector contains key information of attributes and scenarios. Then, the feature vector is input into the association rule mining module, which has preset a variety of attribute association rules and scenario connection rules. For example, the attribute association rule may stipulate that when the road material is asphalt, its maintenance period is usually different from that of concrete roads; the scenario connection rule may indicate that the traffic flow monitoring scenario is often associated with the traffic signal timing scenario. Through these rules, potential associated attributes that the current road network data entity may have, such as the maximum carrying traffic volume based on the number of lanes of the road, and potential application scenarios, such as the traffic congestion warning scenario that may be extended from the traffic flow monitoring scenario, are mined.

[0029] Step S1262: Based on the potential associated attributes, retrieving other road network data entities with the same or complementary attributes from the road network basic data to form a potential associated data candidate set, which contains data entity identifiers and attribute matching points.

[0030] After obtaining the potential associated attributes, the attributes are used as search conditions to search in the road network basic data. Other road network data entities having the same attributes or complementary attributes with the current road network data entity are searched. The same attributes are, for example, roads made of asphalt, and the complementary attributes are, for example, traffic flow data of a road and traffic signal timing data of another road, which complement each other to achieve traffic optimization. The searched data entities are integrated to form a potential associated data candidate set. In the candidate set, each data entity contains a unique data entity identifier and an attribute matching point with the current data entity, so that it can be known that each candidate entity is associated based on which attributes.

[0031] Step S1263: Based on the potential application scenario, the similarity or correlation degree of the application scenario of other road network data entities in the road network basic data and the potential application scenario is calculated, and data entities with a similarity or correlation degree exceeding a preset threshold are filtered out and supplemented to the potential associated data candidate set.

[0032] In addition to attribute-based association search, the association of application scenarios also needs to be considered. According to the mined potential application scenario, the similarity or correlation degree of the application scenario of other road network data entities in the road network basic data and the potential application scenario is calculated. For example, if the potential application scenario is traffic congestion management, the similarity of the application scenario of other data entities and the traffic congestion management scenario is calculated. The similarity or correlation degree can be calculated by analyzing the keywords in the scenario description, the business links involved, and the like. When the similarity or correlation degree exceeds a preset threshold, it indicates that the data entity has strong relevance with the current road network data entity in the application scenario, and it is filtered out and supplemented to the potential associated data candidate set, so that the candidate set is more comprehensive.

[0033] Step S1264: Based on the number of attribute matching points and the scenario overlap range, an associated close description of each data entity in the potential associated data candidate set and the current road network data entity is generated, and the data entities in the potential associated data candidate set are sorted according to the associated close description, and a data entity with a more comprehensive associated dimension corresponding to the associated close description is selected as a priority association object.

[0034] For each data entity in the potential associated data candidate set, the closeness of its association with the current road network data entity needs to be evaluated. According to the number of attribute matching points obtained in the previous step, such as 3 attribute matching points, and the scenario overlap range, such as 50% overlap area in the traffic management scenario, the association closeness description is generated. The association closeness description can include the number of attribute matches, the proportion of scenario overlap, and the matching of key attributes and scenarios, etc. Then, according to these association closeness descriptions, the data entities in the candidate set are sorted. The principle of sorting is that the more comprehensive the association dimension, the higher the priority, that is, those data entities with more matches and overlaps in attributes and scenarios are given priority and selected as the priority association objects.

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

[0036] After selecting the priority association objects, they need to be verified for association. The complete attribute information of these priority association objects is extracted, including all attribute items and their values, as well as detailed application scenario descriptions. Then, the above information is compared and verified with the corresponding information of the current road network data entity. The association verification process strictly follows the matching rules in the business association transmission logic model, such as checking whether the attribute values meet the pre-set matching conditions, whether the application scenarios have a logical connection, etc. Only the priority association objects that pass the verification can be determined as the real associated data entities.

[0037] Step S1266: Record the association basis, association attributes, and scenario connection points between the priority association objects and the current road network data entity, form a new association derivative record, and the new association derivative record maintains the same format as the original data association derivative record.

[0038] After completing the association verification, the association information needs to be recorded. The association basis between the priority association objects and the current road network data entity, such as the association based on which attribute matches and scenario overlaps, the association attributes, i.e. which attributes are associated, the scenario connection points, i.e. how to connect in the application scenario, etc. are recorded to form a new association derivative record. In order to ensure data consistency and facilitate subsequent processing, the new association derivative record maintains the same format as the original data association derivative record, including the starting data identifier, the target data identifier, the association derivation basis, etc.

[0039] Step S1267: Take the priority association objects as the new starting point, repeat the process of attribute mining, scenario screening, association calculation, and verification recording, continuously expand the data association range, and form a chain-like association derivative path.

[0040] The verified priority association object is taken as a new current road network data entity, i.e., a new starting point, and the above-mentioned whole process from mining potential association attributes and scenarios, to screening a candidate set, calculating an association closeness description, performing association verification, and recording an association derivative record is repeated. Thus, the expansion is continuously performed with a new association data entity as a starting point, like a chain, so as to continuously expand the range of data association and form a chain-like association derivative path.

[0041] Step S1268: integrating all chain-like association derivative paths and corresponding association derivative records, and completing expansion of the range of data association.

[0042] When the chain-like association derivative path is expanded to a certain extent or there is no more association data entity meeting the condition, the expansion process is stopped. Then, all formed chain-like association derivative paths and corresponding association derivative records on each path are integrated. The integrated information comprehensively reflects all association relationships expanded from the initial data association seed, thereby completing expansion of the range of data association.

[0043] Step S127: recording a business transmission basis, a data attribute association point, and a scenario connection logic of each association derivative derivation, and forming a data association derivative record.

[0044] In the process of association derivation performed by the data association derivative algorithm, key information of each derivation needs to be recorded in detail to form a data association derivative record. Each record contains a starting data identifier (used to identify a starting data entity of a derivation process), a target data identifier (identifying a target data entity obtained by derivation), and an association derivation basis. The association derivation basis further includes a business transmission basis, a data attribute association point, and a scenario connection logic. The business transmission basis indicates which business transmission rule or process sequence is used for the present derivation; the data attribute association point explicitly indicates specific association content of two data entities in attributes; and the scenario connection logic describes how they are connected in application scenarios. For example, in the process of deriving from a maintenance resource allocation data entity to a maintenance construction progress data entity, the business transmission basis is “maintenance resource allocation needs to be followed by maintenance construction and tracking of progress”, the data attribute association point is “the type and quantity of allocated resources are associated with resource consumption in 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”.

[0045] Step S128: based on all data association derivative records, constructing a basic framework of a data association derivative network, in which road network data entities are defined as network nodes and filled with complete attribute information of data, and association derivative relationships are defined as network edges and filled with association derivation bases.

[0046] After completing multiple association derivation deductions and forming a sufficient number of data association derivation records, the infrastructure of the data association derivation network can be built. First, each road network data entity is defined as a node in the network, and the complete attribute information of the data entity is filled in the node, such as the identification, name, detailed attribute description, application scenario, etc. of the data entity, so that the network node has rich information, facilitating subsequent analysis and application. Then, the association derivation relationship embodied in the data association derivation record is defined as an edge in the network, and each edge connects two road network data entity nodes with an association relationship, and the corresponding association derivation basis is filled in the edge, that is, the business transmission basis, data attribute association point, scene connection logic, etc. recorded in the foregoing. Through the above method, the scattered data association derivation records are integrated into a structured network architecture, and the infrastructure of the data association derivation network is initially formed.

[0047] Step S129: Adding association transmission strength description and transmission direction identification to each network edge of the data association derivation network, the association transmission strength description is generated based on the dependence degree of data in business transmission, and the transmission direction identification is consistent with the business process transmission direction.

[0048] In order to make the data association derivation network more perfect and accurately reflect the association relationship between road network data, it is necessary to add association transmission strength description and transmission direction identification to each network edge in the network. The association transmission strength description is used to represent the closeness of the association relationship between two road network data entities, which is generated based on the dependence degree of data in business transmission. If the change of one data entity will have a significant impact on another data entity, the association transmission strength between them will be higher. For example, in the road maintenance business, the dependence degree of maintenance level evaluation data entity on pavement damage data entity is high, and the accuracy of pavement damage data directly affects the result of maintenance level evaluation, so the association transmission strength description between them will be stronger. The transmission direction identification clearly indicates the transmission direction of the association relationship, which must be consistent with the business process transmission direction to ensure that the network can accurately reflect the flow direction of data in the business process.

[0049] Step S1210: Integrating network nodes, network edges, association transmission strength description and transmission direction identification to form a data association derivation network, which is used to dynamically present the association derivation path and dependence relationship of road network data with business transmission.

[0050] Finally, the network nodes, network edges and added associated conduction strength description and conduction direction identifier are integrated to form a data association derived network. The data association derived network can dynamically present the association derived paths and dependency relationships of the road network data generated along the business conduction. Through the data association derived network, users can see how the road network data entities are associated and derived along the business conduction direction starting from the initial data association seed, and the dependency degree and conduction direction between different data entities.

[0051] Step S130: dynamically adapt the road network data combination corresponding to different business conduction paths according to the data association derived network, and construct a dynamic directory unit.

[0052] After forming the data association derived network, the road network data combination corresponding to different business conduction paths can be dynamically adapted according to the network, and then a dynamic directory unit is constructed. Different urban road network businesses have different business conduction paths, for example, road maintenance business has its specific conduction path, and traffic signal optimization business also has its unique conduction path. Each business conduction path needs a specific road network data combination to support. The data association derived network shows the association relationship between the road network data and the conduction path, so the road network data matching each business conduction path can be filtered based on the network. Through dynamic adaptation, it is ensured that the filtered data combination can accurately reflect the demand changes of the business conduction path, and when the business conduction path is adjusted, the data combination can also be updated accordingly. The adapted road network data combination is organized according to certain structure and rules, and a dynamic directory unit is constructed, each dynamic directory unit corresponds to a complete data support system of a business conduction path.

[0053] Step S131: analyze the conduction direction identifier and business conduction node association information in the data association derived network, and extract all independent business conduction paths, each business conduction path containing continuous business conduction nodes and corresponding road network data nodes.

[0054] In this embodiment, the first step of constructing the dynamic directory unit is to analyze the data correlation derivation network to extract all independent service transmission paths. The transmission direction in the data correlation derivation network identifies the transmission direction of data and service, and the service transmission node correlation information describes the connection relationship between each service transmission node. By analyzing the above information, different service transmission paths can be sorted out. Independent service transmission path refers to a complete service process chain that exists relatively independently in the service process and does not intersect or overlap with other paths. For example, in the city road network management service, there may be an independent service transmission path of “road planning design -> road construction -> road completion acceptance -> road daily maintenance”, and another independent service transmission path of “traffic flow monitoring -> traffic signal timing optimization -> traffic operation effect evaluation”. When extracting each service transmission path, it needs to include the continuous service transmission nodes and the corresponding road network data nodes in it. The service transmission node is the key link of the service process, such as the “road planning design” node and the “traffic flow monitoring” node in the above path; the road network data node is the specific road network data entity supporting these service transmission nodes, such as the road planning design node corresponding to the road network data node may include the terrain data node and the land use data node of the planning area.

[0055] Step S132: Based on the service target description of each service transmission path, the core service demand characteristics of the service transmission path are extracted, which include the key data types of service implementation, data use sequence requirements, and data correlation strength threshold.

[0056] For each independent service transmission path extracted, its service target description needs to be clarified, which describes the business purpose that the path ultimately wants to achieve, for example, the service target description of the “traffic flow monitoring -> traffic signal timing optimization -> traffic operation effect evaluation” path may be “through optimizing traffic signal timing, improving road traffic efficiency, and reducing traffic congestion”. Based on this service target description, the core service demand characteristics are extracted. The key data type refers to the data category necessary for the implementation of the service target, for the above traffic signal timing optimization path, the key data types may include real-time traffic flow data, vehicle average speed data, and traffic signal cycle length data of each intersection. The data use sequence requirement specifies the order in which these key data are used in the service process, for example, real-time traffic flow data must be obtained first, then traffic signal timing optimization can be based on this data, and finally the traffic operation effect is evaluated according to the optimized timing scheme. The data correlation strength threshold sets the minimum strength requirement of the correlation relationship between different data, only the data with a correlation strength reaching or exceeding the threshold can be included in the data combination of the service transmission path, to ensure that the correlation between the data is sufficient to support the implementation of the service target.

[0057] 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.

[0058] 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.

[0059] 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.

[0060] 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.

[0061] 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.

[0062] Step S1351: Extract the data usage sequence requirement in the core business appeal feature, split the data usage sequence requirement 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 demand of each data usage stage.

[0063] When the road network data nodes in the initial data combination candidate set are sequentially arranged, the data usage sequence requirement needs to be clarified first. The data usage sequence requirement is extracted from the core business appeal feature, and then it is split into multiple data usage stages. Each data usage stage corresponds to a key business link in the business transmission path. For example, in the road maintenance business transmission path, the data usage sequence requirement can be split into "road surface data collection stage", "maintenance scheme development stage", "maintenance construction stage", "maintenance acceptance stage" and other data usage stages, each of which is a key link in the business path. At the same time, the core data demand of each data usage stage is determined, such as the core data demand of the "road surface data collection stage" may be road surface damage location, damage area, damage degree and other data.

[0064] Step S1352: Analyze the transmission direction identifier of the road network data node corresponding to the initial data combination candidate set in the data correlation derivation network, and determine the transmission position of each road network data node in the business transmission path.

[0065] The road network data nodes in the data correlation derivation network have transmission direction identifiers, which indicate the flow direction of data in the business transmission process. Analyze the transmission direction identifier of each road network data node in the initial data combination candidate set, and determine the transmission position of each node in the business transmission path according to the direction indicated by the identifier. For example, in the transmission direction of "road surface data collection node → maintenance scheme development node → maintenance construction node", the transmission position of the road surface data collection node is 1, the transmission position of the maintenance scheme development node is 2, and the transmission position of the maintenance construction node is 3. The position of each node is determined in this way.

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

[0067] Establish the correspondence between each data usage stage after splitting and the determined transmission position. According to the sequence of key business links in the business transmission path, match each data usage stage to the corresponding transmission position interval, so that the road network data nodes belonging to the data usage stage are all in the corresponding transmission position. For example, the "road surface data collection stage" corresponds to the transmission position 1-5, so the transmission position of all road network data nodes belonging to this stage should be within the range of 1-5.

[0068] Step S1354: Based on the correspondence, the road network data nodes in the initial data combination candidate set are preliminarily sorted in the order of the data use stages to form an initial ordered sequence, and the associated conduction intensity descriptions of each road network data node in the initial ordered sequence are extracted, the associated close descriptions between adjacent road network data nodes are analyzed, and the arrangement order of the nodes in the initial ordered sequence is adjusted so that the nodes with more comprehensive associated dimensions corresponding to the associated close descriptions are arranged adjacently.

[0069] According to the correspondence between the data use stages and the conduction positions, the road network data nodes in the initial data combination candidate set are preliminarily sorted in the order of the data use stages to form an initial ordered sequence. Then, the associated conduction intensity descriptions of each road network data node in the sequence are extracted, such as strong association, medium association, weak association, etc. The associated close descriptions between adjacent nodes are analyzed to understand their comprehensiveness in the attribute, application scenario and other associated dimensions. If the associated close descriptions of two adjacent nodes show that their associated dimensions are not comprehensive enough, and the associated dimensions with other non-adjacent nodes are more comprehensive, the arrangement order of these nodes is adjusted so that the nodes with more comprehensive associated dimensions are arranged adjacently to enhance the association between the data nodes in the sequence.

[0070] Step S1355: Analyze the data application scenario start conditions of each road network data node, so that the application scenario start conditions of the sorted road network data nodes are consistent with the process advancement logic of the business conduction path.

[0071] Each road network data node has its data application scenario start condition, that is, under what circumstances the data of the node will be applied. Analyze these start conditions, and then check whether the application scenario start conditions of the sorted road network data nodes are consistent with the process advancement logic of the business conduction path. For example, the business conduction path requires that the maintenance scheme development can be started only after the road surface data collection is completed, so the application scenario start condition of the maintenance scheme development related data node should be set to be after the road surface data collection is completed, to ensure that the start order of the node conforms to the business process advancement logic.

[0072] Step S1356: Extract the data access dependency relationship of the road network data nodes, and the access of some road network data nodes needs to be based on the output of other road network data nodes as a prerequisite, and the sequence order is further adjusted based on the data access dependency relationship.

[0073] There is a data access dependency relationship between the road network data nodes, and the data access of some nodes must be based on the output results of other nodes. For example, the data access of the maintenance scheme evaluation node may need the maintenance scheme content output by the maintenance scheme formulation node as a prerequisite. Extract these data access dependency relationships and further adjust the sequence order according to the dependency relationship. The dependent node is arranged before the dependent node to ensure that the prerequisite data required when accessing the dependent node already exists, ensuring smooth data access.

[0074] Step S1357: Compare and verify the adjusted sequence with the data use order requirement in the core business appeal feature. If there is inconsistency, adjust the sequence again according to the data use order requirement until the sequence order is consistent with the data use order requirement.

[0075] After the above adjustment, the obtained sequence is compared and verified in detail with the data use order requirement in the core business appeal feature. Check whether the arrangement order of the data nodes in the sequence completely conforms to the sequence specified in the data use order requirement. If inconsistencies are found, such as the arrangement order of the nodes in a certain data use stage is reversed, adjust the sequence again according to the data use order requirement. This process may need to be repeated several times until the sequence order is completely consistent with the data use order requirement.

[0076] Step S1358: Record all adjustment bases in the sequence arrangement process, including the initial sorting, adjustment based on the close association description, adjustment based on the application scenario starting condition, adjustment based on the data access dependency relationship, and readjustment based on the comparison and verification, to form the sequence arrangement description.

[0077] During the entire sequence arrangement process, the basis for each adjustment is recorded. Including the data use stage and the corresponding relationship between the transmission positions based on the initial sorting; the specific association dimension analysis results based on the close association description adjustment; the starting conditions and business process logic correspondence based on the application scenario starting condition adjustment; the dependency relationship details based on the data access dependency relationship adjustment; and the inconsistent points and adjustment methods found based on the comparison and verification readjustment. Organize the above bases to form the sequence arrangement description, so as to facilitate subsequent understanding and tracing of the sequence order.

[0078] Step S1359: Integrate the adjusted road network data node sequence and the sequence arrangement description to generate an ordered data sequence, which is used to meet the sequence requirement and association requirement of data use in the business transmission path.

[0079] Finally, the road network data node sequence and the sequence arrangement description that have been adjusted multiple times and verified by comparison are integrated to form a final ordered data sequence. The data nodes in the ordered data sequence are arranged according to the order requirement of data use in the business conduction path, and the association between the nodes is close and reasonable, which can meet the order and association requirements of data use in the business conduction process.

[0080] Step S136: Based on the data association strength threshold in the core business appeal feature, filter the road network data nodes with an unsatisfactory association conduction strength description in the ordered data sequence, optimize the integrity and association of the ordered data sequence, and extract the unique identifier, data access address, data update period, and data format description of each road network data node in the optimized ordered data sequence to form a data element information set.

[0081] After generating the ordered data sequence, it still needs to be optimized to further improve the quality of data combination. The basis for optimization is the data association strength threshold in the core business appeal feature. The data association strength threshold specifies the minimum strength standard for the association between data nodes. For each road network data node in the ordered data sequence, check whether the association conduction strength description of the node and the previous and next nodes meets the threshold. If the association conduction strength description of a certain node does not meet the requirement, it means that the association between the node and other nodes is weak, which may affect the smooth progress of the business conduction 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 the data nodes in the sequence have strong association. After optimization, the key element information of each road network data node is extracted, including the unique identifier (used to uniquely identify the node), data access address (indicating how to access the data), data update period (explaining the frequency of data update), data format description (describing the storage format of data), etc. The above element information is integrated to form a data element information set.

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

[0083] After obtaining the data element information set, additional identification information needs to be added for each road network data node in the ordered data sequence in order to better manage and apply the data node. The above-mentioned identification information includes service conduction path identification, node position identification in the path, and data correlation dependency identification. The service conduction path identification is used to indicate the service conduction path to which the data node belongs, so as to avoid confusion of data nodes of different paths; the node position identification in the path clearly indicates the specific position of the data node in the ordered data sequence, such as the first node, the second node, etc.; the data correlation dependency identification indicates which other data nodes the data node depends on and which data nodes depend on the node. The setting of the above-mentioned identification must be consistent with the characteristics of the service conduction path, for example, the identification of the service conduction path should correspond to the unique name or number of the path, and the position identification should reflect the order of data use, etc.

[0084] Step S138: The ordered data sequence, the data element information set, and the service conduction path identification, the node position identification in the path, and the data correlation dependency identification are integrated to form a path-specific data combination.

[0085] Then, the ordered data sequence, the data element information set, and the added various types of identification obtained in the foregoing are integrated to form a path-specific data combination. The integration process organizes the above-mentioned information together according to a certain structure, so that the path-specific data combination can reflect the data situation required by the service conduction path. For example, the ordered data sequence can be taken as the main framework, and the corresponding data element information and various types of identification are attached to the position of each data node, so as to form a data combination, which is specially used for a specific service conduction path.

[0086] Step S139: The path-specific data combination is encapsulated according to a unified directory unit structure, the service conduction adaptation description and the associated data calling rule of the path-specific data combination are supplemented, and a dynamic directory unit is formed. The dynamic directory unit is used to realize adaptive adjustment of the data combination with the change of the service conduction path.

[0087] Finally, the path-specific data combination is packaged to form a dynamic directory unit. The packaging adopts a unified directory unit structure, ensuring that the format and organization of all dynamic directory units are consistent, facilitating management and use. During the packaging process, the service conduction adaptation instructions and associated data call rules of the path-specific data combination also need to be supplemented. The service conduction adaptation instructions are used to explain how the data combination adapts to the corresponding service conduction path, including the correspondence between data and service links, the role of data in the service process, etc.; the associated data call rules specify how to call the data in the data combination and how to interact between the data. Through packaging and supplementary instructions, a complete dynamic directory unit is formed, which can automatically adjust the data combination in the dynamic directory unit according to the changes in the service conduction path.

[0088] Step S140: Based on the service conduction attributes of the dynamic directory unit, generate an associated conduction link between the directory units, which reflects the collaborative relationship of road network data in different service conduction paths.

[0089] After the dynamic directory units are constructed, the associated conduction links between the directory units need to be generated based on the service conduction attributes of these units. The service conduction attributes of the dynamic directory unit reflect the characteristics of the service conduction path it belongs to, data requirements, and the associated manner with other services. Different dynamic directory units may correspond to different service conduction paths, but there is often a collaborative relationship between these service conduction paths, for example, the road maintenance service conduction path and the traffic diversion service conduction path need to work together during road construction to reduce the impact of construction on traffic. The associated conduction link between the directory units is used to reflect the above-mentioned collaborative relationship, which can connect different dynamic directory units to realize the sharing and interaction of road network data, ensuring that various services can be carried out collaboratively and efficiently.

[0090] Step S141: Extract the service conduction path identifier, core service demand characteristics, and road network data node identifier in the data combination of each dynamic directory unit to form a directory unit conduction feature set.

[0091] To generate the associated conduction link between the directory units, first, the key information of each dynamic directory unit needs to be extracted to form a directory unit conduction feature set. The above-mentioned key information includes the service conduction path identifier, which uniquely identifies the service conduction path to which the dynamic directory unit belongs; the core service demand characteristics, which reflect the core data requirements and goals of the service conduction path; and the road network data node identifier in the data combination, which clearly identifies the specific road network data nodes contained in the dynamic directory unit. By extracting these information, the characteristics and requirements of each dynamic directory unit can be fully understood, and thus the above-mentioned information is integrated together to form a directory unit conduction feature set.

[0092] Step S142: Based on the catalog unit conduction feature set, analyze the core business appeal feature overlap area of different dynamic catalog units, identify catalog unit groups with business collaboration needs, and determine business collaboration needs based on business process connection relationships or data sharing needs.

[0093] After obtaining the catalog unit conduction feature set, the core business appeal features of different dynamic catalog units are analyzed to find the overlap area between them. The core business appeal feature overlap area means that different business conduction paths have common data needs, which is often the basis for business collaboration. For example, the core business appeal features of the road maintenance business conduction path and the traffic diversion business conduction path may overlap in "construction road section traffic flow data", because road maintenance construction will affect traffic flow, and traffic diversion needs to develop a plan based on traffic flow data. Based on these overlapping areas, catalog 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 maintenance construction is completed and traffic recovery diversion is needed) or data sharing needs (such as both businesses need to use the same traffic flow data).

[0094] Step S143: Extract the road network data node identifier in the data combination body of each dynamic catalog unit in each catalog unit group, and find the road network data node identifier common to different catalog units.

[0095] For the identified catalog unit groups with business collaboration needs, the road network data node identifier in the data combination body of each dynamic catalog unit needs to be further extracted, which represents the specific road network data node contained in the catalog unit. By comparing the road network data node identifiers of different catalog units, the road network data node identifiers common to them can be found. The common road network data node identifier is the key connection point of data sharing and association between different catalog units, for example, two dynamic catalog units may both contain "a road section traffic flow data node identifier", which is the road network data node common to them and can be used as an important data bridge for their collaboration.

[0096] Step S144: Based on the common road network data node identifier, extract the associated conduction strength description and conduction direction identifier of the corresponding road network data entity, and determine the data conduction direction and association tightness description between different catalog units.

[0097] After finding the common road network data node identifiers, the associated conduction intensity descriptions and conduction direction identifiers of the road network data entities corresponding to the identifiers need to be extracted from the data association derived network. The associated conduction intensity descriptions reflect the closeness of the association relationship between the road network data entity and other data entities, and the conduction direction identifiers indicate the conduction direction of the data. Based on this information, the data conduction direction between different directory units can be determined, that is, data flows from which directory unit to which directory unit, for example, the construction progress data of the maintenance business directory unit may flow to the traffic diversion business directory unit to support the formulation of the traffic diversion scheme. At the same time, according to the associated conduction intensity descriptions, the association closeness descriptions between different directory units can be generated, which explain the closeness of the coordination relationship between them, such as "high coordination", "moderate coordination", etc.

[0098] Step S145: Analyze the business conduction path identifiers of the dynamic directory units in each directory unit group, extract the sequential connection order or parallel cooperation relationship between the business conduction paths, and form the business conduction coordination logic.

[0099] In addition to the data-level association, the coordination relationship of the dynamic directory units in the directory unit group also needs to be analyzed from the business level. By analyzing the business conduction path identifiers of the dynamic directory units, their belonging business conduction paths can be known. Further research on the relationship between these business conduction paths can extract their sequential connection order or parallel cooperation relationship. The sequential connection order refers to the completion of one business conduction path before another business conduction path can start, for example, the "road construction" business conduction path is completed before the "road completion acceptance" business conduction path can start. The parallel cooperation relationship refers to the simultaneous performance of multiple business conduction paths, which cooperate with each other, for example, the "traffic signal optimization" business conduction path and the "public transportation scheduling" business conduction path may cooperate in parallel during the morning peak period to jointly ensure smooth traffic. After arranging the above relationship, the business conduction coordination logic is formed, which is used to guide the coordination work between the directory units.

[0100] Step S146: Take the common road network data node identifiers as the connection hubs, combine the data conduction direction, the association closeness description, and the business conduction coordination logic to build the initial association links between the directory units. The initial association links include link start point identifiers, link end point identifiers, and connection basis.

[0101] Step S1461: Extract the complete attribute information, the associated conduction intensity descriptions, and the conduction direction identifiers of the road network data entities corresponding to the common road network data node identifiers to form the hub data feature set.

[0102] In the process of building the initial associated link with the common road network data node identifier as the connection hub, the detailed information of the road network data entity corresponding to the common node identifier needs to be extracted first to form the hub data feature set. The complete attribute information includes the name, data type, collection method, storage location, etc. of the road network data entity; the associated conduction strength description indicates the closeness of the association between the entity and other data entities; and the conduction direction identifier indicates the conduction direction of the data. For example, if the common road network data node identifier corresponds to "a certain main road traffic flow data entity", its complete attribute information may include data collection interval, covered lane number, etc., and the associated conduction strength description may be "strongly associated with the surrounding road network traffic capacity data entity", and the conduction direction identifier is "from the traffic flow monitoring node to the signal timing optimization node". The above information is integrated to form the hub data feature set.

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

[0104] With the hub data feature set, the associated dynamic directory unit corresponding to each common road network data node identifier is determined according to the road network data entity information therein. Each common node identifier may be associated with multiple dynamic directory units, for example, "a certain main road traffic flow data entity" may be associated with "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 determined, i.e. data provider or data receiver. The data provider is the directory unit that provides data to the link, and the data receiver is the directory unit that obtains data from the link. For example, "traffic signal optimization dynamic directory unit" may be the data receiver of "a certain main road traffic flow data entity", while "traffic flow monitoring dynamic directory unit" is the data provider of the data entity.

[0105] Step S1463: According to the data conduction direction identifier, determine the data transmission direction between the associated dynamic directory units to form the conduction direction framework of the initial associated link, which includes the starting directory unit, the ending directory unit and the transmission path direction.

[0106] According to the conduction direction identifier in the hub data feature set, the data transmission direction between the associated dynamic directory units is determined. The conduction direction identifier indicates which entity the data is transmitted from and which entity the data is transmitted to, and accordingly the transmission path of the data between the associated dynamic directory units can be determined. For example, the conduction direction identifier of the “certain trunk road traffic flow data entity” is “from the traffic flow monitoring node to the signal timing optimization node”, and then in the corresponding associated dynamic directory unit, the “traffic flow monitoring dynamic directory unit” is the starting directory unit, the “traffic signal optimization dynamic directory unit” is the terminal directory unit, and the transmission path direction is from the starting directory unit to the terminal directory unit, thereby forming the conduction direction framework of the initial associated link.

[0107] Step S1464: Based on the associated close description, a connection strength attribute is added to the conduction direction framework of the initial associated link, and the connection strength attribute directly corresponds to the associated close description.

[0108] The associated close description reflects the closeness of the association between the road network data entities, and based on this, a connection strength attribute is added to the conduction direction framework of the initial associated link. The connection strength attribute directly corresponds to the associated close description, and if the associated close description is “strong association”, the connection strength attribute value is higher; if it is “weak association”, the connection strength attribute value is lower. For example, the associated close description of the “certain trunk road traffic flow data entity” and the “signal timing optimization data entity” is “strong association”, and then in the conduction direction framework of the initial associated link corresponding to them, the connection strength attribute is set to high, to indicate that the importance of data transmission of this link is higher.

[0109] Step S1465: Analyze the business conduction coordination logic, extract the key business nodes and data interaction requirements in the coordination process, and convert the key business nodes and data interaction requirements into connection rules of the initial associated link, which include the timing, content and format of data interaction.

[0110] The business conduction coordination logic specifies the way and rules of coordination between businesses, and analyzing the logic can extract the key business nodes and data interaction requirements in the coordination process. The key business nodes are important links in the coordination process, such as the “signal timing scheme generation node”; the data interaction requirements include the specific content, time requirements, etc. of data interaction. The above key business nodes and data interaction requirements are converted into connection rules of the initial associated link, for example, the “signal timing scheme generation node” needs traffic flow data, and then the connection rule will specify that the timing of data interaction is before the start of the node business, the content is the latest traffic flow data, and the format is a specific structured data format.

[0111] 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.

[0112] 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."

[0113] 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.

[0114] 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.

[0115] 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.

[0116] There can be more than one associated link in the urban road network service, and the newly built initial associated link can overlap with other potential associated links in the same data node or the same directory unit, which can cause connection conflicts, such as both links requiring data from the same data provider at the same time, causing the data provider to be overloaded. At this time, the connection rules of the conflicting links need to be adjusted according to the conduction priority information (the core service link priority is higher than the general service link) or the service conduction coordination logic (such as the sequence of the service flow), such as modifying the data transmission time of one of the links to eliminate the conflict and ensure that all links can work normally.

[0117] Step S1469: Record the building basis of the initial associated link, including the hub data feature set, the conduction direction, the associated tightness description, and the service conduction coordination logic, to form a link building specification.

[0118] The link building specification is a detailed record of the construction process of the initial associated link, which systematically organizes various key information relied on during the building process to facilitate subsequent maintenance, optimization, or traceability of the link. When recording the building basis, the specific content related to link building in the hub data feature set needs to be listed in detail, such as the complete attribute information of the road network data entity corresponding to the shared road network data node identifier, the associated conduction strength description, and the conduction direction identifier. These information are the basic data support for the establishment of the link. The conduction direction, as the core guide of data transmission of the link, its determination process and final result also need to be clearly recorded, including how to determine the data transmission direction between the associated dynamic directory units based on the conduction direction identifier in the hub data feature set, and the specific content of the formed starting directory unit, ending directory unit, and transmission path direction. The associated tightness description reflects the tightness of the link connection, and when recording, it needs to be explained how to generate this description based on the number of attribute matching points and the scene overlap range, and how this description affects the setting of the link connection strength attribute. The service conduction coordination logic is the business-level guidance for link building, which needs to be recorded in detail how to extract this logic by analyzing the sequence or parallel cooperation relationship between the service conduction paths, and how this logic is converted into the connection rules of the initial associated link to ensure that the link building meets the actual needs of the business. By integrating the above basis information in an orderly manner, the link building specification is formed.

[0119] Step S14610: Integrate the basic structure of the initial associated link, the associated data calling rules of the participating directory units, and the link building specification to form the initial associated link, which is used to clearly define the association method and coordination logic between the directory units based on the shared road network data node identifier.

[0120] After the above series of steps, the basic structure of the initial associated link, the associated data call rules of the participating directory unit, and the link building instructions have been obtained respectively. At this time, it is necessary to integrate these three parts organically to form a complete initial associated link. During the integration process, consistency and coherence between the parts are ensured. The link identifier, participating directory unit identifier, transmission direction, connection strength, connection rules, and other elements in the basic structure need to be matched with the permission range, transmission method, format requirement, and other contents in the associated data call rules of the participating directory unit. At the same time, the link building instructions should be able to reasonably and detailedly explain the formation process of the basic structure and the associated data call rules. For example, if the data transmission format is specified as JSON in the basic structure, the associated data call rules of the participating directory unit should also explicitly support JSON format data transmission, and the link building instructions should explain why JSON format is selected, which may be based on the requirements of data compatibility and parsing efficiency in the business transmission coordination logic. Through the above integration, the final initial associated link can clearly and accurately specify the association method and coordination logic between different directory units based on the common road network data node identifier, providing a specific and operable implementation path for business coordination and data association transmission between dynamic directory units in urban road network business.

[0121] Step S147: Add coordination type identifier and transmission priority information to the initial associated link. The coordination type identifier distinguishes between data sharing type coordination, business connection type coordination, and scene complementary type coordination. The transmission priority information is generated based on business attributes.

[0122] In order to make the initial associated link more perfect and operable, it is necessary to add coordination type identifier and transmission priority information. The coordination type identifier is used to distinguish different types of coordination relationship. Common coordination types include data sharing type coordination (mainly to realize the sharing and use of data), business connection type coordination (based on the sequential connection of business processes), and scene complementary type coordination (different business scenes complement each other to achieve a common goal). Transmission priority information is determined according to business attributes, such as core business having higher transmission priority than general business, and emergency business having higher transmission priority than regular business. By adding these information, the coordination method and importance of the associated link can be made more clear.

[0123] Step S148: Extract the associated data call rules of each dynamic directory unit and integrate the associated data call rules into the corresponding initial associated link to determine the permission range, transmission method, and format requirement of data call in the initial associated link.

[0124] Each dynamic directory unit has its associated data call rules, which stipulate how to call the data in the directory unit. When building the initial associated link, the above-mentioned associated data call rules need to be integrated into the link to ensure that the data call between different directory units can proceed smoothly. Specifically, the authority scope of data call (which users or systems can call the data), the transmission method (such as data transmission through HTTP protocol, FTP protocol, etc.), and the format requirement (data transmission and exchange in what format, such as JSON format, XML format, etc.) need to be determined according to the associated data call rules.

[0125] Step S149: Based on all the initial associated links, the collaborative type identifier, the conduction priority information, and the associated data call rules, the infrastructure of the associated conduction link network is built, which contains link nodes, link connection relationships, and link attributes. The link nodes are dynamic directory units.

[0126] All the initial associated links and the added collaborative type identifier, conduction priority information, and associated data call rules are integrated to build the infrastructure of the associated conduction link network. In this infrastructure, the link nodes are dynamic directory units, and each node represents a data support system of a business conduction path. The link connection relationship is embodied through the initial associated link, which describes the association method between the dynamic directory units. The link attributes include the collaborative type identifier, the conduction priority information, and the associated data call rules. By building this infrastructure, a preliminary network structure is formed, which shows the associated conduction relationship between the dynamic directory units.

[0127] Step S1410: Integrate the link nodes, the link connection relationships, and all the link attributes to form the associated conduction link between the directory units, which is used to realize the business collaboration and data associated conduction between different dynamic directory units.

[0128] After all the initial association links are built, the above links need to be integrated as a whole to form the association transmission links between the directory units. First, the link nodes are the dynamic directory units, each dynamic directory unit exists as an independent node in the association transmission link network, with a unique identifier and specific business transmission attributes. Then, all initial association links are sorted out to determine the link connection relationship, that is, which dynamic directory units are connected to each other through the initial association links to form a complex network structure. At the same time, the attribute information of all links is collected, including the coordination type identifier, the transmission priority information, the association data calling rule, the connection strength, the connection rule, etc. In the integration process, the link connection relationship needs to be checked and optimized to ensure that there is no redundant or conflicting connection. For overlapping or conflicting links, they are adjusted and selected according to the transmission priority information and business transmission coordination logic to ensure the rationality and efficiency of the entire association transmission link network. The link nodes, link connection relationships and all link attributes are organized and stored according to a certain logical structure to finally form the association transmission links between the directory units. The association transmission links can organically connect each dynamic directory unit in the city road network management, so that different dynamic directory units can efficiently cooperate and conduct data association transmission according to business needs, realize the sharing of data resources and smooth connection of business processes, and improve the overall efficiency and intelligent level of city road network management.

[0129] Step S150: integrate the dynamic directory units and the association transmission links to form a closed-loop city road network data resource directory, which can be dynamically updated with changes in business association transmission.

[0130] After the construction of dynamic directory units and the generation of association transmission links, the two parts need to be integrated to form a closed-loop city road network data resource directory. Dynamic directory units are the basic components of the city road network data resource directory, and each unit corresponds to a complete data support system of a business transmission path; the association transmission link is the link connecting these basic units, realizing the business cooperation and data association transmission between different units. Through integration, the dynamic directory units are organized according to the connection relationship and coordination logic specified by the association transmission link to form a closed-loop system with clear hierarchy, clear structure and self-updating and optimization capabilities. The city road network data resource directory can comprehensively and accurately reflect the data resource situation of city road network business, and can be dynamically updated with changes in business association transmission sources, always maintaining its timeliness and accuracy.

[0131] Step S151: Collect all the completed dynamic directory units, extract the complete data combination, service transmission adaptation description, associated data call rules and directory unit unique identifier of each dynamic directory unit, and form a directory unit core information library.

[0132] In order to realize the effective integration of dynamic directory units and associated transmission links, it is necessary to first collect and manage all the completed dynamic directory units. During the collection process, the core information of each dynamic directory unit needs to be extracted comprehensively, including complete data combination, service transmission adaptation description, associated data call rules and directory unit unique identifier. The complete data combination contains all road network data nodes supporting the service transmission path and their related identifiers and meta information. The service transmission adaptation description explains in detail how the data combination adapts to the corresponding service transmission path, including the correspondence between data and business links, the role of data in the business process, etc. The associated data call rules specify how to call the data in the data combination and how to interact between the data. The directory unit unique identifier is used to uniquely distinguish different dynamic directory units, ensuring that there is no confusion in the subsequent integration and management process. The above extracted core information is stored and organized according to a unified data format and structure to form a directory unit core information library. The establishment of the directory unit core information library enables quick and accurate access to the key information of each dynamic directory unit, facilitating operations such as associated mapping and hierarchical division.

[0133] Step S152: Retrieve the associated transmission links between the directory units, extract the link node identifier, connection relationship, collaboration type identifier, transmission priority information and associated data call rules in the associated transmission links, and form a link core information library.

[0134] While collecting the core information of dynamic directory units, the associated transmission links between the directory units generated earlier also need to be retrieved, and their core information needs to be extracted. The core information in the associated transmission links includes link node identifier, connection relationship, collaboration type identifier, transmission priority information and associated data call rules. The link node identifier indicates the dynamic directory units connected by the link. The connection relationship describes the connection method and transmission path between the link nodes. The collaboration type identifier distinguishes the collaboration types of the link, such as data sharing type collaboration, business connection type collaboration, scene complementary type collaboration, etc. The transmission priority information determines the priority level of the link in data transmission and business collaboration according to the business attributes. The associated data call rules specify the permission range, transmission method, format requirements, etc. for data call on the link. The above extracted core information of the associated transmission links is organized and structured to form a link core information library. The link core information library corresponds to the directory unit core information library, and together they constitute the basic data resources for integrating dynamic directory units and associated transmission links.

[0135] Step S153: Based on the directory unit unique identifier, the association mapping between the directory unit core information library and the link core information library is established, so as to associate each associated transmission link with the dynamic directory unit core information participating in cooperation.

[0136] The directory unit unique identifier is the key link connecting the directory unit core information library and the link core information library. By matching the link node identifier in the link core information library with the directory unit unique identifier in the directory unit core information library, the association mapping relationship between the two information libraries can be established. For example, the link node identifier is "dynamic directory unit A" and "dynamic directory unit B", and by searching the corresponding directory unit unique identifier in the directory unit core information library, the link is associated with the complete data combination of "dynamic directory unit A" and "dynamic directory unit B", business transmission adaptation instructions, associated data calling rules and other core information. The above association mapping makes each associated transmission link no longer exist in isolation, but can be corresponded to the specific dynamic directory unit participating in cooperation and its core information, ensuring that the relationship between the dynamic directory unit and the associated transmission link in the integrated urban road network data resource directory is clear and the logic is clear.

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

[0138] After establishing the association mapping between the directory unit core information library and the link core information library, all dynamic directory units in the directory unit core information library are hierarchically divided according to the transmission priority information of the associated transmission link. The transmission priority information reflects the importance of different associated transmission links in business cooperation and data transmission, and the dynamic directory units connected by high-priority associated transmission links usually correspond to the core business transmission path in urban road network management. Therefore, the dynamic directory units associated with high-priority associated transmission links are divided into the directory main level, and these directory units support the core business of urban road network management, such as the dynamic directory units corresponding to the core business transmission paths of road daily maintenance, real-time traffic signal optimization, main road traffic flow monitoring, etc. The dynamic directory units associated with other priority associated transmission links are divided into the directory cooperation level, and these directory units are mainly used to support the cooperation of core business or handle some secondary and auxiliary business transmission paths. Through hierarchical division, the structure of the urban road network data resource directory is more clear, the importance of core business data resources is highlighted, and it is convenient for users to quickly locate and access key data.

[0139] Step S155: In the directory main level and the directory coordination level, the horizontal association structure of the directory unit is built according to the connection relationship of the associated conduction link, and the horizontal association structure reflects the coordination logic between the directory units in the same level.

[0140] After the division of the directory main level and the directory coordination level, the horizontal association structure of the directory unit needs to be built in each level. The horizontal association structure is built according to the connection relationship of the associated conduction link, that is, the dynamic directory units in the same level are connected to each other through the associated conduction link to form a network for coordinated work. For example, in the directory main level, the "main road traffic flow monitoring dynamic directory unit" is connected to the "traffic signal real-time optimization dynamic directory unit" through a high-priority associated conduction link, and at the same time, the "traffic signal real-time optimization dynamic directory unit" is connected to the "traffic congestion early warning dynamic directory unit". These connection relationships jointly constitute the horizontal association structure inside the directory main level. The horizontal association structure inside the directory main level can reflect the coordination logic between the directory units in the same level, such as data sharing, business process connection, scene complementation, and other coordination relationships, so that the dynamic directory units in the same level can efficiently coordinate work according to business needs to achieve the core business goal.

[0141] Step S156: Based on the business connection relationship of the associated conduction link, the vertical association structure of the directory unit is built across the directory main level and the directory coordination level, and the vertical association structure reflects the business conduction path between the directory units in different levels.

[0142] In addition to building the horizontal association structure inside the level, the vertical association structure of the directory unit also needs to be built across the directory main level and the directory coordination level. The vertical association structure is built based on the business connection relationship of the associated conduction link, that is, there is a business connection or data dependency relationship between the dynamic directory units in different levels through the associated conduction link. For example, the "secondary road traffic flow data collection dynamic directory unit" in the directory coordination level needs to transmit the collected data to the "traffic flow data analysis dynamic directory unit" in the directory main level for processing and analysis, and the above business connection relationship constitutes part of the vertical association structure. The vertical association structure can reflect the business conduction path between the directory units in different levels, so that the core business conduction path can extend from the directory main level to the directory coordination level, or support the business development of the directory main level from the directory coordination level, realizing the smooth flow of data and the coordinated promotion of business between different levels.

[0143] Step S157: The horizontal association structure and the vertical association structure are integrated to build the overall association framework of the city road network data resource directory, and the overall association framework includes three core elements of level division, associated path, and coordination rule.

[0144] After the horizontal and vertical association structures are built respectively, the two structures need to be integrated to build the overall association framework of the city road network data resource directory. During the integration process, the hierarchical division is taken as the basis of the overall association framework, and the scope and boundaries of the directory main level and the directory coordination level are clarified. The association paths contained in the horizontal and vertical association structures are combed and integrated to form a complete association path network covering all dynamic directory units. At the same time, the coordination rules of all association transmission links, including coordination type identification, association data calling rules, connection rules, etc., are collected and sorted as the coordination rule elements of the overall association framework. Through integration, the overall association framework has the characteristics of clear hierarchical division, clear association path, and perfect coordination rule. The three core elements support and cooperate with each other to form the basic framework of the city road network data resource directory.

[0145] Step S158: Fill all dynamic directory unit information in the directory unit core information library into the corresponding position of the overall association framework, and supplement the association transmission explanation and data interaction process between the directory units.

[0146] After the overall association framework is built, all dynamic directory unit information stored in the directory unit core information library needs to be filled into the corresponding position of the framework. According to the hierarchical division result of the dynamic directory unit, the dynamic directory unit information belonging to the directory main level is filled into the main level area of the overall association framework, and the dynamic directory unit information belonging to the directory coordination level is filled into the coordination level area. During the filling process, not only the complete data combination, business transmission adaptation explanation, association data calling rules, and directory unit unique identification of the dynamic directory unit, but also the association transmission explanation and data interaction process between the directory units need to be supplemented according to the association path in the overall association framework. The association transmission explanation explains in detail how two dynamic directory units are associated through which association transmission link, and the basis and purpose of the association. The data interaction process describes the specific steps of data transmission, processing, and feedback between two dynamic directory units. Through filling and supplementing these information, the overall association framework becomes rich and specific, and can intuitively show the whole content and internal association relationship of the city road network data resource directory.

[0147] Step S159: Build a directory dynamic update trigger mechanism. The directory dynamic update trigger mechanism takes the change of the business association transmission source as the trigger condition, and automatically triggers the update of the dynamic directory unit and the association transmission link when the business process transmission node or transmission rule changes.

[0148] Step S1591: Access the real-time monitoring interface of the business association conduction source, obtain the real-time state information of the business process conduction node and the conduction rule, and the real-time state information includes the change types of node addition, node deletion, rule modification, and rule addition.

[0149] The first step of building a directory dynamic update triggering mechanism is to realize real-time monitoring of the business association conduction source. Access the real-time monitoring interface of the business association conduction source, continuously obtain the real-time state information of the business process conduction node and the conduction rule through the interface, and the above real-time state information records various changes of the business association conduction source in detail. The specific change types include node addition, i.e. a new business process conduction node is added; node deletion, i.e. a certain business process conduction node is removed; rule modification, i.e. the existing conduction rule is adjusted or updated; rule addition, i.e. a new conduction rule is added, etc. By obtaining these state information in real time, the dynamic changes of the business association conduction source can be grasped in time.

[0150] Step S1592: Based on the real-time state information, access the change recognition module, and the change recognition module is used for automatically recognizing the change content, change range, and change influence dimension of the business process conduction node and the conduction rule.

[0151] After obtaining the real-time state information, it is input into the change recognition module. The change recognition module has the ability to analyze and process the above information, and can automatically recognize the specific change content of the business process conduction node and the conduction rule, such as the added node name, function, and modified rule specific provisions; the change range, i.e. which business processes, conduction nodes or rules are involved in the change; and the change influence dimension, such as the possible influence on data demand, business collaboration, and conduction path. Through the processing of the change recognition module, the specific situation of the change of the business association conduction source can be accurately grasped.

[0152] Step S1593: Access the change influence evaluation model, input the change content and change range into the change influence evaluation model, and the change influence evaluation model outputs the influence dimension and influence degree description of the change on the existing dynamic directory unit and associated conduction link.

[0153] In order to evaluate the influence of the change of the business association conduction source on the existing system, the change influence evaluation model is accessed. The change content and change range recognized by the change recognition module are input into the model as input parameters. The change influence evaluation model analyzes the input change content and range based on the preset evaluation algorithm and business rules, and evaluates the possible influence dimension of these changes on the existing dynamic directory unit and associated conduction link, such as affecting data combination, business conduction adaptation description, associated data calling rule, etc.; and the influence degree description, such as serious influence, medium influence, slight influence, etc.

[0154] Step S1594: Based on the impact dimension and impact degree description, determine the range of dynamic directory units and associated conduction link ranges that need to be updated, and form an update object list containing object identification and update priority.

[0155] According to the impact dimension and impact degree description output by the change impact evaluation model, further determine the specific range of dynamic directory units and associated conduction links that need to be updated. For dynamic directory units and associated conduction links that are severely affected, they are included in the update range; for those with lighter impact, it can be decided whether to update or postpone the update according to the actual situation. Then, assign object identification to these objects that need to be updated in order to uniquely identify, and determine the update priority according to the impact degree, business importance and other factors, and form a detailed update object list.

[0156] Step S1595: Configure an update process for each dynamic directory unit in the update object list, which includes data combination adjustment, business conduction adaptation instruction modification, and associated data call rule update operation steps.

[0157] For each dynamic directory unit in the update object list, a special update process needs to be configured. The update process should specify specific operation steps, including data combination adjustment, i.e. adding, deleting or modifying data combinations in the dynamic directory unit according to the change; business conduction adaptation instruction modification, updating the instruction document to reflect the changed business conduction adaptation situation; associated data call rule update, adjusting the rules of data call permission, method, format, etc. to ensure that the dynamic directory unit can adapt to the change of business associated conduction source.

[0158] Step S1596: Configure an update process for each associated conduction link in the update object list, which includes link connection relationship adjustment, collaboration type identification modification, and conduction priority information update operation steps.

[0159] For each associated conduction link in the update object list, an update process also needs to be configured. The process includes link connection relationship adjustment, which adjusts the starting point, ending point or intermediate connection node of the link according to the change of business conduction node and rule; collaboration type identification modification, which updates the collaboration type of the link, such as adjusting from data sharing type collaboration to business connection type collaboration; conduction priority information update, which re-determines the conduction priority of the link according to the changed business importance, to ensure the accuracy and effectiveness of the associated conduction link.

[0160] Step S1597: Access the update execution module, which is configured to automatically execute the update operation of dynamic directory units and associated conduction links according to the update process and update priority.

[0161] An access update execution module is pre-configured to automatically perform update operations on the dynamic directory unit and the associated transmission link according to the previously formulated update procedure and the update priority in the update object list. During the update process, the update execution module strictly performs data combination adjustment, adaptation instruction modification, rule update, and other operations according to the operation steps, ensuring the accuracy and efficiency of the update and reducing manual intervention.

[0162] Step S1598: Access the update verification module. The update verification module can verify the consistency of the updated dynamic directory unit and the associated transmission link with the new state of the business association transmission source after the update operation is performed. The verification process is based on the business association transmission logic model.

[0163] After the update operation is completed, the access update verification module needs to be called. The function of the update verification module is to verify whether the updated dynamic directory unit and the associated transmission link are consistent with the new state of the business association transmission source. The verification process is based on the business association transmission logic model, which checks whether the updated objects meet the requirements of the new business association transmission source in terms of data combination, transmission rules, and coordination relationships, ensuring that the updated system can operate normally.

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

[0165] During the entire update process, detailed log records of all operations are required. The operation logs should include the identification of the update object, the time of the update operation execution, the specific update content, the basis for the update (such as the change impact assessment result), and the verification result output by the update verification module. The above log information is sorted and archived to form a complete update archive, which can be used for subsequent auditing, tracing, and problem troubleshooting of the update process.

[0166] Step S15910: Integrate the change identification module, the change impact assessment model, the update procedure, the update execution module, the update verification module, and the update archive to form a directory dynamic update triggering mechanism.

[0167] Finally, the change identification module, the change impact assessment model, the update procedure configured for the dynamic directory unit and the associated transmission link, the update execution module, the update verification module, and the update archive are integrated to form a directory dynamic update triggering mechanism. When the business association transmission source changes, the directory dynamic update triggering mechanism can automatically complete the entire process from change identification, impact assessment, update execution to result verification, ensuring that the city road network data resource directory can be dynamically updated in a timely and accurate manner following the changes in the business association transmission source.

[0168] Step S1510: integrate the overall association framework, the directory unit information, the association conduction description, the data interaction flow and the directory dynamic updating trigger mechanism to form a closed-loop urban road network data resource directory. The urban road network data resource directory can be dynamically updated with the change of business association conduction.

[0169] After the foregoing steps, the overall association framework has been constructed, the directory unit information has been filled, the association conduction description and the data interaction flow have been supplemented, and the directory dynamic updating trigger mechanism has been built. At this time, the above components need to be systematically integrated to form the final closed-loop urban road network data resource directory. During the integration process, it is necessary to ensure smooth interface between the components, normal data interaction and consistent logical relationship. The overall association framework, as the skeleton of the directory, supports the organization and display of the directory unit information, the association conduction description and the data interaction flow; the directory dynamic updating trigger mechanism monitors the change of the business association conduction source in real time and drives the directory to update accordingly. Through integration, the urban road network data resource directory has the characteristics of comprehensive data resources, clear association relationship, efficient business cooperation, timely and accurate update, and can realize self-circulation and dynamic optimization, that is, form a closed-loop system, provide omnidirectional and high-quality data services for urban road network management business, and can continuously evolve and improve with the development and change of business.

[0170] Based on the same inventive concept, please refer to Figure 2 , which shows a structural schematic block diagram of a business graph combined urban road network data resource directory generation system 100 provided by an embodiment of the present application for executing the above-mentioned business graph combined urban road network data resource directory generation method. The business graph combined urban road network data resource directory generation system 100 can include a communication unit 110, a machine readable storage medium 120 and a processor 130.

[0171] In this embodiment, the machine readable storage medium 120 and the processor 130 are both located in the business graph combined urban road network data resource directory generation system 100 and are separately arranged. 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. Among them, the machine readable storage medium 120 is used to store machine executable instructions for executing the scheme of the present application, and the processor 130 is used to execute the machine executable instructions stored in the machine readable storage medium 120 to realize the business graph combined urban road network data resource directory generation method provided by the foregoing method embodiment.

[0172] It should be noted that, in order to simplify the description of the present application and help understand one or more embodiments of the present application, in the foregoing description of the embodiments of the present application, various features are sometimes combined into one embodiment, figure or description thereof.

Claims

1. A method for generating a city road network data resource directory combined with a service map, characterized in that, The method comprises: accessing the city road network service association conduction source and the road network basic data, generating a service data association conduction pool, the service association conduction source contains the process association information and data appeal association information of various services of city road network; based on the service association conduction logic, deducing the association derivative relationship between the road network data for the service data association conduction pool, forming a data association derivative network, the data association derivative network embodies the dynamic association path of road network data along with service conduction; according to the data association derivative network, dynamically adapting the road network data combination corresponding to different service conduction paths, building a dynamic directory unit, each dynamic directory unit corresponds to a complete data support system of a service conduction path; based on the service conduction attribute of the dynamic directory unit, generating the association conduction link between the directory units, the association conduction link embodies the road network data cooperation relationship of different service conduction paths; integrate the dynamic directory unit and the association conduction link, form a closed-loop city road network data resource directory, which can realize dynamic update along with the change of service association conduction.

2. The method for generating a city road network data resource directory combined with a business map according to claim 1, characterized in that, The method comprises: accessing the business process conduction node and conduction rule in the city road network service association conduction source, extracting the association data appeal and conduction direction information of each business process conduction node, forming a business conduction node feature, the business conduction node feature contains node identification, data appeal type, conduction target node identification; call the data attribute description, data application scene range, data association interface information in the road network basic data, generate road network data basic feature, the dimension of road network data basic feature and the data appeal type dimension of business conduction node feature keep corresponding; access the business association conduction logic model, the business association conduction logic model contains the definition of the conduction order of business process conduction node, the matching rule of data appeal and road network data feature, the derivation trigger condition of association relationship; input the business conduction node feature into the business association conduction logic model, filter out the road network data basic feature corresponding to the data appeal type of each business conduction node through the matching rule in the business association conduction logic model, output the candidate road network data feature set corresponding to each business conduction node; based on the candidate road network data feature set, extract the corresponding road network data entity, analyze the attribute association item and application scene overlap area of the road network data entity, determine the data association seed, the data association seed is the initial direct association relationship between road network data entities; through the data association derivation algorithm, taking the data association seed as the starting point, along the business conduction direction, deducing the adjacent road network data entity which has application scene connection or attribute complement with the current road network data entity, expanding the data association range; recording the business conduction basis, data attribute association point and scene connection logic of each association derivation deduction, forming a data association derivation record, each data association derivation record containing a starting data identifier, a target data identifier and an association deduction basis; based on all data association derivation records, constructing the basic framework of the data association derivation network, wherein the road network data entity is defined as a network node and filled with data complete attribute information, and the association derivation relationship is defined as a network edge and filled with association deduction basis; adding association conduction strength description and conduction direction identification to each network edge of the data association derivation network, the association conduction strength description being generated based on the dependence degree of data in business conduction, and the conduction direction identification being consistent with the business process conduction direction; integrating network nodes, network edges, association conduction strength description and conduction direction identification to form the data association derivation network, which is used to dynamically present the association derivation path and dependence relationship of road network data along with business conduction.

3. The method for generating a city road network data resource directory combined with a business map according to claim 1, characterized in that, based on the data association derivation network, dynamically adapting the road network data combination corresponding to different business conduction paths to construct a dynamic directory unit, including: analyzing the conduction direction identification and business conduction node association information in the data association derivation network, extracting all independent business conduction paths, each business conduction path containing continuous business conduction nodes and corresponding road network data nodes; based on the business target description of each business conduction path, extracting the core business demand characteristics of the business conduction path, the core business demand characteristics including key data types, data use sequence requirements and data association strength threshold of business implementation; traversing the road network data nodes corresponding to the business conduction path in the data association derivation network, extracting the complete attribute information and association conduction strength description of each road network data node to form a path data feature set; according to the key data types in the core business demand characteristics, screening the road network data nodes in the path data feature set that meet the requirements to form an initial data combination candidate set; according to the data use sequence requirements in the core business demand characteristics, combining the conduction direction identification of the data association derivation network, sequentially arranging the road network data nodes in the initial data combination candidate set to generate an ordered data sequence; based on the data association strength threshold in the core business demand characteristics, filtering the road network data nodes in the ordered data sequence whose association conduction strength description does not meet the requirements, optimizing the integrity and association of the ordered data sequence, and extracting the unique identifier, data access address, data update period and data format specification of each road network data node in the optimized ordered data sequence to form a data element information set; based on the data element information set, adding business conduction path identification, node position identification in the path and data association dependence identification to each road network data node in the ordered data sequence, the business conduction path identification, node position identification in the path and data association dependence identification being consistent with the characteristics of the business conduction path. Integrating ordered data sequences, data element information sets, and service transmission path identifiers, node position identifiers in the path, and data correlation dependency identifiers to form path-specific data combinations; Encapsulating the path-specific data combinations according to a unified directory unit structure, supplementing service transmission adaptation instructions and associated data call rules of the path-specific data combinations, and forming dynamic directory units, which are used to adaptively adjust data combinations as the service transmission path changes.

4. The method for generating a city road network data resource directory combined with a business map according to claim 1, characterized in that, The service transmission attributes based on the dynamic directory units generate associated transmission links between the directory units, including: Extracting the service transmission path identifiers, core service appeal characteristics, and road network data node identifiers in the data combinations of each dynamic directory unit to form a directory unit transmission feature set; Based on the directory unit transmission feature set, analyzing the core service appeal characteristic overlap areas of different dynamic directory units, identifying directory unit groups with business collaboration needs, and determining the business collaboration needs based on the connection relationship of the business process or data sharing needs; Extracting the road network data node identifiers in the data combinations of all dynamic directory units in each directory unit group, and finding the road network data node identifiers common to different directory units; Based on the common road network data node identifiers, extracting the associated transmission intensity descriptions and transmission direction identifiers of the corresponding road network data entities, and determining the data transmission direction and associated closeness descriptions between different directory units; Analyzing the service transmission path identifiers of the dynamic directory units in each directory unit group, extracting the sequential connection order or parallel collaboration relationship between the service transmission paths, and forming service transmission collaboration logic; Taking the common road network data node identifiers as the connection hub, combining the data transmission direction, associated closeness description, and service transmission collaboration logic, and building initial associated links between the directory units, the initial associated links containing link start point identifiers, link end point identifiers, and connection basis; Adding collaboration type identifiers and transmission priority information to the initial associated links, the collaboration type identifiers distinguishing between data sharing type collaboration, business connection type collaboration, and scene complementary type collaboration, and the transmission priority information being generated based on business attributes; Extracting the associated data call rules of each dynamic directory unit, integrating the associated data call rules into the corresponding initial associated links, and determining the permission range, transmission mode, and format requirements of data call in the initial associated links; Based on all initial associated links, collaboration type identifiers, transmission priority information, and associated data call rules, building the basic structure of the associated transmission link network, which contains link nodes, link connection relationships, and link attributes, and the link nodes being dynamic directory units; Integrating the link nodes, link connection relationships, and all link attributes to form associated transmission links between the directory units, which are used to realize business collaboration and data associated transmission between different dynamic directory units.

5. The method for generating a city road network data resource directory combined with a business map according to claim 1, characterized in that, The integration of the dynamic directory units and the associated transmission links forms a closed-loop urban road network data resource directory, including: Collect all the built dynamic directory units, extract the complete data combination, service transmission adaptation instructions, associated data call rules and directory unit unique identifier of each dynamic directory unit, and form a directory unit core information library; Call the associated transmission link between the directory units, extract the link node identifier, connection relationship, collaboration type identifier, transmission priority information and associated data call rules in the associated transmission link, and form a link core information library; Based on the directory unit unique identifier, establish the association mapping of the directory unit core information library and the link core information library, so as to associate each associated transmission link with the dynamic directory unit core information participating in collaboration; Based on the transmission priority information of the associated transmission link, the dynamic directory units in the directory unit core information library are hierarchically divided to form a directory main level and a directory collaboration level, and the directory main level corresponds to the directory units of the core business transmission path; Within the directory main level and the directory collaboration level, the horizontal association structure of the directory units is built according to the connection relationship of the associated transmission link, and the horizontal association structure reflects the collaboration logic between the directory units in the same level; Based on the business connection relationship of the associated transmission link, the vertical association structure of the directory units is built across the directory main level and the directory collaboration level, and the vertical association structure reflects the business transmission path between the directory units in different levels; Integrate the horizontal association structure and the vertical association structure to build the overall association framework of the city road network data resource directory, and the overall association framework includes three core elements of hierarchical division, associated path and collaboration rule; Fill all the dynamic directory unit information in the directory unit core information library to the corresponding position of the overall association framework, supplement the associated transmission instructions and data interaction processes between the directory units; Build a directory dynamic update trigger mechanism, which takes the change of the business associated transmission source as the trigger condition, and automatically triggers the update of the dynamic directory unit and the associated transmission link when the business process transmission node or transmission rule changes; Integrate the overall association framework, directory unit information, associated transmission instructions, data interaction processes and directory dynamic update trigger mechanism to form a closed-loop city road network data resource directory, which can be dynamically updated with the change of business associated transmission.

6. The method for generating a city road network data resource directory combined with a business map according to claim 2, characterized in that, The data association derivation algorithm is used to derive adjacent road network data entities that have application scenario connection or attribute complementarity with the current road network data entity along the business transmission direction, expand the data association range, 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 to generate a recognizable feature vector, which is then input into the association rule mining module of the data association derivation algorithm. Based on the preset attribute association rules and scenario connection rules, the potential associated attributes and potential application scenarios of the current road network data entity are mined. retrieve other road network data entities with the same or complementary attributes in the road network basic data based on the potential association attribute, form a potential association data candidate set, and the potential association data candidate set contains data entity identification and attribute matching points; calculate the similarity or correlation degree of the application scenarios of other road network data entities in the road network basic data based on the potential application scenario, and filter out data entities with a similarity or correlation degree exceeding a preset threshold to supplement to the potential association data candidate set; generate an association closeness description of each data entity in the potential association data candidate set and the current road network data entity based on the number of attribute matching points and the scenario overlap range, sort the data entities in the potential association data candidate set according to the association closeness description, and select a data entity with a more comprehensive association dimension corresponding to the association closeness description as a priority association object; extract complete attribute information and application scenario description of the priority association object, and perform association verification with corresponding information of the current road network data entity, wherein the association verification process is performed based on matching rules of a business association conduction logic model; record the association basis, association attribute, and scenario connection point of the priority association object and the current road network data entity, form a new association derivative record, and the new association derivative record has the same format as the original data association derivative record; take the priority association object as a new starting point, repeat the processes of attribute mining, scenario screening, association calculation, and verification record, continuously expand the data association range, and form a chain-like association derivative path; integrate all chain-like association derivative paths and corresponding association derivative records, and complete the expansion of the data association range.

7. The method for generating a city road network data resource directory combined with a business map according to claim 3, characterized in that, arrange the road network data nodes in the initial data combination candidate set in sequence based on the data use sequence requirement in the core business demand characteristics and in combination with the conduction direction identifier of the data association derivative network, generate an ordered data sequence, including: extract the data use sequence requirement in the core business demand characteristics, split the data use sequence requirement into multiple data use stages, each data use stage corresponds to a key business link in the business conduction path, and determine the core data demand of each data use stage; analyze the conduction direction identifier of the road network data nodes corresponding to the initial data combination candidate set in the data association derivative network, and determine the conduction sequence of each road network data node in the business conduction path; establish a correspondence between the data use stage and the conduction sequence, so that each data use stage can be matched to the road network data node corresponding to the conduction direction identifier; based on the correspondence, preliminarily sort the road network data nodes in the initial data combination candidate set according to the sequence of the data use stages, form an initial ordered sequence, extract the association conduction intensity description of each road network data node in the initial ordered sequence, analyze the association closeness description between adjacent road network data nodes, and adjust the arrangement sequence of the nodes in the initial ordered sequence, so that the nodes with a more comprehensive association dimension corresponding to the association closeness description are arranged adjacently. Analyzing the data application scenario starting condition of each road network data node, so that the application scenario starting condition of the sorted road network data node is consistent with the process promotion logic of the business transmission path; Extracting the data access dependency relationship of the road network data node, and some road network data node access needs to be based on the output of other road network data nodes as a prerequisite, further adjusting the sequence order based on the data access dependency relationship; Comparing and verifying the adjusted sequence with the data usage sequence requirements in the core business demand characteristics, if there is inconsistency, then adjusting the sequence again according to the data usage sequence requirements, until the sequence order is consistent with the data usage sequence requirements; Recording all adjustment basis in the sequence arrangement process, including the initial sorting, adjustment based on the correlation tight description, adjustment based on the application scenario starting condition, adjustment based on the data access dependency relationship, and readjustment based on the comparison and verification basis, forming the sequence arrangement explanation; Integrating the adjusted road network data node sequence and the sequence arrangement explanation to generate the ordered data sequence, which is used to meet the sequence requirements and correlation requirements of data usage in the business transmission path.

8. The method for generating a city road network data resource directory combined with a business map according to claim 4, characterized in that, The common road network data node identifier is used as the connection hub to build the initial correlation link between the directory units, including: Extracting the complete attribute information of the road network data entity corresponding to the common road network data node identifier, the correlation transmission intensity description, and the transmission direction identifier to form a hub data feature set; Based on the hub data feature set, determine the correlation dynamic directory unit corresponding to each common road network data node identifier, and clarify the role of each correlation dynamic directory unit in the link, which is divided into data provider or data receiver; According to the data transmission direction identifier, determine the data transmission direction between the correlation dynamic directory units to form the transmission direction framework of the initial correlation link, which includes the starting directory unit, the ending directory unit, and the transmission path direction; Based on the correlation tight description, add the connection strength attribute to the transmission direction framework of the initial correlation link, which directly corresponds to the correlation tight description; Analyzing the business transmission coordination logic, extracting the key business nodes and data interaction requirements in the coordination process, and converting the key business nodes and data interaction requirements into the connection rules of the initial correlation link, which includes the timing, content, and format of data interaction; Based on the transmission direction framework, connection strength attribute, and connection rules of the initial correlation link, build the basic structure of the initial correlation link, which includes the link identifier, participating directory unit identifier, transmission direction, connection strength, and connection rules; Extracting the correlation data calling rules of the participating directory unit, and integrating the correlation data calling rules of the participating directory unit into the basic structure of the initial correlation link to clarify the permissions, methods, and restriction conditions of data calling in the initial correlation link; analyzing overlapping areas of the initial association link and other potential association links, if a connection conflict is found, adjusting connection rules of the conflict link according to the conduction priority information or the business conduction coordination logic to eliminate the conflict; recording the building basis of the initial association link, the building basis including a hub data feature set, a conduction direction, an association tight description, and a business conduction coordination logic, to form a link building description; integrating the basic structure of the initial association link, the association data calling rule of the participating directory unit, and the link building description to form the initial association link, the initial association link being used to clearly define the association manner and coordination logic between the directory units based on the common road network data node identifier.

9. The method for generating a city road network data resource directory combined with a business map according to claim 5, characterized in that, The directory dynamic update trigger mechanism takes the change of the business association conduction source as a trigger condition, and automatically triggers the update of the dynamic directory unit and the associated conduction link when the business process conduction node or the conduction rule changes, including: accessing a real-time monitoring interface of the business association conduction source to obtain real-time state information of the business process conduction node and the conduction rule, the real-time state information including change types such as node addition, node deletion, rule modification, and rule addition; based on the real-time state information, accessing a change recognition module, the change recognition module being used to automatically recognize the change content, change range, and change impact dimension of the business process conduction node and the conduction rule; accessing a change impact evaluation model, inputting the change content and the change range into the change impact evaluation model, and the change impact evaluation model outputting the impact dimension and impact description of the change on the existing dynamic directory unit and the associated conduction link; based on the impact dimension and the impact description, determining the range of the dynamic directory unit and the range of the associated conduction link that need to be updated to form an update object list, the update object list including object identifiers and update priorities; configuring an update process for each dynamic directory unit in the update object list, the update process including operation steps such as data combination adjustment, business conduction adaptation description modification, and association data calling rule update; configuring an update process for each associated conduction link in the update object list, the update process including operation steps such as link connection relationship adjustment, coordination type identifier modification, and conduction priority information update; accessing an update execution module, the update execution module being configured to automatically perform the update operation of the dynamic directory unit and the associated conduction link according to the update process and the update priority; accessing an update verification module, the update verification module being able to verify the fit of the updated dynamic directory unit and the associated conduction link with the new state of the business association conduction source after the update operation is performed, the verification process being performed based on a business association conduction logic model; recording all operation logs in the update process, the operation logs including update objects, update times, update contents, update bases, and verification results to form a complete update archive; integrating the change recognition module, the change impact evaluation model, the update process, the update execution module, the update verification module, and the update archive to form the directory dynamic update trigger mechanism.

10. A system for generating a city road network data resource directory combined with a service map, characterized by, including: a processor; A machine readable storage medium for storing machine executable instructions of the processor; The processor is configured to execute the method for generating a city road network data resource directory combined with a business graph by executing the machine executable instructions according to any one of claims 1 to 9.

Images