CN110661889B - Push message synchronization and compensation method and system of iOS (integrated operation system) terminal - Google Patents

Push message synchronization and compensation method and system of iOS (integrated operation system) terminal Download PDF

Info

Publication number
CN110661889B
CN110661889B CN201911076139.3A CN201911076139A CN110661889B CN 110661889 B CN110661889 B CN 110661889B CN 201911076139 A CN201911076139 A CN 201911076139A CN 110661889 B CN110661889 B CN 110661889B
Authority
CN
China
Prior art keywords
ios
message
push message
server
push
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201911076139.3A
Other languages
Chinese (zh)
Other versions
CN110661889A (en
Inventor
朱盼
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hangzhou Tuya Information Technology Co Ltd
Original Assignee
Hangzhou Tuya Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hangzhou Tuya Information Technology Co Ltd filed Critical Hangzhou Tuya Information Technology Co Ltd
Priority to CN201911076139.3A priority Critical patent/CN110661889B/en
Publication of CN110661889A publication Critical patent/CN110661889A/en
Application granted granted Critical
Publication of CN110661889B publication Critical patent/CN110661889B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/55Push-based network services
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00Reducing energy consumption in communication networks
    • Y02D30/70Reducing energy consumption in communication networks in wireless communication networks

Abstract

The invention relates to a push message synchronization and compensation method and a system, wherein the method comprises the following steps: the iOS server receives and stores the push message sent by the application server; the iOS server generates a unique identifier and marks the push message according to the unique identifier; the iOS server side sends a push message with a unique identifier to the APNS service; the iOS client receives the push message with the unique identification from the APNS service; the iOS client sends a message arrival notification to the iOS server and uploads a unique identifier; the iOS server marks the push message corresponding to the unique identifier as read according to the message arrival notification. After receiving the push message sent by the application server, the iOS server pushes the message to the iOS client on the iOS equipment of the user through the APNS service link, and the iOS client can actively report that the push message arrives to the iOS server, so that the application server can timely know whether the user has received the message.

Description

Push message synchronization and compensation method and system of iOS (integrated operation system) terminal
Technical Field
The invention relates to the technical field of communication, in particular to a push message synchronization and compensation method of an iOS end, and a push message synchronization and compensation system of the iOS end.
Background
Push is a way of communication between a server and a client. The pushing function of the iOS end is provided by the apple company's APNS service, because the iOS is a closed system, the application on the platform can only use the APNS service to realize the pushing function, and no other selection exists, therefore, the iOS application program developed based on the iOS platform can use the service, the APNS service can establish a data connection link with the apple company server when the network of user equipment (including but not limited to iPhone, iPad, iPod equipment and the like) is good, when an application developer needs to send a message to a designated user, the application developer needs to send a request to the apple company server, and then send the message to the user equipment through the established link. The APNS service can help application developers complete the necessary communications between the server and the user when the application is not open.
However, the existing push mechanism for the iOS end has at least the following problems:
1. after an application developer (hereinafter referred to as a developer) sends a message to an APNS service of an apple company (hereinafter referred to as an apple), a specific sending time is determined by the apple, and the developer cannot know when the apple is issued and cannot know whether a user receives the message;
2. the APNS service of the apples is not built with a server in China temporarily, the service quality in China is unstable and easy to fluctuate, so that the message sent to the apples by a developer cannot be sent to user equipment, and finally the message is lost;
3. because of efficiency considerations, an unreliable link is established between the apple's APNS service and the user equipment, and when the user equipment network condition is poor, even if the apple sends a message to the user equipment, the message may be lost;
4. apple APNS service does not provide retransmission mechanism, developer does not back up the message, and the message can not be retrieved after losing.
Disclosure of Invention
The present invention aims to solve at least one of the technical problems existing in the prior art or related art.
Therefore, an object of the present invention is to provide a push message synchronization and compensation method for an iOS end, which enables an iOS client to actively report a message sent by an apple via an APNS service link to a developer server after receiving the message, so that the developer can know the condition that a user receives the message in time.
Another object of the present invention is to provide a push message synchronization and compensation system of an iOS end, which can resend the same message if the same message is not received from a client within a specified time after a message is sent from a server, so as to improve the possibility of receiving the message by a user.
In order to achieve the above object, the technical solution of the first aspect of the present invention provides a push message synchronization and compensation method for an iOS end, including the following steps: the iOS server receives and stores the push message sent by the application server; the iOS server generates a unique identifier and marks the push message according to the unique identifier; the iOS server side sends a push message with a unique identifier to the APNS service; the iOS client receives the push message with the unique identification from the APNS service; the iOS client sends a message arrival notification to the iOS server and uploads a unique identifier; the iOS server marks the push message corresponding to the unique identifier as read according to the message arrival notification.
In the technical scheme, after the server of the application developer sends the push message to the APNS service at present, the specific sending time is determined by the APNS service, and the application developer cannot know when the APNS service sends the push message to the iOS device or whether the user receives the push message. In order to solve the problem, after receiving the push message sent by the application server, the iOS server provided by the invention pushes the message to the iOS client on the iOS equipment of the user through the APNS service link, and the iOS client can actively report that the push message arrives to the iOS server after receiving the push message, so that the application server can timely know whether the user has received the information.
In the above technical solution, preferably, the method further includes the following steps: the iOS server receives an unread message acquisition request from the iOS client, wherein the unread message acquisition request comprises client information and equipment information corresponding to the iOS client; the iOS server side inquires push messages which are not read by the iOS client side according to the client information and the equipment information, and historical push messages are obtained; the iOS client receives the historical push message from the iOS server, compares the historical push message with the local message, and removes the duplication to obtain an unread push message; the iOS client inserts the unread push message into a local message queue of the target device according to the preset priority; the iOS client generates a message arrival notification according to each unread message data of the local message queue; wherein the preset priority is time priority.
In the technical scheme, the message sent to the iOS system by the developer cannot be issued to the user equipment due to unstable and easy fluctuation of the APNS service quality possibly occurring in the current iOS system, and finally the message is lost; in order to solve the problem, the iOS server provided by the invention can backup push messages in time, can be retrieved after the messages are lost, and can actively de-duplicate the received messages when the iOS client of the user equipment receives the backed-up historical push messages, thereby avoiding repeated reception of the same messages.
In any of the above technical solutions, preferably, the method further includes the following steps: the iOS server inquires whether a message arrival notification is received according to a preset time interval, and an inquiry result is obtained; the iOS server judges whether to send the push message to the iOS client again according to the query result; wherein the preset time interval is greater than 30s.
In the technical scheme, because the APNS service of the current iOS system does not provide a retransmission mechanism and a developer does not back up the message, the problem that the message cannot be retrieved after being lost easily occurs; in order to solve the technical problem, after sending the push message, if the iOS server provided by the invention does not receive the message arrival notification of the iOS client on the user equipment within the designated time, the same message is retransmitted, so that the possibility that the user receives the message is improved.
The technical scheme of the second aspect of the present invention provides a push message synchronization and compensation system of an iOS end, which comprises an iOS client and an iOS server, wherein the iOS server specifically comprises: a backup module configured to receive and store push messages sent from the application server; the marking module is used for generating a unique identifier and marking the push message according to the unique identifier; the pushing module is used for sending a pushing message with a unique identification to the APNS service; a message arrival identification module arranged to mark a push message corresponding to the unique identity as read in accordance with the message arrival notification; the iOS client specifically includes: a message acquisition module configured to receive a push message from an APNS service having a unique identity; and the notification expansion module is used for generating a message arrival notification according to the push message, sending the message arrival notification to the iOS server and uploading the unique identifier.
In the technical scheme, after the server of the application developer sends the push message to the APNS service at present, the specific sending time is determined by the APNS service, and the application developer cannot know when the APNS service sends the push message to the iOS device or whether the user receives the push message. In order to solve the problem, after receiving the push message sent by the application server, the iOS server provided by the invention pushes the message to the iOS client on the iOS equipment of the user through the APNS service link, and the iOS client can actively report that the push message arrives to the iOS server after receiving the push message, so that the application server can timely know whether the user has received the information.
In the above technical solution, preferably, the iOS server further includes: the unread message query module is arranged for receiving a request for acquiring unread messages from the iOS client and querying unread push messages of the iOS client according to the request for acquiring the unread messages to obtain historical push messages; the iOS client further comprises: the message deduplication module is arranged to receive the historical push message from the iOS server and compare the historical push message with the local message to deduplicate the historical push message to obtain an unread push message; the local message module is used for inserting unread push messages into a local message queue of the target device according to a preset priority; the unread message obtaining request comprises client information and equipment information corresponding to the iOS client, and the preset priority is time priority.
In the technical scheme, the message sent to the iOS system by the developer cannot be issued to the user equipment due to unstable and easy fluctuation of the APNS service quality possibly occurring in the current iOS system, and finally the message is lost; in order to solve the problem, the iOS server provided by the invention can backup push messages in time, can be retrieved after the messages are lost, and can actively de-duplicate the received messages when the iOS client of the user equipment receives the backed-up historical push messages, thereby avoiding repeated reception of the same messages.
In any of the foregoing solutions, preferably, the iOS server further includes: the query module is used for querying whether a message arrival notification is received according to a preset time interval to obtain a query result; the control module is used for judging whether to send the push message to the iOS client again according to the query result; wherein the preset time interval is more than 30s, and the optional value is 40s, 60s or 90s.
In the technical scheme, because the APNS service of the current iOS system does not provide a retransmission mechanism and a developer does not back up the message, the problem that the message cannot be retrieved after being lost easily occurs; in order to solve the technical problem, after sending the push message, if the iOS server provided by the invention does not receive the message arrival notification of the iOS client on the user equipment within the designated time, the same message is retransmitted, so that the possibility that the user receives the message is improved.
In any of the foregoing solutions, preferably, the unique identifier is generated according to device information, user information, and content of the push message of the iOS client.
In the technical scheme, after an iOS server sends a push message with a unique identifier to an iOS client through an APNS service of an iOS system, recording and backing up are carried out in a database; the unique identification is generated from the user information, the device information, the content of the message, and it is required that the user information and the device information can be checked back by the unique identification, and the code has uniqueness.
Drawings
The foregoing and/or additional aspects and advantages of the invention will become apparent and may be better understood from the following description of embodiments taken in conjunction with the accompanying drawings in which:
figure 1 shows a block flow diagram of a method according to a first embodiment of the invention;
figure 2 shows a block flow diagram of a method according to a second embodiment of the invention;
figure 3 shows a block flow diagram of a method according to a third embodiment of the invention;
figure 4 shows a block flow diagram of a method according to a fourth embodiment of the invention;
FIG. 5 is a block diagram showing the architecture of an iOS server according to a fifth embodiment of the invention;
fig. 6 is a block diagram showing the structure of an iOS client according to a fifth embodiment of the present invention.
Detailed Description
In order that the above-recited objects, features and advantages of the present invention will be more clearly understood, a more particular description of the invention will be rendered by reference to the appended drawings and appended detailed description. It should be noted that, in the case of no conflict, the embodiments of the present application and the features in the embodiments may be combined with each other.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention, however, the present invention may be practiced in other ways than those described herein, and the scope of the invention is therefore not limited to the specific embodiments disclosed below.
Push message synchronization and compensation methods and systems at the iOS end according to some embodiments of the present invention are described below with reference to fig. 1 to 6.
As shown in fig. 1, the push message synchronization and compensation method of the iOS end according to the first embodiment of the present invention includes the following steps:
s1, an iOS server receives and stores a push message sent by an application server;
s2, the iOS server generates a unique identifier and marks the push message according to the unique identifier;
s3, the iOS server side sends a push message with a unique identifier to the APNS service;
s4, the iOS client receives the push message with the unique identification from the APNS service;
s10, an iOS client sends a message arrival notification to an iOS server and uploads a unique identifier;
s11, the iOS server marks the push message corresponding to the unique identifier as read according to the message arrival notification.
In this embodiment, after the server of the application developer sends the push message to the APNS service at present, the specific sending time is determined by the APNS service, and the application developer cannot know when the APNS service issues the push message to the iOS device, or whether the user receives the push message. In order to solve the problem, after receiving the push message sent by the application server, the iOS server provided by the invention pushes the message to the iOS client on the iOS equipment of the user through the APNS service link, and the iOS client can actively report that the push message arrives to the iOS server after receiving the push message, so that the application server can timely know whether the user has received the information.
As shown in fig. 2, the push message synchronization and compensation method of the iOS end according to the second embodiment of the present invention includes the following steps:
s1, an iOS server receives and stores a push message sent by an application server;
s2, the iOS server generates a unique identifier and marks the push message according to the unique identifier;
s3, the iOS server side sends a push message with a unique identifier to the APNS service;
s4, the iOS client receives the push message with the unique identification from the APNS service;
s5, the iOS server receives an unread message acquisition request from the iOS client, wherein the unread message acquisition request comprises client information and equipment information corresponding to the iOS client;
s6, the iOS server side inquires push messages which are not read by the iOS client side according to the client information and the equipment information, and historical push messages are obtained;
s7, the iOS client receives the historical push message from the iOS service, compares the historical push message with the local message and removes the duplication to obtain an unread push message;
s8, the iOS client inserts unread push messages into a local message queue of the target device according to the preset priority;
s9, the iOS client generates a message arrival notification according to each unread message data of the local message queue;
s10, an iOS client sends a message arrival notification to an iOS server and uploads a unique identifier;
s11, marking the push message corresponding to the unique identifier as read according to the message arrival notification by the iOS server;
wherein the preset priority is time priority.
In this embodiment, the quality of the APNS service that may occur in the current iOS system is unstable and is easy to fluctuate, so that the message sent to the iOS system by the developer cannot be sent to the user equipment, and the message is lost finally; in order to solve the problem, the iOS server provided by the invention can backup push messages in time, can be retrieved after the messages are lost, and can actively de-duplicate the received messages when the iOS client of the user equipment receives the backed-up historical push messages, thereby avoiding repeated reception of the same messages.
As shown in fig. 3, the push message synchronization and compensation method of the iOS end according to the third embodiment of the present invention includes the following steps:
s1, an iOS server receives and stores a push message sent by an application server;
s2, the iOS server generates a unique identifier and marks the push message according to the unique identifier;
s3, the iOS server side sends a push message with a unique identifier to the APNS service;
s4, the iOS client receives the push message with the unique identification from the APNS service;
s10, an iOS client sends a message arrival notification to an iOS server and uploads a unique identifier;
s11, marking the push message corresponding to the unique identifier as read according to the message arrival notification by the iOS server;
s12, the iOS server inquires whether a message arrival notification is received according to a preset time interval, and an inquiry result is obtained;
s13, the iOS server judges whether to send the push message to the iOS client again according to the query result;
wherein the preset time interval is more than 30s, and the optional value is 40s, 60s or 90s.
In this embodiment, after the server of the application developer sends the push message to the APNS service at present, the specific sending time is determined by the APNS service, and the application developer cannot know when the APNS service issues the push message to the iOS device, or whether the user receives the push message. In order to solve the problem, after receiving the push message sent by the application server, the iOS server provided by the invention pushes the message to the iOS client on the iOS equipment of the user through the APNS service link, and the iOS client can actively report that the push message arrives to the iOS server after receiving the push message, so that the application server can timely know whether the user has received the information.
In this embodiment, because the APNS service of the iOS system does not provide a retransmission mechanism at present, the developer does not back up the message, so that the problem that the message cannot be retrieved after being lost easily occurs; in order to solve the technical problem, after sending the push message, if the iOS server provided by the invention does not receive the message arrival notification of the iOS client on the user equipment within the designated time, the same message is retransmitted, so that the possibility that the user receives the message is improved.
As shown in fig. 4, the push message synchronization and compensation method at the iOS end according to the fourth embodiment of the present invention includes the following steps:
s1, an iOS server receives and stores a push message sent by an application server;
s2, the iOS server generates a unique identifier and marks the push message according to the unique identifier;
s3, the iOS server side sends a push message with a unique identifier to the APNS service;
s4, the iOS client receives the push message with the unique identification from the APNS service;
s5, the iOS server receives an unread message acquisition request from the iOS client, wherein the unread message acquisition request comprises client information and equipment information corresponding to the iOS client;
s6, the iOS server side inquires push messages which are not read by the iOS client side according to the client information and the equipment information, and historical push messages are obtained;
s7, the iOS client receives the historical push message from the iOS server, compares the historical push message with the local message and removes the duplication to obtain an unread push message;
s8, the iOS client inserts unread push messages into a local message queue of the target device according to the preset priority;
s9, the iOS client generates a message arrival notification according to each unread message data of the local message queue;
s10, an iOS client sends a message arrival notification to an iOS server and uploads a unique identifier;
s11, marking the push message corresponding to the unique identifier as read according to the message arrival notification by the iOS server;
s12, the iOS server inquires whether a message arrival notification is received according to a preset time interval, and an inquiry result is obtained;
s13, the iOS server judges whether to send the push message to the iOS client again according to the query result;
wherein the preset time interval is more than 30s, and the selectable value is 40s, 60s or 90s; the preset priority is time priority.
In this embodiment, the quality of the APNS service that may occur in the current iOS system is unstable and is easy to fluctuate, so that the message sent to the iOS system by the developer cannot be sent to the user equipment, and the message is lost finally; in order to solve the problem, the iOS server provided by the invention can backup push messages in time, can be retrieved after the messages are lost, and can actively de-duplicate the received messages when the iOS client of the user equipment receives the backed-up historical push messages, thereby avoiding repeated reception of the same messages.
In this embodiment, because the APNS service of the iOS system does not provide a retransmission mechanism at present, the developer does not back up the message, so that the problem that the message cannot be retrieved after being lost easily occurs; in order to solve the technical problem, after sending the push message, if the iOS server provided by the invention does not receive the message arrival notification of the iOS client on the user equipment within the designated time, the same message is retransmitted, so that the possibility that the user receives the message is improved.
As shown in fig. 5 and 6, the push message synchronization and compensation system of the iOS side according to the fifth embodiment of the present invention includes an iOS client 1000 and an iOS server 2000, wherein,
the iOS server 1000 specifically includes:
a backup module 110 configured to receive and store push messages sent from the application server;
a tagging module 120 arranged to generate a unique identifier and tag the push message according to the unique identifier;
a push module 130 configured to send a push message with a unique identification to the APNS service;
a message arrival identification module 140 arranged to mark the push message corresponding to the unique identity as read in accordance with the message arrival notification;
the unread message query module 150 is configured to receive a request for acquiring unread messages from the iOS client, and query unread push messages of the iOS client according to the request for acquiring unread messages, so as to obtain historical push messages;
a query module 160 configured to query whether a message arrival notification is received according to a preset time interval, to obtain a query result;
a control module 170 configured to determine whether to resend the push message to the iOS client according to the query result;
the iOS client 2000 specifically includes:
a message acquisition module 210 configured to receive a push message from the APNS service having a unique identity;
a notification extension module 220 configured to generate a message arrival notification according to the push message, send the message arrival notification to the iOS server, and upload the unique identifier;
the message deduplication module 230 is configured to receive the historical push message from the iOS server, and compare the historical push message with the local message to deduplicate, thereby obtaining an unread push message;
a local message module 240 configured to insert unread push messages into a local message queue of the target device according to a preset priority;
the method comprises the steps that an unread message request comprises client information and equipment information corresponding to an iOS client, and a preset priority is time priority; the preset time interval is greater than 30s, and the optional value is 40s, 60s or 90s.
In this embodiment, after the server of the application developer sends the push message to the APNS service at present, the specific sending time is determined by the APNS service, and the application developer cannot know when the APNS service issues the push message to the iOS device, or whether the user receives the push message. In order to solve the problem, after receiving the push message sent by the application server, the iOS server provided by the invention pushes the message to the iOS client on the iOS equipment of the user through the APNS service link, and the iOS client can actively report that the push message arrives to the iOS server after receiving the push message, so that the application server can timely know whether the user has received the information.
In this embodiment, the quality of the APNS service that may occur in the current iOS system is unstable and is easy to fluctuate, so that the message sent to the iOS system by the developer cannot be sent to the user equipment, and the message is lost finally; in order to solve the problem, the iOS server provided by the invention can backup push messages in time, can be retrieved after the messages are lost, and can actively de-duplicate the received messages when the iOS client of the user equipment receives the backed-up historical push messages, thereby avoiding repeated reception of the same messages.
In this embodiment, because the APNS service of the iOS system does not provide a retransmission mechanism at present, the developer does not back up the message, so that the problem that the message cannot be retrieved after being lost easily occurs; in order to solve the technical problem, after sending the push message, if the iOS server provided by the invention does not receive the message arrival notification of the iOS client on the user equipment within the designated time, the same message is retransmitted, so that the possibility that the user receives the message is improved.
In any of the above embodiments, the unique identification is preferably generated from device information, user information, and content of the push message of the iOS client.
In the embodiment, after sending a push message with a unique identifier to an iOS client through an aspect service of an iOS system, an iOS server records and backs up in a database; the unique identification is generated from the user information, the device information, the content of the message, and it is required that the user information and the device information can be checked back by the unique identification, and the code has uniqueness.
It should be noted that, the Apple Push Notification Service (APNS) is a gateway of push notification, and the iPhone and the iPad have many restrictions on the application running in the background, and the application does not allow excessive operations in the background in consideration of the battery power of the mobile phone. Therefore, when the user switches to another program, the original program cannot be kept in an operating state. For applications that need to maintain a continuous connection (such as community network applications), real-time information will not be received. Push is a better solution to traffic and power consumption caused by polling.
To address this limitation, apples have evolved an APNS (apple push notification service Apple Push Notification services). The APNS allows the device to remain in a constantly connected state with the apple's push notification server. When you want to send a push notification to an application on an iPhone of a user, you can send a push message to an application already installed on the target device using the APNS.
The push service APNS of an apple is based on the principle that an apple receives information to be pushed from an application server of the apple by using a special push server (APNS), then pushes the information to a specified iOS device, then notifies the device to an application program of the apple, and the device notifies a user of a new message in the form of notification or sound. The premise of pushing is that the equipment provided with the application needs to register with an APNS server, after the registration is successful, the APNS server returns to a device token, after the device token is taken, the device token is sent to the application server of the device, when the information needing to be pushed exists, the application server packages the information according to a specified format, then the information is sent to the APNS server together with the device token of the equipment, and as the application and the APNS maintain a long connection based on TCP, the APNS pushes the new information to the equipment of the device, and then the new information is displayed on a screen.
Based on the method shown in fig. 1 to fig. 4, correspondingly, the embodiment of the application further provides a storage medium, on which a computer program is stored, where the program, when executed by a processor, implements the steps of the push message synchronization and compensation method of the iOS end shown in fig. 1 to fig. 4.
Based on such understanding, the technical solution of the present application may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.), and includes several instructions for causing a computer device (may be a personal computer, a server, or a network device, etc.) to perform the method of each implementation scenario of the present application.
Based on the method shown in fig. 1 to fig. 4 and the virtual device embodiments shown in fig. 5 and fig. 6, in order to achieve the above objects, the embodiments of the present application further provide a computer device, which may specifically be a personal computer, a server, a network device, etc., where the computer device includes a storage medium and a processor; a storage medium storing a computer program; and a processor for executing a computer program to implement the steps of the push message synchronization and compensation method of the iOS end shown in fig. 1 to 4.
Optionally, the computer device may also include a user interface, a network interface, a camera, radio Frequency (RF) circuitry, sensors, audio circuitry, WI-FI modules, and the like. The user interface may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), etc., and the optional user interface may also include a USB interface, a card reader interface, etc. The network interface may optionally include a standard wired interface, a wireless interface (e.g., bluetooth interface, WI-FI interface), etc.
It will be appreciated by those skilled in the art that the architecture of a computer device provided in the present embodiment is not limited to the computer device, and may include more or fewer components, or may combine certain components, or may be arranged in different components.
The storage medium may also include an operating system, a network communication module. An operating system is a program that manages and saves computer device hardware and software resources, supporting the execution of information handling programs and other software and/or programs. The network communication module is used for realizing communication among all components in the storage medium and communication with other hardware and software in the entity equipment.
The storage medium may also include an operating system, a network communication module. An operating system is a program that manages and saves computer device hardware and software resources, supporting the execution of information handling programs and other software and/or programs. The network communication module is used for realizing communication among all components in the storage medium and communication with other hardware and software in the entity equipment.
In the present invention, the terms "first," "second," "third," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance; the term "plurality" means two or more, unless expressly defined otherwise. The terms "mounted," "connected," "secured," and the like are to be construed broadly, and may be, for example, fixedly connected, detachably connected, or integrally connected; "coupled" may be directly coupled or indirectly coupled through intermediaries. The specific meaning of the above terms in the present invention can be understood by those of ordinary skill in the art according to the specific circumstances.
In the description of the present invention, it should be understood that the directions or positional relationships indicated by the terms "upper", "lower", "left", "right", "front", "rear", etc. are based on the directions or positional relationships shown in the drawings, are merely for convenience of describing the present invention and simplifying the description, and do not indicate or imply that the devices or units referred to must have a specific direction, be constructed and operated in a specific direction, and thus should not be construed as limiting the present invention.
In the description of the present specification, the terms "one embodiment," "some embodiments," "particular embodiments," and the like, mean 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 invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
The above description is only of the preferred embodiments of the present invention and is not intended to limit the present invention, but various modifications and variations can be made to the present invention by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (4)

1. The push message synchronization and compensation method of the iOS end is characterized by comprising the following steps:
the iOS server receives and stores the push message sent by the application server;
the iOS server generates a unique identifier, marks the push message according to the unique identifier, generates the unique identifier according to user information, equipment information and the content of the message, and requires that the user information and the equipment information can be reversely checked through the unique identifier, and the code has uniqueness;
the iOS server side sends the push message with the unique identifier to an APNS service;
the iOS client receives the push message with the unique identifier from the APNS service;
the iOS server receives an unread message acquisition request from the iOS client, wherein the unread message acquisition request comprises client information and equipment information corresponding to the iOS client;
the iOS server side inquires the push message which is not read by the iOS client side according to the client information and the equipment information to obtain a historical push message;
the iOS client receives the history push message from the iOS server, compares the history push message with a local message, and removes duplication to obtain an unread push message;
the iOS client inserts the unread push message into a local message queue of target equipment according to a preset priority, wherein the preset priority is time priority;
the iOS client generates the message arrival notification according to each unread message data of the local message queue;
the iOS client sends a message arrival notification to the iOS server and uploads the unique identifier;
the iOS server marks the push message corresponding to the unique identifier as read according to the message arrival notification;
the iOS server inquires whether the message arrival notification is received or not according to a preset time interval, and an inquiry result is obtained;
and the iOS server judges whether to send the push message to the iOS client again according to the query result.
2. The iOS-side push message synchronization and compensation method according to claim 1, wherein the preset time interval is greater than 30s.
3. A push message synchronization and compensation system of an iOS terminal is characterized by comprising an iOS client and an iOS server, wherein,
the iOS server specifically includes:
a backup module configured to receive and store push messages sent from the application server;
the marking module is used for generating a unique identifier, marking the push message according to the unique identifier, generating the unique identifier according to the user information, the equipment information and the content of the message, and requiring that the user information and the equipment information can be reversely checked through the unique identifier, wherein the code has uniqueness;
a push module configured to send the push message with the unique identification to an APNS service;
a message arrival identification module arranged to mark the push message corresponding to the unique identity as read in accordance with the message arrival notification;
the unread message query module is configured to receive an unread message acquisition request from the iOS client, and query the push message unread by the iOS client according to the unread message acquisition request to obtain a historical push message, wherein the unread message acquisition request comprises client information and equipment information corresponding to the iOS client;
the query module is used for querying whether the message arrival notification is received or not according to a preset time interval to obtain a query result;
the control module is used for judging whether to send the push message to the iOS client again according to the query result;
the iOS client specifically includes:
a message acquisition module configured to receive the push message from the APNS service having the unique identity;
the notification expansion module is used for generating a message arrival notification according to the push message, sending the message arrival notification to the iOS server and uploading the unique identifier;
the message deduplication module is arranged to receive the history push message from the iOS server and compare the history push message with a local message to deduplicate the history push message to obtain an unread push message;
and the local message module is used for inserting the unread push message into a local message queue of the target device according to a preset priority, wherein the preset priority is time priority.
4. The iOS-side push message synchronization and compensation system of claim 3, wherein the preset time interval is greater than 30s.
CN201911076139.3A 2019-11-06 2019-11-06 Push message synchronization and compensation method and system of iOS (integrated operation system) terminal Active CN110661889B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911076139.3A CN110661889B (en) 2019-11-06 2019-11-06 Push message synchronization and compensation method and system of iOS (integrated operation system) terminal

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911076139.3A CN110661889B (en) 2019-11-06 2019-11-06 Push message synchronization and compensation method and system of iOS (integrated operation system) terminal

Publications (2)

Publication Number Publication Date
CN110661889A CN110661889A (en) 2020-01-07
CN110661889B true CN110661889B (en) 2023-06-02

Family

ID=69043016

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911076139.3A Active CN110661889B (en) 2019-11-06 2019-11-06 Push message synchronization and compensation method and system of iOS (integrated operation system) terminal

Country Status (1)

Country Link
CN (1) CN110661889B (en)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111339061B (en) * 2020-02-12 2023-09-26 杭州涂鸦信息技术有限公司 Data migration method and system for distributed database
CN111555965B (en) * 2020-05-11 2022-05-27 南京南瑞信息通信科技有限公司 Message pushing method and system suitable for iOS client
CN113839983A (en) * 2020-06-24 2021-12-24 优信数享(北京)信息技术有限公司 SEM pushing method, system and device
CN111901227A (en) * 2020-07-31 2020-11-06 广东佳米科技有限公司 Simple and lightweight message real-time pushing system and implementation method thereof
CN112468600B (en) * 2021-02-02 2021-04-06 上海有孚智数云创数字科技有限公司 Application message notification method, system and storage medium based on network matrix
CN113407823A (en) * 2021-05-30 2021-09-17 咸宁方片互娱网络有限公司 IOS message pushing method and system
CN113630465B (en) * 2021-08-10 2024-03-12 北京百度网讯科技有限公司 Message processing method, device, equipment and storage medium

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9118689B1 (en) * 2012-04-13 2015-08-25 Zscaler, Inc. Archiving systems and methods for cloud based systems
CN104301203B (en) * 2014-09-10 2016-04-27 腾讯科技(深圳)有限公司 A kind of information push method and equipment
CN107547484B (en) * 2016-06-29 2021-05-07 上海连尚网络科技有限公司 Method, device and system for acquiring and pushing message
CN106878473B (en) * 2017-04-20 2021-03-30 腾讯科技(深圳)有限公司 Message processing method, server cluster and system
CN107087033B (en) * 2017-05-17 2020-05-26 深圳市小牛在线互联网信息咨询有限公司 Message pushing method and device, storage medium and computer equipment
CN109951510A (en) * 2017-12-21 2019-06-28 深圳联友科技有限公司 A kind of information push method and system of application program
CN110401704B (en) * 2019-07-11 2022-04-29 安克创新科技股份有限公司 Message pushing method, device and system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
" 移动终端消息推送机制中关键技术的研究与实现";孙祺;《中国优秀硕士学位论文全文数据库(电子期刊)信息科技辑》;全文 *

Also Published As

Publication number Publication date
CN110661889A (en) 2020-01-07

Similar Documents

Publication Publication Date Title
CN110661889B (en) Push message synchronization and compensation method and system of iOS (integrated operation system) terminal
US9615239B2 (en) Method and apparatus for efficient and deterministic group alerting
AU2002238720B2 (en) Data Storage System
WO2021121370A1 (en) Message loss detection method and apparatus for message queue
US7788382B1 (en) Server initiated synchronization
US8495249B2 (en) Providing sync notifications to client devices
CN101316221B (en) Notification message processing method and equipment
CN102036224B (en) Method, system and upgrading control entity for informing mobile equipment of upgrading software
US7814068B2 (en) Identifying changed records in a file stored on an electronic token
CN103220310B (en) A kind of method exchanged visiting cards and for the terminal exchanged visiting cards, card server
CN102301760A (en) Method and apparatus for tracking device management data changes
KR100728076B1 (en) Method, device and system for synchronizing of data providing for the handling of an interrupted synchronization process
CN100459763C (en) Automatic time setting method for mobile terminal
CN111669717B (en) Cloud mobile phone data sending method, computer device and storage medium
CN111277483A (en) Multi-terminal message synchronization method, server and storage medium
CN102958020B (en) A kind of method, device and equipment of Message Processing
CN103491522A (en) Terminal adaption method and device
CN101325750A (en) Method and apparatus for transmitting short message
CN103581846A (en) User business card updating method and system
GB2373139A (en) A backup system of data stored on a sim card of a mobile telephone
EP3952229A1 (en) Method for sending rcs service message, device, client, and server
US20160112525A1 (en) Distribution control device and method for same, push distribution system, and storage medium
CN112689005A (en) Message sending method and device, storage medium and electronic device
WO2011150968A1 (en) Communication method and device
CN114050986B (en) Signaling tracking method, device, equipment and storage medium

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