Vehicle-to-cloud communication method, device, storage medium, and vehicle-mounted communication equipment

Abstract

The embodiments of the present application disclose a vehicle-cloud communication method, apparatus, storage medium and vehicle-mounted communication equipment, the method comprising: in response to a call request from the second end to the first end service of the first end, obtaining the first end service interface of the first end service in the first end interface definition language; based on the first end service interface and the preset interface correspondence, converting the first end service interface into the second end service interface in the second end interface definition language; based on the second end service interface, generating a second end service corresponding to the first end service, and calling the second end service, wherein the first end is the cloud and the second end is the vehicle, or the first end is the vehicle and the second end is the cloud. According to the technical solution of the embodiments of the present application, cloud-end services and vehicle-end services can be converted to each other, thereby realizing seamless calling of cloud-end services and vehicle-end services.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a vehicle-to-cloud communication method, device, storage medium and vehicle-mounted communication equipment. Background Art

[0002] With the development of Internet of Vehicles technology, the functions of vehicle systems are becoming more and more abundant. How to interconnect vehicle services with cloud services has become the focus of attention.

[0003] At present, in-vehicle services and cloud services each have their own set of standards, and the standards for vehicle-side services and cloud services are incompatible with each other, resulting in the inability to efficiently call cloud services on the vehicle side.

[0004] Therefore, how to efficiently call cloud services on the vehicle side has become a technical problem that needs to be solved urgently. Summary of the invention

[0005] The embodiments of the present application provide a vehicle-cloud communication method, device, storage medium and vehicle-mounted communication device, which can efficiently call cloud services on the vehicle side. The technical solution is as follows:

[0006] In a first aspect, an embodiment of the present application provides a vehicle-cloud communication method, which is applied to a gateway set in a vehicle end, wherein the gateway stores a preset interface correspondence relationship, wherein the preset interface correspondence relationship is a correspondence relationship between a first end interface in a first end interface definition language and a second end interface in a second end interface definition language, and the method includes:

[0007] In response to a call request of the second end to the first end service of the first end, obtaining a first end service interface of the first end service in the first end interface definition language;

[0008] Based on the first-end service interface and the preset interface correspondence, converting the first-end service interface into a second-end service interface in the second-end interface definition language;

[0009] A second-end service corresponding to the first-end service is generated based on the second-end service interface, and the second-end service is called, wherein the first end is the cloud end and the second end is the vehicle end, or the first end is the vehicle end and the second end is the cloud end.

[0010] In a second aspect, an embodiment of the present application provides a vehicle-cloud communication device, which is applied to a gateway set in a vehicle end, wherein the gateway stores a preset interface correspondence relationship, wherein the preset interface correspondence relationship is a correspondence relationship between a first end interface in a first end interface definition language and a second end interface in a second end interface definition language, and the device includes:

[0011] an interface acquisition module, configured to acquire a first-end service interface of the first-end service in the first-end interface definition language in response to a call request from the second end to the first-end service of the first end;

[0012] An interface conversion module, configured to convert the first-end service interface into a second-end service interface in the second-end interface definition language based on the first-end service interface and the preset interface correspondence;

[0013] The first service calling module is used to generate a second-end service corresponding to the first-end service based on the second-end service interface, and call the second-end service, wherein the first end is the cloud and the second end is the vehicle, or the first end is the vehicle and the second end is the cloud.

[0014] In a third aspect, an embodiment of the present application provides a computer storage medium, wherein the computer storage medium stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the steps of the above-mentioned method.

[0015] In a fourth aspect, an embodiment of the present application provides a vehicle-mounted communication device, comprising: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the steps of the above method.

[0016] The beneficial effects brought about by the technical solutions provided by some embodiments of the present application include at least:

[0017] On the one hand, based on the first-end service interface and the preset interface correspondence, the first-end service interface of the first-end service is converted to the second-end service interface, so that the mutual conversion between the first-end service interface and the second-end service interface can be realized; on the other hand, based on the second-end service interface, the second-end service corresponding to the first-end service is generated, and the second-end service is called. Since the mutual conversion between the first-end service and the second-end service is realized, the service of the second end, such as the cloud, can be efficiently called at the first end, such as the vehicle end, so that the service of the second end can be called at the first end just like calling the first-end service, thereby realizing seamless calling of the cloud service and the vehicle-end service. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0019] Figure 1A schematic diagram showing an application scenario of the vehicle-cloud communication method provided according to an embodiment of the present application;

[0020] Figure 2 A schematic diagram of a vehicle-to-cloud communication method according to some embodiments of the present application is shown;

[0021] Figure 3 A schematic diagram of a process of a vehicle-cloud communication method provided according to other embodiments of the present application is shown;

[0022] Figure 4 A schematic diagram of a process of a vehicle-cloud communication method provided according to some other embodiments of the present application is shown;

[0023] Figure 5 A schematic diagram of a process of calling a vehicle-side service from the cloud side according to some embodiments of the present application is shown;

[0024] Figure 6 A schematic diagram showing a process of calling a cloud service from a vehicle side according to some embodiments of the present application

[0025] Figure 7 A schematic diagram showing the structure of another vehicle-to-cloud communication device provided in an embodiment of the present application is shown

[0026] Figure 8 A schematic structural diagram of a vehicle-mounted communication device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0027] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0028] First, the nouns involved in the embodiments of the present application are explained and illustrated.

[0029] Joynr: is a web-based communication framework for applications and services deployed to vehicles, consumer devices, and cloud servers that need to interact with each other. Joynr helps prevent programming errors related to incompatible interfaces by modeling interfaces using FIDL (Franca Interface description language).

[0030] SOA (Service-Oriented Architecture): It can achieve decoupling between distributed system software modules. Through software upgrades, service entities can be deployed on any domain controller more conveniently and flexibly. Services only need to communicate through simple and precisely defined interfaces.

[0031] CAN bus: The data bus in traditional vehicle architecture can carry a large amount of data and is an ISO internationally standardized serial communication protocol.

[0032] LIN (Local Interconnect Network) bus: A data bus in traditional vehicle architecture, used to implement distributed electronic system control in the car. It can carry a small amount of data and is mainly used to control some simple in-vehicle devices. It is an auxiliary bus network.

[0033] SOMEIP (Scalable service-Oriented MiddlewarE over IP) protocol: is an automotive middleware solution for control messages that enables service-oriented communication between controllers. SOMEIP provides a wide range of middleware functions such as serialization, remote procedure calls, service discovery and subscription to enable ECU (Electronic Control Unit) software to communicate with each other.

[0034] C2C (Car To Cloud) Gateway: is a vehicle-to-cloud communication gateway that enables intercommunication between the vehicle and the cloud.

[0035] ARXML (AUTOSAR eXtensible Markup Language): This standard describes how to serialize AUTOSAR models into AUTOSAR XML descriptions, providing support for interoperability between AUTOSAR tools.

[0036] AUTOSAR (AUTOmotive Open System Architecture) is an alliance dedicated to developing automotive electronic software standards and is committed to developing an open and standardized software architecture for the automotive industry.

[0037] FIDL (Franca Interface Definition Language): is a text language used to standardize interface descriptions.

[0038] Below, the technical solution of the vehicle-to-cloud communication method of the embodiment of the present application will be described in detail with reference to the accompanying drawings.

[0039] Figure 1 A schematic diagram showing an application scenario of the vehicle-to-cloud communication method provided according to an embodiment of the present application.

[0040] Reference Figure 1 As shown, the application scenario includes a cloud 110 and a vehicle 120. Among them, a C2C gateway 122 runs on the vehicle 120. The C2C gateway 122 is interconnected with the cloud 110 based on a communication framework such as the Joynr framework, obtains cloud data, converts cloud data into SOA services of the vehicle 110, provides services of the cloud 120 to the vehicle 110, and converts the SOA services of the vehicle 110 into cloud services.

[0041] It should be noted that the cloud 110 may be a cloud server, such as a server cluster consisting of multiple servers, or a cloud server. The vehicle 110 may be a car, a bus, a truck or other vehicle. The above is only an example, and is not specifically limited in the embodiments of the present application.

[0042] Figure 2 A flow chart of a vehicle-to-cloud communication method provided according to some embodiments of the present application is shown. The execution subject of the vehicle-to-cloud communication method may be a computing device with computing and processing functions, such as a C2C gateway. The vehicle-to-cloud communication method includes steps S210 to S230. The vehicle-to-cloud communication method in the example embodiment is described in detail below in conjunction with the accompanying drawings.

[0043] Reference Figure 2 As shown, in step S210, in response to a call request from the second end to the first end service of the first end, a first end service interface of the first end service in the first end interface definition language is obtained.

[0044] In an exemplary embodiment, the first end is the cloud side and the second end is the vehicle side, or the first end is the vehicle side and the second end is the cloud side. Taking the first end as the cloud side and the second end as the vehicle side as an example, the first end service is a cloud service, and the second end service is an SOA service. In response to the vehicle side's call request to the cloud service on the cloud side, the cloud service interface in the cloud interface definition language of the cloud service is obtained. The cloud interface definition language is a FIDL file, and the FIDL file supports the definition of three types of interfaces: method Method, broadcast Broadcast, and attribute Attribute. In response to the vehicle side's call request to the cloud service on the cloud side, the C2C gateway obtains the interface information of the cloud service interface of the cloud service in the FIDL file.

[0045] For example, assuming that the cloud service is a weather forecast service, the C2C gateway responds to the vehicle's call request for the cloud weather forecast service and obtains the cloud service interface of the weather forecast server in the cloud interface definition language, such as the broadcast interface, which is used to publish the weather status to the vehicle.

[0046] In step S220, based on the first-end service interface and the preset interface correspondence, the first-end service interface is converted into a second-end service interface in a second-end interface definition language.

[0047] In an exemplary embodiment, taking the first end as the cloud and the second end as the vehicle-side as an example, based on the cloud service interface and the preset interface correspondence, the cloud service interface is converted into a vehicle-side service interface in the vehicle-side interface definition language. The gateway stores a preset interface correspondence, which is the correspondence between the cloud interface in the cloud interface definition language and the vehicle-side interface in the vehicle-side interface definition language. Among them, the cloud interface definition language is a FIDL file, and the vehicle-side interface definition language is an ARXML file. FIDL files support the definition of three types of interfaces: Method, Broadcast, and Attribute. These three interfaces correspond to three types of interfaces in ARXML: Method, Event, and Field. The correspondence between the interfaces in ARXML and FIDL can be identified by the following Table 1:

[0048] Table 1. Correspondence between ARXML and FIDL interfaces

[0049]

[0050] Among them, the three types of interfaces in ARXML include Method, Event and Field. Method, or remote procedure call, refers to a node sending a request for service to another node. It is mostly used for the client to send control commands to the server. Depending on whether the server has feedback, it is divided into request / response communication and send and forget Fire&Forget communication. Event is similar to CAN message, which is used to publish status. According to the actual application scenario, there can be different sending methods. Field is used to indicate the status of a service. Control commands can be issued through Method, that is, Setter; you can also request to obtain service status through Method, that is, Getter; notifications can also be sent when the service status changes.

[0051] Furthermore, the C2C gateway determines a vehicle-side service interface of a corresponding type in the vehicle-side interface definition language based on the interface type of the cloud service interface and a preset interface correspondence, and converts the cloud service interface into a vehicle-side service interface of the corresponding type.

[0052] For example, suppose the cloud service is a weather forecast service, and the interface type of the cloud service interface is a broadcast type. Based on the interface type of the cloud service interface and the above-mentioned correspondence table, determine the corresponding type of vehicle-side service interface in the vehicle-side interface definition language, namely, the Event interface, and convert the Broadcast type cloud service interface into the corresponding type of Event interface. For example, convert the data type of the Broadcast type cloud service interface into the data type of the Event interface, and generate the corresponding vehicle-side service interface interface instance, such as an ARXML interface file, so that the data types of the cloud service interface and the vehicle-side service interface can be processed uniformly to avoid data conversion errors.

[0053] In step S230, a second-end service corresponding to the first-end service is generated based on the second-end service interface, and the second-end service is called.

[0054] In an exemplary embodiment, taking the first end as the cloud and the second end as the vehicle end as an example, the first end service is a cloud service, the second end service is an SOA service, and a SOA service corresponding to the cloud service is generated based on the vehicle end service interface, and the SOA service is called. The SOA service is a service deployed on the vehicle end, such as services provided by various vehicle-mounted software, and the parameter data of the cloud service interface corresponding to the cloud service is obtained. Based on the interface parameters of the vehicle end service interface and the data type of the interface parameters, the corresponding data is obtained from the parameter data of the cloud service interface, and the service data of the SOA service corresponding to the cloud service is generated, such as an SOA service in ARXML format, and the service interface of the SOA service is called. For example, the cloud service interface includes an interface ID, an interface parameter, and a parameter type of the interface parameter. The data corresponding to the vehicle end service interface is obtained from the parameter data of the cloud service interface, and the service data of the SOA service corresponding to the cloud service, i.e., an SOA service in ARXML format, is generated, and the service interface of the SOA service is called.

[0055] For example, suppose the cloud service is a weather forecast service. Based on the vehicle-side service interface, the corresponding weather data such as weather condition values ​​and temperature values ​​are obtained from the weather forecast service interface. Based on the obtained weather data and the vehicle-side service interface, a SOA service corresponding to the cloud service, namely the SOA weather forecast service, is generated, and the weather forecast service interface is called.

[0056] according to Figure 2The technical solution in the example embodiment, on the one hand, based on the first-end service interface and the preset interface correspondence, the first-end service interface of the first-end service is converted into the second-end service interface, which can realize the mutual conversion between the first-end service interface and the second-end service interface; on the other hand, based on the second-end service interface, a second-end service corresponding to the first-end service is generated, and the second-end service is called. Since the mutual conversion between the first-end service and the second-end service is realized, the service of the second end, such as the cloud, can be efficiently called at the first end, such as the vehicle end, so that the service of the second end can be called at the first end just like calling the first-end service, thereby realizing seamless calling of the cloud service and the vehicle-end service.

[0057] Figure 3 A flow chart of a vehicle-to-cloud communication method provided according to other embodiments of the present application is shown.

[0058] Reference Figure 3 As shown, in step S310, in response to the cloud's call request to the vehicle-side SOA service, the vehicle-side service interface of the SOA service in the vehicle-side interface definition language is obtained.

[0059] In the example embodiment, the first end is the vehicle end and the second end is the cloud end, and the SOA service is a service deployed on the vehicle end, that is, a service provided by various vehicle-mounted software, such as a voice broadcast service, etc. The vehicle-end interface definition language is an ARXML file. ARXML contains three types of interfaces: Method, Event, and Field. Method, or remote procedure call, refers to a node sending a request for service to another node. It is mostly used for the client to send control commands to the server. Depending on whether the server has feedback, it is divided into request Request / Response communication and send and forget Fire&Forget communication. Event is similar to a CAN message, which is used to publish status. Depending on the actual application scenario, there can be different sending methods. Field is used to represent the state quantity of a service. Control commands can be issued through Method, that is, Setter; you can also request to obtain service status through Method, that is, Getter; notifications can also be sent when the service status changes.

[0060] Furthermore, the C2C gateway responds to the call request of the cloud to the vehicle-side SOA service and obtains the vehicle-side service interface of the SOA service in ARXML. For example, assuming that the SOA service is a vehicle speed acquisition service, the C2C gateway responds to the call request of the cloud to the vehicle-side vehicle speed acquisition service and obtains the vehicle-side server interface of the vehicle speed acquisition service in ARXML, such as a Field interface, which is used to obtain the vehicle speed.

[0061] In step S320, based on the vehicle-side service interface and the preset interface correspondence, the vehicle-side service interface is converted into a cloud-side service interface in a cloud-side interface definition language.

[0062] In an example embodiment, the C2C gateway stores a preset interface correspondence relationship, which is the correspondence between the cloud interface in the cloud interface definition language and the vehicle-side interface in the vehicle-side interface definition language. The cloud interface definition language is a FIDL file, and the vehicle-side interface definition language is an ARXML file. The FIDL file supports the definition of three types of interfaces: Method, Broadcast, and Attribute. These three interfaces correspond to three types of interfaces in ARXML: Method, Event, and Field. The correspondence between the interfaces in ARXML and FIDL can be identified by Table 1 above.

[0063] Furthermore, the C2C gateway determines a cloud service interface of a corresponding type in a cloud interface definition language based on the interface type of the vehicle-side service interface and a preset interface correspondence; and generates an interface instance of the cloud service interface of a corresponding type, such as a FIDL interface instance file.

[0064] For example, suppose the SOA service is a vehicle speed acquisition service, and the interface type of the vehicle-side service interface is a Field type. The C2C gateway determines the corresponding type of cloud service interface in FIDL, namely, the Attribute interface, based on the interface type of the vehicle-side service interface and the above-mentioned preset interface correspondence; and generates an interface instance of the corresponding type of cloud server interface, for example, assigning the vehicle speed value of the Field type vehicle speed acquisition service to the cloud server interface, namely, the Attribute interface.

[0065] In step S330, a cloud service corresponding to the SOA service is generated based on the cloud service interface, and the cloud service is called.

