CN107678794B

CN107678794B - Application program starting interface merging method and mobile terminal

Info

Publication number: CN107678794B
Application number: CN201710863897.4A
Authority: CN
Inventors: 倪秉炬
Original assignee: Nubia Technology Co Ltd
Current assignee: Nubia Technology Co Ltd
Priority date: 2017-09-22
Filing date: 2017-09-22
Publication date: 2021-01-01
Anticipated expiration: 2037-09-22
Also published as: CN107678794A

Abstract

The invention discloses a mobile terminal, which comprises a memory, a processor and an application program starting interface merging program which is stored on the memory and can run on the processor, wherein the application program starting interface merging program realizes the following steps when being executed by the processor: intercepting a plurality of starting interfaces for sending requests to a server when an application program is started; merging the starting interfaces to obtain a merged interface and corresponding merged interface parameters; sending a request carrying merging interface parameters to a server and receiving merging parameter values returned by the server; and decomposing the merged parameter value into a plurality of interface parameter values and correspondingly distributing the merged parameter values to each starting interface to finish the starting of the application program. Compared with the prior art, the method and the device realize real-time dynamic automatic start interface merging without carrying out interface merging coding aiming at different application program versions, and the merged interface parameters comprise the version information of the application program, thereby avoiding data disorder in the start process.

Description

Application program starting interface merging method and mobile terminal

Technical Field

The invention relates to the technical field of mobile terminals, in particular to an application program starting interface merging method and a mobile terminal.

Background

When the application program is started, a plurality of interfaces are called to load resources. Specifically, the multiple interfaces respectively initiate HTTP requests to the server and then receive resources returned by the server. In order to increase the starting speed of the application program, in the prior art, the starting interfaces of the application program may be merged, that is, the merged starting interfaces together request resources from the server, but the merging information of this merging manner is often released and hard-coded in each application program version following the application program version.

However, this merging approach has the following disadvantages: (1) if multiple versions of the application exist, the server cannot determine which version of the merged data is to be returned to the requesting application, which may cause data confusion during the startup process. (2) When the application program is upgraded, the starting process of the application program is changed, and the used starting interfaces are different, so that developers need to encode and release the merged information again for each upgrade of the application program, the workload of application program development is increased, the interface merging cost is high, and the overall efficiency is low.

Therefore, it is desirable to provide an application start interface merging method and a mobile terminal to solve the above technical problems.

Disclosure of Invention

The invention mainly aims to provide an application program starting interface merging method and a mobile terminal, and aims to solve the problems that data disorder is easy to occur, the cost is high and the efficiency is low when multiple versions of an application program exist in the existing interface merging technology.

First, to achieve the above object, the present invention provides a mobile terminal, where the mobile terminal includes a memory, a processor, and an application start interface merge program stored in the memory and operable on the processor, and when executed by the processor, the application start interface merge program implements the following steps:

when an application program is started, a plurality of starting interfaces for sending requests to a server are intercepted;

merging the starting interfaces to obtain a merged interface and corresponding merged interface parameters, wherein the merged interface parameters comprise interface parameters of the starting interfaces and version information of the application program;

sending a request carrying the merging interface parameters to the server and receiving merging parameter values returned by the server, wherein the merging parameter values comprise interface parameter values required by each starting interface corresponding to the version information;

and decomposing the merged parameter value into a plurality of interface parameter values corresponding to the starting interfaces and correspondingly distributing the interface parameter values to the starting interfaces so that the starting interfaces complete the starting of the application program.

Optionally, when the application program is started, before the step of intercepting a plurality of start interfaces that send requests to the server, the processor is further configured to execute the application program start interface merging program, so as to implement the following steps:

when an application program is started for the first time, scanning and recording a plurality of starting interfaces called in the starting stage of the application program;

generating a preset interface merging list according to the recorded starting interfaces;

the step of intercepting the plurality of start-up interfaces that send requests to the server specifically includes:

and intercepting a starting interface which sends a request to the server and is positioned in the preset interface merging list.

Optionally, the processor is further configured to execute the application start interface merging program to implement the following steps:

searching a plurality of recorded starting interfaces which can be combined;

and generating the preset interface merging list by using a plurality of starting interfaces which can be merged.

Optionally, after the step of intercepting the plurality of start interfaces that send requests to the server, the processor is further configured to execute the application start interface merging program to implement the following steps:

judging whether a plurality of starting interfaces have a starting interface with a dependency relationship;

and if the starting interface with the dependency relationship exists, performing dependency relationship marking on the starting interface with the dependency relationship in the merged interface parameter to assist the server to search the merged parameter value.

Meanwhile, the invention also provides an application program starting interface merging method which is applied to the mobile terminal and comprises the following steps:

Optionally, when the application program is started, the step of intercepting a plurality of start interfaces that send requests to the server further includes:

Optionally, the step of generating a preset interface merge list according to the recorded multiple start interfaces specifically includes:

searching a plurality of recorded starting interfaces which can be combined;

Optionally, the step of intercepting a plurality of start interfaces that send requests to the server further includes:

Optionally, the step of sending the request carrying the merged interface parameter to the server specifically includes:

and sending a request carrying the merged interface parameters to a unified call address of the server so that the server searches corresponding interface parameter values according to each interface parameter in the merged interface parameters and merges the interface parameter values to obtain the merged parameter values.

In addition, to achieve the above object, the present invention further provides a computer readable storage medium, having an application start interface merging program stored thereon, where the application start interface merging program, when executed by a processor, implements the steps of the application start interface merging method as described above.

Compared with the prior art, the application program starting interface merging method, the mobile terminal and the computer readable storage medium provided by the invention can intercept a plurality of starting interfaces sending requests to a server when an application program is started, then merge the starting interfaces to obtain a merging interface and corresponding merging interface parameters, then send a request carrying the merging interface parameters to the server and receive merging parameter values returned by the server, finally decompose the merging parameter values into a plurality of interface parameter values corresponding to the starting interfaces and correspondingly distribute the interface parameter values to the starting interfaces so that the starting interfaces finish the starting of the application program, thereby realizing the real-time and dynamic automatic merging of the starting interfaces, avoiding interface merging coding aiming at different application program versions and reducing the workload of application program developers, the interface merging cost is reduced, and the updating efficiency of the application program is improved; meanwhile, the merging interface parameters comprise version information of the application program, so that the server can know which version of merging data needs to be returned, and data disorder in the starting process is avoided.

Drawings

Fig. 1 is a schematic diagram of a hardware structure of an optional mobile terminal for implementing various embodiments of the present invention;

fig. 2 is a diagram of a communication network system architecture according to an embodiment of the present invention;

FIG. 3 is a functional block diagram of a first embodiment of an API merge process according to the present invention;

FIG. 4 is a functional block diagram of a second embodiment of an API merge process according to the present invention;

FIG. 5 is a flowchart illustrating a first embodiment of a method for merging application program launch interfaces according to the present invention;

FIG. 6 is a flowchart illustrating an implementation of a second embodiment of the application start interface merging method according to the present invention;

fig. 7 is a schematic diagram of an interface merging process when the application a is started.

Reference numerals:

the implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.

Detailed Description

It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in itself. Thus, "module", "component" or "unit" may be used mixedly.

The terminal may be implemented in various forms. For example, the terminal described in the present invention may include a mobile terminal such as a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a Personal Digital Assistant (PDA), a Portable Media Player (PMP), a navigation device, a wearable device, a smart band, a pedometer, and the like, and a fixed terminal such as a Digital TV, a desktop computer, and the like.

The following description will be given by way of example of a mobile terminal, and it will be understood by those skilled in the art that the construction according to the embodiment of the present invention can be applied to a fixed type terminal, in addition to elements particularly used for mobile purposes.

Referring to fig. 1, which is a schematic diagram of a hardware structure of a mobile terminal for implementing various embodiments of the present invention, the mobile terminal 100 may include: RF (Radio Frequency) unit 101, WiFi module 102, audio output unit 103, a/V (audio/video) input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, processor 110, and power supply 111. Those skilled in the art will appreciate that the mobile terminal architecture shown in fig. 1 is not intended to be limiting of mobile terminals, which may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.

The following describes each component of the mobile terminal in detail with reference to fig. 1:

the radio frequency unit 101 may be configured to receive and transmit signals during information transmission and reception or during a call, and specifically, receive downlink information of a base station and then process the downlink information to the processor 110; in addition, the uplink data is transmitted to the base station. Typically, radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 101 can also communicate with a network and other devices through wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to GSM (Global System for Mobile communications), GPRS (General Packet Radio Service), CDMA2000(Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division duplex long term Evolution), and TDD-LTE (Time Division duplex long term Evolution).

WiFi belongs to short-distance wireless transmission technology, and the mobile terminal can help a user to receive and send e-mails, browse webpages, access streaming media and the like through the WiFi module 102, and provides wireless broadband internet access for the user. Although fig. 1 shows the WiFi module 102, it is understood that it does not belong to the essential constitution of the mobile terminal, and may be omitted entirely as needed within the scope not changing the essence of the invention.

