WO2024093674A1

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

Info

Publication number: WO2024093674A1
Application number: PCT/CN2023/125187
Authority: WO
Inventors: 梁田峰; 栗羽峰; 张雅杰; 王强
Original assignee: 长城汽车股份有限公司
Priority date: 2022-11-01
Filing date: 2023-10-18
Publication date: 2024-05-10
Also published as: CN115834702A

Abstract

A vehicle-to-cloud communication method and apparatus, a storage medium, and a vehicle-mounted communication device. The method comprises: in response to a call request of a second end for a first end service of a first end, acquiring a first end service interface of the first end, wherein the first end service interface is a service interface of the first end service in a first end interface definition language; converting the first end service interface into a second end service interface on the basis of the first end service interface and a preset interface correspondence, wherein the preset interface correspondence is a correspondence between a first end interface in the first end interface definition language and a second end interface in a second end interface definition language, and the second end service interface is a service interface in the second end interface definition language; and on the basis of 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 a cloud end and the second end is a vehicle end, or the first end is a vehicle end and the second end is a cloud end.

Description

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

This application claims priority to Chinese patent application No. 2022113529573 filed on November 1, 2022, with invention name “Vehicle-cloud communication method, device, storage medium and vehicle-mounted communication equipment”, the entire contents of which are incorporated by reference into this application.

Technical Field

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 technique

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

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

Summary of the invention

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:

In a first aspect, an embodiment of the present application provides a vehicle-cloud communication method, which is executed by a gateway provided in a vehicle, and the method includes:

In response to a call request from the second end to a first-end service of the first end, obtaining a first-end service interface of the first end, where the first-end service interface is a service interface of the first-end service in a first-end interface definition language;

Based on the first-end service interface and a preset interface correspondence, converting the first-end service interface into a second-end service interface, wherein the preset interface correspondence is a 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, and the second-end service interface is a service interface in the second-end interface definition language;

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.

In a second aspect, an embodiment of the present application provides a vehicle-cloud communication device, which is a gateway set in a vehicle, and the device includes:

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

an interface conversion module, configured to convert the first-end service interface into a second-end service interface based on the first-end service interface and a preset interface correspondence relationship, wherein the preset interface correspondence relationship is a correspondence relationship between the first-end interface in the first-end interface definition language and the second-end interface in the second-end interface definition language, and the second-end service interface is a service interface in the second-end interface definition language;

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.

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 following steps:

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 following steps:

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram showing an application scenario of a vehicle-to-cloud communication method according to an embodiment of the present application;

FIG2 is a schematic diagram showing a flow chart of a vehicle-cloud communication method according to an embodiment of the present application;

FIG3 is a schematic diagram showing a flow chart of another vehicle-cloud communication method according to an embodiment of the present application;

FIG4 is a schematic diagram showing a flow chart of another vehicle-cloud communication method according to an embodiment of the present application;

FIG5 is a schematic diagram showing a process of the cloud calling a vehicle-side service according to an embodiment of the present application;

FIG6 shows a schematic diagram of a process of calling a cloud service from a vehicle side according to an embodiment of the present application;

FIG7 shows a schematic structural diagram of a vehicle-to-cloud communication device according to an embodiment of the present application;

FIG8 shows a schematic structural diagram of a vehicle-mounted communication device according to an embodiment of the present application.

Detailed ways

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.

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

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 uses FIDL (Franca Interface description language, Franca interface definition language) to model interfaces to help prevent programming errors related to interface incompatibilities.

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 can communicate with each other through simple and precisely defined interfaces.

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.

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

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.

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

ARXML (AUTOSAR eXtensible Markup Language): This standard introduces the rules for serializing AUTOSAR models into AUTOSAR XML descriptions, providing support for interoperability between AUTOSAR tools.

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.

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

Since the standards of vehicle-side services and cloud services in related technologies are incompatible with each other, cloud services cannot be efficiently called on the vehicle side. How to efficiently call cloud services on the vehicle side has become a technical problem that needs to be solved urgently.

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.

FIG1 shows a schematic diagram of an application scenario of a vehicle-to-cloud communication method according to an embodiment of the present application.

