As the computing power of mobile devices (e.g., smart phones, tablets, etc.) has increased, mobile devices have become capable of sending and receiving increasing amounts of data. In addition to e-mail and text messages, many of today's mobile devices can support a variety of applications that send large quantities of information to and from end users. For example, in addition to sending e-mail and text messages, many of today's mobile devices can deliver news, weather, sports, maps, social networking information, music, videos, high-resolution photographs, documents, presentations, and other kinds of information. Furthermore, users can take advantage of applications that provide transactional services, e.g., shopping for content (books, music, videos, etc.) or applications.
The increased computing power of mobile devices has led to an explosion in the number of applications that are available for mobile devices. Hundreds of thousands of applications are available for Android-based devices and for Apple-based devices, and the number of available applications continues to grow at a rapid pace. Many of these applications are available for subscribers to download or purchase through an electronic “app store” or “marketplace.” A subscriber may find applications of interest to him or her by typing in a search word or phrase in a field in a search field offered by the app store or marketplace, or he or she may find an application by browsing a list offered by the app store or marketplace (e.g., popular applications). Often, however, subscriber visits to the app store are “hit and miss” unless a subscriber happens to know the name of a desired application or happens to type in a search word or phrase that results in the application being presented.
For application developers, encouraging subscribers to see, download, purchase, or use their applications can be important to the application developers' success because their revenues often depend on purchases, downloads, and/or use of their applications. Yet because of the sheer number of applications available through marketplaces and app stores, and because of how subscribers may behave when browsing through the marketplace or app store, application developers have little control over whether a subscriber even finds their applications.
Disclosed herein are methods and apparatuses for managing service user discovery and service launch object placement on a mobile device. Disclosed is a method comprising obtaining information to assist in identifying a portion of a user interface of a wireless device, the wireless device communicatively coupled to the network system over a wireless access network, determining a differentiating attribute of the identified portion of the user interface, obtaining one or more service launch objects for placement in the identified portion of the user interface, and sending configuration information to the wireless device over the wireless access network, the configuration information at least configured to assist the wireless device in placing the one or more service launch objects in the identified portion of the user interface.
As the number and types of services on a mobile device increase, it becomes increasingly important to differentiate the services and types of service to users in a way that users can easily understand, access, and launch. In some embodiments, device users can avail themselves of one or more of bite-sized bulk data plans, application-specific data plans, and sponsored data plans (for example, plans that are free to the end user because they are paid for by third party sponsors who make money when users use their over-the-top service or application).
In some embodiments, the management system 100 includes additional or fewer functions than those shown in
In some embodiments, the device management system 170 defines the location in a device UI 136 where a service launch object is placed to aid in managing the manner in which a user discovers the network service 120 or device service 138 (for example, an application) and launches it. In some embodiments, the UI location manager 132 uses information associated with a service launch object (for example, metadata) to instruct the UI agent 134 where to locate the service launch object in the device UI 136.
In some embodiments, a UI location management service provider entity utilizes the apparatus shown in
In some embodiments, service launch object is an object on a device UI 136 that a user of device 130 or a network entity (for example, device management 170, service provider, carrier, etc.) can select (for example, “click on,” “open,” “launch,” etc.) to initiate a network service 120 or device service 138. In some embodiments, the network service 120 or device service 138 is a service or an application. In some embodiments, initiating network service 120 or device service 138 provides (for example, by launching, initiating, streaming, playing, presenting, displaying, purchasing, downloading, or preloading) a content (for example, a video or movie or audio), or a software, or a software download, or software update. In some embodiments, selection of the service launch object initiates the network service 120 or device service 138 by launching an application that is associated with the service launch object; or directing an application (for example, as a browser or portal application) to a particular network destination that is associated with the service launch object; or opening a folder with one or more additional service launch object choices for the user to select from; or providing the user with a notification regarding service status or service plan permissions for this service; or providing the user with payment or service account configuration options to enable the service. In some embodiments, selection of the service launch object initiates the network service 120 or device service 138 by launching a purchase experience or a purchasing environment. In some embodiments, selection of the service launch object initiates providing a user of device 130 with means to download an application from the application download server 140 and launch the network service 120 or device service 138. In some embodiments, the service launch object is an Android “APK” (i.e., an application package) comprising an application and additional associated information, for example, information about an icon (for example, a graphic or location) associated with a service or an application. In some embodiments, a service launch object icon is one or more of a graphic, a text string, a UI user entry field or any other means for the user to choose to activate a service launch object.
In some embodiments, service launch object discovery level refers to the level of priority a service launch object receives relative to gaining the device user's attention in order to encourage selection or launch a service or application associated with the service launch object. In some embodiments, a high discovery level corresponds to a premium UI location for the service launch object (for example, the service launch object is placed in a prominent UI service launch partition, a home screen, or a permanent launcher bar). In some embodiments, a high discovery level also includes or is indicated by one or more of highlighted service launch object icon features (wherein icon features include one or more of size, orientation, color, texture, persistence, transparency, foreground/background presence, skin, wallpaper, etc.) or prominent or frequent service launch object notification messages. In some embodiments, a low discovery level is characterized by a less prominent service launch object UI location or less prominent service launch object notification messaging. In some embodiments, a low discovery level includes one or more of: a service launch object location in the device application stable, a service launch object on an application store/marketplace location, a service launch object without notification messaging, and a one time notification message the first time the service launch object icon is displayed to the user.
In some embodiments, the management system provides for remote management of location and modification of appearance for a service launch object icon. In some embodiments, a service launch object icon is the graphic shown on the device UI screen that represents the service or application (which may include a content or purchase experience) associated with the service launch object. In some embodiments, the service launch object icon is positioned on a touch screen in the location that launches the service or application associated with the service launch object when the user touches it.
In some embodiments, the management system provides for remote management or modification of a service launch object notification message. In some embodiments, a service launch object notification message is a targeted user notification message that a user can observe (for example, see or hear) as associated with (or integral to) a particular actionable service launch object because the service launch object notification message is placed in, on, touching or in close proximity to the service launch object icon. In some embodiments, this kind of integral service launch object notification message requires management of how or when or where the notification message is displayed in the device UI. In some embodiments, the service launch object display location is based on (for example, targeted for, or optimized for) each service launch object or must be mapped for each service launch object and service launch object message pair. In some embodiments, association of a notification message with an actionable (for example, “clickable”) service launch object icon on the device allows for targeted or specific user messaging about various aspects of an available service or application in a manner that does not require the user to search for an icon to act on, nor does the user need to do further research on what an actionable icon offers the user experience. In some embodiments, an advantage of the management system 100 is the remote management of service launch object notification messages that are (easily) recognized or acted on by the user by virtue of the association of the notification message and the actionable service launch object icon. In some embodiments, an additional advantage of the management system 100 is that multiple notification messages for multiple actionable service launch objects may be sent to the device (for presentation to a user) preventing the user from becoming confused about which service launch object notification message goes with which service launch object.
In some embodiments, different types of service launch objects are placed in a common device UI service launch partition in the device UI 136 to aid the user in understanding that one or more service launch object associated with network service 120 or device service 138 represented in that UI service launch partitions are related or of similar type. In some embodiments, the placement of the service launch object within the UI service launch partitions is specified in the device management system 170. In some embodiments, the device management system 170 provides a UI location where a service launch object is desired to be placed, and the UI location manager 132 translates that location into device UI 136 configuration to position the service launch object icon in the desired UI location.
In some embodiments, multiple device UI service launch partitions are used to identify multiple groups of service launch objects. In some embodiments, the management system 170 specifies the one or more UI service launch partitions in which a service launch object is to be displayed.
In some embodiments, the management system 170 specifies that a service launch object is to be placed in a location on a device UI 136, with the location being one or more of a UI service launch partition, a device main screen, a device secondary screen, a device permanent launch area, a device application stable, a device file system location, an application download server, or other division.
In some embodiments, a network service 120 is sponsored on a user's service plan, and it is difficult or inconvenient for the user to remember the website and enter it. In some embodiments, the ability to dynamically configure a device application (such as a browser, a portal application, a dedicated application such as a social network application, a search application, a maps or location application, a voice or chat application, media streaming application, music application, content viewing or purchase application, shopping application, driving directions application, service plan selection or configuration application, service usage reporting application, a gaming application, a weather application, an email application, a widget, or another service related application, etc.) with the proper destination, associate this configured application with a service launch object icon representing the sponsored network service 120, and place the service launch object icon in a convenient location on the device UI 136, provides the user with means to more easily “discover” or “launch” the sponsored network service 120. In some embodiments, a sponsored device service 138 is difficult of inconvenient for the user to remember and the management system performs one or more of the following: dynamically configure a device application with the proper destination, associate this configured application with a service launch object icon representing the sponsored device service 138, place the service launch object icon in a convenient location on the device UI 136, provide the user with means to more easily “discover” or “launch” the sponsored device service 138.
In some embodiments, the service provider (such as a wireless carrier) may have a new service plan that the carrier desires the user to “discover” by trying. In some embodiments, the service provider could configure a “try before buy” service plan wherein a “sample service” with shorter time span is provided or wherein the cost for service is less expensive for a period of time. The service provider can then configure or place a service launch object in a location on the device UI 136 where the user is likely to discover it.
In some embodiments, the service provider (for example, a wireless service provider, application store or application marketplace service provider, etc.) may provide means to specify where a given service launch object is placed on a device UI 136, and charge the application provider or service provider for the UI placement in accordance to the value of the placement. In some embodiments, placement in the application store or marketplace may be free. In some embodiments, placement in the on-device application stable might have lower cost, placement on one of the secondary device screens might be more expensive, placement in a UI service launch partition might cost even more, placement on the device main screen might be yet more expensive, and placement in the permanent launch area might be most expensive of all. It should be understood that the actual hierarchy of pricing may be configured by the service provider. In some embodiments, the hierarchy of pricing is be configured by the service provider or the device management system 170.
In some embodiments, the device management system 170 includes an accounting database 180 to associate the placement of a service launch object on a device UI 136 with a billing rate for the application provider or service provider or sponsor associated with the service launch object.
In some embodiments, device UI discovery location is the portion of the device UI 136 that a service launch object reside in. In some embodiments, there is a single UI service launch partition (or folder or organization) with service launch objects within it.
In some embodiments, the portion of the device UI reserved for one or more service launch objects is identified by a differentiating characteristic or attribute. In some embodiments, the differentiating characteristic to identify the portion of the UI is defined by or characterized by one or more of: a color, a wallpaper, a transparency, a wall, a window, a texture, and a border. In some embodiments, different portions of a UI are classified into tiers (or, alternatively, classes or levels, etc.), and each of the classified sub-portions is differentiated by variations of one or more of: color, wallpaper, transparency, walls, windows, textures, borders, and a plurality of screens.
In some embodiments, the partitioned UI service launch partition portion provides for two or more UI service launch partitions that indicate to the user that the service launch objects in a given service launch partition are members of a type of service. In some embodiments, a service launch partition includes displaying user options for service launch objects for “default” sponsored network services, websites, applications or content. In some embodiments, default sponsored network services, websites, applications or content are subsidized by a service provider or third party. The term “default” refers to services that are pre-configured by a service provider, device original equipment manufacturer (OEM), operating system (OS) provider or third party. In some embodiments, a service launch partition displays user options for service launch objects for “user selected sponsored services,” wherein the user selects from available sponsored service options and once the service option is selected by the user then the service launch object appears in the service launch partition. In some embodiments, the user is enabled to select a certain number of sponsored service options out of a larger list of sponsored service user options. In some embodiments, a service launch partition includes displaying user options for service launch objects for paid services that the user has elected to sign up for. In some embodiments, a service launch partition includes displaying user options for service launch objects for services, sponsored or paid, that the user has not yet elected to sign up for but are available to the user. In some embodiments, each of the two or more service launch partitions in the multi-partition UI service launch partition application (or widget) has text or graphics indicating to the user the type of service for one of more of the multiple partitions. In some embodiments, the device UI discovery location is a UI location within the partitioned service object launcher, and the service launch object UI location also specifies the partition or the location within the partition.
In some embodiments, a service plan or a service component is specified in a service design environment (wherein the “service design environment” may include a service design center, a service design platform, a service design management system, etc.). In some embodiments, the service design environment comprises associating the network service 120 or device service 138 with one or more service launch objects. In some embodiments, the service launch object includes one or more of an icon (graphic), a software application, a folder or similar collection of additional service launch objects, a network destination or a network communication end point, one or more notification message sequences or information, and service selection options. In some embodiments, the service design environment allows an entity to choose the device discovery UI location for the network service 120 or device service 138. In some embodiments, the device discovery UI location is one or more of service launcher application UI, partitioned service object launcher application UI, main device screen or a secondary device screen, quick launch area, permanent launch area, device application stable, device marketplace, application store, website or network server. In some embodiments, the service design environment allows the specification of where to preload an application if the application is not already loaded on the device 130 so that the application may be available the first time the user selects the network service 120 or device service 138. In some embodiments, the specification is formatted into a set of instructions for a network server that communicates with the UI location manager 132 on the device 130. In some embodiments, the set of instructions provides a service launch object with configuration or placement or message information that instructs the UI location manager 132 on the device 130 where to locate the service launch object in the device UI 136 or how to provision the service launch object so that it properly launches or instructs the user when the user selects the launch object. In some embodiments, the service launch object configuration or placement or message information can specify a network server destination where UI location manager 132 on the device 134 is to fetch one or more of the required service launch object parameters.
In some embodiments, device 130 receives a service launch object configuration or placement or message information from a network server. In some embodiments, device 130 identifies the portion of the service launch object configuration or placement or message information that specifies the device UI 136 location for the service launch object. In some embodiments, device 130 installs the service launch object icon in the device UI 136 location. In some embodiments, device 130 associates the service launch object icon with the service launch object that will initiate the network service 120 or device service 138 when the user selects the service launch object icon.
In some embodiments, the service launch object requires an application to launch the network service 120 or device service 138. In some embodiments, the device 130 is configured to search the available applications on the device 130, detect that a required application is not present on the device 130 and preload it prior to the user selecting to launch the network service 120 or device service 138 associated with the service launch object. In some embodiments, the device 130 is configured to detect that the required application is not present and then automatically download the application when the user first selects the service associated with the service launch object. In some embodiments, the device 130 is configured to detect that the required application is not present on the device 130 and offer the user the option to download the application when the user first selects the network service 120 or device service 138 associated with the service launch object. In some embodiments, wherein device 130 downloads or preloads application, the device 130 can either download the application from a pre-defined application download server 140 or can download it from a location specified in the service launch object placement instruction message.
In some embodiments, the service launch object is further configured to include notification messages that are displayed to the user when the user selects or first selects the service launch object icon. In some embodiments, the notification message includes information on how much the service costs or what the service allowances are. In some embodiments, the notification message involves service plan selection options that allow the user to elect to pay for a service, or allow the user to select a sponsored service. In some embodiments, notification messages may be handled by a UI agent 134.
In some embodiments, the UI location manager 132 automatically populates one or more of the service launch object, service launch object associated application, network destination specification or service launch object icon in the proper location in the device UI when user selects the network service 120 or device service 138.
In some embodiments, device network state information is used to define the state of one or more networks 110 that the device 130 is connected to. Network state information includes one or more of the type of access connection to the network (for example, 4G wireless, 3G wireless, 2G wireless, WiFi, cable, DSL, hot spot service provider, home LAN, corporate LAN, etc.), the list of available networks (for example, WiFi and 3G, or 4G and corporate LAN, etc.), time of day, home vs. roaming carrier service provider status, network access cost (for example, service plan details and status), network congestion state, network quality-of-service (QoS) state, device data rate, device signal quality, and any other characteristic of the network.
Device usage state information (wherein information could comprise one or more of parameters, logs, history, etc.) provides information on the manner in which the device is used (for example, in the past, present or predicted future) by the device user. In some embodiments, device usage state information includes one or more of: the current or past state of service usage for one or more services, current or recent states of application usage for one or more selected applications, current or recent geographic locations, current or recent location searches, current or recent network destination history (websites, services, content, search terms, etc.), one or more applications currently being interacted with by the user, the current or recent network state, how long it has been since the user pressed one or more UI feedback elements on the device, whether an application is running in the foreground or background, etc. In some embodiments, the device can collect device usage state information (for example, collected by the UI location manager 132, or some other device agent). In some embodiments, the device usage state includes device cognitive state, wherein the device cognitive state includes information the device gathers from the environment based on the device sensors. In some embodiments, the device uses one or more of a camera, a microphone, a GPS, a motion sensor, a gyroscope, a accelerometer, a temp sensor, a touch sensor, a humidity sensor, to determine the device state relative to the environment or the user of the device. In some embodiments, the service launch object management (for placement, discovery level, notification message, bidding, etc.) is dynamic based on one or more of: device orientation (landscape vs. portrait vs. flat on a horizontal surface) or device distance or relative position to a user (near the head, in one or two hands, on a table, on the seat of a moving car, in the pocket of the user, indoors/outdoors, etc.) or ambient light/noise levels or components. In some embodiments, the device cognitive state is used to decide between a visual or audio or vibration notification or a specialized target bid population or to bill for a service launch object placement or associated service or application usage. In some embodiments, the service launch object management is based in part on the power state of the device, for example, powered up, active, screen saver, hibernate, sleep or powered down mode. In some embodiments, the service launch object management changes the power state (for example, from screen saver to active) to increase awareness of an associated service or application to a user. In some embodiments, the user may disable the power state change mode. In some embodiments, the service launch object management is based on the power mode (e.g., whether plugged in or battery-powered) or the state (percentage or time remaining) of the battery charge.
In some embodiments, device-based usage information is communicated with a network element for further processing or analysis to determine how to enhance (e.g., improve, increase, optimize, etc.) discovery level for one or more service launch objects. In some embodiments, device usage state information is collected by network elements and aggregated in the device management system 170 databases for further processing or analysis to determine how to enhance discovery level for one or more service launch objects. In some embodiments, device usage state information consists of a combination of information collected by the device and information collected by the network for further processing or analysis to determine how to enhance discovery level for one or more service launch objects.
In some embodiments, the availability of a network service 120 or device service 138 is dependent on the network state of the device 130. In some embodiments, if the network service 120 or device service 138 is available for a current network state the service launch object icon is displayed in the specified UI location. In some embodiments, if the network service 120 or device service 138 is not available for the current network state the icon is not displayed. In some embodiments, the service launch object configuration or placement or message information contains information that is a function of network state. In some embodiments, and the UI location manager 132 uses the service launch object configuration or placement or message information and network state information to instruct the UI agent 134 to display the service launch object icon in a given location in the device UI 136 in a first network state and instructs the UI agent 134 to not display the service launch object icon in a second network state.
In some embodiments, a UI location management console 160 provides a network manager a user interface environment for one or more of composing the network state policies describing when one or more services are available, specifying whether to present a service launch object (for example, display a service launch object icon), and specifying whether to provide network state notification information on one or more service launch object icons.
In some embodiments, the availability of a network service 120 or device service 138 is dependent on the network state associated with the device 130, and if the network service 120 or device service 138 is available for a current network state then the service launch object icon is displayed with “normal” (or typical or standard) graphics features in the specified UI location, and if the network service 120 or device service 138 is not available for the current network state then the icon is displayed with graphics features that indicate the service is not available in the current network state. In some embodiments, instead of or in addition to modifying the service launch object icon graphics features to indicate the network service 120 or device service 138 is not available in the current network state, a notification message may be overlaid on the service launch object icon, with the message providing information indicating that the network service 120 or device service 138 is not available in the current network state.
In some embodiments, the service launch object configuration or placement or message information contains one or more of icon versions, icon placements, or network state messages, that are a function of network state, and the UI location manager 132 provides the appropriate one or more icon version, icon placement, network message to the UI agent 134 to modify the associated service launch object icon as the network state changes.
In some embodiments, a network service 120 or device service 138 is sponsored in a first network state and paid in a second network state. In some embodiments, a network service 120 or device service 138 is sponsored in a first network state and paid in a second network state and in the first network state the service launch object icon appears in a UI service launch partition for sponsored services, and in the second network state the service launch object icon appears in a UI service launch partition for paid services. In some embodiments, the service launch object configuration or placement or message information contains placement information that is a function of network state, and the UI location manager 132 uses this placement information to instruct the UI agent 134 to display the service launch object icon in a sponsored service location in the device UI 136 when the device 130 is in the first network state and instructs the UI agent 134 to display the service launch object icon in a paid service location in the device UI 136 when the device 130 is in the second network state.
In some embodiments, it is advantageous to show whether a service or application is free or paid by a feature differentiation directly on the service launch object icon. An example embodiment of this is shown in
In some embodiments, there is a permanent UI service launch partition that the user is not allowed to modify or remove from the device. In some embodiments, the permanent UI service launch partition enables a UI location management service provider to enhance service launch object UI location, or service launch object icon appearance or service launch object notification messages for one or more service launch objects. In some embodiments, the UI location management service provider of the permanent UI service launch partition allows the user to manage the applications, folder and/or service launch objects that are located in other portions of the UI controlled by the user. In some embodiments, the user can control (for example, modify or alter or enhance) some parameters (for example, the ordering, or sorting, or formatting) of service launch objects within a UI service launch partition that is at least partially controlled by a UI location management service provider. In some embodiments, the user can add or delete service launch objects from a UI service launch partition that is at least partially controlled by a UI location management service provider. In some embodiments, the user is not allowed to add or delete or control (for example, modify or alter or enhance) service launch objects contained in a UI service launch partition that is controlled by a UI location management service provider.
In some embodiments, the UI location manager 132 is instructed (or follows a policy) to locate a service launch object in the UI based on the current time (wherein current time could be based time of day, or day of week, or work/holiday, etc.).
In some embodiments, a policy is implemented on the UI location manager 132 to specify that a service launch object is located in one area of the UI at a certain time of day or day of the week, and the service launch object is re-located at another time of day or day of the week. As another example embodiment, rather than storing the time based location policy on the device 130, the network (for example, the device management system 170) can instruct the UI location manager 132 to locate one or more service launch objects in the UI based on time. In related embodiments, other features of one or more service launch objects are altered as a function of time including service launch object appearance or features or service launch object notification messages.
In some embodiments, the UI location manager 132 is instructed (or follows a policy) to locate a service launch object in the UI based on the current network state. In some embodiments, a policy is implemented on the UI location manager 132 to specify that a service launch object is located in one area of the UI for certain network states and service launch object is re-located to another area of the UI for other network states. In some embodiments, the service launch object is located on the home screen or in a prominent location in a UI service launch partition when the device is connected to WiFi, 4G, uncongested, or high QoS networks. In some embodiments, the service launch object is re-located to a less prominent UI location, such as a secondary device screen, a less prominent location in the UI service launch partition, the application stable, or is not displayed at all when network state changes to 3G, 2G, congested or low QoS or roaming network.
As another example embodiment, rather than storing the network state based location policy on the device, the network (for example, the device management system 170) instructs the UI location manager 132 to locate one or more service launch objects in the UI based on network state. In related embodiments, other features of one or more service launch objects are altered as a function of network state including service launch object appearance or features or service launch object notification messages.
In some embodiments, the UI location manager 132 is instructed (or follows a policy) to locate a service launch object in the UI based on the device usage state information (for example, based on current, or past, or predicted, or history, or logs of, device usage state information). For example, a policy might be implemented on the UI location manager 132 to specify that a service launch object is located in one area of the UI for certain device usage state, and the service launch object location is moved for other device usage state. In some embodiments, locate the service launch object on the home screen or in a prominent location in a UI service launch partition when the device usage state information (for example, based on application usage history or user current activity) indicates (for example, based on estimates, or predictions, or cost, etc.) that a given service offer is likely to be or interest to the user.
In some embodiments, the service launch object is located on the home screen or in a prominent location in a UI service launch partition when the device usage state information recognizes a geographic area where a service or retail opportunity is valuable or might be of interest to the user, such as a nearby purchase opportunity.
In some embodiments, the service launch object is re-located to a less prominent location in the UI service launch partition, to the application stable, or is not displayed at all when device usage state indicates that the current device usage information (for example, based on associated application history) is not related to the service launch object or indicates (for example, based on estimates, or predictions, or cost, etc.) that a given service launch object is not likely to be or interest to the user.
In some embodiments, the service launch object is re-located to a less prominent location in the UI service launch partition, the application stable, or is not displayed at all when device usage state indicates that the current geographic location is not close to a retail purchase opportunity associated with the service launch object.
In some embodiments, rather than storing the device usage state based location policy on the device, the network (for example, the device management system 170) instructs the UI location manager 132 to locate one or more service launch objects in the UI based on device usage state. In related embodiments, other features of one or more service launch objects are altered as a function of device usage state including service launch object appearance or features or service launch object notification messages. In some embodiments, a service launch object notification message can alert the user when the service, content, purchase opportunity or application associated with the service launch object is likely to be of interest to the user. In some embodiments, (which may be of interest to wireless access service providers), by using one or more of a service launch object notification messages, a service launch object UI location change or a service launch object icon change (for example, a feature, size, orientation, persistence, etc.), the user of device 130 is made aware of additional access services available for trial or purchase. In some embodiments, (which may be of interest to wireless access service providers), by using one or more of a service launch object notification messages, a service launch object UI location change or a service launch object icon change (for example, a feature, size, orientation, persistence, etc.), the user of device 130 is made aware of additional access services available for trial or purchase based on the device usage state information (for example, history or logs) indicating that the user has been using access services.
In some embodiments, by using one or more of a service launch object notification messages, a service launch object UI location change or a service launch object icon change (for example, a feature, size, orientation, persistence, etc.), the user of device 130 is made aware of additional access services available for trial or purchased based on the device usage state information (for example, history or logs) indicating that the user has been using access services in a manner that suggests the user may desire to try or buy additional access services at the present or future time.
In some embodiments, additional service launch object notification messages are provided for services, applications or content marketing, wherein the notification message is placed in, on, touching or in close proximity to a service launch object icon (an icon proximity message), or wherein the notification message is located in a location in a UI display in which the service launch object icon is contained (an icon container message). In some embodiments, the notification messages include one or more of the following objectives: informative, draw attention to a service launch object, market special offers for a service launch object, provide service usage information for a launch object, or indicate to a user that a service activation or service purchase is required to use a service associated with a service launch object.
In some embodiments, marketing messages for an access service, an application, a content purchase, on-line shopping service, or another service is placed directly on a service launch object icon, or closely adjacent to a service launch object icon, or in a location in a UI display in which the service launch object icon is contained (for example, in service object launcher or a UI service launch partition), for the purpose of providing a convenient way for the device user to learn that the service or application associated with the service launch object icon is available or is available with special advantageous conditions or economics.
In some embodiments, the appearance of a service launch object icon is modified to enhance or downgrade the discovery level. In some embodiments, enhancing or downgrading the discovery level is accomplished by one or more of changing the service launch object icon features, changing the icon graphic, overlaying the service launch object icon graphic with a second icon or graphic, or merging the icon graphic with a second icon graphic. In some embodiments, the icon features or the color scheme are changed in accordance with service launch object icon UI management policy or instructions from the network. In some embodiments, the service launch object icon is made to alternate in appearance (for example, flash or change colors periodically or “bounce” or “wobble” etc.) according to service launch object icon UI management policy or instructions from the network.
In some embodiments, additional service launch object notification messages as described above are managed by the device management system 170. In some embodiments, additional service launch object notification messages as described above are managed by the device management system 170, wherein a service launch object and one or more of associated application, network destination or other policy information, are associated with a service launch object notification message. In some embodiments, additional service launch object notification messages as described above are managed by the device management system 170, wherein a service launch object and one or more of associated application, network destination or other policy information, are associated with a service launch object notification message and the device management system 170 then communicates the service launch object notification message along with the other service launch object information as described herein to the UI location manager 132; and the UI location manager 132 then displays the message in the appropriate UI location.
In some embodiments, the device management system 170 specifies the type of service launch object notification message or service launch object UI location; the type of message or UI location information is communicated to the UI location manager 132; and the UI location manager 132 displays the message in the proper format in the specified UI location. In some embodiments, the device management system 170 specifies the type of message or UI location of the service, application or content marketing message; the type of message or UI location information is communicated to the UI location manager 132 along with the other UI location manager 132 information described above; and the UI location manager 132 then displays the message in the proper format in the specified UI location.
In some embodiments, a service launch object notification message is placed on or in a UI service launch partition UI area that has the capability of displaying one or more service launch object notification messages for one or more service launch objects that are or will be located in one of the UI service launch partitions. An example of this aspect of the invention is shown in the example embodiment of
In some embodiments, a UI location management console 160 provides a network manager a user interface environment for performing the one or more functions for composing service, application or content marketing or informative messages, associating the composed message with a service launch object, or initiating the communication of the message content to the device UI location manager 132.
In some embodiments, the UI location manager console 160 further provides a user interface for specifying when the composed message is to be displayed on the device. In some embodiments, the UI location manager console 160 further provides a user interface for specifying under what network state conditions the composed message is to be displayed on the device. In some embodiments, the UI location manager console 160 further provides a user interface for specifying under what device usage state conditions the composed message is to be displayed on the device.
In some embodiments, a variable is used to define notification messages in a notification template to automatically customize the notification for the associated event.
In some embodiments, a management console 160 UI provides a network manager a UI environment for displaying upsell plans.
In some embodiments, a management console 160 UI provides a network manager a UI environment for displaying notification templates for defining a lack of capable plan (for example, lack of data service plan, or lack of access to an application or content—for example, requiring a service or application purchase) notification message for a desired service or application.
In some embodiments, a management console 160 UI provides a network manager a UI environment for displaying notification templates for defining featured service or application (for example) notification message for a desired service or application.
In some embodiments, a management console 160 UI provides a network manager a UI environment for displaying notification templates for defining a promotional banner (or banner ad) for (or to promote or market) a service or application or a promotional banner for a service launch object (or icon) associated with a service or application. In some embodiments, the promotional banners notification templates include one or more of a language, image, or associated plans.
In some embodiments, a management console 160 UI comprises a service design center showing device UI launcher view. In some embodiments, the service design center includes drag and drop icons. In some embodiments, selection of icons provides menus to components or plan view or settings.
In some embodiments, the service launch object icon appearance is modified to indicate the status of service usage for a service plan. The status of service usage can be a graphic (such as a bar or gauge or hourglass or pie chart located on or near the service launch object icon) or a numeric value signifying amount used, amount remaining, percent used or percent remaining, etc. (for example, relative to a monthly quota or cap).
It will now be appreciated that if the two usage meters were provided only in a UI screen format unrelated to the service launch object icons, then the user would need to open that UI screen, observe the usage status for each of the user's active services, and then remember the usage status later on when the user intended to act on one of the service launch object icons by selecting that icon. In some embodiments, usage information is provided on the same screen that the user uses to act on the available services and applications. In some embodiments, usage information is provided on the same screen that the user uses to act on the available service launch object.
Further example embodiments for usage information displayed directly in association with a service launch object icon are provided in
In some embodiments, service launch object icon modifications make it easier for a user to identify one or more subsets of their one or more services or applications with plenty of service allowance remaining, or near the end of their service allowance, or requiring an initial or additional service purchase to use the service or application.
In some embodiments, usage information displayed on the service launch object icon is obtained by the UI location manager 132 (or an some other device agent), and the UI location manager 132 updates (for example, dynamically based on network state or device usage state) the service launch object icon as described in detail herein by changing the icon, overlaying another graphic, merging with another graphic or overlaying a notification message.
In some embodiments, usage information for a given service launch object is sent by a network element to the UI location manager 132 and formatted by the UI location manager 132 for display on the service launch object icon. In some embodiments, usage information is collected on the device 130 by the UI location manager 132 and formatted by the UI location manager 132 for display on the service launch object icon. In some embodiments, usage information collected on the device 130 by the UI location manager 132 is synchronized with usage information from network element, then displayed on the service launch object icon. In some embodiments, the usage information is displayed on the service launch object icon for a one or more network states. In some embodiments, the usage information is displayed on the service launch object icon when connected to a paid network (for example, 4G/3G/2G) but not displayed for a free network (e.g., home WiFi). In some embodiments, the usage information is displayed on the service launch object icon when usage is above a threshold. In some embodiments, the usage information is updated when network state changes (for example, the device may be subject to different usage limits and/or usage levels for 4G, 3G/2G, WiFi, home/roaming, etc.).
In some embodiments, one or more of the service launch object icon appearance, service launch object location or service launch object notification message change as a function of network state.
In some embodiments, the service launch object icon changes appearance or color or animates to indicate a change in network state or service charges.
In some embodiments, the notification message is provided in a manner that does not interrupt service or application launch. In some embodiments, the service or application launch is held (for example, stalled or paused) until the user dismisses the message.
In some embodiments, the service launch object icon appearance, or service launch object location is modified, or a service launch object notification message is presented based on a network state (for example, network QoS, network congestion, network performance, network bandwidth, network data rate or network signal quality). For the example embodiment in
In some embodiments, (for example, the embodiment in
In some embodiments, service or application discovery level is elevated by providing a service launch object notification message for an offer. In some embodiments, the offer is a limited offer. In some embodiments, the limited offer is a limited offer, wherein the limited offer is offered over one or more of a limited time, limited geography, limited network, limited devices, limited users. In some embodiments, the service launch object associated with the offer may be in a UI service launch partition or some other location on the device including a main or home UI screen, or a secondary UI screen or some other UI area.
It will now be clear to one of ordinary skill in the art that other combinations of network state and device usage state parameters may be used to condition the occurrence and content of one or more service launch object notification messages.
In some embodiments, a device user obtains service launch object usage (for example, network access service) allowance (for example, virtual cash, points, megabytes, etc.) by using services on the device which generate revenue for the UI location management service provider or a customer of the UI location management service provider. In some embodiments, a device user obtains service usage allowance (for example, virtual cash, points, megabytes, etc.) by using services on the device which generate revenue for the UI location management service provider or a customer of the UI location management service provider.
In some embodiments, the UI location management service provider or UI location management service provider customer manages (for example, monitors or keeps track of) usage, visits, views, ad views, clicks, ad clicks, or user purchase revenue generated by the device user's use of service or on-device purchases, and manages (for example, monitors or keeps track of) of how many usage points (for example, point, virtual cash, megabytes, etc.) such events have generated for the user's account, and allows the user to convert the usage points into service or application usage (for example, access service) allowance for one or more services or services plans. In some embodiments, management system 100 counts service launch object interactions or banner ad views, coupon clicks, etc. and gives credit for service or application, discount account, reward points or cash.
There are a number of ways the UI location manager 132 can be designed to accept the various information elements such as service launch object information, application information, destination information, service launch object notification messages, network state policies and usage state policies as described herein, and use the network state information and/or usage state information and/or notification messages from the device management system 170 to re-locate service launch objects (or icons) in the device UI, or to change the features or graphics on the service launch objects, or to display different messages in, on, touching or in proximity to the service launch objects. Several detailed embodiments are provided herein. An exhaustive list of all possible embodiments for these functions is not practical and is of limited value to one of ordinary skill in the art once the various embodiments herein are understood. Armed with the teaching provided herein it will be clear to one of ordinary skill in the art how to create other design embodiments to accomplish the same functions.
It is also understood that the following embodiments for moving service launch objects, modifying service launch objects, and providing service launch object notification messages as a function of network state, device usage state or service launch object UI placement instructions from the device management system 170 are taught individually, it is understood that these embodiments may be combined. For example, the embodiments for moving the service launch object icon to different UI locations as a function of network state, device usage state or service launch object UI placement instructions from the device management system 170 can be combined with one or more of the embodiments for changing the appearance of the service launch object icon or providing a service launch object notification message. Similarly, embodiments for changing service launch object appearance can be combined with embodiments for changing service launch object notification messages, and so on.
In some embodiments, wherein the UI locations of the service launch object are changed as a function of various network states, the various UI locations corresponding with the various network states are stored in a table managed by the UI location manager 132 which indexes the table according to changes in the network state, when the network state change is detected and the proper UI location is looked up with the network state index, and the service launch object is moved to new UI location by the UI location manager 132.
In some embodiments, wherein the features of the service launch object icon are changed as a function of network state, the various icon features (for example, graphics files) and the current service launch object UI location are stored in a table managed by the UI location manager 132 which indexes the table according to changes in the network state, when the network state changes is detected and the proper icon features is looked up with the network state index, and the newly featured service launch object icon is placed by the UI location manager 132 on the device UI in accordance with the current service launch object UI location stored in the table.
In some embodiments, the features of the service launch object icon are changed as a function of network state, the various icon features (for example, graphics files) for a network state overlay feature (wherein the term overlay is used to include overlay, or superposition, or merge, or combine) and the current service launch object UI location are stored in a table managed by the UI location manager 132, and the table is indexed by network state, and when the network state change is detected and the proper overlay icon graphic is used to overlay with a basic icon graphic on the device UI in accordance with the current service launch object UI location stored in the table. In some embodiments, the overlay feature may be obtained from a network element (such as the device management system 170) by the device (such as the UI location manager 132) as described above. In some embodiments, the overlay feature may be obtained jointly by a network element (such as the device management system 170) and by the device (such as the UI location manager 132) as described above.
In some embodiments, the overlay is accomplished by the device (such as the UI location manger 132), wherein the device 130 processes a basic (for example, standard) application icon or service launch object icon to perform the overlay of the basic icon with the overlay feature to build a new composite icon on the device. In some embodiments, the overlay is accomplished by presenting the overlay graphics in, on or in close proximity to the location in the UI containing the application or service launch object icon, with the current service launch object location being derived from the current service launch object UI position in the aforementioned table.
In some embodiments, a service launch object icon (for example, including overlay feature) that changes as a function of network state is obtained from a network element (such as the UI location management server 150), after the UI location manager 132 detects the network state change and receives the new corresponding icon from the network element, the UI location manager 132 places the new icon in the proper service launch object UI location.
In some embodiments, wherein a service launch object notification message is changed as a function of network state, the various service launch object notification messages that vary with network state and the current service launch object UI location are stored in a table managed by the UI location manager 132 which indexes the table according to changes in the network state. In further embodiments, after the network state change is detected and the proper service launch object notification message is looked up with the network state index, the new service launch object notification message is used to replace the service launch object notification message that was used in a prior network state, and the new service launch object notification message is placed in, on, touching or in proximity to the service launch object icon in accordance with the current service launch object UI location stored in the table.
In some embodiments, a service launch object notification message that changes as a function of network state is obtained from a network element (such as the UI location management server 150), after the UI location manager 132 detects the network state change and receives the new corresponding service launch object notification message from the network element, the UI location manager 132 places the notification message in, on, touching or in proximity to the service launch object icon, with the new service launch object notification message being placed in the proper service launch object UI location by the UI location manager 132.
In some embodiments, wherein a service launch object notification message is changed as a function of device usage state, the various service launch object notification messages that vary with device usage state and the current service launch object UI location are stored in a table managed by the UI location manager 132 which indexes the table according to changes in the device usage state.
In some embodiments, the device usage state change is detected and the proper service launch object notification message is looked up with the device usage state index, and the new service launch object notification message is used to replace the service launch object notification message that was used in a prior device usage state. In some embodiments, the device usage state change is detected and the new service launch object notification message is placed in, on, touching or in proximity to the service launch object icon in accordance with the current service launch object UI location stored in the table.
In some embodiments, an updated (for example, dynamic) service launch object (for example, by changing one or more of service launch object location, or service launch object icon, or service launch object overlay feature, or service launch object notification message, or UI service launch partition message) that changes as a function of device usage state is obtained from a network entity (such as the device management system 170), when the UI location manager 132 detects the device usage state change and requests an updated service launch object from the network element, and then the UI location manager 132 places the new service launch object at the appropriate UI location. In some embodiments, the device 130 keeps a device usage state log and provides to a network element (such as the device management system 170) one or more of: the current state of service usage for one or more selected services, current or recent states of application usage for one or more selected applications, current or recent geographic locations, current or recent network destination history, current or recent applications being interacted with by the user, current or recent network state, how long it has been since the user interacted on a UI feedback element on the device; the device 130 receives from the network entity a new updated service launch object (or index) to replaced the previous service launch object and is placed by the UI location manager 132 in the UI location corresponding to the new updated service launch object. In some embodiments, at least a part of the usage state information is collected by the network entity. In some embodiments, at least a part of the usage state information collected by the device 130 is augmented by network entity usage state information. In some embodiments; the device management system 170 receives the device usage state information from the device 130, including one or more of: the current state of service usage for one or more selected services, current or recent states of application usage for one or more selected applications, current or recent geographic locations, current or recent network destination history, current or recent applications being interacted with by the user, current or recent network state, how long it has been since the user interacted on a UI feedback element on the device; and the device management system 170 performs one or more of the following tasks: process the usage state information to select services or applications most advantageous to highlight to the user, or provide special use offers to the user, or create service launch object notification messages for a services or application, or re-locating a service launch object or updating (one or more of location, features, overlay, etc.) a service launch object icon, or create a new set of service launch object UI location instructions or placement policies for the device (for example, for the UI location manager 132); and send the new set of service launch object UI location, updates, instructions or placement policies to the device (for example, the UI location manager 132).
In some embodiments, the device management system 170 receives from the device the device usage state information from multiple devices in a device group (for example, multiple devices associated with a user, an enterprise, a family plan, etc.), including one or more of: the current state of service usage for one or more selected services, current or recent states of application usage for one or more selected applications, current or recent geographic locations, current or recent network destination history, current or recent applications being interacted with by the user, current or recent network state, how long it has been since the user interacted on a UI feedback element on the device; and the device management system 170 performs one or more of the following tasks: process the usage state information to select services or applications most advantageous to highlight to one or more users of the device group, or provide special use offers to one or more users of the device group, or create service launch object notification messages for a services or application to one or more users of the device group, or re-locating a service launch object to one or more users of the device group or updating (one or more of location, features, overlay, etc.) a service launch object icon to one or more users of the device group, or create a new set of service launch object UI location instructions or placement policies for the one or more devices of the device group (for example, for the UI location manager 132); and send the new set of service launch object UI location, updates, instructions or placement policies to the one or more devices of the device group (for example, the UI location manager 132).
In some embodiments, an updated (for example, dynamic) service launch object (for example, by changing one or more of service launch object location, or service launch object icon, or service launch object overlay feature, or service launch object notification message, or UI service launch partition message) is changed with a new service launch object UI policy instruction received by the device UI location manager 132 from a network element (such as the device management system 170).
In some embodiments, the UI location manager 132 or the device management system 170 update a service launch object (for example, by changing one or more of service launch object location, or service launch object icon, or service launch object overlay feature, or service launch object notification message, or UI service launch partition message) in order to change the level of user information or user attention gathering for one or more service launch objects.
In some embodiments, updating a service launch object in order to change the level of user information or user attention is desired because a UI location management service provider desires to change the user discovery or marketing messages associated with one or more service launch objects associated with one or more services or applications. In some embodiments, updating a service launch object in order to change the level of user information or user attention is the result of payments received by the UI location management service provider from service providers or application developers whose services or applications are being highlighted in the new service launch object UI locations, messages and discovery positioning. In some embodiments, updating a service launch object in order to change the level of user information or user attention is the result of the UI location management service provider benefiting directly from enhanced service or application usage by the user. In some embodiments, updating a service launch object in order to change the level of user information or user attention is encourages the user to try new services or applications that the user has not used before.
In some embodiments, updating (for example, dynamically modifying) a service launch object (for example, by changing one or more of service launch object location, or service launch object icon, or service launch object overlay feature, or service launch object notification message, or UI service launch partition message) by the device management system 170 is applied on one device at a time from a device group.
In some embodiments, updating (for example, dynamically modifying) one or more service launch objects (for example, by changing one or more of service launch object location, or service launch object icon, or service launch object overlay feature, or service launch object notification message, or UI service launch partition message) by the device management system 170 is applied on one device at a time in order to enhance the user discovery of one or more services or applications are put in effect for one device at a time in accordance to a desired improvement in service launch object discovery for that device. In some embodiments, for updating service launch objects for device groups, payments received by a UI location management service provider are for the device group and not just individual devices. In some embodiments, for updating service launch objects for device groups, payments received by a UI location management service provider are for the device group and not just individual devices, and the payments are adjusted as a function of how closely the device group information (for example, information derived from device usage state—history, logs, demographic, geographic, etc.) matches the desired device group information for the entity that is paying for enhanced service launch object discovery (or selection, or use, or clicks, etc.).
In some embodiments, the UI location management console 160 provides a web portal (for example, an automated or secure web portal) for application developers to log in to set up sponsored services or device discovery levels for their applications or services. In some embodiments, the web portal provides a variety of options in various embodiments, including but not limited to service launch object discovery pricing that varies with one or more of: time per day or per week or per month spent on a given discovery level; UI location; notification message type; notification message length, extent or content; notification message frequency; network state; device usage state. In some embodiments, the web portal provides one or more of: icon upload for user designed icons, upload of user application or application specification for application store or marketplace download; network destination (for example, URL, domain, website, IP address, port, etc.) for a browser based service; etc.
In some embodiments, updating (for example, dynamic) one or more service launch objects (for example, by changing one or more of service launch object location, or service launch object icon, or service launch object overlay feature, or service launch object notification message, or UI service launch partition message) by the device management system 170 in order to enhance the user discovery of one or more services or applications are put in effect in accordance to a desired improvement in service launch object discovery for multiple devices that are part of a device group. In such embodiments involving modifications to service launch object UI discovery management for device groups, payments received by a UI location management service provider are for the device group and not just individual devices, and the payments may be adjusted as a function of how closely the device group demographic information (for example, information derived from device usage state history) matches the desired demographics for the entity that is paying for enhanced service launch object discovery.
In some embodiments, the device management system 170 provides a bidding function for enhanced discovery of services or applications, wherein service providers (for example, shopping service providers, location based advertising providers, on-line sellers of merchandise, content providers, access service providers, streaming service providers, social network service providers, Internet search service providers, etc.) or application developers (developers of applications who whish their applications to be highlighted to device users) are provided with a bidding mechanism to bid on service launch object UI location placement, features and/or service launch object notification messages. In some embodiments, the device management system 170 provides a bidding function for enhanced discovery of services or applications, wherein service providers or application developers are provided with a bidding mechanism to bid on service launch object UI location placement, features and/or service launch object notification messages, wherein the highest bidder receives the service discovery position being bid upon.
In some embodiments, the device management system 170 provides a bidding function for enhanced discovery of services or applications, wherein service providers or application developers are provided with a bidding mechanism to bid on one or more service launch object properties: placement, icon features, icon overlay, icon format, notification messages. In some embodiments, the device management system 170 provides a bidding function for enhanced discovery of services or applications, wherein service providers or application developers are provided with a bidding mechanism to bid on one or more service launch object properties: placement, icon features, icon overlay, icon format, notification messages as a function of one or more of: network state, device usage state, user state. In some embodiments, the device management system 170 provides a bidding function for enhanced discovery of services or applications, wherein service providers or application developers are provided with a bidding mechanism to bid on one or more service launch object properties: placement, icon features, icon overlay, icon format, notification messages as a function of one or more of: network state, device usage state, user state, wherein the highest bidder receives the service discovery position being bid upon. In some embodiments, service launch object are classified based on UI location, icon features or service launch object notification messages into “service or application discovery levels,” wherein the premium levels of service discovery in general earn higher bids. Some embodiments involve classifying the service launch object UI location, icon features or service launch object notification messages into “service or application discovery levels,” wherein the premium levels of service discovery in general earn higher bids. In some embodiments, a higher discovery level typically gains more attention from the user by having one or more of: more prominent service launch object UI location placement, more frequent specific information regarding the service launch object, more prominent service launch object notification messages. In some embodiments, a premium discovery level has the service launch object icon placed in one or more of the following attributes: in first position in a permanent or prominent UI service launch partition, the device main screen, or a permanent launcher bar on the device, frequent service launch object notification, frequent service launch object notification involving device usage state dependent analysis for when to provide the notification messages. In some embodiments, a lower discovery level would typically cost a bidder less, involves placement in the application stable of the device with little or no service launch object notification messaging. In some embodiments, an in between (or intermediate or typical or standard) discovery level might include one or more of the following attributes: non-permanent placement (for example, the user can modify the placement or can remove the service launch object icon from all but the application stable) in a UI service launch partition or a secondary device screen, notification messaging taking place only at certain times of day or certain geographic locations.
In some embodiments, device management system 170 (or alternatively a service design center or UI location management console 160) presents device UI view of discovery position on bidding interface. In some embodiments, device management system 170 presents device UI view of icon animation on bidding interface. In some embodiments, device management system 170 presents device UI view of coupon issue from bidding interface. In some embodiments, device management system 170 presents device UI view of notification from bidding interface. In some embodiments, device management system 170 presents device UI view of notification animation or coupon animation from bidding interface.
In some embodiments, the device management system 170 supports static purchase of device UI discovery level via an automated secure portal interface. In some embodiments, the UI location management console 160 is configured as a secure web interface for remote terminals. In some embodiments, a remote terminal user can log into a user sign up system where the users credentials and credit are established. In some embodiments, the user of the device management system 170 (for example, service provider or application developer) purchases pre-configured discovery levels at pre-configured pricing for pre-configured device groups.
In some embodiments, the device group information (for example, demographics, device parameters, device user parameters) are displayed to the user of the device management system 170 to help in determining the relative value of the various levels of discovery available. In some embodiments, the user of device management system 170 purchases one or more of: a discovery level for a pre-determined period of time, or for a pre-determined number of user service launch object views, service launch object notification message views, or service launch object clicks.
In some embodiments, the device management system 170 supports dynamic bidding and purchase of device UI discovery level via an automated secure portal interface. In some embodiments, the UI location management console 160 is configured as a secure web interface for remote terminals. In some embodiments, a remote terminal user can log into a user sign up system where the users credentials and credit are established. In some embodiments, the user of the device management system 170 bids upon various device group discovery levels, with the winning bidder purchasing that discovery level. In some embodiments, the user of the device management system 170 bids upon various device group discovery levels, with the winning bidder purchasing that discovery level for one or more of: a pre-determined period of time, a pre-determined number of user service launch object views, service launch object notification message views, or service launch object clicks.
In some embodiments, the number of views or clicks or selections or usage are tracked by the device (for example, the UI location manager 132) and reported to the device management system 170. In some embodiments, the number of views or clicks or selections or usage are tracked or estimated by the device management system 170, by either estimating the number of views as a function of time or by observing network traffic, or by a combination of both.
In some embodiments, the device management system 170 is configured to allow a portion of the device UI (for example, a partition in a UI service launch partition) to be controlled by a third party, such as an application store or application marketplace service provider, or a search provider, or a location based services provider or a mobile device advertising provider. In some embodiments, the device management system 170 is configured to allow a portion of the device UI (for example, one or more partitions in a UI service launch partition) to be controlled by a third party, such as an application store or application marketplace service provider, or a search provider, or a location based services provider or a mobile device advertising provider for placement of service launch objects, for example, prioritized, ranked, displayed, tiered to enhance discovery of associated service or applications.
There are numerous other detailed embodiment examples for selling UI discovery levels to service providers, a third party, third party service providers, content providers, merchandise retailers or application developers, either with discovery levels that are pre-negotiated and fixed for a period of time or geography or device or user population, or discovery levels that are bid upon in real time, that one of ordinary skill in the art will now understand. The teachings here show how to devise embodiments that enhance the ability to advertise services or applications by associating the marketing messages directly with the location, appearance and notification information directly associated with a service launch object or service launch object icon.
In some embodiments, the UI location manager 132 (or some other device agent), or the device management system 170 evaluates a user's use of services in order to determine a new service plan or an alternate service plan that the user might benefit from or be willing to purchase (an “alternate service”). In some embodiments, a user is currently using a pre-paid hourly Internet access plan, and the user is using several hours per day, and there is a less expensive post-paid recurring service plan, then the post-paid recurring service plan is identified as an alternate service by service analysis algorithms in the UI location manager 132 (or some another device agent), or the device management system 170. In some embodiments, a user is subscribed to a first service and the UI location manager 132 or the device management system 170 identify a service launch object notification message that is associated with a service launch object for the alternate service, and the service launch object message is communicated to the UI location manager 132 (or might be pre-cached on the device for retrieval by the UI location manager 132), and the UI location manager 132 places the service launch object notification message advertising an alternate service on, in, touching or near the service launch object corresponding to the alternate service.
In some embodiments, a user is subscribed to a first service and the UI location manager 132 or the device management system 170 identify a service launch object notification message that is associated with a service launch object for the alternate service, and the UI location manager 132 places the service launch object notification message advertising an alternate service on, in, touching or near the first service launch object.
In some embodiments, the UI location manager 132 manages the UI locations contained in a UI service launch partition with one or more launch partitions for organizing or displaying service launch objects. In some embodiments, the UI service launch partition displays a controlled version of a service launch object icon that is similar to a “standard” (e.g., generic or typical or normal) service or application icon (for example, the standard application icon that comes with an application delivered by conventional means such as application store or marketplace, Internet download or device user load) that is available in other UI locations on the device controlled by the user.
In some embodiments, the UI service launch partition displays a controlled version of a service launch object icon that is similar to a standard service or application icon (for example, that may be available in other UI locations on the device controlled by the user) wherein the controlled service launch object icon that exists within the one or more service launch partitions in the UI service launch partition has an appearance within the UI service launch partition that is modifiable, a location within the UI service launch partition that is modifiable, or has service launch object notification messages applied within the UI service launch partition as described herein.
In some embodiments, the service launch object icon appearance modifications, location modifications or service launch object notification messages that are managed or applied within the UI service launch partition are under the control of the UI location management service provider by means of the device management system 170 and the UI location manager 132 while the standard service or application icon that is located outside the UI service launch partition is not modifiable by the device management system 170.
In some embodiments, the UI service launch partition is an application, widget, OS library function or other software module that is installed in the OS or added to the OS (the “UI discovery management module”) installed on the device. In some embodiments, the UI service launch partition is an application, widget, OS library function or other software module that is installed in the OS or added to the OS (the “UI discovery management module”) installed on the device for the purpose of modularizing the software required to perform the device computing operations, communication operations, UI display operations and other operations required to implement the UI location manager 132. In some embodiments, the UI location manager 132 is integral to or contained within the UI discovery management module that manages which service launch objects are displayed to the user, the organization (wherein organizing includes any or all of ordering, prioritizing, ranking, sorting, classifying, etc.) of the service launch object icons within the UI service launch partition (including which partition a given service launch object is displayed in, the service launch object order within the partition, whether or not the service launch object is in the first display screen or the user has to scroll to see it, etc.).
In some embodiments, the UI discovery management module has pre-assigned UI location or UI graphic areas within the one or more service launch partitions for displaying service launch objects. In some embodiments, in order to simplify the process of communicating service launch object notification messages or placing them with the correct service launch object, each pre-assigned UI location or UI graphics area has the ability to display one or more service launch object notification message types in pre-configured locations or message formats, with the UI location manager 132 maintaining a table (for example, an array, a matrix, a look up table, etc.) or other means to identify which UI location or UI graphics area a given service launch object is located in so that when the service launch object notification message needs to be displayed it is placed in the correct UI location or UI graphics area. In some embodiments, placing service launch object in pre-assigned UI location or UI graphics area reduces the complexity of the modification, placement or notification messaging applied to one or more service launch objects is simplified or the complexity of the UI location and notification messaging management instructions that are communicated from the device management system 170 to the UI location manager 132.
In some embodiments, service provider controlled UI launcher UI partition has a background that is different from the device screen background. In some embodiments, service provider controlled UI launcher UI partition has a background that is different from the device screen background, wherein different is one ore more of color, texture, font, transparency, intensity, gray scale, etc. In some embodiments, service provider controlled UI launcher UI partition has it's own background or is “opaque” to device screen background. In some embodiments, application or widget is “opaque” to screen background.
In some embodiments, service provider controlled UI launcher UI partition is partially visible relative (for example, translucent) to the background of the device screen.
In some embodiments, service provider controlled UI launcher UI partition is not visible (for example, it is transparent or see-through) and takes on the same background as the device screen. In some embodiments, the UI launcher UI partition takes on the background of a live wallpaper or other animated screen type.
In some embodiments, application or widget is “transparent” to screen background. In some embodiments, transparent application or widget to screen background is accomplished with a UI partition graphic that is transparent. In some embodiments, transparent application or widget to screen background is accomplished with a UI partition graphic that determines the screen background and uses it as the UI partition background. In some embodiments, transparent application or widget to screen background is accomplished with a UI partition that consists of several individual launcher icons rather than an entire screen area.
In some embodiments, where the UI discovery management module is a OS library function or other software module that is installed in the OS or added to the OS for a group of devices the advantageous aspects of the invention are included directly in the device OS. In some embodiments, wherein the UI discovery management module is a software application or widget it may be downloaded (for example, “over the air” (OTA) or “over the Internet”) by a user, or installed by a user, or installed by a device OEM, or installed by a service provider or installed by a device distribution agent without the need to include it in the device OS. In some embodiments, wherein the UI discovery management module is a software application or widget not included in the device OS, a download of the UI discovery management module provides the ability to control the service launch object icon appearance (for example, features, overlay etc.), location or notification messages in a controlled manner within the UI discovery management module. In some embodiments, wherein the UI discovery management module is a software application or widget independent (for example, optional or not integral or erasable without affecting OS other operations) of the device OS, a download of the UI discovery management module provides the ability to control the service launch object icon appearance (for example, features, overlay etc.), location or notification messages in a controlled manner within the UI discovery management module. In some embodiments, wherein the UI discovery management module is a software application or widget not included in the device OS, a download of the UI discovery management module provides the ability to control the service launch object icon appearance (for example, features, overlay etc.), location or notification messages in a controlled manner within the UI discovery management module without the need to control other (including for example, similar) application icons on the rest of the device that are controlled by the user. In some embodiments, a UI location management service provider manages the discovery of service launch objects with little or no need to undertake the complexities of device software integration or OS software integration.
In some embodiments, a UI location management service provider, wherein the UI discovery management module is a software application or widget that may be downloaded the complexities of OS software integration are reduced (for example, avoided).
In some embodiments, an organization screen is provided in the UI service launch partition to provide the user with a list of UI service launch partitions that the user can to choose from for displaying one or more categorized (wherein categorized may also be classified, ranked, organized) service launch objects within one or more partitions within the UI service launch partition. In some embodiments, the organization screen provides a user the option to select from a one or more display screens that each consist of one or more UI service launch partition that organizes a categorization of service launch objects. In some embodiments, the organization screen provides a user the option to select from a one or more display screens that each consist of one or more UI service launch partition that organizes a categorization of service launch objects and upon selection the user is provided with a categorization screen. In some embodiments, the categorization screen comprises display screens that organize service launch objects for one or more of: service plan types (have been purchased, available but have not been purchased, sponsored, free, paid, pre-paid, post-paid, recurring, time based, usage based, trial offers, special offers, family plan services, multi-device services, enterprise or work services, consumer services, etc.), services categorized by application type (for example, music and video, news, browsing, voice and video communications, shopping, location services, live event services, one time special event services, etc.), demographic based categorization (for example, work vs. play services, teen demographic services, pre-teen services, family services, etc.), etc.
In some embodiments, the organization screen displaying multiple categorizations of service launch objects is the first screen the user sees (the UI discovery module “default” screen). In some embodiments, the organization screen is accessed by the user via a user action (for example, a voice command, keep pad input, selecting the screen or clicking a UI button). In some embodiments, a organization screen may be provided wherein the user may select from a set of options to display one or more UI service launch partition categories on the default user partition display in the UI service launch partition. In some embodiments, a user may select to display one or more service launch partitions from: free services, pre-paid services and trial services partitions (or any other available service launch object categories) within the UI service launch partition. In some embodiments, a user may elect not to display one or more of post-paid or recurring services (or any other available service categorization). In some embodiments, a subset of the service launch partitions are user selectable. In some embodiments, a subset of the service launch partitions are not user selectable. In some embodiments, a subset of the service launch partitions are exclusively controlled by the device management system 170 via the UI location manager 132. In some embodiments, a some of the service launch partitions are user selectable while others are controlled by the device management system 170 via the UI location manager 132. In some embodiments, if too many service launch partitions are available within the UI service launch partition for simultaneous display to the user, then the UI service launch partition can provide for scrolling through the available service launch partitions.
In some embodiments, the UI discovery management module provides for an alternative display of service usage for one or more service launch objects wherein one or more service launch object identifiers (for example, service launch object icon) are displayed along with a usage indication for the one or more service launch objects. In some embodiments, the UI discovery management module provides for an alternative display of service usage, wherein the service usage is categorized. In some embodiments, service usage is categorized by service launch object. In some embodiments, service usage is categorized by (or further broken down by) one or more of application, network destination, network communication end-point (e.g., source or destination), application type, service type, network type, home vs. roaming, geography and service class.
In some embodiments, service or application discovery level (for example, discovery position) revolve through a UI partition according to a service launch object priority. In some embodiments, one of more of: a discovery level position or a discovery position range, a time in discovery position, a percent of time in discovery position, number of views or clicks, etc. are specified. In some embodiments, notification messaging is specified as a percent of service launch object icon interactions (for example, views, clicks, touches, voice commands, etc.).
In some embodiments, UI 160 manages at least a part of the device UI 136 presentation. In some embodiments, UI 160 manages at least a part of the device UI 136 presentation wherein presentation comprises one or more of view, display, format, number of screens. In some embodiments, UI 160 manages at least a part of the device UI 136 view for one or more of service launch object UI location, service launch object notification messages, service launch partition, service object launcher, UI discovery, service launch object icon. In some embodiments, UI 160 manages at least a part of the device UI 136 view for one or more of service launch object UI location, service launch object notification messages, service launch partition, service object launcher, UI discovery, service launch object icon based on user input (for example, user profile or preferences) or user behavior (for example, usage history or logs).
In some embodiments, UI 160 includes a console UI with view of device UI 136 one or more screens. In some embodiments, UI 160 includes a console UI with view of device UI 136 service launch partition. In some embodiments, UI 160 includes a console UI with view of device UI 136 for arranging configurations for service launch partitions. In some embodiments, UI 160 includes a console UI with view of device UI 136 for arranging configurations of one or more of skins, branding, color scheme, buttons and button arrangements. In some embodiments, UI 160 includes a console UI with view of device UI 136 to drag and drop (wherein for all instances drag and drop may be exchanged for drag or drop or move up or move down) of service launch object onto desired location in UI location management console 160 device UI launcher view for accomplishing correct positioning of service launch object on device. In some embodiments, UI 160 includes a console UI to associate service launch object icons with service launch object configuration elements.
In some embodiments, UI 160 enables drag and drop of service launch object onto a desired location in UI 160 device UI launcher view to provision the device with service launch object parameters. In some embodiments, UI 160 associates service launch object icons with service policy elements in UI location management console 160.
In some embodiments, UI 160 enables drag and drop of service launch object onto desired locations in UI 160 device UI launcher view to define service plan or service plan component policies for the service launch object.
In some embodiments, UI 160 enables managing one or more of service launch object UI location, service launch object notification messages, service launch partition, service object launcher, UI discovery, service launch object icon as a function (or based on) network state, and device usage state.
In some embodiments, UI 160 defines a dynamic service launch object icon as a function of state, wherein the dynamic icon feature include one or more of icon service launch object appearance, overlay, placement, notification messages, etc.
In some embodiments, UI 160 defines a dynamic service launch object icon as a function of state, wherein the state includes one or more of network state, device usage state, and user state.
In some embodiments, UI 160 defines icon appearance as a function of network state or device usage state by selecting an icon and a secondary network state or device usage state screen to enter secondary appearance graphics (for example, one or more of: a new icon, an icon overlay, icon superposition). In some embodiments, UI 160 defines icon notification messages as a function of network state or device usage state by selecting an icon and a secondary network state or device usage state to enter secondary notification messages (for example, one or more of: type notification message text, select format, select graphics, select background, select a message from a table, etc.). In some embodiments, UI 160 defines icon notification message type as a function of network state or device usage state by selecting an icon and a secondary network state or device usage state to enter secondary notification messages. In some embodiments, UI 160 defines icon notification message type as a function of network state or device usage state by selecting an icon and a secondary network state or device usage state to enter secondary notification messages from one or more of: select notification message graphics background from drag and drop list, or enter new graphics, or type in notification message or choose from pre-specified list.
In some embodiments, UI 160 defines UI device views as a function of OS versions or device type. In some embodiments, UI 160 defines UI device views for a device group. In some embodiments, UI 160 defines UI device views for a device group sharing notification messages or icon appearance. In some embodiments, UI 160 defines UI device views for a device group includes one or more of: a configuration of launch objects, UI partitions, skins, branding, messages, etc. In some embodiments, UI 160 defines UI device views for a device group includes selecting notification messages or icon appearance from a common list.
In some embodiments, UI 160 includes a console UI “sandbox” for developers to manage (for example, design, modify, update, select, pick) a service plan. The UI sandbox provides third parties or developers with at least a subset of the suite of service plan management tools available to the service provider. In some embodiments, UI 160 management of a service plan comprises defining discovery position or time in discovery position.
In some embodiments, UI 160 management of a service plan comprises specifying time in discovery position based on a revolving percentage of time. In some embodiments, UI 160 management of a service plan comprises defining time in discovery position based on a screen view percentage.
In some embodiments, UI 160 management of a service plan comprises a developer entering credit credentials. In some embodiments, UI 160 management of a service plan comprises a developer billing based on more of more of: discovery position, discovery time in position, discovery percentage of time, number of views, number of clicks, notification messages (for example, one or more of frequency, period, duty cycle, dwell time, view refreshes, percentage, relationship with other notification messages), purchase revenue share, analytics generated messaging.
In some embodiments, UI 160 management of a service plan comprises a developer billing based on revenue share. In some embodiments, UI 160 management of a service plan comprises a developer obtaining analytics generated messaging.
In some embodiments, management system 100 includes auto-download of associated service or application after UI launcher receives service launch object.
In some embodiments, management system 100 includes auto-download of application when UI launcher receives service launch object so that user does not have to do this through marketplace. In some embodiments, the developer pays (or is billed) for auto-download of application or service capability.
In some embodiments, if a service or application or website is blocked (e.g., the device is not authorized to use the application or access the website under a current service plan or service policy), a notification message (for example, a text string with the blocked message) is presented that no plan is available to allow the service or application or website. In some embodiments, a button is provided to dismiss the message. In some embodiments, a button is provided to manage (for example, stop or stall or put into the background or kill) the service or application or website. In some embodiments, a button is provided to launch the user into an application management screen to manage (for example, stop or stall or put into the background or kill) the service or application or website.
In some embodiments, the UI location management system is associated (for example, coupled) to an application store or marketplace. In some embodiments, when or after an application developer uploads applications, the application developer receives an offer to bid on one or more of more of: discovery position, discovery time in position, discovery percentage of time, number of views, number of clicks, notification messages (for example, one or more of frequency, period, duty cycle, dwell time, view refreshes, percentage, relationship with other notification messages), purchase revenue share, and analytics generated messaging. In some embodiments, when or after an application developer uploads one or more applications, the application developer receives an offer based on revenue share. In some embodiments, when or after the application developer uploads applications, the application developer receives analytics generated messaging.
In some embodiments, when or after an application developer uploads applications, the application developer receives an offer to bid on one or more of more of: discovery position, views, time in position with percentage, clicks, messaging frequency (time, view refreshes, percentage), icon animation, icon feature change, purchase revenue share, analytics generated messaging.
In some embodiments, the management system 100 recognizes the service or application plans a user (or device) has, and the launcher has a buy up (or upsell) selection (for example, a button) that offers upgrades. In some embodiments, the management system 100 recognizes the service or application plans a user (or device) have and the UI 136 has a buy up button that offers upgrades.
In some embodiments, an offer to buy-down (or downsell) is buried in (e.g., available through) a lower discovery screen.
In some embodiments, an offer to buy-down is buried in a lower discovery screen that has a larger number (including all) of service launch object choices and that the user has to discover through a multi-screen navigation.
In some embodiments, management system 100 includes a web application programming interface (API) and application to implement a service object launcher widget. In some embodiments, management system 100 includes a website to implement service object launcher widget.
In some embodiments, service launch objects are organized into categories set by the UI location management server 150. In some embodiments, service launch objects are organized into categories set by the device management system 170 as controlled by a service provider.
In some embodiments, the UI 136 is partitioned in areas of carrier (or service provider) control only or user control only or shared carrier and user control.
In some embodiments, a service launch object assists or becomes a discovery mechanism comprising one or more of the following: changing appearance of the service launch object based on carrier (wherein carrier could be a service provider or third party) control, placing notification messages on, in or near service launch object under carrier control, duplicating (for example, with derivate or modified or enhanced) icons of standard application icons, where duplicate icons are under carrier control and initiate other processes on the device (in addition to or instead of launching the service or application), automatic appearance or addition or removal of launch objects in a category, changing launch object categories, offering a marketing vehicle for application developers to market their services or applications.
In some embodiments, a service or application developer makes a widget (to replace the standard service or application icon) that the service or application developer controls and uses it to market a service or application. In some embodiments, a plurality of service or application developers make a widget to market a service or application. In some embodiments, a plurality of service or application developers share a widget by a third party to market a service or application. In some embodiments, a carrier or service provider or OEM desires to control network load or user attention (for example, so-called “eyeballs”). In some embodiments, a carrier or service provider or OEM desires to control network load or user attention by a shared widget to market services or applications. In some embodiments, management system 100 provides a platform for a many (for example, a plurality of service or application providers) to one (shared device management system or application store or widget) to many (for example, a plurality of devices or users) marketing platform for one or more of: place notification messages (for example, promotions) on service launch object icons, move/add/delete service launch object icons, manage appearance of icons. In some embodiments, management system 100 provides a marketplace for service or application developers or service providers to promote their service or application with a service launch object icon. In some embodiments, management system 100 provides a marketplace for service or application developers or service providers to highlight their icons in the device discovery process.
In some embodiments, management system 100 provides service or application developer levels (where levels is equivalent to classes, categories, ranking, etc.). In some embodiments, management system 100 provides service or application developers one or more levels, with each level including one or more of the following features: place service or application in market place, monetize service or application use (for example, charge by view, click, time, update rate, bandwidth, etc. or for example, separate category for all application related traffic), positioning, amount of time/views/clicks in service discovery launcher, priority positioning, priority amount of time/views/clicks in service discovery launcher. In some embodiments, management system 100 offers service or application developers charge by view or click at a given developer or discovery level.
In some embodiments, a service launch object ad is the presence of the service launch object icon in a managed system that controls the device service launch object icon service discovery level. In some embodiments, ads are for a service or application on the device. In some embodiments, ads are associated to a plurality of applications. In some embodiments, an ad management system determines a service or application on device 132 and provides an ad based on controlling the service launch object.
In some embodiments, the ad management system determines a subset of service or applications on device 132 and manages ads to multiple applications at the same time. In some embodiments, the ad management system advertising functionality comprises downloading the service or application, and highlighting the application on the UI.
In some embodiments, the ad management system presents the service launch object icon as if the service or application had been selected, and initiates other processes in addition to launching the service or application when the service launch object icon is selected. In some embodiments, the ad management system presents the service launch object icon as if the service or application had been selected, and initiates other processes comprising recording the selection for one or more of: analytics, usage statistics, charging, providing service sign up notification or usage notification (for example, “here are your options for service to use this application” or a roaming warning), download the applications, etc.
In some embodiments, ads are associated to a launch partition in, on, or near the service launch object being advertised. In some embodiments, an ad is placed directly on or next to the service launch object icon. In some embodiments, an ad is placed in a banner (for example, a ticker tape). In some embodiments, the device UI portion reserved for ads includes several classified (or tiered or ranked) partitions for ads (for example, a plurality of tiered banners). In some embodiments, the device UI portion reserved for ads includes several classified (or tiered or ranked) partitions for ads (for example, a plurality of tiered banners) and the ad management system places ads into each classified partition based on one or more of network, device usage, device or user state and desired discovery level. In some embodiments, the device UI portion reserved for ads includes several classified (or tiered or ranked) partitions for ads (for example, a plurality of tiered banners) and the ad management system places (alternatively prioritizes) ads into each classified partition based on one or more of network, device usage, device or user state and desired discovery level and bids from one or more ad providers.
In some embodiments, service launch object icon features are varied to increase or decrease service discovery (for example, highlight one or more apps, grey-down one or more apps). In some embodiments, ads associated to service launch object have icon features other (for example, different) than the icon features on the service launch object itself.
In some embodiments, service launch object icons are made available according to a priority policy. In some embodiments, a user controls service launch object presence or placement in certain device UI areas, and service provider controls presence and placement in other UI areas. In some embodiments, the device 130 has a permanent UI placement area that user cannot remove or modify service launch object. In some embodiments, the ads are placed in a service provider controlled device UI area, and dynamically change placement (for example, rotate or round-robin based on a random or ranked method) for presentation to a user.
In some embodiments, management system 100 creates a service launch object icon similar to or identical to the standard service or application icon. In some embodiments, management system 100 places the service launch object icon in a UI discovery location or applies notification messaging on, in or near the standard service or application icon or modifies the service launch object icon appearance according to a service discovery priority policy for that service launch object.
In some embodiments, selecting the service launch object icon registers the selection for one or more of the following functions: usage history log, click charging, intercepting the service or application launch and providing service notifications, downloading the associated service or application, launching the service or application.
In some embodiments, a list of device service or application are obtained (for example, a search by UI location manager 132) for on device screen or in application stable. In some embodiments, management system 100 indicates that the service or application is on device to a marketing message management system. In some embodiments, the marketing message management system places service launch object icon for service or application in UI launcher. In some embodiments, the marketing message management system checks a device or user service plan status (for example, state) and if appropriate provides a marketing message to the user for services associated with that service or application. For example the marketing message management system notices the device has the YouTube application installed but does not have a special media streaming plan in place, and generates the marketing message: “would you like to learn more about a special media streaming plan service option?”
In some embodiments, the marketing message management system checks a device or user service plan status (for example, state) and generates a marketing message to the user for services associated with that service or application and the marketing message management system sends marketing messages related to the service or application. In some embodiments, the marketing message management system enters information of the device receiving the marketing message into a differentiated demographics value database indicating that marketing messages for that service or application are more valuable when sent to that device. In some embodiments, the marketing database charges more for sending marketing messages for that application to that device.
In some embodiments, interactions (responses, views, etc.) of a user with marketing messages are entered into a demographics value database for analysis (for example, regression, model fitting, classification, etc.). In some embodiments, the marketing message management system charges more for sending marketing messages for service or application to devices associated (for example, correlated) with analysis database information. In some embodiments, UI location manager 132 receives (for example, accepts) marketing message, finds service or application, places message on, in or near service or application.
In some embodiments, configuration or management of a UI launch area or other discovery management functions is performed by a device management agent, for improved user experience response time (for example, as user controlled UIs).
In some embodiments, configuration or management of UI launch area or other discovery management functions is performed by a device management agent, resulting in device software that is specific to a given OS. In some embodiments, the device management agent (for example, UI location management 132) accepts policies from a policy server (for example, UI location management server 150) to define one or more of UI launcher: launch partition, service launch object classification, configuration, branding, device placement, icons, icon placement, icon features, icon overlay, icon messaging, icon rotation, highlighting, messaging policies, icon launch processes.
In some embodiments, the device management agent (for example, UI location management 132) performs periodic update of service launch object (for example, one or more of service launch object icon, placement, notification messages, classification), or update of service launch object when user first clicks on portal widget. In some embodiments, the device management agent (for example, UI location management 132) downloads service or application (for example, if not available on device) via portal or portal instruction to download from application store or marketplace. In some embodiments, the device management agent (for example, UI location management 132) comprises device UI management policy instructions tied to UI location management console 160 which configures all of above. In some embodiments, UI location management console 160 accepts manager input and provisions device UI management policy instructions.
In some embodiments, the device management agent is assisted by a portal application and portal server API to define a part of policy on portal server rather than managing all on device. In some embodiments, this assistance provides an option for computation complexity sharing and device response time to user.
In some embodiments, the device management agent being assisted by a portal to define a part of a policy on a portal server results in less OS-specific software on device or a longer UI response. In some embodiments, the device management agent being assisted by a portal to define a part of policy on portal server results in considerable OS-specific software and slowed device responsiveness.
In some embodiments, the device management agent being assisted by a portal to define a part of policy on portal server (for example, UI location management server 150) to define one or more of UI launcher: launch partition, service launch object classification, configuration, branding, device placement, icons, icon placement, icon features, icon overlay, icon messaging, icon rotation, highlighting, messaging policies, icon launch processes.
In some embodiments, the device management agent (for example, UI location management 132) being assisted by a portal to define a part of policy on portal server (for example, UI location management server 150) performs periodic update of service launch object (for example, one or more of service launch object icon, placement, notification messages, classification), or update of service launch object when user first clicks on portal widget. In some embodiments, the device management agent (for example, UI location management 132) being assisted by a portal to define a part of policy on portal server (for example, UI location management server 150) downloads service or application (for example, if not available on device) via portal or portal instruction to download from application store or marketplace. In some embodiments, the device management agent (for example, UI location management 132) being assisted by a portal to define a part of policy on portal server (for example, UI location management server 150) comprises device UI management policy instructions tied to UI location management console 160 which configures all of above. In some embodiments, UI location management console 160 accepts manager input and provisions API information.
In some embodiments, the management system 100 is website based and results in minimal OS specific software on device or longer UI response. In some embodiments, the website-based approach provides less OS-specific device software, but has a longer UI response.
In some embodiments, the website based management system 100 manages one or more of UI launcher functionality: launch partition, service launch object classification, configuration, branding, device placement, icons, icon placement, icon features, icon overlay, icon messaging, icon rotation, highlighting, messaging policies, icon launch processes.
In some embodiments, the website based management system 100 performs periodic update of service launch object (for example, one or more of service launch object icon, placement, notification messages, classification), or update of service launch object when user first clicks on portal widget. In some embodiments, the website based management system 100 downloads from application store or marketplace. In some embodiments, the website based management system 100 comprises device UI management policy instructions tied to UI location management console 160 which configures all of above. In some embodiments, UI location management console 160 accepts manager input and provisions device UI management policy instructions.
In some embodiments, UI location management console 160 displays a device view for manager (for example, carrier, service provider, third party, service or application developer) to drag and drop icons or to drag and drop icons into discovery priority bin for one or more of the following management location options: device management agent based with policy download, portal based with API server log in, or website based. In some embodiments, UI location management console 160 displays device view for manager to specify messaging, or messaging taken from sponsor sandbox or for manager to drags and drops icons into messaging frequency policy bin for one or more of the management location options: device management agent based with policy download, portal based with API server log in, or website based.
In some embodiments, a policy to control (for example, one or more of: allow, block, warn, throttle, background, etc.) a service or application is combined with the policy to present (for example, display) of service launch object (for example, through service launch object icon).
In some embodiments, after a service or application that is attempted is identified, the application is offered as a service launch object in the “unpaid services,” “paid services,” or “free trial” offers. In some embodiments, when a user selects an unpaid service or application, a serve up service offer notification message is presented to the user. In some embodiments, the service launch object icon is used to get the user to try or buy services. In some embodiments, the device shares with a server that a service or application was attempted under a plan that did not cover the service or application. In some embodiments, after the device shares with a server that a service or application was attempted under a plan that did not cover the service or application, the server creates an offer notification message and instructs device to offer service or application in free trial area of service UI. In some embodiments, after the device shares with a server that a service or application was attempted under a plan that did not cover the service or application, a service launch object icon associated with the service or application is included in launcher.
In some embodiments, statistics are collected on one or more top applications tried but not paid for. In some embodiments, a user enters new trial plan by hand.
In some embodiments, the device management system 170 highlights (for example, with notification messaging) to devices where users have tried to install. In some embodiments, the device management system 170 or UI location manager 132 perform automated association of application with application specific policies and notification for free trial. In some embodiments, the device management system 170 or UI location manager 132 perform automated association of application notification for a bulk bucket free trial (“click here for a free trial of a service plan that will allow ‘textstringxyz’ app”).
In some embodiments, user friendly services or applications increase revenues by expanding data users or expanding data devices. In some embodiments, user friendly services or applications increase value for one or more of service providers, access carriers, OEMs, third party over-the-top service or application providers, chipset providers and OS providers.
In some embodiments, a device is configured for select or trial or sponsored data access prior to delivery to a user. In some embodiments, a device is configured for select or trial or sponsored data access prior to delivery to a user, and the user does not need to configure or pay for partial service access. In some embodiments, basic device access is sponsored right out of the box and the user does not need to do anything to activate service. In some embodiments, from this sponsored out of the box condition, the user has certain “free” services that are sponsored by the service provider or third party. In some embodiments, the sponsored right out of the box devices include one or more of: sponsored website and application connection services, access to the carrier store, a limited amount of application specific services and bulk Internet access services that are provided on a trial (or limited or capped) basis. In some embodiments, the consumer is provided with an intuitive service or application user interface (for example, a permanent services discovery area on the device UI) where the user can instantly select from any number of service plans that are configured by the service provider.
In some embodiments, the arrangement of the permanent services discovery area on the device UI is OTA-configurable by the device management system 170 controlled by the carrier. In some embodiments, the enforcement of the required network control, charging or notification policies required to support service offerings, including one or more of sponsored and paid service offerings, is OTA-configurable by the device management system 170 controlled by the carrier. This policy enforcement and configuration capability is far beyond anything else in the market or on the drawing boards in the carrier network equipment world.
In some embodiments, over-the-top services or applications are monetized by managing application or service discovery placement and advertising. In some embodiments, an over-the-top service or application for a device group is sponsored, where the over-the-top service provider or application developer bids on earning a service discovery position for their service or application.
In some embodiments, a portion of the device home screen or other portions of the device UI are remotely configured or re-configured as a permanent carrier controlled service or application discovery UI environment. In some embodiments, a portion of the device home screen or other portions of the device UI are remotely configured or re-configured as a permanent carrier controlled service or application discovery UI environment (for example, dynamically or periodically or state based) by an OTA device management system 170. In some embodiments, an OTA device management system 170 configuration controls what the user can modify and what they cannot.
In some embodiments, the service or application icons displayed in the permanent discovery area are used to display a service or application launch opportunity the carrier wishes to provide the user.
In some embodiments, when the user selects a service launch object icon in the discovery area, the device inserts notification messages prior to, concurrently or after launching the service or application. In some embodiments, the notification messages include service plan offers customized to the service or application, service usage warnings (for example, service or application uses a lot of data, or service or application causes high roaming costs, etc.), offers for a related service or application, etc. In some embodiments, notification messages associated with a service launch object icon launch are OTA-configured.
In some embodiments, a network entity of management system 100 provides updates to the service launch object management (for example, UI discovery, placement, notification message, etc.). In some embodiments, a network entity of management system 100 provides a partial (or full) software upgrade for managing a service launch object. In some embodiments, a network entity of management system 100 provides updates to the policy or policy software or policy parameters associated with a service launch object. In some embodiments, a network entity of management system 100 provides a policy software updates to device 130. In some embodiments, a network entity of management system 100 provides service launch object management (for example, UI discovery policy) software updates to device 130. In some embodiments, a network entity of management system 100 provides a partial of full software upgrade (including new device software) to enable or update service launch object management (for example, UI discovery policy) to device 130.
In some embodiments, the service or application icons are re-arranged (for example, dynamically re-classified, re-ranked, re-prioritized, re-sorted) according to a discovery priority policy set by the device management system 170. In some embodiments, the re-arrangement is static between discovery policy updates between the device management system 170 and the device. In some embodiments, the re-arrangement is dynamic between policy updates between the device management system 170 and the device, wherein the arrangement of the service or application is modified periodically. In some embodiments, the re-arrangement is based on one or more of: interactions (for example, how many views, clicks, selections, voice commands) of the user with the UI launch area, whether or not the service launch object icon has been selected or a number of selections, how much time has elapsed, the geography the device is in, the network the device is connected to, network state, the time of day, the applications the user has recently been using, the websites the user has recently been using, cognitive state of the device, device parameters, user parameters (for example, profile, preferences), etc. In some embodiments, each service launch object icon has a discovery placement priority policy so that some service launch object are always displayed in a high discovery location, some service launch object are often displayed in a high discovery location, and some service launch object are rarely or never displayed in a high discovery location.
In some embodiments, a subset of service launch object icon within the launch area have a marketing message placed on it according to a service discovery policy. In some embodiments, the marketing message is defined by the service provider or entered into the service provider system by the service or application sponsor.
In some embodiments, each service launch object icon has a messaging priority policy so that some service launch object have frequent discovery messages, some service launch object have less frequent service discovery messages, and some service launch object rarely or never get service discovery messages. In some embodiments, the frequency of service launch object discovery messages is based on one or more of: interactions (for example, how many views, clicks, selections, voice commands) of the user with the UI launch area, whether or not the service launch object icon has been selected or a number of selections, how much time has elapsed, the geography the device is in, the network the device is connected to, network state, the time of day, the applications the user has recently been using, the websites the user has recently been using, cognitive state of the device, device parameters, user parameters (for example, profile, preferences), etc.
In some embodiments, management system 100 manages one ore more of: which or how many service discovery message the service provider wants displayed on service launch object icon at a given time (for example, number of simultaneous messages, dwell intervals, time spacing, etc.), how many service discovery messages should be displayed as a function of time, service discovery messages as a function of one or more: time of day, geography, network state, device cognitive state, user state, user interaction with the device, etc.
In some embodiments, the management system 100 locates a service launch object that has been downloaded to the device by the user and places service launch object icons in the launch area. In some embodiments, placing user-downloaded service launch object icons in the launch area is advantageous when the carrier offers services associated with the service or application that the carrier desires to promote. In some embodiments, this is advantageous if the service or application sponsor is willing to pay the carrier for increased discovery priority when the user has downloaded the service or application.
In some embodiments, the management system 100 locates a user service or application that has been downloaded to the device, identifies the location in the UI where the service launch object icon has been placed by the user, and provide service or application marketing messages in, on, or near the service launch object icon. In some embodiments, a marketing message is defined by the service provider or entered into the service provider system (for example, a service design center) by the service or application sponsor.
In some embodiments, each service launch object icon defined by the service provider or entered into the service provider system has a messaging priority policy so that some service launch object have frequent discovery messages, some service launch object have less frequent service discovery messages, and some service launch object rarely or never get service discovery messages.
In some embodiments, the frequency of service launch object discovery messages is defined by the service provider or entered into the service provider system and is based on one or more of: interactions (for example, how many views, clicks, selections, voice commands) of the user with the UI launch area, whether or not the service launch object icon has been selected or a number of selections, how much time has elapsed, the geography the device is in, the network the device is connected to, network state, the time of day, the applications the user has recently been using, the websites the user has recently been using, cognitive state of the device, device parameters, user parameters (for example, profile, preferences), etc. In some embodiments, the service provider (or entered into the service provider system) manages one ore more of: which or how many service discovery message the service provider wants displayed on service launch object icon at a given time (for example, number of simultaneous messages, dwell intervals, time spacing, etc.), how many service discovery messages should be displayed as a function of time, service discovery messages as a function of one or more: TOD, geography, network state, device cognitive state, user state, user interaction with the device, etc.
In some embodiments, the management system 100 locates a user service or application that has been downloaded to the device, identifies the location in the UI where the service launch object icon has been placed by the user, and overlays graphics or text or sounds (for example, a modified icon) in, on, or near the service launch object icon to provide one or more of: highlight the discovery level of the service launch object (or associated service or application) to the user, indicate whether the service or application can access the network (for example, wireless wide-area network (WWAN)) given the services available to the user (for example, services the user has elected to pay for), indicate whether the service or application is free or is charged to a user bucket, indicate whether the service or application currently has access to the network (for example, WWAN or WiFi) or not (for example, roaming policies can be set up according to applications, network policies can be set up according to application [4G, 3G, 2G, WiFi, etc.], QoS or congestion policies can be set up according to applications, etc.).
In some embodiments, management system 100 is configured with a device management secure back-end portal controlled by the carrier.
In some embodiments, the management system 100 device management secure back-end portal has a sandbox capability that allows service or application sponsors (or developers) to log in and pay for, or bid on one or more of the service or application discovery services described above. In some embodiments, the system provides for bidding on discovery location, message frequency, views, clicks, etc.
In some embodiments, the user gets more control of the device UI when the user pays more (for example, buys up or purchases an upsell service). In some embodiments, the user gets less control of the device UI in exchange for a service plan discount from the service provider. In some embodiments, higher levels of service plan (for example, more expensive plans, or by accumulating rewards from service or application usage) provide higher levels of UI customization. In some embodiments, the user gets a discount or a sponsored service (for example, subsidized service or application access) in exchange for allowing the service provider (or some other network entity, such as an application provider) to control the device UI. In some embodiments, the user receives a discount on device service to turn over a UI portion or partition of the device.
In some embodiments, two or more network entities (for example, a carrier and an application developer) share the revenue for an over-the-top service. In some embodiments, two or more network entities (for example, carrier and application developer) share the revenue for an over-the-top service (for example, a service launch object associated to a service or application or content), where one entity provides the service, application or content and the other entity provides the access.
In some embodiments, the device UI changes as user changes service plan. In some embodiments, the device UI shows free service or application until the user tries the service or application. In some embodiments, after the user tries the service or application, the service launch object shows entry level paid service or application. In some embodiments, after the user tries the entry level paid service or application, the service launch object shows upgrade service or application (for example, upsells). In some embodiments, if the usage of service or application (or revenue) falls back, the service launch object shows a lower cost alternative (for example, free service or application again). In some embodiments, the management system 100 change offered service launch object (or associated service or application) based on the available service launch object on the device.
In some embodiments, service plans are sorted from lowest to highest cost data plans based on (or normalized) a per unit time basis based on a number of previous weeks of usage. In some embodiments, only upsell (or buy up) service plans are shown in the sorted list.
In some embodiments, a user or network entity has several options for sponsored data and an auction (or bidding engine) selects the winning service.
In some embodiments, a service or application provider bids for UI discovery or placement (based on priority, user demographics, network state, device usage state, device cognitive state) over one or more geographies (for example, one or more area codes or cities) or over one or more geography tiers (nationwide, statewide, regional, sub-regional, address plus radius). In some embodiments, higher geography tiers receive a bid discount (for example, nationwide has a lower normalized cost than statewide).
In some embodiments, the service launch object provides control of the service or application. In some embodiments, the service launch object intercepts and controls the service or application. In some embodiments, the service provider (or OEM) takes over the service or application by installing a service launch object associated to the service or application. In some embodiments, the service launch object is associate to multiple service or application and has a table of service or application with policy entries for one or more of the associated service or application. In some embodiments, the policies comprise one or more of: hold launch, notify (user or network entity) of launch, acknowledge selection of service or application, launch service or application and log acknowledgement in customer care, notify in parallel to launch, block launch, block launch and notify user or network entity, notify, acknowledge (for example, log selection).
In some embodiments, the notification associated to the service or application associated to the service launch object comprise one or more of the following types of notification: need a service plan, selected application is expensive on this network, selected application is expensive when roaming, an advertisement associated to service or application (typically in parallel, but could be in series), offering alternate applications, offering related applications, offering related activity, offering related merchandise, combine with location, state, etc. information. In some embodiments, the notification associated to the service or application associated to the service launch object comprise informing a user of fraud. In some embodiments, the service is discontinued or discounted or service use is accelerated based on fraud. In some embodiments, the notification ranks service or applications according to what is about to run out. In some embodiments, the notification ranks service or applications according to what is about to run out and give an option to click down.
In some embodiments, the service provider manages location management service or application (for example, access services).
In some embodiments, the service launch object icon is the standard (wherein standard could refer to the generic, normal or typical) icon, and the management system 100 provides one or more of UI placement, location discovery (for example, including selecting portions in one or more UI partitions or tiers or classification) and network entity based policies (or directly managed by network entity) for the standard application icon.
In some embodiments, a service or application is launched when a network state change occurs, an entity of management system 100 obtains usage counts to determine that a service or application is in use, searches through table (for example, for policy instructions associated to service or application) associated with service or application in use, and enforces policy (for example, shut down service or application or keep service or application operating and notify user in parallel). In some embodiments, a network state changes after a service or application is launched, a subset of the service or application included in the active table are forced to quit and to re-launch on new network state.
In some embodiments, for bidding on UI location (placement, discovery level, etc.) of service or application associated to service launch object comprises a bid table. In some embodiments, the bid table includes one or more entries for: spots, graphics, text, animation per entry. In some embodiments, bid table entries have time service launch objects. In some embodiments, bid table entries have a minimum time window. In some embodiments, bid table entries change with time of day. In some embodiments, bid table entries have entries change with device usage state. In some embodiments, bid table entries have entries change with geo. In some embodiments, bid table entries include one or more of: bid on one or more spots, bid on one or more time service launch objects, bid on one or more time of day, bid on one or more geos. In some embodiments, the service launch object are swapped based on one or more of: changes is geo, network state, device usage state, etc.
In some embodiments, the bid is for a pre-configured geo. In some embodiments, the bid is on geographic location (city, state, etc.) or zip with radius. In some embodiments, the user of bidding platform pays for one or more of: per display, per unit time, or per click. In some embodiments, the base pay is for a unit time. In some embodiments, payment increased per view (for example, with a limit). In some embodiments, additional payment per click (for example, with a limit or cap). In some embodiments, pay increases for animation, etc.
In some embodiments, bulk buys (for example, discounts, rebates, coupons, etc.) are provider for large geographic areas (for example, nationwide). In some embodiments, bidder pays more for geographic specific bids. In some embodiments, bids have TOD policies. In some embodiments, bids have device usage (or network) state policies. In some embodiments, table entry in a given geographic and time of day goes to highest bidder. In some embodiments, the bid includes a minimum time window.
In some embodiments, bid winner algorithms as based on geographic level (for example, population or area size or level) selection relative to bid offer. In some embodiments, bidder screen provides selection of geographic areas to bid on and high bidder wins. In some embodiments, the highest nationwide bidder (for example, regardless of regional or local bidders). In some embodiments, regional highest bidder is considered if higher than a nationwide bidder by a target amount (for example, percentage or threshold, etc.). In some embodiments, location specific bidder is considered if higher than a regional (or nationwide) bidder by a desired target amount. In some embodiments, a device usage (or network or device or user) state specific bidder is considered if higher than larger geographic bidders by a target amount. In some embodiments, a previous bid winner is shuffle down if knocked down by higher bid (or higher by a give percentage or threshold) for higher position. In some embodiments, the bid winner algorithm is based on maximizing the revenue from bid pool or devices.
In some embodiments, bidding includes one or more spots including: spot for search, spot for featured sponsored, spot for ads, spots for coupons, spot for maps, etc. In some embodiments, the bidding includes bid types, for example, bid on specialized spots or bid on general purpose spots (for example, based on target user, or device, or geographic location, or network state parameters). In some embodiments, select targeted time or geography or state rules for special spots (vs. general purpose spots). In some embodiments, the bidding platform includes an area (or portion of device UI) for OEM customization. In some embodiments, the bidding platform includes an area (or portion of device UI) for user customization. In some embodiments, the area for OEM or user customization may be viewed on a service design center (SDC) screen.
In some embodiments, the portion of the device UI reserved for the launcher is configurable (for example, left, center right, small, medium, large, upper, middle, lower). In some embodiments, the portion of the device UI reserved for the launcher is SDC or OTA-configurable. In some embodiments, the device is configured to include a UI menu for configurable discovery management display or launcher. In some embodiments, the device includes a default launcher, for example, for (first) power up, and then user can subsequently change. In some embodiments, the default launcher comes back every power cycle or comes back after a set time or comes back after sleep. In some embodiments, the return to default launcher is SDC or OTA-configurable. In some embodiments, the launcher configuration is viewable in SDC screen.
In some embodiment place a special identifier near the launcher (for example, make a shim below launcher) so that launcher area is permanent. In some embodiments, the UI portion includes an enhanced launcher that recognizes permanent areas and gives user control of all other areas when they download the enhanced launcher.
In some embodiments, a user or network entity can drag icons from launcher to standard UI display (or screen). In some embodiments, the icons could be converted (or reverted) between real icons or special launcher icons. In some embodiments, the icons could be converted (or reverted) between real icons or special launcher icons when the icons are dragged between the launcher and the standard UI display.
In some embodiments, a network system performs a method comprising: obtaining information to assist in identifying a plurality of portions of a user interface of a wireless device, the wireless device communicatively coupled to the network system over a wireless access network; obtaining an object placement policy, the object placement policy comprising a first set of one or more rules for identifying a particular portion of the plurality of portions of the user interface of the wireless device in which to place one or more objects; determining a differentiating attribute for the particular portion of the user interface; obtaining the one or more objects; based on the object placement policy, determining configuration information, the configuration information at least configured to assist the wireless device in placing the one or more objects in the particular portion of the user interface; and sending the configuration information to the wireless device over the wireless access network. In some embodiments, obtaining the object placement policy comprises obtaining the first set of one or more rules from a service design center. In some embodiments, obtaining the object placement policy comprises obtaining the first set of one or more rules from memory. In some embodiments, obtaining the object placement policy comprises obtaining the first set of one or more rules from an entity associated with at least one of the one or more objects.
In some embodiments, at least one of the one or more objects is a service launch object. In some embodiments, at least one of the one or more objects is an advertisement.
In some embodiments, the first set of one or more rules is configured to establish an ordering within the plurality of portions. In some embodiments, the plurality of portions includes a first portion and a second portion, and the first set of one or more rules is configured to establish the first portion as a higher priority portion than the second portion.
In some embodiments, at least one of the one or more objects is associated with one or more of a particular application program, a particular service, a particular content item, and a particular advertisement. In some embodiments, at least one of the one or more service launch objects is an icon. In some embodiments, at least one of the one or more service launch objects is a banner advertisement. In some embodiments, at least one of the one or more service launch objects is a particular icon for launching a particular application program. In some embodiments, at least one of the one or more service launch objects is a particular icon for launching a particular service. In some embodiments, at least one of the one or more service launch objects is a particular icon for launching a particular content item. In some embodiments, at least one of the one or more service launch objects comprises an advertisement. In some embodiments, at least one of the one or more service launch objects is configured to launch a purchase offer.
In some embodiments, obtaining information to assist in identifying the plurality of portions of the user interface of the wireless device comprises obtaining the information from an entity. In some embodiments, the entity is an operator of the wireless access network. In some embodiments, obtaining information to assist in identifying the plurality of portions of the user interface of the wireless device comprises obtaining the information from memory. In some embodiments, obtaining information to assist in identifying the plurality of portions of the user interface of the wireless device comprises obtaining the information from the wireless device. In some embodiments, obtaining information to assist in identifying the plurality of portions of the user interface of the wireless device comprises obtaining the information from an entity associated with at least one of the one or more objects. In some embodiments, obtaining information to assist in identifying the plurality of portions of the user interface of the wireless device comprises obtaining the information from a pre-determined configuration.
In some embodiments, the configuration information comprises a software build. In some embodiments, the software build comprises an update to a user interface software build.
In some embodiments, at least one of the one or more objects is a particular icon configured to launch a particular software application, and the configuration information is further configured to assist the wireless device in associating the particular icon with the particular software application.
In some embodiments, the plurality of portions of the user interface includes a partition of a screen of the wireless device. In some embodiments, the plurality of portions of the user interface includes a particular screen of a multi-screen user interface display. In some embodiments, the plurality of portions of the user interface comprises a plurality of partitions of a multi-screen user interface display. In some embodiments, the plurality of portions of the user interface comprises a plurality of partitions. In some embodiments, the plurality of partitions is classified based on ease of discovery to a user of the wireless device. In some embodiments, classifying comprises one or more of prioritizing, ranking, ordering, sorting, and establishing tiers.
In some embodiments, at least one of the one or more objects is associated with an entity comprising one or more of a user interface location manager, an original equipment manufacturer, a carrier, an access carrier, a service provider, and an object provider.
In some embodiments, determining the differentiating attribute or characteristic of the portion of the user interface comprises determining a characteristic to assist a user in identifying the particular portion of the user interface. In some embodiments, the differentiating attribute comprises one or more of a border, a window, a color, a wallpaper, a background, a texture, a transparency, and a brightness.
In some embodiments, the network system obtains information about a network state and obtains the one or more objects for placement in the particular portion of the user interface by obtaining the one or more objects based on the information about the network state. In some embodiments, the network state is one or more of a network type, a network cost, a network service plan, a network latency, and a network quality-of-service level. In some embodiments, the network type is one or more of WiFi, cellular, home, and roaming.
In some embodiments, the network system obtains information about a device state and obtains the one or more objects for placement in the particular portion of the user interface by obtaining the one or more objects based on the information about the device state. In some embodiments, the device state comprises one or more of a current usage measure, a past usage measure, a current device location, a past device location, a current user interaction state, a past user interaction state, a current device cognitive state, and a past device cognitive state.
In some embodiments, the network system obtains information about a user and obtains the one or more objects for placement in the particular portion of the user interface comprises obtaining the one or more objects based on the information about the user. In some embodiments, the information about the user comprises one or more of a user profile, a user preference, a current behavior, or a past behavior.
In some embodiments, the configuration information assists the wireless device in preventing a user from modifying the particular portion of the user interface or a contents of the particular portion of the user interface.
In some embodiments, at least one of the one or more objects is associated with a particular service or a particular application, and wherein the configuration information is further configured to assist the wireless device in one or more of: enabling or launching the particular service or the particular application when a user selects the object, and providing additional management functions to the particular service or the particular application when the user selects the object. In some embodiments, the additional management functions include one or more of providing service usage information, allowing object modification, and providing object notification messages. In some embodiments, allowing object modification comprises allowing modifications to one or more of object placement, object positioning, and object classification.
In some embodiments, the network system classifies the one or more objects, and the configuration information is based on the classification of the one or more objects.
In some embodiments, the network system provides a view of the user interface of the wireless device to a network system manager.
In some embodiments, identifying the particular portion of the user interface of the wireless device comprises obtaining identifying information from a service design center. In some embodiments, determining the differentiating attribute of the identified portion of the user interface comprises obtaining attribute information from a service design center.
In some embodiments, the network system obtains the one or more objects for placement in the particular portion of the user interface by selecting the one or more objects based on a second set of one or more rules.
In some embodiments, at least one of the one or more objects is associated with a particular entity of a plurality of entities, and further comprising: obtaining bids from one or more of the plurality of entities, including the particular entity; and identifying the particular entity as a winning bidder.
This document incorporates by reference for all purposes the following non-provisional U.S. patent applications: 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, now U.S. Pat. No. 8,321,526 (issued Nov. 27, 2012); application Ser. No. 12/380,780, filed Mar. 2, 2009, entitled AUTOMATED DEVICE PROVISIONING AND ACTIVATION, now U.S. Pat. No. 8,839,388 (issued Sep. 16, 2014); application Ser. No. 12/695,019, filed Jan. 27, 2010, entitled DEVICE ASSISTED CDR CREATION, AGGREGATION, MEDIATION AND BILLING, now U.S. Pat. No. 8,275,830 (issued Sep. 25, 2012); application Ser. No. 12/695,020, filed Jan. 27, 2010, entitled ADAPTIVE AMBIENT SERVICES, now U.S. Pat. No. 8,406,748 (issued Mar. 26, 2013); application Ser. No. 12/694,445, filed Jan. 27, 2010, entitled SECURITY TECHNIQUES FOR DEVICE ASSISTED SERVICES, now U.S. Pat. No. 8,391,834 (issued Mar. 5, 2013); application Ser. No. 12/694,451, filed Jan. 27, 2010, entitled DEVICE GROUP PARTITIONS AND SETTLEMENT PLATFORM, now U.S. Pat. No. 8,548,428 (issued Oct. 1, 2013); application Ser. No. 12/694,455, filed Jan. 27, 2010, entitled DEVICE ASSISTED SERVICES INSTALL, now U.S. Pat. No. 8,402,111 (issued Mar. 19, 2013); application Ser. No. 12/695,021, filed Jan. 27, 2010, entitled QUALITY OF SERVICE FOR DEVICE ASSISTED SERVICES, now U.S. Pat. No. 8,346,225 (issued Jan. 1, 2013); application Ser. No. 12/695,980, filed Jan. 28, 2010, entitled ENHANCED ROAMING SERVICES AND CONVERGED CARRIER NETWORKS WITH DEVICE ASSISTED SERVICES AND A PROXY, now U.S. Pat. No. 8,340,634 (issued Dec. 25, 2012); application Ser. No. 13/134,005, filed May 25, 2011, entitled SYSTEM AND METHOD FOR WIRELESS NETWORK OFFLOADING, now U.S. Pat. No. 8,635,335 (issued Jan. 21, 2014); application Ser. No. 13/134,028, filed May 25, 2011, entitled DEVICE-ASSISTED SERVICES FOR PROTECTING NETWORK CAPACITY, now U.S. Pat. No. 8,589,541 (issued Nov. 19, 2013); application Ser. No. 13/229,580, filed Sep. 9, 2011, entitled WIRELESS NETWORK SERVICE INTERFACES, now U.S. Pat. No. 8,626,115 (issued Jan. 7, 2014); application Ser. No. 13/237,827, filed Sep. 20, 2011, entitled ADAPTING NETWORK POLICIES BASED ON DEVICE SERVICE PROCESSOR CONFIGURATION, now U.S. Pat. No. 8,832,777 (issued Sep. 9, 2014); application Ser. No. 13/239,321, filed Sep. 21, 2011, entitled SERVICE OFFER SET PUBLISHING TO DEVICE AGENT WITH ON-DEVICE SERVICE SELECTION, now U.S. Pat. No. 8,898,293; application Ser. No. 13/248,028, filed Sep. 28, 2011, entitled ENTERPRISE ACCESS CONTROL AND ACCOUNTING ALLOCATION FOR ACCESS NETWORKS, now U.S. Pat. No. 8,924,469; application Ser. No. 13/247,998, filed Sep. 28, 2011, entitled COMMUNICATIONS DEVICE WITH SECURE DATA PATH PROCESSING AGENTS, now U.S. Pat. No. 8,725,123 (issued May 13, 2014); application Ser. No. 13/248,025, filed Sep. 28, 2011, entitled SERVICE DESIGN CENTER FOR DEVICE ASSISTED SERVICES, now U.S. Pat. No. 8,924,543; application Ser. No. 13/253,013, filed Oct. 4, 2011, entitled SYSTEM AND METHOD FOR PROVIDING USER NOTIFICATIONS, now U.S. Pat. No. 8,745,191 (issued Jun. 3, 2014); application Ser. No. 13/309,556, filed Dec. 1, 2011, entitled END USER DEVICE THAT SECURES AN ASSOCIATION OF APPLICATION TO SERVICE POLICY WITH AN APPLICATION CERTIFICATE CHECK, now U.S. Pat. No. 8,893,009; application Ser. No. 13/309,463, filed Dec. 1, 2011, entitled SECURITY, FRAUD DETECTION, AND FRAUD MITIGATION IN DEVICE-ASSISTED SERVICES SYSTEMS, now U.S. Pat. No. 8,793,758 (issued Jul. 29, 2014); and application Ser. No. 13/441,821, filed Apr. 6, 2012, entitled MANAGING SERVICE USER DISCOVERY AND SERVICE LAUNCH OBJECT PLACEMENT ON A DEVICE.
This document incorporates by reference for all purposes the following provisional patent applications: Provisional Application No. 61/206,354, filed Jan. 28, 2009, entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD; Provisional Application No. 61/206,944, filed Feb. 4, 2009, entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD; Provisional Application No. 61/207,393, filed Feb. 10, 2009, entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD; and Provisional Application No. 61/207,739, entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD, filed Feb. 13, 2009; Provisional Application No. 61/270,353, filed on Jul. 6, 2009, entitled DEVICE ASSISTED CDR CREATION, AGGREGATION, MEDIATION AND BILLING; Provisional Application No. 61/275,208 filed Aug. 25, 2009, entitled ADAPTIVE AMBIENT SERVICES; and Provisional Application No. 61/237,753, filed Aug. 28, 2009, entitled ADAPTIVE AMBIENT SERVICES; Provisional Application No. 61/252,151, filed Oct. 15, 2009, entitled SECURITY TECHNIQUES FOR DEVICE ASSISTED SERVICES; Provisional Application No. 61/252,153, filed Oct. 15, 2009, entitled DEVICE GROUP PARTITIONS AND SETTLEMENT PLATFORM; Provisional Application No. 61/264,120, filed Nov. 24, 2009, entitled DEVICE ASSISTED SERVICES INSTALL; Provisional Application No. 61/264,126, filed Nov. 24, 2009, entitled DEVICE ASSISTED SERVICES ACTIVITY MAP; Provisional Application No. 61/348,022, filed May 25, 2010, entitled DEVICE ASSISTED SERVICES FOR PROTECTING NETWORK CAPACITY; Provisional Application No. 61/381,159, filed Sep. 9, 2010, entitled DEVICE ASSISTED SERVICES FOR PROTECTING NETWORK CAPACITY; Provisional Application No. 61/381,162, filed Sep. 9, 2010, entitled SERVICE CONTROLLER INTERFACES AND WORKFLOWS; Provisional Application No. 61/384,456, filed Sep. 20, 2010, entitled SECURING SERVICE PROCESSOR WITH SPONSORED SIMS; Provisional Application No. 61/389,547, filed Oct. 4, 2010, entitled USER NOTIFICATIONS FOR DEVICE ASSISTED SERVICES; Provisional Application No. 61/385,020, filed Sep. 21, 2010, entitled SERVICE USAGE RECONCILIATION SYSTEM OVERVIEW; Provisional Application No. 61/387,243, filed Sep. 28, 2010, entitled ENTERPRISE AND CONSUMER BILLING ALLOCATION FOR WIRELESS COMMUNICATION DEVICE SERVICE USAGE ACTIVITIES; Provisional Application No. 61/387,247, filed September 28, entitled SECURED DEVICE DATA RECORDS, 2010; Provisional Application No. 61/407,358, filed Oct. 27, 2010, entitled SERVICE CONTROLLER AND SERVICE PROCESSOR ARCHITECTURE; Provisional Application No. 61/418,507, filed Dec. 1, 2010, entitled APPLICATION SERVICE PROVIDER INTERFACE SYSTEM; Provisional Application No. 61/418,509 filed Dec. 1, 2010, entitled SERVICE USAGE REPORTING RECONCILIATION AND FRAUD DETECTION FOR DEVICE ASSISTED SERVICES; Provisional Application No. 61/420,727, filed Dec. 7, 2010, entitled SECURE DEVICE DATA RECORDS; Provisional Application No. 61/422,565, filed Dec. 13, 2010, entitled SERVICE DESIGN CENTER FOR DEVICE ASSISTED SERVICES; Provisional Application No. 61/422,572, filed Dec. 13, 2010, entitled SYSTEM INTERFACES AND WORKFLOWS FOR DEVICE ASSISTED SERVICES; Provisional Application No. 61/422,574, filed Dec. 13, 2010, entitled SECURITY AND FRAUD DETECTION FOR DEVICE ASSISTED SERVICES; Provisional Application No. 61/435,564, filed Jan. 24, 2011, entitled FRAMEWORK FOR DEVICE ASSISTED SERVICES; Provisional Application No. 61/472,606, filed Apr. 6, 2011, entitled MANAGING SERVICE USER DISCOVERY AND SERVICE LAUNCH OBJECT PLACEMENT ON A DEVICE; Provisional Application No. 61/550,906, filed Oct. 24, 2011, entitled SECURITY FOR DEVICE-ASSISTED SERVICES; Provisional Application No. 61/589,830, filed Jan. 23, 2012, entitled METHODS AND APPARATUS TO PRESENT INFORMATION ABOUT VOICE, MESSAGING, AND DATA SERVICES ON WIRELESS MOBILE DEVICES; Provisional Application No. 61/610,876, filed Mar. 14, 2012, entitled METHODS AND APPARATUS FOR APPLICATION PROMOTION AND SPONSORSHIP; and Provisional Application No. 61/610,910, filed Mar. 14, 2012, entitled WIFI ACTIVATION BACKUP PROCESS.
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 | Feuerstein 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 |
6370139 | Redmond | Apr 2002 | B2 |
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 |
6732176 | Stewart et al. | May 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 |
6842628 | Arnold 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 | Gumani 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 |
6970927 | Stewart et al. | Nov 2005 | B1 |
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 |
7200551 | Senez | Apr 2007 | B1 |
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 |
7433362 | Mallya et al. | Oct 2008 | B2 |
7436816 | Mehta et al. | Oct 2008 | B2 |
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 |
7467160 | McIntyre | 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 |
7505756 | Bahl | Mar 2009 | B2 |
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 |
7522549 | Karaoguz 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 |
7551921 | Petermann | 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 |
7596373 | Mcgregor et al. | Sep 2009 | B2 |
7599288 | Cole et al. | Oct 2009 | B2 |
7599714 | Kuzminskiy | Oct 2009 | B2 |
7602746 | Calhoun et al. | Oct 2009 | B2 |
7606918 | Holzman 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 |
7616962 | Oswal 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 |
7644414 | Smith 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 |
7822849 | Titus | Oct 2010 | B2 |
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 |
7849170 | Hargens et al. | Dec 2010 | B1 |
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 |
7979896 | McMurtry 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 |
3005009 | McKee et al. | Aug 2011 | A1 |
3005459 | Balsillie | Aug 2011 | A1 |
3005726 | Bao | Aug 2011 | A1 |
3005913 | Carlander | Aug 2011 | A1 |
3005988 | Maes | Aug 2011 | A1 |
7990049 | Shioya | Aug 2011 | B2 |
8000276 | Scherzer et al. | Aug 2011 | B2 |
8000318 | Wiley et al. | 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 |
8015249 | Nayak 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 |
8108680 | Murray | 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 |
8266249 | Hu | 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 |
8310943 | Mehta 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 et al. | 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 |
8417234 | Sanding | 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 |
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 |
8463194 | Erlenback 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 |
RE44412 | Naqvi et al. | Aug 2013 | E |
8500533 | Lutnick et al. | Aug 2013 | B2 |
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 et al. | Sep 2013 | B2 |
8526350 | Xue et al. | 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 |
8535160 | Lutnick et al. | Sep 2013 | B2 |
8538394 | Zimmerman et al. | Sep 2013 | B2 |
8538402 | Vidal 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 | Mclean 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 |
8561138 | Rothman et al. | 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 |
8571598 | Valavi | 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 |
8595186 | Mandyam et al. | Nov 2013 | B1 |
8600895 | Felsher | Dec 2013 | B2 |
8601125 | Huang et al. | Dec 2013 | B2 |
8605691 | Soomro et al. | Dec 2013 | B2 |
8615507 | Varadarajulu 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 |
8656472 | McMurtry et al. | Feb 2014 | B2 |
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 |
8701080 | Tripathi | Apr 2014 | B2 |
8705361 | Venkataraman et al. | Apr 2014 | B2 |
8706863 | Fadell | Apr 2014 | B2 |
8712631 | Tietjen et al. | 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 |
8798610 | Prakash et al. | Aug 2014 | B2 |
8799227 | Ferguson et al. | Aug 2014 | B2 |
8804517 | Oerton | Aug 2014 | B2 |
8804695 | Branam | 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 |
8845415 | Lutnick 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 |
8949382 | Cornett et al. | Feb 2015 | B2 |
8949597 | Reeves et al. | Feb 2015 | B1 |
8955038 | Nicodemus et al. | Feb 2015 | B2 |
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 |
8983860 | Beda, III et al. | Mar 2015 | B1 |
8995952 | Baker et al. | Mar 2015 | B1 |
9002322 | Cotterill | Apr 2015 | B2 |
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 |
9042923 | Mirho | May 2015 | B1 |
9049010 | Jueneman et al. | Jun 2015 | B2 |
9064275 | Lu et al. | Jun 2015 | B1 |
9105031 | Shen et al. | Aug 2015 | B2 |
9111088 | Ghai et al. | Aug 2015 | B2 |
9135037 | Petrescu-Prahova et al. | Sep 2015 | B1 |
9137286 | Yuan | Sep 2015 | B1 |
9137389 | Neal et al. | Sep 2015 | B2 |
9143933 | Ikeda et al. | Sep 2015 | B2 |
9154826 | Raleigh | Oct 2015 | B2 |
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 |
9191394 | Novak et al. | Nov 2015 | B2 |
9282460 | Souissi | Mar 2016 | B2 |
9286469 | Kraemer et al. | Mar 2016 | B2 |
9286604 | Aabye et al. | Mar 2016 | B2 |
9313708 | Nam et al. | Apr 2016 | B2 |
9325737 | Gutowski et al. | Apr 2016 | B2 |
9326173 | Luft | Apr 2016 | B2 |
9344557 | Gruchala et al. | May 2016 | B2 |
9361451 | Oberheide et al. | Jun 2016 | B2 |
9363285 | Kitamura | Jun 2016 | B2 |
9367680 | Mahaffey et al. | Jun 2016 | B2 |
9369959 | Ruutu et al. | Jun 2016 | B2 |
9402254 | Kneckt et al. | Jul 2016 | B2 |
9413546 | Meier et al. | Aug 2016 | B2 |
9418381 | Ahuja et al. | Aug 2016 | B2 |
9459767 | Cockcroft et al. | Oct 2016 | B2 |
9497563 | Hornung | Nov 2016 | B2 |
9501803 | Bilac et al. | Nov 2016 | B2 |
9589117 | Ali et al. | Mar 2017 | B2 |
9609459 | Raleigh | Mar 2017 | B2 |
9634850 | Taft et al. | Apr 2017 | B2 |
9755842 | Raleigh et al. | Sep 2017 | B2 |
10027819 | Lu | Jul 2018 | B2 |
10064033 | Raleigh | Aug 2018 | B2 |
20010048738 | Baniak et al. | Dec 2001 | A1 |
20010053694 | Igarashi et al. | Dec 2001 | A1 |
20020013844 | Garrett et al. | Jan 2002 | A1 |
20020022472 | Watler et al. | Feb 2002 | A1 |
20020022483 | Thompson 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 |
20030191646 | D'Avello 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 |
20040019564 | Goldthwaite 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 |
20040116140 | Babbar et al. | Jun 2004 | A1 |
20040127200 | Shaw et al. | Jul 2004 | A1 |
20040127208 | Nair et al. | Jul 2004 | A1 |
20040127256 | Goldthwaite et al. | Jul 2004 | A1 |
20040132427 | Lee et al. | Jul 2004 | A1 |
20040133668 | Nicholas, III | Jul 2004 | A1 |
20040137890 | Kalke | Jul 2004 | A1 |
20040165596 | Garcia et al. | Aug 2004 | A1 |
20040167958 | Stewart et al. | Aug 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 | Huotar 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 |
20060193280 | Lee 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 |
20070111740 | Wandel | 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 et al. | Jul 2007 | A1 |
20070168499 | Chu | Jul 2007 | A1 |
20070171856 | Bruce et al. | Jul 2007 | A1 |
20070174490 | Choi et al. | Jul 2007 | A1 |
20070191006 | Carpenter | Aug 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 |
20070254646 | Sokondar | Nov 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 | Mathews 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 |
20100069074 | Kodialam et al. | Mar 2010 | A1 |
20100071053 | Ansari et al. | Mar 2010 | A1 |
20100075666 | Garner | Mar 2010 | A1 |
20100077035 | Li et al. | Mar 2010 | A1 |
20100080202 | Hanson | Apr 2010 | A1 |
20100082431 | Ramer et al. | Apr 2010 | A1 |
20100088387 | Calamera | Apr 2010 | A1 |
20100103820 | Fuller et al. | Apr 2010 | A1 |
20100113020 | Subramanian et al. | May 2010 | A1 |
20100121744 | Belz et al. | May 2010 | A1 |
20100131584 | Johnson | May 2010 | A1 |
20100142478 | Forssell et al. | Jun 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 |
20100227632 | Bell et al. | Sep 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 et al. | 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 |
20110185202 | Black 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 |
20110244837 | Murata et al. | Oct 2011 | A1 |
20110249668 | Milligan 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 |
20130225151 | King et al. | Aug 2013 | A1 |
20130326356 | Zheng et al. | Dec 2013 | A9 |
20140073291 | Hildner et al. | Mar 2014 | A1 |
20140241342 | Constantinof | Aug 2014 | A1 |
20150181628 | Haverinen et al. | Jun 2015 | A1 |
20160026964 | Rogers | Jan 2016 | A1 |
20160057628 | Sewall | Feb 2016 | A1 |
Number | Date | Country |
---|---|---|
2688553 | Dec 2008 | CA |
1310401 | Aug 2001 | 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 |
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 |
1739518 | Jan 2007 | EP |
1772988 | Apr 2007 | EP |
1850575 | Oct 2007 | EP |
1887732 | Feb 2008 | EP |
1942698 | Jul 2008 | EP |
1978772 | Oct 2008 | EP |
2007065 | Dec 2008 | EP |
2026514 | Feb 2009 | EP |
2466831 | Jun 2012 | EP |
3148713 | Mar 2001 | JP |
2005339247 | Dec 2005 | JP |
2006041989 | Feb 2006 | JP |
2006155263 | Jun 2006 | JP |
2006197137 | Jul 2006 | JP |
2006344007 | Dec 2006 | JP |
2007318354 | Dec 2007 | JP |
2008301121 | Dec 2008 | JP |
2009111919 | May 2009 | JP |
2009212707 | Sep 2009 | JP |
2009218773 | Sep 2009 | JP |
2009232107 | Oct 2009 | JP |
20040053858 | Jun 2004 | KR |
1998058505 | Dec 1998 | WO |
1999027723 | Jun 1999 | WO |
1999065185 | Dec 1999 | WO |
0208863 | Jan 2002 | WO |
2002045315 | Jun 2002 | WO |
2002067616 | Aug 2002 | WO |
2002093877 | Nov 2002 | WO |
2003014891 | Feb 2003 | WO |
2003017063 | 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 |
2010128391 | Jan 2011 | WO |
2011002450 | Jan 2011 | WO |
2011149532 | Dec 2011 | WO |
2012047275 | Apr 2012 | WO |
Number | Date | Country | |
---|---|---|---|
20210105145 A1 | Apr 2021 | US |
Number | Date | Country | |
---|---|---|---|
61472606 | Apr 2011 | US | |
61550906 | Oct 2011 | US | |
61589830 | Jan 2012 | US | |
61610876 | Mar 2012 | US | |
61610910 | Mar 2012 | US | |
61206354 | Jan 2009 | US | |
61206944 | Feb 2009 | US | |
61207393 | Feb 2009 | US | |
61207739 | Feb 2009 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15681730 | Aug 2017 | US |
Child | 16927424 | US | |
Parent | 13441821 | Apr 2012 | US |
Child | 15681730 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12380780 | Mar 2009 | US |
Child | 13441821 | US | |
Parent | 12380778 | Mar 2009 | US |
Child | 12380780 | US |