Mobile terminal application cross-platform migration method and device

Abstract

The invention provides a mobile terminal application cross-platform migration method and device which are used for configuring a corresponding mobile terminal application cross-platform conversion model on the basis of intelligent AI model processing capacity, so that migration processing or adaptation processing from a mobile terminal application to a target platform environment is efficiently, accurately and automatically completed, and the migration efficiency of the mobile terminal application to the target platform environment is improved. The manpower and material resource cost caused by dependence on software development engineers in the prior art is avoided as much as possible, and a good guarantee can be provided for popularization and application of the mobile terminal application in a new target platform environment.

Description

Technical Field

[0001] This application relates to the field of computer technology, and specifically to a method and apparatus for cross-platform migration of mobile applications. Background Technology

[0002] Mobile applications are client applications that run on various types of mobile devices, including smartphones, tablets, smart bracelets, smartwatches, or personal digital assistants (PDAs). Compared to terminal devices such as desktop computers, laptops, or all-in-one computers, their user interface (UE) is highly convenient.

[0003] It is understandable that in the business field, even mobile devices of the same type can differ depending on the system platform they run. Therefore, mobile applications also need to be adapted to the differences between different system platforms. In addition, even if the system platform is the same, adaptation is also required in terms of device manufacturer, application distribution channel, or applicable region. Thus, even the same mobile application often has multiple versions in practice due to different platform environments.

[0004] The inventors of this application have noticed that configuring application files or configuration data for mobile applications to address the differences between different platform environments increases the cost of manual software development work. Taking system platforms as an example, before the emergence or widespread adoption of the HarmonyOS operating system, software development teams / companies typically only needed to have software development engineers for the corresponding Android operating system and software development engineers for the corresponding iOS operating system. If software development engineers for the corresponding HarmonyOS operating system were also required, it would obviously require the original software development engineers to spend a considerable amount of time getting familiar with the new development environment. Furthermore, if new software development engineers specifically for the HarmonyOS operating system were to be added, it would obviously bring additional costs in terms of human and material resources. Summary of the Invention

[0005] This application provides a method and apparatus for cross-platform migration of mobile applications. Based on intelligent AI model processing capabilities, it configures a corresponding cross-platform conversion model for mobile applications, thereby efficiently and accurately completing the migration or adaptation of mobile applications to the target platform environment. This minimizes the human and material costs associated with relying on software development engineers and provides a good guarantee for the promotion and application of mobile applications in the new target platform environment.

[0006] Firstly, this application provides a method for cross-platform migration of mobile applications, which includes:

[0007] Obtain the initial configuration data of the mobile application to be migrated to the target platform environment;

[0008] The first configuration data is input into the pre-configured mobile application cross-platform conversion model, which then performs the corresponding mobile application cross-platform conversion process. The mobile application cross-platform conversion model is obtained by training the initial transform model with the configuration data of the labeled sample mobile applications. The mobile application cross-platform conversion model is used to convert the configuration data input to the model into configuration data that is adapted to the target platform environment.

[0009] Extract the second configuration data, which corresponds to the first configuration data, from the output of the cross-platform conversion model of the mobile application.

[0010] In conjunction with the first aspect of this application, in the first possible implementation of the first aspect of this application, both the first configuration data and the second configuration data include the corresponding code and the UI component library usage data.

[0011] The first configuration data also includes annotations or tags configured for key content, taking into account the language characteristics of the corresponding platform.

[0012] In conjunction with the first aspect of this application, in a second possible implementation of the first aspect of this application, before inputting the first configuration data into the pre-configured mobile application cross-platform conversion model, the mobile application cross-platform migration method further includes:

[0013] The preset splitting strategy is invoked to split the first configuration data and obtain multiple sub-configuration data.

[0014] Input multiple sub-configuration data into a pre-configured cross-platform conversion model for mobile applications.

[0015] In conjunction with the second possible implementation of the first aspect of this application, in the third possible implementation of the first aspect of this application, the segmentation strategy is specifically based on at least one segmentation element among preset annotations, tags, lengths, paragraphs, and functional modules for segmentation.

[0016] In conjunction with the first aspect of this application, in the fourth possible implementation of the first aspect of this application, after extracting the second configuration data output by the mobile application cross-platform conversion model that corresponds to the first configuration data, the mobile application cross-platform migration method further includes:

[0017] The second configuration data is displayed to allow for verification and fine-tuning during the manual verification process;

[0018] The second configuration data, which has passed the manual verification process, will be compiled, packaged, and uploaded to the application store of the target platform environment.

[0019] Secondly, this application provides a mobile application cross-platform migration device, which includes:

[0020] The acquisition unit is used to acquire the first configuration data of the mobile application to be migrated to the target platform environment;

[0021] The conversion unit is used to input the first configuration data into the pre-configured mobile application cross-platform conversion model, so that the mobile application cross-platform conversion model can perform the corresponding mobile application cross-platform conversion processing. The mobile application cross-platform conversion model is obtained by training the initial transform model with the configuration data of the labeled sample mobile applications. The mobile application cross-platform conversion model is used to convert the configuration data input to the model into configuration data adapted to the target platform environment.

[0022] The extraction unit is used to extract the second configuration data output by the cross-platform conversion model of the mobile application, which corresponds to the first configuration data.

[0023] In conjunction with the second aspect of this application, in the first possible implementation of the second aspect of this application, both the first configuration data and the second configuration data include the corresponding code and the UI component library usage data.

[0024] The first configuration data also includes annotations or tags configured for key content, taking into account the language characteristics of the corresponding platform.

[0025] In conjunction with the second aspect of this application, in a second possible implementation of the second aspect of this application, the mobile application cross-platform migration apparatus further includes a segmentation unit, used for:

[0026] The preset splitting strategy is invoked to split the first configuration data and obtain multiple sub-configuration data.

[0027] Input multiple sub-configuration data into a pre-configured cross-platform conversion model for mobile applications.

[0028] In conjunction with the second possible implementation of the second aspect of this application, in the third possible implementation of the second aspect of this application, the segmentation strategy is specifically based on at least one segmentation element among preset annotations, tags, lengths, paragraphs, and functional modules for segmentation.

[0029] In conjunction with the second aspect of this application, in a fourth possible implementation of the second aspect of this application, the mobile application cross-platform migration apparatus further includes an application unit, used for:

[0030] The second configuration data is displayed to allow for verification and fine-tuning during the manual verification process;

[0031] The second configuration data, which has passed the manual verification process, will be compiled, packaged, and uploaded to the application store of the target platform environment.

[0032] Thirdly, this application provides a processing device, including a processor and a memory, wherein a computer program is stored in the memory, and when the processor invokes the computer program in the memory, it executes the method provided by the first aspect of this application or any possible implementation of the first aspect of this application.

[0033] Fourthly, this application provides a computer-readable storage medium storing a plurality of instructions adapted for loading by a processor to perform the method provided in the first aspect of this application or any possible implementation thereof.

[0034] From the above, it can be concluded that this application has the following beneficial effects:

[0035] For the cross-platform migration of mobile applications, this application obtains the first configuration data of the mobile application to be migrated to the target platform environment, and then inputs the first configuration data into a pre-configured mobile application cross-platform conversion model. This causes the mobile application cross-platform conversion model to perform the corresponding mobile application cross-platform conversion processing. Since this mobile application cross-platform conversion model is obtained by training an initial transform model with the configuration data of labeled sample mobile applications, and is used to convert the configuration data input to the model into configuration data adapted to the target platform environment, the corresponding mobile application cross-platform conversion model is configured based on the intelligent AI model processing capability. This efficiently and accurately completes the migration or adaptation processing of mobile applications to the target platform environment automatically, minimizing the human and material costs caused by relying on software development engineers. This provides a good guarantee for the promotion and application of mobile applications in the new target platform environment. Attached Figure Description

[0036] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0037] Figure 1 This is a flowchart illustrating a method for cross-platform migration of mobile applications according to this application.

[0038] Figure 2 This is a schematic diagram of a mobile application cross-platform migration device according to this application.

[0039] Figure 3 This is a schematic diagram of one type of processing equipment used in this application. Detailed Implementation

[0040] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0041] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in a sequence other than that illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or device that includes a series of steps or modules is not necessarily limited to those explicitly listed, but may include other steps or modules not explicitly listed or inherent to such processes, methods, products, or devices. The naming or numbering of steps appearing in this application does not imply that the steps in the method flow must be performed in the chronological / logical order indicated by the naming or numbering. The execution order of named or numbered process steps can be changed according to the desired technical purpose, as long as the same or similar technical effect is achieved.

