CN113127224A - Information acquisition method, device, equipment and storage medium - Google Patents

Information acquisition method, device, equipment and storage medium Download PDF

Info

Publication number
CN113127224A
CN113127224A CN202010040223.6A CN202010040223A CN113127224A CN 113127224 A CN113127224 A CN 113127224A CN 202010040223 A CN202010040223 A CN 202010040223A CN 113127224 A CN113127224 A CN 113127224A
Authority
CN
China
Prior art keywords
client
command word
interface
information
interfaces
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.)
Pending
Application number
CN202010040223.6A
Other languages
Chinese (zh)
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.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen 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 Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN202010040223.6A priority Critical patent/CN113127224A/en
Publication of CN113127224A publication Critical patent/CN113127224A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/547Remote procedure calls [RPC]; Web services
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00Indexing scheme relating to G06F9/00
    • G06F2209/54Indexing scheme relating to G06F9/54
    • G06F2209/541Client-server

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer And Data Communications (AREA)

Abstract

The application discloses an information acquisition method, an information acquisition device, information acquisition equipment and a storage medium, and belongs to the technical field of communication. The method comprises the following steps: a first client receives a first instruction for acquiring first information through a first interface, and at least two interfaces in a plurality of interfaces of the first client multiplex a communication link; the first client converts the first instruction into a first command word and generates a first Remote Procedure Call (RPC) request comprising the first command word; the first client sends the first RPC request to the second client through a target communication link multiplexed by the first interface; and the first client receives a second command word sent by the second client through the target communication link and converts the second command word into the first information. The process is not limited by the interface version, the RPC request is guaranteed to reach the second client, the compatibility is improved, the phenomenon of abnormal interruption of the information acquisition process caused by different interface versions is reduced, and the stability of the information acquisition process is high.

Description

