CN116149628A - Car end service assembly method, architecture, device, equipment and medium - Google Patents

Car end service assembly method, architecture, device, equipment and medium Download PDF

Info

Publication number
CN116149628A
CN116149628A CN202310334479.1A CN202310334479A CN116149628A CN 116149628 A CN116149628 A CN 116149628A CN 202310334479 A CN202310334479 A CN 202310334479A CN 116149628 A CN116149628 A CN 116149628A
Authority
CN
China
Prior art keywords
service
vehicle
service container
container process
operating system
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310334479.1A
Other languages
Chinese (zh)
Inventor
陶登攀
农光能
刘洪丹
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Chongqing Changan Automobile Co Ltd
Original Assignee
Chongqing Changan Automobile Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Chongqing Changan Automobile Co Ltd filed Critical Chongqing Changan Automobile Co Ltd
Priority to CN202310334479.1A priority Critical patent/CN116149628A/en
Publication of CN116149628A publication Critical patent/CN116149628A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/10Requirements analysis; Specification techniques

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

The invention relates to the field of automobile software, in particular to a method, a framework, a device, equipment and a medium for assembling automobile end service, which are applied to an SOA framework, wherein the method comprises the following steps: defining service container processes of different functional domains; selecting a plurality of services to be assembled to the same service container process according to the vehicle type functional requirements; associating at least one of the service container processes with an operating system; and automatically generating codes according to the associated configuration information. According to the invention, a plurality of services are assembled into one service container process according to the functional requirements of the vehicle-end operating system, and the services can be added or deleted rapidly in the service container process, so that the flexibility and the efficiency value of vehicle-end software development are improved; meanwhile, a plurality of related services are assembled into the same service container process, and the service is switched and scheduled through the service container process, so that service switching can be performed in a user space instead of a kernel space, and the system overhead during switching of a large number of processes is avoided.

Description

Car end service assembly method, architecture, device, equipment and medium
Technical Field
The invention relates to the field of automobile software, in particular to a method, a framework, a device, equipment and a medium for assembling automobile end service.
Background
The software-defined automobile is the direction of the future automobile, and along with the intelligent and networking deep propulsion of the automobile, the automobile is fully developed from a common transportation tool to the intelligent automobile direction, so that the automobile cloud integration is realized. Based on an SOA (Service-Oriented Architecture ) software architecture design concept, an automobile software architecture is layered and modularized, so that application layer functions can be multiplexed on different vehicle types, hardware platforms and operating systems, and the application functions can be rapidly and iteratively upgraded through standardized interfaces.
Under the technology, a finished automobile function implementation method based on SOA concept service layering is provided, a layered design concept is adopted, the flexibility and the diversity of functions are realized on the premise of not changing atomic services, and a three-layer service architecture is constructed: atomic services, composite services, and scenario services, three-tier services are deployed into different electronic controllers according to the electronic electrical architecture and network topology. However, the invention does not propose how to dynamically deploy and assemble a plurality of related services into the same service container process for the service interface of the SOA, and the service container can be used for calling the services while the development requirement is rapidly met, so that the system overhead of most process switching is reduced.
Disclosure of Invention
In view of the above-mentioned drawbacks of the prior art, the present invention provides a method, architecture, device, equipment and medium for assembling a vehicle-end service, in which the vehicle-end service required for implementing a software function is assembled into the same service container process, so as to solve the problem of flexible construction of the whole vehicle application software.
The invention provides a vehicle-end service assembly method, which is applied to an SOA architecture and comprises the following steps:
defining service container processes of different functional domains;
selecting a plurality of services to be assembled to the same service container process according to the vehicle type functional requirements;
associating at least one of the service container processes with an operating system;
and automatically generating codes according to the associated configuration information.
In one embodiment of the present invention, the step of defining the service container process of the different functional domains includes:
defining a vehicle-end service type and a use scene;
software base information and software capabilities defining the service container process.
In one embodiment of the present invention, the step of defining the software capabilities of the service container process includes:
software versions and software services of the service container process are defined.
In one embodiment of the present invention, the step of defining the software service of the service container process includes:
defining the service selected by the service container process aiming at a service end;
the service and service interface selected by the service container process are defined for a client.
In one embodiment of the present invention, the step of associating at least one service container process with an operating system includes:
selecting the service container process to be associated according to the function list of the operating system;
and carrying out relevant parameter configuration on the service container process and generating the configuration information to realize the association of the service container process and an operating system.
In an embodiment of the present invention, the step of automatically generating the code according to the associated configuration information includes:
and generating codes through a code automatic generation tool based on a preset code template library and business logic according to the service container process and the configuration information.
In one embodiment of the present invention, the code template library includes a C language source program file, a cpp file, an h file, an hpp file, and an xml file.
To achieve the above and other related objects, the present invention further provides a vehicle-end service architecture applying the vehicle-end service assembly method, including a controller, where the controller includes at least one operating system;
the operating system comprises at least one service container process;
the service container process includes a plurality of services.
In an embodiment of the present invention, communication is implemented between different service container processes in the operating system through a shared memory, and communication is implemented between different service container processes in the operating system through ethernet.
To achieve the above and other related objects, the present invention also provides a vehicle-end service assembling apparatus, including:
the definition module is used for defining service container processes of different functional domains;
the assembly module is used for selecting a plurality of services to be assembled to the same service container process according to the vehicle type function requirements;
the association module is used for associating at least one service container process with an operating system;
and the code generation module is used for automatically generating codes according to the associated configuration information.
To achieve the above and other related objects, the present invention also provides an electronic device including:
one or more processors;
and a storage device for storing one or more programs which, when executed by the one or more processors, cause the electronic device to implement the vehicle-side service assembly method.
To achieve the above and other related objects, the present invention also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor of a computer, causes the computer to execute the vehicle-side service assembling method.
The invention has the beneficial effects that: according to the invention, a configuration construction method is adopted, a plurality of services are assembled into the same service container process according to the functional requirements of the vehicle-end operating system, and the services can be added or deleted rapidly in the service container process, so that the problem of flexible construction of the whole vehicle application software is solved, and the flexibility and efficiency value of development of the vehicle-end software are improved; meanwhile, a plurality of related services are assembled into the same service container process, and the service is switched and scheduled through the service container process, so that service switching can be performed in a user space instead of a kernel space, and the system overhead during switching of a large number of processes is avoided.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application. It is apparent that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained from these drawings without inventive effort for a person of ordinary skill in the art. In the drawings:
fig. 1 is a schematic view of an application scenario of a vehicle-end service assembly method according to an embodiment of the present invention;
FIG. 2 is a flowchart of an embodiment of a method for assembling a vehicle-side service;
FIG. 3 is a schematic diagram of a system frame of a method for assembling a vehicle-end service according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of a service container process of a method for assembling a vehicle-side service according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of a framework of a vehicle-side service architecture according to an embodiment of the present invention;
FIG. 6 is a functional block diagram of a method for vehicle end service assembly according to an embodiment of the present invention;
fig. 7 is a block diagram of an electronic device provided by an embodiment of the invention.
Detailed Description
Further advantages and effects of the present invention will become readily apparent to those skilled in the art from the disclosure herein, by referring to the accompanying drawings and the preferred embodiments. The invention may be practiced or carried out in other embodiments that depart from the specific details, and the details of the present description may be modified or varied from the spirit and scope of the present invention. It should be understood that the preferred embodiments are presented by way of illustration only and not by way of limitation.
It should be noted that the illustrations provided in the following embodiments merely illustrate the basic concept of the present invention by way of illustration, and only the components related to the present invention are shown in the drawings and are not drawn according to the number, shape and size of the components in actual implementation, and the form, number and proportion of the components in actual implementation may be arbitrarily changed, and the layout of the components may be more complicated.
In the following description, numerous details are set forth in order to provide a more thorough explanation of embodiments of the present invention, it will be apparent, however, to one skilled in the art that embodiments of the present invention may be practiced without these specific details, in other embodiments, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring the embodiments of the present invention.
SOA is a model and methodology of software architecture design. In the automotive industry, it is understood that an SOA is designed for various application layer programs (i.e. "services", including various control algorithms, display functions, etc.), and is not dependent on an architectural design concept of a communication manner. One main reason for adopting the SOA architecture in the automotive field is that the interconnection and intercommunication between the vehicle and the Internet can be quickened, and various new functions can be flexibly integrated with the Internet without the conversion from signals to services; based on interconnection, can promote autopilot function by a wide margin: the method has the advantages that functions of creating, updating, route prediction and the like of the high-definition map are conveniently realized, and uploading of vehicle information and issuing of cloud instructions are conveniently realized; based on interconnection and intercommunication, the system and software upgrading performance is improved rapidly: the method is beneficial to realizing more efficient OBD (On Board Diagnostics, on-board automatic diagnosis system) and OTA (Over-the-Air Technology) software upgrading, and is beneficial to realizing various functions of remote diagnosis, pre-diagnosis and the like; based on interconnection and intercommunication, the user experience of the video entertainment function can be greatly improved, a more convenient networking function can be realized, and functions such as sharing of various applications among different platforms are realized; the platform architecture upgrade is more convenient to realize: complexity and the like caused by architecture upgrading can be effectively reduced through the SOA.
Fig. 1 is a schematic diagram of an application scenario of a vehicle-end service assembly method according to an embodiment of the present invention, where in this embodiment, a vehicle-end operating system 100 needs to be provided with a plurality of services to implement a desired function. In order to increase flexibility and efficiency in system service development, the present invention assembles a plurality of related services into one service container process, such as assembling service 111, service 112, service 113 and service 114 into service container process 110, and assembling service 121, service 122 and service 123 into service container process 120. The method can select the service to be assembled in the service container process according to the vehicle type requirement, and can dynamically change the service in the service container process through configurational construction when the service container process needs to be changed or updated so as to realize the flexibility and the high efficiency of the system service development. Meanwhile, a plurality of services are assembled into one service container process, and when the service needs to be switched for realizing the functions, the service container process can be used for scheduling, so that service switching is performed in a user space instead of a kernel space, and the overhead of a system when a large number of processes are switched can be avoided.
In the prior art, when the service of the vehicle-mounted application is constructed, the service and the service are independent, a plurality of service processes are correspondingly started when a plurality of services are started, and the service processes are correspondingly switched when service switching is performed, so that the system memory is greatly occupied, and the load of the system is increased; meanwhile, when the application function is changed, the service needs to be rewritten, and the construction method has complicated process and extremely low efficiency, and cannot flexibly and efficiently develop the service, so the method needs to be used for improvement.
Fig. 2 is a specific flowchart of a vehicle-end service assembling method according to an embodiment of the present invention. The method may be applied to the implementation environment shown in fig. 1, and it should be understood that the method may also be applied to other exemplary implementation environments and be specifically executed by devices in other implementation environments, and the implementation environment to which the method is applied is not limited by the embodiment.
As shown in fig. 2, in an exemplary embodiment, the vehicle end service assembling method at least includes steps S210 to S240, which are described in detail as follows:
step S210: service container processes defining different functional domains.
In one embodiment, the steps include: defining a vehicle-end service type and a use scene; software base information and software capabilities defining the service container process.
In one embodiment, the steps include: software versions and software services of the service container process are defined.
In one embodiment, the step further comprises: defining the service selected by the service container process aiming at a service end; the service and service interface selected by the service container process are defined for a client.
Specifically, the invention needs to define the service type of the vehicle end and the use scene of the service container process, and then define the software basic information and the software capability of the service container process. The service container process in the method can be regarded as vehicle-end software, which belongs to the invisible and non-touchable system bottom software, but when the function of related service is realized, the service container process, namely the vehicle-end software, is also running. Fig. 4 is a schematic view of a service container process of a vehicle-end service assembly method according to an embodiment of the present invention, where a model definition of the service container process includes software basic information and software capabilities. The software basic information comprises a functional domain, a software name, a software piece number and a software description; the functional domain indicates that the service container process belongs to a specific service domain for management and definition; the software name represents an identifier of the service container process uniquely existing in the platform system; the software part number represents a software identification number of the service container process deployed in the vehicle-side controller; the software description represents a related description of the service container process. The software capabilities in the service container process include software versions and software services; the software version is the version number of the service container process and consists of a main version, a secondary version and an auxiliary version; the software service is to define the service capability of the current software, namely the service container process, and divide the current software into a client and a service according to a request-response mode, and define the contained service and a service interface for the client and define only the contained service for the service. Wherein the design of the service interface determines how the service consumer uses the service, the support service interface has three types: methods, events, fields; the Methods interface represents a control, and the communication mode adopts remote call of RPC (Remote Procedure Call ), and generally has verb actions such as control, state inquiry, transmission, registration, setting and the like; the Event interface represents the data actually transmitted, and takes the data as an operation object; the Field interface represents an attribute, commonly referred to as a status value or some information. The definition of a service interface is completely abstract, independent of the communication protocol, and any two services can use this interface for communication.
Step S220: and selecting a plurality of services to be assembled to the same service container process according to the vehicle type functional requirements.
Specifically, according to different functions required to be realized by different vehicle types, a plurality of related services are selected and assembled into the same service container process in a configuration mode, so that the rapid construction of vehicle-end software is realized, and meanwhile, the rapid adjustment and reconstruction by matching with actual service changes are also supported, thereby realizing the flexibility and high efficiency of system service development.
Step S230: at least one of the service container processes is associated with an operating system.
In one embodiment, the steps include: selecting the service container process to be associated according to the function list of the operating system; and carrying out relevant parameter configuration on the service container process and generating the configuration information to realize the association of the service container process and an operating system.
Specifically, the model of the service container process can support two large module deployment modes of an MPU (Micro Processor Unit, microprocessor) and an MCU (Micro Control Unit ), and the deployment modules can be selected according to the complexity of the service container process. For a function list of a specific vehicle type project, selecting a service container process to be associated with an operating system on a controller (MPU deployment/MCU deployment), performing starting parameter configuration, resource group configuration and software diagnosis related parameter configuration on the service container process, and generating configuration information to realize the association of the service container process and the operating system.
Step S240: and automatically generating codes according to the associated configuration information.
In one embodiment, the steps include: and generating codes through a code automatic generation tool based on a preset code template library and business logic according to the service container process and the configuration information.
In one embodiment, the code template library includes a C language source program file, a cpp file, an h file, an hpp file, and an xml file.
Specifically, after the service container process is associated with the operating system in the logic level, the method calls a preset code template library and business logic according to the relevant definition and configuration information of the service container process, automatically generates an ARXML configuration file, inputs the ARXML configuration file into a code automatic generation tool component for analysis, and automatically generates and downloads codes. Wherein the code template library comprises a C language source program file, a cpp file, an h file, an hpp file and an xml file.
The vehicle-end service assembly method provided by the invention is based on the SOA architecture, and the communication between services is more flexible in the form of modeling the vehicle-end function SOA service and configuring the service interface communication. The invention designs the vehicle-end application to form the service container process according to the service deployment requirement, and assembles a plurality of related services to the clients and the service end of the same service container process on the basis of the communication mode of request-response, thereby improving the flexibility and the efficiency value of vehicle-end software development. Meanwhile, a plurality of related services are assembled into the same service container process, the service container process is used for scheduling the services, service switching can be performed in a user space instead of a kernel space, and system overhead caused by a large number of process switching is avoided.
Fig. 3 is a schematic system frame diagram of a vehicle end service assembly method according to an embodiment of the present invention, where the system frame shown in fig. 3 exists according to the foregoing description, and the implementation process of the present invention may be combined with the implementation process of the specific embodiment of the present invention to help understand the implementation process of the present invention.
The system framework shown in fig. 3 includes a design module 310, a code template library 320, and a code automatic generation tool 330, and the design module 310 includes an SOA service model design module 311, a vehicle end application model design module 312, and a vehicle end application deployment module 313. The SOA service model design module 311 is used for designing service container processes defining different functional domains, and defining basic information, software versions and software services of the service container processes; the vehicle-end application model design module 312 is configured to assemble a plurality of related services into the same service container process according to the functional requirements, so as to implement rapid construction of vehicle-end software; the vehicle-end application deployment module 313 is configured to select a service container process to be deployed on the controller according to the function lists of different vehicle types, associate the service container process with the operating system in a logic level, and perform starting parameter configuration, resource group configuration and software diagnosis related parameter configuration on the service container process to generate configuration information. After the design module 310 designs the service container process, configures a plurality of services and associates with the operating system, the system automatically generates an ARXML configuration file and inputs the ARXML configuration file into the code automatic generation tool 330, and automatically generates and downloads codes by calling the C language source program file, & cpp file, & h file, & hpp file or xml file and business logic in the code template library 320.
The invention also provides a vehicle end service architecture using the vehicle end service assembly method, as shown in fig. 5, which is a frame schematic diagram of a vehicle end service architecture provided by an embodiment of the invention, and the vehicle end service architecture comprises a controller, wherein the controller comprises at least one operating system; the operating system comprises at least one service container process;
the service container process includes a plurality of services.
In an embodiment, communication is realized between different service container processes in the operating system through a shared memory, and communication is realized between different service container processes in the operating system through Ethernet.
Specifically, to implement different functions, the operating system of the vehicle-side controller may include a plurality of service container processes; in order to realize the flexible construction of the whole vehicle application software and improve the flexibility and efficiency value of vehicle-end software development, a plurality of services are assembled in one service container process. In connection with the domain controller shown in fig. 5, the domain controller includes a middleware layer (hypervisor) running between a physical server and an operating System, a System on Chip (Soc), a Linux OS (Linux Operating System, virtual operating System), a QNX OS (Quick Unix, distributed real-time operating System), etc., where the Linux OS includes a service container process a, a service container process B, etc., and the QNX OS includes a service container process C, etc. According to the service deployment requirements, the service container processes are designed, one or more service container processes are deployed in corresponding OSs, high-efficiency communication between different service container processes can be achieved in the same OS system through a shared memory, and communication between different service container processes can be achieved through Ethernet. The service container process can schedule a plurality of services to switch the services in the user space instead of the kernel space, so that the system overhead of switching most processes is avoided.
Fig. 6 is a functional block diagram of a vehicle end service assembly method according to an embodiment of the present invention, and the apparatus may be applied to the implementation environment shown in fig. 1. The apparatus may also be adapted to other exemplary implementation environments and may be specifically configured in other devices, and the present embodiment is not limited to the implementation environments to which the apparatus is adapted.
As shown in fig. 6, the apparatus includes a definition module 610, an assembly module 620, an association module 630, and a code generation module 640;
the defining module 610 is configured to define service container processes of different functional domains;
the assembling module 620 is configured to select a plurality of services to be assembled to the same service container process according to the vehicle type function requirement;
the association module 630 is configured to associate at least one service container process with an operating system;
the code generating module 640 is configured to automatically generate a code according to the associated configuration information.
It should be noted that, the vehicle-end service assembling device provided by the foregoing embodiment and the vehicle-end service assembling method provided by the foregoing embodiment belong to the same concept, and specific manners in which the respective modules and units perform operations have been described in detail in the method embodiments, which are not repeated herein. In practical application, the device for assembling a vehicle-end service provided in the above embodiment may allocate the functions to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above, which is not limited herein.
The embodiment of the application also provides electronic equipment, which comprises: one or more processors; and a storage device for storing one or more programs, which when executed by the one or more processors, cause the electronic device to implement a vehicle-end service assembly method provided in the foregoing embodiments.
Fig. 7 shows a schematic diagram of a computer system suitable for use in implementing the electronic device of the embodiments of the present application. It should be noted that, the computer system 700 of the electronic device shown in fig. 7 is only an example, and should not impose any limitation on the functions and the application scope of the embodiments of the present application.
As shown in fig. 7, the computer system 700 includes a central processing unit (Central Processing Unit, CPU) 701 that can perform various appropriate actions and processes, such as performing the methods described in the above embodiments, according to a program stored in a Read-Only Memory (ROM) 702 or a program loaded from a storage section 708 into a random access Memory (Random Access Memory, RAM) 703. In the RAM 703, various programs and data required for the system operation are also stored. The CPU 701, ROM 702, and RAM 703 are connected to each other through a bus 704. An Input/Output (I/O) interface 705 is also connected to bus 704.
The following components are connected to the I/O interface 705: an input section 706 including a keyboard, a mouse, and the like; an output section 707 including a Cathode Ray Tube (CRT), a liquid crystal display (Liquid Crystal Display, LCD), and the like, a speaker, and the like; a storage section 708 including a hard disk or the like; and a communication section 709 including a network interface card such as a LAN (Local Area Network ) card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. The drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed on the drive 710 as needed, so that a computer program read out therefrom is installed into the storage section 708 as needed.
In particular, according to embodiments of the present application, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising a computer program for performing the method shown in the flowchart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion 709, and/or installed from the removable medium 711. When executed by a Central Processing Unit (CPU) 701, performs the various functions defined in the system of the present application.
It should be noted that, the computer readable medium shown in the embodiments of the present application may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium may be, for example, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-Only Memory (ROM), an erasable programmable read-Only Memory (Erasable Programmable Read Only Memory, EPROM), flash Memory, an optical fiber, a portable compact disc read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with a computer-readable computer program embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. A computer program embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems according to various embodiments of the present application. Where each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present application may be implemented by means of software, or may be implemented by means of hardware, and the described units may also be provided in a processor. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.
Another aspect of the present application also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor of a computer, causes the computer to perform a vehicle end service assembly method as described above. The computer-readable storage medium may be included in the electronic device described in the above embodiment or may exist alone without being incorporated in the electronic device.
Another aspect of the present application also provides a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs a vehicle-end service assembly method provided in the above embodiments.
The above embodiments are merely illustrative of the principles of the present invention and its effectiveness, and are not intended to limit the invention. Modifications and variations may be made to the above-described embodiments by those skilled in the art without departing from the spirit and scope of the invention. It is therefore intended that all equivalent modifications and changes made by those skilled in the art without departing from the spirit and technical spirit of the present invention shall be covered by the appended claims.

Claims (12)

1. The vehicle-end service assembly method is characterized by being applied to an SOA architecture, and comprises the following steps:
defining service container processes of different functional domains;
selecting a plurality of services to be assembled to the same service container process according to the vehicle type functional requirements;
associating at least one of the service container processes with an operating system;
and automatically generating codes according to the associated configuration information.
2. The vehicle-side service assembling method according to claim 1, wherein the step of defining service container processes of different functional domains includes:
defining a vehicle-end service type and a use scene;
software base information and software capabilities defining the service container process.
3. The vehicle-side service assembly method of claim 2, wherein the step of defining software capabilities of the service container process comprises:
software versions and software services of the service container process are defined.
4. A vehicle-end service assembly method according to claim 3, wherein the step of defining the software services of the service container process comprises:
defining the service selected by the service container process aiming at a service end;
the service and service interface selected by the service container process are defined for a client.
5. The vehicle-side service assembly method of claim 1, wherein the step of associating at least one service container process with an operating system comprises:
selecting the service container process to be associated according to the function list of the operating system;
and carrying out relevant parameter configuration on the service container process and generating the configuration information to realize the association of the service container process and an operating system.
6. The vehicle-end service assembling method according to claim 1, wherein the step of automatically generating a code according to the associated configuration information comprises:
and generating codes through a code automatic generation tool based on a preset code template library and business logic according to the service container process and the configuration information.
7. The vehicle-end service assembling method according to claim 6, wherein the code template library includes a C language source program file, a cpp file, an h file, an hpp file, and an xml file.
8. A vehicle end service architecture applying the vehicle end service assembly method of claims 1-7, comprising a controller, wherein the controller comprises at least one operating system;
the operating system comprises at least one service container process;
the service container process includes a plurality of services.
9. The vehicle-side service architecture of claim 8, wherein communication is implemented between different service container processes within the operating system via a shared memory, and wherein communication is implemented between different service container processes within the operating system via ethernet.
10. A vehicle-end service assembling apparatus, characterized by comprising:
the definition module is used for defining service container processes of different functional domains;
the assembly module is used for selecting a plurality of services to be assembled to the same service container process according to the vehicle type function requirements;
the association module is used for associating at least one service container process with an operating system;
and the code generation module is used for automatically generating codes according to the associated configuration information.
11. An electronic device, the electronic device comprising:
one or more processors;
storage means for storing one or more programs which, when executed by the one or more processors, cause the electronic device to implement the vehicle end service assembly method of any one of claims 1 to 7.
12. A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor of a computer, causes the computer to perform the vehicle-end service assembly method of any one of claims 1 to 7.
CN202310334479.1A 2023-03-31 2023-03-31 Car end service assembly method, architecture, device, equipment and medium Pending CN116149628A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310334479.1A CN116149628A (en) 2023-03-31 2023-03-31 Car end service assembly method, architecture, device, equipment and medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310334479.1A CN116149628A (en) 2023-03-31 2023-03-31 Car end service assembly method, architecture, device, equipment and medium

