Source: https://patents.google.com/patent/US9787789
Timestamp: 2018-03-24 23:55:30
Document Index: 227666872

Matched Legal Cases: ['Application No. 201310016651', 'Application No. 201110009879', 'Application No. 2015', 'application No. 127370724', 'Application No. 2013', 'Application No. 201110009879', 'Application No. 201110009879', 'Application No. 201110009879', 'Application No. 201210147824', 'Application No. 201210147824', 'Application No. 10521154280']

US9787789B2 - Method, device and system for pushing information - Google Patents
US9787789B2
US9787789B2 US14155077 US201414155077A US9787789B2 US 9787789 B2 US9787789 B2 US 9787789B2 US 14155077 US14155077 US 14155077 US 201414155077 A US201414155077 A US 201414155077A US 9787789 B2 US9787789 B2 US 9787789B2
US14155077
US20140201239A1 (en )
This application claims priority to People's Republic of China Patent Application No. 201310016651.5 entitled A METHOD, EQUIPMENT AND SYSTEM FOR PUSHING INFORMATION, filed Jan. 16, 2013 which is incorporated herein by reference for all purposes.
instant messaging Data information (Data information content
identifier and time information)
11111111 www.XYZ.com, Discount information, 05.01-05.03
22222222 www.YYYY.com, Flash sale information, 09:00-19:00
33333333 www.ZZZZ.com
44444444 Merchandise information and picture information
In the event that the search results sent by the instant messaging server include one second instant messaging identifier corresponding to one first instant messaging identifier, the instant messaging server first determines the target database based on the correspondence between the first instant messaging identifier and the target database. The instant messaging server then includes the first instant messaging identifier and the second instant messaging identifier in a query request message and sends the query request message to the corresponding target database.
determining whether a user's instant messaging identifier has a corresponding target database based at least in part on whether there is a stored correspondence between the user's instant messaging identifier and the target database;
in the event that the user's instant messaging identifier does not have the corresponding target database:
sending an additional information request to an instant messaging client associated with the user;
receiving a response message from the instant messaging client, the response message including additional data information and a first instant messaging identifier;
selecting the target database;
sending the included additional data information and the first instant messaging identifier to the selected target database; and
locally storing a correspondence between the first instant messaging identifier and the selected target database;
in the event that the user's instant messaging identifier has the corresponding target database:
sending a query request including the user's instant messaging identifier to the target database; and
receiving a query result from the target database, the query result including data information corresponding to the user's instant messaging identifier;
determining an instant messaging client to push the data information, the determination being based on the user's instant messaging identifier; and
pushing the data information to the determined instant messaging client,
wherein the data information is looked up in the target database based on a stored correspondence between the user's instant messaging identifier and the data information.
in the event that the user's instant messaging identifier is valid:
in the event that the user's instant messaging identifier satisfies the set priority level condition:
in the event that the user's instant messaging identifier does not satisfy the set priority condition:
3. The method as described in claim 2, wherein the determining of the user's instant messaging identifier is the first instant messaging identifier comprises:
determining whether the received first instant messaging identifier has a corresponding target database based on a stored correspondence between the first instant messaging identifier and the target database; and
in the event that the received first instant messaging identifier has the corresponding target database:
sending a query request including the user's first instant messaging identifier to the target database.
5. The method as described in claim 1, wherein the sending of the query request including the user's instant messaging identifier to the target database includes:
6. The method as described in claim 2, wherein the determining of the user's instant messaging identifier is the second instant messaging identifier comprises:
in the event that the user's second instant messaging identifier does not have a corresponding first instant messaging identifier, permitting the user to login.
7. The method as described in claim 6, wherein the determining of whether the user's second instant messaging identifier has the corresponding first instant messaging identifier comprises:
in the event that the user's second instant messaging identifier has a first instant messaging identifier:
in the event that the attribute information of the first instant messaging identifier corresponding to the user's second instant messaging identifier is the information publishing group:
in the event that the attribute information of the first instant messaging identifier corresponding to the user's second instant messaging identifier is not the information publishing group:
8. The method as described in claim 7, wherein the receiving of the query result including the data information corresponding to the user's instant messaging identifier from the target database comprises:
9. The method as described in claim 1, wherein the instant messaging client associated with the user acquires the additional data information based on generating the response message to include merchandise information to be published by the user and the first instant message identifier, and returning the response message.
10. A method for pushing information, comprising:
determining whether a user's first instant messaging identifier has a corresponding target database based at least in part on whether there is a stored correspondence between the user's first instant messaging identifier and the target database;
in the event that the user's first instant messaging identifier has the corresponding target database:
receiving a query result from the target database, the query result including data information corresponding to the user's first instant messaging identifier;
determining an instant messaging client to push information, the determination being based on the first instant messaging identifier; and
wherein the data information is looked up in the target database according to a stored correspondence between the user's first instant messaging identifier and the data information.
in the event that the user's first instant messaging identifier satisfies the set priority level condition:
12. The method as described in claim 11, wherein the determining of whether the user's first instant messaging identifier satisfies the set priority level condition comprises:
determining whether the user's first instant messaging identifier has a corresponding target database based on the stored correspondence between the first instant messaging identifier and the target database;
in the event that the received first instant messaging identifier does not have the corresponding target database:
sending the request to the user to request the data information.
14. The method as described in claim 10, wherein the sending of the query request including the user's first instant messaging identifier to the target database comprises:
15. A method for pushing information, comprising:
sending a query request including a user's second instant messaging identifier and the user's first instant messaging identifier to a target database, wherein a correspondence between the user's second instant messaging identifier and the user's first instant messaging identifier exists; and
receiving a query result sent by the target database, the query result including the user's second instant messaging identifier and data information corresponding to the user's first instant messaging identifier;
determining an instant messaging client to push information, the determination being based on the user's second instant messaging identifier; and
pushing the data information corresponding to the first instant messaging identifier to the determined instant messaging client,
wherein the data information is looked up in the target database based on a stored correspondence between the first instant messaging identifier and the data information.
determining whether the user's second instant messaging identifier has a corresponding first instant messaging identifier based on the stored correspondence between the first instant messaging identifier and the second instant messaging identifier;
in the event that the user's second instant messaging identifier does not have the corresponding first instant messaging identifier:
17. The method as described in claim 16, wherein the determining of whether the user's second instant messaging identifier has a corresponding first instant messaging identifier comprises:
in the event that the user's second instant messaging identifier has the corresponding first instant messaging identifier:
18. The method as described in claim 17, wherein the receiving of the query result including the data information corresponding to the user's instant messaging identifier comprises:
19. A method for querying information, comprising:
determining, by an instant messaging server, whether a user's instant messaging identifier has a corresponding target database based at least in part on whether there is a stored correspondence between the user's instant messaging identifier and data information;
in the event that the instant messaging server has the stored correspondence between the user's instant messaging identifier and the data information:
receiving a query request sent by the instant messaging server, the query request including the user's instant messaging identifier;
looking up data information corresponding to the user's instant messaging identifier based on a stored correspondence between the user's instant messaging identifier and the data information; and
sending a query result including the looked up data information and the user's instant messaging identifier to the instant messaging server.
21. An instant messaging server for pushing information, comprising:
determine whether a user's instant messaging identifier has a corresponding target database based at least in part on whether there is a stored correspondence between a first instant messaging identifier and the target database;
send an additional information request to an instant messaging client associated with the user;
receive a response message from the instant messaging client, the response message including additional data information and a first instant messaging identifier;
select the target database;
send the included additional data information and the first instant messaging identifier to the selected target database; and
locally store a correspondence between the first instant messaging identifier and the selected target database;
send a query request including a user's instant messaging identifier to the target database; and
receive a query result including data information corresponding to the user's instant messaging identifier;
determine the instant messaging client to push information based on the user's instant messaging identifier; and
push the data information to the determined instant messaging client, wherein the data information is looked up in the target database based on a stored correspondence between the user's instant messaging identifier and the data information; and
22. A system for pushing information, comprising:
send a query request including an instant messaging identifier of a user to the target database; and
receive a query result containing data information corresponding to the user's instant messaging identifier sent by the target database;
determine the instant messaging client to push information, the determination being based on the user's instant messaging identifier; and
push the data information to the determined instant messaging client; and
23. A computer program product for pushing information, the computer program product being embodied in a tangible non-transitory computer readable storage medium and comprising computer instructions for:
determining whether a user's instant messaging identifier has a corresponding target database based at least in part on whether there is a stored correspondence between a first instant messaging identifier and the target database;
sending a query request including a user's instant messaging identifier to the target database; and
receiving a query result including data information corresponding to the user's instant messaging identifier from the target database;
US14155077 2013-01-16 2014-01-14 Method, device and system for pushing information Active 2035-03-31 US9787789B2 (en)
CN 201310016651 CN103929350A (en) 2013-01-16 2013-01-16 Information pushing method, device and system
EP20140703982 EP2946532A1 (en) 2013-01-16 2014-01-15 Method, device and system for pushing information
PCT/US2014/011691 WO2014113476A1 (en) 2013-01-16 2014-01-15 Method, device and system for pushing information
JP2015552679A JP6085691B2 (en) 2013-01-16 2014-01-15 The method for pushing information, device, and system
US20140201239A1 true US20140201239A1 (en) 2014-07-17
US9787789B2 true US9787789B2 (en) 2017-10-10
US14155077 Active 2035-03-31 US9787789B2 (en) 2013-01-16 2014-01-14 Method, device and system for pushing information
US (1) US9787789B2 (en)
CN (1) CN103929350A (en)
WO2004061611A2 (en) 2002-12-31 2004-07-22 America Online, Inc. Implicit access for communications pathway
US20070006027A1 (en) 2005-07-01 2007-01-04 Imiogic, Inc. Methods and systems for detecting and preventing the spread of malware on instant messaging (IM) networks by analyzing message traffic patterns
US20070204063A1 (en) 2003-01-16 2007-08-30 Scott Banister Electronic message delivery using a virtual gateway approach
CN101047662A (en) 2006-04-20 2007-10-03 华为技术有限公司 Method and system for implementing multi-identity immediate message communication and present service of single account number
US20070254683A1 (en) 2006-04-27 2007-11-01 Guo Chang Jie Method and apparatus for filtering short message system spam
US20080004048A1 (en) 2006-06-29 2008-01-03 Lucent Technologies Inc. Map message processing for sms spam filtering
US20080037755A1 (en) 2006-08-11 2008-02-14 Bellsouth Intellectual Property Corporation Personal Directory Services with Directed Communication
JP2008171315A (en) 2007-01-15 2008-07-24 Rakuten Inc Message transmission/reception system, information providing device, information providing method, terminal equipment, information provision processing program and terminal processing program
CN101247406A (en) 2007-08-30 2008-08-20 飞塔信息科技（北京）有限公司 Junk e-mail checking system and local information classification method using global information
WO2009086765A1 (en) 2007-12-29 2009-07-16 Tencent Technology (Shenzhen) Company Limited Group information conversion device, method and group information interaction system
CN101534261A (en) 2009-04-10 2009-09-16 阿里巴巴集团控股有限公司 A method, device and system of recognizing spam information
US20090305678A1 (en) 2008-06-06 2009-12-10 Kabushiki Kaisha Toshiba Communication apparatus
US20100050095A1 (en) 2008-08-21 2010-02-25 Huawei Technologies Co., Ltd. Method, system and apparatus for displaying an instant message
US20100274843A1 (en) 2007-09-12 2010-10-28 Tencent Technology (Shenzhen) Company Limited Instant Messaging Method And System
CN102325172A (en) 2011-08-30 2012-01-18 中兴通讯股份有限公司 Method for sharing data among mobile terminals, system and control server
CN102347848A (en) 2011-09-26 2012-02-08 深圳中兴网信科技有限公司 Method and system for sending bulk message
US20120226561A1 (en) 2011-03-02 2012-09-06 Richard Sinn Aggregated Contextual Targeting Advertisements Using Instant Messaging Clients
US20120265831A1 (en) 2011-01-17 2012-10-18 Alibaba Group Holding Limited System and Method for Transmitting and Filtering Instant Messaging Information
CN102761496A (en) 2011-04-29 2012-10-31 阿里巴巴集团控股有限公司 Community information issuing method, device and system for network communities
US20130073588A1 (en) 2010-08-05 2013-03-21 Tencent Technology (Shenzhen) Company Limited Method and system for information query
US20140201239A1 (en) * 2013-01-16 2014-07-17 Alibaba Group Holding Limited Method, device and system for pushing information
US20150271012A1 (en) 2008-06-06 2015-09-24 Alibaba Group Holding Limited Promulgating information on websites using servers
JP2009294986A (en) 2008-06-06 2009-12-17 Toshiba Corp Communication terminal
Chinese Office Action for Chinese Application No. 201110009879.2, mailed on Oct. 27, 2015 (7 pages).
English translation of Office Action issued in Japanese Application No. 2015-552679, dated Aug. 9, 2016, 19 pages.
Extended European Search Report dated Jan. 13, 2017 for European patent application No. 127370724.4, 5 pages.
Japanese Office Action mailed Nov. 4, 2015 for Japanese Application No. 2013-549590, a counterpart foreign application of U.S. Appl. No. 13/518,129 (7 pages).
PCT Search Report and Written Opionion dated May 21, 2014 for PCT application No. PCT/US2014/011691, 10 pages.
The Chinese Office Action mailed Apr. 24, 2015, for Chinese Patent Application No. 201110009879.2, foreign priority application of U.S. Appl. No. 13/518,129, 6 pages.
The Chinese Office Action mailed Feb. 7, 2014, for Chinese Patent Application No. 201110009879.2, foreign priority application of U.S. Appl. No. 13/518,129, 9 pages.
The Chinese Office Action mailed Oct. 17, 2014, for Chinese Patent Application No. 201110009879.2, foreign priority application of U.S. Appl. No. 13/518,129, 9 pages.
The PCT Search Report mailed Apr. 26, 2012 for PCT application No. PCT/US12/21326, 6 pages.
Translated Chinese Office Action dated May 11, 2016, for Chinese Patent Application No. 201210147824.2, foreign priority application of U.S. Appl. No. 13/518,129, 7 pages.
Translated Chinese Office Action dated Nov. 4, 2015, for Chinese Patent Application No. 201210147824.2, foreign priority application of U.S. Appl. No. 13/518,129, 9 pages.
Translated Taiwanese Office Action dated Sep. 19, 2016, for Taiwan Patent Application No. 10521154280, foreign application related to U.S. Appl. No. 14/155,077, 11 pages.
US20140201239A1 (en) 2014-07-17 application
JP6085691B2 (en) 2017-02-22 grant
CN103929350A (en) 2014-07-16 application
EP2946532A1 (en) 2015-11-25 application
WO2014113476A1 (en) 2014-07-24 application
JP2016510457A (en) 2016-04-07 application
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LIU, JILI;REEL/FRAME:032305/0653