Application Data Sheet
`
`Application Information
`
`Application number::
`
`Not yet assigned
`
`Herewith
`
`Provisional
`
`Utility
`
`Filing Date::
`
`Application Type::
`
`Subject Matter::
`
`Suggested classification::
`
`Suggested Group Art Unit::
`
`CD-ROM or CD-R??::
`
`Number of CD disks::
`
`Number of copies of COs::
`
`Sequence Submission::
`
`Computer Readable Form (CRF)?::
`
`Number of copies of CRF::
`
`Title::
`
`ONE WAY INTELLIGENT HEARTBEAT
`
`Attorney Docket Number::
`
`028482-003700US
`
`Request for Early Publication::
`
`Request for Non-Publication::
`
`Suggested Drawing Figure::
`
`Total Drawing Sheets::
`
`Small Entity?::
`
`Latin name::
`
`Variety denomination name::
`
`Petition included?::
`
`Petition Type::
`
`Licensed US Govt. Agency::
`
`Contract or Grant Numbers One::
`
`No
`
`No
`
`1
`
`4
`
`yes
`
`No
`
`Secrecy Order in Parent Appl.::
`
`No
`
`Page 1
`
`lnitial11/1/10
`
`Page 1 of 47
`
`GOOGLE EXHIBIT 1014
`
`

`

`Applicant Information
`
`Applicant Authority Type::
`
`Primary Citizenship Country::
`Status::
`
`Given Name::
`
`Middle Name::
`
`Family Name::
`
`Name Suffix::
`
`Inventor
`
`Finland
`Full Capacity
`
`Mikko
`
`Tervahauta
`
`City of Residence::
`
`San Francisco
`
`State or Province of Residence::
`
`Country of Residence::
`
`Street of Mailing Address::
`
`City of Mailing Address::
`
`CA
`
`US
`
`2015 Castro St.
`
`San Francisco
`
`State or Province of mailing address:: CA
`
`Country of mailing address::
`
`US
`
`Postal or Zip Code of mailing address:: 94131
`
`Correspondence Information
`
`Correspondence Customer Number::
`
`20350
`
`Representative Information
`
`Representative Customer Number::
`
`20350
`
`Domestic Priority Information
`
`Application::
`
`Continuity Type::
`
`Parent Application:: Parent Filing Date::
`
`Foreign Priority Information
`
`Country::
`
`Application number::
`
`Filing Date::
`
`Page 2
`
`Initial 11/1/10
`
`Page 2 of 47
`
`

`

`Assignee Information
`
`Assignee Name::
`
`Street of mailing address::
`
`City of mailing address::
`
`State or Province of mailing address::
`
`Country of mailing address::
`
`Postal or Zip Code of mailing address::
`
`Submitted by:
`
`Signature ______ ....;/A__;,I;.:_a.;,.:.n-=D....:..._M_i_ns_kl ____ _
`
`Date November 1, 2010
`
`Printed Name
`
`Alan D. Minsk
`--------------------
`
`Registration Number
`
`35,956
`
`Page 3
`
`lnitial11/1/10
`
`Page 3 of 47
`
`

`

`Attorney Docket No.: 028482-003700
`
`PROVISIONAL PATENT APPLICATION
`
`ONE WAY INTELLIGENT HEARTBEAT
`
`Inventor:
`
`Mikko Tervahauta, a citizen of Finland, residing at San Francisco,
`
`CA, 94131
`
`Assignee:
`
`Seven Networks
`
`Entity:
`
`Small
`
`TOWNSEND and TOWNSEND and CREW LLP
`Two Embarcadero Center, Eighth Floor
`San Francisco, CA 94111-3 834
`Tel: 415-576-0200
`
`1
`
`Page 4 of 47
`
`

