CN111147363A - Method and system for transferring third party application information in a message exchange session - Google Patents

Method and system for transferring third party application information in a message exchange session Download PDF

Info

Publication number
CN111147363A
CN111147363A CN202010119259.3A CN202010119259A CN111147363A CN 111147363 A CN111147363 A CN 111147363A CN 202010119259 A CN202010119259 A CN 202010119259A CN 111147363 A CN111147363 A CN 111147363A
Authority
CN
China
Prior art keywords
party application
user
account
server
message exchange
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.)
Granted
Application number
CN202010119259.3A
Other languages
Chinese (zh)
Other versions
CN111147363B (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.)
Tianjin Yinben Fruitful Enterprise Management Consulting Partnership LP
Original Assignee
Tianjin Yinben Fruitful Enterprise Management Consulting Partnership LP
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 Tianjin Yinben Fruitful Enterprise Management Consulting Partnership LP filed Critical Tianjin Yinben Fruitful Enterprise Management Consulting Partnership LP
Priority to CN202010119259.3A priority Critical patent/CN111147363B/en
Publication of CN111147363A publication Critical patent/CN111147363A/en
Priority to PCT/CN2020/121052 priority patent/WO2021169320A1/en
Application granted granted Critical
Publication of CN111147363B publication Critical patent/CN111147363B/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
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/07User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
    • H04L51/18Commands or executable codes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04Real-time or near real-time messaging, e.g. instant messaging [IM]
    • H04L51/046Interoperability with other network applications or services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0884Network architectures or network communication protocols for network security for authentication of entities by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/06Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • 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/53Network services using third party service providers

Abstract

The present disclosure relates to methods and systems for communicating third party application information in a message exchange application. The method comprises the following steps: invoking an input method in a message exchange client on a first computing device; after a user activates an interface module of a third-party application in an input method, detecting whether an account associated with the user is an account authenticated by a server of the third-party application, and if the account is authenticated, receiving account exchange data from the user in the interface module; sending a structured string corresponding to the account exchange data to a second message exchange client at a second computing device, the structured string configured to be selectable by a second user at the second message exchange client to send to the server. The method enables information exchange between different user accounts in a third-party application to be performed indirectly through a message exchange session without starting or invoking the third-party application client on the computing device.

Description