As shown in FIG1 , the application scenario includes a cloud 110 and a vehicle 120, and the vehicle 120 is provided with a C2C gateway 122. The C2C gateway 122 is interconnected with the cloud 110 based on a communication framework such as the Joynr framework, obtains cloud data, converts the cloud data into SOA services of the vehicle 110, provides the vehicle 110 with services of the cloud 120, and converts the SOA services of the vehicle 110 into cloud services.

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 end 110 may be a vehicle-mounted terminal (e.g., a vehicle-mounted controller) of a car, bus, truck, etc., which is not limited in the embodiments of the present application.

FIG2 shows a flow chart of a vehicle-to-cloud communication method according to an embodiment of the present application. 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 provided on the vehicle side. The vehicle-to-cloud communication method includes S210 to S230. The vehicle-to-cloud communication method according to an embodiment of the present application will be described below in conjunction with the accompanying drawings.

2 , in S210 , in response to a call request from the second end to the first end service of the first end, the C2C gateway obtains a first end service interface of the first end service, where the first end service interface is a service interface of the first end service in a first end interface definition language.

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. The first end service is a service that the first end can provide.

In some embodiments, 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 and the second end service is an SOA service. In response to the vehicle end's call request to the cloud service on the cloud, the C2C gateway obtains the cloud service interface of the cloud service in the cloud interface definition language.

In some embodiments, the cloud interface definition language is a FIDL file, and the FIDL file supports the definition of three types of interfaces, including: method, broadcast, and attribute. Accordingly, the above steps are in response to the vehicle-side call request to the cloud service on the cloud side, and the C2C gateway obtains the interface information of the cloud service interface in the FIDL file of the cloud service.

In some embodiments, the cloud service is a weather forecast service. In response to a vehicle-side call request to the cloud weather forecast service, the C2C gateway obtains the cloud service interface of the weather forecast server in the cloud interface definition language. For example, the cloud service interface is a Broadcast interface. The Broadcast interface is used to The vehicle side publishes the weather status. It should be noted that, in addition to the above-mentioned weather forecast service, the cloud service can also provide other types of services in the vehicle scenario, such as navigation service, music service, video service or rescue service, etc., which is not limited in the embodiment of the present application.

In S220, the C2C gateway converts the first-end service interface into a second-end service interface based on the first-end service interface and a preset interface correspondence relationship, wherein the preset interface correspondence relationship is a correspondence relationship between the first-end interface in the first-end interface definition language and the second-end interface in the second-end interface definition language, and the second-end service interface is a service interface in the second-end interface definition language.

In some embodiments, taking the first end as the cloud and the second end as the vehicle end as an example, the C2C gateway converts the cloud service interface into a vehicle end service interface in the vehicle end interface definition language based on the cloud service interface and the preset interface correspondence.

Among them, the C2C gateway stores the preset interface correspondence, and the preset interface correspondence 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. In some embodiments, 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 corresponding relationship between the interfaces in ARXML and FIDL is shown in Table 1 below.

Table 1. Correspondence between ARXML and FIDL interfaces

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, and is mostly used by the client to send control commands to the server. Depending on whether the server has feedback, Method is divided into Request/Response communication and 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 represent the status of a service. Control commands can be issued through Method, that is, Setter, and service status can be requested through Method, that is, Getter. Notifications can also be sent when the service status changes.

In some embodiments, the C2C gateway determines the corresponding type of vehicle-side service interface from the vehicle-side interface definition language based on the interface type of the cloud service interface and the preset interface correspondence relationship, thereby converting the cloud service interface into a vehicle-side service interface. The service interface is converted into the vehicle-side service interface of the corresponding type.

For example, 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 (Table 1), the C2C gateway determines the corresponding type of vehicle-side service interface, namely, the Event interface, from the vehicle-side interface definition language. The C2C gateway converts the cloud service interface of the Broadcast type into the corresponding type of Event interface, for example, converts the data type of the cloud service interface of the Broadcast type into the data type of the Event interface, and generates an interface instance of the corresponding vehicle-side service interface, such as an ARXML interface file, so that the data types of the cloud service interface and the vehicle-side service interface can be uniformly processed to avoid data conversion errors.

In S230, the C2C gateway generates a second-end service corresponding to the first-end service based on the second-end service interface, and calls the second-end service.

In some embodiments, 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 and the second end service is an SOA service. The C2C gateway generates an SOA service corresponding to the cloud service based on the vehicle end service interface and calls the SOA service.

Among them, SOA services are services deployed on the vehicle side, such as services provided by various vehicle-mounted software. The C2C gateway obtains the parameter data of the cloud service interface corresponding to the cloud service. Based on the interface parameters of the vehicle-side service interface and the data type of the interface parameters, the C2C gateway obtains the corresponding data from the parameter data of the cloud service interface, generates the service data of the SOA service corresponding to the cloud service, such as the SOA service in ARXML format, and calls the service interface of the SOA service.

For example, the parameter data of the cloud service interface includes the interface ID, interface parameters, and parameter types of the interface parameters. The C2C gateway obtains data corresponding to the vehicle-side service interface from the parameter data of the cloud service interface, generates service data of the SOA service corresponding to the cloud service, that is, the SOA service in ARXML format, and calls the service interface of the SOA service.

For example, the cloud service is a weather forecast service. The C2C gateway obtains corresponding weather data, such as weather conditions and temperature, from the weather forecast service interface based on the vehicle-side service interface. The C2C gateway generates a SOA service corresponding to the weather forecast service, namely, a SOA weather forecast service, based on the obtained weather data and the vehicle-side service interface. The C2C gateway calls the weather forecast service interface.

According to the technical solution of the embodiment of the present application, 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 first-end service interface and the second-end service interface can be converted to each other; 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. The mutual conversion between the first-end service and the second-end service can efficiently call the second-end service, such as the cloud, at the first end, such as the vehicle end, so that the first end can call the second-end service just like calling the first-end service, thereby realizing seamless calling of the cloud service and the vehicle-end service.

FIG3 shows a flow chart of another vehicle-to-cloud communication method according to an embodiment of the present application.

3 , in S310 , in response to a call request from the cloud to the vehicle-side SOA service, the C2C gateway obtains the vehicle-side service interface of the SOA service in the vehicle-side interface definition language.

In some embodiments, 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.

In some embodiments, in response to the cloud's call request to the vehicle-side SOA service, the C2C gateway obtains the vehicle-side service interface of the SOA service in ARXML. For example, the SOA service is a vehicle speed acquisition service. In response to the cloud's call request to the vehicle-side vehicle speed acquisition service, the C2C gateway 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.

In S320 , the C2C gateway converts the vehicle-side service interface into a cloud-side service interface in a cloud-side interface definition language based on the vehicle-side service interface and a preset interface correspondence relationship.

In some embodiments, the C2C gateway stores the 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. 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 determined by Table 1 above.

In some embodiments, 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 the corresponding type, such as a FIDL interface instance file.

For example, 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. The C2C gateway generates an interface instance of the corresponding type of cloud server interface, for example, assigning the vehicle speed of the Field type vehicle speed acquisition service to the cloud server interface, namely the Attribute interface.

In S330, the C2C gateway generates a cloud service corresponding to the SOA service based on the cloud service interface and calls the cloud service.

In some embodiments, the cloud service is a service provided by the cloud, such as a weather service, an intelligent recommendation service, etc., and the C2C gateway stores a client of the SOA service. The C2C gateway generates a cloud service corresponding to the SOA service through the cloud service interface and the client of the SOA service. The C2C gateway calls the cloud service corresponding to the SOA service through the client of the SOA service. For example, the C2C gateway obtains the parameter data of the vehicle-side service interface corresponding to the SOA service. Based on the interface parameters of the cloud service interface and the data type of the interface parameters, the C2C gateway obtains the corresponding data from the parameter data of the vehicle-side service interface, generates the service data of the cloud service corresponding to the SOA service, and calls the service interface of the cloud service.

For example, the SOA service is a vehicle speed acquisition service. The C2C gateway acquires corresponding vehicle speed data, such as vehicle speed, from the vehicle speed acquisition service interface based on the cloud service interface. The C2C gateway generates a cloud service corresponding to the vehicle speed acquisition service based on the acquired vehicle speed and the cloud service interface, such as a vehicle speed acquisition service interface in a FIDL file format, and calls the cloud service in the FIDL file format.

According to the technical solution of the embodiment of the present application, 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 in-vehicle SOA service can be called in the cloud just like calling a cloud service.

FIG4 shows a flow chart of another vehicle-cloud communication method according to an embodiment of the present application.

The C2C gateway 122 is set on the vehicle end 120, that is, it runs on the vehicle end 120. The C2C gateway 122 realizes interconnection with the cloud 110 based on a communication framework such as the Joynr framework. The C2C gateway 122 obtains cloud data, converts the cloud data into SOA services of the vehicle end 110, and provides the vehicle end 110 with services of the cloud 120. At the same time, the C2C gateway 122 can also convert the SOA services of the vehicle end 110 into cloud services.

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.

According to the technical solution in the above exemplary 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 enabling the cloud service to be The end and the vehicle are seamlessly connected, and seamless calls support vehicle-side services and cloud services.

FIG5 shows a schematic diagram of a process of the cloud calling a vehicle-side service according to some embodiments of the present application.

5, the C2C gateway 122 generates a cloud FIDL file based on the ARXML content of the SOA service, that is, converting the ARXML file of the SOA service into a corresponding FIDL file based on the correspondence between the ARXML and FIDL files, that is, the cloud service file corresponding to the SOA service. 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 the SOA client 124 and the cloud service files can be connected through the C2C gateway 122.

According to the technical solution of the embodiment of the present application, 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, and the cloud service file corresponding to the SOA service is saved by the C2C gateway, so that the cloud service and the vehicle-side service are seamlessly connected and called without feeling. In addition, the existing vehicle-mounted SOA or cloud service can be quickly deployed without major modifications, which can more conveniently accelerate the deployment of vehicle-cloud interconnection.

FIG6 shows a schematic diagram of the process of the vehicle-side calling cloud services according to the present application.

6, the cloud service provides a 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.

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.

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.

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.

FIG7 shows a schematic structural diagram of a vehicle-to-cloud communication device according to an exemplary embodiment of the present application.

As shown in FIG7 , 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 belongs to a gateway set in the vehicle end. The vehicle-to-cloud communication device 700 includes an interface acquisition module 710, an interface conversion module 720, and a service call module. Block 730.

The interface acquisition module 710 is used to obtain the first-end service interface of the first end in response to the second end's call request for the first-end service of the first end, where the first-end service interface is the service interface of the first-end service in the first-end interface definition language.

The interface conversion module 720 is used to convert the first-end service interface into a second-end service interface based on the first-end service interface and a preset interface correspondence relationship. The preset interface correspondence relationship 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 second-end service interface is a service interface in the second-end interface definition language.

The first 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.

In some embodiments, the first end is the cloud end and the second end is the vehicle end, and the interface conversion module 720 is used to determine the corresponding type of vehicle-end service interface from the vehicle-end interface definition language based on the interface type of the cloud service interface and the preset interface correspondence.

In some embodiments, 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 an SOA service, and the service calling module 730 is used to generate the vehicle end SOA service corresponding to the cloud service through the vehicle end service interface and the client of the first end, and call the SOA service corresponding to the cloud service through the client.

In some embodiments, the first end is the vehicle end and the second end is the cloud end, and the interface conversion module 720 is used to determine the corresponding type of cloud service interface from the cloud interface definition language based on the interface type of the vehicle end service interface and the preset interface correspondence.

In some embodiments, the first end is a vehicle end and the second end is a cloud end, the first end service is an SOA service, the second end service is a cloud service, and the service calling module 730 is used to generate a cloud service corresponding to the SOA service through the cloud service interface and the client of the SOA service. The cloud service corresponding to the SOA service is called through the client of the SOA service.

In some embodiments, the cloud-side interface definition language is Franca interface definition language FIDL, and the vehicle-side interface definition language is automotive open system architecture extensible markup language ARXML.

In some embodiments, the preset interface correspondence is stored in the gateway.

According to the technical solution of the embodiment of the present application, on the one hand, based on the first end service interface and the preset interface correspondence relationship, the first end service interface of the first end service is converted into the second end service interface, On the other hand, 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. 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 the service of the first end, thereby realizing seamless calling of the cloud service and the vehicle-end service.

It should be noted that, when the vehicle-to-cloud communication device according to the above embodiment executes the vehicle-to-cloud communication method, only the division of the above functional modules is used as an example. In actual applications, the above 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. These modules can be processors that can realize the above functions.

