CN107135258B - Message pushing method and server - Google Patents

Message pushing method and server Download PDF

Info

Publication number
CN107135258B
CN107135258B CN201710306803.3A CN201710306803A CN107135258B CN 107135258 B CN107135258 B CN 107135258B CN 201710306803 A CN201710306803 A CN 201710306803A CN 107135258 B CN107135258 B CN 107135258B
Authority
CN
China
Prior art keywords
message
list
user terminal
server
updated
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
CN201710306803.3A
Other languages
Chinese (zh)
Other versions
CN107135258A (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.)
Zhejiang Shulian Technology Co ltd
Original Assignee
Zhejiang Shulian 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 Zhejiang Shulian Technology Co ltd filed Critical Zhejiang Shulian Technology Co ltd
Priority to CN201710306803.3A priority Critical patent/CN107135258B/en
Publication of CN107135258A publication Critical patent/CN107135258A/en
Application granted granted Critical
Publication of CN107135258B publication Critical patent/CN107135258B/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/14Session management
    • H04L67/146Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • 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

Abstract

The embodiment of the invention provides a message pushing method and a server. The method is applied to a server which is in communication connection with the user terminal, the server comprises a first message ID list, and the method further comprises the following steps: the server acquires the message and updates the first message ID list so as to store the ID corresponding to the message in the first message ID list; and the server sends the updated first message ID list to the user terminal. Through ID pushing of the message, processing of the server on data is reduced, the performance of the server is improved in a phase-changing mode, and waste of server resources is reduced.

Description

Message pushing method and server
Technical Field
The present invention relates to the field of information transmission, and in particular, to a method and a server for pushing a message.
Background
With the rapid development of the internet in recent years, a large amount of data is generated in the world where we live every day, and the data growth rate is almost a terrorist affair. In the message push scenario, a large number of clients frequently encountered subscribe to the same message type, and all users can receive the message. The common processing mode of such a scenario is that each user space stores one piece of push data, which results in a phenomenon of a large amount of wasted storage space and performance consumption, and each user needs to store and go through one time, which is an extreme waste to the performance of the server.
How to solve the above problems is a problem to be solved.
Disclosure of Invention
The invention aims to provide a message pushing method and a server.
In order to achieve the above purpose, the embodiment of the present invention adopts the following technical solutions:
the embodiment of the invention provides a message pushing method, which is applied to a server in communication connection with a user terminal, wherein the server comprises a first message ID list, and the method comprises the following steps:
the server acquires a message and updates the first message ID list so as to store an ID corresponding to the message in the first message ID list;
and the server sends the updated first message ID list to the user terminal.
The embodiment of the invention also provides a message pushing method, which is applied to a user terminal in communication connection with a server, wherein the user terminal comprises a second message ID list, and the method comprises the following steps:
the user terminal receives a first message ID list;
the user terminal compares the first message ID list with the second message ID list, and updates the second message ID list based on the first message ID list;
and the user terminal downloads the message according to the ID in the updated second message ID list.
The embodiment of the invention also provides a message pushing method, which is applied to a server and a user terminal which are in communication connection with each other, wherein the server comprises a first message ID list, the user terminal comprises a second message ID list, and the method comprises the following steps:
the server acquires a message and updates the first message ID list so as to store an ID corresponding to the message in the first message ID list;
the server sends the updated first message ID list to the user terminal;
the user terminal compares the updated first message ID list with the second message ID list, and updates the second message ID list based on the updated first message ID list;
and the user terminal downloads according to the ID in the updated second message ID list.
The embodiment of the invention also provides a server, which is applied to a server and a user terminal which are mutually connected in a communication way, wherein the server comprises a first message ID list, the user terminal comprises a second message ID list, and the method comprises the following steps:
the server acquires a message and updates the first message ID list so as to store an ID corresponding to the message in the first message ID list;
the server sends the updated first message ID list to the user terminal;
the user terminal compares the updated first message ID list with the second message ID list, and updates the second message ID list based on the updated first message ID list;
and the user terminal downloads according to the ID in the updated second message ID list.
Compared with the prior art, the invention has the following beneficial effects:
the embodiment of the invention provides a message pushing method, which is applied to a server in communication connection with a user terminal, wherein the server comprises a first message ID list, and the method also comprises the following steps: the server acquires a message and updates the first message ID list so as to store an ID corresponding to the message in the first message ID list; and the server sends the updated first message ID list to the user terminal. Through ID pushing of the message, processing of the server on data is reduced, the performance of the server is improved in a phase-changing mode, and waste of server resources is reduced.
In order to make the aforementioned and other objects, features and advantages of the present invention comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, 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, but not all, embodiments of the present invention. The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present invention, presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the 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.
Fig. 1 illustrates a message pushing method and an application environment of a server provided by an embodiment of the present invention.
Fig. 2 is a block diagram of a user terminal according to an embodiment of the present invention.
Fig. 3 is a schematic diagram of an apparatus applied to a server in the method for pushing a message shown in fig. 1 according to a first embodiment of the present invention.
Fig. 4 is a flowchart illustrating a server applied to the method for pushing a message shown in fig. 1 according to a second embodiment of the present invention.
Fig. 5 is a schematic diagram of an apparatus applied to a user terminal in the method for pushing a message shown in fig. 1 according to a third embodiment of the present invention.
Fig. 6 is a flowchart illustrating a user terminal applied to the method for pushing a message shown in fig. 1 according to a fourth embodiment of the present invention.
Fig. 7 is a schematic diagram illustrating an apparatus applied to a user terminal and a server in the method for pushing a message shown in fig. 1 according to a fifth embodiment of the present invention.
Fig. 8 is a flowchart illustrating a user terminal and a server according to a sixth embodiment of the present invention, where the method is applied to the message pushing method shown in fig. 1.
Icon: 100-a server; 101-an update module; 102-a confirmation module; 103-a deletion module; 104-a sending module; 200-a user terminal; 210-a memory; 220-a storage controller; 230-a processor; 240-radio frequency module; 250-peripheral interfaces; 400-a message push device; 401-a receiving module; 402-a corresponding update module; 403-add module; 404-a cancellation module; 405-a download module; 300-wired or wireless network.
Detailed Description
The message pushing method and the server provided by the embodiment of the invention can be applied to the application environment shown in fig. 1. As shown in fig. 1, the user terminal 200 and the server 100 are located in a wired or wireless network 300, and the user terminal 200 performs data interaction with the server 100 through the wired or wireless network 300.
In the embodiment of the present invention, the user terminals 200 are differentiated according to different users, in the embodiment, they may be terminal devices with the same hardware configuration, and in the embodiment, the user terminals 200 may include smart phones, tablet computers, e-book readers, laptop portable computers, vehicle-mounted computers, wearable mobile terminals, and the like.
Please refer to fig. 2, which is a block diagram illustrating a ue 200 according to an embodiment of the present invention. The user terminal 200 may include a message pushing apparatus 400, a memory 210, a storage controller 220, a processor 230, a peripheral interface 250, and a radio frequency module 240.
The memory 210, the memory controller 220, the processor 230, the peripheral interface 250, and the rf module 240 are electrically connected to each other directly or indirectly to realize data transmission or interaction. For example, the components may be electrically connected to each other via one or more communication buses or signal lines. The message pushing apparatus 400 may include at least one software module, which may be stored in the memory 210 in the form of software or firmware or solidified in the operating system of the first user terminal 200, such as a software function module and a computer program included in the message pushing apparatus 400.
The Memory 210 may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Read-Only Memory (EPROM), an electrically Erasable Read-Only Memory (EEPROM), and the like. The memory 210 is used for storing programs, and the processor 230 executes the programs after receiving the execution instructions. Access to the memory 210 by the processor 230, and possibly other components, may be under the control of the memory controller 220.
Processor 230 may be an integrated circuit chip having signal processing capabilities. The processor 230 may be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The various methods, steps and logic blocks disclosed in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
Peripheral interface 250 couples various input/output devices to processor 230 and memory 210 in some embodiments, peripheral interface 250, processor 230, and memory controller 220 may be implemented in a single chip, in other embodiments, they may be implemented separately by separate chips.
The rf module 240 is configured to establish a communication connection between the user terminal 200 and the server 100 through the wired network or the wireless network 300, so as to implement data transmission between the user terminal 200 and the server 100.
It will be appreciated that the configuration shown in fig. 2 is merely illustrative and that user terminal 200 may also include more or fewer components than shown in fig. 2 or have a different configuration than shown in fig. 2. The components shown in fig. 2 may be implemented in hardware, software, or a combination thereof.
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 only a part of the embodiments of the present invention, and not all of the embodiments. The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present invention, presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present invention without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present invention, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.
First embodiment
Referring to fig. 3, a schematic diagram of a server 100 according to a first embodiment of the present invention applied to the method for pushing a message shown in fig. 1 is shown, where the apparatus includes an updating module 101, a confirming module 102, a deleting module 103, and a sending module 104, and the server 100 stores a first message ID list.
The updating module 101 is configured to acquire a message and update the first message ID list to store an ID corresponding to the message in the first message ID list.
The server 100 acquires the message, stores the message in the server 100, updates the first message ID list according to the ID of the message, and stores the ID corresponding to the message in the first message ID list.
The confirmation module 102 is configured to compare the ID with an ID in the first message ID list, and if the ID is not found in the first message ID list, add the ID to the first message ID list to update the first message ID list.
The server 100 compares the ID of the message to be updated with the ID in the first message ID list, and if there is no message ID to be updated in the first message ID list, adds the ID to the first message ID list, thereby completing the update of the first message ID list.
And the deleting module 103 records the recording time when the ID is stored in the first message ID list, compares the recording time with the local time, and deletes the ID from the first message ID list if the interval between the recording time and the local time reaches the preset time.
The server 100 adds the ID to the recording time of the first message ID list, compares the recording time with the local time, and deletes the ID from the first message ID list when the interval between the recording time and the local time reaches a preset time, thereby completing an automatic deletion function of the expired message.
The sending module 104 sends the updated first message ID list to the user terminal 200.
The server 100 sends the updated first message ID list to the user terminal 200, and completes the push of the message.
Second embodiment
Referring to fig. 4, a flowchart of a server 100 applied to the method for pushing a message shown in fig. 1 according to a second embodiment of the present invention is shown, where the method is applied to the server 100 communicatively connected to a user terminal 200, and the server 100 includes a first message ID list, including the following steps:
s101: the server 100 acquires the message, and updates the first message ID list to store the ID corresponding to the message in the first message ID list.
The server 100 acquires the message, stores the message in the server 100, updates the first message ID list according to the ID of the message, and stores the ID corresponding to the message in the first message ID list.
S102: the server 100 compares the ID with the ID in the first message ID list, and if the ID is not found in the first message ID list, adds the ID to the first message ID list to update the first message ID list.
The server 100 compares the ID of the message to be updated with the ID in the first message ID list, and if there is no message ID to be updated in the first message ID list, adds the ID to the first message ID list, thereby completing the update of the first message ID list.
S103: the server 100 compares the ID with the ID in the first message ID list, and if the ID is not found in the first message ID list, adds 1ID to the first message ID list to update the first message ID list.
The server 100 adds the ID to the recording time of the first message ID list, compares the recording time with the local time, and deletes the ID from the first message ID list when the interval between the recording time and the local time reaches a preset time, thereby completing an automatic deletion function of the expired message.
S104: the server 100 transmits the updated first message ID list to the user terminal 200.
The server 100 sends the updated first message ID list to the user terminal 200, and completes the push of the message.
Third embodiment
Referring to fig. 5, a schematic diagram of an apparatus applied to the user terminal 200 in the message pushing method shown in fig. 1 according to a third embodiment of the present invention is shown, where the apparatus includes a receiving module 401, a corresponding updating module 402, an adding module 403, a removing module 404, and a downloading module 405, and the user terminal 200 includes a second message ID list.
The receiving module 401 receives the first message ID list by the user terminal 200.
The user terminal 200 receives the first message ID list sent by the server 100, and pushes the pushed message by means of ID.
In response to the update module 402, the user terminal 200 compares the first message ID list with the second message ID list, and updates the second message ID list based on the first message ID list.
The ue 200 compares the first message ID list with the second message ID list, and updates the second message ID list according to the IDs in the first message ID list.
The adding module 403, the user terminal 200 compares the first message ID list with the second message ID list, and adds the ID different from the first message ID list and the second message ID list to the second message ID list.
The user terminal 200 adds an ID that is present in the first message ID list but not present in the second message ID list. The updating of the second message ID list is completed.
The eliminating module 404, the user terminal 200 further compares the second message ID list with the first message ID list, and deletes the ID different from the first message ID list from the second message ID list.
The user terminal 200 deletes the ID that is present in the second message ID list but not present in the first message ID list, thereby completing the update of the second message ID list, reducing the memory usage of the user terminal 200, and improving the performance of the user terminal 200.
And the downloading module 405, the user terminal 200 downloads the message according to the ID in the updated second message ID list.
And the user terminal 200 downloads the IDs in the second message ID list from the server 100, and finishes message pushing.
Fourth embodiment
Referring to fig. 6, it is a flowchart of a user terminal 200 applied to the method for pushing a message shown in fig. 1 according to a fourth embodiment of the present invention, where the method is applied to the user terminal 200 communicatively connected to the server 100, and the user terminal 200 includes a second message ID list, including the following steps:
s401: the user terminal 200 receives the first message ID list.
The user terminal 200 receives the first message ID list sent by the server 100, and pushes the pushed message by means of ID.
S402: the user terminal 200 compares the first message ID list with the second message ID list, and updates the second message I D list based on the first message I D list.
The ue 200 compares the first message ID list with the second message ID list, and updates the second message ID list according to the IDs in the first message ID list.
S403: the user terminal 200 compares the first message ID list with the second message ID list, and adds an ID different from the first message ID list and the second message ID list to the second message ID list.
The user terminal 200 adds an ID that is present in the first message ID list but not present in the second message ID list. The updating of the second message ID list is completed.
S404: the user terminal 200 also compares the second message ID list with the first message ID list, and deletes an ID different from the first message ID list from the second message ID list.
The user terminal 200 deletes the ID that is present in the second message ID list but not present in the first message ID list, thereby completing the update of the second message ID list, reducing the memory usage of the user terminal 200, and improving the performance of the user terminal 200.
S405: and the user terminal 200 downloads the message according to the ID in the updated second message ID list.
And the user terminal 200 downloads the IDs in the second message ID list from the server 100, and finishes message pushing.
Fifth embodiment
Referring to fig. 7, a schematic diagram of an apparatus applied to a user terminal 200 and a server 100 in the method for pushing a message shown in fig. 1 according to a fifth embodiment of the present invention is shown, where the apparatus includes an updating module 101, a confirming module 102, a deleting module 103, and a sending module 104.
The updating module 101 is configured to acquire a message and update the first message ID list to store an ID corresponding to the message in the first message ID list.
The server 100 acquires the message, stores the message in the server 100, updates the first message ID list according to the ID of the message, and stores the ID corresponding to the message in the first message ID list.
The sending module 104 sends the updated first message ID list to the user terminal 200.
The server 100 sends the updated first message ID list to the user terminal 200, and completes the push of the message.
In response to the update module 402, the user terminal 200 compares the first message ID list with the second message ID list, and updates the second message ID list based on the first message ID list.
The ue 200 compares the first message ID list with the second message ID list, and updates the second message ID list according to the IDs in the first message ID list.
And the downloading module 405, the user terminal 200 downloads the message according to the ID in the updated second message ID list.
And the user terminal 200 downloads the IDs in the second message ID list from the server 100, and finishes message pushing.
Sixth embodiment
Referring to fig. 8, it is a flowchart of a sixth embodiment of the present invention applied to a user terminal 200 and a server 100 in a method for pushing messages shown in fig. 1, where the method is applied to the server 100 and the user terminal 200 that are communicatively connected to each other, the server 100 includes a first message ID list, and the user terminal 200 includes a second message ID list, including the following steps:
s501: the server 100 acquires the message, and updates the first message ID list to store the ID corresponding to the message in the first message ID list.
The server 100 acquires the message, stores the message in the server 100, updates the first message ID list according to the ID of the message, and stores the ID corresponding to the message in the first message ID list.
S502: the server 100 transmits the updated first message ID list to the user terminal 200.
The server 100 sends the updated first message ID list to the user terminal 200, and completes the push of the message.
S503: the user terminal 200 compares the updated first message ID list with the second message ID list, and updates the second message I D list based on the updated first message I D list.
The ue 200 compares the first message ID list with the second message ID list, and updates the second message ID list according to the IDs in the first message ID list.
S504: the user terminal 200 downloads according to the ID in the updated second message ID list.
And the user terminal 200 downloads the IDs in the second message ID list from the server 100, and finishes message pushing.
In summary, the present invention provides a method for pushing a message and a server. The method is applied to a server which is in communication connection with the user terminal, the server comprises a first message ID list, and the method further comprises the following steps: the server acquires the message and updates the first message ID list so as to store the ID corresponding to the message in the first message ID list; and the server sends the updated first message ID list to the user terminal. Through ID pushing of the message, processing of the server on data is reduced, the performance of the server is improved in a phase-changing mode, and waste of server resources is reduced.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a unit, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, each functional unit in the embodiments of the present invention may be integrated together to form an independent part, or each unit may exist separately, or two or more units may be integrated to form an independent part.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.