[0042] The module division described in this application is a logical division. In practical applications, there may be other division methods. For example, multiple modules may be combined or integrated into another system, or some features may be ignored or not executed. In addition, the coupling or direct coupling or communication connection between modules shown or discussed may be through some interfaces, and the indirect coupling or communication connection between modules may be electrical or other similar forms, none of which are limited in this application. Furthermore, the modules or sub-modules described as separate components may or may not be physically separated, may or may not be physical modules, or may be distributed in multiple circuit modules. Some or all of the modules may be selected to achieve the purpose of the solution in this application according to actual needs.

[0043] Before introducing the cross-platform migration method for mobile applications provided in this application, we will first introduce the background content involved in this application.

[0044] The mobile application cross-platform migration method, apparatus, and computer-readable storage medium provided in this application can be applied to processing devices to configure corresponding mobile application cross-platform conversion models based on intelligent AI model processing capabilities. This enables efficient and accurate automatic migration or adaptation of mobile applications to the target platform environment, minimizing the human and material costs previously incurred by relying on software development engineers. It provides a good guarantee for the promotion and application of mobile applications in the new target platform environment.

[0045] The mobile application cross-platform migration method mentioned in this application can be implemented by a mobile application cross-platform migration device, or by different types of processing devices such as servers, physical hosts, or user equipment (UE) that integrate the mobile application cross-platform migration device. The mobile application cross-platform migration device can be implemented in hardware or software. The UE can be a terminal device such as a smartphone, tablet, laptop, desktop computer, or personal digital assistant (PDA). The processing devices can be configured in a device cluster.

[0046] It is understood that the focus of this application is to convert the mobile applications that need to be migrated to the target platform environment in order to achieve the effect of adapting to the target platform environment. This process mainly involves local data processing. Therefore, the processing device that executes the cross-platform migration method of mobile applications provided in this application, or the processing device that carries the application service corresponding to the cross-platform migration method of mobile applications provided in this application, only needs to have the required data processing capabilities to meet the requirements. In this case, the processing device can be a server, a physical host, or even a UE. Its specific device type and device deployment form are quite flexible, and this application does not impose specific restrictions.

[0047] As an example, this solution allows for local processing of mobile applications on the physical host that the software development engineer, who was originally responsible for the development / maintenance of the mobile application, previously relied on for their work.

[0048] For example, a software development team / company can deploy a cloud service. The software development engineer who was originally responsible for the development / maintenance of the mobile application can upload the target application to the corresponding server on the cloud server, or trigger the server to automatically retrieve the mobile application. In this way, the server can remotely process the mobile application through the solution proposed in this application, which facilitates the deployment of powerful data processing capabilities on the server side and provides work support for the migration / adaptation of the platform environment of the mobile application within the team / company.

[0049] The following section introduces the cross-platform migration method for mobile applications provided in this application.

[0050] First, refer to Figure 1 , Figure 1 This paper illustrates a flowchart of a mobile application cross-platform migration method according to this application. The mobile application cross-platform migration method provided by this application may specifically include the following steps S101 to S103:

[0051] Step S101: Obtain the first configuration data of the mobile application to be migrated to the target platform environment;

[0052] It is important to understand that the migration involved in this application is not the installation process when deploying the mobile application on the target platform environment (this installation process is something that application users can usually perceive), but rather the processing of the mobile application on the side of the software development engineer / team / company to transform the original mobile application to adapt to the target platform environment. This allows the transformed mobile application to run normally or even efficiently in the target platform environment, providing the expected application services, avoiding problems such as inability to recognize or run the application, and ensuring a good user experience for application users.

[0053] As an example, the original platform environment of the mobile application in this application can be the Android operating system or the iOS operating system, and the target platform environment can be the Harmony operating system.

[0054] Software development for the Android operating system typically uses programming languages ​​such as Java or Kotlin, and the UI components used are usually the Android SDK. Software development for the iOS operating system typically uses programming languages ​​such as Swift or Objective-C, and the UI components used are usually UIKit or SwiftUI. Software development for the Harmony operating system typically uses the ArkTS programming language, and the UI components used are usually ArkUI.

[0055] As an example here, when a software development engineer has just finished developing a mobile application corresponding to the Android or iOS operating system, the mobile application can be actively identified or passively identified as the processing object of this application solution under manual triggering, and the application solution can be triggered to perform migration processing to adapt to the Harmony operating system.

[0056] Furthermore, for mobile applications, when it is necessary to migrate them to the target platform environment, it is of course necessary to obtain the mobile application for specific data processing, so as to obtain a mobile application that can be installed / deployed on the target platform environment.

[0057] This process is based on the configuration data of the mobile application. The configuration data involved in this application can be the file data of the application installation package that is intuitive and perceptible to the application user, or it can be the data after the application installation package is unpacked or the data before it is packaged into the application installation package, or it can be the data from an earlier time before it is packaged into the application installation package. In other words, the configuration data can be the data of the mobile application at any stage of software development without involving any substantial content adjustment.

[0058] For ease of explanation, this application refers to the original configuration data obtained here as the first configuration data, and the corresponding configuration data subsequently migrated to the target platform environment as the second configuration data.

[0059] Furthermore, in practical applications, the automatic migration processing of current mobile applications in this application is usually initiated in the form of tasks. The mobile application migration task defaults to or specifies the mobile application to be processed. Specifically, the task can be initiated manually, or the device can initiate the task autonomously according to a preset autonomous initiation strategy, or the task can be forwarded from other devices. All of these are possible.

[0060] Among them, mobile applications are easy to understand, and they can be any type of application. This application does not make specific restrictions on the application type of the mobile application itself. This application focuses on the platform environment that it is adapted to, and then proceeds to the migration process between the adapted platform environments.

[0061] Step S102: Input the first configuration data into the pre-configured mobile application cross-platform conversion model, so that the mobile application cross-platform conversion model performs the corresponding mobile application cross-platform conversion process. The mobile application cross-platform conversion model is obtained by training the initial transform model with the configuration data of the labeled sample mobile applications. The mobile application cross-platform conversion model is used to convert the configuration data input to the model into configuration data adapted to the target platform environment.

[0062] For the purpose of migrating mobile applications between platform environments, this application pre-configures a cross-platform conversion model for mobile applications based on artificial intelligence (AI). In the actual use of the model, it can autonomously complete the migration of mobile applications between platform environments by virtue of its intelligent and powerful model processing capabilities.

[0063] The model used in this application is specifically the transform model. The core idea of ​​the transform model is to represent each element in the sequence as a weighted sum of all elements. The weights are obtained by calculating the similarity between elements. Compared with traditional recurrent neural networks and convolutional neural networks, the transform model has better parallel computing capabilities and long-distance dependency processing capabilities.

[0064] Specifically, through its self-attention mechanism, it can better capture long-distance dependencies in sequences, improve the model's expressive power, and perform parallel computation, greatly improving computational efficiency and shortening training time. It can also handle multiple tasks simultaneously, which helps improve the model's generalization ability. Furthermore, it has a good modular design, which can be easily combined with other model architectures (such as recurrent neural networks, convolutional neural networks, etc.) to achieve more complex and higher-performance models.

[0065] In practice, this application can adopt the existing, general transform model architecture, or it can make corresponding improvements and optimizations based on the existing general transform model architecture, which is also possible.

[0066] Training the transform model mainly includes the following:

[0067] Configure the configuration data of the sample mobile application, output the model according to the model design, and annotate the configuration data of the sample mobile application. The annotation of the cross-platform conversion result of the mobile application, that is, the configuration data of the sample mobile application migrated to the target platform environment, provides guidance during the model training process. After the configuration data of the sample mobile application is configured, the specific model training can begin.

[0068] In each round of model training, the configuration data of the sample mobile applications is input into the transform model during initialization / training, enabling the model to perform the corresponding cross-platform migration and transformation processing for mobile applications, achieving forward propagation. Then, based on the configuration data of the mobile applications output by the model and the previously labeled results, the loss function is calculated, and the model parameters are optimized based on the loss function calculation results, achieving backpropagation. When the model training requirements such as training time, number of training iterations, and prediction accuracy are met, the model training is complete, and a cross-platform mobile application transformation model ready for practical use is obtained.

[0069] Furthermore, the specific loss function used during model training, such as the model itself, can be an existing loss function, an improved loss function, or a self-developed, novel loss function. This can be adjusted according to the actual situation. Similarly, the same applies to the data preprocessing operations introduced for the input data of the model (which can also be involved after the model is put into actual use).

