Remote decoupled application persistent state apparatuses, methods and systems

Information

  • Patent Grant
  • 11010756
  • Patent Number
    11,010,756
  • Date Filed
    Friday, February 22, 2019
    5 years ago
  • Date Issued
    Tuesday, May 18, 2021
    3 years ago
  • Inventors
  • Original Assignees
  • Examiners
    • Maguire; Lindsay M
    Agents
    • Loeb & Loeb LLP
Abstract
A method comprising receiving a purchase action from a first user device associated with a user, creating and storing a first cookie associated with the purchase action. The method includes receiving, from a second user device, a request for cookie data related to products viewed on a platform other than the second user device, and identifying the first cookie in response to the request for cookie data. The method includes determining a platform type of the second user device, and generating a second cookie compliant with the platform type of the second user device. The method includes sending the generated second cookie to the second user device.
Description

This application for letters patent disclosure document describes inventive aspects directed at various novel innovations (hereinafter “disclosure”) and contains material that is subject to copyright, mask work, and/or other intellectual property protection. The respective owners of such intellectual property have no objection to the facsimile reproduction of the disclosure by anyone as it appears in published Patent Office file/records, but otherwise reserve all rights.


FIELD

The present innovations are directed generally to digital wallets and account management, and more particularly, to REMOTE DECOUPLED APPLICATION PERSISTENT STATE APPARATUSES, METHODS AND SYSTEMS.


BACKGROUND

Consumers using the World Wide Web browse product listings of merchants and make purchases on selected products. Electronic data can be stored in computers and other storage devices for future access.


SUMMARY

In accordance with the teachings provided herein, systems, methods, non-transitory computer-readable medium, and apparatuses are disclosed for operation upon data processing devices for processing digital wallet transaction-related persistent states, such as by: receiving, by use of one or more processors, a wallet transaction-related persistent state update request identifying a wallet user, wherein the wallet transaction-related persistent state update request includes wallet persistent state payload; storing, by use of the one or more processors, the wallet persistent state payload associated with the wallet user; receiving, by use of the one or more processors, a wallet persistent state search criteria from the wallet user; providing, by use of the one or more processors, the wallet persistent state search results to the wallet user; receiving, by use of the one or more processors, a wallet persistent state selection; and generating, by use of the one or more processors, the wallet persistent state presentation based on the wallet persistent state selection.





BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying appendices and/or drawings illustrate various non-limiting, example, innovative aspects in accordance with the present descriptions:



FIG. 1 shows a block diagram illustrating example cookie/states storage in some embodiments of the P-STATE:



FIG. 2 shows a block diagram illustrating example cookie/states storage data flow in some embodiments of the P-STATE;



FIG. 3 shows a logic flow diagram illustrating example cookie/states storage component in some embodiments of the P-STATE;



FIGS. 4A-4C show user interfaces illustrating example cookie/states storage in some embodiments of the P-STATE;



FIG. 5 shows a block diagram illustrating example cookie states search presentation data flow in some embodiments of the P-STATE;



FIG. 6 shows a logic flow diagram illustrating example cookie states search presentation component in some embodiments of the P-STATE;



FIG. 7 shows a block diagram illustrating example cookie states reload/recreate data flow in some embodiments of the P-STATE;



FIG. 8 shows a logic flow diagram illustrating example cookie states reload/recreate component in some embodiments of the P-STATE;



FIG. 9 shows a block diagram illustrating embodiments of a P-STATE controller.





The leading number of each reference number within the drawings indicates the figure in which that reference number is introduced and/or detailed. As such, a detailed discussion of reference number 101 would be found and/or introduced in FIG. 1. Reference number 201 is introduced in FIG. 2, etc.


DETAILED DESCRIPTION

Various embodiments of the P-STATE facilitate an enriched user experience for digital wallet consumers and allow the consumers to store the cookies and the states of their browsing and purchasing history with their digital wallet. In some embodiments, the digital wallet server serves as a cloud based storage to the merchant so that the wallet consumers may retrieve any states they had in the past with this merchant. In some embodiments, the cookie that the wallet stores may have multiple states and the consumer may choose go to any random state and view the page. In some embodiments, because the cookies and states are stored with the digital wallet server, it may be shared across platform. For example, a consumer is at the kiosk at a merchant physical store and desires to purchase the items he looked for last night on this merchant's website. The P-STATE may identify the consumer's digital wallet and bring the items up at the kiosk. For another example, a consumer is at a airplane and desires to watch the movie he purchased before at home. The P-STATE may retrieve his prior purchase cookies and recognize that he has already paid for that (although with another device) and provide the movie to him.


P-STATE


FIG. 1 shows a block diagram illustrating example cookie/states storage in some embodiments of the P-STATE. One possible cookie state 101 may include a timestamp of when the state takes place 103, the merchant 105, the shopping cart status 107, the shipper 109, the offer in, the payment method 113, the checkout status 115, the search criteria (e.g., T-shirt) 117, the search results list 119, the purchase status 121, the platform the consumer is using (e.g., iphone, Android, merchant kiosk, point of sale, etc.) 123. The timestamp may be in the format of 2005 Feb. 3. The merchant of the order may be e-commerce sites such as Amazon. The search criteria may be the name of the product of interest, such as T-shirt. Another possible cookie state 125 may be the webpage providing the search results related to the search criteria (e.g., T-shirt) to the consumer. In some embodiments, it may also have the timestamp, merchant, shopping cart, shipper, offer, payment method, checkout status, purchase status, and order platform. Meanwhile, it may have an empty search criteria field 129, and some products in the search results list, such as blue T-shirt, pink T-shirt, and so forth. The reason may be that the search criteria may have been processed by the system and search results may have been generated. The consumer may choose to add one of the products 9 e.g., blue T-shirt) from the search results into the cart. In another possible cookie state 133, the timestamp, merchant, shopping cart, shipper, offer, payment method, search criteria, search results list, purchase status, and order platform may be the same as the previous cookie state. Meanwhile, its checkout status may include one or more items, the home address, payment method, and a link to the payment processing component. All possible cookie and states may be stored 137 to the cookies database 139. For example, the P-STATE server may issue PHP/SQL commands similar to the example listing below to store the cookies data 137 in a database:














<?PHP


header(′Content-Type: text/plain′);


mysql_connect(″254.92.185.103”,$DBserver,$password); // access


database server


mysql_select(″CookieStates.SQL″); // select database to append


mysql_query(“INSERT INTO CookieStatesTable (state_session_ID


cookie_session_ID


timestamp merchant shopping_cart shipper offer payment_method


checkout search


search_results purchase platform)


VALUES ($state_session_ID $cookie_session_ID


timestamp( )$merchant


$shopping_cart $shipper $offer $payment_method $checkout $search


$search_results $purchase $platform”); // add data to table in database


mysql_close(″CookieStates.SQL”); // close connection to database


?>









In some embodiments, a cookie may have multiple states. In some embodiments, after the consumer places an order or finishes browsing with this merchant, multiple states may be combined to one cookie.



FIG. 2 shows a block diagram illustrating example cookie/states storage data flow in some embodiments of the P-STATE. A user 200 may submit the purchase action input 211 to the client device 202. The purchase action input may include search, add to cart, pay and so forth. After receiving the purchase action input, the client device may perform the requested purchase action and generate cookies 215. Then the client device may store the cookie states 220 to the client cookie database 207. An example of the cookie state structure is discussed in message 230. Examples of PHP/SQL commands to store 220 may be similar to example 137. Following that the client device may update the wallet determination 225 and determine how often the P-STATE server (e.g, wallet server) may need to be updated with the cookies. If the P-STATE server needs updating, then the client device may send the cookie states update package 230 to the P-State server 205. An example cookies/states update package substantially in the form of a HTTP(S) POST message 230 including XML-formatted data, is provided below:














POST /updateacookiestates.php HTTP/1.1


Host: www.P-STATE.com


Content-Type: Application/XML


Content-Length: 667


<?XML version = “1.0” encoding = “UTF-8”?>


<cookie_states_update_package>









<update_timestamp>2010-05-06 05:00</update_timestamp>



<last_update_timestamp>2010-05-05 05:00</last_update_timestamp>



<wallet_id>joesmith@gmail.com</wallet_id>



<cookie_session_ID>123adg









<state_session_ID>1









<timestamp>2010-05-05-09:12</timestamp>



<merchant_id>A12345</merchant_id>



<merchant>Amazon</merchant>



<merchant_session_id>vme0345</merchant_session_id>









<merchant_connection_server>159.2.8.45



</merchant_connection_server>









<shopping_cart></shopping_cart>



<shipper></shipper>



<offer></offer>



<payment_method></payment_method>



<checkout> </checkout>



<search>T-shirt</search>



<search_results></search_results>



<purchase></purchase>



<platform></platform>









</state_session_ID>



<state_session_ID>2









<timestamp>2010-05-05-09:30</timestamp>



<merchant_id>A12345</merchant_id>



<merchant>Amazon</merchant>



<merchant_session_id>vme0345</merchant_session_id>









<merchant_connection_server>159.2.8.45



</merchant_connection_server>









<shopping_cart></shopping_cart>



<shipper></shipper>



<offer></offer>



<payment_method></payment_method>



<checkout></checkout>



<search>T-shirt</search>



<search_results>1 Blue T-shirt, 2. Pink T-







shirt</search_results>









<purchase></purchase>



<platform></platform>









</state_session_ID>



<state_session_ID>3









<timestamp>2010-05-05-09:40</timestamp>



<merchant_id>A12345</merchant_id>



<merchant>Amazon</merchant>



<merchant_session_id>vme0345</merchant_session_id>









<merchant_connection_server>159.2.8.45



</merchant_connection_server>









<shopping_cart></shopping_cart>



<shipper></shipper>



<offer></offer>



<payment_method> Visa 1234</payment_method>



<checkout>1. Blue T-shirt, 2. Camera Total $320 Address:







123 peace st. New York NY</checkout>









<search>T-shirt</search>



<search_results></search_results>



<purchase></purchase>



<platform></platform>









</state_session_ID>









</cookie_session_ID>



<cookie_session_ID>523adg









<state_session_ID>1









<timestamp>2011-05-05-09:12</timestamp>



<merchant_id>B12345</merchant_id>



<merchant>Bestbuy</merchant>



<merchant_session_id>vme1345</merchant_session_id>









<merchant_connection_server>259.2.8.45



</merchant_connection_server>









<shopping_cart>Computer XXXX</shopping_cart>



<shipper>UPS</shipper>



<offer></offer>



<payment_method></payment_method>



<checkout> </checkout>



<search></search>



<search_results></search_results>



<purchase></purchase>



<platform>iphone</platform>









</state_session_ID>



<state_session_ID>2









<timestamp>2011-05-05-10:30</timestamp>



<merchant_id>B12345</merchant_id>



<merchant>Bestbuy</merchant>



<merchant_session_id>vme1345</merchant_session_id>









<merchant_connection_server>259.2.8.45



</merchant_connection_server>









<shopping_cart>Computer XXXX</shopping_cart>



<shipper>UPS</shipper>



<offer>20% off</offer>



<payment_method></payment_method>



<checkout></checkout>



<search> </search>



<search_results></search_results>



<purchase></purchase>



<platform> iphone </platform>









</state_session_ID>









</cookie_session_ID>







</cookie_states_update_package>









After receiving the cookie states update package the P-State server may update the cookie states 234. Then the P-State server may store the cookie states 240 into the P-State cookies database 209. Examples of PHP/SQL commands to store 240 may be similar to example 137.



FIG. 3 shows a logic flow diagram illustrating example cookie/states storage component in some embodiments of the P-STATE. In some embodiments, the client may receive purchase action input, such as search, add to cart, and so forth 311. Then the client may determine whether the input includes a new merchant 313. If it does not include a new merchant, then the client may determine whether the transaction is complete 315. In some embodiments, it may determine whether a previous transaction is complete. If the transaction is not complete, then the client may determine if it is the first transaction 317. If the input includes a new merchant, or the transaction is complete, or it is the first transaction, then the client may set a new cookie flag 319. After that the client may create a new cookie 321. The client may also set the cookie flag to complete and store the cookie on the device 329. Then the client may create a new cookie state 325. After that and also if it does not involve a first transaction with the merchant 317, for each action that is queued 327, the client may create a new cookie state 325 and perform the received purchase action 323. Following that the client may store the cookie states to the client cookies database with performed action state information 331. Then the client may determine whether there is a wallet update quantum 333. If there is a wallet update quantum, then the client may update the wallet determination, such as to update every 5 minutes, or one hour, or 3 days, and so forth 335. After that the client may send cookie sates update package to the P-State server 337. Then the P-State server may update the cookie states 341. After that the P-State server may store the updated cookie states to the P-State cookies database 343. If ted is not a wallet update quantum, then the client may determine whether there is a next queued action 339. If there is a next queued action, then the client may receive purchase additional action input.



FIGS. 4A-4C show user interfaces illustrating example cookie/states storage in some embodiments of the P-STATE. Referring to FIG. 4A, in some embodiments, cookies and states (cookies and states may be referred to cookie states, cookies, or states in some instances) may be viewed in a timeline fashion. 405, 407, 409 are different cookie states and when the mouse lies on one state, a preview of this state may be seen 405. Cookies on the right 401 have a newer timestamp than the cookies on the left 403. Also a list of the cookies with file information may be shown underneath 411. In the preview window 405, you may choose different information to show. If you choose to view cart 413, you may see the merchant name, session id, timestamp, and a list of products in the cart. You may also search 415 in the cookies, view file info 423, preview the cookie 421, reload the cookie 419, and recreate the cookie 417. In some embodiments, reloading the cookie means the merchant still has the cookie loaded. The merchant may send the payload information and consumer's client device may load the cookie and generate for webpage or app's display. In some embodiments, recreating the cookie means the merchant may not have the cookie loaded. Based on the payload info in the stored cookie, the merchant may recreate the cookie and send to the consumer. The reloading and recreating features are discussed in more details in FIGS. 7 and 8.


Referring to FIG. 4B, in some embodiments, cookies and states are searchable. You may put in a search term 431, for example boot, the P_STATE may return you the cookies and states with “boot” in it 437.


Referring to FIG. 4C, in some embodiments, consumer may also view the cookies in a list view 451. Timestamp 455, product 457, price 459, merchant 461, platform 463, coupons 465, shippers 467, payment method, and other information may be shown. For some products, consumers may view it in different platforms (for example, iPad 477, and merchant kiosk 479). In some embodiments, the cookies and states are searchable 453. Users may choose different categories to search.



FIG. 5 shows a block diagram illustrating example cookie states search presentation data flow in some embodiments of the P-STATE. In some embodiments, a user 501 may submit the cookie states search criteria input 511 to the client device 502. After receiving the search criteria input, the client device may look up cookie state or states associated with the search criteria 515. After that it may generate a cookie states presentation 520. Alternatively the client device may submit a cookie states search request with search criteria 530 to the P-State server 505. An example cookie states search request substantially in the form of a HTTP(S) POST message 530 including XML-formatted data, is provided below:














POST /cookiestatessearch.php HTTP/1.1


Host: www.P-STATE.com


Content-Type: Application/XML


Content-Length: 667


<?XML version = “1.0” encoding = “UTF-8”?>


<cookie_states_search_request>









<wallet_id>joesmith@gmail.com</wallet_id>



<wallet_digital_certificate>****</wallet_digital_certificate>



<search_target>cookies</search_target>



<search_criteria>boots</search_criteria>



<search_period_from>2005-01-03</search_period_from>



<search_period_to>2006-01-03</search_period_to>







</cookie_states_search_request>









Then the P-State server may look up the cookie state or states associated with the search criteria 535. After that the P-State server may send the cookie states search results 540 back to the client device. An example cookie states search results substantially in the form of a HTTP(S) PUSH message 540 including XML-formatted data, is provided below:














PUSH /cookiestatessearchresults.php HTTP/1.1


Host: www.P-STATE.com


Content-Type: Application/XML


Content-Length: 667


<?XML version = “1.0” encoding = “UTF-8”?>


<cookie_states_search_results>









<wallet_id>joesmith@gmail.com</wallet_id>



<cookie_session_ID>123adg









<state_session_ID>3









<timestamp>2010-05-05-09:40</timestamp>



<merchant_id>A12345</merchant_id>



<merchant>Amazon</merchant>



<merchant_session_id>vme0345</merchant_session_id>









<merchant_connection_server>159.2.8.45



</merchant_connection_server>









<shopping_cart></shopping_cart>



<shipper></shipper>



<offer></offer>



<payment_method> Visa 1234</payment_method>



<checkout>1. baby boots 2. books Total $320 Address: 123







peace st. New York NY</checkout>









<search></search>



<search_results></search_results>



<purchase></purchase>



<platform></platform>









</state_session_ID>









</cookie_session_ID>



<cookie_session_ID>523adg









<state_session_ID>1









<timestamp>2011-05-05-09:40</timestamp>



<merchant_id>M12345</merchant_id>



<merchant>Macy's</merchant>



<merchant_session_id>vme3345</merchant_session_id>









<merchant_connection_server>159.2.8.45



</merchant_connection_server>









<shopping_cart></shopping_cart>



<shipper></shipper>



<offer></offer>



<payment_method> Visa 1234</payment_method>



<checkout>1. leather boots 2. computer Total $920







Address: 123 peace st. New York NY</checkout>









<search> </search>



<search_results></search_results>



<purchase></purchase>



<platform></platform>









</state_session_ID>









</cookie_session_ID>







</cookie_states_search_results>









The client device then may generate the cookie states presentation. Then the client device may display the results 525 to the user.



FIG. 6 shows a logic flow diagram illustrating example cookie states search presentation component in some embodiments of the P-STATE. The client may receive cookie states search criteria input 601. After that the client may look up cookie states associated with the search criteria 605. Then the client may determine whether the cookies are found 607. If the cookies are found, the client may load the cookie stats 609. If the cookies are not found, the client may send the cookie states search request with the search criteria to the P-State server 615. Following that the P-State server may look up the cookie state or states associated with the search criteria 620. Then the P-State server may send the cookie states search results to the client 625. After the client loads the cookie states or the P-State server sends the cookie states search results to the client, the client may generate cookie states presentation 630.



FIG. 7 shows a block diagram illustrating example cookie states reload/recreate data flow in some embodiments of the P-STATE. In some embodiments, the user may submit the cookie state(s) selection input 711 to the client device 702. Then the client device may determine the platform that is used, such as webpage, mobile app, and so forth, and load the cookies 715. After that the client device may reload or recreate the cookie state request message, such as payload cookie and states 720. An example reload/recreate cookie state request substantially in the form of a HTTP(S) POST message 720 including XML-formatted data, is provided below:
















POST /reloadrecreatecookiestaterequest.php HTTP/1.1



HOST: www.P-STATE.com



Content-Type: Application/XML



Content-Length: 667



<?XML version = “1.0” encoding = “UTF-8”?>



<reload_recreate_cookie_state_request>









<merchant_id>A12345</merchant_id>



<search_target>cookies</search_target>



<search_criteria>









<cookie_session_ID>123adg</cookie_session_ID>1



<state_session_ID>3</state_session_ID>









</search_criteria>



<search_period_from>2005-01-03</search_period_from>



<search_period_to>2006-01-03</search_period_to>









</reload_recreate_cookie_state_request>









Then the merchant server 705 may determine if the selected cookie state is still loaded 725. Then the merchant server may load the selected cookie state 730 and send the reloaded cookie state response back to client, with info, for example, the webpage served or the mobile application payload 740. An example reload (or recreate) cookie state response substantially in the form of a HTTP(S) PUSH message 740 (or 745) including XML-formatted data, is provided below:














PUSH /reloadrecreatecookiestateresposne.php HTTP/1.1


Host: www.P-STATE.com


Content-Type: Application/XML


Content-Length: 667


<?XML version = “1.0” encoding = “UTF-8”?>


<reload_recreate_cookie_state_response>









<state_on_server_status>reloaded</state_on_server_status>







//Alternatively, the state_on_server_status may also be recreated









<cookie_session_ID>123adg









<state_session_ID>3









<timestamp>2010-05-05-09:40</timestamp>



<merchant_id>A12345</merchant_id>



<merchant>Amazon</merchant>



<merchant_session_id>vme0345</merchant_session_id>









<merchant_connection_server>159.2.8.45



</merchant_connection_server>









<shopping_cart></shopping_cart>



<shipper></shipper>



<offer></offer>



<payment_method> Visa 1234</payment_method>



<checkout>1. baby boots 2. books Total $320 Address: 123







peace st. New York NY</checkout>









<search></search>



<search_results></search_results>



<purchase></purchase>



<platform></platform>









</state_session_ID>









</cookie_session_ID>







</reload_recreate_cookie_state_response>









The client may launch target for executing response payload, for example, open browser or application, and load payload in target 750 for display to the user 760. In an alternative embodiment, if the merchant server do not have the selected cookie loaded 725, the merchant server may recreate selected cookie state with payload cookie states (e.g., load cart, search, shipping, pay, etc.) 735 and send it back to the client 745. In another alternative embodiment, the merchant or the client may request the selected cookie from the P-STATE server.



FIG. 8 shows a logic flow diagram illustrating example cookie states reload/recreate component in some embodiments of the P-STATE. In some embodiments, the client may receive a cookie state selection input from the consumer 801. The client may then determine what platform was used to send the input (e.g., webpage, mobile device application, etc.). The client may then generate and send a reload/recreate cookie states request 805 to the merchant server 801. The merchant server may determine if selected cookie sate is till loaded on the merchant server 815. If the cookie state is still loaded 822, the merchant server may load selected cookie state and sends reload cookie state response to the client 825. The response may also include a webpage server or application payload 830. Upon receiving the reload cookie state response, the client may launch a target for executing response payload (e.g., open a browser, a mobile device application) and load payload in target for display to the user 835. In some embodiments, if the cookie is no longer loaded at the merchant server 820, in an alternative embodiment, the merchant server may determine if the session can be recreated 840. If the session can be recreated, the merchant server may recreate selected cookie state with actions such as loading card, searching, adding shipping, etc. 855. The merchant server may then send recreate confirmation response message with webpage served or application payload to the client 860. The client may then laugh target and load payload in target 835. Alternatively, if the session can not be recreated 840 at the merchant server, the merchant may send a load cookie state request to the P-STATE server 845 and retrieve cookie states from the P-STATE server. Once the merchant receives cookie states from the P-STATE server 855, the merchant may recreate selected cookie state and send to client to load in target 835


P-STATE Controller


FIG. 9 shows a block diagram illustrating embodiments of a P-STATE controller. In this embodiment, the P-STATE controller 900 may serve to aggregate, process, store, search, serve, identify, instruct, generate, match, and/or facilitate interactions with a computer through various bi-directional linking technologies, and/or other related data.


Typically, users, which may be people and/or other systems, may engage information technology systems (e.g., computers) to facilitate information processing. In turn, computers employ processors to process information; such processors 903 may be referred to as central processing units (CPU). One form of processor is referred to as a microprocessor. CPUs use communicative circuits to pass binary encoded signals acting as instructions to enable various operations. These instructions may be operational and/or data instructions containing and/or referencing other instructions and data in various processor accessible and operable areas of memory 929 (e.g., registers, cache memory, random access memory, etc.). Such communicative instructions may be stored and/or transmitted in batches (e.g., batches of instructions) as programs and/or data components to facilitate desired operations. These stored instruction codes, e.g., programs, may engage the CPU circuit components and other motherboard and/or system components to perform desired operations. One type of program is a computer operating system, which, may be executed by CPU on a computer; the operating system enables and facilitates users to access and operate computer information technology and resources. Some resources that may be employed in information technology systems include: input and output mechanisms through which data may pass into and out of a computer; memory storage into which data may be saved; and processors by which information may be processed. These information technology systems may be used to collect data for later retrieval, analysis, and manipulation, which may be facilitated through a database program. These information technology systems provide interfaces that allow users to access and operate various system components.


In one embodiment, the P-STATE controller 901 may be connected to and/or communicate with entities such as, but not limited to: one or more users from user input devices 91i; peripheral devices 912; an optional cryptographic processor device 928; and/or a communications network 913.


Networks are commonly thought to comprise the interconnection and interoperation of clients, servers, and intermediary nodes in a graph topology. It should be noted that the term “server” as used throughout this application refers generally to a computer, other device, program, or combination thereof that processes and responds to the requests of remote users across a communications network. Servers serve their information to requesting “clients.” The term “client” as used herein refers generally to a computer, program, other device, user and/or combination thereof that is capable of processing and making requests and obtaining and processing any responses from servers across a communications network. A computer, other device, program, or combination thereof that facilitates, processes information and requests, and/or furthers the passage of information from a source user to a destination user is commonly referred to as a “node.” Networks are generally thought to facilitate the transfer of information from source points to destinations. A node specifically tasked with furthering the passage of information from a source to a destination is commonly called a “router.” There are many forms of networks such as Local Area Networks (LANs), Pico networks, Wide Area Networks (WANs), Wireless Networks (WLANs), etc. For example, the Internet is generally accepted as being an interconnection of a multitude of networks whereby remote clients and servers may access and interoperate with one another.


The P-STATE controller 901 may be based on computer systems that may comprise, but are not limited to, components such as: a computer systemization 902 connected to memory 929.


Computer Systemization

A computer systemization 902 may comprise a clock 930, central processing unit (“CPU(s)” and/or “processor(s)” (these terms are used interchangeable throughout the disclosure unless noted to the contrary)) 903, a memory 929 (e.g., a read only memory (ROM) 9006, a random access memory (RAM) 905, etc.), and/or an interface bus 907, and most frequently, although not necessarily, are all interconnected and/or communicating through a system bus 9004 on one or more (mother)board(s) 902 having conductive and/or otherwise transportive circuit pathways through which instructions (e.g., binary encoded signals) may travel to effectuate communications, operations, storage, etc. The computer systemization may be connected to a power source 986; e.g., optionally the power source may be internal. Optionally, a cryptographic processor 926 and/or transceivers (e.g., ICs) 974 may be connected to the system bus. In another embodiment, the cryptographic processor and/or transceivers may be connected as either internal and/or external peripheral devices 912 via the interface bus I/O. In turn, the transceivers may be connected to antenna(s) 975, thereby effectuating wireless transmission and reception of various communication and/or sensor protocols; for example the antenna(s) may connect to: a Texas Instruments WiLink WL1283 transceiver chip (e.g., providing 802.11n, Bluetooth 3.0, FM, global positioning system (GPS) (thereby allowing P-STATE controller to determine its location)); Broadcom BCM4329FKUBG transceiver chip (e.g., providing 802.11n, Bluetooth 2.1+ EDR, FM, etc.); a Broadcom BCM4750IUB8 receiver chip (e.g., GPS); an Infineon Technologies X-Gold 618-PMB9800 (e.g., providing 2G/3G HSDPA/HSUPA communications); and/or the like. The system clock typically has a crystal oscillator and generates a base signal through the computer systemization's circuit pathways. The clock is typically coupled to the system bus and various clock multipliers that will increase or decrease the base operating frequency for other components interconnected in the computer systemization. The clock and various components in a computer systemization drive signals embodying information throughout the system. Such transmission and reception of instructions embodying information throughout a computer systemization may be commonly referred to as communications. These communicative instructions may further be transmitted, received, and the cause of return and/or reply communications beyond the instant computer systemization to: communications networks, input devices, other computer systemizations, peripheral devices, and/or the like. It should be understood that in alternative embodiments, any of the above components may be connected directly to one another, connected to the CPU, and/or organized in numerous variations employed as exemplified by various computer systems.


The CPU comprises at least one high-speed data processor adequate to execute program components for executing user and/or system-generated requests. Often, the processors themselves will incorporate various specialized processing units, such as, but not limited to: integrated system (bus) controllers, memory management control units, floating point units, and even specialized processing sub-units like graphics processing units, digital signal processing units, and/or the like. Additionally, processors may include internal fast access addressable memory, and be capable of mapping and addressing memory 929 beyond the processor itself; internal memory may include, but is not limited to: fast registers, various levels of cache memory (e.g., level 1, 2, 3, etc.), RAM, etc. The processor may access this memory through the use of a memory address space that is accessible via instruction address, which the processor can construct and decode allowing it to access a circuit path to a specific memory address space having a memory state. The CPU may be a microprocessor such as: AMD's Athlon, Duron and/or Opteron; ARM's application, embedded and secure processors; IBM and/or Motorola's DragonBall and PowerPC; IBM's and Sony's Cell processor; Intel's Celeron, Core (2) Duo, Itanium, Pentium, Xeon, and/or XScale; and/or the like processor(s). The CPU interacts with memory through instruction passing through conductive and/or transportive conduits (e.g., (printed) electronic and/or optic circuits) to execute stored instructions (i.e., program code) according to conventional data processing techniques. Such instruction passing facilitates communication within the P-STATE controller and beyond through various interfaces. Should processing requirements dictate a greater amount speed and/or capacity, distributed processors (e.g., Distributed P-STATE), mainframe, multi-core, parallel, and/or super-computer architectures may similarly be employed. Alternatively, should deployment requirements dictate greater portability, smaller Personal Digital Assistants (PDAs) may be employed.


Depending on the particular implementation, features of the P-STATE may be achieved by implementing a microcontroller such as CAST's R8051XC2 microcontroller; Intel's MCS 51 (i.e., 8051 microcontroller); and/or the like. Also, to implement certain features of the P-STATE, some feature implementations may rely on embedded components, such as: Application-Specific Integrated Circuit (“ASIC”), Digital Signal Processing (“DSP”), Field Programmable Gate Array (“FPGA”), and/or the like embedded technology. For example, any of the P-STATE component collection (distributed or otherwise) and/or features may be implemented via the microprocessor and/or via embedded components; e.g., via ASIC, coprocessor, DSP, FPGA, and/or the like. Alternately, some implementations of the P-STATE may be implemented with embedded components that are configured and used to achieve a variety of features or signal processing.


Depending on the particular implementation, the embedded components may include software solutions, hardware solutions, and/or some combination of both hardware/software solutions. For example, P-STATE features discussed herein may be achieved through implementing FPGAs, which are a semiconductor devices containing programmable logic components called “logic blocks”, and programmable interconnects, such as the high performance FPGA Virtex series and/or the low cost Spartan series manufactured by Xilinx. Logic blocks and interconnects can be programmed by the customer or designer, after the FPGA is manufactured, to implement any of the P-STATE features. A hierarchy of programmable interconnects allow logic blocks to be interconnected as needed by the P-STATE system designer/administrator, somewhat like a one-chip programmable breadboard. An FPGA's logic blocks can be programmed to perform the operation of basic logic gates such as AND, and XOR, or more complex combinational operators such as decoders or mathematical operations. In most FPGAs, the logic blocks also include memory elements, which may be circuit flip-flops or more complete blocks of memory. In some circumstances, the P-STATE may be developed on regular FPGAs and then migrated into a fixed version that more resembles ASIC implementations. Alternate or coordinating implementations may migrate P-STATE controller features to a final ASIC instead of or in addition to FPGAs. Depending on the implementation all of the aforementioned embedded components and microprocessors may be considered the “CPU” and/or “processor” for the P-STATE.


Power Source

The power source 986 may be of any standard form for powering small electronic circuit board devices such as the following power cells: alkaline, lithium hydride, lithium ion, lithium polymer, nickel cadmium, solar cells, and/or the like. Other types of AC or DC power sources may be used as well. In the case of solar cells, in one embodiment, the case provides an aperture through which the solar cell may capture photonic energy. The power cell 986 is connected to at least one of the interconnected subsequent components of the P-STATE thereby providing an electric current to all subsequent components. In one example, the power source 986 is connected to the system bus component 904. In an alternative embodiment, an outside power source 986 is provided through a connection across the I/O 908 interface. For example, a USB and/or IEEE 1394 connection carries both data and power across the connection and is therefore a suitable source of power.


Interface Adapters

Interface bus(ses) 907 may accept, connect, and/or communicate to a number of interface adapters, conventionally although not necessarily in the form of adapter cards, such as but not limited to: input output interfaces (I/O) 908, storage interfaces 909, network interfaces 910, and/or the like. Optionally, cryptographic processor interfaces 927 similarly may be connected to the interface bus. The interface bus provides for the communications of interface adapters with one another as well as with other components of the computer systemization. Interface adapters are adapted for a compatible interface bus. Interface adapters conventionally connect to the interface bus via a slot architecture. Conventional slot architectures may be employed, such as, but not limited to: Accelerated Graphics Port (AGP), Card Bus, (Extended) Industry Standard Architecture ((E)ISA), Micro Channel Architecture (MCA), NuBus, Peripheral Component Interconnect (Extended) (PCI(X)), PCI Express, Personal Computer Memory Card International Association (PCMCIA), and/or the like.


Storage interfaces 909 may accept, communicate, and/or connect to a number of storage devices such as, but not limited to: storage devices 914, removable disc devices, and/or the like. Storage interfaces may employ connection protocols such as, but not limited to: (Ultra) (Serial) Advanced Technology Attachment (Packet Interface) ((Ultra) (Serial) ATA(PI)), (Enhanced) Integrated Drive Electronics ((E)IDE), Institute of Electrical and Electronics Engineers (IEEE) 1394, fiber channel, Small Computer Systems Interface (SCSI), Universal Serial Bus (USB), and/or the like.


Network interfaces 910 may accept, communicate, and/or connect to a communications network 913. Through a communications network 913, the P-STATE controller is accessible through remote clients 933b (e.g., computers with web browsers) by users 933a. Network interfaces may employ connection protocols such as, but not limited to: direct connect, Ethernet (thick, thin, twisted pair 10/100/1000 Base T, and/or the like), Token Ring, wireless connection such as IEEE 802.11a-x, and/or the like. Should processing requirements dictate a greater amount speed and/or capacity, distributed network controllers (e.g., Distributed P-STATE), architectures may similarly be employed to pool, load balance, and/or otherwise increase the communicative bandwidth required by the P-STATE controller. A communications network may be any one and/or the combination of the following: a direct interconnection; the Internet; a Local Area Network (LAN); a Metropolitan Area Network (MAN); an Operating Missions as Nodes on the Internet (OMNI); a secured custom connection; a Wide Area Network (WAN); a wireless network (e.g., employing protocols such as, but not limited to a Wireless Application Protocol (WAP), I-mode, and/or the like); and/or the like. A network interface may be regarded as a specialized form of an input output interface. Further, multiple network interfaces 910 may be used to engage with various communications network types 913. For example, multiple network interfaces may be employed to allow for the communication over broadcast, multicast, and/or unicast networks.


Input Output interfaces (I/O) 908 may accept, communicate, and/or connect to user input devices 911, peripheral devices 912, cryptographic processor devices 928, and/or the like. I/O may employ connection protocols such as, but not limited to: audio: analog, digital, monaural, RCA, stereo, and/or the like; data: Apple Desktop Bus (ADB), IEEE 1394a-b, serial, universal serial bus (USB); infrared; joystick; keyboard; midi; optical; PC AT; PS/2; parallel; radio; video interface: Apple Desktop Connector (ADC), BNC, coaxial, component, composite, digital, Digital Visual Interface (DVI), high-definition multimedia interface (HDMI), RCA, RF antennae, S-Video, VGA, and/or the like; wireless transceivers: 802.11a/b/g/n/x; Bluetooth; cellular (e.g., code division multiple access (CDMA), high speed packet access (HSPA(+)), high-speed downlink packet access (HSDPA), global system for mobile communications (GSM), long term evolution (LTE), WiMax, etc.); and/or the like. One typical output device may include a video display, which typically comprises a Cathode Ray Tube (CRT) or Liquid Crystal Display (LCD) based monitor with an interface (e.g., DVI circuitry and cable) that accepts signals from a video interface, may be used. The video interface composites information generated by a computer systemization and generates video signals based on the composited information in a video memory frame. Another output device is a television set, which accepts signals from a video interface. Typically, the video interface provides the composited video information through a video connection interface that accepts a video display interface (e.g., an RCA composite video connector accepting an RCA composite video cable; a DVI connector accepting a DVI display cable, etc.).


User input devices 911 often are a type of peripheral device 512 (see below) and may include: card readers, dongles, finger print readers, gloves, graphics tablets, joysticks, keyboards, microphones, mouse (mice), remote controls, retina readers, touch screens (e.g., capacitive, resistive, etc.), trackballs, trackpads, sensors (e.g., accelerometers, ambient light, GPS, gyroscopes, proximity, etc.), styluses, and/or the like.


Peripheral devices 912 may be connected and/or communicate to I/O and/or other facilities of the like such as network interfaces, storage interfaces, directly to the interface bus, system bus, the CPU, and/or the like. Peripheral devices may be external, internal and/or part of the P-STATE controller. Peripheral devices may include: antenna, audio devices (e.g., line-in, line-out, microphone input, speakers, etc.), cameras (e.g., still, video, webcam, etc.), dongles (e.g., for copy protection, ensuring secure transactions with a digital signature, and/or the like), external processors (for added capabilities; e.g., crypto devices 528), force-feedback devices (e.g., vibrating motors), network interfaces, printers, scanners, storage devices, transceivers (e.g., cellular, GPS, etc.), video devices (e.g., goggles, monitors, etc.), video sources, visors, and/or the like. Peripheral devices often include types of input devices (e.g., cameras).


It should be noted that although user input devices and peripheral devices may be employed, the P-STATE controller may be embodied as an embedded, dedicated, and/or monitor-less (i.e., headless) device, wherein access would be provided over a network interface connection.


Cryptographic units such as, but not limited to, microcontrollers, processors 926, interfaces 927, and/or devices 928 may be attached, and/or communicate with the P-STATE controller. A MC68HC16 microcontroller, manufactured by Motorola Inc., may be used for and/or within cryptographic units. The MC68HC16 microcontroller utilizes a 16-bit multiply-and-accumulate instruction in the 16 MHz configuration and requires less than one second to perform a 512-bit RSA private key operation. Cryptographic units support the authentication of communications from interacting agents, as well as allowing for anonymous transactions. Cryptographic units may also be configured as part of the CPU. Equivalent microcontrollers and/or processors may also be used. Other commercially available specialized cryptographic processors include: Broadcom's CryptoNetX and other Security Processors; nCipher's nShield; SafeNet's Luna PCI (e.g., 7100) series; Semaphore Communications' 40 MHz Roadrunner 184; Sun's Cryptographic Accelerators (e.g., Accelerator 6000 PCIe Board, Accelerator 500 Daughtercard); Via Nano Processor (e.g., L2100, L2200, U2400) line, which is capable of performing 500+MB/s of cryptographic instructions; VLSI Technology's 33 MHz 6868; and/or the like.


Memory

Generally, any mechanization and/or embodiment allowing a processor to affect the storage and/or retrieval of information is regarded as memory 929. However, memory is a fungible technology and resource, thus, any number of memory embodiments may be employed in lieu of or in concert with one another. It is to be understood that the P-STATE controller and/or a computer systemization may employ various forms of memory 929. For example, a computer systemization may be configured wherein the operation of on-chip CPU memory (e.g., registers), RAM, ROM, and any other storage devices are provided by a paper punch tape or paper punch card mechanism; however, such an embodiment would result in an extremely slow rate of operation. In a typical configuration, memory 929 will include ROM 906, RAM 905, and a storage device 914. A storage device 914 may be any conventional computer system storage. Storage devices may include a drum; a (fixed and/or removable) magnetic disk drive; a magneto-optical drive; an optical drive (i.e., Blueray, CD ROM/RAM/Recordable (R)/ReWritable (RW), DVD R/RW, HD DVD R/RW etc.); an array of devices (e.g., Redundant Array of Independent Disks (RAID)); solid state memory devices (USB memory, solid state drives (SSD), etc.); other processor-readable storage mediums; and/or other devices of the like. Thus, a computer systemization generally requires and makes use of memory.


Component Collection

The memory 929 may contain a collection of program and/or database components and/or data such as, but not limited to: operating system component(s) 915 (operating system); information server component(s) 916 (information server); user interface component(s) 917 (user interface); Web browser component(s) 918 (Web browser); database(s) 919; mail server component(s) 921; mail client component(s) 922; cryptographic server component(s) 920 (cryptographic server); the P-STATE component(s) 935; cookie/states storage (“CSS”) component 941; cookie states search presentation (“CSSP”) component 942; and cookie/states reload/recreate (“CSRR”) component 943; and/or the like (i.e., collectively a component collection). These components may be stored and accessed from the storage devices and/or from storage devices accessible through an interface bus. Although non-conventional program components such as those in the component collection, typically, are stored in a local storage device 914, they may also be loaded and/or stored in memory such as: peripheral devices, RAM, remote storage facilities through a communications network, ROM, various forms of memory, and/or the like.


Operating System

The operating system component 915 is an executable program component facilitating the operation of the P-STATE controller. Typically, the operating system facilitates access of I/O, network interfaces, peripheral devices, storage devices, and/or the like. The operating system may be a highly fault tolerant, scalable, and secure system such as: Apple Macintosh OS X (Server); AT&T Plan 9; Be OS; Unix and Unix-like system distributions (such as AT&T's UNIX; Berley Software Distribution (BSD) variations such as FreeBSD, NetBSD, OpenBSD, and/or the like; Linux distributions such as Red Hat, Ubuntu, and/or the like); and/or the like operating systems. However, more limited and/or less secure operating systems also may be employed such as Apple Macintosh OS, IBM OS/2, Microsoft DOS, Microsoft Windows 2000/2003/3.1/95/98/CE/Millenium/NT/Vista/XP (Server), Palm OS, and/or the like. An operating system may communicate to and/or with other components in a component collection, including itself, and/or the like. Most frequently, the operating system communicates with other program components, user interfaces, and/or the like. For example, the operating system may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. The operating system, once executed by the CPU, may enable the interaction with communications networks, data, I/O, peripheral devices, program components, memory, user input devices, and/or the like. The operating system may provide communications protocols that allow the P-STATE controller to communicate with other entities through a communications network 913. Various communication protocols may be used by the P-STATE controller as a subcarrier transport mechanism for interaction, such as, but not limited to: multicast, TCP/IP, UDP, unicast, and/or the like.


Information Server

An information server component 916 is a stored program component that is executed by a CPU. The information server may be a conventional Internet information server such as, but not limited to Apache Software Foundation's Apache, Microsoft's Internet Information Server, and/or the like. The information server may allow for the execution of program components through facilities such as Active Server Page (ASP), ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, Common Gateway Interface (CGI) scripts, dynamic (D) hypertext markup language (HTML), FLASH, Java, JavaScript, Practical Extraction Report Language (PERL), Hypertext Pre-Processor (PHP), pipes, Python, wireless application protocol (WAP), WebObjects, and/or the like. The information server may support secure communications protocols such as, but not limited to, File Transfer Protocol (FTP); HyperText Transfer Protocol (HTTP); Secure Hypertext Transfer Protocol (HTTPS), Secure Socket Layer (SSL), messaging protocols (e.g., America Online (AOL) Instant Messenger (AIM), Application Exchange (APEX), ICQ, Internet Relay Chat (IRC), Microsoft Network (MSN) Messenger Service, Presence and Instant Messaging Protocol (PRIM), Internet Engineering Task Force's (IETF's) Session Initiation Protocol (SIP), SIP for Instant Messaging and Presence Leveraging Extensions (SIMPLE), open XML-based Extensible Messaging and Presence Protocol (XMPP) (i.e., Jabber or Open Mobile Alliance's (OMA's) Instant Messaging and Presence Service (IMPS)), Yahoo! Instant Messenger Service, and/or the like. The information server provides results in the form of Web pages to Web browsers, and allows for the manipulated generation of the Web pages through interaction with other program components. After a Domain Name System (DNS) resolution portion of an HTTP request is resolved to a particular information server, the information server resolves requests for information at specified locations on the P-STATE controller based on the remainder of the HTTP request. For example, a request such as http://123.124.125.126/myInformation.html might have the IP portion of the request “123.124.125.126” resolved by a DNS server to an information server at that IP address; that information server might in turn further parse the http request for the “/myInformation.html” portion of the request and resolve it to a location in memory containing the information “myInformation.html.” Additionally, other information serving protocols may be employed across various ports, e.g., FTP communications across port 21, and/or the like. An information server may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the information server communicates with the P-STATE database 919, operating systems, other program components, user interfaces, Web browsers, and/or the like.


Access to the P-STATE database may be achieved through a number of database bridge mechanisms such as through scripting languages as enumerated below (e.g., CGI) and through inter-application communication channels as enumerated below (e.g., CORBA, WebObjects, etc.). Any data requests through a Web browser are parsed through the bridge mechanism into appropriate grammars as required by the P-STATE. In one embodiment, the information server would provide a Web form accessible by a Web browser. Entries made into supplied fields in the Web form are tagged as having been entered into the particular fields, and parsed as such. The entered terms are then passed along with the field tags, which act to instruct the parser to generate queries directed to appropriate tables and/or fields. In one embodiment, the parser may generate queries in standard SQL by instantiating a search string with the proper join/select commands based on the tagged text entries, wherein the resulting command is provided over the bridge mechanism to the P-STATE as a query. Upon generating query results from the query, the results are passed over the bridge mechanism, and may be parsed for formatting and generation of a new results Web page by the bridge mechanism. Such a new results Web page is then provided to the information server, which may supply it to the requesting Web browser.


Also, an information server may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.


User Interface

Computer interfaces in some respects are similar to automobile operation interfaces. Automobile operation interface elements such as steering wheels, gearshifts, and speedometers facilitate the access, operation, and display of automobile resources, and status. Computer interaction interface elements such as check boxes, cursors, menus, scrollers, and windows (collectively and commonly referred to as widgets) similarly facilitate the access, capabilities, operation, and display of data and computer hardware and operating system resources, and status. Operation interfaces are commonly called user interfaces. Graphical user interfaces (GUIs) such as the Apple Macintosh Operating System's Aqua, IBM's OS/2, Microsoft's Windows 2000/2003/3.1/95/98/CE/Millenium/NT/XP/Vista/7 (i.e., Aero), Unix's X-Windows (e.g., which may include additional Unix graphic interface libraries and layers such as K Desktop Environment (KDE), mythTV and GNU Network Object Model Environment (GNOME)), web interface libraries (e.g., ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, etc. interface libraries such as, but not limited to, Dojo, jQuery(UI), MooTools, Prototype, script.aculo.us, SWFObject, Yahoo! User Interface, any of which may be used and) provide a baseline and means of accessing and displaying information graphically to users.


A user interface component 917 is a stored program component that is executed by a CPU. The user interface may be a conventional graphic user interface as provided by, with, and/or atop operating systems and/or operating environments such as already discussed. The user interface may allow for the display, execution, interaction, manipulation, and/or operation of program components and/or system facilities through textual and/or graphical facilities. The user interface provides a facility through which users may affect, interact, and/or operate a computer system. A user interface may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the user interface communicates with operating systems, other program components, and/or the like. The user interface may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.


Web Browser

A Web browser component 918 is a stored program component that is executed by a CPU. The Web browser may be a conventional hypertext viewing application such as Microsoft Internet Explorer or Netscape Navigator. Secure Web browsing may be supplied with 128 bit (or greater) encryption by way of HTTPS, SSL, and/or the like. Web browsers allowing for the execution of program components through facilities such as ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, web browser plug-in APIs (e.g., FireFox, Safari Plug-in, and/or the like APIs), and/or the like. Web browsers and like information access tools may be integrated into PDAs, cellular telephones, and/or other mobile devices. A Web browser may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the Web browser communicates with information servers, operating systems, integrated program components (e.g., plug-ins), and/or the like; e.g., it may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. Also, in place of a Web browser and information server, a combined application may be developed to perform similar operations of both. The combined application would similarly affect the obtaining and the provision of information to users, user agents, and/or the like from the P-STATE enabled nodes. The combined application may be nugatory on systems employing standard Web browsers.


Mail Server

A mail server component 921 is a stored program component that is executed by a CPU 903. The mail server may be a conventional Internet mail server such as, but not limited to sendmail, Microsoft Exchange, and/or the like. The mail server may allow for the execution of program components through facilities such as ASP, ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, CGI scripts, Java, JavaScript, PERL, PHP, pipes, Python, WebObjects, and/or the like. The mail server may support communications protocols such as, but not limited to: Internet message access protocol (IMAP), Messaging Application Programming Interface (MAPI)/Microsoft Exchange, post office protocol (POP3), simple mail transfer protocol (SMTP), and/or the like. The mail server can route, forward, and process incoming and outgoing mail messages that have been sent, relayed and/or otherwise traversing through and/or to the P-STATE.


Access to the P-STATE mail may be achieved through a number of APIs offered by the individual Web server components and/or the operating system.


Also, a mail server may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, information, and/or responses.


Mail Client

A mail client component 922 is a stored program component that is executed by a CPU 903. The mail client may be a conventional mail viewing application such as Apple Mail, Microsoft Entourage, Microsoft Outlook, Microsoft Outlook Express, Mozilla, Thunderbird, and/or the like. Mail clients may support a number of transfer protocols, such as: IMAP, Microsoft Exchange, POP3, SMTP, and/or the like. A mail client may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the mail client communicates with mail servers, operating systems, other mail clients, and/or the like; e.g., it may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, information, and/or responses. Generally, the mail client provides a facility to compose and transmit electronic mail messages.


Cryptographic Server

A cryptographic server component 920 is a stored program component that is executed by a CPU 903, cryptographic processor 926, cryptographic processor interface 927, cryptographic processor device 928, and/or the like. Cryptographic processor interfaces will allow for expedition of encryption and/or decryption requests by the cryptographic component; however, the cryptographic component, alternatively, may run on a conventional CPU. The cryptographic component allows for the encryption and/or decryption of provided data. The cryptographic component allows for both symmetric and asymmetric (e.g., Pretty Good Protection (PGP)) encryption and/or decryption. The cryptographic component may employ cryptographic techniques such as, but not limited to: digital certificates (e.g., X.509 authentication framework), digital signatures, dual signatures, enveloping, password access protection, public key management, and/or the like. The cryptographic component will facilitate numerous (encryption and/or decryption) security protocols such as, but not limited to: checksum, Data Encryption Standard (DES), Elliptical Curve Encryption (ECC), International Data Encryption Algorithm (IDEA), Message Digest 5 (MD5, which is a one way hash operation), passwords, Rivest Cipher (RC5), Rijndael, RSA (which is an Internet encryption and authentication system that uses an algorithm developed in 1977 by Ron Rivest, Adi Shamir, and Leonard Adleman), Secure Hash Algorithm (SHA), Secure Socket Layer (SSL), Secure Hypertext Transfer Protocol (HTTPS), and/or the like. Employing such encryption security protocols, the P-STATE may encrypt all incoming and/or outgoing communications and may serve as node within a virtual private network (VPN) with a wider communications network. The cryptographic component facilitates the process of “security authorization” whereby access to a resource is inhibited by a security protocol wherein the cryptographic component effects authorized access to the secured resource. In addition, the cryptographic component may provide unique identifiers of content, e.g., employing and MD5 hash to obtain a unique signature for an digital audio file. A cryptographic component may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. The cryptographic component supports encryption schemes allowing for the secure transmission of information across a communications network to enable the P-STATE component to engage in secure transactions if so desired. The cryptographic component facilitates the secure accessing of resources on the P-STATE and facilitates the access of secured resources on remote systems; i.e., it may act as a client and/or server of secured resources. Most frequently, the cryptographic component communicates with information servers, operating systems, other program components, and/or the like. The cryptographic component may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.


The P-STATE Database

The P-STATE database component 919 may be embodied in a database and its stored data. The database is a stored program component, which is executed by the CPU; the stored program component portion configuring the CPU to process the stored data. The database may be a conventional, fault tolerant, relational, scalable, secure database such as Oracle or Sybase. Relational databases are an extension of a flat file. Relational databases consist of a series of related tables. The tables are interconnected via a key field. Use of the key field allows the combination of the tables by indexing against the key field; i.e., the key fields act as dimensional pivot points for combining information from various tables. Relationships generally identify links maintained between tables by matching primary keys. Primary keys represent fields that uniquely identify the rows of a table in a relational database. More precisely, they uniquely identify rows of a table on the “one” side of a one-to-many relationship.


Alternatively, the P-STATE database may be implemented using various standard data-structures, such as an array, hash, (linked) list, struct, structured text file (e.g., XML), table, and/or the like. Such data-structures may be stored in memory and/or in (structured) files. In another alternative, an object-oriented database may be used, such as Frontier, ObjectStore, Poet, Zope, and/or the like. Object databases can include a number of object collections that are grouped and/or linked together by common attributes; they may be related to other object collections by some common attributes. Object-oriented databases perform similarly to relational databases with the exception that objects are not just pieces of data but may have other types of capabilities encapsulated within a given object. If the P-STATE database is implemented as a data-structure, the use of the P-STATE database 919 may be integrated into another component such as the P-STATE component 935. Also, the database may be implemented as a mix of data structures, objects, and relational structures. Databases may be consolidated and/or distributed in countless variations through standard data processing techniques. Portions of databases, e.g., tables, may be exported and/or imported and thus decentralized and/or integrated.


In one embodiment, the database component 919 includes several tables 919a-o. A user table 919a includes fields such as, but not limited to: a user_ID, name, home_address, work_address, telephone_number, email, merchant_ID client_id, account_id, and/or the like. The user table may support and/or track multiple entity accounts on a P-STATE. A merchant/service provider table 919b includes fields such as, but not limited to: merchant_ID, merchant_name, merchant_location, merchant_address, merchant_category_code, merchant_api_key, loyalty_program_ID and/or the like. A customer profile table 919c includes fields such as, but not limited to: user_ID, merchant_ID, payment_card_ID, preferred_payment_type, demographics, prefetch_preferences, and/or the like. A permissions table 919d includes fields such as, but not limited to: customer ID, transaction execution authorization status, confirmation authorization status, billing authorization status, subscription payment authorization status, and/or the like. A payment card table 919e includes fields such as, but not limited to: payment_card_id, user_id, identifier, brand, expiration date, spending limit, billing address, issuer, name, nick name, loyalty program ID, and/or the like. A billing agreement table 919f includes fields such as, but not limited to: customer_id, billing_id, billing_date, billing_amount_limit, confirmation requirement, authentication_level, billing_authorization_status, and/or the like. A redemption table 919g includes fields such as, but not limited to: customer_id, loyalty_program_id, coupon_id, redemption_date, redemption_time, redemption_amount, redemption_type, transaction_id, and/or the like. A loyalty table 919h includes fields such as, but not limited to: loyalty program ID, rules, loyalty currency amount, loyalty expiry date, transaction ID, and/or the like. A coupons table 919i includes fields such as, but not limited to: coupon ID, coupon value, coupon accepted location, coupon expiry date, and/or the like. A wish list table 919j includes fields such as, but not limited to: wish list ID, merchant ID, item ID, and/or the like. A shopping lists table 919k includes fields such as, but not limited to: shopping_lists_ID, merchant_ID, item_ID, transaction_ID, and/or the like. A store injections table 919l includes fields such as, but not limited to: store_injection_id, merchant_id, item_id, and/or the like. A transaction table 919m includes fields such as, but not limited to: transaction_id, merchant_id, user_id, session_id, date, time, item_model, manufacturer, price, item_id, and/or the like. A products table 919n includes fields such as, but not limited to: product_id, merchant_id, item_id, and/or the like. A cookie_states table 919o includes fields such as, but not limited to: cookie_states_id, cookie_session_id, states_session_id, merchant_id, timestamp, shopping_list_id, payment_method_id, payment_card_id, search, search_results, platform, checkout, shipper, offer, and/or the like.


An Account table 919e includes fields such as, but not limited to: account_id, account_PAN, account_type, brand, expiration date, spending limit, billing address, issuer, name, nick name, loyalty program ID, and/or the like. A third parties table 919f includes fields such as, but not limited to: 3rd_parties_ID, 3rd_parties_name, 3rd_parties_type, 3rd_parties_location, 3rd_parties_address, 3rd_parties_api_key, prefetch_request_id, user_id, merchant_id, security_credentials, and/or the like. A redemption table 919g includes fields such as, but not limited to: customer ID, loyalty program ID, coupon ID, redemption date, redemption time, redemption amount, redemption type, transaction ID, and/or the like. A loyalty table 919h includes fields such as, but not limited to: loyalty program ID, rules, loyalty currency amount, loyalty expiry date, transaction ID, and/or the like. A coupons table 919i includes fields such as, but not limited to: coupon ID, coupon value, coupon accepted location, coupon expiry date, and/or the like. A wish list table 919j includes fields such as, but not limited to: wish list ID, merchant ID, item ID, and/or the like. A plug-ins table 919k includes fields such as, but not limited to: plug-in ID, plug-in provider ID (merchant ID, issuer ID, etc.), plug-in type, plug-in function, plug-in installation guide, plug-in authorization, plug-in restrictions, and/or the like. A client cookies table 919l includes fields such as, but not limited to: client_cookie_id, session_ID, client_id, user_id, merchant_id, wallet_id, merchant_login, wallet_login, cookie_timestamp, cookie_address, and/or the like. An account balance table 919m includes fields such as, but not limited to: user_ID, Account_ID, issuer, api key, balance amount, balance retrieval date/time, and/or the like, and/or the like. A payments table 919n includes fields such as, but not limited to: user_id, billing ID, billing date, billing amount, Account_ID, authentication level, and/or the like. A prefetch requests table 919o includes fields such as, but not limited to: prefetch_requests_id, user_id, client_id, 3rd_parties_id, api_id, prefetch_info_type, prefetch_info_value, and/or the like.


In one embodiment, the P-STATE database may interact with other database systems. For example, employing a distributed database system, queries and data access by search P-STATE component may treat the combination of the P-STATE database, an integrated data security layer database as a single database entity.


In one embodiment, user programs may contain various user interface primitives, which may serve to update the P-STATE. Also, various accounts may require custom database tables depending upon the environments and the types of clients the P-STATE may need to serve. It should be noted that any unique fields may be designated as a key field throughout. In an alternative embodiment, these tables have been decentralized into their own databases and their respective database controllers (i.e., individual database controllers for each of the above tables). Employing standard data processing techniques, one may further distribute the databases over several computer systemizations and/or storage devices. Similarly, configurations of the decentralized database controllers may be varied by consolidating and/or distributing the various database components 919a-o. The P-STATE may be configured to keep track of various settings, inputs, and parameters via database controllers.


The P-STATE database may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the P-STATE database communicates with the P-STATE component, other program components, and/or the like. The database may contain, retain, and provide information regarding other nodes and data.


The P-STATEs

The P-STATE component 935 is a stored program component that is executed by a CPU. In one embodiment, the P-STATE component incorporates any and/or all combinations of the aspects of the P-STATE that was discussed in the previous figures. As such, the P-STATE affects accessing, obtaining and the provision of information, services, transactions, and/or the like across various communications networks.


The P-STATE transforms inputs such as purchase action input (e.g., 211), cookie states search criteria input (e.g., 511), and cookie states selection input (e.g., 711) via P-STATE components such as cookie/states storage (“CSS”) component 941; cookie states search presentation (“CSSP”) component 942; and cookie/states reload/recreate (“CSRR”) component 943, into cookie state presentation (e.g., 525, 760) outputs.


The P-STATE component enabling access of information between nodes may be developed by employing standard development tools and languages such as, but not limited to: Apache components, Assembly, ActiveX, binary executables, (ANSI) (Objective-) C (++), C# and/or .NET, database adapters, CGI scripts, Java, JavaScript, mapping tools, procedural and object oriented development tools, PERL, PHP, Python, shell scripts, SQL commands, web application server extensions, web development environments and libraries (e.g., Microsoft's ActiveX; Adobe AIR, FLEX & FLASH; AJAX; (D)HTML; Dojo, Java; JavaScript; jQuery(UI); MooTools; Prototype; script.aculo.us; Simple Object Access Protocol (SOAP); SWFObject; Yahoo! User Interface; and/or the like), WebObjects, and/or the like. In one embodiment, the P-STATE server employs a cryptographic server to encrypt and decrypt communications. The P-STATE component may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the P-STATE component communicates with the P-STATE database, operating systems, other program components, and/or the like. The P-STATE may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.


Distributed P-STATEs

The structure and/or operation of any of the P-STATE node controller components may be combined, consolidated, and/or distributed in any number of ways to facilitate development and/or deployment. Similarly, the component collection may be combined in any number of ways to facilitate deployment and/or development. To accomplish this, one may integrate the components into a common code base or in a facility that can dynamically load the components on demand in an integrated fashion.


The component collection may be consolidated and/or distributed in countless variations through standard data processing and/or development techniques. Multiple instances of any one of the program components in the program component collection may be instantiated on a single node, and/or across numerous nodes to improve performance through load-balancing and/or data-processing techniques. Furthermore, single instances may also be distributed across multiple controllers and/or storage devices; e.g., databases. All program component instances and controllers working in concert may do so through standard data processing communication techniques.


The configuration of the P-STATE controller will depend on the context of system deployment. Factors such as, but not limited to, the budget, capacity, location, and/or use of the underlying hardware resources may affect deployment requirements and configuration. Regardless of if the configuration results in more consolidated and/or integrated program components, results in a more distributed series of program components, and/or results in some combination between a consolidated and distributed configuration, data may be communicated, obtained, and/or provided. Instances of components consolidated into a common code base from the program component collection may communicate, obtain, and/or provide data. This may be accomplished through intra-application data processing communication techniques such as, but not limited to: data referencing (e.g., pointers), internal messaging, object instance variable communication, shared memory space, variable passing, and/or the like.


If component collection components are discrete, separate, and/or external to one another, then communicating, obtaining, and/or providing data with and/or to other component components may be accomplished through inter-application data processing communication techniques such as, but not limited to: Application Program Interfaces (API) information passage; (distributed) Component Object Model ((D)COM), (Distributed) Object Linking and Embedding ((D)OLE), and/or the like), Common Object Request Broker Architecture (CORBA), Jini local and remote application program interfaces, JavaScript Object Notation (JSON), Remote Method Invocation (RMI), SOAP, process pipes, shared files, and/or the like. Messages sent between discrete component components for inter-application communication or within memory spaces of a singular component for intra-application communication may be facilitated through the creation and parsing of a grammar. A grammar may be developed by using development tools such as lex, yacc, XML, and/or the like, which allow for grammar generation and parsing capabilities, which in turn may form the basis of communication messages within and between components.


For example, a grammar may be arranged to recognize the tokens of an HTTP post command, e.g.:

    • w3c -post http:// . . . Value1


where Value1 is discerned as being a parameter because “http://” is part of the grammar syntax, and what follows is considered part of the post value. Similarly, with such a grammar, a variable “Value1” may be inserted into an “http://” post command and then sent. The grammar syntax itself may be presented as structured data that is interpreted and/or otherwise used to generate the parsing mechanism (e.g., a syntax description text file as processed by lex, yacc, etc.). Also, once the parsing mechanism is generated and/or instantiated, it itself may process and/or parse structured data such as, but not limited to: character (e.g., tab) delineated text, HTML, structured text streams, XML, and/or the like structured data. In another embodiment, inter-application data processing protocols themselves may have integrated and/or readily available parsers (e.g., JSON, SOAP, and/or like parsers) that may be employed to parse (e.g., communications) data. Further, the parsing grammar may be used to beyond message parsing, but may also be used to parse: databases, data collections, data stores, structured data, and/or the like. Again, the desired configuration will depend upon the context, environment, and requirements of system deployment.


For example, in some implementations, the P-STATE controller may be executing a PHP script implementing a Secure Sockets Layer (“SSL”) socket server via the information sherver, which listens to incoming communications on a server port to which a client may send data, e.g., data encoded in JSON format. Upon identifying an incoming communication, the PHP script may read the incoming message from the client device, parse the received JSON-encoded text data to extract information from the JSON-encoded text data into PHP script variables, and store the data (e.g., client identifying information, etc.) and/or extracted information in a relational database accessible using the Structured Query Language (“SQL”). An exemplary listing, written substantially in the form of PHP/SQL commands, to accept JSON-encoded input data from a client device via a SSL connection, parse the data to extract variables, and store the data to a database, is provided below:














<?PHP


header(′Content-Type: text/plain′);


// set ip address and port to listen to for incoming data


$address = ‘192.168.0.100’;


$port = 255;


// create a server-side SSL socket, listen for/accept incoming


communication


$sock = socket_create(AF_INET, SOCK_STREAM, 0);


socket_bind($sock, $address, $port) or die(‘Could not bind to address’);


socket_listen($sock);


$client = socket_accept($sock);


// read input data from client device in 1024 byte blocks until end of


message


do {









$input = “”;



$input = socket_read($client, 1024);



$data .= $input;







} while($input != “”);


// parse data to extract variables


$obj = json_decode($data, true);


// store input data in a database


mysql_connect(″201.408.185.132″,$DBserver,$password); // access


database server


mysql_select(″CLIENT_DB.SQL″); // select database to append


mysql_query(″INSERT INTO UserTable (transmission)


VALUES ($data)”); // add data to UserTable table in a CLIENT database


mysql_close(″CLIENT_DB.SQL″); // close connection to database


?>









Also, the following resources may be used to provide example embodiments regarding SOAP parser implementation:














http://www.xav.com/perl/site/lib/SOAP/Parser.html


http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=


/com.ibm.IBMDI.doc/referenceguide295.htm









and other parser implementations:














http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=


/com.ibm.IBMDI.doc/referenceguide259.htm









all of which are hereby expressly incorporated by reference.


In order to address various issues and advance the art, the entirety of this application for REMOTE DECOUPLED APPLICATION PERSISTENT STATE APPARATUSES, METHODS AND SYSTEMS (including the Cover Page, Title, Headings, Field, Background, Summary, Brief Description of the Drawings, Detailed Description, Claims, Abstract, Figures, Appendices, and otherwise) shows, by way of illustration, various embodiments in which the claimed innovations may be practiced. The advantages and features of the application are of a representative sample of embodiments only, and are not exhaustive and/or exclusive. They are presented only to assist in understanding and teach the claimed principles. It should be understood that they are not representative of all claimed innovations. As such, certain aspects of the disclosure have not been discussed herein. That alternate embodiments may not have been presented for a specific portion of the innovations or that further undescribed alternate embodiments may be available for a portion is not to be considered a disclaimer of those alternate embodiments. It will be appreciated that many of those undescribed embodiments incorporate the same principles of the innovations and others are equivalent. Thus, it is to be understood that other embodiments may be utilized and functional, logical, operational, organizational, structural and/or topological modifications may be made without departing from the scope and/or spirit of the disclosure. As such, all examples and/or embodiments are deemed to be non-limiting throughout this disclosure. Also, no inference should be drawn regarding those embodiments discussed herein relative to those not discussed herein other than it is as such for purposes of reducing space and repetition. For instance, it is to be understood that the logical and/or topological structure of any combination of any program components (a component collection), other components and/or any present feature sets as described in the figures and/or throughout are not limited to a fixed operating order and/or arrangement, but rather, any disclosed order is exemplary and all equivalents, regardless of order, are contemplated by the disclosure. Furthermore, it is to be understood that such features are not limited to serial execution, but rather, any number of threads, processes, services, servers, and/or the like that may execute asynchronously, concurrently, in parallel, simultaneously, synchronously, and/or the like are contemplated by the disclosure. As such, some of these features may be mutually contradictory, in that they cannot be simultaneously present in a single embodiment. Similarly, some features are applicable to one aspect of the innovations, and inapplicable to others. In addition, the disclosure includes other innovations not presently claimed. Applicant reserves all rights in those presently unclaimed innovations including the right to claim such innovations, file additional applications, continuations, continuations in part, divisions, and/or the like thereof. As such, it should be understood that advantages, embodiments, examples, functional, features, logical, operational, organizational, structural, topological, and/or other aspects of the disclosure are not to be considered limitations on the disclosure as defined by the claims or limitations on equivalents to the claims. It is to be understood that, depending on the particular needs and/or characteristics of a P-STATE individual and/or enterprise user, database configuration and/or relational model, data type, data transmission and/or network framework, syntax structure, and/or the like, various embodiments of the P-STATE, may be implemented that enable a great deal of flexibility and customization. For example, aspects of the P-STATE may be adapted for system latency reduction. While various embodiments and discussions of the P-STATE have been directed to prefetching and on-demand fetching user account information, however, it is to be understood that the embodiments described herein may be readily configured and/or customized for a wide variety of other applications and/or implementations.

Claims
  • 1. A method comprising: receiving a purchase action from a first user device associated with a user;creating and storing a first cookie associated with the purchase action;receiving, from a second user device, a request for cookie data related to products viewed by the user in the previous purchase action on a platform other than the second user device;identifying the first cookie in response to the request for cookie data;determining a platform type of the second user device;generating a second cookie compliant with the platform type of the second user device based on the first cookie; andsending the generated second cookie to the second user device, the second cookie including instructions to present the product viewed by the user in the previous purchase action.
  • 2. The method of claim 1, wherein the first cookie stores a state of the user's browsing and purchase history associated with a digital wallet account of the user.
  • 3. The method of claim 2, wherein the first cookie contains multiple states.
  • 4. The method of claim 3 further comprising providing cloud-based storage to a merchant associated with the purchase action such that the user can retrieve any of the multiple states associated with the merchant.
  • 5. The method of claim 2, wherein the first cookie is used to recognize that the user has previously paid for a particular purchase.
  • 6. The method of claim 1, wherein the first cookie is stored in a database associated with a digital wallet account of the user.
  • 7. The method of claim 6 further comprising providing a user interface for searching the database.
  • 8. The method of claim 1, wherein the first cookie includes at least one of a timestamp of when the purchase action took place, a merchant associated with the purchase action, a shopping cart status, shipper information associated with the purchase action, offer information, payment method information, checkout status, search criteria, purchase status, or a platform type of the first device.
  • 9. The method of claim 1, wherein multiple states of a user's browsing history are combined into the first cookie.
  • 10. The method of claim 9 further comprising providing a preview window to facilitate viewing the multiple states included in the first cookie.
  • 11. A non-transitory computer readable medium storing instructions that, when executed, cause an apparatus at least to perform: receiving a purchase action from a first user device associated with a user;creating and storing a first cookie associated with the purchase action;receiving, from a second user device, a request for cookie data related to products viewed by the user in the previous purchase action on a platform other than the second user device;identifying the first cookie in response to the request for cookie data;determining a platform type of the second user device;generating a second cookie compliant with the platform type of the second user device based on the first cookie; andsending the generated second cookie to the second user device, the second cookie including instructions to present the product viewed by the user in the previous purchase action.
  • 12. The non-transitory computer readable medium of claim 11, wherein the first cookie stores a state of the user's browsing and purchase history associated with a digital wallet account of the user.
  • 13. The non-transitory computer readable medium of claim 12, wherein the first cookie contains multiple states.
  • 14. The non-transitory computer readable medium of claim 13, further comprising instructions causing the apparatus to perform providing cloud-based storage to a merchant associated with the purchase action such that the user can retrieve any of the multiple states associated with the merchant.
  • 15. The non-transitory computer readable medium of claim 11, wherein the first cookie is stored in a database associated with a digital wallet account of the user.
  • 16. The non-transitory computer readable medium of claim 15, further comprising instructions causing the apparatus to perform providing a user interface for searching the database.
  • 17. The non-transitory computer readable medium of claim 11, wherein the first cookie is used to recognize that the user has previously paid for a particular purchase.
  • 18. A platform-specific cookie generating apparatus comprising: a memory; anda processor disposed in communication with said memory, and configured to issue a plurality of processing instructions stored in the memory, wherein the processor issues instructions to:receiving a purchase action from a first user device associated with a user;creating and storing a first cookie associated with the purchase action;receiving, from a second user device, a request for cookie data related to products viewed by the user in the previous purchase action on a platform other than the second user device;identifying the first cookie in response to the request for cookie data;determining a platform type of the second user device;generating a second cookie compliant with the platform type of the second user device based on the first cookie; andsending the generated second cookie to the second user device, the second cookie including instructions to present the product viewed by the user in the previous purchase action.
  • 19. The apparatus of claim 18, wherein the first cookie stores a state of the user's browsing and purchase history associated with a digital wallet account of the user.
  • 20. The apparatus of claim 19, wherein the first cookie contains multiple states.
PRIORITY CLAIM

This application is a continuation of U.S. patent application Ser. No. 14/216,351, filed Mar. 17, 2014, which claims priority to U.S. Patent Application Ser. No. 61/798,483, filed Mar. 15, 2013, and is a continuation of U.S. patent application Ser. No. 13/624,779, filed Sep. 21, 2012, which is a continuation-in-part of U.S. patent application Ser. No. 13/589,053, filed Aug. 17, 2012, which claims priority to: U.S. provisional patent application Ser. No. 61/525,168, filed Aug. 18, 2011; U.S. provisional patent application Ser. No. 61/537,421, filed Sep. 21, 2011; U.S. provisional patent application Ser. No. 61/588,620 filed Jan. 19, 2012; and U.S. provisional patent application Ser. No. 61/668,441 filed Jul. 5, 2012. The entire contents of the aforementioned applications are expressly incorporated by reference herein.