Publications (1)

Publication Number Publication Date
CN116149628A true CN116149628A (en) 2023-05-23

Family

ID=86373843

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310334479.1A Pending CN116149628A (en) 2023-03-31 2023-03-31 Car end service assembly method, architecture, device, equipment and medium

Country Status (1)

Country Link
CN (1) CN116149628A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117215958A (en) * 2023-10-11 2023-12-12 深圳市浩科智联科技有限公司 Vehicle-mounted application separation design software and test method thereof

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117215958A (en) * 2023-10-11 2023-12-12 深圳市浩科智联科技有限公司 Vehicle-mounted application separation design software and test method thereof
CN117215958B (en) * 2023-10-11 2024-05-31 深圳市浩科智联科技有限公司 Vehicle-mounted application separation design software and test method thereof

Similar Documents

Publication Publication Date Title
CN110851145B (en) Container arrangement-based edge cloud installation and maintenance method and system
CN112272234B (en) Platform management system and method for realizing edge cloud cooperation intelligent service
CN111682973B (en) Method and system for arranging edge cloud
CN109117252B (en) Method and system for task processing based on container and container cluster management system
CN110413346A (en) A kind of parameter updating method and device
CN110704070B (en) Method for constructing DDS communication middleware under partitioned real-time operating system
CN110297670B (en) Method and system for improving training efficiency of distributed tasks on container cloud
EP4390674A1 (en) Vehicle development platform, domain controller, whole vehicle control system, and vehicle
CN116149628A (en) Car end service assembly method, architecture, device, equipment and medium
CN111552550A (en) Task scheduling method, device and medium based on GPU (graphics processing Unit) resources
CN114461357B (en) Remote sensing satellite original data real-time processing flow scheduling system
CN115834375A (en) Vehicle-side service communication configuration method, system, equipment and storage medium
CN112395736A (en) Parallel simulation job scheduling method of distributed interactive simulation system
CN112015371B (en) Software development device under non-embedded software platform
Fletcher et al. The case for an end-to-end automotive-software platform
CN113435012B (en) Distributed aircraft simulation method and device and electronic equipment
CN110852623A (en) BPMN-based command control process design method
CN114490062A (en) Local disk scheduling method and device, electronic equipment and storage medium
CN112558968B (en) Method, device, equipment and storage medium for generating resource tree view
CN111027221B (en) Modular comprehensive avionics simulation training system based on components
CN116248629B (en) Registration optimization method for SCA equipment component
CN117056201A (en) Intelligent cabin testing method, device and medium
CN111683005A (en) Internet of things intelligent gateway equipment and construction method thereof
CN115437647A (en) Multi-frame-adaptive micro-service deployment method, device, terminal and storage medium
CN114546387A (en) Service arrangement script execution system and method

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