Web feeds over SIP

• US 8,321,557 B2
• Filed: 10/10/2007
• Issued: 11/27/2012
• Est. Priority Date: 10/10/2007
• Status: Expired due to Fees

• Current Assignee: Sony Ericsson Mobile Communications AB (Sony Group Corp.)
• Original Assignee: Sony Mobile Communications AB (Sony Group Corp.)
• Inventors: Apelqvist, Johan Anders
• Primary Examiner(s): Backer, Firmin
• Assistant Examiner(s): Chambers, Michael A
• Application Number:
  US11/869,912
• Publication Number:
  US 20090100124A1
• Time in Patent Office: 1,875 Days
• Field of Search: 709/224, 709/227, 709/206, 370/352, 719/318
• US Class Current: 709/224
• CPC Class Codes: H04L 12/1859 adapted to provide push services, e.g. data channels
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

A method may include issuing a Session Initiation Protocol (SIP) request to a Web feed server to receive a Web feed, and receiving from the Web feed server the Web feed.

Claims

1. A method comprising:

determining whether a client is SIP (Session Initiation Protocol) enabled;

determining a type of request to issue from the client to a Web feed server, the type of request being based on whether the client is SIP enabled;

in response to determining the client is SIP enabled, issuing, by the client and to the Web feed server, a SIP request to subscribe to a Web feed;

in response to receiving, by the client and from the Web feed server, a response to the SIP request, determining, by the client, that the Web feed server is not compatible with the SIP request where the response indicates that the Web feed server does not support the SIP request method;

in response to determining that the Web feed server is not compatible with the SIP request, polling, by the client, the Web feed server to receive the Web feed from the Web feed server, where polling the Web feed server includes sending, to the Web feed server, a Hypertext Transfer Protocol (HTTP) request based on the SIP request; and

receiving, by the client and in response to polling the Web feed server, the Web feed from the Web feed server.

2. The method of claim 1, where the SIP request includes a subscribe message.

3. The method of claim 1, where determining that the Web feed server is not compatible with the SIP request includes:

determining that the response, from the Web server, does not include a 200 class SIP response.

4. The method of claim 1, where determining that the Web feed server is not compatible with the SIP request includes:

determining that the response from the Web feed server includes a 500 class SIP response.

5. The method of claim 1, where the HTTP request includes a get message.

6. The method of claim 1, where the client comprises a handheld device.

24. The method of claim 1, further comprising:

in response to not receiving a response to the SIP request, determining, by the client, that the Web feed server is not compatible with the SIP request.

25. The method of claim 1, where the Web feed server is identified as SIP-enabled in response to the client transmitting a query message to a network.

7. A method comprising:

determining whether a client is SIP (Session Initiation Protocol) enabled;

determining a type of request to issue from the client to a Web feed server, the type of request being based on whether the client is SIP enabled;

in response to determining the client is not SIP enabled, issuing, by the client, a first Hypertext Transfer Protocol (HTTP) request for a Web feed;

intercepting, by the client, the first HTTP request;

translating, by the client, the first HTTP request to a SIP request for the Web feed;

issuing, by the client, the SIP request to the Web feed server;

determining, by the client, that the Web feed server is not compatible with the SIP request in response to receiving a message from the Web feed server indicating that the Web feed server does not support the SIP request method;

automatically issuing, by the client to the Web feed server and in response to determining that the Web feed server is not compatible with the SIP request, a second HTTP request to receive the Web feed from the Web feed server, wherein the second HTTP request is not translated to a SIP request; and

receiving, by the client, at least a portion of the Web feed from the Web feed server in response to the second HTTP request.

8. The method of claim 7, where the first HTTP request includes a get message and the SIP request includes a subscribe message.

9. The method of claim 7, where the client comprises a handheld device.

10. The method of claim 7, where determining that the Web feed server is not compatible with the SIP request further includes:

determining that the response, from the Web feed server, includes a 500 class SIP response.

11. A device, comprising:

a memory to store instructions; and

a processor to execute the instructions to;

determine whether the device is SIP (Session Initiation Protocol) enabled;

determine a type of request to issue from the device to a Web feed server, the type of request being based on whether the device is SIP enabled;

in response to determining the device is SIP enabled, issue a SIP request to the Web feed server to request a Web feed associated with the Web feed server;

determine that the Web feed server is not compatible with the SIP request in response to receiving a message from the Web feed server indicating that the Web feed server does not support the SIP request method;

poll the Web feed server to receive the Web feed in response to determining that the Web feed server is not compatible with the SIP request, where the processor, when polling the Web feed server, further sends, to the Web feed server, a Hypertext Transfer Protocol (HTTP) request based on the SIP request; and

receive, from the Web feed server, the Web feed in response to sending the HTTP request.

12. The device of claim 11, where the SIP request includes a subscribe message for the Web feed based on Really Simple Syndication (RSS).

13. The device of claim 11, where the device includes a wireless telephone.

14. The device of claim 11, where the device is a handheld device.

15. The device of claim 11, where the HTTP request includes a get message.

16. The device of claim 11, where the processor, when determining that the Web feed server is not compatible with the SIP request, further executes instructions to:

determine that the response, from the Web feed server to the SIP request, includes a 500 class SIP response.

17. The device of claim 11, where the processor, when determining that the Web feed server is not compatible with the SIP request, further executes instructions to:

determine the response, from the Web feed server, does not include a 200 class SIP response.

18. A memory device containing instructions executable by at least one processor, the memory device comprising:

one or more instructions for determining whether a client is SIP (Session Initiation Protocol) enabled;

one or more instructions for determining a type of request to issue from the client to a Web feed server, the type of request being based on whether the client is SIP enabled;

in response to determining the client is SIP enabled, one or more instructions for issuing a SIP request for a Web feed to the Web feed server;

one or more instructions for determining that the Web feed server is not compatible with the SIP request in response to receiving a message from the Web feed server indicating that the Web feed server does not support the SIP request method;

one or more instructions for polling the Web feed server in response to determining that the Web feed server is not compatible with the SIP request, where the one or more instructions for polling the Web feed server include;

one or more instructions for sending a Hypertext Transfer Protocol (HTTP) request based on the SIP request; and

one or more instructions for receiving the Web feed from the Web feed server in response to sending the HTTP request.

19. The memory device of claim 18, where the SIP request includes a subscribe message.

20. The memory device of claim 18, where the one or more instructions for determining that the Web feed server is not compatible with the SIP request further include:

one or more instructions for determining that the response, from the Web feed server, does not include a 200 class SIP response.

21. The memory device of claim 18, where the one or more instructions for determining that the Web feed server is not compatible with the SIP request further include:

one or more instructions for determining that the response, from the Web feed server, includes a 500 class response.

22. The memory device of claim 18, where the HTTP request includes a get message.

23. A device, comprising:

a memory to store instructions; and

a processor to execute the instructions to;

determine whether the device is SIP (Session Initiation Protocol) enabled;

determine a type of request to issue from the device to a Web feed server, the type of request being based on whether the device is SIP enabled;

in response to determining the device is not SIP enabled;

issue a first Hypertext Transfer Protocol (HTTP) request for a Web feed;

intercept the first HTTP request;

translate the first HTTP request to a SIP request;

transmit the SIP request for the Web feed to the Web feed server;

determine that the Web feed server is not compatible with the SIP request, where a message is received at the device when the Web feed server does not support the SIP request method;

in response to determining that the Web feed server is not compatible with the SIP request, transmit a second HTTP request to the Web feed server to receive the Web feed, wherein the second HTTP request is not translated to a SIP request; and

receive the Web feed from the Web feed server in response to transmitting the second HTTP request.