Information acquisition method, device, equipment and storage medium
Technical Field
The embodiment of the application relates to the technical field of communication, in particular to an information acquisition method, an information acquisition device, information acquisition equipment and a storage medium.
Background
With the development of science and technology, one client communicates with another client in a Remote Procedure Call (RPC) manner to obtain more and more scenes of information. For example, in a scene of performing face-brushing payment based on a self-service payment terminal, a merchant client needs to communicate with a human face client in an RPC manner to acquire payment-related information.
Disclosure of Invention
The embodiment of the application provides an information acquisition method, an information acquisition device, information acquisition equipment and a storage medium, which can be used for improving the stability of an information acquisition process. The technical scheme is as follows:
in one aspect, an embodiment of the present application provides an information obtaining method, where the method includes:
a first client receives a first instruction for acquiring first information through a first interface, wherein the first interface is any interface in a plurality of interfaces of the first client, and at least two interfaces in the plurality of interfaces multiplex a communication link;
the first client converts the first instruction into a first command word and generates a first Remote Procedure Call (RPC) request comprising the first command word;
the first client sends the first RPC request to a second client through a target communication link multiplexed by the first interface, the second client is used for calling a target interface corresponding to the first RPC request to acquire the first information, converting the first information into a second command word, and sending the second command word to the first client through the target communication link;
and the first client receives the second command word sent by the second client through the target communication link, and converts the second command word into the first information.
There is also provided an information acquisition method, the method comprising:
the method comprises the steps that a second client receives a first Remote Procedure Call (RPC) request sent by a first client through a target communication link, wherein the first RPC request comprises a first command word;
the second client calls a target interface corresponding to the first RPC request to acquire first information, and at least two interfaces in the plurality of interfaces of the second client multiplex a communication link;
and the second client converts the first information into a second command word and sends the second command word to the first client through the target communication link.
In another aspect, an information acquisition apparatus is provided, the apparatus including:
a receiving module, configured to receive a first instruction for obtaining first information through a first interface, where the first interface is any interface among multiple interfaces of the first client, and at least two interfaces of the multiple interfaces multiplex a communication link;
a conversion module for converting the first instruction into a first command word;
a generation module to generate a first remote procedure call, RPC, request including the first command word;
the sending module is used for sending the first RPC request to a second client through a target communication link multiplexed by the first interface, the second client is used for calling a target interface corresponding to the first RPC request to obtain the first information, converting the first information into a second command word, and sending the second command word to the first client through the target communication link;
the receiving module is further configured to receive the second command word sent by the second client through the target communication link;
the conversion module is further configured to convert the second command word into the first information.
In one possible implementation, the plurality of interfaces of the first client each multiplex the target communication link.
There is also provided an information acquisition apparatus, the apparatus including:
the Remote Procedure Call (RPC) system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving a first RPC request sent by a first client through a target communication link, and the first RPC request comprises a first command word;
the acquisition module is used for calling a target interface corresponding to the first RPC request to acquire first information, and at least two interfaces in the plurality of interfaces of the second client multiplex a communication link;
the conversion module is used for converting the first information into a second command word;
a sending module, configured to send the second command word to the first client through the target communication link.
In another aspect, a computer device is provided, which includes a processor and a memory, where at least one program code is stored in the memory, and the at least one program code is loaded and executed by the processor to implement any one of the above-mentioned information acquisition methods.
In another aspect, a computer-readable storage medium is provided, in which at least one program code is stored, and the at least one program code is loaded and executed by a processor to implement any of the above-mentioned information acquisition methods.
The technical scheme provided by the embodiment of the application at least has the following beneficial effects:
in the embodiment of the application, at least two interfaces multiplex the same communication link, in order to enable the multiplexed communication link to be suitable for a plurality of interfaces, the instruction received from the interfaces is converted into the command word, and the RPC request including the command word is transmitted in the multiplexed communication link, so that the process is not limited by the interface version, the RPC request is guaranteed to reach a second client, the compatibility among the interfaces of different versions is improved, the phenomenon of abnormal interruption of the information acquisition process caused by different interface versions is reduced, and the stability of the information acquisition process is high.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are 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 to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic diagram of an implementation environment of an information acquisition method provided in an embodiment of the present application;
fig. 2 is a schematic diagram of a self-service payment terminal provided in an embodiment of the present application;
fig. 3 is a flowchart of an information obtaining method according to an embodiment of the present application;
fig. 4 is a schematic diagram of a process in which a second client calls a target interface to obtain first information according to an embodiment of the present application;
fig. 5 is a schematic diagram of an information acquisition apparatus according to an embodiment of the present application;
fig. 6 is a schematic diagram of an information acquisition apparatus according to an embodiment of the present application;
fig. 7 is a schematic diagram of an information acquisition apparatus according to an embodiment of the present application;
fig. 8 is a schematic diagram of an information acquisition apparatus according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of a terminal according to an embodiment of the present application;
fig. 10 is a schematic structural diagram of a computer device according to an embodiment of the present application.
Detailed Description
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
Referring to fig. 1, a schematic diagram of an implementation environment of the information acquisition method provided in the embodiment of the present application is shown. The implementation environment may be an information acquisition system 10, where the information acquisition system 10 includes: a first client 11 and a second client 12.
The first client 11 and the second client 12 may be installed in the same terminal, or may be installed in different terminals, which is not limited in this embodiment of the present application. The first client 11 and the second client 12 may implement an information obtaining process based on the method provided in the embodiment of the present application. In one possible implementation, the first client 11 may call an interface of the second client 12 to obtain information by means of RPC. In the course of communication based on the RPC method, the first client 11 that initiates the RPC request is used as a client, and the second client 12 that provides service for the RPC request is used as a server.
Illustratively, the first client 11 may be a merchant client installed in the self-service payment terminal, and the second client 12 may be a human face client installed in the self-service payment terminal. As shown in fig. 2, the self-service payment terminal 13 is an electronic device for realizing self-service shopping, and is generally disposed in a supermarket, a store and other places, and is capable of enabling a user to scan goods and check out payment in a self-service manner. When the user selects the face-brushing payment, the merchant client can call a related interface of the face client in an RPC (remote position control) mode to identify the face of the user and acquire identity information or payment code information corresponding to the user.
It should be understood by those skilled in the art that the first client 11 and the second client 12 are only examples, and other existing or future first clients and second clients may be applicable to the present application, and are included in the scope of the present application and are herein incorporated by reference.
Based on the implementation environment shown in fig. 1, an embodiment of the present application provides an information obtaining method, which is applied to an interaction process between a first client and a second client as an example. As shown in fig. 3, the method provided by the embodiment of the present application may include the following steps:
in step 301, a first client receives a first instruction for acquiring first information through a first interface, where the first interface is any interface among a plurality of interfaces of the first client, and at least two interfaces of the plurality of interfaces multiplex a communication link.
The first client is any client needing to acquire information from the second client, the first client is provided with a plurality of interfaces, and at least two interfaces in the plurality of interfaces of the first client multiplex a communication link. The multiplexing of one communication link by at least two interfaces means that the at least two interfaces communicate with the interface in the second client through the same communication link. It should be noted that, in the embodiment of the present application, the specific number of the interfaces multiplexing the same communication link is not limited, as long as at least two interfaces are ensured to multiplex the same communication link. In one possible implementation, the multiple interfaces of the first client each multiplex the same communication link. At this time, all the interfaces in the first client communicate with the interface of the second client through the same communication link.
Exemplarily, it is assumed that the first client has 5 interfaces, interface 1, interface 2, interface 3, interface 4, and interface 5, respectively. The multiplexing of at least two interfaces by one communication link may mean that interface 1 and interface 2 multiplex communication link 1, and interface 3, interface 4 and interface 5 multiplex communication link 2. Of course, that at least two interfaces multiplex one communication link may also mean that interface 1, interface 2, interface 3, interface 4, and interface 5 all multiplex communication link 1.
The first interface is any interface in a plurality of interfaces of the first client. In this embodiment of the application, the first information is information that the first client needs to obtain currently, and the first instruction is an instruction for obtaining the first information. The first interface is an interface capable of receiving a first command. The first client may receive a first instruction to obtain first information through the first interface. It should be noted that, according to a difference in function or type of the first interface, the first client may receive, through the first interface, a different first instruction for acquiring different first information.
Exemplarily, assuming that the first client is a merchant client in the self-service payment terminal and the second client is a face client in the self-service payment terminal, the first interface may be an interface capable of receiving an instruction for acquiring user identity information in the merchant client, or may be an interface capable of receiving an instruction for acquiring user payment code information in the merchant client. For the condition that the first interface is an interface which can receive an instruction for acquiring user identity information in the merchant client, the first information is the user identity information, the first instruction is the instruction for acquiring the user identity information, and the first client can receive the instruction for acquiring the user identity information through the first interface; for the condition that the first interface is an interface which can receive an instruction for acquiring user payment code information in the merchant client, the first information is the user payment code information, the first instruction is the instruction for acquiring the user payment code information, and the first client can receive the instruction for acquiring the user payment code information through the first interface.
In one possible implementation, the first instruction for acquiring the first information may be generated based on a trigger operation of a user. Different trigger operations may generate different first instructions for obtaining different first information. Illustratively, when a face-brushing payment triggering operation of the user is detected, a first instruction for acquiring payment code information of the user can be generated, and at the moment, the first information is the payment code information of the user; when the user identity authentication triggering operation is detected, a first instruction for acquiring the user identity information may be generated, and at this time, the first information is the user identity information. The first client may store a corresponding relationship between the instruction and the interface, and after generating the first instruction, the first client determines the first interface in the corresponding relationship between the instruction and the interface, and then receives the first instruction through the first interface.
In step 302, the first client converts the first instruction into a first command word, generating a first remote procedure call, RPC, request comprising the first command word.
The first client may convert the first instruction into a first command word after receiving the first instruction through the first interface. The first command word may refer to a representation of the first instruction that facilitates communication over the communication link multiplexed by the first interface. That is, the first command word and the first instruction correspond to each other, and both of them represent the same meaning with different expressions, and since the first instruction is used to indicate that the first information needs to be acquired, the first command word is also used to indicate that the first information needs to be acquired.
In one possible implementation, the manner in which the first client converts the first instruction into the first command word includes, but is not limited to, the following two:
the first method is as follows: the first client converts the first instruction into a first command word based on a first conversion mode.
In this manner, the bottom layer of the first client may store a first conversion scheme for converting instructions into command words. The first conversion method may be formulated by a developer of the first client, or may be freely adjusted according to an actual application scenario, which is not limited in the embodiment of the present application. The first client may automatically convert the first instruction into the first command word at the bottom layer based on the first conversion mode.
The second method comprises the following steps: the first client stores the corresponding relation between the instruction and the command word, queries a first command word corresponding to the first instruction based on the corresponding relation between the instruction and the command word, and then converts the first instruction into the first command word.
After obtaining the first command word, the first client generates a first RPC request including the first command word. The first RPC request is used for requesting to call an interface of the second client to acquire first information. RPC is a protocol that requests services from a remote computer program over a network without knowledge of the underlying network technology. Based on the RPC mode, the communication between the two clients can be realized.
For an Android operating system, RPC communication may be implemented based on AIDL (Android interface definition Language). In the process of realizing RPC communication based on AIDL, two roles are included: a client and a server. In the embodiment of the present application, the first client that generates the first RPC request is used as a client, that is, an SDK (Software Development Kit) of the client that integrates the aid id in the first client; and taking the second client which acquires the first information based on the PRC request as a service machine, namely integrating the SDK of the service machine of the AIDL with the second client.
In one possible implementation, after generating the first RPC request, the first client may encode the first RPC request to encode the first RPC request into a format capable of network transmission.
In step 303, the first client sends the first RPC request to the second client over the target communication link multiplexed by the first interface.
It should be noted that, since at least two interfaces of the plurality of interfaces of the first client multiplex one communication link, there is at least one interface that also multiplexes the target communication link in addition to the first interface. In one possible implementation, multiple interfaces in the first client each multiplex the target communication link. That is, there is only one target communication link for all interfaces in the first client to communicate with all interfaces in the second client.
In one possible implementation manner, the manner in which the first client sends the first RPC request to the second client through the target communication link is as follows: and the first client sends the first RPC request after the coding processing to the second client through the target communication link.
The second client is a client capable of providing the first information for the first client. For example, in the case that the first client is a merchant client in the self-service payment terminal and the first information is user payment code information, the second client may be a face client in the self-service payment terminal, and the face client may provide the user payment code information for the merchant client, so that the merchant performs a subsequent deduction process based on the user payment code information.
In step 304, the second client receives the first remote procedure call, RPC, request sent by the first client over the target communication link.
After the first client sends the first RPC request to the second client through the target communication link, the second client can receive the first RPC request through the target communication link. The first RPC request comprises a first command word, wherein the first command word is obtained by converting a first instruction used for acquiring first information. Since the first command word corresponds to the first instruction association, the first command word in the first RPC request is used to indicate that the first information needs to be obtained.
In one possible implementation manner, for a case that the first client sends the encoded first RPC request to the second client through the target communication link, the second client receives the encoded first RPC request through the target communication link. After receiving the first RPC request subjected to encoding processing, the second client needs to decode the first RPC request subjected to encoding processing to obtain the first RPC request.
In a possible implementation manner, after receiving the first RPC request, the second client may parse the first RPC request to obtain the first command word, so as to determine the service logic to be executed according to the first command word. In the embodiment of the present application, since the first command word indicates that the first information needs to be acquired, the service logic that needs to be executed may be determined to acquire the first information according to the first command word.
In one possible implementation manner, the second client parses the first RPC request, and the manner of obtaining the first command word may be: and the second client identifies the format of each message in the first RPC request, and extracts the message in the command word format to obtain the first command word. It should be noted that the manner of parsing the first RPC request and obtaining the first command word is only an exemplary description, and the embodiment of the present application does not limit this.
The second client has a plurality of interfaces, different interfaces for executing different business logic. After the first command word is obtained, the second client needs to determine a target interface for executing the service logic corresponding to the first command word, so as to execute the service logic corresponding to the first command word by calling the target interface. In one possible implementation, the second client is configured with a mapping of command words and interfaces. In one possible implementation, in the mapping relationship between the command word and the interface, the same interface in different versions may have a mapping relationship with the same command word, thereby improving compatibility between interfaces in different versions.
After obtaining the first command word, the second client may determine whether a target interface having a mapping relationship with the first command word exists based on a mapping relationship between the command word and the interface. The process may be: the second client inquires the first command word in the mapping relation between the command word and the interface; responding to the fact that the mapping relation between the command word and the interfaces comprises the first command word, and a target interface corresponding to the first RPC request exists in the plurality of interfaces of the second client; and responding to the condition that the mapping relation between the command word and the interface does not comprise the first command word, and not having a target interface corresponding to the first RPC request in the plurality of interfaces of the second client.
When the mapping relationship between the command word and the interface includes the first command word, a target interface having a mapping relationship with the first command word may be directly determined according to the mapping relationship between the command word and the interface, which indicates that a target interface corresponding to the first RPC request exists in the plurality of interfaces of the second client, and step 305 is executed; when the mapping relationship between the command word and the interface does not include the first command word, a target interface having a mapping relationship with the first command word cannot be determined according to the mapping relationship between the command word and the interface, which indicates that no target interface corresponding to the first RPC request exists in the plurality of interfaces of the second client.
In one possible implementation, in response to no target interface corresponding to the first RPC request among the plurality of interfaces of the second client, the second client sends the hint information to the first client through the target communication link. The prompt information is used for prompting the first client, and a target interface corresponding to the first RPC request does not exist in the plurality of interfaces of the second client. In one possible implementation, the prompt may be an error message, and the prompt may include a possible reason for the error. By the method, the phenomenon of abnormal interruption of the information acquisition process caused by the absence of the called interface can be avoided, and the stability of the information acquisition process is high.
After the second client sends the prompt message to the first client through the target communication link, the first client receives the prompt message sent by the second client through the target communication link, and the prompt message is used for indicating that the second client does not have a target interface corresponding to the first RPC request. After receiving the prompt message, the first client may present the prompt message to inform the user that the first message was not successfully obtained. Exemplarily, in a scene that a user performs face brushing payment by using a self-service payment terminal, the prompt information may inform that the user fails to successfully acquire payment code information corresponding to the face of the user, so that the user performs face brushing or changes other payment modes again, and user experience is improved.
In step 305, the second client calls a target interface corresponding to the first RPC request to obtain the first information, and at least two interfaces of the plurality of interfaces of the second client multiplex a communication link.
The target interface is an interface for acquiring the first information. When a target interface corresponding to the first RPC request exists in the plurality of interfaces of the second client, the second client calls the target interface corresponding to the first RPC request to acquire first information.
Illustratively, for the case that the second client is a face client in the self-service payment terminal, in a scene that the user performs payment by using a face-brushing payment method, the first information is user payment code information. The process that the second client calls the target interface to acquire the first information is as follows: and the second client calls the target interface to identify the face of the user, determines a user account corresponding to the face of the user, and takes the payment code information corresponding to the user account as the first information.
It should be noted that, the interfaces of the first client and the second client communicate with each other through the communication link. Therefore, for the second client, at least two of the plurality of interfaces of the second client also multiplex a communication link to ensure efficient communication with the interface of the first client. It should be noted that any interface in the first client and the interface to be called in the second client corresponding to the interface correspond to the same communication link.
In a possible implementation manner, when a plurality of interfaces of the first client all multiplex the target communication link, a plurality of interfaces to be called in the second client corresponding to the respective interfaces of the first client also all multiplex the target communication link.
For example, the process of the second client calling the target interface to obtain the first information may be as shown in fig. 4. In fig. 4, the merchant client 41 is a first client, and the face client 42 is a second client. The merchant client 41 is a client in the RPC communication process, and the face client 42 is a server in the RPC communication process. The interface 1 and the interface 2 of the merchant client multiplex a target communication link, and the interface 1 and the interface 2 of the face client multiplex the target communication link. The interface 1 of the merchant client can receive an instruction for acquiring user identity information, and the interface 2 of the merchant client can receive an instruction for acquiring user payment code information. Interface 1 and interface 2 of the merchant client can both be used as the first interface.
Assuming that the information currently required to be acquired is user identity information, the interface 1 of the merchant client is used as a first interface. After receiving an instruction for acquiring user identity information through the interface 1, the merchant client converts the instruction into a first command word, where the first command word may be represented as cmd: gettuserinfo. Assuming that the information which needs to be acquired currently is user payment code information, the interface 2 of the merchant client is used as a first interface. After receiving an instruction for acquiring user payment code information through the interface 2, the merchant client converts the instruction into a first command word, wherein the first command word can be represented as cmd: getfacecode.
After the merchant client obtains the first command word, a first RPC request including the first command word is generated. After the first RPC request is generated, the merchant client sends the first RPC request to the face client through the target communication link. After receiving the first RPC request, the face client analyzes the first RPC request to obtain a first command word. And then determining a target interface according to the mapping relation between the command word and the interface. It is assumed that the mapping of the command word and the interface indicates that the command word cmd: gettuserinfo has a mapping with interface 1 and the command word cmd: getfacecode has a mapping with interface 2. When the first command word is cmd: gettuserinfo, the interface 1 is a target interface, and the face client calls the interface 1 to acquire the user identity information, so that the face client acquires the first information; when the first command word is cmd: getfacecode, the interface 2 is a target interface, and the face client calls the interface 2 to acquire the face payment code information of the user, so that the face client acquires the first information. In the embodiment of the application, a high-availability compatibility processing mechanism is provided by a mode that at least two interfaces multiplex a bottom layer of communication link, and user experience is improved.
In step 306, the second client converts the first information into a second command word, and sends the second command word to the first client through the target communication link.
And after calling the target interface to acquire the first information, the second client converts the first information into a second command word so as to be transmitted in the target communication link. The second command word corresponds to the first information, and both of them have the same meaning by different expressions.
In one possible implementation, the manner in which the second client converts the first information into the second command word includes, but is not limited to, the following two:
the first method is as follows: and the second client converts the first information into a second command word based on a second conversion mode.
In this manner, the underlying layer of the second client may store a second conversion scheme for converting information into command words. The second conversion mode may be formulated by a developer of the second client, or may be freely adjusted according to an actual application scenario, which is not limited in the embodiment of the present application. The second client may automatically convert the first information into the second command word at the bottom layer based on the second conversion manner.
The second conversion method may be the same as or different from the first conversion method, and this is not limited in the embodiments of the present application.
The second method comprises the following steps: the first client inquires a second command word corresponding to the first information based on the corresponding relation between the information and the command word, and then converts the first information into the second command word.
After converting the first information into the second command word, the second client sends the second command word to the first client through the target communication link.
In step 307, the first client receives the second command word sent by the second client through the target communication link, and converts the second command word into the first information.
After the second client sends the second command word to the first client through the target communication link, the first client receives the second command word through the target communication link and then converts the second command word into first information which can be directly utilized.
In one possible implementation, the manner in which the first client converts the second command word into the first information includes, but is not limited to, the following two:
the first method is as follows: and the first client converts the second command word into the first information based on the third conversion mode.
In this way, the bottom layer of the first client may store a third conversion means for converting the command word into information. The third conversion mode may be formulated by a developer of the first client according to a reverse process of converting information into command words, or may be freely adjusted according to an actual application scenario, which is not limited in the embodiment of the present application. The first client may automatically convert the second command word into the first information at the bottom layer based on the third conversion manner.
The second method comprises the following steps: the first client stores the corresponding relation between the information and the command word, queries the first information corresponding to the second command word based on the corresponding relation between the information and the command word, and then converts the second command word into the first information.
In a possible implementation manner, after the first client receives, through the target communication link, the second command word sent by the second client, the method further includes: and determining a second interface having a mapping relation with the second command word in the plurality of interfaces of the first client based on the mapping relation of the command word and the interfaces. The second interface having a mapping relationship with the second command word refers to an interface capable of utilizing the first information represented by the second command word. The second interface may be the same as or different from the first interface, and this is not limited in this application.
After determining the second interface and converting the second command word into the first information, the first client may feed back the first information to the second interface for the second interface to perform a subsequent process using the first information.
For example, assuming that the first information is user payment code information, the second interface may transfer funds from the user's account to the merchant's account using the user payment code information; assuming that the first information is user identity information, the second interface may verify the identity of the user using the user identity information.
In a possible implementation manner, in a scenario of performing a face-brushing payment by using a self-service payment terminal, the implementation code of the process of acquiring the first information may be as follows:
Figure BDA0002367473210000121
in the embodiment of the application, at least two interfaces multiplex the same communication link, in order to enable the multiplexed communication link to be suitable for a plurality of interfaces, the instruction received from the interfaces is converted into the command word, and the RPC request including the command word is transmitted in the multiplexed communication link, so that the process is not limited by the interface version, the RPC request is guaranteed to reach a second client, the compatibility among the interfaces of different versions is improved, the phenomenon of abnormal interruption of the information acquisition process caused by different interface versions is reduced, and the stability of the information acquisition process is high.
Referring to fig. 5, an embodiment of the present application provides an information obtaining apparatus, which is applied to a first client, and implements functions performed by the first client in the information obtaining method in fig. 3 through the following modules shown in fig. 5. The device includes:
a receiving module 501, configured to receive a first instruction for obtaining first information through a first interface, where the first interface is any interface of multiple interfaces of a first client, and at least two interfaces of the multiple interfaces multiplex a communication link;
a conversion module 502 for converting the first instruction into a first command word;
a generating module 503 for generating a first remote procedure call, RPC, request comprising a first command word;
a sending module 504, configured to send the first RPC request to a second client through a target communication link multiplexed by the first interface, where the second client is configured to call a target interface corresponding to the first RPC request to obtain first information, convert the first information into a second command word, and send the second command word to the first client through the target communication link;
the receiving module 501 is further configured to receive a second command word sent by a second client through a target communication link;
the converting module 502 is further configured to convert the second command word into the first information.
In one possible implementation, referring to fig. 6, the apparatus further includes:
a determining module 505, configured to determine, based on a mapping relationship between the command word and the interface, a second interface having a mapping relationship with a second command word in the plurality of interfaces of the first client;
a feedback module 506, configured to feed back the first information to the second interface.
In a possible implementation manner, the receiving module 501 is further configured to receive, through the target communication link, a prompt message sent by the second client, where the prompt message is used to indicate that the second client does not have a target interface corresponding to the first RPC request;
referring to fig. 6, the apparatus further comprises:
and a display module 507 for displaying the prompt information.
In one possible implementation, the plurality of interfaces of the first client each multiplex the target communication link.
In the embodiment of the application, at least two interfaces multiplex the same communication link, in order to enable the multiplexed communication link to be suitable for a plurality of interfaces, the instruction received from the interfaces is converted into the command word, and the RPC request including the command word is transmitted in the multiplexed communication link, so that the process is not limited by the interface version, the RPC request is guaranteed to reach a second client, the compatibility among the interfaces of different versions is improved, the phenomenon of abnormal interruption of the information acquisition process caused by different interface versions is reduced, and the stability of the information acquisition process is high.
Referring to fig. 7, an embodiment of the present application further provides an information obtaining apparatus, which is applied to a second client, and the following modules shown in fig. 7 are used to implement the functions executed by the second client in the information obtaining method in fig. 3. The device includes:
a receiving module 701, configured to receive, through a target communication link, a first Remote Procedure Call (RPC) request sent by a first client, where the first RPC request includes a first command word;
an obtaining module 702, configured to call a target interface corresponding to the first RPC request to obtain first information, where at least two interfaces of the multiple interfaces of the second client multiplex a communication link;
a conversion module 703, configured to convert the first information into a second command word;
a sending module 704, configured to send the second command word to the first client through the target communication link.
In one possible implementation, the sending module 704 is further configured to send the hint information to the first client through the target communication link in response to no target interface corresponding to the first RPC request in the plurality of interfaces of the second client.
In a possible implementation manner, the obtaining module 701 is further configured to parse the first RPC request to obtain a first command word;
referring to fig. 8, the apparatus further comprises:
the query module 705 is configured to query the first command word in the mapping relationship between the command word and the interface; responding to the fact that the mapping relation between the command word and the interfaces comprises the first command word, and a target interface corresponding to the first RPC request exists in the plurality of interfaces of the second client; and responding to the condition that the mapping relation between the command word and the interface does not comprise the first command word, and not having a target interface corresponding to the first RPC request in the plurality of interfaces of the second client.
In the embodiment of the application, at least two interfaces multiplex the same communication link, in order to enable the multiplexed communication link to be suitable for a plurality of interfaces, the instruction received from the interfaces is converted into the command word, and the RPC request including the command word is transmitted in the multiplexed communication link, so that the process is not limited by the interface version, the RPC request is guaranteed to reach a second client, the compatibility among the interfaces of different versions is improved, the phenomenon of abnormal interruption of the information acquisition process caused by different interface versions is reduced, and the stability of the information acquisition process is high.
It should be noted that, when the apparatus provided in the foregoing embodiment implements the functions thereof, only the division of the functional modules is illustrated, and in practical applications, the functions may be distributed by different functional modules according to needs, that is, the internal structure of the apparatus may be divided into different functional modules to implement all or part of the functions described above. In addition, the apparatus and method embodiments provided by the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments for details, which are not described herein again.
The first client and the second client related to the above technical solution may be installed in a terminal, and fig. 9 is a schematic structural diagram of a terminal provided in an embodiment of the present application. The terminal may be: a smart phone, a tablet computer, a self-service payment terminal, a notebook computer or a desktop computer. A terminal may also be referred to by other names such as user equipment, portable terminal, laptop terminal, desktop terminal, etc.
Generally, a terminal includes: a processor 901 and a memory 902.
Processor 901 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and so forth. The processor 901 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 901 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 901 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed by the display screen. In some embodiments, the processor 901 may further include an AI (Artificial Intelligence) processor for processing computing operations related to machine learning.
Memory 902 may include one or more computer-readable storage media, which may be non-transitory. The memory 902 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in memory 902 is used to store at least one instruction for execution by processor 901 to implement the information acquisition methods provided by the method embodiments herein.
In some embodiments, the terminal may further include: a peripheral interface 903 and at least one peripheral. The processor 901, memory 902, and peripheral interface 903 may be connected by buses or signal lines. Various peripheral devices may be connected to the peripheral interface 903 via a bus, signal line, or circuit board. Specifically, the peripheral device includes: at least one of a radio frequency circuit 904, a touch display screen 905, a camera assembly 906, an audio circuit 907, a positioning assembly 908, and a power supply 909.
The peripheral interface 903 may be used to connect at least one peripheral related to I/O (Input/Output) to the processor 901 and the memory 902. In some embodiments, the processor 901, memory 902, and peripheral interface 903 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 901, the memory 902 and the peripheral interface 903 may be implemented on a separate chip or circuit board, which is not limited by this embodiment.
The Radio Frequency circuit 904 is used for receiving and transmitting RF (Radio Frequency) signals, also called electromagnetic signals. The radio frequency circuitry 904 communicates with communication networks and other communication devices via electromagnetic signals. The radio frequency circuit 904 converts an electrical signal into an electromagnetic signal to transmit, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 904 comprises: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and so forth. The radio frequency circuit 904 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocols include, but are not limited to: metropolitan area networks, various generation mobile communication networks (2G, 3G, 4G, and 5G), Wireless local area networks, and/or WiFi (Wireless Fidelity) networks. In some embodiments, the radio frequency circuit 904 may also include NFC (Near Field Communication) related circuits, which are not limited in this application.
The display screen 905 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display screen 905 is a touch display screen, the display screen 905 also has the ability to capture touch signals on or over the surface of the display screen 905. The touch signal may be input to the processor 901 as a control signal for processing. At this point, the display 905 may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, the display 905 may be one, disposed on the front panel of the terminal; in other embodiments, the number of the display panels 905 may be at least two, and the two display panels are respectively disposed on different surfaces of the terminal or are in a folding design; in still other embodiments, the display 905 may be a flexible display, disposed on a curved surface or on a folded surface of the terminal. Even more, the display screen 905 may be arranged in a non-rectangular irregular figure, i.e. a shaped screen. The Display panel 905 can be made of LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), and other materials.
The camera assembly 906 is used to capture images or video. Optionally, camera assembly 906 includes a front camera and a rear camera. Generally, a front camera is disposed at a front panel of the terminal, and a rear camera is disposed at a rear surface of the terminal. In some embodiments, the number of the rear cameras is at least two, and each rear camera is any one of a main camera, a depth-of-field camera, a wide-angle camera and a telephoto camera, so that the main camera and the depth-of-field camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize panoramic shooting and VR (Virtual Reality) shooting functions or other fusion shooting functions. In some embodiments, camera assembly 906 may also include a flash. The flash lamp can be a monochrome temperature flash lamp or a bicolor temperature flash lamp. The double-color-temperature flash lamp is a combination of a warm-light flash lamp and a cold-light flash lamp, and can be used for light compensation at different color temperatures.
Audio circuit 907 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals to the processor 901 for processing, or inputting the electric signals to the radio frequency circuit 904 for realizing voice communication. For the purpose of stereo sound collection or noise reduction, a plurality of microphones can be arranged at different parts of the terminal respectively. The microphone may also be an array microphone or an omni-directional pick-up microphone. The speaker is used to convert electrical signals from the processor 901 or the radio frequency circuit 904 into sound waves. The loudspeaker can be a traditional film loudspeaker or a piezoelectric ceramic loudspeaker. When the speaker is a piezoelectric ceramic speaker, the speaker can be used for purposes such as converting an electric signal into a sound wave audible to a human being, or converting an electric signal into a sound wave inaudible to a human being to measure a distance. In some embodiments, audio circuit 907 may also include a headphone jack.
The positioning component 908 is used to locate the current geographic Location of the terminal to implement navigation or LBS (Location Based Service). The Positioning component 908 may be a Positioning component based on the GPS (Global Positioning System) in the united states, the beidou System in china, the graves System in russia, or the galileo System in the european union.
The power supply 909 is used to supply power to each component in the terminal. The power source 909 may be alternating current, direct current, disposable or rechargeable. When power source 909 comprises a rechargeable battery, the rechargeable battery may support wired or wireless charging. The rechargeable battery may also be used to support fast charge technology.
In some embodiments, the terminal also includes one or more sensors 910. The one or more sensors 910 include, but are not limited to: acceleration sensor 911, gyro sensor 912, pressure sensor 913, fingerprint sensor 914, optical sensor 915, and proximity sensor 916.
The acceleration sensor 911 may detect the magnitude of acceleration on three coordinate axes of a coordinate system established with the terminal. For example, the acceleration sensor 911 may be used to detect the components of the gravitational acceleration in three coordinate axes. The processor 901 can control the touch display 905 to display the user interface in a landscape view or a portrait view according to the gravitational acceleration signal collected by the acceleration sensor 911. The acceleration sensor 911 may also be used for acquisition of motion data of a game or a user.
The gyroscope sensor 912 can detect the body direction and the rotation angle of the terminal, and the gyroscope sensor 912 and the acceleration sensor 911 cooperate to acquire the 3D motion of the user on the terminal. The processor 901 can implement the following functions according to the data collected by the gyro sensor 912: motion sensing (such as changing the UI according to a user's tilting operation), image stabilization at the time of photographing, game control, and inertial navigation.
The pressure sensor 913 may be disposed at a side frame of the terminal and/or at a lower layer of the touch display 905. When the pressure sensor 913 is disposed on the side frame of the terminal, the user's holding signal to the terminal may be detected, and the processor 901 performs left-right hand recognition or shortcut operation according to the holding signal collected by the pressure sensor 913. When the pressure sensor 913 is disposed at a lower layer of the touch display 905, the processor 901 controls the operability control on the UI interface according to the pressure operation of the user on the touch display 905. The operability control comprises at least one of a button control, a scroll bar control, an icon control and a menu control.
The fingerprint sensor 914 is used for collecting a fingerprint of the user, and the processor 901 identifies the user according to the fingerprint collected by the fingerprint sensor 914, or the fingerprint sensor 914 identifies the user according to the collected fingerprint. Upon recognizing that the user's identity is a trusted identity, processor 901 authorizes the user to perform relevant sensitive operations including unlocking the screen, viewing encrypted information, downloading software, paying, and changing settings, etc. The fingerprint sensor 914 may be disposed on the front, back, or side of the terminal. When a physical key or vendor Logo is provided on the terminal, the fingerprint sensor 914 may be integrated with the physical key or vendor Logo.
The optical sensor 915 is used to collect ambient light intensity. In one embodiment, the processor 901 may control the display brightness of the touch display 905 based on the ambient light intensity collected by the optical sensor 915. Specifically, when the ambient light intensity is high, the display brightness of the touch display screen 905 is increased; when the ambient light intensity is low, the display brightness of the touch display screen 905 is turned down. In another embodiment, the processor 901 can also dynamically adjust the shooting parameters of the camera assembly 906 according to the ambient light intensity collected by the optical sensor 915.
A proximity sensor 916, also known as a distance sensor, is typically provided on the front panel of the terminal. The proximity sensor 916 is used to collect the distance between the user and the front face of the terminal. In one embodiment, when the proximity sensor 916 detects that the distance between the user and the front face of the terminal gradually decreases, the processor 901 controls the touch display 905 to switch from the bright screen state to the dark screen state; when the proximity sensor 916 detects that the distance between the user and the front surface of the terminal gradually becomes larger, the processor 901 controls the touch display 905 to switch from the breath screen state to the bright screen state.
Those skilled in the art will appreciate that the configuration shown in fig. 9 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components may be used.
In an exemplary embodiment, a computer device is also provided, see fig. 10, comprising a processor 1001 and a memory 1002, the memory 1002 having at least one program code stored therein. The at least one program code is loaded and executed by one or more processors 1001 to implement any of the above-described information acquisition methods.
In an exemplary embodiment, there is also provided a computer-readable storage medium having at least one program code stored therein, the at least one program code being loaded and executed by a processor of a computer device to implement any of the above-mentioned information acquisition methods.
Alternatively, the computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a Compact Disc Read-Only Memory (CD-ROM), a magnetic tape, a floppy disk, an optical data storage device, and the like.
It should be understood that reference to "a plurality" herein means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
The above description is only exemplary of the present application and should not be taken as limiting the present application, and any modifications, equivalents, improvements and the like that are made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims (15)

1. An information acquisition method, characterized in that the method comprises:
a first client receives a first instruction for acquiring first information through a first interface, wherein the first interface is any interface in a plurality of interfaces of the first client, and at least two interfaces in the plurality of interfaces multiplex a communication link;
the first client converts the first instruction into a first command word and generates a first Remote Procedure Call (RPC) request comprising the first command word;
the first client sends the first RPC request to a second client through a target communication link multiplexed by the first interface, the second client is used for calling a target interface corresponding to the first RPC request to acquire the first information, converting the first information into a second command word, and sending the second command word to the first client through the target communication link;
and the first client receives the second command word sent by the second client through the target communication link, and converts the second command word into the first information.
2. The method of claim 1, wherein after the first client receives the second command word sent by the second client over the target communication link, the method further comprises:
the first client determines a second interface having a mapping relation with the second command word in the plurality of interfaces of the first client based on the mapping relation of the command word and the interface;
after said converting the second command word to the first information, the method further comprises:
and the first client feeds the first information back to the second interface.
3. The method of claim 1, further comprising:
the first client receives prompt information sent by the second client through the target communication link, wherein the prompt information is used for indicating that a target interface corresponding to the first RPC request does not exist in the second client;
and the first client displays the prompt message.
4. The method of any of claims 1-3, wherein a plurality of interfaces of the first client each multiplex the target communication link.
5. An information acquisition method, characterized in that the method comprises:
the method comprises the steps that a second client receives a first Remote Procedure Call (RPC) request sent by a first client through a target communication link, wherein the first RPC request comprises a first command word;
the second client calls a target interface corresponding to the first RPC request to acquire first information, and at least two interfaces in the plurality of interfaces of the second client multiplex a communication link;
and the second client converts the first information into a second command word and sends the second command word to the first client through the target communication link.
6. The method of claim 5, further comprising:
and responding to the fact that a target interface corresponding to the first RPC request does not exist in the plurality of interfaces of the second client, and the second client sends prompt information to the first client through the target communication link.
7. The method of claim 5 or 6, wherein after the second client receives the first Remote Procedure Call (RPC) request sent by the first client through the target communication link, the method further comprises:
the second client analyzes the first RPC request to obtain the first command word;
the second client inquires the first command word in the mapping relation between the command word and the interface;
responding to the first command word in the mapping relation between the command word and the interfaces, wherein a target interface corresponding to the first RPC request exists in a plurality of interfaces of the second client;
and responding to the condition that the mapping relation between the command word and the interface does not comprise the first command word, wherein a target interface corresponding to the first RPC request does not exist in the plurality of interfaces of the second client.
8. An information acquisition apparatus, characterized in that the apparatus comprises:
a receiving module, configured to receive a first instruction for obtaining first information through a first interface, where the first interface is any interface among multiple interfaces of the first client, and at least two interfaces of the multiple interfaces multiplex a communication link;
a conversion module for converting the first instruction into a first command word;
a generation module to generate a first remote procedure call, RPC, request including the first command word;
the sending module is used for sending the first RPC request to a second client through a target communication link multiplexed by the first interface, the second client is used for calling a target interface corresponding to the first RPC request to obtain the first information, converting the first information into a second command word, and sending the second command word to the first client through the target communication link;
the receiving module is further configured to receive the second command word sent by the second client through the target communication link;
the conversion module is further configured to convert the second command word into the first information.
9. The apparatus of claim 8, further comprising:
a determining module, configured to determine, based on a mapping relationship between a command word and an interface, a second interface having a mapping relationship with the second command word from among the plurality of interfaces of the first client;
and the feedback module is used for feeding back the first information to the second interface.
10. The apparatus of claim 8, wherein the receiving module is further configured to receive a hint message sent by the second client over the target communication link, the hint message indicating that the second client does not have a target interface corresponding to the first RPC request;
the device further comprises:
and the display module is used for displaying the prompt information.
11. An information acquisition apparatus, characterized in that the apparatus comprises:
the Remote Procedure Call (RPC) system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving a first RPC request sent by a first client through a target communication link, and the first RPC request comprises a first command word;
the acquisition module is used for calling a target interface corresponding to the first RPC request to acquire first information, and at least two interfaces in the plurality of interfaces of the second client multiplex a communication link;
the conversion module is used for converting the first information into a second command word;
a sending module, configured to send the second command word to the first client through the target communication link.
12. The apparatus of claim 11, wherein the sending module is further configured to send a hint information to the first client over the target communication link in response to an absence of a target interface of the plurality of interfaces of the second client that corresponds to the first RPC request.
13. The apparatus according to claim 11 or 12, wherein the obtaining module is further configured to parse the first RPC request to obtain the first command word;
the device further comprises:
the query module is used for querying the first command word in the mapping relation between the command word and the interface; responding to the first command word in the mapping relation between the command word and the interfaces, wherein a target interface corresponding to the first RPC request exists in a plurality of interfaces of the second client; and responding to the condition that the mapping relation between the command word and the interface does not comprise the first command word, wherein a target interface corresponding to the first RPC request does not exist in the plurality of interfaces of the second client.
14. A computer device comprising a processor and a memory, the memory having stored therein at least one program code, the at least one program code being loaded and executed by the processor to implement the information acquisition method as claimed in any one of claims 1 to 4 or the information acquisition method as claimed in any one of claims 5 to 7.
15. A computer-readable storage medium having stored therein at least one program code, the at least one program code being loaded and executed by a processor, to implement the information acquisition method according to any one of claims 1 to 4, or the information acquisition method according to any one of claims 5 to 7.
CN202010040223.6A 2020-01-15 2020-01-15 Information acquisition method, device, equipment and storage medium Pending CN113127224A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010040223.6A CN113127224A (en) 2020-01-15 2020-01-15 Information acquisition method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010040223.6A CN113127224A (en) 2020-01-15 2020-01-15 Information acquisition method, device, equipment and storage medium

Publications (1)

Publication Number Publication Date
CN113127224A true CN113127224A (en) 2021-07-16

Family

ID=76771421

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010040223.6A Pending CN113127224A (en) 2020-01-15 2020-01-15 Information acquisition method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113127224A (en)

Similar Documents

Publication Publication Date Title
CN112312226B (en) Wheat connecting method, system, device, electronic equipment and storage medium
CN110674022A (en) Behavior data acquisition method and device and storage medium
CN111324259A (en) Group creation method, device and storage medium
CN110705983A (en) Code scanning payment processing method, device, equipment and storage medium
CN113204298A (en) Method and device for displaying release progress, electronic equipment and storage medium
CN113190362B (en) Service calling method and device, computer equipment and storage medium
CN112764608A (en) Message processing method, device, equipment and storage medium
CN110290191B (en) Resource transfer result processing method, device, server, terminal and storage medium
CN111523878A (en) Service processing method, device, system and storage medium
CN109783176B (en) Page switching method and device
CN111064657B (en) Method, device and system for grouping concerned accounts
CN109413190B (en) File acquisition method and device, electronic equipment and storage medium
CN111881423A (en) Method, device and system for limiting function use authorization
CN109033473B (en) Picture sharing method and device and computer readable storage medium
CN111047328A (en) Mobile payment method, device, system and storage medium
CN111258683A (en) Detection method, detection device, computer equipment and storage medium
CN111008083A (en) Page communication method and device, electronic equipment and storage medium
CN110971692B (en) Method and device for opening service and computer storage medium
CN111580892B (en) Method, device, terminal and storage medium for calling service components
CN113051015A (en) Page rendering method and device, electronic equipment and storage medium
CN114385939A (en) Application display method, application display system, application display device and application display equipment
CN113127224A (en) Information acquisition method, device, equipment and storage medium
CN112988254A (en) Method, device and equipment for managing hardware equipment
CN111741040A (en) Connection establishing method, address obtaining method, device, equipment and storage medium
CN111414563B (en) Webpage interaction method, device, computer equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 40047923

Country of ref document: HK

SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination