CN117176793A - Automatic forwarding method, system, device, equipment and medium for uplink message - Google Patents
Automatic forwarding method, system, device, equipment and medium for uplink message Download PDFInfo
- Publication number
- CN117176793A CN117176793A CN202311123123.XA CN202311123123A CN117176793A CN 117176793 A CN117176793 A CN 117176793A CN 202311123123 A CN202311123123 A CN 202311123123A CN 117176793 A CN117176793 A CN 117176793A
- Authority
- CN
- China
- Prior art keywords
- service
- push
- uplink message
- uplink
- message
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 54
- 238000012545 processing Methods 0.000 claims abstract description 45
- 230000008569 process Effects 0.000 claims abstract description 14
- 230000004044 response Effects 0.000 claims description 10
- 230000026676 system process Effects 0.000 claims description 5
- 238000004891 communication Methods 0.000 abstract description 8
- 238000010586 diagram Methods 0.000 description 12
- 238000004590 computer program Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 8
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000006467 substitution reaction Methods 0.000 description 3
- 238000003491 array Methods 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- SGUAFYQXFOLMHL-UHFFFAOYSA-N 2-hydroxy-5-{1-hydroxy-2-[(4-phenylbutan-2-yl)amino]ethyl}benzamide Chemical compound C=1C=C(O)C(C(N)=O)=CC=1C(O)CNC(C)CCC1=CC=CC=C1 SGUAFYQXFOLMHL-UHFFFAOYSA-N 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 229940108522 trandate Drugs 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- 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
- Information Transfer Between Computers (AREA)
Abstract
The application discloses an automatic forwarding method, a system, a device, equipment and a medium for uplink messages, wherein the method comprises the following steps: acquiring an uplink message; identifying the type and content of the uplink message; if the identification result is that the uplink message belongs to the push service keyword, acquiring a target push service matched with the push service keyword from a plurality of preset push services; and forwarding the request body parameters corresponding to the target push service to the service system through the push interface so as to enable the service system to process the uplink message. The application can improve the processing efficiency of the uplink message and can be widely applied to the field of message communication.
Description
Technical Field
The present application relates to the field of message communication, and in particular, to a method, a system, an apparatus, a device, and a medium for automatically forwarding an uplink message.
Background
The downlink message is that the system sends notification content to the user through different communication channels, and the uplink message is that the user replies to the downlink message through the communication channels. Business systems in enterprises actively push messages to users through downlink messages of a message processing platform; and after receiving the uplink message, the message processing platform collects and processes the message and submits the message to a business system corresponding to the enterprise, and the business system executes corresponding data processing according to the uplink message of the user. The relevant keyword information of the user can be received through the uplink message, and corresponding services are triggered according to the uplink keyword information, for example, the client can reply the keyword in an uplink manner, and the balance in the card is inquired.
According to the prior art, a business system in an enterprise needs to develop different calling business scene interfaces aiming at different scenes; in the message processing platform, a keyword configuration page and a business scene interface associated with the keyword need to be developed. When the user uplink message is sent, the operator pushes the user uplink message to the message processing platform, the message processing platform identifies whether the uplink content contains keywords, if yes, a corresponding service scene is found according to the keywords, then a service scene interface is called, the keywords and the uplink message are pushed to other service systems of the enterprise according to the interface format requirement, and then the service system performs the next service operation.
Fig. 1 is a schematic diagram of a prior art implementation, and if there are multiple service systems to receive uplink keyword information, multiple service interfaces need to be issued to an ESB (Enterprise Service Bus ), and the message processing platform needs to interface multiple service interfaces according to different service scenarios. The prior art has the following problems: 1) Different service systems are needed to be used, and when the uplink information of a user is needed to be received, different service scenes need to develop a set of interfaces respectively; 2) The message processing platform calls different interfaces according to different service scenes; 3) Since the interface services are all published in the ESB, the data call also needs to pass through the ESB, so as the service scenario increases, the ESB service pressure increases gradually.
Disclosure of Invention
In view of the above, the present application provides a method, a system, a device and a medium for automatically forwarding an uplink message, so as to improve the processing efficiency of the uplink message.
One aspect of the present application provides an automatic forwarding method for uplink messages, including:
acquiring an uplink message;
identifying the type and content of the uplink message;
if the identification result is that the uplink message belongs to a push service keyword, acquiring a target push service matched with the push service keyword from a plurality of preset push services;
and forwarding the request body parameters corresponding to the target push service to a service system through a push interface so that the service system can process the uplink message.
Optionally, the acquiring the uplink message includes:
acquiring an uplink message sent by a user terminal;
or inquiring the data in the uplink record table according to a set period through the push interface; and matching the uplink record list with the key words configured according to the automatic reporting, and obtaining the uplink message by matching.
Optionally, the forwarding, through a push interface, a request body parameter corresponding to the target push service to a service system, so that the service system processes the uplink message, includes:
and pushing the request body parameters corresponding to the target push service to a designated path of the service system through a push interface so as to enable the service system to process the uplink message.
Optionally, the method further comprises:
and if the identification result is that the uplink message does not belong to the push service keyword, storing the uplink message into a database.
Optionally, the method further comprises:
receiving response body parameters returned by the service system;
and judging whether the request body parameters corresponding to the target push service are forwarded to the service system or not according to the response body parameters.
Optionally, the method further includes a step of presetting a plurality of push services, and the step of presetting the plurality of push services includes the steps of:
acquiring a plurality of keywords, a service scene name corresponding to each keyword, a request body parameter and a called service system ID;
setting each keyword and the corresponding service scene name, the request body parameter and the called service system ID as a push service to obtain the push service corresponding to each keyword.
Optionally, the method further comprises a step of configuring a new push service, the step of configuring a new push service comprising the steps of:
acquiring a new keyword, a service scene name corresponding to the new keyword, a request body parameter and a called service system ID;
and setting the new keyword, the corresponding service scene name, the request body parameter and the called service system ID as a new push service.
The application also provides an uplink message automatic forwarding system, which comprises a user terminal, a message processing platform and a service system;
the user terminal is used for sending uplink messages to the message processing platform;
the message processing platform is used for executing the automatic forwarding method of the uplink message;
the service system is used for receiving and processing the uplink message sent by the message processing platform.
Another aspect of the present application also provides an automatic forwarding device for uplink messages, including:
a first unit, configured to obtain an uplink message;
a second unit, configured to identify a type and a content of the uplink message;
a third unit, configured to obtain, if the identification result indicates that the uplink message belongs to a push service keyword, a target push service that matches the push service keyword from a plurality of preset push services;
and a fourth unit, configured to forward, through a push interface, a request body parameter corresponding to the target push service to a service system, so that the service system processes the uplink message.
Another aspect of the application also provides an electronic device comprising a processor and a memory;
the memory is used for storing programs;
the processor executes the program to implement the method.
Another aspect of the present application also provides a computer-readable storage medium storing a program that is executed by a processor to implement the method.
The application also discloses a computer program product or a computer program comprising computer instructions stored in a computer readable storage medium. The computer instructions may be read from a computer-readable storage medium by a processor of an electronic device, and executed by the processor, cause the electronic device to perform the method described above.
The application firstly obtains the uplink message, identifies the type and the content of the uplink message, obtains the target push service matched with the push service key from a plurality of preset push services if the identification result is that the uplink message belongs to the push service key, and forwards the request body parameter corresponding to the target push service to the service system through the push interface so as to be used for the service system to process the uplink message. Because the prior art needs to repeatedly develop a new push interface to realize message push when a service scene is newly added each time, the application can acquire the target push service matched with the push service keywords from a plurality of preset push services, and then realize automatic forwarding of the uplink message through one push interface, and can push the uplink message to a service system without developing a new push interface.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a diagram illustrating a related art data communication between a message processing platform and a related service system;
fig. 2 is a schematic flow chart of an automatic forwarding method for uplink messages according to an embodiment of the present application;
FIG. 3 is an exemplary diagram of an interface for configuring a push service according to an embodiment of the present application;
FIG. 4 is an exemplary diagram of an interface of a new push service according to an embodiment of the present application;
fig. 5 is a schematic diagram of data communication between a message processing platform and a related service system according to an embodiment of the present application;
fig. 6 is a schematic flow chart of processing an uplink message according to an embodiment of the present application;
fig. 7 is a block diagram of an automatic forwarding device for uplink messages according to an embodiment of the present application.
Detailed Description
The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. 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 application.
It should be noted that although functional block division is performed in a device diagram and a logic sequence is shown in a flowchart, in some cases, the steps shown or described may be performed in a different order than the block division in the device, or in the flowchart.
The terms first, second and the like in the description and in the claims and in the above-described figures, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. Moreover, 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.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the application only and is not intended to be limiting of the application.
Referring to fig. 2, an embodiment of the present application provides an automatic forwarding method for uplink messages, which includes steps S200 to S230, specifically as follows:
s200: and obtaining the uplink message.
Further, S200 may include:
acquiring an uplink message sent by a user terminal;
or inquiring the data in the uplink record table according to a set period through the push interface; and matching the uplink record list with the key words configured according to the automatic reporting, and obtaining the uplink message by matching.
Specifically, a timing task (the timing time is configured by a configuration file) may be set in the push server. The timing task queries the data of the uplink record table, matches the latest uplink data according to the automatically-reported configured keywords and the matching mode.
After matching the automatic reporting key word, the ESB interface is called, and the message processing platform transmits the set parameters (the detailed view of the request parameters below) to report to the designated push address. The push protocol defaults to the HTTP protocol and adopts an XML message format.
After the request is completed, the service system returns a corresponding response code (detailed parameter checks the following response body parameter) to the message processing platform according to whether the receiving is successful or not, so that the message processing platform is informed of whether the uplink message pushing is successful or not.
S210: and identifying the type and the content of the uplink message.
S220: and if the identification result is that the uplink message belongs to the push service keyword, acquiring a target push service matched with the push service keyword from a plurality of preset push services.
Firstly, describing the push service, the embodiment of the present application may further include a step of presetting a plurality of push services, where the step of presetting the plurality of push services includes the following steps:
acquiring a plurality of keywords, a service scene name corresponding to each keyword, a request body parameter and a called service system ID;
setting each keyword and the corresponding service scene name, the request body parameter and the called service system ID as a push service to obtain the push service corresponding to each keyword.
Specifically, referring to fig. 3, an exemplary diagram of an interface for configuring a push service is provided in an embodiment of the present application.
The data on the push service setting list may include currently set service scenes, corresponding keywords, and service system coding information of the service.
In addition, the embodiment of the application can further comprise a step of configuring a new push service, wherein the step of configuring the new push service comprises the following steps:
acquiring a new keyword, a service scene name corresponding to the new keyword, a request body parameter and a called service system ID;
and setting the new keyword, the corresponding service scene name, the request body parameter and the called service system ID as a new push service.
Specifically, referring to fig. 4, an exemplary interface diagram of a new push service is provided in an embodiment of the present application.
The user clicks the "new" button of the interface shown in fig. 3, and then the embodiment of the application responds to the user operation to open the new keyword window, and the related information and keyword information of the service system need to be configured and invoked.
The service code and caller system ID may be defined according to the ESB specification. When the message processing platform recognizes the keyword, the content can be pushed to the designated service system according to the format of the push template.
Further, S220 may include:
and pushing the request body parameters corresponding to the target push service to a designated path of the service system through a push interface so as to enable the service system to process the uplink message.
In addition, the embodiment of the application can further comprise:
and if the identification result is that the uplink message does not belong to the push service keyword, storing the uplink message into a database.
S230: and forwarding the request body parameters corresponding to the target push service to a service system through a push interface so that the service system can process the uplink message.
Specifically, the push protocol may default to HTTP protocol and use XML message format.
The following table shows specific examples of the requester parameters:
| field name | Field type | Whether or not to transmit | Meaning of |
| TranCode | String(20) | Is that | Transaction code |
| ServiceCode | String(11) | Is that | Service code |
| ServiceScene | String(2) | Is that | Service scenario (service scenario corresponding to configuration field) |
| CnlInd | String(2) | Is that | Channel label (received channel label) |
| ConsumerId | String(8) | Is that | Consumption system number (fixed; follow-up provision) |
| OrgConsumerId | String(8) | Is that | Initiator system number (fixed) |
| TranDate | String(10) | Is that | Transaction date YYYYY-MM-DD |
| TranTime | String(12) | Is that | Transaction time HH: MM: SS |
| MblNo | String(20) | Is that | Mobile phone number (11 bit) |
| ShrtInfUpCd | String(512) | Is that | Short message uplink code (keyword corresponding to configuration field) |
| BsnTpNm | String(120) | Is that | Service type name (service system name) |
Further, the implementation of the application can also comprise:
receiving response body parameters returned by the service system;
and judging whether the request body parameters corresponding to the target push service are forwarded to the service system or not according to the response body parameters.
The following table shows specific examples of response body parameters:
the embodiment of the application also provides an uplink message automatic forwarding system, which comprises a user terminal, a message processing platform and a service system;
the user terminal is used for sending uplink messages to the message processing platform;
the message processing platform is used for executing the automatic forwarding method of the uplink message;
the service system is used for receiving and processing the uplink message sent by the message processing platform.
The application of the present application will be described in the following with specific examples.
Referring to fig. 5, an embodiment of the present application provides a data communication schematic diagram of a message processing platform and a related service system.
Specifically, the message processing platform maintains an uplink keyword configuration management function on the web service, receives the uplink message through an uplink receiving module in the message processing service, identifies keywords in the uplink message, matches the corresponding service system, and pushes the uplink keywords to the designated service system through the ESB through the interface service.
Referring to fig. 6, a flow diagram of processing an uplink message is provided in an embodiment of the present application.
Specifically, the following may be included:
1. and forwarding the uplink message of the user terminal to a message processing platform by the service provider, and receiving the uplink message of the user terminal by the message processing platform.
2. The message processing platform identifies the communication type of the uplink message and judges the message type (short message and WeChat) of the uplink message.
3. The content of the uplink message is identified, and whether a push service keyword exists or not is judged.
4. If the push service key word does not exist, the push service key word is used as a common uplink message and is subjected to warehousing processing.
5. If the push service keywords exist, pushing the push service keywords to a designated path of a corresponding service system through a push interface according to service system information corresponding to the keywords. And the service system returns whether the response body parameter corresponding to the uplink message is received or not, and the process is ended.
The embodiment of the application can realize the automatic forwarding of the uplink message and solve the following technical problems: the message processing platform broadcasts keywords to the corresponding service systems by issuing a set of uplink message processing service to the ESB according to the used service systems, so that the development work of interfaces of the service systems can be reduced, redundant interface service processing on the ESB is reduced, and the processing efficiency of the uplink message is improved.
The embodiment of the application has the following beneficial effects:
1. and the user uplink information is automatically forwarded to the corresponding service system through the interface service, so that the conditions that the service systems develop interfaces respectively and release a plurality of interfaces on the ESB are reduced, the redundant transaction of the ESB is reduced, and the service efficiency is improved.
2. By defining the template format for forwarding the uplink message on the message processing platform, the user-defined adaptation can be performed according to different parameters required by different service systems, so that the subsequent processes of deploying the interface and re-developing the interface are avoided.
Referring to fig. 7, an embodiment of the present application provides an automatic forwarding device for uplink messages, including:
a first unit, configured to obtain an uplink message;
a second unit, configured to identify a type and a content of the uplink message;
a third unit, configured to obtain, if the identification result indicates that the uplink message belongs to a push service keyword, a target push service that matches the push service keyword from a plurality of preset push services;
and a fourth unit, configured to forward, through a push interface, a request body parameter corresponding to the target push service to a service system, so that the service system processes the uplink message.
The specific implementation of the automatic forwarding device for uplink messages is basically the same as the specific embodiment of the automatic forwarding method for uplink messages, and will not be described herein.
The embodiment of the application also provides electronic equipment, which comprises a memory and a processor, wherein the memory stores a computer program, and the processor realizes the automatic forwarding method of the uplink message when executing the computer program. The electronic equipment can be any intelligent terminal including a tablet personal computer, a vehicle-mounted computer and the like.
Specifically, the electronic device may be a user terminal or a server.
The embodiment of the application also provides a computer readable storage medium, which stores a computer program, and the computer program realizes the automatic forwarding method of the uplink message when being executed by a processor.
The memory, as a non-transitory computer readable storage medium, may be used to store non-transitory software programs as well as non-transitory computer executable programs. In addition, the memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory optionally includes memory remotely located relative to the processor, the remote memory being connectable to the processor through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
Embodiments of the present application also disclose a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The computer instructions may be read from a computer-readable storage medium by a processor of an electronic device, and executed by the processor, to cause the electronic device to perform the method shown in fig. 2.
In some alternative embodiments, the functions/acts noted in the block diagrams may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Furthermore, the embodiments presented and described in the flowcharts of the present application are provided by way of example in order to provide a more thorough understanding of the technology. The disclosed methods are not limited to the operations and logic flows presented herein. Alternative embodiments are contemplated in which the order of various operations is changed, and in which sub-operations described as part of a larger operation are performed independently.
Furthermore, while the application is described in the context of functional modules, it should be appreciated that, unless otherwise indicated, one or more of the described functions and/or features may be integrated in a single physical device and/or software module or one or more functions and/or features may be implemented in separate physical devices or software modules. It will also be appreciated that a detailed discussion of the actual implementation of each module is not necessary to an understanding of the present application. Rather, the actual implementation of the various functional modules in the apparatus disclosed herein will be apparent to those skilled in the art from consideration of their attributes, functions and internal relationships. Accordingly, one of ordinary skill in the art can implement the application as set forth in the claims without undue experimentation. It is also to be understood that the specific concepts disclosed are merely illustrative and are not intended to be limiting upon the scope of the application, which is to be defined in the appended claims and their full scope of equivalents.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution in the form of a software product stored in a storage medium, comprising several instructions for causing an electronic device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Logic and/or steps represented in the flowcharts or otherwise described herein, e.g., a ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). In addition, the computer readable medium may even be paper or other suitable medium on which the program is printed, as the program may be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.
It is to be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
While embodiments of the present application have been shown and described, it will be understood by those of ordinary skill in the art that: many changes, modifications, substitutions and variations may be made to the embodiments without departing from the spirit and principles of the application, the scope of which is defined by the claims and their equivalents.
While the preferred embodiment of the present application has been described in detail, the present application is not limited to the embodiments described above, and those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of the present application, and these equivalent modifications or substitutions are included in the scope of the present application as defined in the appended claims.
Claims (10)
1. An automatic forwarding method for uplink messages is characterized by comprising the following steps:
acquiring an uplink message;
identifying the type and content of the uplink message;
if the identification result is that the uplink message belongs to a push service keyword, acquiring a target push service matched with the push service keyword from a plurality of preset push services;
and forwarding the request body parameters corresponding to the target push service to a service system through a push interface so that the service system can process the uplink message.
2. The method for automatically forwarding an uplink message according to claim 1, wherein the step of obtaining the uplink message comprises:
acquiring an uplink message sent by a user terminal;
or inquiring the data in the uplink record table according to a set period through the push interface; and matching the uplink record list with the key words configured according to the automatic reporting, and obtaining the uplink message by matching.
3. The method for automatically forwarding the uplink message according to claim 1, wherein forwarding the request body parameter corresponding to the target push service to the service system through the push interface, so that the service system processes the uplink message, includes:
and pushing the request body parameters corresponding to the target push service to a designated path of the service system through a push interface so as to enable the service system to process the uplink message.
4. The method for automatically forwarding an uplink message according to claim 1, wherein the method further comprises:
and if the identification result is that the uplink message does not belong to the push service keyword, storing the uplink message into a database.
5. The method for automatically forwarding an uplink message according to claim 1, wherein the method further comprises:
receiving response body parameters returned by the service system;
and judging whether the request body parameters corresponding to the target push service are forwarded to the service system or not according to the response body parameters.
6. An automatic forwarding method of uplink messages according to any one of claims 1 to 5, further comprising the step of presetting a plurality of push services, said step of presetting a plurality of push services comprising the steps of:
acquiring a plurality of keywords, a service scene name corresponding to each keyword, a request body parameter and a called service system ID;
setting each keyword and the corresponding service scene name, the request body parameter and the called service system ID as a push service to obtain the push service corresponding to each keyword.
7. An automatic forwarding system for uplink messages is characterized by comprising a user terminal, a message processing platform and a service system;
the user terminal is used for sending uplink messages to the message processing platform;
the message processing platform is configured to perform an automatic forwarding method for uplink messages according to any one of claims 1 to 6;
the service system is used for receiving and processing the uplink message sent by the message processing platform.
8. An automatic forwarding device for uplink messages, comprising:
a first unit, configured to obtain an uplink message;
a second unit, configured to identify a type and a content of the uplink message;
a third unit, configured to obtain, if the identification result indicates that the uplink message belongs to a push service keyword, a target push service that matches the push service keyword from a plurality of preset push services;
and a fourth unit, configured to forward, through a push interface, a request body parameter corresponding to the target push service to a service system, so that the service system processes the uplink message.
9. An electronic device comprising a processor and a memory;
the memory is used for storing programs;
execution of the program by the processor implements an automatic forwarding method for uplink messages according to any one of claims 1 to 6.
10. A computer-readable storage medium storing a program that is executed by a processor to implement an uplink message automatic forwarding method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311123123.XA CN117176793A (en) | 2023-08-31 | 2023-08-31 | Automatic forwarding method, system, device, equipment and medium for uplink message |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311123123.XA CN117176793A (en) | 2023-08-31 | 2023-08-31 | Automatic forwarding method, system, device, equipment and medium for uplink message |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117176793A true CN117176793A (en) | 2023-12-05 |
Family
ID=88940558
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311123123.XA Pending CN117176793A (en) | 2023-08-31 | 2023-08-31 | Automatic forwarding method, system, device, equipment and medium for uplink message |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117176793A (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011041969A1 (en) * | 2009-10-10 | 2011-04-14 | 中兴通讯股份有限公司 | Method and system for realizing the capability of supporting initiative push of data message |
| US20170041257A1 (en) * | 2014-04-16 | 2017-02-09 | Huawei Technologies Co., Ltd. | Information Processing Method, Apparatus and System Based on Instant Messaging |
| CN108206742A (en) * | 2016-12-19 | 2018-06-26 | 腾讯科技（深圳）有限公司 | A kind of message method, device, server and system |
| CN108989264A (en) * | 2017-05-31 | 2018-12-11 | 华为技术有限公司 | A kind of live broadcasting method, system and relevant device |
| CN113011969A (en) * | 2021-03-31 | 2021-06-22 | 建信金融科技有限责任公司 | Banking business processing method, device, medium and electronic equipment based on 5G message |
| WO2021180104A1 (en) * | 2020-03-12 | 2021-09-16 | 阿里巴巴集团控股有限公司 | Message pushing method and system, and client, storage medium and processor |
| WO2021237433A1 (en) * | 2020-05-26 | 2021-12-02 | 深圳市欢太科技有限公司 | Message pushing method and apparatus, and electronic device and computer-readable medium |
| WO2022088804A1 (en) * | 2020-10-30 | 2022-05-05 | 深圳壹账通智能科技有限公司 | Message pushing method and apparatus, and electronic device, and storage medium |
-
2023
- 2023-08-31 CN CN202311123123.XA patent/CN117176793A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011041969A1 (en) * | 2009-10-10 | 2011-04-14 | 中兴通讯股份有限公司 | Method and system for realizing the capability of supporting initiative push of data message |
| US20170041257A1 (en) * | 2014-04-16 | 2017-02-09 | Huawei Technologies Co., Ltd. | Information Processing Method, Apparatus and System Based on Instant Messaging |
| CN108206742A (en) * | 2016-12-19 | 2018-06-26 | 腾讯科技（深圳）有限公司 | A kind of message method, device, server and system |
| CN108989264A (en) * | 2017-05-31 | 2018-12-11 | 华为技术有限公司 | A kind of live broadcasting method, system and relevant device |
| WO2021180104A1 (en) * | 2020-03-12 | 2021-09-16 | 阿里巴巴集团控股有限公司 | Message pushing method and system, and client, storage medium and processor |
| WO2021237433A1 (en) * | 2020-05-26 | 2021-12-02 | 深圳市欢太科技有限公司 | Message pushing method and apparatus, and electronic device and computer-readable medium |
| WO2022088804A1 (en) * | 2020-10-30 | 2022-05-05 | 深圳壹账通智能科技有限公司 | Message pushing method and apparatus, and electronic device, and storage medium |
| CN113011969A (en) * | 2021-03-31 | 2021-06-22 | 建信金融科技有限责任公司 | Banking business processing method, device, medium and electronic equipment based on 5G message |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110704521A (en) | Interface data access method and system | |
| CN104253741A (en) | Information sending method and device and system thereof | |
| JP2005117637A (en) | Method and system for web-based event notification | |
| CN108550057B (en) | Agent answering request processing method, electronic device and computer readable storage medium | |
| CN112396432B (en) | Interview task generation system, interview task generation method, interview task generation equipment and interview task generation medium | |
| CN104869048A (en) | Grouping processing method, device and system of MicroBlog data | |
| CN112380229A (en) | Service data synchronization method and device, nonvolatile storage medium and processor | |
| KR101098800B1 (en) | Automatic handling of incoming commuincations at a wireless device | |
| CN114025027A (en) | Data transmission script running method and device, storage medium and electronic device | |
| CN117176793A (en) | Automatic forwarding method, system, device, equipment and medium for uplink message | |
| CN112182378A (en) | Message pushing method, device, terminal and medium | |
| CN115514759B (en) | File forwarding method, electronic device and storage medium | |
| CN101753428A (en) | Method, device and processing system for capturing and reporting the information of instance labels | |
| CN112749190B (en) | Data query method and device, computing equipment and computer storage medium | |
| CN101083678A (en) | Menu dynamic selection system and method | |
| CN109348053B (en) | Telephone number mark processing method, server, terminal device and computer readable storage medium | |
| CN114092211A (en) | Processing method of accounting data, electronic device and readable storage medium | |
| CN110493735B (en) | Short message processing method and device | |
| CN107222559B (en) | Information calling method | |
| CN109246686B (en) | Multi-card user address book updating method and device based on cloud technology | |
| CN111061543A (en) | Multi-tenant workflow engine service method, device and server | |
| CN114745421B (en) | Method, device, server and storage medium for recording fission path data | |
| CN109451185A (en) | Incoming call recognition methods, device and storage medium based on enterprise directory | |
| CN110418020B (en) | List state information processing method and device, electronic terminal and storage medium | |
| CN112019452B (en) | Method, system and related device for processing service requirement |
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 |