Method and system for updating catenary arrangement data based on object semantics

Abstract

The application discloses a catenary arrangement data updating method and system based on object semantics, carries out semantic modeling on a catenary engineering design entity object, and generates an entity semantic object; an association mapping relationship is established between the entity semantic object and a preset data table in a service end arrangement database; in response to a target entity object modification operation of a front end user based on a catenary design result map, the target entity object modification operation is encapsulated as an object operation intention in a preset format and is submitted to the service end; after the service end obtains the object operation intention, the object operation intention is parsed, and based on the association mapping relationship between the entity semantic object and the preset data table in the database, data table information corresponding to the target entity object is updated. The application effectively reduces front and rear end coupling, improves semantic clarity and traceability of engineering data modeling, is particularly suitable for batch editing and complex object management in a catenary arrangement scene, and provides a key basic technology in catenary engineering design.

Description

Technical Field

[0001] This invention relates to the field of overhead contact line design technology, and specifically to an overhead contact line layout data update method and system based on object semantics. Background Technology

[0002] The overhead contact system is a special type of power supply line used in electrified railways to supply power to electric locomotives. With the development of information technology, the design of overhead contact systems has been initially automated. This means that the design process is driven by conditions such as lines, bridges, tunnels, and climate parameters, automatically generating data on the overhead contact system layout and storing it on a server. This data is then parsed into two-dimensional DWG drawings or three-dimensional models as design deliverables.

[0003] However, due to the complexity of engineering design environments, automatically generated design deliverables often require secondary modifications to meet specific construction needs. Currently, a common practice is to import the generated drawings or models into CAD or other editing software for modification before using them as the final deliverable. While this method meets construction requirements, the modification process becomes disconnected from the initially generated layout data, resulting in server-side layout data that fails to accurately reflect the final state of the overhead contact line engineering design deliverables. This not only affects the usability and accuracy of the deliverable data in subsequent stages but also fails to meet the requirements of the overhead contact line profession for digital deliverables and cannot support further exploration and utilization of the data's value.

[0004] Therefore, it is necessary to develop a new method that can directly edit the catenary layout design results while ensuring accuracy and efficiency, and reflect the editing results in the layout data in a timely and rapid manner, thereby meeting the actual needs of the catenary profession in digital design, digital deliverables, and construction management throughout the entire project lifecycle. Summary of the Invention

[0005] This invention provides a method and system for updating catenary layout data based on object semantics, in order to solve the problems of existing technologies such as the disconnect between layout data and modification results, poor data consistency, and difficulty in supporting digital delivery and lifecycle management.

[0006] According to a first aspect, one embodiment provides a method for updating catenary layout data based on object semantics, the method comprising:

[0007] Semantic modeling is performed on the physical objects of the overhead contact line engineering design to generate entity semantic objects;

[0008] Establish an association mapping relationship between the entity semantic object and the preset data table in the database deployed on the server;

[0009] In response to a front-end user's modification operation of the target entity object based on the catenary design result drawing, the modification operation of the target entity object is encapsulated into an object operation intent in a preset format and submitted to the server.

[0010] After obtaining the operation intent of the object, the server parses it and updates the data table information corresponding to the target entity object based on the association mapping relationship between the entity semantic object and the preset data table in the database.

[0011] Furthermore, semantic modeling is performed on the contact network engineering design entity objects to generate entity semantic objects, specifically including:

[0012] The entity object is described using multiple attribute information of the contact network engineering design entity object, and the multiple attribute information of the entity object is used to generate corresponding semantic fields.

[0013] Furthermore, an association mapping relationship is established between the entity semantic objects and the preset data tables in the server-side database, specifically including:

[0014] Use a server to set up a pre-defined data table in the database to store the attribute information of entity objects.

[0015] Furthermore, in response to a front-end user's modification operation on the target entity object based on the catenary design result drawing, the modification operation is encapsulated into an object operation intent in a preset format and submitted to the server, specifically including:

