SOA Middleware Service Subscription Table Decoupling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The close association between applications and services in vehicle systems increases development and management costs due to the need for detailed information exchange, such as version numbers and physical addresses, in existing communication protocols like SOMEIP.
Innovation Solution
A service management method and apparatus that initializes a service subscription table to record subscription relationships between services and applications, allowing decoupling by managing these relationships through a SOA service management middleware, which reduces the need for applications and services to know each other's detailed information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a close association between applications and services is maintained using SOMEIP protocol, then communication between service and application can be realized, but development and management costs increase due to the need for detailed information exchange
Solution Approach 1:
The patent introduces a service management middleware as an intermediary component between applications and services. This middleware maintains a service subscription table that records subscription relationships, allowing applications to subscribe to services without direct detailed information exchange. The middleware handles the complex information matching and routing, thereby reducing system complexity while maintaining reliable communication through the subscription-based mechanism.
2Measurement precision
If detailed information exchange is implemented between applications and services, then precise service invocation is achieved, but development and management costs increase
Solution Approach 1:
The patent segments the service invocation process into two independent parts: service publishing and service subscription. Applications subscribe to services by specifying only the service name and version range, without needing detailed information about the service implementation. The service management middleware handles the precise matching and invocation, separating the complexity of precise service location from the simplicity of service subscription, thereby reducing development costs while maintaining invocation precision.
3Speed
If applications directly access service information, then service invocation speed is improved, but coupling between applications and services increases
Solution Approach 1:
The patent implements preliminary action by having applications pre-subscribe to services based on service names and version ranges before actual invocation is needed. The service management middleware pre-establishes the subscription relationships and maintains the service subscription table, so that when service invocation is required, the matching can be performed quickly without complex real-time information exchange. This decouples applications from direct service information access while maintaining fast invocation through pre-established subscriptions.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Disclosed in the embodiments of the present application includes a service management method, an application management method, an apparatus, and a vehicle. The service management method includes: acquiring a new service and information corresponding to the new service; initializing a service subscription table of a vehicle based on the information corresponding to the new service; in response to a successful registration of the new service, acquiring a first target application based on the initialized service subscription table; publishing the new service to the first target application to inform the first target application that the new service is in an available status; and in response to an invoking request of the first target application for the new service, providing the first target application with service content corresponding to the new service. By means of the method, a plurality of tables related to services can be dynamically maintained by a middleware, such that when the first target application and the new service do not need to know detailed information about each other, the first target application may obtain service content corresponding to the new service by the invoking request, so as to realize decoupling between the service and the application, thereby reducing the development and management costs.