Type associated data synchronization method and device, computer equipment, readable storage medium and program product
By detecting and synchronizing the differences in service data types between AP and CP platforms, determining the standards and platforms to be updated, modifying the associated data, the problem of inconsistent data types is solved, and normal interaction between platforms and service operation is achieved.
Patent Information
- Application Number
- CN202411215464.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-30
- Publication Date
- 2024-12-06
AI Technical Summary
Under the automotive open system architecture, there are differences in data type consistency between adaptive platforms and classic platforms, resulting in inconsistent data types and affecting interaction and service operation.
By detecting the differences in service data types of the two software platforms, determine the standard platform and the platform to be updated, obtain the service data of the standard platform, and determine the first type of association data from the target service data, based on the second type of association in the data to be synchronized The data modify the first type of associated data to ensure that the data types of the two platforms are consistent.
It realizes data type consistency between AP and CP platforms, ensures normal interaction and operation of services, and ensures data synchronization and interoperability.
Smart Images

Figure CN119088597A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of vehicle technology, and in particular to a type-associated data synchronization method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art
[0002] Within the AUTOSAR (Automotive Open System Architecture) framework, the Adaptive Platform (AP) and the Classic Platform (CP) are two core platforms designed for different application scenarios. While they differ significantly in design philosophy, operating environment, and technical features, they adhere to common fundamental specifications, including data type consistency requirements, to ensure compatibility and interoperability among software components.
[0003] In actual modeling work, although the AP and CP are separated, if running a certain service generates bilateral interaction between the AP and CP, the data type of the service data run by the AP and CP must be consistent. At this time, if the data type of the service data on one side changes, it will cause the data type of the AP and CP to be inconsistent. Therefore, how to ensure the consistency of data types on the AP and CP sides is an urgent problem to be solved. Summary of the Invention
[0004] Based on this, it is necessary to provide a type-associated data synchronization, apparatus, computer device, computer-readable storage medium and computer program product that can keep the data types of AP and CP consistent in order to address the above technical problems.
[0005] In a first aspect, the present application provides a type-related data synchronization method, the method comprising:
[0006] When a difference in service data types between at least two software platforms under the open automotive software architecture is detected, determining a standard platform and a platform to be updated from the at least two software platforms, obtaining service data of the standard platform, and using the service data as data to be synchronized;
[0007] Acquire target service data belonging to the same service as the data to be synchronized from the platform to be updated; the service is implemented through interaction between the standard platform and the platform to be updated;
[0008] determining first type association data from the target service data, where the first type association data is associated with a service data type of the target service data;
[0009] The first type of associated data is modified based on second type associated data in the data to be synchronized, where the second type associated data is associated with the service data type of the service data to be synchronized.
[0010] In one embodiment, determining the first type of associated data from the target service data includes:
[0011] Determining the data type field from the target service data;
[0012] determining other data associated with the data type from the target service data;
[0013] The data type field and the other data are used as the first type associated data.
[0014] In one embodiment, before modifying the first type of associated data based on the second type of associated data in the data to be synchronized, the method further includes:
[0015] Converting the data format of the data to be synchronized into a data format recognizable by the platform to be updated;
[0016] determining, from the format-converted data to be synchronized, data associated with the service data type of the service data to be synchronized;
[0017] The data associated with the service data type of the service data to be synchronized is used as the second-type associated data.
[0018] In one embodiment, the modifying the first type of associated data based on the second type of associated data in the data to be synchronized includes:
[0019] comparing the second-type associated data with the first-type associated data;
[0020] If there is new data in the second type of associated data relative to the first type of associated data, adding the new data to the first type of associated data;
[0021] If there is deletion data in the second type of associated data relative to the first type of associated data, deleting the deletion data from the first type of associated data;
[0022] When the second type of associated data is updated relative to the first type of associated data, the data to be updated in the first type of associated data is deleted, and the data in the second type of associated data corresponding to the data to be updated is used as updated data, and the updated data is added to the first type of associated data.
[0023] In one embodiment, when the standard platform is a classic platform and the platform to be updated is an adaptive platform, the data type field includes: implementation data type, and the other data includes: reference information of the implementation data type, data calculation method, and implementation record elements;
[0024] When the standard platform is an adaptive platform and the platform to be updated is a classic platform, the data type field includes: implementation data type and abstract data type, and the other data includes: reference information of the implementation data type, reference information of the abstract data type, a mapping relationship between data of the abstract data type and data of the implementation data type, a data calculation method, and a data type representation value.
[0025] In one embodiment, the modifying the first type of associated data based on the second type of associated data in the data to be synchronized includes:
[0026] Determining a data member structure and a number of data members under an interface structure from the data to be synchronized; the data member structure and the number of data members are related to a service data type of the data to be synchronized;
[0027] Based on the data member structure, modify the value structure of the data type representation value;
[0028] The number of the data type representation values is set based on the number of the data members.
[0029] In a second aspect, the present application further provides a type-related data synchronization device, the device comprising:
[0030] a first determining module configured to, upon detecting a difference in service data types between at least two software platforms under the open automotive software architecture, determine a standard platform and a platform to be updated from the at least two software platforms, obtain service data of the standard platform, and use the service data as data to be synchronized;
[0031] an acquisition module, configured to acquire target service data belonging to the same service as the data to be synchronized from the platform to be updated; the service is implemented through interaction between the standard platform and the platform to be updated;
[0032] a second determining module, configured to determine first-type associated data from the target service data, where the first-type associated data is associated with a service data type of the target service data;
[0033] The modification module is configured to modify the first type of associated data based on second type associated data in the data to be synchronized, where the second type associated data is associated with a service data type of the service data to be synchronized.
[0034] In a third aspect, the present application further provides a computer device comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the method of each embodiment when executing the computer program.
[0035] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which implements the steps of the method of each embodiment when the computer program is executed by a processor.
[0036] In a fifth aspect, the present application also provides a computer program product, including a computer program, which implements the steps of the method of each embodiment when executed by a processor.
[0037] The above-mentioned type-associated data synchronization method, apparatus, computer device, computer-readable storage medium, and computer program product, when detecting a difference in the service data types of at least two software platforms under an open automotive software architecture, indicating that the service data types of the two software platforms are inconsistent, can then determine a standard platform and a platform to be updated from the at least two software platforms, and obtain service data of the standard platform, using the service data as the data to be synchronized. Then, target service data belonging to the same service as the data to be synchronized is obtained from the platform to be updated. After determining first-type associated data associated with the service data type of the target service data from the target service data, the first-type associated data can be modified based on second-type associated data associated with the service data type in the service data to be synchronized. This can synchronize the first-type associated data with the second-type associated data, thereby making the service data types of the standard platform and the platform to be updated consistent. In this way, when running the service, since the service data types of the two platforms are the same, normal interaction between the standard platform and the platform to be updated can be guaranteed, thereby ensuring the normal operation of the service. BRIEF DESCRIPTION OF THE DRAWINGS
[0038] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the following briefly introduces the drawings required for use in the embodiments of the present application or related technical descriptions. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying any creative work.
[0039] Figure 1 1 is a flow chart of a method for synchronizing type-related data in one embodiment;
[0040] Figure 2 A schematic flow chart of a method for synchronizing type-related data in another embodiment;
[0041] Figure 3 A schematic flow chart of a method for synchronizing type-related data in another embodiment;
[0042] Figure 4 is a structural block diagram of a type-related data synchronization device in another embodiment;
[0043] Figure 5 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION
[0044] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.
[0045] In one embodiment, Figure 1 As shown, a type-related data synchronization method is provided. This embodiment uses the method applied to a vehicle system as an example. In this embodiment, the method includes the following steps:
[0046] Step 102: When a difference in service data types between at least two software platforms under the open automotive software architecture is detected, a standard platform and a platform to be updated are determined from the at least two software platforms, and service data of the standard platform is obtained, and the service data is used as data to be synchronized.
[0047] At least two software platforms under the open automotive software architecture include an AP and a CP. When a service is run under the open automotive software architecture, this service generates communication between the AP and the CP. If differences in the service data types of at least two software platforms are detected, a standard platform and a platform to be updated can be determined from the at least two software platforms.
[0048] The service data type of the software platform (the data type in the following description is the service data type) refers to the data type based on which the software platform configures services;
[0049] The service data of any software platform includes type association data associated with its service data type. When the service data type of the software platform is updated, the type association data will also be updated accordingly.
[0050] In this embodiment, a standard platform and a platform to be updated are determined from at least two software platforms, specifically including: determining the software platform that has most recently updated the service data type in the time dimension among the at least two software platforms, and using the software platform that has most recently updated the service data type as the standard platform, and using the other platforms of the at least two software platforms except the standard platform as the platforms to be updated.
[0051] For example, the AP serves as a standard platform and the CP serves as a platform to be updated, or the CP serves as a standard platform and the AP serves as a platform to be updated.
[0052] Step 104: Acquire target service data belonging to the same service as the data to be synchronized from the platform to be updated; the service is implemented through interaction between the standard platform and the platform to be updated;
[0053] In this embodiment, the service exists on both the AP and CP sides and has the same name. It is necessary to obtain target service data with the same service name as the data to be synchronized from the platform to be updated.
[0054] Step 106: Determine first type associated data from the target service data, where the first type associated data is associated with a service data type of the target service data;
[0055] The target service data includes data associated with the service data type. The data associated with the service data type will change accordingly with changes in the service data type. It is necessary to determine the data associated with the service data type from the target service data as the first type of associated data.
[0056] Step 108: Modify the first type of associated data based on the second type of associated data in the data to be synchronized, where the second type of associated data is associated with the service data type of the service data to be synchronized.
[0057] Determine the second type of associated data associated with the service data type in the data to be synchronized, compare difference information between the second type of associated data and the first type of associated data, and modify the first type of associated data based on the difference information so that the first type of associated data is consistent with the second type of associated data, thereby achieving synchronization of the first type of associated data of the platform to be updated and the second type of associated data of the standard platform, thereby making the data types of the service data of the two platforms consistent.
[0058] In the present application, when it is detected that there is a difference in the service data type of at least two software platforms under the open automotive software architecture, that is, it means that the service data types of the two software platforms are inconsistent, then the standard platform and the platform to be updated can be determined from the at least two software platforms, and the service data of the standard platform can be obtained, and the service data of the standard platform can be used as the data to be synchronized. Then, the target service data belonging to the same service as the data to be synchronized is obtained from the platform to be updated. After determining the first type of associated data associated with the service data type of the target service data from the target service data, the first type of associated data can be modified based on the second type of associated data associated with the service data type in the service data to be synchronized. The first type of associated data can be synchronized with the second type of associated data, so that the service data types of the standard platform and the platform to be updated are consistent. In this way, when running the service, since the service data types of the two platforms are the same, normal interaction between the standard platform and the platform to be updated can be guaranteed, thereby ensuring the normal operation of the service.
[0059] In one embodiment, determining first-type associated data from target service data includes: determining a data type field from the target service data; determining other data associated with the data type from the target service data; and using the data type field and other data as first-type associated data.
[0060] In this embodiment, the data type field includes an implementation data type (IDT) and / or an abstract data type (ADT);
[0061] Other data associated with a data type may be at least one of reference information of a data type field, a mapping relationship between data types, a data calculation method, a data type representation value, and an implementation record element.
[0062] The data type field and other data are collectively regarded as the first type of associated data.
[0063] It can be seen that the first type of associated data not only includes the data type field itself, but also includes other data associated with the data type. These data will change accordingly with the change of the data type. Therefore, this application synchronizes the first type of associated data with the second type of associated data to ensure the consistency of the data types of the standard platform and the platform to be updated.
[0064] In one embodiment, before modifying the first type of associated data based on the second type of associated data in the data to be synchronized, the method further includes:
[0065] For the data to be synchronized, the verification tool will verify the service identifier, service interface elements, and data type of the data to be synchronized, and compare the data to be synchronized with the blueprint in the existing model to ensure that the exported data to be synchronized is consistent with the blueprint in the corresponding model. If there is any inconsistency, the data to be synchronized will be modified based on the model blueprint.
[0066] It can be seen that this application can check and modify the data to be synchronized to ensure consistency with the model blueprint.
[0067] Reference Figure 2 , the specific implementation of this embodiment may also be:
[0068] Step 202: When a difference in service data types between at least two software platforms under the open automotive software architecture is detected, a standard platform and a platform to be updated are determined from the at least two software platforms, and service data of the standard platform is obtained, and the service data is used as data to be synchronized.
[0069] Step 204: Convert the data format of the data to be synchronized into a data format recognizable by the platform to be updated; determine data associated with the service data type of the service data to be synchronized from the format-converted data to be synchronized; and use the data associated with the service data type of the service data to be synchronized as second-type associated data.
[0070] Step 206: Acquire target service data belonging to the same service as the data to be synchronized from the platform to be updated;
[0071] Step 208: Determine first type associated data from the target service data, where the first type associated data is associated with the service data type of the target service data;
[0072] Step 210: Modify the first type of associated data based on the second type of associated data in the data to be synchronized, where the second type of associated data is associated with the service data type of the service data to be synchronized.
[0073] In this embodiment, step 204 may be performed before step 206 , or after step 208 and before step 210 .
[0074] In this embodiment, the verified data to be synchronized can be imported into the project using the import plug-in of the platform to be updated, and the data format of the verified data to be synchronized can be converted into a data format recognizable by the platform to be updated.
[0075] It can be seen that this application ensures the format consistency of the second type of associated data and the first type of associated data by converting the data format of the data to be synchronized into a data format recognizable by the platform to be updated, so that the first type of associated data can be directly modified based on the second type of associated data, thereby ensuring the consistency of data types on the two platforms.
[0076] In one embodiment, when the standard platform is a classic platform and the platform to be updated is an adaptive platform, the data type field includes: implementation data type, and the other data includes: reference information of the implementation data type, data calculation method, and implementation record element; when the standard platform is an adaptive platform and the platform to be updated is a classic platform, the data type field includes: implementation data type and abstract data type, and the other data includes: reference information of the implementation data type, reference information of the abstract data type, a mapping relationship between data of the abstract data type and data of the implementation data type, data calculation method, and data type representation value.
[0077] The reference information of the above data types includes: reference information of implementation data types and / or reference information of abstract data types.
[0078] The computation method defines how the data in the service is computed.
[0079] The mapping relationship between the data of the abstract data type and the data of the implementation data type defines the association relationship between each ADT data and IDT data;
[0080] The data type representation value is associated with the service interface and is used to represent the type of data and is compared with the quantity of data.
[0081] In one embodiment, the modification of the first type of associated data based on the second type of associated data in the data to be synchronized includes: comparing the second type of associated data and the first type of associated data; when there is new data in the second type of associated data relative to the first type of associated data, adding the new data to the first type of associated data; when there is deleted data in the second type of associated data relative to the first type of associated data, deleting the deleted data from the first type of associated data; when there is data update in the second type of associated data relative to the first type of associated data, deleting the data to be updated in the first type of associated data, and using the data in the second type of associated data corresponding to the data to be updated as updated data, and adding the updated data to the first type of associated data.
[0082] When the standard platform is a CP platform and the platform to be updated is an AP platform, this embodiment is specifically implemented as follows:
[0083] Comparing the second type of associated data with the first type of associated data, the content that needs to be changed on the AP side is the IDT, the reference information of the IDT, the data calculation method, and the implementation record element. The implementation record element is an element under the structure (struct) type. If the data type that needs to be modified has a structure type, the implementation record element needs to be modified. If the structure type does not exist, no modification is required. When the second type of associated data on the CP side does not include deletion data, and the first type of associated data on the AP side includes deletion data, the deletion data needs to be deleted from the service data on the AP side. The specific implementation method is: the service data can be a service list, and the deletion data at the corresponding position in the service list is directly deleted;
[0084] When the second-type associated data on the CP side includes newly added data (for example, the newly added data may be reference information of the IDT, data calculation method, or implementation record element), and the first-type associated data on the AP side does not include the newly added data, the newly added data needs to be added to the service data on the AP side. Specifically, the service data may be a service list, and the imported newly added data is directly dragged into the corresponding position of the service list.
[0085] When the second type of association data on the CP side needs to replace the first type of association data on the AP side, the data to be updated in the first type of association data is manually deleted, and data to replace the data to be updated is determined from the second type of association data as updated data. The updated data is then added to the first type of association data. Specifically, the service data can be a service list. The data to be updated at a certain list position in the service list is manually deleted, and the updated data is then added to the same list position.
[0086] When the standard platform is a CP platform and the platform to be updated is an AP platform, this embodiment is specifically implemented as follows:
[0087] The CP side requires more modifications than the AP side. (The data that needs to be modified on the CP side involves the ADT, its reference information, the IDT, its reference information, the mapping relationship between the abstract data type and the implementation data type, data calculation methods, and data type representation values.)
[0088] When the second type of association data on the AP side does not include the deletion data, but the first type of association data on the CP side includes the deletion data, the deletion data needs to be deleted from the service data on the CP side. Specifically, the service data can be a service list, and the deletion data at the corresponding position in the service list is directly deleted.
[0089] When the second type of associated data on the AP side includes newly added data (for example, the newly added data may be reference information of the IDT, data calculation method, or implementation record element), and the first type of associated data on the CP side does not include the newly added data, the newly added data needs to be added to the service data on the CP side. Specifically, the service data may be a service list, and the imported newly added data is directly dragged into the corresponding position of the service list.
[0090] When the second type of association data on the AP side needs to replace the first type of association data on the CP side, the data to be updated in the first type of association data is manually deleted, and data to replace the data to be updated is determined from the second type of association data as updated data. The updated data is then added to the first type of association data. Specifically, the service data can be a service list. The data to be updated at a certain list position in the service list is manually deleted, and the updated data is then added to the same list position.
[0091] The focus is on replacing the data type representation value corresponding to the data type. The initial value can be the initial value. The initial value is related to the service interface. To ensure that the initial value corresponds to the data type referenced by the interface, the specific replacement method of the initial value is:
[0092] In one embodiment, the modification of the first type of associated data based on the second type of associated data in the data to be synchronized includes: determining the data member structure and the number of data members under the interface structure from the data to be synchronized; the data member structure and the number of data members are related to the service data type of the data to be synchronized; based on the data member structure, modifying the value structure of the data type representation value; based on the number of data members, setting the number of the data type representation values.
[0093] Different service data types have different data member structures and numbers under the interface structure. Based on the data member structure, you can modify the value structure of the data type representation value. At the same time, based on the number of data members, you can set the number of data type representation values. In other words, the number of initial values will be the same as the number of data types contained in the structure referenced by the interface. The initial value structure is also a nested structure. If the data type referenced by the interface is a basic data type, the initial value only needs to correspond to the basic data type.
[0094] In the above embodiments, the synchronization method of the service data on the AP side and the service data on the CP side, and the synchronization method of the service data on the CP side and the service data on the AP side are specifically introduced, thereby ensuring the consistency of the data types on the AP side and the CP side.
[0095] In summary, refer to Figure 3 The specific implementation method of the overall solution of this application is:
[0096] Identify the output differences between the AP and CP sides. If the data types on the AP and CP sides are inconsistent, determine whether the platform with the most recent data type update is the CP or the AP. This determines whether the AP data type needs to be unified with the CP data type, or vice versa.
[0097] If you need to unify the AP data type to the CP data type, export the service list from the CP and complete the verification to ensure that it meets the project standards. Then use the AP service import plug-in to import the service list into the project to convert the service list into a data format that the AP can recognize.
[0098] Find the service type (i.e., the first associated type data) that needs to be modified within the corresponding service in the AP, including the IDT, IDT_Ref (IDT reference information), and data calculation method. If there is a structure and its members need to be modified, find the corresponding implementation record element. Drag the data type to be replaced (i.e., the first associated type data) to the data type location selected in the previous step. After dragging and dropping, delete the product line used to import the replacement data type. Finally, verify that the replaced data type corresponds to the required data type.
[0099] If you need to unify the CP data type into the AP data type, export the service list from the AP and complete the verification to ensure that it meets the project standards. Then use the CP service import plug-in to import the service list into the project to convert the service list into a data format that the CP can recognize.
[0100] Find the service type (i.e., the first associated type data) that needs to be modified under the corresponding service in the CP, including ADT, ADT_Ref (ADT reference information), IDT, IDT_Ref (IDT reference information), as well as the mapping relationship between ADT data and IDT data (mapping), data calculation method, and initial value. Drag the data type to be replaced (i.e., the first associated type data) to the data type location selected in the previous step. After dragging and dropping, delete the product line used to import the replacement data type. Finally, check whether the replaced data type corresponds one-to-one with the requirements, focusing on checking whether the quantity and format of the initial value correspond to the modified data type.
[0101] It should be understood that, although the various steps in the flowcharts involved in the various embodiments described above are displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the various embodiments described above can include multiple steps or multiple stages, and these steps or stages are not necessarily executed and completed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of steps or stages in other steps.
[0102] Based on the same inventive concept, embodiments of the present application also provide a type-association data synchronization device for implementing the aforementioned type-association data synchronization method. The implementation solution provided by this device is similar to the implementation solution described in the aforementioned method. Therefore, the specific limitations of one or more of the following embodiments of the type-association data synchronization device can be found in the above-mentioned limitations of the type-association data synchronization method and will not be further elaborated here.
[0103] In an exemplary embodiment, Figure 4 As shown, a type-related data synchronization device 400 is provided, including:
[0104] A first determining module 401 is configured to, upon detecting a difference in service data types between at least two software platforms under the open automotive software architecture, determine a standard platform and a platform to be updated from the at least two software platforms, obtain service data of the standard platform, and use the service data as data to be synchronized;
[0105] An acquisition module 402 is configured to acquire target service data belonging to the same service as the data to be synchronized from the platform to be updated; the service is implemented through interaction between the standard platform and the platform to be updated;
[0106] A second determining module 403 is configured to determine first type associated data from the target service data, where the first type associated data is associated with a service data type of the target service data;
[0107] The modification module 404 is configured to modify the first-type associated data based on the second-type associated data in the data to be synchronized, where the second-type associated data is associated with the service data type of the service data to be synchronized.
[0108] In one embodiment, the second determining module 403 is specifically configured to:
[0109] Determining the data type field from the target service data;
[0110] determining other data associated with the data type from the target service data;
[0111] The data type field and the other data are used as the first type associated data.
[0112] In one embodiment, the device also includes a third determination module, which is used to convert the data format of the data to be synchronized into a data format recognizable by the platform to be updated before modifying the first type of associated data in the data to be synchronized based on the second type of associated data in the data to be synchronized as described in the modification module 404; determine the data associated with the service data type of the service data to be synchronized from the format-converted data to be synchronized; and use the data associated with the service data type of the service data to be synchronized as the second type of associated data.
[0113] In one embodiment, the modification module 404 is specifically configured to:
[0114] comparing the second-type associated data with the first-type associated data;
[0115] If there is new data in the second type of associated data relative to the first type of associated data, adding the new data to the first type of associated data;
[0116] If there is deletion data in the second type of associated data relative to the first type of associated data, deleting the deletion data from the first type of associated data;
[0117] When the second type of associated data is updated relative to the first type of associated data, the data to be updated in the first type of associated data is deleted, and the data in the second type of associated data corresponding to the data to be updated is used as updated data, and the updated data is added to the first type of associated data.
[0118] In one embodiment, when the standard platform is a classic platform and the platform to be updated is an adaptive platform, the data type field includes: implementation data type, and the other data includes: reference information of the implementation data type, data calculation method, and implementation record elements;
[0119] When the standard platform is an adaptive platform and the platform to be updated is a classic platform, the data type field includes: implementation data type and abstract data type, and the other data includes: reference information of the implementation data type, reference information of the abstract data type, a mapping relationship between data of the abstract data type and data of the implementation data type, a data calculation method, and a data type representation value.
[0120] In one embodiment, the modification module 404 is specifically used to: determine the data member structure and the number of data members under the interface structure from the data to be synchronized; the data member structure and the number of data members are related to the service data type of the data to be synchronized; based on the data member structure, modify the value structure of the data type representation value; based on the number of data members, set the number of the data type representation values.
[0121] Each module in the aforementioned type of association data synchronization device may be implemented in whole or in part through software, hardware, or a combination thereof. Each module may be embedded in or independent of a processor in a computer device in the form of hardware, or may be stored in a memory in the computer device in the form of software, so that the processor can call and execute the corresponding operations of each module.
[0122] In an exemplary embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as shown in FIG. Figure 5As shown. The computer device includes a processor, memory, an input / output interface, a communication interface, a display unit, and an input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and external devices. The communication interface of the computer device is used to communicate with external terminals via wired or wireless means, and the wireless means can be implemented via Wi-Fi, a mobile cellular network, near-field communication (NFC), or other technologies. When executed by the processor, the computer program implements a type-associated data synchronization method. The display unit of the computer device is used to form a visually visible image, and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device casing, or an external keyboard, touchpad or mouse.
[0123] Those skilled in the art will understand that Figure 5 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.
[0124] In an exemplary embodiment, a computer device is provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps in the above method embodiments when executing the computer program.
[0125] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.
[0126] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.
[0127] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.
[0128] Those skilled in the art will understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. In particular, any reference to memory, database, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The databases involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the various embodiments provided herein may be, but are not limited to, general-purpose processors, central processing units (CPUs), graphics processing units (GPUs), digital signal processors (DSPs), programmable logic devices (PLDs), quantum computing-based data processing logic devices, artificial intelligence (AI) processors, and the like.
[0129] The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.
[0130] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.
Claims
1. A type-related data synchronization method, characterized in that: The method comprises: When it is detected that there is a difference in the service data types of at least two software platforms under the open automotive software architecture, determining a standard platform and a platform to be updated from the at least two software platforms, and obtaining service data of the standard platform, and using the service data as data to be synchronized; Acquire target service data belonging to the same service as the data to be synchronized from the platform to be updated; the service is implemented through interaction between the standard platform and the platform to be updated; Determine first type association data from the target service data, where the first type association data is associated with a service data type of the target service data; The first type of associated data is modified based on second type associated data in the data to be synchronized, where the second type associated data is associated with the service data type of the service data to be synchronized.
2. The method according to claim 1, characterized in that The determining the first type of associated data from the target service data comprises: Determining the data type field from the target service data; Determining other data associated with the data type from the target service data; The data type field and the other data are used as the first type associated data.
3. The method according to claim 1 or 2, characterized in that: Before modifying the first type of associated data based on the second type of associated data in the data to be synchronized, the method further includes: Converting the data format of the data to be synchronized into a data format recognizable by the platform to be updated; Determining data associated with a service data type of the service data to be synchronized from the format-converted data to be synchronized; The data associated with the service data type of the service data to be synchronized is used as the second type associated data.
4. The method according to claim 3, characterized in that The modifying the first type of associated data based on the second type of associated data in the data to be synchronized includes: comparing the second type of associated data with the first type of associated data; If there is new data in the second type of associated data relative to the first type of associated data, adding the new data to the first type of associated data; If there is deletion data in the second type of associated data relative to the first type of associated data, deleting the deletion data from the first type of associated data; When the second type of associated data is updated relative to the first type of associated data, the data to be updated in the first type of associated data is deleted, and the data in the second type of associated data corresponding to the data to be updated is used as updated data, and the updated data is added to the first type of associated data.
5. The method according to claim 1 or 2, characterized in that: In the case where the standard platform is a classic platform and the platform to be updated is an adaptive platform, the data type field includes: implementation data type, and the other data includes: reference information of the implementation data type, data calculation method, and implementation record element; When the standard platform is an adaptive platform and the platform to be updated is a classic platform, the data type field includes: an implementation data type and an abstract data type, and the other data includes: reference information of the implementation data type, reference information of the abstract data type, a mapping relationship between data of the abstract data type and data of the implementation data type, a data calculation method, and a data type characterization value.
6. The method according to claim 5, characterized in that The modifying the first type of associated data based on the second type of associated data in the data to be synchronized includes: Determine a data member structure and a number of data members under an interface structure from the data to be synchronized; the data member structure and the number of data members are related to a service data type of the data to be synchronized; Based on the data member structure, modify the value structure of the data type representation value; The number of the data type representation values is set based on the number of data members.
7. A type-related data synchronization device, characterized in that: The device comprises: A first determination module is configured to, when detecting that there is a difference in the service data types of at least two software platforms under the open automotive software architecture, determine a standard platform and a platform to be updated from the at least two software platforms, obtain service data of the standard platform, and use the service data as data to be synchronized; An acquisition module, used for acquiring target service data belonging to the same service as the data to be synchronized from the platform to be updated; the service is realized through the interaction between the standard platform and the platform to be updated; A second determining module, configured to determine first type associated data from the target service data, where the first type associated data is associated with a service data type of the target service data; The modification module is used to modify the first type of associated data based on the second type of associated data in the data to be synchronized, where the second type of associated data is associated with the service data type of the service data to be synchronized.
8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.
10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.
Citation Information
Cited By
Data analysis method and system for ship repair enterprise operation management
CN120541084A
