CN106909395B

CN106909395B - Interface calling method and terminal

Info

Publication number: CN106909395B
Application number: CN201710121489.1A
Authority: CN
Inventors: 朱海军; 徐凯鹏
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2017-03-02
Filing date: 2017-03-02
Publication date: 2022-05-17
Anticipated expiration: 2037-03-02
Also published as: CN106909395A

Abstract

The invention discloses an interface calling method and a terminal, wherein the method comprises the following steps: receiving a first operation acting on a first interface; responding to the first operation, and transmitting a calling command to the unified caller in a character string mode; extracting interface information associated with the calling command from the unified caller, and determining to perform interface calling on a second interface according to the interface information; and triggering the call of the second interface, and starting the second interface.

Description

Interface calling method and terminal

Technical Field

The present invention relates to a calling technology, and in particular, to an interface calling method and a terminal.

Background

The information interaction mode is realized by more and more depending on the application, the calling of the interfaces between the application and the calling between different interfaces in the application are frequently used. For interface calling, the prior art is adopted, and an interface in an application directly transfers the class name of a target interface as a parameter to open the target interface so as to realize interface calling.

The problems existing in the prior art are as follows: 1) the interface is directly related to the class of the target interface, so that the codes are strongly coupled; 2) the codes for opening the target interface are scattered in each module, and unified and centralized management is not performed; 3) the interface is directly associated with the class of the target interface, and the target interface is difficult to modify subsequently.

In the related art, there is no effective solution to the above-mentioned problems.

Disclosure of Invention

In view of this, embodiments of the present invention provide an interface calling method and a terminal, which at least solve the problems in the prior art.

The technical scheme of the embodiment of the invention is realized as follows:

the interface calling method of the embodiment of the invention comprises the following steps:

receiving a first operation acting on a first interface;

responding to the first operation, and transmitting a calling command to the unified caller in a character string mode;

extracting interface information associated with the calling command from the unified caller, and determining to perform interface calling on a second interface according to the interface information;

and triggering the call of the second interface, and starting the second interface.

In the foregoing solution, the responding to the first operation and transmitting the call command to the unified caller in a character string manner includes:

acquiring an operation parameter triggered by the first operation, and acquiring a command line character string for executing the calling command according to the operation parameter;

and transmitting the command line character string to a unified caller.

In the foregoing solution, the extracting interface information associated with the call command from the unified caller, and determining to perform interface call on a second interface according to the interface information includes:

and querying a character string of the second interface class corresponding to the command line character string, and determining to perform interface call on the second interface.

In the foregoing solution, the opening the second interface includes:

and opening the second interface according to the character string of the second interface class.

In the foregoing solution, the opening the second interface includes:

reflecting the character string of the second interface class through the unified caller to create a second interface class corresponding to the second interface;

opening the second interface according to the second interface class.

In the above scheme, the method further comprises:

the first interface establishes association with the second interface through the unified caller, and association is not directly generated between the first interface and the second interface.

A terminal according to an embodiment of the present invention includes:

the receiving unit is used for receiving a first operation acting on the first interface;

the response unit is used for responding to the first operation and transmitting a calling command to the unified caller in a character string mode;

the calling unit is used for extracting interface information associated with the calling command from the unified caller and determining to carry out interface calling on a second interface according to the interface information;

and the starting unit is used for triggering the calling of the second interface and starting the second interface.

In the foregoing solution, the response unit is further configured to:

acquiring an operation parameter triggered by the first operation, and acquiring a command line character string for executing the call command according to the operation parameter;

and transmitting the command line character string to a unified caller.

In the foregoing solution, the invoking unit is further configured to:

In the foregoing solution, the opening unit is further configured to:

opening the second interface according to the second interface class.

In the foregoing solution, the terminal further includes: an association unit configured to:

The interface calling method of the embodiment of the invention comprises the following steps: receiving a first operation acting on a first interface; responding to the first operation, and transmitting a calling command to the unified caller in a character string mode; extracting interface information associated with the calling command from the unified caller, and determining to perform interface calling on a second interface according to the interface information; and triggering the calling of the second interface, and starting the second interface.

By adopting the embodiment of the invention, the calling command and the interface information associated with the calling command are stored in the unified caller, so that the unified caller can realize information transmission and management between the first interface and the second interface based on the information associated with each other. After responding to the first operation acting on the first interface, the calling command is transmitted to the unified caller in a character string mode (such as a character string of the calling command), and the calling action is transmitted in a character string mode (such as a character string of the calling command), so that decoupling of codes is realized. The unified caller is adopted to realize the association of calling action and target interface, thereby realizing the centralized unified management of codes scattered in each module of the application on the basis. And adopting the calling command extracted from the unified caller and the interface information associated with the calling command, thereby obtaining that a target interface associated with the calling command is a second interface, and starting the second interface after triggering the calling of the second interface. And the calling command and the interface information associated with the calling command are easy to be subsequently expanded and modified in the unified caller.

Drawings

Fig. 1 is a schematic diagram of an alternative hardware architecture of a mobile terminal implementing various embodiments of the present invention;

FIG. 2 is a schematic diagram of a communication system of the mobile terminal shown in FIG. 1;

FIG. 3 is a diagram of hardware entities performing information interaction according to an embodiment of the present invention;

FIG. 4 is a schematic flow chart illustrating a method according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of an interface call relationship according to an embodiment of the present invention;

FIG. 6 is a diagram illustrating a prior art interface call relationship;

FIG. 7 is a flowchart illustrating an implementation of another method according to an embodiment of the present invention;

FIG. 8 is a flow chart illustrating an implementation of another method according to an embodiment of the present invention;

FIG. 9 is a diagram of a system architecture according to an embodiment of the present invention;

fig. 10 is a schematic diagram of an interface call scenario to which an embodiment of the present invention is applied.

Detailed Description

The following describes the embodiments in further detail with reference to the accompanying drawings.

A mobile terminal implementing various embodiments of the present invention will now be described with reference to the accompanying drawings. In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the description of the embodiments of the present invention, and have no specific meaning in themselves. Thus, "module" and "component" may be used in a mixture.

In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks that have been disclosed have not been described in detail as not to unnecessarily obscure aspects of the embodiments.

In addition, although the terms "first", "second", etc. are used herein several times to describe various elements (or various thresholds or various applications or various instructions or various operations), etc., these elements (or thresholds or applications or instructions or operations) should not be limited by these terms. These terms are only used to distinguish one element (or threshold or application or instruction or operation) from another element (or threshold or application or instruction or operation). For example, a first operation may be referred to as a second operation, and a second operation may be referred to as a first operation, without departing from the scope of the invention, the first operation and the second operation being operations, except that they are not the same operation.

The steps in the embodiment of the present invention are not necessarily processed according to the described step sequence, and may be optionally rearranged in a random manner, or steps in the embodiment may be deleted, or steps in the embodiment may be added according to requirements.

The term "and/or" in embodiments of the present invention refers to any and all possible combinations including one or more of the associated listed items. It is also to be noted that: when used in this specification, the term "comprises/comprising" specifies the presence of stated features, integers, steps, operations, elements and/or components but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements and/or components and/or groups thereof.

The intelligent terminal (e.g., mobile terminal) of the embodiments of the present invention may be implemented in various forms. For example, the mobile terminal described in the embodiments of the present invention may include a mobile terminal such as a mobile phone, a smart phone, a notebook computer, a Digital broadcast receiver, a Personal Digital Assistant (PDA), a tablet computer (PAD), a Portable Multimedia Player (PMP), a navigation device, and the like, and a fixed terminal such as a Digital TV, a desktop computer, and the like. In the following, it is assumed that the terminal is a mobile terminal. However, it will be understood by those skilled in the art that the configuration according to the embodiment of the present invention can be applied to a fixed type terminal in addition to elements particularly used for moving purposes.

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

The mobile terminal 100 may include a communication unit 110, an audio/video (a/V) input unit 120, a user input unit 130, a receiving unit 140, a responding unit 141, a calling unit 142, a turning-on unit 143, an output unit 150, a storage unit 160, an interface unit 170, a processing unit 180, a power supply unit 190, and the like. Fig. 1 illustrates a mobile terminal having various components, but it is to be understood that not all illustrated components are required to be implemented. More or fewer components may alternatively be implemented. Elements of the mobile terminal will be described in detail below.

The communication unit 110 typically includes one or more components that allow radio communication between the mobile terminal 100 and a wireless communication system or network (or may be in electrical communication by wire if the mobile terminal is replaced with a fixed terminal). For example, when the communication unit is embodied as a wireless communication unit, it may include at least one of the broadcast receiving unit 111, the mobile communication unit 112, the wireless internet unit 113, the short-range communication unit 114, and the location information unit 115, which are optional and may be added or deleted according to different requirements.

The broadcast receiving unit 111 receives a broadcast signal and/or broadcast associated information from an external broadcast management server via a broadcast channel. The broadcast channel may include a satellite channel and/or a terrestrial channel. The broadcast management server may be a server that generates and transmits a broadcast signal and/or broadcast associated information or a server that receives a previously generated broadcast signal and/or broadcast associated information and transmits it to a terminal. The broadcast signal may include a TV broadcast signal, a radio broadcast signal, a data broadcast signal, and the like. Also, the broadcast signal may further include a broadcast signal combined with a TV or radio broadcast signal. The broadcast associated information may also be provided via a mobile communication network, and in this case, the broadcast associated information may be received by the mobile communication unit 112. The broadcast signal may exist in various forms, for example, it may exist in the form of an Electronic Program Guide (EPG) of Digital Multimedia Broadcasting (DMB), an Electronic Service Guide (ESG) of Digital Video Broadcasting Handheld (DVB-H), and the like. The broadcast receiving unit 111 can receive signal broadcasts by using various types of broadcast systems. In particular, the broadcast receiving unit 111 may receive Digital broadcasts by using a Digital Broadcasting system such as a Digital Multimedia Broadcasting-Terrestrial (DMB-T), a Digital Multimedia Broadcasting-Satellite (DMB-S), DVB-H, a data Broadcasting system of a Forward Link Media (Media Forward Link Only), an Integrated Services Digital Broadcasting-Terrestrial (ISDB-T), and the like. The broadcast receiving unit 111 may be configured to be suitable for various broadcast systems that provide broadcast signals as well as the above-described digital broadcast system. The broadcast signal and/or the broadcast-related information received via the broadcast receiving unit 111 may be stored in the storage unit 160 (or other type of storage medium).

The mobile communication unit 112 transmits and/or receives radio signals to and/or from at least one of a base station (e.g., access point, node B, etc.), an external terminal, and a server. Such radio signals may include voice call signals, video call signals, or various types of data transmitted and/or received according to text and/or multimedia messages.

The wireless internet unit 113 supports wireless internet access of the mobile terminal. The unit may be internally or externally coupled to the terminal. The Wireless internet Access technology related to the unit may include a Wireless Local Area Network (WLAN), a Wireless Fidelity (Wi-Fi) Wireless broadband (Wibro), a worldwide interoperability for microwave Access (Wimax), a High Speed Downlink Packet Access (HSDPA), and the like.

The short-range communication unit 114 is a unit for supporting short-range communication. Some examples of short-range communication technologies include bluetooth, Radio Frequency Identification (RFID), Infrared Data Association (IrDA), Ultra Wideband (UWB), zigbee, and the like.

The location information unit 115 is a unit for checking or acquiring location information of the mobile terminal. A typical example of the location information unit is a Global Positioning System (GPS). According to the current technology, the location information unit 115 calculates distance information and accurate time information from three or more satellites and applies triangulation to the calculated information, thereby accurately calculating three-dimensional current location information according to longitude, latitude, and altitude. Currently, a method for calculating position and time information uses three satellites and corrects an error of the calculated position and time information by using another satellite. Further, the position information unit 115 can calculate the speed information by continuously calculating the current position information in real time.

The a/V input unit 120 is used to receive an audio or video signal. The a/V input unit 120 may include a camera 121 and a microphone 122, and the camera 121 processes image data of still pictures or video obtained by an image capturing apparatus in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 151. The image frames processed by the cameras 121 may be stored in the storage unit 160 (or other storage medium) or transmitted via the communication unit 110, and two or more cameras 121 may be provided according to the construction of the mobile terminal. The microphone 122 may receive sounds (audio data) via the microphone in a phone call mode, a recording mode, a voice recognition mode, or the like, and can process 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 mobile communication unit 112 in case of the phone call mode. The microphone 122 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 user input unit 130 may generate key input data according to a command input by a user to control various operations of the mobile terminal. The user input unit 130 allows a user to input various types of information, and may include a keyboard, a mouse, a touch pad (e.g., a touch-sensitive member that detects changes in resistance, pressure, capacitance, and the like due to being touched), a wheel, a joystick, and the like. In particular, when the touch pad is superimposed on the display unit 151 in the form of a layer, a touch screen may be formed.

A receiving unit 140, configured to receive a first operation applied to a first interface; a response unit 141, configured to respond to the first operation and transmit a call command to the unified caller in a character string manner; the calling unit 142 is configured to extract interface information associated with the calling command from the unified caller, and determine to perform interface calling on a second interface according to the interface information; the opening unit 143 is configured to trigger the call to the second interface, and open the second interface.

The interface unit 170 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 unit, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The identification unit may store various information for authenticating a User using the mobile terminal 100 and may include a User identification Unit (UIM), a Subscriber identification unit (SIM), a Universal Subscriber Identity Module (USIM), and the like. In addition, a device having an identification unit (hereinafter, referred to as an "identification device") may take the form of a smart card, and thus, the identification device may be connected with the mobile terminal 100 via a port or other connection means. The interface unit 170 may be used to receive input (e.g., data information, power, etc.) from an external device 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 and the external device.

In addition, when the mobile terminal 100 is connected with an external cradle, the interface unit 170 may serve as a path through which power is supplied from the cradle to the mobile terminal 100 or may serve as a path through which various command signals input from the cradle are transmitted to the mobile terminal. Various command signals or power input from the cradle may be used as signals for recognizing whether the mobile terminal is accurately mounted on the cradle. The output unit 150 is configured to provide output signals (e.g., audio signals, video signals, vibration signals, etc.) in a visual, audio, and/or tactile manner. The output unit 150 may include a display unit 151, an audio output unit 152, and the like.

The display unit 151 may display information processed in the mobile terminal 100. For example, the mobile terminal 100 may display a related User Interface (UI) or a Graphical User Interface (GUI). When the mobile terminal 100 is in a video call mode or an image capturing mode, the display unit 151 may display a captured image and/or a received image, a UI or GUI showing a video or an image and related functions, and the like.

Meanwhile, when the display unit 151 and the touch pad are overlapped with each other in the form of a layer to form a touch screen, the display unit 151 may serve as an input device and an output device. The Display unit 151 may include at least one of a Liquid Crystal Display (LCD), a Thin Film Transistor LCD (TFT-LCD), an Organic Light-Emitting Diode (OLED) Display, a flexible Display, a three-dimensional (3D) Display, and the like. Some of these displays may be configured to be transparent to allow a user to see from the outside, which may be referred to as transparent displays, and a typical transparent display may be, for example, a Transparent Organic Light Emitting Diode (TOLED) display or the like. The mobile terminal 100 may include two or more display units (or other display devices) according to particular desired embodiments, for example, the mobile terminal may include an external display unit (not shown) and an internal display unit (not shown). The touch screen may be used to detect a touch input pressure as well as a touch input position and a touch input area.

The audio output unit 152 may convert audio data received by the communication unit 110 or stored in the storage unit 160 into an audio signal and output as sound when the mobile terminal 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 152 may 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 152 may include a speaker, a buzzer, and the like.

The storage unit 160 may store software applications and the like that control operations and processes performed by the processing unit 180, or may temporarily store data (e.g., a phonebook, messages, still images, videos, and the like) that has been output or is to be output. Also, the storage unit 160 may store data regarding various ways of vibration and audio signals output when a touch is applied to the touch screen.

The storage unit 160 may include at least one type of storage medium including a flash Memory, a hard disk, a multimedia card, a card-type Memory (e.g., SD or DX Memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic Memory, a magnetic disk, an optical disk, and so on. Also, the mobile terminal 100 may cooperate with a network storage device that performs a storage function of the storage unit 160 through network connection.

The processing unit 180 generally controls the overall operation of the mobile terminal. For example, the processing unit 180 performs control and processing related to voice calls, data communications, video calls, and the like. As another example, the processing unit 180 may perform a pattern recognition process to recognize a handwriting input or a picture drawing input performed on the touch screen as a character or an image.

The power supply unit 190 receives external power or internal power and provides appropriate power required to operate the elements and components under the control of the processing unit 180.

The various embodiments described herein may be implemented in a computer-readable medium using, for example, computer software, hardware, or any combination thereof. For a hardware implementation, the embodiments described herein may be implemented using at least one of an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Digital Signal Processing Device (DSPD), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a processor, a controller, a microcontroller, a microprocessor, and an electronic unit designed to perform the functions described herein, and in some cases, such embodiments may be implemented in the Processing unit 180. For a software implementation, the implementation such as a procedure or a function may be implemented with separate software units allowing to perform at least one function or operation. The software codes may be implemented by software applications written in any suitable programming language, which may be stored in the memory unit 160 and executed by the processing unit 180. A specific hardware entity of the storage unit 160 may be a memory, and a specific hardware entity of the processing unit 180 may be a controller.

Up to now, the mobile terminal has been described in terms of its functions. Hereinafter, a slide-type mobile terminal among various types of mobile terminals, such as a folder-type, bar-type, swing-type, slide-type mobile terminal, and the like, will be described as an example for the sake of brevity. Accordingly, the present invention can be applied to any type of mobile terminal, and is not limited to a slide type mobile terminal.

The mobile terminal 100 as shown in fig. 1 may be configured to operate with communication systems such as wired and wireless communication systems and satellite-based communication systems that transmit data via frames or packets.

A communication system in which a mobile terminal according to an embodiment of the present invention is operable will now be described with reference to fig. 2.

Such communication systems may use different air interfaces and/or physical layers. For example, the air interface used by the communication System includes, for example, Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), and Universal Mobile Telecommunications System (UMTS) (in particular, Long Term Evolution (LTE)), global System for Mobile communications (GSM), and the like. By way of non-limiting example, the following description relates to a CDMA communication system, but such teachings are equally applicable to other types of systems.

Referring to fig. 2, the CDMA wireless communication system may include a plurality of Mobile terminals 100, a plurality of Base Stations (BSs) 270, a Base Station Controller (BSC) 275, and a Mobile Switching Center (MSC) 280. The MSC280 is configured to interface with a Public Switched Telephone Network (PSTN) 290. The MSC280 is also configured to interface with BSCs 275, which may be coupled to the BS270 via a backhaul. The backhaul may be constructed according to any of several known interfaces including, for example, E1/T1, ATM, IP, PPP, frame Relay, HDSL, ADSL, or xDSL. It will be understood that a system as shown in fig. 2 may include multiple BSCs 275.

Each BS270 may serve one or more sectors (or regions), each sector covered by a multi-directional antenna or an antenna pointing in a particular direction being radially distant from the BS 270. Alternatively, each partition may be covered by two or more antennas for diversity reception. Each BS270 may be configured to support multiple frequency allocations, with each frequency allocation having a particular frequency spectrum (e.g., 1.25MHz, 5MHz, etc.).

The intersection of partitions with frequency allocations may be referred to as a CDMA channel. The BS270 may also be referred to as a Base Transceiver Subsystem (BTS) or other equivalent terminology. In such a case, the term "base station" may be used to generically refer to a single BSC275 and at least one BS 270. The base stations may also be referred to as "cells". Alternatively, each sector of a particular BS270 may be referred to as a plurality of cell sites.

As shown in fig. 2, a Broadcast Transmitter (BT) 295 transmits a Broadcast signal to the mobile terminal 100 operating within the system. A broadcast receiving unit 111 as shown in fig. 1 is provided at the mobile terminal 100 to receive a broadcast signal transmitted by the BT 295. In fig. 2, several satellites 300 are shown, for example, GPS satellites 300 may be employed. The satellite 300 assists in locating at least one of the plurality of mobile terminals 100.

In fig. 2, a plurality of satellites 300 are depicted, but it is understood that useful positioning information may be obtained with any number of satellites. The location information unit 115 as shown in fig. 1 is generally configured to cooperate with the satellites 300 to obtain desired positioning information. Other techniques that can track the location of the mobile terminal may be used instead of or in addition to GPS tracking techniques. In addition, at least one GPS satellite 300 may selectively or additionally process satellite DMB transmission.

As a typical operation of the wireless communication system, the BS270 receives reverse link signals from various mobile terminals 100. The mobile terminal 100 is generally engaged in conversations, messaging, and other types of communications. Each reverse link signal received by a particular base station is processed within a particular BS 270. The obtained data is forwarded to the associated BSC 275. The BSC provides call resource allocation and mobility management functions including coordination of soft handoff procedures between BSs 270. The BSCs 275 also route the received data to the MSC280, which provides additional routing services for interfacing with the PSTN 290. Similarly, the PSTN290 interfaces with the MSC280, the MSC interfaces with the BSCs 275, and the BSCs 275 accordingly control the BS270 to transmit forward link signals to the mobile terminal 100.

The mobile communication unit 112 of the communication unit 110 in the mobile terminal accesses the mobile communication network based on the necessary data (including the user identification information and the authentication information) of the mobile communication network (such as the mobile communication network of 2G/3G/4G, etc.) built in the mobile terminal to transmit the mobile communication data (including the uplink mobile communication data and the downlink mobile communication data) for the services of web browsing, network multimedia playing, etc. of the mobile terminal user.

The wireless internet unit 113 of the communication unit 110 performs a function of a wireless hotspot by operating a related protocol function of the wireless hotspot, the wireless hotspot supports access by a plurality of mobile terminals (any mobile terminal other than the mobile terminal), transmits mobile communication data (including uplink mobile communication data and downlink mobile communication data) for mobile terminal user's web browsing, network multimedia playing and other services by multiplexing the mobile communication connection between the mobile communication unit 112 and the mobile communication network, since the mobile terminal essentially multiplexes the mobile communication connection between the mobile terminal and the communication network for transmitting mobile communication data, the traffic of mobile communication data consumed by the mobile terminal is charged to the communication tariff of the mobile terminal by a charging entity on the side of the communication network, thereby consuming the data traffic of the mobile communication data included in the communication tariff contracted for use by the mobile terminal.

