Enterprise access control and accounting allocation for access networks

Description

BACKGROUND

With the advent of mass market digital communications and content distribution, many access networks such as wireless networks, cable networks and DSL (Digital Subscriber Line) networks are pressed for user capacity, with, for example, EVDO (Evolution-Data Optimized), HSPA (High Speed Packet Access), LTE (Long Term Evolution), WiMax (Worldwide Interoperability for Microwave Access), and Wi-Fi (Wireless Fidelity) wireless networks increasingly becoming user capacity constrained. Although wireless network capacity will increase with new higher capacity wireless radio access technologies, such as MIMO (Multiple-Input Multiple-Output), and with more frequency spectrum being deployed in the future, these capacity gains are likely to be less than what is required to meet growing digital networking demand.

Similarly, although wire line access networks, such as cable and DSL, can have higher average capacity per user, wire line user service consumption habits are trending toward very high bandwidth applications that can quickly consume the available capacity and degrade overall network service experience. Because some components of service provider costs go up with increasing bandwidth, this trend will also negatively impact service provider profits.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the following detailed description and the accompanying drawings.

FIG. 1 illustrates a functional diagram of a network architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 2 illustrates a functional diagram of another network architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 3 illustrates a functional diagram of another network architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 4 illustrates a functional diagram of another network architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 5 illustrates a functional diagram of another network architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 6 illustrates a functional diagram of another network architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 7 illustrates a functional diagram of another network architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 8 illustrates a functional diagram of another network architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 9 illustrates a functional diagram of another network architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 10 illustrates a functional diagram of another network architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 11 illustrates a functional diagram of another network architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 12 illustrates a functional diagram of another network architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 17 illustrates a functional diagram of another network architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 18 illustrates a functional diagram of another network architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 19 illustrates a functional diagram of another network architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 20 illustrates a functional diagram of another network architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 21 illustrates a functional diagram of another network architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 22 illustrates a functional diagram of another network architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 23 illustrates a functional diagram of a secure device application architecture with device based service usage monitoring for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 24 illustrates a functional diagram of a secure device virtual machine architecture with device based service usage monitoring for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 25 illustrates a functional diagram of a secure device hardware execution partition architecture with device based service usage monitoring for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 26 illustrates a functional diagram of a secure device service processor architecture with device based service usage monitoring for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 27 illustrates a flow diagram for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 28 illustrates another flow diagram for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 29 illustrates another flow diagram for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

FIG. 30 illustrates another flow diagram for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as a process; an apparatus; a system; a composition of matter; a computer program product embodied on a computer readable storage medium; and/or a processor, such as a processor configured to execute instructions stored on and/or provided by a memory coupled to the processor. In this specification, these implementations, or any other form that the invention may take, may be referred to as techniques. In general, the order of the steps of disclosed processes may be altered within the scope of the invention. Unless stated otherwise, a component such as a processor or a memory described as being configured to perform a task may be implemented as a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task. As used herein, the term ‘processor’ refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention is provided below along with accompanying figures that illustrate the principles of the invention. The invention is described in connection with such embodiments, but the invention is not limited to any embodiment. The scope of the invention is limited only by the claims and the invention encompasses numerous alternatives, modifications and equivalents. Numerous specific details are set forth in the following description in order to provide a thorough understanding of the invention. These details are provided for the purpose of example and the invention may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to the invention has not been described in detail so that the invention is not unnecessarily obscured.

Some enterprises only allow certain specialized wireless devices to be used for connection to their enterprise network. Such devices typically contain secure data storage and enterprise program execution environments to protect enterprise information and network access. This approach is generally directed towards maintaining enterprise data integrity and enterprise network security. However, this approach does not address the various problems associated with allocating service usage or billing between consumer or non-enterprise service usage activities and enterprise service usage activities.

Accordingly, there is a need to provide for an enterprise and consumer billing allocation for wireless communication device service usage activities. There is also a need to address various issues with enterprise policies that can vary from employee to employee. For example, roaming policies can be configured differently for a global sales person than for a finance administrator who does not travel as much on enterprise business. Furthermore, some enterprises may not elect to pay for employee wireless communication device purchase or all employee wireless communication service usage needs or desires. As a result, some enterprises would benefit from techniques that allowed such enterprises to piggy back on consumer device or service purchases while maintaining an enterprise and consumer billing allocation for wireless communication device service usage activities.

Also, some consumers prefer to select their own wireless communication device that may not be an enterprise approved wireless communication device or a specialized enterprise device specified by enterprise IT managers. For example, certain enterprises may only offer certain Blackberry smart phone devices, and certain employees may prefer Apple iPhone and/or various Android based smart phone devices. Another trend suggests that a growing number of enterprise employees desire to use a single wireless communication device for their enterprise mobile communication, enterprise information access, and enterprise network access as well as for, for example, their personal mobile communication, access, and application needs (e.g., consumer/personal, that is, non-enterprise, use of cellular calls, text messaging, web browsing, social networking, games, and various other service usage activities). Such dual persona devices, where a first persona is oriented to enterprise access and/or application needs and a second persona is oriented to personal access and/or application needs, are enabled by the disclosure herein.

As a result, enterprise network managers generally need a way to safely allow consumers to perform consumer mobile access services that the enterprise can specify that will not be paid for by the enterprise. Various network architectures and techniques are described herein that allow an enterprise to determine how much service usage (e.g., how much of a corresponding service bill) should be allocated to device user services or consumer services and how much should be allocated to enterprise services in which the enterprise sponsors the enterprise access. Various design approaches and techniques are described herein for allocating enterprise and consumer billing in a secure manner that works with both specialized enterprise wireless communication devices as well as other wireless communication devices. For example, crediting a user bill with sponsored enterprise service usage is provided using various techniques described herein. As another example, providing enterprise employee reimbursement for enterprise services used on the employee wireless communication device or allowing an enterprise to deduct employee consumer service usage from their paycheck is provided using various techniques described herein. As yet another example, allowing a consumer to select from an instant activation platform on a wireless communication device that comes pre-loaded with various enterprise services is provided using various techniques described herein. As yet a further example, providing for a capability to install or download an enterprise application that provides secure enterprise mobile services access and allocating enterprise and consumer billing for consumer wireless communication devices is provided using various techniques described herein.

Various techniques for monitoring service usage and providing for secured and verifiable device assisted services (DAS), including DAS based service usage monitoring, are disclosed in co-pending U.S. patent application Ser. No. 12/380,758, entitled VERIFIABLE DEVICE ASSISTED SERVICE USAGE MONITORING WITH REPORTING, SYNCHRONIZATION, AND NOTIFICATION, filed on Mar. 2, 2009, published as U.S. Pub. App. No. 20100191612, co-pending U.S. patent application Ser. No. 12/695,019, entitled DEVICE ASSISTED CDR CREATION, AGGREGATION, MEDIATION and BILLING, filed on Jan. 27, 2010, published as U.S. Pub. App. No. 20100197266, co-pending U.S. patent application Ser. No. 12/695,020, entitled ADAPTIVE AMBIENT SERVICES, filed on Jan. 27, 2010, published as U.S. Pub. App. No. 20100198698, co-pending U.S. patent application Ser. No. 12/694,445, entitled SECURITY TECHNIQUES FOR DEVICE ASSISTED SERVICES, filed on Jan. 27, 2010, published as U.S. Pub. App. No. 20100199325, co-pending U.S. patent application Ser. No. 12/694,451, entitled DEVICE GROUP PARITIONS AND SETTLEMENT PLATFORM, filed on Jan. 27, 2010, published as U.S. Pub. App. No. 20100197267, which are incorporated herein by reference for all purposes.

In some embodiments, allocating enterprise and consumer billing for service usage activities on a wireless communication device is provided for service usage activities that an enterprise configures as approved and/or sponsored for enterprise billing (e.g., such service usage activities are paid for at least in part by the enterprise) and consumer applications and service usage activities that the device user chooses to use from the wireless communication device and that the enterprise does not sponsor. Various embodiments are disclosed herein describing a wide range of devices that users and enterprises may desire to use for such dual-purpose application scenarios. In some embodiments, devices for such applications can include a less specialized and secure device program execution environment as further described herein.

Accordingly, enterprise and consumer billing allocation for wireless communication device service usage activities is provided. In some embodiments, enterprise and consumer billing allocation for wireless communication device service usage activities includes monitoring a service usage activity of a wireless communication device (e.g., the monitoring can be performed in the wireless communication device and/or the monitoring of enterprise application service usage can be performed using a secure application server in the enterprise network), and determining an enterprise and consumer billing allocation for the monitored service usage activity. In some embodiments the allocation is determined by classifying the service usage activities as associated with a consumer service usage activity (e.g., in a consumer service usage activity list) or associated with an enterprise service usage activity (e.g., in an enterprise service usage activity list; or, as another example, if the monitored service usage activity is not included in the enterprise service usage activity list, then it can be automatically classified as a consumer service usage activity by default).

In some embodiments, enterprise and consumer billing allocation for wireless communication device service usage activities includes providing a service design center (SDC) for configuring an enterprise and consumer billing allocation of monitored service usage activities for a plurality of wireless communication devices associated with an enterprise account, and implementing the configured enterprise and consumer billing allocation for monitored service usage activities for the plurality of wireless communication devices associated with the enterprise account.

In some embodiments, enterprise and consumer billing allocation for wireless communication device service usage activities includes monitoring service usage of a wireless communication device, and determining whether a user is acting as a consumer (e.g., personal service usage activities on the wireless communication device) or a professional (e.g., enterprise service usage activities on the wireless communication device, that is, the user is working on the wireless communication device in his or her capacity as an employee for an enterprise, in which the wireless communication device is associated with an enterprise account for the enterprise) based on the monitored service usage activity (e.g., based on place, time of day, application or service activity, and/or other criteria or factors). In some embodiments, enterprise and consumer billing allocation for wireless communication device service usage activities differentially charges and/or allocates billing between the enterprise and the consumer based on a classification of the monitored service usage activity as allocated to the enterprise or to the consumer for billing/charging purposes. Such embodiments enable a dual persona device user experience.

In some embodiments, enterprise and consumer billing allocation for wireless communication device service usage activities includes monitoring a service usage activity of a wireless communication device, and reporting the monitored service usage activity to a network element (e.g., a service controller, a service usage reconciliation function, another service control or billing/charging function in the network, or another network element), in which the network element determines an enterprise and consumer billing allocation for the monitored service usage activity. In some embodiments, the network element (e.g., a service controller, a service usage reconciliation function, another service control or billing/charging function in the network, or another network element) determines an enterprise and consumer billing allocation for the monitored service usage activity. In some embodiments, a service usage reconciliation function determines how much service usage is due to enterprise service usage activities and how much is due to consumer service usage activities. In some embodiments, after determining the allocation between consumer and enterprise service usage activities, the service usage reconciliation function provides the information to a service usage accounting function (e.g., a carrier billing server or an enterprise service usage accounting server), which in turn delivers a consumer usage report or bill and/or an enterprise usage report or bill. In some embodiments, the service usage reconciliation function determines the amount of enterprise service usage and creates a service usage credit record so that a device user's account can be credited or a device user can be compensated or reimbursed for enterprise service usage costs. In some embodiments, a service usage monitor is configured to monitor service usage activities of a device. In some embodiments, the service usage monitor is configured to classify the monitored service usage activities as enterprise service usage activities. In some embodiments, the service usage monitor is configured to classify the monitored service usage activities as consumer service usage activities. In some embodiments, the service usage monitor is configured to monitor a first group of service usage activities for service usage allocation to a device user (e.g., using a list of service usage activities associated with a consumer service usage), and a second group of service usage activities for service usage allocation to an enterprise (e.g., using a list of service usage activities associated with an enterprise service usage). In some embodiments, service usage activities (e.g., service activities, such as applications, network, and/or voice based activities that use wireless network service usage resources) are classified using various techniques described herein, such as based on application (e.g., application credential), device (e.g., device credential), time of day, network destination, network traffic protocol and/or port, and various other criteria/factors. In some embodiments, the service usage monitor is implemented in the network (e.g., on one or more network elements in the carrier network and/or enterprise network, as described herein). In some embodiments, the service usage monitor is implemented in the device (e.g., using various techniques described herein, including verifiable and/or secured device-based implementations). In some embodiments, the service usage monitor is implemented using both network-based and device-based techniques, as described herein with respect to various embodiments.

In some embodiments, a set of service activities that will be sponsored by an enterprise (e.g., a specified or configured list of enterprise sponsored service activities) is managed by an enterprise service design center. In some embodiments, a list of service activities and the associated service policies for each service activity are compiled to form an enterprise sponsored service activity policy set. For example, enterprise email, enterprise calendar, and enterprise contacts can be configured as sponsored service activities. In some embodiments, the sponsored enterprise services list includes a list of network destinations that are associated with the services (e.g., an enterprise mail server address and/or an enterprise internal corporate network). For example, the enterprise email can be a sponsored service that is associated with an enterprise sponsored email service policy, which can limit destinations for corporate email, sizes of emails and/or email attachments, and/or other email related usage criteria or factors (e.g., a service usage charging policy).

In some embodiments, the monitored service usage is reported to the reconciliation function by a carrier network service usage monitoring element (e.g., a home agent (HA), access network gateway, or other network element, such as a deep packet inspection (DPI) function). In some embodiments, the monitored service usage is reported to the reconciliation function by an enterprise network service usage monitoring element (e.g., a carrier network gateway or a mobile services gateway/server or other element in the enterprise network that can measure service usage and associate it with a given device credential or application credential). In some embodiments, the monitored service usage is reported to the reconciliation function by an element in the mobile device (e.g., a service usage monitor in a secure enterprise mobile services application or a Service Processor function, which can be securely implemented and/or verified using various techniques described herein).

In some embodiments, a service design center for implementing enterprise and consumer billing allocation for wireless communication device service usage activities is provided. For example, an enterprise manager can use the service design center to select one or more services that the enterprise agrees to pay for/is responsible for paying for and to select one or more other services that the employees of the enterprise must agree to pay for/are responsible for paying for (e.g., if the employee elects to use/have such services that are not charged to the enterprise, or included as enterprise services that are charged to or paid for by the enterprise).

In some embodiments, a service design center that facilitates configuration of sponsored enterprise services for implementing enterprise and consumer billing allocation for wireless communication device service usage activities is provided. In some embodiments, a service design center for implementing enterprise and consumer billing allocation for wireless communication device service usage activities includes providing a service design center for a carrier network and another service design center for an enterprise network (e.g., in some cases, these service design centers can be combined).

In some embodiments, an enterprise sponsored service activity policy set is created by an enterprise network administrator through an enterprise service design center user interface (UI). In some embodiments, the enterprise sponsored service activity policy set includes a list of network destination addresses that corresponds to the desired sponsored service activity list, along with an access policy or service usage charging policy for the service activities. In some embodiments, all service activities in the enterprise sponsored service activity policy set receive the same access policies or charging policies. In some embodiments, a first subset of one or more of the service activities in the enterprise sponsored service activity policy set receive access policies or charging policies that are different than that of a second subset of service activities. For example, a sponsored enterprise email service can be in the first subset, and sponsored mobile voice services can be in the second subset, as certain employees (e.g., traveling sales personnel and/or executives) can be granted international and/or roaming mobile voice services, and other employees can be granted more limited sponsored mobile voice services.

In some embodiments, the enterprise network administrator uses the enterprise service design center to create an enterprise sponsored service device group list that includes device credentials or device application credentials that the carrier network and/or the enterprise network can use to identify a device or an application on a device as belonging to the group of devices for which the enterprise desires to sponsor enterprise service activities. In some embodiments, a sponsored service activity policy set is created by an enterprise network administrator through an enterprise service design center UI, and an enterprise sponsored service device group list is created by an enterprise network administrator through an enterprise service design center UI, and the two lists are stored in the enterprise service design center in which they are associated with one another for the purpose of provisioning the carrier network, the enterprise network, and/or the devices to provide the desired enterprise sponsored services policy set to the enterprise sponsored services device group, as described herein with respect to various embodiments.

In some embodiments, the association between an enterprise sponsored services device group and an enterprise sponsored service policy set is used by a service design center to create a provisioning table, in which the provisioning table is a list of the provisioning programming required for the various carrier network elements, enterprise network elements, and/or device elements to implement the desired sponsored service activity policy set for the enterprise sponsored services device group.

For example, an enterprise can use the service design center to configure certain destinations/services as enterprise services or potentially enterprise services based on various factors (e.g., corporate sites, corporate email/email servers, corporate web pages/intranet, and can, for example, agree to pay for a certain level of general web browsing by usage/time of day and/or other factors, corporate contacts/calendars, corporate videoconferencing; and certain applications, such as web conferencing applications or other applications; certain telephone service usages, etc.). As another example, the service design center can present a configuration interface that allows users to select from one or more service plans that include various consumer and enterprise allocations and/or to select an enterprise only service plan.

In some embodiments, the service design center specifies one or more service plans the device user can select from and these service plan selection options are configured into a configuration interface on a device software application that allows users to select from one or more service plans that includes various consumer and enterprise allocations and/or to select an enterprise only service plan. In some embodiments, the configuration interface is made available directly on the device via a device client that provides a service plan selection user interface that displays one or more service plan options configured in the service design center or the enterprise service design center. In some embodiments, the configuration interface is presented directly on a device user interface (UI) when the user attempts to use an access service usage activity that requires a service plan to be activated or purchased. In some embodiments, the configuration interface presented via the device UI accepts a user response, transmits it to a carrier network element responsible for provisioning a new user service plan that in turn activates the service plan chosen by the user, possibly after confirming service payment credit for the user or enterprise entity. In some embodiments, the carrier network element responsible for provisioning a new user service plan is a carrier usage accounting server. In some embodiments, the carrier network element responsible for provisioning a new user service plan is a consumer internet services element. In some embodiments, the carrier network element responsible for provisioning a new user service plan is a carrier gateway or home agent. In some embodiments the carrier network element responsible for provisioning a new user service plan is a billing system or service plan provisioning system. In some embodiments, the configuration interface is made available to the user in the form of a web site that provides a service plan selection user interface that displays one or more service plan options configured in the service design center or the enterprise service design center.

In some embodiments, the initial configuration of the end-user device includes one or more enterprise access service plans that allow the user to access certain applications or network destinations associated with enterprise access services, and the user can choose from one or more additional consumer oriented service plans offered directly on the device UI by a device software application in communication with a carrier network element responsible for provisioning a new user service plan that in turn activates the service plan chosen by the user, possibly after confirming service payment credit for the user or enterprise entity. In some embodiments, these access service plan options are configured with a service design center. In some embodiments, these access service plan options are configured with an enterprise service design center.

In some embodiments, enterprise data locally stored on the wireless communication device is secured and access to an enterprise network from the wireless communication device is secured so that only authorized devices or applications can access the network. In some embodiments, security for enterprise data and network access is accomplished by connecting the wireless communication device to the enterprise network via a secure mobile services application on the wireless communication device that connects via a secure channel to a secure mobile services gateway server in the enterprise network. In some embodiments, the SDC is programmed to provision the network and/or device apparatus to detect service usage communication with the mobile services gateway server and record that as a usage charge for network services. In some embodiments, such service usage communication with the mobile services gateway server is credited to the user's carrier account or used as a reimbursement to the user bill.

In some embodiments, determining the enterprise and consumer billing allocation for wireless communication device service usage activities is performed using a classifier implemented on the wireless communication device that classifies the monitored service usage activity (e.g., service usage can also be measured by the classifier and/or another function implemented on the wireless communication device, which can similarly be implemented in a secure execution area or in a secure memory), in which the classifier is executed in a secure execution area or a secure memory of the wireless communication device. In some embodiments, the security of the classifier is verified, periodically or at other times, using various techniques, such as by comparing a local service usage measure with a network based service usage measure and/or comparing a secured local service usage measure with another local service usage measure. In some embodiments, a secured application protects one or more enterprise applications (e.g., email, calendar, contacts, intranet access, and/or other enterprise specified applications, such as applications configured as approved or authorized enterprise applications for a particular enterprise by an enterprise manager using a service design center) from unauthorized use or tampering.

In some embodiments, the secure mobile services application also provides for usage monitoring of the enterprise service usage of the device. In some embodiments, the secure mobile services application also provides for service access control for the enterprise services of the device so that enterprise network access policies can be locally enforced on the device.

In some embodiments, security for enterprise data and network access is provided by connecting to the enterprise network via a secure mobile services application executed securely (e.g., in a virtual machine or in a hardware secured execution partition) on the wireless communications device that connects via a secure channel to a secure mobile services gateway server in the enterprise network. In some embodiments, security for enterprise data and network access is provided by connecting to the enterprise network via a secure mobile services application executed on a wireless communications device that includes a service processor, as described herein, that connects via a secure channel to a secure mobile services gateway server in the enterprise network. In some embodiments, the SDC is programmed to provision the network and/or wireless communications device apparatus to detect service usage communication with the mobile services gateway server, and record that as a usage charge for network services. In some embodiments, such service usage communication with the mobile services gateway server is credited to the user's carrier account or used as a reimbursement to the user bill.

In some embodiments, the service processor also provides for service usage monitoring of the enterprise service usage of the device, as described herein with respect to various embodiments. In some embodiments, the service processor also provides for service access control for the enterprise services of the device so that enterprise network access policies can be enforced on the device, as described herein with respect to various embodiments.

In some embodiments, enterprise and consumer billing allocation for wireless communication device service usage activities includes associating the wireless communication device and/or an authorized user of the wireless communication device (e.g., using device/user credentials) with an enterprise account (and, in some embodiments, a consumer account), associating an application with a service, and associating the service with the enterprise account (e.g., a service for the wireless communication device that the enterprise agreed to pay for). In some embodiments, enterprise and consumer billing allocation for wireless communication device service usage activities further includes using application-based monitoring and/or control using, for example, device assisted services.

In some embodiments, enterprise and consumer billing allocation for wireless communication device service usage activities includes crediting an associated consumer account for service usage allocated to an enterprise account. In some embodiments, enterprise and consumer billing allocation for wireless communication device service usage activities includes billing the enterprise for service usage allocated to the enterprise account. In some embodiments, enterprise and consumer billing allocation for wireless communication device service usage activities includes reporting to the enterprise (and, in some embodiments, the consumer) service usage allocated to the enterprise account, and the enterprise can, for example, provide an expense reimbursement to the consumer (e.g., employee, partner, associate, or contractor of the enterprise).

In some embodiments, enterprise and consumer billing allocation for wireless communication device service usage activities includes associating the wireless communication device with an enterprise account and a consumer account, associating an application with a service, and associating the service with the consumer account (e.g., a service for the wireless communication device that the consumer, such as an employee of the enterprise, agreed to personally pay for). In some embodiments, enterprise and consumer billing allocation for wireless communication device service usage activities further includes using application-based monitoring and/or control using, for example, device assisted services.

In some embodiments, enterprise and consumer billing allocation for wireless communication device service usage activities includes crediting an associated enterprise account for service usage allocated to a consumer account. In some embodiments, enterprise and consumer billing allocation for wireless communication device service usage activities includes billing the consumer for service usage allocated to the consumer account. In some embodiments, enterprise and consumer billing allocation for wireless communication device service usage activities includes reporting to the enterprise (and, in some embodiments, the consumer) service usage allocated to the consumer account, and the enterprise can, for example, deduct the cost for such service usage as an expense from the consumer's periodic/next paycheck.

In some embodiments, enterprise and consumer billing allocation for wireless communication device service usage activities does not require a network element or a device element to control services. For example, a user with a device associated with a bulk service usage plan can be automatically credited for sponsored enterprise service usage. If the bulk service usage plan has a service plan cap associated with the user's consumer service plan, then the service usage classified as sponsored enterprise service usage can be deducted from the total service usage such that the sponsored enterprise service usage does not count towards the user's capped consumer service plan usage. As another example, an enterprise account associated with the wireless communication device and/or user can allow the user to exceed a monthly or other service plan cap for sponsored enterprise service usage (e.g., based on various criteria and/or other factors, such as a more restrictive enterprise service policy to avoid potential misuse of sponsored enterprise services for personal use).

In some embodiments, enterprise and consumer billing allocation for wireless communication device service usage activities is provided using network-based and/or device-based techniques as described herein with respect to various embodiments. For example, using various techniques described herein, an enterprise manager can control the services for wireless communication devices for the enterprise, including access to such services and/or charging for such services (e.g., services used by employees in which some are charged to the enterprise on behalf of the employee and some are charged to the employee as a consumer of such services) and user notification messages. For example, the enterprise manager or another network element/function can cap and/or control service usage for consumer services and/or enterprise services.

In some embodiments, a service usage reconciliation function is provided. In some embodiments, the service usage reconciliation function implements the rules for a billing split for the enterprise and consumer billing allocation for wireless communication device service usage activities, as described herein with respect to various embodiments. In some embodiments, the service usage reconciliation function also facilitates fraud detection, as described herein with respect to various embodiments.

Carrier Managed Billing Allocation with Service Usage Monitoring in Carrier Network

FIG. 1 illustrates a functional diagram of a network architecture 100 for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. In some embodiments, a wireless communication device 110 includes a memory, an application processor (e.g., or more than one application processor or general processor), and a wireless modem, shown as an access modem 151. As shown, the wireless communication device 110 includes an operating system application space 131 for executing applications and communicating wirelessly using operating system lower layers 130, network stack 136, and the access modem 151. As used herein, application space refers to a portion of memory and a portion of a processor operating system execution environment for executing application programs. As also shown, the wireless communications device 110 includes operating system lower layers 130. As used herein, operating system lower layers refers to one or more OS layers that typically implement networking functions (e.g., network stack 136). In some embodiments, operating system lower layers 130 is where certain application data and communications security functions are implemented as described herein. In some embodiments, operating system lower layers 130 is where certain service usage monitoring and reporting functions are implemented as described herein. In some embodiments, operating system application space 131 executes various user applications, including one or more of user data application 111 and user voice application 112, and various enterprise applications, including enterprise data application 124 and enterprise voice application 126. In some embodiments, the execution environment for user applications and enterprise applications is the same (e.g., as shown in FIGS. 1 through 7). For example, a consumer Internet browser can execute in the operating system application space 131 for providing Internet web site browsing or web based email service via network stack 136 and wireless access modem 151 (e.g., a wireless modem), and an enterprise email program can also execute in the operating system application space 131 to communicate with an enterprise email server also via network stack 136 and wireless access modem 151. In some embodiments, the execution environment for user applications and enterprise applications are not the same (e.g., as shown in FIGS. 8 through 12).

In some embodiments, device 110 accesses various network-based voice services, such as consumer voice services 167 and/or enterprise sponsored/paid-for consumer voice services usage, via voice network 165. As shown, voice network 165 is in communication with carrier access network 150 via carrier gateway/home agent (HA) 152. In some embodiments, device 110 accesses various Internet based services, such as consumer Internet services 162 and/or enterprise sponsored/paid-for consumer Internet services usage, via Internet 160.

As also shown in FIG. 1, device 110 is in wireless communication (e.g., 2G/3G/4G access) with carrier access network 150. The carrier provides a carrier usage accounting server 154 (e.g., a carrier billing server) in communication with carrier access network 150. Carrier network access 150 is shown in communication with both Internet 160 and enterprise network 170 via Internet 160. Enterprise network 170 is shown in communication with Internet 160 as via enterprise firewall and secure access gateway 171 for protecting enterprise network 170 from unauthorized access. In some embodiments, to access enterprise network 170 through enterprise firewall and secure access gateway 171, device 110 includes a secure data application or a virtual private network application/function to facilitate secure authorization with enterprise firewall and secure access gateway 171 and to also protect the communication (e.g., encrypt such data communications). As also shown, behind enterprise firewall and secure access gateway 171, enterprise network 170 provides communication with secure enterprise mobile services gateway/server 172 in communication with enterprise network 170. As shown, secure enterprise mobile services gateway server 172 includes various enterprise applications/functions, including as shown, mobile email 173, mobile synchronization 174, mobile contacts 175, mobile calendar 176, mobile communications 177, and mobile intranet 178. In some embodiments, secure enterprise mobile services gateway server 172 provides mobile device mobile access to various enterprise network intranet services via enterprise intranet servers 180. In some embodiments, the enterprise mobile services include email, contacts, calendar, enterprise communications, mobile device synchronization services, intranet internal web sites, internal enterprise applications, enterprise file systems, and/or other enterprise networking services. In some embodiments, secure enterprise mobile services gateway server 172 provides optimized mobile application formatting of the enterprise information or synchronization services to synchronize the enterprise database for the above services in an efficient and/or timely manner.

In some embodiments, carrier usage accounting server 154 (e.g., the carrier billing server) communicates (e.g., using secure communication techniques) with service usage reconciliation server function 158 to obtain reconciled service charging reports (e.g., reconciled billing reports) and/or enterprise service usage charging credit reports. In some embodiments, the reconciled service charging reports (e.g., reconciled billing reports) and/or enterprise service usage charging credit reports are processed by carrier usage accounting server 154 and reported as user usage record(s) 155 and/or enterprise usage record(s) 156. For example, mediating such charging and credit reports can be based on various factors as described herein (e.g., by application, time of day/day of week, and/or other factors). For example, the service usage charges that occur due to communication with the servers or services that are part of enterprise network 170, including secure enterprise mobile services gateway server 172 and intranet servers 180, can be counted as an enterprise service usage credit.

In some embodiments, enterprise service design center 194 issues device provisioning instructions for the device credential list from the enterprise services device group, and for each of the credentials, a service control policy is set on enterprise firewall/secure gateway 171 to allow properly authorized devices to reach the desired destinations listed on the enterprise service activity policy set. The provisioning of enterprise firewall/secure gateway 171 with the enterprise service device group credentials and the enterprise service policy set is illustrated in FIG. 1 by the “C” input designator.

In some embodiments, enterprise service design center UI 196 and enterprise service design center 194 are provided as shown in FIG. 1. In some embodiments, enterprise service design center UI 196 and enterprise service design center 194 provide dedicated enterprise control of the network policy provisioning for configuring the service charging, accounting or billing allocation policies for differentiating between enterprise device service usage activities and consumer device service usage activities. Furthermore, in some embodiments, the portion of the enterprise network policy provisioning information that is needed to provision the carrier network elements to implement various techniques for allocating device service usage between enterprise and consumer activities is communicated between enterprise service design center 194 and carrier service design center 190.

A carrier provisioning system is typically not capable of providing direct access to an enterprise network administrator (e.g., carrier or enterprise personnel) for the purpose of provisioning such service charging capabilities. For example, such direct access is often not provided due to concerns related to the risk to the entire network that exists if network provisioning controls are made available to many different administrators to program charging allocation policies for many enterprises. However, as described herein, by isolating the required carrier network provisioning information to a secure service design center UI and policy configuration that only influences a small portion of the carrier network policy provisioning available to the carrier service design center and UI, the risk of causing such problems with the carrier network configuration is significantly reduced. Additionally, the process of performing the carrier side of the necessary provisioning is simplified for an administrator or in some cases can be automated.

The service design centers (e.g., carrier service design center 190 and enterprise service design center 194) are shown in FIG. 1 and various other figures as separate network elements in order to more clearly define and discuss the functions of the service design centers. In some embodiments, enterprise service design center 194 is implemented in various other network elements (e.g., in enterprise network management apparatus, such as management functions of secure enterprise mobile services gateway server 172 or other enterprise network management apparatus). In some embodiments, enterprise service design center 194 is implemented as a securely partitioned and managed device group interface to a subset of the provisioning capabilities of carrier network service design center 190. In some embodiments, enterprise service design center 194 is implemented as a securely partitioned and managed device group interface to a subset of the provisioning capabilities of a cloud-based secure enterprise mobile services network that is run by a centralized enterprise services provider such as an ASP or MVNO. As would be appreciated by one of ordinary skill in the art in view of the various embodiments described herein, enterprise service design center 194 can be implemented using various network and software/hardware architectures while providing for secure and controlled access as described herein.

In some embodiments, the enterprise service design center administrator creates or imports the enterprise service device group credentials and the enterprise service policy set using enterprise service design center UI 196. In some embodiments, the information included in the enterprise service device group credentials and the enterprise service policy set is also communicated from enterprise service design center 194 to carrier service design center 190 via the “C” connection designator as shown. For each of the device credentials listed in the enterprise services device group, carrier service design center 190 determines the information it needs to properly provision carrier gateway/home agent 152 with the proper access policy allowances and service usage charging policies to provide enterprise service access and usage credit for communications from device 110 to the enterprise network destination addresses specified in the enterprise service policy set. Programming of this provisioning information to carrier gateway/home agent 152 is indicated by the “A” information connector from carrier service design center 190 to carrier gateway/home agent 152. In some embodiments, this provisioning (e.g., programming) information sent via provisioning communication link “A” to carrier gateway/home agent 152 includes information to facilitate programming the enterprise device group credentials to: (i) receive the desired access service policy permissions, and (ii) implement the desired service usage accounting/charging policy settings. From the enterprise device group credentials list and the enterprise service activity policy set information provided in “C,” carrier service design center 190 determines the information needed to properly provision the service usage reconciliation server function 158. Programming of this provisioning information to service usage reconciliation server function 158 is indicated by the “B” information connector from carrier service design center 190 to service usage reconciliation server function 158. In some embodiments, service usage reconciliation function 158 is part of the carrier network, and service usage reconciliation function 158 implements the charging reconciliation rules to determine how much of the recorded device 110 service usage to place on the user's usage record or service bill (e.g., consumer service usage cost allocation) and how much to place on the enterprise's usage record or service bill (e.g., enterprise service usage cost allocation).

An enterprise may wish to allow consumer services on an end-user device that also allows an employee to access enterprise services over the access network. In some such embodiments, service design center 190 specifies one or more service plans from which the device user can select, and these service plan selection options are configured into a configuration interface on a device software application (e.g., user data app 111, user voice app 112 or service processor framework program 139 (shown, e.g., in FIG. 16)) that allows users to select from one or more service plans, for example, one or more plans with both consumer and enterprise allocations, and/or an enterprise-only service plan. In some embodiments, the configuration interface is made available directly on the device via a device client that provides a service plan selection user interface that displays one or more service plan options configured in service design center 190 or enterprise service design center 194. In some embodiments, the configuration interface is presented directly on the device user interface (UI) when the user attempts an access service usage activity that requires a service plan to be activated or purchased. In some embodiments, the configuration interface presented to the device UI accepts a user response and assists in sending the user response to a carrier network element responsible for provisioning a new user service plan that in turn activates the service plan chosen by the user, possibly after confirming service payment credit for the user or enterprise entity. In some embodiments, the carrier network element responsible for provisioning a new user service plan is carrier usage accounting server 154. In some embodiments, the carrier network element responsible for provisioning a new user service plan is consumer Internet services elements 162. In some embodiments, the carrier network element responsible for provisioning a new user service plan is a carrier gateway/home agent 152. In some embodiments, the carrier network element responsible for provisioning a new user service plan is a billing system or service plan provisioning system. In some embodiments, the configuration interface is made available to the user in the form of a web site that provides a service plan selection user interface that displays one or more service plan options configured in service design center 190 or enterprise service design center 194.

In some embodiments, the initial configuration of device 110 includes one or more enterprise access service plans that allow the user to access certain applications or network destinations associated with enterprise access services, and the user can choose from one or more additional consumer-oriented service plans offered directly on the device UI by a device software application (e.g., user data app 111, user voice app 112, or service processor framework program 139) in communication with a carrier network element responsible for provisioning a new user service plan that in turn activates the service plan chosen by the user, possibly after confirming service payment credit for the user or enterprise entity. In some embodiments, these access service plan options are configured using service design center 190. In some embodiments, these access service plan options are configured using enterprise service design center 194.

In some embodiments in which a user has selected a consumer-oriented service plan in addition to an enterprise service plan, service usage reconciliation function 158 distinguishes between data usage within the enterprise service plan and data usage within the consumer-oriented service plan. In some embodiments, the enterprise does not pay for, backhaul, process, or police data usage associated with the consumer-oriented plan. In some embodiments, service usage reconciliation function 158 determines how much data usage by device 110 is enterprise data usage, and how much data usage by device 110 is consumer data usage. In some embodiments, service usage reconciliation function 158 allocates data usage associated with applications and/or services specified by the enterprise service plan to the enterprise, and data usage associated with applications and/or services specified by the consumer-oriented data plan to the consumer.

The various embodiments described herein with respect to FIG. 1 support a variety of techniques for allocating service usage accounting or billing between enterprise services and consumer services. For example, service usage reconciliation function 158 can report measured total usage, measured consumer usage, and/or measured enterprise usage to carrier usage accounting server 154. In some embodiments, the reconciliation service usage function (e.g., provided by service usage reconciliation function 158 and/or another element/function) implements the business rules that determine how much of the service usage to charge the user (e.g., a consumer service usage allocation) and how much of the service usage to charge the enterprise (e.g., an enterprise service usage allocation). In some embodiments, the service usage reconciliation service usage function records total device service usage, records total enterprise service activity service usage, and then subtracts the enterprise service usage from the total device service usage to determine a consumer service usage (e.g., a consumer service usage allocation). In some embodiments, service usage reconciliation function 158 passes on the enterprise service usage as a credit to the consumer account. In some embodiments, this credit is accounted for by the carrier billing the user at a reduced amount according to the credit and billing the enterprise for an increased amount according to the credit. In some embodiments, the credit is accounted for by communicating the credit to the enterprise so the enterprise can reimburse the consumer (e.g., generating an expense reimbursement for the credit to the consumer as an employee or contractor of the enterprise, directly paying the enterprise allocation of the carrier bill for the consumer, and/or various other approaches as described herein). In some embodiments, the credit is reported to the enterprise so that the enterprise can seek payment for the non-enterprise service usage (e.g., consumer service usage allocation) from the consumer (e.g., who can be an employee or contractor of the enterprise).

As another example, an enterprise allocation can also include providing an allowance for a certain level of monthly usage of data and/or voice. In some embodiments, carrier usage accounting server 154 generates a bill for the associated consumer account (e.g., associated with device 110, such as based on the device/user credentials) that reflects the cost of the service usage allocated to consumer service usage and a credit for the cost of service usage allocated to enterprise service usage (e.g., to offset the cost of the enterprise service usage, which can be billed to the enterprise account associated with the enterprise service usage for the device 110). As described herein, based on an allocation of enterprise and consumer service usage, various techniques for billing/charging and generating credits/reporting (e.g., the enterprise can generate the user/employee monthly expense reimbursements to compensate the user/employee for the determined cost of the enterprise service usage and/or other approaches as described herein) can be provided using the network architecture 100 and/or other network architectures, as described herein.

In some embodiments, an enterprise manager manages service usage by specifying an access network service usage limit for a service usage activity (such as data service, voice service, text service, a roaming service, or a more detailed classification of data service such as one or more websites or one or more device applications), and, when that usage limit is reached for a device that is managed by the enterprise manager, a service usage notification message is generated. In some embodiments, the service usage notification message is configured through enterprise service design center UI 196. In some embodiments, the service usage notification message is delivered to device 110. In some embodiments, the service usage notification message is presented to the user via a user interface of device 110.

In some embodiments, the service usage notification message provides information about data usage or the status of device 100. In some embodiments, the service usage notification message is triggered by an event, e.g., detection that device 110 reaches a data usage ceiling, determination that device 110 is roaming, etc. In some embodiments, the service usage notification message provides real-time or near-real-time information about data usage. In some embodiments, the service usage notification message provides information about remaining data usage availability or entitlement. In some embodiments, the service usage notification message comprises a detailed report of enterprise usage by user, user group, device, device group, or location.

In some embodiments, secure enterprise mobile services gateway server 172 is a dedicated enterprise application server for a particular enterprise (e.g., company, government organization, school/university, or another entity). In some embodiments, secure enterprise mobile services gateway server 172 is a carrier or a third party service provider (e.g., a carrier for wireless network services, such as AT&T, Sprint, T-Mobile, and/or various other wireless network service providers/carriers or third party service providers) controlled/managed application server that performs the application server functions for various different enterprises (e.g., as a service/outsourced IT services model). In some embodiments, device 110 is partitioned (e.g., associated with a particular enterprise/MVNO partition and associated enterprise account) based on device credentials and/or VPN to determine a service plan for managing (e.g., to determine how to allocate enterprise/consumer service usage for) device 110. In some embodiments, based on the partition determination of device 110, and the associated service plan for managing device 110, appropriate service usage monitoring and classification can be determined for providing an enterprise and consumer allocation for service usage activities of device 110 based on the associated service plan(s).

For example, by programming the business rules in service usage reconciliation function 158 that determine the service usage accounting allocation between enterprise services and consumer services, many approaches can be provided for creating a service that provides an enterprise service to a device when the device user has selected a consumer service plan or elected to pay for a consumer service plan. As an example, if the device user has chosen a service plan, the enterprise service usage accounted for in enterprise usage record 156 can be billed to the enterprise rather than the consumer. As another example, if the device user has chosen a service plan, the consumer service usage accounted for in user usage record 155 can be billed to the device user rather than the enterprise. As yet another example, if the device user has selected a service plan, the enterprise service usage can be communicated to the enterprise (e.g., and/or the device user), and the enterprise can issue a reimbursement to the device user for the enterprise portion of the user's bill, or pay the carrier directly for a portion of the user's bill, thus reducing the amount the user must pay. In some embodiments, the business rules in service usage reconciliation function 158 are programmed to provide the device user with a certain amount of service usage that may or may not be directly related to enterprise services.

For example, the user can be allocated a certain amount of general purpose browsing that includes network destinations that are not specified in the enterprise service activity policy set. In some embodiments, there is a cap to such general purpose browsing, and carrier service design center 190 can provision the network and/or the device to alert the user regarding how much of the enterprise sponsored browsing remains or when the enterprise sponsored internet browsing cap is reached or exceeded. In some embodiments, the business rules in service usage reconciliation function 158 are programmed to deduct the service usage associated with the enterprise sponsored general purpose browsing, up to the specified cap, from the user's bill. In this way, the user can be allocated an allowance for services that either the enterprise sponsors to account for enterprise related service usage that may not be included in the enterprise service activity policy set or that the enterprise simply desires to sponsor to reduce the device user's consumer service plan billing.

In a similar manner, services other than browsing that are not necessarily associated with enterprise service usage can also be sponsored by the enterprise by properly provisioning the business rules in service usage reconciliation function 158. For example, a catch-all enterprise sponsored allowance (e.g., or cap) for “bulk” internet usage can be provided. The fact that the user is provided with such an allowance may be pointed out to the user if the user disputes how much of his or her device service usage cost should be covered by the enterprise and how much the user should cover personally. Another example is to provide a certain amount of voice minutes to any phone number or to phone numbers not in the enterprise service activity policy set.

In some embodiments, the business rules in service usage reconciliation function 158 are provisioned so that the enterprise specifically does not allow, sponsor, or pay for certain device service usage activities. In some embodiments, these service usage activities can include access to network destinations, applications, or services that pose security risks to enterprise data stored on device 110 or pose security risks to enterprise network 170. In some embodiments, these activities include access to network destinations, applications, or services that the enterprise does not wish to sponsor or that are potentially associated with user activity that violates enterprise policy or laws. For example, the business rules may be configured to allow only transmission of business data on approved networks, e.g., excluding free or unknown WiFi hotspots, or only when device 110 is connected to the network via a VPN. In some embodiments, such service usage activities that violate enterprise security policies or other service usage policies are blocked by the business rules programmed into the network or the device as specified in the enterprise service activity policy set.

By programming the business rules in service usage reconciliation function 158 that determine the service usage accounting allocation between enterprise services and consumer services, many approaches can be provided for creating a service that provides an enterprise service to a device when the device user has not selected a consumer service plan or elected to pay for a consumer service plan. For example, if the device user has not chosen to select or pay for a consumer service plan, carrier gateway/home agent 152 can be programmed to allow service usage for the enterprise service policy set but deny all other access until the user chooses a consumer service plan. In some embodiments, when/if the consumer chooses a consumer service plan then access would be expanded beyond just the enterprise services, because when the service plan activation occurs, consumer service policy set in carrier gateway/home agent 152 will be updated to allow service (e.g., as the carrier administrator user of carrier service design center 190 programs a different set of consumer service access policies for each consumer service plan that can be chosen). In some embodiments, the user is allocated a certain amount of general purpose data access or voice minutes as described above even though the user does not have a consumer data plan. Another example is to provide the user with a certain monetary allowance that is sponsored by the enterprise rather than a service usage amount.

Although enterprise service design center 194 is shown provisioning mobile server usage counter 179 (e.g., shown in FIG. 5) and enterprise firewall/secure gateway 171, it should be understood that not all device provisioning connections as shown from secure enterprise mobile services gateway/server 172 to device 110 are shown for device functions including secure mobile services application access, communication link provisioning (e.g., cryptographic encryption keys, VPN settings, and various other security/communication provisioning), security programs, service control programs, and program settings for enterprise service applications, such as email, calendar, contacts, mobile synchronization services, and traffic control. As shown, the labeled provisioning connections are provided as exemplary embodiments to assist in identifying the network elements that are provisioned for network access control and network service usage charging reporting. Those of ordinary skill in the art will appreciate that these additional device provisioning functions are not necessarily specifically called out with provisioning connection labels in each figure, and it will be apparent to one of ordinary skill in the art which of these device provisioning functions and connections are needed from enterprise service design center 194 and device 110. It will also be apparent to one of ordinary skill in the art in view of the various embodiments described herein that the various device provisioning connections and device element programming configurations needed to provision these device functions can be managed by secure enterprise mobile services gateway/server 172 via a device management communications link. It will also be apparent to one of ordinary skill in the art that, in some embodiments, the flow of policy provisioning information for the various device elements that participate in establishing service usage monitoring and reporting policies or service access control policies starts in enterprise service design center 194 and flows through secure enterprise mobile services gateway/server 172 over a device management link, and through the device management link on device 110 to the device 110 functional elements that need to be provisioned. In various embodiments described herein, the device elements that are provisioned in some embodiments to set up enterprise services, service usage monitoring and reporting policies, or service usage access control policies include one or more of enterprise data application 124, enterprise voice application 126, secure mobile enterprise application environment 120 (shown, e.g., in FIG. 8), secure network interface 128 (shown, e.g., in FIG. 8), secure enterprise mobile services application 125 (shown, e.g., in FIG. 13), virtual machine #2 secure enterprise application environment 118 (shown, e.g., in FIG. 14), enterprise application secured hardware execution partition 106 (shown, e.g., in FIG. 15), device service usage monitor 119 (shown, e.g., in FIG. 17), service processor framework program 139 (shown, e.g., in FIG. 16), and/or service processor kernel program 138 (shown, e.g., in FIG. 16).

In some embodiments, service usage reconciliation function 158, or secure enterprise mobile services gateway/server 172, or another similar network function, is programmed to review traffic usage patterns of mobile device 110 for the purpose of determining if the device may have fallen into unauthorized hands or if the device secure enterprise communications and data management software may have been hacked or tampered with in a way that endangers enterprise security or causes the enterprise to be billed for usage that is not enterprise usage. For example, service usage reconciliation function 158 (e.g., or secure enterprise mobile services gateway/server 172) can be programmed to monitor “bulk” enterprise service usage for the enterprise device group and trigger a fraud detection alert for a device that exhibits enterprise usage that is higher than a pre-determined “normal” limit. As another example, service usage reconciliation function 158 can be programmed to monitor “bulk” enterprise service usage for the enterprise device group and trigger a fraud detection alert for a device that exhibits enterprise usage access patterns that are determined to be outside of “normal” limits. Examples of usage patterns can include usage as a function of time of day, duration of usage, usage above a certain limit for a subset of service usage activities, and/or usage above a certain limit for all service usage activities.

In some embodiments, enterprise service design center 194 is configured to receive or accept a specification for an access network service usage limit (e.g., a service amount in minutes, bytes, or cost) for a service usage activity (such as a data service, a voice service, a text service, a roaming service, or a more detailed classification of a data service, such as one or more websites or one or more device applications), and the service usage limit is applied to one or more devices 110 or device groups (or users or user groups) managed by enterprise service design center 194. In some embodiments, enterprise service design center 194 is further configured to receive service usage records for device 110, which is managed by enterprise service design center 194, from a network element configured to monitor and report device 110 service usage (e.g., carrier usage accounting server 154, enterprise firewall/security gateway 171, or another network element), and when the usage limit is reached, to generate a service usage notification message. In some embodiments, enterprise service design center 194 is configured to deliver the service usage notification message to enterprise service design center UI 196. In some embodiments, enterprise service design center 194 is configured to deliver the service usage notification message to a software application of device 110 (e.g., service processor framework program 139 or user data app 111) for presentation to the device user through a user interface of device 110.

In some embodiments, enterprise service design center 194 is configured to receive or accept a specification for an access network service notification event consisting of a network access pattern achieved or attempted by device 110 that belongs to a device group (or user group) managed by enterprise service design center 194, wherein the network access pattern is access attempted or achieved by one or more pre-defined device applications, or access attempted or achieved by device 110 to one or more network destinations, websites or network servers. In some embodiments, enterprise service design center 194 is further configured to receive service usage records for device 110, which is managed by enterprise service design center 194, from a network element configured to monitor and report device 110 service usage (e.g., carrier usage accounting server 154, enterprise firewall/security gateway 171, or another network element), and when the service usage indicates that the network access pattern has occurred, enterprise service design center 194 is further configured to send a notification message to enterprise service design center UI 196.

Carrier Managed Billing Allocation with Service Usage Monitoring in Carrier Network and Enterprise Firewall/Gateway

FIG. 2 illustrates a functional diagram of another network architecture 101 for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. Network architecture 101 of FIG. 2 is similar to network architecture 100 of FIG. 1, except that in network architecture 101 of FIG. 2, service usage reconciliation function 158 receives service usage information from enterprise firewall/secure gateway 171 in addition to carrier gateway/home agent 152. This allows for various techniques that augment the capabilities of carrier gateway/home agent 152. For example, in networks in which it is impractical or infeasible for carrier gateway/home agent 152 to keep track of the service usage accounting allocation between the enterprise service policy set and consumer services for the devices in the device group, service usage reconciliation function 158 can receive total device service usage from carrier gateway/home agent 152, and receive the enterprise service usage from enterprise firewall/secure gateway 171. With this information, service usage reconciliation service usage function 158 can perform the allocation between enterprise service usage and consumer service usage without any detailed service usage reports from carrier gateway/home agent 152.

There are several reasons that the carrier network may not support numerous enterprise service customers with an enterprise/consumer allocation architecture that requires carrier gateway/home agent 152 to perform the necessary traffic classification or service usage classification as in the FIG. 1 embodiment. For example, these reasons can include: (i) carrier gateway/home agent 152 does not have the detailed service usage classification capability (e.g., deep packet inspection function(s)) required to allocate service usage between the enterprise service policy set and consumer services for the devices in the device group, (ii) carrier gateway/home agent 152 is capable of performing the service monitoring required but can only do it for a limited number of devices (e.g., scaling issues), and/or (iii) there are too many device groups being managed by enterprise partners of the carrier creating a situation where the number of specialized profiles that must be supported by carrier gateway/home agent 152 is larger than can be accommodated by the profile management capacity of the gateway system (e.g., scaling issues). As would now be apparent to those of ordinary skill in the art in view of the embodiments described herein, there are other reasons that can make it advantageous to provide the enterprise service usage from the enterprise network.