The audio output unit 103 may convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into an audio signal and output as sound when the mobile terminal 100 is in a call signal reception mode, a call mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Also, the audio output unit 103 may also provide audio output related to a specific function performed by the mobile terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 103 may include a speaker, a buzzer, and the like.

The a/V input unit 104 is used to receive audio or video signals. The a/V input Unit 104 may include a Graphics Processing Unit (GPU) 1041 and a microphone 1042, the Graphics processor 1041 Processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 106. The image frames processed by the graphic processor 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 may receive sounds (audio data) via the microphone 1042 in a phone call mode, a recording mode, a voice recognition mode, or the like, and may be capable of processing such sounds into audio data. The processed audio (voice) data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 101 in case of a phone call mode. The microphone 1042 may implement various types of noise cancellation (or suppression) algorithms to cancel (or suppress) noise or interference generated in the course of receiving and transmitting audio signals.

The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that can adjust the brightness of the display panel 1061 according to the brightness of ambient light, and a proximity sensor that can turn off the display panel 1061 and/or a backlight when the mobile terminal 100 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the posture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone, further description is omitted here.

The display unit 106 is used to display information input by a user or information provided to the user. The Display unit 106 may include a Display panel 1061, and the Display panel 1061 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.

The user input unit 107 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the mobile terminal. Specifically, the user input unit 107 may include a touch panel 1071 and other input devices 1072. The touch panel 1071, also referred to as a touch screen, may collect a touch operation performed by a user on or near the touch panel 1071 (e.g., an operation performed by the user on or near the touch panel 1071 using a finger, a stylus, or any other suitable object or accessory), and drive a corresponding connection device according to a predetermined program. The touch panel 1071 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 110, and can receive and execute commands sent by the processor 110. In addition, the touch panel 1071 may be implemented in various types, such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may include other input devices 1072. In particular, other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like, and are not limited to these specific examples.

Further, the touch panel 1071 may cover the display panel 1061, and when the touch panel 1071 detects a touch operation thereon or nearby, the touch panel 1071 transmits the touch operation to the processor 110 to determine the type of the touch event, and then the processor 110 provides a corresponding visual output on the display panel 1061 according to the type of the touch event. Although the touch panel 1071 and the display panel 1061 are shown in fig. 1 as two separate components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 and the display panel 1061 may be integrated to implement the input and output functions of the mobile terminal, and is not limited herein.

The interface unit 108 serves as an interface through which at least one external device is connected to the mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from external devices and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and external devices.

The memory 109 may be used to store software programs as well as various data. The memory 109 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 109 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The processor 110 is a control center of the mobile terminal, connects various parts of the entire mobile terminal using various interfaces and lines, and performs various functions of the mobile terminal and processes data by operating or executing software programs and/or modules stored in the memory 109 and calling data stored in the memory 109, thereby performing overall monitoring of the mobile terminal. Processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 110.

The mobile terminal 100 may further include a power supply 111 (e.g., a battery) for supplying power to various components, and preferably, the power supply 111 may be logically connected to the processor 110 via a power management system, so as to manage charging, discharging, and power consumption management functions via the power management system.

Although not shown in fig. 1, the mobile terminal 100 may further include a bluetooth module or the like, which is not described in detail herein.

In order to facilitate understanding of the embodiments of the present invention, a communication network system on which the mobile terminal of the present invention is based is described below.

Referring to fig. 2, fig. 2 is an architecture diagram of a communication Network system according to an embodiment of the present invention, where the communication Network system is an LTE system of a universal mobile telecommunications technology, and the LTE system includes a UE (User Equipment) 201, an E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, an EPC (Evolved Packet Core) 203, and an IP service 204 of an operator, which are in communication connection in sequence.

Specifically, the UE201 may be the terminal 100 described above, and is not described herein again.

The E-UTRAN202 includes eNodeB2021 and other eNodeBs 2022, among others. Among them, the eNodeB2021 may be connected with other eNodeB2022 through backhaul (e.g., X2 interface), the eNodeB2021 is connected to the EPC203, and the eNodeB2021 may provide the UE201 access to the EPC 203.

The EPC203 may include an MME (Mobility Management Entity) 2031, an HSS (Home Subscriber Server) 2032, other MMEs 2033, an SGW (Serving gateway) 2034, a PGW (PDN gateway) 2035, and a PCRF (Policy and Charging Rules Function) 2036, and the like. The MME2031 is a control node that handles signaling between the UE201 and the EPC203, and provides bearer and connection management. HSS2032 is used to provide registers to manage functions such as home location register (not shown) and holds subscriber specific information about service characteristics, data rates, etc. All user data may be sent through SGW2034, PGW2035 may provide IP address assignment for UE201 and other functions, and PCRF2036 is a policy and charging control policy decision point for traffic data flow and IP bearer resources, which selects and provides available policy and charging control decisions for a policy and charging enforcement function (not shown).

The IP services 204 may include the internet, intranets, IMS (IP Multimedia Subsystem), or other IP services, among others.

Although the LTE system is described as an example, it should be understood by those skilled in the art that the present invention is not limited to the LTE system, but may also be applied to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, and future new network systems.

Based on the hardware structure of the mobile terminal 100 and the communication network system, various embodiments of the method of the present invention are provided.

First, the present invention provides a mobile terminal, which includes a memory, a processor, and an application start interface merge program 400 stored in the memory and operable on the processor.

Fig. 3 is a functional block diagram of an application start interface merge program 400 according to a first embodiment of the present invention. In this embodiment, the application launching interface merging procedure 400 may be divided into one or more modules, and the one or more modules are stored in the memory 109 of the mobile terminal 100 and executed by one or more processors (in this embodiment, the controller 110) to complete the present invention. For example, in fig. 3, the application launch interface merge program 400 can be partitioned into an intercept module 401, a merge module 402, a request module 403, and a distribution module 404. The module referred to in the present invention refers to a series of instruction segments of the fetcher program that can perform specific functions, and is more suitable than the fetcher program for describing the execution process of the software in the mobile terminal 100. The detailed description of the functions of the

functional modules

401 and 404 will be described below. Wherein:

the intercepting module 401 is configured to intercept a plurality of start interfaces that send requests to a server when an application program is started. The application program calls a plurality of starting interfaces in a starting stage, the starting interfaces initiate requests to the server, and then the starting process of the application program is completed after each starting interface receives interface parameter values returned by the server. In the prior art, the interface merging method of each version of application program is hard coded in the application program, but the invention dynamically merges the interfaces in real time. Specifically, when the application program is started, the method and the device can intercept a plurality of starting interfaces which send requests to the server so as to prevent each starting interface from sending the requests to the server. Such as: when the starting interface 1, the starting interface 2 and the starting interface 3 need to be called in the starting stage of the application program A, the starting interface merging method of the application program can intercept the starting interfaces after scanning the starting interfaces, and enable the starting interfaces to enter a waiting state to wait for the returned interface parameter values. In this embodiment, the request sent by the start interface to the server is specifically an http request.