Fig. 3 is a schematic diagram of hardware entities performing information interaction in the embodiment of the present invention, where fig. 3 includes: a terminal device 1 and a server 2. The terminal device 1 is composed of terminal devices 11-14, and the terminal devices perform information interaction with a server through a wired network or a wireless network. The terminal equipment comprises mobile phones, desktop computers, PC machines, all-in-one machines and the like. By adopting the embodiment of the invention, at least one application is locally operated on the terminal, the application data or the application upgrading data can be acquired from the server, and the server exists as a data source. In the prior art, an interface in the application transfers the class name of a target interface as a parameter to open the target interface, and different from the prior art, the embodiment of the invention modifies the transfer mode of the parameter from the class name of the transferred target interface into a character string of a call command. The character string is similar to the character array in the storage format, and can be used as a command line, such as a symbol string (a string of characters "abc"), or a binary number string (a string of binary numbers "0110", etc.), such as a command line with the character string "ssqchaose", for opening the ball selection interface of the bicolor ball. Because a string is similar to a character array in storage format, the individual elements of each bit in the string can be directly identified and extracted, and if s ═ abcdefghij ", s [0] ═ a", s [9] ═ j ", and the zero position of the string is exactly its length, e.g., s [0] ═ 10, and so on. In the process of transmitting the character string, the character string is used as a continuous sequence of symbols or numerical values, and can be transmitted in a character string array form, and parameter transmission of a character string command line can also be realized in a pointer mode. And then, the character string is transmitted to the unified caller, the information transmission of a first interface (such as an application interface) and a second interface (such as a target interface to be called) and the unified centralized management of a plurality of interfaces (such as the first interface and the second interface and the like) are carried out according to the relevance between the first interface and the second interface established in the unified caller, and finally the second interface (such as the target interface) is opened through the unified caller. In the embodiment of the present invention, in order to simplify the description of interface invocation, only invocation between two interfaces is taken as an example, and in practical application, the interface invocation is not limited to two interfaces. The processing logic called by the interface is executed on the terminal side, specifically, as shown in fig. 3, the processing logic 10 includes: s1, establishing configuration information, wherein the configuration information can be a mapping relation between a calling command (such as a calling command for the first interface to call the second interface) and interface information associated with the calling command; s2, after receiving the first operation acting on the first interface and responding to the first operation acting on the first interface, transmitting the calling command to the unified caller in a character string mode so as to transmit and manage information between the first interface and the second interface through the unified caller; s3, extracting the configuration information from the unified caller, obtaining interface information associated with the calling command as a second interface according to the configuration information, triggering the calling of the second interface, and starting the second interface.

The above example of fig. 3 is only an example of a system architecture for implementing the embodiment of the present invention, and the embodiment of the present invention is not limited to the system architecture described in the above fig. 3, and various embodiments of the method of the present invention are proposed based on the system architecture described in the above fig. 3.

As shown in fig. 4, an interface calling method according to an embodiment of the present invention includes: a first operation (101) is received that acts on a first interface. In actual operation, before receiving the first operation, the configuration information may be pre-established, and the configuration information may be a mapping relationship between a call command (e.g., a call command for the first interface to make an interface call to the second interface) and interface information associated with the call command. The configuration information may be used directly afterwards after initial establishment. Of course, the configuration information may also update the content according to actual needs. That is, the operation of establishing the configuration information may be a preset storage operation, the configuration information is not generated every time the process of the embodiment of the present invention is executed, and the establishment of the configuration information may be an initial operation, which is preset only when the process of the embodiment of the present invention is executed for the first time. And after receiving a first operation acting on the first interface, responding to the first operation, transmitting the calling command to the unified caller in a character string mode, and performing information transmission and management between the first interface and the second interface through the unified caller (102). In practical applications, the first interface may be an application interface, and the second interface may be a target interface to be opened. For example, in an application interface, a user may select an option in a graphical user interface corresponding to an application to trigger a first operation, receive an event parameter (the event parameter may be a character string of an invocation command) caused by the first operation, and then respond to the first operation, and then transmit the invocation command to the unified invoker in the form of a character string. And extracting interface information associated with the call command from the unified caller, and determining to perform interface call on the second interface according to the interface information (103). If the configuration information is stored in advance, the configuration information can be extracted from the unified caller, the interface information associated with the calling command is obtained according to the configuration information, and when the interface information is the second interface, the calling of the second interface is triggered, and the second interface is started (104).

By adopting the embodiment of the invention, the calling command (or called calling action) is transmitted in a character string mode, and the unified caller is used for uniformly managing and opening the second interface relative to the first interface. The first interface can be an application interface, and the second interface is a target interface which the application interface wants to call. The application interface and the target interface of the calling party are not directly associated, and both the application interface and the target interface are only associated with the unified caller as shown in fig. 5, so that the association relationship between the interfaces is greatly simplified by collecting the calling relationship between the interfaces to the unified caller for association and unified management, the existing interface association relationship is shown in fig. 6, the application interface and the target interface of the calling party are directly associated, the management is very inconvenient, and the relationship between the application interface and the target interface is not clear.

As shown in fig. 7, an interface calling method according to an embodiment of the present invention includes: a first operation is received (201) acting on a first interface. In actual operation, before receiving the first operation, configuration information may be pre-established, where the configuration information may be a mapping relationship between a call command (e.g., a call command for the first interface to make an interface call to the second interface) and interface information associated with the call command. The configuration information may be used directly afterwards after initial establishment. Of course, the configuration information may also update the content according to actual needs. That is, the operation of establishing the configuration information may be a preset storage operation, the configuration information is not generated every time the process of the embodiment of the present invention is executed, and the establishment of the configuration information may be an initial operation, which is preset only when the process of the embodiment of the present invention is executed for the first time. And after receiving a first operation acting on a first interface, responding to the first operation and acquiring an operation parameter triggered by the first operation. The operation parameter in this embodiment is an event parameter for the first operation, for example, the first operation is a button click event for a certain news link on a web application interface, and a button is clicked, a corresponding event parameter is generated by triggering, the event parameter determines that the button click event is a button click event for a current news link, and the event parameter is dynamically obtained, and the parameter may use a single or double quotation mark to carry out value transfer, for example, < inputtype ═ button "id ═ button1 ═ class ═ nimi-button" on click ═ setdate this); "value ═ set date"/>. And after the first operation is triggered, obtaining a command line character string for executing the call command according to the operation parameters, and transmitting the command line character string to a unified caller (202). Specifically, an action is called by executing a "call command"; after the command line character string is transmitted to the unified caller, the subsequent unified caller can uniformly manage the 'call command' call action and the target interface through the association of the two, and finally, the parameter is transmitted in the character string mode to open the target interface quickly. In practical applications, the first interface may be an application interface, and the second interface may be a target interface to be opened. For example, in an application interface, a user may select an option in a graphical user interface corresponding to an application to trigger a first operation, receive an event parameter (the event parameter may be a character string of an invocation command) caused by the first operation, and then respond to the first operation, and then transmit the invocation command to the unified invoker in the form of a character string. And extracting interface information associated with the call command from the unified caller, and determining to perform interface call on a second interface according to the interface information (203). If the configuration information is stored in advance, the established configuration information can be extracted from the unified caller, the character string of the second interface class corresponding to the command line character string is inquired according to the established configuration information, and the second interface is opened according to the character string of the second interface class (204).

By adopting the embodiment of the invention, in an actual application, the first interface is an application interface, the second interface is a target interface to be opened, the application interface and the target interface of the calling party are not directly associated, and both the application interface and the target interface are only associated with the unified calling device. And modifying the transfer mode of the parameters from the class name of the transfer target interface into a character string of a call command, transferring the character string of the call command to the unified caller, finding the character string of the target interface class by the unified caller through inquiring the configuration of the call command and the target interface, and finally opening the target interface. Transferring the calling action in a character string mode, and realizing the decoupling of codes; and a unified caller is introduced to realize the association and unified management of the calling action and the target interface, and the flexibility of modifying the target interface can be improved by utilizing a configuration table of the target interface.

As shown in fig. 8, an interface calling method according to an embodiment of the present invention includes: a first operation is received (301) acting on a first interface. In actual operation, before receiving the first operation, the configuration information may be pre-established, and the configuration information may be a mapping relationship between a call command (e.g., a call command for the first interface to make an interface call to the second interface) and interface information associated with the call command. The configuration information may be used directly afterwards after initial establishment. Of course, the configuration information may also update the content according to actual needs. That is, the operation of establishing the configuration information may be a preset storage operation, the configuration information is not generated every time the process of the embodiment of the present invention is executed, and the establishment of the configuration information may be an initial operation, which is preset only when the process of the embodiment of the present invention is executed for the first time. After receiving a first operation acting on a first interface, responding to the first operation, and acquiring an operation parameter triggered by the first operation. The operation parameter in this embodiment is an event parameter for the first operation, for example, the first operation is a button click event for a certain news link on a web application interface, and a button is clicked, a corresponding event parameter is generated by triggering, the event parameter determines that the button click event is a button click event for a current news link, and the event parameter is dynamically obtained, and the parameter may use a single or double quotation mark to carry out value transfer, for example, < inputtype ═ button "id ═ button1 ═ class ═ nimi-button" on click ═ setdate this); "value ═ set date"/>. And after the first operation is triggered, obtaining a command line character string for executing the call command according to the operation parameters, and transmitting the command line character string to a unified caller (302). Specifically, an action is called by executing a "call command"; after the command line character string is transmitted to the unified caller, the subsequent unified caller can uniformly manage the 'call command' call action and the target interface through the association of the two, and finally, the parameter is transmitted in the character string mode to open the target interface quickly. In practical applications, the first interface may be an application interface, and the second interface may be a target interface to be opened. For example, in an application interface, a user may select an option in a graphical user interface corresponding to an application to trigger a first operation, receive an event parameter (the event parameter may be a character string of a call command) caused by the first operation, and then, in response to the first operation, transmit the call command to a unified caller for information transmission and management between the first interface and the second interface in the form of a character string. And extracting interface information associated with the call command from the unified caller, and determining to perform interface call on the second interface according to the interface information (303). If the configuration information is stored in advance, the established configuration information can be extracted from the unified caller, and the character string of the second interface class corresponding to the command line character string is inquired according to the configuration information (304). Reflecting the character string of the second interface class through the unified caller to create a second interface class corresponding to the second interface, and opening the second interface according to the second interface class (305).

By adopting the embodiment of the invention, in an actual application, the first interface is an application interface, the second interface is a target interface to be opened, the application interface and the target interface of the calling party are not directly associated, and both the application interface and the target interface are only associated with the unified calling device. Modifying the transfer mode of the parameters from the class name of the transfer target interface into a character string of a call command, transferring the character string to the unified caller, finding the character string of the target interface class by inquiring the configuration of the call command and the target interface by the unified caller, creating the target interface class by reflection, and finally opening the target interface. Transferring the calling action in a character string mode, and realizing the decoupling of codes; and a unified caller is introduced to realize the association and unified management of the calling action and the target interface, and the flexibility of modifying the target interface can be improved by utilizing a configuration table of the target interface.

In a specific implementation, the method includes: 1) the caller calls the unified call management class, and transmits a scheduling command, if a double-color ball selection button is clicked on an interface A, a command word of 'ssqchaose' is transmitted, and the unified call management class transmits the call command ssqchaose to a target interface query class so as to find a target interface corresponding to the command; 3) when a corresponding target interface is searched in the command and interface configuration according to the command words ssqchaose, if no ssqchaose command words exist in the command and interface configuration, failure is returned to terminate the call; if the ssqchoose command word is found in the command and interface configuration, the character string com.ssq.SSQChoseeActivy of the target interface is continuously transmitted backwards, and finally the character string of the target interface class is reflected into the target interface class through a java/objc reflection mechanism; 4) calling a method of the system to open a target interface, for example, android calls startActivity (context, "com.ssq.SSQChoseActivity") to open a two-color ball selection interface; and iOS calls pushcontroller (xxx) to open the two-color ball-selection interface.

