CN115865980A - SOA communication architecture, vehicle, construction method and storage medium - Google Patents
SOA communication architecture, vehicle, construction method and storage medium Download PDFInfo
- Publication number
- CN115865980A CN115865980A CN202211511969.6A CN202211511969A CN115865980A CN 115865980 A CN115865980 A CN 115865980A CN 202211511969 A CN202211511969 A CN 202211511969A CN 115865980 A CN115865980 A CN 115865980A
- Authority
- CN
- China
- Prior art keywords
- soa
- communication
- interface
- service
- architecture
- 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.)
- Withdrawn
Links
- 238000004891 communication Methods 0.000 title claims abstract description 159
- 238000010276 construction Methods 0.000 title abstract description 8
- 238000006243 chemical reaction Methods 0.000 claims abstract description 137
- 238000013507 mapping Methods 0.000 claims abstract description 4
- 238000000034 method Methods 0.000 claims description 30
- 238000012545 processing Methods 0.000 claims description 13
- 230000006978 adaptation Effects 0.000 claims description 8
- 238000001914 filtration Methods 0.000 claims description 8
- 230000008859 change Effects 0.000 claims description 6
- 238000004590 computer program Methods 0.000 claims description 5
- 239000000126 substance Substances 0.000 claims 1
- 238000005516 engineering process Methods 0.000 abstract description 2
- 230000006870 function Effects 0.000 description 8
- 230000008569 process Effects 0.000 description 8
- 238000011161 development Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000007935 neutral effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
- 238000002054 transplantation Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Landscapes
- Communication Control (AREA)
Abstract
The application relates to the technical field of intelligent cabins, in particular to an SOA communication architecture, a vehicle, a construction method and a storage medium, wherein the communication architecture comprises the following components: different levels of application and service are provided in a target software development framework; the conversion module is communicated with each layer through a communication interface defined based on Service Oriented Architecture (SOA), and comprises a communication middleware and an SOA service interface, wherein the SOA service interface is used for mapping an interface called by an upper layer into a corresponding SOA service interface so as to realize calling of SOA service interfaces by applications and/or services of different layers; the communication middleware is used for sending application data of the application and/or service data of the service to the Ethernet, receiving calling requests of other domain applications, and calling the SOA service interface to provide an interface to the outside based on the calling requests. Therefore, the problems that the SOA architecture cannot be applied to other systems in the related technology and the like are solved.
Description
Technical Field
The application relates to the technical field of intelligent cabins, in particular to an SOA communication architecture, a vehicle, a construction method and a storage medium.
Background
Under a traditional distributed electronic and electrical architecture, an automobile adopts a 'signal-oriented' software architecture, and each node in the automobile communicates through a CAN (Controller Area Network)/LIN (Local Interconnect Network) bus and other buses. With the rapid increase of the automobile intelligent upgrading requirement, the problems of poor expansibility, high transplanting cost and the like in the traditional signal-based communication network and software architecture are gradually highlighted.
Therefore, the architectural design for introducing the SOA (Service-Oriented Architecture) surface type Service is the mainstream solution at present, and the related art proposes the SOA Architecture on the instrument and the implementation method. However, the SOA architecture and implementation method on meters proposed by the related art cannot be applied to other systems due to system differences.
Disclosure of Invention
The application provides an SOA communication architecture, a vehicle, a construction method and a storage medium, which are used for solving the problems that the SOA architecture cannot be applied to other systems in the related art and the like.
An embodiment of a first aspect of the present application provides an SOA communication architecture, including: different levels of applications and services are provided in a software development framework; the conversion module is communicated with each layer through a communication interface defined based on Service Oriented Architecture (SOA), and comprises a communication middleware and an SOA service interface, wherein the SOA service interface is used for mapping an interface called by an upper layer into a corresponding SOA service interface so as to realize calling of the SOA service interface by applications and/or services of different layers; the communication middleware is used for sending the application data of the application and/or the service data of the service to the Ethernet, receiving calling requests of other domain applications, and calling the SOA service interface to provide an interface to the outside based on the calling requests.
According to the technical means, the method and the device for realizing the SOA service interface and the communication middleware can realize that the applications and services in different layers in the architecture can be accessed into the conversion module, realize the communication based on the SOA architecture with other domains, and simultaneously integrate the SOA service interface and the communication middleware in the conversion module in a unified mode instead of being distributed in different applications, thereby improving the overall development efficiency and facilitating management and control.
Further, the different layers include an application program APP layer and a local program Native layer, the conversion module includes a first conversion module and a second conversion module, a first communication interface is arranged between the first conversion module and the APP layer, and a second communication interface and a third communication interface are respectively arranged between the second conversion module and the first conversion module and between the second conversion module and the Native layer; the first conversion module is used for converting the call of the first communication interface into the call of the second communication interface; the second conversion module is integrated with a dynamic library of the communication middleware and a dynamic library of the SOA service interface code.
According to the technical means, the embodiment of the application can realize communication with the APP and the Native layer through the first conversion module and the second conversion module.
Further, the SOA service interface code includes a framework code of an SOA client and a framework code of an SOA service end.
Furthermore, the APP layer is integrated with a JAR package, and the Native layer is integrated with a so library to realize calling of the corresponding interface.
Further, the second conversion module further comprises: and the adaptation module is used for adapting service interfaces of different communication protocols in the communication middle.
According to the technical means, the second conversion module is further provided with an adaptation module, so that the service interfaces of different communication protocols can be intelligently adapted, and different communication middleware protocols can be compatible without changing an upper layer architecture.
Further, the conversion module further comprises: and the authority authentication module is used for configuring preset authority to the application and the service so as to realize the calling of an SOA service interface within the preset authority range.
According to the technical means, the authority authentication module is further arranged in the conversion module, corresponding authorities are configured for application and service, and the SOA conversion module is used for calling corresponding SOA service, so that the functional safety of the whole vehicle can be improved.
Further, the conversion module further comprises: and the filtering module is used for carrying out differential processing on the data to obtain change data and reporting the change data.
According to the technical means, the filtering module is further arranged in the conversion module in the embodiment of the application, and the data is subjected to differential processing, so that the processing overhead of the application can be reduced, and the robustness of the software is improved.
Furthermore, the SOA service interface is packaged with a calling code of the communication middleware to realize SOA communication.
According to the technical means, the calling code in the middle of communication can be packaged through the SOA service interface, and therefore SOA communication is achieved.
Further, the communication middleware supports a TCP/IP protocol stack.
Further, the communication middleware is used for serializing the SOA data and then sending the SOA data to a receiving end through a TCP/IP protocol stack, and the receiving end receives the data and conducts deserialization to obtain the SOA data.
In a second aspect of the present application, an embodiment provides a vehicle including an SOA communication architecture as described in the above embodiments.
An embodiment of a third aspect of the present application provides a method for constructing an SOA communication architecture, including the following steps: acquiring an implementation source code and SOA service definition of a communication middleware protocol stack; compiling implementation source codes of a communication middleware protocol stack into a dynamic link library, generating SOA service interface codes according to SOA service definition, compiling the SOA service interface codes into the dynamic library, and defining a communication interface according to the SOA service; and creating a conversion module according to the dynamic link library and the dynamic library, enabling the conversion module to comprise a communication middleware and an SOA service interface, and establishing communication between the conversion module and different layers providing applications and services in a target software development framework based on the communication interface.
Optionally, the different layers include an application APP layer and a Native layer of a local program, the APP layer is integrated with a JAR package, and the Native layer is integrated with a so library to implement the call of the corresponding interface.
A fourth aspect of the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor, so as to implement the SOA communication architecture building method according to the foregoing embodiment.
Therefore, the application has at least the following beneficial effects:
(1) The conversion module can be accessed to applications and services of different layers in the architecture, communication based on the SOA architecture with other domains is realized, and the SOA service interface and the communication middleware are integrated in the conversion module in a unified mode instead of being distributed in different applications, so that the overall development efficiency is improved, and management and control are facilitated.
(2) Communication with the APP and Native layers can be achieved through the first conversion module and the second conversion module.
(3) The second conversion module is also provided with an adaptation module which can intelligently adapt to service interfaces of different communication protocols and can be compatible with different communication middleware protocols under the condition of not changing an upper layer architecture.
(4) The conversion module is also provided with an authority authentication module, corresponding authorities are configured for application and service, and the SOA conversion module calls corresponding SOA service, so that the functional safety of the whole vehicle can be improved.
(5) The conversion module is also provided with a filtering module for carrying out differential processing on the data, so that the processing overhead of the application can be reduced, and the robustness of the software is improved.
Additional aspects and advantages of the present application will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the present application.
Drawings
The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
fig. 1 is a block diagram illustrating an SOA communication architecture according to an embodiment of the present application;
fig. 2 is a schematic block diagram of an SOA communication architecture according to an embodiment of the present application;
fig. 3 is a flowchart of a method for constructing an SOA communication architecture according to an embodiment of the present application;
fig. 4 is a flowchart of a method for constructing an SOA communication architecture according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary and intended to be used for explaining the present application and should not be construed as limiting the present application.
The SOA is a software architecture and is a software design method and idea at the same time. It splits the different functional units (services) of an application, linking them by well-defined interfaces and protocols. The interfaces are defined in a neutral manner, independent of the hardware platform, operating system and programming language that implements the services, which allows services in building a wide variety of systems to interact in a unified and universal manner.
The SOA is a software foundation for realizing software defined automobile, and the automobile field adopts the SOA to accelerate the interconnection of the automobile and the Internet and greatly improve the user experience of entertainment audio-visual entertainment function. The vehicle machine is a main entrance for vehicle application operation, and Android OS is the mainstream at present in the selection of the vehicle machine system. Therefore, how the Android system vehicle and other domains (such as a vehicle body domain, a self-driving domain, and the like) communicate based on the SOA architecture is a problem that must be faced.
The SOA communication architecture, vehicle, construction method, and storage medium of the embodiments of the present application are described below with reference to the drawings. In order to solve the problems of poor expansibility and high transplantation cost in the conventional signal-based communication network and software architecture, the application provides an SOA communication architecture, in which a communication architecture is constructed based on an SOA, so that applications and services on different layers in a system architecture such as an Android architecture can be accessed to an SOA conversion module, communication with other domains based on the SOA architecture can be realized, and an SOA service interface and a communication middleware are integrated in the conversion module in a unified manner, thereby improving the overall development efficiency and facilitating management and control. Therefore, the problems that the SOA architecture cannot be applied to other systems in the related technology and the like are solved.
It should be noted that the SOA communication architecture in the following embodiments may be applied to multiple operating systems such as an Android system or a Linux system, and is not particularly limited to the Android system.
Fig. 1 is a SOA communication architecture according to an embodiment of the present application, including: different layers and conversion modules for providing applications and services are provided in the target software development framework.
The conversion module is communicated with each layer through a communication interface defined based on Service Oriented Architecture (SOA), and comprises a communication middleware and an SOA service interface, wherein the SOA service interface is used for mapping an interface called by an upper layer into a corresponding SOA service interface so as to realize calling of SOA service interfaces by applications and/or services of different layers; the communication middleware is used for sending application data of the application and/or service data of the service to the Ethernet, receiving calling requests of other domain applications, and calling the SOA service interface to provide an interface to the outside based on the calling requests.
Wherein the application and the service correspond to different application units, which may be callers of the SOA service, such as a vehicle setting application; it is also possible that the provider of the SOA service, such as a music application, provides music-controlled services to the outside. Meanwhile, the applications and services are divided according to a system architecture, for example, an Android system architecture, and may exist in different layers of the system architecture, such as APP, framework, native.
The conversion module communicates with different layers through a communication interface defined based on service oriented architecture SOA service; the conversion module comprises communication middleware and an SOA service interface.
And the SOA service interface is internally packaged with calling codes of the communication middleware to realize SOA communication.
It can be understood that the conversion module is a uniform access way for SOA data in a system SOA communication architecture, and the conversion module calls the SOA service interface, whereas the conversion module calls the exposed interface of the application by the application in other domains.
In the embodiment of the application, different layers include an application program APP layer and a local program Native layer, the conversion module includes a first conversion module and a second conversion module, a first communication interface is arranged between the first conversion module and the APP layer, and a second communication interface and a third communication interface are respectively arranged between the second conversion module and the first conversion module and between the second conversion module and the Native layer; the first conversion module is used for converting the call of the first communication interface into the call of the second communication interface; the second conversion module is integrated with a dynamic library of communication middleware and a dynamic library of SOA service interface codes.
It can be understood that the embodiment of the present application mainly divides different layers into an application program APP layer and a local program Native layer. The APP layer is integrated with a JAR package, and the Native layer is integrated with a so library to realize calling of the corresponding interface.
The first conversion module can be understood as an SOA conversion JAVA module, the second conversion module can be understood as an SOA conversion Native module, and the first conversion module and the second conversion module exist in two independent process forms on an Android system.
And a first conversion module (namely an SOA conversion JAVA module) exists in an independent service process on the Android system and is mainly realized by Java. The module is upwards connected with an Android APP application and communicates with the Android APP through an AIDL (Android Interface Definition Language). And the SOA conversion JAVA module is downwards connected with the SOA conversion Native module, and the SOA conversion JAVA module and the SOA conversion Native module are communicated by HIDL. And the SOA conversion JAVA module converts the call of the SOA Java interface into the call of the SOA Native interface.
And a second conversion module (namely an SOA conversion Native module) exists in an independent process form on the Android system and is mainly realized by C + +/C. The module integrates a dynamic library of the communication middleware and a dynamic library of the SOA service interface codes, and the SOA conversion Native module can digest most of variation influence on the SOA conversion Native module when the communication middleware and the SOA service interface codes are changed. The SOA conversion Native module maps the interface called by the upper layer into the calling of the corresponding SOA service interface, and the calling of the communication middleware is packaged in the SOA service interface, so that the SOA communication is realized.
In an embodiment of the present application, the second conversion module further includes: and the adaptation module is used for adapting service interfaces of different communication protocols in the middle of communication.
It can be understood that the second conversion module further has a protocol intelligent adaptation module, which can intelligently adapt the DDS protocol service interface and the SOME/IP protocol service interface, and can be compatible with different communication middleware protocols without changing the upper layer architecture.
In an embodiment of the present application, the conversion module further includes: and the authority authentication module is used for configuring preset authority to the application and the service so that the application and the service realize the calling of the SOA service interface within a preset authority range.
It can be understood that the conversion module is also provided with an authority authentication module, corresponding authorities are required to be configured for application and service, and the corresponding SOA service can be called through the conversion module, otherwise, the conversion module rejects the calling, so that the functional safety of the whole vehicle can be improved.
In an embodiment of the present application, the conversion module further includes: and the filtering module is used for carrying out differential processing on the data to obtain change data and reporting the change data.
It can be understood that the conversion module further has a filtering module, and performs differential processing on some frequently transmitted data, reports changed data, and does not report unchanged data (a specific strategy is combined with an actual situation), so that processing overhead of applications can be reduced, and software robustness can be improved.
In the embodiment of the application, the SOA service interface code comprises a framework code of the SOA client and a framework code of the SOA service terminal.
It should be noted that the SOA service interface code is an SOA service framework code generated by a service definition, and is generally a C + +/C language, and the framework code is mainly composed of two parts, SOA Proxy and SOA skeletton. The SOA Proxy is a framework code of an SOA client, and the SOA Skeleton is a framework code of an SOA server; the framework code has a correlation with the communication middleware actually used.
It should be noted that the communication middleware described in the foregoing embodiment is a communication protocol between SOA services, and belongs to an application layer communication protocol. Currently, the mainstream communication Middleware on the vehicle is DDS (data distribution Service) data distribution Service, SOME/IP (Scalable Service-organized Middleware over IP). Both DDS and SOME/IP allow applications to communicate using a publish/subscribe mode and a service request/reply mode (RPC). Currently, DDS and SOME/IP protocol libraries are implemented primarily in C + +/C code.
In the embodiment of the application, the communication middleware can support a TCP/IP protocol stack, the communication middleware is used for serializing SOA data and then sending the SOA data to a receiving end through the TCP/IP protocol stack, and the receiving end receives the data and conducts deserialization to obtain the SOA data.
It can be understood that the communication middleware is responsible for serializing the SOA data and then sending the SOA data to the receiving end through the TCP/IP protocol stack, and the receiving end receives the SOA data and performs deserialization.
In summary, the communication middleware is configured to send application data of the application and/or service data of the service to the ethernet, receive a call request of an application in another domain, and call the SOA service interface to provide an interface to the outside based on the call request. The system in the vehicle transmits through the Ethernet, each system supports a TCP/IP protocol stack, and the communication middleware sends data to the Ethernet through the TCP/IP protocol stack.
As shown in fig. 2, the SOA communication architecture includes the following units:
1. communication middleware, a communication protocol between SOA services, belongs to an application layer communication protocol. At present, the main communication Middleware on a vehicle is Data Distribution Service (DDS), service-aware Middleware (SOME/IP), which all support a TCP/IP protocol stack. And the communication middleware is responsible for serializing the SOA data and then sending the serialized SOA data to the receiving end through the TCP/IP protocol stack, and the receiving end receives the SOA data and performs deserialization. Both DDS and SOME/IP allow applications to communicate using a publish/subscribe mode and a service request/reply mode (RPC). Currently, DDS and SOME/IP protocol libraries are implemented primarily in C + +/C code.
2. The SOA service interface code is an SOA service framework code generated by service definition and mainly comprises two parts, namely SOA Proxy and SOA Skeleton. The SOA Proxy is a framework code of an SOA client, and the SOA Skeleton is a framework code of an SOA server; the service interface code has certain correlation with the communication middleware, does not contain main logic for realizing functions, and has regularity, so that the code can be automatically generated by using a uniform template. The SOA service is designed with a uniform template, which comprises a service name, a method type, an input parameter, an output parameter and the like. In particular implementations, the SOA service interface code typically exists in the form of a library.
3. The application or service corresponds to different business units, which may be users of SOA service, such as vehicle setting application, and the vehicle window SOA service of a vehicle body domain is triggered and called by clicking a vehicle window control button on the vehicle setting application to realize functions of closing and opening a vehicle window; it is also possible that the application is a provider of SOA services, such as music applications, providing music-controlled services to the outside. Meanwhile, according to the Android architecture division, the applications or services may exist in different layers of the Android architecture, such as APP, framework, native, and the like, and here, the applications or services are mainly divided into two types, framework and above APP and Native.
4. And the SOA conversion module is an SOA data uniform access path in the Android SOA communication architecture. Calling of the SOA service interface by the application/service is realized through the SOA conversion module; otherwise, through the SOA conversion module, the application of other domains can call the interface provided by the SOA service interface. Applications/services may exist in different levels of the Android architecture, and therefore, the SOA transition module needs to be able to satisfy the access of applications/services in different levels of the architecture. According to the foregoing classification, the SOA conversion module includes the following two sub-modules:
(1) And the SOA converts a Native module, and the module exists in an independent process form on an Android system and is mainly realized by C + +/C. The module integrates a dynamic library of the communication middleware and a dynamic library of the SOA service interface codes, and the SOA conversion Native module can digest most of variation influence on the SOA conversion Native module when the communication middleware and the SOA service interface codes are changed. The SOA conversion Native module maps the interface called by the upper layer into the calling of the corresponding SOA service interface, and the calling of the communication middleware is packaged in the SOA service interface, so that the SOA communication is realized.
(2) And the SOA converts the JAVA module, and the module exists in a single service process on the Android system and is mainly realized by Java. The module upwards connects to an Android APP application and communicates with the Android APP through an AIDL (Android Interface Definition Language). And the SOA conversion JAVA module is downwards connected with the SOA conversion Native module, and the SOA conversion JAVA module and the SOA conversion Native module are communicated by HIDL. And the SOA conversion JAVA module converts the call of the SOA Java interface into the call of the SOA Native interface.
5. And the Ethernet is used for transmitting data among the systems in the vehicle through the Ethernet. Further, each system supports a TCP/IP protocol stack through which communication middleware sends data onto the ethernet.
Furthermore, an SOA JAVA API is defined according to SOA service definition, is a communication interface between an SOA conversion Java module and an Android APP, has a one-to-one correspondence relationship with the SOA service interface, and has some differences in parameter data types in consideration of different implementation languages;
furthermore, an SOA Native API is defined according to the SOA service definition, is a communication interface between the SOA conversion Native module and the SOA conversion Java module and between the SOA conversion Native module and Native application, and has a one-to-one correspondence relationship with the SOA service interface.
Furthermore, the SOA conversion Native module is also provided with a protocol intelligent adaptation module which can be intelligently adapted to the DDS protocol service interface and the SOME/IP protocol service interface, so that different communication middleware protocols can be compatible without changing the upper layer architecture.
The SOA conversion module is also provided with an authority authentication module, corresponding authority is required to be configured for application/service, the corresponding SOA service can be called through the SOA conversion module, otherwise, the SOA conversion module rejects the calling, and therefore the functional safety of the whole vehicle can be improved.
The SOA conversion module is also provided with a data filtering module, differential processing is carried out on some frequently sent data, changed data are reported, and unchanged data are not reported (a specific strategy is combined with an actual situation), so that the processing overhead of application can be reduced, and the software robustness is improved.
According to the SOA communication architecture provided by the embodiment of the application, the applications and services of different layers in the architecture can be accessed to the conversion module, the communication with other domains based on the SOA architecture is realized, and simultaneously, the SOA service interface and the communication middleware are integrated in the conversion module in a unified way instead of being distributed in different applications, so that the overall development efficiency is improved and the management and control are facilitated; communication with the APP and Native layers can be realized through the first conversion module and the second conversion module; the second conversion module is also provided with an adaptation module which can be intelligently adapted to service interfaces of different communication protocols and can be compatible with different communication middleware protocols under the condition of not changing an upper layer architecture; the conversion module is also provided with an authority authentication module, corresponding authorities are configured for application and service, and the SOA conversion module calls corresponding SOA service, so that the functional safety of the whole vehicle can be improved; the conversion module is also provided with a filtering module for carrying out differential processing on the data, so that the processing overhead of the application can be reduced, and the robustness of the software is improved.
The embodiment of the application also provides a vehicle, which comprises the SOA communication architecture.
Next, referring to the attached drawings, a flowchart of a method for constructing an SOA communication architecture according to an embodiment of the present application is provided.
As shown in fig. 3, the SOA communication architecture construction method includes the following steps:
in step S101, an implementation source code and an SOA service definition of a communication middleware protocol stack are acquired.
In step S102, the implementation source code of the communication middleware protocol stack is compiled into a dynamic link library, an SOA service interface code is generated according to the SOA service definition, the SOA service interface code is compiled into the dynamic library, and a communication interface is defined according to the SOA service.
According to the embodiment of the application, android NDK can be used for compiling the implementation source code of a communication middleware protocol stack into a shared library, namely a dynamic link library; automatically generating SOA service interface codes according to the SOA service definition, and compiling the SOA service interface codes into a dynamic library; and defining communication interfaces, namely an SOA Native API and an SOA JAVA API according to the SOA service.
In step S103, a conversion module is created according to the dynamic link library and the dynamic library, such that the conversion module includes a communication middleware and an SOA service interface, and communication between the conversion module and different layers providing applications and services in the target software development framework is established based on the communication interface.
It is understood that the conversion module can be created according to the dynamic link library and the dynamic library in the embodiment of the application.
For example, an SOA conversion Native module is created, the Native module comprises an interface conversion unit, and the interface conversion unit is responsible for converting an SOA service interface into an interface for communication between the Native module and external applications (an SOA conversion Java module and Native layer applications); the Native module integrates a DDS dynamic library and an SOA dynamic library in a linked mode; and creating an SOA conversion Java module which comprises an interface conversion unit and converts the SOA Java API called by the Android application into an SOA Native API.
In the embodiment of the application, different layers comprise an application program APP layer and a local program Native layer, the APP layer is integrated with a JAR package Native layer and is integrated with a so library, and calling of corresponding interfaces is achieved.
A method for constructing an SOA communication architecture is described below by using an embodiment, as shown in fig. 4, including the following steps:
s1, compiling the implementation source code of a communication middleware protocol stack into a shared library, namely a dynamic link library, by using an Android NDK.
And S2, automatically generating SOA service interface codes according to the SOA service definition, and compiling the SOA service interface codes into a dynamic library.
And S3, defining the SOA Native API and the SOA JAVA API according to the SOA service, and generating an SOA JAVA API Jar and an SOA Native API so library according to the definition.
S4, establishing an SOA conversion Native module, wherein the Native module comprises an interface conversion unit which is responsible for converting an SOA service interface into an interface for communication between the Native module and external applications (an SOA conversion Java module and Native layer applications); and the Native module integrates a DDS dynamic library and an SOA service dynamic library in a linked mode.
And S5, creating an SOA conversion Java module which comprises an interface conversion unit and converts the SOA Java API called by the Android application into an SOA Native API.
S6, integrating the Android APP with the JAR package to realize calling of the corresponding interface; and Native application integrates an SOA Native API so library to realize calling of a corresponding interface.
It should be noted that the foregoing explanation of the embodiment of the SOA communication architecture is also applicable to the SOA communication architecture construction method of the embodiment, and the embodiments may refer to each other.
According to the method for constructing the SOA communication architecture, the applications/services on different layers in the Android architecture can be accessed to the SOA conversion module, and the communication with other domains based on the SOA architecture is realized; meanwhile, the SOA service interface and the communication middleware are integrated in the module in a unified mode instead of being distributed in different applications for respective integration, and the method has positive significance for improving the overall development efficiency and controlling the function development process based on the SOA architecture.
The embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the SOA communication architecture building method as above is implemented.
In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or N embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or to implicitly indicate the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the feature. In the description of the present application, "N" means at least two, e.g., two, three, etc., unless specifically limited otherwise.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more N executable instructions for implementing steps of a custom logic function or process, and alternate implementations are included within the scope of the preferred embodiment of the present application in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present application.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. If implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are well known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a programmable gate array, a field programmable gate array, or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
Although embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present application, and that variations, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present application.
Claims (14)
1. An SOA communication architecture, comprising:
different levels of application and service are provided in a target software development framework;
the conversion module is communicated with each layer through a communication interface defined based on Service Oriented Architecture (SOA) service and comprises communication middleware and an SOA service interface,
the SOA service interface is used for mapping an interface called by an upper layer into a corresponding SOA service interface so as to realize calling of the SOA service interface by applications and/or services of different layers; the communication middleware is used for sending the application data of the application and/or the service data of the service to the Ethernet, receiving calling requests of other domain applications, and calling the SOA service interface to provide an interface to the outside based on the calling requests.
2. The architecture of claim 1, wherein the different layers include an application program APP layer and a local program Native layer, the conversion module includes a first conversion module and a second conversion module, a first communication interface is disposed between the first conversion module and the APP layer, and a second communication interface and a third communication interface are disposed between the second conversion module and the first conversion module and the Native layer, respectively; wherein the content of the first and second substances,
the first conversion module is used for converting the call of the first communication interface into the call of the second communication interface; the second conversion module is integrated with a dynamic library of the communication middleware and a dynamic library of the SOA service interface code.
3. The architecture of claim 2, wherein the SOA service interface code comprises framework code for a SOA client and framework code for a SOA server.
4. The architecture of claim 2, wherein the APP layer is integrated with JAR package, and the Native layer is integrated with so library to realize calling of corresponding interface.
5. The architecture of claim 2, wherein the second conversion module further comprises:
and the adaptation module is used for adapting service interfaces of different communication protocols in the communication middle.
6. The architecture of claim 1, wherein the conversion module further comprises:
and the authority authentication module is used for configuring preset authority to the application and the service so as to realize the calling of an SOA service interface within the preset authority range.
7. The architecture of claim 1, wherein the conversion module further comprises:
and the filtering module is used for carrying out differential processing on the data to obtain change data and reporting the change data.
8. The architecture of claim 1, wherein invocation code of the communication middleware is encapsulated in the SOA service interface to implement SOA communication.
9. The architecture of claim 1, wherein the communication middleware supports a TCP/IP protocol stack.
10. The architecture of claim 1, wherein the communication middleware is configured to serialize SOA data and send the serialized SOA data to a receiving end through a TCP/IP protocol stack, and the receiving end receives the data and deserializes the data to obtain the SOA data.
11. A vehicle comprising an SOA communication architecture according to any of claims 1-10.
12. A method for constructing an SOA communication architecture is characterized by comprising the following steps:
acquiring an implementation source code and SOA service definition of a communication middleware protocol stack;
compiling implementation source codes of a communication middleware protocol stack into a dynamic link library, generating SOA service interface codes according to SOA service definition, compiling the SOA service interface codes into the dynamic library, and defining a communication interface according to the SOA service;
and establishing a conversion module according to the dynamic link library and the dynamic library, enabling the conversion module to comprise a communication middleware and an SOA service interface, and establishing communication between the conversion module and different layers providing applications and services in a software development framework based on the communication interface.
13. The method of claim 12, wherein the different layers comprise an application APP layer and a Native layer, the APP layer is integrated with JAR packages, and the Native layer is integrated with so libraries to enable invocation of corresponding interfaces.
14. A computer-readable storage medium on which a computer program is stored, the program being executable by a processor for implementing the SOA communication architecture building method according to any one of claims 12-13.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211511969.6A CN115865980A (en) | 2022-11-29 | 2022-11-29 | SOA communication architecture, vehicle, construction method and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211511969.6A CN115865980A (en) | 2022-11-29 | 2022-11-29 | SOA communication architecture, vehicle, construction method and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115865980A true CN115865980A (en) | 2023-03-28 |
Family
ID=85667822
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211511969.6A Withdrawn CN115865980A (en) | 2022-11-29 | 2022-11-29 | SOA communication architecture, vehicle, construction method and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115865980A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104932895A (en) * | 2015-06-26 | 2015-09-23 | 南京邮电大学 | Middleware based on SOA (Service-Oriented Architecture) and information publishing method thereof |
| CN105721562A (en) * | 2016-01-28 | 2016-06-29 | 武汉大学 | Proxy-based heterogeneous service calling method and collaborative calling system |
| CN113407362A (en) * | 2021-06-16 | 2021-09-17 | 武汉光庭信息技术股份有限公司 | SOMEIP communication intermediate layer implementation method and system based on SOA architecture of vehicle-mounted Android system |
| CN113806109A (en) * | 2021-09-15 | 2021-12-17 | 诚迈科技（南京）股份有限公司 | Cabin system for realizing SOA (service oriented architecture) based on ROS2 and operation method thereof |
| CN114172938A (en) * | 2022-02-10 | 2022-03-11 | 诚迈科技（南京）股份有限公司 | Method and system for realizing SOA (service oriented architecture) of intelligent cabin and intelligent automobile |
| US20220150317A1 (en) * | 2020-11-12 | 2022-05-12 | Harman International Industries, Incorporated | Universal software communication bus |
-
2022
- 2022-11-29 CN CN202211511969.6A patent/CN115865980A/en not_active Withdrawn
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104932895A (en) * | 2015-06-26 | 2015-09-23 | 南京邮电大学 | Middleware based on SOA (Service-Oriented Architecture) and information publishing method thereof |
| CN105721562A (en) * | 2016-01-28 | 2016-06-29 | 武汉大学 | Proxy-based heterogeneous service calling method and collaborative calling system |
| US20220150317A1 (en) * | 2020-11-12 | 2022-05-12 | Harman International Industries, Incorporated | Universal software communication bus |
| CN113407362A (en) * | 2021-06-16 | 2021-09-17 | 武汉光庭信息技术股份有限公司 | SOMEIP communication intermediate layer implementation method and system based on SOA architecture of vehicle-mounted Android system |
| CN113806109A (en) * | 2021-09-15 | 2021-12-17 | 诚迈科技（南京）股份有限公司 | Cabin system for realizing SOA (service oriented architecture) based on ROS2 and operation method thereof |
| CN114172938A (en) * | 2022-02-10 | 2022-03-11 | 诚迈科技（南京）股份有限公司 | Method and system for realizing SOA (service oriented architecture) of intelligent cabin and intelligent automobile |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7925710B2 (en) | Simultaneous API exposure for messages | |
| US7167861B2 (en) | Mobile application service container | |
| US8091097B2 (en) | Distributed virtual machine architecture | |
| US20080140857A1 (en) | Service-oriented architecture and methods for direct invocation of services utilizing a service requestor invocation framework | |
| US6484214B1 (en) | Method for distributed object communications based on dynamically acquired and assembled software components | |
| US20060029054A1 (en) | System and method for modeling and dynamically deploying services into a distributed networking architecture | |
| US20050267979A1 (en) | Services layer model for providing standards-based communications | |
| US6282579B1 (en) | Method for supporting address interaction between a first entity and a second entity, converter for address interaction, and computer system | |
| US20020138659A1 (en) | Method and system for application development and a data processing architecture utilizing destinationless messaging | |
| US20080109828A1 (en) | Application component communication apparatus of sca-based system and method thereof | |
| US8650573B2 (en) | System and method for controlling priority in SCA multi-component and multi-port environment | |
| EP2215547A1 (en) | Integrating service-orientated architecture applications with a common messaging interface | |
| US20240045657A1 (en) | System architecture for implementing dds communication based on autosar, communication method, and device | |
| CN106790084A (en) | A kind of heterogeneous resource integrated framework and its integrated approach based on ICE middlewares | |
| Leitão et al. | Integration patterns for interfacing software agents with industrial automation systems | |
| Yan et al. | Researching and Designing the Architecture of E-government Based on SOA | |
| US20200278891A1 (en) | Dynamic Load Balancing In Network Centric Process Control Systems | |
| WO2024093731A1 (en) | Automotive open system architecture, data processing method and on-board device | |
| CN115865980A (en) | SOA communication architecture, vehicle, construction method and storage medium | |
| US8464218B2 (en) | Method port arrangement and configuration method thereof for robot software component | |
| CN103684904A (en) | Tri-networks integration network monitoring system based on IP | |
| JP2002259126A (en) | Software constituent for distributed control system, and method for designing control system | |
| De et al. | Towards Translation of Semantics of Automotive Interface Description Models from Franca to AUTOSAR Frameworks: An Approach using Semantic Synergies | |
| CN116996551B (en) | Vehicle-mounted service control system and method based on SOA central network controller | |
| CN111399808B (en) | Implementation method supporting customization of waveform component interface |
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 | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20230328 |