Claims Analysis

From Push API PAG
Jump to: navigation, search

(See the * Pointer Events PAG Report for an example of a completed report and claims analysis). PAG Wiki main page

List of patents

These patents are categorized into group of related patents (e.g. international versions of an issued patent, or divisional patents of an issued patent claiming on a same aspect of the invention):

Group 1

US 6188909

text content/metadata, with link to a PDF

Claims of the Patent and Push API Specification Features
Claims of the Patent Evaluation against the Push API Specification
1

A terminal for a communication network, the terminal comprising a plurality of applications for displaying information and processing information and further comprising wireless communication means for communicating user messages, wherein said terminal comprises means for receiving a wireless communicated user message having information for one of said applications and a header pointing to one of said applications, said terminal further comprising means for addressing said information to a respective application according to said header, the user message having an address field containing the address of the destination of the message and a data field containing said information of the user message, wherein said header is disposed in said data field.

[EF] This claim does not read on the Push API as the Push API does not rely on user messages to transmit the push notifications. In this patent the term ‘user message’ is firstly introduced in the claims as a way to generalize the term ‘short message’ (i.e. Short Message Service) used throughout the patent description. The term ‘user message’ can be understood as a way to encompass all messaging technologies, which like the Short Message Service are a communication means for the final user, but that are re-used in the frame if this invention to transfer information to/from an application. As the Push API is not specified in a way that needs to rely on user messages it can be implemented without matching this claim.
8

A terminal for a communication network, the terminal comprising a plurality of applications for displaying information and processing information and further comprising wireless communication means for communicating user messages, wherein said terminal comprises means for sending information relating to one of said applications in a user message over wireless communication and means for adding a header to the user message, the header indicating a respective application that the information relates to, the user message having an address field containing the address of the destination of the user message and a data field containing said information of the message, wherein said header is disposed in said data field.

[EF] Same analysis as for claim 1.

13

A mobile station, comprising a plurality of applications for displaying information and processing information and further comprising wireless communication means for communicating short messages having information in the form of characters, wherein the mobile station comprises means for receiving wireless communication short messages having information for one of said applications and a header pointing to said one of said applications, and means for addressing the information to said one of said applications according to said header.

[EF] This claim does not read on the Push API as the Push API does not need to rely on short messages (i.e. Short Message Service) to transmit push notifications.

18

A mobile station, comprising a plurality of applications for displaying information and processing information and further comprising a wireless communication means for communicating short messages having information in the form of characters, wherein the mobile station comprises means for processing information relating to one of said applications into characters and for sending the processed information in a short message over wireless communication and means for adding a header to the short message, the header indicating a respective application that the information relates to.

[EF] Same analysis as for claim 13.

22

A method of transferring data between a first device and a second device that is remote from the first device, both the first device and the second device being one of a mobile station capable of communicating over a mobile communications network and a server connected to the mobile communications network, comprising steps of: retrieving a data entry from an application of a plurality of applications of the first device, said application containing a plurality of data entries each having a number of data fields individual ones of which are separated by field separators, transmitting said retrieved data entry to the second device in a short message via the mobile communications network, and receiving said retrieved data entry at the second device and storing, based on said field separators, the data fields of the received data entry in corresponding data fields in a corresponding application of the second device.

[EF] Same analysis as for claim 13.

US 7366529

text and metadata (including links) This is a divisional patent of US 7088990 , which is in turn a divisional patent of US 6188909 (above) Nokia sued HTC over this patent

Claims of the Patent and Push API Specification Features
Claims of the Patent Evaluation against the Push API Specification
1

An apparatus, comprising:

  • at least one data processing unit configured
    • to process messages having a predefined format, the predefined format including an application header identifying an application of a plurality of applications,
    • to execute applications of the plurality, and
    • after messages having the predefined format are received via a radio receiver, to address and store data from the received messages into applications of the plurality according to the application headers of said received messages.

[EF] This claim does not read on the Push API as the push notifications described in this specification do not contain actual data, but just notify applications about data being awaiting at the corresponding app servers for subsequent retrieval.

12

An apparatus, comprising:

  • at least one data processing unit configured
    • to process messages having a predefined format, the predefined format including an application header identifying an application of a plurality of applications,
    • to execute applications of the plurality,
    • to add, to messages having the predefined format, data from applications of the plurality and application headers identifying applications of the plurality, and
    • to transmit said messages with the added data and application headers via a radio transmitter.

[EF] This claim does not read on the Push API for the following reasons:

  • The device where the user agent and the web applications described in the Push API run does not match the behavior of the apparatus described in this claim as it does not transfer any message with data of the applications up to the push server or any other entity.
  • The push server does not match the behavior of the apparatus described in this claim as it does not ‘execute the applications of the plurality’.
  • The app server does not match the behavior of the apparatus described in this claim as it does not need to use a radio transmitter.
23

A method, comprising:

  • receiving a user message at a first device via a mobile communications network, wherein
    • the user message includes a header indicating to the first device an application of a plurality of applications stored in the first device,
    • the user message further includes a data entry retrieved from an application in a second device,
    • the second device is remote from the first device,
    • the application in the second device corresponds to the indicated application in the first device,
    • the application in the second device has a plurality of data entries each having a number of data fields separated by field separators, and
    • at least one of the first and second devices is a mobile station configured for communicating over a mobile communications network; and
  • storing the retrieved data entry in the indicated application of the first device, said storing including storing data in the data fields of the retrieved entry into corresponding data fields in the indicated application based on the field separators in the retrieved data.

[EF] This claim does not read on the Push API as the Push API does not rely on user messages to transmit the push notifications. In this patent the term ‘user message’ is firstly introduced in the claims as a way to generalize the term ‘short message’ (i.e. Short Message Service) used throughout the patent description. The term ‘user message’ can be understood as a way to encompass all messaging technologies, which like the Short Message Service are a communication means for the final user, but that are re-used in the frame if this invention to transfer information to/from an application. As the Push API is not specified in a way that needs to rely on user messages it can be implemented without matching this claim.

25

A memory comprising instructions stored thereon which, when executed by one or more processors, cause the one or more processors to perform:

  • receiving an application message via an RF interface at a wirelessly communicating device, the application message having a format characteristic of user messages also received via the RF interface, wherein
    • the application message contains an identifier corresponding to one of a plurality of applications stored on the wirelessly communicating device,
    • the plurality of applications provide services in addition to telephone calls and user messages received via the RF interface, and
    • the plurality of applications receive input based on messages received via the RF interface and having the user message format; and
  • determining that the application message pertains to an application of the plurality.

[EF] Same analysis as for claim 23.

31

A memory comprising instructions stored thereon which, when executed by one or more processors, cause the one or more processors to perform:

  • receiving a user message containing an identifier corresponding to one of a plurality of applications stored on a wirelessly communicating device, wherein
    • the plurality of applications provide services in addition to telephone calls and user messages,
    • each of the plurality of applications receives input based on user messages,
    • the corresponded-to application of the plurality accesses a plurality of records, each of the records having a plurality of predefined fields, and
    • the received user message contains data of a type associated with one or more of the predefined fields;
  • placing the received user message data in the one or more of the predefined fields of a record of the plurality;
  • determining that the received user message pertains to an application of the plurality; and
  • launching the corresponded-to application of the plurality.

[EF] Same analysis as for claim 23.

33

A memory comprising instructions stored thereon which, when executed by one or more processors, cause the one or more processors to perform:

  • receiving a user message containing an identifier corresponding to one of a plurality of applications stored on a wirelessly communicating device, wherein
    • the plurality of applications provide services in addition to telephone calls and user messages,
    • each of the plurality of applications receives input based on user messages,
    • receiving a user message includes receiving a user message containing data and an identifier corresponding to an application of the plurality,
    • the corresponded-to application of the plurality accesses a plurality of records, and
    • the received user message data is a record of a type accessed by the corresponded-to application of the plurality;
  • determining that the received user message pertains to an application of the plurality;
  • providing the data contained in the received user message to the corresponded-to application of the plurality; and
  • adding the record of the received user message to the plurality of records.

[EF] Same analysis as for claim 23.

35

A memory comprising instructions stored thereon which, when executed by one or more processors, cause the one or more processors to perform:

  • receiving a user message containing an identifier corresponding to one of a plurality of applications stored on a wirelessly communicating device, wherein
    • the plurality of applications provide services in addition to telephone calls and user messages,
    • each of the plurality of applications receives input based on user messages,
    • receiving a user message includes receiving a user message containing data and an identifier corresponding to an application of the plurality,
    • the corresponded-to application of the plurality accesses a plurality of records of a first type, and
    • the received user message data includes a record of the first type;
  • determining that the received user message pertains to an application of the plurality;
  • providing the data contained in the received user message to the corresponded-to application of the plurality; and
  • prompting a user to send a second type of record in response to the received first type of record.

[EF] Same analysis as for claim 23.

EP 0882375

Filing date 1997-02-21 Published 2004-09-24

This patent belongs to the same family of US6188909 (above)

Nokia sued HTC over this patent

EP 0882375 A2 (text in HTML, has link to PDF scan) EP 0882375 B1 (text in HTML, has link to PDF scan)

Claims of the Patent and Push API Specification Features
Claims of the Patent Evaluation against the Push API Specification
1

A terminal (1) for a communication network, the terminal comprising a plurality of applications (17, 18) for displaying and processing of information and further comprising wireless communication means for communicating user messages, characterised in that it comprises means that have been arranged to receive a wirelessly communicated user message having information for one of said applications (17, 18) and a header relating to said one of said applications (17, 18), and means (8) arranged to address the information to a respective one of said applications (17, 18) according to said header, the user message has an address field (ADD) containing the address of the destination of the message and a data field (INFO) containing the information of the message, and that said header is in said data field (INFO).

[EF] This claim does not read on the Push API as the Push API does not rely on user messages to transmit the push notifications. In this patent the term ‘user message’ is firstly introduced in the claims as a way to generalize the term ‘short message’ (i.e. Short Message Service) used throughout the patent description. The term ‘user message’ can be understood as a way to encompass all messaging technologies, which like the Short Message Service are a communication means for the final user, but that are re-used in the frame if this invention to transfer information to/from an application. As the Push API is not specified in a way that needs to rely on user messages it can be implemented without matching this claim.
2

A terminal (1) for a communication network, the terminal comprising a plurality of applications (17, 18) for displaying and processing of information and further comprising wireless communication means for communicating user messages, characterised in that it comprises means (8, 10 - 12) that have been arranged to send information relating to one of said applications (17, 18) in a user message over wireless communication and means (8) arranged to add a header to the user message, the header indicating the respective application (17, 18) that the information relates to, the user message has an address field (ADD) containing the address of the destination of the message and a data field (INFO) containing the information of the message, and that said header is in said data field (INFO).

[EF] Same analysis as for claim 1.

16

A method of transferring data between a first device and a second device, the second device being remote from the first device, and both the first and second device being one of a mobile station capable of communicating over a mobile communications network and of a computer having a connection to the mobile communications network, the method comprising:

  • retrieving a data entry from an application of the first device, said application containing a plurality of data entries each having a number of data fields,
  • transmitting said entry to the second device in a user message via the mobile communications network, the user message comprising a header for indicating, to the second device, which application of a plurality of applications is comprised in the second device that the data relates to, and the user message has an address field containing the address of the destination of the message and a data field containing the information of the message, and that said header is in said data field, and
  • storing the received data entry in corresponding data fields in a corresponding application of the second device.

[EF] Same analysis as for claim 1.

EP 1439723

This patent is a divisional patent of EP 0882375 (above) and thus belongs to the same family of US 6188909 (above)

EP 1439723 A1 (PDF) and EP 1439723 B1 (PDF)

Nokia sued HTC over this patent

Claims of the Patent and Push API Specification Features
Claims of the Patent Evaluation against the Push API Specification
1

A terminal (1) for a communication network, the terminal comprising a plurality of applications (17, 18) for displaying and processing of information and further comprising wireless communication means for communicating user messages, characterised in that it comprises means that have been arranged to receive a wirelessly communicated user message having information for one of said applications (17, 18) and a header relating to said one of said applications (17, 18), and means (8) arranged to address and store the information to a respective one of said applications (17, 18) according to said header, and the information is divided into at least two data fields, the data fields being separated by field separators.

[EF] This claim does not read on the Push API as the Push API does not rely on user messages to transmit the push notifications. In this patent the term ‘user message’ is firstly introduced in the claims as a way to generalize the term ‘short message’ (i.e. Short Message Service) used throughout the patent description. The term ‘user message’ can be understood as a way to encompass all messaging technologies, which like the Short Message Service are a communication means for the final user, but that are re-used in the frame if this invention to transfer information to/from an application. As the Push API is not specified in a way that needs to rely on user messages it can be implemented without matching this claim.

