CN112165535A - Message push processing method and system - Google Patents
Message push processing method and system Download PDFInfo
- Publication number
- CN112165535A CN112165535A CN202011255700.7A CN202011255700A CN112165535A CN 112165535 A CN112165535 A CN 112165535A CN 202011255700 A CN202011255700 A CN 202011255700A CN 112165535 A CN112165535 A CN 112165535A
- Authority
- CN
- China
- Prior art keywords
- user
- temporary
- temporary user
- message
- user account
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- 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/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
-
- 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/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
-
- 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/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate
Abstract
The invention discloses a message pushing processing method and a message pushing processing system, which are used for effectively ensuring the normal pushing of a web temporary user. The method comprises the following steps: when the web page is opened, the client side and the server side establish long connection; the web application program calls an interface of the client to set a temporary user identifier corresponding to the web page; the message pushing system checks whether a user account corresponding to the temporary user identification exists in the database, and if so, the user account is returned to the client; if not, acquiring an account from the temporary user queue as a user account and returning the user account to the client, storing the temporary user identification binding relationship into a database, and feeding the user account back to a web application program background by the web application program; a web application program background initiates a message pushing request targeting a user account; the message pushing system forwards the message pushing request to a temporary user processing center; when the temporary user is an effective user, the temporary user processing center locally stores the offline push message, and when the temporary user is online, the push message is issued.
Description
Technical Field
The present invention relates to the field of message pushing technologies, and in particular, to a message pushing processing method and system.
Background
One characteristic of web pushing is that a web page client cannot solidify and store identification information of a web user, so that identification of the web pushing user depends on an identification code set by an application layer program. Each time the webweb page user opens a web page (establishes a new connection with the background), the webweb page user is considered as a new web pushing target, before the web user completes login at the application level and the web application binds a formal user identification code, the connection established with the background can only be bound with a temporary user identification code, and the user who cannot exactly find the connection of the web user at the application level is considered as a tourist (a temporary user). A temporary user is only active during the time period from the web page open to the web page closed, and becomes meaningless after the web page is closed.
However, the inventor recognizes that the tourists have great significance at the application level, for example, the application operator needs to communicate with the tourists to achieve the conversion of the customers at the business level, and therefore, the inventor considers that a special processing flow is designed for the temporary users to ensure the normal pushing of the temporary users.
Disclosure of Invention
The invention provides a message pushing processing method and a message pushing processing system, which are used for effectively ensuring normal message pushing of a web temporary user.
In a first aspect, a message push processing method is provided, including:
when a web page is opened, a client establishes an http connection with a web application background and converts the http connection into a long connection;
the web application program calls an interface of the client to set a temporary user identifier corresponding to the web page and feeds the temporary user identifier back to the message pushing system;
the message pushing system checks whether a user account uid corresponding to the temporary user identifier exists in a database, and if so, returns the user account uid to the client; if not, acquiring an account from a temporary user queue as the user account uid, storing the temporary user identifier and the user account uid into the database after the temporary user identifier and the user account uid are in a binding relationship, and returning the user account uid to the client;
the web application program acquires the user account uid through sdk and feeds the user account uid back to a web application program background;
the web application program background initiates a message pushing request with the user account uid as a target, wherein the message pushing request comprises the user account uid;
the message pushing system identifies the message pushing request to determine whether the user account uid is a temporary user;
when the user account uid is identified as the user account uid of the temporary user, forwarding the message pushing request to a temporary user processing center;
the temporary user processing center checks the user state of the temporary user through the user account, when the temporary user is a valid user, the temporary user processing center locally stores an offline push message, and when the temporary user is online, the temporary user processing center issues the push message to the client.
Further, after the sending the push message to the client, the method further includes:
and when receiving the message confirmation character corresponding to the push message, the temporary user processing center deletes the local corresponding offline push message.
Further, when the web page is opened, the method further comprises:
the temporary user processing center caches the user state of the temporary user;
and when the web page is closed or the long connection is disconnected, the temporary user processing center marks that the temporary user is offline.
Further, the method further comprises:
the temporary user center polls the user states of all temporary users regularly according to a polling plan;
and when the user state of the temporary user is in an off-line state and exceeds a first preset time, deleting the local data of the temporary user by the temporary user center.
Further, the method further comprises:
the message pushing system determines whether the binding relationship between the temporary user identification and the user account uid in the database exceeds a second preset duration;
and when the binding relationship between the temporary user identification and the user account uid exceeds the second preset duration, contacting the binding relationship between the temporary user identification and the user account uid, and returning the user account id to the temporary user queue.
Further, the converting the http connection into a long connection includes:
and converting the http connection into a websocket long connection.
In a second aspect, a message push processing system is provided, including: the system comprises a client, a web application program, a message pushing system, a web application program background and a temporary user processing center;
the client is used for establishing an http connection with a web application program background and converting the http connection into a long connection when the web page is opened;
the web application program is used for calling an interface of the client to set a temporary user identifier corresponding to the web page and feeding the temporary user identifier back to the message pushing system;
the message pushing system is used for checking whether a user account uid corresponding to the temporary user identifier exists in a database or not, and if so, returning the user account uid to the client; if not, acquiring an account from a temporary user queue as the user account uid, storing the temporary user identifier and the user account uid into the database after the temporary user identifier and the user account uid are in a binding relationship, and returning the user account uid to the client;
the web application program is further used for acquiring the user account uid through sdk and feeding the user account uid back to a web application program background;
the web application program background is used for initiating a message pushing request which takes the user account uid as a target, and the message pushing request comprises the user account uid;
the message pushing system is used for identifying the message pushing request to determine whether the user account uid is a temporary user, and forwarding the message pushing request to a temporary user processing center when the user account uid is identified as the user account uid of the temporary user;
the temporary user processing center is used for checking the user state of the temporary user through the user account, storing offline push messages locally when the temporary user is a valid user, and issuing the push messages to the client when the temporary user is online.
Further, the temporary user center is further configured to:
and after the push message is sent to the client, deleting the local corresponding offline push message when a message confirmation character corresponding to the push message is received.
Further, the temporary user processing center is further configured to:
caching the user state of the temporary user when the web page is opened;
when the web page is closed or the long connection is disconnected, marking the temporary user offline.
Further, the temporary user center is further configured to:
polling the user states of all temporary users regularly according to a polling plan; and when the user state of the temporary user is in an off-line state and exceeds a first preset time, deleting the local data of the temporary user.
In the message pushing processing method and the message pushing processing system, when the web page is opened, the client establishes http connection with the web application program background and converts the http connection into long connection, so that the connection state of the current web page can be kept, the web application program calls an interface of the client to set a temporary user identifier corresponding to the web page and feeds the temporary user identifier back to the message pushing system, the message pushing system checks whether a user account uid corresponding to the temporary user identifier exists in a database, and if so, the user account uid is returned to the client; if not, acquiring an account from the temporary user queue as a user account uid, storing the temporary user identifier and the user account uid into a database after the temporary user identifier and the user account uid are in a binding relationship, and returning the user account uid to the client, so that registration and maintenance of the temporary user are completed, and when a user who opens a current web page needs to be subjected to message pushing, the web application program acquires the user account uid through sdk and feeds the user account uid back to a web application program background; the web application program background initiates a message pushing request with a user account uid as a target, wherein the message pushing request comprises the user account uid; the message pushing system identifies the message pushing request to determine whether the user account uid is a temporary user; when the user account uid is identified as the user account uid of the temporary user, forwarding the message pushing request to a temporary user processing center; the method comprises the steps that a temporary user processing center checks the user state of a temporary user through a user account, when the temporary user is an effective user, the temporary user processing center locally stores offline push messages, and when the temporary user is online, the temporary user processing center sends the push messages to a client.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive labor.
Fig. 1 is a flow chart of a message push processing method according to an embodiment of the present invention;
fig. 2 is another schematic flow chart of a message pushing processing method according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a message push processing system in an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a computer device in the embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The invention provides a message pushing processing method, and for convenience of understanding, some terms related to the invention are introduced first.
The client, or called as the client, refers to a program corresponding to the server and providing local services to the client.
The Web application program is an application program which can be accessed through a Web client, and a user only needs to have a browser to access the Web application program and does not need to install other software.
web application background refers to the background that provides application services for web applications.
The Web page refers to a corresponding page when a Web page is opened through a Web client.
The message push system is a push system for providing a message push service for a web application program.
The temporary user processing center is a server for performing related control on the pushing of the temporary user.
As shown in fig. 1-2, the following describes a message pushing processing method according to an embodiment of the present invention, which mainly includes a login process and a registration process of a temporary user, a message pushing process of the temporary user, and a destruction process of the temporary user, and mainly includes the following steps:
s10: when the web page is opened, the client establishes an http connection with the server and converts the http connection to a long connection.
When a user accesses a web application program through a client, a corresponding web page is opened, wherein the web page refers to any one page opened when the user browses the web application program, and when the web page is opened, the client establishes an http connection with an application program background of the web application program and converts the http connection into a long connection. It should be noted that the web application may refer to any type of web application, such as a shopping web application, and the like, and is not limited specifically.
In one embodiment, the http connection is converted into the long connection, which means that the http connection is converted into the websocket long connection.
S20: and the web application program calls an interface of the client to set a temporary user identifier corresponding to the web page and feeds the temporary user identifier back to the message pushing system.
After the http connection is established between the client and the server and the http connection is converted into the long connection, the web application program calls an interface of the client to set a temporary user identifier corresponding to the web page and feeds the temporary user identifier back to the message pushing system. When the temporary user identifier corresponding to the web page is set, the prefix of the temporary user identifier may be set according to a preset rule to distinguish the setting mode of other user identifiers, the preset rule may be changed according to a requirement, and the present invention is not limited thereto.
S30: the message push system checks whether the database has a user account uid corresponding to the temporary user identifier.
S40: if so, returning the user account uid to the client;
s50: and if not, acquiring the account from the temporary user queue as the user account uid, storing the temporary user identifier and the user account uid into a database after the temporary user identifier and the user account uid are in a binding relationship, and returning the user account uid to the client.
The message pushing system receives the temporary user identifier and needs to verify the temporary user identifier, and specifically, the message pushing system checks whether a user account uid corresponding to the temporary user identifier exists in the database, and the following two situations exist:
first, if a user account uid corresponding to a temporary user identifier exists in the database, it is indicated that the user account uid is created for the temporary user corresponding to the temporary user identifier, and at this time, the user account uid corresponding to the temporary user identifier is returned to the client.
Secondly, if the database does not have the user account uid corresponding to the temporary user identifier, it is indicated that the temporary user corresponding to the temporary user identifier is new, at this time, an account needs to be acquired from the temporary user queue as the user account uid corresponding to the temporary user identifier, the temporary user identifier and the user account uid are stored in the database after being in a binding relationship, and finally the user account uid is returned to the client.
S60: and the temporary user processing center caches the user state of the temporary user corresponding to the temporary user identification.
It can be seen that the above steps S10-S60 are the process of the login and registration process of the temporary user.
S70: the web application program obtains the user account uid through sdk, and feeds the user account uid back to the web application program background.
S80: and the web application program background initiates a message pushing request which takes the user account uid as a target, wherein the message pushing request comprises the user account uid.
For steps S70-S80, after the message pushing system feeds back the user account uid corresponding to the temporary user identifier to the client, the web application may analyze the sdk (software Development kit) corresponding to the client, so as to obtain the user account uid through sdk, and feed back the user account uid to the web application background, so that the web application background initiates a message pushing request targeting the user account uid, where the message pushing request includes the user account uid, and sends the message pushing request to the message pushing system, so that the message pushing system initiates message pushing for a page associated with the user account uid, that is, initiates message pushing to a page corresponding to the temporary user identifier corresponding to the user account uid.
S90: the message push system identifies the message push request to determine whether the user account uid is a temporary user.
S100: and when the user account uid is identified as the user account uid of the temporary user, the message pushing system sends a pushing message to the temporary user processing center, and forwards the message pushing request to the temporary user processing center.
As to steps S90-S100, specifically, when the message push system receives the message push request, the message push request needs to be identified to determine whether the user account uid is a temporary user, and specifically, the user account id may be confirmed in the user account-temporary user identifier correspondence stored in the database. And when the user account uid is determined to be the temporary user, acquiring a push message which is required to be pushed to the temporary user, finally sending the push message to the temporary user processing center, and forwarding a message push request to the temporary user processing center.
S110: and the temporary user processing center checks the user state of the temporary user through the user account.
S120: when the temporary user is on line, the temporary user processing center issues a push message to the client.
S130: and when the temporary user is a valid user, the temporary user processing center locally stores the offline push message.
It should be noted that, as described above, the temporary user processing center may cache the cache state of the temporary user corresponding to the temporary user identifier, after receiving the message push request, the temporary user processing center checks the user state of the temporary user through the user account, and when the temporary user is online, the temporary user processing center issues the push message to the client; and when the temporary user is a valid user, the temporary user processing center locally stores the offline push message.
It can be seen that the above steps S70-S130 are the message pushing process for the temporary user.
Further, after the push message is sent to the client, when a message confirmation character corresponding to the push message is received, it indicates that the push message is successfully pushed at this time, and at this time, the temporary user processing center deletes the locally corresponding offline push message, thereby releasing the storage space.
In one embodiment, when the web page is closed or the long connection is disconnected, the temporary user processing center marks that the temporary user is offline, so that the pushing of the push message can be controlled according to the state of the temporary user.
In one embodiment, the temporary user center polls the user states of all temporary users regularly according to a polling plan; when the user state of the temporary user is in the offline state for more than a first preset time, for example, more than 10 minutes, it indicates that the temporary user is offline for a long time, and the temporary user center deletes the local data of the temporary user. It can be understood that a large number of web users open/close pages extremely frequently, which causes explosive increase of temporary users and pressure on pushing system resources; therefore, the temporary user needs to be distinguished from the formal user, and the consumption of the temporary user on system resources is reduced; especially after the page is closed, the resources occupied by the temporary user need to be released in time.
In one embodiment, the method further comprises the steps of:
the message pushing system determines whether the binding relationship between the temporary user identification and the user account uid in the database exceeds a second preset time length; and when the binding relationship between the temporary user identification and the user account uid exceeds a second preset time, contacting the binding relationship between the temporary user identification and the user account uid, and returning the user account id to the temporary user queue. The second preset time period may be half an hour, and may be set empirically.
In the embodiment of the invention, a special processing flow is designed for a temporary user to ensure the normal pushing of the temporary user, and corresponding resources can be released in time after the web page is closed, so that the influence on the message pushing of the normal user is reduced, the normal pushing of the temporary user can be ensured, the message pushing effect is greatly improved, the conversion of customers on a commercial level is facilitated, and the temporary customer is converted into a real customer.
An embodiment of the present invention, as shown in fig. 3, further provides a message pushing processing system, including: the system comprises a client, a web application program, a message pushing system, a web application program background and a temporary user processing center; the client is installed and operated with terminal equipment such as a mobile phone and a computer, and the web application program is a web application program opened through the client, wherein the functions or functions of the modules of the message push processing system are as follows:
the client is used for establishing an http connection with a web application program background and converting the http connection into a long connection when the web page is opened;
the web application program is used for calling an interface of the client to set a temporary user identifier corresponding to the web page and feeding the temporary user identifier back to the message pushing system;
the message pushing system is used for checking whether a user account uid corresponding to the temporary user identifier exists in a database or not, and if so, returning the user account uid to the client; if not, acquiring an account from a temporary user queue as the user account uid, storing the temporary user identifier and the user account uid into the database after the temporary user identifier and the user account uid are in a binding relationship, and returning the user account uid to the client;
the web application program is further used for acquiring the user account uid through sdk and feeding the user account uid back to a web application program background;
the web application program background is used for initiating a message pushing request which takes the user account uid as a target, and the message pushing request comprises the user account uid;
the message pushing system is used for identifying the message pushing request to determine whether the user account uid is a temporary user, and forwarding the message pushing request to a temporary user processing center when the user account uid is identified as the user account uid of the temporary user;
the temporary user processing center is used for checking the user state of the temporary user through the user account, storing offline push messages locally when the temporary user is a valid user, and issuing the push messages to the client when the temporary user is online.
Further, the temporary user center is further configured to: and after the push message is sent to the client, deleting the local corresponding offline push message when a message confirmation character corresponding to the push message is received.
Further, the temporary user processing center is further configured to:
caching the user state of the temporary user when the web page is opened;
when the web page is closed or the long connection is disconnected, marking the temporary user offline.
Further, the temporary user center is further configured to: polling the user states of all temporary users regularly according to a polling plan; and when the user state of the temporary user is in an off-line state and exceeds a first preset time, deleting the local data of the temporary user.
In the embodiment of the invention, the message pushing processing device for the web page is provided, a special processing flow is designed for a temporary user to ensure the normal pushing of the temporary user, corresponding resources can be released in time after the web page is closed, the message pushing influence on a normal user is reduced, the normal pushing of the temporary user can be ensured, the message pushing effect is greatly improved, the conversion of customers on a commercial level is facilitated, and the temporary customer is converted into a real customer.
For the role or implemented function of each module in the message push processing system, specific limitations may refer to the above related limitations in the message push processing method, and are not described herein again.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.
In one embodiment, a computer device is provided, the internal structure of which may be as shown in FIG. 4. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. When executed by the processor, the computer program implements functions or steps corresponding to related hardware devices in the message push processing method, such as functions or steps corresponding to a terminal device side, a web application program background, a temporary user processing center, and a message push system.
In an embodiment, a private cloud server is further provided, where the private cloud server is configured to implement a server-side function in the message push processing system.
In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, which when executed by a processor implements the functions or steps of the relevant body in the above-described message push processing method, including the functions or steps of the client, the web application, the message push system, and the temporary user processing center body.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present invention, and are intended to be included within the scope of the present invention.
Claims (10)
1. A message push processing method is characterized by comprising the following steps:
when a web page is opened, a client establishes an http connection with a web application background and converts the http connection into a long connection;
the web application program calls an interface of the client to set a temporary user identifier corresponding to the web page and feeds the temporary user identifier back to the message pushing system;
the message pushing system checks whether a user account uid corresponding to the temporary user identifier exists in a database, and if so, returns the user account uid to the client; if not, acquiring an account from a temporary user queue as the user account uid, storing the temporary user identifier and the user account uid into the database after the temporary user identifier and the user account uid are in a binding relationship, and returning the user account uid to the client;
the web application program acquires the user account uid through sdk and feeds the user account uid back to the web application program background;
the web application program background initiates a message pushing request with the user account uid as a target, wherein the message pushing request comprises the user account uid;
the message pushing system identifies the message pushing request to determine whether the user account uid is a temporary user;
when the user account uid is identified as the user account uid of the temporary user, sending a push message to a temporary user processing center, and forwarding the message push request to the temporary user processing center;
the temporary user processing center checks the user state of the temporary user through the user account, when the temporary user is a valid user, the temporary user processing center locally stores the offline push message, and when the temporary user is online, the temporary user processing center issues the push message to the client.
2. The message push processing method of claim 1, wherein after the sending the push message to the client, the method further comprises:
and when receiving the message confirmation character corresponding to the push message, the temporary user processing center deletes the local corresponding offline push message.
3. The message push processing method of claim 1, wherein when a web page is opened, the method further comprises:
the temporary user processing center caches the user state of the temporary user;
and when the web page is closed or the long connection is disconnected, the temporary user processing center marks that the temporary user is offline.
4. The message push processing method of claim 3, wherein the method further comprises:
the temporary user center polls the user states of all temporary users regularly according to a polling plan;
and when the user state of the temporary user is in an off-line state and exceeds a first preset time, deleting the local data of the temporary user by the temporary user center.
5. The message push processing method of claim 1, wherein the method further comprises:
the message pushing system determines whether the binding relationship between the temporary user identification and the user account uid in the database exceeds a second preset duration;
and when the binding relationship between the temporary user identification and the user account uid exceeds the second preset duration, contacting the binding relationship between the temporary user identification and the user account uid, and returning the user account id to the temporary user queue.
6. The message push processing method according to claim 1, wherein the converting the http connection to a long connection comprises:
and converting the http connection into a websocket long connection.
7. A message push processing system, comprising: the system comprises a client, a web application program, a message pushing system, a web application program background and a temporary user processing center;
the client is used for establishing an http connection with a web application program background and converting the http connection into a long connection when the web page is opened;
the web application program is used for calling an interface of the client to set a temporary user identifier corresponding to the web page and feeding the temporary user identifier back to the message pushing system;
the message pushing system is used for checking whether a user account uid corresponding to the temporary user identifier exists in a database or not, and if so, returning the user account uid to the client; if not, acquiring an account from a temporary user queue as the user account uid, storing the temporary user identifier and the user account uid into the database after the temporary user identifier and the user account uid are in a binding relationship, and returning the user account uid to the client;
the web application program is further used for acquiring the user account uid through sdk and feeding the user account uid back to a web application program background;
the web application program background is used for initiating a message pushing request which takes the user account uid as a target, and the message pushing request comprises the user account uid;
the message pushing system is used for identifying the message pushing request to determine whether the user account uid is a temporary user, and forwarding the message pushing request to a temporary user processing center when the user account uid is identified as the user account uid of the temporary user;
the temporary user processing center is used for checking the user state of the temporary user through the user account, storing offline push messages locally when the temporary user is a valid user, and issuing the push messages to the client when the temporary user is online.
8. The message push processing system of claim 7, wherein the temporary user hub is further configured to:
and after the push message is sent to the client, deleting the local corresponding offline push message when a message confirmation character corresponding to the push message is received.
9. The message push processing system of claim 7, wherein the temporary user processing center is further configured to:
caching the user state of the temporary user when the web page is opened;
when the web page is closed or the long connection is disconnected, marking the temporary user offline.
10. The message push processing system of claim 9, wherein the temporary user hub is further configured to:
polling the user states of all temporary users regularly according to a polling plan; and when the user state of the temporary user is in an off-line state and exceeds a first preset time, deleting the local data of the temporary user.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011255700.7A CN112165535B (en) | 2020-11-11 | 2020-11-11 | Message pushing processing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011255700.7A CN112165535B (en) | 2020-11-11 | 2020-11-11 | Message pushing processing method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112165535A true CN112165535A (en) | 2021-01-01 |
| CN112165535B CN112165535B (en) | 2023-07-04 |
Family
ID=73865795
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011255700.7A Active CN112165535B (en) | 2020-11-11 | 2020-11-11 | Message pushing processing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112165535B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040117247A1 (en) * | 2002-12-12 | 2004-06-17 | Aseem Agrawal | Method and system for enabling unregistered users to manage electronic items across sessions |
| CN102882888A (en) * | 2012-10-18 | 2013-01-16 | 北京奇虎科技有限公司 | Network application access method and system |
| CN104767775A (en) * | 2014-01-06 | 2015-07-08 | 腾讯科技（深圳）有限公司 | Webpage application information push method and webpage application information push system |
| CN109274705A (en) * | 2017-07-17 | 2019-01-25 | 车伯乐（北京）信息科技有限公司 | Service providing method, apparatus and system based on user identity |
| CN111475843A (en) * | 2020-04-08 | 2020-07-31 | 腾讯科技（深圳）有限公司 | Data processing method and related device |
-
2020
- 2020-11-11 CN CN202011255700.7A patent/CN112165535B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040117247A1 (en) * | 2002-12-12 | 2004-06-17 | Aseem Agrawal | Method and system for enabling unregistered users to manage electronic items across sessions |
| CN102882888A (en) * | 2012-10-18 | 2013-01-16 | 北京奇虎科技有限公司 | Network application access method and system |
| CN104767775A (en) * | 2014-01-06 | 2015-07-08 | 腾讯科技（深圳）有限公司 | Webpage application information push method and webpage application information push system |
| CN109274705A (en) * | 2017-07-17 | 2019-01-25 | 车伯乐（北京）信息科技有限公司 | Service providing method, apparatus and system based on user identity |
| CN111475843A (en) * | 2020-04-08 | 2020-07-31 | 腾讯科技（深圳）有限公司 | Data processing method and related device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112165535B (en) | 2023-07-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108833521B (en) | Message pushing method, device, system, computer equipment and storage medium | |
| CN110138741B (en) | Micro-service management method and device based on unified management platform and computer equipment | |
| CN102333081B (en) | Authentication method, equipment and system | |
| CN105592035A (en) | Single sign on method used for multiple application systems | |
| CN104092839A (en) | Communication method, system, IM server and operator service platform and terminal | |
| CN112417416A (en) | Authentication interaction method, system and storage medium of service system | |
| CN111200633A (en) | Indirect access method and system for business system | |
| CN108966159B (en) | Short message withdrawing method, system, computer equipment and storage medium | |
| CN101227456B (en) | System and method for implementing data synchronization | |
| CN112468540A (en) | Data distribution method, device and medium based on cloud platform | |
| CN104767614A (en) | Information authentication method and device | |
| CN110769482B (en) | Method and device for network connection of wireless equipment and wireless router equipment | |
| CN110913083A (en) | Communication line connection method, communication line connection device, computer equipment and storage medium | |
| CN112910868A (en) | Enterprise network security management method and device, computer equipment and storage medium | |
| CN112165535B (en) | Message pushing processing method and system | |
| CN112632375A (en) | Session information processing method, server and storage medium | |
| CN112968963A (en) | WebSocket-based method for user forced real-time offline | |
| CN109587013B (en) | APP network compatibility testing method and device, computer equipment and storage medium | |
| CN110856145B (en) | IOT (Internet of things) equipment and user binding method, equipment and medium based on near field authentication | |
| CN111147548A (en) | Service data processing method and device, computer equipment and storage medium | |
| CN109766062A (en) | Web page contents Method of printing, device, equipment and storage medium based on PHP service | |
| JP2016154332A (en) | Devices and methods for performing tcp handshakes | |
| WO2022116696A1 (en) | Method and apparatus for establishing communication connection | |
| CN113993124A (en) | Number portability method, number portability device, communication terminal, and storage medium | |
| CN104219263A (en) | Push processing method and system for defaulting prompt information |
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 |