Transport method selection for delivery of server notifications

Patent metadata

Field	Value
Publication number	US-11323502-B2
Application number	US-201716635527-A
Country	US
Kind code	B2
Filing date	Aug 4, 2017
Priority date	Aug 4, 2017
Publication date	May 3, 2022
Grant date	May 3, 2022

Abstract

Methods and apparatus, including computer program products, are provided for transport method selection of asynchronous notifications. In some example embodiments, there may be provided a method that includes sending, by a client, a hypertext transfer protocol request for at least one asynchronous notification to be sent by a server to the client, the hypertext transfer protocol request including at least one proposed transport method for carrying the at least one asynchronous notification; determining, by the client, whether a first transport method selected by the server from the at least one proposed transport method is successfully established; and when the determination is that the first transport method is not established successfully, sending, by the client, another hypertext transfer protocol request to the server, the other hypertext transfer protocol request including at least one other proposed transport method. Related systems, methods, and articles of manufacture are also described.

First claim

What is claimed:

1. A method comprising:
sending, by a client, a hypertext transfer protocol request for at least one asynchronous notification to be sent by a server to the client, the hypertext transfer protocol request including at least one proposed transport method for carrying the at least one asynchronous notification, the at least one proposed transport method comprising a first transport method, the first transport method comprising a separate hypertext transfer connection, the hypertext transfer protocol request including a callback uniform resource identifier at the client to enable the separate hypertext transfer connection, the separate hypertext transfer connection comprising a reverse hypertext transport protocol callback to the client;
determining, by the client, whether the first transport method comprising the separate hypertext transfer connection is successfully established, the first transport method being selected by the server from the at least one proposed transport method included in the hypertext transfer protocol request; and
when the determination is that the first transport method comprising the separate hypertext transfer connection is not established successfully, sending, by the client, another hypertext transfer protocol request to the server, the other hypertext transfer protocol request including at least one other proposed transport method comprising a websocket.

2. The method of claim 1 , wherein the hypertext transfer protocol request includes a request for the server to probe, via a test notification message, whether the first transport method comprising the separate hypertext transfer connection is successfully established.

3. The method of claim 1 , wherein the first transport method comprising the separate hypertext transfer connection is determined to be successfully established based on a test notification received before a timeout.

4. The method of claim 1 , further comprising:
receiving, by the client, the at least one asynchronous notification carried via the first transport method comprising the separate hypertext transfer connection, when the determination is that the first transport method is established successfully.

5. A method comprising:
receiving, by a server, a hypertext transfer protocol request for the server to send at least one asynchronous notification, the hypertext transfer protocol request including at least one proposed transport method for carrying the at least one asynchronous notification, the at least one proposed transport method comprising a first transport method, the first transport method comprising a separate hypertext transfer connection, the hypertext transfer protocol request including a callback uniform resource identifier at a client to enable the separate hypertext transfer connection, the separate hypertext transfer connection comprising a reverse hypertext transport protocol callback to the client;
sending, by the server, an indication of whether the first transport method comprising the separate hypertext transfer connection selected by the server from the at least one proposed transport method is accepted for establishment;
sending, by the server, a message to probe establishment of the first transport method comprising the separate hypertext transfer connection; and
receiving, by the server, another hypertext transfer protocol request including at least one other proposed transport method comprising a websocket, when the first transport method comprising the separate hypertext transfer connection is not accepted for establishment or not successfully established.

6. The method of claim 5 , wherein the indication comprises a reply to the hypertext transfer protocol request accepting or rejecting the request.

7. The method of claim 5 , further comprising:
sending, by the server, the at least one asynchronous notification carried via the first transport method, when the first transport is accepted for establishment by the server or successfully established.

8. An apparatus comprising:
at least one processor; and
at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to at least:
send a hypertext transfer protocol request for at least one asynchronous notification to be sent by a server to the apparatus, the hypertext transfer protocol request including at least one proposed transport method for carrying the at least one asynchronous notification, the at least one proposed transport method comprising a first transport method, the first transport method comprising a separate hypertext transfer connection, the first transport method comprising a separate hypertext transfer connection, the hypertext transfer protocol request including a callback uniform resource identifier at the apparatus to enable the separate hypertext transfer connection, the separate hypertext transfer connection comprising a reverse hypertext transport protocol callback to the apparatus;
determine whether the first transport method comprising the separate hypertext transfer connection is successfully established, the first transport method being selected by the server from the at least one proposed transport method included in the hypertext transfer protocol request; and
when the determination is that the first transport method comprising the separate hypertext transfer connection is not established successfully, send another hypertext transfer protocol request to the server, the other hypertext transfer protocol request including at least one other proposed transport method comprising a websocket.

9. An apparatus comprising:
at least one processor; and
at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to at least:
receive a hypertext transfer protocol request for the apparatus to send at least one asynchronous notification, the hypertext transfer protocol request including at least one proposed transport method for carrying the at least one asynchronous notification, the at least one proposed transport method comprising a first transport method, the first transport method comprising a separate hypertext transfer connection, the hypertext transfer protocol request including a callback uniform resource identifier at a client to enable the separate hypertext transfer connection, the separate hypertext transfer connection comprising a reverse hypertext transport protocol callback to the client;
send an indication of whether the first transport method comprising the separate hypertext transfer connection selected by the apparatus from the at least one proposed transport method is accepted for establishment;
send a message to probe establishment of the first transport method comprising the separate hypertext transfer connection; and
receive another hypertext transfer protocol request including at least one other proposed transport method comprising a websocket, when the first transport method comprising the separate hypertext transfer connection is not accepted for establishment or not successfully established.

10. A non-transitory computer-readable medium including program code which when executed causes operations comprising:
sending, by a client, a hypertext transfer protocol request for at least one asynchronous notification to be sent by a server to the client, the hypertext transfer protocol request including at least one proposed transport method for carrying the at least one asynchronous notification, the at least one proposed transport method comprising a first transport method, the first transport method comprisi

Assignees

• Nokia Technologies Oy

Inventors

• Rauschenbach Uwe
• Belling Thomas

Classifications

• G06F9/542

  Event management; Broadcasting; Multicasting; Notifications · CPC title

• H04L67/04

  specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability · CPC title

• H04L67/02 Primary

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

• H04L67/42

  Electricity · mapped topic