METHOD FOR SUBSCRIBING TO NOTIFICATION, APPARATUS AND SYSTEM

• US 20130246504A1
• Filed: 09/07/2012
• Published: 09/19/2013
• Est. Priority Date: 09/09/2011
• Status: Abandoned Application

• Current Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: HU, Lixin, LI, Dexu
• Application Number:
  US13/606,890
• Publication Number:
  US 20130246504A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 67/55 Push-based network services

Abstract

The present invention discloses a method for subscribing to a notification by a user terminal, an apparatus and a system. The user terminal includes a client, and the user terminal communicates with a website and a notification server via a network. The method includes the following steps: A browser obtains a webpage from the website, and presents the webpage; and the browser triggers, according to an event of the webpage, that the client sends a registration request to the notification server, where a registration request message includes a website identifier, so that the notification server pushes a notification of the website to the user terminal.

Claims

1. A method for subscribing to a notification by a user terminal, wherein the user terminal comprises a browser and a client, and the user terminal communicates with a website and a notification server via a network, and the method comprises:

obtaining, by the browser, a webpage from the website, and presenting the webpage;

generating, by the browser, a trigger event according to text content of the webpage; and

sending, by the client, a registration request to the notification server according to the trigger event, wherein the registration request comprises a website identifier of the website, so that the notification server pushes a notification of the website to the user terminal.

2. The method according to claim 1, comprising:

sending, by the notification server and according to the registration request, a permission message comprising a receiver identifier to the website.

3. The method according to claim 1, comprising:

sending, by the notification server, a registration response message to the client according to the registration request, and forwarding, by the client, the permission message comprising the receiver identifier to the website.

4. The method according to claim 3, wherein the step of forwarding, by the client, the permission message to the website comprises:

sending, by the client, the permission message to the browser, and forwarding, by the browser, the permission message to the website.

5. The method according to claims 1, comprising:

sending, by the website, a notification push request to the notification server.

6. The method according to claim 5, wherein the permission message comprises a notification server identifier, and the method comprises:

sending, by the website, a website registration request to the notification server, wherein the website registration request comprises the website identifier;

receiving, by the website, a registration response of the notification server, wherein the response comprises a login authentication key generated by the notification server;

saving, by the website, a received login authentication key and a corresponding notification server identifier, wherein when the website sends the notification push request to the notification server, the request comprises the login authentication key; and

authenticating, by the notification server, the website by comparing a login authentication key in a registration record with a received key.

7. The method according to claim 5, wherein the permission message comprises the receiver identifier, and the notification push request comprises the receiver identifier;

and the method comprises;

searching, by the notification server and according to the website identifier and the receiver identifier, for a terminal identifier corresponding to the website identifier and the receiver identifier, and pushing notification content to the terminal according to the terminal identifier.

8. A user terminal, comprising a browser and a client, wherein

the browser communicates with a website via a network, and the browser obtains a webpage from the website, presents the webpage, and generates a trigger event according to text content of the webpage;

the client uses a terminal identifier to establish network communication with a notification server, and the client comprises a notification receiving module and a registration management module;

the registration management module receives the trigger event, obtains a website identifier corresponding to the webpage, displays an authorization interface to a user, and receives an authorization operation of the user on the website;

the registration management module sends a registration request comprising the website identifier to the notification server according to the authorization operation of the authorization interface; and

the notification receiving module receives a notification from the website through the notification server.

9. The user terminal according to claim 8, wherein the registration management module obtains a self-defined parameter corresponding to the webpage from the browser, and the registration request comprises the self-defined parameter.

10. The user terminal according to claim 8, wherein, according to the authorization operation of the authorization interface, the registration management module obtains a receiver identifier corresponding to the terminal identifier, and sends a permission message to the website, wherein the permission message comprises the receiver identifier.

11. The user terminal according to claim 10, wherein the step of sending, by the registration management module, the permission message to the website comprises:

obtaining, by the registration management module, the self-defined parameter corresponding to the webpage from the browser, and sending, by the registration management module, the permission message to the website via the network, wherein the permission message comprises a website self-defined parameter.

12. The user terminal according to claim 10, wherein the step of sending, by the registration management module, the permission message to the website comprises:

sending the permission message to the browser, and sending, by the browser, the permission message comprising the self-defined parameter corresponding to the webpage to the website.

13. The user terminal according to claim 10, wherein the registration management module saves a corresponding relationship between the website identifier and the receiver identifier.

14. The user terminal according to claim 13, wherein the registration management module reads an authorization state corresponding to the website identifier, and selects different operations according to the authorization state:

if the authorization state corresponding to the website identifier does not exist, a registration request message is continuously sent; and

if the authorization state is refusal, sending the registration request message is terminated.

15. A notification server, comprising a registration module and a notification push module, wherein

the registration module receives a registration request which is of a terminal and comprises a website identifier, saves a corresponding relationship between a terminal identifier and the website identifier;

the registration module receives a notification push request of a website, wherein the notification push request comprises notification content and a receiver identifier;

the registration module searches for a corresponding terminal identifier according to the website identifier and the receiver identifier;

if the corresponding terminal identifier exists, the registration module sends the notification content and the terminal identifier to the notification push module; and

the notification push module sends the notification content to a user terminal according to the terminal identifier.

16. The notification server according to claim 15, wherein

the registration module generates a receiver identifier according to the terminal identifier;

and

the registration module sends a permission message to the website according to the website identifier, wherein the permission message comprises a receiver identifier corresponding to the terminal identifier.

17. The notification server according to claim 15, wherein

the registration module receives a website registration request which is of the website and comprises the website identifier;

and

the registration module communicates with the website according to a domain name corresponding to the website identifier, to complete registration.

18. The notification server according to claim 16, wherein

the registration module receives a website registration request which is of the website and comprises the website identifier;

and

the registration module communicates with the website according to a domain name corresponding to the website identifier, to complete registration.

19. A notification push system, comprising a user terminal and a notification server, wherein

the user terminal receives an event triggered by a webpage, obtains a website identifier corresponding to the webpage, displays an authorization interface to a user, and receives an authorization operation of the user on the website;

according to the authorization operation of the authorization interface, the user terminal or the notification server generates a receiver identifier, and sends a permission message comprising the receiver identifier to the website;

the notification server receives a notification which is of the website and comprises the receiver identifier; and

the notification server sends the notification to the user terminal according to the receiver identifier.