AMENDMENTS TO THE CLAIMS
`
`All pending claims, along with a current status of each, is reproduced below. If
`
`indicated, please amend the claims accordingly.
`
`1.
`
`(Currently Amended) A method for delivering mobile event notification data, the
`
`method comprising:
`
`receiving, by a computing server mobile-enent—sttenniing—system, a plurality of mobile
`
`event notifications from a plurality of event source devices, onoh—of—the—pl-u-ta-l-ity
`
`of a particular mobile event notification notif-iontions generated in response to an
`
`action associated with one of the plurality of event source devices, enoh—of—tho
`
`piuta-l-ity—mobi-le-enont—notifiontions the particular mobile event notification
`
`comprising n—messnge—thnt—oonq-ptises (i) an event descriptor describing the event
`
`action, gii) a particular destination address associated with a message publisher,
`
`and giii) a tag trigger that is associated an automated message set by the message
`
`publisher;
`
`filtering, by the computing server mobile-enent—sttoaniing—system, the plurality of mobile
`
`event notifications including the particular mobile event notification based on one
`
`or more criteria specified by the message publisher and based on destination
`
`addresses included in the plurality of mobile event notifications, filtered mobile
`
`event notifications including the particular mobile event notification generated in
`
`response to the action a—system—onstonier;
`
`generating, by the computing server mobiloevent—streanqnig—system, a plurality of data
`
`
`
`objects that comprise filtered information of events thoevent—desori—ptots
`
`

`

`transmitted from the plurality of event source devices extracted from the filtered
`
`mobile event notifications;
`
`transmitting2 by the computing server and based on the tag trigger remained in the filtered
`
`information: the automated message set by the message publisher to the one of the
`
`event source devices; and
`
`
`
`transmitting, by the computing server mobile-event—strea-ming—system, the plurality of
`
`
`data objects comprising filtered information of the events to a data store: the data
`
`store accessible by message publisher event—desefl-pters—transmitted—frem—the
`
`1].;
`
`I'll
`
`‘ll
`
`.
`
`2.
`
`(Original) The method of claim 1, further comprising:
`
`decorating the filtered plurality of mobile event notifications with one or more metadata
`
`tags.
`
`3.
`
`(Original) The method of claim 2, wherein the generated plurality of data objects
`
`further comprise the metadata tags.
`
`4.
`
`(Currently Amended) The method of claim 1, wherein the action associated with
`
`ene—ef—t—he—pl-u-ra—l—i-t—y—ef the particular mobile event notification is an action performed by a user
`
`when using [[the]] a mobile application.
`
`5.
`
`(Currently Amended) The method of claim 1, wherein the action associated with
`
`ene—ef—t—he—pl-u-ra—l—i-t—y—ef the particular mobile event notification is associated with an application
`
`lifecycle event.
`
`

`

`6.
`
`(Currently Amended) The method of claim 1, wherein the action associated with
`
`one-of—the—pl-uta—l—i-t—y—of the particular mobile event notification is associated with a user
`
`engagement event.
`
`7.
`
`(Original) The method of claim 1, wherein the data objects are in a pre—defined
`
`data format.
`
`8.
`
`(Original) The method of claim 7, wherein the pre—defined data format is a format
`
`that allows a plurality of key—value pairs.
`
`9.
`
`(Original) The method of claim 7, wherein the pre—defined data format is J SON.
`
`10.
`
`(Currently Amended) The method of claim 1, wherein nt—lenst—one—of—the—mobi—le
`
`event—nonfientions—eoni-ptises—an—enent—desetipton the event descriptor describing incl-hiding at
`
`
`least one of an app lifecycle event, [[an]] a user engagement event, a behavior event, or a user
`
`location event, and the event descriptor including a timestamp.
`
`ll.
`
`(Currently Amended) A mobile event streaming system, comprising:
`
`a processor;
`
`a memory configured to store instructions, the instructions, when executed by the
`
`processor, cause the processor to:
`
`receive, by a computing server mobile-enent—strennnng—systena, a plurality of
`
`mobile event notifications from a plurality of event source devices, oneh—of
`
`the—pl-uta—l—ity—of a particular mobile event notification noti-f-ientions
`
`generated in response to an action associated with one of the plurality of
`
`event source devices, eneh—of—the—phatal-ity—mobi—le—event—notifientions the
`
`

`

`particular mobile event notification comprising a—mess—age—t—h-at—eempfises
`
`(i) an event descriptor describing the event action, gii) a particular
`
`destination address associated with a message publisher, and giii) a tag
`
`trigger that is associated an automated message set by the message
`
`publisher;
`
`filter, by the computing server mobile-event—strea—mi—ng—system, the plurality of
`
`mobile event notifications including the particular mobile event
`
`notification based on one or more criteria specified by the message
`
`publisher and based on destination addresses included in the plurality of
`
`mobile event notifications= filtered mobile event notifications including
`
`the particular mobile event notification generated in response to the action
`
`a—system—eustemer;
`
`generate, by the computing server mobile-event—strea-mi-n-g—system, a plurality of
`
`
`
`data objects that comprise filtered information of events the-event
`
`descriptors transmitted from the plurality of event source devices extracted
`
`from the filtered mobile event notifications;
`
`transmit, by the computing server and based on the tag trigger remained in the
`
`filtered information: the automated message set by the message publisher
`
`to the one of the event source devices; and
`
`
`
`transmit, by the computing server mobile-event—strea-ming—system, the plurality of
`
`
`data objects comprising filtered information of the events to a data store,
`
`

`

`the data store accessible by message publisher event—descriptors
`
`
`
`12.
`
`(Original) The mobile event streaming system of claim 11, wherein the
`
`instructions further cause the processor to:
`
`decorate the filtered plurality of mobile event notifications with one or more metadata
`
`tags.
`
`13.
`
`(Original) The mobile event streaming system of claim 12, wherein the generated
`
`plurality of data objects further comprise the metadata tags.
`
`14.
`
`(Currently Amended) The mobile event streaming system of claim 11, wherein
`
`the action associated with ene—ef—t-he—pl-u-ra—l—i-t—y—ef the particular mobile event notification is an
`
`action performed by a user when using [[the]] a mobile application.
`
`15.
`
`(Currently Amended) The mobile event streaming system of claim 11, wherein
`
`the action associated with ene—ef—t-he—pl-u-ra—l—i-t—y—ef the particular mobile event notification is
`
`associated with an application lifecycle event.
`
`16.
`
`(Currently Amended) The mobile event streaming system of claim 11, wherein
`
`the action associated with ene—ef—t-he—pl-u-ra—l—i-t—y—ef the particular mobile event notification is
`
`associated with a user engagement event.
`
`17.
`
`(Original) The mobile event streaming system of claim 11, wherein the data
`
`objects are in a pre—defined data format.
`
`

`

`18.
`
`(Original) The mobile event streaming system of claim 17, wherein the pre—
`
`defined data format is a format that allows a plurality of key—value pairs.
`
`19.
`
`(Original) The mobile event streaming system of claim 17, wherein the pre—
`
`defined data format is J S ON.
`
`20.
`
`(Currently Amended) The mobile event streaming system of claim ll, wherein at
`
` the event descriptor
`
`describing i-nel-ud-i—ng at least one of [[an]] a app lifecycle event, an user engagement event, a
`
`
`behavior event, or a user location event, and the event descriptor including a timestamp.
`
`

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.

We are unable to display this document.

PTO Denying Access

Refresh this Document
Go to the Docket