Methods, devices, and program carriers for cross-platform application migration

Abstract

This invention provides a method for cross-platform application migration, the method comprising: converting a source platform-specific application into an application executable on a vehicle platform, wherein the conversion includes: converting the source platform-specific user interface of the application to be converted into a web-based user interface; and converting calls to source platform-specific APIs in the application to be converted into calls to vehicle platform APIs. This invention also provides a device for cross-platform application migration, an application platform, a vehicle system, a system for cross-platform application migration, and a machine-readable program carrier. This invention eliminates the dependency of applications on different platforms and operating systems by directly porting applications from mobile terminals with specific ecosystems to vehicle platforms, reducing the difficulty of providing applications on vehicle platforms.

Description

Technical Field

[0001] The present invention relates to a method for cross-platform application migration, a device for cross-platform application migration, an application platform, a vehicle system, a system for cross-platform application migration, and a machine-readable program carrier. Background Technology

[0002] Currently, different vehicle manufacturers possess their own in-vehicle infotainment systems, upon which they can offer vehicle users applications with diverse services and content. However, developing these applications one by one requires significant time and effort. Furthermore, with the rapid development of the mobile internet, various content providers have developed a wealth of applications (so-called mobile applications) for consumers on smart mobile devices. How to migrate these mature applications from smart mobile device platforms to vehicle platforms is a major challenge.

[0003] To port applications from third-party mobile device platforms (or third-party application ecosystems) to vehicle platforms, many vehicle manufacturers rely on integrating their in-vehicle operating systems with Android or iOS (e.g., using an Android-based in-vehicle operating system). This approach has several disadvantages, including: requiring deep integration of the specific operating system (e.g., Android) with the vehicle's hardware and software; necessitating hardware and security modifications to meet vehicle requirements; and requiring additional hardware or hypervisors, often at significant overhead. Even with a specific operating system integrated into the vehicle, each native application typically needs to be tweaked and adapted, sometimes even completely rewritten, to fit the vehicle's operating system and environment. Furthermore, Android-based in-vehicle operating systems are limited to the Android ecosystem and cannot integrate or be compatible with other ecosystems.

[0004] Existing technologies also propose cloud-based distributed application systems, which aim to centrally deploy and host applications in the cloud, allowing applications to run on different types of devices. However, cloud-based distributed application systems also have shortcomings. For example, to obtain vehicle data resources, the vehicle must first synchronize it to a cloud server. This means that large amounts of user data operations (such as file reading and writing) also need to be stored in the cloud, posing risks to data security and user privacy. Furthermore, cloud-based distributed applications rely on a network connection between the terminal device and the cloud or server; they cannot function properly when the terminal device cannot connect to the network. Summary of the Invention

[0005] The present invention relates to a method for cross-platform application migration, a device for cross-platform application migration, an application platform, a vehicle system, a system for cross-platform application migration, and a machine-readable program carrier, in order to at least solve some of the problems in the prior art.

[0006] According to a first aspect of the present invention, a method for cross-platform application migration is provided, the method comprising:

[0007] Converting a source platform-specific application into a vehicle platform-compatible application, wherein the conversion includes:

[0008] Convert the source platform-specific user interface of the application to be converted into a web-based user interface;

[0009] Convert calls to source platform-specific APIs in the application to be converted into calls to vehicle platform APIs.

[0010] This invention particularly includes the following technical concept: by porting applications from mobile terminals based on specific ecosystems to vehicle platforms, automakers can easily port and deploy rich content and services from smart mobile device platforms to vehicle platforms (e.g., vehicle platforms) through in-vehicle app stores, without having to redevelop and compile the applications on the vehicle platform, thus significantly reducing the burden on content service providers and developers. Simultaneously, by performing conversions in user interface and API calls, the application's dependence on different underlying in-vehicle operating systems is eliminated or reduced, enabling the converted application to be used better across platforms / operating systems and improving the application's cross-platform / operating system versatility.

[0011] Optionally, the method further includes downloading, deploying, and / or installing the converted application onto the vehicle platform.

[0012] Here, unlike the common client-server based cloud sharing application model, it is not necessary to constantly synchronize vehicle data to the cloud in real time over the network when running the application. Instead, the transformed application is deployed on the vehicle platform, which allows it to reliably call and access local vehicle resources (such as GPS location information, vehicle unique identifiers, etc.), which greatly improves the security of vehicle data.

[0013] Optionally, the user interface transformation includes a transformation of the application in terms of UI / UX elements, wherein the conceptual description model of the application is transformed into a model relevant to the vehicle platform implementation.

[0014] Here, web-based applications are not limited by operating systems or platforms and possess secure isolation features. Through this adaptation of the conceptual description model, for example, by simply opening it in a browser on a vehicle platform, users can enjoy the same operating experience as on any operating system.

[0015] Optionally, the user interface transition includes:

[0016] Obtain the developer declarations of the application's UI / UX elements, including the display and logical attributes of the UI / UX elements. The display attributes specifically include annotations regarding the style, size, and / or layout of the UI / UX elements on the vehicle platform, and the logical attributes specifically include annotations regarding the interaction logic of the UI / UX elements on the vehicle platform.

[0017] Determine the rendering strategy;

[0018] Based on the rendering strategy, web-based UI / UX elements are generated using the display attributes and the logical attributes.

[0019] Here, since the original conceptual description model extracted from the application's source code or developer declarations already possesses sufficient abstraction, only backend logic transformation using an intermediate layer is required to complete the platform-to-platform mapping process, thereby significantly improving transformation efficiency.

[0020] Optionally, the API call conversion includes converting access to source platform system resources into access to vehicle platform resources, enabling the converted application to access the vehicle platform's hardware devices, local resources, and / or local data.

[0021] By modifying the API calls, applications can be enabled to check resource access permissions on the vehicle platform, ensuring data security.

[0022] Optionally, the conversion of the user interface and the conversion of API calls in the application conversion can be performed on one of the vehicle platform side, the vehicle platform cloud side, and the source platform side.

[0023] Here, since the conversion according to the invention is not limited by time and location, the flexibility of application migration is greatly improved. Especially when the network signal is poor, this conversion can be performed on a cloud server, thereby enabling the migration process to be executed more efficiently on the one hand, and reducing the hardware requirements and computing overhead on the vehicle's local premises on the other.

[0024] Optionally, the application conversion is performed in stages at two of the following locations: the vehicle platform side, the vehicle platform cloud side, and the source platform side.

[0025] For example, the transformation of vehicle-sensitive data can be performed locally on the vehicle, while the rest of the transformation can be performed on the source platform, thereby reducing the computational overhead on the vehicle side while ensuring data security.

[0026] Optionally, the API call conversion can be performed on the vehicle platform cloud side or the vehicle platform side, especially locally on the vehicle platform.

[0027] Here, the API call conversion process usually involves a large number of calls to and reads of vehicle local resources. Performing the interface with the physical layer and the interaction with vehicle local data resources on the vehicle side can ensure that data related to security and privacy are obtained and / or stored locally, avoiding the abuse of vehicle data by untrusted third-party platforms through content synchronization and sharing.

[0028] Optionally, the method further includes:

[0029] Receive migration or conversion requests for applications.

[0030] In response to a request to migrate or convert an application, the application is converted from a source platform-specific application to an application that can run on the vehicle platform.

[0031] Optionally, the migration or conversion request for the application may be initiated in response to a user's request to download or install the application on the vehicle platform and / or a request to use the application on the vehicle platform for the first time, or may be initiated by the system.

[0032] Optionally, the conversion of the application is not performed in advance based on a migration or conversion request.

[0033] This provides multiple application migration triggering mechanisms, which can be guided not only by the user's specific usage process, but also by performing pre-conversion during the development phase, thus expanding the application scenarios of this solution.

[0034] According to a second aspect of the present invention, an apparatus for cross-platform application migration is provided, the apparatus being configured to perform the method according to a first aspect of the present invention, the apparatus comprising:

[0035] The conversion module is configured to convert source platform-specific applications into applications that can run on the vehicle platform.

[0036] The conversion includes:

[0037] Convert the source platform-specific user interface of the application to be converted into a web-based user interface;

[0038] Convert calls to source platform-specific APIs in the application to be converted into calls to vehicle platform APIs.

[0039] According to a third aspect of the present invention, an application platform, particularly a vehicle platform, is provided, the application platform comprising: a user interface layer, a system layer, and an application interface layer; the application platform is configured to run an application transformed by means of the method described in the first aspect of the present invention.

[0040] Optionally, the application platform includes the device according to the second aspect of the invention.

[0041] According to a fourth aspect of the present invention, a vehicle system is provided, the vehicle system comprising the device according to a second aspect of the present invention and / or the application platform according to a third aspect of the present invention.

[0042] According to a fifth aspect of the present invention, a system for cross-platform application migration is provided, the system comprising a vehicle platform, a vehicle platform cloud, and a source platform ecosystem cloud, the system being configured to perform the method according to a first aspect of the present invention.

[0043] According to a sixth aspect of the invention, a machine-readable program carrier is provided, on which a computer program is stored, said computer program being configured to implement the method according to the first aspect of the invention when executed on a computer. Attached Figure Description

[0044] The invention will now be described in more detail with reference to the accompanying drawings, which will provide a better understanding of its principles, features, and advantages. The drawings include:

[0045] Figure 1 A block diagram of a device for cross-platform application migration according to an exemplary embodiment of the present invention is shown;

[0046] Figure 2 A block diagram of a system for cross-platform application migration according to an exemplary embodiment of the present invention is shown;

[0047] Figure 3 A flowchart illustrating a method for cross-platform application migration according to an exemplary embodiment of the present invention is shown;

[0048] Figure 4 A schematic diagram illustrating the migration of an application to a vehicle platform using an exemplary embodiment of the method according to the present invention is shown;

[0049] Figure 5 A schematic diagram illustrating the migration of an application to a vehicle platform using another exemplary embodiment of the method according to the invention is shown;

[0050] Figure 6A timing diagram is shown illustrating a method for cross-platform application migration according to an exemplary embodiment of the present invention; and

[0051] Figure 7 Another timing diagram is shown for implementing a method for cross-platform application migration according to an exemplary embodiment of the present invention. Detailed Implementation

[0052] To make the technical problems to be solved, the technical solutions, and the beneficial technical effects of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and several exemplary embodiments. It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the scope of protection of this invention.

[0053] Figure 1 A block diagram of a device for cross-platform application migration according to an exemplary embodiment of the present invention is shown.

[0054] In the context of this invention, the application includes, but is not limited to, word processing applications, spreadsheet applications, navigation applications, audio / video playback applications, email applications, database applications, game applications, and information retrieval applications.

[0055] like Figure 1 As shown, device 1 includes an application conversion module 3. In this embodiment, device 1 may also optionally include an interface module 2 and a download service module 4.

[0056] Interface module 2 may be configured as or connected to a user interface (UI) of the vehicle platform, and may include or be able to access various resource components of the vehicle (e.g., screen, speaker, microphone, touchscreen, and / or keyboard). Based on this user interface, it can present the user with the applications available on the vehicle platform and their list. Interface module 2 may also include a communication interface and be able to communicatively receive application migration requests from within the system or from outside the system. For example, such migration requests may be user-triggered download and / or installation requests for applications, or pre-conversion requests for applications automatically triggered by the system.

[0057] Interface module 2 can be connected to application conversion module 3 in a signal transmission manner. Application conversion module 3 can be configured, for example, as a conversion engine to convert source platform-specific applications into applications that can run on a vehicle platform (and other platforms or operating systems different from the source platform). The applications that can run on the vehicle platform can, for example, run on the vehicle platform in an operating system-independent manner, and can also be cross-platform applications that can run on different platforms in an operating system-independent manner. Application conversion can be performed based on migration or conversion requests, or it can be performed in advance without prior migration or conversion requests. Migration or conversion requests can be initiated, for example, in response to user requests to download or install applications on the vehicle platform and / or requests to use applications for the first time on the vehicle platform, or they can be initiated by the system. Application conversion can be performed synchronously or asynchronously. For example, synchronous application conversion can be performed simultaneously with receiving user requests to download or install applications on the vehicle platform and / or requests to use an application for the first time on the vehicle platform. Executing application conversion asynchronously can pre-complete the application conversion (e.g., in response to a pre-conversion request from the system) before a user initiates a request to download and install the application on the vehicle platform and / or to use the application on the vehicle platform for the first time; when the user initiates a request to download and install the application on the vehicle platform and / or to use the application on the vehicle platform for the first time, the (pre)conversion of the application has already been pre-completed.

[0058] In this invention, a source platform-specific application can be understood as an application developed for any specific mobile terminal platform (e.g., smartphone, smart tablet, laptop, wearable device, etc.) and / or a specific operating system (e.g., embedded Linux operating system, Windows operating system, Unix operating system, Android operating system, Mac OS X operating system and iOS operating system, specific in-vehicle operating system, etc.). These applications depend on the specific platform and / or specific operating system to run and cannot be directly run and used on other ecosystems (e.g., other platforms or other operating systems). According to one embodiment of the invention, a cross-platform application can be an application that can run independently of a specific platform and / or specific operating system (e.g., a hybrid application). These applications can function normally without deep integration with a specific platform and / or specific operating system. As an example, such a cross-platform application can be, for example, a web-based and / or containerized application.

[0059] As in Figure 1As exemplarily shown, the application conversion module 3 may include a UI / UX element conversion unit 10 and an API call conversion unit 20. The UI / UX element conversion unit 10 can convert the source platform-specific user interface (UI / UX) of the application to be converted into a web-based user interface. For example, the UI / UX element conversion unit 10 may be configured to convert the application in terms of UI / UX elements. In the context of this invention, UI elements can be understood as including control elements and layout elements presented on the user interface. Control elements include, for example, buttons, menus, scrollbars, windows, child windows, search bars, tables, graphics, etc., while layout elements represent, for example, the layout positioning, interaction events, interface animations, transitions, etc., between controls. UX elements depend on the user's operating experience, and this includes, for example, elements related to the design of the user's interaction methods.

[0060] In the UI / UX element conversion unit 10, for example, the conceptual description model of the source application can be converted into a model related to the vehicle platform implementation. For example, the developer declaration (e.g., source code) of the UI / UX elements of the source application can be obtained first. This developer declaration includes the display attributes and logical attributes of the UI / UX elements. The display attributes include comments about the style, size, and layout of the content elements on the vehicle platform, while the logical attributes include comments about the interaction logic of the content elements on the vehicle platform. After obtaining the display attributes and logical attributes, a rendering strategy can be determined, for example, using a state machine: for example, determining the corresponding rendering strategy (e.g., shading, culling, blending) based on the graphics display methods supported by the vehicle platform. Finally, based on the determined rendering strategy, a description document of the UI / UX elements on the vehicle platform is generated based on the display attributes and logical attributes, thereby generating web-based UI / UX elements that can be displayed in a browser.

[0061] As an example, the developer declaration of the application to be converted is "a button that, when clicked, redirects to another page". Therefore, in the conversion unit, this developer declaration is converted into a description document of the corresponding button and click event on the vehicle platform, as well as the corresponding web-based UI / UX elements, thereby completing the mapping from the abstract model to the vehicle platform model.

[0062] In addition to display and logical attributes, the application and its content elements can also obtain state attributes on the source platform. Based on these state attributes, the execution state of the application in the source platform's operating environment and user history preference data can be recorded. This allows the transformed application to continue running in the target container created in the vehicle platform system layer with the recorded state attributes.

[0063] Furthermore, the application conversion module 3 may also include an API (Application Programming Interface) call conversion unit 20. The API call conversion unit 20 can perform API call conversion. For example, it can convert API calls specific to the source platform in the application to be converted into API calls to the vehicle platform or API calls independent of a specific platform. In this process, specific access to source platform system resources is converted into access to vehicle platform resources. For example, by changing the API calls to define GPS information return requests, album access requests, incoming call interfaces, define the method of audio transmission to the speaker, obtain the mobile terminal's unique code, etc., the way resources and / or data are accessed and called is adapted to the vehicle platform's usage environment. As an example, when using a navigation application on a smartphone platform, the native API request for obtaining location information returns the mobile terminal's positioning standard and positioning coordinates. However, in a vehicle platform, only the national standard is generally supported, so only the positioning coordinates are returned, while the positioning standard, as the system default configuration, is not returned. Therefore, in a vehicle platform, for the normal operation of the application, the API call conversion unit can supplement the API with a positioning standard field, specifying it as the national standard.

[0064] By converting and adapting API calls, applications can achieve conversion and adaptation of interactive functions without deep integration with the vehicle platform at the operating system level. This ensures that neither application developers nor end users perceive any API differences. Taking the scanning function on a mobile terminal as an example, the native API is configured to access the user's mobile terminal's camera. After conversion using the method according to the present invention, the new API can, for example, request and access the vehicle's front-facing camera to take a picture, save the captured image file to a predetermined storage location, parse and read the image file through predetermined events, and then execute code to process the image file. However, if the vehicle does not support a camera, an error message similar to "no camera on the phone" will be displayed.

[0065] On a vehicle platform, browsers and / or container technology and / or the Vehicle Abstraction Layer (VAS) can be used as a means of communication between the transformed application and the underlying hardware devices or local resources and / or data of the vehicle platform, after the transformed application runs on the vehicle platform (e.g., the vehicle platform itself) or is loaded into a container on the vehicle platform.

[0066] exist Figure 1The document also exemplarily illustrates an (optional) download service module 4, which can be used, for example, to download unconverted, partially converted, or converted applications to the vehicle platform, and / or to deploy and / or install converted applications onto the vehicle platform. The download service module can also provide a runtime environment for the downloaded applications, enabling application components to run appropriately within the vehicle platform environment and to access resources and / or data within the vehicle platform. The application conversion module 3 is connected to the download service module 4 in a manner capable of bidirectional communication. According to one embodiment of the invention, in response to an application migration request, the download service module 4 can download source platform-specific applications to be converted from a cloud server (e.g., the source platform's ecosystem cloud, the original platform's application store, or the vehicle cloud), and then (e.g., using the application conversion module 3) convert these source platform-specific applications so that they can run on the vehicle platform side in a non-deeply integrated manner. According to another embodiment of the present invention, the application can also be pre-converted across platforms to eliminate its dependence on a specific platform or operating system, and the converted application installation package can be stored on a server or in the cloud (e.g., the ecosystem cloud of the source platform or the vehicle platform cloud); then, for example, in response to a user's request or instruction to download / install the corresponding application on the vehicle platform, the converted (cross-platform) application can be downloaded from the server or cloud and installed and run on the vehicle platform (e.g., through the download service module 4 on the vehicle platform). According to another embodiment of the present invention, the converted application can also be pre-deployed and / or installed on the vehicle platform as a pre-installed application (without requiring the user to download it from the server or cloud).

[0067] Figure 2 A block diagram of a system for cross-platform application migration according to an exemplary embodiment of the present invention is shown.

[0068] In this exemplary embodiment, the system for cross-platform application migration includes a vehicle platform 100, a vehicle platform cloud 200, and a source platform ecosystem cloud 300.

[0069] In this exemplary embodiment, the application platform used to run the cross-platform application is a vehicle platform. According to embodiments of the present invention, the target platform for cross-platform application migration may also include other platforms (e.g., other mobile devices) or other operating systems different from the source platform (i.e., the platform on which the application was based before migration or conversion). Reference Figure 2 The vehicle platform 100 is shown as part of the vehicle system and may include, for example, a user interface layer 110, a system layer 120, and an application interface layer 130.

[0070] The user interface layer 110 is used, for example, to implement human-computer interaction with the user and to present visual graphical components to the user in the form of a user interface (UI). For example, a web-based user interface can be used, enabling cross-platform (or platform-independent) application user interface display and interaction. Here, the web-based user interface can include UI components based on web technologies, such as standard web elements in the form of HTML, CSS, or JavaScript. These web elements can run in standard web browsers or web views, thus achieving cross-platform or platform independence. For example, most vehicle platforms or in-vehicle operating systems support web browsers or web views. As an example, an application store graphical element 111 and corresponding application list graphical elements 112, 113, and 114 can be presented to the user through the user interface.

[0071] In this exemplary embodiment, system layer 120 is configured to interact with user interface layer 110. System layer 120 may, for example, have a container-based application runtime environment, thereby serving as a virtualization solution enabling applications to run on different vehicle platforms or underlying operating systems (e.g., Linux-based vehicle platforms and Android-based vehicle platforms). Applications running in user interface layer 110 and / or system layer 120 may, for example, be cross-platform applications converted from source platform-specific applications (e.g., cross-platform applications that can run independently of the underlying operating system). In this exemplary embodiment, system layer 120 may include application conversion module 121, which may have… Figure 1 The application conversion module 3 in the illustrated embodiment has all or part of its functions. System layer 120 may also include an application management service module 122. The application management service module 122 is responsible for the lifecycle management of applications, including downloading, installing, uninstalling, and launching. System layer 120 may also include a Web Content Server module.

[0072] In this exemplary embodiment, the application interface layer 130 can be coupled to the system layer 120 in a manner that enables signal transmission. The application interface layer 130 can provide the system layer 120 and / or the applications running in the system layer 120 with access to the local hardware and software resources, functions and / or data (e.g., underlying hardware, vehicle data) of the vehicle platform underlying through, for example, an API interface.

[0073] In addition to vehicle platform 100, Figure 2The document also illustrates a vehicle platform cloud 200 and a source platform ecosystem cloud 300. In this embodiment, the vehicle platform cloud 200 is also referred to simply as the vehicle cloud. It may be, for example, a cloud or backend server provided by a vehicle manufacturer, and can directly communicate with the vehicle platform 100 to provide cloud services or backend services to the vehicle system. The vehicle cloud 200 includes, for example, an application store backend module 210 and a corresponding application management service module 220. The application management service module 220 can, for example, manage applications (e.g., cross-platform converted applications that can run on the vehicle platform) on the vehicle platform cloud; it can, for example, download applications from a third-party platform (e.g., the source platform ecosystem cloud 300) to the vehicle cloud; and it can, for example, push applications to the vehicle platform (e.g., the vehicle platform) based on application download requests from the vehicle platform (e.g., the vehicle platform). Optionally, the vehicle cloud 200 may also include an application conversion module 230, which may have… Figure 1 All or part of the functions of the application conversion module 3 in the illustrated embodiment.

[0074] The source platform ecosystem cloud 300 may be, for example, a third-party cloud or server for source platform-based applications, providing application packages 310 based on the source platform (different from the vehicle platform) (e.g., Android-based, Quick App-based, or Mini Program-based). Furthermore, the source platform ecosystem cloud 300 may include application development tools, enabling third-party application developers to develop various applications for this source platform ecosystem. Optionally, the source platform ecosystem cloud 300 may also include an application conversion module 330, which may have… Figure 1 All or part of the functions of the application conversion module 3 in the illustrated embodiment.

[0075] Figure 3 A flowchart of a method for cross-platform application migration according to an exemplary embodiment of the present invention is shown.

[0076] In optional step S1, it is possible (e.g., by means of) Figure 1 The interface module 2 shown receives application migration or conversion requests from users and / or the system. As an example, a user can trigger an application installation or usage request through corresponding actions within the user interface (UI) provided in the vehicle platform (e.g., the vehicle system). Such application requests can be transmitted to... Figure 1 The application conversion module 3 shown is shown.

[0077] In step S2, an application specific to the source platform can be converted (e.g., via application conversion module 3) into an application that can run on the vehicle platform (and other platforms or operating systems different from the source platform), enabling the application to run on the vehicle platform in a manner independent of the underlying operating system. Application conversion may include, for example, converting the source platform-specific user interface of the application to be converted into a web-based user interface; and converting calls to source platform-specific APIs in the application to be converted into API calls to the vehicle platform. Application conversion may be performed based on, for example, a migration or conversion request as described in step S1, or it may be performed in advance without a migration or conversion request.

[0078] According to embodiments of the present invention, step S3 may optionally be included before or after the conversion step S2. In step S3, the converted, unconverted, or partially converted application can be downloaded / installed from the server or cloud to the vehicle platform, so that the application can be run and used on the vehicle platform even without internet connection.

[0079] Figure 4 A schematic diagram illustrating the migration of an application to a vehicle platform using an exemplary embodiment of the method according to the invention is shown.

[0080] exist Figure 4The exemplary embodiment shown depicts a vehicle platform 100'. Cross-platform conversion of the application can be performed in stages on the vehicle platform 100' and the source platform ecosystem cloud 300'. This application conversion is divided into two stages. In the first stage, the application user interface is converted in the source platform ecosystem cloud 300', transforming the user interface of the source platform-specific application into a web-based user interface. For example, the UI / UX elements of the source platform-specific native application 400 are converted into web-based UI / UX elements, thereby forming a partially converted (user interface converted) application 401. Next, this partially converted application 401 is downloaded from the source platform ecosystem cloud 300' to the vehicle cloud 200'. Subsequently, the vehicle platform 100' can, for example, download the partially converted application 401 to the vehicle's local storage (i.e., to the vehicle platform 100') using a corresponding application management service module, for the second stage of conversion. In the vehicle platform 100', for example, the application conversion module 121' in the system layer 120' can perform a second-stage conversion on the application 401, namely, API call conversion, converting the source platform-specific native API calls into vehicle platform API calls, thereby enabling the converted application to access the local resources, functions, and / or data of the vehicle platform (in this embodiment, the vehicle platform). The application that has undergone user interface conversion and API call conversion can, for example, run on the vehicle platform based on Web and / or container technologies, and can, for example, access the local resources, functions, and / or data of the vehicle platform through the application interface layer 130'.

[0081] Figure 5 A schematic diagram of a method for migrating an application to a vehicle platform according to another exemplary embodiment of the present invention is shown.

[0082] exist Figure 5 The exemplary embodiment shown depicts a vehicle platform 100". The cross-platform conversion of the application can be performed in stages on the vehicle platform 100 and the vehicle cloud 200. Here, the application conversion is also performed in two stages, however, unlike... Figure 4 In the embodiment shown, the application conversion is no longer performed on the source platform ecosystem cloud 300 (or on the source platform side), but is performed entirely on the vehicle platform side or vehicle cloud. The advantage of this is that it can better protect the security of vehicle data resources.

[0083] In this embodiment, the application 400' to be migrated is first downloaded from the source platform side (e.g., source platform ecosystem cloud 300") to the vehicle cloud 200". Then, in the vehicle cloud 200", the application user interface is transformed, converting the user interface of the source platform-specific application into a web-based user interface. For example, the UI / UX elements of the source platform-specific native application 400' are converted into web-based UI / UX elements, thus forming a partially transformed (user interface transformed) application 401'. Next, this partially transformed application 401' can be downloaded from the vehicle cloud 200 to the vehicle platform 100. On the vehicle platform, for example, the transformation module 121 in the system layer 120' of the vehicle platform 100" can perform a second stage of transformation on the application 401', namely, API call transformation, converting the source platform-specific API calls into vehicle platform API calls, thereby enabling the transformed application to access the local resources, functions, and / or data of the vehicle platform. The application that has undergone user interface transformation and API call transformation can, for example, run on the vehicle platform based on web and / or container technologies, and can, for example, access the local resources, functions, and / or data of the vehicle platform through the application interface layer 130".

[0084] According to different embodiments of the present invention, the conversion of the user interface and the conversion of API calls in the application conversion can be performed on one of the vehicle platform side, the vehicle platform cloud side and the source platform side (e.g., the source platform ecosystem cloud), or they can be performed in stages on two of the vehicle platform side, the vehicle platform cloud side and the source platform side (e.g., the source platform ecosystem cloud).

[0085] Figure 6 A timing diagram is shown for implementing a method for cross-platform application migration according to an embodiment of the present invention.

[0086] refer to Figure 6The various nodes or entities involved are shown at the top: user 600, vehicle platform (vehicle in this example) 601, vehicle platform cloud (vehicle cloud in this embodiment) 602, and source platform system ecosystem cloud 603. According to different embodiments of the invention: the conversion module for cross-platform application migration according to the invention can be arranged on one or more of vehicle 601, vehicle cloud 602, and source platform system ecosystem cloud 603. In step S101, user 600 triggers a request to download and / or install an application on the in-vehicle platform provided by vehicle 601, for example, through appropriate interactive operations. In step S102, vehicle 601 sends the application download and / or installation request to vehicle cloud 602. Then, in step S103, vehicle cloud 602 determines whether the installation package of the application requested by the user exists on its server (e.g., an application installation package that can run on the target vehicle platform after pre-conversion by the source platform-specific application according to the cross-platform application migration / conversion method of the invention). If it exists, the installation package is directly returned to vehicle 601. If it does not exist, then in step S103, the vehicle cloud 602 can forward the request to download the application installation package to the source platform system ecosystem cloud 603.

[0087] According to one embodiment of the present invention, in optional step S104, the source platform-specific application can be converted into an installation package of an application that can run on the target vehicle platform in the source platform system ecosystem cloud 603 (e.g., using a conversion module arranged there); in step S105, the converted application installation package is downloaded to the vehicle cloud 601, and in step S106, it is further downloaded to the local vehicle 601. Finally, in step S107, the installation and operation of the application are completed in the vehicle 601.

[0088] According to another embodiment of the present invention, the cross-platform conversion of the application can be performed without performing the cross-platform conversion in the source platform system ecosystem cloud 603. Instead, in step S105, the unconverted source platform-specific application is downloaded to the vehicle cloud 602, and then converted into an application that can run on the target vehicle platform in the vehicle cloud.

[0089] Alternatively, as mentioned earlier, the transformation of the user interface and API calls in the application transformation can be carried out in stages at two of the following locations: the vehicle platform side, the vehicle platform cloud side, or the source platform side (e.g., the source platform ecosystem cloud).

[0090] Figure 7 Another signal timing diagram is shown during the implementation of the method for cross-platform application migration according to the present invention.

[0091] Here, also at the top, are the various nodes or entities involved: user 700, vehicle platform (vehicle 701 in this example), vehicle platform cloud (vehicle cloud in this embodiment) 702, and source platform system ecosystem cloud 703. According to different embodiments of the present invention: the conversion module for cross-platform application migration according to the present invention can be arranged on one or more of vehicle 701, vehicle cloud 702, and source platform system ecosystem cloud 703.

[0092] In step S201, user 700 triggers an initial request for the application to be used on the in-vehicle platform provided by vehicle 701 through an interactive operation. In response, steps S202 to S207 then sequentially execute the following steps: update detection, update request, cross-platform conversion of the update data package, downloading the update data package, preparing runtime data, and launching the application. Up to step S206, the application conversion and... Figure 6 The initial download and installation process is the same. However, when preparing runtime data in step S207, additional local conversions may be involved in vehicle 701, such as updating application authorization information (to ensure the security of vehicle data and / or functions).

[0093] Although specific embodiments of the invention have been described in detail herein, they are given for illustrative purposes only and should not be construed as limiting the scope of the invention. Various substitutions, alterations, and modifications can be conceived without departing from the spirit and scope of the invention.

Claims

1. A method for cross-platform application migration, the method comprising: The process involves converting a source platform-specific application into an application that can run on a vehicle platform. The source platform-specific application is one developed for and dependent on a specific operating system, and the converted application runs on the vehicle platform in an operating system-independent manner. The conversion includes: The application to be converted transforms the source platform-specific user interface into a web-based user interface. After user interface and API call conversion, the application runs on the vehicle platform's container-based runtime environment based on web technology. Calls to source platform-specific APIs in the application to be converted are transformed into calls to vehicle platform APIs in the following way: The converted application accesses the local resources, functions and / or data of the vehicle platform through the application interface layer, which provides the converted application with access to the underlying local hardware and software resources, functions and / or data of the vehicle platform through API interfaces.

2. The method according to claim 1 further includes downloading, deploying, and / or installing the converted application onto the vehicle platform.

3. The method according to claim 1 or 2, wherein, The transformation of the user interface includes the transformation of the application in terms of UI / UX elements, wherein the conceptual description model of the application is transformed into a model related to the vehicle platform implementation.

4. The method according to any one of claims 1 to 3, wherein, The user interface transition includes: Obtain the developer declarations of the application's UI / UX elements, including the display and logical attributes of the UI / UX elements. The display attributes specifically include annotations regarding the style, size, and / or layout of the UI / UX elements on the vehicle platform, and the logical attributes specifically include annotations regarding the interaction logic of the UI / UX elements on the vehicle platform. Determine the rendering strategy; Based on the rendering strategy, web-based UI / UX elements are generated using the display attributes and the logical attributes.

5. The method according to any one of claims 1 to 4, wherein, The API call conversion includes converting access to source platform system resources into access to vehicle platform resources, enabling the converted application to access the vehicle platform's hardware devices, local resources, and / or local data.

6. The method according to any one of claims 1 to 5, wherein, The conversion of the user interface and the conversion of API calls in the application conversion are performed on one of the vehicle platform side, the vehicle platform cloud side and the source platform side, or in stages on two of the vehicle platform side, the vehicle platform cloud side and the source platform side respectively; preferably, the conversion of API calls is performed on the vehicle platform cloud side or the vehicle platform side, especially on the vehicle platform local.

7. The method according to any one of claims 1 to 6, wherein, The method further includes: Receive migration or conversion requests for applications. In response to a request to migrate or convert an application, the application is converted from a source platform-specific application to an application that can run on the vehicle platform.

8. The method according to claim 7, wherein, The migration or conversion request for the application is initiated in response to a user's request to download or install the application on the vehicle platform and / or a request to use the application on the vehicle platform for the first time, or is initiated by the system.

9. The method according to any one of claims 1 to 6, wherein, The conversion of the application is not performed in advance based on a migration or conversion request.

10. An apparatus for cross-platform application migration, the apparatus being configured to perform the method according to any one of claims 1 to 9, the apparatus comprising: The conversion module is configured to convert source platform-specific applications into applications that can run on the vehicle platform. The conversion includes: Convert the source platform-specific user interface of the application to be converted into a web-based user interface; Convert calls to source platform-specific APIs in the application to be converted into calls to vehicle platform APIs.

11. An application platform, particularly a vehicle platform, said application platform comprising: User interface layer, system layer, and application interface layer; The application platform is configured to run applications transformed using the method described in any one of claims 1 to 9.

12. The application platform according to claim 11, characterized in that, The application platform includes the device according to claim 10.

13. A vehicle system comprising the device according to claim 10 and / or the application platform according to claim 11 or 12.

14. A system for cross-platform application migration, the system comprising a vehicle platform, a vehicle platform cloud, and a source platform ecosystem cloud, the system being configured to perform the method according to any one of claims 1 to 9.

15. A machine-readable program carrier having a computer program stored thereon, the computer program being able to perform the method according to any one of claims 1 to 9 when it is run on a computer.

Images