Vehicle end data subscription method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention provides a vehicle end data subscription method and device, electronic equipment and a storage medium, and the method comprises the steps: transmitting a vehicle end collection task of a data subscription request to each target vehicle end according to the data subscription request of a subscription end; obtaining each vehicle end data packet of each target vehicle end corresponding to the vehicle end acquisition task, and based on the data subscription request, recombining each vehicle end acquisition signal in each vehicle end data packet to obtain a subscription data packet of the data subscription request; and sending the subscription data packet to a subscription end. Therefore, according to the invention, repeated acquisition and transmission of the same signal can be avoided, so that the data transmission flow is reduced, and the system computing power is reduced.

Description

TECHNICAL FIELD

[0001] Embodiments of the present disclosure relate to the technical field of communication, and particularly relate to a vehicle-end data subscription method and device, electronic equipment and storage medium. BACKGROUND

[0002] A vehicle is a very complex terminal, and has very many signals, wherein, the same signal can be applicable to multiple different services, the same service needs to collect multiple different signals, and different signals play a very important role in different services. The relationship between different signals and different services is complex.

[0003] In the prior art, each service performs independent data collection according to respective data collection requirements, however, since the vehicle end (collection end) does not know the specific purpose of each collection data (signal), it can only perform corresponding data collection according to each issued vehicle-end collection task, and this processing mechanism is prone to repeated collection of the same signal and repeated transmission of the same data, which not only wastes system computing power but also wastes network traffic, and lacks effective data management and processing, resulting in low vehicle-end data subscription processing efficiency. SUMMARY

[0004] Therefore, embodiments of the present disclosure provide a vehicle-end data subscription method and device, electronic equipment and storage medium to at least partially solve the above problems.

[0005] According to a first aspect of embodiments of the present disclosure, a vehicle-end data subscription method is provided, applied to a cloud end, and the method comprises: issuing a vehicle-end collection task of a data subscription request to each target vehicle end according to the data subscription request of a subscription end; obtaining each vehicle-end data packet corresponding to the vehicle-end collection task of each target vehicle end, reorganizing each vehicle-end collection signal in each vehicle-end data packet based on the data subscription request to obtain a subscription data packet of the data subscription request; and sending the subscription data packet to the subscription end.

[0006] According to a second aspect of embodiments of the present disclosure, a vehicle-end data subscription device is provided, applied to a cloud end, and the device comprises: a task issuing module, configured to issue a vehicle-end collection task of a data subscription request to each target vehicle end according to the data subscription request of a subscription end; a data processing module, configured to obtain each vehicle-end data packet corresponding to the vehicle-end collection task of each target vehicle end, reorganize each vehicle-end collection signal in each vehicle-end data packet based on the data subscription request to obtain a subscription data packet of the data subscription request; and a data distribution module, configured to send the subscription data packet to the subscription end.

[0007] According to a third aspect of the embodiments of the present disclosure, an electronic device is provided, comprising: a processor; and a memory storing a program, wherein the program comprises instructions which, when executed by the processor, cause the processor to perform the method of the first aspect.

[0008] According to a fourth aspect of the embodiments of the present disclosure, a non-transitory computer-readable storage medium storing computer instructions is provided, wherein the computer instructions are used to cause the computer to perform the method of the first aspect.

[0009] To sum up, the vehicle-end data subscription scheme provided by the aspects of the present disclosure is based on a data subscription request of a subscription end, and corresponding vehicle-end collection tasks are issued to the vehicle end. Based on the data subscription request, data reorganization is performed on the vehicle-end data packets uploaded by the vehicle end, and the subscription data packets meeting the data subscription request are obtained and fed back to the subscription end. By means of the technical scheme of the present disclosure, repeated collection and repeated transmission of the same vehicle-end data can be avoided, so as to reduce network transmission flow and system computing power. BRIEF DESCRIPTION OF DRAWINGS

