# US 2026/0037259 A1 · Method, Device and Program Carrier for Cross-Platform Porting of Applications

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0037259 A1
- Document ID: US20260037259A1
- Status: Published application
- Kind: A1
- Application number: 18/996,359
- Filed: 2023-07-19
- Published: 2026-02-05
- Earliest claimed: 2022-07-19
- Assignees: Mercedes-Benz Group AG
- Applicants: Mercedes-Benz-Group AG
- Inventors: Hao HU; Ming WAN; Xuefei DUAN
- Web page: https://patentgrep.com/patent/US20260037259A1

## CPC

- G06F 8/76: Adapting program code to run in a different environment; Porting
- G06F 8/51: Source to source
- G06F 8/61: Installation
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method for cross-platform porting of applications includes converting a source-platform-specific application into an application that can be run on an in-vehicle platform. The converting includes converting a source-platform-specific user interface of the application to be converted into a web-based user interface and converting a call to a source-platform-specific application programming interface (API) of the application to be converted into a call to an in-vehicle platform API.

## Claims

### Claim at position 1

-15. (canceled)

### Claim 16

A method for cross-platform porting of applications, comprising the steps of:
converting a source-platform-specific application into an application that can be run on an in-vehicle platform;
wherein the converting comprises:
converting a source-platform-specific user interface of the application to be converted into a web-based user interface; and
converting a call to a source-platform-specific application programming interface (API) of the application to be converted into a call to an in-vehicle platform API.

### Claim 17 (depends on 16)

The method according to claim 16, wherein the method further comprises downloading, deploying and/or installing the converted application to the in-vehicle platform.

### Claim 18 (depends on 16)

The method according to claim 16, wherein the converting of the user interface comprises conversion of the application in an aspect of UI/UX elements, and wherein a conceptual description model of the application is converted into a model related to realization of the in-vehicle platform.

### Claim 19 (depends on 16)

The method according to claim 16, wherein the converting of the user interface comprises:
acquiring a developer statement of UI/UX elements of the application, which developer statement includes display attributes and logical attributes of the UI/UX elements, wherein the display attributes include annotations about a style, a size and/or a layout of the UI/UX elements in the in-vehicle platform, and the logical attributes include annotations about interactive logic of the UI/UX elements in the in-vehicle platform;
determining rendering strategies; and
generating web-based UI/UX elements based on the display attributes and the logical attributes according to the rendering strategies.

### Claim 20 (depends on 16)

The method according to claim 16, wherein the converting of the API call comprises converting an access to system resources of the source platform into an access of system resources of the in-vehicle platform such that the converted application can access hardware devices, local resources and/or local data of the in-vehicle platform.

### Claim 21 (depends on 16)

The method according to claim 16, wherein both the converting of the user interface and the converting of the API call of the application conversion are performed at one of the in-vehicle platform side, an in-vehicle platform cloud side and the source platform side, or are performed in stages at two of the in-vehicle platform side, the in-vehicle platform cloud side and the source platform side respectively.

### Claim 22 (depends on 16)

The method according to claim 16, wherein the method further comprises:
receiving a request for application porting or conversion; and
converting a source-platform-specific application into an application that can be run on the in-vehicle platform in response to the request for application porting or conversion.

### Claim 23 (depends on 22)

The method according to claim 22, wherein the request for application porting or conversion is initiated in response to a user-initiated request to download and/or install an application on the in-vehicle platform and/or a user-initiated request to use an application on the in-vehicle platform for a first time, or is initiated by the system.

### Claim 24 (depends on 16)

The method according to claim 16, wherein the converting of the application is performed in advance without being based on a request for porting or conversion.

### Claim 25 (depends on 16)

A device for cross-platform porting of applications, wherein the device is configured to perform the method according to claim 16, the device comprising:
a conversion module which is configured to convert a source-platform-specific application into an application that can be run on an in-vehicle platform by:
converting a source-platform-specific user interface of the application to be converted into a web-based user interface; and
converting a call to a source-platform-specific API of the application to be converted into a call to an in-vehicle platform API.

### Claim 26 (depends on 16)

An application platform, comprising:
a user interface layer, a system layer and an application interface layer; wherein the application platform is configured to run applications that are converted by the method according to claim 16.

### Claim 27 (depends on 26)

The application platform according to claim 26, wherein the application platform is an in-vehicle platform,

### Claim 28 (depends on 16, 26)

The application platform according to claim 26, wherein the application platform further comprises:
a device for cross-platform porting of applications, wherein the device is configured to perform the method according to claim 16, the device comprising:
a conversion module which is configured to convert a source-platform-specific application into an application that can be run on an in-vehicle platform by:
converting a source-platform-specific user interface of the application to be converted into a web-based user interface; and
converting a call to a source-platform-specific API of the application to be converted into a call to an in-vehicle platform API.

### Claim 29 (depends on 16)

A system for cross-platform porting of applications, comprising:
an in-vehicle platform, an in-vehicle platform cloud and a source platform ecosystem cloud, wherein the system is configured to perform the method according to claim 16.
