CN111200648B - Service calling method, device, terminal equipment and storage medium - Google Patents

Service calling method, device, terminal equipment and storage medium Download PDF

Info

Publication number
CN111200648B
CN111200648B CN201911400757.9A CN201911400757A CN111200648B CN 111200648 B CN111200648 B CN 111200648B CN 201911400757 A CN201911400757 A CN 201911400757A CN 111200648 B CN111200648 B CN 111200648B
Authority
CN
China
Prior art keywords
service
module
target
party
function
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
Application number
CN201911400757.9A
Other languages
Chinese (zh)
Other versions
CN111200648A (en
Inventor
潘显跃
钱杰
沈云峰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ruiting Network Technology Shanghai Co ltd
Original Assignee
Ruiting Network Technology Shanghai Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Ruiting Network Technology Shanghai Co ltd filed Critical Ruiting Network Technology Shanghai Co ltd
Priority to CN201911400757.9A priority Critical patent/CN111200648B/en
Publication of CN111200648A publication Critical patent/CN111200648A/en
Application granted granted Critical
Publication of CN111200648B publication Critical patent/CN111200648B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/60Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Abstract

The application provides a service calling method, a service calling device, terminal equipment and a storage medium. The method comprises the following steps: receiving a service calling request sent by a first service party; determining a target service module to be called by the first service party according to the service calling request; acquiring a target service function corresponding to the target service module which is registered on the service platform in advance; and providing the target service module and the target service function to the first service party. According to the method and the system, the service functions corresponding to the service modules are registered on the service platform in advance, the service modules registered on the service platform and the service functions corresponding to the service modules are externally disclosed, a service party can be directly called, UI components do not need to be repeatedly developed on the service party, the occurrence of repeated functions is reduced, the problem that the experience in the service is not uniform is solved, and the investment of labor cost is reduced.

Description

Service calling method, device, terminal equipment and storage medium
Technical Field
The present application relates to the field of cross-service communication technologies, and in particular, to a service invoking method, an apparatus, a terminal device, and a storage medium.
Background
In a conventional research and development process, a research and development service is usually split into a plurality of service modules, and different groups of research and development personnel respectively develop the corresponding service modules and finally combine the service modules into a complete research and development service.
In the development process, the service modules generally need to interact with each other to obtain corresponding data and implement integrity of the service, in the prior art, different service data are generally loaded through a universal UI (User Interface Design) component to implement access between the service modules, and in this way, each UI component only corresponds to one type of service data and cannot meet service differences. In the prior art, a repeated wheel-making mode is adopted, UI styles are developed by isolating data in each service module in a user-defined mode, UI components are developed by isolating data in each service module in a user-defined mode, and data interaction is performed, so that although business differences can be supported, repeated functions occur, experience in each service is not uniform, and labor cost is increased due to repeated development of the UI components and data interaction.
Disclosure of Invention
The embodiment of the application provides a service calling method and device, terminal equipment and a storage medium, and aims to solve the problems that in the prior art, repeated functions can occur due to a repeated wheel manufacturing mode, experience in each service is not uniform, and labor cost is increased due to repeated UI component development and data interaction.
In order to solve the above technical problem, the embodiment of the present application is implemented as follows:
in a first aspect, an embodiment of the present application provides a service invoking method, which is applied to a service platform, and includes:
receiving a service calling request sent by a first service party;
determining a target service module to be called by the first service party according to the service calling request;
acquiring a target service function corresponding to the target service module which is registered on the service platform in advance;
and providing the target service module and the target service function to the first service party.
Optionally, before the receiving the service invocation request sent by the first service party, the method further includes:
acquiring registration requests aiming at a plurality of service modules, which are sent by a second service party; the target business module is a business module in the plurality of business modules;
acquiring a service function to be registered corresponding to each service module according to the registration request;
formulating a network data exchange protocol corresponding to each service function to be registered;
and storing each service module and the network data exchange protocol corresponding to each service module.
Optionally, the acquiring a target service function corresponding to the target service module pre-registered on the service platform includes:
acquiring a target network data exchange protocol corresponding to the target service module;
and acquiring a target service function corresponding to the target service module based on the target network data exchange protocol.
Optionally, after the providing the target service module and the target service function to the first service party, further includes:
when the calling frequency of the target service module is less than or equal to a preset frequency threshold, releasing the target service module from the service platform;
and when the calling frequency of the target service module is greater than the preset frequency threshold and a warning message of insufficient memory is received, releasing the target service module from the service platform.
In a second aspect, an embodiment of the present application provides a service invoking device, which is applied to a service platform, and includes:
the service calling request receiving module is used for receiving a service calling request sent by a first service party;
the target service module determining module is used for determining a target service module required to be called by the first service party according to the service calling request;
a target service function acquiring module, configured to acquire a target service function corresponding to the target service module that is pre-registered on the service platform;
and the target service function providing module is used for providing the target service module and the target service function to the first service party.
Optionally, the apparatus further comprises:
the registration request acquisition module is used for acquiring registration requests aiming at the plurality of service modules and sent by a second service party; the target business module is a business module in the plurality of business modules;
a function to be registered acquisition module, configured to acquire a service function to be registered corresponding to each service module according to the registration request;
the exchange protocol specifying module is used for specifying a network data exchange protocol corresponding to each service function to be registered;
and the exchange protocol storage module is used for storing each service module and the network data exchange protocol corresponding to each service module.
Optionally, the target service function obtaining module includes:
the data exchange protocol acquisition submodule is used for acquiring a target network data exchange protocol corresponding to the target service module;
and the target service function acquisition submodule is used for acquiring a target service function corresponding to the target service module based on the target network data exchange protocol.
Optionally, the method further comprises:
the first service module releasing module is used for releasing the target service module from the service platform when the calling frequency of the target service module is less than or equal to a preset frequency threshold;
and the second service module release module is used for releasing the target service module from the service platform when the calling frequency of the target service module is greater than the preset frequency threshold and a warning message of insufficient memory is received.
In a third aspect, an embodiment of the present application provides a terminal device, including: a memory, a processor and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing a service invocation method as previously described.
In a fourth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the service invocation method as described above.
In the embodiment of the application, a service calling request sent by a first service party is received, a target service module required to be called by the first service party is determined according to the service calling request, a target service function corresponding to the target service module which is registered on a service platform in advance is obtained, and the target service module and the target service function are provided for the first service party. According to the embodiment of the application, the service functions corresponding to the service modules are registered on the service platform in advance, the service modules registered on the service platform and the service functions corresponding to the service modules are externally disclosed, a service party can directly call the service modules, UI components do not need to be repeatedly developed on the service party, the occurrence of repeated functions is reduced, the problem that experience in the service is not uniform is solved, and the investment of labor cost is reduced.
The foregoing description is only an overview of the technical solutions of the present application, and the present application can be implemented according to the content of the description in order to make the technical means of the present application more clearly understood, and the following detailed description of the present application is given in order to make the above and other objects, features, and advantages of the present application more clearly understandable.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments of the present application will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a flowchart illustrating steps of a service invocation method according to an embodiment of the present application;
fig. 2 is a flowchart illustrating steps of another service invocation method according to an embodiment of the present application;
fig. 3 is a schematic diagram of service module registration and invocation provided in an embodiment of the present application;
fig. 4 is a schematic structural diagram of a service invoking device according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of another service invocation device provided in the embodiment of the present application;
fig. 6 is a schematic diagram of a hardware structure of a terminal device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. 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 application.
Example one
Referring to fig. 1, a flowchart illustrating steps of a service invocation method provided in an embodiment of the present application is shown. As shown in fig. 1, the service invoking method may be applied to a service platform, and specifically may include the following steps:
step 101: and receiving a service calling request sent by a first service party.
The embodiment of the application can be applied to registering the service module developed by the service party on the service platform, the service party provides one or more functions of the service module, the functions of the service module and the service module registered on the service platform are open to the outside, and other service parties can directly call the service module to realize cross-service calling of the service module.
The service platform is a platform for a service party to register a service module, and the service platform can store service modules respectively provided by one or more service parties, for example, in a house service, the service modules are divided into service modules such as a new house, a second-hand house, a rented house, a broker, a cell, information and the like, and the service party can provide a certain function of one or more service modules in the service modules and register the service modules on the service platform to provide for other service parties to call.
The first service party refers to a party calling the required service module from the service platform. The first service party is a terminal used by research and development personnel, and in the application, the first service party may be a mobile terminal, such as a mobile phone, a PAD (Portable Android Device, tablet computer), and other mobile electronic devices. The first service party may also be a PC (Personal Computer) end, such as an electronic device like a desktop Computer or a notebook Computer. Specifically, the method may be determined according to business requirements, and the embodiment of the present application is not limited thereto.
In this application, the first service party may be a service party that has registered a service module on the service platform, or may also be a service party that has not registered a service module on the service platform, and specifically, may be determined according to a service requirement, which is not limited in this embodiment of the application.
The service calling request refers to a request sent by a first service party for calling a required service module, the service modules registered on the service platform are all open to the outside, the service party can view the service modules registered on the service platform, and when the service party needs to call a certain service module, the service calling request can be generated by combining the service modules required to be called, and the service calling request is sent to the service platform, for example, a module identifier, such as module identifier 1, module identifier 2 and module identifier 3, can be allocated to each service module on the service platform, and when the first service party needs to acquire the service module corresponding to module identifier 2, the first service party can generate a corresponding service calling request by combining module identifier 2, and the like.
It should be understood that the above examples are only examples for better understanding of the technical solutions of the embodiments of the present application, and are not to be taken as the only limitation of the embodiments of the present application.
After receiving the service invocation request from the first service party, step 102 is performed.
Step 102: and determining a target service module required to be called by the first service party according to the service calling request.
The target service module refers to a service module that the first service party needs to call, for example, a service module registered on the service platform includes: the first service party calls the service module a according to the service calling request, and then the service module a is used as a target service module; and when the service modules required to be called by the first service party according to the service calling request are the service module b and the service module c, taking the service module b and the service module c as target service modules.
It should be understood that the above examples are only examples for better understanding of the technical solutions of the embodiments of the present application, and are not to be taken as the only limitation of the embodiments of the present application.
After receiving the service call request of the first service party, the service call request may be analyzed, so as to determine a target service module to be called by the first service party according to a result obtained by the analysis.
After determining the target service module to be called by the first service party according to the service calling request, step 103 is executed.
Step 103: and acquiring a target service function corresponding to the target service module which is registered on the service platform in advance.
The target service function refers to a function of a target service module registered on the service platform, where the target service function is a function registered on the service platform by a service party of the target service module, for example, when the service party registers the target service module on the service platform, the service party can provide a service function that the target service module can disclose, and register on the service platform, so as to be called by other service parties, for example, the target service module includes a service function 1, a service function 2, and a service function 3, and after the service party of the target service module registers the service function 1 on the service platform, when the first service party calls the target service module, the service function 1 of the target service module is provided only to the first service party; after the service party of the target service module registers the service function 1 and the service function 3 on the service platform, when the first service party calls the target service module, only the service function 1 and the service function 3 of the target service module are provided for the first service party.
It should be understood that the above examples are only examples for better understanding of the technical solutions of the embodiments of the present application, and are not to be taken as the only limitation of the embodiments of the present application.
After determining the target service module to be called by the first service party according to the service calling request, the target service function corresponding to the target service module pre-registered on the service platform can be obtained.
After acquiring the target service function corresponding to the target service module pre-registered on the service platform, step 104 is executed.
Step 104: and providing the target service module and the target service function to the first service party.
After the target service module and the target service function corresponding to the target service module pre-registered on the service platform are obtained, the target service module and the target service function corresponding to the target service module can be provided to the first service party. Specifically, the target service module stores a module code of the service module and a function code of a target service function corresponding to the target service module on the service platform, and when the first service party needs to call the target service module, the service platform may send the module code of the target service module and the function code of the target service function corresponding to the target service module to the first service party.
According to the embodiment of the application, the service function corresponding to the service module is registered on the service platform in advance, the service module registered on the service platform and the service function corresponding to the service module are disclosed to the outside, and a service party can directly call the service module.
The service calling method provided by the embodiment of the application determines the target service module to be called by the first service party according to the service calling request by receiving the service calling request sent by the first service party, acquires the target service function corresponding to the target service module which is registered on the service platform in advance, and provides the target service module and the target service function for the first service party. According to the embodiment of the application, the service functions corresponding to the service modules are registered on the service platform in advance, the service modules registered on the service platform and the service functions corresponding to the service modules are externally disclosed, a service party can directly call the service modules, UI components do not need to be repeatedly developed on the service party, the occurrence of repeated functions is reduced, the problem that experience in the service is not uniform is solved, and the investment of labor cost is reduced.
Example two
Referring to fig. 2, a flowchart illustrating steps of another service invocation method provided in the embodiment of the present application is shown. As shown in fig. 2, the service invoking method may be applied to a service platform, and specifically may include the following steps:
step 201: acquiring registration requests aiming at a plurality of service modules, which are sent by a second service party; the target service module is a service module in the plurality of service modules.
The embodiment of the application can be applied to registering the service module developed by the service party on the service platform, the service party provides one or more functions of the service module, the functions of the service module and the service module registered on the service platform are open to the outside, and other service parties can directly call the service module to realize cross-service calling of the service module.
The service platform is a platform for a service party to register a service module, and the service platform can store service modules respectively provided by one or more service parties, for example, in a house service, the service modules are divided into service modules such as a new house, a second-hand house, a rented house, a broker, a cell, information and the like, and the service party can provide a certain function of one or more service modules in the service modules and register the service modules on the service platform to provide for other service parties to call.
The second service party refers to a service party that needs to register a service module on the service platform, and it can be understood that the second service party may be one service party or multiple service parties, and specifically, the second service party may be determined according to actual situations, which is not limited in this embodiment of the present application. The second service party is a terminal used by research and development personnel, and in the application, the second service party may be a mobile terminal, such as a mobile phone, a PAD (Portable Android Device, tablet computer), and other mobile electronic devices. The second service party may also be a PC (Personal Computer) end, such as an electronic device like a desktop Computer or a notebook Computer. Specifically, the method may be determined according to business requirements, and the embodiment of the present application is not limited thereto.
When a second service party needs to register a service module on the service platform, a registration request can be generated according to a plurality of service modules which need to be registered, and the second service party sends the registration request to the service platform. For example, referring to fig. 3, a schematic diagram of service module registration and invocation provided in this embodiment of the present application is shown, as shown in fig. 3, a service 2 is a second service party, and when the service 2 needs to register a service module on a service platform, a registration request may be sent to the service platform: protocol Register.
The target service module mentioned in the following steps is a service module in a plurality of service modules, specifically, the target service module may be one service module in the plurality of service modules, or may be at least two service modules in the plurality of service modules, specifically, may be determined according to service requirements.
After acquiring the registration requests for the plurality of service modules sent by the second service party, step 202 is executed.
Step 202: and acquiring the service function to be registered corresponding to each service module according to the registration request.
The service function to be registered refers to a service function that a service module provided by a second service party needs to be registered on a service platform, for example, the service module includes a service function 1, a service function 2, a service function 3, and a service function 4, and the second service party may register one of the service function 1, the service function 2, the service function 3, and the service function 4 on the service platform, or may register at least two of the service function 1, the service function 2, the service function 3, and the service function 4 on the service platform, which may be specifically determined according to service requirements.
After acquiring the registration request for the plurality of service modules sent by the second service party, the service function to be registered corresponding to each service module provided by the second service party may be acquired according to the service request, for example, as shown in fig. 3, in the process of generating the registration request by the service 2, the service function of the service module, such as the service function of a Protocol module, may be provided: imp1 and Imp 2. And constructing a registration request by combining the service function and the service module.
It should be understood that the above examples are only examples for better understanding of the technical solutions of the embodiments of the present application, and are not to be taken as the only limitation of the embodiments of the present application.
Furthermore, after the second service party sends the registration request to the service platform,
after acquiring the service function to be registered corresponding to each service module according to the registration request, step 203 is executed.
Step 203: and formulating a network data exchange protocol corresponding to each service function to be registered.
The network data exchange Protocol (i.e. Protocol) refers to a Protocol established by the service platform for each service function to be registered of the service module.
After the service platform obtains the service function to be registered corresponding to each service module, a network data exchange protocol corresponding to each service function to be registered may be formulated, for example, the service function to be registered includes a service function 1, a service function 2, and a service function 3, and the service platform may formulate a network data exchange protocol for the service function 1: protocol a, a network data exchange Protocol is established for the service function 2: protocol b, which makes network data exchange Protocol for service function 3: protocol c. The network data protocol of the established service function may be a Protoco Name as shown in fig. 3.
After the network data exchange protocol corresponding to each service function to be registered is formulated, a mapping relationship between the network data exchange protocol and the corresponding service module can be generated through the network data protocol (as shown in fig. 3).
After a network data exchange protocol corresponding to each service function to be registered is formulated, step 204 is executed.
Step 204: and storing each service module and the network data exchange protocol corresponding to each service module.
After the network data exchange protocol corresponding to each service function to be registered is formulated, each service module and the network data exchange protocol corresponding to each service module may be stored in the service platform.
After saving each service module and the network data exchange protocol corresponding to each service module, step 205 is performed.
Step 205: and receiving a service calling request sent by a first service party.
The first service party refers to a party calling the required service module from the service platform. The first service party is a terminal used by research and development personnel, and in the application, the first service party may be a mobile terminal, such as a mobile phone, a PAD (Portable Android Device, tablet computer), and other mobile electronic devices. The first service party may also be a PC (Personal Computer) end, such as an electronic device like a desktop Computer or a notebook Computer. Specifically, the method may be determined according to business requirements, and the embodiment of the present application is not limited thereto.
In this application, the first service party may be a service party that has registered a service module on the service platform, or may also be a service party that has not registered a service module on the service platform, and specifically, may be determined according to a service requirement, which is not limited in this embodiment of the application.
The service calling request refers to a request sent by a first service party for calling a required service module, the service modules registered on the service platform are all open to the outside, the service party can view the service modules registered on the service platform, and when the service party needs to call a certain service module, the service calling request can be generated by combining the service modules required to be called, and the service calling request is sent to the service platform, for example, a module identifier, such as module identifier 1, module identifier 2 and module identifier 3, can be allocated to each service module on the service platform, and when the first service party needs to acquire the service module corresponding to module identifier 2, the first service party can generate a corresponding service calling request by combining module identifier 2, and the like. Service 1 (i.e. the first service party) shown in fig. 3 sends a service invocation request to the service platform, and the service module Model to be invoked may be included in the service invocation request.
It should be understood that the above examples are only examples for better understanding of the technical solutions of the embodiments of the present application, and are not to be taken as the only limitation of the embodiments of the present application.
After receiving the service invocation request from the first service party, step 206 is performed.
Step 206: and determining a target service module required to be called by the first service party according to the service calling request.
The target service module refers to a service module that the first service party needs to call, for example, a service module registered on the service platform includes: the first service party calls the service module a according to the service calling request, and then the service module a is used as a target service module; and when the service modules required to be called by the first service party according to the service calling request are the service module b and the service module c, taking the service module b and the service module c as target service modules.
It should be understood that the above examples are only examples for better understanding of the technical solutions of the embodiments of the present application, and are not to be taken as the only limitation of the embodiments of the present application.
After receiving the service call request of the first service party, the service call request may be analyzed, so as to determine a target service module to be called by the first service party according to a result obtained by the analysis.
After determining the target service module to be called by the first service party according to the service calling request, step 207 is executed.
Step 207: and acquiring a target network data exchange protocol corresponding to the target service module.
The target network data exchange protocol refers to a network data exchange protocol which is registered for the target service module by the service platform in advance.
After determining the target service module to be called by the first service party according to the service calling request, a target network data exchange protocol corresponding to the target service module may be obtained.
After acquiring the target network data exchange protocol corresponding to the target service module, step 208 is executed.
Step 208: and acquiring a target service function corresponding to the target service module based on the target network data exchange protocol.
The target service function refers to a function of a target service module registered on the service platform, where the target service function is a function registered on the service platform by a service party of the target service module, for example, when the service party registers the target service module on the service platform, the service party can provide a service function that the target service module can disclose, and register on the service platform, so as to be called by other service parties, for example, the target service module includes a service function 1, a service function 2, and a service function 3, and after the service party of the target service module registers the service function 1 on the service platform, when the first service party calls the target service module, the service function 1 of the target service module is provided only to the first service party; after the service party of the target service module registers the service function 1 and the service function 3 on the service platform, when the first service party calls the target service module, only the service function 1 and the service function 3 of the target service module are provided for the first service party.
It should be understood that the above examples are only examples for better understanding of the technical solutions of the embodiments of the present application, and are not to be taken as the only limitation of the embodiments of the present application.
After the target network data exchange protocol is acquired, the target service function corresponding to the target service module can be acquired according to the target network data exchange protocol.
After acquiring the target service function corresponding to the target service module according to the target network data exchange protocol, step 209 is executed.
Step 209: and providing the target service module and the target service function to the first service party, and providing the target service module and the target service function to the first service party.
After the target service module and the target service function corresponding to the target service module pre-registered on the service platform are obtained, the target service module and the target service function corresponding to the target service module can be provided to the first service party. Specifically, the target service module stores a module code of the service module and a function code of a target service function corresponding to the target service module on the service platform, and when the first service party needs to call the target service module, the service platform may send the module code of the target service module and the function code of the target service function corresponding to the target service module to the first service party.
According to the embodiment of the application, the service function corresponding to the service module is registered on the service platform in advance, the service module registered on the service platform and the service function corresponding to the service module are disclosed to the outside, and a service party can directly call the service module.
After the target service module and the target service function corresponding to the target service module are provided to the first service party, step 210 is performed, or step 211 is performed.
Step 210: and when the calling frequency of the target service module is less than or equal to a preset frequency threshold, releasing the target service module from the service platform.
The preset frequency threshold refers to a calling frequency threshold of the service module preset by a manager of the service platform. The specific value of the preset frequency threshold may be determined according to the service requirement, and this is not limited in the embodiment of the present application.
When the calling frequency of the target service module is less than or equal to the preset frequency threshold, the target service module can be released from the service platform, that is, the target service module is removed from the service platform, so that the memory pressure of the service platform can be reduced.
Step 211: and when the calling frequency of the target service module is greater than the preset frequency threshold and a warning message of insufficient memory is received, releasing the target service module from the service platform.
When the calling frequency of the target service module is greater than the preset frequency threshold, the use frequency of the target service module is high, the target service module can be continuously reserved on the service platform, and when a warning message that the memory of the service platform is insufficient is received, the target service module is released from the service platform, that is, the target service module is cleared from the service platform, so that the memory occupied by the service platform is released.
The service calling method provided by the embodiment of the application determines the target service module to be called by the first service party according to the service calling request by receiving the service calling request sent by the first service party, acquires the target service function corresponding to the target service module which is registered on the service platform in advance, and provides the target service module and the target service function for the first service party. According to the embodiment of the application, the service functions corresponding to the service modules are registered on the service platform in advance, the service modules registered on the service platform and the service functions corresponding to the service modules are externally disclosed, a service party can directly call the service modules, UI components do not need to be repeatedly developed on the service party, the occurrence of repeated functions is reduced, the problem that experience in the service is not uniform is solved, and the investment of labor cost is reduced.
EXAMPLE III
Referring to fig. 4, a schematic structural diagram of a service invocation device in the embodiment of the present application is shown.
The service invoking device of the embodiment of the application can be applied to a service platform, and specifically can include: a service invocation request receiving module 310, a target service module determining module 320, a target service function acquiring module 330 and a target service function providing module 340, wherein,
a service call request receiving module 310, configured to receive a service call request sent by a first service party;
a target service module determining module 320, configured to determine, according to the service invocation request, a target service module that needs to be invoked by the first service party;
a target service function acquiring module 330, configured to acquire a target service function corresponding to the target service module that is pre-registered on the service platform;
a target service function providing module 340, configured to provide the target service module and the target service function to the first service party.
The service calling device provided in the embodiment of the application determines a target service module to be called by a first service party according to a service calling request by receiving the service calling request sent by the first service party, obtains a target service function corresponding to the target service module pre-registered on a service platform, and provides the target service module and the target service function to the first service party. According to the embodiment of the application, the service functions corresponding to the service modules are registered on the service platform in advance, the service modules registered on the service platform and the service functions corresponding to the service modules are externally disclosed, a service party can directly call the service modules, UI components do not need to be repeatedly developed on the service party, the occurrence of repeated functions is reduced, the problem that experience in the service is not uniform is solved, and the investment of labor cost is reduced.
Example four
Referring to fig. 5, a schematic structural diagram of another service invocation device in the embodiment of the present application is shown.
The service invoking device of the embodiment of the application can be applied to a service platform, and specifically can include:
a registration request obtaining module 410, configured to obtain registration requests for multiple service modules sent by a second service party; the target business module is a business module in the plurality of business modules;
a function acquiring module 420 for acquiring a service function to be registered corresponding to each service module according to the registration request;
an exchange protocol specifying module 430, configured to specify a network data exchange protocol corresponding to each service function to be registered;
the exchange protocol storage module 440 is configured to store each service module and a network data exchange protocol corresponding to each service module;
a service call request receiving module 450, configured to receive a service call request sent by a first service party;
a target service module determining module 460, configured to determine, according to the service invocation request, a target service module that needs to be invoked by the first service party;
a target service function acquiring module 470, configured to acquire a target service function corresponding to the target service module that is registered in the service platform in advance;
a target service function providing module 480, configured to provide the target service module and the target service function to the first service party;
a first service module releasing module 490, configured to release the target service module from the service platform when the calling frequency of the target service module is less than or equal to a preset frequency threshold;
a second service module releasing module 4100, configured to release the target service module from the service platform when the calling frequency of the target service module is greater than the preset frequency threshold and a warning message that the memory is insufficient is received.
Optionally, the target service function obtaining module 470 includes:
a data exchange protocol obtaining sub-module 471, configured to obtain a target network data exchange protocol corresponding to the target service module;
the target service function obtaining sub-module 472 is configured to obtain a target service function corresponding to the target service module based on the target network data exchange protocol.
The service calling device provided in the embodiment of the application determines a target service module to be called by a first service party according to a service calling request by receiving the service calling request sent by the first service party, obtains a target service function corresponding to the target service module pre-registered on a service platform, and provides the target service module and the target service function to the first service party. According to the embodiment of the application, the service functions corresponding to the service modules are registered on the service platform in advance, the service modules registered on the service platform and the service functions corresponding to the service modules are externally disclosed, a service party can directly call the service modules, UI components do not need to be repeatedly developed on the service party, the occurrence of repeated functions is reduced, the problem that experience in the service is not uniform is solved, and the investment of labor cost is reduced.
EXAMPLE five
Fig. 6 is a schematic diagram of a hardware structure of a terminal device for implementing various embodiments of the present application.
The terminal device 500 includes but is not limited to: a radio frequency unit 501, a network module 502, an audio output unit 503, an input unit 504, a sensor 505, a display unit 506, a user input unit 507, an interface unit 508, a memory 509, a processor 510, and a power supply 511. Those skilled in the art will appreciate that the terminal device configuration shown in fig. 6 does not constitute a limitation of the terminal device, and that the terminal device may include more or fewer components than shown, or combine certain components, or a different arrangement of components. In the embodiment of the present application, the terminal device includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer, and the like.
It should be understood that, in the embodiment of the present application, the radio frequency unit 501 may be used for receiving and sending signals during a message sending and receiving process or a call process, and specifically, receives downlink data from a base station and then processes the received downlink data to the processor 510; in addition, the uplink data is transmitted to the base station. In general, radio frequency unit 501 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 501 can also communicate with a network and other devices through a wireless communication system.
The terminal device provides the user with wireless broadband internet access through the network module 502, such as helping the user send and receive e-mails, browse webpages, access streaming media, and the like.
The audio output unit 503 may convert audio data received by the radio frequency unit 501 or the network module 502 or stored in the memory 509 into an audio signal and output as sound. Also, the audio output unit 503 may also provide audio output related to a specific function performed by the terminal apparatus 500 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 503 includes a speaker, a buzzer, a receiver, and the like.
The input unit 504 is used to receive an audio or video signal. The input Unit 504 may include a Graphics Processing Unit (GPU) 5041 and a microphone 5042, and the Graphics processor 5041 processes image data of a still picture or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 506. The image frames processed by the graphic processor 5041 may be stored in the memory 509 (or other storage medium) or transmitted via the radio frequency unit 501 or the network module 502. The microphone 5042 may receive sounds and may be capable of processing such sounds into audio data. The processed audio data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 501 in case of the phone call mode.
The terminal device 500 further comprises at least one sensor 505, such as light sensors, motion sensors and other sensors. Specifically, the light sensor includes an ambient light sensor that adjusts the brightness of the display panel 5061 according to the brightness of ambient light, and a proximity sensor that turns off the display panel 5061 and/or a backlight when the terminal device 500 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used to identify the terminal device posture (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration identification related functions (such as pedometer, tapping), and the like; the sensors 505 may also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., which are not described in detail herein.
The display unit 506 is used to display information input by the user or information provided to the user. The Display unit 506 may include a Display panel 5061, and the Display panel 5061 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.
The user input unit 507 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the terminal device. Specifically, the user input unit 507 includes a touch panel 5071 and other input devices 5072. Touch panel 5071, also referred to as a touch screen, may collect touch operations by a user on or near it (e.g., operations by a user on or near touch panel 5071 using a finger, stylus, or any suitable object or attachment). The touch panel 5071 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 510, and receives and executes commands sent by the processor 510. In addition, the touch panel 5071 may be implemented in various types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 5071, the user input unit 507 may include other input devices 5072. In particular, other input devices 5072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.
Further, the touch panel 5071 may be overlaid on the display panel 5061, and when the touch panel 5071 detects a touch operation thereon or nearby, the touch operation is transmitted to the processor 510 to determine the type of the touch event, and then the processor 510 provides a corresponding visual output on the display panel 5061 according to the type of the touch event. Although in fig. 6, the touch panel 5071 and the display 5061 are two independent components to implement the input and output functions of the terminal device, in some embodiments, the touch panel 5071 and the display 5061 may be integrated to implement the input and output functions of the terminal device, and is not limited herein.
The interface unit 508 is an interface for connecting an external device to the terminal apparatus 500. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 508 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 terminal apparatus 500 or may be used to transmit data between the terminal apparatus 500 and the external device.
The memory 509 may be used to store software programs as well as various data. The memory 509 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 509 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.
The processor 510 is a control center of the terminal device, connects various parts of the entire terminal device by using various interfaces and lines, and performs various functions of the terminal device and processes data by running or executing software programs and/or modules stored in the memory 509 and calling data stored in the memory 509, thereby performing overall monitoring of the terminal device. Processor 510 may include one or more processing units; preferably, the processor 510 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 510.
The terminal device 500 may further include a power supply 511 (e.g., a battery) for supplying power to various components, and preferably, the power supply 511 may be logically connected to the processor 510 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system.
In addition, the terminal device 500 includes some functional modules that are not shown, and are not described in detail herein.
Preferably, an embodiment of the present application further provides a terminal device, including: the processor 510, the memory 509, and a computer program stored in the memory 509 and capable of running on the processor 510, where the computer program, when executed by the processor 510, implements each process of the foregoing service invocation method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again.
The embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when being executed by a processor, the computer program implements each process of the foregoing service invocation method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
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 application 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 (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 application.
While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.
Those of ordinary skill in the art would appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed in the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
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, 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, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present application, but the scope of the present application 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 application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (8)

1. A service calling method is applied to a service platform and is characterized by comprising the following steps:
receiving a service calling request sent by a first service party;
determining a target service module to be called by the first service party according to the service calling request;
acquiring a target service function corresponding to the target service module which is registered on the service platform in advance;
providing the target service module code and the target service function code to the first service party;
before the receiving of the service invocation request sent by the first service party, the method further includes:
acquiring registration requests aiming at a plurality of service modules, which are sent by a second service party; the target business module is a business module in the plurality of business modules;
acquiring a service function to be registered corresponding to each service module according to the registration request;
formulating a network data exchange protocol corresponding to each service function to be registered;
storing each service module and a network data exchange protocol corresponding to each service module;
the service function to be registered refers to a service function which needs to be registered on the service platform in a service module provided by the second service party.
2. The method according to claim 1, wherein the obtaining of the target service function corresponding to the target service module pre-registered on the service platform comprises:
acquiring a target network data exchange protocol corresponding to the target service module;
and acquiring a target service function corresponding to the target service module based on the target network data exchange protocol.
3. The method of claim 1, wherein after said providing the target service module code and target service function code to the first service party, further comprising:
when the calling frequency of the target service module is less than or equal to a preset frequency threshold, releasing the target service module from the service platform;
and when the calling frequency of the target service module is greater than the preset frequency threshold and a warning message of insufficient memory is received, releasing the target service module from the service platform.
4. A service calling device is applied to a service platform and is characterized by comprising:
the service calling request receiving module is used for receiving a service calling request sent by a first service party;
the target service module determining module is used for determining a target service module required to be called by the first service party according to the service calling request;
a target service function acquiring module, configured to acquire a target service function corresponding to the target service module that is pre-registered on the service platform;
the target service function providing module is used for providing a target service module code and a target service function code to the first service party;
the device further comprises:
the registration request acquisition module is used for acquiring registration requests aiming at the plurality of service modules and sent by a second service party; the target business module is a business module in the plurality of business modules;
a function to be registered acquisition module, configured to acquire a service function to be registered corresponding to each service module according to the registration request;
the exchange protocol specifying module is used for specifying a network data exchange protocol corresponding to each service function to be registered;
the exchange protocol storage module is used for storing each service module and the network data exchange protocol corresponding to each service module;
the service function to be registered refers to a service function which needs to be registered on the service platform in a service module provided by the second service party.
5. The apparatus of claim 4, wherein the target service function obtaining module comprises:
the data exchange protocol acquisition submodule is used for acquiring a target network data exchange protocol corresponding to the target service module;
and the target service function acquisition submodule is used for acquiring a target service function corresponding to the target service module based on the target network data exchange protocol.
6. The apparatus of claim 4, further comprising:
the first service module releasing module is used for releasing the target service module from the service platform when the calling frequency of the target service module is less than or equal to a preset frequency threshold;
and the second service module release module is used for releasing the target service module from the service platform when the calling frequency of the target service module is greater than the preset frequency threshold and a warning message of insufficient memory is received.
7. A terminal device, comprising: memory, a processor and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing a service invocation method according to any of claims 1 to 3.
8. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored thereon a computer program which, when executed by a processor, implements the service invocation method according to any of claims 1-3.
CN201911400757.9A 2019-12-30 2019-12-30 Service calling method, device, terminal equipment and storage medium Active CN111200648B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911400757.9A CN111200648B (en) 2019-12-30 2019-12-30 Service calling method, device, terminal equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911400757.9A CN111200648B (en) 2019-12-30 2019-12-30 Service calling method, device, terminal equipment and storage medium

Publications (2)

Publication Number Publication Date
CN111200648A CN111200648A (en) 2020-05-26
CN111200648B true CN111200648B (en) 2021-05-11

Family

ID=70747671

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911400757.9A Active CN111200648B (en) 2019-12-30 2019-12-30 Service calling method, device, terminal equipment and storage medium

Country Status (1)

Country Link
CN (1) CN111200648B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114584605B (en) * 2022-03-21 2024-04-05 平安壹钱包电子商务有限公司 Service distribution method and device, electronic equipment and storage medium
CN115482633A (en) * 2022-09-13 2022-12-16 珠海市新德汇信息技术有限公司 Method, system, storage medium and device compatible with communication interaction of different devices

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101075192A (en) * 2007-06-14 2007-11-21 高建强 Method and apparatus for defining service flow in data system
CN101119268A (en) * 2007-06-28 2008-02-06 杭州东信北邮信息技术有限公司 Method for implementing universal message bus based universal service system structure
JP2011048492A (en) * 2009-08-25 2011-03-10 Toyota Motor Corp Program creation support device, creation support method, and creation support program
CN102223396A (en) * 2011-05-12 2011-10-19 杭州动量云霄网络技术有限公司 System and method for associating service logic with user interface in computer system based on cloud computing
CN103645919A (en) * 2013-12-18 2014-03-19 用友软件股份有限公司 Method for extending functions of management information system through plugins
CN103646210A (en) * 2013-12-27 2014-03-19 税友软件集团股份有限公司 Method and device for calling system function
CN106406911A (en) * 2016-10-26 2017-02-15 国云科技股份有限公司 Method for modularizing functions of computer software system
CN106897072A (en) * 2017-02-28 2017-06-27 北京三快在线科技有限公司 Traffic engineered call method, device and electronic equipment
CN109857489A (en) * 2017-11-30 2019-06-07 阿里巴巴集团控股有限公司 Development system, decoupling method and device based on android system

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100382493C (en) * 2006-03-06 2008-04-16 华为技术有限公司 System and method for realizing service
CN102378170B (en) * 2010-08-27 2014-12-10 中国移动通信有限公司 Method, device and system of authentication and service calling
CN104391689B (en) * 2014-11-04 2018-10-16 中国石油天然气股份有限公司 A kind of development approach, middleware and the PaaS platform of Internet of Things application

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101075192A (en) * 2007-06-14 2007-11-21 高建强 Method and apparatus for defining service flow in data system
CN101119268A (en) * 2007-06-28 2008-02-06 杭州东信北邮信息技术有限公司 Method for implementing universal message bus based universal service system structure
JP2011048492A (en) * 2009-08-25 2011-03-10 Toyota Motor Corp Program creation support device, creation support method, and creation support program
CN102223396A (en) * 2011-05-12 2011-10-19 杭州动量云霄网络技术有限公司 System and method for associating service logic with user interface in computer system based on cloud computing
CN103645919A (en) * 2013-12-18 2014-03-19 用友软件股份有限公司 Method for extending functions of management information system through plugins
CN103646210A (en) * 2013-12-27 2014-03-19 税友软件集团股份有限公司 Method and device for calling system function
CN106406911A (en) * 2016-10-26 2017-02-15 国云科技股份有限公司 Method for modularizing functions of computer software system
CN106897072A (en) * 2017-02-28 2017-06-27 北京三快在线科技有限公司 Traffic engineered call method, device and electronic equipment
CN109857489A (en) * 2017-11-30 2019-06-07 阿里巴巴集团控股有限公司 Development system, decoupling method and device based on android system

Also Published As

Publication number Publication date
CN111200648A (en) 2020-05-26

Similar Documents

Publication Publication Date Title
CN110062105B (en) Interface display method and terminal equipment
CN110058836B (en) Audio signal output method and terminal equipment
CN109343788B (en) Operation control method of mobile terminal and mobile terminal
CN110752981B (en) Information control method and electronic equipment
CN107734172B (en) Information display method and mobile terminal
CN111030917B (en) Message display method and electronic equipment
CN110049187B (en) Display method and terminal equipment
CN109995862B (en) Resource scheduling method and terminal
CN111124706A (en) Application program sharing method and electronic equipment
CN108322897B (en) Card package meal combination method and device
CN111163449B (en) Application sharing method, first electronic device and computer-readable storage medium
CN111107223B (en) Message processing method and electronic equipment
CN111200648B (en) Service calling method, device, terminal equipment and storage medium
CN110022551B (en) Information interaction method and terminal equipment
CN111131607A (en) Information sharing method, electronic equipment and computer readable storage medium
CN109992192B (en) Interface display method and terminal equipment
CN109117037B (en) Image processing method and terminal equipment
CN111061404A (en) Control method and first electronic device
CN108093119B (en) Strange incoming call number marking method and mobile terminal
CN111163227B (en) Sharing method and electronic equipment
CN110032422B (en) Application management method, terminal equipment and computer readable storage medium
CN109451154B (en) Method for setting multimedia file and terminal equipment
CN109068276B (en) Message conversion method and terminal
CN108429805B (en) File downloading processing method, sending terminal and receiving terminal
CN110750318A (en) Message reply method and device and mobile terminal

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant