US20100138501A1 - End-to-end validation in a push environment - Google Patents

End-to-end validation in a push environment Download PDF

Info

Publication number
US20100138501A1
US20100138501A1 US12327484 US32748408A US2010138501A1 US 20100138501 A1 US20100138501 A1 US 20100138501A1 US 12327484 US12327484 US 12327484 US 32748408 A US32748408 A US 32748408A US 2010138501 A1 US2010138501 A1 US 2010138501A1
Authority
US
Grant status
Application
Patent type
Prior art keywords
application
gateway
endpoint
device
timeout
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US12327484
Inventor
Nathaniel T. Clinton
Adam Sapek
Johannes Klein
Farookh Mohammed
Rashid Qureshi
Shai Herzog
Eric David Deily
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Microsoft Technology Licensing LLC
Original Assignee
Microsoft Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00Digital computers in general; Data processing equipment in general
    • G06F15/16Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs

Abstract

In a push environment having a communication path along which a service provides messages to a computing device via a gateway, an inactivity timeout value and a registration timeout value enable the computing device to detect failures in the communication path. An application executing on the computing device registers an application endpoint with the gateway. The application separately subscribes to the service to receive the messages. If there is inactivity in accordance with the inactivity timeout value, the application de-registers and re-registers with the gateway, and unsubscribes and re-subscribes with the service.

Description

    BACKGROUND
  • [0001]
    Mobile devices receive data asynchronously from a variety of sources. The data is pushed to the mobile devices and includes updates to online user profiles (e.g., at social networking web sites), weather and traffic conditions, and notifications such as package delivery notifications. Existing systems include a plurality of services sending the data through a plurality of gateways to the mobile devices. However, existing systems fail to provide a mechanism in the push environment for detecting failures along the communication path to the mobile devices.
  • SUMMARY
  • [0002]
    Embodiments of the invention provide end-to-end validation along a communication path involving a service, a gateway, and a computing device. A component executing on the computing device receives a request from an application to register an application endpoint. The component registers the application endpoint with the gateway responsive to the received request. The application subscribes to the service. The gateway defines an inactivity timeout value for the application endpoint, and monitors the communication path. When the component receives a notification from the gateway of expiration of the inactivity timeout value, the component notifies the application to re-register with the gateway and to re-subscribe with the service.
  • [0003]
    This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • [0004]
    FIG. 1 is an exemplary block diagram illustrating a push environment having a communication path from a service to a gateway to a computing device.
  • [0005]
    FIG. 2 is an exemplary sequence diagram illustrating application endpoint registration and subscription.
  • [0006]
    FIG. 3 is an exemplary flow chart illustrating operation of failure detection and resolution.
  • [0007]
    FIG. 4 is an exemplary sequence diagram illustrating detection of a gateway failure.
  • [0008]
    FIG. 5 is an exemplary sequence diagram illustrating detection of a loss of connectivity between the application and the gateway.
  • [0009]
    FIG. 6 is an exemplary sequence diagram illustrating detection of a computing device failure.
  • [0010]
    FIG. 7 is an exemplary sequence diagram illustrating detection of a failure of the service.
  • [0011]
    FIG. 8 is an exemplary block diagram illustrating a computing device storing computer-executable components for implementing failure detection in a push environment.
  • [0012]
    Corresponding reference characters indicate corresponding parts throughout the drawings.
  • DETAILED DESCRIPTION
  • [0013]
    Referring to the figures, embodiments of the disclosure enable end-to-end validation in a push environment. In an exemplary push environment such as illustrated in FIG. 1, one or more services 102 push messages to at least one gateway 106. The gateway 106 delivers the messages to a computing device 104. The message flow is unidirectional in that the messages are sent by the services 102 to an application 108 via the gateway 106. In the push environment, detecting a failure along the communication path is difficult. Embodiments of the invention provide an inactivity timeout value and a registration timeout value. These timeout values are used to determine when a failure has occurred along the communication path. The computing device 104 may then re-establish the connection.
  • [0014]
    The service 102 is any type of service that pushes content to the computing device 104. For example, the service 102 may include an email server, a sales server, a web server, a database server, a file server, a print server, or any other kind of server.
  • [0015]
    The messages include any kind of information or data such as text messages, electronic mail messages, voice messages, images, and video. The computing device 104 can be a mobile telephone, a portable media player, a smartphone, a personal digital assistant, an information appliance, a personal communicator, a handheld game console, an ultra-mobile personal computer, a handheld television, or any other type of electronic device that is able to communicate with another system through a network.
  • [0016]
    In some embodiment, there are a plurality of services 102, a plurality of gateways 106, and a plurality of computing devices 104. The computing device 104 has at least one application 108 executing thereon. The application 108 has one or more application endpoints 110 for receipt of the messages. The application endpoints 110 are associated with, for example, a mail application program, an instant messaging application program, or a web browser. The computing device 104 has at least one push component or pipe component for interfacing between the gateway 106 and the application 108. In some embodiments, there is one push client 112 for each application 108. In other embodiments, there is one push client 112 for all the applications 108 executing on the computing device 104.
  • [0017]
    In the example of FIG. 1, the gateway 106 has access to a message buffer 114. The message buffer 114 stores messages received from the services 102. For example, the gateway 106 may queue messages until the messages may be delivered to the computing device 104. In this manner, the messages are persisted during computing device 104 offline periods. In addition, the computing device 104 may move between gateways 106 without losing queued messages. In some embodiments, the message buffer 114 is shared by multiple instances of the gateway 106.
  • [0018]
    Referring next to FIG. 2, an exemplary sequence diagram illustrates application endpoint 110 registration and subscription. Registration includes establishing a bi-directional communication link between the computing device 104 and the gateway 106 such that the gateway 106 forwards messages from the services 102 to the computing device 104. In the example of FIG. 2, the application 108 creates an endpoint with the push client 112. The push client 112 registers the created endpoint with the gateway 106.
  • [0019]
    In some embodiments, registration includes receiving, by the push client 112, a request from the application 108 to register the application endpoint 110 (e.g., RegisterEndpoint). The push client 112 identifies one or more channels available for communication and selects one of the identified channels. The push client 112 works with the gateway 106 to define an object, address space, or other globally unique identifier such as an endpoint uniform resource identifier (URI) for the selected channel, and provides the defined object to the application 108. In some examples, the channel is selected based on one or more policy settings for the application 108. Alternatively, the gateway 106 provides the object to the push client 112 to give to the application 108.
  • [0020]
    The push client 112 registers the application endpoint 110 with the gateway 106, and provides the object to the application 108. The application 108 uses the object to subscribe with the service 102. Additionally, the application 108 or the push client 112 defines a registration timeout value. The registration timeout value includes, for example, a maximum time in seconds for a message to be received by the application 108 after requesting registration from the push client 112. The push client 112, or the application 108, calculates an elapsed time since, for example, the registration request was submitted to the push client 112. If the elapsed time exceeds or violates the registration timeout value before a first message is received by the application 108, the application 108 is notified of a registration failure or timeout condition. Responsive to the notification, the application 108 de-registers and unsubscribes, then subsequently re-registers and subscribes. For example, the application 108 may re-register with another gateway 106.
  • [0021]
    Responsive to the registration, the application 108 receives the object such as a uniform resource locator (URL) or other address space from the gateway 106. The object identifies the gateway 106 and the computing device 104. The computing device 104 subscribes to receive messages from the service 102. This subscription occurs separate from, or independent, exclusive, or outside of the gateway 106. In other words, the subscription occurs directly between the application 108 and the service 102 without involvement of the gateway 106. During subscription, the application 108 communicates the object to the service 102 and requests that the messages be sent to the application 108 via the object.
  • [0022]
    The object may be any type of identifier that can identify the gateway 106. In one example, the URL has the following exemplary format: {Gateway Domain Name Server Name}/{Computing Device Name}/{Application Name}/{Extension}. The first portion “Gateway Domain Name Server Name” is the domain name of the gateway 106 in the Domain Name System (DNS). The first portion tells the service 102 where to send the message (e.g. to the gateway 106). The second portion “Client Name” tells the gateway 106 which computing device 104 to receive the message. The third portion “Application Name” tells the computing device 104 which application 108 executing on the computing device 104 to receive it. The fourth portion “Extension” is an extension of the application 108. The “Extension” is optional. One particular example of the object includes PushGW.xyz.com/Client 123/App456/doc.
  • [0023]
    After or during registration, the application 108 or gateway 106 defines an inactivity timeout value for the application endpoint 110. The inactivity timeout value represents a maximum time in seconds between receipt of messages from the service 102. In an example, the application 108 provides the inactivity timeout value to the gateway 106. The gateway 106 monitors the communication path. If there is no activity by the gateway 106 for that application endpoint 110 after the inactivity timeout value expires, the gateway 106 notifies the push client 112 or the application 108 of the timeout condition. In some embodiments, to avoid the timeout expiring absent of communication failure, the service 102 sends periodic “heartbeat” messages to the gateway 106. Such messages are not delivered to the application endpoint 110 (e.g., to save device resources) and serve to confirm liveliness of the application endpoint 110. In such embodiments, the service 102 knows the inactivity timeout value so that the service 102 can time the heartbeat messages to be more frequent than the timeout. The service 102 may learn the inactivity timeout value as part of subscription.
  • [0024]
    Exemplary application programming interfaces for implementing registration and other functions are described in Appendix A.
  • [0025]
    Referring next to FIG. 3, an exemplary flow chart illustrates operation of failure detection and resolution by the application 108 in concert with the push client 112. The application 108 receives messages when the messages become available at the push client 112, so long as the endpoint is working. A non-working endpoint is detected using the timeouts (e.g., registration and inactivity) as described herein. In a non-working push system, there is not any channel to any known gateway working. If the endpoint is not working and the push system is not working, the application 108 displays an error to the user or attempts to connect directly to the service 102. If the endpoint is not working yet the push system is working, the application 108 unsubscribes from the service 102, de-registers the application endpoint 110, re-registers a new application endpoint 110, and re-subscribes to the service 102.
  • [0026]
    Referring next to FIG. 4, an exemplary sequence diagram illustrates detection of a gateway 106 failure. In the example of FIG. 4, one of the gateways 106 has failed or crashed. When the gateway 106 recovers, or another gateway 106 takes over, the inactivity timeout value has expired because the gateway 106 missed messages from the service 102 when the gateway 106 was offline after the crash. The gateway 106 notifies the push client 112, which prompts the application 108 to unsubscribe from the service 102, de-register the application endpoint 110, re-register the application endpoint 110, and re-subscribe to the service 102.
  • [0027]
    Referring next to FIG. 5, an exemplary sequence diagram illustrates detection of a loss of connectivity between the application 108 and the gateway 106. A connectivity problem lasting more than a channel timeout value may result in a state of the application endpoint 110 being removed from the gateway 106 and the object being invalidated. In this example, the push client 112 queries the status of the registered application endpoint 110. Because the state of the application endpoint 110 has been removed, the gateway 106 informs the push client 112 that the endpoint is invalid. Subsequently, the application 108 re-registers the application endpoint 110 and notifies the service 102 about the re-registered application endpoint 110.
  • [0028]
    In some embodiments, the channel timeout value detects whether the device 104 is interested in the registered application endpoint 110. If the device 104 gets disconnected (e.g., due to a general packet radio service disruption), the channel/endpoint is still maintained on the gateway 106, provided the push client 112 re-establishes the connection within the channel timeout interval. However, if the push client 112 unregisters the application endpoint 110 and the request is not delivered or processed by the gateway 106, this mechanism allows the gateway 106 to clean up the state (e.g., remove the channel and associated queue) after the channel timeout value interval and conserve memory.
  • [0029]
    If the channel timeout value is longer than the inactivity timeout value, the device 104 may be offline for a longer period of time (e.g., up to the channel timeout value) and the gateway 106 queues messages to the device 104 in the buffer. However, the application 108 does not learn about the potential failure of communication for a longer period of time.
  • [0030]
    If the channel timeout value is set to the same value as the inactivity timeout value, the push client 112 provides a guarantee to the application 108 that if any communication failure (e.g., be it on the channel between the device 104 and the gateway 106 or between the gateway 106 and the service 102) lasts more than the channel timeout value, the application 108 is notified and can initiate a recover sequence.
  • [0031]
    Referring next to FIG. 6, an exemplary sequence diagram illustrates detection of a computing device failure. In the example of FIG. 6, the push client 112 does not receive messages from the gateway 106. After the expiration of the channel timeout value, the application endpoint 110 and state are deleted.
  • [0032]
    Referring next to FIG. 7, an exemplary sequence diagram illustrates detection of a failure of the service 102. After the expiration of the inactivity timeout value, the gateway 106 notifies the push client 112 of the service 102 failure. Subsequently, the application 108 unsubscribes from the service 102, de-registers with the gateway 106, re-registers the application endpoint 110, and re-subscribes to the service 102.
  • [0033]
    Referring next to FIG. 8, an exemplary block diagram illustrates the computing device 104 storing computer-executable components for implementing failure detection in a push environment. In the example of FIG. 8, the computing device 104 includes a processor 802 and a memory area 804. The memory area 804 stores data 806 defining one or more communication paths between the computing device 104 and the service 102. The memory area 804 further stores a communication component 808, a registration component 810, a timeout component 812, and an inactivity component 814. The communication component 808 interfaces, or facilitates data exchange, between the computing device 104 and the gateway 106. The registration component 810 registers the application endpoint 110 with the gateway 106. The timeout component 812 monitors the registration by the registration component 810. The timeout component 812 notifies the application 108 of a timeout condition after a predefined period of inactivity (e.g., based on the registration timeout value). After a successful registration, the inactivity component 814 receives a notice of inactivity from the gateway 106 if the inactivity timeout value maintained by the gateway 106 expires (e.g., if the service 102 crashed). The inactivity component 814 notifies the application 108 of the inactivity responsive to the received notice of inactivity. Responsive to the notification from the inactivity component 814, the application 108 re-registers the application endpoint 110 and re-subscribes with the service 102.
  • [0034]
    Aspects of the invention transform a general-purpose computer into a special-purpose computing device when configured to execute the instructions described herein.
  • [0035]
    While aspects of the invention are described with reference to the computing device 104 being a mobile computing device such as a mobile telephone, embodiments of the invention are operable with any computing device. For example, aspects of the invention are operable with devices such as laptop computers, gaming consoles, hand-held or vehicle-mounted navigation devices, portable music players, and other devices.
  • Exemplary Operating Environment
  • [0036]
    By way of example and not limitation, computer readable media comprise computer storage media and communication media. Computer storage media store information such as computer readable instructions, data structures, program modules or other data. Communication media typically embody computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and include any information delivery media. Combinations of any of the above are also included within the scope of computer readable media.
  • [0037]
    Although described in connection with an exemplary computing system environment, embodiments of the invention are operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use with aspects of the invention include, but are not limited to, mobile computing devices, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, gaming consoles, microprocessor-based systems, set top boxes, programmable consumer electronics, mobile telephones, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
  • [0038]
    Embodiments of the invention may be described in the general context of computer-executable instructions, such as program modules, executed by one or more computers or other devices. The computer-executable instructions may be organized into one or more computer-executable components or modules. Generally, program modules include, but are not limited to, routines, programs, objects, components, and data structures that perform particular tasks or implement particular abstract data types. Aspects of the invention may be implemented with any number and organization of such components or modules. For example, aspects of the invention are not limited to the specific computer-executable instructions or the specific components or modules illustrated in the figures and described herein. Other embodiments of the invention may include different computer-executable instructions or components having more or less functionality than illustrated and described herein.
  • [0039]
    The embodiments illustrated and described herein as well as embodiments not specifically described herein but within the scope of aspects of the invention constitute exemplary means for identifying a communication failure based on the inactivity timeout value, and exemplary means for re-establishing the communication path responsive to expiration of the inactivity timeout value.
  • [0040]
    The order of execution or performance of the operations in embodiments of the invention illustrated and described herein is not essential, unless otherwise specified. That is, the operations may be performed in any order, unless otherwise specified, and embodiments of the invention may include additional or fewer operations than those disclosed herein. For example, it is contemplated that executing or performing a particular operation before, contemporaneously with, or after another operation is within the scope of aspects of the invention.
  • [0041]
    When introducing elements of aspects of the invention or the embodiments thereof, the articles “a,” “an,” “the,” and “said” are intended to mean that there are one or more of the elements. The terms “comprising,” “including,” and “having” are intended to be inclusive and mean that there may be additional elements other than the listed elements.
  • [0042]
    Having described aspects of the invention in detail, it will be apparent that modifications and variations are possible without departing from the scope of aspects of the invention as defined in the appended claims. As various changes could be made in the above constructions, products, and methods without departing from the scope of aspects of the invention, it is intended that all matter contained in the above description and shown in the accompanying drawings shall be interpreted as illustrative and not in a limiting sense.
  • Appendix A
  • [0043]
    Exemplary application programming interfaces (API) are described below.
  • CreateEndpoint
  • [0044]
    Creates object representing endpoint. Until the endpoint is registered, no communication with gateway is established and no state on the gateway is created.
  • [0000]
    [out] hEndpoint
  • SetEndpointOption
  • [0045]
    Sets endpoint settings. The API may be called at any endpoint state, however since most options apply only to active endpoints, setting may not take effect until endpoint is registered. All options have reasonable defaults that may differ for different channels/gateways.
  • [0000]
    [in] hEndpoint
    [in] Option Type
    [in] blobOption—a structure containing option parameters as specified in the table below.
  • [0000]
    TABLE A1
    Option Parameters.
    Option type Description Parameters
    SUPRESS_MESSAGE This option allows applications to unsigned Bitmap-32 bit bitmap
    suppress messages based on specifying which classes of messages to
    message class. Suppressed be rejected by the gateway. Note that
    messages are dropped by the class 0 used for idle messages from
    gateway. The setting can be Application Server to gateway and is
    changed at any time and takes suppressed.
    effect immediately of the endpoint Default is 0 (all messages are accepted).
    is active.
    FRIENDLY_NAME This option can be used by the string Name-human readable name of
    gateway for logging, reports, the endpoint
    troubleshooting, etc. Default is generated by Push Client (e.g.,
    The setting takes effect when the it may be derived from the friendly name
    endpoint is registered. of the application account, on other OS
    versions it can be name of the
    executable).
    LIFETIME Specifies how long the gateway unsigned Lifetime-time in seconds
    keeps the endpoint when the Default is selected by the channel.
    device is unreachable. This is a
    hint from application and
    channel/gateway may override it.
    The setting takes effect when the
    endpoint is registered.
    DELIVERY_PARAMS Allows applications to fine tune MessageClass-specifies message class
    delivery parameters for different for which the parameters are set.
    message classes. Most unsigned Delay-maximum batching
    applications will not change these delay, in second, for messages in
    settings. The settings are treated specified class.
    as hints and can be ignored by the unsigned Burst-maximum burst for
    channel/gateway or overridden by messages in specified class.
    device policy. Defaults are set by the channel such that
    Device policy may limit valid classes 1-9 will provide real time
    ranges for each parameter delivery, 10-21 will be delayed by
    separately for each message class. several minutes and 22-31 may be
    delayed by up to an hour.

    RegisterEndpoint [async]
  • [0046]
    Establishes communication channel between the device and the gateway, allocates endpoint state on the gateway and returns endpoint URL to the appliation. The URL is generated by the channel/gateway.
  • [0047]
    Registered endpoint does not guarantee end-to-end from service to device. If service is not able to reach the device using the endpoint, application may unregister and register the endpoint. The Push Client will first try to use a different gateway and then different channel if the previous one was unreachable.
  • [0048]
    The API is asynchronous and the call returns immediately as pending. The Push Client performs registration in the background and notifies application when the process completes. The application can then obtain the endpoint URL. Application may cancel pending registrations at any time by calling UnregisterEndpoint or CloseEndpoint.
  • [0049]
    The call fails with ALREADY_REGISTERED error if the endpoint is already registered or RegisterEndpoint or RegisterStaticEndpoint call is pending.
  • [0000]
    [in] hEndpoint
  • [0050]
    [in, optional] strApplicationServer—name of Application Server that is authorized to send messages to the endpoint. Application Server will need to authenticate using SSL mutual authentication in order to send a message to the endpoint.
  • [0051]
    If not specified, endpoint will not require Application Server to authenticate. If endpoints w/o authentication are not supported, the registration will fail
  • [0052]
    [in, optional] nEndToEnd Verification Timeout—maximum time in seconds for the first message to arrive to the endpoint. If initial message does not arrive within specified time the endpoint is considered invalid and application is notified. 0 means no timeout. If not specified, default is 120 seconds.
  • [0053]
    [in] nInactivity Timeout—maximum time in seconds between massages. If endpoint is inactive for longer than the specified time the endpoint is considered invalid and application is notified. 0 means no timeout. If not specified, default is 0.
  • [0054]
    [out] strEndpointURL—URL representing registered endpoints. If strApplicationServer was not specified then the endpoint does not require authentication and the URL itself includes the authorization ticket and MUST NOT be transmitted in the clear.
  • [0000]
    RegisterStaticEndpoint [async]
  • [0055]
    Establishes communication channel between the device and the gateway and registers device with a static endpoint. Unlike RegisterEndpoint, this API does not return endpoint URL. Static endpoints URLs are predictable (or discoverable through the gateway) and thus do not need to be communicated by the application to the Application Server.
  • [0056]
    Static endpoints do not support initialization and inactivity timeouts. Lifetime of static endpoint is fully controlled by the channel/gateway. Application will be notified when endpoint is deleted by the gateway.
  • [0057]
    The API is asynchronous and the call returns immediately as pending. The Push Client performs registration in the background and notifies application when the process completes. Application may cancel pending registrations at any time by calling UnregisterEndpoint or CloseEndpoint.
  • [0058]
    The call fails with ALREADY_REGISTERED error if the endpoint is already registered or RegisterEndpoint or RegisterStaticEndpoint call is pending.
  • [0000]
    [in] hEndpoint
  • [0059]
    [in] strChannel—identifies channel used to register the static endpoint. Static endpoints can be only registered on a specific channel and are discoverable through the gateway on which they are registered.
  • [0060]
    [in] strApplication—unique identifier of application. If a static endpoint with this identifier is already registered on the device, the call will fail.
  • DeregisterEndpoint
  • [0061]
    Deregisters the endpoint on the gateway and dereferences the channel connection. The API is synchronous and call completes immediately although the actual deregistration with the gateway will be completed asynchronously (e.g. in particular when device does not have connectivity with the gateway, deregistration will be pending until connection is reestablished). Application is not notified about completion of deregistration. Pending deregistration is not associated with the local endpoint object (hEndpoint) and the endpoint can be reregistered immediately after the API returns. The Push Client service must be able to handle several pending deregistration requests however it may drop deregistration requests that cannot be completed after some time since the gateway will independently cleanup endpoint state for an unreachable device anyways.
  • [0000]
    [in] hEndpoint
  • CloseEndpoint
  • [0062]
    Performs DeregisterEndpoint, if necessary, and destroys the local endpoint object.
  • [0000]
    [in] hEndpoint
    GetEndpointNotification [async]
  • [0063]
    Returns notification associated with the endpoint when available. There are two types of notifications:
  • [0064]
    1. MESSAGE—push message(s) are queued and available for retrieval using GetEndpointMessage.
  • [0065]
    2. STATUS—endpoint status has changed since the last time application checked it using GetEndpointStatus.
  • [0066]
    The API is asynchronous. The call returns immediately as pending and application is notified of completion when a notification is available. After processing the notification application calls GetEndpointNotification again. Only one outstanding call to GetEndpointNotification is allowed; the API will fail if there is already a pending call.
  • [0000]
    [in] hEndpoint
  • [0067]
    [in] dwNotificationsRequested—bitmap indicating which notification types (MESSAGE and/or STATUS) the application is interested in.
  • [0068]
    [out] dwNotificationsAvailable—bitmap indicating which notifications are available.
  • GetEndpointMessage
  • [0069]
    Retrieves message from local endpoint queue. If there are no messages in the queue, the API returns appropriate error code.
  • [0000]
    [in] hEndpoint
    [out] blobMessage
  • GetEndpointStatus
  • [0070]
    Returns status of the endpoint. Status changes are not queued and only current status is returned.
  • [0000]
    [in] hEndpoint
  • [0071]
    [out] Status—structure describing endpoint status:
  • [0000]
    struct EnpointStatus
    {
    bool bEndpointWorking; // true if endpoint is working
    bool bPushSystemWorking; // true if any of the channels are working
    FailureReason Reason; // set when bEndpointWorking is false
    time LastMessageTimestamp;
    };
    enum FailureReason
    {
    Invalid, // endpoint hasn't received initial message w/o specified
    timeframe
    Inactive, // endpoint was inactive for longer than specified timeframe
    Disconnected,// device lost channel connectivity and thus can't reach gateway
    Deleted // gateway doesn't recognize the endpoint
    };

Claims (20)

  1. 1. A system for end-to-end validation in a push environment including a service sending messages to a gateway for delivery to a mobile computing device, said system comprising:
    a memory area for storing data defining a communication path between the mobile computing device and the service, said mobile computing device configured to receive messages from the service via the gateway; and
    a processor programmed to:
    receive a request from an application to register an application endpoint, said application executing on the mobile computing device;
    register the application endpoint with the gateway responsive to the received request, wherein the gateway defines an inactivity timeout value for the application endpoint, wherein the gateway monitors the communication path, and wherein the application subscribes the application endpoint to receive the messages from the service;
    subsequently receive a notification from the gateway when the inactivity timeout value expires based on the monitored communication path; and
    notify the application of the received notification, wherein the application re-registers the application endpoint with the gateway and re-subscribes with the service to receive the messages.
  2. 2. The system of claim 1, wherein the processor is further configured to:
    receive the inactivity timeout value from the application for the application endpoint; and
    provide the received inactivity timeout value to the gateway.
  3. 3. The system of claim 1, wherein the processor is configured to register the application endpoint by:
    identifying one or more channels available for communication;
    selecting one of the identified channels;
    defining an object for the selected channel; and
    providing the defined object to the application;
  4. 4. The system of claim 3, wherein the processor is configured to select said one of the identified channels based on one or more policy settings for the application.
  5. 5. The system of claim 1, wherein the processor is further configured to receive a uniform resource locator from the gateway for the application endpoint.
  6. 6. The system of claim 1, wherein the inactivity timeout value represents a maximum time in seconds between receipt of messages from the service.
  7. 7. The system of claim 1, wherein the processor is further configured to de-register the application endpoint responsive to the received notification from the gateway.
  8. 8. The system of claim 1, further comprising means for identifying a communication failure based on the inactivity timeout value.
  9. 9. The system of claim 1, further comprising means for re-establishing the communication path responsive to expiration of the inactivity timeout value.
  10. 10. A method comprising:
    receiving a request from an application to register an application endpoint, said application executing on a computing device, said computing device configured to receive messages from a service via a gateway;
    registering the application endpoint with the gateway responsive to the received request, wherein the gateway defines a registration timeout value, and wherein the application subscribes the application endpoint to receive the messages from the service;
    calculating, relative to a current time, an elapsed time since said receiving; and
    notifying the application of a timeout condition when the calculated elapsed time exceeds the registration timeout value without one of the messages being received from the service, wherein the application re-registers the application endpoint and re-subscribes with the service responsive to said notifying to receive the messages.
  11. 11. The method of claim 10, wherein the gateway defines the registration timeout value as a maximum time in seconds for a message to arrive at the application endpoint after said receiving.
  12. 12. The method of claim 10, further comprising receiving a request from the application to register the application endpoint with another gateway responsive to the notification of a timeout condition.
  13. 13. The method of claim 10, wherein a unidirectional message flow exists from the service to the gateway to the computing device.
  14. 14. The method of claim 10, further comprising de-registering the application endpoint with the gateway responsive to said notifying.
  15. 15. The method of claim 10, wherein the application unsubscribes from the service responsive to said notifying.
  16. 16. One or more computer-readable media having computer-executable components, said components comprising:
    a communication component for interfacing between a computing device and a gateway, said computing device configured to receive messages from a service via the gateway;
    a registration component for registering an application endpoint with the gateway, said application endpoint being associated with an application executing on the computing device, wherein the application subscribes with the service to receive the messages;
    a timeout component for monitoring the registration by the registration component, wherein the timeout component notifies the application of a timeout condition after a predefined period of inactivity responsive to the registering by the registration component; and
    an inactivity component for receiving notice of inactivity from the gateway after expiration of an inactivity timeout value maintained by the gateway, wherein the inactivity component notifies the application of the inactivity responsive to the received notice of inactivity.
  17. 17. The computer-readable media of claim 16, wherein the application re-registers the application endpoint and re-subscribes with the service responsive to the notification from the inactivity component.
  18. 18. The computer-readable media of claim 16, wherein a unidirectional message flow exists from the service to the gateway to the computing device.
  19. 19. The computer-readable media of claim 16, wherein the application endpoint comprises a uniform resource locator referencing the application.
  20. 20. The computer-readable media of claim 16, wherein the application communicates with the service outside of the gateway to subscribe to the messages.
US12327484 2008-12-03 2008-12-03 End-to-end validation in a push environment Abandoned US20100138501A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12327484 US20100138501A1 (en) 2008-12-03 2008-12-03 End-to-end validation in a push environment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US12327484 US20100138501A1 (en) 2008-12-03 2008-12-03 End-to-end validation in a push environment

Publications (1)

Publication Number Publication Date
US20100138501A1 true true US20100138501A1 (en) 2010-06-03

Family

ID=42223776

Family Applications (1)

Application Number Title Priority Date Filing Date
US12327484 Abandoned US20100138501A1 (en) 2008-12-03 2008-12-03 End-to-end validation in a push environment

Country Status (1)

Country Link
US (1) US20100138501A1 (en)

Cited By (62)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110289172A1 (en) * 2009-02-25 2011-11-24 Apple Inc. Managing notification messages
US20120278475A1 (en) * 2011-04-28 2012-11-01 Matthew Nicholas Papakipos Managing Notifications Pushed to User Devices
US20120324022A1 (en) * 2011-06-14 2012-12-20 Lowry Adam C Push gateway systems and methods
US20130047034A1 (en) * 2011-08-17 2013-02-21 Lookout, Inc., A California Corporation System and method for mobile device push communications
US8407776B2 (en) 2011-02-11 2013-03-26 Good Technology Corporation Method, apparatus and system for provisioning a push notification session
US20130144954A1 (en) * 2010-07-30 2013-06-06 Huawei Technologies Co., Ltd. Method and Apparatus for Cooperation Between Push Devices
US20130198381A1 (en) * 2012-01-30 2013-08-01 International Business Machines Corporation Optimizing Data Extraction from Distributed Systems into a Unified Event Aggregator Using Time-Outs
US8554855B1 (en) 2011-06-14 2013-10-08 Urban Airship, Inc. Push notification delivery system
US8649768B1 (en) * 2011-08-24 2014-02-11 Cellco Partnership Method of device authentication and application registration in a push communication framework
US8676238B2 (en) 2008-06-02 2014-03-18 Apple Inc. Managing notification messages
WO2014068182A1 (en) * 2012-10-31 2014-05-08 Nokia Corporation Method and apparatus for providing application notifications
US8731523B1 (en) * 2011-06-14 2014-05-20 Urban Airship, Inc. Push notification delivery system with feedback analysis
US20140148205A1 (en) * 2012-11-27 2014-05-29 Alcatel-Lucent Canada Inc. Push service without persistent tcp connection in a mobile network
US20140324972A1 (en) * 2013-04-28 2014-10-30 Tencent Technology (Shenzhen) Company Limited Method, Server, User Terminal, and System For Pushing Notification Message
US20140325506A1 (en) * 2013-04-24 2014-10-30 QRC, Inc. dba QRC Technologies, Inc. System and Method for RF Digitization and Collection
US8881292B2 (en) 2008-10-21 2014-11-04 Lookout, Inc. Evaluating whether data is safe or malicious
US8997181B2 (en) 2008-10-21 2015-03-31 Lookout, Inc. Assessing the security state of a mobile communications device
US20150120805A1 (en) * 2013-10-24 2015-04-30 Sap Ag Bi-directional Channel-based Progress Indicator
US20150131651A1 (en) * 2013-11-12 2015-05-14 Twilio, Inc. System and method for client communication in a distributed telephony network
US9130935B2 (en) 2011-05-05 2015-09-08 Good Technology Corporation System and method for providing access credentials
US9208215B2 (en) 2012-12-27 2015-12-08 Lookout, Inc. User classification based on data gathered from a computing device
US9215074B2 (en) 2012-06-05 2015-12-15 Lookout, Inc. Expressing intent to control behavior of application components
US9294500B2 (en) 2008-10-21 2016-03-22 Lookout, Inc. System and method for creating and applying categorization-based policy to secure a mobile communications device from access to certain data objects
US9374369B2 (en) 2012-12-28 2016-06-21 Lookout, Inc. Multi-factor authentication and comprehensive login system for client-server networks
US9408143B2 (en) 2012-10-26 2016-08-02 Lookout, Inc. System and method for using context models to control operation of a mobile communications device
US9424409B2 (en) 2013-01-10 2016-08-23 Lookout, Inc. Method and system for protecting privacy and enhancing security on an electronic device
US9456008B2 (en) 2008-04-02 2016-09-27 Twilio, Inc. System and method for processing telephony sessions
US9455949B2 (en) 2011-02-04 2016-09-27 Twilio, Inc. Method for processing telephony sessions of a network
US9459925B2 (en) 2010-06-23 2016-10-04 Twilio, Inc. System and method for managing a computing cluster
US9459926B2 (en) 2010-06-23 2016-10-04 Twilio, Inc. System and method for managing a computing cluster
US9477975B2 (en) 2015-02-03 2016-10-25 Twilio, Inc. System and method for a media intelligence platform
US9483328B2 (en) 2013-07-19 2016-11-01 Twilio, Inc. System and method for delivering application content
US9491309B2 (en) 2009-10-07 2016-11-08 Twilio, Inc. System and method for running a multi-module telephony application
US9495227B2 (en) 2012-02-10 2016-11-15 Twilio, Inc. System and method for managing concurrent events
US9509782B2 (en) 2014-10-21 2016-11-29 Twilio, Inc. System and method for providing a micro-services communication platform
US9531827B1 (en) 2011-06-14 2016-12-27 Urban Airship, Inc. Push notification delivery system with feedback analysis
US9529417B2 (en) 2011-04-28 2016-12-27 Facebook, Inc. Performing selected operations using low power-consuming processors on user devices
US9553900B2 (en) 2014-07-07 2017-01-24 Twilio, Inc. System and method for managing conferencing in a distributed communication network
US9589129B2 (en) 2012-06-05 2017-03-07 Lookout, Inc. Determining source of side-loaded software
US9591033B2 (en) 2008-04-02 2017-03-07 Twilio, Inc. System and method for processing media requests during telephony sessions
US9588974B2 (en) 2014-07-07 2017-03-07 Twilio, Inc. Method and system for applying data retention policies in a computing platform
US9590849B2 (en) 2010-06-23 2017-03-07 Twilio, Inc. System and method for managing a computing cluster
US9602586B2 (en) 2012-05-09 2017-03-21 Twilio, Inc. System and method for managing media in a distributed communication network
US9614972B2 (en) 2012-07-24 2017-04-04 Twilio, Inc. Method and system for preventing illicit use of a telephony platform
US9621733B2 (en) 2009-03-02 2017-04-11 Twilio, Inc. Method and system for a multitenancy telephone network
US9628624B2 (en) 2014-03-14 2017-04-18 Twilio, Inc. System and method for a work distribution service
US9642008B2 (en) 2013-10-25 2017-05-02 Lookout, Inc. System and method for creating and assigning a policy for a mobile communications device based on personal data
US9641677B2 (en) 2011-09-21 2017-05-02 Twilio, Inc. System and method for determining and communicating presence information
US9648006B2 (en) 2011-05-23 2017-05-09 Twilio, Inc. System and method for communicating with a client application
US9654647B2 (en) 2012-10-15 2017-05-16 Twilio, Inc. System and method for routing communications
US9753796B2 (en) 2013-12-06 2017-09-05 Lookout, Inc. Distributed monitoring, evaluation, and response for multiple devices
US9774687B2 (en) 2014-07-07 2017-09-26 Twilio, Inc. System and method for managing media and signaling in a communication platform
US9807244B2 (en) 2008-10-01 2017-10-31 Twilio, Inc. Telephony web event system and method
US9811398B2 (en) 2013-09-17 2017-11-07 Twilio, Inc. System and method for tagging and tracking events of an application platform
US9853872B2 (en) 2013-09-17 2017-12-26 Twilio, Inc. System and method for providing communication platform metadata
US9860263B2 (en) 2008-10-21 2018-01-02 Lookout, Inc. System and method for assessing data objects on mobile communications devices
US9907010B2 (en) 2014-04-17 2018-02-27 Twilio, Inc. System and method for enabling multi-modal communication
US9948703B2 (en) 2015-05-14 2018-04-17 Twilio, Inc. System and method for signaling through data storage
US9955352B2 (en) 2009-02-17 2018-04-24 Lookout, Inc. Methods and systems for addressing mobile communications devices that are lost or stolen but not yet reported as such
US9967224B2 (en) 2010-06-25 2018-05-08 Twilio, Inc. System and method for enabling real-time eventing
US9992608B2 (en) 2013-06-19 2018-06-05 Twilio, Inc. System and method for providing a communication endpoint information service
US10003693B2 (en) 2017-03-06 2018-06-19 Twilio, Inc. System and method for a work distribution service

Citations (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6226762B1 (en) * 1998-04-20 2001-05-01 National Instruments Corporation System and method for providing delayed start-up of an activity monitor in a distributed I/O system
US20030076808A1 (en) * 1998-09-17 2003-04-24 Mcniff Peter Gerald System and method for mobile computing device registration with a service node
US20040012769A1 (en) * 2001-05-15 2004-01-22 Shinichiro Murakami Use charge calculation system, method, program, and computer-readable recording medium
US20040117339A1 (en) * 2002-12-13 2004-06-17 Pascal Thubert Arrangement in a router of a mobile network for optimizing use of messages carrying reverse routing headers
US20050111441A1 (en) * 2001-08-24 2005-05-26 Petri Koskelainen Service mobility and recovery in communication networks
US6917612B2 (en) * 2000-09-01 2005-07-12 Telefonaktiebolaged L M Ericsson System and method for address resolution in internet protocol (IP)-based networks
US7020717B1 (en) * 1999-09-29 2006-03-28 Harris-Exigent, Inc. System and method for resynchronizing interprocess communications connection between consumer and publisher applications by using a shared state memory among message topic server and message routers
US20060187916A1 (en) * 2005-02-23 2006-08-24 Jean-Philippe Vasseur Methods and apparatus based on message transmission times
US20070064886A1 (en) * 2005-08-26 2007-03-22 Tekelec Methods, systems, and computer program products for dynamically controlling a PSTN network element from an IP network element using signaling
US20070254677A1 (en) * 2006-05-01 2007-11-01 Motorola, Inc. Method and system to enable paging for mobile ip nodes
US20080096597A1 (en) * 2004-04-21 2008-04-24 Brahmananda Vempati Providing Push-to-Talk Communications in a Telecommunications Network
US20080109529A1 (en) * 2006-11-06 2008-05-08 Audible Method and apparatus for targeted content delivery
US20080250484A1 (en) * 2001-12-28 2008-10-09 Chong Lester J System and method for content filtering
US20080313331A1 (en) * 2007-06-12 2008-12-18 Boykin James R Managing Computer Resources In A Distributed Computing System
US20100042674A1 (en) * 2008-08-15 2010-02-18 Sony Ericsson Mobile Communications Ab Method and system for discovery of dynamic ip addresses
US7751807B2 (en) * 2007-02-12 2010-07-06 Oomble, Inc. Method and system for a hosted mobile management service architecture
US7860981B1 (en) * 2006-09-29 2010-12-28 Juniper Networks, Inc. Systems and methods for IP session keepalive using BFD protocols
US7961703B2 (en) * 2006-11-30 2011-06-14 Research In Motion Limited System and method for maintaining packet protocol context

Patent Citations (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6226762B1 (en) * 1998-04-20 2001-05-01 National Instruments Corporation System and method for providing delayed start-up of an activity monitor in a distributed I/O system
US20030076808A1 (en) * 1998-09-17 2003-04-24 Mcniff Peter Gerald System and method for mobile computing device registration with a service node
US7130296B2 (en) * 1998-09-17 2006-10-31 Openwave Systems Inc. System and method for mobile computing device registration with a service node
US7020717B1 (en) * 1999-09-29 2006-03-28 Harris-Exigent, Inc. System and method for resynchronizing interprocess communications connection between consumer and publisher applications by using a shared state memory among message topic server and message routers
US6917612B2 (en) * 2000-09-01 2005-07-12 Telefonaktiebolaged L M Ericsson System and method for address resolution in internet protocol (IP)-based networks
US20040012769A1 (en) * 2001-05-15 2004-01-22 Shinichiro Murakami Use charge calculation system, method, program, and computer-readable recording medium
US20050111441A1 (en) * 2001-08-24 2005-05-26 Petri Koskelainen Service mobility and recovery in communication networks
US20080250484A1 (en) * 2001-12-28 2008-10-09 Chong Lester J System and method for content filtering
US20040117339A1 (en) * 2002-12-13 2004-06-17 Pascal Thubert Arrangement in a router of a mobile network for optimizing use of messages carrying reverse routing headers
US20080096597A1 (en) * 2004-04-21 2008-04-24 Brahmananda Vempati Providing Push-to-Talk Communications in a Telecommunications Network
US20060187916A1 (en) * 2005-02-23 2006-08-24 Jean-Philippe Vasseur Methods and apparatus based on message transmission times
US20070064886A1 (en) * 2005-08-26 2007-03-22 Tekelec Methods, systems, and computer program products for dynamically controlling a PSTN network element from an IP network element using signaling
US20070254677A1 (en) * 2006-05-01 2007-11-01 Motorola, Inc. Method and system to enable paging for mobile ip nodes
US7860981B1 (en) * 2006-09-29 2010-12-28 Juniper Networks, Inc. Systems and methods for IP session keepalive using BFD protocols
US20080109529A1 (en) * 2006-11-06 2008-05-08 Audible Method and apparatus for targeted content delivery
US7961703B2 (en) * 2006-11-30 2011-06-14 Research In Motion Limited System and method for maintaining packet protocol context
US7751807B2 (en) * 2007-02-12 2010-07-06 Oomble, Inc. Method and system for a hosted mobile management service architecture
US20080313331A1 (en) * 2007-06-12 2008-12-18 Boykin James R Managing Computer Resources In A Distributed Computing System
US20100042674A1 (en) * 2008-08-15 2010-02-18 Sony Ericsson Mobile Communications Ab Method and system for discovery of dynamic ip addresses

Cited By (106)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9456008B2 (en) 2008-04-02 2016-09-27 Twilio, Inc. System and method for processing telephony sessions
US9591033B2 (en) 2008-04-02 2017-03-07 Twilio, Inc. System and method for processing media requests during telephony sessions
US9596274B2 (en) 2008-04-02 2017-03-14 Twilio, Inc. System and method for processing telephony sessions
US9906651B2 (en) 2008-04-02 2018-02-27 Twilio, Inc. System and method for processing media requests during telephony sessions
US9906571B2 (en) 2008-04-02 2018-02-27 Twilio, Inc. System and method for processing telephony sessions
US8676238B2 (en) 2008-06-02 2014-03-18 Apple Inc. Managing notification messages
US9807244B2 (en) 2008-10-01 2017-10-31 Twilio, Inc. Telephony web event system and method
US8997181B2 (en) 2008-10-21 2015-03-31 Lookout, Inc. Assessing the security state of a mobile communications device
US9223973B2 (en) 2008-10-21 2015-12-29 Lookout, Inc. System and method for attack and malware prevention
US9294500B2 (en) 2008-10-21 2016-03-22 Lookout, Inc. System and method for creating and applying categorization-based policy to secure a mobile communications device from access to certain data objects
US9407640B2 (en) 2008-10-21 2016-08-02 Lookout, Inc. Assessing a security state of a mobile communications device to determine access to specific tasks
US9860263B2 (en) 2008-10-21 2018-01-02 Lookout, Inc. System and method for assessing data objects on mobile communications devices
US8881292B2 (en) 2008-10-21 2014-11-04 Lookout, Inc. Evaluating whether data is safe or malicious
US9955352B2 (en) 2009-02-17 2018-04-24 Lookout, Inc. Methods and systems for addressing mobile communications devices that are lost or stolen but not yet reported as such
US8630624B2 (en) * 2009-02-25 2014-01-14 Apple Inc. Managing notification messages
US9485208B2 (en) * 2009-02-25 2016-11-01 Apple Inc. Managing notification messages
US20170041273A1 (en) * 2009-02-25 2017-02-09 Apple Inc. Managing Notification Messages
US9985917B2 (en) * 2009-02-25 2018-05-29 Apple Inc. Managing notification messages
US20140164541A1 (en) * 2009-02-25 2014-06-12 Apple Inc. Managing notification messages
US20110289172A1 (en) * 2009-02-25 2011-11-24 Apple Inc. Managing notification messages
US9894212B2 (en) 2009-03-02 2018-02-13 Twilio, Inc. Method and system for a multitenancy telephone network
US9621733B2 (en) 2009-03-02 2017-04-11 Twilio, Inc. Method and system for a multitenancy telephone network
US9491309B2 (en) 2009-10-07 2016-11-08 Twilio, Inc. System and method for running a multi-module telephony application
US9459925B2 (en) 2010-06-23 2016-10-04 Twilio, Inc. System and method for managing a computing cluster
US9459926B2 (en) 2010-06-23 2016-10-04 Twilio, Inc. System and method for managing a computing cluster
US9590849B2 (en) 2010-06-23 2017-03-07 Twilio, Inc. System and method for managing a computing cluster
US9967224B2 (en) 2010-06-25 2018-05-08 Twilio, Inc. System and method for enabling real-time eventing
US20130144954A1 (en) * 2010-07-30 2013-06-06 Huawei Technologies Co., Ltd. Method and Apparatus for Cooperation Between Push Devices
US9247018B2 (en) * 2010-07-30 2016-01-26 Huawei Technologies Co., Ltd. Method and apparatus for cooperation between push devices
US9882942B2 (en) 2011-02-04 2018-01-30 Twilio, Inc. Method for processing telephony sessions of a network
US9455949B2 (en) 2011-02-04 2016-09-27 Twilio, Inc. Method for processing telephony sessions of a network
US8407776B2 (en) 2011-02-11 2013-03-26 Good Technology Corporation Method, apparatus and system for provisioning a push notification session
US8825842B2 (en) * 2011-04-28 2014-09-02 Facebook, Inc. Managing notifications pushed to user devices
US20120278475A1 (en) * 2011-04-28 2012-11-01 Matthew Nicholas Papakipos Managing Notifications Pushed to User Devices
US9628577B2 (en) * 2011-04-28 2017-04-18 Facebook, Inc. Managing notifications pushed to user devices
US20140330933A1 (en) * 2011-04-28 2014-11-06 Facebook, Inc. Managing Notifications Pushed to User Devices
US9237201B2 (en) * 2011-04-28 2016-01-12 Facebook, Inc. Managing notifications pushed to user devices
US20160072907A1 (en) * 2011-04-28 2016-03-10 Facebook, Inc. Managing Notifications Pushed to User Devices
US9529417B2 (en) 2011-04-28 2016-12-27 Facebook, Inc. Performing selected operations using low power-consuming processors on user devices
US9130935B2 (en) 2011-05-05 2015-09-08 Good Technology Corporation System and method for providing access credentials
US9648006B2 (en) 2011-05-23 2017-05-09 Twilio, Inc. System and method for communicating with a client application
US8731523B1 (en) * 2011-06-14 2014-05-20 Urban Airship, Inc. Push notification delivery system with feedback analysis
US9762690B2 (en) 2011-06-14 2017-09-12 Urban Airship, Inc. Push notification delivery system
US8423656B2 (en) * 2011-06-14 2013-04-16 Urban Airship, Inc. Push gateway systems and methods
US8572263B1 (en) 2011-06-14 2013-10-29 Urban Airship, Inc. Push gateway systems and methods
US20120324022A1 (en) * 2011-06-14 2012-12-20 Lowry Adam C Push gateway systems and methods
US8554855B1 (en) 2011-06-14 2013-10-08 Urban Airship, Inc. Push notification delivery system
US9277023B1 (en) 2011-06-14 2016-03-01 Urban Airship, Inc. Push notification delivery system with feedback analysis
US9531827B1 (en) 2011-06-14 2016-12-27 Urban Airship, Inc. Push notification delivery system with feedback analysis
CN103718578A (en) * 2011-08-01 2014-04-09 苹果公司 Managing notification messages
WO2013019708A3 (en) * 2011-08-01 2013-05-16 Apple Inc. Managing notification messages
KR101417722B1 (en) 2011-08-01 2014-07-08 애플 인크. Managing notification messages
JP2014527665A (en) * 2011-08-01 2014-10-16 アップル インコーポレイテッド Management of the notification message
US8788881B2 (en) * 2011-08-17 2014-07-22 Lookout, Inc. System and method for mobile device push communications
US20130047034A1 (en) * 2011-08-17 2013-02-21 Lookout, Inc., A California Corporation System and method for mobile device push communications
US8649768B1 (en) * 2011-08-24 2014-02-11 Cellco Partnership Method of device authentication and application registration in a push communication framework
US9037118B2 (en) 2011-08-24 2015-05-19 Cellco Partnership Method of device authentication and application registration in a push communication framework
US9641677B2 (en) 2011-09-21 2017-05-02 Twilio, Inc. System and method for determining and communicating presence information
US9942394B2 (en) 2011-09-21 2018-04-10 Twilio, Inc. System and method for determining and communicating presence information
US20130198381A1 (en) * 2012-01-30 2013-08-01 International Business Machines Corporation Optimizing Data Extraction from Distributed Systems into a Unified Event Aggregator Using Time-Outs
US9495227B2 (en) 2012-02-10 2016-11-15 Twilio, Inc. System and method for managing concurrent events
US9602586B2 (en) 2012-05-09 2017-03-21 Twilio, Inc. System and method for managing media in a distributed communication network
US9992025B2 (en) 2012-06-05 2018-06-05 Lookout, Inc. Monitoring installed applications on user devices
US9215074B2 (en) 2012-06-05 2015-12-15 Lookout, Inc. Expressing intent to control behavior of application components
US9589129B2 (en) 2012-06-05 2017-03-07 Lookout, Inc. Determining source of side-loaded software
US9940454B2 (en) 2012-06-05 2018-04-10 Lookout, Inc. Determining source of side-loaded software using signature of authorship
US9407443B2 (en) 2012-06-05 2016-08-02 Lookout, Inc. Component analysis of software applications on computing devices
US9948788B2 (en) 2012-07-24 2018-04-17 Twilio, Inc. Method and system for preventing illicit use of a telephony platform
US9614972B2 (en) 2012-07-24 2017-04-04 Twilio, Inc. Method and system for preventing illicit use of a telephony platform
US9654647B2 (en) 2012-10-15 2017-05-16 Twilio, Inc. System and method for routing communications
US9769749B2 (en) 2012-10-26 2017-09-19 Lookout, Inc. Modifying mobile device settings for resource conservation
US9408143B2 (en) 2012-10-26 2016-08-02 Lookout, Inc. System and method for using context models to control operation of a mobile communications device
WO2014068182A1 (en) * 2012-10-31 2014-05-08 Nokia Corporation Method and apparatus for providing application notifications
US9148765B2 (en) * 2012-11-27 2015-09-29 Alcatel Lucent Push service without persistent TCP connection in a mobile network
US20140148205A1 (en) * 2012-11-27 2014-05-29 Alcatel-Lucent Canada Inc. Push service without persistent tcp connection in a mobile network
US9208215B2 (en) 2012-12-27 2015-12-08 Lookout, Inc. User classification based on data gathered from a computing device
US9374369B2 (en) 2012-12-28 2016-06-21 Lookout, Inc. Multi-factor authentication and comprehensive login system for client-server networks
US9424409B2 (en) 2013-01-10 2016-08-23 Lookout, Inc. Method and system for protecting privacy and enhancing security on an electronic device
US20140325506A1 (en) * 2013-04-24 2014-10-30 QRC, Inc. dba QRC Technologies, Inc. System and Method for RF Digitization and Collection
US9348608B2 (en) * 2013-04-24 2016-05-24 QRC, Inc. System and method for registering application and application transforms on a radiofrequency digitization and collection device
US20140324972A1 (en) * 2013-04-28 2014-10-30 Tencent Technology (Shenzhen) Company Limited Method, Server, User Terminal, and System For Pushing Notification Message
US9826055B2 (en) * 2013-04-28 2017-11-21 Tencent Technology (Shenzhen) Company Limited Method, server, user terminal, and system for pushing notification message
US9992608B2 (en) 2013-06-19 2018-06-05 Twilio, Inc. System and method for providing a communication endpoint information service
US9483328B2 (en) 2013-07-19 2016-11-01 Twilio, Inc. System and method for delivering application content
US9959151B2 (en) 2013-09-17 2018-05-01 Twilio, Inc. System and method for tagging and tracking events of an application platform
US9853872B2 (en) 2013-09-17 2017-12-26 Twilio, Inc. System and method for providing communication platform metadata
US9811398B2 (en) 2013-09-17 2017-11-07 Twilio, Inc. System and method for tagging and tracking events of an application platform
US9774659B2 (en) * 2013-10-24 2017-09-26 Sap Se Bi-directional channel-based progress indicator
US20150120805A1 (en) * 2013-10-24 2015-04-30 Sap Ag Bi-directional Channel-based Progress Indicator
US9642008B2 (en) 2013-10-25 2017-05-02 Lookout, Inc. System and method for creating and assigning a policy for a mobile communications device based on personal data
US9553799B2 (en) * 2013-11-12 2017-01-24 Twilio, Inc. System and method for client communication in a distributed telephony network
US20150131651A1 (en) * 2013-11-12 2015-05-14 Twilio, Inc. System and method for client communication in a distributed telephony network
US9753796B2 (en) 2013-12-06 2017-09-05 Lookout, Inc. Distributed monitoring, evaluation, and response for multiple devices
US9628624B2 (en) 2014-03-14 2017-04-18 Twilio, Inc. System and method for a work distribution service
US9907010B2 (en) 2014-04-17 2018-02-27 Twilio, Inc. System and method for enabling multi-modal communication
US9588974B2 (en) 2014-07-07 2017-03-07 Twilio, Inc. Method and system for applying data retention policies in a computing platform
US9858279B2 (en) 2014-07-07 2018-01-02 Twilio, Inc. Method and system for applying data retention policies in a computing platform
US9774687B2 (en) 2014-07-07 2017-09-26 Twilio, Inc. System and method for managing media and signaling in a communication platform
US9553900B2 (en) 2014-07-07 2017-01-24 Twilio, Inc. System and method for managing conferencing in a distributed communication network
US9509782B2 (en) 2014-10-21 2016-11-29 Twilio, Inc. System and method for providing a micro-services communication platform
US9906607B2 (en) 2014-10-21 2018-02-27 Twilio, Inc. System and method for providing a micro-services communication platform
US9749428B2 (en) 2014-10-21 2017-08-29 Twilio, Inc. System and method for providing a network discovery service platform
US9477975B2 (en) 2015-02-03 2016-10-25 Twilio, Inc. System and method for a media intelligence platform
US9805399B2 (en) 2015-02-03 2017-10-31 Twilio, Inc. System and method for a media intelligence platform
US9948703B2 (en) 2015-05-14 2018-04-17 Twilio, Inc. System and method for signaling through data storage
US10003693B2 (en) 2017-03-06 2018-06-19 Twilio, Inc. System and method for a work distribution service

Similar Documents

Publication Publication Date Title
US6839737B1 (en) Messaging system for indicating status of a sender of electronic mail and method and computer program product therefor
US20040125941A1 (en) Presence enabled queue management
US8352546B1 (en) Contextual and location awareness for device interaction
US20030105800A1 (en) Dynamically routing messages between software application programs using named routing nodes and named message queues
US20080189421A1 (en) SIP and HTTP Convergence in Network Computing Environments
US20050235038A1 (en) Method of and apparatus for server-side management of buddy lists in presence based services provided by a communication system
US20060047742A1 (en) Method and apparatus to accomplish peer-to-peer application data routing between service consumers and service providers within a service oriented architecture
US20060242300A1 (en) Load balancing server and system
US7644171B2 (en) Mobile networking system and method using IPv4 and IPv6
US20080040441A1 (en) Push e-mail inferred network presence
US20080147551A1 (en) System and Method for a SIP Server with Online Charging
US20110167172A1 (en) Methods, systems and computer readable media for providing a failover measure using watcher information (winfo) architecture
US20070239884A1 (en) Apparatus, and associated method, for facilitating background processing of push content
US6981047B2 (en) Method and apparatus for providing mobile and other intermittent connectivity in a computing environment
US20090300162A1 (en) System and method for performing mobile services, in particular push services in a wireless communication
US9294391B1 (en) Managing network computing components utilizing request routing
US20050223115A1 (en) Method and apparatus for providing mobile and other intermittent connectivity in a computing environment
US20050223114A1 (en) Method and apparatus for providing mobile and other intermittent connectivity in a computing environment
US20060182255A1 (en) Resilient regisration with a call manager
US20100094985A1 (en) Http push to simulate server-initiated sessions
US20070197196A1 (en) Apparatus, and associated method, for facilitating delivery and processing of push content
US20100088371A1 (en) Method for obtaining device information of user terminals and communication service function entity
US20060009213A1 (en) Method and apparatus for providing mobile and other intermittent connectivity in a computing environment
US20020129103A1 (en) Instant messaging presence service protocol
US20060004924A1 (en) Method and system providing support for location and service category service discovery in a SIP environment using a SIP event package, forking and AOR registration

Legal Events

Date Code Title Description
AS Assignment

Owner name: MICROSOFT CORPORATION,WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CLINTON, NATHANIEL T.;SAPEK, ADAM;KLEIN, JOHANNES;AND OTHERS;SIGNING DATES FROM 20090203 TO 20090205;REEL/FRAME:022388/0258

AS Assignment

Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034766/0509

Effective date: 20141014