[0070] Meanwhile, the model training process may also involve other configuration work, such as the specific configuration work of learning rate scheduling and early stopping rules (early stopping mechanism). Considering that these are not the focus of this application, they will not be explained in detail, such as loss function and data preprocessing operations.

[0071] Therefore, it is easy to understand that the cross-platform migration method for mobile applications in this application may also include a prior model training phase:

[0072] Obtain the configuration data of the labeled sample mobile applications;

[0073] An initial transform model is trained using the configuration data of labeled sample mobile applications. After the model training is completed, a cross-platform transformation model for mobile applications is obtained.

[0074] Thus, in the actual use of the model, once the mobile application to be migrated is determined and the corresponding first configuration data is obtained, it can be input into the mobile application cross-platform conversion model to prompt the mobile application cross-platform conversion model to carry out the corresponding mobile application cross-platform conversion process, converting the first configuration data into second configuration data adapted to the target platform environment.

[0075] Step S103: Extract the second configuration data output by the cross-platform conversion model of the mobile application, which corresponds to the first configuration data.

[0076] It is understandable that after the mobile application cross-platform conversion model completes the cross-platform conversion process, the processing result can be output. In this case, the second configuration data corresponding to the first configuration data of the input model can be extracted.

[0077] At this point, the second configuration data can be stored, output (content display or forwarding), or used for further data applications (e.g., packaged into an application installation package or directly deployed on a device in the target platform environment). The specific data applications can be adjusted according to the pre-configured data application strategy and the real-time configured data application strategy.

[0078] from Figure 1 As can be seen from the embodiments shown, for the cross-platform migration target of mobile applications, after obtaining the first configuration data of the mobile application to be migrated to the target platform environment, this application inputs the first configuration data into a pre-configured mobile application cross-platform conversion model, so that the mobile application cross-platform conversion model performs the corresponding mobile application cross-platform conversion processing. Since the mobile application cross-platform conversion model is obtained by training the initial transform model with the configuration data of the labeled sample mobile applications, and is used to convert the configuration data input to the model into configuration data adapted to the target platform environment, the corresponding mobile application cross-platform conversion model is configured based on the intelligent AI model processing capability, so as to efficiently and accurately complete the migration or adaptation processing of the mobile application to the target platform environment automatically, thereby avoiding the human and material costs caused by relying on software development engineers as much as possible, and providing a good guarantee for the promotion and application of mobile applications in the new target platform environment.

[0079] Continue with the above Figure 1 The steps of the illustrated embodiments and their possible implementations in practical applications are described in detail.

[0080] As an exemplary embodiment, the first configuration data involved in step S101 and the second configuration data involved in step S103 both include the corresponding code and UI component library usage data.

[0081] The first configuration data also includes annotations or tags configured for key content, taking into account the language characteristics of the corresponding platform.

[0082] It is understandable that configuration data includes not only the code related to the mobile application, but also the usage data (information) of related UI component libraries, forming these two main categories.

[0083] UI stands for User Interface.

[0084] In addition to revealing that the configuration data involved in this application can involve two major categories of configuration data, namely code and UI component library, the embodiments here also reveal that the configuration data can also involve comments or tags specifically configured by software development engineers.

[0085] As is easy to understand, comments are a unique explanation used in the software development process to help users understand the meaning of the code. Deleting comments does not affect the operation of the application; that is, comments are a kind of non-substantive configuration data. Markers, on the other hand, can be substantive configuration data, such as specific code terms or fragments that correspond to the actual functions involved in the operation of the application. Alternatively, marks can also be non-substantive configuration data, or in other words, explanations other than comments that help users understand the code.

[0086] It is understandable that annotations and tags with personal / team / company style, such as prompt words, can guide the model to focus on key configuration data and understand the semantics of different languages ​​and UI libraries, thereby improving training and processing. This helps the model understand more accurately, resulting in better processing precision and making the model's processing more tailored to its own needs and more unique. In particular, when the tags involved in this embodiment can be of any type, they can also be custom-configured explanations with a unique form, which can further enhance this feature and make it more suitable for its own needs.

[0087] Thus, the trained cross-platform conversion model for mobile applications is highly adaptable to the configuration data of mobile applications for individuals, teams, and companies, and its processing performance is significantly better than that of general processing models configured according to common approaches.

