CN115834702A - Vehicle cloud communication method and device, storage medium and vehicle-mounted communication equipment - Google Patents
Vehicle cloud communication method and device, storage medium and vehicle-mounted communication equipment Download PDFInfo
- Publication number
- CN115834702A CN115834702A CN202211352957.3A CN202211352957A CN115834702A CN 115834702 A CN115834702 A CN 115834702A CN 202211352957 A CN202211352957 A CN 202211352957A CN 115834702 A CN115834702 A CN 115834702A
- Authority
- CN
- China
- Prior art keywords
- service
- interface
- cloud
- vehicle
- definition language
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 76
- 238000004891 communication Methods 0.000 title claims abstract description 74
- 238000006243 chemical reaction Methods 0.000 claims description 15
- 238000004590 computer program Methods 0.000 claims description 5
- 230000001939 inductive effect Effects 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 14
- 230000008569 process Effects 0.000 description 11
- 230000006870 function Effects 0.000 description 10
- 230000004044 response Effects 0.000 description 9
- 230000001953 sensory effect Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000003672 processing method Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000002457 bidirectional effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
- H04L41/0273—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using web services for network management, e.g. simple object access protocol [SOAP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Computer And Data Communications (AREA)
Abstract
The embodiment of the application discloses a vehicle cloud communication method, a device, a storage medium and vehicle-mounted communication equipment, wherein the method comprises the following steps: responding to a calling request of a second end to a first end service of a first end, and acquiring a first end 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 in a second end interface definition language based on the first end service interface and the corresponding relation of the preset interface; and generating a second end service corresponding to the first end service based on the second end service interface, 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 the vehicle end and the second end is the cloud end. According to the technical scheme of the embodiment of the application, the cloud service and the vehicle-side service can be mutually converted, and therefore the cloud service and the vehicle-side service can be invoked in a non-inductive mode.
Description
Technical Field
The application relates to the technical field of communication, in particular to a vehicle cloud communication method and device, a storage medium and vehicle-mounted communication equipment.
Background
With the development of the car networking technology, the functions of the car-mounted system are more and more abundant. How to interconnect and intercommunicate the vehicle-mounted service and the cloud service becomes a focus of attention.
At present, the vehicle-mounted service and the cloud service respectively have a set of standards, and the standards of the vehicle-side service and the cloud service are incompatible with each other, so that the cloud service cannot be efficiently called at a vehicle side.
Therefore, how to efficiently call the cloud service at the vehicle end becomes a technical problem to be solved urgently.
Disclosure of Invention
The embodiment of the application provides a vehicle cloud communication method and device, a storage medium and vehicle-mounted communication equipment, and cloud service can be efficiently called at a vehicle end. The technical scheme is as follows:
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, where a preset interface corresponding relationship is stored in the gateway, and the preset interface corresponding relationship is a corresponding 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, where the method includes:
responding to a calling request of the second end to a first end service of the first end, and acquiring a first end service interface of the first end service in the first end interface definition language;
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 corresponding relation;
generating a second end service corresponding to the first end service based on the second end service interface, 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 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 applied to a gateway provided in a vehicle end, where the gateway stores a preset interface corresponding relationship, and the preset interface corresponding relationship is a corresponding 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, where the device includes:
an interface obtaining module, configured to obtain, in response to a call request of the second end to a first end service of the first end, a first end service interface of the first end service in the first end interface definition language;
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 for generating a second end service corresponding to the first end service based on the second end service interface 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 the vehicle end and the second end is the cloud end.
In a third aspect, embodiments of the present application provide a computer storage medium storing a plurality of instructions adapted to be loaded by a processor and execute the steps of the above-mentioned method.
In a fourth aspect, an embodiment of the present application provides an in-vehicle communication device, including: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to perform the steps of the method as described above.
The beneficial effects brought by the technical scheme provided by some embodiments of the application at least comprise:
on one hand, the first end service interface of the first end service is converted into the second end service interface based on the corresponding relation between the first end service interface and the preset 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, 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, so that the first end service and the second end service are mutually converted, the second end service such as a cloud end service can be efficiently called at the first end such as a vehicle end, the second end service can be called at the first end like the first end service, and the cloud end service and the vehicle end service can be called in a non-sensory mode.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic diagram illustrating an application scenario of a vehicle cloud communication method provided in an embodiment of the present application;
FIG. 2 illustrates a flow diagram of a vehicle cloud communication method provided in accordance with some embodiments of the present application;
FIG. 3 illustrates a flow diagram of a vehicle cloud communication method provided in accordance with further embodiments of the present application;
FIG. 4 illustrates a flow diagram of a vehicle cloud communication method provided in accordance with further embodiments of the present application;
fig. 5 illustrates a flow diagram of cloud-invoked vehicle-side services provided in accordance with some embodiments of the present application;
fig. 6 is a schematic flow chart illustrating a process of invoking cloud service by a vehicle end according to some embodiments of the present application
Fig. 7 shows a schematic structural diagram of another vehicle cloud communication device provided in the embodiment of the present application
Fig. 8 shows a schematic structural diagram of an in-vehicle communication device provided in an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described clearly and completely with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only some embodiments of the present application, and not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort belong to the protection scope of the present application.
First, terms referred to in the embodiments of the present application are explained and explained.
Joynr: the method is a Web-based communication framework and is used for deploying applications and services to vehicles, consumption equipment and cloud servers which need to interact with each other. Joynr helps prevent programming errors related to Interface incompatibilities by modeling the Interface using FIDL (Franca Interface description language).
SOA (Service-Oriented Architecture): the decoupling between the software modules of the distributed system can be realized, the service entities can be more conveniently and flexibly deployed on any domain controller through software upgrading, and the services only need to be communicated through a simple and accurately defined interface.
CAN bus: the data bus in the conventional vehicle-mounted architecture can carry a large amount of data, and is a serial communication protocol of ISO international standardization.
LIN (Local Interconnect Network) bus: the data bus in the traditional vehicle-mounted architecture is used for realizing the control of a distributed electronic system in an automobile, can bear smaller data volume, is mainly used for controlling some simple in-vehicle devices, and is an auxiliary bus network.
SOMEIP (Scalable service-organized MiddlewarE over IP, service-Oriented Scalable MiddlewarE over IP) protocol: is an automotive middleware solution for control messages that enables service-oriented communication between controllers. SOMEIP provides extensive 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: the vehicle cloud communication gateway realizes the intercommunication between a vehicle end and a cloud end.
ARXML (AUTOSAR eXtensible Markup Language): the standard introduces rules for how the AUTOSAR model is serialized into AUTOSAR XML descriptions, providing support for interoperability between AUTOSAR tools.
AUTOSAR (automatic Open System Architecture, open systems Architecture for automobiles): is a alliance which aims at establishing automobile electronic software standards and aims at developing an open and standardized software architecture for the automobile industry.
FIDL (Franca Interface Definition Language ): is a text language for specifying interface descriptions.
Hereinafter, a technical solution of the vehicle cloud communication method according to the embodiment of the present application will be described in detail with reference to the accompanying drawings.
Fig. 1 shows a schematic diagram of an application scenario of a vehicle cloud communication method provided in an embodiment of the present application.
Referring to fig. 1, the application scenario includes a cloud terminal 110 and a vehicle terminal 120. Where the C2C gateway 122 operates at the vehicle end 120. The C2C gateway 122 realizes interconnection with the cloud terminal 110 based on a communication framework such as a Joynr framework, obtains cloud terminal data, converts the cloud terminal data into SOA service of the vehicle terminal 110, provides service of the cloud terminal 120 for the vehicle terminal 110, and converts the SOA service of the vehicle terminal 110 into the cloud terminal service.
It should be noted that the cloud 110 may be a cloud server, such as a server cluster composed of a plurality of servers, or a cloud server. The vehicle end 110 may be a car, a bus, or a truck, etc. The above description is merely an example, and is not limited in this respect in the embodiments of the present application.
Fig. 2 illustrates a flow diagram of a vehicle cloud communication method provided in accordance with some embodiments of the present application. The execution subject of the vehicle cloud communication method may be a computing device having a computing processing function, such as a C2C gateway. The vehicle cloud communication method includes steps S210 to S230, and the vehicle cloud communication method in the example embodiment is described in detail below with reference to the drawings.
Referring to fig. 2, in step S210, in response to a call request of a second end to a first end service of a first end, a first end service interface of the first end service in a first end interface definition language is obtained.
In an example embodiment, 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. Taking the first end as the cloud end 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 cloud service interface of the cloud service in the cloud end interface definition language is obtained in response to a call request of the vehicle end to the cloud service of the cloud end. The cloud interface definition language is a FIDL file, and the FIDL file supports the definition of three types of interfaces: method, broadcast, attribute Attribute. The C2C gateway responds to a call request of a vehicle end to cloud service of a cloud end, and obtains interface information of a cloud service interface of the cloud service in the FIDL file.
For example, if the cloud service is a weather forecast service, the C2C gateway obtains a cloud service interface, such as a Broadcast interface, of the weather forecast server in a cloud interface definition language in response to a request for calling the weather forecast service from the vehicle end to the cloud end, and the Broadcast interface is used for publishing a weather state to the vehicle end.
In step S220, the first end service interface is converted into a second end service interface in the second end interface definition language based on the first end service interface and the preset interface corresponding relationship.
In an example embodiment, taking the first end as the cloud end and the second end as the vehicle end as an example, the cloud end service interface is converted into the vehicle end service interface in the vehicle end interface definition language based on the cloud end service interface and the preset interface corresponding relationship. The gateway stores a preset interface corresponding relation, and the preset interface corresponding relation is a corresponding relation between a cloud end interface in the cloud end interface definition language and a vehicle end interface in the vehicle end interface definition language. The cloud interface definition language is a FIDL file, and the vehicle interface definition language is an ARXML file. The FIDL file supports the definition of three types of interfaces: method, broadcast, attribute, which corresponds to three types of interfaces in ARXML: method, event, field. The correspondence of ARXML to interfaces in FIDL can be identified by the following Table 1:
TABLE 1 correspondence of interfaces in ARXML and FIDL
| Interface types in ARXML | Interface type in FIDL |
| Field | Attribute |
| Method | Method |
| Event | Broadcast |
Wherein, the three types of interfaces in ARXML comprise Method, event and Field. The Method, namely remote procedure call, is that a node sends a Request service to another node, is mainly used for a client to send a control command to a server, and is divided into Request/Response communication and Forget after sending Fire & form communication according to whether the server has feedback. The Event is similar to a CAN message and used for releasing the state, and different sending modes CAN be provided according to the actual application scene. Field is used to represent the state quantity of a certain service. The control command, i.e. Setter, can be issued by means; the service state can also be requested to be acquired through the Method, namely Getter; notifications may also be sent when a change in service status occurs.
Further, the C2C gateway determines the vehicle-side service interface of the corresponding type in the vehicle-side interface definition language based on the interface type of the cloud-side service interface and the preset interface corresponding relation, and converts the cloud-side service interface into the vehicle-side service interface of the corresponding type.
For example, a cloud service is set as a weather forecast service, an interface type of a cloud service interface is a Broadcast interface, based on the interface type of the cloud service interface and the corresponding relationship table, an Event interface, which is a vehicle-side service interface of a corresponding type in a vehicle-side interface definition language, is determined, and the cloud service interface of the Broadcast interface is converted into an Event interface of a corresponding type, for example, the data type of the cloud service interface of the Broadcast interface is converted into the data type of the Event interface, and an interface instance, such as an ARXML interface file, of the corresponding vehicle-side service interface is generated, so that the data types of the cloud service interface and the vehicle-side service interface can be processed uniformly, and data conversion errors are avoided.
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.
In an example embodiment, taking the first end as the cloud end and the second end as the vehicle end as an example, the first end service is cloud service, the second end service is SOA service, and the SOA service corresponding to the cloud service is generated based on the vehicle end service interface and called. The SOA service is a service deployed at a vehicle end, such as a service provided by various vehicle-mounted software, parameter data of a cloud service interface corresponding to the cloud service is obtained, corresponding data is obtained from the parameter data of the cloud service interface based on interface parameters of the vehicle-end service interface and data types of the interface parameters, service data of the SOA service corresponding to the cloud service, such as SOA service in an ARXML format, is generated, and the service interface of the SOA service is called. For example, the cloud service interface comprises an interface ID, interface parameters and parameter types of the interface parameters, data corresponding to the vehicle-side service interface are obtained from parameter data of the cloud service interface, service data of SOA service corresponding to the cloud service, namely the SOA service in the ARXML format, is generated, and the service interface of the SOA service is called.
For example, the cloud service is set as a weather forecast service, corresponding weather data such as a weather condition value and a temperature value is acquired from a weather forecast service interface based on a vehicle-side service interface, an SOA service, namely an SOA weather forecast service, corresponding to the cloud service is generated based on the acquired weather data and the vehicle-side service interface, and the weather forecast service interface is called.
According to the technical solution in the example embodiment of fig. 2, on one hand, a first end service interface of a first end service is converted into a second end service interface based on a corresponding relationship between the first end service interface and a preset interface, so that mutual conversion between the first end service interface and the second end service interface can be realized; 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, so that the first end service and the second end service are mutually converted, the second end service such as a cloud end service can be efficiently called at the first end such as a vehicle end, the second end service can be called at the first end like the first end service, and the cloud end service and the vehicle end service can be called in a non-sensory mode.
Fig. 3 shows a flow diagram of a vehicle cloud communication method provided in accordance with further embodiments of the present application.
Referring to fig. 3, in step S310, in response to a request for calling the SOA service of the vehicle end from the cloud, a vehicle end service interface of the SOA service in the vehicle end interface definition language is obtained.
In an example embodiment, the first end is a vehicle end and the second end is a cloud end, and the SOA service is a service deployed by the vehicle end, that is, a service provided by various vehicle-mounted software, such as a voice broadcast service. The vehicle-end interface definition language is an ARXML file. The ARXML contains three types of interfaces: method, event, field. The Method, namely remote procedure call, is that a node sends a Request service to another node, is mainly used for a client to send a control command to a server, and is divided into Request/Response communication and Forget after sending Fire & form communication according to whether the server has feedback. The Event is similar to a CAN message and used for releasing the state, and different sending modes CAN be provided according to the actual application scene. Field is used to represent the state quantity of a service. A control command, i.e., setter, can be issued by Method; the service state can also be requested to be acquired through the Method, namely Getter; notifications may also be sent when a change in service status occurs.
Further, the C2C gateway responds to a call request of the cloud terminal to the SOA service of the vehicle end, and obtains a vehicle end service interface of the SOA service in the ARXML. For example, the SOA service is set as a vehicle speed obtaining service, and the C2C gateway obtains a vehicle-side server interface, such as a Field interface, of the vehicle speed obtaining service in the ARXML in response to a call request of the cloud to the vehicle-side vehicle speed obtaining service, where the Field interface is used for obtaining a vehicle speed of a vehicle.
In step S320, the vehicle-side service interface is converted into a cloud service interface in the cloud interface definition language based on the vehicle-side service interface and the preset interface corresponding relationship.
In an example embodiment, the C2C gateway stores a preset interface correspondence relationship, where the preset interface correspondence relationship is a correspondence relationship between a cloud end interface in the cloud end interface definition language and a vehicle end interface in the vehicle end interface definition language. The cloud interface definition language is a FIDL file, and the vehicle interface definition language is an ARXML file. The FIDL file supports the definition of three types of interfaces: method, broadcast, attribute, which corresponds to three types of interfaces in ARXML: method, event, field. The correspondence of ARXML to interfaces in FIDL can be identified by Table 1 above.
Further, 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 corresponding relation; and generating an interface instance of the cloud service interface of the corresponding type, such as a FIDL interface instance file.
For example, setting the SOA service as a vehicle speed acquisition service, setting the interface type of a vehicle-side service interface as a Field type, and determining a corresponding type of cloud service interface, namely an Attribute interface, in the FIDL by the C2C gateway based on the interface type of the vehicle-side service interface and the preset interface corresponding relation; and generating an interface instance of the cloud server interface of the corresponding type, for example, giving a vehicle speed value of the vehicle speed acquisition service of the Field type to the cloud server interface, namely an Attribute interface.
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.
In an example embodiment, the cloud service is a service provided by the cloud, such as a weather service, an intelligent recommendation service, and the like. The C2C gateway stores a client of the SOA service, and generates cloud service corresponding to the SOA service through a cloud service interface and the client of the SOA service; and calling the cloud service corresponding to the SOA service through the client of the SOA service. For example, parameter data of a vehicle-side service interface corresponding to the SOA service is acquired, corresponding data is acquired from the parameter data of the vehicle-side service interface based on interface parameters of the cloud-side service interface and data types of the interface parameters, service data of cloud service corresponding to the SOA service is generated, and the service interface of the cloud service is called.
For example, setting the SOA service as a vehicle speed obtaining service, obtaining corresponding vehicle speed data such as a vehicle speed value from the vehicle speed obtaining service interface based on the cloud service interface, generating a cloud service corresponding to the vehicle speed obtaining service, such as a vehicle speed obtaining service interface in a FIDL file format, based on the obtained vehicle speed value and the cloud service interface, and calling the cloud service in the FIDL file format.
According to the technical scheme in the example embodiment of fig. 3, on one hand, based on the vehicle-side service interface and the preset interface corresponding relationship, the vehicle-side service interface of the SOA service is converted into the cloud-side service interface, so that the vehicle-side service interface and the cloud-side service interface can be mutually converted; on the other hand, the cloud service corresponding to the SOA service is generated based on the cloud service interface, and the cloud service is called, so that the vehicle-side service can be efficiently called at the cloud end due to the fact that mutual conversion of the vehicle-side service and the cloud-side service is achieved, and the SOA service in the vehicle can be called at the cloud end like the cloud-side service.
Fig. 4 shows a flow diagram of a vehicle cloud communication method provided in accordance with further embodiments of the present application.
The C2C gateway 122 operates at the vehicle end 120. The C2C gateway 122 realizes interconnection with the cloud terminal 110 based on a communication framework such as a Joynr framework, obtains cloud terminal data, converts the cloud terminal data into SOA service of the vehicle terminal 110, provides service of the cloud terminal 120 for the vehicle terminal 110, and converts the SOA service of the vehicle terminal 110 into the cloud terminal service.
The cloud end 110 uses a cloud service definition file FIDL, the vehicle end 120 uses an SOA service definition file ARXML, bidirectional conversion between the cloud service definition file FIDL and the SOA service definition file ARXML is realized through a communication framework such as a Joynr framework, and the C2C gateway 122 automatically generates a conversion code according to the file, converts the FIDL file into the ARXML file, or converts the ARXML file into the FIDL file.
According to the technical scheme in the above example embodiment, the C2C gateway performs mutual conversion on the FIDL and the ARXML of the service definition file, so that the cloud service and the vehicle-side service can be mutually converted, the cloud and the vehicle-side are seamlessly linked, and the vehicle-mounted service and the cloud service are supported through non-inductive call.
Fig. 5 is a schematic flow chart illustrating a cloud-invoked vehicle-side service according to some embodiments of the present disclosure.
Referring to fig. 5, the C2C gateway 122 generates a cloud FIDL file according to the ARXML content of the SOA service, that is, converts the ARXML file of the SOA service into a corresponding FIDL file, that is, a cloud service file corresponding to the SOA service, according to the correspondence between the ARXML and the FIDL file. The C2C gateway 122 stores the SOA client 124 and a cloud service file corresponding to the SOA service, so that other cloud programs can call the file, and the SOA client 124 and the cloud service file are connected through the C2C gateway 122.
According to the technical scheme in the example embodiment, the ARXML file of the SOA service is converted into the cloud service file corresponding to the SOA service according to the corresponding relation between the ARXML file and the FIDL file, seamless linking and noninductive calling of the cloud service and the vehicle-side service are achieved through the cloud service file corresponding to the SOA service stored in the C2C gateway, the existing vehicle-mounted SOA or cloud service does not need to be greatly modified, deployment can be carried out quickly, and deployment of vehicle-cloud interconnection can be accelerated more conveniently.
Fig. 6 illustrates a flow diagram of a vehicle-side invoking cloud service provided in accordance with some embodiments of the present application.
Referring to fig. 6, the cloud service provides an FIDL file of the cloud service, 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 an SOA service corresponding to the cloud service, that is, an ARXML file of the SOA service, is generated to provide the cloud service to other programs at the vehicle end. The C2C gateway 122 serves as a gateway between the vehicle end 120 and the cloud end 110, and is responsible for mutually converting services of the cloud end 110/the vehicle end 120.
Further, in an example embodiment, the gateway stores a cloud client 126 in a cloud, and generates an SOA service corresponding to the cloud service of the vehicle end through the vehicle end service interface and the cloud client 126; and calling the SOA service corresponding to the cloud service through the client at the cloud end.
According to the technical solution in the above example embodiment, the vehicle cloud gateway 122 based on the Joynr framework is responsible for converting cloud/vehicle-side services to each other. In the vehicle, the cloud service can be called like calling the SOA service in the vehicle. Unified service conversion is carried out on the C2C gateway, and cloud vehicle-side service interconnection is realized.
The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the embodiments of the method of the present application.
Fig. 7 shows a schematic structural diagram of a vehicle cloud communication device according to an exemplary embodiment of the present application.
Referring to fig. 7, the vehicle cloud communication device 700 may be implemented as all or a part of a device by software, hardware, or a combination of the two, where the vehicle cloud communication device 700 is applied to a gateway disposed in a vehicle end, where the gateway stores a preset interface corresponding relationship, and the preset interface corresponding relationship is a corresponding 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 car cloud communication device 700 includes an interface acquisition module 710, an interface conversion module 720, and a service call module 730. Wherein:
an interface obtaining module 710, configured to, in response to a call request of the second end to a first end service of the first end, obtain a first end service interface of the first end service in the first end interface definition language;
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 corresponding relationship;
the service calling module 730 is configured 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, where 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.
In some example embodiments, based on the above scheme, where the first end is a cloud end and the second end is a vehicle end, the interface conversion module 720 is configured to:
and determining the vehicle-end service interface of the corresponding type in the vehicle-end interface definition language based on the interface type of the cloud-end service interface and the preset interface corresponding relation.
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 client of the cloud end, and the service invocation module 730 is configured to:
generating the SOA service of the vehicle end corresponding to the cloud service through the vehicle end service interface and the client;
and calling the SOA service corresponding to the cloud service through the client.
In some example embodiments, based on the above scheme, the first end is a vehicle end and the second end is a cloud end, the first end service is an SOA service, and the second end service is a cloud service.
In some example embodiments, based on the above scheme, the interface conversion module 720 is configured to:
and determining the corresponding type of the cloud service interface in the cloud interface definition language based on the interface type of the vehicle-side service interface and the preset interface corresponding relation.
In some example embodiments, based on the above solution, the gateway stores a client of the SOA service, and the service invocation module 730 is configured to:
generating cloud service corresponding to the SOA service through the cloud service interface and the client of the SOA service;
and calling the cloud service corresponding to the SOA service through the client of the SOA service.
In some example embodiments, based on the above scheme, the cloud interface definition language is Franca interface definition language FIDL, and the vehicle-side interface definition language is an automobile open system architecture extensible markup language ARXML.
According to the technical solution in the example embodiment of fig. 7, on one hand, a first end service interface of a first end service is converted into a second end service interface based on a corresponding relationship between the first end service interface and a preset interface, so that mutual conversion between the first end service interface and the second end service interface can be realized; 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, so that the first end service and the second end service are mutually converted, the second end service such as a cloud end service can be efficiently called at the first end such as a vehicle end, the second end service can be called at the first end like the first end service, and the cloud end service and the vehicle end service can be called in a non-sensory mode.
It should be noted that, when the vehicle cloud communication device provided in the foregoing embodiment executes the vehicle cloud communication method, only the division of the functional modules is illustrated, and in practical applications, the functions may be distributed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules, so as to complete all or part of the functions described above.
In addition, the vehicle cloud communication device and the vehicle cloud communication method provided by the embodiment belong to the same concept, and the detailed implementation process is shown in the method embodiment and is not described herein again.
The embodiment of the application further provides a computer storage medium, where multiple instructions may be stored in the computer storage medium, where the instructions are suitable for being loaded by a processor and executing the vehicle cloud communication method according to the embodiment, and specific execution processes may refer to specific descriptions of the above embodiments and are not described herein again.
The embodiment of the present application further provides a computer program product, where at least one instruction is stored in the computer program product, and the at least one instruction is loaded by the processor and executes the vehicle cloud communication method according to the embodiment, and a specific execution process may refer to specific descriptions in the above embodiments, which is not described herein again.
The embodiment of the present application further provides a chip, where the chip is configured to execute the vehicle cloud communication method according to the foregoing embodiment, and specific execution processes may refer to specific descriptions of the foregoing embodiment, which are not described herein again.
In addition, please refer to fig. 8, which provides a schematic structural diagram of a vehicle-mounted communication device according to an embodiment of the present application. As shown in fig. 8, the in-vehicle communication apparatus 800 may include: at least one processor 801, at least one communication module 804, an input output interface 803, a memory 805, at least one communication bus 802.
Wherein, the communication bus 802 is used to realize connection 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 standard wireless interface.
The communication module 804 may optionally include a standard wired interface or a wireless interface (e.g., a WIFI interface).
The Memory 805 may include a Random Access Memory (RAM) or a Read-Only Memory (Read-Only Memory). Optionally, the memory 805 includes a non-transitory computer-readable medium. The memory 805 may be used to store instructions, programs, code sets, or instruction sets. The memory 805 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing the various method embodiments described above, and the like; the storage data area may store data and the like referred to in the above respective method embodiments. The memory 805 may optionally be at least one memory device located remotely from the processor 801 as previously described. As shown in fig. 8, the memory 805, which is a kind of computer storage medium, may include therein an operating system, a communication module, an input-output interface module, and a car cloud communication application.
In the vehicle-mounted communication device 800 shown in fig. 8, the input/output interface 803 is mainly used as an interface for providing input for a user and acquiring data input by the user; and the processor 801 may be configured to invoke the car cloud communication application stored in the memory 805, such that the processor 801 performs the steps in the car cloud communication method according to various exemplary embodiments of the present disclosure. For example, the processor 801 may perform the steps as shown in fig. 2: step S210, responding to a call request of a second end to a first end service of a first end, and acquiring a first end service interface of the first end service in a first end interface definition language; step S220, based on the first end service interface and the corresponding relation of the preset interface, converting the first end service interface into a second end service interface in a second end interface definition language; step S230, generating a second end service corresponding to the first end service based on the second end service interface, and invoking the second end service.
The foregoing is a schematic view of a vehicle-mounted communication device according to an embodiment of the present disclosure, and the vehicle-mounted communication device may be a C2C gateway, or may be another suitable device central gateway. It should be noted that the technical solution of the vehicle-mounted communication device and the technical solution of the vehicle cloud communication processing method belong to the same concept, and details that are not described in detail in the technical solution of the vehicle-mounted communication device can be referred to the description of the technical solution of the vehicle cloud communication processing method.
In the description of the embodiments of the present application, it should be understood that the terms "cloud end", "vehicle end", and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. In the description of the embodiments of the present application, it is noted that, unless explicitly stated or limited otherwise, "including" and "having" and any variants thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements but may alternatively include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. The specific meaning of the above terms in the present application can be understood in a specific case by those of ordinary skill in the art. In addition, in the description of the embodiments of the present application, "a plurality" means two or more unless otherwise specified. "and/or" describes the association relationship of the associated object, indicating that there may be three relationships, for example, a and/or B, which may indicate: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a read-only memory or a random access memory.
The above disclosure is only for the purpose of illustrating the preferred embodiments of the present application and is not intended to limit the scope of the present application, which is defined by the appended claims.
Claims (10)
1.A vehicle cloud communication method is applied to a gateway arranged in a vehicle end, wherein a preset interface corresponding relation is stored in the gateway, and the preset interface corresponding relation is a corresponding relation 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 comprises the following steps:
responding to a calling request of the second end to a first end service of the first end, and acquiring a first end service interface of the first end service in the first end interface definition language;
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 corresponding relation;
generating a second end service corresponding to the first end service based on the second end service interface, 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 the vehicle end and the second end is the cloud end.
2. The method of claim 1, wherein the first end is a cloud end and the second end is a vehicle end, and the converting the first end service interface into the second end service interface in the second end interface definition language based on the first end service interface and the preset interface correspondence comprises:
and determining the vehicle-end service interface of the corresponding type in the vehicle-end interface definition language based on the interface type of the cloud-end service interface and the preset interface corresponding relation.
3. The method of 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 Service Oriented Architecture (SOA) service, the gateway stores a client of the first end, and the generating a second end service corresponding to the first end service based on the second end service interface calls the second end service comprises:
generating the SOA service of the vehicle end corresponding to the cloud service through the vehicle end service interface and the client;
and calling the SOA service corresponding to the cloud service through the client.
4. The method of claim 1, wherein 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.
5. The method according to claim 4, wherein the converting the first end service interface into the second end service interface in the second end interface definition language based on the first end service interface and the preset interface correspondence includes:
and determining the corresponding type of the cloud service interface in the cloud interface definition language based on the interface type of the vehicle-side service interface and the preset interface corresponding relation.
6. The method of claim 4, wherein the gateway stores a client of the SOA service, and wherein generating a second end service corresponding to the first end service based on the second end service interface and invoking the second end service comprises:
generating cloud service corresponding to the SOA service through the cloud service interface and the client of the SOA service;
and calling the cloud service corresponding to the SOA service through the client of the SOA service.
7. The method of claim 1, wherein the cloud interface definition language is Franca Interface Definition Language (FIDL), and the vehicle end interface definition language is the automobile open systems architecture extensible markup language (ARXML).
8. The vehicle cloud communication device is applied to a gateway arranged in a vehicle end, the gateway stores a preset interface corresponding relationship, the preset interface corresponding relationship is a corresponding 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 comprises:
the interface acquisition module is used for responding to a calling request of the second end to a first end service of the first end, and acquiring a first end service interface of the first end service in the first end interface definition language;
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 for generating a second end service corresponding to the first end service based on the second end service interface 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 the vehicle end and the second end is the cloud end.
9. A computer storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform the steps of the method according to any of claims 1 to 7.
10. An in-vehicle communication apparatus characterized by comprising: a processor and a memory, the memory storing a computer program adapted to be loaded by the processor and to perform the steps of the method according to any of claims 1 to 7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211352957.3A CN115834702A (en) | 2022-11-01 | 2022-11-01 | Vehicle cloud communication method and device, storage medium and vehicle-mounted communication equipment |
| PCT/CN2023/125187 WO2024093674A1 (en) | 2022-11-01 | 2023-10-18 | Vehicle-to-cloud communication method and apparatus, storage medium, and vehicle-mounted communication device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211352957.3A CN115834702A (en) | 2022-11-01 | 2022-11-01 | Vehicle cloud communication method and device, storage medium and vehicle-mounted communication equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115834702A true CN115834702A (en) | 2023-03-21 |
Family
ID=85525995
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211352957.3A Pending CN115834702A (en) | 2022-11-01 | 2022-11-01 | Vehicle cloud communication method and device, storage medium and vehicle-mounted communication equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN115834702A (en) |
| WO (1) | WO2024093674A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2024093674A1 (en) * | 2022-11-01 | 2024-05-10 | 长城汽车股份有限公司 | Vehicle-to-cloud communication method and apparatus, storage medium, and vehicle-mounted communication device |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180281598A1 (en) * | 2017-04-04 | 2018-10-04 | Kuang-I Shu | Apparatuses and methods of an in-vehicle gateway system for monitoring and controling in-vehicle subsystems |
| CN109474912A (en) * | 2018-04-10 | 2019-03-15 | 西南大学 | The monitoring method and device of a kind of car borne gateway system and onboard subsystem |
| WO2020016976A1 (en) * | 2018-07-19 | 2020-01-23 | 三菱電機株式会社 | Communication system, in-vehicle device, information acquisition method, and information acquisition program |
| CN112104697A (en) * | 2018-05-31 | 2020-12-18 | 华为技术有限公司 | Data processing method, multi-cloud management system and related equipment |
| CN112153071A (en) * | 2020-09-30 | 2020-12-29 | 深圳市腾讯计算机系统有限公司 | Message sending method, device, gateway and storage medium |
| CN112738144A (en) * | 2019-10-28 | 2021-04-30 | 标致雪铁龙汽车股份有限公司 | Cloud communication system and method combined with vehicle distributed computing architecture and vehicle |
| CN114327401A (en) * | 2021-12-22 | 2022-04-12 | 奇瑞商用车（安徽）有限公司 | API development method, device, equipment and storage medium based on SOA architecture |
| CN114553608A (en) * | 2022-04-26 | 2022-05-27 | 云丁网络技术(北京)有限公司 | Method and device for accessing cloud platform |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106375738A (en) * | 2016-11-28 | 2017-02-01 | 东莞职业技术学院 | Intelligent vehicle video unmanned control device and intelligent vehicle video unmanned control system |
| CN113824795B (en) * | 2021-10-21 | 2024-07-26 | 畅索软件科技（上海）有限公司 | Communication method, device and system of vehicle end and cloud end |
| CN114553873B (en) * | 2022-02-27 | 2023-06-09 | 重庆长安汽车股份有限公司 | SOA-based vehicle-cloud cooperative control system, method and readable storage medium |
| CN114844930B (en) * | 2022-04-21 | 2023-06-06 | 重庆长安汽车股份有限公司 | Vehicle-end remote control method and system based on SOA architecture |
| CN115225449A (en) * | 2022-06-08 | 2022-10-21 | 广州汽车集团股份有限公司 | Message reporting method and system for SOA service oriented interface |
| CN115842868A (en) * | 2022-11-01 | 2023-03-24 | 长城汽车股份有限公司 | Interface data conversion method, device, storage medium and vehicle-mounted communication equipment |
| CN115834702A (en) * | 2022-11-01 | 2023-03-21 | 长城汽车股份有限公司 | Vehicle cloud communication method and device, storage medium and vehicle-mounted communication equipment |
-
2022
- 2022-11-01 CN CN202211352957.3A patent/CN115834702A/en active Pending
-
2023
- 2023-10-18 WO PCT/CN2023/125187 patent/WO2024093674A1/en unknown
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180281598A1 (en) * | 2017-04-04 | 2018-10-04 | Kuang-I Shu | Apparatuses and methods of an in-vehicle gateway system for monitoring and controling in-vehicle subsystems |
| CN109474912A (en) * | 2018-04-10 | 2019-03-15 | 西南大学 | The monitoring method and device of a kind of car borne gateway system and onboard subsystem |
| CN112104697A (en) * | 2018-05-31 | 2020-12-18 | 华为技术有限公司 | Data processing method, multi-cloud management system and related equipment |
| WO2020016976A1 (en) * | 2018-07-19 | 2020-01-23 | 三菱電機株式会社 | Communication system, in-vehicle device, information acquisition method, and information acquisition program |
| CN112738144A (en) * | 2019-10-28 | 2021-04-30 | 标致雪铁龙汽车股份有限公司 | Cloud communication system and method combined with vehicle distributed computing architecture and vehicle |
| CN112153071A (en) * | 2020-09-30 | 2020-12-29 | 深圳市腾讯计算机系统有限公司 | Message sending method, device, gateway and storage medium |
| CN114327401A (en) * | 2021-12-22 | 2022-04-12 | 奇瑞商用车（安徽）有限公司 | API development method, device, equipment and storage medium based on SOA architecture |
| CN114553608A (en) * | 2022-04-26 | 2022-05-27 | 云丁网络技术(北京)有限公司 | Method and device for accessing cloud platform |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2024093674A1 (en) * | 2022-11-01 | 2024-05-10 | 长城汽车股份有限公司 | Vehicle-to-cloud communication method and apparatus, storage medium, and vehicle-mounted communication device |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2024093674A1 (en) | 2024-05-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109889551B (en) | Method for accessing intelligent hardware to Internet of things cloud platform | |
| CN114553873B (en) | SOA-based vehicle-cloud cooperative control system, method and readable storage medium | |
| Chen et al. | Android/OSGi-based vehicular network management system | |
| US20240045657A1 (en) | System architecture for implementing dds communication based on autosar, communication method, and device | |
| CN105183452B (en) | Spring AOP-based remote protocol service system for monitoring power distribution equipment | |
| WO2022061804A1 (en) | Data transmission system, data transmission method, smart vehicle and device | |
| CN110650203B (en) | Data transmission method, device and system, computer storage medium and electronic equipment | |
| CN113723840B (en) | Internet of vehicles scene calculation method, device and system | |
| CN115842868A (en) | Interface data conversion method, device, storage medium and vehicle-mounted communication equipment | |
| WO2024093674A1 (en) | Vehicle-to-cloud communication method and apparatus, storage medium, and vehicle-mounted communication device | |
| CN115268405A (en) | Method, device, equipment and medium for powering on and powering off during starting of whole vehicle | |
| US20150046342A1 (en) | System and method for telematics service of vehicle | |
| US20180352040A1 (en) | Method for data transmission in a transportation vehicle communication network, transportation vehicle communication network, subscribers and transportation vehicle | |
| WO2024093731A1 (en) | Automotive open system architecture, data processing method and on-board device | |
| CN112083938B (en) | Vehicle and method for managing user setting menu thereof | |
| CN109669793B (en) | Object calling method in middleware process | |
| CN115794445B (en) | Data processing method, device and equipment based on flink and rule expression | |
| CN114374714A (en) | Construction method, topological structure and storage medium of centralized automobile electronic and electrical architecture | |
| CN115344347A (en) | Control method and system for algorithm application of edge computing device | |
| CN116996551B (en) | Vehicle-mounted service control system and method based on SOA central network controller | |
| Mihajlović et al. | Challenges of Integrating Machine Vision Algorithms Based on Franca IDL into Adaptive AUTOSAR Environment | |
| CN118138628A (en) | Service return value acquisition method and device, electronic equipment and storage medium | |
| CN118869660A (en) | Interaction method, device, equipment and medium supporting service-oriented software architecture | |
| CN115941749B (en) | Vehicle-mounted communication system and method and vehicle | |
| CN109582481A (en) | Transmission method, device, equipment and the storage medium of call result |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |