Patent Description:
In recent years, methods of accessing Internet content have evolved. For example, Internet content was formerly primarily accessed via computer systems such as desktop and laptop computers. Recently, handheld mobile devices (e.g., smartphones) have been introduced that allow users to request and view Internet content. Typically, mobile devices request and receive Internet content via a wireless access network such as, but not limited to, an <NUM> WiFi network.

<CIT> relates to measuring and/or analysing usage of resources on a network using data sources retrieved from actions performed by users of the resources. The data source may comprise user centric measurements including panel data, sample data, and survey data.

<CIT> describes a facility for identifying users of client computer systems sending server requests to a recipient computer system. The facility preferably also uses a user-agent field containing a text string identifying a browser.

The scope of this invention is defined by the claims. Any "embodiment" or "example" which is disclosed in the description but is not covered by the claims should be considered as presented for illustrative purpose only. An example method to monitor Internet activity includes determining if an application identified by an identifier of a content request from a client device supports authentication. Further, the example method includes not requesting authentication credentials if it is determined that the application does not support authentication. Further, the example method includes transmitting a request for credentials to the client device if the identifier of the content request identifies an application that supports authentication. Further, the example method includes storing an identifier of the content requested by the content request in association with the client device.

In some examples, the method includes storing a portion of the content in association with the client device.

In some examples, the identifier of the content request comprises a user agent identifier.

In some examples, the method includes determining if valid credentials are supplied in association with the content request. Further, in some examples, the method includes transmitting the request for credentials to the client device if the user agent identifier substantially matches a pattern of applications that support authentication and valid credentials are not supplied in association with the content request. Further, in some examples, the method includes transmitting content identified by the content request to the client device if the user agent identifier substantially matches the pattern of applications that support authentication and valid credentials are supplied in association with the content request.

In some examples, the method includes associating a panelist identifier associated with the credentials with the identifier.

In some examples, the panelist identifier is the credentials supplied in association with the content request.

In some examples, the method includes designating a client device to transmit content requests via a proxy.

In some examples, designating the client device to transmit content requests via the proxy further comprises transmitting the credentials and an Internet proxy address of the proxy; and causing the client device to transmit all subsequent requests for content to the proxy.

In some examples, transmitting the credentials and the Internet proxy address further comprises generating a configuration document comprising the credentials and the Internet proxy address.

In some examples, the configuration document further comprises instructions instructing a panelist associated with the client device to configure the client device to transmit all subsequent request for content to the proxy.

An example method to monitor Internet activity includes receiving registration data from a panelist. Further, the example method includes assigning credentials to a client device of the panelist. Further, the example method includes generating a configuration document identifying the credentials associated with the client device and a proxy address, the configuration document to instruct the panelist to cause subsequent requests for content via the proxy address. Further, the example method includes transmitting the configuration document to the client device.

In some examples, the registration data received from the panelist comprises an electronic mail address associated with the panelist; and transmitting the configuration document comprises electronically mailing the configuration document to the electronic mail address associated with the panelist.

In some examples, the method includes providing a hyperlink to download the configuration document to the panelist.

In some examples, the registration data received from the panelist comprises a phone number associated with the panelist; and transmitting the configuration document comprises text messaging a link to the configuration document to the phone number associated with the panelist.

In some examples, the registration data received from the panelist comprises a unique identifier associated with the panelist; and transmitting the configuration document comprises sending a link to the configuration document to the panelist.

In some examples, the registration data received from the panelist comprises a mailing address associated with the panelist; and transmitting the configuration document comprises mailing the configuration document to the mailing address associated with the panelist.

In some examples, the configuration document comprises an instruction document that instructs the panelist to enter the credentials and the Internet proxy address as configuration settings into the client device.

In some examples, the configuration document is interpreted by the client device such that the credentials associated with the client device and the Internet proxy address are applied to the client device.

In some examples, the registration data received from the panelist contains a model number of the client device used by the panelist; and the configuration document is generated specifically to instruct the panelist to apply the settings to the client device.

An example method to monitor Internet activity includes receiving a request for Internet content at a proxy, the request originating from a mobile device transmitting requests via a wireless access point. Further, the method includes determining if a user agent identifier of the request for Internet content identifies an application supporting proxy authentication. Further, the method includes determining if valid credentials are provided in association with the request for Internet content. Further, the method includes transmitting a request for credentials if the user agent identifier of the request for Internet content identifies an application supporting proxy authentication and valid credentials are not provided in association with the request for Internet content. Further, the method includes associating the request for Internet content with a mobile device if the user agent identifier of the request for Internet content identifies an application supporting proxy authentication and valid credentials are provided in association with the request for Internet content. Further, the method includes requesting content from an Internet content provider identified in the request for Internet content, the Internet content provider being different than the proxy. Further, the method includes transmitting the content to the mobile device.

In some examples, the method includes storing the request for Internet content a database.

In some examples, the method includes storing the association between the request for Internet content and the mobile device in the database if the user agent identifier of the request for Internet content identifies an application supporting proxy authentication and valid credentials are provided in association with the request for Internet content.

An example system to monitor Internet activity includes a proxy to service Internet data requests from at least one client device for Internet data. The proxy of the example system includes a request port to receive requests for Internet data. Further, the proxy includes an Internet port to retrieve Internet data based on the requests for Internet data. Further, the proxy includes a request servicer to determine if a user agent identifier of the requests received by the request port identify applications supporting proxy authentication, and to determine if valid credentials are provided in association with the requests received by the first port. Further, the example system includes a database to store an identification of the Internet data requested via the request port in association with a panelist based on the credentials associated with the request if valid credentials are provided in association with the requests.

In some examples, the system includes a registrar to register the client device, to uniquely assign credentials to the client device, and to generate configuration document to transmit the credentials and an Internet proxy address to the client device.

In some examples, the registrar is to store an association between the credentials, a panelist, and the client device in the database.

In some examples, the proxy is to store the Internet data requests from the client in the database.

In some examples, the proxy is to store the retrieved Internet data transmitted to the client in the database.

In some examples, the proxy is to receive requests for Internet data and transmit Internet data via a wireless network.

In some examples, the wireless network is a WiFi network.

An example apparatus to monitor Internet activity includes a request and response port to receive a request for Internet content. Further, the example apparatus includes a request servicer to receive the requests for Internet content via the request and response port, and transmit Internet content identified in the request for Internet content via the request and response port. Further, the example apparatus includes an Internet content processor to store the request for Internet content in a database. Further, the example apparatus includes an Internet port. Further, the example apparatus includes a content gatherer to receive the Internet content identified in the request for Internet content via the Internet port.

In some examples, the Internet content processor is to store credentials associated with the request in the database.

In some examples, the Internet content processor is to store a portion of the Internet content identified in the request for Internet content.

Mobile monitoring companies desire to gain knowledge on how users interact with their handheld mobile devices such as smartphones. In particular, the mobile monitoring companies want to monitor Internet traffic to and/or from the handheld mobile devices to, among other things, monitor exposure to advertisements, determine advertisement effectiveness, determine user behavior, identify purchasing behavior associated with various demographics, etc. Some known systems have utilized a proxy server to monitor Internet content being transmitted to and from the monitored device.

Such known monitoring systems implemented the proxy server as a Hypertext Transfer Protocol (HTTP) proxy that communicated with monitored handheld devices via a single port and required the monitored devices to provide authentication credentials including a username/device name and password that uniquely identified the mobile device involved in this Internet communication. These monitoring systems allowed mobile monitoring companies to associate Internet activity with the mobile device it originated from based on the username and password. Internet activity on handheld mobile devices is not limited to use of browsers (e.g., Apple® Safari®). For example, the Apple@ iPhone® and Apple® iPad™ support many third party applications (sometimes referred to as "Apps") accessing Internet content to perform a special function. For example, a weather application may request and display HTTP data from www. These apps typically do not permit unrestricted browsing from website to website on the Internet (although they may permit movement within a defined set of webpages). Thus, apps typically provide access to a limited set of data on the Internet. In contrast, a browser enables a user to access virtually any publicly available site on the Internet (subject to restrictions such as content blockers) and directly shows the user the contents of a website such as www.

While some applications accessing Internet content properly respond to proxy requests to provide credentials, many applications, such as the weather application from the previous example, do not presently support proxy authentication and therefore fail to function if a proxy requests credentials. This can be frustrating for panelists and may cause the panelist to abandon participation in the monitoring panel. Furthermore, it is desirable for monitoring entities to monitor Internet activity without affecting the manner in which users behave. Causing application failure due to a monitoring technique is inconsistent with that desire.

Some example methods of monitoring involve using an un-authenticated proxy on a port uniquely assigned to the panelist and/or handheld mobile device. However, when the handheld mobile device communicates via a WiFi network, a firewall likely exists between the handheld mobile device and the proxy. For example, many businesses and/or companies use firewalls to prohibit malicious and/or unwanted Internet content from reaching the users of their network. Firewalls block and/or prohibit malicious and/or unwanted Internet content by blocking particular ports. Ports <NUM> through <NUM> are defined as Well Known Ports by the Internet Assigned Numbers Authority (IANA), and are prohibited from use without registration with IANA, and therefore, communications over the Well Known Ports are more likely to be legitimate communications, and are conversely less likely to be blocked. Internet communications outside of the Well Known Ports range may be determined to be malicious and/or unwanted, and, thus, may be blocked by a firewall. The firewall may block all Internet communications from port <NUM> to port <NUM>, and if the uniquely assigned port is within the blocked range (e.g., port <NUM> to port <NUM>); the Internet communications of the handheld mobile device may be blocked. Because firewalls may be configured to block communication on unregistered ports, some panelists (e.g., panelists communicating via a blocked port) may experience application failures when using a WiFi network. This can be frustrating for panelists and may cause the panelist to abandon participation in the monitoring panel. Again, it is desirable for monitoring entities to monitor Internet activity without affecting the manner in which users behave. Causing application failure due to a monitoring technique is inconsistent with that desire.

To avoid errors inherent in using both an un-authenticated proxy (e.g., proxy ports being blocked by a firewall) and an authenticated proxy (e.g., applications failing to properly respond to requests for authentication credentials), the example system shown in <FIG> employs an actively filtered proxy. The actively filtered proxy monitors the Internet communications, and requests authentication credentials for applications supporting proxy authentication, while allowing un-authenticated Internet communications when the Internet communications originate from an application that does not support authentication credentials.

When an application of the client device requests Internet content, the application embeds a user agent field in the request for content. The user agent Field represents the application that is requesting the content. For example, if a browser application was to request Internet content, the user agent field identifies to the content server that a browser application was requesting the content. If an application is known to respond to requests for authentication, the monitoring system of <FIG>, upon receiving a request from the application, determines if valid credentials were supplied. If valid credentials are supplied, the monitoring system forwards the request to the Internet content provider identified by the request. Alternatively, if an application is known to not respond to requests for authentication, the monitoring system, upon receiving a request from the application, forwards the request to the Internet content provider identified by the request.

Applications are being developed every day and, therefore, new user agent identifiers are constantly being generated. For example, upon the release of a new version of an application, a new user agent identifier may identify the version of the application requesting Internet content. To properly identify applications that respond to requests for authentication, the user agent is matched against applications where the authentication capabilities are known. For example, if a new version of a browser application is released and includes a new user agent identifier, the user agent identifier of previous versions of the browser application may substantially match the user agent identifier of the new version. If the previous version of the browser application supported authentication, it is likely that the next version will also support authentication, and therefore authentication credentials are required.

The monitoring system may then record the data that the client devices request and/or receive and/or some or all of the data itself. Identifications of data and/or the data itself (e.g., web content) are collectively referred to herein as "session data. " The session data is recorded in association with the panelist via the credentials with which the session data is transmitted. From the recorded session data and recorded credentials, the monitoring system can uniquely identify the site(s) that a particular panelist is visiting and how the panelist interacted with their mobile device, while avoiding interruption of services for the panelist.

<FIG> is a block diagram of an example system <NUM> to monitor mobile Internet activity. The example system monitors Internet traffic to and/or from handheld mobile devices (e.g., a first client device <NUM> associated with a first panelist <NUM>, a second client device <NUM> associated with a second panelist <NUM>). The monitored Internet traffic between the monitored devices (e.g., the client device <NUM>, and the client device <NUM>) and Internet sites (illustrating Internet content provider(s) <NUM>) is routed to the example monitoring system <NUM>. As shown in <FIG>, the traffic passes through a wireless (e.g., WiFi) communication system (e.g., an Internet service provider <NUM> and communicative links <NUM>, <NUM>). The example monitoring system <NUM> includes a registrar <NUM>, a storage database <NUM>, and a proxy <NUM>.

The example first and second client devices <NUM>, <NUM> of <FIG> are handheld mobile devices. While in the illustrated example the first client device <NUM> is shown as an Apple® iPhone® and the second client device <NUM> is shown as a flip phone, any other type of device may be used. For example, other types or phones, a laptop computer, a desktop computer, a personal digital assistant (PDA), a netbook, or a tablet computer (e.g., an Apple® iPad™) may additionally or alternatively be used. The first and second client devices <NUM>, <NUM> may implement any mobile operating system, and may implement any type of hardware and/or form factor. In the illustrated example, the first and second client devices <NUM>, <NUM> are mobile devices and communicate via the first and second wireless communication links <NUM>, <NUM>.

The first and second communication links <NUM>, <NUM> of the illustrated example are WiFi communication links. However, any other method and/or system of communication may additionally or alternatively be used such as, for example, an Ethernet connection, a Bluetooth connection, a cellular connection, etc. Further, the example first and second communication links <NUM>, <NUM> of <FIG> implement the WiFi connection via an Institute of Electrical and Electronics Engineers (IEEE) <NUM> standard. However, any other systems and/or protocols for communications may be used such as, for example, IEEE <NUM>. 11n, IEEE <NUM>1b, etc..

The first and second panelists <NUM>, <NUM> of the illustrated example are panelists participating in a monitoring service. Although the example system of <FIG> is a panelist-based system, non-panelist and/or hybrid panelist systems may alternatively be employed. In the panelist system of the illustrated example, demographic information is obtained from the user when the user joins and/or registers for the panel. The demographic information may be obtained from the user via a telephone interview, by having the user complete an online survey, etc. Additionally or alternatively, panelists may be contacted and/or enlisted using any desired methodology (e.g., random selection, statistical selection, phone solicitations, Internet advertisements, surveys, advertisements in shopping malls, etc.).

In the illustrated example, the first and second panelists <NUM>, <NUM> are associated with the first and second client devices <NUM>, <NUM>, respectively. In the illustrated example, the client devices <NUM>, <NUM> are owned, leased, or otherwise belong to their respective panelists. The monitoring entity of the illustrated example does not provide the client devices. In other systems, panelists may be provided with client devices to participate in the panel. While in the illustrated example, the first and second client devices <NUM>, <NUM> are each associated with a single panelist, the first and second client devices <NUM>, <NUM> may alternatively be associated with more than one panelist. For example, a family may have a single client device that may be shared amongst multiple users. The sharing of a client device is less common when the client device is a cellular phone then when the client device is a portable computer (e.g., an Apple® iPad™).

The Internet service provider <NUM> of the illustrated example provides wireless Internet service to the first and second client devices <NUM>, 130via the communication links <NUM>, <NUM>. In the illustrated example, the wireless service is provided via a WiFi connection. However, the Internet service provider <NUM> may provide Internet service via any other type of connection. Further, the Internet service provider <NUM> may implement the WiFi connection via the IEEE <NUM><NUM> standard. However, any other systems and/or protocols for communications may be used. In practice, the Internet service provider <NUM> is sometimes referred to as a local access point, and provides a local area network to the client devices. In the illustrated example, the Internet service provider includes a firewall that blocks all ports that are not within the Well Known Ports range as defined by IANA (ports <NUM> to <NUM>). However, the ports blocked by the firewall may be any other ports, and may vary from Internet service provider to Internet service provider. For example, a security policy of a firewall of a corporate network (e.g., at an office or business) may be more restrictive and block more ports than a security policy of a firewall of a public network (e.g., a wireless access network hosted in a public location, such a coffee shop).

In the illustrated example, the monitoring system <NUM> is shown as multiple computing systems. However, the monitoring system <NUM> may ultimately be comprised of a single computing system. In the illustrated example, the monitoring system <NUM> includes the registrar <NUM>, the storage database <NUM>, and the proxy <NUM>. However, additional structures may be implemented to carry out one or more portions of the functionalities implemented by the registrar <NUM>, the storage database <NUM>, and/or the proxy <NUM>, and/or other functions.

In the example of <FIG>, the registrar <NUM> receives registration information from the panelists <NUM>, <NUM> and stores a record identifying the panelist <NUM>, <NUM> and/or their respective client devices <NUM>, <NUM>. In the illustrated example, the received registration information includes demographic information. However, any other information may additionally or alternatively be collected. The registration information may include, for example, information identifying the model of mobile device associated with the panelist, a mailing address associated with the panelist, an email address associated with the panelist, a phone number associated with the mobile device, a unique identifier of the panelist and/or mobile device (e.g., a social security number of the panelist, a phone number of the mobile device, a zip code of the panelist, and/or any combination or derivation of any information related to the panelist and/or mobile device), the age of the panelist, the gender of the panelist, the race of the panelist, the income of the panelist, where the panelist typically intend to use their device, how long the panelist has owned their device, the education level of the panelist and/or any other information related to the panelist and/or the mobile device.

In the illustrated example, the registration data is received by the registrar <NUM> via an electronic interface (e.g., by a panelist entering data into a form at a website or answering survey questions at a website). However, the registrar may receive the registration data may via other means. For example, the registrar may receive the registration data via a personal interview (by telephone or in person), a telephone interface, direct mailing, purchased lists, etc. While the registrar <NUM> of the illustrated example is an electronic system, the registrar <NUM> may alternatively be implemented manually by a person or group of people collecting and entering the registration data into the storage database <NUM>.

Upon receiving the registration data, the registrar <NUM> of the illustrated example creates a record associating the panelist and a device identifier information with the collected demographic information. The registrar <NUM> may also assign a unique alphanumeric identifier to the panelist or device. The identifier may be based on, for example, a serial number of the client device. The record is stored in the storage database <NUM>. In the illustrated example, the registrar <NUM> also assigns unique credentials to the panelist <NUM>, <NUM> and/or the client device <NUM>, <NUM> and stores the credentials in the record (or in association with the record for that panelist and/or client device). As noted above, in addition to assigning and storing the credentials, the registrar may assign and store additional identifiers. For example, the registrar may assign and store an identifier of the client device and/or the panelist. The panelist or client device identifier(s) may be the same as the credentials, or they may be different from the credentials. Further, when storing the credentials in the storage database <NUM>, the registrar may encode and/or encrypt the credentials to provide security and/or anonymity to the panelists.

In addition to assigning and storing the credentials, the registrar <NUM> of the illustrated example generates a configuration document. In the illustrated example, the configuration document instructs the panelist to configure the client device. The instruction document in the illustrated example is an email message. However, any other type of instruction document may additionally or alternatively be used. For example, a portable document format (PDF) document and/or a Microsoft® Word® document may be sent to the panelist as an attachment to an email message. Further, the configuration file may be custom generated for the particular type of mobile device based on the model of the mobile device as received by the registrar as part of the registration data.

Alternatively, the configuration document may comprise an electronically readable file that may instruct the mobile device to apply the settings contained in the configuration document. In some examples, the configuration document is an Extensible Markup Language (XML) file implementing a property list (referred to herein as a plist) file comprising configuration data such as the credentials, a port number, and an Internet proxy address to be used by the corresponding panelist and/or client device. However, any other type of document may be generated such as, for example, a comma separated (CSV) document, a portable document format (PDF) document, a Microsoft® Word® document, etc. In the illustrated example, the configuration document is signed using a public/private key infrastructure. However, the configuration may alternatively not be signed. If the configuration document is not signed, it may appear as an invalid configuration file to the panelist, which may cause the panelist to abandon participation in the panel. The configuration document is sent to the corresponding client device (e.g., via an email message with the file attached or with a link to the file). The client device may then interpret the data in the configuration file, thereby applying the data (e.g., the credentials and Internet proxy address) to future communication of the mobile device. In the illustrated example, the configuration file causes the mobile device to send all Internet traffic to the Internet address of the proxy <NUM> and to specify the credentials assigned to the client device in such communication. As a result, all Internet communications to and/or from the mobile device are addressed to the proxy <NUM> and can, when authenticated, be identified or associated with that particular client device. In the illustrated example the plist file is implemented for interpretation by an Apple® iPhone®, an Apple® iPod®, an Apple® iPad™. However, the mobile device may be any other type of mobile device, and may accept any type of configuration document.

While in the example of <FIG>, the configuration document is an instruction document that instructs the panelist to configure the client device to communicate with the proxy <NUM>. However, the configuration document may additionally or alternatively be an electronic document that may be interpreted by the client device to automatically configure the client device to communicate Internet related messages the proxy <NUM>. The configuration document may thereby instruct the panelist on how to apply the data stored in the configuration document or may instruct the panelist on how to directly apply the data stored in the configuration document to the client device.

As noted in the illustrated example above, the configuration document is transmitted to the panelist via an email message. However, any other means of transmitting the configuration document to the panelist may additionally or alternatively be used. For example, an email message may be transmitted containing a hyperlink to the configuration document, the configuration document may be transmitted to the panelist via a Short Message Service (SMS) message, the configuration document may be mailed to the panelist, and/or a telephone call may be placed to the panelist to instruct the panelist to configure the client device.

Finally, the registrar <NUM> transmits the configuration document to the panelist and/or client device. In the illustrated example, the configuration document is provided via an electronic mail (email) message. The email message includes a hyperlink to download the configuration document to the client device. However, any other methods of transmitting the configuration document may additionally or alternatively be used. For example, the configuration document may be transmitted as an attachment to the email message, the registrar <NUM> may transmit a short message service (SMS) message comprising a link to or a textural representation of an Internet address where the client device may download the configuration document, a direct mailing may be sent to the panelist comprising the configuration document and/or additionally comprising an electronic medium containing the configuration document, a telephone call may be placed to orally instruct the panelist on how to configure the client device, etc..

The registrar <NUM> of <FIG> is implemented by a processor executing instructions, but it could alternatively be implemented by an ASIC, DSP, FPGA, or other circuitry. The storage database <NUM> receives and stores identifiers associating the panelists <NUM>, <NUM> with the client devices <NUM>, <NUM> from the registrar <NUM>. Additionally, the storage database <NUM> receives and stores monitoring data from the proxy <NUM>. The monitoring data is associated with the corresponding panelist and/or client device via the authentication credentials used for the corresponding monitored Internet traffic, when credentials are provided. The storage database <NUM> may also be capable of storing data that is not identifiers and/or measurement data. For example, updated software and/or updated firmware for any component of the monitoring system <NUM> may be stored in the storage database <NUM>. Further, the storage database <NUM> may be capable of storing information that enables the registrar <NUM> to generate the configuration document. For example, the storage database <NUM> may store registration information such as the model of the client device <NUM>, <NUM>. Additionally, the storage database <NUM> may store demographic data as collected by the registrar <NUM>.

The storage database <NUM> may be any device for storing data such as, for example, flash memory, magnetic media, optical media, etc. Furthermore, the data stored in the storage database <NUM> may be in any data format such as, for example, binary data, comma delimited data, tab delimited data, structured query language (SQL) structures, etc. While in the illustrated example the storage database is illustrated as a single database, the storage database <NUM> may be implemented by multiple databases.

The proxy <NUM> of the illustrated example receives requests from the client devices <NUM>, <NUM> via the wireless Internet service provider <NUM>. The requests of the client devices <NUM>, <NUM> are received by the proxy <NUM> due to the configuration document having been applied to respective ones of the client device instructing the client device to transmit all subsequent requests through the proxy <NUM>. In the illustrated example, the proxy <NUM> receives Internet content requests via at least one Well Known Port (e.g., port <NUM> through port <NUM>). By only using Well Known Ports, it is less likely that the Internet communications will be blocked by a firewall. While in the illustrated example, a single proxy <NUM> is used, any number of proxies may represent the proxy <NUM> of <FIG>. Since the only limiting factor to the number of panelists that can be serviced is the processing power of the proxy <NUM>, this size of the panel can be expanded by using additional proxies at other Internet addresses. The additional proxies at other Internet addresses may be implemented by the same proxy <NUM> or by multiple proxies. For example, the proxy <NUM> may have multiple Internet addresses assigned to a network interface of the proxy <NUM> (e.g., virtual interfaces), or the proxy <NUM> may have multiple network interfaces each having an Internet address. While in the illustrated example only ports used within the Well Known Ports range are used, any other ports may additionally or alternatively be used. For example, ports within the Registered Ports range and/or the Dynamic and/or Private Ports range may potentially be used to accept requests for Internet content from the panelists. In a scenario where a panel monitoring system such as the monitoring system <NUM> is being tested, a typical panel will include at least sixty panelists. In a scenario where an ongoing panel is used a panel size of at least <NUM>,<NUM> panelists may be used.

Upon receiving a request from a client device <NUM>, <NUM>, the proxy <NUM> retrieves the requested Internet content from the Internet content providers <NUM> (or from a local cache if, for example, it had previously been requested and stored). In order to identify the panelist associated with the request, the proxy <NUM> determines whether the request originated from an application that supports proxy authentication. If the application is identified to support proxy authentication, the proxy <NUM> determines whether credentials were provided. If no credentials were provided, the proxy <NUM> requests credentials from the requesting device. If credentials were provided, the proxy associates the request with the panelist via the credentials.

Typically, the port used by the proxy to communicate with content providers <NUM> is limited to hypertext transfer protocol (HTTP) data that occurs over port <NUM>. After retrieving the requested Internet content from the Internet content provider(s) <NUM>, in the illustrated example the content is relayed to the requesting client device <NUM>, <NUM> via the assigned port. Additionally or alternatively, the content may be relayed to the requesting client device <NUM>, <NUM> via a port other than the assigned port (e.g., port <NUM>).

The proxy <NUM> of the illustrated example stores the requests for Internet content and/or portion(s) of such requests originating from the client devices <NUM>, <NUM> in the storage database <NUM> in association with the credentials with which the request was received. In storing the requests, the proxy <NUM> may additionally store other identifiers such as, for example, the identifier of the client device <NUM>, <NUM>, the identifier of the panelist <NUM>, <NUM>, and/or the credentials provided by the client device <NUM>, <NUM>. Additionally or alternatively, the proxy <NUM> may store a portion of the Internet content in the storage database <NUM>. For example, the proxy <NUM> may store the body of a webpage transmitted to the client device <NUM>, <NUM>. In another example, the proxy <NUM> may store an identifier of an advertisement appearing on the webpage transmitted to the client. This is particularly useful in situations where advertisements are rotated at websites. Additionally or alternatively, the proxy <NUM> may store characteristics of the response, such as, for example the HTTP header, a status code of the HTTP header, a content type of the HTTP header, etc..

The Internet content providers <NUM> supply content to clients via the Internet. In the illustrated example, the proxy <NUM> acts an intermediary for the client devices <NUM>, <NUM>, and, thus, is the client of the Internet content providers <NUM>. Internet content is often supplied over port <NUM>, as most Internet content is in the form of HTTP data. However, any other port may be used to supply Internet content. For example, File Transfer Protocol (FTP) data may be transmitted over port <NUM>, HTTP over Secure Socket Layer (SSL) may be transmitted over port <NUM>, etc..

The Internet content providers <NUM> can be any provider. For example, the Internet content providers <NUM> may comprise a web server hosting webpages formatted as Hypertext Markup Language (HTML) content. Alternatively, the Internet content provider <NUM> may be an application server providing application content to applications accessing Internet content. The application content may be formatted as HTML, XML, or may use any other protocol or port to return content to the requester. In some examples, the application data is implemented in a protocol specifically targeted for an application requesting Internet content (e.g., as the weather application described above).

<FIG> is a block diagram <NUM> illustrating an example request and response flow through the example system of <FIG>. The block diagram <NUM> of <FIG> illustrates communication between a mobile device <NUM>, a local network <NUM>, a firewall <NUM>, the proxy <NUM>, the storage database <NUM>, the Internet <NUM>, and the Internet content providers <NUM>. The mobile device <NUM> represents either of the client devices <NUM>, <NUM> and comprises a device networking subsystem <NUM>, a browser application <NUM>, an application accessing Internet content <NUM>, and a user interface <NUM>. Additionally, the block diagram illustrates a first request <NUM>, a second request <NUM>, a first response <NUM>, and a second response <NUM>.

The device networking subsystem <NUM> provides a framework for transmitting and receiving content. The device networking subsystem <NUM> may be implemented via an application processor, a software system that facilitates networked communication, a browser engine, a baseband processor that transmits network traffic, and/or any other system that provides a framework for transmitting and receiving content. In the illustrated example, the device networking subsystem is implemented by the networking libraries provided in the Apple® iPhone® operating system. However, any other libraries, systems, or programs may additionally or alternatively be used.

The browser application <NUM> and application accessing Internet content <NUM> are applications that are executed by a processor of the mobile device <NUM>. The browser application <NUM> requests HTTP Internet content from Internet content providers <NUM>, and renders the HTTP content for display. Additionally or alternatively, the browser application may request and render HTTPS Internet content. In some examples, the browser application is implemented by Apple® Safari®. However, any other application may alternatively be used. For example, Pocket Internet Explorer may be used. In some examples, the HTTP Internet content is HTML content. However, the content may be presented in any format that may be rendered by the browser application <NUM>.

The application accessing Internet content <NUM> may be any application on the mobile device that requests Internet content. For example, the application accessing Internet content <NUM> may be a weather application accessing Internet content provided by www. The Internet content provider <NUM> providing content for www. com may respond to content requests with HTML data. However, any other type of data may be contained in the content request. For example, the Internet content provider <NUM> providing content for www. com may provide an XML file containing a condensed weather forecast. Additionally or alternatively, the application accessing Internet content <NUM> may request media such as, for example, photos, video, audio, etc. Typically, applications accessing Internet content <NUM> are limited to a small amount of information to be displayed. For example, the weather application may not be able to display sports news. Although the browser <NUM> or the application accessing Internet content <NUM> may initiate requests for content, in some devices, such as the Apple® iPhone®, requests are formatted and transmitted by the device networking subsystem <NUM> based on system wide settings that control routing and/or addressing of such requests (e.g., to a specific port of a proxy <NUM>).

The user interface <NUM> of the illustrated example provides a display to the user and receives input from the user. The user interface <NUM> may comprise hardware, a graphics library, and/or a graphics driver for displaying content to the panelist, and may comprise hardware, an input library, and/or an input driver for receiving input from the panelist. Either or both the browser application <NUM> and the application accessing Internet content <NUM> may utilize the user interface to display content and receive input.

The local network <NUM> is hosted by the Internet service provider <NUM>. In the illustrated example, the local network <NUM> is an Internet Protocol (IP) version <NUM> (IPv4) based network. However, any other networking technology may additionally or alternatively be implemented. For example, the local network <NUM> may implement the IP version <NUM> (IPv6) protocol. Further, the local network <NUM> of the illustrated example is implemented using communication links <NUM>, <NUM>. While WiFi connections are shown, any other method of communication may additionally or alternatively be used such as, for example, an Ethernet network, a cellular network, etc. Additionally, the local network <NUM> is shown as a public network. However, the network may be a private network.

The firewall <NUM> of the illustrated example applies security policies to the requests and responses passing through the firewall <NUM>. In some examples, the firewall <NUM> may only allow communications over the Well Known Ports (e.g., ports <NUM> to <NUM>), as the ports may represent protocols which are known to not have security risks. If communication on a port is not allowed to pass through the firewall <NUM>, the communication is not transmitted from the requesting client device to the proxy <NUM>.

The proxy <NUM> receives a request <NUM> for Internet content from the mobile device, retrieves the content by sending a second request <NUM> to the corresponding content provider <NUM>, receive the content in a response <NUM> from the content provider <NUM>, and relays the content to the mobile device <NUM> via a second response <NUM>. In the illustrated example, the proxy <NUM> stores characteristics and/or identifiers of the request and/or response in the storage database <NUM>. These characteristics and/or identifiers may be, for example, a timestamp of the request and/or response, an IP address of the client, a user agent of the request, a status code of the response, a content type of the response, etc. However, the proxy <NUM> may additionally store the Internet content of the response in the storage database <NUM>. In relaying the request, the proxy <NUM> translates the port of the requests, as is described below in conjunction with <FIG>.

The Internet <NUM> in the illustrated example is a public network. However, a private network may instead be employed. For example, a network internal to an organization and/or company may be used to determine how members of the organization and/or employees of the company utilize internal web content via mobile devices.

The illustrated example shows a communication stream for a single request. The first request <NUM> is transmitted to the proxy <NUM> from the mobile device <NUM> over the local network <NUM> and through the firewall. The first request <NUM> uses a port that is not prohibited by the firewall <NUM>, and is for HTTP content (e.g., the request is for content that is served over port <NUM>). However, the content requested may be requested over any port. For example, the request may be for file transfer protocol (FTP) content and may occur over port <NUM>. The proxy <NUM>, upon receiving the first request <NUM>, stores some or all of the request in the storage database <NUM>, and generates a second request <NUM>. The second request <NUM> is effectively a translation of the first address as shown in <FIG>. The second request <NUM> is addressed to the Internet content provider <NUM> identified in the first request <NUM>. The second request <NUM> in the illustrated example is transmitted via the Internet <NUM> over port <NUM>, as the first request <NUM> identified content to be served over port <NUM>. The Internet content provider <NUM> responds to the second request <NUM> with the first response <NUM>. The proxy <NUM> receives the first response <NUM> via port <NUM>, stores some or all of the request in the storage database <NUM>, and forwards the content of the first response <NUM> as the second response <NUM> to the mobile device <NUM> over the port assigned to the mobile device <NUM>.

<FIG> is a block diagram <NUM> illustrating an example request and response flow through the example system of <FIG>. The block diagram <NUM> includes the proxy <NUM>, the Internet content provider(s) <NUM>, the mobile device <NUM>, the carrier network <NUM>, and the Internet <NUM>. The block diagram <NUM> additionally includes the first request <NUM>, the second request <NUM>, the first response <NUM>, and the second response <NUM>. Further, the requests and responses of the illustrated example are represented by HTTP request and response headers. The first request <NUM> is represented by the first HTTP request header <NUM> and the second request <NUM> is represented by the second HTTP request header <NUM>. The first response <NUM> is represented by the first HTTP response header <NUM> and the second response <NUM> is represented by the second HTTP response header <NUM>.

The first HTTP request header <NUM> is the header of a GET request generated by the mobile device <NUM>. In the illustrated example, the Internet content provider <NUM> is identified by the absolute Universal Resource Locator (URL) identified in the first line of the first HTTP request header <NUM> and the address of the proxy <NUM> and uniquely assigned port are identified by the "Host" line of the first HTTP request header <NUM>. The host identified in the illustrated example is proxy. MonitoringEntity. com, and the port that the request was made on is <NUM>. However, any other address identifying the proxy <NUM>, and any other port may alternatively be used. For example, the address identifying the proxy <NUM> may be the Internet Protocol (IP) address of the proxy <NUM>. In the illustrated example, the absolute URL of the Internet resource is "http://www. However, any other URL may additionally or alternatively be used.

The proxy <NUM> receives the first content request <NUM> and generates the second content request <NUM>. The second content request <NUM> is represented by the second HTTP request header <NUM>. In the illustrated example, the second HTTP request header <NUM> is a GET request directed to "http://www. com", and is transmitted over port <NUM> as no port other than port <NUM> is identified. The content being requested from "http://www. com/" in the illustrated example is "/". The proxy generates the contents of the second request by inspecting the first request <NUM>. For example, the proxy <NUM> identifies the requested content of the first request <NUM> as "http://www. com/", determines that the port to be translated to is port <NUM> (identified by http://), determines that the Internet content provider <NUM> identified is "www. com", and determines that the requested webpage from the Internet content provider is "/". The second content request <NUM> is transmitted over port <NUM> because the proxy <NUM> determines that the requested content is HTTP content, and no alternative port number is specified. Alternatively, the content identified by the first content request <NUM> may be content that is provided on a port other than port <NUM>. In that example, the absolute URL of the first HTTP request header <NUM> would identify the requested content as "http://www. com:<NUM>/", to convey that the content identified by the request is provided on port <NUM>. Further, the proxy <NUM> would generate the second HTTP request header <NUM> and include port <NUM> in the identified host (e.g., www. com:<NUM>).

The Internet content providers <NUM> receive the second content request <NUM>, and respond to the request via the first response <NUM>. The first response <NUM> is transmitted to the proxy <NUM>. In the illustrated example, the first response is transmitted over port <NUM>, as it is a response to a content request made on port <NUM>. However, any other port may be used to transmit the first response to the proxy <NUM>. The proxy <NUM> receives the first response <NUM>, and determines the correct port that the second response <NUM> should be transmitted over. In the illustrated example, the proxy <NUM> determines the port that the second response should be transmitted over by associating the first response <NUM> with the first request <NUM> via the second request <NUM>. In such an example, the proxy <NUM> can identify that the first request <NUM> originated on port <NUM>, and thus, the second response should be transmitted on port <NUM>. However, any other method of determining the port to transmit the second response over may additionally or alternatively be used. Further, the response may be transmitted over a port other than the port assigned to the mobile device <NUM>.

<FIG> is a block diagram of the example proxy <NUM> of <FIG>. The example proxy <NUM> includes a request and response port <NUM>, a request servicer <NUM>, an Internet content processor <NUM>, a content gatherer <NUM>, and an Internet port <NUM>. The request and response port <NUM> receives requests and transmit responses to and/or from the client devices <NUM>, <NUM>. The requests received by the port <NUM> are passed to the request servicer <NUM>. The content gatherer <NUM> transmits requests and receives responses from the Internet content providers <NUM> via the Internet port <NUM>. The Internet content processor <NUM> stores the requests (or portions thereof) and/or the retrieved content (or portions thereof or identifiers associated therewith) in the storage database <NUM>.

The request and response port <NUM> of the illustrated example is a Transmission Control Protocol (TCP) port and/or a User Datagram Protocol (UDP) port. However, any other port-based system may additionally or alternatively be used. The request and response port of the illustrated example is port <NUM>, as port <NUM> is typically used for HTTP content and is not typically blocked by most firewalls. However, the port may be any other port number such as, for example, a port within the Well Defined Ports range (ranging from port <NUM> to port <NUM>) and/or a port within the Registered Ports range (ranging from port <NUM> to port <NUM>).

The request servicer <NUM> of the illustrated example receives the requests from the request and response port <NUM> and performs a port translation if necessary. A port translation may not be necessary in the event that the proxy is hosted via the same port that the requested content is hosted on. For example, if the proxy is hosted on port <NUM> and the content request is for content provided on port <NUM> (e.g., HTTP content), no port translation would occur. First, the request is inspected to determine the destination port that is intended for communication with the Internet content provider <NUM>. For example, in many situations, the request will be for HTTP content and the destination port will be identified as port <NUM>. However, any other destination port may be employed. For example, FTP traffic may be translated to port <NUM>. The content gatherer <NUM> is responsible for gathering the content identified in the request (e.g., by sending translated requests to the corresponding content provider). Once the content is gathered, the request servicer <NUM> performs another port translation on the received content response to generate a translated response and to send the translated response to the client device over the port assigned to the client device that made the request.

In addition to translating the port of the request for Internet content, the request servicer inspects the user agent identifier of the request. If the user agent identifier identifies an application that supports authentication, the request servicer <NUM> determines if valid credentials are provided with the request. If valid credentials are not provided, the request servicer <NUM> requests credentials from the client device. If valid credentials are provided, the request servicer <NUM> provides the request to the content gatherer <NUM>.

The Internet content processor <NUM> of the illustrated example determines the credentials associated with the request if available, and stores the request in the storage database <NUM> in association with the credentials to uniquely identify the client device. In some situations, credentials may not be available for storing. For example, when the user agent indicates that the application requesting Internet content does not support proxy authentication, no credentials are requested. Therefore, some of the content requests stored in the storage database <NUM> may not uniquely identify the originating client device <NUM>, <NUM> and/or alternatively, the Internet content processor <NUM> may use the credentials to determine and store the panelist ID and/or the client device ID that was generated by the registrar <NUM> upon registration. In the illustrated example, the Internet content processor <NUM> stores the request for content. However, the Internet content processor <NUM> may store less than the entire request, a symbol for the request, etc., as shown in the tables of <FIG>. Additionally or alternatively, the Internet content processor <NUM> may store the content provided in the response and/or segments and/or portions of the content provided in the response in the storage database <NUM>. For example, the Internet content processor <NUM> may store advertisements transmitted to the client device in the storage database <NUM>.

The content gatherer <NUM> of the illustrated example requests the content identified by the request for Internet content. In particular, the content gatherer <NUM> utilizes the Internet address of the content requested in the request via one of the ports <NUM> to generate a second request to gather the requested Internet content. The content gatherer <NUM> transmits the second request via the Internet port <NUM>. The Internet port <NUM> of the illustrated example is a Transmission Control Protocol (TCP) port and/or a User Datagram Protocol (UDP) port. However, any other port-based system may additionally or alternatively be used. The Internet port of the illustrated example is for HTTP traffic (e.g., port <NUM>). However, any other port may be used. For example, port <NUM> could be used for File Transfer Protocol (FTP) traffic.

<FIG> is an example Hypertext Transfer Protocol (HTTP) request <NUM> as received by the example proxy <NUM> of <FIG>, <FIG>, and <FIG>. The example HTTP request <NUM> comprises a user agent identifier <NUM>. In the illustrated example, the HTTP request <NUM> is a GET request for www. com, as identified by the first and second lines. Further, the user agent identifier <NUM> identifies Apple® Safari®, a browser application of the Apple@ iPhone®, as the requesting application. However, any other application may request Internet content and be identified by the user agent identifier <NUM>. In the illustrated example, version identifiers of the user agent identifier <NUM> suggest that the version of Apple@ Safari® transmitting the request is an application for the Apple@ iPhone®; and further, that version <NUM> of Apple® Safari® is transmitting the request. In another example, an application accessing Internet content, such as a weather application may transmit a user agent identifier <NUM> suggesting that the application transmitting the request is the weather application.

While an example manner of implementing the proxy <NUM> of <FIG> has been illustrated in <FIG> and <FIG>, one or more of the elements, processes, and/or devices illustrated in <FIG> may be combined, divided, re-arranged, omitted, eliminated, and/or implemented in any other way. Further, the request and response ports <NUM>, the request servicer <NUM>, the Internet content processor <NUM>, the content gatherer <NUM>, the Internet port <NUM> and/or, more generally, the example proxy <NUM> of <FIG> and/or the example registrar <NUM> of <FIG> may be implemented by hardware, software, firmware, and/or any combination of hardware, software, and/or firmware. Thus, for example, any of the example request and response ports <NUM>, the example request servicer <NUM>, the example Internet content processor <NUM>, the example content gatherer <NUM>, the example Internet port <NUM> and/or, more generally, the example proxy <NUM> could be implemented by one or more circuit(s), programmable processor(s), application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)) and/or field programmable logic device(s) (FPLD(s)), etc. When any of the appended apparatus claims are read to cover a purely software and/or firmware implementation, at least one of the example request and response ports <NUM>, the example request servicer <NUM>, the example Internet content processor <NUM>, the example content gatherer <NUM>, the example Internet port <NUM>, the example proxy <NUM>, the example registrar <NUM>, and/or the storage database <NUM> are hereby expressly defined to include hardware and/or a computer readable medium such as a memory, DVD, CD, etc. storing the software and/or firmware. Further still, the example proxy <NUM> of <FIG> and <FIG> may include one or more elements, processes, and/or devices in addition to, or instead of, those illustrated in <FIG>, and/or may include more than one of any or all of the illustrated elements, processes, and devices.

A flowchart representative of example machine-readable instructions for implementing the proxy <NUM> of <FIG> and/or <NUM> is shown in <FIG> and <FIG>. Further, a flowchart representative of example machine-readable instructions for implementing the registrar <NUM> of <FIG> is shown in <FIG>. In these examples, the machine-readable instructions comprise program(s) for execution by a processor such as the processor <NUM> shown in the example computer <NUM> discussed below in connection with <FIG>. The program may be embodied in software stored on a computer readable medium such as a CD-ROM, a floppy disk, a hard drive, a digital versatile disk (DVD), or a memory associated with the processor <NUM>, but the entire program(s) and/or parts thereof could alternatively be executed by a device other than the processor <NUM> and/or embodied in firmware or dedicated hardware. Further, although the example program(s) are described with reference to the flowcharts illustrated in <FIG>, <FIG>, and <FIG>, many other methods of implementing the example proxy <NUM> and/or the example registrar <NUM> may alternatively be used. For example, the order of execution of the blocks may be changed, and/or some of the blocks described may be changed, eliminated, or combined.

As mentioned above, the example processes of <FIG>, <FIG>, and <FIG> may be implemented using coded instructions (e.g., computer-readable instructions) stored on a tangible computer readable medium such as a hard disk drive, a flash memory, a read-only memory (ROM), a compact disk (CD), a digital versatile disk (DVD), a cache, a random-access memory (RAM) and/or any other storage media in which information is stored for any duration (e.g., for extended time periods, permanently, brief instances, for temporarily buffering, and/or for caching of the information). As used herein, the term tangible computer-readable medium is expressly defined to include any type of computer readable storage and to exclude propagating signals. Additionally or alternatively, the example processes of <FIG>, <FIG>, and <FIG> may be implemented using coded instructions (e.g., computer-readable instructions) stored on a non-transitory computer-readable medium such as a hard disk drive, a flash memory, a read-only memory, a compact disk, a digital versatile disk, a cache, a random-access memory and/or any other storage media in which information is stored for any duration (e.g., for extended time periods, permanently, brief instances, for temporarily buffering, and/or for caching of the information). As used herein, the term non-transitory computer-readable medium is expressly defined to include any type of computer-readable medium and to exclude propagating signals.

<FIG> is a flowchart representative of example machine-readable instructions <NUM> that may be executed to implement the example proxy of <FIG>, <FIG>, and <FIG>. The program of <FIG> begins at block <NUM>, where the example machine-readable instructions <NUM> begin execution. First, the request servicer <NUM> of the proxy <NUM> waits for content requests (block <NUM>). In the illustrated example, the request servicer <NUM> waits for content requests only on port <NUM>. However, the request servicer <NUM> may wait for content requests on any other port, or the request servicer <NUM> may wait for content requests on multiple ports. Next, the request servicer <NUM> receives a content request (block <NUM>). Since multiple requests for content may be received at substantially the same time, the content requests may be processed in parallel to decrease the amount of time taken to respond to requests. However, the content requests may be processed in any other manner. For example, the content requests may be processed serially.

The request servicer <NUM> then determines if the user agent identifier identifies an application supporting authentication (block <NUM>). In the illustrated example, a predefined set of patterns identifying applications supporting authentication are stored in the storage database <NUM>. For example, upon the release of a new version of an application, a new user agent identifier may identify the version of the application requesting Internet content. To properly identify applications that that respond to requests for authentication, the user agent is matched against applications where the authentication capabilities are known. For example, if a new version of a browser application is released and includes a new user agent identifier, the user agent identifier of previous versions of the browser application may substantially match the user agent identifier of the new version. If the previous version of the browser application supported authentication, it is likely that the next version will also support authentication, and therefore authentication credentials are required. An example user agent pattern is "safari", and any user agent identifier that contains the term "safari" will be subject to authentication. However, any other pattern or set of patterns may additionally or alternatively be used. In the illustrated example, the patterns are updated by an administrator. However, as discussed in conjunction with <FIG>, an automated pattern generating system may additionally or alternatively be used.

The request servicer <NUM> attempts to match the user agent identifier against the predefined patterns, and if a pattern is found that substantially matches the user agent identifier, the request servicer <NUM> proceeds to determine if credentials were associated with the request (block <NUM>). If valid credentials were not associated with the request, the request servicer <NUM> transmits a request for valid credentials to the client device <NUM>, <NUM> (block <NUM>). The request for credentials may prompt the panelist and/or client device to re-transmit the previous request with valid credentials. If valid credentials were associated with the request, the credentials are associated with the panelist and/or client device (block <NUM>).

Next, the content gatherer <NUM> generates second request(s) based on corresponding ones of the request received at block <NUM>, to retrieve the Internet content identified in the corresponding content requests (block <NUM>). The content gatherer <NUM> gathers the requested Internet content by sending the second requests via the Internet port <NUM>. In the illustrated example, port <NUM> is used for sending requests. However, any other port may additionally or alternatively be used.

The Internet content processor <NUM> also associates the content requests with the corresponding requesting device and stores the association in the storage database <NUM> (block <NUM>). In the illustrated example, the Internet content processor <NUM> associates the content request with the client device via the credentials associated with the request. In some situations, the application requesting Internet content may not support proxy authentication and/or credentials. In those instances, the content request is stored in the storage database without the associated credentials. Additionally, the Internet content processor <NUM> may store the returned content or a portion of the returned content in the storage database <NUM> (block <NUM>). For example, the Internet content processor <NUM> may store images contained in the returned content.

The Internet content processor <NUM> may filter what is stored in the storage database. For example, the Internet content processor <NUM> may only store content requests that request HTTP content, as requests for non-HTTP content may not be parsed properly when analyzing the information. As another example, the Internet content processor <NUM> may omit style content (e.g., cascading style sheet (CSS) documents) from being stored in the storage database <NUM>, as style content may be of limited use when analyzing the information.

The request servicer <NUM> finishes servicing the request from the client device by transmitting the requested Internet content to the client device via the port on which the content request was received (blocks <NUM>). Control returns to block <NUM>, where the request servicer <NUM> waits for more content requests (block <NUM>).

<FIG> is a flowchart representative of example machine-readable instructions <NUM> that may be executed to implement the example proxy of <FIG>, <FIG>, and <FIG>. The example machine-readable instructions <NUM> of <FIG> are similar to the machine-readable instructions <NUM> of <FIG>. However, where in <FIG>, block <NUM> determines whether a user agent identifier matches a single list of patterns representing applications that support authentication, a more complex algorithm may additionally or alternatively be used. In the illustrated example of <FIG>, the request servicer <NUM> waits for content requests (block <NUM>), and receives a content request (block <NUM>). In the illustrated example of <FIG>, the request servicer <NUM> determines if the user agent identifier matches an application not supporting proxy authentication (block <NUM>). The request servicer <NUM> may consult a pattern or set of patterns stored in the storage database <NUM>. If the request servicer determines that the application does not support proxy authentication, control proceeds to block <NUM> where the machine-readable instructions <NUM> proceed in a fashion similar to <FIG>. If the request servicer <NUM> determines that the user agent identifier does not match a pattern or set of patterns identifying applications not supporting proxy authentication, the request servicer <NUM> determines if the user agent identifier matches an application supporting proxy authentication (block <NUM>). Since new applications accessing Internet content are created every day, new user agent identifiers are constantly being introduced. It is unlikely that at any given time a single list exists that can identify proxy authentication support based solely on the user agent identifier. Therefore, the two pattern or set of patterns method identifies proxy authentication support for known user agent identifiers. If the request servicer <NUM> determines that the application accessing Internet content does support proxy authentication, control proceeds to block <NUM>, where the machine-readable instructions <NUM> complete execution in a manner similar to the machine-readable instructions <NUM> of <FIG>.

If the user agent identifier is not identified by either block <NUM> or block <NUM>, control proceeds to block <NUM>, where the request servicer <NUM> determines if valid credentials were provided with the request (block <NUM>). If credentials were provided, then the application supports proxy authentication, and a pattern is created and stored in the storage database <NUM>. Subsequent requests including that particular user agent identifier will then be identified to support proxy authentication. Control then proceeds to block <NUM>, where the machine-readable instructions <NUM> complete execution in a manner similar to the machine-readable instructions <NUM> of <FIG>. If valid credentials were not provided with the request, the request servicer <NUM> transmits a request for credentials and waits for a response (block <NUM>). The request servicer may wait a short period of time (e.g., <NUM> seconds, <NUM> minute, <NUM> minutes, etc.), as the panelist may be prompted to enter their credentials. The request servicer <NUM> then determines if credentials were received in response to the request for credentials (block <NUM>). If credentials were received in response to the request for credentials, then the application supports credentials and control proceeds to block <NUM>, where the request servicer <NUM> stores a pattern in the storage database <NUM> that causes subsequent requests from that particular user agent to be identified as originating from an application that supports proxy authentication. If no response is received, it is likely that the application crashed or otherwise malfunctioned, and the request servicer <NUM> stores a pattern in the storage database <NUM> indicating that the application does not support proxy authentication (block <NUM>). Thus, subsequent requests originating from that particular application are not required to provide authentication credentials. Control then proceeds to block <NUM>, where the request servicer <NUM> waits for a content request. Thus, when a new user agent identifier is discovered, proxy authentication is attempted in order to determine whether the user agent identifier identifies an application supporting proxy authentication.

In addition to the example two pattern or set of patterns method shown in <FIG>, any other type of list may be implemented to control Internet communications through the proxy <NUM>. For example, if a user outside of the panel was attempting to use the proxy <NUM> (e.g., to maliciously to influence results, to redirect their internet traffic, etc.), a blocking list may be implemented to block users having certain IP addresses. Additionally or alternatively, other blocking lists may be implemented. For example, a list of user agents that are not supported by the proxy may be implemented to prevent Internet communications from desktop browsing applications. In particular, users of the proxy <NUM> (whether a panelist or not) may configure a browser running on a desktop computer to use the proxy <NUM>. To prevent Internet activity from the browser running on the desktop from affecting the results of the monitoring system, the proxy <NUM> may block Internet content requests when the user agent identifier matches a user agent identifier in a list of blocked user agents.

<FIG> is a flowchart representative of example machine-readable instructions <NUM> that may be executed to implement the example registrar <NUM> of <FIG>. The example machine-readable instructions <NUM> of <FIG> begin execution at block <NUM>, where the panelist <NUM>, <NUM> submits registration data to the registrar <NUM> (block <NUM>). In the illustrated example, the registration data is received by the registrar <NUM> (block <NUM>)via an electronic interface (e.g., a website). However, the registrar may receive the registration data in any other way. For example, the registrar may receive the registration data via a telephone interface, direct mailings, predefined lists, etc..

Next, the registrar <NUM> assigns the panelist credentials (block <NUM>). In the illustrated example, the panelist enters their desired credentials upon registering for the panel. The credentials of some examples are a username and password. If some or all of the desired credentials (e.g., the username) are unique to the panelist (e.g., the username is not already associated with another panelist in the panel), the credentials are associated with the panelist. The credentials are then transmitted to the panelist via the configuration document. Alternatively, the credentials may be randomly assigned to the panelist. For example, the username may be a first initial of the panelist followed by a last name of the panelist, and the password may be a random string of characters. Further, the panelist may be able to change their password by contacting the registrar <NUM> (e.g., by accessing a webpage hosted by the registrar <NUM>).

The registrar <NUM> generates a configuration document (block <NUM>). The configuration document includes the credentials assigned to the client device of the panelist, and an Internet proxy address. The Internet proxy address is the address of the proxy <NUM>. In the illustrated example, the configuration document is an instruction document that instructs the panelist on how to configure the client device, and is formatted as an email message transmitted to the panelist. However, any other type of document may be generated such as, for example, a comma separated (CSV) document, a portable document format (PDF) document, a Microsoft® Word® document, etc..

Next, the registrar <NUM> transmits the configuration document to the client device (block <NUM>). In the illustrated example, the configuration document is transmitted via an electronic mail (email) message. The email message includes a hyperlink that may be selected to download the configuration document. However, any other methods of transmitting the configuration document may additionally or alternatively be used. For example, the configuration document may be transmitted as an attachment to the email message, the registrar <NUM> may transmit a short message service (SMS) message comprising an Internet address where the client device may download the configuration document, a direct mailing may be sent to the panelist comprising the instruction document and/or additionally comprising an electronic medium containing the configuration document, a telephone call may be placed to orally instruct the panelist on how to configure the client device, etc. The panelist and/or client device then receive the configuration document (block <NUM>).

The client device <NUM>, <NUM> is then configured by the panelist (block <NUM>). Since the configuration document is an instruction document that may guide the panelist on how to configure the client device, the panelist may then configure the client device with the credentials, Internet proxy address, and proxy port as defined in the configuration document. The instruction document may thereby instruct the panelist on how to apply the configuration file or may instruct the panelist on how to manually apply the data in the configuration file. However, the configuration file may additionally or alternatively comprise an electronic document that may be interpreted by the client device. As such, instructions may be provided to the panelist regarding how to apply the electronic configuration file.

Upon application of the data contained in the configuration document, subsequent requests for Internet content made by the client device <NUM>, <NUM> are routed according to the configuration document. In particular, since the configuration document includes the Internet proxy address, the proxy port number, and the credentials, requests are proxied through the Internet proxy address via the proxy port number, and use the credentials for application supporting credentials.

<FIG> is a block diagram of an example computer <NUM> capable of executing the instructions of <FIG> and <FIG> to implement the monitoring system of <FIG>. The computer <NUM> can be, for example, a server, a personal computer, or any other type of computing device.

The system <NUM> of the instant example includes a processor <NUM>. For example, the processor <NUM> can be implemented by one or more Intel® microprocessors from the Pentium® family, the Itanium® family or the XScale® family. Of course, other processors from other families are also appropriate.

The processor <NUM> is in communication with a main memory including a volatile memory <NUM> and a non-volatile memory <NUM> via a bus <NUM>. Access to the main memory <NUM> is typically controlled by a memory controller (not shown).

The computer <NUM> also includes an interface circuit <NUM>.

One or more input devices <NUM> are connected to the interface circuit <NUM>. The input device(s) <NUM> permit a user to enter data and commands into the processor <NUM>. The input device(s) can be implemented by, for example, a keyboard, a mouse, a touchscreen, a track-pad, a trackball, isopoint and/or a voice recognition system.

One or more output devices <NUM> are also connected to the interface circuit <NUM>. The output devices <NUM> can be implemented, for example, by display devices (e.g., a liquid crystal display, a cathode ray tube display (CRT), a printer and/or speakers). The interface circuit <NUM>, thus, typically includes a graphics driver card.

The interface circuit <NUM> also includes a communication device (e.g., the request servicer <NUM>) such as a modem or network interface card to facilitate exchange of data with external computers via a network (e.g., an Ethernet connection, a digital subscriber line (DSL), a telephone line, coaxial cable, a cellular telephone system, etc.).

The computer <NUM> also includes one or more mass storage devices <NUM> for storing software and data. Examples of such mass storage devices <NUM> include floppy disk drives, hard drive disks, compact disk drives, and digital versatile disk (DVD) drives. The mass storage device <NUM> may implement the storage database <NUM>.

The coded instructions <NUM> of <FIG> and <FIG> may be stored in the mass storage device <NUM>, in the volatile memory <NUM>, in the non-volatile memory <NUM>, in the local memory <NUM>, and/or on a removable storage medium such as a CD or DVD.

From the foregoing, it will be appreciated that example methods, apparatus and articles of manufacture have been disclosed which allow Internet content requests from any application accessing Internet content on a mobile device via an authenticated proxy to be monitored while uniquely identifying the requesting device and/or panelist when the application accessing Internet content responds to requests for proxy authentication.

Claim 1:
A method to monitor Internet activity, the method comprising:
obtaining, by a registrar from a panelist during a panelist registration process, by executing an instruction with a processor, panelist demographic information identifying a demographic of the panelist;
assigning, by the registrar in response to the obtaining of the panelist demographic information, by executing an instruction with the processor, credentials to a mobile device of the panelist;
determining by a request servicer, if an application identified by an identifier of a content request from the mobile device supports proxy authentication, the identifier of the content request including a user agent identifier;
transmitting by the request servicer a request for credentials to the mobile device if the application supports proxy authentication, the proxy authentication based on a user identifier match to a pattern of applications that support authentication; blocking by an Internet content processor,
when the user agent identifier matches a user agent identifier in a list of blocked user agents, the content request; and
storing by the Internet content processor an identifier of a content requested by the content request in association with the mobile device to monitor Internet activity on the mobile device.