Middleware-based data transmission method and device, vehicle and storage medium

Abstract

The application discloses a middleware-based data transmission method and device, a vehicle and a storage medium. If the middleware receives a target data request sent by an upper-layer application, it is determined whether the target data corresponding to the target data request is cached in a first cache area of the middleware. If it is determined that the target data is cached in the first cache area, the target data is fed back to the upper-layer application. The target data in the first cache area is historical data requested from a lower-layer application based on a historical data request by calling a set interface function corresponding to the lower-layer application. Based on this, when the target data request is received, the middleware first determines whether the target data corresponding to the target data request is cached in the first cache area, so that the target data is directly fed back from the first cache area to the upper-layer application in the case that the target data is cached in the first cache area, thereby reducing the consumption of redundant resources and improving the timeliness of request feedback between the upper-layer application and the lower-layer application.

Description

Technical Field

[0001] This application relates to the field of vehicle data transmission technology, and more specifically, to a middleware-based data transmission method, apparatus, vehicle, and storage medium. Background Technology

[0002] With the development of intelligent driving technology, more and more sensors and underlying applications are being used in intelligent driving systems. Furthermore, the upper-level applications of vehicles need to implement more and more system functions, and the data transmission tasks between multiple upper-level applications and multiple lower-level applications in the system are becoming increasingly heavy.

[0003] In related technologies, lower-layer applications need to respond immediately to each data request sent by upper-layer applications. This results in redundant resource consumption when data is repeatedly requested from the same lower-layer application, causing other lower-layer applications to be unable to respond to the received data requests in a timely manner. Therefore, how to enable lower-layer applications to respond to data requests sent by upper-layer applications in a timely manner has become an important technical problem. Summary of the Invention

[0004] This application proposes a middleware-based data transmission method, apparatus, vehicle, and storage medium to improve upon the aforementioned deficiencies.

[0005] In a first aspect, embodiments of this application provide a middleware-based data transmission method, comprising: if the middleware receives a target data request sent by an upper-layer application, determining whether a first cache of the middleware contains target data corresponding to the target data request, wherein the target data request is used to request the target data from its corresponding lower-layer application; if it is determined that the target data is cached in the first cache, then feeding back the target data to the upper-layer application, wherein the target data in the first cache is historical data requested from the lower-layer application based on a historical data request, by calling a set interface function corresponding to the lower-layer application, wherein the historical data request and the target data request are data requests of the same type.

[0006] Secondly, embodiments of this application provide a middleware-based data transmission device, comprising: a target data determination module, configured to determine whether a first cache of the middleware contains target data corresponding to the target data request if the middleware receives a target data request sent by an upper-layer application, wherein the target data request is used to request the target data from its corresponding lower-layer application; and a feedback module, configured to feed back the target data to the upper-layer application if it is determined that the target data is cached in the first cache, wherein the target data in the first cache is historical data requested from the lower-layer application based on a historical data request, by calling a set interface function corresponding to the lower-layer application, wherein the historical data request and the target data request are of the same type.

[0007] Thirdly, embodiments of this application also provide a vehicle, including: one or more processors; a memory; one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs are configured to perform the methods described above.

[0008] Fourthly, embodiments of this application also provide a computer-readable storage medium storing program code that can be invoked by a processor to execute the above-described method.

[0009] In the middleware-based data transmission method provided in this application, if the middleware receives a target data request sent by an upper-layer application, it determines whether the first buffer of the middleware contains target data corresponding to the target data request. The target data request is used to request target data from its corresponding lower-layer application. If it is determined that the first buffer contains target data, the target data is fed back to the upper-layer application. The target data in the first buffer is historical data requested from the lower-layer application based on historical data requests, by calling the set interface function corresponding to the lower-layer application. The historical data request and the target data request are data requests of the same type. In other words, this application sets up middleware between the upper-layer application and the lower-layer application. The middleware can cache the application data requested from the lower-layer application in its first cache area. When it receives a target data request sent by the upper-layer application, the middleware first determines whether the target data corresponding to the target data request is cached in its first cache area. If the target data is cached in its first cache area, the middleware directly feeds back the target data from the first cache area to the upper-layer application, thereby avoiding repeated requests for data from the same lower-layer application, reducing the consumption of redundant resources, and thus improving the timeliness of request feedback between the upper-layer application and the lower-layer application.

[0010] Other features and advantages of the embodiments of this application will be set forth in the following description, and will be apparent in part from the description, or may be learned by practicing the embodiments of this application. The objects and other advantages of the embodiments of this application may be realized and obtained by means of the structures particularly pointed out in the written description, claims, and drawings. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 A system architecture diagram of a middleware-based data transmission system provided in an embodiment of this application is shown.

[0013] Figure 2 A schematic flowchart of a middleware-based data transmission method provided in an embodiment of this application is shown.

[0014] Figure 3 A flowchart illustrating a middleware-based data transmission method provided in another embodiment of this application is shown.

[0015] Figure 4 This application shows Figure 3 A flowchart illustrating a sub-step of step S350 in one embodiment.

[0016] Figure 5 This application shows Figure 3 A flowchart illustrating a sub-step of step S350 in another embodiment.

[0017] Figure 6 A schematic flowchart of a middleware-based data transmission method provided in another embodiment of this application is shown.

[0018] Figure 7 The diagram shows a structural block diagram of a middleware-based data transmission device according to an embodiment of this application.

[0019] Figure 8 A structural block diagram of a vehicle provided in an embodiment of this application is shown.

[0020] Figure 9 A structural block diagram of a computer-readable storage medium provided in an embodiment of this application is shown. Detailed Implementation

[0021] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, and not all of them. The components of the embodiments of the present application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of the present application. All other embodiments obtained by those skilled in the art based on the embodiments of the present application without inventive effort are within the scope of protection of the present application.

[0022] It should be noted that some processes described in the specification, claims, and accompanying drawings of this application include multiple operations that appear in a specific order. These operations may not be performed in the order they appear herein, or they may be performed in parallel. Operation numbers such as S110, S120, etc., are merely used to distinguish different operations and do not represent any execution order. Furthermore, these processes may include more or fewer operations, and these operations may be performed sequentially or in parallel. Also, the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having”, and any variations thereof, are intended to cover non-exclusive inclusion, such that a process, method, system, product, or server that includes a series of steps or sub-modules is not necessarily limited to those steps or sub-modules that are explicitly listed, but may include other steps or sub-modules that are not explicitly listed or that are inherent to such process, method, product, or device.

[0023] Please see Figure 1 , Figure 1 This diagram illustrates the system architecture of a middleware-based data transmission system 100 according to an embodiment of this application. The middleware-based data transmission system 100 of this embodiment includes at least a middleware 110, multiple upper-layer applications 120, and multiple lower-layer applications 130.

[0024] In this embodiment, middleware 110 is located between multiple upper-layer applications 120 and multiple lower-layer applications 130. Middleware 110 is used to obtain target data requests from upper-layer applications 120 and send the target data requests to the corresponding lower-layer applications 130. Middleware 110 also obtains target data corresponding to the target data requests fed back by lower-layer applications 130 and sends the target data to upper-layer applications 120. Each upper-layer application 120 can send target data requests for each lower-layer application 130 to different lower-layer applications 130, and multiple upper-layer applications 120 can also send target data requests for the same lower-layer application 130. Middleware 110 includes a first buffer 140 and a second buffer 150. The first buffer 140 of middleware 110 is used to cache the target data corresponding to the target data requests obtained by middleware 110 from lower-layer applications 130, and the second buffer 150 of middleware 110 is used to cache the target data requests received from upper-layer applications 120.

[0025] In this embodiment, the middleware-based data transmission system 100, where the middleware 110 resides, can be a domain controller for a target domain in the vehicle intelligent driving system. The target domain includes, but is not limited to, the body domain, powertrain domain, chassis domain, autonomous driving domain, and cockpit domain. The body domain contains body electronics and related information; the powertrain domain includes vehicle safety and related information; the chassis domain includes vehicle motion and related information; the autonomous driving domain includes driver assistance and related information; and the cockpit domain includes entertainment information and related information. For example, when the target domain is the body domain, the upper-layer application 120 includes at least a seat control application and a door control application, and the lower-layer application 130 includes at least a vehicle speed detection application. The seat control application needs to determine whether to lock the seat based on the current vehicle speed data, and the door control application needs to determine whether to lock the door based on the current vehicle speed data. Both the seat control application and the door control application need to request body data from the vehicle speed detection application.

[0026] In this embodiment, a preset communication matrix is ​​imported into the middleware 110. This communication matrix is ​​typically defined by the vehicle manufacturer. It represents the signal transmission links between multiple upper-layer applications 120 and multiple lower-layer applications 130 during vehicle communication. The communication matrix is ​​essential for information interaction and sharing between the upper-layer applications 120 and lower-layer applications 130 in the middleware-based data transmission system 100. Based on this communication matrix, designers can clearly define the message signals that each upper-layer application 120 needs to send and receive to achieve its corresponding application function, thus defining multiple message signals. Each message signal includes at least a signal identifier, a signal type, and a signal value. Each lower-layer application 130 can only provide corresponding application data feedback for one message signal, but each upper-layer application 120 can send its corresponding message signal to multiple different lower-layer applications 130.

[0027] Optionally, the middleware 110 can determine the corresponding lower-level application 130 by parsing the signal identifier contained in each message signal sent by the upper-level application 120. This allows it to create functional logic code for implementing the corresponding setting interface function call of the lower-level application 130 when requesting application data from the lower-level application 130, and to cache the functional logic code corresponding to each lower-level application 130. Furthermore, the middleware 110 is also used to create functional logic code for implementing the setting interface function call of the upper-level application 120 when the target data requested from the lower-level application 130 is fed back to the upper-level application 120, and to cache the functional logic code corresponding to each upper-level application 120. Here, the setting interface function is the Application Programming Interface (API), which is a calling interface provided by the operating system for applications. Applications use the operating system's API to cause the operating system to execute commands from the application.

[0028] Specifically, for a target data request (i.e., a message signal) sent by the upper-layer application 120 to the middleware 110 for the lower-layer application 130, the middleware 110 parses the target data request, determines the lower-layer application 130 corresponding to the target data request, and caches the target data request in the second buffer 150. Further, the middleware 110 uses pre-cached functional logic code corresponding to the lower-layer application 130 to call the corresponding defined interface function of the lower-layer application 130 to request the target data corresponding to the target data request from the lower-layer application 130. For the target data fed back by the lower-layer application 130 to the middleware 110 based on the obtained target data request, the middleware 110 encapsulates the requested target data into a message signal and caches the target data in the second buffer 150. Furthermore, the middleware 110 uses the pre-cached functional logic code corresponding to the upper-layer application 120 to call the setting interface function corresponding to the upper-layer application 120, and sends the encapsulated message signal to the uploading application, thereby realizing the feedback of target data to the upper-layer application 120.

[0029] It should be noted that for the multiple lower-level applications 130 in the middleware-based data transmission system 100, since these lower-level applications 130 are developed and designed by different application vendors, most popular lower-level applications 130 use proprietary application programming interfaces and transmission protocols, resulting in different configuration interface functions for different lower-level applications 130. Correspondingly, for the multiple upper-level applications 120 in the middleware-based data transmission system 100, since these upper-level applications 120 are developed and designed by the vehicle manufacturer, they can be configured with the same configuration interface functions. When the multiple upper-level applications 120 and the multiple lower-level applications 130 in the vehicle domain controller directly interact, the functional logic code of the corresponding port call components needs to be pre-configured for each upper-level application 120 and its corresponding multiple lower-level applications 130. When a lower-level application 130 is updated or its number increases or decreases, the functional logic code of the original port call components of each upper-level application 120 corresponding to that lower-level application 130 needs to be modified, significantly increasing the workload of developers.