`

`ONE WAY INTELLIGENT HEARTBEAT
`
`In the art today there are performance enhancing proxies and general standards for
`
`improvements of TCP performance in wired and wireless networks. Some of these techniques
`
`use clients and some are clientless. Some can look at network performance to enhance the
`
`optimization they provide. As noted, some may utilize a client and some may operate clientless.
`
`Almost all, if not all, are focused on optimization based on only a one-sided view of the
`
`networks connected to such a platform- either outbound wired, inbound/outbound wireless, or
`
`based solely on the cooperation with a client.
`
`The present invention is directed to enabling a client device to detect the health of a
`
`server side component (a:nd vice versa) when attempting to limit or eliminate IP signaling
`
`between the client and server.
`
`Heartbeat and some other forms of connection keep-alive mechanisms are known and
`
`used in the communications industry. A periodic message can be sent, or implied from messages
`
`sent between two entities. As long as these messages arrive on-time, each entity can assume that
`
`the other is properly functional (i.e., healthy, operative, etc.).
`
`However, when attempting to limit the use of a radio channel in mobile networks (e.g., to
`
`increase mobile device battery life, reduce congestion or signaling, etc.) simple heartbeat
`
`messages can have the opposite effect on the system -that is, if they are sent too often the radio
`
`channel will be activated too often, or if they are sent using alternative channels such as SMS
`
`they could result in too many expensive (to either the operator or the user) messages that are
`
`system overhead. Therefore, as recognized by the inventor(s), an effective means of generating
`
`and exchanging a heartbeat, indicating a functional/operational state of a component, or
`
`otherwise causing a network connection to be maintained between the functional components, is
`
`needed.
`
`2
`
`Page 5 of 47
`
`

`

`Description of One or More Embodiments of the Invention
`
`Embodiments of the present invention provide a system that optimizes multiple aspects of
`
`the connection with wired and wireless networks and devices through a complete view of activity
`
`including: loading, current application needs on a client, controlling the type of access (push vs.
`
`pull or hybrid), location, concentration of users in a single area, time of day, how often the user
`
`interacts with the application, content or device, and using this information to shape traffic to a
`
`cooperative client/server or simultaneously mobile devices without a cooperative client. Because
`
`the inventive server is not tied to any specific network provider it has visibility into the network
`
`performance across all service providers. This enables optimizations to be applied to devices
`
`regardless of the operator or service provider, thereby enhancing the user experience and
`
`managing network utilization while roaming. Bandwidth has been considered the major issue in
`
`wireless networks today. More and more research has been done related to the need for
`
`additional bandwidth to solve access problems- many of the performance enhancing solutions
`
`and next generation standards, such as L TE and WiMAX are focused on providing increased
`
`bandwidth. However, history has shown that this simply doesn't solve all the problems. A key
`
`problem is lack of bandwidth on the signaling channel more so than the data channel.
`
`Embodiments of the present invention align requests from multiple applications to
`
`minimize the need for several polling requests; leverage specific content types to determine how
`
`to proxy/manage a connection/content; and apply specific heuristics associated with device, user
`
`behavioral patterns (how often they interact with the device/application) and network parameters.
`
`Embodiments of the present invention move recurring http polls done by various widgets,
`
`RSS readers etc. to a fixed internet (NOC), thus considerably lowering device battery/power
`
`consumption, radio channel signaling, and bandwidth usage. Additionally, embodiments ofthe
`
`present invention do this transparently so that existing applications do not need to be changed. In
`
`some embodiments, this can be done by implementing a local proxy on the device which
`
`automatically detects recurring requests for the same content (RSS feed, Widget data set) that
`
`matches a specific rule (e.g. happens every 15 minutes) and automatically caches the content on
`
`3
`
`Page 6 of 47
`
`

`

`the client while delegating the polling to the server (e.g., to a proxy or virtual proxy operated as
`
`an element of a communications network). The server would then notify the mobile/client proxy
`
`if the content changes, and if content has not changed (or not changed sufficiently, or in an
`
`identified manner or amount) the mobile proxy provides the latest version in its cache to the user
`
`, (without need to utilize the radio at all). This way the mobile device (e.g., a handset) does not
`
`need to open up or use a data connection if the request is for content that is monitored and that
`
`has been not flagged as new/changed.
`
`The logic for automatically adding URLs/content to be monitored can check for various
`
`factors like how often the content is the same, how often the same request is made (is there a
`
`fixed interval/pattern?), which application is requesting the data, etc. Similar rules to skip using
`
`the cache and request the data from the original source may also be used. For example, when the
`
`request comes at an unscheduled/unexpected time (user initiated check), or after every (n)
`
`consecutive times the response has been provided from the cache, etc., or if the application is
`
`running in the background vs. in a more interactive mode of the foreground. As more and more
`
`mobile applications base their features on resources available in the network, this becomes
`
`increasingly important. Embodiments of the present invention also remove unnecessary chatter
`
`from the network, benefitting the operators trying to optimize the wireless spectrum usage.
`
`In some embodiments, the present invention includes a distributed proxy for network
`
`traffic optimization, as shown in Figure 1. The main components include a proxy client running
`
`on a device [105], a proxy server running in the network [102], and an internal protocol between
`
`the proxy client and the proxy server [1 09, 11 0]. Typically, the proxy client and proxy server
`
`would be implemented as a set of instructions executed by a (micro) processor, although other
`
`implementations are possible (firmware, etc.). The proxy client, shown in Figure 2, includes
`
`connection management functionality [206], application protocol logic modules [213], a local
`
`cache [203], and an interface to retrieve information on device properties (e.g., information on
`
`device battery level, whether the device is being actively used or not, and the registered network)
`
`[210]. The proxy server, shown in Figure 3, includes connection management functionality
`
`[302], application protocol logic modules [31 0], a connection and content metadata database
`
`[303], and a device information database [304].
`
`4
`
`Page 7 of 47
`
`

`

`In general operation, the proxy client [202] is an application independent proxy that
`
`mobile applications [200] can use to open any TCP connection to any host. The proxy client will
`
`detect the type of traffic and utilize an appropriate application protocol module [213] to process
`
`the traffic. With the chosen protocol/logic module, the proxy client may process the data locally
`
`and generate necessary talkback communication using its local cache, communicate the
`
`processed data along with device properties to the proxy server using the internal protocol [11 0],
`
`modify or delay any data before sending it to the proxy server, detect usage patterns between
`
`similar connections and provide this to the proxy server as connection metadata, or any
`
`combination of the above.
`
`If the proxy server is contacted regarding processing the original connection, the proxy
`
`server will utilize an appropriate application protocol module [31 0] to process the traffic. With
`
`the chosen protocol/logic module, the proxy server may contact the intended target of the
`
`connection and route the data from the proxy client to the target, generate talkback
`
`communication using its local cache, modify or delay any talkback communication data based on
`
`the device properties, and based on the connection metadata, start background processing to
`
`gather data for later use with similar connections, as well as any combination of the above.
`
`Both the proxy client and the proxy server will, where applicable continue to observe and
`
`process the data using the application protocol modules for the entire duration of the connection.
`
`After the original connection no longer exists, the proxy client and proxy server may still share
`
`information about the ceased connection and its properties for later use with similar connections.
`
`In this mode of operation, the proxy server may signal the proxy client that some data in its local
`
`cache is no longer up to date (and hence is stale), or alternatively pre-load the client cache with
`
`the fresh data. This can be done in bulk to avoid multiple radio requests, or on an application by
`
`application basis.
`
`From a mobile application's [200] point of view, the proxy is transparent and no
`
`modifications are needed in the way the application uses the connections. Proxy-aware mobile
`
`applications [212] may also be implemented, and can provide additional information about the
`
`connection characteristics to the proxy client.
`
`5
`
`Page 8 of 47
`
`

`

`In some embodiments, the present invention offers benefits with respect to network
`
`usage, in that by serving requests from the local cache, the proxy client reduces the number of
`
`requests that are done over the wireless network. Further, the proxy client and the proxy server
`
`may filter irrelevant data from the communicated data. The proxy client and the proxy server
`
`may also accumulate low priority data and send it in batches to avoid the protocol overhead of
`
`sending individual data fragments. The proxy client and the proxy server may compress or
`
`transcode the traffic, reducing the amount of data sent over a wireless network. The signaling
`
`traffic in a wireless network is reduced, as the wireless network is used less often by optimizing
`
`small bursts away and the network traffic can be synchronized among individual applications.
`
`With respect to the battery life of a mobile device, by serving requests from the local
`
`cache, the proxy client reduces the number of times the radio module is powered up. The proxy
`
`client and the proxy server may accumulate low priority data and send it in batches to reduce the
`
`number oftimes and/or amount oftime when the radio is powered up. The proxy client may
`
`synchronize the network usage by performing the hatched data transfer for all connections
`
`simultaneously.
`
`In some embodiments, the present invention may be used in the case of home screen
`
`widget polling for data using HTTP, as shown in Figure 4. In the normal flow of operation, the
`
`widget performs a HTTP request to the data provider server [405, 406]. If the data has been
`
`updated, the widget refreshes itself. The widget waits for a small period of time and starts over at
`
`the initial step. With respect to using a distributed proxy, the widget performs a HTTP request
`
`via the proxy client [ 407, 408]. The proxy client detects the connection type to be a HTTP GET
`
`request. The proxy client checks the local cache for any previous information about the request.
`
`If the locally stored response is not available, the client updates all information about the
`
`request and the time it was made for later use. The client sends the request to the proxy server
`
`and the server performs the request and returns the results. The client stores information about
`
`the result and returns the result to the requestor. If the same request has occurred multiple times
`
`(within a certain time period) and it has often yielded same results, the client notifies the proxy
`
`6
`
`Page 9 of 47
`
`

`

`server that the request should be monitored for result changes [409]. If the request was marked
`
`for monitoring, the client will store the results into its local cache. If the locally stored response
`
`is available, the client will return the response from the local cache without performing
`
`communication over the wireless network [413].
`
`Independently of the widget or client operation, the server proxy will perform the
`
`requests marked for monitoring to see whether the response has changed [ 41 0]. Whenever an
`
`unexpected response is received for some request, the server will notify the client that the
`
`response has changed and that the locally stored response on the client should be erased or
`
`replaced with a new response [ 416]. A subsequent data request by the client results in the data
`
`being returned from the proxy server [ 417, 418]. A benefit of using the distributed proxy in this
`
`case is that the wireless network is only used whenever the content for the widget has actually
`
`changed; the traffic required to check for the changes is not done over the wireless network. This
`
`reduces the amount of generated network traffic and shortens the total time and the number of
`
`times the radio module is powered up on the mobile device, thus reducing battery consumption.
`
`With respect to polling for changes in a mailbox, in the normal flow of operation, the
`
`mail client opens a connection to the mail server, the mail client authenticates with the server and
`
`queries for new email, and if new mail has arrived, a notification is shown. The mail client then
`
`closes the connection. The mail client waits for a period of time and starts over. A variation is to
`
`leave the connection open and start over at the second step after a predetermined period of time.
`
`In the context of a distributed proxy, the mail client opens a connection to the mail server
`
`via the proxy client, the proxy client detects the traffic type and the chosen application logic
`
`module simulates a mail server authentication, and the proxy client looks up from the local
`
`database whether information about the particular mail connection is available. If the information
`
`is not available, the connection is routed to the proxy server, the proxy server establishes a
`
`connection to the mail server and performs authentication using the data from the mail client, the
`
`data between the mail client and the mail server is directly routed through the proxy connection,
`
`and when the mail client closes the connection, the proxy client may choose to leave the actual
`
`connection to the backend open and store information about the connection into the local
`
`7
`
`Page 10 of 47
`
`

`

`database for later use if the same mail connection has been used frequently. If the information is
`
`available, the client proxy will continue to simulate mail server responses for the mail client for
`
`all queries for which it has the data available. If the mail client performs an operation that cannot
`
`be simulated by the proxy client, the proxy client will route the data to the proxy server and the
`
`proxy server will pass the data to the mail server and route the data between the two. The proxy
`
`server may need to re-establish the connection to the mail server at this point. When the mail
`
`client closes the connection, the proxy client may choose to continue to store information about
`
`the connection for later use or it may request the proxy server to terminate the mail server
`
`connection and remove any information about the connection from the database.
`
`Independently of the mail client or the proxy client, the proxy server will query the mail
`
`server for any changes that the mail client has previously queried. If any information in the mail
`
`server has changed, the proxy server will notify the proxy client to stop simulating any responses
`
`based on locally cached data in order to let the mail client receive the changed data from the mail
`
`server.
`
`Embodiments of the present invention mitigate application protocol keep-alive traffic.
`
`Existing application protocols may provide long lived connections that allow servers to push
`
`updated data to the client without the need of the client to periodically re-establish the
`
`connection or to periodically query for changes. However, the client needs to be sure that the
`
`connection remains usable by periodically sending some data, often called a keep-alive message,
`
`to the server and making sure the server is receiving this data. While the amount of data sent for
`
`a single keep alive message is not significant and the keep-alive interval for an individual
`
`application is not too short, the cumulative effect of multiple applications performing this
`
`operation individually will amount to small pieces of data being sent very frequently. Frequently
`
`sending bursts of data in a wireless network results in high battery consumption by a mobile
`
`device due to the constant need of powering the radio module. Each burst will also require a
`
`significant amount of signaling traffic in a wireless network compared to the actual data being
`
`sent. By using the inventive distributed proxy model, the proxy client can prevent the keep-alive
`
`messages (or at least many of them) from being sent over the network and the proxy server can
`
`independently generate the required keep-alive messages to maintain the actual backend
`
`connection.
`
`8
`
`Page 11 of 47
`
`

`

`In alternative embodiments, the proxy client can be implemented directly into the TCPIIP
`
`stack of the device operating system. The proxy client can be bundled into a wireless modem to
`
`provide transparent use for the device operating system. The proxy client can also be bundled
`
`into a firewall or a router to provide transparent use for the device operating system.
`
`Alternative embodiments apply similar techniques for a variety of protocols including
`
`HTTP, HTTPS, IMAP, POP, SMTP and ActiveSync. Use of application specific protocol
`
`handlers allows for optimization of any protocol that can be port mapped to a hander in the
`
`distributed proxy.
`
`One Way Intelligent Heartbeat
`
`As recognized by the inventor(s), by understanding the rate of client-side requests and the
`
`rate of change in the source data that is being monitored by the virtual proxy it is possible (on the
`
`server-side) to develop a variable value for a time interval used to control the generation of a
`
`heartbeat (or similar signaling or keep alive message), where the time interval of the invention is
`
`proportional to the average rate of change of the content that is being monitored. The interval
`
`may be adjusted dynamically, for example, being initially based on the criticality and polling rate
`
`of the specific set of URI's (e.g., links, web-sites, content locations) being monitored, but later
`
`being based on the rate of changes in the data being monitored.
`
`As further recognized by the inventor(s), using a local proxy to manage signaling and
`
`other network congestion in mobile networks can be very effective but may create a potential
`
`problem ofblocking all IP traffic and disabling any access to content if both the client side and
`
`the server side of the virtual proxy are not operational and properly functional (i.e., healthy,
`
`operative, etc.).
`
`In some embodiments, the heartbeat interval may be communicated with every heartbeat
`
`message and every cache update message. During radio access quiet time (when the radio is
`
`dormant) if an alternative channel is available (such as SMS, or a form of signaling or control
`
`9
`
`Page 12 of 47
`
`

`

`channel) the heartbeat can be delivered using the alternative channel. This has the beneficial
`
`impact of increasing device battery life and reducing network congestion by limiting the need to
`
`bring the radio channel into an active mode to communicate system overhead messages (such as
`
`the heartbeat message or interval).
`
`Initially, the heartbeat interval may be based on a polling rate. For example, assume there
`
`are multiple resources being polled on the server side with different polling intervals. The first
`
`heartbeat interval may be based on the smallest (shortest) polling interval and is communicated
`
`to the client in the acknowledgement to the last polling request. In some embodiments, the
`
`interval can be configured so that it is 0.5, 1 or 2 (or N) times the smallest polling interval.
`
`In addition to the average communication (e.g., polling) rate, determining when to
`
`generate a heartbeat may also need to consider the average deviation of the communication rate.
`
`Preferably, this should happen as soon as the server starts communicating content changes to the
`
`client side. Assume the time interval between two communication events from server to client is
`
`identified as (t), with tavg being the average value of such interval. The average deviation of the
`
`actual intervals from tavg is davg ..
`
`In this scenario, using the concept of "trust" or reliance on the server's health and proper
`
`operation and functioning:
`
`• The client should have full trust of the server until the time from previous communication
`
`reaches tavg .
`• The client should have adequate trust of the server until the time reaches tavg + davg.
`
`In some embodiments, beyond this point the delay from a previous communication becomes
`
`exceptionally (or at least unacceptably) long, and the server should send a heartbeat message (or
`
`similar form of communication) to maintain the client's trust in the server's health (e.g., its
`
`proper functional and/or operational status).
`
`In practice, once the client receives a heartbeat from the server, it should set its
`
`expectation for the next communication event based on the timestamp in the heartbeat message,
`
`10
`
`Page 13 of 47
`
`

`

`not on the historical rate of changes which were driven by the actual data sources. The fact that a
`
`heartbeat gets sent means that there was a sufficient change in the rate of changes and the server
`
`is sending the heartbeat message(s) to bridge the gap.
`
`As mentioned, typically the interval between a last data communication and a first
`
`heartbeat message should be based on statistics of the communication intervals in the past. But in
`
`some embodiments of the invention, immediately after sending a first heartbeat message the
`
`server should start increasing that interval relatively aggressively. This may be because:
`
`(1) If there has really been a dramatic change in the average rate of communication from
`
`server to client, then the server should adapt to the new level with as few heartbeat messages as
`
`possible; and
`
`(2) If there hasn't been a real change in the rate of communication and the heartbeat was
`
`sent out due to a random spike in the interval value, then the algorithm should reset the interval
`
`with the first data package going out.
`
`In some embodiments, an aggressive increase in the heartbeat interval means multiplying
`
`the current heartbeat interval with a constant, not adding a constant value on top of it. This
`
`makes the growth exponential instead oflinear and is a fast yet predictable way of bridging the
`
`gap. Delivering the heartbeat is preferably done in a manner that causes minimal impact on the
`
`device's battery life and on the signaling/data load of the mobile network. When the device radio
`
`is dormant and there is no existing data channel between the server and the client, the heartbeat
`
`may be delivered using an alternative channel such as SMS or a signaling or control channel.
`
`11
`
`Page 14 of 47
`
`

`

`ONE WAY INTELLIGENT HEARTBEAT
`
`What is claimed is:
`
`1.
`
`A method of determining an interval for sending a heartbeat message between a
`
`client and a server, comprising:
`
`determining an initial value for the interval, the initial value based on a shortest
`
`polling interval used by the server for a service requested by the client;
`
`determining an average value for communication events between the server and
`
`the client;
`
`determining a value for a deviation of the average value;
`
`generating a heartbeat message at the server for communication to the client when
`
`there has been no communication event for a period equal to a sum of the average value and the
`
`standard deviation; and
`
`altering the initial value of the interval to be a sum of the average value and the
`
`standard deviation.
`
`12
`
`Page 15 of 47
`
`

`

`[106]
`
`Caching Web
`Proxy [101]
`
`[108]
`
`SEVEN
`Traffic Harmonizer
`Server [102]
`
`SMSC [103]
`
`~
`(106] \
`
`\
`
`[110]
`
`~ [109]
`Radio Access Network [104]" )...---
`_;;--·
`~
`[106] ~ [110] t ~[109]
`~\
`
`-
`
`Mobile Clients
`[105]
`
`I
`
`I
`Figure 1 SEVEN Network Harmonizer System Architecture
`
`13
`
`Page 16 of 47
`
`

`

`Proxy-Unaware
`Mobile
`Application
`[200]
`
`Proxy-Aware Mobile
`Application
`[212]
`
`J!k
`
`Caching
`Policy
`[204]
`
`App.
`Protocols
`[213]
`
`Client-Side Proxy API [201)
`
`I
`Client-Side Proxy [202}
`
`I
`
`,....--
`["--
`
`_..,.
`
`Cache
`[203]
`------·-
`
`Traffic
`Shaping
`[205]
`
`Connection
`Management
`[206]
`
`Device Operating System
`[211)
`
`Device Context APl
`[210]
`
`SMS 1/F
`[207]
`
`WiFi 1/F
`[208J
`
`3G/4G 1/F
`[209]
`
`Figure 2 SEVEN Network Harmonizer Client Architecture
`
`14
`
`Page 17 of 47
`
`

`

`Web
`Access
`[309]
`
`Caching
`Policy [300]
`
`Application
`Protocols
`[310]
`
`Proxy Control
`Protocol
`[306]
`
`Hybrid Control
`Protocol
`[308]
`
`Control
`Protocol
`[307J
`
`SMS Controf
`Protocol
`[305]
`
`Traffic Shaping
`[301]
`
`Connection
`Management
`[302]
`
`Connection and
`Content Metadata
`DB {303]
`
`Device Information
`DB [304)
`
`Figure 3 SEVEN Network Harmonizer Server Architecture
`
`15
`
`Page 18 of 47
`
`

`