2

A terminal (1) for a communication network, the terminal comprising a plurality of applications (17, 18) for displaying and processing of information and further comprising wireless communication means for communicating user messages, characterised in that it comprises means (8, 10 - 12) that have been arranged to send information stored in one of said applications (17, 18) in a user message over wireless communication and means (8) arranged to add a header to the user message, the header indicating the respective application (17, 18) that the information relates to, and the information is divided into at least two data fields, the data fields being separated by field separators.

[EF] Same analysis as for claim 1.

18

A method of transferring data between a first device and a second device, the second device being remote from the first device, and both the first and second device being one of a mobile station capable of communicating over a mobile communications network and of a computer having a connection to the mobile communications network, the method comprising:

  • retrieving a data entry from an application of the first device, said application containing a plurality of data entries each having a number of data fields and the data entry is divided into at least two data fields, the data fields being separated by field separators,
  • transmitting said entry to the second device in a user message via the mobile communications network, the user message comprising a header for indicating, to the second device, which application of a plurality of applications comprising in the second device that the data relates to, and
  • storing the received data entry in corresponding data fields in a corresponding application of the second device.

[EF] Same analysis as for claim 1.

Group 2

US 6292668

This patent is a divisional patent of US 6188909 (above)

US 6292668 html (links to PDF scan)

Claims of the Patent and Push API Specification Features
Claims of the Patent Evaluation against the Push API Specification
1

A mobile terminal of a mobile communication network for accessing Internet over the mobile communication network, the mobile terminal comprising

  • means for wireless communication with a device by opening a communication link over the mobile communication network, means for wireless communication with a device by communicating information in user messages over the mobile communication network,
  • two modes of operation for fetching information from the Internet, wherein
  • in a first mode of operation the mobile terminal has been arranged to open said communication link to the Internet and to download information from a server in the Internet through transmission over said opened communication link, and
  • in a second mode of operation the mobile terminal has been arranged to send requests to and to receive information from a server in the Internet in said user messages.
 [EF] This claim describes a behavior by a mobile terminal, which is much more specific than the functionality in W3C Push API. So the W3C Push API can be implemented without matching the claim.

In a nutshell such behavior by a mobile terminal is the following. The mobile terminal downloads a first piece of information (basically a web page) over a regular Internet connection, having that piece of information (i.e. the web page) details as to how to further communicate with a server via user messages (e.g. SMS). Then the mobile terminal communicates via user messages (e.g. SMS) to request and receive information from said server.

16

A method of transferring data between a mobile station for communicating over a mobile communications network and a server in the Internet having a connection to the mobile communications network, the method comprising:

  • providing the mobile station with two modes of operation for fetching information from the Internet;
  • when the mobile station is in a first mode of operation, opening a communication link from the mobile station over the mobile communications network to the Internet; and
  • downloading information from the server in the Internet to the mobile station through transmission over said opened communication link; and
  • when the mobile station is in a second mode of operation, sending a request from the mobile station to the server in a first user message via the mobile communications network,
  • as a response to receiving the request at the server sending a response from the server to the mobile station in a second user message via the mobile communications network.
 [CMN] At first glance looks like a subset of Claim 22 of US6188909 (above)

[EF] Same analysis as for claim 1.

EP 1581016

This patent is a divisional patent of EP 1439723 (above), which is in turn a divisional patent of EP 0882375 (above) and thus belongs to the same family of US 6188909 (above).

Its claims relate to the same aspect of the invention as US 6292668 (above)

A3 text, metadata..., A2 text, metadata, B1 text, metadata

Nokia sued HTC over this patent

Claims of the Patent and Push API Specification Features
Claims of the Patent Evaluation against the Push API Specification
1

A terminal (1) for accessing Internet over a wireless communication network, the terminal comprising

  • means for wireless communication with a server (SERV) by opening a communication link (101, 101', 102) over the wireless communication network,
  • means for wireless communicating with a device (SM-SC) by sending (103) and receiving (106) user messages over the wireless communication network,
  • wherein the terminal is configured to fetch information from the Internet,
  • wherein the terminal is configured to open the communication link to the Internet and to download (102) service page information from the server in the Internet through said communication link, and
  • wherein the terminal is configured to send requests (103), which requests reuse the downloaded service page information, to and configured to receive (106, 105) service page response information from a server in the Internet in respective user messages.
 [EF] This claim describes a behavior by a mobile terminal, which is much more specific than the functionality in W3C Push API. So the W3C Push API can be implemented without matching the claim.

In a nutshell such behavior by a mobile terminal is the following. The mobile terminal downloads a first piece of information (basically a web page) over a regular Internet connection, having that piece of information (i.e. the web page) details as to how to further communicate with a server via user messages (e.g. SMS). Then the mobile terminal communicates via user messages (e.g. SMS) to request and receive information from said server.

11

A method of transferring data between a terminal capable of communicating over a mobile communications network and a server in the Internet having a connection to the mobile communications network, the method comprising:

  • opening a communication link from the terminal to the Internet and downloading service page information from the server in the Internet through said communication link to the terminal,
  • sending a request from the terminal to a server in a first user message, which request reuses service page information downloaded via the mobile communications network, and
  • responsive to receiving the request at the server, sending a service page response from the server to the terminal in a second user message via the mobile communications network.
 [EF] Same analysis as for claim 1.

JP 3917596

This patent belongs to the same family of US 6188909 (above). Its claims relate to the same aspect of the invention as US 6292668 (above) EP 1581016 (above)

Abstract/metadata


Claims of the Patent and Push API Specification Features
Claims of the Patent Evaluation against the Push API Specification
Notes

http://www.ipdl.inpit.go.jp/homepg_e.ipdl

1.This document has been translated by computer. So the translation may not reflect the original precisely. 2.**** shows the word which can not be translated. 3.In the drawings, any words are not translated.

1

It is a terminal which accesses the Internet via a wireless communication network, A means which carries out a wireless communication to equipment by opening a communication link through the aforementioned wireless communication network, A means which carries out a wireless communication to equipment by passing the aforementioned wireless communication network, and transmitting and receiving user messages, They are two operational modes for pulling out information from the aforementioned Internet, In first operational mode, the aforementioned terminal can open a communication link to the aforementioned Internet, and can download information through the aforementioned communication link from a server in the aforementioned Internet, A terminal which the aforementioned terminal transmits a demand to a server in the aforementioned Internet in the aforementioned user messages based on information downloaded by said first operational mode in second operational mode, and is provided with operational mode which can receive information from the server.

WS: same analysis as other Group 2

11

It is how to transmit data between a mobile station which can communicate via a mobile communications network, and a server in the Internet which has connection with the aforementioned mobile communications network, A step which opens a communication link from the aforementioned mobile station to the aforementioned Internet, and downloads information from a server in the aforementioned Internet through the aforementioned communication link in first operational mode to the aforementioned mobile station, A step which transmits a demand to the aforementioned server from the aforementioned mobile station via the aforementioned mobile communications network in second operational mode based on information downloaded by said first operational mode in first user messages, A method provided with a step which transmits a response to the aforementioned mobile station via the aforementioned mobile communications network as a response to having received the aforementioned demand in the aforementioned server in second user messages from the aforementioned server.

WS: same analysis as other Group 2

Abstract:

PROBLEM TO BE SOLVED: To provide a terminal for easily transmitting and receiving application related information.

SOLUTION: The terminal 1 for accessing to the Internet via a radio communication network comprises means for performing a radio communication with a device by opening a communication link via the radio communication network, means for performing radio communication with the device by transmitting and receiving a user message via the radio communication network, and a pair of operation modes for deriving pieces of information from the Internet in which the operation modes includes a first operation mode and a second operation mode. In the first operation mode, the terminal can download the pieces of information through a communication link from a server located in the Internet after opening the communication link to the Internet. In the second operation mode, the terminal can transmit a request to the server located in the Internet by a user message, and receive the pieces of information from the server.

Group 3

EP 1322072

EP 1322072 A1 (text in HTML, has link to PDF) EP 1322072 B1 (text in HTML, has link to PDF)

Nokia sued HTC over this patent

Claims of the Patent and Push API Specification Features
Claims of the Patent Evaluation against the Push API Specification
1

Mobile communication system comprising a mobile data unit (3, 4) acting via a digital mobile communication network as a remote workstation in a data network (24); a mobile exchange (10, 15); means for establishing a digital data connection between the mobile data unit (3, 4) and the mobile exchange (10, 15); characterized in that the system further comprises an interconnecting computer (19) attached to the mobile exchange (10, 15), the interconnecting computer being connected to a data network by a digital interface and arranged for extending the connection and simulating the mobile data unit (3, 4) towards said data network (24) in order to establish a digital communication between said mobile data unit and any further party in said data network.

[EF] This claim does not read on the Push API as the Push Server in W3C Push API cannot be mapped to the “interconnecting computer” described in the invention as it is not arranged to simulate any “mobile data unit”. It should be noted that the scope of the W3C Push API specification is merely the interface between the Web app and the User Agent.
6

Method for connecting a remote workstation to a data network via a mobile communication network, the method comprising the steps of starting a data session from the remote workstation; establishing a digital data connection over the radio path in the mobile communication network for the data session; extending the digital data connection between the mobile communication network and the data network in order to establish a digital communication between the remote workstation and any other party in said data network; characterized by temporarily releasing said digital data connection between the mobile data unit and an interconnecting computer connected to the data network by a digital interface in the mobile communication network during the data session, and when the digital data connection has been temporarily released

[EF] This claim does not read on the Push API for the following reasons:
  • the Push Server in W3C Push API cannot be mapped to the Interconnecting computer described in the invention as it is not arranged to simulate any “remote workstation”.
  • W3C Push API does not require that notifications sent to the user agent are transmitted using a “non-switched message transmission”. It should be noted that the scope of the W3C Push API specification is merely the interface between the Web app and the User Agent.
12

An interconnecting computer acting as a gateway in a mobile communications system for providing a mobile data unit (3,4) using a mobile communications network with an access to a data network (24), characterized in that the interconnecting computer (19) is arranged to communicate with the mobile data unit (3,4) over a digital data connection established between the mobile data unit and the interconnecting computer over a mobile communications network, and the interconnecting computer being further connected to said data network by a digital interface and arranged for extending the digital connection and simulating the mobile data unit (3,4) towards said data network (24) in order to enable a digital communication between said mobile data unit and any further party in said data network (24).

[EF] This claim does not read on the Push API as the Push Server in W3C Push API cannot be mapped to the “interconnecting computer” described in the invention as it is not arranged to simulate any “mobile data unit”. It should be noted that the scope of the W3C Push API specification is merely the interface between the Web app and the User Agent.

Group 4

US 7079517

Claims of the Patent and Push API Specification Features
Claims of the Patent Evaluation against the Push API Specification
1

A method for transferring information, by a server to a mobile terminal in a predetermined area of a packet-switched network comprising a plurality of support nodes,

  • the method comprising the steps of:
  • associating at least one identifier of the mobile terminal with a Packet Data Protocol address, or PDP address, of the same mobile terminal;
  • operationally connecting the server and all support nodes in said predetermined area to an intelligent network node;
  • informing the intelligent network node about the identifier and the current PDP address of the mobile terminal; and
  • using the PDP address stored in the intelligent network node for routing said information to the mobile terminal.
 [EF] This claim does not read on the Push API as the specification does not mandate any means by which notifications are transferred from a server to the device where the user agent and the web application reside, and specifically do not mandate the interaction with an Intelligent Network. It should be noted that the scope of the W3C Push API specification is merely the interface between the Web app and the User Agent.
9

A Service Control Point, wherein

  • for transferring information by a server to a mobile terminal having at least one identifier and a PDP address, in a packet-switched network comprising a plurality of support nodes, the Service Control Point is
  • operationally connected to the packet-switched network and the server;
  • adapted to store said at least one identifier and the PDP address of the mobile terminal in response to a first message originating from the packet-switched network; and
  • adapted to support said transferring of information by a server.
 [EF] This claim does not read on the Push API as the specification does not mandate any means by which notifications are transferred from a server to the device where the user agent and the web application reside, and specifically do not mandate the interaction with an Intelligent Network, and more specifically with a Service Control Point. It should be noted that the scope of the W3C Push API specification is merely the interface between the Web app and the User Agent.

Image File Wrappers

See USPTO Public Pair system

Retrieved from "https://www.w3.org/2013/papag/wiki/index.php?title=Claims_Analysis&oldid=86"