The merging module 402 is configured to merge the plurality of boot interfaces to obtain a merged interface and corresponding merged interface parameters, where the merged interface parameters include interface parameters of the plurality of boot interfaces and version information of the application program. Specifically, after intercepting a plurality of start-up interfaces, the plurality of start-up interfaces are merged into one interface, the merged interface is recorded as a merged interface, and when merging the start-up interfaces, the interface parameters of each start-up interface are merged to obtain corresponding merged interface parameters. The format of the merged interface parameter is as follows: { starting interface 1: parameter 1, start interface 2: parameter 2, start interface 3: parameter 3, … … starts interface n: and n represents that n starting interfaces are required to be called when the application program is started, and the version information of the application program is contained in each interface parameter in the merged interface parameters, such as the interface parameters of parameter 1, parameter 2 and the like, and the version information of the current application program can be obtained by analyzing and identifying the interface parameters.

The request module 403 is configured to send a request carrying the merged interface parameters to the server and receive merged parameter values returned by the server, where the merged parameter values include interface parameter values required by each of the start interfaces corresponding to the version information. Specifically, after receiving the request carrying the merged interface parameter, the server searches for a corresponding interface parameter value according to the merged interface parameter, and merges the found interface parameter values according to the format of the merged interface parameter to obtain a merged parameter value and returns the merged parameter value. Such as: the format of the merged parameter values is as follows: { starting interface 1: parameter value 1, start interface 2: parameter value 2, start interface 3: parameter value 3, … … starts interface n: parameter n, where parameter n represents the interface parameter value required to start interface n.

The distributing module 404 is configured to decompose the merged parameter value into a plurality of interface parameter values corresponding to the starting interfaces and correspondingly distribute the merged parameter values to each of the starting interfaces so that each of the starting interfaces completes the starting of the application program. When the mobile terminal receives the merged parameter value returned by the server, the merged parameter value is decomposed to obtain the interface parameter value required by each starting interface, and the interface parameter value is correspondingly distributed to each waiting starting interface. If the merged parameter value returned by the server is { starting interface 1: parameter value 1, start interface 2: parameter value 2, start interface 3: and 3, decomposing the merged parameter value by the mobile terminal to obtain a parameter value 1, a parameter value 2 and a parameter value 3, then distributing the parameter value 1 to the starting interface 1, distributing the parameter value 2 to the starting interface 2, and distributing the parameter value 3 to the starting interface 3, wherein each starting interface can finish the starting of the application program after receiving the return value.

Referring to fig. 7, fig. 7 is a schematic diagram of an interface merging process when an application program a is started, as shown in fig. 7, when the application program a is started, a start interface 1, a start interface 2, and a start interface 3 need to be called, and then in the starting process, the start interface 1, the start interface 2, and the start interface 3 are merged to obtain a merged interface X and merged interface parameters, a server has a uniform calling address, and if the uniform calling address is http:// app. nubia.com/api _ united, then the present invention uses a program start interface merging method to send a request carrying the merged interface parameters to the uniform calling address of the server, the server searches for corresponding interface parameter values according to the interface parameters in the merged interface parameters and merges the interface parameter values to obtain merged parameters, and then returns the merged parameters to the application program a, and then the application program a decomposes the merged parameters into

interface parameter values

1, 2, and 3, And the

interface parameter values

2 and 3 are respectively distributed to the corresponding starting interface 1, starting interface 2 and starting interface 3. The merging interface parameter is in a json character string format.

Through the

module

401 and 404, when the application program is started, the application program start interface merging program of the present invention intercepts multiple start interfaces that send requests to the server, then merges the multiple start interfaces to obtain a merged interface and corresponding merged interface parameters, then sends a request carrying the merged interface parameters to the server and receives merged parameter values returned by the server, and finally decomposes the merged parameter values into multiple interface parameter values corresponding to the start interfaces and correspondingly distributes the interface parameter values to the start interfaces so that the start interfaces complete the start of the application program, thereby realizing the real-time and dynamic automatic start interface merging without performing interface merging coding for different application program versions, reducing the workload of application program developers and reducing the interface merging cost, the updating efficiency of the application program is improved; meanwhile, the merging interface parameters comprise version information of the application program, so that the server can know which version of merging data needs to be returned, and data disorder in the starting process is avoided.

Further, based on the above-mentioned first embodiment of the api merging procedure 400 of the present invention, a second embodiment of the api merging procedure 400 of the present invention is proposed. Referring to fig. 4, fig. 4 is a functional block diagram illustrating an application start interface merging procedure 400 according to a second embodiment of the present invention, wherein compared with the first embodiment, the application start interface merging procedure 400 further includes a list generating module 405, a dependency determining module 406, and a marking module 407. In this embodiment, each functional module is described as follows:

the list generating module 405 is configured to scan and record a plurality of start interfaces called in a start stage of an application program when the application program is started for the first time, and generate a preset interface merge list according to the recorded plurality of start interfaces. In this embodiment, before the step of automatically starting the interface merging, a preset interface merging list needs to be generated for the current application program. Specifically, the generation process of the preset interface merge list is as follows: when the application program is started for the first time, a plurality of starting interfaces used in the starting stage of the application program are scanned and recorded, and a preset interface merging list is generated according to the starting interfaces. The preset interface merge list may include all the start-up interfaces used in the start-up phase, or only include some start-up interfaces used in the start-up phase. In this embodiment, the step of generating the preset interface merge list according to the recorded multiple start interfaces specifically includes: (1) searching a plurality of recorded starting interfaces which can be combined; (2) and generating the preset interface merging list by using a plurality of starting interfaces which can be merged. Therefore, if all the boot interfaces can be merged, the preset interface merging list includes all the boot interfaces to be used in the boot process, and otherwise, if only part of the boot interfaces can be merged, the preset interface merging list includes only part of the boot interfaces to be used in the boot process. In addition, it should be noted that, because the start interfaces used in the start stages of the application programs of different versions are different, the merging interface processes may also be different, and therefore different application program versions should correspond to different preset interface merging lists, for this reason, generating the preset interface merging list when the application program is started for the first time in this embodiment is specifically automatically generating the preset interface merging list when the application program of the current version is started for the first time; and then, after the application program is upgraded or updated, generating a preset interface merging list in the same way when the application program is started for the first time.

The dependency determining module 406 is configured to determine, after the merging module 402, whether a plurality of boot interfaces have a dependency relationship, and if the determination result is yes, execute the marking module 407, otherwise execute the request module 403.

The marking module 407 is configured to mark, in the merged interface parameter, a dependency relationship of the start interface having a dependency relationship to assist the server in finding the merged parameter value. Specifically, there may be a dependency relationship between multiple start interfaces, for example: it is possible that a certain interface parameter of the starting interface 2 needs a certain return value (i.e. a returned interface parameter value) to the starting interface 1, and at this time, in order to enable the server to obtain the interface parameter of the starting interface 2, the return value of the starting interface needs to be used, and for this reason, the dependency relationship of the starting interface with the dependency relationship is marked in the merged interface parameter in this embodiment. For example, for the application B, the combinable start interfaces include a start interface 1, a start interface 2, a start interface 3, and a start interface 4, where the interface parameters of the start interface 2 need to use the interface parameters of the start interface 1, and the combinable interface parameters at this time are { start interface 1: parameter 1, start interface 2: { parameter 2-1, interface 1 returns value 1}, start interface 3: parameter 3, start interface 4: parameter 4, where { parameter 2-1, interface 1 returns a value of 1} indicates that interface parameter 2 of initiating interface 2 is the return value of interface 1, i.e. the server finds the interface parameter value requested by initiating interface 1. By marking the dependency relationship among the starting interfaces, the server can find the interface parameter values of the starting interfaces with the dependency relationship. In addition, when judging whether each interface has a dependency relationship, intelligent identification can be carried out by analyzing the code structure and the calling sequence of each starting interface.

Through the

module

401 and 407, when the application program is started for the first time, the application program start interface merging program provided by the invention firstly records all start interfaces used in the start stage of the application program and generates the preset interface merging list according to the start interfaces, and then automatically merges the start interfaces in the preset interface merging list when the application program is started again, and because the application program generates the preset interface merging list when the application program is started for the first time, the corresponding preset interface merging list can be automatically generated and the interfaces are merged for the same application program of different versions, program developers do not need to merge and encode for different versions, and the workload of developers is greatly reduced; in addition, the invention can also judge whether each starting interface has the dependency relationship and carry out marking, thereby enabling the server to search the corresponding interface parameter value for the starting interface with the dependency relationship without the problem that the starting interface cannot be searched.

In addition, the present invention provides an application start interface merging method, which is applied to the mobile terminal shown in fig. 1 to 2, where the mobile terminal includes a memory and a processor.

Fig. 5 is a flowchart illustrating an implementation of a first embodiment of the method for merging api launched by an application program according to the present invention. In this embodiment, the execution order of the steps in the flowchart shown in fig. 5 may be changed and some steps may be omitted according to different requirements. The application program starting interface merging method comprises the following steps:

step S501, when the application program is started, a plurality of starting interfaces for sending requests to the server are intercepted.

The application program calls a plurality of starting interfaces in a starting stage, the starting interfaces initiate requests to the server, and then the starting process of the application program is completed after each starting interface receives interface parameter values returned by the server. In the prior art, the interface merging method of each version of application program is hard coded in the application program, but the invention dynamically merges the interfaces in real time. Specifically, when the application program is started, the method and the device can intercept a plurality of starting interfaces which send requests to the server so as to prevent each starting interface from sending the requests to the server. Such as: when the starting interface 1, the starting interface 2 and the starting interface 3 need to be called in the starting stage of the application program A, the starting interface merging method of the application program can intercept the starting interfaces after scanning the starting interfaces, and enable the starting interfaces to enter a waiting state to wait for the returned interface parameter values. In this embodiment, the request sent by the start interface to the server is specifically an http request.

Step S502, merging the plurality of start interfaces to obtain a merged interface and corresponding merged interface parameters, where the merged interface parameters include interface parameters of the plurality of start interfaces and version information of the application program.

Specifically, after intercepting a plurality of start-up interfaces, the plurality of start-up interfaces are merged into one interface, the merged interface is recorded as a merged interface, and when merging the start-up interfaces, the interface parameters of each start-up interface are merged to obtain corresponding merged interface parameters. The format of the merged interface parameter is as follows: { starting interface 1: parameter 1, start interface 2: parameter 2, start interface 3: parameter 3, … … starts interface n: and n represents that n starting interfaces are required to be called when the application program is started, and the version information of the application program is contained in each interface parameter in the merged interface parameters, such as the interface parameters of parameter 1, parameter 2 and the like, and the version information of the current application program can be obtained by analyzing and identifying the interface parameters.

Step S503, sending a request carrying the merged interface parameters to the server, and receiving merged parameter values returned by the server, where the merged parameter values include interface parameter values required by each of the start interfaces corresponding to the version information.

Specifically, after receiving the request carrying the merged interface parameter, the server searches for a corresponding interface parameter value according to the merged interface parameter, and merges the found interface parameter values according to the format of the merged interface parameter to obtain a merged parameter value and returns the merged parameter value. Such as: the format of the merged parameter values is as follows: { starting interface 1: parameter value 1, start interface 2: parameter value 2, start interface 3: parameter value 3, … … starts interface n: parameter n, where parameter n represents the interface parameter value required to start interface n.

Step S504, decomposing the merged parameter value into a plurality of interface parameter values corresponding to the starting interfaces and distributing the interface parameter values to the starting interfaces correspondingly, so that the starting interfaces complete the starting of the application program.

When the mobile terminal receives the merged parameter value returned by the server, the merged parameter value is decomposed to obtain the interface parameter value required by each starting interface, and the interface parameter value is correspondingly distributed to each waiting starting interface. If the merged parameter value returned by the server is { starting interface 1: parameter value 1, start interface 2: parameter value 2, start interface 3: and 3, decomposing the merged parameter value by the mobile terminal to obtain a parameter value 1, a parameter value 2 and a parameter value 3, then distributing the parameter value 1 to the starting interface 1, distributing the parameter value 2 to the starting interface 2, and distributing the parameter value 3 to the starting interface 3, wherein each starting interface can finish the starting of the application program after receiving the return value.

interface parameter values

1, 2, and 3, And the

interface parameter values

Through the steps S501-S504, the application program starting interface merging method of the invention intercepts a plurality of starting interfaces sending requests to a server when an application program is started, then merges the starting interfaces to obtain a merging interface and corresponding merging interface parameters, then sends requests carrying the merging interface parameters to the server and receives merging parameter values returned by the server, finally decomposes the merging parameter values into a plurality of interface parameter values corresponding to the starting interfaces and correspondingly distributes the interface parameter values to the starting interfaces so as to enable the starting interfaces to finish the starting of the application program, thereby realizing the real-time dynamic automatic starting interface merging without carrying out interface merging coding aiming at different application program versions, reducing the workload of application program developers and the interface merging cost, the updating efficiency of the application program is improved; meanwhile, the merging interface parameters comprise version information of the application program, so that the server can know which version of merging data needs to be returned, and data disorder in the starting process is avoided.

Further, based on the first embodiment, a second embodiment of the method for merging application program start interfaces is provided. Fig. 6 is a flowchart illustrating an implementation of a second embodiment of the application start interface merging method according to the present invention. In this embodiment, the execution order of the steps in the flowchart shown in fig. 6 may be changed and some steps may be omitted according to different requirements. The application program starting interface merging method comprises the following steps:

step S601, when the application program is started for the first time, scanning and recording a plurality of starting interfaces called in the starting stage of the application program.

Step S602, generating a preset interface merge list according to the recorded multiple starting interfaces.

In this embodiment, before the step of automatically starting the interface merging, a preset interface merging list needs to be generated for the current application program. Specifically, the generation process of the preset interface merge list is as follows: when the application program is started for the first time, a plurality of starting interfaces used in the starting stage of the application program are scanned and recorded, and a preset interface merging list is generated according to the starting interfaces. The preset interface merge list may include all the start-up interfaces used in the start-up phase, or only include some start-up interfaces used in the start-up phase. In this embodiment, the step of generating the preset interface merge list according to the recorded multiple start interfaces specifically includes: (1) searching a plurality of recorded starting interfaces which can be combined; (2) and generating the preset interface merging list by using a plurality of starting interfaces which can be merged. Therefore, if all the boot interfaces can be merged, the preset interface merging list includes all the boot interfaces to be used in the boot process, and otherwise, if only part of the boot interfaces can be merged, the preset interface merging list includes only part of the boot interfaces to be used in the boot process. In addition, it should be noted that, because the start interfaces used in the start stages of the application programs of different versions are different, the merging interface processes may also be different, and therefore different application program versions should correspond to different preset interface merging lists, for this reason, generating the preset interface merging list when the application program is started for the first time in this embodiment is specifically automatically generating the preset interface merging list when the application program of the current version is started for the first time; and then, after the application program is upgraded or updated, generating a preset interface merging list in the same way when the application program is started for the first time.

Step S603, when the application program is started again, scanning the start interface that sends the request to the server and intercepting the start interface that sends the request to the server and is located in the preset interface merge list.

In this embodiment, the application program is restarted in a starting process after the preset interface merge list has been generated. At this time, the method for merging the application program starting interfaces intercepts the starting interfaces in the preset interface merging list, and does not intercept certain starting interfaces which cannot be merged.

Step S604, merging the plurality of start interfaces to obtain a merged interface and corresponding merged interface parameters, where the merged interface parameters include interface parameters of the plurality of start interfaces and version information of the application program.

Step S605, determining whether a plurality of the boot interfaces have a dependency relationship, if so, executing step S606, otherwise, executing step S607.

Step S606, perform dependency marking on the start interface with dependency in the merged interface parameter to assist the server to find the merged parameter value, and then execute step S607.

Because there may be dependencies between multiple boot interfaces, for example: it is possible that a certain interface parameter of the starting interface 2 needs a certain return value (i.e. a returned interface parameter value) to the starting interface 1, and at this time, in order to enable the server to obtain the interface parameter of the starting interface 2, the return value of the starting interface needs to be used, and for this reason, the dependency relationship of the starting interface with the dependency relationship is marked in the merged interface parameter in this embodiment. For example, for the application B, the combinable start interfaces include a start interface 1, a start interface 2, a start interface 3, and a start interface 4, where the interface parameters of the start interface 2 need to use the interface parameters of the start interface 1, and the combinable interface parameters at this time are { start interface 1: parameter 1, start interface 2: { parameter 2-1, interface 1 returns value 1}, start interface 3: parameter 3, start interface 4: parameter 4, where { parameter 2-1, interface 1 returns a value of 1} indicates that interface parameter 2 of initiating interface 2 is the return value of interface 1, i.e. the server finds the interface parameter value requested by initiating interface 1. By marking the dependency relationship among the starting interfaces, the server can find the interface parameter values of the starting interfaces with the dependency relationship. In addition, when judging whether each interface has a dependency relationship, intelligent identification can be carried out by analyzing the code structure and the calling sequence of each starting interface.

Step S607, sending a request carrying the merged interface parameter to the unified call address of the server, so that the server searches for a corresponding interface parameter value according to each interface parameter in the merged interface parameter and merges the interface parameter values to obtain the merged parameter value.

Step S608, receiving the merged parameter value returned by the server.

Step S609, decomposing the merged parameter value into a plurality of interface parameter values corresponding to the starting interfaces and distributing the interface parameter values to the starting interfaces correspondingly, so that the starting interfaces complete the starting of the application program.

Through the steps S601 to S609, the application program starting interface merging method firstly records all starting interfaces used in the application program starting stage when the application program is started for the first time and generates the preset interface merging list according to the starting interfaces, then automatically merges the starting interfaces in the preset interface merging list when the application program is started again, and because the preset interface merging list is generated when the application program is started for the first time, the corresponding preset interface merging list can be automatically generated and the interfaces are merged aiming at the same application program with different versions, program developers do not need to merge codes aiming at different versions, and the workload of the developers is greatly reduced; in addition, the invention can also judge whether each starting interface has the dependency relationship and carry out marking, thereby enabling the server to search the corresponding interface parameter value for the starting interface with the dependency relationship without the problem that the starting interface cannot be searched.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.

The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims

1. A mobile terminal comprising a memory, a processor, and an application launching interface consolidator stored on the memory and executable on the processor, the application launching interface consolidator when executed by the processor implementing the steps of:

generating a preset interface merging list according to the recorded starting interfaces; intercepting a starting interface which sends a request to a server and is positioned in the preset interface merging list;

2. The mobile terminal of claim 1, wherein the processor is further configured to execute the application-initiated interface merge process to implement the steps of:

searching a plurality of recorded starting interfaces which can be combined;

3. The mobile terminal of claim 1, wherein after the step of intercepting a plurality of start-up interfaces that send requests to a server, the processor is further configured to execute the application start-up interface merging procedure to implement the steps of:

4. An application program starting interface merging method is applied to a mobile terminal and is characterized by comprising the following steps:

5. The method for merging application program startup interfaces according to claim 4, wherein the step of generating the preset interface merging list according to the recorded multiple startup interfaces specifically includes:

searching a plurality of recorded starting interfaces which can be combined;

6. The application launching interface consolidation method of claim 4, wherein the step of intercepting a plurality of launching interfaces that send requests to the server is followed by further comprising:

7. The method for merging application program startup interfaces according to claim 4, wherein the step of sending the request carrying the merged interface parameters to the server specifically includes:

8. A computer-readable storage medium, having an application launching interface merging program stored thereon, which when executed by a processor implements the steps of the application launching interface merging method as recited in any one of claims 4 to 7.