CN107911401B - Application plug-in extension function method and application server - Google Patents
Application plug-in extension function method and application server Download PDFInfo
- Publication number
- CN107911401B CN107911401B CN201710658116.8A CN201710658116A CN107911401B CN 107911401 B CN107911401 B CN 107911401B CN 201710658116 A CN201710658116 A CN 201710658116A CN 107911401 B CN107911401 B CN 107911401B
- Authority
- CN
- China
- Prior art keywords
- plug
- interface
- application
- request
- application server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Signal Processing (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention discloses an application server, which comprises a memory, a processor and an application plug-in extension function system which is stored on the memory and can run on the processor, wherein the application plug-in extension function system realizes the following steps when being executed by the processor: when an extended function request sent by a mobile terminal client is received, determining the function type of a plug-in to be called according to the extended function request; sending a request for calling a plug-in interface according to the plug-in function type to be called; verifying whether the plug-in requested to be called is registered in the application server; and when the plug-in requested to be called is verified to be registered, loading and enabling the data of the plug-in, and generating the user operation interface element. The invention also provides a method for extending the function of the application plug-in. The application server and the application plug-in extension function method provided by the invention can extend the functions of the application server through the application plug-in, relieve the operation pressure of the application server and improve the user experience.
Description
Technical Field
The invention relates to the field of computer communication, in particular to an application plug-in extension function method and an application server.
Background
With the development of society and the advancement of technology, people have more and more requirements on the service functions of network service systems, such as anti-fraud systems, and the demand of data is increasing. Accordingly, the network service system needs to be expanded to update new services and new functions, upgrading the database. However, many systems at present cannot support user-defined development, and if the system needs function extension, manufacturer customized development is needed, the process is tedious, and flexibility is lacked.
Disclosure of Invention
In view of this, the present invention provides an application plug-in extension function method and an application server, which can load external data, apply a plug-in extension function, and improve user experience.
First, to achieve the above object, the present invention provides an application server, where the application server includes a memory, a processor, and an application plug-in extended function system stored in the memory and capable of running on the processor, and when executed by the processor, the application plug-in extended function system implements the following steps:
when an extended function request sent by a mobile terminal client is received, determining the function type of a plug-in to be called according to the extended function request;
sending a request for calling a plug-in interface according to the plug-in function type to be called;
verifying whether the plug-in requested to be called is registered in the application server or not according to the request for calling the plug-in interface;
and when the plug-in requested to be called is verified to be registered, loading and enabling the data of the plug-in, and generating the user operation interface element.
Optionally, the processor is further configured to execute the application plug-in extension function system, so as to implement the following steps:
defining the plug-in interface;
and when a plug-in registration request sent by the mobile terminal client is received, executing plug-in registration, and generating a plug-in information table to be mapped to the plug-in interface.
Optionally, before the step of reading, according to the request for calling the plug-in interface, plug-in function information requested to be called, and verifying whether a plug-in is already registered in the application server, the processor is further configured to execute the application plug-in extended function system to implement the following steps:
verifying whether the plug-in interface is a legal component or not;
and if the plug-in interface is verified to be a non-legal component, sending out a warning of refusing to call the plug-in and feeding back the warning to the mobile terminal client.
Optionally, the step of loading and enabling the plug-in interface data is preceded by the step of loading and enabling the plug-in interface data
The processor is also used for executing the application plug-in extension function system to realize the following steps:
sending a starting instruction to an initialization interface of the plug-in;
receiving confirmation calling information returned by the initialization interface;
and loading and starting the data of the plug-in according to the confirmation calling information.
Optionally, the processor is further configured to execute the application plug-in extension function system to implement the following steps:
when a request for removing the plug-in sent by a mobile terminal client is received, stopping calling the plug-in interface;
and unloading the plug-in and clearing the user operation interface elements generated by the plug-in.
In addition, in order to achieve the above object, the present invention further provides a method for extending a function by an application plug-in, where the method is applied to an application server, and the method includes:
when an extended function request sent by a mobile terminal client is received, determining the function type of a plug-in to be called according to the extended function request;
sending a request for calling a plug-in interface according to the plug-in function type to be called;
verifying whether the plug-in requested to be called is registered in the application server or not according to the request for calling the plug-in interface;
and when the plug-in requested to be called is verified to be registered, loading and enabling the data of the plug-in, and generating the user operation interface element.
Optionally, before the step of sending a service invocation request to a invocation interface layer of the application server according to the type of the service request, the method further includes:
judging whether a plug-in extension function needs to be applied or not according to the type of the service request;
and if the application plug-in extension function is judged not to be needed, loading the internal data of the application server.
Optionally, the method further comprises the steps of:
defining the plug-in interface;
and when a plug-in registration request sent by the mobile terminal client is received, executing plug-in registration, and generating a plug-in information table to be mapped to the plug-in interface.
Optionally, before the step of reading the plug-in function information requested to be called according to the request for calling the plug-in interface and verifying whether the plug-in is registered in the application server, the following steps are further performed:
verifying whether the plug-in interface is a legal component or not;
if the plug-in interface is verified to be a non-legal component, sending a warning of refusing to call the plug-in and feeding back the warning to the mobile terminal client;
before the step of loading and enabling the data of the plug-in, the plug-in interface further comprises the following steps.
Sending a starting instruction to an initialization interface of the plug-in;
receiving confirmation calling information returned by the initialization interface;
and loading and starting the data of the plug-in according to the confirmation calling information.
Optionally, the method further comprises the steps of:
also comprises the following steps:
when a request for removing the plug-in sent by a mobile terminal client is received, stopping calling the plug-in interface;
and unloading the plug-in and clearing the user operation interface elements generated by the plug-in.
Further, to achieve the above object, the present invention also provides a computer readable storage medium storing an application plug-in extension function system, which is executable by at least one processor to cause the at least one processor to execute the steps of the application plug-in extension function method as described above.
Compared with the prior art, the application server, the application plug-in extended function method and the computer readable storage medium provided by the invention have the advantages that firstly, when the application server 2 receives an extended function request sent by a mobile terminal client, the function type of the plug-in to be called is determined according to the extended function request; then, the method is used for sending a request for calling a plug-in interface according to the plug-in function type called by the request; then, according to the request for calling the plug-in interface, reading the plug-in information requested to be called from the plug-in interface, and verifying whether the plug-in is registered in the application server; and finally, when the plug-in requested to be called is verified to be registered, loading and starting the data of the plug-in, and generating a user operation interface element, thereby realizing that the application plug-in expands the function of the application server 2. Therefore, the defect that the function of a system needs to be developed by a manufacturer in a customized manner when the function is expanded in the prior art can be overcome, external data can be introduced through the application plug-in, the interaction of the internal data and the external data is realized, the function of the application server is expanded, and the user experience is improved.
Drawings
FIG. 1 is a schematic diagram of an alternative application environment for various embodiments of the present invention;
FIG. 2 is a schematic diagram of an alternative hardware architecture of the application server of FIG. 1;
FIG. 3 is a schematic diagram of program modules of the first and third embodiments of the system for extended functionality of application plug-ins according to the present invention;
FIG. 4 is a schematic diagram of program modules of a second embodiment of the system for extended functionality using plug-ins according to the present invention;
FIG. 5 is a schematic diagram of program modules of a fourth embodiment of the system for extended functionality of application plug-ins according to the present invention;
FIG. 6 is a schematic diagram of program modules of a fifth embodiment of the system for extended functionality using plug-ins of the present invention;
FIG. 7 is a flowchart illustrating a first embodiment of a method for extending functionality of an application plug-in according to the present invention;
FIG. 8 is a flowchart illustrating an implementation of a second embodiment of a method for extending functionality of an application plug-in according to the present invention;
FIG. 9 is a flowchart illustrating a third embodiment of a method for extending functionality of an application plug-in according to the present invention;
FIG. 10 is a flowchart illustrating a fourth embodiment of a method for extending functionality of an application plug-in according to the present invention;
fig. 11 is a schematic flow chart illustrating an implementation of a method for extending a function by using a plug-in according to a fifth embodiment of the present invention.
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
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the description relating to "first", "second", etc. in the present invention is for descriptive purposes only and is not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In addition, technical solutions between various embodiments may be combined with each other, but must be realized by a person skilled in the art, and when the technical solutions are contradictory or cannot be realized, such a combination should not be considered to exist, and is not within the protection scope of the present invention.
Fig. 1 is a schematic diagram of an alternative application environment according to various embodiments of the present invention.
In the present embodiment, the present invention can be applied to an application environment including, but not limited to, the mobile terminal 1, the application server 2, and the network 3. Among them, the mobile terminal 1 may be a mobile device such as a mobile phone, a smart phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a navigation device, etc., and a fixed terminal such as a digital TV, a desktop computer, a notebook, a server, etc. The application server 2 may be a rack server, a blade server, a tower server, or a rack server, and the application server 2 may be an independent server or a server cluster composed of a plurality of servers. The network 3 may be a wireless or wired network such as an Intranet (Intranet), the Internet (Internet), a Global System of Mobile communication (GSM), Wideband Code Division Multiple Access (WCDMA), a 4G network, a 5G network, Bluetooth (Bluetooth), Wi-Fi, and the like.
The application server 2 is in communication connection with one or more mobile terminals 1 (only one is shown in the figure) through the network 3, and each mobile terminal 1 is installed with and runs an application client (hereinafter referred to as "mobile terminal client") corresponding to the application server 2. The mobile terminal client is used for responding to the operation of a mobile terminal user and establishing a long connection between the mobile terminal client and the application server 2, so that the mobile terminal client can perform data transmission and interaction with the application server 2 through the long connection.
In this embodiment, when the application server 2 is installed and operated with the application plug-in extension function system 200, and when the application plug-in extension function system 200 is operated, the application server 2 determines the plug-in function type requested to be called when receiving a plug-in calling request sent by a mobile terminal client, sends a plug-in interface calling request according to the plug-in function type requested to be called, reads the plug-in function information requested to be called according to the plug-in interface calling request, verifies whether a plug-in is registered in the application server, and finally when verifying that the plug-in requested to be called is registered, the plug-in interface loads and enables the data of the plug-in to realize the data interaction between the application server 2 and the plug-in, and by using the application plug-in extension function, avoids the service function being single, and relieves the operating pressure of the application server 2, the user experience is improved.
Fig. 2 is a schematic diagram of an alternative hardware architecture of the application server 2 in fig. 1. In this embodiment, the application server 2 may include, but is not limited to, a memory 11, a processor 12, and a network interface 13, which may be communicatively connected to each other through a system bus. It is noted that fig. 2 only shows the mobile terminal 1 with components 11-13, but it is to be understood that not all shown components are required to be implemented, and that more or fewer components may be implemented instead.
The memory 11 includes at least one type of readable storage medium, which includes 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, etc. In some embodiments, the storage 11 may be an internal storage unit of the application server 2, such as a hard disk or a memory of the application server 2. In other embodiments, the memory 11 may also be an external storage device of the application server 2, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like, provided on the application server 2. Of course, the memory 11 may also comprise both an internal storage unit of the application server 2 and an external storage device thereof. In this embodiment, the memory 11 is generally used for storing an operating system installed in the application server 2 and various types of application software, such as program codes of the application plug-in extended function system 200. Furthermore, the memory 11 may also be used to temporarily store various types of data that have been output or are to be output.
The processor 12 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data Processing chip in some embodiments. The processor 12 is generally configured to control the overall operation of the application server 2, such as performing control and processing related to data interaction or communication with the mobile terminal 1. In this embodiment, the processor 12 is configured to run the program code stored in the memory 11 or process data, for example, run the application plug-in extended function system 200.
The network interface 13 may comprise a wireless network interface or a wired network interface, and the network interface 13 is generally used for establishing a communication connection between the application server 2 and other electronic devices. In this embodiment, the network interface 13 is mainly used for connecting the application server 2 with one or more mobile terminals 1 through the network 3, and establishing a data transmission channel and a communication connection between the application server 2 and the one or more mobile terminals 1.
The application environment and the hardware structure and function of the related devices of the various embodiments of the present invention have been described in detail so far. Hereinafter, various embodiments of the present invention will be proposed based on the above-described application environment and related devices.
First, the present invention provides an application plug-in extension function system 200.
Fig. 3 is a program module diagram of a first embodiment of the system 200 for extending functionality by using plug-ins according to the present invention. In this embodiment, the application plug-in extended function system 200 may be divided into one or more modules, and the one or more modules are stored in the memory 11 and executed by one or more processors (in this embodiment, the processor 12) to complete the present invention. For example, in fig. 3, the application plug-in extension function system 200 may be divided into a determination module 201, a request module 202, a verification module 203, and a loading module 204. The program module referred to in the present invention refers to a series of computer program instruction segments capable of performing specific functions, and is more suitable than a program for describing the execution process of the application plug-in extended function system 200 in the application server 2. The functions of the program modules 201 and 205 will be described in detail below.
The determining module 201 is configured to determine, when receiving an extended function request sent by a mobile terminal client, a function type of a plug-in to be called according to the extended function request.
Specifically, the application server 2 includes an internal service item, and when the internal service item meets the current requirements of the client, the application server 2 provides a functional service. When the internal service cannot meet the current customer requirements, it means that the application server 2 needs to extend the functionality to load plug-ins to meet the customer's requirements. The user sends an extended function request through the mobile terminal client, and when receiving the extended function request sent by the mobile terminal client, the application server 2 analyzes the information of the extended function request through the determining module 201, and further determines the function type of the plug-in to be called. For example, when the user needs to implement the academic duration, an extended academic duration verification function request may be sent through the mobile end client, and the determining module 201 determines, according to the extended academic duration verification function request, that the plug-in which the extended request needs to be invoked at this time is authenticated by the academic duration verification plug-in.
The request module 202 is configured to send a request for invoking a plug-in interface according to the plug-in function type invoked by the request.
Specifically, the application server 2 includes a network interface layer, and the network interface layer is provided with a plurality of calling plug-in interfaces. Each calling plug-in interface comprises plug-in information, and the plug-in information comprises but is not limited to information such as function description, service type and the like of the plug-in. When the application server determines the type of the plug-in function to be called, the request module 202 sends a request for calling a plug-in interface to the plug-in interface.
The verification module 203 is configured to verify whether the plug-in requested to be invoked is already registered in the application server according to the request for invoking the plug-in interface.
As can be seen from the above, each calling plug-in interface includes plug-in function information, which includes, but is not limited to, information such as function description, service type, plug-in registry, etc. of the plug-in.
Specifically, in order to ensure information security, when the request module 202 issues a request for calling a plug-in interface, the verification module 203 reads plug-in information requested to be called from the plug-in interface according to the request for calling the plug-in interface, and verifies whether a plug-in is already registered in the application server. In this embodiment, the verification module 203 confirms that the plug-in has completed registration with the application server 2 by looking up the registry of the plug-in.
The loading module 204 is configured to load and enable data of the plug-in to generate a user operation interface element when it is verified that the plug-in requested to be invoked is registered.
Specifically, when the application server 2 already stores a plug-in registry requested to be called, that is, when the plug-in requested to be called has already been registered, the loading module 204 loads and enables data of the plug-in through the plug-in interface, and displays a user operation interface element generated by the plug-in on an interface of the mobile terminal client, thereby implementing internal and external data interaction.
Through the program module 201 and 204, the application plug-in extended function system 200 provided by the invention firstly determines the function type of the plug-in to be called according to the extended function request when the application server 2 receives the extended function request sent by the mobile terminal client; then, the method is used for sending a request for calling a plug-in interface according to the plug-in function type called by the request; then, according to the request for calling the plug-in interface, reading the plug-in information requested to be called from the plug-in interface, and verifying whether the plug-in is registered in the application server; and finally, when the plug-in requested to be called is verified to be registered, loading and starting the data of the plug-in, and generating a user operation interface element, thereby realizing that the application plug-in expands the function of the application server 2. Therefore, the defect that the function of a system needs to be developed by a manufacturer in a customized manner when the function is expanded in the prior art can be overcome, external data can be introduced through the application plug-in, the interaction of the internal data and the external data is realized, the function of the application server is expanded, and the user experience is improved.
Further, a second embodiment of the present invention (as shown in fig. 4) is proposed based on the above-described first embodiment of the application plug-in extension function system 200 of the present invention. In this embodiment, the system 200 further includes a definition module 205 and a registration module 206.
As can be seen from the above, in the first embodiment, the application server 2 loads and enables the data of the plug-in through the plug-in interface, and in order to ensure information security, the application server 2 also verifies whether the plug-in requested to be invoked has completed registration before loading and enabling the data of the plug-in.
Therefore, in this embodiment, the defining module 205 is configured to define the plug-in interface at the network interface layer of the application server 2.
Specifically, when a certain function is extended, the application server 2 needs to perform information interaction with a plug-in having the function, and the information interaction needs to call a corresponding plug-in through a preset plug-in interface. And calling the plug-in by setting a plug-in port at a system network interface layer so as to reference the plug-in function service and data. In this embodiment, a plurality of plug-in interfaces may be provided, and each plug-in interface mainly includes a plug-in initialization interface, a plug-in release interface, and an information callback interface.
The registration module 206 is configured to execute plug-in registration when receiving a plug-in registration request sent by the mobile terminal client, and generate a plug-in information table to be mapped to the plug-in interface.
Specifically, the developer generates a registration request of a corresponding plug-in according to the service function requirement, and sends the plug-in registration request to the registration module 206 through the mobile terminal client. When receiving a plug-in registration request sent by a mobile terminal client, the registration module 206 executes plug-in registration, generates a plug-in information table and maps the plug-in information table to the plug-in interface, so that the plug-in information can be read from the plug-in interface. Each calling function of the plug-in which the registration is successful can dynamically generate an operation interface (such as a toolbar button, a menu item and the like). The plug-in registration file comprises plug-in function description, a plug-in calling entry and the like. In the present embodiment, the plug-in expresses plug-in information using XML language. For example, a plug-in is verified with a reference calendar, and the function of the plug-in information is described as: verifying whether the person is the true highest school calendar or not; the risk degree prompts the plug-in, and the function description of the plug-in information is as follows: the risk of fraud present is assessed.
In other embodiments of the present invention, the application server 2 can further determine whether the function description information and the plug-in interface are legal, if so, the registration is confirmed to be successful, and if not, the system rejects the registration. The judgment of legality can be based on whether the function description information is required, whether the address and format of the plug-in interface conform to the relevant protocol, and the like.
Through the program module 205 and 206, the application plug-in extension function system 200 provided by the invention can define a plug-in interface, execute plug-in registration when receiving a plug-in registration request sent by a mobile terminal client, generate a plug-in information table and map the plug-in information table to the plug-in interface, so that the plug-in information can be read from the plug-in interface, the plug-in can be flexibly and conveniently called, and the user experience is improved.
Further, a third embodiment of the present invention (as shown in fig. 3) is proposed based on the above-mentioned first and second embodiments of the application plug-in extension function system 200 of the present invention. In this embodiment, the verification module 203 is further configured to:
verifying whether the plug-in interface is a legal component or not; and
and if the plug-in interface is verified to be a non-legal component, sending out a warning of refusing to call the plug-in and feeding back the warning to the mobile terminal client.
As can be seen from the above, in the second embodiment, the network interface layer of the application server 2 defines a plurality of plug-in interfaces. In actual practice, however, the properties of the plug-in interface may be modified. Therefore, in this embodiment, in order to confirm that the plug-in interface is not tampered with, thereby ensuring the security of the plug-in interface, when the application server 2 receives the request for calling the plug-in interface, the verification module 203 further authenticates whether the plug-in interface is a legitimate component, that is, verifies that the plug-in interface is not tampered with. If the plug-in interface is verified to be a non-legal component, the verification module 203 sends out a warning for refusing to call the plug-in and feeds the warning back to the mobile terminal client.
In other embodiments of the invention, the verification module 203 may verify another plug-in interface.
Through the program module 203, the application plug-in extension function system 200 provided by the invention can also verify whether the plug-in interface is a legal component; and if the plug-in interface is verified to be a non-legal component, sending out information of refusing to call the plug-in and feeding back the information to the mobile terminal client, thereby ensuring the safety of the plug-in interface.
Further, a fourth embodiment of the present invention (as shown in fig. 5) is proposed based on the above-mentioned first and second embodiments of the application plug-in extension function system 200 of the present invention. In this embodiment, the system 200 further includes a sending module 207 and a receiving module 208, wherein the sending module and the receiving module are connected to each other
The sending module 207 is configured to send a start instruction to the plug-in initialization interface;
the receiving module 208 is configured to receive confirmation call information returned by the call entry;
the loading module 204 is further configured to load and enable data of the plug-in according to the confirmation call information.
Specifically, as can be seen from the above, in the first and second embodiments, the application server 2 loads and enables the data of the plug-in called by the request through the plug-in interface when verifying that the plug-in is registered. And each plug-in interface mainly comprises a plug-in initialization interface, a plug-in release interface and an information callback interface. In this embodiment, before loading the data of the plug-in, the sending module 207 sends an instruction for starting the plug-in to the plug-in initialization interface, and generates a confirmation call message after the plug-in initialization interface completes initialization. The receiving module 208 receives the confirmation call information returned by the initialization interface. The loading module 204 further loads and enables the data of the plug-in according to the confirmation call information, completes the referencing of the plug-in, and expands the functions of the application server 2.
Through the program module 207 and 208, the application plug-in extension function system 200 provided by the invention can also send a start instruction to the plug-in initialization interface, receive the confirmation call information returned by the call entry, and further load and enable the data of the plug-in according to the confirmation call information. The application server 2 is simple and flexible in the way of applying the plug-in extension function.
Further, based on the above-described first embodiment of the application plug-in extension function system 200 of the present invention, a fifth embodiment of the present invention (as shown in fig. 6) is proposed. In this embodiment, the application plug-in extension function system 200 further includes an uninstall module 209.
The unloading module 209 is configured to stop calling the plug-in interface when receiving a request for removing the plug-in sent by a mobile terminal client; and
and unloading the plug-in and clearing the user operation interface elements generated by the plug-in.
Specifically, when the user finishes executing the plug-in, a request for removing the plug-in can be sent through the mobile terminal client. When the uninstalling module 209 receives a request for removing the plug-in sent by the mobile terminal client, the call to the plug-in interface is stopped, and the plug-in is uninstalled at the same time. The uninstall module 209 also makes clear the ui elements of the plug-in, and relieves the operating stress of the application server 2.
Through the program module 209, the application plug-in extension function system 200 provided by the present invention can also stop the call of the plug-in interface when receiving a request for removing the plug-in sent by the mobile terminal client; and simultaneously unloading the plug-in and clearing the user operation interface elements generated by the plug-in, thereby relieving the operating pressure of the application server 2 and improving the user experience.
In addition, the invention also provides a method for extending the function of the application plug-in.
Fig. 7 is a schematic flow chart showing an implementation of the method for extending functions of an application plug-in according to the first embodiment of the present invention. In this embodiment, the execution order of the steps in the flowchart shown in fig. 7 may be changed and some steps may be omitted according to different requirements.
Step S301, when an extended function request sent by a mobile terminal client is received, determining the function type of the plug-in to be called according to the extended function request.
Specifically, the application server 2 includes an internal service item, and when the internal service item meets the current requirements of the client, the application server 2 provides a functional service. When the internal service cannot meet the current customer requirements, it means that the application server 2 needs to extend the functionality to load plug-ins to meet the customer's requirements. The user sends an extended function request through the mobile terminal client, and the application server 2 determines the function type of the plug-in to be called by analyzing the information of the extended function request when receiving the extended function request sent by the mobile terminal client. For example, when the user needs to implement the verification duration, the mobile end client sends an extended academic history verification function request, and the application server 2 authenticates the academic history verification plug-in when determining the plug-in which the extended request needs to be called according to the extended academic history verification function request.
Step S302, according to the plug-in function type called by the request, sending out a request for calling a plug-in interface.
Specifically, the application server 2 includes a network interface layer, and the network interface layer is provided with a plurality of calling plug-in interfaces. Each calling plug-in interface comprises plug-in information, and the plug-in information comprises but is not limited to information such as function description, service type and the like of the plug-in. And when the application server 2 determines the plug-in function type needing to be called, sending a request for calling the plug-in interface to the plug-in interface.
Step S303, according to the request for calling the plug-in interface, verifying whether the plug-in requested to be called is registered in the application server.
As can be seen from the above, each calling plug-in interface includes plug-in function information, which includes, but is not limited to, information such as function description, service type, plug-in registry, etc. of the plug-in.
Specifically, in order to ensure information security, the application server 2 reads the plug-in information requested to be called from the plug-in interface according to the request for calling the plug-in interface, and verifies whether the plug-in is already registered in the application server. In this embodiment, it is confirmed that the plug-in has completed registration in the application server 2 by looking up the registry of the plug-in.
Step S304, when the plug-in requested to be called is verified to be registered, loading and enabling the data of the plug-in, and generating a user operation interface element.
Specifically, when the application server 2 has stored the plug-in registry requested for calling, that is, when the plug-in requested for calling has completed registration, the data of the plug-in is loaded and enabled through the plug-in interface, and the user operation interface element generated by the plug-in is displayed on the interface of the mobile terminal client, so as to implement internal and external data interaction.
Through the steps S301-305, the method for extending the function of the application plug-in provided by the present invention, first, when the application server 2 receives an extended function request sent by the mobile terminal client, determines the function type of the plug-in to be called according to the extended function request; then, the method is used for sending a request for calling a plug-in interface according to the plug-in function type called by the request; then, according to the request for calling the plug-in interface, reading the plug-in information requested to be called from the plug-in interface, and verifying whether the plug-in is registered in the application server; and finally, when the plug-in requested to be called is verified to be registered, loading and starting the data of the plug-in, and generating a user operation interface element, thereby realizing that the application plug-in expands the function of the application server 2. Therefore, the defect that the function of a system needs to be developed by a manufacturer in a customized manner when the function is expanded in the prior art can be overcome, external data can be introduced through the application plug-in, the interaction of the internal data and the external data is realized, the function of the application server is expanded, and the user experience is improved.
Further, based on the above first embodiment of the method for extending a function by using a plug-in of the present invention, a second embodiment of the method for extending a function by using a plug-in of the present invention is provided.
As can be seen from the above, in the first embodiment, the application server 2 loads and enables the data of the plug-in through the plug-in interface, and in order to ensure information security, the application server 2 also verifies whether the plug-in requested to be invoked has completed registration before loading and enabling the data of the plug-in.
Fig. 8 is a schematic flow chart illustrating an implementation of the method for extending a function by using a plug-in according to the second embodiment of the present invention. In this embodiment, the method includes:
step S401, defining a plug-in interface.
Specifically, when a certain function is extended, the application server 2 needs to perform information interaction with a plug-in having the function, and the information interaction needs to call a corresponding plug-in through a preset plug-in interface. And calling the plug-in by setting a plug-in port at a system network interface layer so as to reference the plug-in function service and data. In this embodiment, a plurality of plug-in interfaces may be provided, and each plug-in interface mainly includes a plug-in initialization interface, a plug-in release interface, and an information callback interface.
Step S402, when a plug-in registration request sent by the mobile terminal client is received, executing plug-in registration, generating a plug-in information table and mapping the plug-in information table to the plug-in interface.
Specifically, the developer generates a registration request of a corresponding plug-in according to the service function requirement, and sends the plug-in registration request to the registration module 206 through the mobile terminal client. When receiving a plug-in registration request sent by a mobile terminal client, the registration module 206 executes plug-in registration, generates a plug-in information table and maps the plug-in information table to the plug-in interface, so that the plug-in information can be read from the plug-in interface. Each calling function of the plug-in which the registration is successful can dynamically generate an operation interface (such as a toolbar button, a menu item and the like). The plug-in registration file comprises plug-in function description, a plug-in calling entry and the like. In the present embodiment, the plug-in expresses plug-in information using XML language. For example, a plug-in is verified with a reference calendar, and the function of the plug-in information is described as: verifying whether the person is the true highest school calendar or not; the risk degree prompts the plug-in, and the function description of the plug-in information is as follows: the risk of fraud present is assessed.
In other embodiments of the present invention, the application server 2 can further determine whether the function description information and the plug-in interface are legal, if so, the registration is confirmed to be successful, and if not, the system rejects the registration. The judgment of legality can be based on whether the function description information is required, whether the address and format of the plug-in interface conform to the relevant protocol, and the like.
Through the steps S401-S402, the method for extending the function of the application plug-in can define the plug-in interface, execute plug-in registration when receiving a plug-in registration request sent by a mobile terminal client, generate a plug-in information table and map the plug-in information table to the plug-in interface, so that the plug-in information can be read from the plug-in interface, the plug-in can be flexibly and conveniently called, and the user experience is improved.
Further, based on the first and second embodiments of the method for extending a function by using a plug-in of the present invention, a third embodiment of the method for extending a function by using a plug-in of the present invention is provided.
Fig. 9 is a schematic flow chart illustrating an implementation of the method for extending a function by using a plug-in according to the third embodiment of the present invention. In this embodiment, the method further includes:
step S501, when an extended function request sent by a mobile terminal client is received, determining the function type of the plug-in to be called according to the extended function request.
Step S502, according to the plug-in function type called by the request, sending out a request for calling a plug-in interface.
Step S503, verifying whether the plug-in interface is a legal component, if the plug-in interface is verified to be a non-legal component, executing step S504, and if the plug-in interface is verified to be a legal component, executing step S505.
And step S504, sending out a warning of refusing to call the plug-in and feeding back the warning to the mobile terminal client.
As can be seen from the above, in the second embodiment, the network interface layer of the application server 2 defines a plurality of plug-in interfaces. In actual practice, however, the properties of the plug-in interface may be modified. Therefore, in this embodiment, in order to confirm that the plugin interface is not tampered with, thereby ensuring the security of the plugin interface, the application server 2, upon receiving the request for invoking the plugin interface, further authenticates whether the plugin interface is a legitimate component, i.e., verifies that the plugin interface is not tampered with. And if the plug-in interface is verified to be a non-legal component, sending out a warning of refusing to call the plug-in and feeding back the warning to the mobile terminal client.
In other embodiments of the invention, the verification module 203 may verify another plug-in interface.
Step S505, verifying whether the plug-in requested to be called is registered in the application server according to the request for calling the plug-in interface.
Step S506, when the plug-in requested to be called is verified to be registered, loading and enabling the data of the plug-in, and generating the user operation interface element.
Through the steps S501-S505, the method for extending the function by using the plug-in provided by the invention can also verify whether the plug-in interface is a legal component; and if the plug-in interface is verified to be a non-legal component, sending out information of refusing to call the plug-in and feeding back the information to the mobile terminal client, thereby ensuring the safety of the plug-in interface.
Further, based on the above first embodiment of the method for extending a function by using a plug-in of the present invention, a fourth embodiment of the method for extending a function by using a plug-in of the present invention is proposed.
Fig. 10 is a schematic flow chart illustrating an implementation of the fourth embodiment of the method for extending functionality of an application plug-in according to the present invention. In this embodiment, the method further includes:
step S601, sending a start instruction to the plugin initialization interface.
Step S602, receiving the confirmation call information returned by the call entry.
Step S603, loading and enabling the data of the plug-in according to the confirmation call information.
Specifically, as can be seen from the above, in the first and second embodiments, the application server 2 loads and enables the data of the plug-in called by the request through the plug-in interface when verifying that the plug-in is registered. And each plug-in interface mainly comprises a plug-in initialization interface, a plug-in release interface and an information callback interface. In this embodiment, before loading the data of the plug-in, an instruction for starting the plug-in is sent to the plug-in initialization interface, and when the plug-in initialization interface completes initialization, a confirmation call message is generated. And the application server 2 receives the confirmation calling information returned by the initialization interface, loads and starts the data of the plug-in according to the confirmation calling information, completes the reference of the plug-in and expands the functions of the application server 2.
Through the steps S601-602, the method for extending a function of an application plug-in provided by the present invention can send a start instruction to a plug-in initialization interface, receive the confirmation call information returned by the call entry, and further load and enable the data of the plug-in according to the confirmation call information. The application server 2 is simple and flexible in the way of applying the plug-in extension function.
Further, a fifth embodiment of the method for extending a function by using a plug-in according to the present invention is provided based on the first and fourth embodiments of the method for extending a function by using a plug-in according to the present invention.
Fig. 11 is a schematic flow chart illustrating an implementation of the method for extending functionality of an application plug-in according to the fifth embodiment of the present invention. In this embodiment, the method further includes:
and step S701, when a request for removing the plug-in sent by the client of the mobile terminal is received, stopping calling the plug-in interface.
And S702, unloading the plug-in and clearing the user operation interface elements generated by the plug-in.
Specifically, when the user finishes executing the plug-in, a request for removing the plug-in can be sent through the mobile terminal client. When the application server 2 receives a request for removing the plug-in sent by a mobile terminal client, the calling of the plug-in interface is stopped, the plug-in is unloaded through the plug-in release interface, the user operation interface elements of the plug-in are also clear, and the operating pressure of the application server 2 is relieved.
Through the steps S701-702, the application plug-in extension function method provided by the invention can stop calling the plug-in interface when receiving a request for removing the plug-in sent by a mobile terminal client; and simultaneously unloading the plug-in and clearing the user operation interface elements generated by the plug-in, thereby relieving the operating pressure of the application server 2 and improving the user experience.
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 (9)
1. An application server, comprising a memory, a processor, and an application plug-in extended function system stored on the memory and operable on the processor, wherein the application plug-in extended function system when executed by the processor implements the steps of:
when an extended function request sent by a mobile terminal client is received, determining the function type of a plug-in to be called according to the extended function request;
sending a request for calling a plug-in interface according to the plug-in function type to be called, wherein the plug-in interface comprises plug-in information, and the plug-in information comprises function description of a plug-in;
verifying whether the plug-in requested to be called is registered in the application server or not according to the request for calling the plug-in interface;
when the plug-in requested to be called is verified to be registered, loading and starting the data of the plug-in, and generating a user operation interface element;
before verifying whether the plug-in requested to be called is registered in the application server according to the request for calling the plug-in interface, the processor is further used for executing the application plug-in extended function system to realize the following steps:
verifying whether the plug-in interface is a legal component or not;
and if the plug-in interface is verified to be a non-legal component, sending out a warning of refusing to call the plug-in and feeding back the warning to the mobile terminal client.
2. The application server of claim 1, wherein the processor is further configured to execute the application plug-in extension function system to implement the steps further comprising:
defining the plug-in interface;
and when a plug-in registration request sent by the mobile terminal client is received, executing plug-in registration, and generating a plug-in information table to be mapped to the plug-in interface.
3. The application server of claim 1, wherein prior to the step of the plug-in interface loading and enabling data of the plug-in, the processor is further configured to execute the application plug-in extension function system to perform the steps of:
sending a starting instruction to an initialization interface of the plug-in;
receiving confirmation calling information returned by the initialization interface;
and loading and starting the data of the plug-in according to the confirmation calling information.
4. The application server of any of claims 1-3, wherein the processor is further configured to execute the application plug-in extension function system to perform the steps of:
when a request for removing the plug-in sent by a mobile terminal client is received, stopping calling the plug-in interface;
and unloading the plug-in and clearing the user operation interface elements generated by the plug-in.
5. An application plug-in extension function method applied to an application server is characterized by comprising the following steps:
when an extended function request sent by a mobile terminal client is received, determining the function type of a plug-in to be called according to the extended function request;
sending a request for calling a plug-in interface according to the plug-in function type to be called, wherein the plug-in interface comprises plug-in information, and the plug-in information comprises function description of a plug-in;
verifying whether the plug-in requested to be called is registered in the application server or not according to the request for calling the plug-in interface;
when the plug-in requested to be called is verified to be registered, loading and starting the data of the plug-in, and generating a user operation interface element;
before the step of verifying whether the plug-in requested to be called is registered with the application server according to the request of calling the plug-in interface, the method further comprises the following steps:
verifying whether the plug-in interface is a legal component or not;
and if the plug-in interface is verified to be a non-legal component, sending out a warning of refusing to call the plug-in and feeding back the warning to the mobile terminal client.
6. The method of claim 5, wherein the method further comprises the steps of:
defining the plug-in interface;
and when a plug-in registration request sent by the mobile terminal client is received, executing plug-in registration, and generating a plug-in information table to be mapped to the plug-in interface.
7. The method for extending functionality of an application plug-in as claimed in claim 6, wherein the step of loading and enabling the data of the plug-in by the plug-in interface is preceded by the steps of:
sending a starting instruction to an initialization interface of the plug-in;
receiving confirmation calling information returned by the initialization interface;
and loading and starting the data of the plug-in according to the confirmation calling information.
8. The method for extending functions of an application plug-in according to any one of claims 5 to 7, further comprising the steps of:
when a request for removing the plug-in sent by a mobile terminal client is received, stopping calling the plug-in interface;
and unloading the plug-in and clearing the user operation interface elements generated by the plug-in.
9. A computer-readable storage medium storing an application plug-in extended functionality system executable by at least one processor to cause the at least one processor to perform the steps of the application plug-in extended functionality method of any one of claims 5-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710658116.8A CN107911401B (en) | 2017-08-04 | 2017-08-04 | Application plug-in extension function method and application server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710658116.8A CN107911401B (en) | 2017-08-04 | 2017-08-04 | Application plug-in extension function method and application server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107911401A CN107911401A (en) | 2018-04-13 |
| CN107911401B true CN107911401B (en) | 2021-11-26 |
Family
ID=61840009
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710658116.8A Active CN107911401B (en) | 2017-08-04 | 2017-08-04 | Application plug-in extension function method and application server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107911401B (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109960505B (en) * | 2019-03-28 | 2022-11-25 | 江苏满运软件科技有限公司 | User interface component plug-in method, system, equipment and storage medium |
| CN110297671A (en) * | 2019-05-22 | 2019-10-01 | 深圳壹账通智能科技有限公司 | Client plug-in implementation method, device, computer equipment and storage medium |
| CN110445791B (en) * | 2019-08-12 | 2021-07-27 | 北京顺丰同城科技有限公司 | Plug-in authentication method and device, and plug-in authentication information storage method and device |
| CN110764836B (en) | 2019-09-18 | 2024-02-09 | 华为技术有限公司 | Plug-in implementation method and plug-in implementation system |
| CN110704035A (en) * | 2019-10-17 | 2020-01-17 | 北京首贝科技发展有限公司 | Plug-in type software architecture system and implementation method thereof |
| CN113448653B (en) * | 2020-03-27 | 2024-01-26 | 北京猎户星空科技有限公司 | Service processing method, system, electronic equipment and computer readable medium |
| CN113391852A (en) * | 2021-06-07 | 2021-09-14 | 广州通达汽车电气股份有限公司 | Platform software extension method and device |
| CN113485769B (en) * | 2021-07-23 | 2024-05-14 | 统信软件技术有限公司 | Application program running method, computing device and storage medium |
| CN115328375A (en) * | 2022-06-30 | 2022-11-11 | 深圳市国电科技通信有限公司 | Function expansion method and device for intelligent measurement terminal and intelligent terminal |
| CN117422288A (en) * | 2023-11-07 | 2024-01-19 | 广州市玄武无线科技股份有限公司 | Visiting flow accurate matching templatization and plugin method |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101042718A (en) * | 2006-03-21 | 2007-09-26 | 北京汉辰科技有限公司 | Network hand-hold multimedia terminals with security authentication and implementing method thereof |
| CN101119335A (en) * | 2007-07-13 | 2008-02-06 | 腾讯科技（深圳）有限公司 | Method for logging in game server and implementing system thereof |
| CN102149090A (en) * | 2011-03-28 | 2011-08-10 | 苏州汉辰数字多媒体有限公司 | Security certification method for accessing extended function module into network mobile terminal |
| CN105260177A (en) * | 2015-09-21 | 2016-01-20 | 广东大工数值仿真研究院有限公司 | SiPESC platform based Python extension module development method |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TW201110022A (en) * | 2009-09-15 | 2011-03-16 | Inventec Corp | Plug-in downloading system for expanding functions of software and method thereof |
| US10146566B2 (en) * | 2009-12-21 | 2018-12-04 | Microsoft Technology Licensing, Llc | Enabling virtual desktop connections to remote clients |
| CN103023976B (en) * | 2012-11-19 | 2016-08-03 | 北京奇虎科技有限公司 | A kind of apparatus and method of browser application plug-in extension |
| CN103036871B (en) * | 2012-11-19 | 2017-04-19 | 北京奇虎科技有限公司 | Support device and method of application plug-in of browser |
| CN103645919A (en) * | 2013-12-18 | 2014-03-19 | 用友软件股份有限公司 | Method for extending functions of management information system through plugins |
| CN104954462A (en) * | 2015-06-12 | 2015-09-30 | 福建新大陆通信科技股份有限公司 | High-concurrency extensible smart home communication method and high-concurrency extensible smart home communication system |
| CN106155739A (en) * | 2016-06-30 | 2016-11-23 | 北京奇虎科技有限公司 | A kind of plug-in unit control metering method, server, client and control amount platform |
-
2017
- 2017-08-04 CN CN201710658116.8A patent/CN107911401B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101042718A (en) * | 2006-03-21 | 2007-09-26 | 北京汉辰科技有限公司 | Network hand-hold multimedia terminals with security authentication and implementing method thereof |
| CN101119335A (en) * | 2007-07-13 | 2008-02-06 | 腾讯科技（深圳）有限公司 | Method for logging in game server and implementing system thereof |
| CN102149090A (en) * | 2011-03-28 | 2011-08-10 | 苏州汉辰数字多媒体有限公司 | Security certification method for accessing extended function module into network mobile terminal |
| CN105260177A (en) * | 2015-09-21 | 2016-01-20 | 广东大工数值仿真研究院有限公司 | SiPESC platform based Python extension module development method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107911401A (en) | 2018-04-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107911401B (en) | Application plug-in extension function method and application server | |
| CN108520454B (en) | Method and system for calling back orders in real time | |
| CN108462760B (en) | Electronic device, automatic cluster access domain name generation method and storage medium | |
| CN107920112B (en) | Configuration file pushing method supporting gray mode, central server and storage medium | |
| CN108388599B (en) | Electronic device, data migration and calling method and storage medium | |
| CN110633160A (en) | Interface calling method and device, computer equipment and storage medium | |
| CN110018765B (en) | Page display method, device, terminal and storage medium | |
| CN112039896B (en) | Data processing method, equipment, server and storage medium | |
| EP3584732B1 (en) | Application management method for terminal, application server and terminal | |
| CN110007936B (en) | Data processing method and device | |
| CN109257426B (en) | Service line resource loading method and device, computer equipment and storage medium | |
| CN110851151B (en) | Method, device, terminal, server and storage medium for pre-installing application | |
| CN112818270B (en) | Data cross-domain transfer method and device and computer equipment | |
| CN107491316B (en) | Expansion method and device of baseboard management controller and electronic equipment | |
| CN106569851B (en) | Application program processing method and device | |
| CN112416384A (en) | Software upgrading method and device and computer equipment | |
| CN114710297B (en) | Block chain evidence storing method, device and equipment based on aggregated signature and storage medium | |
| JP2002169621A (en) | Program download system, terminal device, program download method and storage medium | |
| US20240031166A1 (en) | Web-side data signature method and apparatus and computer device | |
| CN113360172B (en) | Application deployment method, device, computer equipment and storage medium | |
| CN113742110A (en) | Message transmission method and device, electronic equipment and storage medium | |
| CN109828752B (en) | Project code automatic generation method, device, computer equipment and storage medium | |
| CN108243180B (en) | Bank policy data docking method and policy data server | |
| CN107315951B (en) | Program installation package anti-interception method and device | |
| CN111654398A (en) | Configuration updating method and device, computer equipment and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20180608 Address after: 518000 Room 201, building A, No. 1, Qian Wan Road, Qianhai Shenzhen Hong Kong cooperation zone, Shenzhen, Guangdong (Shenzhen Qianhai business secretary Co., Ltd.) Applicant after: Shenzhen one ledger Intelligent Technology Co., Ltd. Address before: 200030 Xuhui District, Shanghai Kai Bin Road 166, 9, 10 level. Applicant before: Shanghai Financial Technologies Ltd |
|
| TA01 | Transfer of patent application right | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |