CN114513761A - Message interaction method, system, terminal device and medium - Google Patents
Message interaction method, system, terminal device and medium Download PDFInfo
- Publication number
- CN114513761A CN114513761A CN202210101522.5A CN202210101522A CN114513761A CN 114513761 A CN114513761 A CN 114513761A CN 202210101522 A CN202210101522 A CN 202210101522A CN 114513761 A CN114513761 A CN 114513761A
- Authority
- CN
- China
- Prior art keywords
- message
- client terminal
- preset
- template
- message template
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/07—User-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/10—Multimedia information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Multimedia (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a message interaction method, a system, terminal equipment and a computer readable storage medium, wherein the message interaction method comprises the following steps: sending a preset message template to the client terminal, and receiving an uplink message which is returned by the client terminal and is triggered based on a click module or a keyword module in the preset message template; if the uplink message is a preset URL, sending an H5 page corresponding to the preset URL to the client terminal; receiving user information collected by a client terminal based on an H5 page, obtaining a first downlink message template based on user information matching, and sending the first downlink message template to the client terminal; if the uplink message is not the preset URL, judging whether the service data needs to be acquired from the service system or not based on the uplink message; and if so, acquiring the service data from the service system through the data engine, assembling the service data into a second downlink message template, and issuing the second downlink message template to the client terminal. The invention can realize high-efficiency message interaction.
Description
Technical Field
The present invention relates to the field of data transmission, and in particular, to a method, a system, a terminal device, and a computer-readable storage medium for message interaction.
Background
At present, a Unified Message Center (UMC) has a multi-channel communication capability, can send various messages such as a 5G Message, a rich media Message, a short Message, a WeChat, an email, and an APP, and has a capability of interconversion, interconnection, multi-network integration, and multi-party delivery among various messages.
In the process of docking multiple 5G message projects and the like, it is found that an enterprise user hopes that a 5G message has the capability of performing data bidirectional interaction with an enterprise service system in the actual use scene of the 5G message, but the current UMC unified message center only supports the limited interaction capability of sending a 5G static message and a template in the interaction, and in order to meet the actual landing requirements of the enterprise user, the UMC unified message center faces the following three problems:
1. the template dynamic parameters can only be actively transmitted by a service system, and the bidirectional interaction of data cannot be realized;
2. the message has limited interaction capacity and cannot have functions of opening APP, H5 production and the like;
3. the relation between the template dynamic parameter data and the judgment event and the template is lack of effective management, and the dynamic template can not acquire data in uplink and downlink interaction, so that the interaction can be carried out only through the static template.
In summary, the current 5G message information interaction function is not complete, so that the message interaction efficiency is low, and further the user experience is affected.
Disclosure of Invention
The invention mainly aims to provide a message interaction method, a message interaction system, terminal equipment and a computer readable storage medium, aiming at realizing efficient message interaction.
In order to achieve the above object, the present invention provides a message interaction method, including:
sending a preset message template to the client terminal, and receiving an uplink message which is returned by the client terminal and is triggered based on a click module or a keyword module in the preset message template;
if the uplink message is a preset URL, sending an H5 page corresponding to the preset URL to the client terminal;
receiving user information collected by the client terminal based on the H5 page, obtaining a first downlink message template based on the user information matching, and sending the first downlink message template to the client terminal;
if the uplink message is not the preset URL, judging whether service data needs to be acquired from the service system or not based on the uplink message;
and if so, acquiring the service data from the service system through a preset data engine, assembling the service data into a second downlink message template, and issuing the second downlink message template to the client terminal.
Optionally, the click module comprises a button and/or a floating menu;
the message interaction method further comprises the following steps:
and binding the preset URL with the button in advance.
Optionally, the step of assembling the service data into a second downlink message template includes:
and assembling the service data to a preset template of the server to obtain a second downlink message template.
Optionally, after the step of determining whether to acquire service data from the service system based on the uplink message, the method further includes:
and if the corresponding service data does not need to be acquired from the service system based on the uplink message, acquiring a message template matched with the uplink message, and issuing the message template matched with the uplink message to the client terminal.
Optionally, the step of issuing the second downlink message template to the client terminal includes:
judging whether the client terminal needs to be authenticated or not based on the service data in the second downlink message template;
if the client terminal needs to be authenticated, authenticating the client terminal by adopting a preset authentication mode, and issuing the downlink message template to the client terminal after the authentication is passed;
and if the client terminal does not need to be authenticated, the downlink message template is issued to the client terminal.
Optionally, the preset authentication manner includes: one-touch login authentication or account login authentication, wherein the one-touch login authentication comprises the following steps:
obtaining a corresponding message number based on one-key login authentication triggered by an H5 page in the client terminal, and comparing the message number with the current number of the client terminal, wherein the H5 page is obtained based on a URL (uniform resource locator) bound by the click module;
judging whether the message number is consistent with the current number;
if the message number is consistent with the current number, the authentication is passed, and the client terminal is allowed to log in;
the account login authentication step comprises the following steps:
acquiring user information generated through the H5 page based on the account login authentication, and acquiring corresponding user source data from the service system through the data engine based on the user information;
judging whether the user information is consistent with the user source data;
and if the user information is judged to be consistent with the user source data, the authentication is passed, and the client terminal is allowed to log in.
Optionally, the message interaction method further includes:
if the user information collected based on the H5 page of the client terminal is not received within the preset first waiting time, the preset message template is issued to the client terminal again;
and if the user information is not received within the preset second waiting time, no response is carried out on the uplink message.
In order to achieve the above object, the present invention further provides a message interaction system, including:
a sending module, configured to send an H5 page corresponding to a preset URL to the client terminal if the uplink message is the preset URL;
a first issuing module, configured to receive user information collected by the client terminal based on the H5 page, obtain a first downlink message template based on the user information matching, and issue the first downlink message template to the client terminal;
the judging module is used for judging whether the service data needs to be acquired from the service system or not based on the uplink message;
and the second issuing module is used for acquiring the service data from the service system through a preset data engine, assembling the service data into a second downlink message template and issuing the second downlink message template to the client terminal.
Wherein, each functional module of the message interaction system of the invention realizes the steps of the message interaction method when running.
In order to achieve the above object, the present invention further provides a terminal device, including: a memory, a processor, and a messaging program stored on the memory and executable on the processor, the messaging program when executed by the processor implementing the steps of the messaging method as described above.
In addition, to achieve the above object, the present invention further provides a computer readable storage medium, which stores a message interaction program, and the message interaction program, when executed by a processor, implements the steps of the message interaction method as described above.
Furthermore, to achieve the above object, the present invention also provides a computer program product comprising a computer program which, when executed by a processor, implements the steps of the message interaction method as described above.
The invention provides a message interaction method, a system, terminal equipment, a computer readable storage medium and a computer program product, which are characterized in that a preset message template is issued to a client terminal, and an uplink message which is returned by the client terminal and is triggered based on a click module or a keyword module in the preset message template is received; if the uplink message is a preset URL, sending an H5 page corresponding to the preset URL to the client terminal; receiving user information collected by the client terminal based on the H5 page, obtaining a first downlink message template based on the user information matching, and sending the first downlink message template to the client terminal; if the uplink message is not the preset URL, judging whether service data needs to be acquired from the service system or not based on the uplink message; and if so, acquiring the service data from the service system through a preset data engine, assembling the service data into a second downlink message template, and issuing the second downlink message template to the client terminal.
Compared with the problem that the 5G message interaction function is limited in the prior art, the invention opens a data interaction channel between the server and the client business system according to the message interaction among the client terminal, the server and the business system, realizes the active acquisition of business data from the business system, avoids interface modification work caused by parameter mapping relation modification by automatically identifying dynamic parameters of the message template and business system fields associated with a visual interface, improves the flexibility of data interaction modes among the systems, further can issue corresponding message templates according to the user requirements of the client terminal, realizes efficient and accurate message pushing, and enables enterprises to carry out informatization development of businesses such as production, marketing and the like.
Drawings
FIG. 1 is a schematic diagram of a hardware operating environment according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a message interaction method according to an embodiment of the present invention;
fig. 3 is a schematic view of a message interaction scenario involved in an embodiment of the message interaction method of the present invention;
FIG. 4 is a schematic view illustrating a flow of a click event according to an embodiment of a message interaction method of the present invention;
FIG. 5 is a schematic diagram illustrating a message template authentication reply flow according to an embodiment of the message interaction method of the present invention;
FIG. 6 is a schematic diagram of a one-touch login process according to an embodiment of the message interaction method of the present invention;
FIG. 7 is a schematic diagram illustrating an event flow of H5 according to an embodiment of the message interaction method of the present invention;
fig. 8 is a schematic view illustrating an account login process according to an embodiment of the message interaction method of the present invention;
fig. 9 is a functional block diagram of a messaging system according to an embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
As shown in fig. 1, fig. 1 is a schematic device structure diagram of a hardware operating environment according to an embodiment of the present invention.
It should be noted that, the terminal device in the embodiment of the present invention may be a device for message interaction, and the terminal device may specifically be a smart phone, a personal computer, a server, and the like.
As shown in fig. 1, the apparatus may include: a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, a communication bus 1002. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (e.g., a magnetic disk memory). The memory 1005 may alternatively be a storage device separate from the processor 1001.
Those skilled in the art will appreciate that the configuration of the apparatus shown in fig. 1 is not intended to be limiting of the apparatus and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
As shown in fig. 1, a memory 1005, which is a kind of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and a message interaction program. An operating system is a program that manages and controls the hardware and software resources of a device, supporting the operation of messaging programs and other software or programs. In the apparatus shown in fig. 1, the user interface 1003 is mainly used for data communication with the client terminal; the network interface 1004 is mainly used for establishing communication connection with a server; and processor 1001 may be configured to invoke the messaging program stored in memory 1005 and perform the following operations:
sending a preset message template to the client terminal, and receiving an uplink message which is returned by the client terminal and is triggered based on a click module or a keyword module in the preset message template;
if the uplink message is a preset URL, sending an H5 page corresponding to the preset URL to the client terminal;
receiving user information collected by the client terminal based on the H5 page, obtaining a first downlink message template based on the user information matching, and sending the first downlink message template to the client terminal;
if the uplink message is not the preset URL, judging whether service data needs to be acquired from the service system or not based on the uplink message;
and if so, acquiring the service data from the service system through a preset data engine, assembling the service data into a second downlink message template, and issuing the second downlink message template to the client terminal.
Further, the click module includes a button and/or a floating menu, and the processor 1001 may be further configured to call the message interaction program stored in the memory 1005, and further perform the following operations:
and binding the preset URL with the button in advance.
Further, the processor 1001 may be further configured to call the message interaction program stored in the memory 1005, and further perform the following operations:
and assembling the service data into a preset template of the server to obtain a second downlink message template.
Further, after the step of determining whether service data needs to be acquired from the service system based on the uplink message, the processor 1001 may be further configured to invoke a message interaction program stored in the memory 1005, and further perform the following operations:
and if the corresponding service data does not need to be acquired from the service system based on the uplink message, acquiring a message template matched with the uplink message, and issuing the message template matched with the uplink message to the client terminal.
Further, the processor 1001 may be further configured to invoke a messaging program stored in the memory 1005 to perform the following operations:
judging whether the client terminal needs to be authenticated or not based on the service data in the second downlink message template;
if the client terminal needs to be authenticated, authenticating the client terminal by adopting a preset authentication mode, and issuing the downlink message template to the client terminal after the authentication is passed;
and if the client terminal does not need to be authenticated, the downlink message template is issued to the client terminal.
Further, the preset authentication manner includes: the method comprises the following steps of one-key login authentication or account login authentication, wherein the step of authenticating the client terminal by adopting a preset authentication mode comprises the following steps:
obtaining a corresponding message number based on one-key login authentication triggered by an H5 page in the client terminal, and comparing the message number with the current number of the client terminal, wherein the H5 page is obtained based on a URL (uniform resource locator) bound by the click module;
judging whether the message number is consistent with the current number;
if the message number is consistent with the current number, the authentication is passed, and the client terminal is allowed to log in;
acquiring user information generated through the H5 page based on the account login authentication, and acquiring corresponding user source data from the service system through the data engine based on the user information;
judging whether the user information is consistent with the user source data;
if the user information is judged to be consistent with the user source data, the authentication is passed, and the client terminal is allowed to log in.
Further, the processor 1001 may be further configured to call the message interaction program stored in the memory 1005, and further perform the following operations:
if the user information collected based on the H5 page of the client terminal is not received within the preset first waiting time, the preset message template is issued to the client terminal again;
and if the user information is not received within the preset second waiting time, no response is carried out on the uplink message.
Referring to fig. 2, fig. 2 is a flowchart illustrating a message interaction method according to a first embodiment of the present invention.
In the present embodiment, an embodiment of a message interaction method applied to a server is provided, and it should be noted that, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in an order different from that here.
Application scenarios of the present invention may include: including 5G messages, short messages, intelligent short messages, rich messages, etc. The invention comprises a client terminal, a server and a service system and aims to realize efficient three-terminal message interaction. The server is respectively connected with the client terminal and the service system, wherein the client terminal can be a mobile phone terminal, a large number of message templates are pre-configured in the server so as to realize the issuing of the message templates required by a user at the mobile phone terminal, and a large number of service data are contained in the service system. As shown in fig. 3, the interface is an interface in the UMC unified message, the interface includes a start, a message template, a click, a keyword, a fixed button, a floating menu, H5 (fifth generation HTML), a judgment, and the like, and a back-end developer can view an interaction scenario and configure a message interaction flow on the interface. Wherein, the template must be connected after the keyword, and the template is only connected or not connected before the keyword; all nodes can be connected in front of the message template, and all nodes except the beginning can be connected behind the message template; clicking a button/menu which can only connect the event as a reply template in front and connecting the message template in the back; h5 can only connect events before to open H5 button/menu, and must connect messages after; whereas for the button/menu, only the button/menu with events of opening H5 and replying to the template can connect the subsequent node.
Step S10, a preset message template is sent to the client terminal, and an uplink message which is returned by the client terminal and is triggered based on a click module or a keyword module in the preset message template is received;
the server issues a preset message template to the client terminal, and the client terminal triggers a button (including a fixed button and a suspension menu) in the preset message module or an uplink keyword to generate an uplink message after receiving the preset message template, and further, the server receives the uplink message.
It should be noted that, in this embodiment, the triggering manner of the uplink message received by the server may include triggering based on a fixed button, triggering based on a floating menu, or triggering based on an uplink keyword, and the server may generate a message template matched with the uplink message according to different triggering manners, and issue the message template, so that accurate pushing of the message can be realized, various operation requirements of the client terminal are met, and an enterprise can be enabled to perform informatization development of services such as production, marketing, and the like. In this embodiment, the message interaction between the client terminal and the server is involved, and the manner in which the client terminal generates the uplink message may include a fixed button, a floating menu, or an uplink keyword in the message module, thereby realizing personalized transmission of the message.
Step S20, if the uplink message is a preset URL, sending an H5 page corresponding to the preset URL to the client terminal;
step S30, receiving the user information collected by the client terminal based on the H5 page, obtaining a first downlink message template based on the user information matching, and sending the first downlink message template to the client terminal;
it should be noted that, in the embodiment, as shown in the schematic flow diagram of H5 event flow shown in fig. 4, for other buttons on the preset message template (such as the "active entry" button), if the button binds a URL (Uniform Resource Locator) in advance, the server (i.e., UMC unified message center) sends a H5 page corresponding to the URL to the client terminal, so that the user can directly click the corresponding button at the client terminal, jump to the H5 page (such as an active entry page) of information collection corresponding to the URL bound by the button, and submit the information to the UMC unified message center after the H5 page fills in the relevant information, the UMC unified message center matches the corresponding message template according to the filled-in related information (for example, after the entry information is filled in, the corresponding message template is matched according to the keyword in the entry information), and then sends the message template to the user of the client terminal. In this case, the UMC unified message center does not need to obtain the corresponding service data from the service system. In the embodiment, flexible message interaction between the client terminal and the UMC unified message center is realized.
Step S40, if the uplink message is not the preset URL, determining whether service data needs to be acquired from the service system based on the uplink message;
after receiving an uplink message triggered by the client terminal, the server analyzes the uplink message, and if the uplink message is detected not to be a URL, the server needs to determine whether to acquire service data matched with the uplink message from a service system through a data engine.
It should be noted that, in this embodiment, the manner in which the client terminal generates the uplink message may include a fixed button, a floating menu, or an uplink keyword in the message module, and the server generates a corresponding message template according to the triggering manner of the uplink message and issues the message template to the client terminal.
Specifically, for example, the server will determine whether the uplink message is triggered based on a button in the click module or based on an uplink keyword, and determine whether the button is pre-bound with a URL to determine whether to acquire service data corresponding to the uplink message from the service system.
Further, the message interaction method of the present invention further comprises:
step S50, if yes, acquiring the service data from the service system through a preset data engine, assembling the service data into a second downlink message template, and issuing the second downlink message template to the client terminal;
it should be noted that, in this embodiment, the data engine solves the problem of bidirectional interaction of data, reads the plug-in information through interface docking or accessing a database, and obtains the service data in the service system, so as to actively obtain data from the service system, open a data interaction channel between the server and the client service system (e.g., a financial system, a client system, a subscription record system, etc.), and provide a basic link for bidirectional data query and push in a later period.
Specifically, for example, as shown in the click event flow diagram shown in fig. 5, after acquiring an uplink message and determining that service data matched with the uplink message needs to be acquired from a service system according to the uplink message, a server (i.e., a UMC unified message center) acquires corresponding service data in the service system by docking a data engine through a corresponding interface or accessing a database, and assembles the service data into a corresponding preset template to obtain a downlink message template, so as to send the downlink message template to a client terminal.
It should be noted that, in this embodiment, the visual interface configuration may be performed on the user information determination rule of the client terminal, and the dynamic parameter of the message template is mapped and bound to the data source field of the service system, so that the interface modification work caused by the modification of the parameter mapping relationship is avoided, and the flexibility of the data interaction mode between systems is improved.
It should be noted that, in the present embodiment, the visual interface is associated with the business system field,
further, after the step of "determining whether to acquire service data from the service system based on the uplink message" in step S40, the method further includes:
step S60, if it is determined based on the uplink message that it is not necessary to acquire corresponding service data from the service system, acquiring a message template matching the uplink message, and issuing the message template matching the uplink message to the client terminal.
After the server acquires the uplink message and judges that the service data does not need to be acquired from the service system according to the uplink message, the server matches a corresponding message template according to the uplink message and issues the message template to the client terminal.
It should be noted that, in this embodiment, since the server is preset with the message template bound to the uplink keyword, when it is detected that the uplink message is generated by the uplink keyword, the server does not need to obtain service data from the service system, but can directly issue the message template bound to the uplink keyword in advance to the client terminal. In addition, if it is detected that the uplink message is triggered by a click module, i.e., a button, the server needs to further determine whether to acquire corresponding service data from the service system.
Further, in the step S50, the issuing the second downlink message template to the client terminal may include:
step S501, judging whether the client terminal needs to be authenticated based on the service data in the second downlink message template;
step S502, if the client terminal needs to be authenticated, the client terminal is authenticated by adopting a preset authentication mode, and the downlink message template is issued to the client terminal after the authentication is passed;
step S503, if it is determined that the client terminal does not need to be authenticated, issuing the downlink message template to the client terminal.
It should be noted that, in this embodiment, before the server issues the downlink message template to the client, it needs to determine in advance whether the service data in the downlink message template needs to be authenticated, and if the service data needs to be authenticated, the server issues the downlink message template after the authentication is passed.
Specifically, for example, as shown in fig. 6, the message template authentication reply flow is schematic, and the message template authentication reply flow includes: when a server (namely a UMC unified message center) identifies that a downlink message template to be replied in a downlink mode is a message which can be sent only after a client terminal user logs in authentication (such as a transaction bill), the UMC unified message center firstly issues a login authentication message template which is set in advance, a user jumps to an H5 page corresponding to a URL (uniform resource locator) bound by a button through clicking the button on the message template to perform mobile phone number one-key login, the UMC unified message center issues the downlink message template to the client terminal after detecting that the client terminal user logs in successfully, or acquires a user information form filled in the H5 page by the user, and issues the downlink message template to the client terminal after comparing the user form information with the client service system information successfully. And after the UMC unified message center judges that the service data in the downlink message template does not need to be authenticated, the UMC unified message center directly skips the authentication process and directly issues the downlink message template to the corresponding client terminal.
Further, in step S50, the "assembling the service data into the second downlink message template" may include:
step S504, the service data is assembled to a preset template of the server to obtain a second downlink message template.
It should be noted that, in this embodiment, since the server is configured with a large number of message templates in advance, when it is determined that the service data needs to be acquired from the service system, the service system acquired by docking the data engine through a corresponding interface or accessing a database may be directly assembled into the existing corresponding message template to obtain the required downlink message template.
Further, the message interaction method of the present invention further includes:
and step S70, binding the preset URL with the button in advance.
It should be noted that, in this embodiment, the click module includes a button and/or a floating menu, and a user of the client terminal performs a click operation on the button and/or the floating menu, where the floating menu may be an uplink keyword.
Specifically, for example, a button (for example, an "activity entry" button) in the click module is bound with a preset URL in advance, so that when the user of the client terminal clicks the button, the user can directly jump to an H5 page corresponding to the bound URL, and then the user can fill related form information and the like in the H5 page, and send an uplink message including the form information to the server.
In this embodiment, the server issues a preset message template to the client terminal, and the client terminal triggers a button (including a fixed button and a floating menu) or an uplink keyword in the preset message module to generate an uplink message after receiving the preset message template, and further, the server receives the uplink message. After receiving the uplink message triggered by the client terminal, the server analyzes the uplink message to judge whether the service data matched with the uplink message needs to be acquired from the service system through the data engine according to the uplink message. After acquiring the uplink message and judging that the service data matched with the uplink message needs to be acquired from the service system according to the uplink message, the server acquires the corresponding service data in the service system through corresponding interface docking or accessing a database and the like based on a data engine, and assembles the corresponding preset template with the service data to obtain a downlink message template. After the server acquires the service data from the service system and assembles the service data into the preset template to obtain the downlink message template, whether the service data in the downlink message template needs to be authenticated is further judged, so that the client terminal is allowed to log in after the authentication is passed. And after judging that the service data in the downlink message template does not need to be authenticated, the server directly issues the downlink message template to the corresponding client terminal. If the service data in the downlink message template needs to be authenticated, the user jumps to an H5 page corresponding to the URL bound by a button by clicking the button on the message template to perform one-key login of the mobile phone number, and issues the downlink message template to the client terminal after the client terminal successfully logs in, or acquires a user information form filled in by the user at the client terminal, and issues the downlink message template to the client terminal after the user form information is successfully compared with the client service system information.
Compared with the problem that the 5G message interaction function is limited in the prior art, the invention opens a data interaction channel between the server and the client business system according to the message interaction among the client terminal, the server and the business system, realizes the active acquisition of business data from the business system, can carry out visual interface configuration on the user information judgment rule of the client terminal, and maps and binds the dynamic parameters of the template and the data source field, avoids the interface modification work caused by the modification of the parameter mapping relation, improves the flexibility of the data interaction mode among the systems, further can issue the corresponding message template according to the user requirement of the client terminal, realizes efficient and accurate message pushing, and enables enterprises to carry out the informatization development of the businesses such as production, marketing and the like.
Further, based on the above first embodiment of the message interaction method of the present invention, a second embodiment of the message interaction method of the present invention is proposed.
The main difference between this embodiment and the first embodiment described above is that the preset authentication manner includes: one-touch login authentication or account login authentication, wherein the one-touch login authentication comprises the following steps:
step S5021, obtaining a corresponding message number based on one-key login authentication triggered by an H5 page in the client terminal, and comparing the message number with the current number of the client terminal, wherein the H5 page is obtained based on a URL (uniform resource locator) bound by the click module;
step S5022, judging whether the message number is consistent with the current number;
step S5023, if the message number is consistent with the current number, the authentication is passed, and the client terminal is allowed to log in.
It should be noted that, in this embodiment, the preset authentication manner includes: and (4) one-key login authentication, namely, a user of the client terminal jumps to an H5 page corresponding to the URL bound by a button to perform mobile phone number one-key login by clicking the button on the message template, and the server issues a downlink message template to the client terminal after the client terminal successfully logs in.
Specifically, for example, as shown in the schematic diagram of one-touch login process shown in fig. 7, after determining that the service data in the downlink message template needs to be authenticated, the server issues a "login authentication" message template, and the user of the client terminal may click a one-touch login button in the "login authentication" message template, go to the H5 page corresponding to the URL bound to the button to perform one-touch login, the server acquires a login message triggered by clicking the one-touch login button, acquires a corresponding message number from the login message, compares the message number with the current number of the client terminal, determines whether the message number is consistent with the current number of the client terminal, and if so, passes authentication and allows the user of the client terminal to log in.
The account login authentication step comprises the following steps:
step S5024, user information generated through the H5 page is obtained based on the account login authentication, and corresponding user source data are obtained from the business system through the data engine based on the user information;
step S5025, judging whether the user information is consistent with the user source data;
step S5026, if the user information is judged to be consistent with the user source data, the authentication is passed, and the client terminal is allowed to log in.
It should be noted that, in this embodiment, the preset authentication manner includes: and account login authentication, namely acquiring a user information form filled in by a user on an H5 page of the client terminal, and issuing a downlink message template to the client terminal after the user form information is successfully compared with the client service system information.
Specifically, for example, as shown in the account login flow diagram shown in fig. 8, after determining that the service data in the downlink message template needs to be authenticated, the server issues a "login authentication" message template, and the user of the client terminal may click a skip button in the "login authentication" message template, go to the H5 page corresponding to the URL bound by the button to fill in the user information, and submit the user information to the server, the server obtains the user source data in the service system through a data engine based on interface docking or accessing a database, and compares the user information with the user source data, determines whether the user information is consistent with the user source data, and if so, the server determines that the authentication is passed, and allows the client terminal to log in.
Further, the message interaction method of the present invention further includes:
step a, if the user information collected based on the H5 page of the client terminal is not received within a preset first waiting time, issuing the preset message template to the client terminal again;
and b, if the user information is not received within the preset second waiting time, no response is carried out on the uplink message.
It should be noted that, in this embodiment, if the server has sent the message template including the page jumped to H5 to the client terminal, but the user information collected based on the H5 page is not received within the preset first waiting duration, the server will resend the message template to the client terminal and continue to wait for the user information submitted by the client terminal, where the message template sent by the server may not be consistent with the message template sent last time; or, the server does not receive the user information submitted by the client terminal within the preset second waiting time, and does not respond to the uplink message sent by the client terminal any more, that is, does not respond to the interaction of the client terminal any more. In this embodiment, the preset second waiting duration is longer than the preset first waiting duration.
In this embodiment, the server may authenticate the user of the client terminal through two modes, i.e., one-key login authentication and account login authentication, and in addition, the server needs to receive the H5 page information within a preset waiting time, otherwise, the client terminal cannot continue to submit the H5 page information to the server. Therefore, the invention realizes the high-efficiency interaction efficiency between the server and the client terminal.
In addition, an embodiment of the present invention further provides a message interaction system, and referring to fig. 9, fig. 9 is a functional module schematic diagram of an embodiment of the message interaction system according to the present invention. As shown in fig. 9, the message interaction system of the present invention includes:
the receiving module 10 is configured to send a preset message template to the client terminal, and receive an uplink message returned by the client terminal and triggered based on a click module or a keyword module in the preset message template;
a sending module 20, configured to send, if the uplink message is a preset URL, an H5 page corresponding to the preset URL to the client terminal;
a first issuing module 30, configured to receive user information collected by the client terminal based on the H5 page, obtain a first downlink message template based on the user information matching, and issue the first downlink message template to the client terminal;
a judging module 40, configured to judge whether service data needs to be acquired from the service system based on the uplink message;
the second issuing module 50 is configured to obtain the service data from the service system through a preset data engine, assemble the service data into a second downlink message template, and issue the second downlink message template to the client terminal.
Further, the click module includes a button and/or a floating menu, and the message interaction system of the present invention further includes:
and the binding module is used for binding the preset URL with the button in advance.
Further, the second issuing module 50 includes:
and the assembling module is used for assembling the service data to a preset template of the server to obtain a second downlink message template.
Further, the message interaction system of the present invention further comprises:
and the third issuing module is used for acquiring the message template matched with the uplink message and issuing the message template matched with the uplink message to the client terminal if the corresponding service data does not need to be acquired from the service system based on the uplink message.
Further, the second issuing module 50 further includes:
a judging unit, configured to judge whether the client terminal needs to be authenticated based on the service data in the second downlink message template;
the first issuing unit is used for authenticating the client terminal by adopting a preset authentication mode if the client terminal is judged to need to be authenticated, and issuing the downlink message template to the client terminal after the authentication is passed;
and the second issuing unit is used for issuing the downlink message template to the client terminal if the client terminal does not need to be authenticated.
Further, the preset authentication manner includes: the first issuing unit comprises:
a first comparison subunit, configured to obtain a corresponding message number based on a one-key login authentication triggered by an H5 page in the client terminal, and compare the message number with a current number of the client terminal, where the H5 page is obtained based on a URL bound by the click module;
the first judging subunit is used for judging whether the message number is consistent with the current number;
and the first allowing subunit is used for passing authentication and allowing the client terminal to log in if the message number is consistent with the current number.
The second comparison subunit is used for acquiring the user information generated through the H5 page based on the account login authentication, and acquiring corresponding user source data from the service system through the data engine based on the user information;
the second judging subunit is used for judging whether the user information is consistent with the user source data;
and the third allowing subunit is used for passing the authentication and allowing the client terminal to log in if the user information is judged to be consistent with the user source data.
Further, the message interaction system of the present invention further comprises:
a second issuing module, configured to issue the preset message template to the client terminal again if the user information collected based on the H5 page of the client terminal is not received within a preset first waiting time;
and the response module is used for not responding to the uplink message if the user information is not received within the preset second waiting time.
The specific implementation of each functional module of the message interaction system of the present invention is basically the same as that of each embodiment of the message interaction method described above, and is not described herein again.
In addition, an embodiment of the present invention further provides a computer-readable storage medium, where a message interaction program is stored on the computer-readable storage medium, and when executed by a processor, the message interaction program implements the steps of the message interaction method described above.
The embodiments of the message interaction system and the computer-readable storage medium of the present invention can refer to the embodiments of the message interaction method of the present invention, and are not described herein again.
Furthermore, an embodiment of the present invention also provides a computer program product, which includes a computer program, and when being executed by a processor, the computer program implements the steps of the message interaction method according to any one of the above message interaction method embodiments.
The specific embodiment of the computer program product of the present invention is substantially the same as the embodiments of the message interaction method described above, and is not described herein again.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention essentially or contributing to the prior art may be embodied in the form of a software product, which is stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) and includes instructions for causing a terminal device (e.g. a smart phone, a personal computer, a server, etc.) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A message interaction method is applied to a server, and is characterized by comprising the following steps:
sending a preset message template to the client terminal, and receiving an uplink message which is returned by the client terminal and is triggered based on a click module or a keyword module in the preset message template;
if the uplink message is a preset URL, sending an H5 page corresponding to the preset URL to the client terminal;
receiving user information collected by the client terminal based on the H5 page, obtaining a first downlink message template based on the user information matching, and sending the first downlink message template to the client terminal;
if the uplink message is not the preset URL, judging whether service data needs to be acquired from the service system or not based on the uplink message;
and if so, acquiring the service data from the service system through a preset data engine, assembling the service data into a second downlink message template, and issuing the second downlink message template to the client terminal.
2. The message interaction method of claim 1, wherein the click module comprises a button and/or a flyover menu;
the message interaction method further comprises the following steps:
and binding the preset URL with the button in advance.
3. The message interaction method as claimed in claim 1, wherein the step of assembling the service data into a second downlink message template comprises:
and assembling the service data into a preset template of the server to obtain a second downlink message template.
4. The message interaction method as claimed in claim 1, wherein after the step of determining whether service data needs to be acquired from the service system based on the uplink message, the method further comprises:
and if the corresponding service data does not need to be acquired from the service system based on the uplink message, acquiring a message template matched with the uplink message, and issuing the message template matched with the uplink message to the client terminal.
5. The message interaction method as claimed in claim 1, wherein the step of issuing the second downlink message template to the client terminal comprises:
judging whether the client terminal needs to be authenticated or not based on the service data in the second downlink message template;
if the client terminal needs to be authenticated, authenticating the client terminal by adopting a preset authentication mode, and issuing the downlink message template to the client terminal after the authentication is passed;
and if the client terminal does not need to be authenticated, the downlink message template is issued to the client terminal.
6. The message interaction method of claim 5, wherein the preset authentication manner comprises: one-touch login authentication or account login authentication, wherein the one-touch login authentication comprises the following steps:
obtaining a corresponding message number based on one-key login authentication triggered by an H5 page in the client terminal, and comparing the message number with the current number of the client terminal, wherein the H5 page is obtained based on a URL (uniform resource locator) bound by the click module;
judging whether the message number is consistent with the current number;
if the message number is consistent with the current number, the authentication is passed, and the client terminal is allowed to log in;
the account login authentication step comprises the following steps:
acquiring user information generated through the H5 page based on the account login authentication, and acquiring corresponding user source data from the service system through the data engine based on the user information;
judging whether the user information is consistent with the user source data;
and if the user information is judged to be consistent with the user source data, the authentication is passed, and the client terminal is allowed to log in.
7. The message interaction method of claim 1, wherein the message interaction method further comprises:
if the user information collected based on the H5 page of the client terminal is not received within the preset first waiting time, the preset message template is issued to the client terminal again;
and if the user information is not received within the preset second waiting time, no response is carried out on the uplink message.
8. A messaging system, the messaging system comprising:
the receiving module is used for sending a preset message template to the client terminal and receiving an uplink message which is returned by the client terminal and is triggered based on a click module or a keyword module in the preset message template;
a sending module, configured to send an H5 page corresponding to a preset URL to the client terminal if the uplink message is the preset URL;
a first issuing module, configured to receive user information collected by the client terminal based on the H5 page, obtain a first downlink message template based on the user information matching, and issue the first downlink message template to the client terminal;
the judging module is used for judging whether the service data needs to be acquired from the service system or not based on the uplink message;
and the second issuing module is used for acquiring the service data from the service system through a preset data engine, assembling the service data into a second downlink message template and issuing the second downlink message template to the client terminal.
9. A terminal device, characterized in that the terminal device comprises a memory, a processor and a messaging program stored on the memory and executable on the processor, the messaging program, when executed by the processor, implementing the steps of the messaging method according to any one of claims 1 to 7.
10. A computer-readable storage medium, having stored thereon a messaging program, which when executed by a processor, performs the steps of the messaging method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210101522.5A CN114513761B (en) | 2022-01-27 | 2022-01-27 | Message interaction method, system, terminal equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210101522.5A CN114513761B (en) | 2022-01-27 | 2022-01-27 | Message interaction method, system, terminal equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114513761A true CN114513761A (en) | 2022-05-17 |
| CN114513761B CN114513761B (en) | 2023-08-11 |
Family
ID=81549658
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210101522.5A Active CN114513761B (en) | 2022-01-27 | 2022-01-27 | Message interaction method, system, terminal equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114513761B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070118599A1 (en) * | 2000-11-06 | 2007-05-24 | Envoyworldwide, Inc. | System and method for service specific notification |
| US20140019564A1 (en) * | 2012-07-12 | 2014-01-16 | Salesforce.Com, Inc. | Methods and systems for generating electronic messages based upon dynamic content |
| WO2016065285A1 (en) * | 2014-10-24 | 2016-04-28 | Boingnet, Inc. | Pay as you go marketing campaign |
| CN106534356A (en) * | 2016-12-12 | 2017-03-22 | 腾讯科技（深圳）有限公司 | Method and apparatus for processing template data, requesting template data and displaying template data |
| US20170187666A1 (en) * | 2015-12-28 | 2017-06-29 | Facebook, Inc. | Systems and methods for providing messages based on preconfigured messages templates |
| US20180103004A1 (en) * | 2016-10-07 | 2018-04-12 | Facebook, Inc. | Reengaging website visitors with social networking system electronic messages |
-
2022
- 2022-01-27 CN CN202210101522.5A patent/CN114513761B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070118599A1 (en) * | 2000-11-06 | 2007-05-24 | Envoyworldwide, Inc. | System and method for service specific notification |
| US20140019564A1 (en) * | 2012-07-12 | 2014-01-16 | Salesforce.Com, Inc. | Methods and systems for generating electronic messages based upon dynamic content |
| WO2016065285A1 (en) * | 2014-10-24 | 2016-04-28 | Boingnet, Inc. | Pay as you go marketing campaign |
| US20170187666A1 (en) * | 2015-12-28 | 2017-06-29 | Facebook, Inc. | Systems and methods for providing messages based on preconfigured messages templates |
| US20180103004A1 (en) * | 2016-10-07 | 2018-04-12 | Facebook, Inc. | Reengaging website visitors with social networking system electronic messages |
| CN106534356A (en) * | 2016-12-12 | 2017-03-22 | 腾讯科技（深圳）有限公司 | Method and apparatus for processing template data, requesting template data and displaying template data |
Non-Patent Citations (1)
| Title |
|---|
| 刘涛;于宏文;祝志凌;: "华中电网调度生产短信息平台研究开发与应用", 华中电力, no. 01 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114513761B (en) | 2023-08-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108449418B (en) | Hybrid cloud platform management system and method | |
| US11711434B2 (en) | Information transmission method and device | |
| CN107146074B (en) | Work order task cooperative processing method and device and computer readable storage medium | |
| CN111143207B (en) | Method for checking model training notice and training log at mobile terminal | |
| CN101689210A (en) | Gathering and search are from the profile data of a plurality of services | |
| CN102843413B (en) | Screen creating system, screen generating method and generation program of graphic display | |
| CN101006680A (en) | System and method for authentificting a user to a service provider | |
| CN104869143A (en) | Data sharing method and device, client and server | |
| CN107438054B (en) | Method and system for realizing menu information control based on public platform | |
| CN107979520B (en) | Message processing method and message processing device | |
| US8856230B2 (en) | In browser real time collaboration lists and forms | |
| CN110503559B (en) | Block chain-based clearing method, device, equipment and computer storage medium | |
| CN111737334A (en) | Data reporting method, device, equipment and storage medium | |
| CN114385382A (en) | Light application access method and device, computer equipment and storage medium | |
| US9577967B2 (en) | Method and system for managing an informational site using a social networking application | |
| CN109040331B (en) | Electronic business card processing method and device, computing equipment and storage medium | |
| CN110673970A (en) | Cross-process calling system and method based on web application | |
| CN103139306A (en) | Method facing forwarding of browse clipping page information and obtaining of enterprise cooperation information interaction | |
| CN110874278A (en) | Embedding method of external system, workflow system, device and storage medium | |
| CN114513761A (en) | Message interaction method, system, terminal device and medium | |
| CN113127335A (en) | System testing method and device | |
| CN114417318A (en) | Third-party page jumping method and device and electronic equipment | |
| EP2913957B1 (en) | Method and apparatus for controlling internet access | |
| CN113934557A (en) | Method for communicating small program with webpage, related equipment and system | |
| CN102236665A (en) | Page loading method and page loading 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 |