[0066] In an example embodiment, the cloud service is a service provided by the cloud, such as a weather service, an intelligent recommendation service, etc. The C2C gateway stores a client of the SOA service, generates a cloud service corresponding to the SOA service through the cloud service interface and the client of the SOA service; and calls the cloud service corresponding to the SOA service through the client of the SOA service. For example, the parameter data of the vehicle-side service interface corresponding to the SOA service is obtained, and based on the interface parameters of the cloud service interface and the data type of the interface parameters, the corresponding data is obtained from the parameter data of the vehicle-side service interface, the service data of the cloud service corresponding to the SOA service is generated, and the service interface of the cloud service is called.

[0067] For example, suppose the SOA service is a vehicle speed acquisition service. Based on the cloud service interface, the corresponding vehicle speed data, such as the vehicle speed value, is obtained from the vehicle speed acquisition service interface. Based on the obtained vehicle speed value and the cloud service interface, a cloud service corresponding to the vehicle speed acquisition service is generated, such as a vehicle speed acquisition service interface in a FIDL file format, and the cloud service in the FIDL file format is called.

[0068] according to Figure 3 The technical solution in the example embodiment, on the one hand, based on the vehicle-side service interface and the preset interface correspondence, the vehicle-side service interface of the SOA service is converted into a cloud-side service interface, which can realize the mutual conversion between the vehicle-side service interface and the cloud-side service interface; on the other hand, a cloud service corresponding to the SOA service is generated based on the cloud-side service interface, and the cloud service is called. Since the mutual conversion between the vehicle-side service and the cloud-side service is realized, the vehicle-side service can be efficiently called in the cloud, so that the SOA service in the vehicle can be called in the cloud just like calling the cloud service.

[0069] Figure 4 A flow chart of a vehicle-cloud communication method provided according to some further embodiments of the present application is shown.

[0070] The C2C gateway 122 runs on the vehicle side 120. The C2C gateway 122 is interconnected with the cloud side 110 based on a communication framework such as the Joynr framework, obtains cloud data, converts the cloud data into SOA services of the vehicle side 110, provides services of the cloud side 120 to the vehicle side 110, and converts the SOA services of the vehicle side 110 into cloud services.

[0071] The cloud end 110 uses the cloud service definition file FIDL, and the vehicle end 120 uses the SOA service definition file ARXML. Through a communication framework such as the Joynr framework, bidirectional conversion between the cloud service definition file FIDL and the SOA service definition file ARXML is implemented. The C2C gateway 122 automatically generates conversion codes based on the files to convert FIDL files into ARXML files, or convert ARXML files into FIDL files.

[0072] According to the technical solution in the above-mentioned example embodiment, the service definition files FIDL and ARXML are converted to each other through the C2C gateway, so that the cloud service and the vehicle-side service can be converted to each other, thereby making the cloud and the vehicle-side seamlessly connected, and supporting the in-vehicle service and the cloud service with seamless calling.

[0073] Figure 5 A schematic diagram of the process of cloud-based calling of vehicle-side services provided according to some embodiments of the present application is shown.

[0074] Reference Figure 5As shown, the C2C gateway 122 generates a cloud FIDL file based on the ARXML content of the SOA service, that is, converts the ARXML file of the SOA service into a corresponding FIDL file, i.e., a cloud service file corresponding to the SOA service, according to the correspondence between the ARXML and FIDL files. The C2C gateway 122 stores the cloud service files corresponding to the SOA client 124 and the SOA service for other cloud programs to call, and connect the SOA client 124 and the cloud service files through the C2C gateway 122.

[0075] According to the technical solution in the above-mentioned example embodiment, the ARXML file of the SOA service is converted into the cloud service file corresponding to the SOA service according to the correspondence between the ARXML and FIDL files. The cloud service file corresponding to the SOA service is saved by the C2C gateway, thereby realizing seamless connection and senseless calling of cloud services and vehicle-side services. In addition, the existing vehicle-mounted SOA or cloud services do not need to be significantly modified and can be deployed quickly, which can more conveniently accelerate the deployment of vehicle-cloud interconnection.

[0076] Figure 6 A schematic diagram of a process of a vehicle-side calling a cloud service according to some embodiments of the present application is shown.

[0077] Reference Figure 6 As shown, the cloud service provides the FIDL file of the cloud service, and the FIDL file of the cloud service is converted into an ARXML file in the C2C gateway 122. The cloud client 126 of the cloud service is stored in the C2C gateway 122, and the SOA service corresponding to the cloud service, that is, the ARXML file of the SOA service, is generated to provide the cloud service to other programs on the vehicle side. The C2C gateway 122 serves as a gateway between the vehicle side 120 and the cloud side 110, and is responsible for converting the services of the cloud side 110 / vehicle side 120 to each other.

[0078] Furthermore, in the example embodiment, the gateway stores a cloud client 126 on the cloud side, generates a vehicle-side SOA service corresponding to the cloud service through the vehicle-side service interface and the cloud client 126; and calls the SOA service corresponding to the cloud service through the cloud client 126 on the cloud side.

[0079] According to the technical solution in the above example embodiment, the car-to-cloud gateway 122 based on the Joynr framework is responsible for converting cloud-side / car-side services to each other. In the car, cloud services can be called just like calling in-car SOA services. Unified service conversion is done in the C2C gateway to realize the interconnection of cloud-side and car-side services.

[0080] The following are device embodiments of the present application, which can be used to execute the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

[0081] Figure 7A schematic structural diagram of a vehicle-to-cloud communication device provided by an exemplary embodiment of the present application is shown.

[0082] Reference Figure 7 As shown, the vehicle-to-cloud communication device 700 can be implemented as all or part of the device through software, hardware or a combination of both. The vehicle-to-cloud communication device 700 is applied to a gateway set in the vehicle end, and the gateway stores a preset interface correspondence relationship, which is the correspondence between the first end interface in the first end interface definition language and the second end interface in the second end interface definition language. The vehicle-to-cloud communication device 700 includes an interface acquisition module 710, an interface conversion module 720 and a service call module 730. Among them:

[0083] An interface acquisition module 710, configured to acquire a first-end service interface of the first-end service in the first-end interface definition language in response to a call request from the second end to the first-end service of the first end;

[0084] An interface conversion module 720, configured to convert the first-end service interface into a second-end service interface in the second-end interface definition language based on the first-end service interface and the preset interface correspondence relationship;

[0085] The service calling module 730 is used to generate a second-end service corresponding to the first-end service based on the second-end service interface, and call the second-end service, wherein the first end is the cloud and the second end is the vehicle, or the first end is the vehicle and the second end is the cloud.

[0086] In some example embodiments, based on the above solution, the first end is a cloud end and the second end is a vehicle end, and the interface conversion module 720 is configured as follows:

[0087] Based on the interface type of the cloud service interface and the preset interface correspondence, a vehicle-side service interface of a corresponding type in the vehicle-side interface definition language is determined.

[0088] In some example embodiments, based on the above solution, the first end is a cloud end and the second end is a vehicle end, the first end service is a cloud service, the second end service is a service-oriented architecture SOA service, the gateway stores a cloud client on the cloud end, and the service calling module 730 is configured as follows:

[0089] Generate the SOA service of the vehicle side corresponding to the cloud service through the vehicle side service interface and the client;

[0090] The SOA service corresponding to the cloud service is called through the client.

[0091] In some example embodiments, based on the above solution, the first end is a vehicle end and the second end is a cloud end, the first end service is a SOA service, and the second end service is a cloud service.

[0092] In some example embodiments, based on the above solution, the interface conversion module 720 is configured to:

[0093] Based on the interface type of the vehicle-side service interface and the preset interface correspondence, a cloud service interface of a corresponding type in the cloud interface definition language is determined.

[0094] In some example embodiments, based on the above solution, the gateway stores the client of the SOA service, and the service calling module 730 is configured as follows:

[0095] Generate a cloud service corresponding to the SOA service through the cloud service interface and the client of the SOA service;

[0096] The cloud service corresponding to the SOA service is called through the client of the SOA service.

[0097] In some example embodiments, based on the above solution, the cloud-side interface definition language is the Franca interface definition language FIDL, and the vehicle-side interface definition language is the Automotive Open System Architecture Extensible Markup Language ARXML.

[0098] according to Figure 7 The technical solution in the example embodiment, on the one hand, based on the first-end service interface and the preset interface correspondence, the first-end service interface of the first-end service is converted into the second-end service interface, which can realize the mutual conversion between the first-end service interface and the second-end service interface; on the other hand, based on the second-end service interface, a second-end service corresponding to the first-end service is generated, and the second-end service is called. Since the mutual conversion between the first-end service and the second-end service is realized, the service of the second end, such as the cloud, can be efficiently called at the first end, such as the vehicle end, so that the service of the second end can be called at the first end just like calling the first-end service, thereby realizing seamless calling of the cloud service and the vehicle-end service.

[0099] It should be noted that the vehicle-cloud communication device provided in the above embodiment only uses the division of the above-mentioned functional modules as an example when executing the vehicle-cloud communication method. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0100] In addition, the vehicle-cloud communication device and the vehicle-cloud communication method embodiments provided in the above embodiments belong to the same concept, and their implementation process is detailed in the method embodiments, which will not be repeated here.

[0101] An embodiment of the present application also provides a computer storage medium, which can store multiple instructions, and the instructions are suitable for being loaded by a processor and executing the vehicle-cloud communication method as described in the above embodiment. The specific execution process can be found in the specific description of the above embodiment, and will not be repeated here.

[0102] An embodiment of the present application also provides a computer program product, which stores at least one instruction, and the at least one instruction is loaded by the processor and executed as the vehicle-cloud communication method in the above embodiment. The specific execution process can be found in the specific description of the above embodiment, and will not be repeated here.

[0103] An embodiment of the present application also provides a chip, which is configured to execute the vehicle-cloud communication method as described in the above embodiment. The specific execution process can be found in the specific description of the above embodiment, and will not be repeated here.

[0104] Also, see Figure 8 , which is a schematic diagram of the structure of a vehicle-mounted communication device provided in an embodiment of the present application. Figure 8 As shown, the vehicle-mounted communication device 800 may include: at least one processor 801 , at least one communication module 804 , an input / output interface 803 , a memory 805 , and at least one communication bus 802 .

[0105] The communication bus 802 is used to realize the connection and communication between these components, and the communication bus 802 may be an Ethernet bus.

[0106] The input / output interface 803 may include a display screen (Display) and a camera (Camera). Optionally, the input / output interface 803 may also include a standard wired interface and a wireless interface.

[0107] The communication module 804 may optionally include a standard wired interface or a wireless interface (such as a WIFI interface).

[0108] Among them, the processor 801 may include one or more processing cores. The processor 801 uses various interfaces and lines to connect various parts of the entire vehicle-mounted communication device 800, and executes various functions and processes data of the server 800 by running or executing instructions, programs, code sets or instruction sets stored in the memory 805, and calling data stored in the memory 805. Optionally, the processor 801 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA). The processor 801 can integrate one or a combination of a central processing unit (Central Processing Unit, CPU), a car-cloud communicator (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; and the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 801, but implemented separately through a chip.

[0109] Among them, the memory 805 may include a random access memory (Random Access Memory, RAM) and may also include a read-only memory (Read-Only Memory). Optionally, the memory 805 includes a non-transitory computer-readable storage medium. The memory 805 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 805 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned method embodiments, etc.; the data storage area may store data involved in the above-mentioned method embodiments, etc. The memory 805 may optionally be at least one storage device located away from the aforementioned processor 801. As Figure 8 As shown, the memory 805 as a computer storage medium may include an operating system, a communication module, an input / output interface module, and a vehicle-to-cloud communication application.

[0110] exist Figure 8In the vehicle-mounted communication device 800 shown in the figure, the input / output interface 803 is mainly used to provide an input interface for the user and obtain the data input by the user; and the processor 801 can be used to call the vehicle-to-cloud communication application stored in the memory 805, so that the processor 801 executes the steps in the vehicle-to-cloud communication method according to various exemplary embodiments of the present disclosure. For example, the processor 801 can execute the following steps: Figure 2 The steps shown in: Step S210, in response to the second end's call request for the first end service of the first end, obtain the first end service interface of the first end service in the first end interface definition language; Step S220, based on the first end service interface and the preset interface correspondence, convert the first end service interface into a second end service interface in the second end interface definition language; Step S230, based on the second end service interface, generate a second end service corresponding to the first end service, and call the second end service.

[0111] The above is a schematic scheme of an in-vehicle communication device of an embodiment of this specification. The in-vehicle communication device may be a C2C gateway or other appropriate device central gateway, etc. It should be noted that the technical scheme of the in-vehicle communication device and the technical scheme of the above-mentioned vehicle-to-cloud communication processing method belong to the same concept. For details not described in detail in the technical scheme of the in-vehicle communication device, please refer to the description of the technical scheme of the above-mentioned vehicle-to-cloud communication processing method.

[0112] In the description of the embodiments of the present application, it should be understood that the terms "cloud", "vehicle end", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. In the description of the embodiments of the present application, it should be noted that, unless otherwise clearly specified and limited, "including" and "having" and any of their variations are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices. For ordinary technicians in this field, the specific meanings of the above terms in this application can be understood in specific circumstances. In addition, in the description of the embodiments of the present application, unless otherwise specified, "multiple" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B, which can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0113] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing related hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a disk, an optical disk, a read-only storage memory, or a random access memory, etc.

[0114] The above disclosure is only the preferred embodiment of the present application, which certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the embodiments of the present application.

Claims

1. A vehicle-cloud communication method, characterized in that: A gateway is applied to a vehicle end, the gateway stores a preset interface correspondence relationship, the preset interface correspondence relationship is a correspondence relationship between a first end interface in a first end interface definition language and a second end interface in a second end interface definition language, the preset interface correspondence relationship includes three types of the first end interface and three types of the second end interface, if the first end is a cloud end and the second end is a vehicle end, the three types of the first end interface include Method, Broadcast and Attribute, the three types of the second end interface include Method, Event and Field, the method includes: In response to a call request of the second end to the first end service of the first end, obtaining a first end service interface of the first end service in the first end interface definition language; Based on the first-end service interface and the preset interface correspondence, converting the first-end service interface into a second-end service interface in the second-end interface definition language; In the case where the first end is a cloud end, the second end is a vehicle end, the first end service is a cloud service, the second end service is a service-oriented architecture (SOA) service, and the gateway stores a cloud client, the SOA service of the vehicle end corresponding to the cloud service is generated through the vehicle end service interface and the cloud client, and the SOA service corresponding to the cloud service is called through the cloud client; When the first end is the vehicle end and the second end is the cloud end, the first end service is an SOA service, the second end service is a cloud service, and the gateway stores a client of the SOA service, a cloud service corresponding to the SOA service is generated through the cloud service interface and the client of the SOA service, and the cloud service corresponding to the SOA service is called through the client of the SOA service.

2. The method according to claim 1, characterized in that The first end is a cloud end and the second end is a vehicle end, and the converting the first end service interface into a second end service interface in the second end interface definition language based on the first end service interface and the preset interface correspondence includes: Based on the interface type of the cloud service interface and the preset interface correspondence, a vehicle-side service interface of a corresponding type in the vehicle-side interface definition language is determined.

3. The method according to claim 1, characterized in that The converting the first-end service interface into a second-end service interface in the second-end interface definition language based on the first-end service interface and the preset interface correspondence includes: Based on the interface type of the vehicle-side service interface and the preset interface correspondence, a cloud service interface of a corresponding type in the cloud interface definition language is determined.

4. The method according to claim 1, characterized in that The cloud-side interface definition language is the Franca interface definition language FIDL, and the vehicle-side interface definition language is the automotive open system architecture extensible markup language ARXML.

5. A vehicle-cloud communication device, characterized in that: A gateway is applied to a vehicle end, the gateway stores a preset interface correspondence relationship, the preset interface correspondence relationship is a correspondence relationship between a first end interface in a first end interface definition language and a second end interface in a second end interface definition language, the preset interface correspondence relationship includes three types of the first end interface and three types of the second end interface, if the first end is a cloud end and the second end is a vehicle end, the three types of the first end interface include Method, Broadcast and Attribute, the three types of the second end interface include Method, Event and Field, the device includes: an interface acquisition module, configured to acquire a first-end service interface of the first-end service in the first-end interface definition language in response to a call request from the second end to the first-end service of the first end; An interface conversion module, configured to convert the first-end service interface into a second-end service interface in the second-end interface definition language based on the first-end service interface and the preset interface correspondence; The first service calling module is used to generate the SOA service of the vehicle side corresponding to the cloud service through the vehicle side service interface and the cloud client, and call the SOA service corresponding to the cloud service through the cloud client when the first end is the cloud side and the second end is the vehicle side, the first end service is the cloud service, the second end service is the service-oriented architecture SOA service, and the gateway stores a cloud client; when the first end is the vehicle side and the second end is the cloud side, the first end service is the SOA service, the second end service is the cloud service, and the gateway stores a client of the SOA service, generate the cloud service corresponding to the SOA service through the cloud service interface and the client of the SOA service, and call the cloud service corresponding to the SOA service through the client of the SOA service.

6. A computer storage medium storing a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the steps of the method according to any one of claims 1 to 4.

7. A vehicle-mounted communication device, characterized in that: include: A processor and a memory, wherein the memory stores a computer program, wherein the computer program is suitable for being loaded by the processor and executing the steps of the method according to any one of claims 1 to 4.

Images