`I Home Screen I
`
`Widget [400]
`
`I Clf ent-Side I
`
`Proxy [401]
`
`I Caching Web I
`
`Proxy [402]
`
`I Traffic Harmonizer I
`
`Server[403J
`
`I Data Provider Server I
`
`[404]
`
`Data Request [405)
`
`Data Response [406]
`
`Prmded Data Request !4C l
`
`JSj
`ro1ded Data Response [4
`IF
`I'
`
`I
`I
`
`Mo ['litor Data Request [409)
`
`I
`Prmded Data Request t: ~2l
`
`Request Satisfied From ocal Cache [413]
`
`'
`
`Invalidate Notifkatior [416]
`
`Prmded Data Request~ 17!
`
`" Request Satisfied From ~ching Web Proxy [418J
`
`Monitor Data [410]
`
`/
`
`Same Response [411!
`
`Monitor Data [414!
`
`Changed Response [415)
`
`Figure 4 SEVEN Network Harmonizer Distributed Proxy Polling
`
`'
`
`Page 19 of 47
`
`

`

`Electronic Patent Application Fee Transmittal
`
`Application Number:
`
`Filing Date:
`
`Title of Invention:
`
`ONE WAY INTELLIGENT HEARTBEAT
`
`First Named Inventor/Applicant Name:
`
`Mikko Tervahauta
`
`Filer:
`
`Alan D. Minsk/Stacy Villa rose
`
`Attorney Docket Number:
`
`028482-003700US
`
`Filed as Small Entity
`
`Provisional Filing Fees
`
`Description
`
`Fee Code
`
`Quantity
`
`Amount
`
`Sub-Total in
`USD($)
`
`Provisional Application filing fee
`
`2005
`
`1
`
`110
`
`110
`
`Basic Filing:
`
`Pages:
`
`Claims:
`
`Miscellaneous-Filing:
`
`Petition:
`
`Patent-Appeals-and-Interference:
`
`Post-Allowance-and-Post-Issuance:
`
`Extension-of-Time:
`
`Page 20 of 47
`
`

`

`Description
`
`Fee Code
`
`Quantity
`
`Amount
`
`Sub-Total in
`USD($)
`
`Miscellaneous:
`
`Total in USD ($)
`
`110
`
`Page 21 of 47
`
`

`

`Electronic Acknowledgement Receipt
`
`EFSID:
`
`Application Number:
`
`8743424
`
`61408826
`
`International Application Number:
`
`Confirmation Number:
`
`1608
`
`Title of Invention:
`
`ONE WAY INTELLIGENT HEARTBEAT
`
`First Named Inventor/Applicant Name:
`
`Mikko Tervahauta
`
`Customer Number:
`
`20350
`
`Filer:
`
`Alan D. Minsk/Stacy Villa rose
`
`Filer Authorized By:
`
`Alan D. Minsk
`
`Attorney Docket Number:
`
`028482-003700US
`
`Receipt Date:
`
`01-NOV-201 0
`
`Filing Date:
`
`TimeStamp:
`
`Application Type:
`
`Payment information:
`
`Submitted with Payment
`
`Payment Type
`
`Payment was successfully received in RAM
`
`RAM confirmation Number
`
`Deposit Account
`
`Authorized User
`
`15:48:10
`
`Provisional
`
`yes
`
`Deposit Account
`
`$110
`
`2003
`
`201430
`
`The Director of the USPTO is hereby authorized to charge indicated fees and credit any overpayment as follows:
`
`Charge any Additional Fees required under 37 C.F.R. Section 1.16 (National application filing, search, and examination fees)
`
`Charge any Additional Fees required under 37 C.F.R. Section 1.17 (Patent application and reexamination processing fees)
`
`Page 22 of 47
`
`

`

`Charge any Additional Fees required under 37 C.F.R. Section 1.19 (Document supply fees)
`
`Charge any Additional Fees required under 37 C.F.R. Section 1.20 (Post Issuance fees)
`
`Charge any Additional Fees required under 37 C.F.R. Section 1.21 (Miscellaneous fees and charges)
`
`File Listing:
`
`Document
`Number
`
`1
`
`Warnings:
`
`Information:
`
`Document Description
`
`File Name
`
`File Size( Bytes)/
`Message Digest
`
`Multi
`Part /.zip
`
`Pages
`(ifappl.)
`
`2010_11_01 1 O_FWR_ADS_AP
`-
`PLN_FIGS_028482-003700US.
`pdf
`
`719296
`
`6b20e4df00c95643cf425ff0d953bee3f1 be
`9fe
`
`yes
`
`19
`
`Multipart Description/PDF files in .zip description
`
`Document Description
`
`Start
`
`End
`
`Application Data Sheet
`
`Specification
`
`Claims
`
`Drawings-only black and white line drawings
`
`3
`
`14
`
`15
`
`19
`
`1
`
`4
`
`15
`
`16
`
`29824
`
`2
`
`Fee Worksheet (PT0-875)
`
`fee-info. pdf
`
`no
`
`2
`
`77 ceeb23aa2e950b2f0c60b6b7c421859a3
`be3aa
`
`Warnings:
`
`Information:
`
`Total Files Size (in bytes)
`
`749120
`
`This Acknowledgement Receipt evidences receipt on the noted date by the USPTO of the indicated documents,
`characterized by the applicant, and including page counts, where applicable. It serves as evidence of receipt similar to a
`Post Card, as described in MPEP 503.
`
`New A~~lications Under 35 U.S.C. 111
`If a new application is being filed and the application includes the necessary components for a filing date (see 37 CFR
`1.53(b)-(d) and MPEP 506), a Filing Receipt (37 CFR 1.54) will be issued in due course and the date shown on this
`Acknowledgem