AUTOSAR Service Instance Mapping for Connector Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The manual establishment of mapping relationships for communication services in the AUTOSAR adaptive platform is complex and inefficient, particularly in configuring communication management (CM) for intelligent vehicles with multiple auxiliary functions.

Innovation Solution

A method and apparatus that automatically create mapping relationships between service instances and communication connectors by determining network domain IDs and using communication connector information sets, eliminating the need for manual operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If mapping relationships are established manually for each communication service instance, then the mapping relationship accuracy is ensured, but the configuration complexity and time consumption increase significantly

Engineering Contradiction:
Improvemapping relationship accuracyVSAvoidconfiguration complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-establishing mapping relationships between communication connectors and network domains at the configuration stage. The system pre-configures the mapping between service instances and communication connectors based on predetermined rules and templates, so that when communication services are deployed, the mapping relationships are already in place and do not require manual establishment for each instance.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating template-based mapping relationships that can be replicated across multiple service instances. Instead of manually configuring each instance individually, the system defines a standard mapping template that automatically copies the correct communication connector mappings to all service instances of the same type, ensuring consistency while reducing configuration effort.

Inventive Principle:
Principle #26Copying

2Measurement precision

If mapping relationships are established manually for each communication service instance, then the configuration accuracy is maintained, but the configuration efficiency decreases

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidconfiguration efficiency
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent applies universality by creating a unified mapping management system that handles multiple service instances through a single configuration interface. The system defines universal mapping templates that can be applied across different service types and instances, allowing the same mapping rules to be universally applied throughout the system rather than requiring separate manual configuration for each instance.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system automatically copies mapping relationships from templates to multiple service instances, ensuring configuration accuracy is maintained while dramatically improving efficiency. The copying mechanism preserves the exact mapping relationships defined in templates across all instances, eliminating manual repetition while maintaining consistency.

Inventive Principle:
Principle #26Copying

3Productivity

If automated methods are used to establish mapping relationships, then the configuration efficiency is improved, but the system complexity increases

Engineering Contradiction:
Improveconfiguration efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary configuration management system that acts as a mediator between service instances and communication connectors. This intermediary layer automatically manages the mapping relationships based on predefined rules and templates, shielding users from the underlying complexity while maintaining high configuration efficiency. The intermediary handles the complex matching logic internally through standardized interfaces.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system uses parameter changes by dynamically adjusting mapping parameters based on service instance characteristics. Instead of hardcoding complex mapping logic, the system changes mapping parameters automatically based on input parameters such as service type, network domain, and communication protocol, allowing automated configuration without requiring complex system architecture.

Inventive Principle:
Principle #35Parameter changes

4Extent of automation

If automated service instance creation is implemented, then manual operations are eliminated, but the automation extent increases system complexity

Engineering Contradiction:
Improveautomation levelVSAvoidsystem complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The patent implements self-service by enabling service instances to automatically obtain their mapping relationships without external manual intervention. When a service instance is created, it automatically queries the configuration management system using its identifying parameters and receives the appropriate mapping information autonomously. This self-service mechanism eliminates manual operations while keeping the system complexity manageable through standardized self-configuration protocols.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12549446B2Mapping relationship generation method and apparatus, and storage medium
Publication Date: 2026.02.10 YINWANG INTELLIGENT TECHNOLOGIES CO LTD
  • US12549446B2 patent drawing
  • US12549446B2 patent drawing
  • US12549446B2 patent drawing

AI summary

A mapping relationship generation method includes: obtaining information about a mapping relationship between a communication connector on a node and a network domain; obtaining information about a mapping relationship between a process and the node, where the information about the mapping relationship between the process and the node includes a software component corresponding to the process, and the software component includes at least one port prototype; creating, based on the information about the mapping relationship between the communication connector on the node and the network domain and the information about the mapping relationship between the process and the node, a service instance for the port prototype used by the process in the network domain; and creating a mapping relationship between the service instance and a target communication connector on the node.