In some embodiments, provisioning with the service design centers and UIs for the embodiment shown in FIG. 2 is similar to that of FIG. 1. In some embodiments, the billing allocation capabilities of the two embodiments are similar if carrier gateway/home agent 152 is fully capable of differentiating service usage between the enterprise service policy set and the consumer services, but if not, then as discussed above, the billing allocation capabilities of the FIG. 2 embodiment can be preferable in such environments.

Because the enterprise service usage is monitored by the enterprise network elements in the embodiments depicted in FIG. 2, various service accounting or billing policies are available to the enterprise or carrier. For example, the amount of service usage resulting from enterprise services that occur during roaming conditions can be accounted for even when the carrier network does not receive detailed classification of service usage from roaming network partners. The business rules programmed into service usage reconciliation function 158 that are determined by the enterprise service activity policy set can break-out enterprise-service-related roaming charges separately from consumer-service-related roaming charges so that the enterprise-service-related roaming charges are sponsored or paid by the enterprise and consumer roaming service usage activities are not subsidized or are only partially subsidized. In addition, in some embodiments, secure enterprise mobile services gateway/server 172 includes the capability to determine if device 110 is roaming so that the access control policies specified in the enterprise service activity policy set can include modification or denial of access to enterprise network 170 services allowed by enterprise firewall/secure gateway 171 or secure enterprise mobile services gateway/server 172 during roaming conditions even though the access is not controlled by the carrier home network.

In some embodiments, an active network detection function is included on the device to assist the network policy enforcement elements to determine the type of network the device is connected to or to determine if the device is on a home or roaming network, as described herein. For example, the service usage policy allowances provided by the enterprise service activity policy set can be programmed so that the allowances change depending on the availability of a particular network or set of networks, the time of day, the congestion state of a network, or the current cost of service on the network. For example, if the carrier home network is not available and only a roaming network is available, the allowance may be decreased or removed. As another example, if a certain network type is not available but another network type is (e.g., 2G is available instead of 3G or 3G is available instead of 4G), then the allocation can be reduced. As yet another example, if a variable charging policy is in place with the carrier for access when the network is busy or during certain times of day, then the enterprise sponsored allowance can be reduced during times of higher charging.

Enterprise Managed Billing Allocation with Service Usage Monitoring in Carrier Network and Enterprise Firewall/Gateway

FIG. 3 illustrates a functional diagram of another network architecture 102 for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. Network architecture 102 of FIG. 3 is similar to network architecture 101 of FIG. 2, except that in network architecture 102 of FIG. 3, service usage reconciliation function 158 receives overall device service usage information from carrier usage accounting server 154 and also receives enterprise device service usage information from enterprise firewall/secure gateway 171. In some embodiments, there is no interaction between the provisioning of the carrier network and the provisioning of the enterprise network, and it is assumed that service usage reconciliation function 158 and enterprise usage accounting server 159 are both under the control of the enterprise administrator. This approach allows for various techniques that provide for enterprise allocation of consumer service usage and enterprise service usage without the need to interface to the carrier network other than to get the overall usage summary. For example, service usage reconciliation function 158 can receive total or “bulk” usage from carrier usage accounting server 154, receive enterprise service usage from enterprise firewall/secure gateway 171, and determine the amount of consumer service usage, enterprise service usage, and/or an enterprise service usage credit.

In some embodiments, provisioning with the service design centers and UIs for the embodiment shown in FIG. 3 is similar to that of FIG. 1 except that no provisioning of enterprise service parameters is required in the carrier network. The billing allocation capabilities are also similar if carrier gateway/home agent 152 is fully capable of differentiating service usage between the enterprise service policy set and the consumer services, but if not, then as discussed above, the billing allocation capabilities of the FIG. 3 embodiment can be preferable in such environments. For example, using network architecture 102, the enterprise can deal directly with its employees without the need to bring the carrier into the consumer-versus-enterprise allocation process. As an example, the enterprise could have a policy in which consumers purchase their own mobile device services and then get credit for enterprise mobile device services at the end of each billing period. This credit can be provided back to the employee in the form of an expense reimbursement or an increase in their next paycheck.

Enterprise Usage Credit with Service Usage Monitoring in Enterprise Firewall/Gateway

FIG. 4 illustrates a functional diagram of another network architecture 103 for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. Network architecture 103 of FIG. 4 is similar to network architecture 102 of FIG. 3, except that in network architecture 103 of FIG. 4, service usage reconciliation server function 158 receives no overall device service usage information from the carrier network. As shown in FIG. 4, the source of service usage information is enterprise network 170 (e.g., via the enterprise firewall/secure gateway 171). In some embodiments, there is no interaction between the provisioning of the carrier network and the provisioning of the enterprise network, and it is assumed that service usage reconciliation function 158 and enterprise usage accounting server 159 could both be under the control of the enterprise administrator. For example, network architecture 103 of FIG. 4 can be less dependent on the carrier than network architecture 102 of FIG. 3 in that no billing information feed is provided. Using various techniques described herein, an enterprise service usage credit can be determined, and the determined enterprise service usage credit can be reimbursed to the device user.

Carrier Managed Billing Allocation with Service Usage Monitoring in Carrier Gateway/Home Agent and Enterprise Mobile Services Gateway Server

FIG. 5 illustrates a functional diagram of another network architecture 200 for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. Network architecture 200 of FIG. 5 is similar to network architecture 101 of FIG. 2, except that in network architecture 200 of FIG. 5, secure enterprise mobile services gateway/server 172 includes mobile server usage monitor 179, and the enterprise service usage reports from this function are sent to service usage reconciliation function 158 instead of usage reports being sent from enterprise firewall/secure gateway 171. In some embodiments, various specialized needs of monitoring, recording, and reporting enterprise service usage are confined to the special-purpose secure enterprise mobile services gateway/server 172 rather than requiring the often more general-purpose enterprise firewall/secure gateway 171 to perform these functions.

Enterprise Managed Billing Allocation with Service Usage Monitoring in Carrier Network and Enterprise Mobile Services Gateway Server

FIG. 6 illustrates a functional diagram of another network architecture 201 for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. Network architecture 201 of FIG. 6 is similar to network architecture 102 of FIG. 3, except that in network architecture 201 of FIG. 6, secure enterprise mobile services gateway/server 172 includes mobile server usage monitor 179, and the enterprise service usage reports from this function are sent to service usage reconciliation function 158 instead of usage reports being sent from enterprise firewall/secure gateway 171. For example, this approach allows for the specialized needs of monitoring, recording, and reporting enterprise service usage to be performed by the special-purpose secure enterprise mobile services gateway/server 172 rather than requiring the often more general-purpose enterprise firewall/secure gateway 171 to perform such functions.

Enterprise Usage Credit with Service Usage Monitoring in Enterprise Mobile Services Gateway Server

FIG. 7 illustrates a functional diagram of another network architecture 202 for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. Network architecture 202 of FIG. 7 is similar to network architecture 103 of FIG. 4, except that in network architecture 202 of FIG. 7, secure enterprise mobile services gateway/server 172 includes mobile server usage counter 179, and the enterprise service usage reports from this function are sent to service usage reconciliation function 158 instead of usage reports being sent from enterprise firewall/secure gateway 171. For example, this approach allows for the specialized needs of monitoring, recording and reporting enterprise service usage to be performed by the special-purpose secure enterprise mobile services gateway/server 172 rather than requiring the often more general-purpose enterprise firewall/secure gateway 171 to perform such functions.

Carrier Managed Billing Allocation with Device Mobile Enterprise Services Application Environment and Service Usage Monitoring in Carrier Network

FIG. 8 illustrates a functional diagram of another network architecture 300 for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. As shown, secure mobile enterprise application environment 120 and secure network interface 128 within secure mobile enterprise application environment 120 are included in device 110. Also, server secure network interface 127 is included in secure enterprise mobile services gateway/server 172. In some embodiments, secure mobile enterprise application environment 120 protects sensitive enterprise information that is stored on device 110 (e.g., email text and downloads, calendar information, contacts, intranet data, or any other enterprise data) and provides a secure communication channel function to allow for authentication with server secure network interface 127 on secure enterprise mobile services gateway/server 172. As also shown, a user services application environment in device 110 includes various user applications, such as user data application 111 and user voice application 112.

In some embodiments, provisioning of the various network architecture elements to facilitate the allocation between enterprise service usage accounting or billing and consumer service usage accounting or billing is established as follows. The device portion of secure network interface 128 and the enterprise server portion of server secure network interface 127 are provisioned with connection “E.” In some embodiments, this provisioning operation with the connection labeled “E” includes programming information for secure network interface 128 to direct enterprise network 170 access traffic associated with application functions running in secure mobile enterprise application environment 120 to enterprise network 170 destinations that are to be sponsored (and, in some embodiments, possibly intermediate network routes) according to the enterprise services policy set, including, for example, the addresses (e.g., IP, IP/port or other higher layer address identifiers) of secure enterprise mobile services gateway/server 172 or enterprise intranet servers 180. In some embodiments, the provisioning operation designated with the connection label “E” also establishes the parameters required for the secure communication of information between secure network interface 128 and server secure network interface 127. In some embodiments, this provisioning step sets up the policies for the authentication process, data encryption, and cryptographic key exchange processes take place to establish secure communication between secure mobile enterprise application environment 120 and secure enterprise services gateway/server 172.

In some embodiments, the enterprise network destinations that are to be sponsored according to the enterprise services policy set identified by provisioning connection “E” are also communicated to carrier service design center 190. For example, this allows carrier service design center 190 to determine and transmit the proper provisioning information to establish the access control policies or service usage accounting policies for these aspects of the enterprise services policy set. Carrier service design center provisioning connections “A” communicate the provisioning information (programming) to carrier gateway/home agent 152. Carrier service design center provisioning connections “B” communicate the provisioning information (programming) to service usage reconciliation function 158.

In some embodiments, the provisioning operation associated with the provisioning connection label “C” provisions enterprise firewall/secure gateway 171 to admit devices 110 with device credentials or application credentials that belong to the desired enterprise services device group associated with the enterprise service policy set. In some embodiments, the provisioning information labeled as “C” includes enterprise network 170 destinations that are to be sponsored (and, in some embodiments, possibly intermediate network routes) according to the enterprise services policy set. In some embodiments, the provisioning information labeled as “C” includes only the network destinations for secure enterprise mobile services gateway/server 172, and devices 110 are not allowed access to other parts of enterprise network 170.

