CN111934986A - Asynchronous message terminal pushing solution method and system - Google Patents
Asynchronous message terminal pushing solution method and system Download PDFInfo
- Publication number
- CN111934986A CN111934986A CN202010758198.5A CN202010758198A CN111934986A CN 111934986 A CN111934986 A CN 111934986A CN 202010758198 A CN202010758198 A CN 202010758198A CN 111934986 A CN111934986 A CN 111934986A
- Authority
- CN
- China
- Prior art keywords
- message
- pushing
- channel
- merchant
- information
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/214—Monitoring or handling of messages using selective forwarding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
- H04L51/18—Commands or executable codes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention discloses a method and a system for solving asynchronous message terminal pushing, and the scheme of the invention is to build a message pushing platform to custom-send messages, integrate channels needing message pushing, and push corresponding channels to corresponding messages through message switch information configuration, thereby relieving the pressure of the message pushing channels, reducing the development cost of pushing messages from a server to a terminal, facilitating system upgrading and maintenance, and facilitating service decoupling and performance improvement.
Description
Technical Field
The invention relates to the field of message pushing systems, in particular to a solution method and a system for asynchronous message terminal pushing.
Background
Due to the development of the internet industry, it is indispensable that a service party push necessary messages to a user terminal to inform the user.
The existing technical solution is not a diversified platform push solution (such as apnsk, meter push, etc.), and the existing technical solution requires a developer of each message push use scenario to develop again a corresponding development scenario that is not used. Because a business scene needs to feed back transaction information to terminal equipment of a user in time, the existing mainstream message pushing only completes the function of pushing an individual message, the function is original, other pushing modes are not compatible, a business development team is not willing to connect a plurality of terminal pushing modes, the performance cannot be improved, and the experience of an individual user is poor, so that an asynchronous message terminal pushing solution method and an asynchronous message terminal pushing solution system are needed in the market.
Disclosure of Invention
In order to overcome the defects of the prior art, the invention provides a solution method and a system for pushing an asynchronous message terminal.
The technical scheme adopted by the invention for solving the technical problems is as follows:
an asynchronous message terminal push solution, comprising:
s1, configuring a service message channel switch by the merchant:
s1.1, arranging configuration information: configuring a service channel switch for pushing the message to the merchant;
s1.2, the platform acquires a configuration information request: the platform obtains configuration data of a merchant and verifies and collates the information;
s1.3, configuration information is stored in a warehouse: firstly, inquiring whether the merchant data exists, if so, modifying the current merchant configuration, and if not, storing the data in a warehouse, and completing the updating and maintenance of the merchant on the configuration data;
s1.4, synchronously returning a storage operation result: synchronously returning the calling result of the merchant;
s2, pushing service messages:
s2.1, initiating message pushing: the service side initiates an asynchronous message pushing, sends the service information to RMQ server, and pushes the message to the message server;
s2.2, message monitoring: monitoring RMQ server message, analyzing the message after receiving the message, and implementing distributed monitoring message;
s2.3, message processing: inquiring switch configuration information of a database according to the obtained merchant number;
s2.4, judging message pushing: inquiring the result according to the configuration information to obtain a record of the inquiry result;
s2.5, message pushing: and according to the configuration information query result, matching the corresponding message channel and executing corresponding push calling.
Further, the configuration information includes a merchant number, a parent merchant number, a service type, a push channel, and a push switch.
Further, said step S1.2 comprises: the platform obtains the configuration data of the merchant through the calling of the interface, and verifies and sorts the information through the processing of the background logic.
Further, said step S1.4 comprises: calling result true is execution success, and false is execution failure.
Further, said step S2.1 comprises: the message content is a json string.
Further, said step S2.1 comprises: the message is pushed RMQ through the producer's client API to the message server.
Further, said step S2.2 comprises: the message platform monitors RMQ the server messages, parses the messages after receiving them, and implements the distributed listening messages using RMQ consuming client API.
Further, said step S2.3 comprises: querying the switch configuration information entails querying the record that the channel of the push message is open.
Further, said step S2.4 comprises: if the record of the query result is not available, the fact that the channel which meets the pushing condition does not exist is indicated; if there is a record, the record of the query result is a plurality of records, and the downstream message push call is carried out on the channel corresponding to the queried configuration information.
The invention also discloses a system for solving the problem of pushing the asynchronous message terminal, which comprises the following steps:
the service message sender is used for asynchronously pushing the service information to the RMQ server according to the message pushing convention of RMQ when the message needs to be pushed;
RMQ server, which is a message middleware server for saving and consuming messages;
the message pushing application platform is used for providing an external interface to configure the switch information of the merchant and storing the information in a warehouse; RMQ message monitoring subscription, timely receiving service message processing, matching with downstream channel configuration information, and sending to downstream channel;
and the downstream docking information channel is used for completing the pushing of the information channel by the pushing platform through docking a downstream channel interface, and the pushed information can be received by a corresponding channel terminal opened by the merchant.
Further, the content of the message stored in the RMQ server is a json character string.
Further, if the downstream docking message channel has no record of the query result, it indicates that there is no channel meeting the push condition; if the record exists, the message pushing call of the downstream is carried out on the channel corresponding to the inquired configuration information.
The invention has the beneficial effects that: the scheme of the invention is that a message pushing platform is built to custom-send the message, channels needing message pushing are integrated, corresponding channel pushing processing is carried out on the corresponding message through message pushing switch information configuration, the message pushing channel pressure is relieved, the development cost of pushing the message from a server to a terminal is reduced, system upgrading and maintenance are facilitated, the coupling degree of each service is decoupled, and the performance is improved.
Drawings
The invention is further illustrated with reference to the following figures and examples.
Fig. 1 is a flow chart of a merchant configuration service message channel switch of an asynchronous message terminal push solution of the present invention;
fig. 2 is a flow chart of a service message pushing of an asynchronous message terminal pushing solution of the present invention;
fig. 3 is a schematic structural diagram of a message platform system of an asynchronous message terminal push solution system according to the present invention.
Detailed Description
The conception, the specific structure, and the technical effects produced by the present invention will be clearly and completely described below in conjunction with the embodiments and the accompanying drawings to fully understand the objects, the features, and the effects of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all embodiments, and those skilled in the art can obtain other embodiments without inventive effort based on the embodiments of the present invention, and all embodiments are within the protection scope of the present invention. In addition, all the connection/connection relations referred to in the patent do not mean that the components are directly connected, but mean that a better connection structure can be formed by adding or reducing connection auxiliary components according to specific implementation conditions. All technical characteristics in the invention can be interactively combined on the premise of not conflicting with each other.
The invention discloses a solution for pushing an asynchronous message terminal, which comprises the following steps:
as shown in fig. 1, fig. 1 is a flow chart of a merchant configuring service message channel switch, where the flow chart includes:
s1, configuring a service message channel switch by the merchant:
s1.1, arranging configuration information: configuring a business channel switch for pushing a message to a merchant, wherein the configuration is used for controlling important information content of which message channel the business is finally pushed to, and the configuration information comprises a merchant number, a father merchant number, a business type, a pushing channel and a pushing switch; in the embodiment, a merchant actively initiates interface calling on a message platform, the interface is provided by the message platform and sends merchant configuration information calling;
s1.2, the platform acquires a configuration information request: the platform obtains configuration data of the merchant through the calling of the interface, and verifies and sorts the information through the processing of background logic;
s1.3, configuration information is stored in a warehouse: putting the arranged configuration information data into a warehouse, firstly inquiring whether the merchant data exists, if so, modifying the current merchant configuration, and if not, finishing the updating and maintenance of the merchant on the configuration data; for example: a user with a merchant number of 12345 configures a message switch with a business type of transaction and a channel for voice broadcast as on; the first configuration is stored in the database, if the data is already available, the merchant modifies and stores the information according to the transmitted data when configuring the information; if the updated data and the record stored in the database are the same, the data updating operation is not carried out;
s1.4, synchronously returning a storage operation result: synchronously returning the calling result of the merchant, wherein the calling result true is successful execution, and the false is failed execution;
as shown in fig. 2, fig. 2 is a flow chart of pushing a service message, where the flow includes:
s2, pushing service messages:
s2.1, initiating message pushing: a service party initiates an asynchronous message pushing, service information is sent to RMQ server 2, the message is pushed to a message server through a client API of RMQ producer, and the message content is a json character string;
s2.2, message monitoring: monitoring RMQ the server 2 message by the message platform, analyzing the message after receiving the message, and implementing distributed monitoring message by using RMQ consumption client API;
s2.3, message processing: inquiring the switch configuration information of the database according to the obtained business number, wherein the channel for inquiring the switch configuration information and pushing the message is the record for opening;
s2.4, judging message pushing: inquiring the result according to the configuration information to obtain the record of the inquiry result, and if the record of the inquiry result does not exist, indicating that no channel which meets the pushing condition exists; if the records exist, the records of the query result are a plurality of records, and the downstream message pushing and calling are carried out on the channel corresponding to the queried configuration information; for example: the merchant 123456 is provided with two push channels, namely voice broadcast and WeChat public number, so that the query result is two records;
s2.5, message pushing: according to the configuration information query result, matching the corresponding message channel and executing corresponding push calling; for example: the configuration information of the merchant 123456 queries two channel records, namely voice broadcast and wechat public number, and then the two different message channels of the service message are matched, and a related downstream interface is called to push the service message to the merchant 123456.
As shown in fig. 3, fig. 3 is a schematic structural diagram of a message platform system:
definitions of abbreviations and key terms in fig. 3:
RMQ: a curie third party middleware technology, rocktrmq;
apns: apple push notification service;
voice broadcasting: the message platform uses MPush to push the message to the message terminal in a voice form;
WeChat public number: the message platform pushes the message to a user micro signal of a message terminal in a text form;
cloud loudspeaker: the message platform pushes the message to the message terminal in the form of voice;
pushing of the allies: and the third party message pushing service provider.
As shown in fig. 3, fig. 3 discloses an asynchronous message terminal push solution system, which includes:
the service message sender 1 is used for asynchronously pushing the service information to the RMQ server 2 according to the message pushing convention of RMQ when the message needs to be pushed, and the service party executes the service of the service party without being influenced by any other service, without any dependence and with high decoupling; in this embodiment, for the whole message pushing process, the module is the source, and only if the pushing message is generated here, the following series of processes can be triggered;
RMQ, server 2 is a message middleware server for storing and consuming messages, the message content stored in RMQ server 2 is json character string; the message producer pushes the message to the server, the message consumer subscribes to the monitoring message, once a new message is obtained, the service message is pushed to the monitoring party, and the server removes the message after the monitoring party consumes the message;
the message pushing application platform 3 is used for providing an external interface to configure the switch information of the commercial tenant and storing the information in a warehouse; RMQ message monitoring subscription, timely receiving service message processing, matching with downstream channel configuration information, and sending to downstream channel;
the downstream docking information channel 4 is used for completing the information channel pushing by the pushing platform through docking a downstream channel interface, the pushed information can be received by a corresponding channel terminal opened by a merchant, and if the downstream docking information channel 4 does not have a record of a query result, the fact that no channel which meets the pushing condition exists is indicated; if the record exists, the message pushing call of the downstream is carried out on the channel corresponding to the inquired configuration information.
The solution method and the system for pushing the asynchronous message terminal are adopted:
A. according to the configured database information, the method is used for maintaining the customization of merchants in selecting different push services and push channels, thereby realizing different message push requirements according to the personalized requirements of users.
B. The platform may maintain and extend the business type and downstream push channels of the push messages.
The technical key of the application is that the platform back end uses RMQ middleware as message processing. Each service processing pushes the message to be processed to the server by using RMQ according to the service convention, and the message monitoring application monitors the message pushed to the server and pushes the message to a downstream service channel according to the message platform configuration information. The configuration information of the message pushing platform needs to be configured in advance according to requirements, the configuration information is divided into a service type and a downstream channel type, once the message is obtained, the platform pushes the message to the downstream channel for completing the pushing and the releasing of the message information according to the attribute configured by the message.
The existing mainstream message push only completes the function of pushing the single message, and the function is atomic and is not compatible with other push modes.
The method and the system solve the problems that a message pushing platform is built to custom-send the message, channels needing message pushing are integrated, corresponding channel pushing processing is carried out on the corresponding message through message switch information configuration, the pressure of the message pushing channel is relieved, the development cost of pushing the message from a server to a terminal is reduced, system upgrading and maintenance are facilitated, and decoupling and performance improvement of services are facilitated.
The invention has the beneficial effects that: the scheme of the invention is that a message pushing platform is built to custom-send the message, channels needing message pushing are integrated, corresponding channel pushing processing is carried out on the corresponding message through message pushing switch information configuration, the message pushing channel pressure is relieved, the development cost of pushing the message from a server to a terminal is reduced, system upgrading and maintenance are facilitated, the coupling degree of each service is decoupled, and the performance is improved.
While the preferred embodiments of the present invention have been illustrated and described, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (12)
1. An asynchronous message terminal push solution, comprising:
s1, configuring a service message channel switch by the merchant:
s1.1, arranging configuration information: configuring a service channel switch for pushing the message to the merchant;
s1.2, the platform acquires a configuration information request: the platform obtains configuration data of a merchant and verifies and collates the information;
s1.3, configuration information is stored in a warehouse: firstly, inquiring whether the merchant data exists, if so, modifying the current merchant configuration, and if not, storing the data in a warehouse, and completing the updating and maintenance of the merchant on the configuration data;
s1.4, synchronously returning a storage operation result: synchronously returning the calling result of the merchant;
s2, pushing service messages:
s2.1, initiating message pushing: the service side initiates an asynchronous message pushing, sends the service information to RMQ server, and pushes the message to the message server;
s2.2, message monitoring: monitoring RMQ server message, analyzing the message after receiving the message, and implementing distributed monitoring message;
s2.3, message processing: inquiring switch configuration information of a database according to the obtained merchant number;
s2.4, judging message pushing: inquiring the result according to the configuration information to obtain a record of the inquiry result;
s2.5, message pushing: and according to the configuration information query result, matching the corresponding message channel and executing corresponding push calling.
2. The asynchronous message terminal push solution as claimed in claim 1, wherein in step S1.1: the configuration information comprises a merchant number, a father merchant number, a service type, a pushing channel and a pushing switch.
3. The asynchronous message terminal push solution as claimed in claim 1, wherein said step S1.2 comprises: the platform obtains the configuration data of the merchant through the calling of the interface, and verifies and sorts the information through the processing of the background logic.
4. The asynchronous message terminal push solution as claimed in claim 1, wherein said step S1.4 comprises: calling result true is execution success, and false is execution failure.
5. The asynchronous message terminal push solution as claimed in claim 1, wherein said step S2.1 comprises: the message content is a json string.
6. The asynchronous message terminal push solution as claimed in claim 1, wherein said step S2.1 comprises: the message is pushed RMQ through the producer's client API to the message server.
7. The asynchronous message terminal push solution as claimed in claim 1, wherein said step S2.2 comprises: the message platform monitors RMQ the server messages, parses the messages after receiving them, and implements the distributed listening messages using RMQ consuming client API.
8. The asynchronous message terminal push solution as claimed in claim 1, wherein said step S2.3 comprises: querying the switch configuration information entails querying the record that the channel of the push message is open.
9. The asynchronous message terminal push solution as claimed in claim 1, wherein said step S2.4 comprises: if the record of the query result is not available, the fact that the channel which meets the pushing condition does not exist is indicated; if there is a record, the record of the query result is a plurality of records, and the downstream message push call is carried out on the channel corresponding to the queried configuration information.
10. An asynchronous message terminal push resolution system, comprising:
the service message sender is used for asynchronously pushing the service information to the RMQ server according to the message pushing convention of RMQ when the message needs to be pushed;
RMQ server, which is a message middleware server for saving and consuming messages;
the message pushing application platform is used for providing an external interface to configure the switch information of the merchant and storing the information in a warehouse; RMQ message monitoring subscription, timely receiving service message processing, matching with downstream channel configuration information, and sending to downstream channel;
and the downstream docking information channel is used for completing the pushing of the information channel by the pushing platform through docking a downstream channel interface, and the pushed information can be received by a corresponding channel terminal opened by the merchant.
11. The asynchronous message terminal push resolution system of claim 10, wherein: the content of the message stored in the RMQ server is a json character string.
12. The asynchronous message terminal push resolution system of claim 10, wherein: if the downstream docking message channel has no record of the query result, the downstream docking message channel indicates that no channel which meets the pushing condition exists; if the record exists, the message pushing call of the downstream is carried out on the channel corresponding to the inquired configuration information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010758198.5A CN111934986A (en) | 2020-07-31 | 2020-07-31 | Asynchronous message terminal pushing solution method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010758198.5A CN111934986A (en) | 2020-07-31 | 2020-07-31 | Asynchronous message terminal pushing solution method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111934986A true CN111934986A (en) | 2020-11-13 |
Family
ID=73315019
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010758198.5A Pending CN111934986A (en) | 2020-07-31 | 2020-07-31 | Asynchronous message terminal pushing solution method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111934986A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112800332A (en) * | 2021-02-04 | 2021-05-14 | 北京易车互联信息技术有限公司 | Platform suitable for pushing text and picture messages to mobile phone terminal equipment |
| CN114584525A (en) * | 2022-01-28 | 2022-06-03 | 深圳市梦网科技发展有限公司 | Message processing method, system, terminal device and storage medium |
| CN116866427A (en) * | 2023-09-04 | 2023-10-10 | 杭州比智科技有限公司 | Unified pushing method and system for heterogeneous messages |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120143969A1 (en) * | 2010-10-21 | 2012-06-07 | Subrao Venugopal Shenoy | Methods and systems for creating online unified contact and communication management (CM) platform |
| CN103020056A (en) * | 2011-09-20 | 2013-04-03 | 佳都新太科技股份有限公司 | Subscription pushing engine for cross-open-platform social intercourse information optimizing computation |
| CN110955857A (en) * | 2019-10-18 | 2020-04-03 | 苏宁云计算有限公司 | Service processing method and device for high concurrency environment |
| CN110971508A (en) * | 2019-11-27 | 2020-04-07 | 中国银行股份有限公司 | Message pushing method, device and system |
-
2020
- 2020-07-31 CN CN202010758198.5A patent/CN111934986A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120143969A1 (en) * | 2010-10-21 | 2012-06-07 | Subrao Venugopal Shenoy | Methods and systems for creating online unified contact and communication management (CM) platform |
| CN103020056A (en) * | 2011-09-20 | 2013-04-03 | 佳都新太科技股份有限公司 | Subscription pushing engine for cross-open-platform social intercourse information optimizing computation |
| CN110955857A (en) * | 2019-10-18 | 2020-04-03 | 苏宁云计算有限公司 | Service processing method and device for high concurrency environment |
| CN110971508A (en) * | 2019-11-27 | 2020-04-07 | 中国银行股份有限公司 | Message pushing method, device and system |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112800332A (en) * | 2021-02-04 | 2021-05-14 | 北京易车互联信息技术有限公司 | Platform suitable for pushing text and picture messages to mobile phone terminal equipment |
| CN114584525A (en) * | 2022-01-28 | 2022-06-03 | 深圳市梦网科技发展有限公司 | Message processing method, system, terminal device and storage medium |
| CN114584525B (en) * | 2022-01-28 | 2023-12-05 | 深圳市梦网科技发展有限公司 | Message processing method, system, terminal equipment and storage medium |
| CN116866427A (en) * | 2023-09-04 | 2023-10-10 | 杭州比智科技有限公司 | Unified pushing method and system for heterogeneous messages |
| CN116866427B (en) * | 2023-09-04 | 2023-12-12 | 杭州比智科技有限公司 | Unified pushing method and system for heterogeneous messages |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111934986A (en) | Asynchronous message terminal pushing solution method and system | |
| CN1788474B (en) | Method, device and system for processing message addressed to client terminal | |
| US20110113062A1 (en) | System and method for searching disparate datastores via a remote device | |
| US20070118648A1 (en) | Service broker integration layer for supporting telecommunication client service requests | |
| EP1780983B1 (en) | Service broker integration layer for supporting telecommunication client service requests | |
| CN105592158A (en) | System And Method For Using Presence Information | |
| CN114338793B (en) | Message pushing method and device, electronic equipment and readable storage medium | |
| US20110145270A1 (en) | Service personas for address books | |
| CN112015578B (en) | Wind control system and method based on pre-synchronous processing and post-asynchronous processing | |
| CN109688047B (en) | Message adaptation method, device and storage medium based on XML | |
| WO2015000307A1 (en) | Media information display method and device, client, and graphical control display method and device | |
| CN112445868A (en) | Service message processing method and device | |
| CN108418894A (en) | A kind of Distributed Data Synchronization method based on push technologies | |
| CN113992460B (en) | Message sending method, device, electronic equipment and storage medium | |
| EP2641363B1 (en) | Message targeting platform | |
| CN113992352A (en) | Message pushing method and device, electronic equipment and storage medium | |
| CN102065099A (en) | Signaling and bearing separated communication system | |
| CN113783913A (en) | Message pushing management method and device | |
| CN115412597B (en) | Real-time data communication method | |
| CN102611635A (en) | Microblog-based message interaction method and system | |
| CN114301783B (en) | Optimization method and device for micro-service, storage medium and electronic device | |
| CN112866268B (en) | Message processing method and system | |
| CN115629909A (en) | Service data processing method and device, electronic equipment and storage medium | |
| US20210058361A1 (en) | System and method for collecting and storing electronic messages of different types based on subject matter | |
| CN109036427B (en) | Method and system for dynamically configuring voice recognition service |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201113 |
|
| RJ01 | Rejection of invention patent application after publication |