US Referenced Citations (1364)
Number Name Date Kind
789106 Seymour May 1905 A
4896363 Taylor Jan 1990 A
5177342 Adams Jan 1993 A
5221838 Gutman Jun 1993 A
5237164 Takada Aug 1993 A
5311594 Penzias May 1994 A
5383113 Kight Jan 1995 A
5384449 Peirce Jan 1995 A
5446890 Renslo Aug 1995 A
5459656 Fields Oct 1995 A
5500513 Langhans Mar 1996 A
5510777 Pilc Apr 1996 A
5521362 Powers May 1996 A
5526409 Conrow Jun 1996 A
5530438 Bickham Jun 1996 A
5536045 Adams Jul 1996 A
5590038 Pitroda Dec 1996 A
5613012 Hoffman Mar 1997 A
5615110 Wong Mar 1997 A
5615264 Kazmierczak Mar 1997 A
5621201 Langhans Apr 1997 A
5640193 Wellner Jun 1997 A
5649118 Carlisle Jul 1997 A
5655007 McAllister Aug 1997 A
5748737 Daggar May 1998 A
5781438 Lee Jul 1998 A
5796832 Kawan Aug 1998 A
5815657 Williams Sep 1998 A
5850446 Berger Dec 1998 A
5878337 Joao Mar 1999 A
5883810 Franklin Mar 1999 A
5884271 Pitroda Mar 1999 A
5892838 Brady Apr 1999 A
5903830 Joao May 1999 A
5914472 Foladare Jun 1999 A
5943624 Fox Aug 1999 A
5953710 Fleming Sep 1999 A
5956699 Wong Sep 1999 A
5963924 Williams Oct 1999 A
6000832 Franklin Dec 1999 A
6006200 Boies Dec 1999 A
6014635 Harris Jan 2000 A
6044360 Picciallo Mar 2000 A
6052675 Checchio Apr 2000 A
6058127 Joannopoulos May 2000 A
6064990 Goldsmith May 2000 A
6092053 Boesch Jul 2000 A
6160903 Hamid Dec 2000 A
6161130 Horvitz Dec 2000 A
6163771 Walker Dec 2000 A
6164533 Barton Dec 2000 A
6182894 Hackett Feb 2001 B1
6195447 Ross Feb 2001 B1
6202052 Miller Mar 2001 B1
6202933 Poore Mar 2001 B1
6226624 Watson May 2001 B1
6227447 Campisano May 2001 B1
6236981 Hill May 2001 B1
6243688 Kalina Jun 2001 B1
6263447 French Jul 2001 B1
6267292 Walker Jul 2001 B1
6327578 Linehan Dec 2001 B1
6336099 Barnett Jan 2002 B1
6339766 Gepharl Jan 2002 B1
6341724 Campisano Jan 2002 B2
6381584 Ogram Apr 2002 B1
6385596 Wiser May 2002 B1
6385655 Smith May 2002 B1
6422462 Cohen Jul 2002 B1
6425523 Shem-Ur Jul 2002 B1
6439345 Recktenwald Aug 2002 B1
6456984 Demoff Sep 2002 B1
6468823 Scherer Oct 2002 B1
6473500 Risafi Oct 2002 B1
6529725 Joao Mar 2003 B1
6535855 Cahill Mar 2003 B1
6560581 Fox May 2003 B1
6592044 Wong Jul 2003 B1
6601761 Katis Aug 2003 B1
6636833 Flitcroft Oct 2003 B1
6735572 Landesmann May 2004 B2
6748367 Lee Jun 2004 B1
6805287 Bishop Oct 2004 B2
6853982 Smith Feb 2005 B2
6857073 French Feb 2005 B2
6865522 Gastiger Mar 2005 B1
6873974 Schutzer Mar 2005 B1
6879965 Fung Apr 2005 B2
6891953 DeMello May 2005 B1
6898598 Himmel May 2005 B2
6901387 Wells May 2005 B2
6925439 Pitroda Aug 2005 B1
6931382 Laage Aug 2005 B2
6934528 Loureiro Aug 2005 B2
6938019 Uzo Aug 2005 B1
6941285 Sarcanin Sep 2005 B2
6944595 Graser Sep 2005 B1
6980670 Hoffman Dec 2005 B1
6990470 Hogan Jan 2006 B2
6991157 Bishop Jan 2006 B2
6999943 Johnson Feb 2006 B1
7024383 Mancini Apr 2006 B1
7028052 Chapman Apr 2006 B2
7047041 Vanska May 2006 B2
7051002 Keresman, III May 2006 B2
7051929 Li May 2006 B2
7069249 Stolfo Jun 2006 B2
7089208 Levchin Aug 2006 B1
7096003 Joao Aug 2006 B2
7103576 Mann Sep 2006 B2
7111789 Rajasekaran Sep 2006 B2
7113930 Eccles Sep 2006 B2
7117172 Black Oct 2006 B1
7136835 Flitcroft Nov 2006 B1
7155411 Blinn Dec 2006 B1
7156311 Attia Jan 2007 B2
7167903 Percival Jan 2007 B2
7177835 Walker Feb 2007 B1
7177848 Hogan Feb 2007 B2
7180457 Trott Feb 2007 B2
7194437 Britto Mar 2007 B1
7206847 Alberth Apr 2007 B1
7209561 Shankar Apr 2007 B1
7212979 Matz May 2007 B1
7228011 Queeno Jun 2007 B1
RE39736 Morrill Jul 2007 E
7264154 Harris Sep 2007 B2
7266557 Aschen Sep 2007 B2
7268667 Beenau Sep 2007 B2
7268668 Beenau Sep 2007 B2
7287692 Patel Oct 2007 B1
7290704 Ball Nov 2007 B1
7292999 Hobson Nov 2007 B2
7313546 Alarcon-Luther Dec 2007 B2
7318049 Iannacci Jan 2008 B2
7337119 Geschwender Feb 2008 B1
7337144 Blinn Feb 2008 B1
7343149 Benco Mar 2008 B2
7343351 Bishop Mar 2008 B1
7349885 Gangi Mar 2008 B2
7350230 Forrest Mar 2008 B2
7353382 Labrou Apr 2008 B2
7356505 March Apr 2008 B2
7357310 Calabrese Apr 2008 B2
7359880 Abel Apr 2008 B2
7373669 Eisen May 2008 B2
7379899 Junger May 2008 B1
7379919 Hogan May 2008 B2
7392222 Hamilton Jun 2008 B1
RE40444 Linehan Jul 2008 E
7395242 Blinn Jul 2008 B2
7398250 Blinn Jul 2008 B2
7413113 Zhu Aug 2008 B1
7415443 Hobson Aug 2008 B2
7415469 Singh Aug 2008 B2
7427021 Kemper Sep 2008 B2
7444676 Asghari-Kamrani Oct 2008 B1
7450966 Vanska Nov 2008 B2
7469151 Khan Dec 2008 B2
7477780 Boncyk Jan 2009 B2
7499889 Golan Mar 2009 B2
7500607 Williams Mar 2009 B2
7505935 Mendiola Mar 2009 B2
7533064 Boesch May 2009 B1
7536318 Wolfe May 2009 B1
7536335 Weston May 2009 B1
7536360 Stolfo May 2009 B2
7540012 Herzberg May 2009 B1
7548889 Bhambri Jun 2009 B2
7567934 Flitcroft Jul 2009 B2
7567936 Peckover Jul 2009 B1
7571139 Giordano Aug 2009 B1
7571140 Weichert Aug 2009 B2
7571142 Flitcroft Aug 2009 B1
7580898 Brown Aug 2009 B2
7584153 Brown Sep 2009 B2
7593858 Matz Sep 2009 B2
7593896 Flitcroft Sep 2009 B1
7603311 Yadav-ranjan Oct 2009 B1
7606560 Labrou Oct 2009 B2
7627531 Breck Dec 2009 B2
7627895 Gifford Dec 2009 B2
7630937 Mo Dec 2009 B1
7634295 Hayaashi Dec 2009 B2
7644037 Ostrovsky Jan 2010 B1
7644859 Zhu Jan 2010 B1
7650314 Saunders Jan 2010 B1
7660749 Koski Feb 2010 B2
7664733 Erol Feb 2010 B2
7668754 Bridgelall Feb 2010 B1
7669760 Zettner Mar 2010 B1
7676434 Evans Mar 2010 B2
7685037 Reiners Mar 2010 B2
7685067 Britto Mar 2010 B1
7698221 Blinn Apr 2010 B2
7702578 Fung Apr 2010 B2
7707113 Dimartino Apr 2010 B1
7707120 Dominguez Apr 2010 B2
7708194 Vawter May 2010 B2
7708198 Gangi May 2010 B2
7712655 Wong May 2010 B2
7712658 Gangi May 2010 B2
7720436 Hamynen May 2010 B2
7734527 Uzo Jun 2010 B2
7739194 Blinn Jun 2010 B2
7742984 Mohsenzadeh Jun 2010 B2
7753265 Harris Jul 2010 B2
7770789 Oder Aug 2010 B2
7774076 Skowronek Aug 2010 B2
7783569 Abel Aug 2010 B2
7784684 Labrou Aug 2010 B2
7784685 Hopkins Aug 2010 B1
7793851 Mullen Sep 2010 B2
7797215 Zerenner Sep 2010 B1
7801826 Labrou Sep 2010 B2
7801829 Gray Sep 2010 B2
7802719 Johnson Sep 2010 B2
7805376 Smith Sep 2010 B2
7805378 Berardi Sep 2010 B2
7810720 Lovett Oct 2010 B2
7818264 Hammad Oct 2010 B2
7819307 Lyons Oct 2010 B2
7827288 Da Nov 2010 B2
7828206 Hessburg Nov 2010 B2
7828220 Mullen Nov 2010 B2
7828992 Kilickiran Nov 2010 B2
7835960 Breck Nov 2010 B2
7837125 Biskupski Nov 2010 B2
7841523 Oder Nov 2010 B2
7841539 Newton Nov 2010 B2
7844530 Ziade Nov 2010 B2
7844550 Walker Nov 2010 B2
7848980 Carlson Dec 2010 B2
7849014 Erikson Dec 2010 B2
7849020 Johnson Dec 2010 B2
7853529 Walker Dec 2010 B1
7853995 Chow Dec 2010 B2
7865414 Fung Jan 2011 B2
7870027 Tannenbaum Jan 2011 B1
7873579 Hobson Jan 2011 B2
7873580 Hobson Jan 2011 B2
7877299 Bui Jan 2011 B2
7878400 Harris Feb 2011 B2
7890370 Whitsitt Feb 2011 B2
7890393 Talbert Feb 2011 B2
7891563 Oder Feb 2011 B2
7895119 Praisner Feb 2011 B2
7896238 Fein Mar 2011 B2
7899744 Bishop Mar 2011 B2
7904360 Evans Mar 2011 B2
7908216 Davis Mar 2011 B1
7908227 Zizzimopoulos Mar 2011 B2
7922082 Muscato Apr 2011 B2
7926714 Zhu Apr 2011 B1
7931195 Mullen Apr 2011 B2
7933779 Rooks Apr 2011 B2
7937324 Patterson May 2011 B2
7938318 Fein May 2011 B2
7942337 Jain May 2011 B2
7954705 Mullen Jun 2011 B2
7959076 Hopkins Jun 2011 B1
7962418 Wei Jun 2011 B1
7963441 Emmons Jun 2011 B2
7967196 Bierbaum Jun 2011 B1
7971782 Shams Jul 2011 B1
7996259 Distefano, III Aug 2011 B1
7996288 Stolfo Aug 2011 B1
8016192 Messerges Sep 2011 B2
8020763 Kowalchyk Sep 2011 B1
8024260 Hogl Sep 2011 B1
8025223 Saunders Sep 2011 B2
8028041 Olliphant Sep 2011 B2
8032438 Barton Oct 2011 B1
8041338 Chen Oct 2011 B2
8046256 Chien Oct 2011 B2
8050997 Nosek Nov 2011 B1
8060413 Castell Nov 2011 B2
8060448 Jones Nov 2011 B2
8060449 Zhu Nov 2011 B1
8073565 Johnson Dec 2011 B2
8074876 Foss Dec 2011 B2
8074877 Mullen Dec 2011 B2
8074879 Harris Dec 2011 B2
8082210 Hansen Dec 2011 B2
8090351 Klein Jan 2012 B2
8095113 Kean Jan 2012 B2
8095602 Orbach Jan 2012 B1
8104679 Brown Jan 2012 B2
8108261 Carlier Jan 2012 B2
RE43157 Bishop Feb 2012 E
8109436 Hopkins Feb 2012 B1
8117127 Sanders Feb 2012 B1
8121942 Carlson Feb 2012 B2
8121956 Carlson Feb 2012 B2
8126449 Beenau Feb 2012 B2
8127982 Casey Mar 2012 B1
8131666 OBrien Mar 2012 B2
8140418 Casey Mar 2012 B1
8145188 Park Mar 2012 B2
8145561 Zhu Mar 2012 B1
8145566 Ahuja Mar 2012 B1
8145569 Gong Mar 2012 B2
8145898 Kamalakantha Mar 2012 B2
8150767 Wankmueller Apr 2012 B2
8150772 Mardikar Apr 2012 B2
8151328 Lundy Apr 2012 B1
8151330 Vishik Apr 2012 B2
8151336 Savoor Apr 2012 B2
8155999 De Boer Apr 2012 B2
8156000 Thompson Apr 2012 B1
8156026 Junger Apr 2012 B2
8156042 Winkleman, III Apr 2012 B2
8156549 Rice Apr 2012 B2
8157178 Dewan Apr 2012 B2
8157181 Bates Apr 2012 B2
8160935 Bui Apr 2012 B2
8160959 Rackley, III Apr 2012 B2
8165961 Dimartino Apr 2012 B1
8166068 Stevens Apr 2012 B2
RE43351 Jordan May 2012 E
8170921 Stocker May 2012 B2
8171525 Pelly May 2012 B1
8175235 Mumford May 2012 B2
8175965 Moore May 2012 B2
8175967 OLeary May 2012 B2
8175968 OLeary May 2012 B2
8175973 Davis May 2012 B2
8175975 Cai May 2012 B2
8175979 Baentsch May 2012 B2
8176416 Williams May 2012 B1
8176554 Kennedy May 2012 B1
8179563 King May 2012 B2
8180289 Glickman May 2012 B1
8180705 Kowalchyk May 2012 B2
8180804 Narayanan May 2012 B1
8190513 Felger May 2012 B2
8190523 Patterson May 2012 B2
8191775 Hildred Jun 2012 B2
8195233 Morikuni Jun 2012 B2
8195544 Horsfall Jun 2012 B2
8195547 Aaltonen Jun 2012 B2
8195565 Bishop Jun 2012 B2
8195576 Grigg Jun 2012 B1
8196131 Von Behren Jun 2012 B1
8196813 Vadhri Jun 2012 B2
8200582 Zhu Jun 2012 B1
8200868 T Hooft Jun 2012 B1
8204774 Chwast Jun 2012 B2
8204829 Alvarez Jun 2012 B2
8205791 Randazza Jun 2012 B2
8209245 Dennes Jun 2012 B2
8209744 Zhu Jun 2012 B2
8214288 Olliphant Jul 2012 B2
8214289 Scipioni Jul 2012 B2
8214291 Pelegero Jul 2012 B2
8214292 Duggal Jul 2012 B2
8214293 Powell Jul 2012 B2
8214886 Foley Jul 2012 B2
8215546 Lin Jul 2012 B2
8219411 Matz Jul 2012 B2
8219474 Sutton Jul 2012 B2
8219489 Patterson Jul 2012 B2
8219490 Hammad Jul 2012 B2
8220047 Soghoian Jul 2012 B1
8224702 Mangerink Jul 2012 B2
8224754 Pastusiak Jul 2012 B2
8224773 Spiegel Jul 2012 B2
8225385 Chow Jul 2012 B2
8225997 Bierbaum Jul 2012 B1
8227936 Folk Jul 2012 B1
8229354 Sklovsky Jul 2012 B2
8229808 Heit Jul 2012 B1
8229844 Felger Jul 2012 B2
8229851 Doran Jul 2012 B2
8229852 Carlson Jul 2012 B2
8229854 Stephen Jul 2012 B2
8233841 Griffin Jul 2012 B2
8234183 Smith Jul 2012 B2
8239276 Lin Aug 2012 B2
8244580 Mankoff Aug 2012 B2
8245139 Michelman Aug 2012 B2
8249925 Broms Aug 2012 B2
8249965 Tumminaro Aug 2012 B2
8255278 Young Aug 2012 B1
8255323 Casey Aug 2012 B1
8255324 Bercy Aug 2012 B2
8265993 Chien Sep 2012 B2
8275704 Bishop Sep 2012 B2
8280777 Mengerink Oct 2012 B2
8281991 Wentker Oct 2012 B2
8281998 Tang Oct 2012 B2
8282002 Shams Oct 2012 B2
8285640 Scipioni Oct 2012 B2
8285820 Olliphant Oct 2012 B2
8285832 Schwab Oct 2012 B2
8286875 Tang Oct 2012 B2
8290433 Fisher Oct 2012 B2
8290819 Bawcutt Oct 2012 B2
8290829 Katz Oct 2012 B1
8295898 Ashfield Oct 2012 B2
8296187 Light Oct 2012 B2
8296204 Templeton Oct 2012 B2
8296228 Kloor Oct 2012 B1
8296231 Britto Oct 2012 B2
8301500 Pharris Oct 2012 B2
8301510 Boesch Oct 2012 B2
8301556 Hogl Oct 2012 B2
8311520 Choi Nov 2012 B2
8312096 Cohen Nov 2012 B2
8321267 Hoerenz Nov 2012 B2
8321294 Carlier Nov 2012 B2
8321315 Abel Nov 2012 B2
8321338 Baumgart Nov 2012 B2
8321343 Ramavarjula Nov 2012 B2
8321364 Gharpure Nov 2012 B1
8326756 Egendorf Dec 2012 B2
8326769 Weisman Dec 2012 B1
8326770 Weisman Dec 2012 B1
8327450 Clement Dec 2012 B2
8328095 Oder Dec 2012 B2
8332272 Fisher Dec 2012 B2
8332275 Poon Dec 2012 B2
8332323 Stals Dec 2012 B2
8335720 Juang Dec 2012 B2
8335726 Ling Dec 2012 B1
8335822 Ahmed Dec 2012 B2
8335921 Von Behren Dec 2012 B2
8335932 Von Behren Dec 2012 B2
8336088 Raj Dec 2012 B2
8340666 Ramer Dec 2012 B2
8341029 Ramalingam Dec 2012 B1
8346643 Boyer Jan 2013 B2
8346659 Mohsenzadeh Jan 2013 B1
8346663 Kawan Jan 2013 B2
8346666 Lindelsee Jan 2013 B2
8352323 Fisher Jan 2013 B2
8352362 Mohsenzadeh Jan 2013 B2
8352499 Bharat Jan 2013 B2
8352749 Von Behren Jan 2013 B2
8355987 Hirson Jan 2013 B2
8359070 Zhu Jan 2013 B1
8364587 Nuzum Jan 2013 B2
8364590 Casey Jan 2013 B1
8370264 Wei Feb 2013 B1
8376225 Hopkins Feb 2013 B1
8380177 Laracey Feb 2013 B2
8380349 Hickman Feb 2013 B1
8386078 Hickman Feb 2013 B1
8387873 Saunders Mar 2013 B2
8396750 Hariharan Mar 2013 B1
8396810 Cook Mar 2013 B1
8401539 Beenau Mar 2013 B2
8401898 Chien Mar 2013 B2
8401904 Simakov Mar 2013 B1
8402555 Grecia Mar 2013 B2
8403211 Brooks Mar 2013 B2
8412586 Foulser Apr 2013 B1
8412623 Moon Apr 2013 B2
8412630 Ross Apr 2013 B2
8412837 Emigh Apr 2013 B1
8417633 Chmara Apr 2013 B1
8417642 Oren Apr 2013 B2
8423462 Amacker Apr 2013 B1
8429521 Lloyd Apr 2013 B2
8437633 Chmara Apr 2013 B2
8447699 Batada May 2013 B2
8453223 Svigals May 2013 B2
8453925 Fisher Jun 2013 B2
8458487 Palgon Jun 2013 B1
8484134 Hobson Jul 2013 B2
8485437 Mullen Jul 2013 B2
8494959 Hathaway Jul 2013 B2
8498908 Mengerink Jul 2013 B2
8504475 Brand Aug 2013 B2
8504478 Saunders Aug 2013 B2
8510816 Quach Aug 2013 B2
8433116 Davis Sep 2013 B2
8527360 Groat Sep 2013 B2
8533860 Grecia Sep 2013 B1
8538845 Liberty Sep 2013 B2
8555079 Shablygin Oct 2013 B2
8560004 Tsvetkov Oct 2013 B1
8566168 Bierbaum Oct 2013 B1
8567670 Stanfield Oct 2013 B2
8571939 Lindsey Oct 2013 B2
8577336 Mechaley Nov 2013 B2
8577803 Chatterjee Nov 2013 B2
8577813 Weiss Nov 2013 B2
8578176 Mattsson Nov 2013 B2
8583494 Fisher Nov 2013 B2
8584251 McGuire Nov 2013 B2
8589237 Fisher Nov 2013 B2
8589271 Evans Nov 2013 B2
8589291 Carlson Nov 2013 B2
8595098 Starai Nov 2013 B2
8595812 Bomar Nov 2013 B2
8595850 Spies Nov 2013 B2
8606060 Hamann Dec 2013 B2
8606638 Dragt Dec 2013 B2
8606700 Carlson Dec 2013 B2
8606720 Baker Dec 2013 B1
8612325 Stacy Dec 2013 B2
8615468 Varadarajan Dec 2013 B2
8620754 Fisher Dec 2013 B2
8627420 Furlan Jan 2014 B2
8635157 Smith Jan 2014 B2
8639621 Ellis Jan 2014 B1
8646059 von Behren Feb 2014 B1
8651374 Brabson Feb 2014 B2
8656180 Shablygin Feb 2014 B2
8661495 Reisman Feb 2014 B2
8662384 Dodin Mar 2014 B2
8739016 Goldman May 2014 B1
8751391 Freund Jun 2014 B2
8762263 Gauthier Jun 2014 B2
8793186 Patterson Jul 2014 B2
8838982 Carlson Sep 2014 B2
8856539 Weiss Oct 2014 B2
8887308 Grecia Nov 2014 B2
8893009 Raleigh Nov 2014 B2
9065643 Hurry Jun 2015 B2
9070129 Sheets Jun 2015 B2
9082119 Ortiz Jul 2015 B2
9100826 Weiss Aug 2015 B2
9105050 Tietzen Aug 2015 B2
9160741 Wentker Oct 2015 B2
9195750 Hayden Nov 2015 B2
9229964 Stevelinck Jan 2016 B2
9245267 Singh Jan 2016 B2
9249241 Dai Feb 2016 B2
9256871 Anderson Feb 2016 B2
9280765 Hammad Mar 2016 B2
9307342 Sojoodi Apr 2016 B2
9355393 Purves May 2016 B2
9448972 Greenberg Sep 2016 B2
9524089 Ghosh Dec 2016 B1
9530137 Weiss Dec 2016 B2
9582598 Kalgi Feb 2017 B2
9626351 Davis Apr 2017 B2
9710807 Theurer Jul 2017 B2
9772987 Davis Sep 2017 B2
9804834 Lopyrev Oct 2017 B1
9846863 Grossi Dec 2017 B2
9904537 Lopyrev Feb 2018 B2
10360561 Poon Jul 2019 B2
20010037297 McNair Mar 2001 A1
20010029485 Brody Oct 2001 A1
20010034720 Armes Oct 2001 A1
20010049635 Chung Dec 2001 A1
20010054003 Chien Dec 2001 A1
20010056359 Abreu Dec 2001 A1
20010056409 Bellovin Dec 2001 A1
20020002522 Clift Jan 2002 A1
20020004783 Paltenghe Jan 2002 A1
20020007320 Hogan Jan 2002 A1
20020016749 Borecki Feb 2002 A1
20020026575 Wheeler Feb 2002 A1
20020029193 Ranjan Mar 2002 A1
20020035548 Hogan Mar 2002 A1
20020040325 Takae Apr 2002 A1
20020046184 Villaret Apr 2002 A1
20020048422 Cotteverte Apr 2002 A1
20020052778 Murphy May 2002 A1
20020069122 Yun Jun 2002 A1
20020073045 Rubin Jun 2002 A1
20020077976 Meyer Jun 2002 A1
20020077978 OLeary Jun 2002 A1
20020087894 Foley Jul 2002 A1
20020099642 Schwankl Jul 2002 A1
20020099647 Howorka Jul 2002 A1
20020099656 Poh Wong Jul 2002 A1
20020107755 Steed Aug 2002 A1
20020111919 Weller Aug 2002 A1
20020112014 Bennett Aug 2002 A1
20020116271 Mankoff Aug 2002 A1
20020116341 Hogan Aug 2002 A1
20020120864 Wu Aug 2002 A1
20020128977 Nambiar Sep 2002 A1
20020133467 Hobson Sep 2002 A1
20020138290 Metcalfe Sep 2002 A1
20020138445 Laage Sep 2002 A1
20020141575 Hird Oct 2002 A1
20020143614 MacLean Oct 2002 A1
20020147913 Lun Yip Oct 2002 A1
20020174030 Praisner Nov 2002 A1
20020178370 Gurevich Nov 2002 A1
20020194081 Perkowski Dec 2002 A1
20030014307 Heng Jan 2003 A1
20030018524 Fishman Jan 2003 A1
20030026404 Joyce Feb 2003 A1
20030028451 Ananian Feb 2003 A1
20030028481 Flitcroft Feb 2003 A1
20030055785 Lahiri Mar 2003 A1
20030080185 Werther May 2003 A1
20030097318 Yu May 2003 A1
20030101134 Liu May 2003 A1
20030126076 Kwok Jul 2003 A1
20030130955 Hawthorne Jul 2003 A1
20030144935 Sobek Jul 2003 A1
20030174823 Justice Sep 2003 A1
20030177361 Wheeler Sep 2003 A1
20030179230 Seidman Sep 2003 A1
20030191709 Elston Oct 2003 A1
20030191711 Jamison Oct 2003 A1
20030191945 Keech Oct 2003 A1
20030195659 Kasuga Oct 2003 A1
20030200142 Hicks Oct 2003 A1
20030200184 Dominguez Oct 2003 A1
20030212589 Kish Nov 2003 A1
20030212642 Weller Nov 2003 A1
20030216996 Cummings Nov 2003 A1
20030220835 Barnes Nov 2003 A1
20040010462 Moon Jan 2004 A1
20040030601 Pond Feb 2004 A1
20040050928 Bishop Mar 2004 A1
20040059682 Hasumi Mar 2004 A1
20040068443 Hopson Apr 2004 A1
20040078332 Ferguson Apr 2004 A1
20040093281 Silverstein May 2004 A1
20040103037 Wetmore May 2004 A1
20040103063 Takayama May 2004 A1
20040111698 Soong Jun 2004 A1
20040128197 Bam Jul 2004 A1
20040138999 Friedman Jul 2004 A1
20040139008 Mascavage Jul 2004 A1
20040143532 Lee Jul 2004 A1
20040148255 Beck Jul 2004 A1
20040158532 Breck Aug 2004 A1
20040204128 Zakharia Oct 2004 A1
20040210449 Breck Oct 2004 A1
20040210498 Freund Oct 2004 A1
20040215560 Amalraj Oct 2004 A1
20040215963 Kaplan Oct 2004 A1
20040230536 Fung Nov 2004 A1
20040232225 Bishop Nov 2004 A1
20040236646 Wu Nov 2004 A1
20040236819 Anati Nov 2004 A1
20040243520 Bishop Dec 2004 A1
20040254891 Blinn Dec 2004 A1
20040260646 Berardi Dec 2004 A1
20040267608 Mansfield Dec 2004 A1
20040267655 Davidowitz Dec 2004 A1
20040267878 Osias Dec 2004 A1
20050010483 Ling Jan 2005 A1
20050037735 Courts Feb 2005 A1
20050038724 Roever Feb 2005 A1
20050065819 Pamela Mar 2005 A1
20050080730 Sorrentino Apr 2005 A1
20050080732 Warin Apr 2005 A1
20050080747 Anderson Apr 2005 A1
20050080821 Breil Apr 2005 A1
20050097320 Golan May 2005 A1
20050101309 Croome May 2005 A1
20050102188 Hutchison May 2005 A1
20050108178 York May 2005 A1
20050114784 Spring May 2005 A1
20050137969 Shah Jun 2005 A1
20050144082 Coolman Jun 2005 A1
20050171894 Traynor Aug 2005 A1
20050171898 Bishop Aug 2005 A1
20050184145 Law Aug 2005 A1
20050187873 Labrou Aug 2005 A1
20050192893 Keeling Sep 2005 A1
20050192895 Rogers Sep 2005 A1
20050199709 Linlor Sep 2005 A1
20050201660 Grot Sep 2005 A1
20050220326 Sim Oct 2005 A1
20050234817 VanFleet Oct 2005 A1
20050246278 Gerber Nov 2005 A1
20050246293 Ong Nov 2005 A1
20050251446 Jiang Nov 2005 A1
20050254714 Anne Nov 2005 A1
20050256802 Ammermann Nov 2005 A1
20050261967 Barry Nov 2005 A1
20050269401 Spitzer Dec 2005 A1
20050269402 Spitzer Dec 2005 A1
20050273462 Reed Dec 2005 A1
20060002607 Boncyk Jan 2006 A1
20060020542 Litle Jan 2006 A1
20060053056 Alspach-goss Mar 2006 A1
20060059277 Zito Mar 2006 A1
20060069619 Walker Mar 2006 A1
20060075235 Renkis Apr 2006 A1
20060085328 Cohen Apr 2006 A1
20060085477 Phillips Apr 2006 A1
20060124729 Martin Jun 2006 A1
20060129427 Wennberg Jun 2006 A1
20060163349 Neugebauer Jul 2006 A1
20060178918 Mikurak Aug 2006 A1
20060178986 Giordano Aug 2006 A1
20060178994 Stolfo Aug 2006 A1
20060190347 Cuervo Aug 2006 A1
20060195598 Fujita Aug 2006 A1
20060208060 Mendelovich Sep 2006 A1
20060212434 Crawford Sep 2006 A1
20060226216 Keithley Oct 2006 A1
20060235795 Johnson Oct 2006 A1
20060237528 Bishop Oct 2006 A1
20060247982 Stolfo Nov 2006 A1
20060277143 Almonte Dec 2006 A1
20060278704 Saunders Dec 2006 A1
20060280396 Wu Dec 2006 A1
20060282332 Pfleging Dec 2006 A1
20060293947 Nicholson Dec 2006 A1
20070011025 Cracchiolo Jan 2007 A1
20070016523 Blair Jan 2007 A1
20070022007 Lawe Jan 2007 A1
20070038515 Postrel Feb 2007 A1
20070038516 Apple Feb 2007 A1
20070055571 Fox Mar 2007 A1
20070067215 Agarwal Mar 2007 A1
20070087820 Van Apr 2007 A1
20070094066 Kumar Apr 2007 A1
20070100691 Patterson May 2007 A1
20070100728 Rotman May 2007 A1
20070106504 Deng May 2007 A1
20070106607 Seib May 2007 A1
20070106627 Srivastava May 2007 A1
20070107044 Yuen May 2007 A1
20070113289 Blumenau May 2007 A1
20070125840 Law Jun 2007 A1
20070129955 Dalmia Jun 2007 A1
20070136193 Starr Jun 2007 A1
20070136211 Brown Jun 2007 A1
20070143204 Claus Jun 2007 A1
20070150413 Morgenstern Jun 2007 A1
20070156726 Levy Jul 2007 A1
20070162350 Friedman Jul 2007 A1
20070170247 Friedman Jul 2007 A1
20070179885 Bird Aug 2007 A1
20070180119 Khivesara Aug 2007 A1
20070198435 Siegal Aug 2007 A1
20070198587 Kobayasfii Aug 2007 A1
20070208662 Jeronimus Sep 2007 A1
20070208671 Brown Sep 2007 A1
20070214078 Coppinger Sep 2007 A1
20070214250 Ahmed Sep 2007 A1
20070226152 Jones Sep 2007 A1
20070233590 Hardison Oct 2007 A1
20070233615 Tumminaro Oct 2007 A1
20070239502 Babu Oct 2007 A1
20070245414 Chan Oct 2007 A1
20070276765 Hazel Nov 2007 A1
20070288377 Shaked Dec 2007 A1
20070291995 Rivera Dec 2007 A1
20080004116 Van Jan 2008 A1
20080004952 Koli Jan 2008 A1
20080010096 Patterson Jan 2008 A1
20080013335 Tsutsumi Jan 2008 A1
20080015988 Brown Jan 2008 A1
20080021829 Kranzley Jan 2008 A1
20080027218 Daugs Jan 2008 A1
20080027850 Brittan Jan 2008 A1
20080029607 Mullen Feb 2008 A1
20080035738 Mullen Feb 2008 A1
20080048022 Vawter Feb 2008 A1
20080052226 Agarwal Feb 2008 A1
20080054068 Mullen Mar 2008 A1
20080054079 Mullen Mar 2008 A1
20080054081 Mullen Mar 2008 A1
20080059370 Sada Mar 2008 A1
20080065554 Hogan Mar 2008 A1
20080065555 Mullen Mar 2008 A1
20080077489 Gilley Mar 2008 A1
20080082424 Walton Apr 2008 A1
20080086365 Zollino Apr 2008 A1
20080090513 Collins Apr 2008 A1
20080091553 Koski Apr 2008 A1
20080091616 Helwin Apr 2008 A1
20080097856 Blagg Apr 2008 A1
20080103795 Jakubowski May 2008 A1
20080114639 Meek May 2008 A1
20080114737 Neely May 2008 A1
20080126145 Racklet, III May 2008 A1
20080133351 White Jun 2008 A1
20080140568 Henry Jun 2008 A1
20080140684 OReilly Jun 2008 A1
20080147883 Philyaw Jun 2008 A1
20080154623 Derker Jun 2008 A1
20080162361 Sklovsky Jul 2008 A1
20080167965 Von Jul 2008 A1
20080172274 Hurowitz Jul 2008 A1
20080172331 Graves Jul 2008 A1
20080177574 Marcos Jul 2008 A1
20080177672 Brunner Jul 2008 A1
20080201232 Walker Aug 2008 A1
20080201264 Brown Aug 2008 A1
20080201265 Newton Aug 2008 A1
20080221945 Pace Sep 2008 A1
20080223918 Williams Sep 2008 A1
20080228646 Myers Sep 2008 A1
20080229217 Kembel Sep 2008 A1
20080235261 Malek Sep 2008 A1
20080024561 Fein Oct 2008 A1
20080243305 Lee Oct 2008 A1
20080243702 Hart Oct 2008 A1
20080245855 Fein Oct 2008 A1
20080245861 Fein Oct 2008 A1
20080270300 Jones Oct 2008 A1
20080272188 Keithley Nov 2008 A1
20080283591 Oder Nov 2008 A1
20080288376 Panthaki Nov 2008 A1
20080288889 Hunt Nov 2008 A1
20080300980 Benjamin Dec 2008 A1
20080301055 Borgs Dec 2008 A1
20080302869 Mullen Dec 2008 A1
20080302876 Mullen Dec 2008 A1
20080313264 Pestoni Dec 2008 A1
20080319905 Carlson Dec 2008 A1
20090006181 Ghosh Jan 2009 A1
20090006262 Brown Jan 2009 A1
20090010488 Matsuoka Jan 2009 A1
20090013266 Gandhi Jan 2009 A1
20090018895 Weinblatt Jan 2009 A1
20090024527 Sellen Jan 2009 A1
20090024636 Shiloh Jan 2009 A1
20090037255 Chiu Feb 2009 A1
20090037326 Chitti Feb 2009 A1
20090037333 Flitcroft Feb 2009 A1
20090037388 Cooper Feb 2009 A1
20090043702 Bennett Feb 2009 A1
20090048934 Haddad Feb 2009 A1
20090048971 Hathaway Feb 2009 A1
20090061884 Rajan Mar 2009 A1
20090063261 Scribner Mar 2009 A1
20090064056 Anderson Mar 2009 A1
20090076953 Saville Mar 2009 A1
20090076966 Bishop Mar 2009 A1
20090083065 Unland Mar 2009 A1
20090089176 Mccabe Apr 2009 A1
20090089193 Paintin Apr 2009 A1
20090104888 Cox Apr 2009 A1
20090106112 Dalmia Apr 2009 A1
20090106151 Nelsen Apr 2009 A1
20090106160 Skowronek Apr 2009 A1
20090106234 Siedlecki Apr 2009 A1
20090108080 Meyer Apr 2009 A1
20090112775 Chiulli Apr 2009 A1
20090119176 Johnson May 2009 A1
20090119190 Realini May 2009 A1
20090119211 Johnson May 2009 A1
20090125429 Takayama May 2009 A1
20090132347 Anderson May 2009 A1
20090132366 Lam May 2009 A1
20090132395 Lam May 2009 A1
20090134217 Flitcroft May 2009 A1
20090144104 Johnson Jun 2009 A1
20090144201 Gierkink Jun 2009 A1
20090157555 Biffle Jun 2009 A1
20090159673 Mullen Jun 2009 A1
20090159700 Mullen Jun 2009 A1
20090159707 Mullen Jun 2009 A1
20090164344 Shiftan Jun 2009 A1
20090170608 Herrmann Jul 2009 A1
20090171778 Powell Jul 2009 A1
20090173782 Muscato Jul 2009 A1
20090182664 Trombley Jul 2009 A1
20090187492 Hammad Jul 2009 A1
20090200371 Kean Aug 2009 A1
20090210300 Cansler Aug 2009 A1
20090216910 Duchesneau Aug 2009 A1
20090222347 Whitten Sep 2009 A1
20090228211 Rasanen Sep 2009 A1
20090233579 Castell Sep 2009 A1
20090234751 Chan Sep 2009 A1
20090238528 Spillane Sep 2009 A1
20090240620 Kendrick Sep 2009 A1
20090241159 Campagna Sep 2009 A1
20090248583 Chhabra Oct 2009 A1
20090248738 Martinez Oct 2009 A1
20090254471 Seidel Oct 2009 A1
20090254479 Pharris Oct 2009 A1
20090254535 Eickelmann Oct 2009 A1
20090265274 Hahn-Carlson Oct 2009 A1
20090271246 Alvarez Oct 2009 A1
20090271265 Lay Oct 2009 A1
20090276347 Kargman Nov 2009 A1
20090281948 Carlson Nov 2009 A1
20090288012 Hertel Nov 2009 A1
20090294527 Brabson Dec 2009 A1
20090307060 Merz Dec 2009 A1
20090307135 Gupta Dec 2009 A1
20090307139 Mardikar Dec 2009 A1
20090308921 Mullen Dec 2009 A1
20090313132 McKenna Dec 2009 A1
20090319638 Faith Dec 2009 A1
20090327045 Olives Dec 2009 A1
20090327088 Puthupparambil Dec 2009 A1
20090327131 Beenau Dec 2009 A1
20100004989 Bonalle Jan 2010 A1
20100005025 Kumar Jan 2010 A1
20100008535 Abulafia Jan 2010 A1
20100009663 Chang Jan 2010 A1
20100010964 Skowronek Jan 2010 A1
20100012728 Rosset Jan 2010 A1
20100021149 Mulder Jan 2010 A1
20100023386 Avisar Jan 2010 A1
20100023455 Dispensa Jan 2010 A1
20100023457 Riviere Jan 2010 A1
20100036741 Cleven Feb 2010 A1
20100036775 Edens Feb 2010 A1
20100036884 Brown Feb 2010 A1
20100042456 Stinchcombe Feb 2010 A1
20100042537 Smith Feb 2010 A1
20100042540 Graves Feb 2010 A1
20100049879 Leavitt Feb 2010 A1
20100057548 Edwards Mar 2010 A1
20100063903 Whipple Mar 2010 A1
20100070359 Heasley Mar 2010 A1
20100076873 Taylor Mar 2010 A1
20100078471 Lin Apr 2010 A1
20100078472 Lin Apr 2010 A1
20100082444 Lin Apr 2010 A1
20100082445 Hodge Apr 2010 A1
20100082447 Lin Apr 2010 A1
20100082455 Rosenblatt Apr 2010 A1
20100082480 Korosec Apr 2010 A1
20100082481 Lin Apr 2010 A1
20100082485 Lin Apr 2010 A1
20100082490 Rosenblatt Apr 2010 A1
20100082491 Rosenblatt Apr 2010 A1
20100088188 Kumar Apr 2010 A1
20100088237 Wankmueller Apr 2010 A1
20100094730 Koski Apr 2010 A1
20100094755 Kloster Apr 2010 A1
20100094878 Soroca Apr 2010 A1
20100100480 Altman Apr 2010 A1
20100106644 Annan Apr 2010 A1
20100114664 Jobin May 2010 A1
20100120408 Beenau May 2010 A1
20100121707 Goeldi May 2010 A1
20100125492 Lin May 2010 A1
20100125495 Smith May 2010 A1
20100125509 Kranzley May 2010 A1
20100125803 Johnson May 2010 A1
20100131347 Sarptipi May 2010 A1
20100131415 Sartipi May 2010 A1
20100133334 Vadhri Jun 2010 A1
20100133339 Gibson Jun 2010 A1
20100138026 Kaushal Jun 2010 A1
20100138347 Chen Jun 2010 A1
20100145860 Pelegero Jun 2010 A1
20100153865 Barnes Jun 2010 A1
20100155470 Woronec Jun 2010 A1
20100161433 White Jun 2010 A1
20100162126 Donaldson Jun 2010 A1
20100174599 Rosenblatt Jul 2010 A1
20100179855 Chen Jul 2010 A1
20100185505 Sprogoe Jul 2010 A1
20100185531 Van Jul 2010 A1
20100185545 Royyuru Jul 2010 A1
20100191578 Tran Jul 2010 A1
20100191622 Reiss Jul 2010 A1
20100191770 Cho Jul 2010 A1
20100198626 Cho Aug 2010 A1
20100211445 Bodington Aug 2010 A1
20100211452 D Aug 2010 A1
20100211469 Salmon Aug 2010 A1
20100211499 Zanzot Aug 2010 A1
20100211505 Saunders Aug 2010 A1
20100217613 Kelly Aug 2010 A1
20100217682 Chan Aug 2010 A1
20100223186 Hogan Sep 2010 A1
20100228668 Hogan Sep 2010 A1
20100235284 Moore Sep 2010 A1
20100243728 Wiesman Sep 2010 A1
20100250351 Gillenson Sep 2010 A1
20100256976 Atsmon Oct 2010 A1
20100258620 Torreyson Oct 2010 A1
20100268645 Martino Oct 2010 A1
20100276484 Banerjee Nov 2010 A1
20100287048 Ramer Nov 2010 A1
20100287229 Hauser Nov 2010 A1
20100291904 Musfeldt Nov 2010 A1
20100293032 Engelsma Nov 2010 A1
20100299267 Faith Nov 2010 A1
20100299292 Collazo Nov 2010 A1
20100305848 Stallman Dec 2010 A1
20100306075 Drance Dec 2010 A1
20100306076 Taveau Dec 2010 A1
20100306113 Grey Dec 2010 A1
20100312645 Niekadlik Dec 2010 A1
20100312676 Muthukumaran Dec 2010 A1
20100312724 Pinckney Dec 2010 A1
20100325041 Berardi Dec 2010 A1
20100332262 Horvitz Dec 2010 A1
20100332283 Ng Dec 2010 A1
20110004498 Readshaw Jan 2011 A1
20110010292 Giordano Jan 2011 A1
20110016047 Wu Jan 2011 A1
20110016320 Bergsten Jan 2011 A1
20110035273 Parikh Feb 2011 A1
20110040640 Erikson Feb 2011 A1
20110040655 Hendrickson Feb 2011 A1
20110047017 Lieblang Feb 2011 A1
20110047075 Fourez Feb 2011 A1
20110047076 Carlson Feb 2011 A1
20110078082 Gupta Mar 2011 A1
20110082789 Boyd Apr 2011 A1
20110083018 Kesanupalli Apr 2011 A1
20110087596 Dorsey Apr 2011 A1
20110087726 Shim Apr 2011 A1
20110093335 Fordyce Apr 2011 A1
20110093397 Carlson Apr 2011 A1
20110099057 Tenyer Apr 2011 A1
20110105183 Hsiao May 2011 A1
20110106698 Issacson May 2011 A1
20110109737 Aben May 2011 A1
20110119300 Marcade May 2011 A1
20110125597 Oder May 2011 A1
20110137740 Bhattacharya Jun 2011 A1
20110137742 Parikh Jun 2011 A1
20110153437 Archer Jun 2011 A1
20110153498 Makhotin Jun 2011 A1
20110154466 Harper Jun 2011 A1
20110161233 Tieken Jun 2011 A1
20110178896 Nakajima Jul 2011 A1
20110178926 Lindelsee Jul 2011 A1
20110180598 Morgan Jul 2011 A1
20110184827 Hubert Jul 2011 A1
20110191244 Dai Aug 2011 A1
20110208418 Looney Aug 2011 A1
20110215146 Shams Sep 2011 A1
20110218870 Shams Sep 2011 A1
20110221692 Seydoux Sep 2011 A1
20110238474 Carr Sep 2011 A1
20110238511 Park Sep 2011 A1
20110238573 Varadarajan Sep 2011 A1
20110246290 Howard Oct 2011 A1
20110246317 Coppinger Oct 2011 A1
20110251892 Laracey Oct 2011 A1
20110258049 Ramer Oct 2011 A1
20110258111 Raj Oct 2011 A1
20110258123 Dawkins Oct 2011 A1
20110270665 Kim Nov 2011 A1
20110272471 Mullen Nov 2011 A1
20110272478 Mullen Nov 2011 A1
20110276380 Mullen Nov 2011 A1
20110276381 Mullen Nov 2011 A1
20110276424 Mullen Nov 2011 A1
20110276425 Mullen Nov 2011 A1
20110282780 French Nov 2011 A1
20110288684 Farlow Nov 2011 A1
20110295745 White Dec 2011 A1
20110296508 Os Dec 2011 A1
20110302081 Saunders Dec 2011 A1
20110312423 Mosites Dec 2011 A1
20110320344 Faith Dec 2011 A1
20110320345 Taveau Dec 2011 A1
20120005026 Khan Jan 2012 A1
20120011009 Lindsey Jan 2012 A1
20120011063 Killian Jan 2012 A1
20120016731 Smith Jan 2012 A1
20120022943 Howard Jan 2012 A1
20120023026 Chen Jan 2012 A1
20120023417 Nesladek Jan 2012 A1
20120023567 Hammad Jan 2012 A1
20120028609 Hruska Feb 2012 A1
20120030047 Fuentes Feb 2012 A1
20120030101 Boyd Feb 2012 A1
20120035998 Chien Feb 2012 A1
20120036071 Fulton Feb 2012 A1
20120041881 Basu Feb 2012 A1
20120047237 Arvidsson Feb 2012 A1
20120066065 Switzer Mar 2012 A1
20120066078 Kingston Mar 2012 A1
20120072311 Khan Mar 2012 A1
20120072350 Goldthwaite Mar 2012 A1
20120078735 Bauer Mar 2012 A1
20120078798 Downing Mar 2012 A1
20120078799 Jackson Mar 2012 A1
20120084132 Khan Apr 2012 A1
20120084204 Castell Apr 2012 A1
20120095852 Bauer Apr 2012 A1
20120095865 Doherty Apr 2012 A1
20120095895 Aston Apr 2012 A1
20120101881 Taylor Apr 2012 A1
20120110044 Nagpal May 2012 A1
20120116902 Cardina May 2012 A1
20120116966 Tan May 2012 A1
20120118950 Belk May 2012 A1
20120123838 Sparks May 2012 A1
20120123882 Carlson May 2012 A1
20120123940 Killian May 2012 A1
20120124496 Rose May 2012 A1
20120129514 Beenau May 2012 A1
20120130794 Strieder May 2012 A1
20120136780 El-Awady May 2012 A1
20120143706 Crake Jun 2012 A1
20120143767 Abadir Jun 2012 A1
20120143772 Abadir Jun 2012 A1
20120150750 Law Jun 2012 A1
20120158580 Eram Jun 2012 A1
20120158589 Katzin Jun 2012 A1
20120158593 Garfinkle Jun 2012 A1
20120158792 MacLaurin Jun 2012 A1
20120158893 Boyns Jun 2012 A1
20120159163 von Behren Jun 2012 A1
20120165978 Li Jun 2012 A1
20120166333 von Behren Jun 2012 A1
20120166655 Maddali Jun 2012 A1
20120173431 Ritchie Jul 2012 A1
20120173962 Oh Jul 2012 A1
20120185386 Salama Jul 2012 A1
20120190386 Anderson Jul 2012 A1
20120197691 Grigg Aug 2012 A1
20120197794 Grigg Aug 2012 A1
20120197807 Schlesser Aug 2012 A1
20120203662 Morgan Aug 2012 A1
20120203664 Torossian Aug 2012 A1
20120203665 Morgan Aug 2012 A1
20120203666 Torossian Aug 2012 A1
20120203673 Morgan Aug 2012 A1
20120209749 Hammad Aug 2012 A1
20120215640 Ramer Aug 2012 A1
20120215648 Rose Aug 2012 A1
20120215650 Oba Aug 2012 A1
20120215684 Kidron Aug 2012 A1
20120215688 Musser Aug 2012 A1
20120215696 Salonen Aug 2012 A1
20120221421 Hammad Aug 2012 A1
20120221502 Jerram Aug 2012 A1
20120226582 Hammad Sep 2012 A1
20120231844 Coppinger Sep 2012 A1
20120233004 Bercaw Sep 2012 A1
20120233170 Musgrove Sep 2012 A1
20120239417 Pourfallah Sep 2012 A1
20120239556 Magruder Sep 2012 A1
20120239560 Pourfallah Sep 2012 A1
20120246070 Vadhri Sep 2012 A1
20120246071 Jain Sep 2012 A1
20120246079 Wilson Sep 2012 A1
20120254108 Wedewer Oct 2012 A1
20120259763 Pessin Oct 2012 A1
20120265631 Cronic Oct 2012 A1
20120265685 Brudnicki Oct 2012 A1
20120271770 Harris Oct 2012 A1
20120284035 Gillin Nov 2012 A1
20120290472 Mullen Nov 2012 A1
20120297446 Webb Nov 2012 A1
20120300932 Cambridge Nov 2012 A1
20120303425 Katzin Nov 2012 A1
20120303503 Cambridge Nov 2012 A1
20120303736 Novotny Nov 2012 A1
20120303961 Kean Nov 2012 A1
20120304273 Bailey Nov 2012 A1
20120310725 Chien Dec 2012 A1
20120310826 Chatterjee Dec 2012 A1
20120310831 Harris Dec 2012 A1
20120316992 Oborne Dec 2012 A1
20120317035 Royyuru Dec 2012 A1
20120317036 Bower Dec 2012 A1
20120317149 Jagota Dec 2012 A1
20120323664 Klems Dec 2012 A1
20120330874 Jerram Dec 2012 A1
20130013499 Kalgi Jan 2013 A1
20130017784 Fisher Jan 2013 A1
20130018757 Anderson Jan 2013 A1
20130019098 Gupta Jan 2013 A1
20130024364 Shrivastava Jan 2013 A1
20130024371 Hariramani Jan 2013 A1
20130024916 Evans Jan 2013 A1
20130030828 Pourfallah Jan 2013 A1
20130031006 McCullagh Jan 2013 A1
20130054337 Brendell Feb 2013 A1
20130054454 Purves Feb 2013 A1
20130054466 Muscato Feb 2013 A1
20130054470 Campos Feb 2013 A1
20130054474 Yeager Feb 2013 A1
20130080238 Kelly Mar 2013 A1
20130081122 Svigals Mar 2013 A1
20130085877 Ruehrig Apr 2013 A1
20130090750 Herrman Apr 2013 A1
20130091028 Oder Apr 2013 A1
20130103574 Conrad Apr 2013 A1
20130110658 Lyman May 2013 A1
20130110678 Vigier May 2013 A1
20130111599 Gargiulo May 2013 A1
20130117170 Coppinger May 2013 A1
20130117185 Collison May 2013 A1
20130124290 Fisher May 2013 A1
20130124291 Fisher May 2013 A1
20130124364 Mittal May 2013 A1
20130138525 Bercaw May 2013 A1
20130144785 Karpenko Jun 2013 A1
20130144888 Faith Jun 2013 A1
20130144957 Sherman Jun 2013 A1
20130145148 Shablygin Jun 2013 A1
20130145172 Shablygin Jun 2013 A1
20130151417 Gupta Jun 2013 A1
20130159081 Shastry Jun 2013 A1
20130159112 Schultz Jun 2013 A1
20130159154 Purves Jun 2013 A1
20130159178 Colon Jun 2013 A1
20130159184 Thaw Jun 2013 A1
20130159196 Dizoglio Jun 2013 A1
20130166332 Hammad Jun 2013 A1
20130166402 Parento Jun 2013 A1
20130166456 Zhang Jun 2013 A1
20130166621 Zhu Jun 2013 A1
20130173736 Krzeminski Jul 2013 A1
20130179340 Alba Jul 2013 A1
20130185202 Goldthwaite Jul 2013 A1
20130191286 Cronic Jul 2013 A1
20130191289 Cronic Jul 2013 A1
20130198071 Jurss Aug 2013 A1
20130198080 Anderson Aug 2013 A1
20130200146 Moghadam Aug 2013 A1
20130204776 King Aug 2013 A1
20130204787 Dubois Aug 2013 A1
20130204793 Kerridge Aug 2013 A1
20130212007 Mattsson Aug 2013 A1
20130212017 Bangia Aug 2013 A1
20130212019 Mattsson Aug 2013 A1
20130212024 Mattsson Aug 2013 A1
20130212026 Powell Aug 2013 A1
20130212666 Mattsson Aug 2013 A1
20130218640 Kidder Aug 2013 A1
20130218657 Salmon Aug 2013 A1
20130218698 Moon Aug 2013 A1
20130218721 Borhan Aug 2013 A1
20130218765 Hammad Aug 2013 A1
20130218769 Pourfallah Aug 2013 A1
20130226799 Raj Aug 2013 A1
20130226813 Voltz Aug 2013 A1
20130246199 Carlson Sep 2013 A1
20130246202 Tobin Sep 2013 A1
20130246203 Laracey Sep 2013 A1
20130246258 Dessert Sep 2013 A1
20130246259 Dessert Sep 2013 A1
20130246261 Purves Sep 2013 A1
20130246267 Tobin Sep 2013 A1
20130254028 Salci Sep 2013 A1
20130254052 Royyuru Sep 2013 A1
20130254102 Royyuru Sep 2013 A1
20130254117 von Mueller Sep 2013 A1
20130262296 Thomas Oct 2013 A1
20130262302 Lettow Oct 2013 A1
20130262315 Hruska Oct 2013 A1
20130262316 Hruska Oct 2013 A1
20130262317 Collinge Oct 2013 A1
20130275300 Killian Oct 2013 A1
20130275307 Khan Oct 2013 A1
20130275308 Paraskeva Oct 2013 A1
20130282502 Jooste Oct 2013 A1
20130282575 Mullen Oct 2013 A1
20130282588 Hruska Oct 2013 A1
20130297501 Monk Nov 2013 A1
20130297504 Nwokolo Nov 2013 A1
20130297508 Belamant Nov 2013 A1
20130304649 Cronic Nov 2013 A1
20130308778 Fosmark Nov 2013 A1
20130311382 Fosmark Nov 2013 A1
20130317982 Mengerink Nov 2013 A1
20130325579 Salmon Dec 2013 A1
20130332344 Weber Dec 2013 A1
20130339240 Anderson Dec 2013 A1
20130339253 Sincai Dec 2013 A1
20130346302 Purves Dec 2013 A1
20130346305 Mendes Dec 2013 A1
20130346314 Mogollon Dec 2013 A1
20140006195 Wilson Jan 2014 A1
20140006198 Daly Jan 2014 A1
20140006283 Hogg Jan 2014 A1
20140007213 Sanin Jan 2014 A1
20140013106 Red path Jan 2014 A1
20140013114 Red path Jan 2014 A1
20140013452 Aissi Jan 2014 A1
20140019352 Shrivastava Jan 2014 A1
20140025581 Caiman Jan 2014 A1
20140025585 Caiman Jan 2014 A1
20140025958 Caiman Jan 2014 A1
20140032417 Mattsson Jan 2014 A1
20140032418 Weber Jan 2014 A1
20140040127 Chatterjee Feb 2014 A1
20140040137 Carlson Feb 2014 A1
20140040139 Brudnicki Feb 2014 A1
20140040144 Plomske Feb 2014 A1
20140040145 Ozvat Feb 2014 A1
20140040148 Ozvat Feb 2014 A1
20140040628 Fort Feb 2014 A1
20140041018 Bomar Feb 2014 A1
20140046853 Spies Feb 2014 A1
20140047517 Ding Feb 2014 A1
20140047551 Nagasundaram Feb 2014 A1
20140052532 Tsai Feb 2014 A1
20140052620 Rogers Feb 2014 A1
20140052637 Jooste Feb 2014 A1
20140068706 Aissi Mar 2014 A1
20140074637 Hammad Mar 2014 A1
20140095589 Johnson Apr 2014 A1
20140108172 Weber Apr 2014 A1
20140108197 Smith Apr 2014 A1
20140114857 Griggs Apr 2014 A1
20140136945 Ligman May 2014 A1
20140143137 Carlson May 2014 A1
20140164243 Aabye Jun 2014 A1
20140188586 Carpenter Jul 2014 A1
20140294701 Dai Oct 2014 A1
20140297534 Patterson Oct 2014 A1
20140310080 Salmon Oct 2014 A1
20140310183 Weber Oct 2014 A1
20140330721 Wang Nov 2014 A1
20140330722 Laxminarayanan Nov 2014 A1
20140331265 Mozell Nov 2014 A1
20140337175 Katzin Nov 2014 A1
20140337236 Wong Nov 2014 A1
20140344153 Raj Nov 2014 A1
20140365295 Postrel Dec 2014 A1
20140372308 Sheets Dec 2014 A1
20150019443 Sheets Jan 2015 A1
20150019944 Kalgi Jan 2015 A1
20150026049 Theurer Jan 2015 A1
20150032625 Dill Jan 2015 A1
20150032626 Dill Jan 2015 A1
20150032627 Dill Jan 2015 A1
20150046338 Laxminarayanan Feb 2015 A1
20150046339 Wong Feb 2015 A1
20150052064 Karpenko Feb 2015 A1
20150088756 Makhotin Mar 2015 A1
20150089350 Davis Mar 2015 A1
20150106239 Gaddam Apr 2015 A1
20150112870 Nagasundaram Apr 2015 A1
20150112871 Kumnick Apr 2015 A1
20150120472 Aabye Apr 2015 A1
20150127529 Makhotin May 2015 A1
20150127547 Powell May 2015 A1
20150140960 Powell May 2015 A1
20150142673 Nelsen May 2015 A1
20150154588 Purves Jun 2015 A1
20150161597 Subramanian Jun 2015 A1
20150178724 Ngo Jun 2015 A1
20150180836 Wong Jun 2015 A1
20150186864 Jones Jul 2015 A1
20150193222 Pirzadeh Jul 2015 A1
20150195133 Sheets Jul 2015 A1
20150199679 Palanisamy Jul 2015 A1
20150199689 Kumnick Jul 2015 A1
20150220917 Aabye Aug 2015 A1
20150269566 Gaddam Sep 2015 A1
20150302453 Tietzen Oct 2015 A1
20150312038 Palanisamy Oct 2015 A1
20150319158 Kumnick Nov 2015 A1
20150332262 Lingappa Nov 2015 A1
20150339767 Chen Nov 2015 A1
20150356560 Shastry Dec 2015 A1
20160028550 Gaddam Jan 2016 A1
20160042263 Gaddam Feb 2016 A1
20160065370 Le Saint Mar 2016 A1
20160092696 Guglani Mar 2016 A1
20160092872 Prakash Mar 2016 A1
20160103675 Aabye Apr 2016 A1
20160119296 Laxminarayanan Apr 2016 A1
20160224976 Basu Aug 2016 A1
20160291920 Sirpal Oct 2016 A1
20160379192 Purves Dec 2016 A1
20170046696 Powell Feb 2017 A1
20170103387 Weber Apr 2017 A1
20170134479 Kalgi May 2017 A1
20170220818 Nagasundaram Aug 2017 A1
20170228723 Taylor Aug 2017 A1
20170300314 Lopyrev Oct 2017 A1
20170346876 Lim Nov 2017 A1
20180075081 Chipman Mar 2018 A1
Foreign Referenced Citations (60)
Number Date Country
1841425 Oct 2006 CN
1922623 Feb 2007 CN
1928907 Mar 2007 CN
101025806 Aug 2007 CN
101075316 Nov 2007 CN
101231727 Jul 2008 CN
101334876 Dec 2008 CN
101388125 Mar 2009 CN
101719255 Jun 2010 CN
101840550 Sep 2010 CN
101924690 Dec 2010 CN
101945127 Jan 2011 CN
101958025 Jan 2011 CN
102143290 Aug 2011 CN
102779304 Nov 2012 CN
102947847 Feb 2013 CN
0745961 Dec 1996 EP
0855659 Jul 1998 EP
1921578 May 2008 EP
2156397 Feb 2010 EP
2503496 Sep 2012 EP
2001344544 Dec 2001 JP
2005004621 Jan 2005 JP
2007328549 Dec 2007 JP
2008527495 Jul 2008 JP
2008545210 Dec 2008 JP
2009151730 Jul 2009 JP
2009176259 Aug 2009 JP
2011186660 Sep 2011 JP
2012027824 Feb 2012 JP
20000058839 Oct 2000 KR
20010055426 Jul 2001 KR
100432430 May 2004 KR
20060117177 Nov 2006 KR
20070104087 Oct 2007 KR
2013069539 Oct 2013 SG
2000046769 Aug 2000 WO
2001035304 May 2001 WO
0165502 Sep 2001 WO
2003001866 Jan 2003 WO
03023674 Mar 2003 WO
2003046697 Jun 2003 WO
2003071386 Aug 2003 WO
2003083737 Oct 2003 WO
2004042536 May 2004 WO
2005079254 Sep 2005 WO
2006113834 Oct 2006 WO
2009032523 Mar 2009 WO
2010078522 Jul 2010 WO
2010148704 Dec 2010 WO
2010148737 Dec 2010 WO
2012068078 May 2012 WO
2012098556 Jul 2012 WO
2012112822 Aug 2012 WO
2012142370 Oct 2012 WO
2012167941 Dec 2012 WO
2013048538 Apr 2013 WO
2013056104 Apr 2013 WO
2013119914 Aug 2013 WO
2013179271 Dec 2013 WO
Non-Patent Literature Citations (253)
Entry
Chinese Office Action (with English language translation) for Application No. CN201710037081.6, dated Mar. 17, 2020, 23 pages.
Notice of Allowance dated Jun. 10, 2020 for U.S. Appl. No. 15/494,294 (pp. 1-10).
Office Action dated May 19, 2020 for U.S. Appl. No. 15/627,085 (pp. 1-11).
Chinese Office Action (with English language translation) for Application No. 201480023694.9, dated Jun. 26, 2019, 7 pages.
Notice of Allowance dated May 30, 2019 for U.S. Appl. No. 13/758,472 (pp. 1-10).
Office Action dated Jul. 10, 2019 for U.S. Appl. No. 13/398,817 (pp. 1-8).
Office Action dated Jun. 27, 2019 for U.S. Appl. No. 13/629,006 (pp. 1-7).
Office Action dated Oct. 29, 2019 for U.S. Appl. No. 14/216,382 (pp. 1-8).
Office Action dated Oct. 31, 2019 for U.S. Appl. No. 15/627,085 (pp. 1-9).
Notice of Allowance dated Nov. 8, 2019 for U.S. Appl. No. 14/698,317 (pp. 1-10).
Indian Examination Report for Application No. 8894/DELNP/2015, dated Oct. 21, 2019, 7 pages.
Office Action dated Dec. 12, 2019 for U.S. Appl. No. 14/935,122 (pp. 1-12).
Notice of Allowance dated Jun. 15, 2020 for U.S. Appl. No. 16/440,486 (pp. 1-8).
Office Action dated Jul. 10, 2020 for U.S. Appl. No. 16/017,241 (pp. 1-9).
Notice of Allowance dated Apr. 12, 2019 for U.S. Appl. No. 16/182,288 (pp. 1-8).
Office Action dated May 14, 2019 for U.S. Appl. No. 14/935,122 (pp. 1-11).
Chinese Office Action (with English language translation) for Application No. CN201480023694.9, dated Jan. 21, 2020, 12 pages.
Office Action dated Feb. 4, 2020 for U.S. Appl. No. 13/629,006 (pp. 1-7).
David Breitkopf, “ACS to Take Over Mich. WC Distribution Program”, American Banker, New York, NY: Jul. 20, 2006, vol. 171. Issue 138, p. 6.
Business Wire, “New York State Department of Labor Selects JPMorgan Chase to Provide New Banking Services for Unemployment Insurance Benefits; JPMorgan Chase Electronic Services to Help Speed Benefit Payments”, Business Wire, New York, Aug. 4, 2006, 2 p.
Gopalan, NP & Selvan, B Siva. TCP/IP Illustrated. Prentice-Hall. 2008. pp. 101-102, 175-176 and 235. 7 pages.
Shadrach, D.C. “A Weighted Metric Based Adaptive Algorithm for Web Server Load Balancing.” 2009 Third International Symposium on Intelligent Information Technology Application, http://ieeexplore.ieee.org/xpl/articleDetails.jsp?amumber=5369384, pp. 449-452.
International Search Report for PCT/US09/54921 dated Oct. 21, 2009. (2 pages).
International Search Report and Written Opinion for PCT/US2010/048344 dated Nov. 15, 2010. (7 pages).
International Search Report and Written Opinion for PCT/US2010/041860 dated Feb. 1, 2011. (8 pages).
International Search Report and Written Opinion for PCT/US12/41437 dated Aug. 24, 2012. (20 pages).
International Search Report for PCT/US11/49393 dated Dec. 5, 2011. (2 pages).
International Search Report and Written Opinion for PCT/US11/57179 dated Jan. 5, 2012. (7 pages).
International Search Report and Written Opinion for PCT/US11/57173 dated Mar. 15, 2012. (11 pages).
International Search Report and Written Opinion for PCT/US2012/026205, dated May 29, 2012. 2 pages.
International Search Report for PCT/US11/65305 dated Apr. 16, 2012. 2 pages.
International Search Report for PCT/US12/23856 dated Jun. 6, 2012. 3 pages.
International Search Report for PCT/US12/24772 dated Jul. 24, 2012. 3 pages.
International Search Report for PCT/US12/25530 dated Aug. 7, 2012. 4 pages.
International Search Report PCT/US12/27620 dated Aug. 10, 2012. 3 pages.
International Search Report for PCT/US12/39638 dated Sep. 24, 2012. 4 pages.
International Search Report for PCT/US12/45875 dated Nov. 16, 2012. 4 pages.
International Search Report and Written Opinion for PCT/US12/47092 dated Nov. 26, 2012. 11 pages.
International Search Report for PCT/US12/57577 dated Nov. 29, 2012. 2 pages.
International Search Report and Written Opinion for PCT/US12/57528 dated Dec. 17, 2012. 8 pages.
International Search Report and Written Opinion for PCT/US12/66898 dated Feb. 11, 2013. 14 pages.
International Search Report and Written Opinion for PCT/US12/56759 dated Feb. 25, 2013. 12 pages.
International Search Report and Written Opinion for PCT/US2013/020411 dated May 21, 2013. 18 pages.
Written Opinion for PCT/US12/27620 dated Aug. 10, 2012. 5 pages.
International Search Report and Written Opinion for PCT/US2010/033861 dated Dec. 9, 2010 (7 pages).
International Search Report for PCT/US2010/033547 dated Dec. 14, 2010 (3 pages).
International Search Report for PCT/US2010/045445 dated Feb. 24, 2011 (3 pages).
International Search Report for PCT/US2010/045500 dated Mar. 29, 2011 (3 pages).
International Search Report and Written Opinion for PCT/US2011/024941 dated Apr. 19, 2011 (6 pages).
International Search Report and Written Opinion for PCT/US2010/046833 dated Apr. 26, 2011 (8 pages).
International Search Report and Written Opinion for PCT/US2011/26734 dated Apr. 29, 2011 (7 pages).
International Search Report and Written Opinion for PCT/US2011/29790 dated May 19, 2011 (6 pages).
International Search Report for PCT/US2011/035268 dated Aug. 5, 2011 (3 pages).
International Search Report and Written Opinion for PCT/US2011/032093 dated Aug. 24, 2011 (11 pages).
International Search Report and Written Opinion for PCT/US12/37597 dated Sep. 21, 2012 (11 pages).
International Search Report and Written Opinion for PCT/US2012/045601 dated Feb. 1, 2013. 11 pages.
International Search Report and Written Opinion for PCT/US12/65738 dated Apr. 19, 2013. 9 pages.
U.S. Appl. No. 61/250,440, filed Oct. 9, 2009, entitled “Systems and Methods to Provide Loyalty Programs”.
Australian Patent Office, Patent Examination Report No. 2 in Australian Patent Application No. 2012217606, dated Jun. 15, 2016, 6 pages.
Cash et al., U.S. Appl. No. 15/041,495 (unpublished), Peer Forward Authorization of Digital Requests filed Feb. 11, 2016.
Dizaj, Mohammad Vahid Alizadeh, Moghaddam, Rexa Askari, Momenebellah, Samad, New Mobile Payment Protocol: Mobile Pay Center Protocol 2 (MPCP2) By Using New Key Agreement Protocol: VAM, 3d International Conference on Electronics Computer Technology, vol. 2, Apr. 2011, pp. 12-18.
State Intellectual Property Office of the People's Republic of China, First Office Action in Chinese Application No. 201280018719.7, dated Jul. 4, 2016, 15 pages.
Flurscheim et al., U.S. Appl. No. 15/004,705 (unpublished), Cloud-Based Transactions With Magnetic Secure Transmission filed Jan. 22, 2016.
Flurscheim et al., U.S. Appl. No. 62/108,403 (unpublished), Wearables With NFC HCE filed Jan. 27, 2015.
Gaddam et al., U.S. Appl. No. 62/053,736 (unpublished), Completing Transactions Without a User Payment Device, filed Sep. 22, 2014.
Gao, Jerry, Kulkarni, Vijay, Ranavat, Himanshu, Chang, Lee, Mei, Hsing, A2D Barcode-Based Mobile Payment System, 3d International Conference on Multimedia and Ubiquitous Engineering, Jun. 2009, pp. 320-329.
International Search Report and Written Opinion for PCT/US2014/030517, dated Aug. 18, 2014. (9 pages).
Kalgi et al., U.S. Appl. No. 62/024,426 (unpublished), Secure Transactions Using Mobile Devices, filed Jul. 14, 2014.
Kinagi, U.S. Appl. No. 62/117,291 (unpublished), Token and Cryptogram Using Transaction Specific Information filed Feb. 17, 2015.
Le Saint et al., U.S. Appl. No. 15/008,388 (unpublished), Methods for Secure Credential Provisioning, filed Jan. 27, 2016.
McGuire, U.S. Appl. No. 14/600,523 (unpublished), Secure Payment Processing Usnig Authorization Request, filed Jan. 20, 2015.
Patterson, U.S. Appl. No. 15/019,157 (unpublished), Token Processing Utilizing Multiple Authorizations, filed Feb. 9, 2016.
Patterson, U.S. Appl. No. 62/054,346 (unpublished), Mirrored Token Vault, filed Sep. 23, 2014.
Hoverson et al., U.S. Appl. No. 62/038,174 (unpublished), Customized Payment Gateway, filed Aug. 15, 2014.
Stubbs et al., U.S. Appl. No. 62/103,522 (unpublished), Methods and Systems for Wallet Provider Provisioning filed Jan. 14, 2015.
Prakash et al., U.S. Appl. No. 14/955,716 (unpublished), Provisioning Platform for Machine-to-Machine Devices, filed Dec. 1, 2015.
Prakash et al., U.S. Appl. No. 62/037,033 (unpublished), Sharing Payment Token, filed Aug. 13, 2014.
Galland et al., U.S. Appl. No. 62/128,709 (unpublished), Tokenizing Transaction Amounts, filed Mar. 5, 2015.
IP Australia, Patent Examination Report No. 1, Australian Application No. 2012220669, dated Sep. 8, 2014, 6 pages.
State Intellectual Property of the People's Republic of China, First Office Action in Chinese Application No. 201280019629.X, dated Aug. 1, 2016, 15 pages.
Smartphone e-payment and Google AD send blog, ‘Google Wallet on Smartphone’, <http://stockpedia.blogspot.kr/2011/06/google-wallet.html> Jun. 10, 2011, pp. 1-3.
Lowry P B XML data mediation and collaboration: a proposed comprehensive architecture and query requirements for using XML to mediate heterogeneous data sources and targets, Proceedings of the 34th Hawaii International Conference on System Sciences—2001, Jan. 3, 2001; Jan. 3, 2001-Jan. 6, 2001, IEEE, pp. 1-9.
Wang, U.S. Appl. No. 62/000,288 (unpublished), Payment System Canonical Address Format, filed May 19, 2014.
Wang, U.S. Appl. No. 62/042,050 (unpublished), Payment Device Authentication and Authorization System, filed Aug. 26, 2014.
Wong et al., U.S. Appl. No. 14/966,948 (unpublished), Automated Access Data Provisioning filed Dec. 11, 2015.
Wong et al., U.S. Appl. No. 61/879,362 (unpublished), Systems and Methods for Managing Mobile Cardholder Verification Methods filed Sep. 18, 2013.
European Patent Office, Supplementary European Search Report and European Search Opinion, in EP Application No. 12749451.6, dated Apr. 20, 2015, 7 pages.
International Search Report and Written Opinion for PCT/US13/46875, dated Oct. 24, 2013, 14 pages.
IP Australia, Patent Examination Report No. 2, Australian Application No. 2012220669, dated Jun. 8, 2016, 4 pages.
International Search Report and Writtten Opinion for PCT/US2011/039178 dated Sep. 16, 2011 (7 pages).
International Search Report and Written Opinion for PCT/US11/57180 dated Mar. 15, 2012 (11 pages).
International Search Report and Written Opinion for PCT/US12/55636 dated Nov. 30, 2012. 2 pages.
Powell, U.S. Appl. No. 61/892,407 (unpublished), Issuer Over-the-Air Update Method and System filed Oct. 17, 2013.
Dimmick, U.S. Appl. No. 14/952,444 (unpublished), Tokenization Request Via Access Device, filed Nov. 25, 2015.
Dimmick, U.S. Appl. No. 14/952,514 (unpublished), Systems Communications With Non-Sensitive Identifiers, filed Nov. 25, 2015.
International Preliminary Report on Patentability dated Jan. 14, 2014 cited in related/corresponding International PCT Appl. No. PCT/US2012/045875 filed Jul. 7, 2012. (11 pages).
Vitt, Elizabeth et al. Data Integration Solutions for Master Data Management (Feb. 2006). https://technet.microsoft.com/en-us/library/aa964123(v=sql.90).aspx (19 pages).
Vitt, Elizabeth, et al. “Microsoft SQL Server 2005 Analysis Services Performance Guide.” White Paper, White Paper (2007). (116 pages).
Stack Exchange, Why aren't there automated translators from one programming language to another, 2010 (5 pages).
McCarney et al., “Tapas: Design, Implementation, and Usability Evaluation of a Password Manager,” Copyright 2012, ACM 978 1-4503-1312—Apr. 12, 2012 (10 pages).
International Search Report for PCT/US2010/033229 dated Dec. 29, 2010, 8 pages.
International Search Report for PCT/US12/21000 dated May 15, 2012. 2 pages.
International Search Report and Written Opinion for PCT/US2012/027043 dated Jul. 13, 2012. 15 pages.
Corrected Petition for Inter Partes Review of U.S. Pat. No. 8,533,860 Challenging Claims 1-30 Under 35 U.S.C. .sctn.312 and 37 C.F.R. sctn.42.104, dated Mar. 14, 2016, before the USPTO Patent Trial and Appeal Board, IPR 2016-00600, 65 pages.
Rangarajan et al., U.S. Appl. No. 61/751,763 (unpublished), Payments Bridge filed Jan. 11, 2013.
Li, U.S. Appl. No. 61/894,749 (unpublished), Methods and Systems for Authentication and Issuance of Tokens in a Secure Environment filed Oct. 23, 2013.
Aissi et al., U.S. Appl. No. 61/738,832 (unpublished), Management of Sensitive Data filed Dec. 18, 2012.
Powell, U.S. Appl. No. 61/926,236 (unpublished), Methods and Systems for Provisioning Mobile Devices With Payment Credentials and Payment Token Identifiers filed Jan. 10, 2014.
Petition for Inter Partes Review of U.S. Pat. No. 8,533,860 Challenging Claims 1-30 Under 35 U.S.C. 312 and 37 C.F.R. 42.104, filed Feb. 17, 2016, Before the USPTO Patent Trial and Appeal Board, IPR 2016-00600, 65 pages.
International Search Report and Written Opinion for PCT/US2010/033229 dated Dec. 29, 2010. (8 pages).
International Search Report and Written Opinion for PCT/US2012/069557 dated Feb. 22, 2013. 8 pages.
International Search Report and Written Opinion for PCT/US2012/057528, dated May 29, 2012. (8 pages).
U.S. Appl. No. 12/940,664 (unpublished), entitled “System and Method for Determining Transaction Distance” filed Nov. 5, 2010.
International Search Report and Written Opinion issued in connection with PCT/US11/42062 dated Sep. 29, 2011 (8 pages).
International Search Report and Written Opinion for PCT/US2013/031084, dated Jun. 4, 2013. 9 pages.
ShopSavvy Blog. Feb. 2012. Retrieved from https://web.archive.Org/web/20120212104611/http://shopsavvy.com/blog. pp. 1-13 (Year: 2012).
Chipman, et al., U.S. Appl. No. 15/265,282 (Unpublished), Self-Cleaning Token Vault, filed Sep. 14, 2016.
U.S. Appl. No. 15/462,658 (Unpublished), Replacing Token on a Multi-Token User Device, filed Mar. 17, 2017.
Sabba et al., U.S. Appl. No. 15/011,366 (unpublished), Token Check Offline, filed Jan. 29, 2016.
Sharma et al., U.S. Appl. No. 62/003,717 (unpublished), Mobile Merchant Application filed May 28, 2014.
International Preliminary Report on Patentability dated Jan. 16, 2014 in related/corresponding PCT Patent Appl. No. PCT/US2012/045601 filed Jul. 5, 2012. (7 pages).
Petition for Inter Partes Review of U.S. Pat. No. 8,887,308 Challenging Claim 1 Under 35 U.S.C. 312 and 37 C.F. R. 42.104, dated Mar. 3, 2016, before the USPTO Patent Trial and Appeal Board, IPR 2016-00602, 58 pages.
Petition for Inter Partes Review of U.S. Pat. No. 8,402,555 Challenging Claims 1-26 Under 35 U.S.C. 312 and 37 C.F.R. 42.104, dated Mar. 22, 2016, before the USPTO Patent Trial and Appeal Board, IPR 2016-00789, 65 pages.
Office Action dated Feb. 28, 2018 for U.S. Appl. No. 14/242,403 (pp. 1-11).
Office Action dated Apr. 12, 2018 for U.S. Appl. No. 13/520,481 (pp. 1-8).
International Search Report and Written Opinion for PCT/US2013/024538, dated May 31, 2013. 15 pages.
Charland et al., Mobile Application Development: Web vs. Native, Apr. 2011, 9 pages.
Lee et al., osgGap: scene graph library for mobile based on hybrid web app framework, Nov. 2013, 4 pages.
Immaneni et al., Hybrid retrieval from the unified web, Mar. 2007, 5 pages.
Gao et al., “A 2D Barcode-Based Mobile Payment System”, (2009), XP031561633 (10 pages).
Australian Examination Report for AU2017203295 dated Apr. 19, 2018, 4 pages.
Ratha, N., and Bolle, R., 1. History of Fingerprint Pattern Recognition—1.1 Introduction; 1.2 The Development of Fingerprint Classification Systems “Automatic Fingerprint Recognition Systems,” Springer-Verlag, (2004) (466 pages).
Office Action dated May 22, 2018 for U.S. Appl. No. 14/216,382 (pp. 1-8).
Chinese Office Action dated Oct. 10, 2017 for CN Application No. 201280019629.X, 7 pages.
Pan Kexian “Development of the Location-Based Service LBS Application of Intelligent Mobile Phone”, Information Technologies, Oct. 25, 2009, pp. 134-137, cited on Oct. 10, 2017 in CN201280019629.
Yang Jingjing “Help Web: Life Search Forerunner”Scientific and Technological Information, Aug. 5, 2010, pp. 36-37, cited on Oct. 10, 2017 in CN201280019629.
Wang Lepeng et al. “Discuss of Foursquare Pattern and Its Deelopment Strategies in China” Scientific and Technological Information, Aug. 15, 2010, pp. 90-91, cited on Oct. 10, 2017 in CN201280019629.
Chinese Office Action dated Nov. 6, 2017 for CN Application No. 201280018719.7, 24 pages.
Office Action dated Dec. 3, 2018 for U.S. Appl. No. 14/935,122 (pp. 1-13).
Notice of Allowance dated Jun. 27, 2018 for U.S. Appl. No. 13/542,443 (pp. 1-13).
Office Action dated Jun. 22, 2018 for U.S. Appl. No. 13/629,006 (pp. 1-8).
Office Action dated Jun. 21, 2018 for U.S. Appl. No. 14/216,351 (pp. 1-12).
Office Action dated Jun. 27, 2018 for U.S. Appl. No. 15/717,409 (pp. 1-7).
Office Action dated Jul. 16, 2018 for U.S. Appl. No. 14/698,317 (pp. 1-13).
I. Malavolta, Web-based hybrid mobile apps: state of the practice and research opportunities, 2 pages (Year: 2016).
Notice of Allowance dated Jul. 23, 2018 for U.S. Appl. No. 15/406,325 (pp. 1-9).
Office Action dated Sep. 21, 2018 for U.S. Appl. No. 15/839,493 (pp. 1-21).
Office Action dated Oct. 4, 2018 for U.S. Appl. No. 13/758,472 (pp. 1-22).
Notice of Allowance dated Oct. 11, 2018 for U.S. Appl. No. 13/520,481 (pp. 1-9).
Brick-and-mortar retailers snatching customers away from E-tailers. (Feb. 16, 2012). PR Newswire Retrieved from https:// dialog.proguest.corn/professional/docview/1346330115?accountid=142257 (Year: 2012) 3 pages.
Notice of Allowance dated Oct. 10, 2018 for U.S. Appl. No. 14/242,403 (pp. 1-11).
Office Action dated Nov. 2, 2018 for U.S. Appl. No. 13/624,779 (pp. 1-18).
Notice of Allowance dated Nov. 30, 2018 for U.S. Appl. No. 15/717,409 (pp. 1-8).
Office Action dated Dec. 27, 2018 for U.S. Appl. No. 13/398,817 (pp. 1-10).
Office Action dated Jan. 17, 2019 for U.S. Appl. No. 14/216,382 (pp. 1-7).
Ex Parte Quayle Action dated Jan. 18, 2019 for U.S. Appl. No. 16/182,288 (pp. 1-5).
Chinese Office Action (with English language translation) dated Jan. 30, 2019 for Application No. 201280019629.X, 10 pages.
Chinese Office Action (with English language translation) for Application No. 201480023694.9 dated Dec. 3, 2018, 17 pages.
Nunnenkamp, A., et al., “Cooling and squeezing via quadratic optomechanical coupling,” Physical Review, vol. A 82, pp. 021806-1-021806-4 (2010).
Olivero, J.J., and Longbothum, R.L., “Empirical fits to the Voigt line width: A brief review,” Journal of Quantitative Spectroscopy and Radiative Transfer, vol. 17, Issue 2, pp. 233-236, Feb. 1977.
Perahia, R., et al., “Electrostatically tunable optomechanical “zipper” cavity laser,” Applied Physics Letters, vol. 97, No. 19, pp. 191112-1-191112-3 (2010).
Regal, C.A., “Measuring nanomechanical motion with a microwave cavity interferometer,” Nature Physics, vol. 4, No. 7, pp. 555-560 (2008).
Rosenberg, J., et al., “Static and dynamic wavelength routing via the gradient optical force,” Nature Photonics, vol. 3, No. 8, pp. 478-483 (2009).
Safavi-Naeini, A. H., “Electromagnetically induced transparency and slow light with optomechanics,” Nature, vol. 472, No. 7341, pp. 69-73 (2011).
Safavi-Naeini, A.H., and Painter, O., et al., “Proposal for an optomechanical travelling wave phonon-photon translator,” New Journal Physics, vol. 13, No. 013017, pp. 1-30 (2011).
Safavi-Naeini, A.H., et al., “Optomechanics in an ultrahigh-Q two dimensional photonic crystal cavity,” Applied Physics Letter, vol. 97 No. 18, pp. 181106-1-181106-3 (2010).
Schliesser, A., “Highsensitivity monitoring of micromechanical vibration using optical whispering gallery moderesonators,” New Journal of Physics, vol. 10, No. 095015, pp. 1-19 (2008).
Serafini, A., et al, “Generation of continuous variable squeezing and entanglement of trapped ions in time-varying potentials,” Quantum Information Processing, vol. 8, pp. 619-630, Apr. 2009.
Song, B-S., et al., “Ultra-high-Q photonic double-heterostructure nanocavity,” Nature Materials, vol. 4, No. 3, pp. 207-210 (2010).
Sridaran, S., and Bhave, S.A., “Electrostatic acuation of silicon optomechanical resonators,” Optics Express, vol. 19, No. 10, pp. 7 (2011).
Stowe, T.D., et al, “Attonewton force detection using ultrathin silicon cantilevers,” Applied Physics Letters, vol. 71, Issue 2, pp. 288-290 (1997).
Sun, X., “A superhigh-frequency optoelectromechanical system based on a slotted photonic crystal cavity,” Applied Physics Letters, vol. 101, Issue 22, pp. 221116-1-221116-5, American Institute of Physics (2012).
Tadigadapa, S., and Mateti, K., Piezoelectric MEMS sensors: state-of-the-art and perspectives Measurement Science and Technology, vol. 20, No. 9, p. 092001 (2009).
Teufel, J. D., “Sideband cooling of micromechanical motion to the quantum ground state,” Nature, vol. 475, No. 7356, pp. 359-363 (2011).
Teufel, J.D., “Circuit cavity electromechanics in the strong-coupling regime,” Nature, vol. 471, No. 7337, pp. 204-208 (2011).
Thompson, J.D., et al., “Strong dispersive coupling of a high-finesse cavity to micromechnical membrane,” Nature, vol. 452, pp. 72-75 (2008).
Thourhout, D.V., and Roels, J., “Optomechanical device actuation through the optical gradient force,” Nature Photonics, vol. 4, pp. 211-217 Macmillan Publishers Limited (2010).
Weis, S., et al., “Optomechanically Induced Transparency,” Science, vol. 330, No. 6010, pp. 1520-1523 (2010).
Winger, M., et al., “A chip-scale integrated cavity-electro-optomechanics platform,” Optics Express, vol. 19, No. 25, pp. 17 (2011).
Woolley, M.J., et al, “Nanomechanical squeezing with detection via a microwave cavity,” Physical Review, vol. 78, No. 06, pp. 062303-1-062303-12 (2008).
Wu, J., et al, “A Low-Noise Low-Offset Capacitive Sensing Amplifier for a 50-.mu.g Hz Monolithic CMOS MEMS Accelerometer,” IEEE Journal of Solid-State Circuits, vol. 39, No. 5, pp. 722-730 (2004).
Yazdi, N., and Najafi, K., et al., “Performance limits of a closed-loop micro-g silicon accelerometer with deposited rigid electrodes,” Proceedings of the 12th International Conference on Microelectronics, pp. 313-316 (2000).
Yazdi, N., et al, “A high-sensitivity silicon accelerometer with a folded-electrode structure,” Journal of Microelectromechanical Systems, vol. 12, Issue 4, pp. 479-486 (2003).
Yazdi, N., et al, “Micromachined inertial sensors,” Proceeding of the IEEE, vol. 86, No. 8, pp. 1640-1659 (1998).
Yazdi, N., et al, “Precision readout circuits for capacitive microaccelerometers,” Proceedings of IEEE Sensors, vol. 1, pp. 28-31 (2004).
Yin, L., et al., “A low-noise CMOS interface circuit for closed-loop accelerometer,” 4th IEEE International Conference on Nano/Micro Engineered and Molecular Systems, pp. 502-505 (2009).
Zwahlen, P., et al, “Navigation grade MEMS accelerometer,” IEEE 23rd International Conference on Micro Electro Mechanical Systems (MEMS), pp. 631-634 (2010).
“Cavity opto-mechanics,” wikipedia, accessed at http://web.archive.org/web/20131102145212/http://en.wikipedia.org/wiki/Ca vity_opto-mechanics, last modified on Oct. 16, 2013. (6 pages).
“RF MEMS,” Wikipedia, accessed at http://web.archive.org/web/20100726064442/http://en.wikipedia.org/wiki/RF_MEMS, last modified Jul. 22, 2010. (8 pages).
Albrecht, T.R., et al., “Frequency modulation detection using high-Q cantilevers for enhanced force microscope sensitivity,” Journal of Applied Physics, vol. 69, No. 2, pp. 668-673 (1991).
Alegre, T.P.M, et al., “Optomechanical zipper cavity lasers: theoretical analysis of tuning range and stability,” Optic Express, vol. 18, No. 8, pp. 7872-7885 (2010).
Arcizet, O., et al., “Radiation-pressure cooling and optomechanical instability of a micro-mirror,” Nature, vol. 444, No. 7115, pp. 71-74 (2006).
Arlett, J.L., et al, “Self-Sensing Micro- and Nanocantilevers with Attonewton-Scale Force Resolution,” Nano Letter, vol. 6, No. 5, pp. 1000-1006, American Chemical Society (2006).
Ashkin, A., “Acceleration and Trapping of Particles by Radiation Pressure,” Physical Review Letter, vol. 24, No. 4, pp. 156-159 (1970).
Barclay, P.E, et al., “Nonlinear response of silicon photonic crystal microresonators excited via an integrated waveguide and fiber taper,” Optic Express, vol. 13, No. 3, pp. 801-820 (2005).
Binnig, G., and Quate, C.F., “Atomic Force Microscope,” Physical Review Letter, vol. 56, No. 9, pp. 930-933 (1986).
Braginsky, V.B., et al., “Quantum nondemolition measurements,” Science, vol. 209, No. 4456, pp. 547-557 (1980).
Chan, J., et al., “Laser cooling of a nanomechanical oscillator into its quantum ground state,” Nature, vol. 478, pp. 89-92 (2011).
Cooper, E.B., et al, “High-resolution micromachined interferometric accelerometer,” Applied Physics Letters, vol. 76, No. 22, pp. 3316-3318 (2000).
Eichenfield, M., et al., “A picogram- and nanometre-scale photoniccrystal optomechanical cavity,” Nature, vol. 459, No. 7246, pp. 550-556 (2009).
Eichenfield, M., et al., “Optomechanical crystals,” Nature, vol. 462, No. 7269, pp. 78-82 (2009).
Ekinci, K.L., and Roukes, M.L., “Nanoelectromechanical systems,” Review of Scientific Instrument, vol. 76, pp. 061101-1-061101-12 (2005).
Favero, I., and Karrai, K., “Optomechanics of deformable optical cavities,” Nature Photonics, vol. 3, No. 4, pp. 201-205, Macmillan Publishers Limited (2009).
Fleming, W.J., “New Automotive Sensors—A Review,” IEEE Sensors Journal, vol. 8, Issue 11, pp. 1900-1921 (2008).
Frank, I.W., et al., “Programmable photonic crystal nanobeam cavities,” Optics Express, vol. 18, No. 8, pp. 8705-8712 (2010).
Gabrielson, T. B., “Mechanical-thermal noise in micromachined acoustic and vibration sensors,” IEEE Transaction on Electron Devices, vol. 40, Issue 5, pp. 903-909, May 1993.
Gavartin, E., et al., “Optomechanical coupling in a two-dimensional photonic crystan defect cavity,” Physical Review Letter, vol. 106, No. 20, pp. 203902-1-203902-4, American Physical Society (2011).
Gigan, S., et al., “Self-cooling of a micro-mirror by radiation pressure,” Nature, vol. 444, No. 7115, pp. 67-70 (2006).
Gong, Y., et al., “Low power resonant optical excitation of an optomechanical cavity,” Optics Express, vol. 19, No. 2, pp. 12 (2011).
Groblacher, S., “Demonstration of an ultracold micro-optomechanical oscillator in a cryogenic cavity,” Nature Physics, vol. 5, No. 7, pp. 485-488 (2009).
Jiang, Y.G., et al, “Fabrication of piezoresistive nanocantilevers for ultra-sensitive force detection”, Measurement Science and Technology, vol. 19, No. 8, p. 084011 (2008).
Johnson, S.G., et al., “Perturbation theory for Maxwell's equations with shifting material boundaries,” Physical Review E, vol. 65, pp. 066611-1-066611-4 (2002).
Kenny, T., “Nanometer-Scale Force Sensing with MEMS Devices,” IEEE Sensors Journal, vol. 1, Issue 2, pp. 148-157, Aug. 2001.
Kippenberg, T. J., “Analysis of Radiation-Pressure Induced Mechanical Oscillation of an Optical Microcavity,” Physical Review Letter, vol. 95, No. 3, pp. 033901-1-033901-4 (2005).
Kippenberg, T. J., and Vahala, K. J., “Cavity Opto-Mechanics,” Optical Society of America, pp. 1-21 (2007).
Kippenberg, T. J., and Vahala, K. J., “Cavity Optomechanics: Back-Action at the Mesoscale,” Science, vol. 321, No. 5893, pp. 1172-1176 (2008).
Kippenberg, T., “Cavity Optomechanics: Back-action Cooling of Mechanical Oscillators,” p. 1-1 (Abstract).
Kleckner, D., and Bouwmeester, D., “Sub-kelvin optical cooling of a micromechanical resonator,” Nature, vol. 444, No. 7115, pp. 75-78 (2006).
Krause, A.G., et al., “A high-resolution microchip optomechanical accelerometer,” Nature Photonics, vol. 6, pp. 768-772 (2012).
Krishnan, G., et al, “Micromachined High-Resolution Accelerometers,” Journal of the Indian Institute of Science, vol. 87, No. 3, pp. 333-361 (2007).
Kulah, H., et al, “Noise analysis and characterization of a sigma-delta capacitive microaccelerometer”, IEEE J. Sol-Stat. Circ. 41, 352 (2006).
Lee, K. H., et al., “Cooling and Control of a Cavity Opto-electromechanical System,” Phys. Rev. Lett. vol. 104, No. 12, pp. 123604-1-123604-4, Feb. 2010.
Li, Y., et al., “Design of dispersive optomechanical coupling and cooling in ultrahigh-Q/V slot-type photonic crystal cavities,” Optics Express, vol. 18, No. 23, pp. 13 (2010).
Lin, Q., et al., “Mechanical Oscillation and Cooling Actuated by the Optical Gradient Force,” Physical Review Letter, vol. 103, pp. 1103601-1-1103601-4 (2009).
Liu, C-H., and Kenny, T.W., “A high-precision, wide-bandwidth micromachined tunneling accelerometer,” Journal of Microelectromechanical Systems, vol. 10, Issue 3, pp. 425-433, Sep. 2001.
Loh, N.C., et al., “Sub-10 cm3 lnterferometric Accelerometer with Nano-g Resolution,” Journal of Microelectromechanical Systems, vol. 11, No. 3, pp. 182-187 (2002).
Lopez, D., et al., “MEMS-based force sensor: Design and applications,” Bell Lab Technical Journal, vol. 10, No. 3, pp. 61-80, Jan. 2005.
Mamin, H.J., and Rugar, D., et al, “Sub-attonewton force detection at millikelvin temperature,” Applied Physics Letters, vol. 79, Issue 20, pp. 3358-3360, Nov. 2001.
Mari, A., and Eisert, J., “Gently modulating optomechanical systems,” Phys. Rev. Lett., vol. 103, No. 213603, pp. 1-7 (2009).
Marquardt, F., and Girvin, S.M., “Optomechanics,” Physics, vol. 2, No. 40, pp. 7 (2009).
Marquardt, F., et al., “Quantum theory of Cavity-Assisted Sideband Cooling of Mechanical Motion,” Physical. Review Letter, vol. 99, pp. 093902-1-093902-4 (2007).
Michael, C.P., et al., “An optical fiber-taper probe for wafer-scale microphotonic device characterization,” Optic Express, vol. 15, No. 8, pp. 4745-4752 (2010).
Midolo, L., “Electromechanical wavelength tuning of double-membrane photonic crystal cavities,” Applied Physics Letters, vol. 98, No. 21, pp. 9 (2011).
Mohd-Yasin, F., et al, “Noise in MEMS,” Measurement Science Technology, vol. 21, No. 1, pp. 1-22 (2010).
Muller, D.J., and Dufr ne, Y.F., “Atomic force microscopy as a multifunctional molecule toolbox in nanobiotechnology,” Nature Nanotech, vol. 3, pp. 261-269 (2008).
Jiang Hao, “Research on the discovery mechanism of relay node in the middle of the peer network”, the full-text database of excellent Master's degree thesis in China, (May 15, 2009).
Xing Changyou, etc.; “Network distance prediction technology”, Journal of Software , (Sep. 30, 2009), vol. 20, No. 9, p. 2470-2482.
Win Anyu, “A cluster based routing relay node selection algorithm”, 2010 Asia-Pacific Conference on Information Network and Digital Content Security (2010APCID), (Dec. 31, 2010).
Notice of Allowance dated Feb. 27, 2019 for U.S. Appl. No. 15/839,493 (pp. 1-9).
Office Action dated Mar. 1, 2019 for U.S. Appl. No. 14/698,317 (pp. 1-11).
Liang, J., Shi, R., Liang, F., & Gao, Z. H. (2001). WAP clients & SET protocol. Dr.Dobb's Journal, 26(6), 85-91. Retrieved from http:/ /dialog.proguest.conn/professional/docview/202692023?accountid=131444 (Year: 2001).
Office Action dated Apr. 1, 2020 for U.S. Appl. No. 16/140,879 (pp. 1-17).
Office Action dated Mar. 13, 2020 for U.S. Appl. No. 15/494,294 (pp. 1-8).
Office Action dated Mar. 6, 2020 for U.S. Appl. No. 16/017,241 (pp. 1-7).
Office Action dated Mar. 6, 2020 for U.S. Appl. No. 16/440,486 (pp. 1-8).
Office Action dated Aug. 21, 2020 for U.S. Appl. No. 15/988,485 (pp. 1-10).
Office Action dated Sep. 4, 2020 for U.S. Appl. No. 15/627,085 (pp. 1-10).
Office Action dated Oct. 6, 2020 for U.S. Appl. No. 16/532,095 (pp. 1-13).
Office Action dated Oct. 22, 2020 for U.S. Appl. No. 14/244,488 (pp. 1-13).
Office Action dated Oct. 27, 2020 for U.S. Appl. No. 16/294,676 (pp. 1-9).
Chinese Office Action (with English language translation) for Application No. CN201710037081.6, dated Oct. 21, 2020, 11 pages.
Office Action dated Nov. 12, 2020 for U.S. Appl. No. 16/273,976 (pp. 1-9).
Office Action dated Dec. 4, 2020 for U.S. Appl. No. 16/017,241 (pp. 1-10).
Related Publications (1)
Number Date Country
20190188691 A1 Jun 2019 US
Provisional Applications (5)
Number Date Country
61798483 Mar 2013 US
61668441 Jul 2012 US
61588620 Jan 2012 US
61537421 Sep 2011 US
61525168 Aug 2011 US
Continuations (2)
Number Date Country
Parent 14216351 Mar 2014 US
Child 16283251 US
Parent 13624779 Sep 2012 US
Child 14216351 US
Continuation in Parts (1)
Number Date Country
Parent 13589053 Aug 2012 US
Child 13624779 US