In some embodiments, network architecture 300 for providing enterprise and consumer billing allocation for wireless communication device service usage activities includes executing an enterprise application as a secure enterprise data application 124 in secure mobile enterprise application environment 120 of device 110 in which the secure applications are in network communication (e.g., secure network communication, such as via a virtual private network (VPN) or other secure network communication techniques) with secure enterprise mobile services gateway/server 172 (e.g., executing an enterprise server side of the enterprise authorized/sponsored applications, such as an enterprise email server, an enterprise calendar server, an enterprise contacts server, and/or an enterprise network access server) of the enterprise. In some embodiments, the secure enterprise mobile services gateway/server 172 performs application monitoring that includes counting application service usage (e.g., bytes used in communicating with the device's execution of secure enterprise application 124). In some embodiments, secure enterprise mobile services gateway/server 172 performs application monitoring that further includes classifying application service usage (e.g., classifying secure enterprise application 124 by application/service usage activity such as based on application name or using signed code/hash techniques, by time of day/day of week, enterprise server, destinations, enterprise intranet, and/or other factors).

Carrier Managed Billing Allocation with Device Mobile Enterprise Services Application Environment and Mobile Services Gateway Server with Service Usage Monitoring in Carrier Network

FIG. 9 illustrates a functional diagram of another network architecture 301 for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. Network architecture 301 of FIG. 9 is similar to network architecture 300 of FIG. 8, except that in network architecture 301 of FIG. 9, secure enterprise mobile services gateway/server 172 is located between the Internet 160 and enterprise network 170. For example, this approach allows for server secure network interface 127 of secure enterprise mobile services gateway/server 172 to restrict access to enterprise network 170 and enterprise intranet servers 180 based on device authentication and/or various other security techniques (e.g., secure access, authentication, and/or communication techniques), as would be apparent to one of ordinary skill in the art in view of the various embodiments described herein.

Carrier Managed Billing Allocation with Device Mobile Enterprise Services Application Environment and Mobile Services Gateway Server with Service Usage Monitoring in Carrier Network and Mobile Services Gateway Server

FIG. 10 illustrates a functional diagram of another network architecture 302 for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. Network architecture 302 of FIG. 10 is similar to network architecture 301 of FIG. 9, except that in network architecture 302 of FIG. 10, secure enterprise mobile services gateway/server 172 includes mobile service usage monitor 179 that reports enterprise service usage to the service usage reconciliation function 158. In some embodiments, various specialized needs of monitoring, recording, and reporting enterprise service usage are confined to the special-purpose enterprise mobile services gateway/server 172 rather than requiring the often more general-purpose enterprise firewall/secure gateway 171 and/or other network elements/functions to perform such functions.

Enterprise Managed Billing Allocation with Device Mobile Enterprise Services Application Environment and Mobile Services Gateway Server with Service Usage Monitoring in Mobile Services Gateway Server

FIG. 11 illustrates a functional diagram of network architecture 303 for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. Network architecture 303 of FIG. 11 is similar to network architecture 302 of FIG. 10, except that network architecture 303 of FIG. 11 includes another carrier usage accounting server 154B that reports service usage to service usage reconciliation function 158. In some embodiments, carrier usage accounting server 154B receives overall or bulk service usage data from carrier gateway/home agent 152 and forwards such information to service usage reconciliation function 158. Service usage reconciliation function 158 reconciles the overall or bulk service usage received from carrier accounting server 154B and the enterprise service usage received from mobile server usage monitor 179 and provides such reconciled service usage information to carrier usage accounting server 154A.

Enterprise Usage Credit with Device Mobile Enterprise Services Application Environment and Mobile Services Gateway Server with Service Usage Monitoring in Mobile Services Gateway Server

FIG. 12 illustrates a functional diagram of network architecture 304 for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. Network architecture 304 of FIG. 12 is similar to network architecture 303 of FIG. 11, except that in network architecture 304 of FIG. 12, the only service usage reported to service usage reconciliation function 158 is the enterprise service usage received from mobile server usage monitor 179. In some embodiments, service usage reconciliation function 158 reconciles the enterprise service usage received from mobile server usage monitor 179 and provides such reconciled service usage information to carrier usage accounting server 154, which generates enterprise service usage record(s) 156.

Device Configurations without Service Usage Monitoring and Reporting

FIG. 13 illustrates a functional diagram of a secure device application architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. As shown, device 110 includes an operating system application space 131, operating system lower layers 130 including network stack 121, and access modem (e.g., wireless modem) 129. As also shown, operating system application space 131 includes various user applications, such as user data application 111 and user voice application 119, and service usage monitor 119. Operating system application space 131 also includes secure enterprise mobile services application 125, which includes various enterprise applications, such as email, synchronization, contacts, calendar communications, and intranet. Secure enterprise mobile services application 125 also includes secure network interface 128 (e.g., for securely communicating with an enterprise network).

FIG. 14 illustrates a functional diagram of another secure device virtual machine architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. FIG. 14 is similar to FIG. 13, except that in FIG. 14 the user applications are executed/stored within virtual machine (VM) #1 consumer application environment 117, and secure enterprise mobile services application 125 is included within virtual machine (VM) #2 secure enterprise application environment 118. Device 110 also includes virtual machine operating system 115 that includes virtual OS instantiation #1117A for VM #1 consumer application environment 117 and virtual OS instantiation #2118A for VM #2 secure enterprise application environment 118. As also shown, virtual machine operating system 115 includes virtual machine OS network stack 116.

FIG. 15 illustrates a functional diagram of another secure device hardware execution partition architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. FIG. 15 is similar to FIG. 14, except that in FIG. 15 hardware partitions are provided instead of virtual partitions. As shown, the user applications are executed/stored within user application secured hardware execution partition 105 and secure enterprise mobile services application 125 is included within enterprise application secured hardware execution partition 106. Device 110 also includes secured hardware partition for OS 115 that includes secure hardware partition manager #1107 for user application secured hardware execution partition 105 and secure hardware partition manager #2108 for enterprise application secured hardware execution partition 106. As also shown, secured hardware partition for OS 115 includes OS network stack 116.

FIG. 16 illustrates a functional diagram of another secure device service processor architecture for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. As similarly described herein with respect to various embodiments, the device architecture of FIG. 16 includes service processor framework program 139 (e.g., framework space agent/function) and network stack framework components 137 in operating system framework space 133, and service processor kernel program 138 (e.g., kernel space agent/function) and network stack kernel components 135 in operating system kernel space 132. In some embodiments, the service processor functions provide a user interface function to communicate to a user of device 110 whether or not a service usage activity is an approved/authorized service usage activity, or whether it is a disallowed service usage activity for device 110 (e.g., the enterprise has disallowed the usage of device 110 for such service usage activities, such as online gaming and/or certain other online activities or certain long distance calling or voice usage during certain days, such as weekends) or whether such would/will be charged/billed to the user as a consumer under the user's consumer plan. In some embodiments, the service processor functions provide a user interface function to communicate to a user of device 110 an associated cost of certain service usage activities allocated to consumer service usage. In some embodiments, the service processor functions provide a user interface function to communicate to a user of device 110 an associated credit of certain service usage activities allocated to enterprise service usage. In some embodiments, the service processor functions provide a user interface function to communicate to a user of device 110 various other information as described herein with respect to providing an enterprise and consumer allocation for service usage activities. In some embodiments, the service processor shown in FIG. 16 communicates with a service controller, such as described herein with respect to various embodiments.

Carrier Managed Billing Allocation with Device Mobile Enterprise Services Application Environment and Mobile Services Gateway Server with Service Usage Monitoring in Carrier Network and on Device

FIG. 17 illustrates a functional diagram of another network architecture 400 for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. Network architecture 400 of FIG. 17 is similar to network architecture 302 of FIG. 10, except that as shown in FIG. 17, device 110 also includes service usage monitor 119 (e.g., agent/function) in secure mobile enterprise application environment 120. In some embodiments, service usage monitor 119 performs application monitoring that includes counting application service usage for secure data application 124 and secure voice application 126 (and, in some embodiments, for also counting application service usage for user applications that are not enterprise or secure enterprise applications 124 or 126). In some embodiments, counting application service usage includes counting bytes or network connection time used in communicating via carrier access network 150 during the device's execution of monitored data applications. In some embodiments, counting application service usage includes counting voice network connection time used in communicating via carrier access network 150 during the device's execution of monitored voice applications. In some embodiments, service usage monitor 119 performs application monitoring that further includes classifying application service usage for secure enterprise applications 124, 126 (e.g., classifying various secure enterprise applications 124, 126 and in some embodiments, including ambient services classification/determination, by application/service usage activity such as based on application name or using signed code/hash techniques, by time of day/day of week, enterprise server, destinations, enterprise intranet, and/or other factors).

In some embodiments, carrier usage accounting server 154 communicates (e.g., using secure communication techniques) with service usage monitor 119 to mediate billing/charging and credit reports, for example, using the various approaches and techniques as described herein.

In some embodiments, service usage monitor 119 and/or another function/agent executed in secure mobile enterprise application environment 120 of device 110 blocks user access for non-enterprise activities that the user has not agreed to pay for.

Because the enterprise service usage is monitored by the device network elements in the embodiments depicted in FIG. 17, various service accounting or billing policies are available to the enterprise or carrier. For example, the amount of service usage resulting from enterprise services that occur during roaming conditions may be accounted for even when the carrier network does not receive detailed classification of service usage from roaming network partners. The business rules programmed into service usage reconciliation function 158 that are determined by the enterprise service activity policy set can break-out enterprise service related roaming charges separate from consumer service related roaming charges. In addition, in some embodiments, the device secure mobile enterprise environment includes an access control function so that the access control policies specified in the enterprise service activity policy set can be enforced on roaming networks that have access that is not controlled by the carrier home network.

For example, the allowances provided by the enterprise service activity policy set can be programmed so that the allowances change depending on the availability of a particular network or set of networks, the time of day, the congestion state of a network, or the current cost of service on the network. As another example, if the carrier home network is not available and only a roaming network is available, the allowance can be decreased or removed. As yet another example, if a certain network type is not available but another network type is (e.g., 2G is available instead of 3G or 3G is available instead of 4G), then the allocation can be reduced. As yet a further example, if a variable charging policy is in place with the carrier for access when the network is busy or during certain times of day, then the enterprise sponsored allowance can be reduced during times of higher charging. As described herein, in some embodiments, an active network detection function can be included on the device to assist the network policy enforcement to determine the type of network the device is connected to or to determine if the device is on a home or roaming network. As also described herein, in some embodiments, a network busy state monitor function can be included on the device to assist the network policy enforcement to determine the network busy state or state of network congestion.

FIG. 18 illustrates a functional diagram of another network architecture 401 for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. Network architecture 401 of FIG. 18 is similar to network architecture 400 of FIG. 17, except that in network architecture 401 of FIG. 18, secure enterprise mobile services gateway/server 172 includes mobile server usage counter 179, and the enterprise service usage reports from this function are sent to service usage reconciliation function 158. In some embodiments, various specialized needs of monitoring, recording, and reporting enterprise service usage are confined to the special-purpose secure enterprise mobile services gateway/server 172.

Enterprise Managed Billing Allocation with Device Mobile Enterprise Services Application Environment and Mobile Services Gateway Server with Service Usage Monitoring on Device and in Enterprise Mobile Services Gateway Server

FIG. 19 illustrates a functional diagram of another network architecture 402 for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. Network architecture 402 of FIG. 19 is similar to network architecture 401 of FIG. 18, except that network architecture 402 of FIG. 19 does not include the service usage feed from carrier gateway/home agent 152, and service usage reconciliation function 158 relies solely on a device service usage feed from device 110 usage monitors 119 and secure enterprise mobile services gateway/server 172 mobile service usage monitor 179. In some embodiments, service usage reconciliation function 158 and enterprise service usage accounting server 159 are under the control of the enterprise or the carrier. For example, an enterprise entity can establish enterprise service and consumer service usage allocation accounting without the need to tie into the carrier network for usage feeds and usage accounting. Using various techniques described herein, an enterprise service usage credit can be determined, and the determined enterprise service usage credit can be reimbursed to the device user.

Enterprise Managed Billing Allocation with Device Mobile Enterprise Services Application Environment and Mobile Services Gateway Server with Service Usage Monitoring on Device

FIG. 20 illustrates a functional diagram of another network architecture 403 for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. Network architecture 403 of FIG. 20 is similar to network architecture 402 of FIG. 19, except that in network architecture 403 of FIG. 20, service usage reconciliation function 158 receives feeds from device 110 service usage monitors 119 and there is no feed from the secure enterprise mobile services gateway server.

Enterprise Usage Credit with Device Mobile Enterprise Services Application Environment and Mobile Services Gateway Server with Service Usage Monitoring on Device and in Enterprise Mobile Services Gateway Server

FIG. 21 illustrates a functional diagram of another network architecture 404 for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. Network architecture 404 of FIG. 21 is similar to network architecture 402 of FIG. 19, except that in network architecture 404 of FIG. 21, there is no service usage monitor function 119 in user services application environment 122 providing service usage reports/information to service usage reconciliation function 158, and enterprise usage accounting server 159 only generates enterprise usage records 156.

Enterprise Usage Credit with Device Mobile Enterprise Services Application Environment and Mobile Services Gateway Server with Usage Monitoring on Device

FIG. 22 illustrates a functional diagram of another network architecture 405 for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. Network architecture 405 of FIG. 22 is similar to network architecture 404 of FIG. 21, except that network architecture 405 of FIG. 22 does not include mobile server usage monitor 179 providing enterprise service usage reports/information to service usage reconciliation function 158.

Device Configurations with Service Usage Monitoring and Reporting

In some embodiments, secure enterprise mobile services application 125 and network stack 121 can be implemented in access modem 129, as described below with respect to FIGS. 23 through 26.

FIG. 23 illustrates a functional diagram of a secure device application architecture with device-based service usage monitoring (and in some embodiments, access control) for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. FIG. 23 is similar to FIG. 13 except that in FIG. 23 usage monitor 119 is provided as shown, and secure enterprise mobile services application 125 and network stack 121 can be implemented in access modem 129 as also shown.

FIG. 24 illustrates a functional diagram of a secure device virtual machine architecture with device-based service usage monitoring (and in some embodiments, access control) for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. FIG. 24 is similar to FIG. 14 except that in FIG. 24, usage monitor 119 is provided as shown, and secure enterprise mobile services application 125 and virtual machine OS network stack 116 can be implemented in access modem 129 as also shown.

FIG. 25 illustrates a functional diagram of a secure device hardware execution partition architecture with device-based service usage monitoring (and in some embodiments access control) for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. FIG. 25 is similar to FIG. 15 except that in FIG. 25 usage monitor 119 is provided as shown, and secure enterprise mobile services application 125 and virtual machine OS network stack 116 can be implemented in access modem 129 as also shown.

FIG. 26 illustrates a functional diagram of a secure device service processor architecture with device based service usage monitoring (and in some embodiments, access control) for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. FIG. 263 is similar to FIG. 16 except that in FIG. 26 usage monitor 119 is provided as shown, and secure enterprise mobile services application 125, service processor framework 139, and service processor kernel program 138, can be implemented in the access modem 129 as also shown.

In some embodiments, service processor framework program 139 (or service processor kernel program 138) interacts with network stack framework components 137 or network stack kernel components 135 to inspect traffic for service usage classification and service policy enforcement (e.g., access control policy enforcement, traffic control policy enforcement, service usage accounting, charging policy enforcement, or service notification policy enforcement) purposes. In some embodiments, one or more of network stack framework components 137 and network stack kernel components 135 provides classification information on one or more traffic flows to service processor framework program 139 (or service processor kernel program 138). In some embodiments, service processor framework program 139 (or service processor kernel program 138) seeks to match the classification information to one or more classification parameters contained in the service policy definitions in order to determine the service policy enforcement actions that may be required for a traffic flow. In some embodiments, a traffic flow is a flow of data packets. In some embodiments, a traffic flow is a flow of one or more data packets that are associated with a device application, the association of a traffic flow to a device application being identified by network stack framework components 137 or network stack kernel components 135 or service processor framework program 139 (or service processor kernel program 138). In some embodiments, the service usage classification determines that the traffic flow is associated with a combination of one or more of: a device application, a network destination, a traffic type, a content type, a QoS level, a roaming network, a home network.

In some embodiments, the association of traffic flow to a specific device application is used to determine a service policy enforcement action that is dependent on the specific device application. In some embodiments, a specific device application identifier (e.g., an application name, application signature, application hash or application certificate) forms an application credential that is used to index a service policy enforcement action that is intended to be implemented following a service usage activity or attempted service usage activity by the specific device application. In some embodiments, a specific device application is verified as consistent with an application credential in order to ensure that an application service policy enforcement action intended to be applied to the specific device application is applied to the correct application. In some embodiments, the verification that a specific application is consistent with an application credential associated with a service policy enforcement action is performed in service processor framework program 139 (or service processor kernel program 138) to ensure that ensure that an application service policy enforcement action intended to be applied to the specific device application is applied to the correct application. In some embodiments, the verification that a specific application is consistent with an application credential associated with a service policy enforcement action is performed in network stack framework components 137 or network stack kernel components 135, and service processor framework program 139 (or service processor kernel program 138) ascertains the application credential verification to ensure that ensure that an application service policy enforcement action intended to be applied to the specific device application is applied to the correct application.

In some embodiments, the association of traffic flow to a specific device application is used to determine a service policy enforcement action that is dependent on the specific device application, and service processor framework program 139 (or service processor kernel program 138) instructs network stack framework components 137 or network stack kernel components 135 to implement the service policy enforcement action on the traffic flow associated with the specific device application. In some embodiments, the association of traffic flow to a specific device application is used to determine a service policy enforcement action that is dependent on the specific device application, and service processor framework program 139 (or service processor kernel program 138) implements the service policy enforcement action. In some embodiments, a traffic flow is buffered pending classification (e.g., buffered in one or more of network stack framework components 137, network stack kernel components 135, service processor framework program 139, or service processor kernel program 138). In some embodiments, upon classification of the traffic flow (e.g., determination of an association of the traffic flow to a specific device application), a service policy enforcement action that is dependent on the specific device application is determined by service processor framework program 139 (or service processor kernel program 138) and implemented in one or more of network stack framework components 137, network stack kernel components 135, service processor framework program 139, and service processor kernel program 138. In some embodiments, the service policy enforcement action for the traffic flow is implemented in service processor framework program 139 (or service processor kernel program 138). In some embodiments, service processor framework program 139 (or service processor kernel program 138) instructs a device UI program that displays a device service notification (e.g., a service usage notification, a service plan offer notification, or an indication of a service usage event or attempted service usage event that requires a user notification) to implement the service policy enforcement action for the traffic flow. In some embodiments, service processor framework program 139 (or service processor kernel program 138) instructs a service usage monitor (e.g., accounting traffic to bulk classification or a more detailed classification of service usage) to implement the service policy enforcement action for the traffic flow.

In some embodiments, the network destination of a traffic flow is used to determine if a service policy enforcement action that is dependent on a specific network destination should be applied to the traffic flow. In some embodiments, a traffic flow is inspected by network stack framework components 137 or network stack kernel components 135, and one or more traffic characteristics (e.g., an address, a socket/flow tuple, a layer-7 packet information, or a packet header string) are passed to service processor framework program 139 (or service processor kernel program 138), wherein the one or more traffic characteristics are matched against one or more classification parameters contained in a service policy definition, and if a match is present then a service policy enforcement action is implemented for the traffic flow. In some embodiments, a traffic flow is inspected by service processor framework program 139 (or service processor kernel program 138), and one or more traffic characteristics (e.g., an address, a socket/flow tuple, a layer-7 packet information, or a packet header string) are matched against one or more classification parameters contained in a service policy definition, and if a match is present then a service policy enforcement action is implemented for the traffic flow. In some embodiments, the service policy enforcement action for the traffic flow is implemented in service processor framework program 139 (or service processor kernel program 138). In some embodiments, service processor framework program 139 (or service processor kernel program 138) instructs network stack framework components 137 or network stack kernel components 135 to implement the service policy enforcement action for the traffic flow. In some embodiments, the service policy enforcement action for the traffic flow is implemented by a device UI program that displays a device service notification (e.g., a service usage notification, a service plan offer notification, or an indication of a service usage event or attempted service usage event that requires a user notification). In some embodiments, the service policy enforcement action for the traffic flow is implemented by a service usage monitor (e.g., accounting traffic to bulk classification or a more detailed classification of service usage).

In some embodiments, an enterprise manger can define or select service plan policies that confine enterprise-sponsored access services to a pre-defined list of device applications. For example, an enterprise manager might choose to define or select a service plan wherein only corporate applications may be accessed (e.g., email, contacts, intranet services, text, and/or voice). In such embodiments, enterprise service design user interface 196 may be used by the enterprise manager to define or select the allowable applications that are to have access. In some embodiments, an enterprise access manager may define or select a different set of applications to be accessible when device 110 is roaming than when device 110 is on a home network or on a WiFi network. In some embodiments, an enterprise manager may define or select a set of applications that are to be not allowed access when a device is on a certain network (e.g., a roaming network). For example, many modern smart phone, tablet, and laptop operating systems have background services that have the potential to incur large roaming charges during roaming conditions (e.g., Google Android “gallery” functions that share device data with the Google network, Microsoft “system” functions that do the same, software update programs, etc.). In such cases, enterprise service design center 194 may be used to specify the device applications that are not allowed to access the network during certain network conditions.

In some embodiments, the identification and network access control for a device application is performed with a device software program or agent (e.g., service processor framework program 139 or service processor kernel program 138), and enterprise service design center 194 programs the device agent with the application identification parameters and associated access policies. In some embodiments, the device agent identifies the application using an application name, certificate, signature, or hash for an application running on the device and a policy instruction stored on the device.

In some embodiments, the identification and network access control for a device application is performed with one or more network access policy enforcement elements (e.g., carrier gateway/home agent 152, carrier usage accounting server 154, enterprise firewall/security gateway 171), and enterprise service design center 194 causes the one or more network access policy enforcement elements to be provisioned with the application identification parameters and associated access policies. In some embodiments, the one or more network access policy enforcement elements identify an application by observing the traffic headers inserted by the application. In some embodiments, the one or more network access policy enforcement elements identify an application by observing the network destinations or destination patterns accessed by the application. In some embodiments, the one or more network access policy enforcement elements identify an application by routing or tunneling the application traffic to one or more network gateways or servers associated with the application (e.g., APN routes, dedicated application addressing, or a device agent that steers the application traffic to a server). In some embodiments, the device assists in this routing or tunneling with a device agent that is programmed to route or re-direct the traffic for an application.

In some embodiments, an enterprise manger can define or select service plan policies that confine enterprise-sponsored access services to a pre-defined list of network destinations, servers, or resources. For example, an enterprise manager might choose to define or select a service plan wherein only corporate network destinations may be accessed (e.g., email server, contacts server, intranet servers, text service servers, and VOIP servers). In some embodiments, enterprise service design center interface 196 may be used by an enterprise manager to define or select the allowable network destinations that device 110 may access. In some embodiments, the enterprise access manager may define or select a different set of network destinations when device 110 is roaming than when device 110 is on a home network or on a WiFi network. In some embodiments, an enterprise manager may define or select a set of network destinations that device 110 cannot access when device 110 is on a certain network (e.g., a roaming network). For example, many websites and enterprise services exhibit network access service usage behavior that can incur large roaming charges during roaming conditions (e.g., software update websites or servers, contact database synchronization websites, email download synchronization websites, video conference websites, etc.). In such cases, enterprise service design center 194 may be used to specify the device applications, services, and/or websites that are not to be accessed or used during certain network connection conditions.

In some embodiments, a device agent identifies the network destination and applies the appropriate access policy by comparing traffic characteristics with pre-defined characteristics in the access policy instructions provisioned on device 110, and then applies the corresponding traffic control rule, and enterprise service design center 194 performs the provisioning of the device agent. In some embodiments, the identification and network access control for a network destination is performed with one or more network access policy enforcement elements (e.g., carrier gateway/home agent 152, carrier usage accounting server 154, enterprise firewall/security gateway 171) and enterprise service design center 194 performs the provisioning of the one or more network elements.

In some embodiments, enterprise service design center 194 is configured to receive or accept a specification for an access network service usage limit (e.g., a service amount in minutes, bytes, or cost) for a service usage activity (such as a data service, a voice service, a text service, a roaming service, or a more detailed classification of data service such as one or more websites or one or more device applications), and the service usage limit is applied to one or more devices 110 or device groups (or users or user groups) managed by enterprise service design center 194. In some embodiments, enterprise service design center 194 is further configured to receive service usage records for device 110, which is managed by enterprise service design center 194, from a device-based element that monitors and reports device 110 service usage (e.g., one or more device usage monitors 119, device service processor framework program 139, or service processor kernel program 138, network stack 134, or access modem 151), and when the usage limit is reached a service usage notification message is generated. In some embodiments, enterprise service design center 194 is configured to deliver the service usage notification message to enterprise service design center UI 196. In some embodiments, enterprise service design center 194 is configured to deliver the service usage notification message to a device 110 software application (e.g., service processor framework program 139 or user data app 111) for presentation to the device user via a user interface.

In some embodiments, enterprise service design center 194 is configured to receive or accept a specification for an access network service usage limit (e.g., a service amount in minutes, bytes, or cost) for a service usage activity (such as a data service, a voice service, a text service, a roaming service, or a more detailed classification of data service such as one or more websites or one or more device applications), and the service usage limit is applied to one or more devices 110 or device groups (or users or user groups) managed by enterprise service design center 194. In some embodiments, enterprise service design center 194 is further configured to receive service usage records for device 110, which is managed by the enterprise service design center 194, from a device-based element configured to monitor and report device 110 service usage (e.g., one or more device usage monitors 119, device service processor framework program 139 or service processor kernel program 138, network stack 134, or access modem 151), and when the usage limit is reached a restriction or limitation on further usage is applied by the service design center by provisioning one or more network elements responsible for enforcing network access policy (e.g., carrier gateway/home agent 152, carrier usage accounting server 154, enterprise firewall/security gateway 171). In some embodiments, enterprise service design center 194 is configured to send the user a notification message or a message to contact an enterprise manager.

In some embodiments, secure network interface 128 on device 110 is configured with a VPN device client function to securely communicate between one or more approved enterprise applications (e.g., enterprise data app 124, enterprise voice app 126, secure enterprise mobile services app 125) and a counterpart VPN function that secures access to enterprise network 170 (e.g., enterprise firewall/security gateway 171 or server secure network interface 127). In some embodiments, a device software application or agent (e.g., service processor framework program 139 or service processor kernel program 138, secure network interface 128, secure hardware partition manager 108) is configured to identify network access activity associated with individual applications and allow network access to one or more approved enterprise applications when a VPN device client function is in operation, or not allow network access to one or more approved enterprise applications when a VPN device client function is not in operation. In some embodiments, service design center 190 or enterprise service design center 194 is configured to provision a device 110 software application or agent (e.g., service processor framework program 139 or service processor kernel program 138, secure network interface 128, secure hardware partition manager 108) with application access policy rules to identify network access activity associated with individual applications and allow network access to one or more approved enterprise applications when a VPN device client function is in operation, or not allow network access to one or more approved enterprise applications when a VPN device client function is not in operation. In this manner, enterprise applications that might be subject to spoofing by network elements, websites, servers, or programs operating outside the secure enterprise environment are not placed in communication with such network elements.

In some embodiments, a device software application or agent (e.g., service processor framework program 139 or service processor kernel program 138, secure network interface 128, secure hardware partition manager 108) is configured to identify network access activity associated with individual applications and not allow network access to one or more non-approved applications when a VPN device client function is in operation, or allow network access to one or more non-approved applications when a VPN device client function is not in operation. In some embodiments, service design center 190 or enterprise service design center 194 is configured to provision a device 110 software application or agent (e.g., service processor framework program 139 or service processor kernel program 138, secure network interface 128, secure hardware partition manager 108) with application access policy rules to identify network access activity associated with individual applications and not allow network access to one or more non-approved applications when a VPN device client function is in operation, or allow network access to one or more enterprise applications when a VPN device client function is not in operation. In this manner, applications that might maliciously access enterprise network resources when the VPN is running are not permitted to do so.

In some embodiments, the application access policy rules are enforced by allowing or not allowing an application to access the network. In some embodiments, the application access policy rules are enforced by allowing or not allowing the application to run. In some embodiments, the identification of approved enterprise applications associated with traffic flows is confirmed or secured by identifying the application certificate and comparing it to an application signature or hash on the device. In some embodiments, the identity of an approved enterprise application is confirmed by inspecting an application certificate, signature or hash that is provided by service design center 190 or enterprise service design center 194.

In some embodiments, secure network interface 128 is configured with a split-tunnel VPN device client function, wherein an enterprise side of the split tunnel is configured to securely communicate between one or more enterprise applications (e.g., enterprise data app 124, enterprise voice app 126, secure enterprise mobile services app 125) and a counterpart VPN function that secures access to the enterprise network 170 (e.g., enterprise firewall/security gateway 171 or server secure network interface 127), and a consumer side of the split tunnel is configured to communicate without encryption for access network services provided to consumer applications on the device. In some embodiments, a device software application or agent (e.g. service processor framework program 139 or service processor kernel program 138, secure network interface 128, secure hardware partition manager 108) is configured to identify network access activity associated with individual applications and route or direct traffic associated with one or more enterprise applications to the enterprise side of the split VPN tunnel, and route or direct traffic associated with one or more consumer applications to the consumer side of the VPN tunnel. In some embodiments, service design center 190 or enterprise service design center 194 is configured to provision a device 110 software application or agent (e.g., service processor framework program 139 or service processor kernel program 138, secure network interface 128, secure hardware partition manager 108) with application access policy rules to identify network access activity associated with individual applications and specify which applications are to be routed or directed to the enterprise side of the VPN tunnel and which applications are to be routed or directed to the consumer side of the VPN tunnel. In some embodiments, the identification of applications associated with traffic flows is secured by identifying the application certificate and comparing it to an application signature or hash on the device. In some embodiments, the application certificate, signature or hash is provided by service design center 190 or enterprise service design center 194.

In some embodiments, the policy rules only enable secure applications on device 110 to access enterprise data. In some embodiments, an enterprise manager sets policy rules that do not allow secure applications on device 110 to upload data to unsecure destinations.

In some embodiments, service design center 190 is configured to provide enterprise service design center 194. In some embodiments, enterprise service design center 194 comprises a policy management system configured to select a set of access network policies to be enforced for one or more device groups (or user groups) where the set of access network policies consists of a subset of the full set of access network policies capable of being enforced by the access network policy enforcement elements. In some embodiments, the subset of the full set of policies capable of being enforced by the access network policy enforcement elements comprises a pre-defined subset of the policy configuration capabilities. In some embodiments, the enterprise service design center policy management subset limitations for enterprise service design center 194 provide the ability to define and manage one or more of the policies that define a service policy set or service plan that is applied to a given device, user, device group or user group. In some embodiments, the enterprise service design center policy management subset limitations for enterprise service design center 194 can provide the ability to enroll a device, user, device group or user group in a set limited to one or more pre-defined service policy configurations or service plans.

As an example embodiment, the enterprise service design center policy management subset limitations for enterprise service design center 194 may provide the following policy definition and management capabilities for a device (or user) or device group (or user group): specify service usage limits (caps) for bulk access service or for a specific classification of access service activities, require all traffic or certain traffic associated with enterprise-critical applications or content to be communicated via an enterprise VPN, define controls for which applications that can access the network or certain defined destinations on the network, specify network destinations that are allowed or not allowed, specify roaming service limitations, specify WiFi networks that are allowed or not allowed, specify security settings in the device access control or I/O access control ports, specify service usage notification triggers and notification content associated with the triggers (e.g., warnings when a specified service usage activity occurs, access is not allowed for a given attempted service usage activity, or service usage reaches a limit), and other such examples that are allowed to be managed under the policy management subset limitations. In some embodiments, the charging rates for such services may not be allowed to be managed under the policy management subset limitations.

In some embodiments, enterprise service design center 194 has an allowable subset of the full set of policies capable of being enforced by the access network policy enforcement elements that comprises a pre-defined set of one or more access network policy configurations (e.g., service plans). As an example embodiment, the set of pre-configured service plans may be defined for a certain implementation of enterprise service design center 194 comprising multiple pre-defined service plans, each of which provides variations in one or more of service notification policy, access control policy, service classification policy, service QoS policy, or service charging policy.

In some embodiments, enterprise service design center 194 is configured to allow a service design administrator to select one or more pre-configured access network policy configurations (or service plans) to be applied to a device, a user, a device group or a user group.

In some embodiments, enterprise service design center 194 comprises a device enrollment management system configured to enroll a device credential into a device group (or a user credential into a user group), where the set of device credentials (or user credentials) that enterprise service design center 194 is capable of managing is a subset of the device credentials (or user credentials) allowed on the access network. In some embodiments, the subset of device credentials (or user credentials) that are subject to management by enterprise service design center 194 is defined using service design center 190.

As an example embodiment, the set of pre-defined service plans that are made available to a first enterprise service design center 194 implementation managed by a first enterprise entity might consist of three service plans, wherein the first service plan comprises network policies (e.g., access policies, charging policies, or notification policies) that provide for limited or restricted home network access service but do not provide for roaming access services, the second service plan comprises network policies that provide for unlimited or unrestricted home network access service and also provide for limited roaming access services, and the third service plan comprises network policies that provide for unlimited or unrestricted home network access service and also provide for unlimited or unrestricted roaming access services. In another example embodiment, on the same carrier access network as the previous example, a second enterprise service design center 194 implementation managed by a second enterprise entity might consist of two service plans, wherein the two service plans might be the same as two of the service plans from the previous example embodiment, or they might be completely different.

Given these examples, it will now be understood and appreciated by one of ordinary skill in the art that enterprise service design center 194 provides a convenient means of designing and distributing custom service plans to different enterprise entities that meet the needs of each enterprise entity, wherein the various policy definition capabilities disclosed herein can be used in a large number of combinations to create the service plans, with the number of combinations of service plan design capabilities being too numerous to list here. It will also now be understood and appreciated by one of ordinary skill in the art that each enterprise can effectively manage its devices (or users) and device groups (or user groups) to provide the appropriate level of policy control needed by the enterprise in a simplified manner, without the need to manage all the full policy capabilities of the access network.

For example, the embodiments of service design center 190 and enterprise service design center 194 disclosed herein support a carrier network business process wherein a carrier network manager utilizes service design center 190 to create a set of access network policies that consist of a subset of the full set of access network policies capable of being enforced by the access network policy enforcement elements (referred to as specialized enterprise service plans), and the specialized enterprise service plans are designed and offered to meet the special needs of one or more enterprise entities. In some embodiments, an enterprise manager uses enterprise service design center 194 to apply the one or more specialized enterprise service plans to one or more devices (or users) or device groups (or user groups) that belong to the enterprise entity's mobile device inventory (or employee list). The different needs of various employee groups (or device types) can be among the factors that determine which service plan is assigned to a given user group (or device group). The specific needs of an employee can assist in determining which user group (or device group) the employee should be assigned to. The carrier manager can also create other specialized enterprise service plans for other enterprise entities to meet varied needs among enterprise market customers.

In some embodiments, an enterprise manager controls access network usage, costs, and access limits for an employee user group (e.g., a group of devices that could be as small as a single device or as large as all devices under the enterprise manager's control). In some embodiments, the enterprise manager establishes at least two user groups and establishes and manages different network-access policies for different employee user groups. For example, the enterprise manager may set and manage different policies for data usage on WiFi, 3G, 4G, or other networks for different employee user groups. Likewise, the enterprise manager may set different roaming privileges for different employee user groups.

In some embodiments, an enterprise manager sets expenditure ceilings by limiting allowed data usage for secure business applications to enforce security rules. In some embodiments, an enterprise manager tracks enterprise data access to improve compliance records. For example, the enterprise manager can track enterprise data usage by employee, device, application, location, network, or time of day.

Process Flows for Providing Enterprise and Consumer Billing Allocation for Wireless Communication Device Service Usage Activities

FIG. 27 illustrates a flow diagram for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. At 402, the process begins. At 404, a service usage activity of a wireless communication device (e.g., application based service usage that uses a wireless network in which the wireless communication device has an associated service plan) is performed. In some embodiments, the monitoring is performed on the wireless communication device. In some embodiments, the monitoring is performed by a network element, such as a secure application server for monitoring enterprise applications, as described herein with respect to various embodiments. At 406, an enterprise/consumer allocation is determined. In some embodiments, the monitored service usage activity is reported to a network element that determines the enterprise/consumer allocation based on the associated service plan that includes a defined enterprise/consumer allocation based on various factors, such as can be performed by a carrier billing server as described herein with respect to various embodiments. At 408, an associated consumer account is billed for the consumer service usage. At 410, the consumer account is credited for the enterprise service usage. At 412, the process is completed.

FIG. 28 illustrates another flow diagram for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. At 502, the process begins. At 504, a service usage activity of a wireless communication device (e.g., application based service usage that uses a wireless network in which the wireless communication device has an associated service plan) is performed. At 506, an enterprise/consumer allocation is determined. At 508, an associated enterprise account is billed for the enterprise service usage. At 510, the enterprise account is credited for the consumer service usage. At 512, the process is completed.

FIG. 29 illustrates another flow diagram for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. At 602, the process begins. At 604, a service usage activity of a wireless communication device (e.g., application based service usage that uses a wireless network in which the wireless communication device has an associated service plan) is performed. At 606, an enterprise/consumer allocation is determined. At 608, the enterprise service usage is reported. At 610, an expense reimbursement for the enterprise service usage is generated (e.g., by the enterprise for the consumer, who is, for example, an employee of the enterprise). At 612, the process is completed.

FIG. 30 illustrates another flow diagram for providing enterprise and consumer billing allocation for wireless communication device service usage activities in accordance with some embodiments. At 702, the process begins. At 704, a service usage activity of a wireless communication device (e.g., application based service usage that uses a wireless network in which the wireless communication device has an associated service plan) is performed. At 706, the monitored service usage is reported. At 708, an enterprise/consumer allocation is determined. At 710, a bill/charge based on the enterprise/consumer allocation is generated. At 712, the process is completed.

Although the foregoing embodiments have been described in some detail for purposes of clarity of understanding, the invention is not limited to the details provided. There are many alternative ways of implementing the invention. The disclosed embodiments are illustrative and not restrictive. In particular, many of the embodiments are not limited to supporting an enterprise/consumer split. As would be appreciated by one of ordinary skill in the art, the disclosed embodiments may be applied, for example, when a sponsor entity subsidizes a cost associated with an end-user device's use of a sponsored (or ambient) data service or application, and the user pays for the end-user device's use of non-sponsored (or non-ambient) data services or applications. The sponsor entity may use enterprise service design center 194 to configure devices that may use the sponsored service, policies applicable to the sponsored service, etc. Moreover, the disclosed embodiments may be applied when a first sponsor subsidizes a cost associated with an end-user device's use of a first sponsored data service or application, a second sponsor subsidizes a cost associated with the end-user device's use of a second sponsored data service or application, and the user pays for the end-user device's use of non-sponsored data services or applications. The sponsor entities may use one or more enterprise service design centers to configure aspects of the sponsored services. As would be appreciated by one of ordinary skill in the art, there are many other environments in which the disclosed embodiments are useful or applicable.

Several advantageous combination embodiments are now disclosed for allocating enterprise service usage accounting and personal service usage accounting. These combinations are for example purposes, are not meant to be exhaustive or limiting in any way; as will be apparent to one of ordinary skill in the art, these combinations represent only a fraction of the embodiments provided herein.

In some embodiments, a network system for classifying the accounting of access network service usage for an end user device comprises (i) a first service design center configured to receive an accounting split classification policy defining the classification rules for dividing an overall access network service usage into an enterprise service usage allocation and a personal service usage allocation, (ii) a network provisioning instruction translator configured to receive the accounting split classification policy and translate it to a set of network service usage classification and reporting instructions for one or more network elements responsible for classifying service usage, (iii) a network provisioning system for communicating the set of network service usage classification and reporting instructions to the one or more network elements responsible for classifying service usage, (iv) the one or more network elements responsible for classifying service usage configured to classify service usage to determine the enterprise service usage allocation and the personal service usage allocation, and generate service usage reports, and (v) a service usage accounting system that receives the service usage reports and (a) accrues the enterprise service usage allocation, and (b) accrues the personal service usage allocation.

In some embodiments, the network system for classifying the accounting of access network service usage for an end user device can be augmented wherein the first network access notification message policy is associated with a first device group defined by a first list of device credentials or a first user group defined by a first list of user credentials, and the service design center is further configured to obtain a second network access notification message policy comprising a plurality of second network access trigger conditions and, for each of the plurality of second network access trigger conditions, an associated second network access notification message, the second network access notification message policy associated with a second device group defined by a second list of device credentials or a second user group defined by a second list of user credentials.

In some embodiments, the network system for classifying the accounting of access network service usage for an end user device further comprises a master service design center configured to define a first notification policy design capability set for the first service design center, the first notification policy design capability set comprising a first subset of a master policy capability set. This embodiment can be further augmented wherein the master service design center is further configured to define a second notification policy design capability set for a second service design center, the second notification policy design capability set comprising a second subset of the master policy capability set, the second subset of the master policy capability set either identical to or different from the first subset of the master policy capability set.

In some embodiments, the network system for classifying the accounting of access network service usage for an end user device is further augmented wherein the first service design center is hosted on an operator network. In some embodiments, the network system for classifying the accounting of access network service usage for an end user device is optimized for smaller enterprise data center deployments wherein the first service design center is hosted on an enterprise business network.

In some embodiments, the network system for classifying the accounting of access network service usage for an end user device can be augmented wherein the enterprise service usage allocation comprises a classification of service usage that specifies one or more enterprise device software applications. In some embodiments, the enterprise applications can be one or more of email, calendar, contacts, enterprise intranet (e.g., a secure intranet browser with a secure SSL connection or other secure connection to enterprise services), mobile device synchronization or mobile enterprise communications.

In some embodiments, the network system for classifying the accounting of access network service usage for an end user device can be augmented wherein the enterprise service usage allocation comprises a classification of service usage that specifies one or more enterprise network destinations and the one or more enterprise network destinations comprise an address or identifier for a secure enterprise gateway. In some embodiments, the enterprise gateway comprises a VPN server.

In some embodiments, the network system for classifying the accounting of access network service usage for an end user device can be augmented wherein the enterprise service usage allocation comprises a classification of service usage that specifies one or more enterprise network destinations and the one or more enterprise network destinations comprise an address or identifier for one or more secure enterprise mobile services gateways or servers comprising one or more of an email server, a calendar server, a contacts server, an enterprise intranet access server, a mobile device synchronization services server or a mobile enterprise communication server.

In some embodiments, the network system for classifying the accounting of access network service usage for an end user device can be augmented wherein the one or more network elements responsible for classifying service usage and generating service usage reports comprises a service usage monitor located in a wireless operator network.

In some embodiments, the network system for classifying the accounting of access network service usage for an end user device can be augmented wherein the service usage accounting system is managed by an enterprise manager under the control of the entity that manages an enterprise business.

In some embodiments, the network system for classifying the accounting of access network service usage for an end user device can be augmented wherein the service usage accounting system is managed by an operator manager under the control of the entity that manages a network operator.

In some embodiments, the network system for classifying the accounting of access network service usage for an end user device can be augmented wherein the service usage accounting system is further configured to credit a user account with a service usage credit or monetary credit associated with the accrued enterprise service usage allocation.

In some embodiments, the network system for classifying the accounting of access network service usage for an end user device can be augmented wherein the service usage accounting system is further configured to debit a user account with a service usage debit or monetary cost associated with the accrued personal service usage allocation.

In some embodiments, the network system for classifying the accounting of access network service usage for an end user device can be augmented wherein the service usage accounting system is further configured to credit an enterprise account with a service usage credit or monetary credit associated with the accrued personal service usage allocation.

In some embodiments, the network system for classifying the accounting of access network service usage for an end user device can be augmented wherein the service usage accounting system is further configured to debit an enterprise account with a service usage debit or monetary cost associated with the accrued enterprise service usage allocation.

In some embodiments, the network system for classifying the accounting of access network service usage for an end user device can be augmented by further configuring the service design center to: (i) receive a personal service plan offer comprising one or more service plans for personal network access services accounted to the personal service usage allocation, (ii) configure a device user interface service plan offer notification message, (iii) communicate the device user interface service plan offer notification message to one or more device groups comprising a collection of devices identified by device credentials, (iv) receive a service plan selection option from an end user device user in response to the device user interface service plan offer notification message, and (v) cause one or more network elements responsible for activating service plans to activate the service plan selection chosen by the end user device user.

In some embodiments the end-user device system in communication with the network system for classifying the accounting of access network service usage comprises: (i) a device software application environment comprising: (a) an enterprise application execution environment configured with: (1) an enterprise application execution memory and data memory to support secure execution of enterprise software applications, the enterprise software applications comprising applications approved to execute in the secure execution environment and to communicate with secure enterprise services, (2) a secure enterprise communication link configured to provide communication between the enterprise software applications and enterprise network services, the enterprise network services comprising enterprise network resources and servers, (b) a personal application execution environment configured with execution memory and data memory to support execution of personal software applications not approved to execute in the secure execution environment, (ii) a personal service plan selection user interface comprising a notification software agent configured to receive personal service plan offer from a network element and display the service plan offers, the personal service plan offer comprising one or more service plans for personal network access services accounted to a personal service usage allocation, and receive a service plan selection option from an end user device user and forward the service plan selection option to a network element.

In some embodiments, the end-user device system can be augmented wherein the secure enterprise communication link comprises a VPN client in communication with an enterprise VPN gateway.

In some embodiments, the end-user device system can be augmented wherein the enterprise network services comprise access to one or more secure enterprise mobile services gateways or servers comprising one or more of an email server, a calendar server, a contacts server, an enterprise intranet access server, a mobile device synchronization services server or a mobile enterprise communication server.

In some embodiments, the end-user device system can be augmented wherein the enterprise application execution environment is further configured to: (i) acquire a device software application signature prior to allowing execution of the device software application in the virtual machine operating environment, (ii) compare the signature to an approved list of signatures, (iii) allow the application to execute if it is on the list, and (iv) not allow the application to execute if it is not on the list.

In some embodiments, the end-user device system can be augmented wherein enterprise application execution environment comprises a virtual machine operating environment.

In some embodiments, the end-user device system can be augmented wherein enterprise application execution environment comprises a secure CPU hardware execution partition.

In some embodiments, the end-user device system can be augmented wherein enterprise application execution environment comprises a secure operating system execution partition.

In some embodiments, the end-user device system can be augmented wherein enterprise application execution environment comprises a secure memory area protected by an enterprise application software program that encrypts the enterprise data stored on device memory and runs a secure encrypted communication protocol for communication with a secure mobile enterprise services gateway server.

Several advantageous combination embodiments are now disclosed for providing enterprise control of network access service to an end user device. These combinations are for example purposes, are not meant to be exhaustive or limiting in any way; as would be appreciated by one of ordinary skill in the art, these combinations represent only a fraction of the advantageous embodiment combinations provided herein.

In some embodiments, a network system for providing network access service control for an end user device comprising: (i) a first service design center configured to receive from an administrator user or a configuration file a first network access policy comprising a first set of network access service permissions associated with an end user device or end user device user, (ii) a network provisioning instruction translator configured to receive the first network access policy and translate it to a set of network access policy enforcement instructions for one or more network elements responsible for controlling network access, (iii) a network provisioning system for communicating the set of network access policy enforcement instructions to the one or more network elements responsible for controlling network access, (iv) the one or more network elements responsible for controlling network access configured to execute the set of network access policy enforcement instructions to enforce network access service permissions and limits.

In some embodiments, the network system for providing network access service control can be augmented wherein the first network access policy is associated with a first device group defined by a first list of device credentials or a first user group defined by a first list of user credentials, and the service design center is further configured to obtain a second network access policy comprising a second set of network access service permissions and, the second network access policy associated with a second device group defined by a second list of device credentials or a second user group defined by a second list of user credentials.

In some embodiments, the network system for classifying the accounting of access network service usage for an end user device further comprises a master service design center configured to define a first network access policy design capability set for the first service design center, the first network access policy design capability set comprising a first subset of a master policy capability set. This embodiment can be further augmented wherein the master service design center is further configured to define a second network access policy design capability set for a second service design center, the second network access policy design capability set comprising a second subset of the master policy capability set, the second subset of the master policy capability set either identical to or different from the first subset of the master policy capability set.

In some embodiments, the network system for providing network access service control can be augmented wherein the first network access policy defines a set of one or more service usage limits or service cost limits.

In some embodiments, the network system for providing network access service control can be augmented wherein the first network access policy defines a set of one or more roaming network service usage limits or service cost limits.

In some embodiments, the network system for providing network access service control can be augmented wherein the first network access policy defines a set of one or more network type restrictions, wherein a network type comprises one or more of a cellular network, a 2G network, a 3G network, a 4G network, a WiFi network, a particular WiFi network APN, roaming cellular network, a particular cellular operator network.

In some embodiments, the network system for providing network access service control can be augmented wherein the first network access policy defines a set of one or more device application software network access restrictions.

In some embodiments, the network system for providing network access service control can be augmented wherein the first network access policy defines a set of one or more enterprise network destination allowances or restrictions.

In some embodiments, the network system for providing network access service control can be augmented wherein the first network access policy defines a set of one or more application or network destination allowances or restrictions communicated over a non-secure communication link.

In some embodiments, the network system for providing network access service control can be augmented wherein the first network access policy defines a set of one or more personal application or network destination allowances or restrictions.

In some embodiments, the network system for providing network access service control can be augmented wherein the first network access policy defines a set of one or more geographic location allowances or restrictions.

In some embodiments, the network system for providing network access service control can be augmented wherein the one or more network elements responsible for controlling network access comprises a service usage monitor located in an enterprise access network. In some embodiments, the one or more network elements responsible for controlling network access comprises a service usage monitor located in an enterprise access network comprise a VPN gateway wherein all device traffic is communicated from the device to the VPN gateway configured to control the device traffic. In some embodiments, the VPN gateway performs service usage classification to identify and control enterprise traffic. In some embodiments, the VPN gateway performs service usage classification to identify and control personal traffic.

INCORPORATION BY REFERENCE

The following U.S. applications are hereby incorporated by reference for all purposes: application Ser. No. 13/248,028, filed Sep. 28, 2011, entitled ENTERPRISE ACCESS CONTROL AND ACCOUNTING ALLOCATION FOR ACCESS NETWORKS; application Ser. No. 12/380,780, entitled AUTOMATED DEVICE PROVISIONING AND ACTIVATION, filed Mar. 2, 2009; application Ser. No. 12/380,778, filed Mar. 2, 2009, entitled VERIFIABLE DEVICE ASSISTED SERVICE USAGE BILLING WITH INTEGRATED ACCOUNTING, MEDIATION ACCOUNTING, AND MULTI-ACCOUNT; Provisional Application No. 61/206,354, entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD, filed Jan. 28, 2009; Provisional Application No. 61/206,944, entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD, filed Feb. 4, 2009; Provisional Application No. 61/207,393, entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD filed Feb. 10, 2009; Provisional Application No. 61/207,739, entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD filed Feb. 13, 2009; and Provisional Application No. 61/387,243, entitled ENTERPRISE AND CONSUMER BILLING ALLOCATION FOR WIRELESS COMMUNICATION DEVICE SERVICE USAGE ACTIVITIES filed Sep. 28, 2010.

Claims

1. A method of operating a wireless end-user device, the method comprising: storing secure policy information indicative of an application-specific execution environment policy and a configurable communication security policy;based on the secure stored information indicative of an application-specific execution environment policy, allowing a first set of multiple device application instances to run only in a first secure application environment on the wireless end-user device, and allowing a second set of device application instances to run only outside of the first secure application environment; andbased on the secure stored information indicative of a configurable communication security policy, initiate a first secure tunnel to a network tunnel endpoint, and direct all network data communications to and from device application instances executing in the first secure application environment through the first secure tunnel.
2. The method of claim 1, wherein the configurable communication security policy defines a first configuration, which indicates that application instances in the second set of device application instances are not allowed to use the first secure tunnel, the method further comprising, based on the secure stored information indicative of a configurable communication security policy indicating the first configuration, directing all network data communications to and from device application instances executing outside of the first secure application environment through a network path outside of the first secure tunnel.

US Referenced Citations (1444)

Number	Name	Date	Kind
5131020	Liebesny et al.	Jul 1992	A
5283904	Carson et al.	Feb 1994	A
5325532	Crosswy et al.	Jun 1994	A
5572528	Shuen	Nov 1996	A
5577100	McGregor et al.	Nov 1996	A
5594777	Makkonen et al.	Jan 1997	A
5617539	Ludwig et al.	Apr 1997	A
5630159	Zancho	May 1997	A
5633484	Zancho et al.	May 1997	A
5633868	Baldwin et al.	May 1997	A
5754953	Briancon et al.	May 1998	A
5774532	Gottlieb et al.	Jun 1998	A
5794142	Vanttila et al.	Aug 1998	A
5814798	Zancho	Sep 1998	A
5889477	Fastenrath	Mar 1999	A
5892900	Ginter et al.	Apr 1999	A
5903845	Buhrmann et al.	May 1999	A
5915008	Dulman	Jun 1999	A
5915226	Martineau	Jun 1999	A
5933778	Buhrmann et al.	Aug 1999	A
5940472	Newman et al.	Aug 1999	A
5974439	Bollella	Oct 1999	A
5983270	Abraham et al.	Nov 1999	A
6035281	Crosskey et al.	Mar 2000	A
6038452	Strawczynski et al.	Mar 2000	A
6038540	Krist et al.	Mar 2000	A
6047268	Bartoli et al.	Apr 2000	A
6058434	Wilt et al.	May 2000	A
6061571	Tamura	May 2000	A
6064878	Denker et al.	May 2000	A
6078953	Vaid et al.	Jun 2000	A
6081591	Skoog	Jun 2000	A
6098878	Dent et al.	Aug 2000	A
6104700	Haddock et al.	Aug 2000	A
6115823	Velasco et al.	Sep 2000	A
6119933	Wong et al.	Sep 2000	A
6125391	Meltzer et al.	Sep 2000	A
6141565	Feurerstein et al.	Oct 2000	A
6141686	Jackowski et al.	Oct 2000	A
6148336	Thomas et al.	Nov 2000	A
6154738	Call	Nov 2000	A
6157636	Voit et al.	Dec 2000	A
6185576	McIntosh	Feb 2001	B1
6198915	McGregor et al.	Mar 2001	B1
6219786	Cunningham et al.	Apr 2001	B1
6226277	Chuah	May 2001	B1
6246870	Dent et al.	Jun 2001	B1
6263055	Garland et al.	Jul 2001	B1
6292828	Williams	Sep 2001	B1
6317584	Abu-Amara et al.	Nov 2001	B1
6381316	Joyce et al.	Apr 2002	B2
6393014	Daly et al.	May 2002	B1
6397259	Lincke et al.	May 2002	B1
6401113	Lazaridis et al.	Jun 2002	B2
6418147	Wiedeman	Jul 2002	B1
6438575	Khan et al.	Aug 2002	B1
6445777	Clark	Sep 2002	B1
6449479	Sanchez	Sep 2002	B1
6466984	Naveh et al.	Oct 2002	B1
6477670	Ahmadvand	Nov 2002	B1
6502131	Vaid et al.	Dec 2002	B1
6505114	Luciani	Jan 2003	B2
6510152	Gerszberg et al.	Jan 2003	B1
6522629	Anderson, Sr.	Feb 2003	B1
6532235	Benson et al.	Mar 2003	B1
6532579	Sato et al.	Mar 2003	B2
6535855	Cahill et al.	Mar 2003	B1
6535949	Parker	Mar 2003	B1
6539082	Lowe et al.	Mar 2003	B1
6542500	Gerszberg et al.	Apr 2003	B1
6542992	Peirce et al.	Apr 2003	B1
6546016	Gerszberg et al.	Apr 2003	B1
6563806	Yano et al.	May 2003	B1
6570974	Gerszberg et al.	May 2003	B1
6574321	Cox et al.	Jun 2003	B1
6574465	Marsh et al.	Jun 2003	B2
6578076	Putzolu	Jun 2003	B1
6581092	Motoyama	Jun 2003	B1
6591098	Shieh et al.	Jul 2003	B1
6598034	Kloth	Jul 2003	B1
6601040	Kolls	Jul 2003	B1
6603969	Vuoristo et al.	Aug 2003	B1
6603975	Inouchi et al.	Aug 2003	B1
6606744	Mikurak	Aug 2003	B1
6628934	Rosenberg et al.	Sep 2003	B2
6631122	Arunachalam et al.	Oct 2003	B1
6636721	Threadgill et al.	Oct 2003	B2
6639975	O'Neal et al.	Oct 2003	B1
6640097	Corrigan et al.	Oct 2003	B2
6640334	Rasmussen	Oct 2003	B1
6650887	McGregor et al.	Nov 2003	B2
6651101	Gai et al.	Nov 2003	B1
6654786	Fox et al.	Nov 2003	B1
6654814	Britton et al.	Nov 2003	B1
6658254	Purdy et al.	Dec 2003	B1
6662014	Walsh	Dec 2003	B1
6678516	Nordman et al.	Jan 2004	B2
6683853	Kannas et al.	Jan 2004	B1
6684244	Goldman et al.	Jan 2004	B1
6690918	Evans et al.	Feb 2004	B2
6697821	Ziff et al.	Feb 2004	B2
6725031	Watler et al.	Apr 2004	B2
6725256	Albal et al.	Apr 2004	B1
6735206	Oki et al.	May 2004	B1
6748195	Phillips	Jun 2004	B1
6748437	Mankude et al.	Jun 2004	B1
6751296	Albal et al.	Jun 2004	B1
6754470	Hendrickson et al.	Jun 2004	B2
6757717	Goldstein	Jun 2004	B1
6760417	Wallenius	Jul 2004	B1
6763000	Walsh	Jul 2004	B1
6763226	McZeal, Jr.	Jul 2004	B1
6765864	Natarajan et al.	Jul 2004	B1
6765925	Sawyer et al.	Jul 2004	B1
6782412	Brophy et al.	Aug 2004	B2
6785889	Williams	Aug 2004	B1
6792461	Hericourt	Sep 2004	B1
6829596	Frazee	Dec 2004	B1
6829696	Balmer et al.	Dec 2004	B1
6839340	Voit et al.	Jan 2005	B1
6873988	Herrmann et al.	Mar 2005	B2
6876653	Ambe et al.	Apr 2005	B2
6879825	Daly	Apr 2005	B1
6882718	Smith	Apr 2005	B1
6885997	Roberts	Apr 2005	B1
6901440	Bimm et al.	May 2005	B1
6920455	Weschler	Jul 2005	B1
6922562	Ward et al.	Jul 2005	B2
6928280	Xanthos et al.	Aug 2005	B1
6934249	Bertin et al.	Aug 2005	B1
6934751	Jayapalan et al.	Aug 2005	B2
6947723	Gurnani et al.	Sep 2005	B1
6947985	Hegli et al.	Sep 2005	B2
6952428	Necka et al.	Oct 2005	B1
6957067	Iyer et al.	Oct 2005	B1
6959202	Heinonen et al.	Oct 2005	B2
6959393	Hollis et al.	Oct 2005	B2
6965667	Trabandt et al.	Nov 2005	B2
6965872	Grdina	Nov 2005	B1
6967958	Ono et al.	Nov 2005	B2
6970692	Tysor	Nov 2005	B2
6982733	McNally et al.	Jan 2006	B1
6983370	Eaton et al.	Jan 2006	B2
6996062	Freed et al.	Feb 2006	B1
6996076	Forbes et al.	Feb 2006	B1
6996393	Pyhalammi et al.	Feb 2006	B2
6998985	Reisman et al.	Feb 2006	B2
7002920	Ayyagari et al.	Feb 2006	B1
7007295	Rose et al.	Feb 2006	B1
7013469	Smith et al.	Mar 2006	B2
7017189	DeMello et al.	Mar 2006	B1
7024200	McKenna et al.	Apr 2006	B2
7024460	Koopmas et al.	Apr 2006	B2
7027055	Anderson et al.	Apr 2006	B2
7027408	Nabkel et al.	Apr 2006	B2
7031733	Alminana et al.	Apr 2006	B2
7032072	Quinn et al.	Apr 2006	B1
7039027	Bridgelall	May 2006	B2
7039037	Wang et al.	May 2006	B2
7039403	Wong	May 2006	B2
7039713	Van Gunter et al.	May 2006	B1
7042988	Juitt et al.	May 2006	B2
7043225	Patel et al.	May 2006	B1
7043226	Yamauchi	May 2006	B2
7043268	Yukie et al.	May 2006	B2
7047276	Liu et al.	May 2006	B2
7058022	Carolan et al.	Jun 2006	B1
7058968	Rowland et al.	Jun 2006	B2
7068600	Cain	Jun 2006	B2
7069248	Huber	Jun 2006	B2
7082422	Zirngibl et al.	Jul 2006	B1
7084775	Smith	Aug 2006	B1
7092696	Hosain et al.	Aug 2006	B1
7095754	Benveniste	Aug 2006	B2
7102620	Harries et al.	Sep 2006	B2
7110753	Campen	Sep 2006	B2
7113780	McKenna et al.	Sep 2006	B2
7113997	Jayapalan et al.	Sep 2006	B2
7120133	Joo et al.	Oct 2006	B1
7133386	Holur et al.	Nov 2006	B2
7133695	Beyda	Nov 2006	B2
7136361	Benveniste	Nov 2006	B2
7139569	Kato	Nov 2006	B2
7142876	Trossen et al.	Nov 2006	B2
7149229	Leung	Dec 2006	B1
7149521	Sundar et al.	Dec 2006	B2
7151764	Heinonen et al.	Dec 2006	B1
7158792	Cook et al.	Jan 2007	B1
7162237	Silver et al.	Jan 2007	B1
7165040	Ehrman et al.	Jan 2007	B2
7167078	Pourchot	Jan 2007	B2
7174156	Mangal	Feb 2007	B1
7174174	Boris et al.	Feb 2007	B2
7177919	Truong et al.	Feb 2007	B1
7180855	Lin	Feb 2007	B1
7181017	Nagel et al.	Feb 2007	B1
7191248	Chattopadhyay et al.	Mar 2007	B2
7197321	Erskine et al.	Mar 2007	B2
7200112	Sundar et al.	Apr 2007	B2
7203169	Okholm et al.	Apr 2007	B1
7203721	Ben-Efraim et al.	Apr 2007	B1
7203752	Rice et al.	Apr 2007	B2
7212491	Koga	May 2007	B2
7219123	Fiechter et al.	May 2007	B1
7222190	Klinker et al.	May 2007	B2
7222304	Beaton et al.	May 2007	B2
7224968	Dobson et al.	May 2007	B2
7228354	Chambliss et al.	Jun 2007	B2
7236780	Benco	Jun 2007	B2
7242668	Kan et al.	Jul 2007	B2
7242920	Morris	Jul 2007	B2
7245901	McGregor et al.	Jul 2007	B2
7248570	Bahl et al.	Jul 2007	B2
7251218	Jorgensen	Jul 2007	B2
7260382	Lamb et al.	Aug 2007	B1
7266371	Amin et al.	Sep 2007	B1
7269157	Klinker et al.	Sep 2007	B2
7271765	Stilp et al.	Sep 2007	B2
7272660	Powers et al.	Sep 2007	B1
7280816	Fratti et al.	Oct 2007	B2
7280818	Clayton	Oct 2007	B2
7283561	Picher-Dempsey	Oct 2007	B1
7283963	Fitzpatrick et al.	Oct 2007	B1
7286834	Walter	Oct 2007	B2
7286848	Vireday et al.	Oct 2007	B2
7289489	Kung et al.	Oct 2007	B1
7290283	Copeland, III	Oct 2007	B2
7310424	Gehring et al.	Dec 2007	B2
7313237	Bahl et al.	Dec 2007	B2
7315892	Freimuth et al.	Jan 2008	B2
7317699	Godfrey et al.	Jan 2008	B2
7318111	Zhao	Jan 2008	B2
7320029	Rinne et al.	Jan 2008	B2
7322044	Hrastar	Jan 2008	B2
7324447	Morford	Jan 2008	B1
7325037	Lawson	Jan 2008	B2
7336960	Zavalkovsky et al.	Feb 2008	B2
7340772	Panasyuk et al.	Mar 2008	B2
7346410	Uchiyama	Mar 2008	B2
7349695	Oommen et al.	Mar 2008	B2
7353533	Wright et al.	Apr 2008	B2
7356011	Waters et al.	Apr 2008	B1
7356337	Florence	Apr 2008	B2
7366497	Nagata	Apr 2008	B2
7366654	Moore	Apr 2008	B2
7369848	Jiang	May 2008	B2
7369856	Ovadia	May 2008	B2
7373136	Watler et al.	May 2008	B2
7373179	Stine et al.	May 2008	B2
7379731	Natsuno et al.	May 2008	B2
7388950	Elsey et al.	Jun 2008	B2
7389412	Sharma et al.	Jun 2008	B2
7391724	Alakoski et al.	Jun 2008	B2
7395244	Kingsford	Jul 2008	B1
7401338	Bowen et al.	Jul 2008	B1
7403763	Maes	Jul 2008	B2
7409447	Assadzadeh	Aug 2008	B1
7409569	Illowsky et al.	Aug 2008	B2
7411930	Montojo et al.	Aug 2008	B2
7418253	Kavanah	Aug 2008	B2
7418257	Kim	Aug 2008	B2
7421004	Feher	Sep 2008	B2
7423971	Mohaban et al.	Sep 2008	B1
7428750	Dunn et al.	Sep 2008	B1
7440433	Rink et al.	Oct 2008	B2
7444669	Bahl et al.	Oct 2008	B1
7450591	Korling et al.	Nov 2008	B2
7450927	Creswell et al.	Nov 2008	B1
7454191	Dawson et al.	Nov 2008	B2
7457265	Julka et al.	Nov 2008	B2
7457870	Lownsbrough et al.	Nov 2008	B1
7460837	Diener	Dec 2008	B2
7466652	Lau et al.	Dec 2008	B2
7472189	Mallya et al.	Dec 2008	B2
7478420	Wright et al.	Jan 2009	B2
7486185	Culpepper et al.	Feb 2009	B2
7486658	Kumar	Feb 2009	B2
7493659	Wu et al.	Feb 2009	B1
7496652	Pezzutti	Feb 2009	B2
7499438	Hinman et al.	Mar 2009	B2
7499537	Elsey et al.	Mar 2009	B2
7502672	Kolls	Mar 2009	B1
7505795	Lim et al.	Mar 2009	B1
7508799	Sumner et al.	Mar 2009	B2
7512128	DiMambro et al.	Mar 2009	B2
7512131	Svensson et al.	Mar 2009	B2
7515608	Yuan et al.	Apr 2009	B2
7515926	Bu et al.	Apr 2009	B2
7516219	Moghaddam et al.	Apr 2009	B2
7522576	Du et al.	Apr 2009	B2
7526541	Roese et al.	Apr 2009	B2
7529204	Bourlas et al.	May 2009	B2
7535880	Hinman et al.	May 2009	B1
7536695	Alam et al.	May 2009	B2
7539132	Werner et al.	May 2009	B2
7539862	Edgett et al.	May 2009	B2
7540408	Levine et al.	Jun 2009	B2
7545782	Rayment et al.	Jun 2009	B2
7546460	Maes	Jun 2009	B2
7546629	Albert et al.	Jun 2009	B2
7548875	Mikkelsen et al.	Jun 2009	B2
7548976	Bahl et al.	Jun 2009	B2
7551922	Roskowski et al.	Jun 2009	B2
7554983	Muppala	Jun 2009	B1
7555757	Smith et al.	Jun 2009	B2
7561899	Lee	Jul 2009	B2
7562213	Timms	Jul 2009	B1
7564799	Holland et al.	Jul 2009	B2
7565141	Macaluso	Jul 2009	B2
7574509	Nixon et al.	Aug 2009	B2
7574731	Fascenda	Aug 2009	B2
7577431	Jiang	Aug 2009	B2
7580356	Mishra et al.	Aug 2009	B1
7580857	VanFleet et al.	Aug 2009	B2
7583964	Wong	Sep 2009	B2
7584298	Klinker et al.	Sep 2009	B2
7586871	Hamilton et al.	Sep 2009	B2
7593417	Wang et al.	Sep 2009	B2
7593730	Khandelwal et al.	Sep 2009	B2
7599288	Cole et al.	Oct 2009	B2
7599714	Kuzminskiy	Oct 2009	B2
7602746	Calhoun et al.	Oct 2009	B2
7607041	Kraemer et al.	Oct 2009	B2
7609650	Roskowski et al.	Oct 2009	B2
7609700	Ying et al.	Oct 2009	B1
7610047	Hicks, III et al.	Oct 2009	B2
7610057	Bahl et al.	Oct 2009	B2
7610328	Haase et al.	Oct 2009	B2
7610396	Taglienti et al.	Oct 2009	B2
7614051	Glaum et al.	Nov 2009	B2
7617516	Huslak et al.	Nov 2009	B2
7620041	Dunn et al.	Nov 2009	B2
7620065	Falardeau	Nov 2009	B2
7620162	Aaron et al.	Nov 2009	B2
7620383	Taglienti et al.	Nov 2009	B2
7627314	Carlson et al.	Dec 2009	B2
7627600	Citron et al.	Dec 2009	B2
7627767	Sherman et al.	Dec 2009	B2
7627872	Hebeler et al.	Dec 2009	B2
7633438	Tysowski	Dec 2009	B2
7634388	Archer et al.	Dec 2009	B2
7636574	Poosala	Dec 2009	B2
7636626	Oesterling et al.	Dec 2009	B2
7643411	Andreasen et al.	Jan 2010	B2
7644151	Jerrim et al.	Jan 2010	B2
7644267	Ylikoski et al.	Jan 2010	B2
7647047	Moghaddam et al.	Jan 2010	B2
7650137	Jobs et al.	Jan 2010	B2
7653394	McMillin	Jan 2010	B2
7656271	Ehrman et al.	Feb 2010	B2
7657920	Arseneau et al.	Feb 2010	B2
7660419	Ho	Feb 2010	B1
7661124	Ramanathan et al.	Feb 2010	B2
7664494	Jiang	Feb 2010	B2
7668176	Chuah	Feb 2010	B2
7668612	Okkonen	Feb 2010	B1
7668903	Edwards et al.	Feb 2010	B2
7668966	Klinker et al.	Feb 2010	B2
7676673	Weller et al.	Mar 2010	B2
7680086	Eglin	Mar 2010	B2
7681226	Kraemer et al.	Mar 2010	B2
7684370	Kezys	Mar 2010	B2
7685131	Batra et al.	Mar 2010	B2
7685254	Pandya	Mar 2010	B2
7685530	Sherrard et al.	Mar 2010	B2
7688792	Babbar et al.	Mar 2010	B2
7693107	De Froment	Apr 2010	B2
7693720	Kennewick et al.	Apr 2010	B2
7697540	Haddad et al.	Apr 2010	B2
7710932	Muthuswamy et al.	May 2010	B2
7711848	Maes	May 2010	B2
7719966	Luft et al.	May 2010	B2
7720206	Devolites et al.	May 2010	B2
7720464	Batta	May 2010	B2
7720505	Gopi et al.	May 2010	B2
7720960	Pruss et al.	May 2010	B2
7721296	Ricagni	May 2010	B2
7724716	Fadell	May 2010	B2
7725570	Lewis	May 2010	B1
7729326	Sekhar	Jun 2010	B2
7730123	Erickson et al.	Jun 2010	B1
7734784	Araujo et al.	Jun 2010	B1
7742406	Muppala	Jun 2010	B1
7746854	Ambe et al.	Jun 2010	B2
7747240	Briscoe et al.	Jun 2010	B1
7747699	Prueitt et al.	Jun 2010	B2
7747730	Harlow	Jun 2010	B1
7752330	Olsen et al.	Jul 2010	B2
7756056	Kim et al.	Jul 2010	B2
7756534	Anupam et al.	Jul 2010	B2
7756757	Oakes, III	Jul 2010	B1
7760137	Martucci et al.	Jul 2010	B2
7760711	Kung et al.	Jul 2010	B1
7760861	Croak et al.	Jul 2010	B1
7765294	Edwards et al.	Jul 2010	B2
7769397	Funato et al.	Aug 2010	B2
7770785	Jha et al.	Aug 2010	B2
7774323	Helfman	Aug 2010	B2
7774412	Schnepel	Aug 2010	B1
7774456	Lownsbrough et al.	Aug 2010	B1
7778176	Morford	Aug 2010	B2
7778643	Laroia et al.	Aug 2010	B2
7792257	Vanier et al.	Sep 2010	B1
7792538	Kozisek	Sep 2010	B2
7792708	Alva	Sep 2010	B2
7797019	Friedmann	Sep 2010	B2
7797060	Grgic et al.	Sep 2010	B2
7797204	Balent	Sep 2010	B2
7797401	Stewart et al.	Sep 2010	B2
7801523	Kenderov	Sep 2010	B1
7801783	Kende et al.	Sep 2010	B2
7801985	Pitkow et al.	Sep 2010	B1
7802724	Nohr	Sep 2010	B1
7805140	Friday et al.	Sep 2010	B2
7805522	Schlüter et al.	Sep 2010	B2
7805606	Birger et al.	Sep 2010	B2
7809351	Panda et al.	Oct 2010	B1
7809372	Rajaniemi	Oct 2010	B2
7813746	Rajkotia	Oct 2010	B2
7817615	Breau et al.	Oct 2010	B1
7817983	Cassett et al.	Oct 2010	B2
7822837	Urban et al.	Oct 2010	B1
7826427	Sood et al.	Nov 2010	B2
7826607	de Carvalho Resende et al.	Nov 2010	B1
7835275	Swan et al.	Nov 2010	B1
7843831	Morrill et al.	Nov 2010	B2
7843843	Papp, III et al.	Nov 2010	B1
7844034	Oh et al.	Nov 2010	B1
7844728	Anderson et al.	Nov 2010	B2
7848768	Omori et al.	Dec 2010	B2
7849161	Koch et al.	Dec 2010	B2
7849477	Cristofalo et al.	Dec 2010	B2
7853255	Karaoguz et al.	Dec 2010	B2
7853656	Yach et al.	Dec 2010	B2
7856226	Wong et al.	Dec 2010	B2
7860088	Lioy	Dec 2010	B2
7865182	Macaluso	Jan 2011	B2
7865187	Ramer et al.	Jan 2011	B2
7868778	Kenwright	Jan 2011	B2
7873001	Silver	Jan 2011	B2
7873344	Bowser et al.	Jan 2011	B2
7873346	Petersson et al.	Jan 2011	B2
7873540	Arumugam	Jan 2011	B2
7873705	Kalish	Jan 2011	B2
7877090	Maes	Jan 2011	B2
7881199	Krstulich	Feb 2011	B2
7881697	Baker et al.	Feb 2011	B2
7882029	White	Feb 2011	B2
7882247	Sturniolo et al.	Feb 2011	B2
7882560	Kraemer et al.	Feb 2011	B2
7886047	Potluri	Feb 2011	B1
7889384	Armentrout et al.	Feb 2011	B2
7890084	Dudziak et al.	Feb 2011	B1
7890111	Bugenhagen	Feb 2011	B2
7894431	Goring et al.	Feb 2011	B2
7899039	Andreasen et al.	Mar 2011	B2
7899438	Baker et al.	Mar 2011	B2
7903553	Liu	Mar 2011	B2
7907970	Park et al.	Mar 2011	B2
7911975	Droz et al.	Mar 2011	B2
7912025	Pattenden et al.	Mar 2011	B2
7912056	Brassem	Mar 2011	B1
7920529	Mahler et al.	Apr 2011	B1
7921463	Sood et al.	Apr 2011	B2
7925740	Nath et al.	Apr 2011	B2
7925778	Wijnands et al.	Apr 2011	B1
7929959	DeAtley et al.	Apr 2011	B2
7929960	Martin et al.	Apr 2011	B2
7929973	Zavalkovsky et al.	Apr 2011	B2
7930327	Craft et al.	Apr 2011	B2
7930446	Kesselman et al.	Apr 2011	B2
7930553	Satarasinghe et al.	Apr 2011	B2
7933274	Verma et al.	Apr 2011	B2
7936736	Proctor, Jr. et al.	May 2011	B2
7937069	Rassam	May 2011	B2
7937450	Janik	May 2011	B2
7940685	Breslau et al.	May 2011	B1
7940751	Hansen	May 2011	B2
7941184	Prendergast et al.	May 2011	B2
7944948	Chow et al.	May 2011	B2
7945238	Baker et al.	May 2011	B2
7945240	Klock et al.	May 2011	B1
7945945	Graham et al.	May 2011	B2
7948952	Hurtta et al.	May 2011	B2
7948953	Melkote et al.	May 2011	B2
7948968	Voit et al.	May 2011	B2
7949529	Weider et al.	May 2011	B2
7953808	Sharp et al.	May 2011	B2
7953877	Vemula et al.	May 2011	B2
7957020	Mine et al.	Jun 2011	B2
7957381	Clermidy et al.	Jun 2011	B2
7957511	Drudis et al.	Jun 2011	B2
7958029	Bobich et al.	Jun 2011	B1
7962622	Friend et al.	Jun 2011	B2
7965983	Swan et al.	Jun 2011	B1
7966405	Sundaresan et al.	Jun 2011	B2
7969950	Iyer et al.	Jun 2011	B2
7970350	Sheynman	Jun 2011	B2
7970426	Poe et al.	Jun 2011	B2
7974624	Gallagher et al.	Jul 2011	B2
7975184	Goff et al.	Jul 2011	B2
7978627	Taylor et al.	Jul 2011	B2
7978686	Goyal et al.	Jul 2011	B2
7979069	Hupp et al.	Jul 2011	B2
7979889	Gladstone et al.	Jul 2011	B2
7984130	Bogineni et al.	Jul 2011	B2
7984511	Kocher et al.	Jul 2011	B2
7986935	D'Souza et al.	Jul 2011	B1
7987496	Bryce et al.	Jul 2011	B2
7987510	Kocher et al.	Jul 2011	B2
7990049	Shioya	Aug 2011	B2
8000276	Scherzer et al.	Aug 2011	B2
8000318	Wiley et al.	Aug 2011	B2
8005009	McKee et al.	Aug 2011	B2
8005459	Balsillie	Aug 2011	B2
8005726	Bao	Aug 2011	B1
8005913	Carlander	Aug 2011	B1
8005988	Maes	Aug 2011	B2
8010080	Thenthiruperai et al.	Aug 2011	B1
8010081	Roskowski	Aug 2011	B1
8010082	Sutaria et al.	Aug 2011	B2
8010990	Ferguson et al.	Aug 2011	B2
8015133	Wu et al.	Sep 2011	B1
8015234	Lum et al.	Sep 2011	B2
8019687	Wang et al.	Sep 2011	B2
8019820	Son et al.	Sep 2011	B2
8019846	Roelens et al.	Sep 2011	B2
8019868	Rao et al.	Sep 2011	B2
8019886	Harrang et al.	Sep 2011	B2
8023425	Raleigh	Sep 2011	B2
8024397	Erickson et al.	Sep 2011	B1
8024424	Freimuth et al.	Sep 2011	B2
8027339	Short et al.	Sep 2011	B2
8031601	Feroz et al.	Oct 2011	B2
8032168	Ikaheimo	Oct 2011	B2
8032409	Mikurak	Oct 2011	B1
8032899	Archer et al.	Oct 2011	B2
8036387	Kudelski et al.	Oct 2011	B2
8036600	Garrett et al.	Oct 2011	B2
8044792	Orr et al.	Oct 2011	B2
8045973	Chambers	Oct 2011	B2
8046449	Yoshiuchi	Oct 2011	B2
8050275	Iyer	Nov 2011	B1
8050690	Neeraj	Nov 2011	B2
8050705	Sicher et al.	Nov 2011	B2
8059530	Cole	Nov 2011	B1
8060017	Schlicht et al.	Nov 2011	B2
8060463	Spiegel	Nov 2011	B1
8064418	Maki	Nov 2011	B2
8064896	Bell et al.	Nov 2011	B2
8065365	Saxena et al.	Nov 2011	B2
8068824	Shan et al.	Nov 2011	B2
8068829	Lemond et al.	Nov 2011	B2
8073427	Koch et al.	Dec 2011	B2
8073721	Lewis	Dec 2011	B1
8078140	Baker et al.	Dec 2011	B2
8078163	Lemond et al.	Dec 2011	B2
8085808	Brusca et al.	Dec 2011	B2
8086398	Sanchez et al.	Dec 2011	B2
8086497	Oakes, III	Dec 2011	B1
8086791	Caulkins	Dec 2011	B2
8090359	Proctor, Jr. et al.	Jan 2012	B2
8090361	Hagan	Jan 2012	B2
8090616	Proctor, Jr. et al.	Jan 2012	B2
8091087	Ali et al.	Jan 2012	B2
8094551	Huber et al.	Jan 2012	B2
8095112	Chow et al.	Jan 2012	B2
8095124	Balia	Jan 2012	B2
8095640	Guingo et al.	Jan 2012	B2
8095666	Schmidt et al.	Jan 2012	B2
8098579	Ray et al.	Jan 2012	B2
8099077	Chowdhury et al.	Jan 2012	B2
8099517	Jia et al.	Jan 2012	B2
8102814	Rahman et al.	Jan 2012	B2
8103285	Kalhan	Jan 2012	B2
8104080	Burns et al.	Jan 2012	B2
8107953	Zimmerman et al.	Jan 2012	B2
8108520	Ruutu et al.	Jan 2012	B2
8112435	Epstein et al.	Feb 2012	B2
8116223	Tian et al.	Feb 2012	B2
8116749	Proctor, Jr. et al.	Feb 2012	B2
8116781	Chen et al.	Feb 2012	B2
8122128	Burke, II et al.	Feb 2012	B2
8122249	Falk et al.	Feb 2012	B2
8125897	Ray et al.	Feb 2012	B2
8126123	Cai et al.	Feb 2012	B2
8126396	Bennett	Feb 2012	B2
8126476	Vardi et al.	Feb 2012	B2
8126722	Robb et al.	Feb 2012	B2
8130793	Edwards et al.	Mar 2012	B2
8131256	Martti et al.	Mar 2012	B2
8131281	Hildner et al.	Mar 2012	B1
8131840	Denker	Mar 2012	B1
8131858	Agulnik et al.	Mar 2012	B2
8132256	Bari	Mar 2012	B2
8134954	Godfrey et al.	Mar 2012	B2
8135388	Gailloux et al.	Mar 2012	B1
8135392	Marcellino et al.	Mar 2012	B2
8135657	Kapoor et al.	Mar 2012	B2
8140690	Ly et al.	Mar 2012	B2
8144591	Ghai et al.	Mar 2012	B2
8145194	Yoshikawa et al.	Mar 2012	B2
8146142	Lortz et al.	Mar 2012	B2
8149748	Bata et al.	Apr 2012	B2
8149823	Turcan et al.	Apr 2012	B2
8150394	Bianconi et al.	Apr 2012	B2
8150431	Wolovitz et al.	Apr 2012	B2
8151205	Follmann et al.	Apr 2012	B2
8155155	Chow et al.	Apr 2012	B1
8155620	Wang et al.	Apr 2012	B2
8155666	Alizadeh-Shabdiz	Apr 2012	B2
8155670	Fullam et al.	Apr 2012	B2
8156206	Kiley et al.	Apr 2012	B2
8159520	Dhanoa et al.	Apr 2012	B1
8160015	Rashid et al.	Apr 2012	B2
8160056	Van der Merwe et al.	Apr 2012	B2
8160598	Savoor	Apr 2012	B2
8165576	Raju et al.	Apr 2012	B2
8166040	Brindisi et al.	Apr 2012	B2
8166554	John	Apr 2012	B2
8170553	Bennett	May 2012	B2
8174378	Richman et al.	May 2012	B2
8174970	Adamczyk et al.	May 2012	B2
8175574	Panda et al.	May 2012	B1
8180333	Wells et al.	May 2012	B1
8180881	Seo et al.	May 2012	B2
8180886	Overcash et al.	May 2012	B2
8184530	Swan et al.	May 2012	B1
8184590	Rosenblatt	May 2012	B2
8185088	Klein et al.	May 2012	B2
8185093	Jheng et al.	May 2012	B2
8185127	Cai et al.	May 2012	B1
8185152	Goldner	May 2012	B1
8185158	Tamura et al.	May 2012	B2
8190087	Fisher et al.	May 2012	B2
8190122	Alexander et al.	May 2012	B1
8190675	Tribbett	May 2012	B2
8191106	Choyi et al.	May 2012	B2
8191116	Gazzard	May 2012	B1
8191124	Wynn et al.	May 2012	B2
8194549	Huber et al.	Jun 2012	B2
8194553	Liang et al.	Jun 2012	B2
8194572	Horvath et al.	Jun 2012	B2
8194581	Schroeder et al.	Jun 2012	B1
8195093	Garrett et al.	Jun 2012	B2
8195153	Frencel et al.	Jun 2012	B1
8195163	Gisby et al.	Jun 2012	B2
8195661	Kalavade	Jun 2012	B2
8196199	Hrastar et al.	Jun 2012	B2
8200163	Hoffman	Jun 2012	B2
8200200	Belser et al.	Jun 2012	B1
8200509	Kenedy et al.	Jun 2012	B2
8200775	Moore	Jun 2012	B2
8200818	Freund et al.	Jun 2012	B2
8204190	Bang et al.	Jun 2012	B2
8204505	Jin et al.	Jun 2012	B2
8204794	Peng et al.	Jun 2012	B1
8208788	Ando et al.	Jun 2012	B2
8208919	Kotecha	Jun 2012	B2
8213296	Shannon et al.	Jul 2012	B2
8213363	Ying et al.	Jul 2012	B2
8214536	Zhao	Jul 2012	B2
8214890	Kirovski et al.	Jul 2012	B2
8219134	Maharajh et al.	Jul 2012	B2
8223655	Heinz et al.	Jul 2012	B2
8223741	Bartlett et al.	Jul 2012	B1
8224382	Bultman	Jul 2012	B2
8224773	Spiegel	Jul 2012	B2
8228818	Chase et al.	Jul 2012	B2
8229394	Karlberg	Jul 2012	B2
8229914	Ramer et al.	Jul 2012	B2
8230061	Hassan et al.	Jul 2012	B2
8233433	Kalhan	Jul 2012	B2
8233883	De Froment	Jul 2012	B2
8233895	Tysowski	Jul 2012	B2
8234583	Sloo et al.	Jul 2012	B2
8238287	Gopi et al.	Aug 2012	B1
8239520	Grah	Aug 2012	B2
8242959	Mia et al.	Aug 2012	B2
8244241	Montemurro	Aug 2012	B2
8249601	Emberson et al.	Aug 2012	B2
8254880	Aaltonen et al.	Aug 2012	B2
8254915	Kozisek	Aug 2012	B2
8255515	Melman et al.	Aug 2012	B1
8255534	Assadzadeh	Aug 2012	B2
8255689	Kim et al.	Aug 2012	B2
8259692	Bajko	Sep 2012	B2
8264965	Dolganow et al.	Sep 2012	B2
8265004	Toutonghi	Sep 2012	B2
8266681	Deshpande et al.	Sep 2012	B2
8270955	Ramer et al.	Sep 2012	B2
8270972	Otting et al.	Sep 2012	B2
8271025	Brisebois et al.	Sep 2012	B2
8271045	Parolkar et al.	Sep 2012	B2
8271049	Silver et al.	Sep 2012	B2
8271992	Chatley et al.	Sep 2012	B2
8275415	Huslak	Sep 2012	B2
8275830	Raleigh	Sep 2012	B2
8279067	Berger et al.	Oct 2012	B2
8279864	Wood	Oct 2012	B2
8280351	Ahmed et al.	Oct 2012	B1
8280354	Smith et al.	Oct 2012	B2
8284740	O'Connor	Oct 2012	B2
8285249	Baker et al.	Oct 2012	B2
8285992	Mathur et al.	Oct 2012	B2
8291238	Ginter et al.	Oct 2012	B2
8291439	Jethi et al.	Oct 2012	B2
8296404	McDysan et al.	Oct 2012	B2
8300575	Willars	Oct 2012	B2
8301513	Peng et al.	Oct 2012	B1
8306518	Gailloux	Nov 2012	B1
8306741	Tu	Nov 2012	B2
8307067	Ryan	Nov 2012	B2
8307095	Clark et al.	Nov 2012	B2
8315198	Corneille et al.	Nov 2012	B2
8315593	Gallant et al.	Nov 2012	B2
8315594	Mauser et al.	Nov 2012	B1
8315718	Caffrey et al.	Nov 2012	B2
8315999	Chatley et al.	Nov 2012	B2
8320244	Muqattash et al.	Nov 2012	B2
8320902	Moring et al.	Nov 2012	B2
8320949	Matta	Nov 2012	B2
8325638	Jin et al.	Dec 2012	B2
8325906	Fullarton et al.	Dec 2012	B2
8326319	Davis	Dec 2012	B2
8326359	Kauffman	Dec 2012	B2
8326828	Zhou et al.	Dec 2012	B2
8331223	Hill et al.	Dec 2012	B2
8331293	Sood	Dec 2012	B2
8332375	Chatley et al.	Dec 2012	B2
8332517	Russell	Dec 2012	B2
8335161	Foottit et al.	Dec 2012	B2
8339991	Biswas et al.	Dec 2012	B2
8340625	Johnson et al.	Dec 2012	B1
8340628	Taylor et al.	Dec 2012	B2
8340678	Pandey	Dec 2012	B1
8340718	Colonna et al.	Dec 2012	B2
8346210	Balsan et al.	Jan 2013	B2
8346923	Rowles et al.	Jan 2013	B2
8347104	Pathiyal	Jan 2013	B2
8347362	Cai et al.	Jan 2013	B2
8347378	Merkin et al.	Jan 2013	B2
8350700	Fast et al.	Jan 2013	B2
8351592	Freeny, Jr. et al.	Jan 2013	B2
8351898	Raleigh	Jan 2013	B2
8352360	De Judicibus et al.	Jan 2013	B2
8352630	Hart	Jan 2013	B2
8352980	Howcroft	Jan 2013	B2
8353001	Herrod	Jan 2013	B2
8355570	Karsanbhai et al.	Jan 2013	B2
8355696	Olding et al.	Jan 2013	B1
8356336	Johnston et al.	Jan 2013	B2
8358638	Scherzer et al.	Jan 2013	B2
8358975	Bahl et al.	Jan 2013	B2
8363658	Delker et al.	Jan 2013	B1
8363799	Gruchala et al.	Jan 2013	B2
8364089	Phillips	Jan 2013	B2
8364806	Short et al.	Jan 2013	B2
8369274	Sawai	Feb 2013	B2
8370477	Short et al.	Feb 2013	B2
8370483	Choong et al.	Feb 2013	B2
8374090	Morrill et al.	Feb 2013	B2
8374592	Proctor, Jr. et al.	Feb 2013	B2
8375128	Tofighbakhsh et al.	Feb 2013	B2
8375136	Roman et al.	Feb 2013	B2
8379847	Bell et al.	Feb 2013	B2
8380247	Engstrom	Feb 2013	B2
8385199	Coward et al.	Feb 2013	B1
8385896	Proctor, Jr. et al.	Feb 2013	B2
8385964	Haney	Feb 2013	B2
8385975	Forutanpour	Feb 2013	B2
8386386	Zhu	Feb 2013	B1
8391262	Maki et al.	Mar 2013	B2
8391834	Raleigh	Mar 2013	B2
8392982	Harris et al.	Mar 2013	B2
8396458	Raleigh	Mar 2013	B2
8396929	Helfman et al.	Mar 2013	B2
8401968	Schattauer et al.	Mar 2013	B1
8402165	Deu-Ngoc et al.	Mar 2013	B2
8402540	Kapoor et al.	Mar 2013	B2
8406427	Chand et al.	Mar 2013	B2
8406736	Das et al.	Mar 2013	B2
8407472	Hao et al.	Mar 2013	B2
8407763	Weller et al.	Mar 2013	B2
8411587	Curtis et al.	Apr 2013	B2
8411691	Aggarwal	Apr 2013	B2
8412798	Wang	Apr 2013	B1
8413245	Kraemer et al.	Apr 2013	B2
8418168	Tyhurst et al.	Apr 2013	B2
8422988	Keshav	Apr 2013	B1
8423016	Buckley et al.	Apr 2013	B2
8429403	Moret et al.	Apr 2013	B2
8429409	Wall et al.	Apr 2013	B1
8437734	Ray et al.	May 2013	B2
8441955	Wilkinson et al.	May 2013	B2
8442015	Behzad et al.	May 2013	B2
8446831	Kwan et al.	May 2013	B2
8447324	Shuman et al.	May 2013	B2
8447607	Weider et al.	May 2013	B2
8447980	Godfrey et al.	May 2013	B2
8448015	Gerhart	May 2013	B2
8452858	Wu et al.	May 2013	B2
8461958	Saenz et al.	Jun 2013	B2
8463232	Tuli et al.	Jun 2013	B2
8468337	Gaur et al.	Jun 2013	B2
8472371	Bari et al.	Jun 2013	B1
8477778	Lehmann, Jr. et al.	Jul 2013	B2
8483135	Cai et al.	Jul 2013	B2
8483694	Lewis et al.	Jul 2013	B2
8484327	Werner et al.	Jul 2013	B2
8484568	Rados et al.	Jul 2013	B2
8488597	Nie et al.	Jul 2013	B2
8489110	Frank et al.	Jul 2013	B2
8489720	Morford et al.	Jul 2013	B1
8494559	Malmi	Jul 2013	B1
8495181	Venkatraman et al.	Jul 2013	B2
8495227	Kaminsky et al.	Jul 2013	B2
8495360	Falk et al.	Jul 2013	B2
8495700	Shahbazi	Jul 2013	B2
8495743	Kraemer et al.	Jul 2013	B2
8499087	Hu	Jul 2013	B2
8571598	Valavi	Jul 2013	B2
RE44412	Naqvi et al.	Aug 2013	E
8503358	Hanson et al.	Aug 2013	B2
8503455	Heikens	Aug 2013	B2
8504032	Lott et al.	Aug 2013	B2
8504574	Dvorak et al.	Aug 2013	B2
8504687	Maffione et al.	Aug 2013	B2
8504690	Shah et al.	Aug 2013	B2
8504729	Pezzutti	Aug 2013	B2
8505073	Taglienti et al.	Aug 2013	B2
8509082	Heinz et al.	Aug 2013	B2
8514927	Sundararajan et al.	Aug 2013	B2
8516552	Raleigh	Aug 2013	B2
8520589	Bhatt et al.	Aug 2013	B2
8520595	Yadav et al.	Aug 2013	B2
8521110	Rofougaran	Aug 2013	B2
8521775	Poh et al.	Aug 2013	B1
8522039	Hyndman et al.	Aug 2013	B2
8522249	Beaule	Aug 2013	B2
8522337	Adusumilli et al.	Aug 2013	B2
8523547	Pekrul	Sep 2013	B2
8526329	Mahany	Sep 2013	B2
8527410	Markki et al.	Sep 2013	B2
8527662	Biswas et al.	Sep 2013	B2
8528068	Weglein et al.	Sep 2013	B1
8531954	McNaughton et al.	Sep 2013	B2
8531995	Khan et al.	Sep 2013	B2
8532610	Manning Cassett et al.	Sep 2013	B2
8533775	Alcorn et al.	Sep 2013	B2
8538394	Zimmerman et al.	Sep 2013	B2
8538421	Brisebois et al.	Sep 2013	B2
8538458	Haney	Sep 2013	B2
8539544	Garimella et al.	Sep 2013	B2
8539561	Gupta et al.	Sep 2013	B2
8543265	Ekhaguere et al.	Sep 2013	B2
8543814	Laitinen et al.	Sep 2013	B2
8544105	McIean et al.	Sep 2013	B2
8548427	Chow et al.	Oct 2013	B2
8548428	Raleigh	Oct 2013	B2
8549173	Wu et al.	Oct 2013	B1
8554876	Winsor	Oct 2013	B2
8559369	Barkan	Oct 2013	B2
8565746	Hoffman	Oct 2013	B2
8566236	Busch	Oct 2013	B2
8571474	Chavez et al.	Oct 2013	B2
8571501	Miller et al.	Oct 2013	B2
8571993	Kocher et al.	Oct 2013	B2
8572117	Rappaport	Oct 2013	B2
8572256	Babbar	Oct 2013	B2
8583499	De Judicibus et al.	Nov 2013	B2
8588240	Ramankutty et al.	Nov 2013	B2
8589541	Raleigh et al.	Nov 2013	B2
8589955	Roundtree et al.	Nov 2013	B2
8594665	Anschutz	Nov 2013	B2
8600895	Felsher	Dec 2013	B2
8601125	Huang et al.	Dec 2013	B2
8605691	Soomro et al.	Dec 2013	B2
8619735	Montemurro et al.	Dec 2013	B2
8620257	Qiu et al.	Dec 2013	B2
8621056	Coussemaeker et al.	Dec 2013	B2
8626115	Raleigh et al.	Jan 2014	B2
8630314	York	Jan 2014	B2
8631428	Scott et al.	Jan 2014	B2
8634425	Gorti et al.	Jan 2014	B2
8635164	Rosenhaft et al.	Jan 2014	B2
8639215	McGregor et al.	Jan 2014	B2
8644702	Kalajan	Feb 2014	B1
8644813	Gailloux et al.	Feb 2014	B1
8645518	David	Feb 2014	B2
8655357	Gazzard et al.	Feb 2014	B1
8660853	Robb et al.	Feb 2014	B2
8666395	Silver	Mar 2014	B2
8667542	Bertz et al.	Mar 2014	B1
8670334	Keohane et al.	Mar 2014	B2
8670752	Fan et al.	Mar 2014	B2
8675852	Maes	Mar 2014	B2
8676682	Kalliola	Mar 2014	B2
8676925	Liu et al.	Mar 2014	B1
8693323	McDysan	Apr 2014	B1
8694772	Kao et al.	Apr 2014	B2
8700729	Dua	Apr 2014	B2
8701015	Bonnat	Apr 2014	B2
8705361	Venkataraman et al.	Apr 2014	B2
8706863	Fadell	Apr 2014	B2
8713535	Malhotra et al.	Apr 2014	B2
8713641	Pagan et al.	Apr 2014	B1
8719397	Levi et al.	May 2014	B2
8719423	Wyld	May 2014	B2
8725899	Short et al.	May 2014	B2
8730842	Collins et al.	May 2014	B2
8731519	Flynn et al.	May 2014	B2
8732808	Sewall et al.	May 2014	B2
8739035	Trethewey	May 2014	B2
8744339	Halfmann et al.	Jun 2014	B2
8761711	Grignani et al.	Jun 2014	B2
8780857	Balasubramanian et al.	Jul 2014	B2
8787249	Giaretta et al.	Jul 2014	B2
8793304	Lu et al.	Jul 2014	B2
8804517	Oerton	Aug 2014	B2
8811338	Jin et al.	Aug 2014	B2
8811991	Jain et al.	Aug 2014	B2
8812525	Taylor, III	Aug 2014	B1
8818394	Bienas et al.	Aug 2014	B2
8819253	Simeloff et al.	Aug 2014	B2
8825109	Montemurro et al.	Sep 2014	B2
8826411	Moen et al.	Sep 2014	B2
8831561	Sutaria et al.	Sep 2014	B2
8837322	Venkataramanan et al.	Sep 2014	B2
8838686	Getchius	Sep 2014	B2
8838752	Lor et al.	Sep 2014	B2
8843849	Neil et al.	Sep 2014	B2
8849297	Balasubramanian	Sep 2014	B2
8855620	Sievers et al.	Oct 2014	B2
8862751	Faccin et al.	Oct 2014	B2
8863111	Selitser et al.	Oct 2014	B2
8868725	Samba	Oct 2014	B2
8868727	Yumerefendi et al.	Oct 2014	B2
8875042	Lejeune et al.	Oct 2014	B2
8880047	Konicek et al.	Nov 2014	B2
8891483	Connelly et al.	Nov 2014	B2
8898748	Burks et al.	Nov 2014	B2
8908516	Tzamaloukas et al.	Dec 2014	B2
8929374	Tönsing et al.	Jan 2015	B2
8930238	Coffman et al.	Jan 2015	B2
8943551	Ganapathy et al.	Jan 2015	B2
8948726	Smith et al.	Feb 2015	B2
8949597	Reeves et al.	Feb 2015	B1
8966018	Bugwadia et al.	Feb 2015	B2
8971841	Menezes et al.	Mar 2015	B2
8971912	Chou et al.	Mar 2015	B2
8972537	Bastian et al.	Mar 2015	B2
8977284	Reed	Mar 2015	B2
8995952	Baker et al.	Mar 2015	B1
9002342	Tenhunen et al.	Apr 2015	B2
9014973	Ruckart	Apr 2015	B2
9015331	Lai et al.	Apr 2015	B2
9030934	Shah et al.	May 2015	B2
9032427	Gallant et al.	May 2015	B2
9049010	Jueneman et al.	Jun 2015	B2
9064275	Lu et al.	Jun 2015	B1
9111088	Ghai et al.	Aug 2015	B2
9135037	Petrescu-Prahova et al.	Sep 2015	B1
9137286	Yuan	Sep 2015	B1
9172553	Dawes et al.	Oct 2015	B2
9173090	Tuchman et al.	Oct 2015	B2
9176913	Millet et al.	Nov 2015	B2
9177455	Remer	Nov 2015	B2
9282460	Souissi	Mar 2016	B2
9286469	Kraemer et al.	Mar 2016	B2
9286604	Aabye et al.	Mar 2016	B2
9325737	Gutowski et al.	Apr 2016	B2
9326173	Luft	Apr 2016	B2
9344557	Gruchala et al.	May 2016	B2
9367680	Mahaffey et al.	Jun 2016	B2
9402254	Kneckt et al.	Jul 2016	B2
9413546	Meier et al.	Aug 2016	B2
9589117	Ali et al.	Mar 2017	B2
9609459	Raleigh	Mar 2017	B2
9634850	Taft et al.	Apr 2017	B2
20010048738	Baniak et al.	Dec 2001	A1
20010053694	Igarashi et al.	Dec 2001	A1
20020022472	Watler et al.	Feb 2002	A1
20020049074	Eisinger et al.	Apr 2002	A1
20020099848	Lee	Jul 2002	A1
20020116338	Gonthier et al.	Aug 2002	A1
20020120370	Parupudi et al.	Aug 2002	A1
20020120540	Kende et al.	Aug 2002	A1
20020131404	Mehta et al.	Sep 2002	A1
20020138599	Dilman et al.	Sep 2002	A1
20020138601	Piponius et al.	Sep 2002	A1
20020154751	Thompson et al.	Oct 2002	A1
20020161601	Nauer et al.	Oct 2002	A1
20020164983	Raviv et al.	Nov 2002	A1
20020176377	Hamilton	Nov 2002	A1
20020188732	Buckman et al.	Dec 2002	A1
20020191573	Whitehill et al.	Dec 2002	A1
20020199001	Wenocur et al.	Dec 2002	A1
20030004937	Salmenkaita et al.	Jan 2003	A1
20030005112	Krautkremer	Jan 2003	A1
20030013434	Rosenberg et al.	Jan 2003	A1
20030018524	Fishman et al.	Jan 2003	A1
20030028623	Hennessey et al.	Feb 2003	A1
20030046396	Richter et al.	Mar 2003	A1
20030050070	Mashinsky et al.	Mar 2003	A1
20030050837	Kim	Mar 2003	A1
20030084321	Tarquini et al.	May 2003	A1
20030088671	Klinker et al.	May 2003	A1
20030133408	Cheng et al.	Jul 2003	A1
20030134650	Sundar et al.	Jul 2003	A1
20030159030	Evans	Aug 2003	A1
20030161265	Cao et al.	Aug 2003	A1
20030171112	Lupper et al.	Sep 2003	A1
20030182420	Jones et al.	Sep 2003	A1
20030182435	Redlich et al.	Sep 2003	A1
20030184793	Pineau	Oct 2003	A1
20030188006	Bard	Oct 2003	A1
20030188117	Yoshino et al.	Oct 2003	A1
20030220984	Jones et al.	Nov 2003	A1
20030224781	Milford et al.	Dec 2003	A1
20030229900	Reisman	Dec 2003	A1
20030233332	Keeler et al.	Dec 2003	A1
20030236745	Hartsell et al.	Dec 2003	A1
20040019539	Raman et al.	Jan 2004	A1
20040021697	Beaton et al.	Feb 2004	A1
20040024756	Rickard	Feb 2004	A1
20040030705	Bowman-Amuah	Feb 2004	A1
20040039792	Nakanishi	Feb 2004	A1
20040044623	Wake et al.	Mar 2004	A1
20040047358	Chen et al.	Mar 2004	A1
20040054779	Takeshima et al.	Mar 2004	A1
20040073672	Fascenda	Apr 2004	A1
20040082346	Skytt et al.	Apr 2004	A1
20040098715	Aghera et al.	May 2004	A1
20040102182	Reith et al.	May 2004	A1
20040103193	Pandya et al.	May 2004	A1
20040107360	Herrmann et al.	Jun 2004	A1
20040127200	Shaw et al.	Jul 2004	A1
20040127208	Nair et al.	Jul 2004	A1
20040132427	Lee et al.	Jul 2004	A1
20040133668	Nicholas, III	Jul 2004	A1
20040137890	Kalke	Jul 2004	A1
20040168052	Clisham et al.	Aug 2004	A1
20040170191	Guo et al.	Sep 2004	A1
20040176104	Arcens	Sep 2004	A1
20040198331	Coward et al.	Oct 2004	A1
20040203755	Brunet et al.	Oct 2004	A1
20040203833	Rathunde et al.	Oct 2004	A1
20040225561	Hertzberg et al.	Nov 2004	A1
20040225898	Frost et al.	Nov 2004	A1
20040236547	Rappaport et al.	Nov 2004	A1
20040243680	Mayer	Dec 2004	A1
20040243992	Gustafson et al.	Dec 2004	A1
20040249918	Sunshine	Dec 2004	A1
20040255145	Chow	Dec 2004	A1
20040259534	Chaudhari et al.	Dec 2004	A1
20040260766	Barros et al.	Dec 2004	A1
20040267872	Serdy et al.	Dec 2004	A1
20050007993	Chambers et al.	Jan 2005	A1
20050009499	Koster	Jan 2005	A1
20050021995	Lal et al.	Jan 2005	A1
20050041617	Huotari et al.	Feb 2005	A1
20050048950	Morper	Mar 2005	A1
20050055291	Bevente et al.	Mar 2005	A1
20050055309	Williams et al.	Mar 2005	A1
20050055595	Frazer et al.	Mar 2005	A1
20050060266	Demello et al.	Mar 2005	A1
20050060525	Schwartz et al.	Mar 2005	A1
20050075115	Corneille et al.	Apr 2005	A1
20050079863	Macaluso	Apr 2005	A1
20050091505	Riley et al.	Apr 2005	A1
20050096024	Bicker et al.	May 2005	A1
20050097516	Donnelly et al.	May 2005	A1
20050107091	Vannithamby et al.	May 2005	A1
20050108075	Douglis et al.	May 2005	A1
20050111463	Leung et al.	May 2005	A1
20050128967	Scobbie	Jun 2005	A1
20050135264	Popoff et al.	Jun 2005	A1
20050163320	Brown et al.	Jul 2005	A1
20050166043	Zhang et al.	Jul 2005	A1
20050183143	Anderholm et al.	Aug 2005	A1
20050186948	Gallagher et al.	Aug 2005	A1
20050198377	Ferguson et al.	Sep 2005	A1
20050216421	Barry et al.	Sep 2005	A1
20050228985	Ylikoski et al.	Oct 2005	A1
20050238046	Hassan et al.	Oct 2005	A1
20050239447	Holzman et al.	Oct 2005	A1
20050245241	Durand et al.	Nov 2005	A1
20050246282	Naslund et al.	Nov 2005	A1
20050250508	Guo et al.	Nov 2005	A1
20050250536	Deng et al.	Nov 2005	A1
20050254435	Moakley et al.	Nov 2005	A1
20050266825	Clayton	Dec 2005	A1
20050266880	Gupta	Dec 2005	A1
20060014519	Marsh et al.	Jan 2006	A1
20060019632	Cunningham et al.	Jan 2006	A1
20060020787	Choyi et al.	Jan 2006	A1
20060026679	Zakas	Feb 2006	A1
20060030306	Kuhn	Feb 2006	A1
20060034256	Addagatla et al.	Feb 2006	A1
20060035631	White et al.	Feb 2006	A1
20060040642	Boris et al.	Feb 2006	A1
20060045245	Aaron et al.	Mar 2006	A1
20060048223	Lee et al.	Mar 2006	A1
20060068796	Millen et al.	Mar 2006	A1
20060072451	Ross	Apr 2006	A1
20060072550	Davis et al.	Apr 2006	A1
20060072646	Feher	Apr 2006	A1
20060075506	Sanda et al.	Apr 2006	A1
20060085543	Hrastar et al.	Apr 2006	A1
20060095517	O'Connor et al.	May 2006	A1
20060098627	Karaoguz et al.	May 2006	A1
20060099970	Morgan et al.	May 2006	A1
20060101507	Camenisch	May 2006	A1
20060112016	Ishibashi	May 2006	A1
20060114821	Willey et al.	Jun 2006	A1
20060114832	Hamilton et al.	Jun 2006	A1
20060126562	Liu	Jun 2006	A1
20060135144	Jothipragasam	Jun 2006	A1
20060136882	Noonan et al.	Jun 2006	A1
20060143066	Calabria	Jun 2006	A1
20060143098	Lazaridis	Jun 2006	A1
20060156398	Ross et al.	Jul 2006	A1
20060160536	Chou	Jul 2006	A1
20060165060	Dua	Jul 2006	A1
20060168128	Sistla et al.	Jul 2006	A1
20060173959	McKelvie et al.	Aug 2006	A1
20060174035	Tufail	Aug 2006	A1
20060178917	Merriam et al.	Aug 2006	A1
20060178918	Mikurak	Aug 2006	A1
20060182137	Zhou et al.	Aug 2006	A1
20060183462	Kolehmainen	Aug 2006	A1
20060190314	Hernandez	Aug 2006	A1
20060190987	Ohta et al.	Aug 2006	A1
20060199608	Dunn et al.	Sep 2006	A1
20060200663	Thornton	Sep 2006	A1
20060206709	Labrou et al.	Sep 2006	A1
20060206904	Watkins et al.	Sep 2006	A1
20060218395	Maes	Sep 2006	A1
20060233108	Krishnan	Oct 2006	A1
20060233166	Bou-Diab et al.	Oct 2006	A1
20060236095	Smith et al.	Oct 2006	A1
20060242685	Heard et al.	Oct 2006	A1
20060258341	Miller et al.	Nov 2006	A1
20060277590	Limont et al.	Dec 2006	A1
20060291419	McConnell et al.	Dec 2006	A1
20060291477	Croak et al.	Dec 2006	A1
20070005795	Gonzalez	Jan 2007	A1
20070019670	Falardeau	Jan 2007	A1
20070022289	Alt et al.	Jan 2007	A1
20070025301	Petersson et al.	Feb 2007	A1
20070033194	Srinivas et al.	Feb 2007	A1
20070033197	Scherzer et al.	Feb 2007	A1
20070036312	Cai et al.	Feb 2007	A1
20070055694	Ruge et al.	Mar 2007	A1
20070060200	Boris et al.	Mar 2007	A1
20070061243	Ramer et al.	Mar 2007	A1
20070061800	Cheng et al.	Mar 2007	A1
20070061878	Hagiu et al.	Mar 2007	A1
20070073899	Judge et al.	Mar 2007	A1
20070076616	Ngo et al.	Apr 2007	A1
20070093243	Kapadekar et al.	Apr 2007	A1
20070100981	Adamczyk et al.	May 2007	A1
20070101426	Lee et al.	May 2007	A1
20070104126	Calhoun et al.	May 2007	A1
20070109983	Shankar et al.	May 2007	A1
20070130283	Klein et al.	Jun 2007	A1
20070130315	Friend et al.	Jun 2007	A1
20070140113	Gemelos	Jun 2007	A1
20070140145	Kumar et al.	Jun 2007	A1
20070140275	Bowman et al.	Jun 2007	A1
20070143824	Shahbazi	Jun 2007	A1
20070147317	Smith et al.	Jun 2007	A1
20070147324	McGary	Jun 2007	A1
20070155365	Kim et al.	Jul 2007	A1
20070165630	Rasanen	Jul 2007	A1
20070168499	Chu	Jul 2007	A1
20070171856	Bruce et al.	Jul 2007	A1
20070174490	Choi et al.	Jul 2007	A1
20070192460	Choi et al.	Aug 2007	A1
20070198656	Mazzaferri et al.	Aug 2007	A1
20070201502	Abramson	Aug 2007	A1
20070213054	Han	Sep 2007	A1
20070220251	Rosenberg et al.	Sep 2007	A1
20070226225	Yiu et al.	Sep 2007	A1
20070226775	Andreasen et al.	Sep 2007	A1
20070234402	Khosravi et al.	Oct 2007	A1
20070243862	Coskun et al.	Oct 2007	A1
20070248100	Zuberi et al.	Oct 2007	A1
20070254675	Zorlu Ozer et al.	Nov 2007	A1
20070255769	Agrawal et al.	Nov 2007	A1
20070255797	Dunn et al.	Nov 2007	A1
20070255848	Sewall et al.	Nov 2007	A1
20070257767	Beeson	Nov 2007	A1
20070259656	Jeong	Nov 2007	A1
20070259673	Willars et al.	Nov 2007	A1
20070263558	Salomone	Nov 2007	A1
20070266422	Germano et al.	Nov 2007	A1
20070274327	Kaarela et al.	Nov 2007	A1
20070280453	Kelley	Dec 2007	A1
20070282896	Wydroug et al.	Dec 2007	A1
20070293191	Mir et al.	Dec 2007	A1
20070294395	Strub et al.	Dec 2007	A1
20070294410	Pandya et al.	Dec 2007	A1
20070297378	Poyhonen et al.	Dec 2007	A1
20070298764	Clayton	Dec 2007	A1
20070299965	Nieh et al.	Dec 2007	A1
20070300252	Acharya et al.	Dec 2007	A1
20080005285	Robinson et al.	Jan 2008	A1
20080005561	Brown et al.	Jan 2008	A1
20080010379	Zhao	Jan 2008	A1
20080010452	Holtzman et al.	Jan 2008	A1
20080018494	Waite et al.	Jan 2008	A1
20080022354	Grewal et al.	Jan 2008	A1
20080025230	Patel et al.	Jan 2008	A1
20080032715	Jia et al.	Feb 2008	A1
20080034063	Yee	Feb 2008	A1
20080034419	Mullick et al.	Feb 2008	A1
20080039102	Sewall et al.	Feb 2008	A1
20080049630	Kozisek et al.	Feb 2008	A1
20080050715	Golczewski et al.	Feb 2008	A1
20080051076	O'Shaughnessy et al.	Feb 2008	A1
20080052387	Heinz et al.	Feb 2008	A1
20080056273	Pelletier et al.	Mar 2008	A1
20080059474	Lim	Mar 2008	A1
20080059743	Bychkov et al.	Mar 2008	A1
20080060066	Wynn et al.	Mar 2008	A1
20080062900	Rao	Mar 2008	A1
20080064367	Nath et al.	Mar 2008	A1
20080066149	Lim	Mar 2008	A1
20080066150	Lim	Mar 2008	A1
20080066181	Haveson et al.	Mar 2008	A1
20080070550	Hose	Mar 2008	A1
20080077705	Li et al.	Mar 2008	A1
20080080457	Cole	Apr 2008	A1
20080081606	Cole	Apr 2008	A1
20080082643	Storrie et al.	Apr 2008	A1
20080083013	Soliman et al.	Apr 2008	A1
20080085707	Fadell	Apr 2008	A1
20080089295	Keeler et al.	Apr 2008	A1
20080089303	Wirtanen et al.	Apr 2008	A1
20080095339	Elliott et al.	Apr 2008	A1
20080096559	Phillips et al.	Apr 2008	A1
20080098062	Balia	Apr 2008	A1
20080109679	Wright et al.	May 2008	A1
20080120129	Seubert et al.	May 2008	A1
20080120668	Yau	May 2008	A1
20080120688	Qiu et al.	May 2008	A1
20080125079	O'Neil et al.	May 2008	A1
20080126287	Cox et al.	May 2008	A1
20080127304	Ginter et al.	May 2008	A1
20080130534	Tomioka	Jun 2008	A1
20080130656	Kim et al.	Jun 2008	A1
20080132201	Karlberg	Jun 2008	A1
20080132268	Choi-Grogan et al.	Jun 2008	A1
20080134330	Kapoor et al.	Jun 2008	A1
20080139210	Gisby et al.	Jun 2008	A1
20080147454	Walker et al.	Jun 2008	A1
20080160958	Abichandani et al.	Jul 2008	A1
20080162637	Adamczyk et al.	Jul 2008	A1
20080162704	Poplett et al.	Jul 2008	A1
20080164304	Narasimhan et al.	Jul 2008	A1
20080166993	Gautier et al.	Jul 2008	A1
20080167027	Gautier et al.	Jul 2008	A1
20080167033	Beckers	Jul 2008	A1
20080168275	DeAtley et al.	Jul 2008	A1
20080168523	Ansari et al.	Jul 2008	A1
20080177998	Apsangi et al.	Jul 2008	A1
20080178300	Brown et al.	Jul 2008	A1
20080183812	Paul et al.	Jul 2008	A1
20080184127	Rafey et al.	Jul 2008	A1
20080189760	Rosenberg et al.	Aug 2008	A1
20080201266	Chua et al.	Aug 2008	A1
20080207167	Bugenhagen	Aug 2008	A1
20080212470	Castaneda et al.	Sep 2008	A1
20080212751	Chung	Sep 2008	A1
20080219268	Dennison	Sep 2008	A1
20080221951	Stanforth et al.	Sep 2008	A1
20080222692	Andersson et al.	Sep 2008	A1
20080225748	Khemani et al.	Sep 2008	A1
20080229385	Feder et al.	Sep 2008	A1
20080229388	Maes	Sep 2008	A1
20080235511	O'Brien et al.	Sep 2008	A1
20080240373	Wilhelm	Oct 2008	A1
20080250053	Aaltonen et al.	Oct 2008	A1
20080256593	Vinberg et al.	Oct 2008	A1
20080259924	Gooch et al.	Oct 2008	A1
20080262798	Kim et al.	Oct 2008	A1
20080263348	Zaltsman et al.	Oct 2008	A1
20080268813	Maes	Oct 2008	A1
20080270212	Blight et al.	Oct 2008	A1
20080279216	Sharif-Ahmadi et al.	Nov 2008	A1
20080282319	Fontijn et al.	Nov 2008	A1
20080293395	Matthews et al.	Nov 2008	A1
20080298230	Luft et al.	Dec 2008	A1
20080305793	Gallagher et al.	Dec 2008	A1
20080311885	Dawson et al.	Dec 2008	A1
20080313315	Karaoguz et al.	Dec 2008	A1
20080313730	Iftimie et al.	Dec 2008	A1
20080316923	Fedders et al.	Dec 2008	A1
20080318547	Ballou et al.	Dec 2008	A1
20080318550	DeAtley	Dec 2008	A1
20080319879	Carroll et al.	Dec 2008	A1
20080320497	Tarkoma et al.	Dec 2008	A1
20090005000	Baker et al.	Jan 2009	A1
20090005005	Forstall et al.	Jan 2009	A1
20090006116	Baker et al.	Jan 2009	A1
20090006200	Baker et al.	Jan 2009	A1
20090006229	Sweeney et al.	Jan 2009	A1
20090013157	Beaule	Jan 2009	A1
20090016310	Rasal	Jan 2009	A1
20090036111	Danford et al.	Feb 2009	A1
20090042536	Bernard et al.	Feb 2009	A1
20090044185	Krivopaltsev	Feb 2009	A1
20090046707	Smires et al.	Feb 2009	A1
20090046723	Rahman et al.	Feb 2009	A1
20090047989	Harmon et al.	Feb 2009	A1
20090048913	Shenfield et al.	Feb 2009	A1
20090049156	Aronsson et al.	Feb 2009	A1
20090049518	Roman et al.	Feb 2009	A1
20090054030	Golds	Feb 2009	A1
20090065571	Jain	Mar 2009	A1
20090067372	Shah et al.	Mar 2009	A1
20090068984	Burnett	Mar 2009	A1
20090070379	Rappaport	Mar 2009	A1
20090077622	Baum et al.	Mar 2009	A1
20090079699	Sun	Mar 2009	A1
20090113514	Hu	Apr 2009	A1
20090125619	Antani	May 2009	A1
20090132860	Liu et al.	May 2009	A1
20090149154	Bhasin et al.	Jun 2009	A1
20090157792	Fiatal	Jun 2009	A1
20090163173	Williams	Jun 2009	A1
20090172077	Roxburgh et al.	Jul 2009	A1
20090180391	Petersen et al.	Jul 2009	A1
20090181662	Fleischman et al.	Jul 2009	A1
20090197585	Aaron	Aug 2009	A1
20090197612	Kiiskinen	Aug 2009	A1
20090203352	Fordon et al.	Aug 2009	A1
20090217364	Salmela et al.	Aug 2009	A1
20090219170	Clark et al.	Sep 2009	A1
20090248883	Suryanarayana et al.	Oct 2009	A1
20090254857	Romine et al.	Oct 2009	A1
20090257379	Robinson et al.	Oct 2009	A1
20090271514	Thomas et al.	Oct 2009	A1
20090282127	LeBlanc et al.	Nov 2009	A1
20090286507	O'Neil et al.	Nov 2009	A1
20090287921	Zhu et al.	Nov 2009	A1
20090288140	Huber et al.	Nov 2009	A1
20090291665	Gaskarth et al.	Nov 2009	A1
20090299857	Brubaker	Dec 2009	A1
20090307696	Vals et al.	Dec 2009	A1
20090307746	Di et al.	Dec 2009	A1
20090315735	Bhavani et al.	Dec 2009	A1
20090320110	Nicolson et al.	Dec 2009	A1
20100017506	Fadell	Jan 2010	A1
20100020822	Zerillo et al.	Jan 2010	A1
20100027469	Gurajala et al.	Feb 2010	A1
20100027559	Lin et al.	Feb 2010	A1
20100030890	Dutta et al.	Feb 2010	A1
20100041364	Lott et al.	Feb 2010	A1
20100041365	Lott et al.	Feb 2010	A1
20100042675	Fujii	Feb 2010	A1
20100043068	Varadhan et al.	Feb 2010	A1
20100071053	Ansari et al.	Mar 2010	A1
20100075666	Garner	Mar 2010	A1
20100080202	Hanson	Apr 2010	A1
20100082431	Ramer et al.	Apr 2010	A1
20100103820	Fuller et al.	Apr 2010	A1
20100121744	Belz et al.	May 2010	A1
20100131584	Johnson	May 2010	A1
20100144310	Bedingfield	Jun 2010	A1
20100151866	Karpov et al.	Jun 2010	A1
20100153781	Hanna	Jun 2010	A1
20100167696	Smith et al.	Jul 2010	A1
20100188975	Raleigh	Jul 2010	A1
20100188990	Raleigh	Jul 2010	A1
20100188992	Raleigh	Jul 2010	A1
20100188994	Raleigh	Jul 2010	A1
20100190469	Vanderveen et al.	Jul 2010	A1
20100191576	Raleigh	Jul 2010	A1
20100191612	Raleigh	Jul 2010	A1
20100191846	Raleigh	Jul 2010	A1
20100192170	Raleigh	Jul 2010	A1
20100192212	Raleigh	Jul 2010	A1
20100195503	Raleigh	Aug 2010	A1
20100197268	Raleigh	Aug 2010	A1
20100198698	Raleigh et al.	Aug 2010	A1
20100198939	Raleigh	Aug 2010	A1
20100235329	Koren et al.	Sep 2010	A1
20100241544	Benson et al.	Sep 2010	A1
20100248719	Scholaert	Sep 2010	A1
20100284327	Miklos	Nov 2010	A1
20100284388	Fantini et al.	Nov 2010	A1
20100287599	He	Nov 2010	A1
20100311402	Srinivasan et al.	Dec 2010	A1
20100318652	Samba	Dec 2010	A1
20100325420	Kanekar	Dec 2010	A1
20110004917	Saisa et al.	Jan 2011	A1
20110013569	Scherzer et al.	Jan 2011	A1
20110019574	Malomsoky et al.	Jan 2011	A1
20110081881	Baker et al.	Apr 2011	A1
20110082790	Baker et al.	Apr 2011	A1
20110110309	Bennett	May 2011	A1
20110126141	King et al.	May 2011	A1
20110145920	Mahaffey et al.	Jun 2011	A1
20110159818	Scherzer et al.	Jun 2011	A1
20110173678	Kaippallimalil et al.	Jul 2011	A1
20110177811	Heckman et al.	Jul 2011	A1
20110195700	Kukuchka et al.	Aug 2011	A1
20110238545	Fanaian et al.	Sep 2011	A1
20110241624	Park et al.	Oct 2011	A1
20110252430	Chapman et al.	Oct 2011	A1
20110264923	Kocher et al.	Oct 2011	A1
20110277019	Pritchard, Jr.	Nov 2011	A1
20120020296	Scherzer et al.	Jan 2012	A1
20120029718	Davis	Feb 2012	A1
20120101952	Raleigh et al.	Apr 2012	A1
20120108225	Luna et al.	May 2012	A1
20120144025	Melander et al.	Jun 2012	A1
20120155296	Kashanian	Jun 2012	A1
20120166364	Ahmad et al.	Jun 2012	A1
20120166604	Fortier et al.	Jun 2012	A1
20120196644	Scherzer et al.	Aug 2012	A1
20120238287	Scherzer	Sep 2012	A1
20120330792	Kashanian	Dec 2012	A1
20130024914	Ahmed et al.	Jan 2013	A1
20130029653	Baker et al.	Jan 2013	A1
20130030960	Kashanian	Jan 2013	A1
20130058274	Scherzer et al.	Mar 2013	A1
20130065555	Baker et al.	Mar 2013	A1
20130072177	Ross et al.	Mar 2013	A1
20130084835	Scherzer et al.	Apr 2013	A1
20130095787	Kashanian	Apr 2013	A1
20130103376	Gaddam et al.	Apr 2013	A1
20130111572	Gaddam et al.	May 2013	A1
20130117140	Kashanian	May 2013	A1
20130117382	Gaddam et al.	May 2013	A1
20130144789	Aaltonen et al.	Jun 2013	A1
20130149994	Gaddam et al.	Jun 2013	A1
20130183937	Neal et al.	Jul 2013	A1
20130326356	Zheng et al.	Dec 2013	A9
20140073291	Hildner et al.	Mar 2014	A1
20140241342	Constantinof	Aug 2014	A1

Foreign Referenced Citations (109)

Number	Date	Country
2688553	Dec 2008	CA
1310401	Feb 2000	CN
1345154	Apr 2002	CN
1508734	Jun 2004	CN
1538730	Oct 2004	CN
1567818	Jan 2005	CN
101035308	Mar 2006	CN
1801829	Jul 2006	CN
1802839	Jul 2006	CN
1889777	Jul 2006	CN
101155343	Sep 2006	CN
1867024	Nov 2006	CN
1878160	Dec 2006	CN
1878160	Dec 2006	CN
1937511	Mar 2007	CN
101123553	Sep 2007	CN
101080055	Nov 2007	CN
101115248	Jan 2008	CN
101127988	Feb 2008	CN
101183958	May 2008	CN
101335666	Dec 2008	CN
101341764	Jan 2009	CN
101815275	Aug 2010	CN
1098490	May 2001	EP
1289326	Mar 2003	EP
1463238	Sep 2004	EP
1503548	Feb 2005	EP
1545114	Jun 2005	EP
1545114	Jun 2005	EP
1739518	Jan 2007	EP
1772988	Apr 2007	EP
1850575	Oct 2007	EP
1887732	Feb 2008	EP
1887732	Feb 2008	EP
1942698	Jul 2008	EP
1978772	Oct 2008	EP
2007065	Dec 2008	EP
2007065	Dec 2008	EP
2026514	Feb 2009	EP
2466831	Jun 2012	EP
3148713	Mar 2001	JP
2005339247	Dec 2005	JP
2006-041989	Feb 2006	JP
2006155263	Jun 2006	JP
2006-197137	Jul 2006	JP
2006-344007	Dec 2006	JP
2007-318354	Dec 2007	JP
2008-301121	Dec 2008	JP
2009-111919	May 2009	JP
2009-212707	Sep 2009	JP
2009-218773	Sep 2009	JP
2009-232107	Oct 2009	JP
1998058505	Dec 1998	WO
1999027723	Jun 1999	WO
1999065185	Dec 1999	WO
0208863	Jan 2002	WO
2002045315	Jun 2002	WO
2002067616	Aug 2002	WO
2002067616	Aug 2002	WO
2002093877	Nov 2002	WO
2003014891	Feb 2003	WO
2003017063	Feb 2003	WO
2003017063	Feb 2003	WO
2003017065	Feb 2003	WO
2003017065	Feb 2003	WO
2003058880	Jul 2003	WO
2004028070	Apr 2004	WO
2004064306	Jul 2004	WO
2004077797	Sep 2004	WO
2004095753	Nov 2004	WO
2005008995	Jan 2005	WO
2005053335	Jun 2005	WO
2005083934	Sep 2005	WO
2006004467	Jan 2006	WO
2006004784	Jan 2006	WO
2006012610	Feb 2006	WO
2006050758	May 2006	WO
2006073837	Jul 2006	WO
2006077481	Jul 2006	WO
2006093961	Sep 2006	WO
2006120558	Nov 2006	WO
2006130960	Dec 2006	WO
2007001833	Jan 2007	WO
2007014630	Feb 2007	WO
2007018363	Feb 2007	WO
2007053848	May 2007	WO
2007068288	Jun 2007	WO
2007069245	Jun 2007	WO
2007097786	Aug 2007	WO
2007107701	Sep 2007	WO
2007120310	Oct 2007	WO
2007124279	Nov 2007	WO
2007126352	Nov 2007	WO
2007129180	Nov 2007	WO
2007133844	Nov 2007	WO
2008017837	Feb 2008	WO
2008051379	May 2008	WO
2008066419	Jun 2008	WO
2008080139	Jul 2008	WO
2008080430	Jul 2008	WO
2008099802	Aug 2008	WO
2009008817	Jan 2009	WO
2009091295	Jul 2009	WO
2010088413	Aug 2010	WO
2010128391	Nov 2010	WO
2011002450	Jan 2011	WO
2011002450	Jan 2011	WO
2011149532	Dec 2011	WO
2012047275	Apr 2012	WO

Non-Patent Literature Citations (70)

Entry
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and charging control architecture (Release 11),” 3GPP Standard; 3GPP TS 23.203 v11.6.0; Sophia Antipolis, France; pp. 1-177; Jun. 2012.
“End to End QoS Solution for Real-time Multimedia Application;” Computer Engineering and Applications, 2007, 43 (4): 155-159, by Tan Zu-guo, Wang Wen-juan; Information and Science School, Zhanjian Normal College, Zhan jiang, Guangdong 524048, China.
“ASA/PIX: Allow Split Tunneling for VPN Clients on the ASA Configuration Example,” Document ID 70917, Jan. 10, 2008.
VerizonWireless.com news, “Verizon Wireless Adds to Portfolio of Cosumer-Friendly Tools With Introduction of Usage Controls, Usage Controls and Chaperone 2.0 Offer Parents Full Family Security Solution,” Aug. 18, 2008.
“The Construction of Intelligent Residential District in Use of Cable Television Network,” Shandong Science, vol. 13, No. 2, Jun. 2000.
“Communication Concepts for Mobile Agent Systems,” by Joachim Baumann et al.; Inst. Of Parallel and Distributed High-Performance Systems, Univ. of Stuttgart, Germany, pp. 123-135, 1997.
“Prevent iCloud Documents & Data from using your data plan,” Oct. 26, 2011; CNET webarchive, by Jason Ciprian.
Dixon et al., Triple Play Digital Services: Comcast and Verizon (Digital Phone, Television, and Internet), Aug. 2007.
3rd Generation Partnership Project; “Technical Specification Group Services and System Aspects; IP Flow Mobility and seamless WLAN offlload; Stage 2,” Release 10, Document No. 3GPP TS 23.261, V1.0.0, Mar. 2010.
3rd Generation Partnership Project, “Technical Specification Group Core Network and Terminals; Access Network Discovery and Selection Function (ANDSF) Management Object (MO),” Release 9, Document No. 3GPP TS 24.312, V9.1.0, Mar. 2010.
Ahmed et al., “Multi Access Data Network Connectivity and IP Flow Mobility in Evolved Packet System (EPS),” 2010 IEEE.
Li, Yu, “Dedicated E-Reading Device: The State of the Art and the Challenges,” Scroll, vol. 1, No. 1, 2008.
Nilsson et al., “A Novel MAC Scheme for Solving the QoS Parameter Adjustment Problem in IEEE802.11e EDCA,” Feb. 2006.
Oppliger, Rolf, “Internet Security: Firewalls and Bey,” Communications of the ACM, May 1997, vol. 40. No. 5.
Rao et al., “Evolution of Mobile Location-Based Services,” Communication of the ACM, Dec. 2003.
Steglich, Stephan, “I-Centric User Interaction,” Nov. 21, 2003.
Van Eijk, et al., “GigaMobile, Agent Technology for Designing Personalized Mobile Service Brokerage,” Jul. 1, 2002.
Zhu et al., “A Survey of Quality of Service in IEEE 802.11 Networks,” IEEE Wireless Communications, Aug. 2004.
Anton, B. et al., “Best Current Practices for Wireless Internet Service Provider (WISP) Roaming”; Release Date Feb. 2003, Version 1.0; Wi-Fi Alliance—Wireless ISP Roaming (WISPr).
Ruckus Wireless—White Paper; “Smarter Wi-Fi for Mobile Operator Infrastructures” 2010.
Accuris Networks, “The Business Value of Mobile Data Offload—a White Paper”, 2010.
Wireless Broadband Alliance, “WISPr 2.0, Apr. 8, 2010”; Version 01.00.
Thurston, Richard, “WISPr 2.0 Boosts Roaming Between 3G and Wi-Fi”; Jun. 23, 2010; Web page from zdnet.com; Zdnet.com/wispr-2-0-boosts-roaming-between-3g-and-wi-fi-3040089325/.
Wi-Fi Alliance Technical Committee Hotspot 2.0 Technical Task Group, “Hotspot 2.0 (Release 1) Technical Specification—Version 1.0.0”; 2012.
Wi-Fi Alliance Hotspot 2.0 Technical Task Group, “Wi-Fi Certified Passpoint™ (Release 1) Deployment Guidelines—Version 1.0—Oct. 2012”.
3rd Generation Partnership Project, “Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) Enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Access,” Release 8, Document No. 3GPP TS 23.401, V8.4.0, Dec. 2008.
3rd Generation Partnership Project, “Technical Specification Group Services and System Aspects; Policy and Charging Control Architecture,” Release 8, Document No. 3GPP TS 23.203, V8.4.0, Dec. 2008.
Alonistioti et al., “Intelligent Architectures Enabling Flexible Service Provision and Adaptability,” 2002.
Amazon Technologies, Inc., “Kindle™ User's Guide,” 3rd Edition, Copyright 2004-2009.
Chandrasekhar et al., “Femtocell Networks: A Survey,” Jun. 28, 2008.
Chaouchi et al., “Policy Based Networking in the Integration Effort of 4G Networks and Services,” 2004 IEEE.
Cisco Systems, Inc., “Cisco Mobile Exchange (CMX) Solution Guide: Chapter 2—Overview of GSM, GPRS, and UMTS,” Nov. 4, 2008.
Dikaiakos et al., “A Distributed Middleware Infrastructure for Personalized Services,” Nov. 24, 2003.
European Commission, “Data Roaming Tariffs—Transparency Measures,” [online] retrieved from http://web.archive. org/web/20081220232754/http://ec.europa.eu/information_society/activities/roaming/data/measures/index_en.htm, Dec. 20, 2008 [retrieved May 16, 2012].
Farooq et al., “An IEEE 802.16 WiMax Module for the NS-3 Simulator,” Mar. 2-6, 2009.
Han et al., “Information Collection Services for Qos-Aware Mobile Applications,” 2005.
Hartmann et al., “Agent-Based Banking Transactions & Information Retrieval—What About Performance Issues?” 1999.
Hewlett-Packard Development Company, LP, “IP Multimedia Services Charging,” white paper, Jan. 2006.
Hossain et al., “Gain-Based Selection of Ambient Media Services in Pervasive Environments,” Mobile Networks and Applications. Oct. 3, 2008.
Knight et al., “Layer 2 and 3 Virtual Private Networks: Taxonomy, Technology, and Standarization Efforts,” IEEE Communications Magazine, Jun. 2004.
Koutsopoulou et al., “Middleware Platform for the Support of Charging Reconfiguration Actions,” 2005.
Kyriakakos et al., “Ubiquitous Service Provision in Next Generation Mobile Networks,” Proceedings of the 13th IST Mobile and Wireless Communications Summit, Lyon, France, Jun. 2004.
Ahmed et al., “A Context-Aware Vertical Handover Decision Algorithm for Multimode Mobile Terminals and Its Performance,” BenQ Mobile, Munich Germany; University of Klagenfurt, Klagenfurt, Austria; 2006.
Kassar et al., “An overview of vertical handover decision strategies in heterogeneous wireless networks,” ScienceDirect, University Pierre & Marie Curie, Paris, France, Jun. 5, 2007.
Schiller et al., “Location-Based Services,” The Morgan Kaufmann Series in Data Management Systems, 2004.
Sadeh et al., “Understanding and Capturing People's Privacy Policies in a Mobile Social Networking Application,” ISR School of Computer Science, Carnegie Mellon University, 2007.
Jing et al., “Client-Server Computing in Mobile Environments,” GTE Labs. Inc., Purdue University, ACM Computing Surveys, vol. 31, No. 2, Jun. 1999.
Rivadeneyra et al., “A communication architecture to access data services through GSM,” San Sebastian, Spain, 1998.
Loopt User Guide, metroPCS, Jul. 17, 2008.
“Jentro Technologies launches Zenlet platform to accelerate location-based content delivery to mobile devices,” The Mobile Internet, Boston, MA, Feb. 2008.
NetLimiter Lite 4.0.19.0; http://www.heise.de/download/netlimiter-lite-3617703.html from vol. 14/2007.
Muntermann et al., “Potentiale und Sicherheitsanforderungen mobiler Finanzinformationsdienste und deren Systeminfrastrukturen,” Chair of Mobile Commerce & Multilateral Security, Goethe Univ. Frankfurt, 2004.
Kasper et al., “Subscriber Authentication in mobile cellular Networks with virtual software SIM Credentials using Trusted Computing,” Fraunhofer-Institute for Secure Information Technology SIT, Darmstadt, Germany; ICACT 2008.
Fujitsu, “Server Push Technology Survey and Bidirectional Communication in HTTP Browser,” Jan. 9, 2008 (JP).
Roy et al., “Energy Management in Mobile Devices with the Cinder Operating System”, Stanford University, MIT CSAIL, Jun. 3, 2010.
Windows7 Power Management, published Apr. 2009.
Quintana, David, “Mobile Multitasking,” Apr. 14, 2010.
Open Mobile Alliance (OMA), Push Architecture, Candidate Version 2.2; Oct. 2, 2007; OMA-AD-Push-V2_2-20071002-C.
“Ads and movies on the run,” the Gold Coast Bulletin, Southport, Qld, Jan. 29, 2008.
Richtel, “Cellphone consumerism; If even a debit card is too slow, now you have a new way to act on impulse: [National Edition],” National Post, Canada, Oct. 2, 2007.
Kim, “Free wireless a high-wire act; MetroFi needs to draw enough ads to make service add profits,” San Francisco Chronicle, Aug. 21, 2006.
Koutsopoulou et al., “Charging, Accounting and Billing Management Schemes in Mobile Telecommunication Networks and the Internet,” IEEE Communications Surveys & Tutorials, First Quarter 2004, vol. 6, No. 1.
Sun et al., “Towards Connectivity Management Adaptability: Context Awareness in Policy Representation and End-to-end Evaluation Algorithm,” Dept. of Electrical and Information Engineering, Univ. of Oulu, Finland, 2004.
Sabat, “The evolving mobile wireless value chain and market structure,” Nov. 2002.
Nuzman et al., “A compund model for TCP connection arrivals for LAN and WAN applications,” Oct. 22, 2002.
Kuntze et al., “Trustworthy content push,” Fraunhofer-Institute for Secure Information Technology SIT; Germany; WCNC 2007 proceedings, IEEE.
Blackberry Mobile Data System, version 4.1, Technical Overview, 2006.
Client Guide for Symantec Endpoint Protection and Symantec Network Access Control, 2007.
Ehnert, “Small application to monitor IP trafic on a Blackberry—1.01.03”, Mar. 27, 2008; http://www.ehnert.net/MiniMoni/.
Android Cupcake excerpts, The Android Open Source Project, Feb. 10, 2009.

Related Publications (1)

	Number	Date	Country
	20170187839 A1	Jun 2017	US

Provisional Applications (5)

Number	Date	Country
61387243	Sep 2010	US
61206354	Jan 2009	US
61206944	Feb 2009	US
61207393	Feb 2009	US
61207739	Feb 2009	US

Divisions (1)

	Number	Date	Country
Parent	13248028	Sep 2011	US
Child	14578124		US

Continuations (1)

	Number	Date	Country
Parent	14578124	Dec 2014	US
Child	15287603		US

Continuation in Parts (2)

	Number	Date	Country
Parent	12380778	Mar 2009	US
Child	13248028		US
Parent	12380780	Mar 2009	US
Child	12380778		US

Enterprise access control and accounting allocation for access networks

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

CPC

International Classifications

Abstract