[0030] In this embodiment, the middleware 110 is used to realize information interaction and sharing between multiple upper-layer applications 120 and multiple lower-layer applications 130. For multiple lower-layer applications 130 with different configuration interface functions, by setting the corresponding functional logic code for each lower-layer application 130 in the middleware 110 to call the corresponding configuration interface function of each lower-layer application 130, a platform-based communication mechanism for multiple lower-layer applications 130 can be achieved within the middleware 110. Furthermore, when a lower-layer application 130 needs to interact with multiple upper-layer applications 120, only the corresponding functional logic code for that lower-layer application 130 needs to be set in the middleware 110, without repeated settings in multiple upper-layer applications 120. For multiple upper-layer applications 120 with the same configuration interface function, by setting unified functional logic code for multiple upper-layer applications 120 in the middleware 110 to call the corresponding configuration interface function of each upper-layer application 120, unified communication between multiple upper-layer applications 120 can be achieved within the middleware 110. Based on this, the middleware 110 can decouple multiple upper-layer applications 120 from multiple lower-layer applications 130. When the lower-layer application 130 is updated or the number of lower-layer applications 130 increases or decreases, by determining the changes in the setting interface functions of the lower-layer application 130 and the changes in the number of lower-layer applications 130, developers only need to update the functional logic code of the setting port function of the changed lower-layer application 130 cached in the middleware 110 once, which improves the convenience and efficiency of lower-layer application 130 access.

[0031] Please see Figure 2 , Figure 2 A schematic flowchart of a middleware-based data transmission method according to an embodiment of this application is shown. The following will be combined with... Figure 2 The middleware-based data transmission method provided in this application is described in detail. Please refer to [link / reference needed] for details on this middleware-based data transmission method. Figure 2 This may include the following steps:

[0032] Step S210: If the middleware receives a target data request sent by the upper layer application, it determines whether the middleware's first cache contains the target data corresponding to the target data request. The target data request is used to request the target data from its corresponding lower layer application.

[0033] In this embodiment, if the middleware receives a target data request sent by an upper-layer application, it queries the signals cached in the middleware's first buffer to determine whether the first buffer contains target data corresponding to the target data request. Specifically, the middleware requests the target data from the lower-layer application corresponding to the target data request and then feeds back the target data requested from the lower-layer application to the upper-layer application.

[0034] Optionally, upon receiving a target data request from an upper-layer application, the middleware parses the target data request to determine the target data corresponding to the request, and caches the target data request in the middleware's second cache. The middleware's first cache is used to cache the target data corresponding to the target data request obtained by the middleware from the lower-layer application, while the middleware's second cache is used to cache the target data requests received by the middleware from the upper-layer application.

[0035] Step S220: If it is determined that the target data is cached in the first cache area, the target data is fed back to the upper layer application. The target data in the first cache area is based on historical data requests. The corresponding interface function of the lower layer application is called to request historical data from the lower layer application. The historical data request and the target data request are the same type of data request.

[0036] In this embodiment, if the middleware determines that its first cache contains target data corresponding to the target data request, it directly feeds back the target data cached in the first cache to the upper-layer application. The target data currently cached in the first cache corresponding to the target data request is historical data requested by the middleware from the lower-layer application based on historical data requests, by calling a defined interface function corresponding to the lower-layer application. Furthermore, the historical data request and the target data request are of the same type.

[0037] Optionally, if the middleware's first cache contains the target data corresponding to the target data request, when the middleware receives a target data request from an upper-layer application, it only caches the target data request in the middleware's second cache and does not call the corresponding interface function of the lower-layer application, thereby avoiding duplicate requests for target data from the lower-layer application. Since the process of requesting data from the lower-layer application will consume the runtime resources of the middleware-based data transmission system, the middleware can reduce the consumption of redundant resources in the middleware-based data transmission system by avoiding duplicate requests for target data from the lower-layer application, thereby reducing the system's runtime load and improving the timeliness of request feedback between multiple upper-layer applications and multiple lower-layer applications.

[0038] In this embodiment, by setting up middleware between the upper-layer application and the lower-layer application, and the middleware being able to cache application data requested from the lower-layer application in its first cache area, when receiving a target data request sent by the upper-layer application, the middleware first determines whether the target data corresponding to the target data request is cached in its first cache area. If the target data is cached in its first cache area, the middleware directly feeds back the target data from the first cache area to the upper-layer application, thereby avoiding repeated requests for data from the same lower-layer application, reducing the consumption of redundant resources, and thus improving the timeliness of request feedback between the upper-layer application and the lower-layer application.

[0039] Please see Figure 3 , Figure 3 A schematic flowchart of a middleware-based data transmission method according to another embodiment of this application is shown. The following will be combined with... Figure 3 The middleware-based data transmission method provided in this application is described in detail. Please refer to [link / reference needed] for details on this middleware-based data transmission method. Figure 3 This may include the following steps:

[0040] Step S310: If the middleware receives a target data request sent by the upper layer application, it determines whether the middleware's first cache contains the target data corresponding to the target data request. The target data request is used to request the target data from its corresponding lower layer application.

[0041] In this embodiment, the specific implementation of step S310 can be found in the content of the foregoing embodiments, and will not be repeated here.

[0042] Step S320: If it is determined that the target data is cached in the first cache area, and the target data is determined to be application data requested within the current data update cycle of the lower layer application, then the target data is fed back to the upper layer application, and the current data update cycle is the data update cycle at the current moment.

[0043] Optionally, if it is determined that the target data is cached in the first cache area, and the target data is determined to be application data requested within the current data update cycle of the lower-level application, that is, the target data cached in the first cache area is the latest application data of the lower-level application, then the middleware will not call the setting interface function corresponding to the lower-level application, and will directly feed back the target data cached in the first cache area to the upper-level application.