[0010] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the prior art, the drawings needed to be used in the embodiments or prior art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments described in the present disclosure, and other drawings can also be obtained by those skilled in the art based on these drawings.

[0011] Figure 1 The system architecture of the vehicle-end data subscription method or device suitable for implementing the embodiments of the present disclosure.

[0012] Figure 2 The processing flow of the vehicle-end data subscription method of the exemplary embodiments of the present disclosure.

[0013] Figure 3 The processing flow of the vehicle-end data subscription method of another exemplary embodiment of the present disclosure.

[0014] Figure 4 The structural diagram of the vehicle-end data subscription device of the exemplary embodiments of the present disclosure.

[0015] Figure 5 The structural diagram of the electronic device of the exemplary embodiments of the present disclosure. DETAILED DESCRIPTION

[0016] To enable those skilled in the art to better understand the technical solutions in the embodiments of this disclosure, the technical solutions in the embodiments of this disclosure will be clearly and thoroughly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art should fall within the protection scope of this disclosure.

[0017] The specific implementation of the embodiments of this disclosure will be further described below with reference to the accompanying drawings.

[0018] Figure 1 The system architecture 100 is suitable for implementing the vehicle-side data subscription method or apparatus of the various embodiments of this disclosure. As shown in the figure, the system architecture 100 mainly includes a cloud 102, at least one subscription terminal 104 (e.g., subscription terminal A, subscription terminal B, subscription terminal C, etc.) and at least one vehicle terminal 106 (e.g., vehicle terminal A, vehicle terminal B, vehicle terminal C, etc.) that are communicatively connected to the cloud.

[0019] The cloud 102 is used for storing information, data, programs, and / or any other suitable type of content, including but not limited to distributed storage system devices, server clusters, computing cloud server clusters, etc. In some embodiments, the cloud 102 can perform any suitable function. For example, in some embodiments, the cloud 102 can obtain each data subscription request from each subscriber 104 and generate corresponding vehicle-side data collection tasks. The cloud 102 can issue vehicle-side data collection tasks to each vehicle 106, obtain each vehicle-side data packet corresponding to the vehicle-side data collection task from each vehicle 106, and, based on the relevant subscription requirements in the data subscription request, reassemble the data packets of each vehicle-side data packet and feed them back to each subscriber 104 (e.g., the business party).

[0020] Based on the above system architecture 100, various embodiments of this disclosure provide a vehicle-side data subscription method, which will be described below through multiple embodiments.

[0021] Figure 2 The processing flow of the vehicle-side data subscription method, which is an exemplary embodiment of this disclosure, mainly includes the following steps:

[0022] Step 202: Based on the data subscription request from the subscriber, send the data subscription request vehicle-side data collection task to each target vehicle.

[0023] In some embodiments, the data subscription request on the subscription side includes a vehicle model baseline and at least one data subscription topic.

[0024] In some embodiments, a vehicle signal model can be generated based on the baseline of each vehicle model corresponding to each candidate vehicle terminal, the configuration information of each vehicle terminal, and the types of vehicle terminal signals that each candidate vehicle terminal can collect; any vehicle terminal monitoring event can be bound and associated with at least one vehicle terminal signal type in the vehicle signal model to generate a data subscription topic corresponding to any vehicle terminal monitoring event.

[0025] In some embodiments, the acquisition rules for each vehicle-side signal category corresponding to each vehicle-side monitoring event can be defined, such as periodic acquisition (acquiring a signal once per second) or full acquisition (acquiring whenever a signal is generated).

[0026] For example, a vehicle signal model can be constructed based on the vehicle configuration information, vehicle baseline information, and types of vehicle-end signals that can be collected from each vehicle. The vehicle configuration information in the vehicle signal model may include the deployment status of the domain controllers (ECUs) of each vehicle, the deployment status of CAN / LIN, the communication status of each ECU, service deployment status, and software version status. The signals collected from each vehicle may include, but are not limited to, CAN / LIN signals, service signals, DDS signals, embedded signal signals, and signals from cameras, radar waves, etc. The corresponding vehicle-end signal category can be determined based on different collected vehicle-end signals.

[0027] In this embodiment, the cloud can manage the collectable vehicle signals based on the vehicle baseline information of the vehicle terminal. For example, when the cloud detects that the vehicle terminal is online (i.e., the vehicle terminal has established a communication connection with the cloud), it can determine the vehicle baseline information of the vehicle terminal based on the vehicle identification information (e.g., VIN code) uploaded by the vehicle terminal, and determine the various vehicle signals that the vehicle terminal needs to collect based on the vehicle baseline information.

[0028] In some embodiments, the cloud 102 can perform data cleaning on the vehicle configuration information of the vehicle and fill the cleaned vehicle configuration information into each data block in the vehicle signal model according to the vehicle model baseline of the vehicle terminal 106.

[0029] In some embodiments, vehicle-side monitoring events may include, but are not limited to: vehicle emergency braking events, vehicle lateral manual intervention events, vehicle lane change events, vehicle collision events, etc.

[0030] For example, when the vehicle-side monitoring event is a vehicle emergency braking event, the vehicle-side monitoring event can be bound and associated with the vehicle-side brake pad control signal, brake light control signal, etc., to generate a data subscription topic for the vehicle emergency braking event; when the vehicle-side monitoring event is a vehicle collision event, the vehicle-side monitoring event can be bound and associated with the vehicle-side camera signal, vehicle speed signal, brake pad signal, etc., to generate a data subscription topic for the vehicle collision event.

[0031] For example, subscriber 104 can select one or more data subscription topics according to actual subscription needs, and generate a corresponding data subscription request for the subscriber. For example,

[0032] In some embodiments, the vehicle model baseline and each data subscription topic of the data subscription request can be parsed to determine each vehicle-end signal category associated with each data subscription topic. Based on the vehicle model baseline and each vehicle-end signal category of the data subscription request, each target vehicle end that meets the data subscription request can be selected from each candidate vehicle end of the vehicle signal model. Each vehicle end acquisition task corresponding to each target vehicle end 106 can be generated and the corresponding vehicle end acquisition task can be sent to each target vehicle end 106.

[0033] In some embodiments, the various vehicle-side signal categories associated with each data subscription topic can be merged, and vehicle-side data collection task scripts corresponding to each vehicle-side baseline can be generated based on different vehicle-side baselines. When a communication connection is established between the target vehicle-side 106 and the cloud 102, the corresponding vehicle-side data collection task script can be sent to the target vehicle-side 106 based on the vehicle-side baseline of the target vehicle-side 106.

[0034] Step 204: Obtain the vehicle data packets corresponding to the vehicle acquisition task for each target vehicle terminal. Based on the data subscription request, reassemble the vehicle acquisition signals in each vehicle data packet to obtain the subscription data packet of the data subscription request.

[0035] In some embodiments, the vehicle-side can distribute the acquisition instructions and rules from the vehicle-side acquisition task script to different acquisition control devices (e.g., speed detectors, cameras, etc.) within the vehicle. Each acquisition control device determines the triggering conditions for the data acquisition operation (i.e., under what circumstances to execute the data acquisition instruction) based on the received acquisition instructions and rules. Simultaneously, it can identify specific vehicle-side monitoring events based on the acquisition instructions. Examples include sudden braking, manual intervention during lateral movement, and lane changes. Once a corresponding vehicle-side monitoring event is identified, the respective vehicle-side acquisition signals corresponding to that event are acquired by each acquisition control device.

[0036] In some embodiments, the vehicle-side signal acquisition device may, by default, acquire data based on the maximum signal traceability time, but without performing data processing, only caching. When the vehicle-side signal acquisition device acquires signals exceeding the maximum traceability time, the acquired signal data is discarded to save vehicle-side data storage space.

[0037] In some embodiments, when multiple vehicle-side monitoring events are triggered simultaneously, the same vehicle-side signal acquisition device will merge and maximize the acquisition (i.e., maximize the acquisition time span), but only acquire the data once.

[0038] In some embodiments, each vehicle-end acquisition signal in each vehicle-end data packet has a corresponding acquisition timestamp.

[0039] Specifically, the timestamps of the acquisition signals of each vehicle terminal in each vehicle terminal data packet can be synchronized and calibrated. Based on a given duration, the acquisition signals of each vehicle terminal under the same vehicle terminal signal category can be fused to obtain the vehicle terminal fused signals corresponding to each vehicle terminal signal category. Based on the vehicle terminal signals bound and associated with each data subscription topic in the data subscription request, the vehicle terminal fused signals can be reassembled to obtain the subscription data packet corresponding to the data subscription request.

[0040] Step 206: Send the subscription data packet to the subscriber.

[0041] Specifically, a data subscription package that satisfies the data subscription request can be sent to the subscriber based on the subscriber's data subscription request.

[0042] In summary, the vehicle-side data subscription method of this embodiment sends a corresponding vehicle-side data collection task to the vehicle based on the data subscription request from the subscriber, and performs data reassembly on the vehicle-side data packets uploaded by the vehicle based on the data subscription request to obtain a subscription data packet that satisfies the data subscription request and feeds it back to the subscriber. By using the technical solution of this disclosure, duplicate collection and transmission of the same vehicle-side data can be avoided, thereby reducing network traffic and system computing power.

[0043] Figure 3 This embodiment describes the processing flow of a vehicle-side data subscription method as another exemplary embodiment of the present disclosure. This embodiment illustrates the specific implementation means of reassembling the vehicle-side acquisition signals in each vehicle-side data packet in step 204 above. As shown in the figure, this embodiment mainly includes the following steps:

[0044] Step 302: Identify the vehicle-end signal category corresponding to each vehicle-end acquired signal in each vehicle-end data packet, and determine the domain controller corresponding to each vehicle-end acquired signal based on the domain controller corresponding to each vehicle-end signal category in the vehicle signal model.

[0045] Specifically, different domain controllers (ECUs) are usually deployed in the vehicle. Different acquisition and control devices in the vehicle may be controlled by different domain controllers. There may be time differences between different domain controllers. In order to ensure the accuracy of the data analysis results of subsequent vehicle monitoring events, it is necessary to synchronize and calibrate the acquisition timestamps of each vehicle acquisition signal for different vehicle signal categories.

[0046] Step 304: Based on the domain controllers corresponding to the signals collected by each vehicle, perform synchronous calibration on the timestamps corresponding to the signals collected by each vehicle to obtain the calibration timestamps corresponding to the signals collected by each vehicle.

[0047] Specifically, the time deviation values ​​of each domain controller relative to the reference calibration time can be determined. Based on the domain controllers corresponding to each vehicle-end acquired signal and the time deviation values ​​of each domain controller relative to the reference calibration time, synchronous calibration is performed on each acquisition timestamp corresponding to each vehicle-end acquired signal to obtain each calibration timestamp corresponding to each vehicle-end acquired signal.

[0048] Step 306: Based on the given duration and the calibration timestamps corresponding to the signals collected by each vehicle, perform fusion processing on the signals collected by each vehicle under the same vehicle signal category to obtain the fused signals of each vehicle signal category.

[0049] In some embodiments, any vehicle-side signal category can be determined as the current signal category, and each vehicle-side acquired signal corresponding to the current signal category can be determined as the current acquired signal; time period fusion can be performed on each calibration timestamp corresponding to each current acquired signal according to a given duration to obtain each fused time period of the current acquired signal; and based on each calibration timestamp in each fused time period, each current acquired signal can be fused to obtain the vehicle-side fused signal corresponding to each fused time period for the current signal category.

[0050] Considering factors such as network jitter, a dynamic time window can be set, and the signal data of each currently acquired signal can be fused according to each fusion period based on the calibration timestamp corresponding to each currently acquired signal.

[0051] In some embodiments, the currently acquired signals can be arranged sequentially according to each calibration timestamp to obtain a vehicle-side acquired signal sequence; based on the number of timestamps of all calibration timestamps in any fusion period, the number of signals of each currently acquired signal covered by the sliding window and the sliding step size of the sliding window are determined.

[0052] In this embodiment, the duration of each fusion period of the currently acquired signal should be equal, that is, the number of timestamps of all calibration timestamps contained in each fusion period should be equal. For example, if the fusion period contains 10 calibration timestamps, the number of signals of each currently acquired signal covered by the sliding window should also be 10, and the sliding step size of the sliding window each time is also 10 currently acquired signals.

[0053] A sliding window can be used to repeatedly perform sliding processing that satisfies the sliding step size on each currently acquired signal in the vehicle-end acquired signal sequence, so as to obtain the vehicle-end fused signal corresponding to each fusion time period for the current signal category.

[0054] Step 308: Based on the vehicle-end signals that are bound and associated with each data subscription topic in the data subscription request, reassemble the vehicle-end fused signals to obtain the subscription data packet corresponding to the data subscription request.

[0055] Specifically, based on the subscription topics included in the data subscription request, vehicle-mounted signal acquisition signals of different vehicle-mounted signal categories can be fused and recombined to obtain subscription data packets corresponding to the data subscription request.

[0056] In summary, the embodiments of this disclosure achieve signal alignment by collecting signals from vehicles belonging to different domain controllers, thereby resolving time differences between different ECUs within the vehicle and improving the accuracy of the subscription end's analysis results for vehicle-side monitoring events.

[0057] Figure 4 The vehicle-mounted data subscription device 400, which is an exemplary embodiment of this disclosure, is applied to the cloud and includes a task assignment module 402, a data processing module 404, and a data distribution module 406.

[0058] The task distribution module 402 is used to distribute the data subscription request of the data terminal to each target vehicle terminal according to the data subscription request of the subscription terminal;

[0059] Data processing module 404 is used to acquire each vehicle terminal data packet corresponding to the vehicle terminal acquisition task of each target vehicle terminal, and reassemble each vehicle terminal acquisition signal in each vehicle terminal data packet based on the data subscription request to obtain the subscription data packet of the data subscription request.

[0060] The data distribution module 406 is used to send the subscription data packet to the subscriber.

[0061] In some embodiments, the data subscription request from the subscriber includes a vehicle model baseline and at least one data subscription topic.

[0062] In some embodiments, the task distribution module 402 is further configured to: generate a vehicle signal model based on the baseline of each vehicle model corresponding to each candidate vehicle terminal, the configuration information of each vehicle terminal, and the types of vehicle terminal signals that each candidate vehicle terminal can collect; and bind any vehicle terminal monitoring event to at least one vehicle terminal signal type in the vehicle signal model to generate a data subscription topic corresponding to the any one vehicle terminal monitoring event.

[0063] In some embodiments, the task distribution module 402 is further configured to: parse the vehicle model baseline and each data subscription topic of the data subscription request, and determine each vehicle terminal signal category associated with and bound to each data subscription topic; based on the vehicle model baseline and each vehicle terminal signal category, select each target vehicle terminal that meets the data subscription request from each candidate vehicle terminal of the vehicle signal model, generate each vehicle terminal acquisition task corresponding to each target vehicle terminal; and distribute the corresponding vehicle terminal acquisition task to each target vehicle terminal.

[0064] In some embodiments, each vehicle-end acquisition signal in each vehicle-end data packet has a corresponding acquisition timestamp.

[0065] In some embodiments, the data processing module 404 is further configured to: synchronize and calibrate the timestamps of the acquisition signals of each vehicle-end data packet in each vehicle-end data packet, and perform fusion processing on the vehicle-end acquisition signals of the same vehicle-end signal category based on a given duration to obtain the vehicle-end fused signals corresponding to each vehicle-end signal category; and reassemble the vehicle-end fused signals based on the vehicle-end signals bound and associated with each data subscription topic in the data subscription request to obtain the subscription data packet corresponding to the data subscription request.

[0066] In some embodiments, the vehicle signal model further identifies each domain controller corresponding to each vehicle-end signal category. The data processing module 404 is further configured to: identify each vehicle-end signal category corresponding to each vehicle-end acquired signal in each vehicle-end data packet; determine each domain controller corresponding to each vehicle-end acquired signal based on each domain controller corresponding to each vehicle-end signal category in the vehicle signal model; perform synchronization calibration on each acquisition timestamp corresponding to each vehicle-end acquired signal based on each domain controller corresponding to each vehicle-end acquired signal to obtain each calibration timestamp corresponding to each vehicle-end acquired signal; and perform fusion processing on each vehicle-end acquired signal under the same vehicle-end signal category based on a given duration and each calibration timestamp corresponding to each vehicle-end acquired signal to obtain each vehicle-end fused signal corresponding to each vehicle-end signal category.

[0067] In some embodiments, the data processing module 404 is further configured to: determine any vehicle-end signal category as the current signal category, determine each vehicle-end acquisition signal corresponding to the current signal category as the current acquisition signal; perform time period fusion on each calibration timestamp corresponding to each current acquisition signal according to the given duration to obtain each fused time period of the current acquisition signal; and perform fusion processing on each current acquisition signal based on each calibration timestamp in each fused time period to obtain the vehicle-end fused signal corresponding to each fused time period for the current signal category.

[0068] In some embodiments, the data processing module 404 is further configured to: arrange each currently acquired signal in sequence according to each calibration timestamp to obtain a vehicle-end acquired signal sequence; determine the number of signals of each currently acquired signal covered by the sliding window and the sliding step size of the sliding window based on the number of timestamps of all calibration timestamps in any fusion period; and repeatedly perform sliding processing that satisfies the sliding step size on each currently acquired signal of the vehicle-end acquired signal sequence using the sliding window to obtain the vehicle-end fused signal corresponding to each fusion period for the current signal category.

[0069] Reference Figure 5 This document illustrates a schematic diagram of an electronic device according to an exemplary embodiment of the present application. Specific embodiments of the present application do not limit the specific implementation of the electronic device.

[0070] like Figure 5As shown, the electronic device may include: a processor 502, a communications interface 504, a memory 506, and a communications bus 508.

[0071] in:

[0072] The processor 502, communication interface 504, and memory 506 communicate with each other via communication bus 508.

[0073] Communication interface 504 is used to communicate with other electronic devices or servers.

[0074] The processor 502 is used to execute program 510, specifically to execute the relevant steps in the above-described vehicle-side data subscription method embodiment.

[0075] Specifically, program 510 may include program code that includes computer operation instructions.

[0076] The processor 502 may be a CPU, an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application. The smart device may include one or more processors of the same type, such as one or more CPUs; or it may include processors of different types, such as one or more CPUs and one or more ASICs.

[0077] Memory 506 is used to store program 510. Memory 506 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0078] Program 510 may include multiple computer instructions. Specifically, program 510 may use multiple computer instructions to cause processor 502 to perform the operation corresponding to the vehicle-side data subscription method described in any of the foregoing multiple method embodiments.

[0079] The specific implementation of each step in program 510 can be found in the corresponding steps and units described in the above method embodiments, and has corresponding beneficial effects, which will not be repeated here. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the devices and modules described above can be referred to the corresponding process descriptions in the foregoing method embodiments, and will not be repeated here.

[0080] This application also provides a computer storage medium storing a computer program thereon, which, when executed by a processor, implements the method described in any of the foregoing method embodiments. The computer storage medium includes, but is not limited to, compact disc read-only memory (CD-ROM), random access memory (RAM), floppy disk, hard disk, or magneto-optical disk.

[0081] This application also provides a computer program product, including computer instructions that instruct a computing device to perform the operation corresponding to the vehicle-side data subscription method described in any of the above embodiments.

[0082] Furthermore, it should be noted that the user-related information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to sample data used for training the model, data used for analysis, stored data, displayed data, etc.) involved in the embodiments of this application are all information and data authorized by the user or fully authorized by all parties. Moreover, the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0083] It should be noted that, depending on the implementation needs, the various components / steps described in the embodiments of this application can be broken down into more components / steps, or two or more components / steps or parts of the operation of components / steps can be combined into new components / steps to achieve the purpose of the embodiments of this application.

[0084] The methods described in the embodiments of this application can be implemented in hardware, firmware, or as software or computer code that can be stored in a recording medium (such as a CD-ROM, RAM, floppy disk, hard disk, or magneto-optical disk), or as computer code downloaded over a network that is originally stored in a remote recording medium or a non-transitory machine-readable medium and will be stored in a local recording medium. Thus, the methods described herein can be stored on a recording medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware (such as an Application Specific Integrated Circuit (ASIC) or a Field Programmable Gate Array (FPGA)). It is understood that the computer, processor, microprocessor controller, or programmable hardware includes storage components (e.g., Random Access Memory (RAM), Read-Only Memory (ROM), Flash Memory, etc.) capable of storing or receiving software or computer code, which, when accessed and executed by the computer, processor, or hardware, implements the methods described herein. Furthermore, when a general-purpose computer accesses code used to implement the methods shown herein, the execution of the code transforms the general-purpose computer into a dedicated computer for executing the methods shown herein.

[0085] Those skilled in the art will recognize that the units and method steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of this application.

[0086] The above embodiments are only used to illustrate the embodiments of this application, and are not intended to limit the embodiments of this application. Those skilled in the art can make various changes and modifications without departing from the spirit and scope of the embodiments of this application. Therefore, all equivalent technical solutions also fall within the scope of the embodiments of this application, and the patent protection scope of the embodiments of this application should be defined by the claims.

Claims

1. A vehicle-end data subscription method applied to a cloud end, the method comprising: issuing a vehicle-end collection task of a data subscription request to each target vehicle end according to the data subscription request of a subscription end; obtaining each vehicle-end data packet corresponding to the vehicle-end collection task of each target vehicle end, reorganizing each vehicle-end collection signal in each vehicle-end data packet based on the data subscription request to obtain a subscription data packet of the data subscription request; and sending the subscription data packet to the subscription end.

2. The method of claim 1, wherein, The data subscription request of the subscription end comprises a vehicle model baseline and at least one data subscription topic; and wherein the at least one data subscription topic is obtained by: generating a vehicle signal model based on each vehicle model baseline corresponding to each candidate vehicle end, each vehicle-end configuration information, and each vehicle-end signal category that can be collected by each candidate vehicle end; binding and associating any one vehicle-end monitoring event with at least one vehicle-end signal category in the vehicle signal model to generate a data subscription topic corresponding to the any one vehicle-end monitoring event.

3. The method of claim 2, wherein, The step of issuing the vehicle-end collection task of the data subscription request to each target vehicle end according to the data subscription request of the subscription end comprises: analyzing the vehicle model baseline and each data subscription topic of the data subscription request and determining each vehicle-end signal category bound and associated with each data subscription topic; selecting each target vehicle end that meets the data subscription request from each candidate vehicle end of the vehicle signal model according to the vehicle model baseline and each vehicle-end signal category to generate each vehicle-end collection task corresponding to each target vehicle end; and issuing each corresponding vehicle-end collection task to each target vehicle end.

4. The method of claim 2 or 3, wherein, Each vehicle-end collection signal in each vehicle-end data packet has a corresponding collection timestamp; The step of reorganizing each vehicle-end collection signal in each vehicle-end data packet based on the data subscription request to obtain a subscription data packet of the data subscription request comprises: synchronously calibrating each collection timestamp of each vehicle-end collection signal in each vehicle-end data packet and fusing each vehicle-end collection signal under the same vehicle-end signal category based on a given time length to obtain each vehicle-end fusion signal corresponding to each vehicle-end signal category; reorganizing each vehicle-end fusion signal based on each vehicle-end signal category bound and associated with each data subscription topic in the data subscription request to obtain a subscription data packet corresponding to the data subscription request.

5. The method of claim 4, wherein, The vehicle signal model further identifies each domain controller corresponding to each vehicle-end signal category; The step of synchronously calibrating each collection timestamp of each vehicle-end collection signal in each vehicle-end data packet and fusing each vehicle-end collection signal under the same vehicle-end signal category based on a given time length to obtain each vehicle-end fusion signal corresponding to each vehicle-end signal category comprises: identifying each vehicle-end signal category corresponding to each vehicle-end collection signal in each vehicle-end data packet and determining each domain controller corresponding to each vehicle-end collection signal according to each domain controller corresponding to each vehicle-end signal category in the vehicle signal model; synchronously calibrating each collection timestamp corresponding to each vehicle-end collection signal based on each domain controller corresponding to each vehicle-end collection signal to obtain each calibration timestamp corresponding to each vehicle-end collection signal; and The fusion processing is performed on each vehicle-end collected signal under the same vehicle-end signal category based on the given time length and the calibration time stamps corresponding to the vehicle-end collected signals, to obtain each vehicle-end fusion signal corresponding to each vehicle-end signal category.

6. The method of claim 5, wherein, The fusion processing is performed on each vehicle-end collected signal under the same vehicle-end signal category based on the given time length and the calibration time stamps corresponding to the vehicle-end collected signals, to obtain each vehicle-end fusion signal corresponding to each vehicle-end signal category. Any one vehicle-end signal category is determined as a current signal category, and each vehicle-end collected signal corresponding to the current signal category is determined as a current collected signal. According to the given time length, time period fusion is performed on the calibration time stamps corresponding to each current collected signal, to obtain each fusion time period of the current collected signal. Based on each calibration time stamp in each fusion time period, the fusion processing is performed on each current collected signal, to obtain a vehicle-end fusion signal corresponding to each fusion time period of the current signal category.

7. The method of claim 6, wherein, Based on each calibration time stamp in each fusion time period, the fusion processing is performed on each current collected signal, to obtain a vehicle-end fusion signal corresponding to each fusion time period of the current signal category. According to the calibration time stamps, each current collected signal is arranged in sequence to obtain a vehicle-end collected signal sequence. Based on the number of time stamps of all calibration time stamps in any one fusion time period, the signal number of each current collected signal covered by a sliding window and the sliding step of the sliding window are determined. The sliding processing satisfying the sliding step is repeatedly performed on each current collected signal of the vehicle-end collected signal sequence by using the sliding window, to obtain a vehicle-end fusion signal corresponding to each fusion time period of the current signal category.

8. A vehicle-end data subscription device applied to a cloud, the device comprising: a task issuing module configured to issue a vehicle-end collection task of a data subscription request to each target vehicle-end according to the data subscription request of a subscription end; a data processing module configured to obtain each vehicle-end data packet corresponding to the vehicle-end collection task of each target vehicle-end, recombine each vehicle-end collected signal in each vehicle-end data packet based on the data subscription request, and obtain a subscription data packet of the data subscription request; a data distribution module configured to send the subscription data packet to the subscription end.

9. An electronic device comprising: a processor; and a memory storing programs, wherein the programs include instructions that, when executed by the processor, cause the processor to perform the method of any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer program is stored in the computer readable storage medium, and when the computer program runs on the computer, the computer executes the method of any one of claims 1-7.

Images