Function development implementation method based on SOA (Service Oriented Architecture)
By adopting a SOA architecture-based approach in automotive function development, the problem that traditional development models are difficult to meet the needs of rapid iteration and customization is solved, and the convenience of software iteration and innovation of model functions are achieved.
Patent Information
- Application Number
- CN202411601868.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-11
- Publication Date
- 2025-02-25
AI Technical Summary
The traditional signal-based functional development model is difficult to meet the needs of rapid iteration and customization of automotive intelligence and networking, and the trend of software-defined cars requires that software version iterations be more frequent.
Using a functional development implementation method based on SOA architecture, through functional requirements analysis, service architecture design and service design specifications, the functional requirements are split into more detailed service requirements, loosely coupled service architecture is designed, and detailed service design specifications are written. .
It improves the convenience of software iteration, supports the variability and flexibility of user needs, expands the functional innovation points of the vehicle model, shortens the development cycle of the vehicle, and simplifies version upgrade and maintenance.
Smart Images
Figure CN119512506A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of automobile service technology, and more specifically, to a function development implementation method based on SOA architecture. Background Art
[0002] With the rapid development of automobile intelligence and networking, the complexity and diversity of vehicle functions are increasing. The traditional signal-based function development model can no longer meet the needs of rapid iteration and customization. At the same time, with the rapid development of the Internet, the trend of software-defined cars is increasing, so the requirements for software version iteration are becoming more and more frequent. Therefore, the development of vehicle function service-oriented functions based on SOA service architecture has become an industry trend.
[0003] SOA (Service-Oriented Architecture) has the following advantages:
[0004] 1. Flexibility and scalability: SOA decomposes system functions into independent services, which can be flexibly combined and adjusted according to business needs. When business needs change, only related services need to be modified or new services need to be added, without large-scale reconstruction of the entire system, thus improving the scalability and adaptability of the system.
[0005] 2. Reusability: SOA emphasizes the reusability of services. By encapsulating common functions as services, they can be reused in different business processes, reducing the workload of repeated development, improving development efficiency and reducing costs.
[0006] 3. Loose coupling: Services communicate through well-defined interfaces, and the internal implementation details of a service are transparent to other services. This loose coupling minimizes the dependencies between services, reduces system complexity, and improves system reliability and maintainability.
[0007] 4. Easy to integrate: SOA architecture adopts open standards and protocols, making it easy to integrate different systems and services. Whether it is different systems within the enterprise or systems with external partners, they can be seamlessly integrated through SOA architecture to achieve information sharing and business collaboration.
[0008] 5. Improve development efficiency: The functional development process based on SOA architecture can decompose complex systems into multiple relatively simple services. Developers can focus on the development of a single service, reducing the difficulty and complexity of development and improving development efficiency.
[0009] 6. Manageability: SOA architecture makes system management more convenient and efficient. Services can be independently deployed, monitored and managed, problems can be discovered and solved in a timely manner, and the system's operational stability and reliability can be improved.
[0010] The traditional vehicle development process based on functional development, the left half of the "V"-shaped development process is the core work content of vehicle electronic and electrical architecture development, mainly including functional requirements use cases, architecture allocation design, subsystem design and component design. The traditional functional development process has the characteristics of waterfall development, and therefore has the following shortcomings:
[0011] 1) Limitations of the waterfall model: It usually follows a strict sequential phase. This linear approach may result in early errors or deficiencies being discovered only in the late stages of the project, which can be very costly to correct.
[0012] 2) Lack of flexibility: processes are often rigid and difficult to respond quickly to changes in demand;
[0013] 3) Inefficient communication: There may be communication barriers between different departments or teams, and information cannot be delivered in a timely manner;
[0014] 4) Longer cycle;
[0015] 5) It is difficult to adapt to innovative and unique competitive functions.
[0016] Therefore, there is an urgent need for a function development implementation method based on SOA architecture. Summary of the invention
[0017] The purpose of the present invention is to provide a function development implementation method based on SOA architecture to solve the problems in the above-mentioned prior art, improve the convenience of software iteration, support the variability and flexibility of user needs, and greatly expand the functional innovation points of vehicle models.
[0018] The present invention provides a function development implementation method based on SOA architecture, which includes:
[0019] Functional requirement analysis: split the functions of the functional requirement document into smaller functional units to obtain multiple service requirements;
[0020] Service architecture design: Design modules of some software architectures according to service requirements;
[0021] Service design specification writing: Based on the protocol specifications of the in-vehicle service design, write detailed logical specifications of the service requirements and service architecture.
[0022] In the above-mentioned SOA-based function development implementation method, preferably, the function requirement analysis specifically includes:
[0023] Orchestrate, filter and deduplicate a large number of service requirements to extract service requirement interfaces that are more in line with service design principles.
[0024] As described above, the function development implementation method based on SOA architecture, wherein preferably, the service architecture design specifically includes:
[0025] The service requirements are associated and deployed to associate the service requirement interfaces with relevant service providers.
[0026] In the above-mentioned SOA-based function development implementation method, preferably, the service design specification writing specifically includes:
[0027] Clarify the protocol specifications for in-vehicle service design;
[0028] Clarify service interface types and data types according to standard specifications;
[0029] Convert services and service requirement interfaces into service names and service interfaces, and perform more detailed hardware matching and service deployment.
[0030] By adding service discovery, service subscription and detailed service logic specifications, the service design and development work of the entire vehicle is completed.
[0031] As described above, the function development implementation method based on the SOA architecture, wherein, preferably, the function development implementation method based on the SOA architecture further includes:
[0032] Specific flashing and integrated compilation work of software and hardware.
[0033] In the above-mentioned SOA-based function development implementation method, preferably, the specific flashing and integrated compilation of the software and hardware specifically includes:
[0034] The OEM develops it based on its own protocol stack.
[0035] The present invention provides a function development implementation method based on SOA architecture. Based on the software-defined car and service-oriented ideas, the current vehicle development process is optimized, and the problems of too strong coupling and too poor flexibility in traditional function development can be solved. At the same time, the convenience of software iteration is improved, the variability and flexibility of user needs are supported, and the functional innovation points of vehicle models are greatly expanded. It is a software-oriented and service-oriented design process, which can speed up the pace of vehicle component development and shorten the vehicle development cycle. It is convenient for vehicle OTA upgrades and has great convenience for subsequent version upgrades and maintenance. Moreover, the idea of service development fits software development, gradually improves the software thinking of vehicle manufacturers, and meets the trend of software-defined cars. Although this method has challenges in organizational structure and personnel allocation, once the service development process is clear, the service layered architecture is clear, and the service design specifications are clear, it is extremely simple for subsequent scene upgrades, big data collection, flexible deployment and other tasks. The present invention can be used as a reference for the architecture development department of the vehicle manufacturer to make adaptive adjustments to the organizational structure; it can also be used for solution suppliers to provide display materials for the overall architecture development process trend. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] In order to make the purpose, technical solutions and advantages of the present invention more clear, the present invention will be further described below with reference to the accompanying drawings, in which:
[0037] Figure 1 This is a flow chart of an embodiment of a function development implementation method based on SOA architecture provided by the present invention. DETAILED DESCRIPTION
[0038] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. The description of the exemplary embodiments is merely illustrative and is in no way intended to limit the present disclosure and its application or use. The present disclosure can be implemented in many different forms and is not limited to the embodiments described herein. These embodiments are provided to make the present disclosure thorough and complete and to fully express the scope of the present disclosure to those skilled in the art. It should be noted that unless otherwise specifically stated, the relative arrangement of the components and steps, the composition of the materials, the numerical expressions and the numerical values set forth in these embodiments should be interpreted as being merely exemplary and not as limiting.
[0039] The words "first", "second" and similar words used in this disclosure do not indicate any order, quantity or importance, but are only used to distinguish different parts. The words "include" or "comprises" and similar words mean that the elements before the word include the elements listed after the word, and do not exclude the possibility of including other elements. "Up", "down" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.
[0040] In the present disclosure, when a specific component is described as being located between a first component and a second component, there may or may not be an intermediate component between the specific component and the first component or the second component. When a specific component is described as being connected to other components, the specific component may be directly connected to the other components without an intermediate component, or may not be directly connected to the other components but have an intermediate component.
[0041] All terms (including technical terms or scientific terms) used in the present disclosure have the same meanings as those understood by ordinary technicians in the field to which the present disclosure belongs, unless otherwise specifically defined. It should also be understood that terms defined in general dictionaries, such as general dictionaries, should be interpreted as having meanings consistent with their meanings in the context of the relevant technology, and should not be interpreted in an idealized or extremely formal sense, unless explicitly defined herein.
[0042] Technologies, methods, and equipment known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, the technologies, methods, and equipment should be considered part of the specification.
[0043] like Figure 1 As shown, the function development implementation method based on SOA architecture provided in this embodiment includes the following steps in actual execution:
[0044] Step S1, functional requirement analysis: split the functions of the functional requirement document into finer functional units to obtain multiple service requirements.
[0045] Being service-based means that service design is needed, but the service itself is inseparable from the function. Service is a smaller functional unit. At present, the division of services by domestic OEMs varies from person to person, but as a whole it should meet the basic characteristics of object-oriented languages, namely high code reusability, encapsulation, and inheritability.
[0046] Specifically, a large number of service requirements are orchestrated, filtered, and deduplicated to extract service requirement interfaces that are more in line with service design principles. In the service-based function development process, functional requirement analysis is also a primary and important task. It is necessary to explain the current function usage scenarios, function prerequisites, execution actions, etc. from the user's perspective. The difference is that the development process of service-based software-defined cars is more inclined to software requirements. Therefore, in the top-level demand design, it is necessary to split the functions of the functional requirement document to obtain finer functional units, namely service requirements. A large number of service requirements need to be orchestrated, filtered, and deduplicated to extract service requirement interfaces that are more in line with service design principles. The service requirement interface does not need to define a specific interface type for the time being.
[0047] In one embodiment of the present invention, taking the function of closing windows in rainy days as an example, the architecture engineer first needs to decompose the use case according to the analysis process of the user scenario (Use Case), so as to obtain more detailed service requirements based on the refined use case than traditional function development (traditional function development is based on functions as units, distributed downward, and associated subsystems and hardware to implement functional logic), such as improving the ability to detect rainy days, improving the control ability of opening and closing windows, and improving the power mode capability of the whole vehicle. These detailed service interface requirements can be combined, deduplicated, screened and reviewed to extract a more accurate service requirement interface.
[0048] Step S2, service architecture design: perform module design of part of the software architecture according to service requirements.
[0049] Specifically, the service requirements are associated and deployed to associate the service requirement interface with the relevant service provider. The design of the service architecture is also an architectural design work carried out around the service. Because the service itself is an abstract unit of software development, the design of this part of the service architecture is equivalent to the module design of part of the software architecture. Therefore, the hierarchical division of the module determines the layering of the service. In addition, this part also needs to associate and deploy the service requirements of step S1, that is, to associate the service requirement interface with the relevant service provider, thus realizing the matching work of the service and the service requirement interface.
[0050] In one embodiment of the present invention, taking the window closing function on rainy days as an example, a layered architecture analysis of the software architecture / module / service is required in this part. According to the function, the window service module, the vehicle power mode service module, the rainy day detection service module, etc. can be divided. Then, the service demand interface and the service module of step S1 are associated to obtain a more accurate service-service demand module. This association is beneficial to some modeling engineering work. If modeling is not required, the Excel document can be retained.
[0051] Step S3, writing service design specifications: writing detailed logical specifications of service requirements and service architecture according to the protocol specifications of the in-vehicle service design.
[0052] In one implementation of the function development implementation method based on SOA architecture of the present invention, step S3 may specifically include:
[0053] Step S31: clarify the protocol specifications for in-vehicle service design.
[0054] Step S32: Clarify the service interface type and data type according to the standard specification.
[0055] Step S33: convert the service and service requirement interface into a service name and a service interface, and perform more detailed hardware matching and service deployment work.
[0056] Step S34, adding service discovery, service subscription and detailed service logic specifications, completing the service design and development work of the entire vehicle.
[0057] The service design specifications need to clarify the protocol specifications for the in-vehicle service design, and then clarify the service interface type and data type according to the standard specifications. At the same time, the service and service requirement interface of step S2 is converted into a service name and service interface, and more detailed hardware matching and service deployment are carried out. Finally, service discovery, service subscription, and detailed service logic specifications need to be added to complete the service design and development work of the entire vehicle.
[0058] In one embodiment of the present invention, continuing to take the window closing function on rainy days as an example, this part first needs to clarify the in-vehicle Ethernet communication protocol SOME / IP protocol, and then perform standard interface type conversion Method / Event / Field, and then associate deployment with specific hardware, such as the window service module is deployed to BCM (Body control Module), the rainy day detection service module is deployed to BCM, and the vehicle power mode service module is deployed to HPC (High Performance Computer). Finally, it is necessary to describe the discovery and subscription of the service in detail, the client of the service obtains the current service, and the logic that the client needs to execute after obtaining it. For example, the window control module service needs to subscribe to the rainy day detection module service. When the rainy day detection module service status changes to the rainy state, the window control module service needs to obtain the latest rainy state and then perform the window closing execution action. This part of the logic needs to be described.
[0059] Furthermore, in some implementations of the present invention, the function development implementation method based on the SOA architecture further includes:
[0060] Step S4: specific flashing and integrated compilation of software and hardware.
[0061] Specifically, the OEM develops according to its own protocol stack.
[0062] The function development implementation method based on SOA architecture provided in the embodiment of the present invention optimizes the current vehicle development process based on the idea of software-defined cars and service-oriented, can solve the problems of too strong coupling and too poor flexibility of traditional function development, and at the same time improve the convenience of software iteration, support the variability and flexibility of user needs, and greatly expand the functional innovation points of vehicle models; it is a software-oriented and service-oriented design process, which can speed up the pace of vehicle component development and shorten the vehicle development cycle; it is convenient for vehicle OTA upgrades, and has great convenience for subsequent version upgrades and maintenance. Moreover, the idea of service development fits software development, gradually improves the software thinking of vehicle manufacturers, and meets the trend of software-defined cars. Although this method has challenges in organizational structure and personnel allocation, once the service development process is clear, the service layered architecture is clear, and the service design specifications are clear, it is extremely simple for subsequent scene upgrades, big data collection, flexible deployment and other tasks; the present invention can be used as a reference for the architecture development department of the vehicle manufacturer to make adaptive adjustments to the organizational structure; it can also be used for solution suppliers to provide display materials for the overall architecture development process trend.
[0063] So far, various embodiments of the present disclosure have been described in detail. In order to avoid obscuring the concept of the present disclosure, some details known in the art are not described. Based on the above description, those skilled in the art can fully understand how to implement the technical solution disclosed here.
[0064] Although some specific embodiments of the present disclosure have been described in detail by way of examples, it should be understood by those skilled in the art that the above examples are for illustration only and are not intended to limit the scope of the present disclosure. It should be understood by those skilled in the art that the above embodiments may be modified or some technical features may be replaced by equivalents without departing from the scope and spirit of the present disclosure. The scope of the present disclosure is defined by the appended claims.
Claims
1. A function development implementation method based on SOA architecture, characterized in that: include: Functional requirement analysis: split the functions of the functional requirement document into smaller functional units to obtain multiple service requirements; Service architecture design: Design modules of some software architectures according to service requirements; Service design specification writing: Based on the protocol specifications of the in-vehicle service design, write detailed logical specifications of the service requirements and service architecture.
2. The function development implementation method based on SOA architecture according to claim 1 is characterized in that: The functional requirements analysis specifically includes: Orchestrate, filter and deduplicate a large number of service requirements to extract service requirement interfaces that are more in line with service design principles.
3. The function development implementation method based on SOA architecture according to claim 1 is characterized in that: The service architecture design specifically includes: The service requirements are associated and deployed to associate the service requirement interfaces with relevant service providers.
4. The function development implementation method based on SOA architecture according to claim 1 is characterized in that: The service design specification preparation specifically includes: Clarify the protocol specifications for in-vehicle service design; Clarify service interface types and data types according to standard specifications; Convert services and service requirement interfaces into service names and service interfaces, and perform more detailed hardware matching and service deployment. By adding service discovery, service subscription and detailed service logic specifications, the service design and development work of the entire vehicle is completed.
5. The function development implementation method based on SOA architecture according to claim 1 is characterized in that: The function development implementation method based on SOA architecture also includes: Specific flashing and integrated compilation work of software and hardware.
6. The function development implementation method based on SOA architecture according to claim 5 is characterized in that: The specific flashing and integrated compilation work of the software and hardware specifically includes: The OEM develops it based on its own protocol stack.