Method and system for transferring third party application information in a message exchange session
Technical Field
The present invention relates to computer technology for message exchange between different applications, and more particularly to a technology for constructing third-party application information for transfer in a session between message exchange clients via an input method.
Background
With the rapid development of computer technology and communication technology, instant messaging plays an increasingly important role in people's daily life, study and work. How to conveniently transfer application software-specific data of a third party in addition to natural language communication between users in clients of various message exchange applications including instant messaging in the mobile communication era. Increasingly becoming a challenge.
In some existing implementations, in order to send specific account exchange information (e.g., financial transactions related to an account) related to a user account in a third-party software application to other participants in a chat session through instant messaging software, the third-party software application is first installed on a device of an initiator, and the initiator is required to customize specific transaction information in the third-party software application, and transaction data, which is usually a structured character string, is obtained from the third-party software application and then transferred to the session of the instant messaging software through a copy/paste function in an operating system, so as to be sent to other participants in the session. And the other participants need to extract the structured character strings through the paste/copy function of the device system, open the corresponding third-party software application on the system (if the third-party software application is not installed, the third-party software application needs to be downloaded and installed first), and finally log in the own account in the third-party software application to finish the analysis of the structured character strings and finish the account transaction to be performed.
On the other hand, the application of the input method is more and more widespread for mobile devices. Even for various alphabetic languages, mobile devices without physical keyboards need to rely on an input method system to provide convenient and fast input functions for various characters and characters. However, in addition to providing rich input method functionality, current input method systems have difficulty facilitating the transfer of account transaction information from some third-party software application to other participants in a chat session, especially while they are engaged in an instant messaging chat.
Disclosure of Invention
In view of the above, embodiments of the present invention are directed to various specific methods and systems for communicating third party application information in a message exchange application via an input method application. In particular, a structured string associated with a third-party application is constructed by a particular functional module of the input method, and the constructed structured string is passed data relating to particular financial information in the account in a client communication session of the message exchange application.
One aspect of the disclosure relates to a computer-implemented method of communicating third party application information in a message exchange session, the method comprising: a) invoking, by a first computing device, an input method in a text entry field of a first message exchange client based on input from a first user, the first message exchange client operating on the first computing device and in communication with at least a second message exchange client operating on a second computing device; b) in response to the first user activating a representation of a third-party application in the input method, detecting whether a first account associated with the first user is a server-authenticated account of the third-party application; c) in response to determining that the first account associated with the first user has been authenticated by the server of the third-party application, receiving account exchange data from the first user in a third-party application interface module of the input method, the third-party application interface module in communication with the server of the third-party application, the account exchange data associated with account information registered by the first user in the server of the third-party application; and d) sending, by the first computing device, a structured string corresponding to the account exchange data to the second message exchange client operating at least at the second computing device via the first message exchange client, the structured string displayed at the second message exchange client configured to be selectable by a second user at the second message exchange client to send to the server of the third party application.
Wherein detecting whether the first account associated with the first user is a server-authenticated account of the third-party application may comprise: submitting information of a first account associated with the first user to a server of the third-party application to determine whether the first account has been previously registered at the server of the third-party application and whether the first account is currently in a logged-in state at the server of the third-party application.
In another aspect, the method may further comprise: in the event that the first account has previously registered at a server of the third party application but is currently in an unregistered state, marking the first account as a logged in state.
In another aspect, the method may further comprise: in response to determining that the first account has not been previously registered at the server of the third-party application, presenting, via the third-party application interface module, the first user with a page confirming that the first account is registered in the server of the third-party application.
Wherein detecting whether the first account associated with the first user is a server-authenticated account of the third-party application may comprise: detecting whether a client of the third-party application is installed on the first computing device, and displaying a prompt page to the first user to guide the first user to download and install the client of the third-party application under the condition that the client of the third-party application is not installed on the first computing device.
Wherein the first account associated with the first user may be an account of the first user in the input method.
Wherein the representation of the third-party application may include an activatable icon displayed at an interface of the input method, a predefined string submitted by the user in the input method, and a predefined gesture entered by the user in the input method,
the message exchange application may include an instant messaging application, an email application, and a short message application, among others.
Wherein the structured string corresponding to the account exchange data may be generated by the third party application interface module and may further be encoded with information of a client that launches or installs the third party application.
In another aspect, the method may further comprise: after receiving the account exchange data from the first user and before sending the structured string corresponding to the account exchange data to the second message exchange client, sending, by the third-party application interface module, the account exchange data to a server of the third-party application for account data processing associated with the first account, and receiving, from the server of the third-party application, the processed structured string corresponding to the account exchange data, the structured string further encoding information of a client that launches or installs the third-party application.
In another aspect, the method may further comprise: e) in response to selection by the second user of the structured string displayed at the second message exchange client, sending, by a second message exchange client operating at the second computing device, the structured string to the server of the third-party application for account data exchange processing associated with the second account of the second user, including opening, via a browser, a url address contained in the structured string that points to a server of a third-party application for data exchange with the server of the third-party application.
In another aspect, the method may further comprise: e) in response to selection by the second user of the structured string displayed at the second message exchange client, copying the structured string and passing the copied structured string to a corresponding third-party application interface module in a corresponding input method that contains the interface module corresponding to the third-party application by activating the corresponding input method at the second computing device, such that the structured string can be passed to a server of the third-party application via the third-party application interface module for account data exchange processing associated with the second account of the second user.
Wherein the third party application may comprise a red envelope application and the account exchange data received from the first user may comprise red envelope amount data issued by the first user using the first account registered at the red envelope application.
Yet another aspect of the present disclosure relates to a computing device for communicating third party application information in a message exchange application, the device having installed thereon an input method and a first message exchange client, the computing device comprising one or more processors and a memory storing computer-executable instructions that, when executed by the one or more processors, perform operations comprising: a) invoking the input method in a text entry field of the first message exchange client based on input from a first user, the first message exchange client in communication with at least a second message exchange client operating on another computing device; b) in response to the first user activating a representation of a third-party application in the input method, detecting whether a first account associated with the first user is a server-authenticated account of the third-party application; c) in response to determining that the first account associated with the first user has been authenticated by the server of the third-party application, receiving account exchange data from the first user in a third-party application interface module of the input method, the third-party application interface module in communication with the server of the third-party application, the account exchange data associated with account information registered by the first user in the server of the third-party application; d) sending a structured string corresponding to the account exchange data via the first message exchange client to the second message exchange client operating at least at the other computing device, the structured string displayed at the second message exchange client configured to be selectable by a second user at the second message exchange client to send to the server of the third-party application.
Yet another aspect of the present disclosure is directed to a messaging system, comprising: the system comprises a third-party application server and first user equipment, wherein an input method and a first message exchange client are installed on the first user equipment, the input method comprises a third-party application interface module, and the third-party application interface module is configured to be capable of communicating with the third-party application server; and a second user device having a second message exchange client installed thereon, the second message exchange client configured to communicate with the first message exchange client; wherein the first user equipment is configured to: a) invoking an input method in a text entry field of the first message exchange client based on input from a first user; b) in response to the first user activating a representation of a third-party application in the input method, detecting whether a first account associated with the first user is an account authenticated by the third-party application server; c) in response to determining that the first account associated with the first user has been authenticated by the third-party application server, receiving account exchange data from the first user in the third-party application interface module of the input method, the account exchange data associated with account information registered by the first user in the third-party application server; d) sending a structured string corresponding to the account exchange data via the first message exchange client to the second message exchange client operating at the second computing device, the structured string displayed at the second message exchange client configured to be selectable by a second user at the second message exchange client to send to the third-party application server.
According to yet another aspect of embodiments of the present invention, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements a method provided according to embodiments of the present invention.
The method and the system for transmitting the third-party application information in the message exchange application enable information exchange between different user accounts in the third-party application to be indirectly carried out through the message exchange session without starting or calling a third-party application client on a computing device, and enable users of all parties participating in the message exchange session to conveniently download, install and register one or more specific third-party applications on corresponding computing devices.
Drawings
One or more embodiments of the present disclosure will be further explained by way of example, which will be described in detail with reference to the accompanying drawings. The embodiments are not intended to be limiting, and like numerals are used to designate like structures in the drawings, in which:
FIG. 1 is an exemplary system architecture diagram in which some embodiments described in this specification may be implemented.
FIG. 2 is an exemplary flow diagram of a method of communicating third party application information in a message exchange application via an input method, according to some embodiments of the present description;
FIG. 3 is an exemplary flow diagram of a method of processing upon receipt of third party application information in a message exchange application, according to some embodiments of the present description;
fig. 4A-4F are schematic screen shots of transmitting and receiving red packet information via an input method, according to some embodiments of the present description.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
In general, the system of the present disclosure may include at least two user devices and a third party application server. The two pieces of user equipment are respectively installed with the same kind of message exchange applications capable of communicating with each other, such message exchange applications typically include WeChat (WeChat), QQ App, Facebook Messenger, whatsApp, Telegram, line, Kakao Talk, Viber, Skype, Snapchat, LinkedIn, and so on, and alternatively, such message exchange applications may also be email applications or short message applications, such as short message applications installed on smart phones. In some cases, such message exchange applications may also be various browser-based web applications with message exchange functionality. In addition, an Input Method Editor (IME, hereinafter, abbreviated as an Input Method) is installed in at least one of the two user apparatuses. Conventional input methods can assist a user in entering a rich set of characters on an input interface of any application running on the operating system of the user device, which is often not directly available from the physical keyboard associated with the computing device. Moreover, the rich character input provided by the input method is particularly important for some mobile devices since they are not provided with a physical keyboard at all.
In the input method disclosed by the present disclosure, which is installed on one computing device in the system, a functional interface for interfacing with a third-party application is integrated, and the functional interface enables a user to directly communicate with a server of the third-party application through the functional interface in the input method, wherein the communication includes verifying whether the user belongs to a registered user or whether the user is in a login state, and the like. In addition, the functional interface also enables a user to send data processing requests to a server of the third-party application, including submitting specific data associated with the user's account for processing by the server platform of the third-party application, and returning processed string data having a specific format, submitted by the user through the input method editor to the message exchange session in which the user is currently participating. In this way, the user can directly transmit the structured string recognizable by the client and/or the server of the third-party application to at least another party in the message exchange session in which the user participates without starting or calling the client of the third-party application in the operating system on the computing device, so that the another party can perform subsequent account data exchange operation with the server of the third-party application based on the structured string received in the corresponding message exchange session.
In another embodiment, after the user activates the representation of the third-party application included in the input method on the computing device, the interface function integrated in the input method corresponding to the representation of the third-party application does not need to directly communicate with the background server of the third-party application, and the interface function can directly authenticate the current account login situation of the user in the third-party application based on the locally stored history of previous access of the interface function by the user. After authentication has passed, the interface function may further perform a preliminary review of the account exchange data provided by the user, which may include, for example, comparing a particular value contained in the account exchange data submitted by the user with threshold data. After the audit is passed, the interface function may further format the account exchange data to obtain a processed structured string and transmit the structured string to at least one other participant in the message exchange session in which it is participating.
FIG. 1 is an exemplary system architecture diagram in which some embodiments described in this specification may be implemented. As shown, the exemplary system includes at least a first computing device 110, a second computing device 120, and a third party application server 160. Alternatively, the system may further include a message exchange server 130 and an input method server 140. The various components in the system may communicate with each other over a network 150.
In the system of fig. 1, the first computing device 110 has installed thereon an operating system 111, and on the operating system 111 is installed a message exchange client 114 and an input method 116 into which is integrated a third party application interface module 118 that can interface with a client or server of a third party application. The third party application interface module 118 may be a set of SDKs embedded in the input method editor that make calls to specific functions of the third party application. Additionally, a third party application client 112 may already be installed on the first computing device 110. In some embodiments, the first computing device 110 may also have no client of the third-party application installed on it at the beginning of performing the steps described in the present disclosure, and the user may choose to install the third-party application client 112 during use. In addition, in the second computing device 120, the operating system 121 also runs a corresponding message exchange client 124, and users of the first computing device 110 and the second computing device 120 can perform instant messaging chat with each other through corresponding message exchange clients, such as WeChat or Line. Of course, these message exchanges are not limited to instant messaging. Email, short message applications can also implement the related functions in this disclosure. Third party application clients 122 may also have been installed on the second computing device 120 as well. In many embodiments, the second computing device 120 has no clients of the third-party application installed on it at the beginning of performing the steps described in this disclosure, and the user of the second computing device chooses to install the third-party application client 122 during use according to the prompt. In addition, the input method 126 may already be installed on the second computing device 120, or not. And the input method 126 may include a third party application interface module 128 or not. In summary, the user of each computing device can select a client for installing and running the relevant third-party application and/or an input method containing the third-party application according to the prompt of the system in the process of executing each step of the disclosure.
Fig. 2 is an exemplary flow diagram of a method of communicating third party application information in a message exchange application via an input method, according to some embodiments of the present description. The process may be implemented primarily in the first computing device 110 in fig. 1, for example. At block 202, a user invokes an input method, which may be part of a financial processing function in a personal banking application, from an operating system of a user device by parking focus in a text entry field in a message exchange client while participating in a message exchange session with other users. At block 204, an interface module with a third party application is activated in the input method interface based on user input, such as a user click. The user may also invoke a certain third party application integrated in the input method by entering a specific character combination in the input method, e.g. entering a character combination "%:", "% @", etc. In addition, the interface function of the third-party application of the input method can be called by setting a specific gesture input, such as a drawing line of a specific track or shape, on the input method function.
After the user activates the interface module with the third party application in the input method, the interface module first checks whether the user's account is authenticated in the server of the third party application (block 206). The checking act may first determine whether a user account associated with the user is already logged into the third party application. If so, determining that the user's account has been authenticated by the server may be followed by other business processes related to the third-party application. If the user is not already logged in, a prompt page is provided asking the user to first provide account information to log in to the third-party application to use the functionality of the third-party application integrated in the input method (block 208). If the user has not registered any user accounts with the third party application, the user is first required to register an account with the third party application, including providing new account information to a server of the third party application. The operation of registering a new account with the server can be completed by the interface function of the third-party application integrated in the input method, or the user can be guided to open the client of the third-party application in the operating system of the device and separately complete the registered program in the client. If the client is not installed, the user may also be first guided to download the client from the network address where the third party application client is stored, and then launch the client and register a new account thereon. In some embodiments, the login information recorded by the user in the input method application on the device may be used to register the new account with the server of the third party application when registering the new account. For example, the user name and password used by the user in the input method application may be directly used as the user name and password when the user newly registers for an account at the third-party application. In some implementations, the user's account login information at the input method may be associated with the account login information at the third-party application such that the user, when single-sign-on into his user account in the input method, may associatively simultaneously log-in into his associated user account at the third-party application. In this way, when the user subsequently opens the functional interface of the third-party application in the input method, the user can be directly verified as being authenticated at the server of the third-party application, so that the user can directly perform business operation associated with the account information in the interface module of the third-party application of the input method.
In some embodiments, if it is detected that a client of the third party application is not already installed on the user device, a prompt page may first be displayed to the user at block 204 or block 206 to guide the user to download the client from the specified network address and install onto the user device (block 205). However, as mentioned above, since some front-end function modules of the third-party application are integrated into the input method, the user can actually perform some operations on his account in the third-party application directly in the input method interface, and therefore, the above steps of downloading and installing the client are not necessary.
In some embodiments, if the interface module of the third-party application or a subsequent server thereof initially determines that there has been no user account login information associated with the computing device when the user activates the interface function of the third-party application in the input method, then an account information associated with the user (such as the user's account information in the input method) is submitted to the server of the third-party application to determine whether the account has been previously registered at the server of the third-party application based on the account information. If the account is a registered account but the account is currently in an unregistered state, the state of the user account may be set to logged in and the business operations under the user account from the user device may be allowed. If the user account has not been registered, the user may be presented with a page confirming that the user account is registered in the server of the third party application to in effect perform the creation and association of the user account in two different applications.
Upon confirming that the user has logged into the third party application, specific account exchange data relating to the user's account may then be received from the user in an interface module of the third party application in an import method. Such account exchange data may be, for example, data specifying that a particular amount is subtracted from a balance in a financial account opened by the user at the third party application, or an increase or decrease in any virtual incentives associated with the user account, or the like. Any substantive or virtual asset or other incentive measure that can freely flow between different user accounts at the third party application based on the user's desire may be the subject of such account exchange data. Of course, such account exchange data may also more broadly include other various data exchanges between different user accounts in the same application.
A structured string corresponding to the account exchange data is then generated by an interface module of the third party application in the input method based on the account exchange data received from the user and sent to a message exchange client used by another user at another device via a message exchange session (block 212). Such a structured string may be generated by the interface module of the third party application itself, which the input method comprises. Alternatively, upon receiving account exchange data from the user, the interface module of the third-party application in the input method may send the account exchange data to a server of the third-party application for data transaction processing associated with the user account of the user, the processing including generating a structured string based on the account exchange data and sending the structured string back to the user device, for receipt by the interface module of the third-party application in the input method, and further for submission by the user to an input field in the message exchange application client for sending by the user to the other party participating in the session. Alternatively, the generated structured string may also be encoded with information of the client that initiated or installed the third party application. The structured string may be configured in advance when sent to another party in the message exchange session so that another user as a recipient can select the structured string for subsequent operations.
Fig. 3 is an exemplary flow diagram of a method of processing upon receipt of third party application information in a message exchange application, according to some embodiments of the present description. When a structured string applicable to a third-party application is received from another participant in the message exchange session (block 302), the user as the other participant may select the structured string by clicking on it in the message exchange session, or the like (block 304). Selection of the structured string by the user may trigger an operation associated with the structured string, including sending all or part of the structured string to a network address of a server embedded in the structured string that is indicative of a third party application (block 314), e.g., opening a url address contained in the structured string that points to the server of the third party application via http or any other suitable protocol in a browser for data exchange with the server of the third party application. Alternatively, if the same input method has been installed and enabled on the user device as the other participant as on the device at the sender of the structured string, the user as the recipient may also directly copy the structured string and pass the copied structured string to the corresponding third party application interface module in the input method by activating the input method, so that the structured string may be passed to the server of the third party application via the third party application interface module and further processed.
In some implementations, before sending the structured string to a server for processing, it is first determined whether a client of the third-party application is already installed on the user device based on an identifier included in the structured string that identifies the third-party application (block 306). If such a client is not already installed on the user device, a prompt is provided to guide the user to download and install the client of the third party application from the specified network address on the device. Wherein the specified network address may be embedded separately in the structured string received by the message exchange session or may be from the same network address as the server of the third party application. After the user downloads and installs the client, the client of the third party application may be prompted to open and register a new user therein (block 308). The user may also choose to log directly into the account if the user has already registered the user account at the server of the third party application through other means.
If the user device has such a client installed, a further determination is made as to whether the third party application client on the device is in a logged on state (block 310). If the client is not logged in, the user is prompted to log in (block 312). If the client is already in the logged-on state, the structured string received in the message exchange session is directly sent to the server of the third party application for data exchange processing associated with the logged-on account (block 314). The server can analyze the structured character string, extract account information, service transaction information and the like of an original sender from the structured character string, and add related service transaction information into a related account of a receiver, and finally complete one-time account transaction service processing related to two users at a server applied by a third party.
Fig. 4A-4F are schematic screen shots of transmitting and receiving red packet information via an input method, according to some embodiments of the present description. As shown in fig. 4A, an input method is called in an input interface bar of the instant messaging session, and the called input method includes a shortcut button of a red packet function, and a user can conveniently click the red packet function on an interface of the input method, so as to call a function interface related to red packet issue. Because the interface functions related to the red envelope are integrated in the input method interface, a user does not need to firstly search and open a separate third-party application client supporting the red envelope function on a desktop under the system environment, thereby avoiding complex switching and copying operations. Through the red envelope shortcut entry arranged on the input method interface, the user can conveniently send the red envelope to friends when chatting with the friends. As shown in fig. 4E and 4F, such a red envelope is sent to the other party through the chat window in the form of a formatted string, where fig. 4E shows that the structured string completed has been submitted to the text edit bar of the instant messaging application by the input method, and fig. 4F shows that the structured string has been submitted to the currently ongoing messaging conversation, so that other participants of the conversation can instantly see the message and potentially take responsive action, such as clicking on the structured string, to extract the information contained therein, including a link in the structured string to the server processing interface of the third party application.
When the user clicks the red packet function on the input method interface, if the user of the input method does not log in the user account of the third-party application related to the red packet application, the red packet function firstly prompts the user to log in. Such login can be performed quickly by means of the mobile phone number and the verification code of the user, as shown in fig. 4B. After the user successfully logs in, the user is further prompted to perform the red package operation, as shown in fig. 4C. If the mobile phone number of the user is not the current registered user in the third-party application, the red packet function can prompt the user to register to the server of the third-party application at first, for example, prompt the user to download the client of the third-party application and register through the client.
FIG. 4D shows the generation of a structured string. After the user inputs a specific digital packet and a red packet is well, the red packet function in the input method further converts the red packet related information input by the user into a string of structured character strings, and the character strings at least comprise the amount of the red packet, the related address of the server interface of the third-party application for processing the red packet data, and other characters. As described above, the generation of such a structured character string may be completed by the red packet function module itself included in the input method on the user equipment, or the red packet function module may send information such as the amount of money of the red packet, the user ID for creating the red packet, and the like to the server of the third party application, and the server of the third party application returns the created structured character string corresponding to the submitted red packet information and submits the created structured character string to the chat session currently in progress of the user through the input method. In the case where the red packet function module included in the input method itself generates the structured character string, the red packet data information is not actually processed by the server of the third-party application, that is, the corresponding financial account information of the user is not subtracted, and this step is postponed until the user who receives the red packet clicks the red packet and then processes the same. In this case, although there is a risk of consistency of the financial accounts of the users to some extent, the process of the users packing the red packages is also made more convenient because there is no need to communicate with the server.
On the other hand, when another user participating in the chat session receives the red envelope, the received red envelope connection may be clicked. If the user's device does not already have a third party application installed on it that is capable of receiving the red envelope, the user may be prompted to install a client for such third party application. If the client is installed on the equipment of the user, the service function of the third-party application can be automatically called when the user clicks the received structured character string, so that the client of the third-party application can automatically receive the red packet and send the received red packet data to the server of the third-party application, and the server automatically transfers the red packet amount to the corresponding financial account of the user. If the user has not logged into the third-party application when clicking the red envelope link, the user may first be prompted to log in.
In summary, the input method system provided according to various embodiments of the present invention facilitates the release of third-party applications by compactly embedding certain major front-end functionality of such third-party applications in an input method interface, and alternatively, leveraging some incentive mechanisms that such third-party applications can provide, such that users of input methods are more easily exposed to particular functionality of such third-party applications and are willing to install clients of such third-party applications.
In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via a communication interface, and/or installed from a removable medium. The computer program performs the above-described functions defined in the system of the present invention when executed by a Central Processing Unit (CPU).
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor includes a determination module, a selection module, a presentation module, and a display module. Where the names of these modules do not in some cases constitute a limitation on the module itself, for example, a determination module may also be described as a "module that determines an online recipient list".
The above-described embodiments should not be taken as limiting the scope of protection which is set forth in the following claims. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present disclosure should be included in the protection scope of the technical solution to which the present disclosure relates.

Claims (16)

1. A computer-implemented method of communicating third party application information in a message exchange session, comprising:
a) invoking, by a first computing device, an input method in a text entry field of a first message exchange client based on input from a first user, the first message exchange client operating on the first computing device and in communication with at least a second message exchange client operating on a second computing device;
b) in response to the first user activating a representation of a third-party application in the input method, detecting whether a first account associated with the first user is a server-authenticated account of the third-party application;
c) in response to determining that the first account associated with the first user has been authenticated by the server of the third-party application, receiving account exchange data from the first user in a third-party application interface module of the input method, the third-party application interface module in communication with the server of the third-party application, the account exchange data associated with account information registered by the first user in the server of the third-party application;
d) sending, by the first computing device, a structured string corresponding to the account exchange data to the second message exchange client operating at least at the second computing device via the first message exchange client, the structured string displayed at the second message exchange client configured to be selectable by a second user at the second message exchange client to send to the server of the third-party application.
2. The method of claim 1, wherein detecting whether the first account associated with the first user is a server-authenticated account of the third-party application comprises:
submitting information of a first account associated with the first user to a server of the third-party application to determine whether the first account has been previously registered at the server of the third-party application and whether the first account is currently in a logged-in state at the server of the third-party application.
3. The method of claim 2, further comprising: in the event that the first account has previously registered at a server of the third party application but is currently in an unregistered state, marking the first account as a logged in state.
4. The method of claim 2, further comprising: in response to determining that the first account has not been previously registered at the server of the third-party application, presenting, via the third-party application interface module, the first user with a page confirming that the first account is registered in the server of the third-party application.
5. The method of claim 1, wherein detecting whether the first account associated with the first user is a server-authenticated account of the third-party application comprises:
detecting whether a client of the third-party application is installed on the first computing device, and displaying a prompt page to the first user to guide the first user to download and install the client of the third-party application under the condition that the client of the third-party application is not installed on the first computing device.
6. The method of claim 1, wherein the first account associated with the first user is an account of the first user in the input method.
7. The method of claim 1, wherein the representation of the third-party application includes an activatable icon displayed at an interface of the input method, a predefined string submitted by the user in the input method, and a predefined gesture entered by the user in the input method.
8. The method of claim 1, the message exchange application comprising an instant messaging application, an email application, and a short message application.
9. The method of claim 1, wherein the structured string corresponding to the account exchange data is generated by the third party application interface module and further encoded with information of a client that launches or installs the third party application.
10. The method of claim 1, further comprising:
after receiving the account exchange data from the first user and before sending the structured string corresponding to the account exchange data to the second message exchange client, sending, by the third-party application interface module, the account exchange data to a server of the third-party application for account data processing associated with the first account, and receiving, from the server of the third-party application, the processed structured string corresponding to the account exchange data, the structured string further encoding information of a client that launches or installs the third-party application.
11. The method of claim 1, further comprising:
e) in response to selection by the second user of the structured string displayed at the second message exchange client, sending, by a second message exchange client operating at the second computing device, the structured string to the server of the third-party application for account data exchange processing associated with the second account of the second user, including opening, via a browser, a url address contained in the structured string that points to a server of a third-party application for data exchange with the server of the third-party application.
12. The method of claim 1, further comprising:
e) in response to selection by the second user of the structured string displayed at the second message exchange client, copying the structured string and passing the copied structured string to a corresponding third-party application interface module in a corresponding input method that contains the interface module corresponding to the third-party application by activating the corresponding input method at the second computing device, such that the structured string can be passed to a server of the third-party application via the third-party application interface module for account data exchange processing associated with the second account of the second user.
13. The method of claim 1, wherein the third-party application comprises a red envelope application, and the account exchange data received from the first user comprises red envelope amount data issued by the first user using the first account registered at the red envelope application.
14. A computing device to communicate third party application information in a message exchange application, the device having installed thereon an input method and a first message exchange client, the computing device comprising one or more processors and memory storing computer-executable instructions that, when executed by the one or more processors, perform operations comprising:
a) invoking the input method in a text entry field of the first message exchange client based on input from a first user, the first message exchange client in communication with at least a second message exchange client operating on another computing device;
b) in response to the first user activating a representation of a third-party application in the input method, detecting whether a first account associated with the first user is a server-authenticated account of the third-party application;
c) in response to determining that the first account associated with the first user has been authenticated by the server of the third-party application, receiving account exchange data from the first user in a third-party application interface module of the input method, the third-party application interface module in communication with the server of the third-party application, the account exchange data associated with account information registered by the first user in the server of the third-party application;
d) sending a structured string corresponding to the account exchange data via the first message exchange client to the second message exchange client operating at least at the other computing device, the structured string displayed at the second message exchange client configured to be selectable by a second user at the second message exchange client to send to the server of the third-party application.
15. A messaging system, comprising:
the third-party application server is used for the third-party application server,
the first user equipment is provided with an input method and a first message exchange client, wherein the input method comprises a third-party application interface module, and the third-party application interface module is configured to be capable of communicating with the third-party application server; and
a second user device having a second message exchange client installed thereon, the second message exchange client configured to communicate with the first message exchange client;
wherein the first user equipment is configured to:
a) invoking an input method in a text entry field of the first message exchange client based on input from a first user;
b) in response to the first user activating a representation of a third-party application in the input method, detecting whether a first account associated with the first user is an account authenticated by the third-party application server;
c) in response to determining that the first account associated with the first user has been authenticated by the third-party application server, receiving account exchange data from the first user in the third-party application interface module of the input method, the account exchange data associated with account information registered by the first user in the third-party application server;
d) sending a structured string corresponding to the account exchange data via the first message exchange client to the second message exchange client operating at the second computing device, the structured string displayed at the second message exchange client configured to be selectable by a second user at the second message exchange client to send to the third-party application server.
16. A non-transitory computer-readable storage medium having stored thereon instructions, which when executed by one or more processors, cause the one or more processors to perform the method of any one of claims 1-13.
CN202010119259.3A 2020-02-26 2020-02-26 Method and system for transferring third party application information in a message exchange session Active CN111147363B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202010119259.3A CN111147363B (en) 2020-02-26 2020-02-26 Method and system for transferring third party application information in a message exchange session
PCT/CN2020/121052 WO2021169320A1 (en) 2020-02-26 2020-10-15 Method and system for transmitting third-party application information in message exchange sessions

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010119259.3A CN111147363B (en) 2020-02-26 2020-02-26 Method and system for transferring third party application information in a message exchange session

Publications (2)

Publication Number Publication Date
CN111147363A true CN111147363A (en) 2020-05-12
CN111147363B CN111147363B (en) 2021-09-07

Family

ID=70528002

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010119259.3A Active CN111147363B (en) 2020-02-26 2020-02-26 Method and system for transferring third party application information in a message exchange session

Country Status (2)

Country Link
CN (1) CN111147363B (en)
WO (1) WO2021169320A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021169320A1 (en) * 2020-02-26 2021-09-02 Tianjin yinben fruitful enterprise management consulting partnership (limited partnership) Method and system for transmitting third-party application information in message exchange sessions
CN114221921A (en) * 2021-11-22 2022-03-22 中国建设银行股份有限公司 Instant messaging method, device, equipment and storage medium for mobile bank

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101571758A (en) * 2009-06-04 2009-11-04 腾讯科技(深圳)有限公司 Input method system, method and device thereof
CN102393803A (en) * 2011-09-13 2012-03-28 上海量明科技发展有限公司 Method for starting shopping function by utilizing input-method tool, client end and system
US9286935B1 (en) * 2007-01-29 2016-03-15 Start Project, LLC Simplified data entry
CN105653066A (en) * 2016-01-29 2016-06-08 腾讯科技(深圳)有限公司 Input method processing method and equipment
US20180048696A1 (en) * 2016-08-12 2018-02-15 Facebook, Inc. Methods and Systems for Accessing Third-Party Services within Applications
CN109426357A (en) * 2017-09-01 2019-03-05 百度在线网络技术(北京)有限公司 Data inputting method and device
CN109639566A (en) * 2018-12-14 2019-04-16 杭州安司源科技有限公司 A kind of open instant messaging chat robots system
CN109814733A (en) * 2019-01-08 2019-05-28 百度在线网络技术(北京)有限公司 Recommendation information generation method and device based on input
CN110710169A (en) * 2017-06-02 2020-01-17 苹果公司 Instant messaging system interacting with dynamically extended applications

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103744575B (en) * 2013-10-08 2018-05-01 百度在线网络技术(北京)有限公司 A kind of method and apparatus for the input auxiliary area for being used to provide input application
US10051085B2 (en) * 2014-05-21 2018-08-14 Verizon Patent And Licensing Inc. System and method of data and command request processing
CN107171930A (en) * 2017-04-20 2017-09-15 北京三快在线科技有限公司 Information displaying method and device in a kind of instant messaging application, electronic equipment
CN108803892B (en) * 2017-05-04 2024-03-22 北京搜狗科技发展有限公司 Method and device for calling third party application program in input method
CN110391972A (en) * 2019-07-30 2019-10-29 北京三快在线科技有限公司 A kind of business execution system, method and device
CN111147363B (en) * 2020-02-26 2021-09-07 天津银本硕果企业管理咨询合伙企业(有限合伙) Method and system for transferring third party application information in a message exchange session

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9286935B1 (en) * 2007-01-29 2016-03-15 Start Project, LLC Simplified data entry
CN101571758A (en) * 2009-06-04 2009-11-04 腾讯科技(深圳)有限公司 Input method system, method and device thereof
CN102393803A (en) * 2011-09-13 2012-03-28 上海量明科技发展有限公司 Method for starting shopping function by utilizing input-method tool, client end and system
CN105653066A (en) * 2016-01-29 2016-06-08 腾讯科技(深圳)有限公司 Input method processing method and equipment
US20180048696A1 (en) * 2016-08-12 2018-02-15 Facebook, Inc. Methods and Systems for Accessing Third-Party Services within Applications
CN110710169A (en) * 2017-06-02 2020-01-17 苹果公司 Instant messaging system interacting with dynamically extended applications
CN109426357A (en) * 2017-09-01 2019-03-05 百度在线网络技术(北京)有限公司 Data inputting method and device
CN109639566A (en) * 2018-12-14 2019-04-16 杭州安司源科技有限公司 A kind of open instant messaging chat robots system
CN109814733A (en) * 2019-01-08 2019-05-28 百度在线网络技术(北京)有限公司 Recommendation information generation method and device based on input

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021169320A1 (en) * 2020-02-26 2021-09-02 Tianjin yinben fruitful enterprise management consulting partnership (limited partnership) Method and system for transmitting third-party application information in message exchange sessions
CN114221921A (en) * 2021-11-22 2022-03-22 中国建设银行股份有限公司 Instant messaging method, device, equipment and storage medium for mobile bank
CN114221921B (en) * 2021-11-22 2023-07-18 中国建设银行股份有限公司 Instant messaging method, device, equipment and storage medium for mobile bank

Also Published As

Publication number Publication date
CN111147363B (en) 2021-09-07
WO2021169320A1 (en) 2021-09-02

Similar Documents

Publication Publication Date Title
US11810109B2 (en) System and method for token processing to link user accounts
US11683279B2 (en) System and method of using conversational agent to collect information and trigger actions
CN110612528B (en) Method, system and computer storage medium for securely authenticating an automated program user
WO2016145992A1 (en) Method and corresponding device for starting service through voice in communication software
CN111160845B (en) Service processing method and device
WO2017041641A1 (en) Method and device for realizing service function
CN109146437B (en) Virtual resource processing method, client and storage medium
RU2570838C2 (en) Strong authentication by providing number
CN106850503B (en) Login-free identity authentication method and device
US11902326B1 (en) Secure messaging integration with messaging applications
CN105656850B (en) Data processing method, related device and system
KR20150043369A (en) Communications server apparatus, calling device and methods of operation thereof
CN111147363B (en) Method and system for transferring third party application information in a message exchange session
US10326714B2 (en) Instant messaging with non subscriber users
US11900378B2 (en) System and method for providing merchant in-context checkout
US10270865B1 (en) Method for handing off a communications session
EP3782053A1 (en) Natural language interface for a data management system
CN113691602A (en) Service processing method, system, device, equipment and medium based on cloud mobile phone
WO2021138047A1 (en) Reviewing message-based communications via a keyboard application
US20220308918A1 (en) Automated generation of conversational workflows for automation chatbots
CN108200075B (en) Identity authentication method, system, terminal and storage medium
US10404849B2 (en) Launching a designated application using a set of signals
WO2016110200A1 (en) Network resource processing method, apparatus and instant messaging system
KR102428652B1 (en) Character information processing system using Microsoft Excel
CN106936840B (en) Information prompting method and device

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