[0088] In addition, to help the model understand the configuration data of the input mobile application and capture deeper data features, this application can also configure the model's unique input method from a general perspective, in addition to annotation and labeling, as in the above embodiments.

[0089] Specifically, as another exemplary embodiment, before step S102 inputs the first configuration data into the pre-configured mobile application cross-platform conversion model, the mobile application cross-platform migration method of this application may further include:

[0090] The preset splitting strategy is invoked to split the first configuration data and obtain multiple sub-configuration data.

[0091] Input multiple sub-configuration data into a pre-configured cross-platform conversion model for mobile applications.

[0092] It is easy to see that in this embodiment, the segmentation of configuration data can be understood as a data preprocessing operation. In layman's terms, it is to segment the configuration data, including code, into segments / fragments suitable for feeding the model. In this way, based on more granular sub-configuration data, the model can carry out more granular and in-depth processing.

[0093] The segmentation strategy is usually a pre-determined and fixed strategy rule. In some operations, the user can also select the target segmentation strategy from a variety of pre-determined segmentation strategies in real time for specific segmentation processing. Alternatively, the user can make fine adjustments based on the provided segmentation strategy, such as deleting / adding / adjusting some segmentation strategy content.

[0094] Furthermore, it can be understood that, corresponding to the settings in this embodiment, the configuration data of the sample mobile application can also be segmented in this way during the training process of the model.

[0095] Furthermore, as a more specific and exemplary embodiment, the segmentation strategy configured for the segmentation process in this application can be based on at least one segmentation element among preset annotations, tags, lengths, paragraphs, and functional modules for segmentation.

[0096] It is understood that the embodiments described here provide different specific units / elements for the granularity of the segmentation process in this application. In practical applications, the specific segmentation process is usually carried out using multiple and different types of segmentation units / elements.

[0097] In this embodiment, the annotations and markings can directly follow the application methods of the annotations and markings involved in the previous embodiments, while length, paragraphs, and functional modules are different elements that are easy to understand in the text.

[0098] Furthermore, regarding the second configuration data output by the model that corresponds to the first configuration data, in relation to the data application stage mentioned earlier, this application considers that in actual circumstances, there may be a need for individual users to make fine adjustments to address the alignment requirements of special situations. It also needs to provide a channel for individual users to initiate adjustments independently to ensure a high degree of control over the second configuration data. In this regard, this application can also configure a manual verification stage, or a result confirmation stage.

[0099] Correspondingly, after step S103 extracts the second configuration data output by the mobile application cross-platform conversion model that corresponds to the first configuration data, the mobile application cross-platform migration method of this application may further include:

[0100] The second configuration data is displayed to allow for verification and fine-tuning during the manual verification process;

[0101] The second configuration data, which has passed the manual verification process, will be compiled, packaged, and uploaded to the application store of the target platform environment.

[0102] It is understandable that the device can display the content of the second configuration data through a visual page shown to the user. At the same time, the visual interface also has corresponding user operation / command input functions, so that users can view and fine-tune the data.

[0103] Thus, the second configuration data, which undergoes a manual verification process (in practice, this usually involves user confirmation without any fine-tuning), can be compiled and packaged into the corresponding mobile application, which can then be downloaded and installed by different users in the app store of the target platform environment.

[0104] The device's visual interface is easy to understand and can be implemented through its own built-in display / touchscreen, a connected external display / touchscreen device, or other devices equipped with displays / touchscreens. These can all be adapted to meet actual needs.

[0105] The above is an introduction to the cross-platform migration method for mobile applications provided in this application. To facilitate better implementation of the cross-platform migration method for mobile applications provided in this application, this application also provides a cross-platform migration device for mobile applications from the perspective of functional modules.

[0106] See Figure 2 , Figure 2 This is a schematic diagram of a mobile application cross-platform migration device according to this application. In this application, the mobile application cross-platform migration device 200 may specifically include the following structure:

[0107] The acquisition unit 201 is used to acquire the first configuration data of the mobile application to be migrated to the target platform environment;

[0108] The conversion unit 202 is used to input the first configuration data into a pre-configured mobile application cross-platform conversion model, so that the mobile application cross-platform conversion model performs the corresponding mobile application cross-platform conversion process. The mobile application cross-platform conversion model is obtained by training an initial transform model with the configuration data of labeled sample mobile applications. The mobile application cross-platform conversion model is used to convert the configuration data input to the model into configuration data adapted to the target platform environment.

