Service-oriented architecture system, service method, device, equipment and medium

Abstract

The invention relates to the technical field of vehicle hardware data processing, and discloses a service-oriented architecture system, a service method, a service device, equipment and a medium. The system comprises: a data layer, wherein the data layer comprises hardware data of each controller of the vehicle; the packaging service unit is used for acquiring each piece of hardware data from the data layer and packaging each piece of hardware data into a plurality of different service interfaces according to different characteristics of each piece of hardware data; the application implementation environment layer is used for acquiring each service interface from the encapsulation service unit based on an interface transmission protocol and storing the service interfaces; and the application layer is used for calling a target service interface from the application implementation environment layer and acquiring target hardware data packaged in the target service interface according to the target address identifier of the target service interface. The development complexity of the software architecture can be reduced, and the development efficiency can be improved.

Description

Background Art

[0002] With the update and iteration of the vehicle ECU (Electronic Control Unit), the number of its hardware registers has increased significantly, the ECU can provide more and more hardware data, and the business coupling is tighter. In the existing processing system, the IO abstraction layer or other specialized applications are often used to process the hardware data, and then send it to the functional domain application through the middle layer. The above method requires the design of an upper-level application to process the hardware data. For different developers, the designed architecture and the corresponding hardware data processing logic are different, which results in non-standardization of its interface development and architecture design. The resulting software development efficiency is poor, and additional functional safety assessment and design are required. The security of data during transmission cannot be well guaranteed. Summary of the invention

[0003] The present application provides a system, service method, device, equipment, and medium for a service architecture. The encapsulation service unit can encapsulate the hardware data into multiple different service interfaces according to the different characteristics of the hardware data, and then the application implementation environment layer obtains and stores the service interfaces from the encapsulation service unit based on the interface transmission protocol. In the application implementation environment layer, all service interfaces pass the security verification, so there is no need for developers to repeatedly perform functional safety assessment and design on the acquired hardware data. At the same time, by encapsulating the hardware data into multiple different service interfaces, the service interface development can be standardized in the existing SOA architecture. For developers, they can use the existing service interface for iteration without designing the application layer, which reduces the complexity of software development and improves development efficiency.

[0004] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by the practice of the present application.

[0005] According to one aspect of an embodiment of the present application, a service-oriented architecture system is provided for a vehicle, the system comprising:

[0006] A data layer, the data layer including hardware data of each controller of the vehicle;

[0007] An encapsulation service unit, the encapsulation service unit is used to obtain each of the hardware data from the data layer, and encapsulate each of the hardware data into a plurality of different service interfaces according to different characteristics between the hardware data, each of the service interfaces corresponds to hardware data of at least one characteristic, each of the service interfaces has an address identifier, and there is a corresponding relationship between the address identifier and the data address of the hardware data encapsulated in the service interface;

[0008] An application implementation environment layer, the application implementation environment layer is used to obtain and store each of the service interfaces from the encapsulation service unit based on an interface transmission protocol;

[0009] The application layer is used to call the target service interface from the application implementation environment layer, and obtain the target hardware data encapsulated in the target service interface according to the target address identifier of the target service interface.

[0010] In one embodiment of the present application, based on the aforementioned scheme, the system also includes a protocol layer, which is used to obtain each of the service interfaces from the encapsulation service unit, and the application implementation environment layer can obtain each of the service interfaces from the protocol layer based on the interface transmission protocol and store them.

[0011] In one embodiment of the present application, based on the aforementioned scheme, the encapsulation service unit includes: a data acquisition unit and a data processing unit, the data acquisition unit is used to obtain each of the hardware data from the data layer, and transmit each of the hardware data to the data processing unit; the data processing unit is used to perform classification and algorithm processing according to the characteristics of each of the hardware data to obtain each processed target data.

[0012] In one embodiment of the present application, based on the aforementioned scheme, the encapsulation service unit also includes an encapsulation unit, which is used to encapsulate each of the target data into each of the service interfaces, and to perform functional definitions based on the hardware characteristics of each of the target data, and transmit the defined service interfaces to the protocol layer.

[0013] In one embodiment of the present application, based on the aforementioned scheme, the data processing unit is also used to classify each hardware data into IO data and register data, and perform secondary classification based on the data characteristics of each IO data and the hardware characteristics of each register data to obtain each target data; the encapsulation unit is also used to perform different types of service interface encapsulation according to each target data after the secondary classification to obtain a first type of service interface, a second type of service interface and a third type of service interface; wherein the first type of service interface, the second type of service interface and the third type of service interface all correspond to different processing logics, and the first type of service interface, the second type of service interface and the third type of service interface all include multiple service interfaces.

[0014] In one embodiment of the present application, based on the aforementioned scheme, when the application layer calls the service interface, the service interface type corresponding to the service interface is obtained, and the hardware data corresponding to the service interface is obtained according to the address identifier of the service interface, and the hardware data is processed according to the processing logic corresponding to the service interface type.

[0015] According to one aspect of an embodiment of the present application, a service method for a service-oriented architecture is further provided. The method is executed in an encapsulation service unit in a service system for a service-oriented architecture as provided in the above embodiment. The method includes:

[0016] Obtain the hardware data of each controller in the data layer;

[0017] According to different characteristics of each of the hardware data, the hardware data are encapsulated into a plurality of different service interfaces, each of the service interfaces corresponds to hardware data of at least one characteristic, each of the service interfaces has an address identifier, and there is a corresponding relationship between the address identifier and the data address of the hardware data encapsulated in the service interface;

[0018] Each of the service interfaces is transmitted to the application implementation environment layer based on an interface transmission protocol, so that the application implementation environment layer stores each of the service interfaces for the application layer to call the target service interface.

[0019] According to one aspect of an embodiment of the present application, a service device oriented to a service architecture is provided, the device comprising: an acquisition unit for acquiring hardware data of each controller of a data layer; an encapsulation unit for encapsulating each hardware data into a plurality of different service interfaces according to different characteristics between each hardware data, each service interface corresponding to hardware data of at least one characteristic, each service interface having an address identifier, and a corresponding relationship between the address identifier and a data address of the hardware data encapsulated in the service interface; a transmission unit for transmitting each service interface to an application implementation environment layer based on an interface transmission protocol, so that the application implementation environment layer stores each service interface for the application layer to call a target service interface.

[0020] According to one aspect of an embodiment of the present application, a computer-readable storage medium is provided, on which a computer program is stored. The computer program includes executable instructions. When the executable instructions are executed by a processor, the service method of the service-oriented architecture as described in the above embodiment is implemented.

[0021] According to one aspect of an embodiment of the present application, an electronic device is provided, comprising: one or more processors; and a memory for storing executable instructions of the processors, wherein when the executable instructions are executed by the one or more processors, the one or more processors implement a service method of a service-oriented architecture as described in the above embodiments.

[0022] In the technical solution of the embodiment of the present application, the hardware data can be encapsulated into multiple different service interfaces according to the different characteristics of each hardware data by the encapsulation service unit, and then the application implementation environment layer obtains each service interface from the encapsulation service unit based on the interface transmission protocol and stores it. Among them, in the application implementation environment layer, all service interfaces pass the security verification, so there is no need for developers to repeatedly perform functional safety assessment and design on the acquired hardware data. At the same time, by encapsulating the hardware data into multiple different service interfaces, the service interface development can be standardized in the existing SOA architecture. For developers, they can use the existing service interface for iteration without designing the application layer, which reduces the complexity of software development and improves development efficiency.

[0023] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0025] Figure 1 A flowchart of a service method for a service-oriented architecture according to an embodiment of the present application;

[0026] Figure 2 A specific block diagram of a service system for a service-oriented architecture according to an embodiment of the present application;

[0027] Figure 3 A block diagram of a service device for a service-oriented architecture according to an embodiment of the present application;

[0028] Figure 4 is a schematic diagram of a system structure of an electronic device according to an embodiment of the present application;

[0029] Figure 5 It is a schematic diagram of various service interface types according to an embodiment of the present application. DETAILED DESCRIPTION

[0030] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be more comprehensive and complete and fully convey the concept of the example embodiments to those skilled in the art.

[0031] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present application. However, those skilled in the art will appreciate that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, known methods, devices, realizations or operations are not shown or described in detail to avoid blurring the various aspects of the application.

[0032] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or micro-control node devices.

[0033] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0034] It should be noted that the "multiple" mentioned in this article refers to two or more. "And / or" describes the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0035] The implementation details of the technical solution of the embodiment of the present application are described in detail below:

[0036] First of all, it should be noted that the service-oriented architecture service solution proposed in the embodiments of the present application can be applied to the relevant technical fields of vehicle hardware data processing. The problem with the current prior art is that the hardware data obtained from the data layer is processed through the IO abstraction layer in the existing AutoSAR software architecture, and after processing, the application layer needs to be functionally designed so that the application layer can read the processed hardware data. Therefore, the developer needs to design the interface for the application layer and the corresponding IO abstraction layer. The structure developed is non-standardized, and each different developer has different development standards. Therefore, the developed architecture has poor reusability.

[0037] In the embodiment of the present application, by adopting the functions of the SOA architecture, the acquired hardware data is encapsulated as a service interface to ensure standardization during the development process, so that different developers can unify standards through the encapsulation of the service interface when developing software, thereby reducing the efficiency of subsequent developers when improving or upgrading the architecture. After the service interface is transmitted to the application implementation environment layer, the application implementation environment layer can perform functional safety verification on the service interface, so there is no need for developers to perform security verification on the hardware data again.

[0038] According to one aspect of the present application, a service-oriented architecture system is provided for a vehicle, the system comprising:

[0039] A data layer, the data layer including hardware data of each controller of the vehicle;

[0040] An encapsulation service unit, the encapsulation service unit is used to obtain each of the hardware data from the data layer, and encapsulate each of the hardware data into a plurality of different service interfaces according to different characteristics between the hardware data, each of the service interfaces corresponds to hardware data of at least one characteristic, each of the service interfaces has an address identifier, and there is a corresponding relationship between the address identifier and the data address of the hardware data encapsulated in the service interface;

[0041] An application implementation environment layer, the application implementation environment layer is used to obtain and store each of the service interfaces from the encapsulation service unit based on an interface transmission protocol;

[0042] The application layer is used to call the target service interface from the application implementation environment layer, and obtain the target hardware data encapsulated in the target service interface according to the target address identifier of the target service interface.

[0043] Specifically, please refer to Figure 2 As shown, Figure 2This is a framework diagram of the entire system provided in the embodiment of the present application, wherein Hardware layer is the data layer described in the embodiment of the present application, HwDataAbstr is the encapsulation service unit described in the present application, BSW is the protocol layer, RTE is the application implementation environment layer, SWC A and SWC B are both application layers, wherein Coord is the data acquisition unit described in the present application, Alog / Classify is the data processing unit, and Adapt is the encapsulation unit.

[0044] By encapsulating the various hardware data into multiple different service interfaces according to the different characteristics between the various hardware data, each of the service interfaces corresponds to hardware data of at least one characteristic, that is, the hardware data of various characteristics can be classified into major categories and minor categories. For example, the major categories can be divided into body domain functions, and the minor categories can be divided into various functional categories under the body domain functions, such as windows, doors, etc. By encapsulating the hardware data of different functional characteristics into service interfaces of various different characteristics, when the corresponding data needs to be called, the target hardware data encapsulated in the target service interface can be obtained directly by calling the corresponding target service interface.

[0045] In one embodiment of the present application, the system further includes a protocol layer, which is used to obtain each of the service interfaces from the encapsulation service unit, and the application implementation environment layer can obtain and store each of the service interfaces from the protocol layer based on the interface transmission protocol.

[0046] Specifically, the protocol layer only has a transmission function and does not process the encapsulated service interface.

[0047] In one embodiment of the present application, the encapsulation service unit includes: a data acquisition unit and a data processing unit, the data acquisition unit is used to obtain each of the hardware data from the data layer and transmit each of the hardware data to the data processing unit; the data processing unit is used to classify and perform algorithm processing according to the characteristics of each of the hardware data to obtain each processed target data. The encapsulation service unit also includes an encapsulation unit, which is used to encapsulate each of the target data into each of the service interfaces, and to perform functional definitions based on the hardware characteristics of each of the target data, and transmit the defined each of the service interfaces to the protocol layer.

[0048] Specifically, the data acquisition unit is used to collect hardware data, and the data processing unit is used to classify and process common algorithms. The encapsulation unit is used to encapsulate and virtualize each hardware data into a Someip service interface, which includes three service types: Method, Event, and Filed, to achieve cross-core communication and interact with the multi-core system application (SWC).

[0049] The data processing unit is also used to classify each hardware data into IO data and register data, and perform secondary classification based on the data characteristics of each IO data and the hardware characteristics of each register data to obtain each target data; the encapsulation unit is also used to perform different types of service interface encapsulation according to each target data after secondary classification to obtain a first type of service interface, a second type of service interface and a third type of service interface; wherein the first type of service interface, the second type of service interface and the third type of service interface all correspond to different processing logics, and the first type of service interface, the second type of service interface and the third type of service interface all include multiple service interfaces.

[0050] Method, Event and Filed are the first type of service interface, the second type of service interface and the third type of service interface described in the embodiment of the present application. Each type of service interface may include multiple service interfaces. The corresponding interface functions may be as follows: Figure 5 As shown, Method is used to execute a service instruction, and you can choose whether to pay attention to the service result. For example, to turn on the headlights, you can ignore whether it is turned on and just execute the operation. You can also pay attention to whether the headlights are turned on and record it in the system to prompt the driver whether the headlights are turned on.

[0051] The service interface corresponding to Event is used to prompt certain functions, and Field is also used to execute certain functional instructions. Taking the collection of supply voltage by ECU power management as an example, the original value of the voltage ADC is collected, and the common de-jitter filtering algorithm (limiting filtering method / median value filtering method / recursive average filtering method) is used for processing. The platform is maximized to provide multi-algorithm processing of supply voltage Va / Vb / Vc. The commonly used voltages are periodically notified to the application layer in the form of Event, and the uncommon voltages are obtained by the application on demand in the form of Get Field.

[0052] When the application layer calls the service interface, the service interface type corresponding to the service interface is obtained, and the hardware data corresponding to the service interface is obtained according to the address identifier of the service interface, and the hardware data is processed according to the processing logic corresponding to the service interface type.

[0053] Hardware data can be classified into IO data and register data. Different types of hardware data correspond to different processing logics. Therefore, different target data can be functionally defined in the encapsulation unit. The subsequent application layer can obtain data according to the defined processing logic when calling the service interface.

[0054] (1) IO data: Taking the collection of supply voltage by ECU power management as an example, the virtualization module of this solution collects the original value of the voltage ADC, and uses common de-jitter filtering algorithms (limiting filtering method / median value filtering method / recursive average filtering method) for processing, and provides multi-algorithm processing of supply voltage Va / Vb / Vc with platform maximization design. Common voltages are notified to the upper layer periodically in the form of Event, and uncommon voltages are obtained by the application on demand in the form of Get Filed. Through the above method, the hardware data IO data is integrated in the early stage of ECU development, and the corresponding common service interface is designed in combination with development experience, the collection / write cycle and filtering algorithm are specified, and the application layer dynamically obtains / provides services according to business selection.

[0055] (2) Register data: As functional safety puts forward requirements for chip and peripheral safety, register data is more coupled with business during product development. This solution integrates ECU common registers (STM / RTC / GPT, etc.) and fault registers (MMFSR / HFSR), and virtualizes the data content provided by the hardware adaptation layer into a SomeIP service group. By abstracting register data through the above method, applications can focus more on the actual business demand interface without distinguishing between crystal oscillators and addresses of different registers, minimizing the impact of hardware and register changes.

[0056] The solution of the present invention does not require security design at the business layer (application). After the ECU hardware is virtualized as SomeIP service, it interacts with the RTE layer through the LdCom module, and uses AutoSAR's cross-core communication (IOC) and RTE exclusive domain protection to ensure the security of its hardware data transmission link. The multi-core transmission form of hardware data is consistent with AutoSAR SWC cross-core communication, which can achieve a higher functional safety level.

[0057] In the development of ECU embedded software, the application side processes hardware data and relies heavily on the hardware information in the chip manual, which has great disadvantages in standardization, generalization, and data protection. The technical solution of the present invention combines the SOA software design concept to design a data virtualization module, which effectively improves the software development speed and security, enhances the competitiveness of the company's products, realizes the platformization of software and hardware, improves the portability of software products, and reduces product development costs:

[0058] First, fast development speed: the application adds new hardware data requirements, and in order to adapt to the application interface, additional software modules need to be developed to process data, which affects the development iteration speed. Using the technical solution of the present invention, based on the AutoSAR standard SomeIP service interface for development, the application software development process can call standardized service functions, which helps parallel development and rapid integration of various functional domains, and improves the iteration speed of software products.

[0059] Second, high security: In a multi-core operating system, each core corresponds to an application layer described in this application, and hardware IO and register processing need to strictly consider data re-entry and cross-core data protection. Based on this design, the RTE data protection and interface re-entry queue of the AutoSAR architecture can be used, and ultimately a higher functional safety level can be achieved, improving the security of software development.

[0060] Platform solution to adapt to external needs and hardware changes: When developing traditional solutions, the application layer needs to consider the hardware data reading and writing design, and the software architecture after the chip is switched is repeatedly designed. Based on this solution, the hardware data processing is passed through the BSW layer, SomeIP and RTE layer to achieve the decoupling of the software interface and the hardware link to achieve the purpose of isolation, without changing the architectural design of the application implementation environment layer and the application layer. Only the encapsulation service unit needs to be rewritten, and the entire architecture has strong versatility.

[0061] According to one aspect of the present application, a service method for a service-oriented architecture is provided. Figure 1 The flowchart of the service method of the service-oriented architecture according to the embodiment of the present application is shown. The vehicle service capability verification method is executed in the encapsulation service unit in the service-oriented architecture system described above. The method includes at least steps 110 to 130, which are described in detail as follows:

[0062] In step 110, hardware data of each controller of the data layer is obtained.

[0063] Specifically, each controller is an ECU, i.e., an electronic control unit (Electronic Control Unit). Each of the hardware data has different characteristics, and the hardware data is encapsulated into a plurality of different service interfaces, each of which corresponds to hardware data of at least one characteristic, that is, the hardware data of various characteristics are classified into major categories and minor categories, such as major categories can be divided into body domain functions, and minor categories can be divided into various functional categories under body domain functions, such as windows, doors, etc. By encapsulating these hardware data of different functional characteristics into service interfaces of various characteristics, when the corresponding data needs to be called, the target hardware data encapsulated in the target service interface can be obtained directly by calling the corresponding target service interface.

[0064] In step 120, the various hardware data are encapsulated into a plurality of different service interfaces according to different characteristics between the various hardware data, each of the service interfaces corresponds to hardware data of at least one characteristic, and each of the service interfaces has an address identifier, and there is a corresponding relationship between the address identifier and the data address of the hardware data encapsulated in the service interface.

[0065] Specifically, when calling the target service interface, the application layer can obtain the corresponding target hardware data through the data address of the hardware data encapsulated in the target service interface, and the target hardware data can also be virtualized service data corresponding to the service interface.

[0066] In step 130, each of the service interfaces is transmitted to the application implementation environment layer based on the interface transmission protocol, so that the application implementation environment layer stores each of the service interfaces for the application layer to call the target service interface.

[0067] Specifically, the protocol layer may transmit each of the service interfaces to the application implementation environment layer through an interface transmission protocol, so that the application implementation environment layer stores each of the service interfaces for the application layer to call the target service interface.

[0068] In summary, in the technical solution of the embodiment of the present application, the encapsulation service unit can encapsulate the various hardware data into multiple different service interfaces according to the different characteristics between the various hardware data, and then the application implementation environment layer obtains and stores the various service interfaces from the encapsulation service unit based on the interface transmission protocol. Among them, in the application implementation environment layer, all service interfaces pass the security verification, so there is no need for developers to repeatedly perform functional safety assessment and design on the acquired hardware data. At the same time, by encapsulating the hardware data into multiple different service interfaces, in the existing SOA architecture, the service interface development can be standardized. For developers, they can use the existing service interface for iteration without designing the application layer, which reduces the complexity of software development and improves development efficiency.

[0069] Figure 3 This is a block diagram of a service device 300 oriented to a service architecture according to an embodiment of the present application. According to a service device 300 oriented to a service architecture according to an embodiment of the present application, the device 300 includes: an acquisition unit 301, an encapsulation unit 302, and a transmission unit 303.

[0070] An acquisition unit 301 is used to acquire hardware data of each controller of the data layer;

[0071] The encapsulation unit 302 is used to encapsulate the hardware data into a plurality of different service interfaces according to different characteristics of the hardware data, each of the service interfaces corresponds to hardware data of at least one characteristic, each of the service interfaces has an address identifier, and there is a corresponding relationship between the address identifier and the data address of the hardware data encapsulated in the service interface;

[0072] The transmission unit 303 is used to transmit each of the service interfaces to the application implementation environment layer based on the interface transmission protocol, so that the application implementation environment layer stores each of the service interfaces for the application layer to call the target service interface.

[0073] As another aspect, the present application further provides a computer-readable storage medium on which a program product capable of implementing the method provided above in this specification is stored. In some possible implementations, various aspects of the present application may also be implemented in the form of a program product, which includes a program code, and when the program product is run on a terminal device, the program code is used to cause the terminal device to execute the steps according to various exemplary implementations of the present application described in the above "Embodiment Method" section of this specification.

[0074] According to the program product for implementing the above method in the embodiment of the present application, it can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be run on a terminal device, such as a personal computer. However, the program product of the present application is not limited thereto. In this document, a readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, an apparatus or a device.

[0075] The program product may use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0076] Computer readable signal media may include data signals propagated in baseband or as part of a carrier wave, in which readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Readable signal media may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0077] The program code embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0078] Program code for performing the operations of the present application may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., using an Internet service provider to connect through the Internet).

[0079] As another aspect, the present application also provides an electronic device capable of implementing the above method.

[0080] Those skilled in the art will appreciate that various aspects of the present application may be implemented as a system, method or program product. Therefore, various aspects of the present application may be specifically implemented in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software, which may be collectively referred to as "circuit", "module" or "system" herein.

[0081] Refer to the following Figure 4 The electronic device 400 according to this embodiment of the present application is described. Figure 4 The electronic device 400 shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0082] like Figure 4 As shown, the electronic device 400 is in the form of a general computing device. The components of the electronic device 400 may include but are not limited to: at least one processing unit 410, at least one storage unit 420, and a bus 430 connecting different system components (including the storage unit 420 and the processing unit 410).

[0083] The storage unit stores program codes, which can be executed by the processing unit 410, so that the processing unit 410 executes the steps described in the above “Example Method” section of this specification according to various exemplary implementations of the present application.

[0084] The storage unit 420 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 421 and / or a cache memory unit 422 , and may further include a read-only memory unit (ROM) 423 .

[0085] The storage unit 420 may also include a program / utility 424 having a set (at least one) of program modules 425, such program modules 425 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0086] Bus 430 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller node, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0087] The electronic device 400 may also communicate with one or more external devices 1200 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 400, and / or communicate with any device that enables the electronic device 400 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 450. In addition, the electronic device 400 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via a network adapter 460. As shown, the network adapter 460 communicates with other modules of the electronic device 400 via a bus 430. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 400, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0088] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation methods of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation methods of the present application.

[0089] In addition, the above-mentioned figures are only schematic illustrations of the processes included in the method according to the exemplary embodiments of the present application, and are not intended to be limiting. It is easy to understand that the processes shown in the above-mentioned figures do not indicate or limit the time sequence of these processes. In addition, it is also easy to understand that these processes can be performed synchronously or asynchronously, for example, in multiple modules.

[0090] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be performed without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A service-oriented architecture system for a vehicle, characterized in that: The system comprises: A data layer, the data layer including hardware data of each controller of the vehicle; An encapsulation service unit, the encapsulation service unit is used to obtain each of the hardware data from the data layer, and encapsulate each of the hardware data into a plurality of different service interfaces according to different characteristics between the hardware data, each of the service interfaces corresponds to hardware data of at least one characteristic, each of the service interfaces has an address identifier, and there is a corresponding relationship between the address identifier and the data address of the hardware data encapsulated in the service interface; An application implementation environment layer, the application implementation environment layer is used to obtain and store each of the service interfaces from the encapsulation service unit based on an interface transmission protocol; The application layer is used to call the target service interface from the application implementation environment layer, and obtain the target hardware data encapsulated in the target service interface according to the target address identifier of the target service interface.

2. The system according to claim 1, characterized in that The system further comprises a protocol layer, wherein the protocol layer is used to obtain each of the service interfaces from the encapsulation service unit, and the application implementation environment layer can obtain each of the service interfaces from the protocol layer based on the interface transmission protocol and store them.

3. The system according to claim 2, characterized in that The encapsulation service unit includes: a data acquisition unit and a data processing unit. The data acquisition unit is used to obtain each of the hardware data from the data layer and transmit each of the hardware data to the data processing unit; the data processing unit is used to classify and perform algorithm processing according to the characteristics of each of the hardware data to obtain each processed target data.

4. The system according to claim 3, characterized in that The encapsulation service unit also includes an encapsulation unit, which is used to encapsulate each of the target data into each of the service interfaces, perform functional definitions based on hardware characteristics of each of the target data, and transmit the defined service interfaces to the protocol layer.

5. The system according to claim 4, characterized in that The data processing unit is further used to classify each piece of hardware data into IO data and register data, and perform secondary classification based on the data characteristics of each piece of the IO data and the hardware characteristics of each piece of the register data to obtain each piece of the target data; The encapsulation unit is also used to encapsulate different types of service interfaces according to each of the target data after secondary classification to obtain a first type of service interface, a second type of service interface and a third type of service interface; wherein the first type of service interface, the second type of service interface and the third type of service interface each correspond to different processing logics, and the first type of service interface, the second type of service interface and the third type of service interface each include multiple service interfaces.

6. The system according to claim 5, characterized in that When the application layer calls the service interface, the service interface type corresponding to the service interface is obtained, and the hardware data corresponding to the service interface is obtained according to the address identifier of the service interface, and the hardware data is processed according to the processing logic corresponding to the service interface type.

7. A service method for service-oriented architecture, characterized in that: The method is executed in the encapsulation service unit according to any one of claims 1 to 6, and the method comprises: Obtain the hardware data of each controller in the data layer; According to different characteristics of each of the hardware data, the hardware data are encapsulated into a plurality of different service interfaces, each of the service interfaces corresponds to hardware data of at least one characteristic, each of the service interfaces has an address identifier, and there is a corresponding relationship between the address identifier and the data address of the hardware data encapsulated in the service interface; Each of the service interfaces is transmitted to the application implementation environment layer based on an interface transmission protocol, so that the application implementation environment layer stores each of the service interfaces for the application layer to call the target service interface.

8. A service device for a service-oriented architecture, characterized in that: The device comprises: An acquisition unit, used for acquiring hardware data of each controller of the data layer; An encapsulation unit, configured to encapsulate each piece of hardware data into a plurality of different service interfaces according to different characteristics of each piece of hardware data, each of the service interfaces corresponding to hardware data of at least one characteristic, each of the service interfaces having an address identifier, and a corresponding relationship between the address identifier and a data address of the hardware data encapsulated in the service interface; The transmission unit is used to transmit each of the service interfaces to the application implementation environment layer based on the interface transmission protocol, so that the application implementation environment layer stores each of the service interfaces for the application layer to call the target service interface.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores at least one program code, and the at least one program code is loaded and executed by the processor to implement the operations performed by the method according to claim 7.

10. An electronic device, characterized in that: The electronic device includes one or more processors and one or more memories, wherein at least one program code is stored in the one or more memories, and the at least one program code is loaded and executed by the one or more processors to implement the operations performed by the method according to claim 7.

Images