[0044] For example, when the middleware receives target data from the lower-layer application and caches the target data in its defined cache area: It synchronously retrieves the timestamp of the target data, such as January 17th, 14:21:30, and determines whether the current time is within the same data update cycle as the timestamp of the target data cached in the first cache area. If they are within the same data update cycle, the target data is determined to be application data requested within the current data update cycle of the lower-layer application. Alternatively, it synchronously retrieves the target data within the time cycle range of the target data, such as January 17th, 14:21:30-January 17th, 14:22:00, and determines whether the current time is within the time cycle range of the target data cached in the first cache area. If they are within the time cycle range of the target data, the target data is determined to be application data requested within the current data update cycle of the lower-layer application.

[0045] Step S330: If it is determined that the target data is cached in the first cache area, and the target data is determined to be application data requested within the historical data update cycle of the lower layer application, then the updated application data is requested from the lower layer application by calling the set interface function corresponding to the lower layer application. The historical data update cycle is any data update cycle before the current data update cycle.

[0046] Optionally, if it is determined that the target data is cached in the first cache area, and the target data is determined to be application data requested within the historical data update cycle of the lower-level application, that is, the target data cached in the first cache area is not the latest application data of the lower-level application, then the middleware needs to request the updated application data from the lower-level application by calling the set interface function corresponding to the lower-level application.

[0047] For example, when the middleware receives target data from the lower-layer application and caches the target data in its defined cache area: the synchronous cache obtains the timestamp of the target data and determines whether the current time is within the same data update cycle time range as the timestamp of the target data cached in the first cache area. If it is outside the data update cycle time range, it is determined that the target data is not the latest application data of the lower-layer application; or, the synchronous cache obtains the target data within the time cycle range of the target data and determines whether the current time is within the time cycle range of the target data cached in the first cache area. If it is not within the time cycle range of the target data, it is determined that the target data is not the latest application data of the lower-layer application.

[0048] If the middleware directly feeds back the target data cached in the first cache to the upper-layer application, the upper-layer application is prone to mismatches between the control commands generated based on the data processing results and the current application scenario due to deviations in the received application data. For example, when the upper-layer application is a seat control application and the lower-layer application is a vehicle speed detection application, if the vehicle has stopped moving or is within the set safe driving speed range, but the vehicle speed data fed back to the door control application by the middleware is not the latest vehicle speed data from the vehicle speed detection application, the seat control application may lock the vehicle's seat based on the received vehicle speed data, preventing the driver from adjusting the seat.

[0049] In this embodiment, after determining that the target data corresponding to the target data request is cached in the first cache, the middleware further needs to determine whether the target data cached in the first cache is application data requested within the current data update cycle of the lower-layer application. The middleware only directly feeds back the target data cached in the first cache to the upper-layer application when it detects that the target data is application data requested within the current data update cycle of the lower-layer application. When the middleware detects that the target data is application data requested within a historical data update cycle of the lower-layer application, it still needs to call the corresponding interface function of the lower-layer application to request data from the lower-layer application. Based on this, the middleware can not only ensure that the application data fed back to the upper-layer application is the latest application data request from the lower-layer application, but also avoid duplicate requests for application data from the lower-layer application, thereby reducing the consumption of redundant resources.

[0050] like Figure 1 As shown, the configuration interface functions of the lower-layer application 130 include: a configuration interface function corresponding to the lower-layer signal receiving interface, used by the middleware 110 to receive the target data fed back by the lower-layer application 130; and a configuration interface function corresponding to the lower-layer signal sending interface, used by the middleware 110 to send a target data request to the lower-layer application 130.

[0051] In this embodiment, when it is determined that the target data cached by the middleware 110 is application data requested within the current data update cycle of the lower-layer application 130, the middleware 110 no longer calls the setting interface function corresponding to the lower-layer signal sending interface and no longer sends the target data request to the lower-layer application 130. When it is determined that the target data cached by the middleware 110 is application data requested within the historical data update cycle of the lower-layer application 130, the middleware 110 sends the target data request to the lower-layer application 130 by calling the setting interface function corresponding to the lower-layer signal sending interface. Further, when it is determined that the lower-layer application 130 updates application data, the middleware 110 calls the setting interface function corresponding to the lower-layer signal receiving interface to request the updated application data from the lower-layer application 130.

[0052] Step S340: Feed back the updated application data to the upper-layer application and replace the target data in the first cache with the updated application data.

[0053] In this embodiment, the middleware feeds back the updated application data requested from the lower-layer application to the upper-layer application, and replaces the target data currently cached in the first cache with the updated application data.

[0054] Step S350: If it is determined that the target data is not cached in the first cache area, the target data is requested from the lower-level application by calling the set interface function corresponding to the lower-level application.

[0055] In this embodiment, if the middleware determines that its first buffer does not contain the target data corresponding to the target data request, the middleware requests the target data from the lower-level application by calling the designated interface function corresponding to the lower-level application. Specifically, when the middleware calls the designated interface function corresponding to the lower-level application based on the target data request, it needs to determine the signal type of the target data request. Since the target data request includes at least a signal identifier, a signal type, and a signal value, the middleware can determine its signal type upon receiving the target data request.

[0056] Optionally, the signal types for data requests include at least event-based data requests and periodic data requests. An event-based data request means that when the data request appears in the upper-layer application, it is immediately sent to the corresponding lower-layer application. A periodic data request means that when the data request appears in the upper-layer application, it is continuously sent by the upper-layer application to its corresponding lower-layer application according to the request period corresponding to the data request.

[0057] Optionally, when the target data request is an event-based data request, if it is determined that the target data is not cached in the first cache area, the middleware directly calls the set interface function corresponding to the lower-level application to request the target data from the lower-level application.

[0058] Optionally, when the target data request is a periodic data request, if it is determined that the target data is not cached in the first cache area, the middleware calls the set interface function corresponding to the lower-level application based on the request period corresponding to the target data request to request the target data from the lower-level application.

[0059] like Figure 1 As shown, if it is determined that the target data is not cached in the first buffer 140 and the target data request is an event-type data request, the middleware 110 immediately calls the setting interface function corresponding to the lower-level signal sending interface of the lower-level application 130 to send the target data request to the lower-level application 130, and requests the target data from the lower-level application 130 by calling the setting interface function corresponding to the lower-level signal receiving interface.

[0060] Optionally, if it is determined that no target data is cached in the first buffer 140 and the target data request is a periodic data request, the middleware 110, after determining the request period of the target data request, also needs to analyze the request period of the target data request to determine whether to call the set interface function corresponding to the lower-level signal sending interface of the lower-level application 130 corresponding to the target data request at the current time.

[0061] Optionally, if it is determined that the target data is not cached in the first cache, then based on the request period corresponding to the target data request, the set interface function corresponding to the lower-level application is called to request the target data from the lower-level application. Please refer to [reference needed]. Figure 4Specifically, this includes the following steps S351A to S352A:

[0062] In some implementations, there are multiple target data requests and multiple upper-layer applications. Each target data request corresponds one-to-one with a specific upper-layer application. For any one of the multiple target data requests that is a periodic data request:

[0063] Step S351A: If the request period corresponding to the target data request is less than the data update period of the lower layer application, then the request response period corresponding to the target data request is adjusted to the target request response period, and the target request response period matches the data update period of the lower layer application.

[0064] In this embodiment, if the request period corresponding to the target data request is shorter than the data request period of its corresponding lower-level application, the middleware adjusts the request-response period of the target data request to match the target request-response period, so that the adjusted target request-response period matches the data update period of the lower-level application. Specifically, before adjustment: the request-response period of the target data request matches the request period of the target data request, and the middleware calls the designated interface function corresponding to the lower-level application based on the request-response period of the target data request; after adjustment, the request period of the target data request remains unchanged, and the middleware calls the designated interface function corresponding to the lower-level application based on the target data request, thus changing the request-response period for requesting the target data from the lower-level application.

[0065] For example, if the duration of the data request cycle of the lower-level application is twice the duration of the request cycle corresponding to the target data request, and the middleware calls the corresponding interface function of the lower-level application based on the request cycle of the target data request to request the target data from the lower-level application, the middleware will request the target data from the lower-level application twice within the data update cycle of the lower-level application updating its application data. In this case, the two requests for target data obtained by the middleware from the lower-level application are the same, that is, the middleware makes duplicate requests for the same target data, resulting in a waste of middleware runtime resources.

[0066] Step S352A: Based on the target request response cycle, call the set interface function corresponding to the lower-level application to request the target data from the lower-level application.

[0067] In this embodiment, the middleware calls the set interface function corresponding to the lower-layer application to request target data from the lower-layer application based on the adjusted target request response cycle that matches the data update cycle of the lower-layer application.

[0068] In this embodiment, the middleware compares the request period corresponding to the target data request with the data update period of the lower-layer application. When the request period corresponding to the target data request is greater than or equal to the data update period of the lower-layer application, the middleware calls the designated interface function corresponding to the lower-layer application based on the request period to request the target data from the lower-layer application. When the request period corresponding to the target data request is less than the data update period of the lower-layer application, the request-response period corresponding to the target data request is adjusted. Based on the adjusted target request-response period, the middleware calls the designated interface function corresponding to the lower-layer application to request the target data from the lower-layer application. This approach avoids the middleware repeatedly calling the designated interface function corresponding to the lower-layer application to request the same target data repeatedly, reducing the operating energy consumption of the middleware-based data transmission system, thereby reducing the system's operating load and improving the timeliness of request feedback between multiple upper-layer applications and multiple lower-layer applications.

[0069] Optionally, if it is determined that the target data is not cached in the first cache, then based on the request period corresponding to the target data request, the set interface function corresponding to the lower-level application is called to request the target data from the lower-level application. Please refer to [reference needed]. Figure 5 Specifically, it also includes the contents of steps S351B to S352B:

[0070] In some implementations, there are multiple target data requests and multiple upper-layer applications. Each target data request corresponds one-to-one with a specific upper-layer application, and these multiple target data requests are periodic data requests received by the middleware simultaneously.

[0071] Step S351B: If there are multiple first data requests with the same request period among multiple target data requests, and the multiple first data requests are data requests for different lower-level applications, then the request response time of each first data request is adjusted, and the request response time of different first data requests is different after adjustment.

[0072] In this embodiment, when multiple target data requests received by the middleware at the same time are middleware periodic data requests, if it is determined that there are multiple first data requests with the same request period among the multiple target data requests, and the multiple first data requests are data requests for different lower-level applications, then the middleware needs to adjust the request response time of each first data request in order to avoid the middleware calling the set interface function of the lower-level application corresponding to each first data request at the same time, which would cause a large operating load on the middleware-based data transmission system where the middleware is located.

[0073] Optionally, the middleware adjusts the request-response time of each first data request so that the request-response times of different first data requests are different after adjustment. This distributes first data requests with the same request cycle for different lower-level applications at the same time to different times, thereby reducing the system's load peak, improving the system's load balance, and thus reducing the possibility of the system crashing due to excessive load.

[0074] In this embodiment, for data requests other than multiple first data requests among multiple target data requests, the middleware requests the corresponding target data from the lower-level application corresponding to each target data request based on the request period corresponding to each target data request.

[0075] In some implementations, if the middleware receives multiple target data requests at the same time, it determines the priority of each target data request and adjusts the request response time for each target data request. This is done by calling the interface function of the lower-level application corresponding to the higher-priority target data request first, and then calling the interface function of the lower-level application corresponding to the lower-priority target data request. In this way, the middleware requests the corresponding target data from the lower-level application corresponding to each target data request, thereby reducing the peak load of the middleware-based data transmission system, improving the system's load balancing, and reducing the system's operating load.

[0076] Step S352B: Based on the adjusted request-response time of each first data request, call the set interface function of the lower-level application corresponding to each first data request, and request the first data corresponding to each first data request from the lower-level application corresponding to each first data request.

[0077] In this embodiment, based on the adjusted request response time of each first data request, the middleware uses the adjusted request response time of each first data request as a starting point, and calls the set interface function of the lower-level application corresponding to each first data request according to the request cycle corresponding to each first data request, to request the first data corresponding to each first data request from the lower-level application corresponding to each first data request.

[0078] In this process, after adjusting the request-response time for each first data request, the middleware only allocates first data requests for different lower-level applications at the same time to different times for processing. The request cycle and request-response cycle for each first data request remain unchanged. That is, based on the adjusted request-response time for each first data request, the middleware calls the set interface function corresponding to the lower-level application according to the request-response cycle corresponding to that first data request. The specific implementation method is the same as described above and will not be repeated here.

[0079] Step S360: Feed the target data back to the upper layer application and cache the target data in the first cache area.

[0080] In this embodiment, after the middleware obtains the target data corresponding to the target data request from the corresponding lower-layer application, the middleware feeds back the target data to the upper-layer application and caches the target data in the first cache area. Specifically, when the middleware determines that it has obtained the target data corresponding to the target data request from the lower-layer application, it immediately feeds back the requested target data to the upper-layer application.

[0081] like Figure 1 As shown, the setting interface functions of the upper-layer application 120 include: a setting interface function corresponding to the upper-layer signal receiving interface, used by the middleware 110 to receive the target data fed back by the upper-layer application 120; and a setting interface function corresponding to the upper-layer signal sending interface, used by the middleware 110 to send a target data request to the upper-layer application 120. In this embodiment, when the middleware 110 receives the target data, it immediately calls the setting interface function corresponding to the upper-layer signal sending interface of the upper-layer application 120 to feed back the target data to the upper-layer application 120 and stores the target data in the first buffer 140.

[0082] In this embodiment, after determining that the target data corresponding to the target data request is cached in the first cache, the middleware further determines whether the target data cached in the first cache is application data requested within the current data update cycle of the lower-level application. Only when the target data is detected as application data requested within the historical data update cycle of the lower-level application will the request be made to the lower-level application. This ensures the validity of the application data fed back to the upper-level application and avoids duplicate requests for application data from the lower-level application, thereby reducing the consumption of redundant resources. Furthermore, when the target data request is an event-based data request, the middleware analyzes the request cycle of the target data request to determine whether the lower-level application corresponding to the request should be accessed at the current time. This reduces the system's load peak, improves the system's load balancing, and ultimately reduces the possibility of system crashes due to excessive load.

[0083] Please see Figure 6 , Figure 6 A schematic flowchart of a middleware-based data transmission method according to another embodiment of this application is shown. The following will be combined with... Figure 6 The middleware-based data transmission method provided in this application is described in detail. Please refer to [link / reference needed] for details on this middleware-based data transmission method. Figure 6 This may include the following steps:

[0084] Step S410: If the middleware receives a target data request sent by the upper layer application, it determines whether the middleware's first cache contains the target data corresponding to the target data request. The target data request is used to request the target data from its corresponding lower layer application.

[0085] Step S420: If it is determined that the target data is cached in the first cache area, the target data is fed back to the upper layer application. The target data in the first cache area is based on historical data requests. The corresponding interface function of the lower layer application is called to request historical data from the lower layer application. The historical data request and the target data request are the same type of data request.

[0086] In this embodiment, the specific implementation of steps S410 to S420 can be found in the content of the foregoing embodiments, and will not be repeated here.

[0087] There are multiple target data requests, multiple upper-layer applications, and multiple target data requests correspond one-to-one with multiple upper-layer applications. Furthermore, multiple target data requests are data requests for the same lower-layer application.

[0088] Step S430: If it is determined that the target data is not cached in the first cache area, the set interface function corresponding to the lower layer application corresponding to any target data request is called to request the target data from the lower layer application.

[0089] In this embodiment, if the middleware determines that the first cache does not contain target data corresponding to multiple target data requests for the same lower-level application, the middleware only needs to call the defined interface function of the lower-level application corresponding to any one of the target data requests to request the target data from the lower-level application. That is, for multiple identical target data requests for the same lower-level application, the middleware only needs to call the defined interface function of the lower-level application corresponding to the target data request once to request the target data from the lower-level application once, without needing to make multiple data requests.

[0090] Step S440: Feed back the target data to each upper-layer application and cache the target data in the first cache area.

[0091] In this embodiment, the middleware feeds back the received target data to each upper-layer application and caches the target data in the first cache. For example, when the upper-layer applications are a seat control application and a door control application, and the lower-layer application is a vehicle speed detection application, the seat control application needs to determine whether to lock the seat based on the current vehicle speed data, and the door control application needs to determine whether to lock the door based on the current vehicle speed data. If the seat control application and the door control application send vehicle speed data requests to the middleware at the same time, the middleware only needs to call the corresponding set interface function of the vehicle speed detection application based on the vehicle speed data request sent by any one of the upper-layer applications, request vehicle speed data from the vehicle speed detection application once, feed back the requested vehicle speed data to the seat control application and the door control application respectively, and cache the vehicle speed data in the first cache.

[0092] Optionally, when multiple target data requests are data requests for the same lower-level application received by the middleware at the same time, the middleware will simultaneously feed back the target data to each upper-level application that sent the target data request when it obtains the target data corresponding to the target data request.

[0093] Optionally, when multiple data requests are data requests for the same lower-level application received by the middleware at different times, for the later received target data request, the middleware needs to determine whether the target data currently cached in its first cache is application data requested within the current data update cycle of the lower-level application. If it is determined that the target data is application data requested within the current data update cycle of the lower-level application, the target data is fed back to the upper-level application; if it is determined that the target data is application data requested within a historical data update cycle of the lower-level application, the updated application data is requested from the lower-level application by calling the set interface function corresponding to the lower-level application, thereby feeding back the updated application data to the upper-level application.

[0094] In this embodiment, the middleware does not need to repeatedly request the same target data from multiple target data requests for the same lower-level application, thus reducing the middleware's operating power consumption. Furthermore, by detecting whether the target data cached in its first cache is the latest application data in the lower-level application, it determines whether a data request needs to be made again. When the middleware receives multiple target data requests for the same lower-level application at different times, it avoids invalid and repeated requests for application data from the lower-level application while ensuring that the application data fed back to the upper-level application is the latest application data from the lower-level application. This reduces the consumption of redundant resources in the middleware-based data transmission system and improves the timeliness of request feedback between multiple upper-level and lower-level applications.

[0095] Please refer to Figure 7 , Figure 7 A structural block diagram of a middleware-based data transmission device according to an embodiment of this application is shown. In this embodiment, the middleware-based data transmission device 500 includes at least a target data determination module 510 and a feedback module 520.

[0096] The target data determination module 510 is used to determine whether the first cache of the middleware contains target data corresponding to the target data request if the middleware receives a target data request sent by the upper layer application. The target data request is used to request target data from its corresponding lower layer application.

[0097] The feedback module 520 is used to feed back the target data to the upper layer application if it is determined that the target data is cached in the first cache area. The target data in the first cache area is the historical data requested from the lower layer application by calling the set interface function corresponding to the lower layer application. The historical data request and the target data request are the same type of data request.

[0098] Optionally, the feedback module 520 can be specifically used to: if it is determined that the target data is cached in the first cache area, and the target data is determined to be application data requested within the current data update cycle of the lower-level application, then the target data is fed back to the upper-level application, where the current data update cycle is the data update cycle at the current moment; if it is determined that the target data is cached in the first cache area, and the target data is determined to be application data requested within the historical data update cycle of the lower-level application, then the updated application data is requested from the lower-level application by calling the set interface function corresponding to the lower-level application, where the historical data update cycle is any data update cycle before the current data update cycle; the updated application data is fed back to the upper-level application, and the updated application data replaces the target data in the first cache area.

[0099] In this embodiment, the feedback module 520 can also be specifically used to: if it is determined that the target data is not cached in the first cache area, request the target data from the lower-level application by calling the set interface function corresponding to the lower-level application; feed the target data back to the upper-level application, and cache the target data in the first cache area.

[0100] In some implementations, there are multiple target data requests and multiple upper-layer applications. The multiple target data requests correspond one-to-one with the multiple upper-layer applications, and the multiple target data requests are data requests for the same lower-layer application. The feedback module 520 is specifically used to: if it is determined that there is no target data cached in the first cache area, call the set interface function corresponding to the lower-layer application corresponding to any target data request, request the target data from the lower-layer application, and feed back the target data to each upper-layer application respectively.

[0101] Optionally, the feedback module 520 includes at least a request module. The target data request is a periodic data request. The request module can be specifically used to: if it is determined that the target data is not cached in the first cache area, then based on the request period corresponding to the target data request, call the set interface function corresponding to the lower layer application to request the target data from the lower layer application.

[0102] In some implementations, the request module may specifically be used to: if the request period corresponding to the target data request is less than the data update period of the lower-level application, adjust the request response period corresponding to the target data request to the target request response period, and match the target request response period with the data update period of the lower-level application; based on the target request response period, call the set interface function corresponding to the lower-level application to request the target data from the lower-level application.

[0103] In other implementations, there are multiple target data requests and multiple upper-layer applications. Each target data request corresponds one-to-one with an upper-layer application, and the multiple target data requests are periodic data requests received by the middleware at the same time. The request module can also be specifically used to: if there are multiple first data requests with the same request period among the multiple target data requests, and the multiple first data requests are data requests for different lower-layer applications, then the request response time of each first data request is adjusted so that the request response times of different first data requests are different; based on the adjusted request response time of each first data request, the set interface function of the lower-layer application corresponding to each first data request is called to request the first data corresponding to each first data request from the lower-layer application corresponding to each first data request.

[0104] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the above-described device and module can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0105] In the several embodiments provided in this application, the coupling between modules can be electrical, mechanical, or other forms of coupling.

[0106] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0107] In summary, in the solution provided by this application embodiment, if the middleware receives a target data request sent by the upper-layer application, it determines whether the first cache of the middleware contains target data corresponding to the target data request. The target data request is used to request target data from its corresponding lower-layer application. If it is determined that the first cache contains target data, the target data is fed back to the upper-layer application. The target data in the first cache is historical data requested from the lower-layer application based on historical data requests, by calling the set interface function corresponding to the lower-layer application. The historical data request and the target data request are data requests of the same type. In other words, this application sets up middleware between the upper-layer application and the lower-layer application. The middleware can cache the application data requested from the lower-layer application in its first cache area. When it receives a target data request sent by the upper-layer application, the middleware first determines whether the target data corresponding to the target data request is cached in its first cache area. If the target data is cached in its first cache area, the middleware directly feeds back the target data from the first cache area to the upper-layer application, thereby avoiding repeated requests for data from the same lower-layer application, reducing the consumption of redundant resources, and thus improving the timeliness of request feedback between the upper-layer application and the lower-layer application.

[0108] Please refer to Figure 8 , Figure 8 The diagram shows a structural block diagram of a vehicle 600 provided in an embodiment of this application. The above-described method provided in this embodiment of the application can be executed by the vehicle 600.

[0109] The vehicle 600 in this embodiment may include one or more of the following components: processor 601, memory 602, and one or more application programs, wherein the one or more application programs may be stored in memory 602 and configured to be executed by one or more processors 601, and the one or more programs are configured to perform the methods as described in the foregoing method embodiments.

[0110] Processor 601 may include one or more processing cores. Processor 601 connects to various parts within the vehicle 600 using various interfaces and lines, and performs various functions and processes data of the vehicle 600 by running or executing instructions, programs, code sets, or instruction sets stored in memory 602, and by calling data stored in memory 602. Optionally, processor 601 may be implemented using at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). Processor 601 may integrate one or more of the following: Central Processing Unit (CPU), Graphics Processing Unit (GPU), and modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the displayed content; and the modem handles wireless communication. It is understood that the aforementioned modem can also be integrated into processor 601 and implemented using a separate communication chip.

[0111] The memory 602 may include random access memory (RAM) or read-only memory (ROM). The memory 602 can be used to store instructions, programs, code, code sets, or instruction sets. The memory 602 may include a program storage area and a data storage area. The program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as touch functionality, sound playback functionality, image playback functionality, etc.), and instructions for implementing the various method embodiments described below. The data storage area may also store data created by the vehicle 600 during use (such as the various correspondences described above).

[0112] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the above-described device and module can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0113] In the several embodiments provided in this application, the coupling or direct coupling or communication connection between the modules shown or discussed may be an indirect coupling or communication connection through some interface, device or module, and may be electrical, mechanical or other forms.

[0114] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0115] Please refer to Figure 9 , Figure 9 A structural block diagram of a computer-readable storage medium 700 provided in an embodiment of this application is shown. The computer-readable storage medium 700 stores program code 710, which can be called by a processor to execute the methods described in the above method embodiments.

[0116] The computer-readable storage medium 700 may be an electronic memory such as flash memory, EEPROM (Electrically Erasable Programmable Read-Only Memory), EPROM, hard disk, or ROM. Optionally, the computer-readable storage medium 700 includes a non-transitory computer-readable storage medium. The computer-readable storage medium 700 has storage space for program code 710 that performs any of the method steps described above. This program code can be read from or written to one or more computer program products. The program code 710 may be compressed, for example, in a suitable form.

[0117] In some embodiments, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform the steps in the above-described method embodiments.

[0118] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A middleware-based data transmission method, characterized in that, The method includes: If the middleware receives a target data request sent by the upper-layer application, it determines whether the first cache of the middleware contains target data corresponding to the target data request. The target data request is used to request the target data from its corresponding lower-layer application. If it is determined that the target data is cached in the first cache area, the target data is fed back to the upper-layer application. The target data in the first cache area is historical data requested from the lower-layer application by calling the set interface function corresponding to the lower-layer application based on historical data requests. The historical data request and the target data request are data requests of the same type.

2. The method according to claim 1, characterized in that, The step of feeding back the target data to the upper-layer application if it is determined that the target data is cached in the first cache area includes: If it is determined that the target data is cached in the first cache area, and the target data is determined to be application data requested within the current data update cycle of the lower layer application, then the target data is fed back to the upper layer application, where the current data update cycle is the data update cycle at the current moment; If it is determined that the target data is cached in the first cache area, and it is determined that the target data is application data requested within the historical data update cycle of the lower-level application, then the updated application data is requested from the lower-level application by calling the set interface function corresponding to the lower-level application. The historical data update cycle is any data update cycle before the current data update cycle. The updated application data is fed back to the upper-layer application, and the target data in the first cache is replaced with the updated application data.

3. The method according to claim 1, characterized in that, After determining whether the middleware's first cache contains target data corresponding to the target data request if the middleware receives a target data request from an upper-layer application, the method further includes: If it is determined that the target data is not cached in the first cache area, the target data is requested from the lower-level application by calling the set interface function corresponding to the lower-level application. The target data is fed back to the upper-layer application, and the target data is cached in the first cache area.

4. The method according to claim 3, characterized in that, The number of target data requests is multiple, the number of upper-layer applications is multiple, the multiple target data requests correspond one-to-one with the multiple upper-layer applications, and the multiple target data requests are data requests for the same lower-layer application. If it is determined that the target data is not cached in the first cache area, then the target data is requested from the lower-level application by calling the set interface function corresponding to the lower-level application, including: If it is determined that the target data is not cached in the first cache area, then the set interface function corresponding to the lower-level application corresponding to any of the target data requests is called to request the target data from the lower-level application; The step of feeding the target data back to the upper-layer application includes: The target data is fed back to each of the upper-layer applications.

5. The method according to claim 3, characterized in that, The target data request is a periodic data request. If it is determined that the target data is not cached in the first cache, the target data is requested from the lower-level application by calling the set interface function corresponding to the lower-level application, including: If it is determined that the target data is not cached in the first cache area, then based on the request period corresponding to the target data request, the set interface function corresponding to the lower-level application is called to request the target data from the lower-level application.

6. The method according to claim 5, characterized in that, The step of calling a defined interface function corresponding to the lower-level application based on the request period corresponding to the target data request to request the target data from the lower-level application includes: If the request period corresponding to the target data request is less than the data update period of the lower-level application, then the request response period corresponding to the target data request is adjusted to the target request response period, and the target request response period matches the data update period of the lower-level application. Based on the target request response cycle, the set interface function corresponding to the lower-level application is called to request the target data from the lower-level application.

7. The method according to claim 5, characterized in that, The number of target data requests is multiple, the number of upper-layer applications is multiple, the multiple target data requests correspond one-to-one with the multiple upper-layer applications, and the multiple target data requests are periodic data requests received by the middleware at the same time. The step of calling a defined interface function corresponding to the lower-level application based on the request period corresponding to the target data request to request the target data from the lower-level application includes: If multiple target data requests contain multiple first data requests with the same request period, and the multiple first data requests are data requests for different lower-level applications, then the request response time of each first data request is adjusted, and the request response times of different first data requests are different after the adjustment. Based on the adjusted request response time for each first data request, the defined interface function of the lower-level application corresponding to each first data request is called to request the first data corresponding to each first data request from the lower-level application corresponding to each first data request.

8. A middleware-based data transmission device, characterized in that, The device includes: The target data determination module is used to determine whether the first cache of the middleware contains target data corresponding to the target data request if the middleware receives a target data request sent by the upper layer application. The target data request is used to request the target data from its corresponding lower layer application. The feedback module is used to feed back the target data to the upper-layer application if it is determined that the target data is cached in the first cache area. The target data in the first cache area is historical data requested from the lower-layer application by calling a set interface function corresponding to the lower-layer application based on historical data requests. The historical data request and the target data request are data requests of the same type.

9. A vehicle, characterized in that, The vehicles include: One or more processors; Memory; One or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs being configured to perform the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores program code that can be invoked by a processor to perform the method as described in any one of claims 1 to 7.

Images