[0016] The modification operation of the target entity object is encapsulated as an object operation intent in JSON format.

[0017] Furthermore, in response to a front-end user's modification operation on the target entity object based on the catenary design result drawing, the modification operation is encapsulated into an object operation intent in a preset format and submitted to the server, specifically including:

[0018] The object operation intent includes the operation object, operation type, and operation parameters.

[0019] Furthermore, the operation object is the name of the entity semantic object to which the modification operation is performed; the operation type includes add, delete, modify, and move; and the operation parameter is the attribute parameter of the specific entity semantic object to be modified.

[0020] Furthermore, the method also includes:

[0021] The server sends the updated data table results back to the front end. When the front end receives the feedback from the server that the data table has been updated successfully, it confirms the current graph modification status and completes the modification operation; otherwise, it reverts to the state before the modification operation.

[0022] According to a second aspect, one embodiment provides a contact wire layout data update system based on object semantics, the system comprising:

[0023] The semantic modeling module is used to perform semantic modeling on the entity objects of the overhead contact line engineering design, and generate entity semantic objects.

[0024] The data table association module is used to establish an association mapping relationship between entity semantic objects and preset data tables in the server-side database;

[0025] The intent encapsulation module is used to respond to the front-end user's modification operation of the target entity object based on the catenary design result diagram, encapsulate the target entity object modification operation into an object operation intent of a preset format and submit it to the server.

[0026] The data table update module is used by the server to parse the operation intent of the object after obtaining it, and update the data table information corresponding to the target entity object based on the association mapping relationship between the entity semantic object and the preset data table in the database.

[0027] According to a third aspect, one embodiment provides an electronic device, the device comprising: a processor and a memory;

[0028] The memory is used to store one or more program instructions;

[0029] The processor is configured to run one or more program instructions to perform the steps of an object semantics-based contact wire layout data update method as described in any of the preceding claims.

[0030] According to a fourth aspect, one embodiment provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of an object semantics-based contact wire arrangement data update method as described in any of the preceding claims.

[0031] This invention provides a method and system for updating overhead contact line layout data based on object semantics. It involves semantically modeling the entity objects of the overhead contact line engineering design to generate entity semantic objects; establishing an association mapping relationship between the entity semantic objects and preset data tables in the server-side layout database; responding to a front-end user's modification operation on a target entity object based on the overhead contact line design result drawing, encapsulating the modification operation into a preset format object operation intent and submitting it to the server; the server, upon receiving the object operation intent, parses it and updates the data table information corresponding to the target entity object based on the association mapping relationship between the entity semantic objects and the preset data tables in the database. This invention uses an object semantics-driven approach to aggregate and edit engineering design entity objects such as supports, suspension columns, anchors, and guy wires in railway overhead contact line engineering. The front-end only needs to submit object operation intents (such as adding, modifying, deleting, and moving), without needing to concern itself with the database structure; the server, according to the mapping rules between entity semantic objects and data tables, parses and executes the corresponding multi-table modifications in a unified transaction, thereby achieving consistent maintenance of object aggregation operations. This method effectively reduces the coupling between the front-end and back-end, improves the semantic clarity and traceability of engineering data modeling, and is particularly suitable for batch editing and complex object management in catenary layout scenarios. It is a key foundational technology for the digital design of catenary engineering and similar projects. Attached Figure Description

[0032] Figure 1 A flowchart illustrating a contact wire layout data update method based on object semantics, as provided in one embodiment of the present invention;

[0033] Figure 2 This is an overall architecture diagram of a catenary layout data update system based on object semantics, provided as an embodiment of the present invention. Detailed Implementation

