CN114513761B - Message interaction method, system, terminal equipment and medium - Google Patents

Message interaction method, system, terminal equipment and medium Download PDF

Info

Publication number
CN114513761B
CN114513761B CN202210101522.5A CN202210101522A CN114513761B CN 114513761 B CN114513761 B CN 114513761B CN 202210101522 A CN202210101522 A CN 202210101522A CN 114513761 B CN114513761 B CN 114513761B
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.)
Active
Application number
CN202210101522.5A
Other languages
Chinese (zh)
Other versions
CN114513761A (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.)
Shenzhen Montnets Technology Co ltd
Original Assignee
Shenzhen Montnets Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Montnets Technology Co ltd filed Critical Shenzhen Montnets Technology Co ltd
Priority to CN202210101522.5A priority Critical patent/CN114513761B/en
Publication of CN114513761A publication Critical patent/CN114513761A/en
Application granted granted Critical
Publication of CN114513761B publication Critical patent/CN114513761B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12Messaging; Mailboxes; Announcements
    • 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/10Multimedia information
    • 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/02Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06Authentication
    • YGENERAL 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
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE 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/00Reducing energy consumption in communication networks
    • Y02D30/70Reducing 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: the method comprises the steps of sending a preset message template to the client terminal, and receiving an uplink message which is returned by the client terminal and is triggered by a click module or a keyword module in the preset message template; if the uplink message is the 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 transmitting the first downlink message template to the client terminal; if the uplink message is not the preset URL, judging whether service data need to be acquired from a service system or not based on the uplink message; if yes, acquiring service data from the service system through a data engine, assembling the service data into a second downlink message template, and transmitting the second downlink message template to the client terminal. The invention can realize high-efficiency message interaction.

Description