[0109] Extraction unit 203 is used to extract the second configuration data output by the cross-platform conversion model of mobile application, which corresponds to the first configuration data.

[0110] In one exemplary embodiment, both the first configuration data and the second configuration data include the corresponding code and UI component library usage data.

[0111] The first configuration data also includes annotations or tags configured for key content, taking into account the language characteristics of the corresponding platform.

[0112] In yet another exemplary embodiment, the mobile application cross-platform migration apparatus 200 further includes a segmentation unit 204, configured to:

[0113] The preset splitting strategy is invoked to split the first configuration data and obtain multiple sub-configuration data.

[0114] Input multiple sub-configuration data into a pre-configured cross-platform conversion model for mobile applications.

[0115] In yet another exemplary embodiment, the segmentation strategy is specifically based on at least one segmentation element among preset annotations, tags, lengths, paragraphs, and functional modules.

[0116] In yet another exemplary embodiment, the mobile application cross-platform migration device 200 further includes an application unit 205, configured to:

[0117] The second configuration data is displayed to allow for verification and fine-tuning during the manual verification process;

[0118] The second configuration data, which has passed the manual verification process, will be compiled, packaged, and uploaded to the application store of the target platform environment.

[0119] This application also provides a processing device from a hardware architecture perspective, see [link / reference]. Figure 3 , Figure 3 This diagram illustrates a structural schematic of the processing device of this application. Specifically, the processing device may include a processor 301, a memory 302, and an input / output device 303. The processor 301 executes the computer program stored in the memory 302 to implement, for example... Figure 1 The corresponding steps of the mobile application cross-platform migration method in the embodiment; or, when the processor 301 executes the computer program stored in the memory 302, it implements as follows: Figure 2 Corresponding to the functions of each unit in the embodiment, the memory 302 is used to store the functions executed by the processor 301 as described above. Figure 1 The computer program required for the cross-platform migration method of mobile applications in the corresponding embodiment.

[0120] For example, a computer program may be divided into one or more modules / units, one or more of which are stored in memory 302 and executed by processor 301 to complete this application. One or more modules / units may be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of the computer program in a computer device.

[0121] The processing device may include, but is not limited to, processor 301, memory 302, and input / output device 303. Those skilled in the art will understand that the illustrations are merely examples of the processing device and do not constitute a limitation on the processing device. It may include more or fewer components than illustrated, or combine certain components, or different components. For example, the processing device may also include network access devices, buses, etc., and processor 301, memory 302, input / output device 303, etc., are connected via a bus.

[0122] Processor 301 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor. The processor is the control center of the processing device, connecting various parts of the device through various interfaces and lines.

[0123] The memory 302 can be used to store computer programs and / or modules. The processor 301 implements various functions of the computer device by running or executing the computer programs and / or modules stored in the memory 302 and by calling data stored in the memory 302. The memory 302 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function, etc.; the data storage area may store data created according to the use of the processing device, etc. In addition, the memory may include high-speed random access memory, and may also include non-volatile memory, such as hard disk, RAM, plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0124] When processor 301 executes a computer program stored in memory 302, it can specifically perform the following functions:

[0125] Obtain the initial configuration data of the mobile application to be migrated to the target platform environment;

[0126] The first configuration data is input into the pre-configured mobile application cross-platform conversion model, which then performs the corresponding mobile application cross-platform conversion process. The mobile application cross-platform conversion model is obtained by training the initial transform model with the configuration data of the labeled sample mobile applications. The mobile application cross-platform conversion model is used to convert the configuration data input to the model into configuration data that is adapted to the target platform environment.

[0127] Extract the second configuration data, which corresponds to the first configuration data, from the output of the cross-platform conversion model of the mobile application.

[0128] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the mobile application cross-platform migration device, processing equipment, and its corresponding units described above can be found in, for example... Figure 1 The specific details of the cross-platform migration method for mobile applications in the corresponding embodiments will not be repeated here.

[0129] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0130] Therefore, this application provides a computer-readable storage medium storing a plurality of instructions that can be loaded by a processor to execute the present application. Figure 1 For details on the steps of the cross-platform migration method for mobile applications in the corresponding embodiments, please refer to the following: Figure 1 The description of the cross-platform migration method for mobile applications in the corresponding embodiments will not be repeated here.

[0131] The computer-readable storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0132] Because of the instructions stored in the computer-readable storage medium, the present application can be executed as described above. Figure 1 The steps of the mobile application cross-platform migration method in the corresponding embodiment can therefore achieve the results of this application. Figure 1The beneficial effects that the mobile application cross-platform migration method can achieve in the corresponding embodiments are detailed in the preceding description and will not be repeated here.

[0133] The foregoing has provided a detailed description of the mobile application cross-platform migration method, apparatus, processing device, and computer-readable storage medium provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A mobile terminal application cross-platform migration method, characterized by, The mobile terminal application cross-platform migration method comprises: obtaining first configuration data of a mobile terminal application to be migrated to a target platform environment; inputting the first configuration data into a pre-configured mobile terminal application cross-platform conversion model, so that the mobile terminal application cross-platform conversion model develops corresponding mobile terminal application cross-platform conversion processing, wherein the mobile terminal application cross-platform conversion model is obtained by training an initial transform model with labeled sample mobile terminal application configuration data, and the mobile terminal application cross-platform conversion model is used to convert input configuration data of the model into configuration data adapted to the target platform environment; extracting second configuration data corresponding to the first configuration data output by the mobile terminal application cross-platform conversion model.

2. The mobile application cross-platform migration method of claim 1, wherein, The first configuration data and the second configuration data both include corresponding code and UI component library usage data; The first configuration data is also labeled with annotations or markers configured for key content under conditions of corresponding platform language characteristics.

3. The mobile application cross-platform migration method of claim 1, wherein, Before inputting the first configuration data into the pre-configured mobile terminal application cross-platform conversion model, the mobile terminal application cross-platform migration method further comprises: calling a preset segmentation strategy to perform segmentation processing on the first configuration data and obtaining a plurality of sub-configuration data by segmentation; inputting the plurality of sub-configuration data into the pre-configured mobile terminal application cross-platform conversion model.

4. The mobile application cross-platform migration method of claim 3, wherein, The segmentation strategy is based on at least one of preset annotation, marker, length, paragraph, and function module segmentation elements for segmentation.

5. The mobile application cross-platform migration method of claim 1, wherein, After extracting the second configuration data corresponding to the first configuration data output by the mobile terminal application cross-platform conversion model, the mobile terminal application cross-platform migration method further comprises: displaying the content of the second configuration data for verification and fine-tuning in an artificial verification link; compiling and packaging the second configuration data that passes through the artificial verification link and uploading it to an application store of the target platform environment.

6. A mobile terminal application cross-platform migration device, characterized by comprising: The mobile terminal application cross-platform migration device comprises: an obtaining unit configured to obtain first configuration data of a mobile terminal application to be migrated to a target platform environment; a conversion unit configured to input the first configuration data into a pre-configured mobile terminal application cross-platform conversion model, so that the mobile terminal application cross-platform conversion model develops corresponding mobile terminal application cross-platform conversion processing, wherein the mobile terminal application cross-platform conversion model is obtained by training an initial transform model with labeled sample mobile terminal application configuration data, and the mobile terminal application cross-platform conversion model is used to convert input configuration data of the model into configuration data adapted to the target platform environment; an extracting unit configured to extract second configuration data corresponding to the first configuration data output by the mobile terminal application cross-platform conversion model.

7. The mobile application cross-platform migration device of claim 6, wherein, The first configuration data and the second configuration data both include corresponding code and UI component library usage data; The first configuration data is also labeled with annotations or markers configured for key content under conditions of corresponding platform language characteristics.

8. The mobile application cross-platform migration device of claim 6, wherein, The mobile terminal application cross-platform migration device further comprises a segmentation unit, configured to: invoke a preset segmentation strategy to segment the first configuration data, and obtain a plurality of sub-configuration data through segmentation; input the plurality of sub-configuration data into a preconfigured mobile terminal application cross-platform conversion model.

9. The mobile application cross-platform migration device of claim 8, wherein, The segmentation strategy is specifically based on at least one segmentation element in a preset annotation, a marker, a length, a paragraph and a function module.

10. The mobile application cross-platform migration device of claim 6, wherein, The mobile terminal application cross-platform migration device further comprises an application unit, configured to: display the content of the second configuration data to perform verification and fine-tuning in an artificial verification link; compile and package the second configuration data passing through the artificial verification link, and upload the second configuration data to an application store of the target platform environment.

Images