[0034] The present invention will now be described in further detail with reference to specific embodiments and accompanying drawings. Similar elements in different embodiments are referred to by associated similar element reference numerals. In the following embodiments, many details are described to facilitate a better understanding of the invention. However, those skilled in the art will readily recognize that some features may be omitted in different situations, or may be replaced by other elements, materials, or methods. In some cases, certain operations related to the present invention are not shown or described in the specification. This is to avoid obscuring the core parts of the invention with excessive description. For those skilled in the art, detailed description of these related operations is not necessary; they can fully understand the related operations based on the description in the specification and general technical knowledge in the art.

[0035] Furthermore, the features, operations, or characteristics described in the specification can be combined in any suitable manner to form various embodiments. At the same time, the steps or actions in the method description can be rearranged or adjusted in a manner obvious to those skilled in the art. Therefore, the various orders in the specification and drawings are only for the clear description of a particular embodiment and do not imply a necessary order, unless otherwise stated that a particular order must be followed.

[0036] This invention provides a method for updating catenary layout data based on object semantics. The following is a detailed explanation. Figure 1 Please provide a detailed explanation.

[0037] like Figure 1 As shown, in step S100, semantic modeling is performed on the contact network engineering design entity object to generate entity semantic objects.

[0038] The above steps specifically include: using multiple attribute information of the contact network engineering design entity object to describe the entity object, and generating corresponding semantic fields for each of the multiple attribute information of the entity object.

[0039] Specifically, in this embodiment, the contact network engineering design entity objects can be divided into:

[0040] Simple objects: supports, foundations, cantilever installations, additional conductor installations, contact wire anchor sections, additional conductor anchor sections, etc.

[0041] Composite objects: Anchor joints (composed of objects such as carpal arms, lower anchors, and supports), etc.

[0042] Taking "pillar" as an example, the pillar semantic object contains semantic fields corresponding to the following attributes:

[0043] • Mileage

[0044] • Number

[0045] • Drawing number (drawing_no)

[0046] • Material type (e.g., steel column, concrete column, etc.).

[0047] like Figure 1 As shown, in step S200, an association mapping relationship is established between the entity semantic object and the preset data table in the server-side deployment database.

[0048] The above steps specifically include: using a pre-defined data table in the server-side database to store the attribute information of entity objects. For example, there is a mapping relationship between the pillar semantic object and the data table mast_table (pillar basic information table) in the database.

[0049] like Figure 1 As shown, in step S300, in response to the front-end user's modification operation of the target entity object based on the catenary design result drawing, the modification operation of the target entity object is encapsulated into an object operation intent in a preset format and submitted to the server.

[0050] The above steps specifically include: encapsulating the target entity object modification operation into a JSON-formatted object operation intent. The object operation intent contains the operation object, operation type, and operation parameters. The operation object is the name of the entity semantic object to which the modification operation will be performed; the operation type includes add, delete, modify, and move; and the operation parameters are the specific entity semantic object attribute parameters to be modified.

[0051] The following is an example of the intent to manipulate a JSON object:

[0052] {

[0053] "action":XXX,#action type

[0054] "object":"mast", # The object being operated on

[0055] "params":{# Operation parameters

[0056] "mileage":"K12+300",

[0057] "number":"123",

[0058] "drawing_no":"T-001",

[0059] "type":"steel",

[0060] }

[0061] }

[0062] like Figure 1 As shown, in step S400, after the server obtains the object operation intent, it parses it and updates the data table information corresponding to the target entity object based on the association mapping relationship between the entity semantic object and the preset data table in the database.

[0063] In this embodiment, the method further includes: the server feeding back the data table update result to the front end; when the front end receives feedback from the server that the data table has been successfully updated, it confirms the current graphic modification status (such as adding a new pillar) and completes the modification operation; otherwise, it reverts to the state before the modification operation.

[0064] Operation Example 1: Adding and Modifying Pillar Objects (Simple Objects)

[0065] Taking a support pillar as an example, when a user needs to add a support pillar to the overhead contact line design drawing, the front end does not directly manipulate the database. Instead, it encapsulates the operation as an "object operation intent" and submits it to the server in JSON format, as follows:

[0066] {

[0067] "action":"add",

[0068] "object":"mast",

[0069] "params":{

[0070] "mileage":"K12+300",

[0071] "number":"123",

[0072] "drawing_no":"T-001",

[0073] "type":"steel",

[0074] }

[0075] }

[0076] The operation type is "add", which means adding data; the operation object is "mast", which means catenary support; and the operation parameters include the mileage (K12+300), the support number (123), the support drawing number (T-001), and the support material type (steel).

[0077] Similarly, when a user needs to modify a support (such as changing its material type to concrete), the operation is encapsulated as an "object operation intent" and submitted to the server in JSON format, as follows:

[0078] {

[0079] "action":"update",

[0080] "object":"mast",

[0081] "number":"143",

[0082] "params":{

[0083] "type":"concrete"

[0084] }

[0085] }

[0086] The operation type is "update" (update data), the operation object is "mast" (contact wire support), the support number is 143, and the operation parameter "params" is the support material type, which is adjusted to "concrete".

[0087] After receiving the object operation intent, the server parses it according to the mapping relationship between the pillar semantic object and the database table and performs the following operations:

[0088] • Add a pillar: Insert a record into the mast_table and update the pillar number after the new pillar position;

[0089] • Modify the pillar: Update the type field in mast_table.

[0090] All operations are performed within the same database transaction to ensure data consistency.

[0091] Data synchronization setup: After the operation is completed, the server returns the data table update status to the front end. Once the front end receives the successful save status, it confirms the current graphic modification status and adds the new pillar; otherwise, it reverts to the state before the pillar was added.

[0092] Operation Example 2: Modification of Anchor Joint (Composite Object)

[0093] The anchor joint is the overlapping part of two sets of catenary anchor sections. It is a key entity object in catenary engineering, composed of catenary entity objects such as the cantilever conversion post installation and the lower anchor installation. The anchor joint semantic object contains semantic fields corresponding to the following attribute information:

[0094] • Joint starting anchor segment number (start_tension_id)

[0095] • Joint termination anchor segment number (end_tension_id)

[0096] Anchor joint semantic objects have mapping relationships with multiple tables in the database, and associated sub-objects correspond to several tables in the database, for example:

[0097] tension_table (anchor segment information table) records information such as the anchor installation ID "start_install_id" at the starting point of the anchor segment, the anchor installation ID "end_install_id" at the ending point of the anchor segment, and the anchor segment length (tension_length);

[0098] The ocs_assemblies_table (overhead contact line installation information table) records the starting anchor installation ID "start_install_id", the cantilever arm (intermediate post, transition post), the installation purpose of the anchor "install_usage", and the number of the attached support "install_pole_id".

[0099] When a user needs to move an anchor segment joint, the frontend does not directly modify multiple tables, but encapsulates it as an object operation intent and submits it to the server in JSON format, as follows:

[0100] {

[0101] "action":"move",

[0102] "object":"overlap",

[0103] "id":"",

[0104] "params":{

[0105] "start_tension_id":5,

[0106] "end_tension_id":4,

[0107] "dest_start_pole_id":140}

[0108] }

[0109] The operation type is "move", the operation object is "overlap", which is the catenary anchor joint, and the operation parameters include the joint start anchor number "start_tension_id", the joint end anchor number "end_tension_id", and the target support "dest_start_pole_id".

[0110] After receiving the operation intent, the backend performs the following processing based on the semantic mapping rules:

[0111] Read the starting anchor installation ID of the starting anchor segment 5: start_install_id and the ending anchor installation ID of the ending anchor segment 4: end_install_id from the tension_table. Use these two ID values ​​to query the corresponding anchor installation record in the ocs_assemblies_table to obtain its installation paddle number install_pole_id (134 and 138 respectively) and the number of joint spans (the number of paddles between the two paddle IDs is 3+1=4). Then modify the installation paddle number to the target paddle number "dest_start_pole_id" (140).

[0112] Modify the corresponding support number install_pole_id of the starting anchor segment 5 in ocs_assemblies_table to 140, and modify the termination anchor installation ID of the terminating anchor segment 4: install_pole_id to "dest_start_pole_id" + number of joint spans = 144;

[0113] Modify the purpose of the original anchor posts (numbered 134, 138) recorded in the mast_table to intermediate post type, and delete the associated anchor lines. Change the purpose of the new anchor posts (numbered 140, 144) to anchor post, and add associated anchor lines.

[0114] Data synchronization: Upon receiving a successful save notification, the front-end confirms the current graphic modification status and modifies the anchor segment identifiers and guy wire graphic elements. For example, after modifying the start and end mileage of an anchor segment, the anchor segment location identifiers in the DWG drawing and 3D model are automatically updated; after modifying the anchor segment type, the corresponding joint symbols and guy wire graphic elements are added or deleted in the layout data.

[0115] Corresponding to the above-disclosed method for updating catenary layout data based on object semantics, this invention also discloses a system for updating catenary layout data based on object semantics, such as... Figure 2 As shown, it specifically includes:

[0116] The semantic modeling module is used to perform semantic modeling on the entity objects of the overhead contact line engineering design, and generate entity semantic objects.

[0117] The data table association module is used to establish an association mapping relationship between entity semantic objects and preset data tables in the server-side database;

[0118] The intent encapsulation module is used to respond to the front-end user's modification operation of the target entity object based on the catenary design result diagram, encapsulate the target entity object modification operation into an object operation intent of a preset format and submit it to the server.

[0119] The data table update module is used by the server to parse the operation intent of the object after obtaining it, and update the data table information corresponding to the target entity object based on the association mapping relationship between the entity semantic object and the preset data table in the database.

[0120] It should be noted that for a detailed description of the contact wire arrangement data update system based on object semantics provided in the embodiments of the present invention, please refer to the relevant description of the contact wire arrangement data update method based on object semantics provided in the embodiments of the present invention, which will not be repeated here.

[0121] In addition, embodiments of the present invention also provide an electronic device, the device comprising: a processor and a memory; the memory being used to store one or more program instructions; the processor being used to execute one or more program instructions to perform the steps of an object semantics-based contact network layout data update method as described in any of the preceding embodiments.

[0122] It should be noted that for a detailed description of an electronic device provided in the embodiments of the present invention, please refer to the relevant description of a contact network layout data update method based on object semantics provided in the embodiments of the present invention, which will not be repeated here.

[0123] In addition, embodiments of the present invention also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the contact wire layout data update method based on object semantics as described in any of the preceding claims.

[0124] It should be noted that for a detailed description of the computer-readable storage medium provided in the embodiments of the present invention, please refer to the relevant description of the contact wire layout data update method based on object semantics provided in the embodiments of the present invention, which will not be repeated here.

[0125] Those skilled in the art will understand that all or part of the functions of the various methods in the above embodiments can be implemented by hardware or by computer programs. When all or part of the functions in the above embodiments are implemented by computer programs, the program can be stored in a computer-readable storage medium, which may include: read-only memory, random access memory, disk, optical disk, hard disk, etc., and the program is executed by a computer to achieve the above functions. For example, the program can be stored in the memory of a device, and when the program in the memory is executed by the processor, all or part of the above functions can be achieved. In addition, when all or part of the functions in the above embodiments are implemented by computer programs, the program can also be stored in a server, another computer, disk, optical disk, flash drive, or external hard drive, etc., and can be downloaded or copied to the memory of a local device, or the system of the local device can be updated. When the program in the memory is executed by the processor, all or part of the functions in the above embodiments can be achieved.

[0126] The above examples illustrate the present invention only to aid in understanding it and are not intended to limit the scope of the invention. Those skilled in the art can make various simple deductions, modifications, or substitutions based on the principles of this invention.

Claims

1. A method for updating catenary layout data based on object semantics, characterized in that, The method includes: Semantic modeling is performed on the entity objects of the overhead contact line engineering design to generate entity semantic objects. Specifically, this includes: describing the entity objects using multiple attribute information of the entity objects, and generating corresponding semantic fields for each of the multiple attribute information of the entity objects; the entity objects of the overhead contact line engineering design are divided into simple objects and composite objects, where simple objects include supports, foundations, cantilever arm installations, additional conductor installations, overhead contact line anchor sections, and additional conductor anchor sections; composite objects include anchor section joints; Establish an association mapping relationship between entity semantic objects and preset data tables in the server-side database, specifically including: using preset data tables in the server-side database to store the attribute information of entity objects; In response to a front-end user's modification operation on a target entity object based on the overhead contact line design result drawing, the modification operation is encapsulated into a preset format object operation intent and submitted to the server. The object operation intent includes the operation object, operation type, and operation parameters. The operation object is the name of the entity semantic object to which the modification operation is performed. The operation type includes add, delete, modify, and move. The operation parameters are the specific entity semantic object attribute parameters to be modified. After obtaining the operation intent of the object, the server parses it and updates the data table information corresponding to the target entity object based on the association mapping relationship between the entity semantic object and the preset data table in the database. If the entity semantic object has a mapping relationship with multiple data tables in the database, the server parses and executes the corresponding multi-table modification in a unified transaction according to the mapping rules between the entity semantic object and the data table, thereby realizing the consistency maintenance of object aggregation operation.

2. The contact wire layout data update method based on object semantics as described in claim 1, characterized in that, In response to a front-end user's modification operation on the target entity object based on the catenary design result drawing, the modification operation is encapsulated into a preset format object operation intent and submitted to the server, specifically including: The modification operation of the target entity object is encapsulated as an object operation intent in JSON format.

3. The contact wire layout data update method based on object semantics as described in claim 1, characterized in that, The method further includes: The server sends the updated data table results back to the front end. When the front end receives the feedback from the server that the data table has been updated successfully, it confirms the current graph modification status and completes the modification operation; otherwise, it reverts to the state before the modification operation.

4. A contact network layout data update system based on object semantics, characterized in that, The system includes: The semantic modeling module is used to semantically model the entity objects of the overhead contact line engineering design, generating entity semantic objects. Specifically, it includes: describing the entity objects using multiple attribute information of the entity objects, and generating corresponding semantic fields for each of the multiple attribute information of the entity objects; the entity objects of the overhead contact line engineering design are divided into simple objects and composite objects, where simple objects include supports, foundations, cantilever arm installations, additional conductor installations, overhead contact line anchor sections, and additional conductor anchor sections; composite objects include anchor section joints; The data table association module is used to establish an association mapping relationship between entity semantic objects and preset data tables in the server-side database. Specifically, it includes: using preset data tables in the server-side database to store the attribute information of entity objects. The intent encapsulation module is used to respond to the front-end user's modification operation on the target entity object based on the catenary design result diagram, encapsulate the target entity object modification operation into an object operation intent in a preset format and submit it to the server. The object operation intent includes the operation object, operation type and operation parameters; the operation object is the name of the entity semantic object to which the modification operation is performed; the operation type includes add, delete, modify and move; the operation parameters are the specific entity semantic object attribute parameters to be modified. The data table update module is used by the server to parse the operation intent of the object after obtaining it, and update the data table information corresponding to the target entity object based on the association mapping relationship between the entity semantic object and the preset data table in the database. The server parses and executes the corresponding multi-table modification in a unified transaction according to the mapping rules between the entity semantic object and the data table, thereby realizing the consistency maintenance of object aggregation operation.

5. An electronic device, characterized in that, The device includes: a processor and a memory; The memory is used to store one or more program instructions; The processor is configured to run one or more program instructions to perform the steps of the contact wire layout data update method according to any one of claims 1 to 3.

6. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the contact wire layout data update method based on object semantics as described in any one of claims 1 to 3.

Images