Claims (3)

1. A message pushing method applied to a user terminal in communication connection with a server, wherein the user terminal includes a second message ID list, the method comprising:
the user terminal receives a first message ID list;
the user terminal compares the first message ID list with the second message ID list, and updates the second message ID list based on the first message ID list;
the user terminal downloads the message according to the ID in the updated second message ID list;
the step of comparing, by the user terminal, the first message ID list with the second message ID list, and updating the second message ID list based on the first message ID list further includes:
and the user terminal also compares the second message ID list with the first message ID list and deletes the ID of the second message ID list different from the ID of the first message ID list from the second message ID list.
2. The method of message pushing according to claim 1, wherein the user terminal compares the first message ID list with the second message ID list, and the step of updating the second message ID list based on the first message ID list further comprises:
and the user terminal compares the first message ID list with the second message ID list and adds the IDs, different from the first message ID list and the second message ID list, of the first message ID list to the second message ID list.
3. A message pushing method is applied to a server and a user terminal which are in communication connection with each other, wherein the server comprises a first message ID list, and the user terminal comprises a second message ID list, and the method further comprises the following steps:
the server acquires a message and updates the first message ID list so as to store an ID corresponding to the message in the first message ID list;
the server sends the updated first message ID list to the user terminal;
the user terminal compares the updated first message ID list with the second message ID list, and updates the second message ID list based on the updated first message ID list;
the user terminal downloads according to the ID in the updated second message ID list;
the step of the server obtaining the message and updating the first message ID list to store the ID corresponding to the message in the first message ID list further includes:
the server records the recording time when the ID is stored in the first message ID list, compares the recording time with local time, and deletes the ID from the first message ID list if the interval between the recording time and the local time exceeds preset time;
the step of comparing, by the user terminal, the first message ID list with the second message ID list, and updating the second message ID list based on the first message ID list further includes:
and the user terminal also compares the second message ID list with the first message ID list and deletes the ID of the second message ID list different from the ID of the first message ID list from the second message ID list.
CN201710306803.3A 2017-05-04 2017-05-04 Message pushing method and server Active CN107135258B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710306803.3A CN107135258B (en) 2017-05-04 2017-05-04 Message pushing method and server

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710306803.3A CN107135258B (en) 2017-05-04 2017-05-04 Message pushing method and server

Publications (2)

Publication Number Publication Date
CN107135258A CN107135258A (en) 2017-09-05
CN107135258B true CN107135258B (en) 2020-09-18

Family

ID=59716457

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710306803.3A Active CN107135258B (en) 2017-05-04 2017-05-04 Message pushing method and server

Country Status (1)

Country Link
CN (1) CN107135258B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110324377B (en) * 2018-03-30 2022-03-25 武汉斗鱼网络科技有限公司 Push interaction method and device, electronic equipment and medium
CN114070563B (en) * 2020-07-31 2023-09-05 中移(苏州)软件技术有限公司 Data processing method, device, terminal and storage medium

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101795290A (en) * 2009-05-27 2010-08-04 深圳市朗科科技股份有限公司 Network content pushing method and network content pushing device
CN102811131A (en) * 2011-05-30 2012-12-05 国民技术股份有限公司 Information pushing method and system
CN103023750A (en) * 2012-08-01 2013-04-03 福建星网视易信息系统有限公司 Method for getting message by terminal
EP2916233A1 (en) * 2012-10-31 2015-09-09 Warld Limited Content distribution system, program and content distribution method
CN105099894A (en) * 2015-08-28 2015-11-25 广州酷狗计算机科技有限公司 Message pushing method, device and system
CN106161593A (en) * 2016-06-21 2016-11-23 北京奇虎科技有限公司 MESSAGE POLL method and server, communication system
CN106453382A (en) * 2016-10-28 2017-02-22 努比亚技术有限公司 Message pushing method and device

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104601736B (en) * 2013-10-30 2018-10-23 腾讯科技(深圳)有限公司 A kind of implementation method and device of short URL services

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101795290A (en) * 2009-05-27 2010-08-04 深圳市朗科科技股份有限公司 Network content pushing method and network content pushing device
CN102811131A (en) * 2011-05-30 2012-12-05 国民技术股份有限公司 Information pushing method and system
CN103023750A (en) * 2012-08-01 2013-04-03 福建星网视易信息系统有限公司 Method for getting message by terminal
EP2916233A1 (en) * 2012-10-31 2015-09-09 Warld Limited Content distribution system, program and content distribution method
CN105099894A (en) * 2015-08-28 2015-11-25 广州酷狗计算机科技有限公司 Message pushing method, device and system
CN106161593A (en) * 2016-06-21 2016-11-23 北京奇虎科技有限公司 MESSAGE POLL method and server, communication system
CN106453382A (en) * 2016-10-28 2017-02-22 努比亚技术有限公司 Message pushing method and device

Also Published As

Publication number Publication date
CN107135258A (en) 2017-09-05

Similar Documents

Publication Publication Date Title
CN110086877B (en) Application program sharing and information sharing display method, device, equipment and medium
KR101871383B1 (en) Method and system for using a recursive event listener on a node in hierarchical data structure
CN110427551B (en) Information pushing method and device, electronic equipment and computer readable medium
US20160028832A1 (en) Methods and systems for efficient discovery of devices in a peer-to-peer network
CN106790350B (en) Information pushing device, server and method
CN107135258B (en) Message pushing method and server
CN107864044B (en) Information processing method and device, terminal and readable storage medium
US10938773B2 (en) Method and apparatus for synchronizing contact information and medium
CN114785685A (en) Software differential upgrading method and device, electronic equipment and readable storage medium
EP2483878B1 (en) Method for using recording rules and previous value selection rules for presence information in a communications system
WO2015179480A1 (en) Method and systems for synchronizing contact information
CN111694703A (en) Cache region management method and device and computer equipment
CN108989072B (en) Method and device for deploying, managing and calling assembly
CN107852598B (en) Circumventing wireless device spatial tracking based on wireless device identifiers
CN111723007B (en) Test case merging method, system, equipment and medium
CN110688070B (en) Management method and device for solid state disk data table, storage medium and electronic equipment
CN113434525A (en) Cache data updating method and device, storage medium and electronic device
CN113779048A (en) Data processing method and device
CN107209882B (en) Multi-stage de-registration for managed devices
EP2530585A1 (en) Method of handling periodic update of software component and related communication device
CN113612676B (en) Social group message synchronization method, device, equipment and storage medium
TWI531910B (en) Data management method, computer program product and managing server
CN111666484B (en) Content pushing method, pushing device and computer readable storage medium
CN115665074B (en) Message flow-limiting sending method, device, equipment and storage medium
CN110858201A (en) Data processing method and system, processor 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
CB02 Change of applicant information

Address after: 310000 Ning Ning street, Xiaoshan District, Hangzhou, Zhejiang

Applicant after: Zhejiang number Chain Technology Co., Ltd.

Address before: 310000 Ning Ning street, Xiaoshan District, Hangzhou, Zhejiang

Applicant before: Zhejiang Lugang communication technology Limited

CB02 Change of applicant information
GR01 Patent grant
GR01 Patent grant