Message interaction method, system, terminal equipment and medium
Technical Field
The present invention relates to the field of data transmission, and in particular, to a message interaction method, a system, a terminal device, and a computer readable storage medium.
Background
Currently, unified message centers (Unified Message Center, UMC) have multi-channel communication capability, and can send various messages such as 5G messages, rich media messages, short messages, weChat, email, APP, and the like, thereby having the capability of mutual conversion, interconnection and intercommunication, multi-network integration and multi-party delivery among various messages.
In the process of docking 5G message items such as a plurality of items, the enterprise user hopes that the 5G message has the capability of carrying out data bidirectional interaction with an enterprise service system in the actual use scene of the 5G message, and the current UMC unified message center only supports the limited interaction capability of sending 5G static messages and templates in interaction, so as to meet the actual landing requirement of the enterprise user, the UMC unified message center faces the following three major problems:
1. the template dynamic parameter data can only be actively transmitted by a service system, and the bidirectional interaction of the data can not be realized;
2. the interaction capability of the message is limited, and functions of opening APP, H5 production and the like cannot be realized;
3. the relation between the template dynamic parameter data and the judging event and the template lacks effective management, and the dynamic template cannot acquire data in uplink and downlink interaction, so that interaction can be performed only through the static template.
In summary, the current 5G message information exchange function is not complete, so that the message exchange efficiency is low, and the user experience is further affected.
Disclosure of Invention
The invention mainly aims at providing a message interaction method, a 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:
issuing 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 transmitting the first downlink message template to the client terminal;
if the uplink message is not the preset URL, judging whether service data need to be acquired from the service system or not based on the uplink message;
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 transmitting the second downlink message template to the client terminal.
Optionally, the click module comprises a button and/or a hover menu;
the message interaction method further comprises the following steps:
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 service data needs to be acquired from the service system based on the uplink message, the method further includes:
if the service system judges that the corresponding service data does not need to be acquired based on the uplink message, acquiring a message template matched with the uplink message, and transmitting 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 is judged to be required to be authenticated, a preset authentication mode is adopted to authenticate the client terminal, and the downlink message template is issued to the client terminal after the authentication is passed;
And if the fact that the client terminal does not need to be authenticated is judged, the downlink message template is issued to the client terminal.
Optionally, the preset authentication mode includes: one-key login authentication or account login authentication, wherein the step of one-key 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 the URL bound by the click module;
judging whether the message number is consistent with the current number or not;
if the message number is consistent with the current number, passing authentication and allowing the client terminal to log in;
the step of account login authentication 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 or not;
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 period, the preset message template is issued to the client terminal again;
if the user information is not received within the preset second waiting time period, the response to the uplink message is not performed.
To achieve the above object, the present invention also provides a message interaction system, including:
the sending module is used for sending an H5 page corresponding to the preset URL to the client terminal if the uplink message is the preset URL;
the first issuing module is used for receiving user information collected by the client terminal based on the H5 page, obtaining a first downlink message template based on the user information in a matching mode, and issuing the first downlink message template to the client terminal;
the judging module is used for judging whether service data are required to be acquired from the service system or not based on the uplink message;
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 as described above when running.
To achieve the above object, the present invention also provides a terminal device including: a memory, a processor and a message interaction program stored on the memory and executable on the processor, which when executed by the processor implements the steps of the message interaction method as described above.
In addition, to achieve the above object, the present invention also proposes a computer-readable storage medium having stored thereon a message interaction program which, 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, a terminal device, a computer readable storage medium and a computer program product, wherein 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 transmitting the first downlink message template to the client terminal; if the uplink message is not the preset URL, judging whether service data need to be acquired from the service system or not based on the uplink message; 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 transmitting the second downlink message template to the client terminal.
Compared with the problem of limited 5G message interaction function in the prior art, the invention opens the data interaction channel between the server and the client service system according to the message interaction among the client terminal, the server and the service system, realizes the active acquisition of service data from the service system, avoids interface modification work caused by parameter mapping relation modification through automatically identifying the dynamic parameters of the message template and the service system fields related to the visual interface, improves the flexibility of the inter-system data interaction mode, further can issue corresponding message templates according to the user requirement of the client terminal, realizes efficient and accurate message pushing, and enables enterprises to carry out informatization development of the services 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 flow chart of an embodiment of a message interaction method according to the present invention;
FIG. 3 is a schematic diagram of a message interaction scenario according to an embodiment of the message interaction method of the present invention;
FIG. 4 is a schematic diagram of a click event flow according to an embodiment of the message interaction method of the present invention;
FIG. 5 is a schematic diagram of 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 procedure according to an embodiment of the message interaction method of the present invention;
FIG. 7 is a schematic diagram of an H5 event flow according to an embodiment of a message interaction method of the present invention;
FIG. 8 is a schematic diagram of an account login procedure according to an embodiment of the message interaction method of the present invention;
fig. 9 is a schematic diagram of functional modules of an embodiment of a message interaction system according to the present invention.
The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
Detailed Description
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
Referring to fig. 1, fig. 1 is a schematic device structure of a hardware running 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 be a smart phone, a personal computer, a server, or 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 the communication bus 1002 is used to enable connected communication between these components. The user interface 1003 may include a Display, an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may further 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 stable memory (non-volatile memory), such as a disk memory. The memory 1005 may also optionally be a storage device separate from the processor 1001 described above.
It will be appreciated by those skilled in the art that the device structure shown in fig. 1 is not limiting of the device and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.
As shown in fig. 1, an operating system, a network communication module, a user interface module, and a message interaction program may be included in the memory 1005, which is a type of computer storage medium. An operating system is a program that manages and controls the hardware and software resources of a device, supporting the execution of message interaction programs, as well as other software or programs. In the device shown in fig. 1, the user interface 1003 is mainly used for data communication with a client terminal; the network interface 1004 is mainly used for establishing communication connection with a server; and the processor 1001 may be configured to call a message interactive program stored in the memory 1005 and perform the following operations:
issuing 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 transmitting the first downlink message template to the client terminal;
if the uplink message is not the preset URL, judging whether service data need to be acquired from the service system or not based on the uplink message;
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 transmitting the second downlink message template to the client terminal.
Further, the click module includes buttons and/or hover menus, and the processor 1001 may be further configured to invoke a message interaction program stored in the memory 1005, and further perform the following operations:
binding the preset URL with the button in advance.
Further, 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 assembling the service data to 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:
If the service system judges that the corresponding service data does not need to be acquired based on the uplink message, acquiring a message template matched with the uplink message, and transmitting the message template matched with the uplink message to the client terminal.
Further, the processor 1001 may be further configured to invoke a message interaction 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 is judged to be required to be authenticated, a preset authentication mode is adopted to authenticate the client terminal, and the downlink message template is issued to the client terminal after the authentication is passed;
and if the fact that the client terminal does not need to be authenticated is judged, the downlink message template is issued to the client terminal.
Further, the preset authentication mode includes: the step of authenticating the client terminal by adopting a preset authentication mode comprises the following steps of:
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 the URL bound by the click module;
Judging whether the message number is consistent with the current number or not;
if the message number is consistent with the current number, passing authentication and allowing the client terminal 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 or not;
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 invoke a 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 period, the preset message template is issued to the client terminal again;
if the user information is not received within the preset second waiting time period, the response to the uplink message is not performed.
Referring to fig. 2, fig. 2 is a flow chart of a first embodiment of the message interaction method 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 logic order is shown in the flowchart, in some cases, steps shown or described may be performed in a different order from that herein.
The application scene of the invention can comprise: including 5G messages, sms, smart sms, 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, and the server is pre-configured with a large number of message templates so as to realize the issuing of the message templates required by the users of the mobile phone terminal, and the service system contains a large number of service data. As shown in fig. 3, the interface is an interface in the UMC unified message, where the interface includes a start, a message template, a click, a keyword, a fixed button, a suspension menu, H5 (fifth generation HTML), a judgment, and the like, and a back-end developer can view the interaction scene and configure the message interaction flow on the interface. Wherein, the template is 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 in back of the message template; clicking the button/menu which can only connect the event as the reply template in front, and connecting the message template in back; the button/menu that the event is to open H5 can only be connected in front of H5, and the message must be connected in back; whereas for buttons/menus, only buttons/menus with events that open H5 and reply templates can connect to subsequent nodes.
Step S10, a preset message template is issued 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) 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.
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 suspension 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 as to implement accurate pushing of the message, meet various operation requirements of the client terminal, and enable enterprises to perform informationized development of production, marketing and other services. 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 suspension menu or an uplink keyword in the message module, so as to implement personalized sending 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 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 transmitting the first downlink message template to the client terminal;
it should be noted that, in this embodiment, as shown in the H5 event flow diagram of fig. 4, for other buttons (such as an "active registration" button) on a preset message template, if the button is pre-bound to a URL (Uniform Resource Locator ), the server (i.e. the UMC unified message center) sends an H5 page corresponding to the URL to the client terminal, so that the user can click the corresponding button directly on the client terminal, jump to an H5 page (such as an active registration page) collected by the URL corresponding to the URL bound to the button, fill in relevant information on the H5 page, submit the relevant information to the UMC unified message center, and the UMC unified message center matches the corresponding message template (such as a corresponding message template according to a keyword in the registration information after the registration information), and then send the message template to the user who issues the message template to the client terminal. In this case, the UMC unified messaging center does not need to acquire 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, judging whether service data are required to be acquired from the service system or not based on the uplink message;
after receiving the 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 judge whether service data matched with the uplink message is required to be acquired from a service system through a data engine according to the uplink message.
In this embodiment, the manner in which the client terminal generates the uplink message may include a fixed button, a suspension 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 sends 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 to a URL, so as to determine whether service data corresponding to the uplink message needs to be acquired from the service system.
Further, the message interaction method of the invention further comprises the following steps:
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 transmitting 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 service data in the plug-in information obtaining service system by means of interface docking or accessing a database, and the like, so as to realize active data obtaining from the service system, and open a data interaction channel between the server and the client service system (e.g., financial system, client system, subscription record system, etc.), so as to provide a basic link for later bidirectional data query and push.
Specifically, for example, as shown in the click event flow chart of fig. 5, after the server (i.e. the UMC unified message center) acquires the uplink message and determines that service data matched with the uplink message needs to be acquired from the service system according to the uplink message, the server will acquire the corresponding service data in the service system based on the data engine through a corresponding interface docking or database accessing mode, and the like, and assemble the service data into a corresponding preset template to obtain a downlink message template, so as to send the downlink message template to the client terminal.
In this embodiment, the visual interface configuration can be performed on the user information judgment rule of the client terminal, and the mapping binding can be performed on the dynamic parameters of the message template and the data source fields 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 the systems is improved.
In this embodiment, the visual interface associates a service system field,
further, after the step of determining whether the service data needs to be acquired from the service system based on the uplink message in the step S40, the method further includes:
and step S60, if the fact that the corresponding service data do not need to be acquired from the service system is judged based on the uplink message, acquiring a message template matched with the uplink message, and transmitting the message template matched with the uplink message to the client terminal.
After the server acquires the uplink message and judges that the service data is not required 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 transmits the message template to the client terminal.
In this embodiment, since the server is preset with the message template bound with 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 send the message template bound with the uplink keyword to the client terminal. In addition, if it is detected that the uplink message is triggered by the click module, i.e. the button, the server needs to further acquire the corresponding service data from the service system.
Further, in the step S50, the "issue the second downlink message template to the client terminal" may include:
step S501, determining 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 is judged to need to be authenticated, a preset authentication mode is adopted to authenticate the client terminal, and after the authentication is passed, the downlink message template is issued to the client terminal;
step S503, if it is determined that authentication is not required for the client terminal, the downlink message template is issued to the client terminal.
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 authentication, if the service data needs authentication, the server issues the downlink message template after the authentication is passed.
Specifically, for example, as shown in the schematic message template authentication reply flow diagram of fig. 6, the message template authentication reply flow includes: when the server (namely, UMC unified message center) recognizes that the downlink message template to be replied is a message which can be sent only after the user of the client terminal logs in and authenticates (such as a transaction bill), the UMC unified message center firstly issues a login authentication message template which is set in advance, the user jumps to an H5 page corresponding to the URL bound by clicking a button on the message template to carry out mobile phone number one-key login, the UMC unified message center issues the downlink message template to the client terminal after detecting that the user of the client terminal logs in successfully, or acquires a user information form filled in by the user on the H5 page, and issues the downlink message template to the client terminal after comparing the user form information with the user service system information successfully. After judging 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 to directly issue the downlink message template to the corresponding client terminal, thereby realizing the rapid issue of the downlink message template, guaranteeing the safety of data transmission and further improving the user experience.
Further, in the above step S50, "assembling the service data into the second downlink message template" may include:
step S504, the business data is assembled to a preset template of the server to obtain a second downlink message template.
In this embodiment, since a large number of message templates are preconfigured in the server, when it is determined that service data needs to be acquired from the service system, the service system acquired by interfacing or accessing a database based on a data engine through a corresponding interface may be directly assembled into an existing corresponding message template to obtain a required downlink message template.
Further, the message interaction method of the invention further comprises the following steps:
step S70, binding the preset URL with the button in advance.
It should be noted that, in this embodiment, the clicking module includes a button and/or a hover menu, and the user of the client terminal performs a clicking operation on the button and/or hover menu, where the hover menu may be an uplink keyword.
Specifically, for example, a button (such as an "active registration" button) in the click module is bound with a preset URL in advance, so that when a user of the client terminal clicks the button, the user can directly jump to an H5 page corresponding to the bound URL, and further, the user can fill in relevant form information and the like in the H5 page, and send an uplink message containing 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 suspension 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 service data matched with the uplink message is required to be acquired from the service system through a data engine according to the uplink message. After the server acquires the uplink message and judges 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 based on the data engine through the corresponding interface docking or database accessing modes and the like, and assembles the service data into the corresponding preset template to obtain the downlink message template. After the server acquires the service data from the service system and assembles the service data into a preset template to obtain a downlink message template, the server further judges whether the service data in the downlink message template needs authentication or not so as to allow the client terminal to log in after the authentication is passed. After judging that the service data in the downlink message template does not need authentication, the server directly transmits the downlink message template to the corresponding client terminal. If the business data in the downlink message template needs to be authenticated, the user skips to the H5 page corresponding to the URL bound by the button by clicking the button on the message template to carry out one-key login of the mobile phone number, and the downlink message template is issued to the client terminal after the client terminal is successfully logged in, or the user information form filled in by the user at the client terminal is obtained, and the downlink message template is issued to the client terminal after the user form information is successfully compared with the client business system information.
Compared with the problem of limited 5G message interaction function in the prior art, the invention opens the data interaction channel between the server and the client service system according to the message interaction among the client terminal, the server and the service system, realizes the active acquisition of service data from the service system, can perform visual interface configuration on the user information judgment rule of the client terminal, and performs mapping binding on the dynamic parameters of the template and the data source fields, thereby avoiding interface modification work caused by parameter mapping relation modification, improving the flexibility of the data interaction mode between systems, further being capable of issuing corresponding message templates according to the user requirements of the client terminal, realizing efficient and accurate message pushing, and enabling enterprises to perform informationized development of production, marketing and other services.
Further, based on the first embodiment of the message interaction method of the present invention, a second embodiment of the message interaction method of the present invention is presented.
The main difference between the present embodiment and the first embodiment described above is that the preset authentication method includes: one-key login authentication or account login authentication, wherein the step of one-key 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 method includes: and one-key login authentication, namely, a user of the client terminal skips to an H5 page corresponding to the URL bound by the button by clicking the button on the message template to carry out one-key login of the mobile phone number, and the server sends a downlink message template to the client terminal after the client terminal is successfully logged in.
Specifically, for example, as shown in a one-key login flow chart in fig. 7, after determining that service data in a downlink message template needs to be authenticated, the server will issue a "login authentication" message template, and the user of the client terminal may click a one-key login button in the "login authentication" message template, go to an H5 page corresponding to the URL bound by the button to perform one-key login, the server will obtain a login message triggered based on clicking the one-key login button, obtain a corresponding message number from the login message, compare the message number with the current number of the client terminal, determine whether the message number is consistent with the current number of the client terminal, if so, pass authentication, and allow the user of the client terminal to perform login.
The step of account login authentication comprises the following steps:
step S5024, obtaining user information generated through the H5 page based on the account login authentication, and obtaining corresponding user source data from the service system through the data engine based on the user information;
step S5025, judging whether the user information is consistent with the user source data;
and 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 method includes: and (3) account login authentication, namely acquiring a user information form filled in by a user on an H5 page of the client terminal, and after the user form information is successfully compared with the client service system information, issuing a downlink message template to the client terminal.
Specifically, for example, as shown in the account login flow chart of fig. 8, after determining that service data in a downlink message template needs to be authenticated, a server issues a login authentication message template, and a user of a client terminal may click a skip button in the login authentication message template, go to an H5 page corresponding to a URL bound to the button to fill in user information, submit the user information to the server, obtain user source data in a service system according to the user information by means of interface-based docking or database access and the like through a data engine, compare the user information with the user source data, determine whether the user information is consistent with the user source data, if so, the server determines that authentication is passed, and allows the client terminal to log in.
Further, the message interaction method of the invention further comprises the following steps:
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 period, the preset message template is issued to the client terminal again;
and b, if the user information is not received in the preset second waiting time period, not responding to the uplink message.
It should be noted that, in this embodiment, if the server has already sent the message template including the skip to the H5 page 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 waiting 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, namely does not respond to the interaction of the client terminal. In this embodiment, the preset second waiting period is longer than the preset first waiting period.
In this embodiment, the server may implement authentication of the user of the client terminal through two modes of one-key login authentication and account login authentication, and in addition, the server needs to receive the H5 page information within a preset waiting duration, otherwise, the client terminal cannot submit the H5 page information to the server any more. Therefore, the invention realizes the efficient interaction efficiency of the server and the client terminal.
In addition, the embodiment of the invention also provides a message interaction system, referring to fig. 9, fig. 9 is a schematic diagram of functional modules of an embodiment of the message interaction system of the 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;
the sending module 20 is configured to send an H5 page corresponding to a preset URL to the client terminal if the uplink message is the preset URL;
the first issuing module 30 is 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 by 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 clicking module comprises a button and/or a suspension menu, and the message interaction system further comprises:
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 a message template matched with the uplink message if the fact that the corresponding service data do not need to be acquired from the service system is judged based on the uplink message, and issuing the message template matched with the uplink message to the client terminal.
Further, the second issuing module 50 further includes:
The judging unit is used for judging whether the client terminal needs to be authenticated or not 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 judging that the client terminal needs 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 fact that the client terminal does not need to be authenticated is judged.
Further, the preset authentication mode includes: one-key login authentication or account login authentication, the first issuing unit includes:
the first comparison subunit is used for obtaining a corresponding message number based on one-key login authentication triggered by the 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 the URL bound by the click module;
a first judging subunit, configured to judge whether the message number is consistent with the current number;
and the first permission subunit is used for passing the authentication and permitting the client terminal to log in if the message number is consistent with the current number.
The second comparison subunit is used for 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;
a second judging subunit, configured to judge whether the user information is consistent with the user source data;
and the third permission subunit is used for passing the authentication if the user information is judged to be consistent with the user source data, and allowing the client terminal to log in.
Further, the message interaction system of the present invention further comprises:
the secondary issuing module is used for issuing 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 the preset first waiting time period;
and the response module is used for not responding to the uplink message if the user information is not received in the preset second waiting time period.
The specific implementation manner of each functional module of the message interaction system is basically the same as that of each embodiment of the message interaction method, and is not described herein.
In addition, the embodiment of the invention also provides a computer readable storage medium, wherein the computer readable storage medium stores a message interaction program, and the message interaction program realizes the steps of the message interaction method when being executed by a processor.
Embodiments of the message interaction system and the computer readable storage medium of the present invention may refer to embodiments of the message interaction method of the present invention, and are not described herein.
Furthermore, embodiments of the present invention provide a computer program product comprising a computer program which, when executed by a processor, implements the steps of a message interaction method according to any of the embodiments of the message interaction method above.
The specific embodiments of the computer program product of the present invention are substantially the same as the embodiments of the message interaction method described above, and will not be described herein.
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 one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising several instructions for causing a terminal device (which may be a smart phone, a personal computer, a server, etc.) to perform the method according to the embodiments of the present invention.
The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.

Claims (9)

1. A message interaction method, characterized in that it is applied to a server, said message interaction method comprising the steps of:
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 transmitting the first downlink message template to the client terminal;
if the uplink message is not the preset URL, judging whether service data need to be acquired from a service system or not based on the uplink message;
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 transmitting the second downlink message template to the client terminal;
if the service system judges that the corresponding service data does not need to be acquired based on the uplink message, acquiring a message template matched with the uplink message, and transmitting the message template matched with the uplink message to the client terminal.
2. The message interaction method of claim 1, wherein the click module comprises a button and/or a hover menu;
the message interaction method further comprises the following steps:
binding the preset URL with the button in advance.
3. The message interaction method of claim 1, wherein the step of assembling the service data into a second downstream message template comprises:
and assembling the service data to a preset template of the server to obtain a second downlink message template.
4. The message interaction method of claim 1, wherein the step of issuing the second downstream 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 is judged to be required to be authenticated, a preset authentication mode is adopted to authenticate the client terminal, and the downlink message template is issued to the client terminal after the authentication is passed;
and if the fact that the client terminal does not need to be authenticated is judged, the downlink message template is issued to the client terminal.
5. The message interaction method as claimed in claim 4, wherein the preset authentication means comprises: one-key login authentication or account login authentication, wherein the step of one-key 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 the URL bound by the click module;
judging whether the message number is consistent with the current number or not;
if the message number is consistent with the current number, passing authentication and allowing the client terminal to log in;
the step of account login authentication 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 or not;
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.
6. 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 period, the preset message template is issued again to the client terminal;
if the user information is not received within the preset second waiting time period, the response to the uplink message is not performed.
7. A message interaction system, the message interaction system comprising:
the receiving module is used for transmitting 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 the clicking module or the keyword module in the preset message template;
the sending module is used for sending an H5 page corresponding to the preset URL to the client terminal if the uplink message is the preset URL;
the first issuing module is used for receiving user information collected by the client terminal based on the H5 page, obtaining a first downlink message template based on the user information in a matching mode, and issuing the first downlink message template to the client terminal;
the judging module is used for judging whether service data are required to be acquired from the service system or not based on the uplink message;
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;
And the third issuing module is used for acquiring a message template matched with the uplink message if the fact that the corresponding service data do not need to be acquired from the service system is judged based on the uplink message, and issuing the message template matched with the uplink message to the client terminal.
8. A terminal device, characterized in that it comprises a memory, a processor and a message interaction program stored on the memory and executable on the processor, which message interaction program, when executed by the processor, implements the steps of the message interaction method according to any of claims 1 to 6.
9. A computer readable storage medium, characterized in that it has stored thereon a message interaction program, which when executed by a processor, implements the steps of the message interaction method according to any of claims 1 to 6.
CN202210101522.5A 2022-01-27 2022-01-27 Message interaction method, system, terminal equipment and medium Active CN114513761B (en)

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 CN114513761A (en) 2022-05-17
CN114513761B true 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 (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8516047B2 (en) * 2000-11-06 2013-08-20 Rick Castanho System and method for service specific notification
US10148603B2 (en) * 2012-07-12 2018-12-04 Salesforce.Com, Inc. Methods and systems for generating electronic messages based upon dynamic content
US10686745B2 (en) * 2015-12-28 2020-06-16 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

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
刘涛 ; 于宏文 ; 祝志凌 ; .华中电网调度生产短信息平台研究开发与应用.华中电力.2007,(第01期),全文. *

Also Published As

Publication number Publication date
CN114513761A (en) 2022-05-17

Similar Documents

Publication Publication Date Title
JP6517948B2 (en) Cloud printer sharing method in cloud print system, cloud server, cloud print system
US10834031B2 (en) Information exchange method, client, and apparatus
US9461834B2 (en) Electronic document provision to an online meeting
US20200213403A1 (en) Information transmission method and device
CN107146074B (en) Work order task cooperative processing method and device and computer readable storage medium
RU2407232C2 (en) Method, mobile terminal, system and computer software product for online attribution of content
US20180143973A1 (en) Semi-automated form-based chat
CN107438054B (en) Method and system for realizing menu information control based on public platform
CN109391476B (en) Network communication method, device and system
US10326714B2 (en) Instant messaging with non subscriber users
CN107979520B (en) Message processing method and message processing device
US11792144B2 (en) Format-dynamic string processing in group-based communication systems
US9106596B2 (en) Method and apparatus of configuring a data broadcast service
CN114513761B (en) Message interaction method, system, terminal equipment and medium
EP3872726A1 (en) Messaging campaign manager, messaging campaign manager system, bulk or mass messaging system, method of bulk or mass messaging, computer program, computer-readable medium, graphical user interface
CN103051699A (en) Method for forwarding information and acquiring mutual information by enterprises based on web browser
CN109040331B (en) Electronic business card processing method and device, computing equipment and storage medium
CN103139306A (en) Method facing forwarding of browse clipping page information and obtaining of enterprise cooperation information interaction
CN110673970A (en) Cross-process calling system and method based on web application
US20100296637A1 (en) Service Processing Method, Communication System and Related Device
US12021821B2 (en) Methods and apparatuses for managing data integration between an external email resource and a group-based communication system
CN113014404B (en) Message transmission method and device, server and second client
KR102461836B1 (en) Apparatus and method for connecting chatbot
EP2913957B1 (en) Method and apparatus for controlling internet access
US12034885B2 (en) Method for processing a request from a communication terminal

Legal Events

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