In addition, the vehicle-cloud communication device and the vehicle-cloud communication method according to the above-mentioned embodiment belong to the same concept, and their implementation process is detailed in the method embodiment, which will not be repeated here.

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.

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.

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.

In addition, please refer to Figure 8, which is a schematic diagram of the structure of a vehicle-mounted communication device according to an embodiment of the present application. As shown in Figure 8, the vehicle-mounted communication device 800 may include: at least one processor 801, at least one communication module 804, an input and output interface 803, a memory 805, and at least one communication bus 802.

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.

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

The communication module 804 may optionally include a standard wired interface and a wireless interface (such as a WIFI interface).

Among them, the processor 801 may include one or more processing cores. The processor 801 uses various interfaces and lines to connect various parts in 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 communication. It can be understood that the above-mentioned modem may not be integrated into the processor 801, but implemented by a single chip.

Among them, the memory 805 may include a random access memory (RAM) or a read-only memory (ROM). 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 various method embodiments, etc.; the data storage area may store data involved in the above-mentioned various method embodiments, etc. The memory 805 may also be at least one storage device located away from the aforementioned processor 801. As shown in FIG. 8 , 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.

In the vehicle-mounted communication device 800 shown in FIG8 , 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 embodiments of the present application. For example, the processor 801 can execute the steps shown in FIG2 : S210, in response to the second end's call request for the first end service of the first end, obtain the first end service of the first end service S220, based on the first-end service interface and a preset interface correspondence, convert the first-end service interface into a second-end service interface, the preset interface correspondence is a 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, and the second-end service interface is a service interface in the second-end interface definition language; 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.

The above is a schematic scheme of an in-vehicle communication device of an embodiment of the present application. The in-vehicle communication device may be a C2C gateway, or may be 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.

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.

The above disclosure is only the preferred embodiment of the present application, and 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

A vehicle-cloud communication method is performed by a gateway provided in a vehicle terminal, the method comprising:

In response to a call request from the second end to a first-end service of the first end, obtaining a first-end service interface of the first end, where the first-end service interface is a service interface of the first-end service in a first-end interface definition language;

Based on the first-end service interface and a preset interface correspondence, converting the first-end service interface into a second-end service interface, wherein the preset interface correspondence is a 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, and the second-end service interface is a service interface in the second-end interface definition language;

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.
The method according to claim 1, wherein the first end is a cloud end and the second end is a vehicle end, and converting the first end service interface into the second end service interface based on the first end service interface and a preset interface correspondence relationship comprises:

Based on the interface type of the cloud service interface and the preset interface correspondence, a corresponding type of vehicle-side service interface is determined from the vehicle-side interface definition language.
The method according to claim 1, wherein 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 SOA service, and the generating a second end service corresponding to the first end service based on the second end service interface and calling the second end service comprises:

Generate the SOA service of the vehicle side corresponding to the cloud service through the vehicle side service interface and the client of the first side;

The SOA service corresponding to the cloud service is called through the client.
The method according to claim 1, wherein the first end is a vehicle end and the second end is a cloud end, and the first end service interface is configured based on the corresponding relationship between the first end service interface and the preset interface. The service interface is converted into the second-end service interface, including:

Based on the interface type of the vehicle-side service interface and the preset interface correspondence, a cloud service interface of a corresponding type is determined from a cloud interface definition language.
The method according to claim 1, wherein the first end is a vehicle end and the second end is a cloud end, the first end service is an SOA service, the second end service is a cloud service, and the generating a second end service corresponding to the first end service based on the second end service interface and calling the second end service comprises:

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

The cloud service corresponding to the SOA service is called through the client of the SOA service.
According to the method of claim 1, the cloud-side interface definition language is Franca interface definition language FIDL, and the vehicle-side interface definition language is Automotive Open System Architecture Extensible Markup Language ARXML.
The method according to claim 1, wherein the preset interface correspondence is stored in the gateway.
A vehicle-to-cloud communication device, belonging to a gateway arranged in a vehicle, comprises:

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

an interface conversion module, configured to convert the first-end service interface into a second-end service interface based on the first-end service interface and a preset interface correspondence, wherein the preset interface correspondence is a 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, and the second-end service interface is a service interface in the second-end interface definition language;

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.
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 7.
An in-vehicle communication device comprises: 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 method according to any one of claims 1 to 7.