An interface invoking system according to an embodiment of the present invention, as shown in fig. 9, includes a terminal 41 and a server 42, where at least one application is locally executed on the terminal 41, application data or application upgrade data may be obtained from the server 42, and the server 42 exists as a data source. Modifying the transfer mode of the parameters from the class name of a transfer target interface into a character string of a call command, transferring the character string to the unified caller, carrying out the transfer of information of a first interface (such as an application interface) and a second interface (such as a target interface to be called) and the unified centralized management of a plurality of interfaces (such as the first interface and the second interface) according to the relevance of the two interfaces established in the unified caller, and finally opening the second interface (such as the target interface) through the unified caller. In the embodiment of the present invention, in order to simplify the description of interface invocation, only invocation between two interfaces is taken as an example, and in practical application, the interface invocation is not limited to two interfaces. Wherein, the terminal 41 includes: a receiving unit 411 configured to receive a first operation applied to a first interface; a response unit 412, configured to respond to the first operation and transmit a call command to the unified caller in a character string manner; the calling unit 413 is configured to extract interface information associated with the calling command from the unified caller, and determine to perform interface calling on a second interface according to the interface information; the starting unit 414 is configured to trigger the call to the second interface, and start the second interface.

In the embodiment of the present invention, configuration information is established, where the configuration information may be a mapping relationship between a call command (for example, a call command for a first interface to perform interface call on a second interface) and interface information associated with the call command. The configuration information may be used directly afterwards after initial establishment. Of course, the configuration information may also update the content according to actual needs. The operation of establishing the configuration information may be a preset storage operation, and the configuration information is not generated every time the process of the embodiment of the present invention is executed, and the establishment of the configuration information may be an initial operation, which is preset only when the process of the embodiment of the present invention is executed for the first time. And receiving a first operation acting on the first interface, and transmitting the calling command to a unified caller for information transmission and management between the first interface and the second interface in a character string mode after responding to the first operation.

In practical applications, the first interface may be an application interface, and the second interface may be a target interface to be opened. For example, in an application interface, a user may select an option in a graphical user interface corresponding to an application to trigger a first operation, receive an event parameter (the event parameter may be a character string of a call command) caused by the first operation, and then, in response to the first operation, transmit the call command to a unified caller for information transmission and management between the first interface and the second interface in the form of a character string. And extracting the configuration information from the unified caller, obtaining the second interface associated with the calling command according to the configuration information, and carrying out interface calling on the second interface to open the second interface. By adopting the embodiment of the invention, the calling command (or called calling action) is transmitted in a character string mode, and the unified caller is used for uniformly managing and opening the second interface relative to the first interface. The first interface can be an application interface, and the second interface is a target interface which the application interface wants to call. The application interface and the target interface of the calling party are not directly associated, and both the application interface and the target interface are only associated with the unified caller as shown in fig. 5, so that the association relationship between the interfaces is greatly simplified by collecting the calling relationship between the interfaces to the unified caller for association and unified management, the existing interface association relationship is shown in fig. 6, the application interface and the target interface of the calling party are directly associated, the management is very inconvenient, and the relationship between the application interface and the target interface is not clear.

In an implementation manner of the embodiment of the present invention, the response unit is further configured to: acquiring an operation parameter triggered by the first operation, and acquiring a command line character string for executing the calling command according to the operation parameter; and transmitting the command line character string to a unified caller.

In an embodiment of the present invention, the invoking unit is further configured to: and querying a character string of the second interface class corresponding to the command line character string, and determining to perform interface call on the second interface.

In an embodiment of the present invention, configuration information may be stored in advance, and the configuration information may be a mapping relationship between a call command (for example, a call command for making an interface call to a second interface by a first interface) and interface information associated with the call command. The configuration information may be used directly afterwards after initial establishment. Of course, the configuration information may also update the content according to actual needs. The operation of establishing the configuration information may be a predetermined storage operation. The opening unit is further configured to: and after the character string of the second interface class corresponding to the command line character string is inquired according to the configuration information, opening the second interface according to the character string of the second interface class.

In an embodiment of the present invention, configuration information may be stored in advance, and the configuration information may be a mapping relationship between a call command (for example, a call command for making an interface call to a second interface by a first interface) and interface information associated with the call command. The configuration information may be used directly afterwards after initial establishment. Of course, the configuration information may also update the content according to actual needs. The operation of establishing the configuration information may be a predetermined storage operation. The opening unit is further configured to: after the character string of the second interface class corresponding to the command line character string is inquired according to the configuration information, reflecting the character string of the second interface class through the unified caller to create the second interface class corresponding to the second interface; and opening the second interface according to the character string of the second interface class.

In an implementation manner of the embodiment of the present invention, the terminal further includes: an association unit configured to: the first interface establishes association with the second interface through the unified caller, and association is not directly generated between the first interface and the second interface.

For the processor for data Processing, when executing Processing, the processor can be implemented by a microprocessor, a Central Processing Unit (CPU), a DSP or an FPGA; for the storage medium, the storage medium contains operation instructions, which may be computer executable codes, and the operation instructions implement the steps in the flow of the information processing method according to the above-described embodiment of the present invention.

Here, it should be noted that: the above description related to the terminal and the server items is similar to the above description of the method, and the description of the beneficial effects of the same method is omitted for brevity. For technical details not disclosed in the embodiments of the terminal and the server of the present invention, please refer to the description of the embodiments of the method flow of the present invention.

The embodiment of the invention is explained by taking a practical application scene as an example as follows:

in an application scenario of interface calling, the prior art is adopted, and for interface calling, a class name of a target interface is directly transmitted as a parameter through an interface in an application to open the target interface, and the defects are as follows: the interface is directly related to the class of the target interface, so that the codes are strongly coupled; the codes for opening the target interface are scattered in each module of the application, and unified and centralized management is not available; the interface is directly related to the class of the target interface, and the target interface is difficult to modify subsequently.

For the scene, the embodiment of the invention is adopted, the existing implementation mode and flow are changed, the transmission mode of the parameters is modified from the class name of the transmission target interface to a character string of the call command and is transmitted to the unified caller, the unified caller finds the character string of the target interface class by inquiring the configuration of the call command and the target interface, then the target interface class is created through reflection, and finally the target interface is opened. Transferring the calling action in a character string mode, and realizing the decoupling of codes; introducing a unified caller to realize the association and unified management of the calling action and the target interface; the flexibility of modifying the target interface is improved by using the configuration table of the target interface, and specifically, the embodiment can be a scheme for uniformly calling the interface in the App. First, the technical terms involved are described: 1) UI (also called user interface) refers to: a medium for interaction and information exchange between a system and a user that enables conversion between an internal form of information and a human-acceptable form. 2) The command refers to: an indication is sent to some interpreter program in order to accomplish some specific task. In most cases a command is either an indication to a command line interface application (e.g. shell) or an event in a graphical user interface caused by a user selecting a menu of items.

The calling relationship between interfaces before improvement is shown in fig. 6, a calling party interface directly associates a target interface to open the target interface (for example, an interface a associates and references an interface E to open an interface E; an interface a associates and references an interface F to open an interface F; an interface B associates and references an interface E to open an interface E; and an interface C associates and references an interface F to open an interface F), so that the interfaces are associated and cross-referenced.

The improved inter-interface calling relationship is shown in fig. 5, the target interface is managed and opened in a unified manner by using the unified caller, the caller interface and the target interface are not directly associated, and only the caller interface is associated with the unified caller, and the inter-interface calling relationship is collected to the unified caller, so that the inter-interface association relationship is greatly simplified.

Fig. 10 is a flowchart of an act unified scheduling according to an embodiment of the present invention, including: 1) the caller calls the unified call management class, and transmits a scheduling command, and if a double-color ball selecting button is clicked on an interface A, a command word of 'ssqchaose' is transmitted; 2) the unified scheduling management class transmits the command ssqchaose to a target interface query class so as to find a target interface corresponding to the command; 3) searching a corresponding target interface in the command and interface configuration according to the command word ssqchaose; 4) if the command and the interface configuration do not have ssqchaose command words, failure is returned, and the calling is terminated; 5) if the ssqchoose command word is found in the command and interface configuration, the character string com.ssq.ssqchoseeactivy of the target interface is transmitted backwards; 6) reflecting the target interface type character string into a target interface type through a java/objc reflection mechanism; 7) calling a method of the system to open a target interface, for example, calling startActivity (context, "com.ssq.SSQChoseActivity") in android to open a two-color ball selection interface; in iOS, pushcontroller (xxx) is called to open the two-color ball-selecting interface.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the unit is only a logical functional division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or units may be electrical, mechanical or other forms.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on a plurality of network units; some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, all the functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be separately regarded as one unit, or two or more units may be integrated into one unit; the integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

Those of ordinary skill in the art will understand that: all or part of the steps of implementing the method embodiments may be implemented by hardware related to application instructions, where the application may be stored in a computer readable storage medium, and when executed, the application performs the steps including the method embodiments; and the aforementioned storage medium includes: a mobile storage device, a ROM, a RAM, a magnetic disk or an optical disk, and various media capable of storing application codes.

Alternatively, the integrated unit of the present invention may be stored in a computer-readable storage medium if it is implemented in the form of a software functional unit and sold or used as a separate product. Based on such understanding, the technical solutions of the embodiments of the present invention or portions thereof contributing to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a mobile storage device, a ROM, a RAM, a magnetic disk or an optical disk, and various media capable of storing application codes.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.

Claims

1. An interface calling method, comprising:

receiving a first operation acting on a first interface;

responding to the first operation, transmitting a calling command to a unified caller in a character string mode, wherein the unified caller is used for information transmission and management between the first interface and the second interface;

extracting interface information associated with the calling command from the unified caller, and determining to perform interface calling on the second interface according to the interface information;

and triggering the calling of the second interface, and starting the second interface.

2. The method of claim 1, wherein said passing a call command to a unified caller in a string manner in response to said first operation comprises:

and transmitting the command line character string to a unified caller.

3. The method of claim 2, wherein extracting interface information associated with the call command from the unified caller, and determining from the interface information to interface with a second interface comprises:

4. The method of claim 3, wherein said opening said second interface comprises:

5. The method of claim 3, wherein said opening said second interface comprises:

opening the second interface according to the second interface class.

6. The method according to any one of claims 1 to 5, further comprising:

7. A terminal, characterized in that the terminal comprises:

the response unit is used for responding to the first operation and transmitting a calling command to the unified caller in a character string mode, wherein the unified caller is used for carrying out information transmission and management between the first interface and the second interface;

the calling unit is used for extracting interface information associated with the calling command from the unified caller and determining to carry out interface calling on the second interface according to the interface information;

8. The terminal of claim 7, wherein the response unit is further configured to:

and transmitting the command line character string to a unified caller.

9. The terminal of claim 8, wherein the invoking unit is further configured to:

10. The terminal of claim 9, wherein the enabling unit is further configured to:

11. The terminal of claim 9, wherein the enabling unit is further configured to:

opening the second interface according to the second interface class.

12. The terminal according to any of claims 7 to 11, characterized in that the terminal further comprises: an association unit configured to:

13. An electronic device, characterized in that the electronic device comprises:

a memory for storing executable instructions;

a processor for implementing the interface invocation method of any of claims 1 to 6 when executing executable instructions or computer programs stored in the memory.

14. A computer-readable storage medium storing executable instructions or a computer program, wherein the executable instructions, when executed by a processor, implement the interface invocation method of any of claims 1-6.