Patent Grant
10282719
None.
Not applicable.
Not applicable.
In the past, communication service providers (wireline, wireless, broadband cable, satellite) and other companies competed through product differentiation and price points. Today, with products highly commoditized and price differences negligible, the remaining differentiator is how well a company can deliver a customer experience that is personalized, rewarding, and meets customer needs. Billing is a key operations support system (OSS)/business support system (BSS) entity to allow for creative pricing packages.
In an embodiment, a user equipment with a primary identifier and a secondary identifier is disclosed. The user equipment comprises a memory, a processor, and a witness application stored in the memory. When executed by the processor in a trusted security zone, wherein the trusted security zone provides hardware assisted trust, the witness application monitors communication service consumption associated with each of the primary identifier and the secondary identifier of the user equipment and stores a plurality of logs of communication service consumption differentiated by identifier in the trusted security zone. The witness application further transmits a message comprising the logs of the communication service consumption to a server in a network of a service provider associated with the user equipment using a trusted end-to-end communication channel, wherein the logs are translated by the server to a format compatible with a billing data store supported by a billing server, wherein the translated logs are transmitted to the billing data store, whereby a bill is created for each of the primary identifier and the secondary identifier by the billing server accessing the billing data store.
In an embodiment, a method of collecting communication service consumption information associated with a primary identifier and a secondary identifier of a user equipment is disclosed. The method comprises monitoring, by a witness application that executes in a trusted security zone of the UE, communication service consumption associated with each of the primary identifier and the secondary identifier of the UE, wherein the trusted security zone provides hardware assisted trust, and storing a plurality of logs of communication service consumption differentiated by identifier in the trusted security zone. The method further comprises transmitting a message comprising the logs of the communication service consumption over a trusted end-to-end communication channel to a server in a network of a service provider associated with the UE, wherein the logs are translated by the server to a format compatible with a billing data store supported by a billing server, wherein the translated logs are transmitted to the billing data store, whereby a bill is created for each of the primary identifier and the secondary identifier by the billing server accessing the billing data store.
In an embodiment, a method of collecting communication service consumption information associated with a plurality of identifiers of a user equipment is disclosed. The method comprises monitoring, by a witness application that executes in a trusted security zone of the user equipment, communication service consumption associated with the plurality of identifiers, wherein the trusted security zone provides hardware assisted trust and storing a plurality of logs of communication service consumption differentiated by identifier in a trusted security zone. The method further comprises transmitting the plurality of logs of communication service consumption to a data store via a trusted end-to-end communication channel, wherein the data store is supported by a server in a network of a service provider associated with the user equipment and receiving, by the data store, processed billing information transmitted by a billing server, wherein the billing information is processed by the billing server. The method further comprises separating, by the server, the processed billing information based on identifier and the plurality of logs of communication service consumption and creating, by the server, a bill for each of the plurality of identifiers based on the separate billing information.
In an embodiment, a method of providing wireless communication service to a user equipment (UE) is disclosed. The method comprises downloading, by a trusted application on the UE, a broker application that mediates access to a wireless network supported by a wireless communication service provider, wherein the trusted application executes in a trusted security zone of the UE, wherein the trusted security zone provides hardware assisted trust, and installing, by the broker application, a network access key into the trusted security zone of the UE for the wireless network, wherein the broker application executes in the trusted security zone. The method further comprises responsive to receiving a rejection of an attach request to roam by the UE in the wireless network, presenting, by the broker application, credentials to the wireless network, wherein the credentials comprise the network access key, validating, by a wireless communication service provider server, the network access key presented by the UE, and responsive to the network access key being validated based on the examining results, granting, by the wireless communication service provider server, network access of the wireless network to the UE.
These and other features will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings and claims.
For a more complete understanding of the present disclosure, reference is now made to the following brief description, taken in connection with the accompanying drawings and detailed description, wherein like reference numerals represent like parts.
It should be understood at the outset that although illustrative implementations of one or more embodiments are illustrated below, the disclosed systems and methods may be implemented using any number of techniques, whether currently known or not yet in existence. The disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, but may be modified within the scope of the appended claims along with their full scope of equivalents.
When a communication service provider introduces new services, one issue may rise that may prevent or delay the service deployment—it is costly to modify the existing third party billing platform such as AMDOCS to add billing support for the new user devices or services. Additionally, currently there is no way to programmatically trust a user equipment to report its own usage back to the network billing platform or the third party billing platform. The user could compromise billing records on the user equipment, for instance by “rooting” the operating system and subverting the anti-fraud software. Thus, a method of securely recording and storing billing information on the user equipment and reporting the recorded billing information to a billing server through a trusted communication channel may be desirable. The present disclosure teaches a system and method for a secure and trusted device-based billing and charging system and process using new trusted security zone privilege for network proxy authentication and audit.
For example, a witness application may be stored in a trusted security zone in a memory of a user equipment. The trusted security zone may provide hardware assisted trust. The witness application executed in the trusted security zone may monitor communication service consumption associated with a plurality of identifiers of the user equipment. The identifier may be one or more of a phone number, a mobile equipment identifier (MEID), a uniform resource identifier (URI), or a uniform resource locator (URL), or another type of identifier. The plurality of identifiers may comprise at least a primary identifier and a secondary identifier. Alternatively, the identifiers may be separated into one primary identifier and secondary identifiers—identifiers except the primary identifier may be referred to as secondary identifiers. The secondary identifier may be configured to the user equipment in the trusted security zone.
Different identifiers may be associated with different types of communication services or network traffic. For example, one identifier may be associated with personal usage and another with business usage; one identifier may be associated with secure data usage and another with non-secure data usage, etc. The witness application may store a plurality of logs of communication service consumption differentiated by identifier in the trusted security zone.
The billing server, part of the internal system of a communication service provider associated with the user equipment, may monitor and record network activities or communication service consumption related to billing or charging. The network activities or communication service consumption related to billing or charging may be called billing information. In an embodiment, the billing information may be a usage record, a call detail record (CDR), or a data detail record (DDR) in which the information for these is accumulated by an application of the billing server. The billing server may process the billing information to generate processed billing information and transmit the processed billing information to a data store. The data store may be supported by a central server in a network of the communication service provider.
The witness application may transmit the logs of communication service consumption to the data store or the central server via a trusted end-to-end communication channel. As described in more detail below, trusted computation and/or trusted communication is based on hardware assisted security that reduces the ability of nefarious software or corrupt devices to write, read, or otherwise access trusted memory, trusted processing, or trusted messages. For further details about establishing trusted end-to-end communication links, see U.S. patent application Ser. No. 13/532,588, filed Jun. 25, 2012, entitled “End-to-end Trusted Communications Infrastructure,” by Leo Michael McRoberts, et al., which is hereby incorporated by reference in its entirety. Since the logs of communication service consumption have been stored in the trusted security zone of the user equipment and are now transmitted to the data store or the central server via the trusted end-to-end communication channel, the logs of communication service consumption stay intact without being tampered with by unauthorized entities until they reach the data store or the central server.
So far, the processed billing information from the billing server has not been separated based on different identifiers. When the data store receives processed billing information transmitted by the billing server, the central server associated with the communication service provider may separate the processed billing information based on identifier and the logs of communication service consumption received from the witness application. Note that network traffic monitored at the user equipment may be different from the network traffic monitored on network. For example, the start time, the end time, and the duration of the communication session monitored at the user equipment may be different from the start time, the end time, and the duration of the same communication session monitored on network. Thus, communication service consumption records from the user equipment may be different from the billing information from the billing server. The processed billing information with a specific start timestamp, end timestamp, and/or duration may be determined to be for the same communication session as a communication service consumption record with an approximately matching start timestamp, end timestamp, and/or duration from the user equipment. The central server associated with the communication service provider may create a different bill for each of the different identifiers of the same user equipment based on the separate billing information. This is not performed at the third billing platform such as the AMDOCS platform but instead performed by the central server post processing, i.e., after the billing information has been processed by the billing server.
Alternatively, the witness application may still transmit logs of the communication service consumption to the billing server, for example in a message comprising the logs of the communication service consumption over a trusted end-to-end communication channel to the billing server or a billing data store that is supported by the billing server while the logs may be marked or labeled by the witness application in a way that the logs may be ignored by the billing server. In other words, the billing server may not process the logs but may forward the logs to the next entity along the path of the billing process. For instance, the logs may be labeled by the witness application with “rate 0”. The logs may then be forwarded by the billing server to the central server associated with the communication service provider or the data store supported by the central server. The logs may be translated by the central server to a format compatible with the billing data store supported by the billing server. The translated logs may now be transmitted to the billing data store. A different bill may be created for each of the different identifiers such as the primary identifier and the secondary identifier by the billing server accessing the billing data store.
The message comprising the logs of the communication service consumption may be transmitted to the central server using the trusted end-to-end communication channel periodically or asynchronously. When the message is transmitted to the central server periodically, the message may be transmitted every day, every week, every month, every two months, or at some other interval. Alternatively, the message is transmitted to the central server every time that communication services are used.
Non-network related activity may also be monitored by the witness application, for example for billing purposes. The logs of the non-network related activity may be transmitted in the message comprising the logs of the communication service consumption to the central server using the trusted end-to-end communication channel.
Under some circumstances, a user equipment may be determined to be unprovisioned for wireless communication service. For example, when the user equipment can only provide an enhanced Node B (eNB), a base transceiver station (BTS), or a cell tower with its equipment identity but not a network access key, the user equipment may be determined to be unprovisioned. When a user equipment can provide the eNB with an equipment identifier and an expired subscriber account that had been assigned by a wireless communication service provider, the user equipment may be determined to be unprovisioned. Additionally, when a user equipment can provide an equipment identifier and a subscriber account assigned by a home service provider other than the wireless communication service provider that maintains the eNB but is denied roaming with the wireless communication service provider by its own home service provider, the mobile communication device may be determined to be unprovisioned. A home service provider of a user equipment is a communication service provider the user equipment is associated with and/or is subscribed to.
The witness application or another trusted application on the user equipment may download a broker application that mediates access to a wireless network supported by a wireless communication service provider. The user equipment may be unprovisioned, for example to utilize the wireless network. The wireless communication service provider may not be the home service provider of the user equipment and the wireless network may be different from a home network associated with the home service provider of the user equipment. In other words, the wireless network may be a foreign network. A foreign network is any network that is different from the network which is operated by the home service provider to which the user equipment is subscribed. When the user equipment is out of coverage of home network but is in the coverage of a different network—a foreign network—it may receive roaming wireless coverage from the different network.
For example, a user may choose not to roam with the wireless network through the user equipment's home service provider but instead to roam with the wireless network directly—the latter may be more cost effective. In the first case, the wireless communication service provider may bill the home service provider for the roaming service first, and the home service provider may then bill the user for the roaming service with a markup in price. In the second case, the wireless communication service provider may bill the user directly with a unit price for roaming between the unit prices the wireless communication service provider would bill the home service provider and the home service provider would bill the user. Thus, the user saves money when roaming with the wireless communication service provider directly.
The user of the user equipment may choose to download the broker application for this potential use of the wireless network. The broker application may be stored in the trusted security zone on the user equipment. When executed by the processor of the user equipment in a trusted execution environment, the broker application may perform a variety of functions related to network access request and/or grant for the wireless network. For example, the broker application may install a network access key into the trusted security zone of the UE for accessing the wireless network.
When the user equipment is in the vicinity of the wireless network, the user equipment may transmit a message such as an “attach” message through a control channel to make contact with a foreign base transceiver station or a foreign eNB that is part of the wireless network. The user equipment may then attempt to register with the wireless network so that the user equipment can roam with the wireless network through the home service provider. When the wireless network checks with the home network on whether the user equipment may roam with the wireless network, the home network may indicate that the user equipment is configured not to roam with the wireless network through the home service provider—as chosen by the user of the user equipment. Thus, the user equipment may be denied roaming with the wireless network through the home service provider. However, the foreign eNB may inquire whether a broker application has been installed on the user equipment. The user equipment may reply to the foreign eNB indicating that a broker application has been installed on the user equipment and its credentials to roam directly with the wireless network.
The broker application, for example, may mediate access to the wireless network directly with the wireless communication service provider by presenting credentials to the wireless network for access to the wireless network. The credentials may comprise the network access key that is installed and stored in the trusted security zone of the user equipment. A wireless communication service provider server from the wireless communication service provider may validate the credentials including network access key presented by the user equipment. When the network access key is validated, the wireless communication service provider server may grant network access of the wireless network to the user equipment.
Payment information may be provided by the user equipment to the wireless communication service provider via the broker application when the broker application is downloaded and/or installed on the user equipment. After the user equipment is granted access to the wireless network, communication service consumption associated with the wireless network may be monitored and stored. Furthermore, the monitored communication service consumption may be reported to the wireless communication service provider server via a trusted end-to-end communication channel.
Alternatively, instead of installing the broker application in advance, a message may pop up on the screen of the user equipment to indicate an alternative method to access the network such as to access the wireless network associated with the wireless communication service provider when the user equipment receives a denial of roaming with the wireless network through the home service provider. The denial message may be sent by a foreign eNB or a foreign server that is associated with the wireless network. The user equipment receives the denial because the user of the user equipment has chosen not to roam with the wireless network through the home service provider. The denial message may comprise a web address or link for the user equipment to download a broker application that mediates access to the wireless network. When the user chooses to download the broker application, the broker application may be downloaded by the witness application or another trusted application into the trusted security zone on the user equipment. During installation, the user may be asked for a payment method by the broker application to be associated with the wireless network service consumption.
Thus, user equipments that are unprovisioned with the wireless communication service provider or any wireless communication service provider may download the broker application to utilize the wireless network maintained by the wireless communication service provider. User equipments that were unprovisioned with the wireless communication service provider but were provisioned with some home service provider may switch to the wireless communication service provider permanently after using the wireless network temporarily through the broker application, thus creating new business opportunities for the wireless communication service provider.
An identifier database may store user equipment identifiers such as international mobile equipment identities (IMEIs). The identifier database may be a national identifier database that stores equipment identifiers of user equipments across wireless communication technologies, original equipment manufacturers, and/or wireless communication service providers. For example, user equipment identifiers of long-term evolution (LTE) devices may be stored in the identifier database when the user equipments are manufactured. Thus, when an unprovisioned user equipment requests access to the wireless network, the wireless communication service provider may recognize the user equipment by at least its equipment identifier.
A trusted security zone provides chipsets with a hardware root of trust, a secure execution environment for applications, and secure access to peripherals. A hardware root of trust means the chipset should only execute programs intended by the device manufacturer or vendor and resists software and physical attacks, and therefore remains trusted to provide the intended level of security. The chipset architecture is designed to promote a programmable environment that allows the confidentiality and integrity of assets to be protected from specific attacks. Trusted security zone capabilities are becoming features in both wireless and fixed hardware architecture designs. Providing the trusted security zone in the main mobile device chipset and protecting the hardware root of trust removes the need for separate secure hardware to authenticate the device or user. To ensure the integrity of the applications requiring trusted data, such as a mobile financial services application, the trusted security zone also provides the secure execution environment where only trusted applications can operate, safe from attacks. Security is further promoted by restricting access of non-trusted applications to peripherals, such as data inputs and data outputs, while a trusted application is running in the secure execution environment. In an embodiment, the trusted security zone may be conceptualized as hardware assisted security.
A complete trusted execution environment (TEE) may be implemented through the use of the trusted security zone hardware and software architecture. The trusted execution environment is an execution environment that is parallel to the execution environment of the main mobile device operating system. The trusted execution environment and/or the trusted security zone may provide a base layer of functionality and/or utilities for use of applications that may execute in the trusted security zone. For example, in an embodiment, trust tokens may be generated by the base layer of functionality and/or utilities of the trusted execution environment and/or trusted security zone for use in trusted end-to-end communication links to document a continuity of trust of the communications. Through standardization of application programming interfaces (APIs), the trusted execution environment becomes a place to which scalable deployment of secure services can be targeted. A device which has a chipset that has a trusted execution environment on it may exist in a trusted services environment, where devices in the trusted services environment are trusted and protected against attacks. The Trusted execution environment can be implemented on mobile phones and tablets as well as extending to other trusted devices such as personal computers, servers, sensors, medical devices, point-of-sale terminals, industrial automation, handheld terminals, automotive, etc.
The trusted security zone is implemented by partitioning all of the hardware and software resources of the mobile device into two partitions: a secure partition and a normal partition. The secure partition may be implemented by a first physical processor, and the normal partition may be implemented by a second physical processor. Alternatively, the secure partition may be implemented by a first virtual processor, and the normal partition may be implemented by a second virtual processor. Placing sensitive resources in the secure partition can protect against possible attacks on those resources. For example, resources such as trusted software applications may run in the secure partition and have access to hardware peripherals such as a touchscreen or a secure location in memory. Less secure peripherals such as wireless radios may be disabled completely while the secure partition is being accessed, while other peripherals may only be accessed from the secure partition. While the secure partition is being accessed through the trusted execution environment, the main mobile operating system in the normal partition is suspended, and applications in the normal partition are prevented from accessing the secure peripherals and data. This prevents corrupted applications or malware applications from breaking the trust of the device.
The trusted security zone is implemented by partitioning the hardware and software resources to exist in a secure subsystem which is not accessible to components outside the secure subsystem. The trusted security zone is built into the processor architecture at the time of manufacture through hardware logic present in the trusted security zone which enables a perimeter boundary between the secure partition and the normal partition. The trusted security zone may only be manipulated by those with the proper credential and, in an embodiment, may not be added to the chip after it is manufactured. Software architecture to support the secure partition may be provided through a dedicated secure kernel running trusted applications. Trusted applications are independent secure applications which can be accessed by normal applications through an application programming interface in the trusted execution environment on a chipset that utilizes the trusted security zone.
In an embodiment, the normal partition applications run on a first virtual processor, and the secure partition applications run on a second virtual processor. Both virtual processors may run on a single physical processor, executing in a time-sliced fashion, removing the need for a dedicated physical security processor. Time-sliced execution comprises switching contexts between the two virtual processors to share processor resources based on tightly controlled mechanisms such as secure software instructions or hardware exceptions. The context of the currently running virtual processor is saved, the context of the virtual processor being switched to is restored, and processing is restarted in the restored virtual processor. Time-sliced execution protects the trusted security zone by stopping the execution of the normal partition while the secure partition is executing.
The two virtual processors context switch via a processor mode called monitor mode when changing the currently running virtual processor. The mechanisms by which the processor can enter monitor mode from the normal partition are tightly controlled. The entry to monitor mode can be triggered by software executing a dedicated instruction, the Secure Monitor Call (SMC) instruction, or by a subset of the hardware exception mechanisms such as hardware interrupts, which can be configured to cause the processor to switch into monitor mode. The software that executes within monitor mode then saves the context of the running virtual processor and switches to the secure virtual processor.
The trusted security zone runs a separate operating system that is not accessible to the device users. For security purposes, the trusted security zone is not open to users for installing applications, which means users do not have access to install applications in the trusted security zone. This prevents corrupted applications or malware applications from executing powerful instructions reserved to the trusted security zone and thus preserves the trust of the device. The security of the system is achieved at least in part by partitioning the hardware and software resources of the mobile phone so they exist in one of two partitions, the secure partition for the security subsystem and the normal partition for everything else. Placing the trusted security zone in the secure partition and restricting access from the normal partition protects against software and basic hardware attacks. Hardware logic ensures that no secure partition resources can be accessed by the normal partition components or applications. A dedicated secure partition operating system runs in a virtual processor separate from the normal partition operating system that likewise executes in its own virtual processor. Users may install applications on the mobile device which may execute in the normal partition operating system described above. The trusted security zone runs a separate operating system for the secure partition that is installed by the mobile device manufacturer or vendor, and users are not able to install new applications in or alter the contents of the trusted security zone.
Turning now to
The UE 102 may be configured to use a radio transceiver to establish a wireless communication link with an enhanced Node B (eNB) 124, and the eNB 124 may communicatively couple the UE 102 to a network 122. The eNB 124 may alternatively be referred to in some contexts as a base transceiver station (BTS) or a cell tower. The central server 116, the central billing data store 114, the billing server 120, and the billing data store 118 may also be communicatively coupled to the network 122. The network 122 may comprise any combination of private and public networks.
It is understood that the system 100 may comprise any number of UEs 102, any number of billing data stores 118, any number of billing servers 120, and any number of eNBs 124. The collectivity of eNBs 124 may be said to comprise a radio access network (RAN), in that these eNBs 124 may provide a radio communication link to the UEs 102 to provide access to the network 122. The radio transceiver of the UE 102 may communicate with the eNB 124 using any of a variety of wireless communication protocols including a code division multiple access (CDMA) wireless communication protocol, a global system for mobile communication (GSM) wireless communication protocol, a long-term evolution (LTE) wireless communication protocol, a world-wide interoperability for microwave access (WiMAX) wireless communication protocol, or another wireless communication protocol.
While a smart phone is used in the role of UE 102 in a preferred embodiment, the teachings of the present disclosure may also be extended to other network/communications capable devices such as a laptop computer, a notebook computer, a tablet computer, a smart phone, a personal digital assistant (PDA), a media player, a headset computer, a wearable computer, a game console, an Internet digital media streaming device, a television, a set top box, a portable storage device, a hotspot, a 2.5 Wi-Fi translator, an Internet of Things (IoT) device, or another network/communications capable device. In an embodiment, the UE 102 may have other components (not shown) such as a near field communication (NFC) radio transceiver, a short range radio transceiver such as a wireless local area network radio transceiver, or other components and/or devices.
The central server 116 and the central billing data store 114 may be server computers. The central server 116 and the central billing data store 114 may be located in one computer—for example a server computer, in two different computers—for example, a server computer for the central server 116 and another computer for the central billing data store 114, in multiple different computers—for example, multiple server computers for the central server 116 and other multiple computers for the central billing data store 114, or in some other combination of computers. When the central server 116 and the central billing data store 114 are not located in one computer, the central server 116 and the central billing data store 114 may share the same wired or wireless local area network. It is similar with the billing server 120 and the billing data store 118.
The witness application 106 may be stored in a trusted partition of the memory 112, for example in the trusted security zone 104 in the memory 112. When executed by the processor 110 in the trusted security zone 104, the witness application 106 may perform a variety of functionality to monitor and log communication service consumption and/or report the communication service consumption to the central server 116. In an embodiment, the UE 102 may comprise a plurality of identifiers. An identifier of the UE 102 or a wireless communication identifier may be a personal wireless communication identifier, a business wireless communication identifier, a production wireless communication identifier, a testing wireless communication identifier, wireless communication identifiers for different wireless communication providers, wireless communication identifiers for different reward membership, a wireless communication identifier for a mobile wallet, or another wireless communication identifier. For example, a personal identifier may be associated with personal wireless communication on the UE 102 and a business identifier may be associated with business wireless communication on the UE 102. The wireless communication identifier may be referred to as an identifier hereinafter. The identifier may be one of a phone number, a uniform resource identifier (URI), a uniform resource locator (URL), or another type of identifier.
The witness application 106 may monitor communication service consumption of each of the identifiers of the UE 102, store logs of communication service consumption associated with the identifiers, and/or transmit messages comprising the logs of communication service consumption to the central server 116 via a trusted end-to-end communication channel.
A trustlet may be configured and/or installed in the UE 102 to send the message to provide a higher level of security. The trustlet may be associated with a communication application. For example, the trustlet may be part of a communication application on the UE 102. An application may be partitioned into a portion comprised of instructions that need not execute in the trusted security zone 104 and a portion comprised of instructions that desirably do execute in the trusted security zone 104. The portion of instructions of an application that are desirably executed in the trusted security zone 104 may be referred to as a trustlet. A trustlet may be thought of as an extract of a complete application—an extract of the specific instructions that desirably execute in a trusted security zone 104. The portion of the application that need not execute in the trusted security zone 104 may be said to execute in the rich environment or permissive environment.
For example, the witness app 106 may monitor communication service consumption associated with each of the identifiers of the UE 102. Communication service consumption may comprise voice calls, data calls, and/or some other type of communication service consumption or network traffic. In an embodiment, one identifier may be associated with personal usage of the UE 102 or communication services and another identifier may be associated with business usage of the UE 102 or communication services. Alternatively or additionally, one identifier may be associated with secure data usage and another identifier may be associated with non-secure data usage, etc. Thus, different identifiers may be associated with different communication service accounts and may be charged differently based on logs. Among the identifiers of the UE 102, one may be a primary identifier and a second one may be a secondary identifier, etc. The secondary identifier(s) may be configured into the UE 102 via the trusted security zone and the trusted end-to-end communication channel. A service order code (SOC) may be assigned to the secondary identifier by the billing server 120.
The witness app 106 may store logs of communication service consumption associated with the identifiers of the UE 102. For example, the witness app 106 may create a log for each of the identifiers of the UE 102 and store those logs in the trusted security zone 104. The log of communication service consumption may comprise details of communication service consumption, for instance the type of communication service, volume, duration, start time, end time, frequency, and/or some other characteristic of communication service consumption associated with an identifier. Because these logs are stored in the trusted security zone 104, they cannot be tampered with. The witness app 106 may update the logs with monitored communication service consumption information.
The witness app 106 may transmit a message comprising these logs of communication service consumption to the central server 116 via a trusted end-to-end communication channel. In an embodiment, the trusted end-to-end communication infrastructure assures that the message sent from the witness app 106 to the central server 116 is processed by the trusted security zone of each communication node during each step on its way through a foreign network until it enters the network 122 which is operated by a home service provider to which the UE 102 is subscribed. A foreign network is any network that is different from the network 122 which is operated by the home service provider to which the UE 102 is subscribed. When the UE 102 is out of coverage of home network but is in the coverage of a different network—a foreign network—it may receive roaming wireless coverage from the different network. An application may be executed in a trusted security zone of the central server 116 to perform functions associated with receiving the logs of communication service consumption and processing the logs.
In a first embodiment, the witness app 106 may transmit a message comprising the logs of communication service consumption to the central server 116 via a trusted end-to-end communication channel periodically or asynchronously. For instance, the witness app 106 may transmit the message every time communication services are used, every day, every week, every month, every two months, or at some other interval.
The billing server 120, as part of the internal system of a communication service provider associated with the user equipment 102, may also monitor and record network activities or communication service consumption related to billing or charging, like in the current billing systems. The network activities or communication service consumption related to billing or charging may be called billing information. The billing information may be a usage record, a call detail record (CDR), a data detail record (DDR), or some other type of billing records in which the information for these is accumulated by an application on the user equipment 102. The billing server 120 may process the billing information to generate processed billing information and transmit the processed billing information to the central billing data store 114. The billing server 120 may transmit the processed billing information to the central billing data store 114 or the central server 116.
Alternatively, a negative call detail record that deducts from the existing call detail record to exclude billing information associated with secondary identifier(s) may be generated by the witness app 106 and the billing information associated with the secondary identifier(s) may be deducted before the existing CDR reaches the billing server 120. The billing server 120 may process the result of the subtraction to generate processed billing information. Meanwhile, the negative call detail record may also be transmitted by the witness app 106 to the central billing data store 114 or the central server 116.
When the central billing data store 114 receives processed billing information and/or the negative call detail record transmitted by the billing server 120, the central server 116 may separate the processed billing information and/or the negative call detail record based on the logs of communication service consumption received from the UE 102. Note that network traffic monitored at the UE 102 may be different from the network traffic monitored on network, and thus communication service consumption records from the UE 102 may be different from the billing information from the billing server 120. The processed billing information with a specific start timestamp, end timestamp, and/or duration may be determined to be for the same communication session as a communication service consumption record with an approximately matching start timestamp, end timestamp, and/or duration from the UE 102. The logs of communication service consumption may comprise communication service consumption details associated with individual identifiers of the UE 102 and billing information may be separated into portions corresponding to the individual identifiers. The central server 116 may generate a bill for each of the identifiers based on the separate billing information.
In a second embodiment, the witness app 106 may transmit the logs of communication service consumption over a trusted end-to-end communication channel to the billing server 120 or the billing data store 118, for example in a message. The logs may be marked or labeled by the witness app 106 in a way that the logs may be ignored by the billing server 120. In other words, the billing server 120 may not process the logs but may forward the logs to the next entity along the path of the billing process. For instance, the logs may be labeled by the witness app 106 with “rate 0” so that the billing server 120 may forward the logs to the next entity along the path of the billing process without processing the logs. The logs may then be forwarded by the billing server 120 to the central server 116 or the central billing data store 114.
The logs of communication service consumption from the UE 102 or the witness app 106 may be in a first format different from a second format that could be understood by the billing server 120. When the logs reach the central server 116 or the central billing data store 114, the logs may be translated, converted, or transcoded by the central server 116 or an application on the central server 116 into the second format that is compatible with the billing data store 118 and/or the billing server 120. The translated logs may now be transmitted by the central server 116 to the billing data store 118.
A specific service order code (SOC) may be assigned to the secondary identifier by the billing server 120 to manage or handle the translated logs of communication service consumption from the UE 102. In an embodiment, when there is more than one secondary identifier associated with the UE 102, one service order code may be assigned by the billing server 120 to each secondary identifier. This specific service order code may be different from an existing service order code that manages billing information associated with the primary identifier. The billing server 120 and the central server 116 may communicate via a mediator application programming interface (API), for example a Parlay interface. The service order code handling the billing process at the billing server 120 may be configured to ignore 0 rated data on the network side but accept the 0 rated data on the Parlay side. Accordingly, when the logs of communication service consumption with rate 0 from the UE 102 reach the billing server 120, the logs arrive on the network side, and thus the logs may be ignored—forwarded to the next entity without being processed. On the other hand, when the translated logs with rate 0 from the central server 116 reach the billing server 120, the translated logs arrive on the Parlay side, and thus the billing server 120 may process the translated logs. A bill may then be generated for each of the identifiers of the UE 102 by the billing server 120 accessing the billing data store 118.
Note that non-network related activity may also be monitored by the witness application 106 for example for billing purposes. The non-network related activity information may be transmitted in the message comprising the communication service consumption to the central server 116 using the trusted end-to-end communication channel.
Turning now to
At block 204, a plurality of logs of communication service consumption differentiated by identifier are stored in the trusted security zone. For example, the logs of communication service consumption may be stored in the trusted security zone 104. The logs may be differentiated by identifier. At block 206, a message comprising the logs of the communication service consumption is transmitted over a trusted end-to-end communication channel to a server 116 in a network of a service provider associated with the UE 102, wherein the logs are translated by the central server 116 to a format compatible with a billing data store 118 supported by a billing server 120, wherein the translated logs are transmitted to the billing data store 118, whereby a bill is created for each of the primary identifier and the secondary identifier by the billing server 120 accessing the billing data store 118.
Turning now to
At block 306, responsive to receiving a rejection of an attach request to roam by the UE in the wireless network, credentials are presented by the broker application to the wireless network, wherein the credentials comprise the network access key. For example, when the UE 102 is in the vicinity of the wireless network, the UE 102 may receive a rejection to an attach request to roam with the wireless network, for example a rejection to an attach request to roam with the wireless network through the home service provider. This may be because that the UE 102 has been configured not to roam with the wireless network through its home service provider. The UE 102 has not been configured not to roam with the wireless network directly though. When the UE 102 roams directly with the wireless network, the UE 102 may be billed by the wireless network directly. The broker application may provide credentials comprising the installed network access key that is associated with the wireless network to a wireless communication service server. The wireless communication service server may be supported by the wireless communication service provider.
At block 308, the network access key presented by the UE 102 is examined by the wireless communication service provider server. At block 310, responsive to the network access key being validated based on the examining results, network access of the wireless network is granted by the wireless communication service provider server to the UE 102. After the UE 102 is granted access to the wireless network, communication service consumption associated with the wireless network may be monitored by the witness application 106 and stored in the trusted security zone 104. Furthermore, the monitored communication service consumption may be reported to the wireless communication service provider server via a trusted end-to-end communication channel. A payment method may have been stored in the trusted security zone 104 when the broker application was installed on the UE 102. The payment method may be used for wireless network service consumption associated with the wireless communication service provider.
The DSP 502 or some other form of controller or central processing unit operates to control the various components of the UE 400 in accordance with embedded software or firmware stored in memory 504 or stored in memory contained within the DSP 502 itself. In addition to the embedded software or firmware, the DSP 502 may execute other applications stored in the memory 504 or made available via information carrier media such as portable data storage media like the removable memory card 520 or via wired or wireless network communications. The application software may comprise a compiled set of machine-readable instructions that configure the DSP 502 to provide the desired functionality, or the application software may be high-level software instructions to be processed by an interpreter or compiler to indirectly configure the DSP 502.
The DSP 502 may communicate with a wireless network via the analog baseband processing unit 510. In some embodiments, the communication may provide Internet connectivity, enabling a user to gain access to content on the Internet and to send and receive e-mail or text messages. The input/output interface 518 interconnects the DSP 502 and various memories and interfaces. The memory 504 and the removable memory card 520 may provide software and data to configure the operation of the DSP 502. Among the interfaces may be the USB port 522 and the infrared port 524. The USB port 522 may enable the UE 400 to function as a peripheral device to exchange information with a personal computer or other computer system. The infrared port 524 and other optional ports such as a Bluetooth® interface or an IEEE 802.11 compliant wireless interface may enable the UE 400 to communicate wirelessly with other nearby handsets and/or wireless base stations. In an embodiment, the UE 400 may comprise a near field communication (NFC) transceiver. The NFC transceiver may be used to complete payment transactions with point-of-sale terminals or other communications exchanges. In an embodiment, the UE 400 may comprise a radio frequency identify (RFID) reader and/or writer device.
The switches 528 may couple to the DSP 502 via the input/output interface 518 to provide one mechanism for the user to provide input to the UE 400. Alternatively, one or more of the switches 528 may be coupled to a motherboard of the UE 400 and/or to components of the UE 400 via a different path (e.g., not via the input/output interface 518), for example coupled to a power control circuit (power button) of the UE 400. The touch screen display 530 is another input mechanism, which further displays text and/or graphics to the user. The touch screen LCD controller 532 couples the DSP 502 to the touch screen display 530. The GPS receiver 538 is coupled to the DSP 502 to decode global positioning system signals, thereby enabling the UE 400 to determine its position.
It is understood that by programming and/or loading executable instructions onto the computer system 380, at least one of the CPU 382, the RAM 388, and the ROM 386 are changed, transforming the computer system 380 in part into a particular machine or apparatus having the novel functionality taught by the present disclosure. It is fundamental to the electrical engineering and software engineering arts that functionality that can be implemented by loading executable software into a computer can be converted to a hardware implementation by well-known design rules. Decisions between implementing a concept in software versus hardware typically hinge on considerations of stability of the design and numbers of units to be produced rather than any issues involved in translating from the software domain to the hardware domain. Generally, a design that is still subject to frequent change may be preferred to be implemented in software, because re-spinning a hardware implementation is more expensive than re-spinning a software design. Generally, a design that is stable that will be produced in large volume may be preferred to be implemented in hardware, for example in an application specific integrated circuit (ASIC), because for large production runs the hardware implementation may be less expensive than the software implementation. Often a design may be developed and tested in a software form and later transformed, by well-known design rules, to an equivalent hardware implementation in an application specific integrated circuit that hardwires the instructions of the software. In the same manner as a machine controlled by a new ASIC is a particular machine or apparatus, likewise a computer that has been programmed and/or loaded with executable instructions may be viewed as a particular machine or apparatus.
Additionally, after the system 380 is turned on or booted, the CPU 382 may execute a computer program or application. For example, the CPU 382 may execute software or firmware stored in the ROM 386 or stored in the RAM 388. In some cases, on boot and/or when the application is initiated, the CPU 382 may copy the application or portions of the application from the secondary storage 384 to the RAM 388 or to memory space within the CPU 382 itself, and the CPU 382 may then execute instructions that the application is comprised of. In some cases, the CPU 382 may copy the application or portions of the application from memory accessed via the network connectivity devices 392 or via the I/O devices 390 to the RAM 388 or to memory space within the CPU 382, and the CPU 382 may then execute instructions that the application is comprised of. During execution, an application may load instructions into the CPU 382, for example load some of the instructions of the application into a cache of the CPU 382. In some contexts, an application that is executed may be said to configure the CPU 382 to do something, e.g., to configure the CPU 382 to perform the function or functions promoted by the subject application. When the CPU 382 is configured in this way by the application, the CPU 382 becomes a specific purpose computer or a specific purpose machine.
The secondary storage 384 is typically comprised of one or more disk drives or tape drives and is used for non-volatile storage of data and as an over-flow data storage device if RAM 388 is not large enough to hold all working data. Secondary storage 384 may be used to store programs which are loaded into RAM 388 when such programs are selected for execution. The ROM 386 is used to store instructions and perhaps data which are read during program execution. ROM 386 is a non-volatile memory device which typically has a small memory capacity relative to the larger memory capacity of secondary storage 384. The RAM 388 is used to store volatile data and perhaps to store instructions. Access to both ROM 386 and RAM 388 is typically faster than to secondary storage 384. The secondary storage 384, the RAM 388, and/or the ROM 386 may be referred to in some contexts as computer readable storage media and/or non-transitory computer readable media.
I/O devices 390 may include printers, video monitors, liquid crystal displays (LCDs), touch screen displays, keyboards, keypads, switches, dials, mice, track balls, voice recognizers, card readers, paper tape readers, or other well-known input devices.
The network connectivity devices 392 may take the form of modems, modem banks, Ethernet cards, universal serial bus (USB) interface cards, serial interfaces, token ring cards, fiber distributed data interface (FDDI) cards, wireless local area network (WLAN) cards, radio transceiver cards that promote radio communications using protocols such as code division multiple access (CDMA), global system for mobile communications (GSM), long-term evolution (LTE), worldwide interoperability for microwave access (WiMAX), near field communications (NFC), radio frequency identity (RFID), and/or other air interface protocol radio transceiver cards, and other well-known network devices. These network connectivity devices 392 may enable the processor 382 to communicate with the Internet or one or more intranets. With such a network connection, it is contemplated that the processor 382 might receive information from the network, or might output information to the network in the course of performing the above-described method steps. Such information, which is often represented as a sequence of instructions to be executed using processor 382, may be received from and outputted to the network, for example, in the form of a computer data signal embodied in a carrier wave.
Such information, which may include data or instructions to be executed using processor 382 for example, may be received from and outputted to the network, for example, in the form of a computer data baseband signal or signal embodied in a carrier wave. The baseband signal or signal embedded in the carrier wave, or other types of signals currently used or hereafter developed, may be generated according to several methods well-known to one skilled in the art. The baseband signal and/or signal embedded in the carrier wave may be referred to in some contexts as a transitory signal.
The processor 382 executes instructions, codes, computer programs, scripts which it accesses from hard disk, floppy disk, optical disk (these various disk based systems may all be considered secondary storage 384), flash drive, ROM 386, RAM 388, or the network connectivity devices 392. While only one processor 382 is shown, multiple processors may be present. Thus, while instructions may be discussed as executed by a processor, the instructions may be executed simultaneously, serially, or otherwise executed by one or multiple processors. Instructions, codes, computer programs, scripts, and/or data that may be accessed from the secondary storage 384, for example, hard drives, floppy disks, optical disks, and/or other device, the ROM 386, and/or the RAM 388 may be referred to in some contexts as non-transitory instructions and/or non-transitory information.
In an embodiment, the computer system 380 may comprise two or more computers in communication with each other that collaborate to perform a task. For example, but not by way of limitation, an application may be partitioned in such a way as to permit concurrent and/or parallel processing of the instructions of the application. Alternatively, the data processed by the application may be partitioned in such a way as to permit concurrent and/or parallel processing of different portions of a data set by the two or more computers. In an embodiment, virtualization software may be employed by the computer system 380 to provide the functionality of a number of servers that is not directly bound to the number of computers in the computer system 380. For example, virtualization software may provide twenty virtual servers on four physical computers. In an embodiment, the functionality disclosed above may be provided by executing the application and/or applications in a cloud computing environment. Cloud computing may comprise providing computing services via a network connection using dynamically scalable computing resources. Cloud computing may be supported, at least in part, by virtualization software. A cloud computing environment may be established by an enterprise and/or may be hired on an as-needed basis from a third party provider. Some cloud computing environments may comprise cloud computing resources owned and operated by the enterprise as well as cloud computing resources hired and/or leased from a third party provider.
In an embodiment, some or all of the functionality disclosed above may be provided as a computer program product. The computer program product may comprise one or more computer readable storage medium having computer usable program code embodied therein to implement the functionality disclosed above. The computer program product may comprise data structures, executable instructions, and other computer usable program code. The computer program product may be embodied in removable computer storage media and/or non-removable computer storage media. The removable computer readable storage medium may comprise, without limitation, a paper tape, a magnetic tape, magnetic disk, an optical disk, a solid state memory chip, for example analog magnetic tape, compact disk read only memory (CD-ROM) disks, floppy disks, jump drives, digital cards, multimedia cards, and others. The computer program product may be suitable for loading, by the computer system 380, at least portions of the contents of the computer program product to the secondary storage 384, to the ROM 386, to the RAM 388, and/or to other non-volatile memory and volatile memory of the computer system 380. The processor 382 may process the executable instructions and/or data structures in part by directly accessing the computer program product, for example by reading from a CD-ROM disk inserted into a disk drive peripheral of the computer system 380. Alternatively, the processor 382 may process the executable instructions and/or data structures by remotely accessing the computer program product, for example by downloading the executable instructions and/or data structures from a remote server through the network connectivity devices 392. The computer program product may comprise instructions that promote the loading and/or copying of data, data structures, files, and/or executable instructions to the secondary storage 384, to the ROM 386, to the RAM 388, and/or to other non-volatile memory and volatile memory of the computer system 380.
In some contexts, the secondary storage 384, the ROM 386, and the RAM 388 may be referred to as a non-transitory computer readable medium or a computer readable storage media. A dynamic RAM embodiment of the RAM 388, likewise, may be referred to as a non-transitory computer readable medium in that while the dynamic RAM receives electrical power and is operated in accordance with its design, for example during a period of time during which the computer system 380 is turned on and operational, the dynamic RAM stores information that is written to it. Similarly, the processor 382 may comprise an internal RAM, an internal ROM, a cache memory, and/or other internal non-transitory storage blocks, sections, or components that may be referred to in some contexts as non-transitory computer readable media or computer readable storage media.
While several embodiments have been provided in the present disclosure, it should be understood that the disclosed systems and methods may be embodied in many other specific forms without departing from the spirit or scope of the present disclosure. The present examples are to be considered as illustrative and not restrictive, and the intention is not to be limited to the details given herein. For example, the various elements or components may be combined or integrated in another system or certain features may be omitted or not implemented.
Also, techniques, systems, subsystems, and methods described and illustrated in the various embodiments as discrete or separate may be combined or integrated with other systems, modules, techniques, or methods without departing from the scope of the present disclosure. Other items shown or discussed as directly coupled or communicating with each other may be indirectly coupled or communicating through some interface, device, or intermediate component, whether electrically, mechanically, or otherwise. Other examples of changes, substitutions, and alterations are ascertainable by one skilled in the art and could be made without departing from the spirit and scope disclosed herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5303378 | Cohen | Apr 1994 | A |
| 5321735 | Breeden et al. | Jun 1994 | A |
| 5764889 | Ault et al. | Jun 1998 | A |
| 5796952 | Davis et al. | Aug 1998 | A |
| 5825876 | Peterson, Jr. | Oct 1998 | A |
| 6131024 | Boltz | Oct 2000 | A |
| 6177860 | Cromer et al. | Jan 2001 | B1 |
| 6219712 | Mann et al. | Apr 2001 | B1 |
| 6222463 | Rai | Apr 2001 | B1 |
| 6363150 | Bhagavath et al. | Mar 2002 | B1 |
| 6389403 | Dorak, Jr. | May 2002 | B1 |
| 6434561 | Durst, Jr. et al. | Aug 2002 | B1 |
| 6477180 | Aggarwal et al. | Nov 2002 | B1 |
| 6507869 | Franke et al. | Jan 2003 | B1 |
| 6507904 | Ellison et al. | Jan 2003 | B1 |
| 6614893 | Paiz | Sep 2003 | B1 |
| 6651171 | England et al. | Nov 2003 | B1 |
| 6668322 | Wood et al. | Dec 2003 | B1 |
| 6691230 | Bardon | Feb 2004 | B1 |
| 6754784 | North et al. | Jun 2004 | B1 |
| 6823454 | Hind et al. | Nov 2004 | B1 |
| 6824064 | Guthery et al. | Nov 2004 | B2 |
| 6895234 | Laursen et al. | May 2005 | B1 |
| 7023979 | Wu et al. | Apr 2006 | B1 |
| 7043241 | Sladek et al. | May 2006 | B1 |
| 7069234 | Cornelius et al. | Jun 2006 | B1 |
| 7127541 | Govindarajulu et al. | Oct 2006 | B2 |
| 7366806 | Milenkovic et al. | Apr 2008 | B2 |
| 7386275 | Pirzada et al. | Jun 2008 | B2 |
| 7387240 | Ziegler | Jun 2008 | B2 |
| 7519824 | Peyravian et al. | Apr 2009 | B1 |
| 7552467 | Lindsay | Jun 2009 | B2 |
| 7571364 | Whetsel | Aug 2009 | B2 |
| 7574382 | Hubert | Aug 2009 | B1 |
| 7650645 | Langendorf et al. | Jan 2010 | B1 |
| 7716720 | Marek et al. | May 2010 | B1 |
| 7761558 | Jindal et al. | Jul 2010 | B1 |
| 7849309 | Brown | Dec 2010 | B1 |
| 7873837 | Lee et al. | Jan 2011 | B1 |
| 7895642 | Larson et al. | Feb 2011 | B1 |
| 7921303 | Mauro, II | Apr 2011 | B2 |
| 8060449 | Zhu | Nov 2011 | B1 |
| 8073428 | Khetawat et al. | Dec 2011 | B2 |
| 8086238 | Kosar | Dec 2011 | B1 |
| 8112794 | Little et al. | Feb 2012 | B2 |
| 8155642 | Russell | Apr 2012 | B2 |
| 8190919 | Natarajan et al. | May 2012 | B2 |
| 8204480 | Lindteigen et al. | Jun 2012 | B1 |
| 8238823 | Maugars et al. | Aug 2012 | B2 |
| 8271336 | Mikurak | Sep 2012 | B2 |
| 8295811 | Gailloux et al. | Oct 2012 | B1 |
| 8298295 | Aissi et al. | Oct 2012 | B2 |
| 8316237 | Felsher et al. | Nov 2012 | B1 |
| 8332895 | Nathan et al. | Dec 2012 | B2 |
| 8332953 | Lemieux et al. | Dec 2012 | B2 |
| 8402543 | Ranjan et al. | Mar 2013 | B1 |
| 8413229 | Mullick et al. | Apr 2013 | B2 |
| 8429409 | Wall et al. | Apr 2013 | B1 |
| 8442588 | Sims et al. | May 2013 | B2 |
| 8443420 | Brown et al. | May 2013 | B2 |
| 8447983 | Beck et al. | May 2013 | B1 |
| 8494576 | Bye et al. | Jul 2013 | B1 |
| 8498572 | Schooley et al. | Jul 2013 | B1 |
| 8504097 | Cope et al. | Aug 2013 | B1 |
| 8542833 | Devol et al. | Sep 2013 | B2 |
| 8566183 | Bonar et al. | Oct 2013 | B1 |
| 8588749 | Sadhvani et al. | Nov 2013 | B1 |
| 8590012 | Roy et al. | Nov 2013 | B2 |
| 8631247 | OLoughlin et al. | Jan 2014 | B2 |
| 8632000 | Laracey | Jan 2014 | B2 |
| 8649770 | Cope et al. | Feb 2014 | B1 |
| 8650492 | Mui et al. | Feb 2014 | B1 |
| 8661119 | Jindal et al. | Feb 2014 | B1 |
| 8667607 | Paczkowski et al. | Mar 2014 | B2 |
| 8681969 | Rodde et al. | Mar 2014 | B1 |
| 8699998 | Sprigg et al. | Apr 2014 | B2 |
| 8707056 | Felton | Apr 2014 | B2 |
| 8712407 | Cope et al. | Apr 2014 | B1 |
| 8718554 | Abel | May 2014 | B2 |
| 8719586 | Paleja et al. | May 2014 | B1 |
| 8726343 | Borzycki et al. | May 2014 | B1 |
| 8738333 | Behera et al. | May 2014 | B1 |
| 8750839 | Paczkowski et al. | Jun 2014 | B1 |
| 8752140 | Paczkowski et al. | Jun 2014 | B1 |
| 8762298 | Ranjan et al. | Jun 2014 | B1 |
| 8787873 | Hitt et al. | Jul 2014 | B1 |
| 8793808 | Boccon-Gibod | Jul 2014 | B2 |
| 8797875 | Garcia Martin et al. | Aug 2014 | B2 |
| 8811971 | Corda et al. | Aug 2014 | B2 |
| 8826015 | Lakshminarayanan et al. | Sep 2014 | B2 |
| 8831998 | Cramer et al. | Sep 2014 | B1 |
| 8839460 | Shirlen et al. | Sep 2014 | B2 |
| 8850568 | Shirlen et al. | Sep 2014 | B2 |
| 8856600 | Zadigian et al. | Oct 2014 | B2 |
| 8862181 | Cope et al. | Oct 2014 | B1 |
| 8863252 | Katzer et al. | Oct 2014 | B1 |
| 8868898 | Van Hoof | Oct 2014 | B1 |
| 8881977 | Paczkowski et al. | Nov 2014 | B1 |
| 8886925 | Qureshi et al. | Nov 2014 | B2 |
| 8954588 | Bertz et al. | Feb 2015 | B1 |
| 8984592 | Paczkowski et al. | Mar 2015 | B1 |
| 8989705 | Katzer et al. | Mar 2015 | B1 |
| 9015068 | Bertz et al. | Apr 2015 | B1 |
| 9021585 | Paczkowski et al. | Apr 2015 | B1 |
| 9027102 | Katzer et al. | May 2015 | B2 |
| 9049013 | Paczkowski et al. | Jun 2015 | B2 |
| 9049186 | Paczkowski et al. | Jun 2015 | B1 |
| 9066230 | Paczkowski et al. | Jun 2015 | B1 |
| 9069952 | Paczkowski et al. | Jun 2015 | B1 |
| 9104840 | Paczkowski et al. | Aug 2015 | B1 |
| 9118655 | Paczkowski et al. | Aug 2015 | B1 |
| 9161227 | Bye et al. | Oct 2015 | B1 |
| 9161325 | Urbanek | Oct 2015 | B1 |
| 9171243 | Cordes et al. | Oct 2015 | B1 |
| 9177157 | Binder | Nov 2015 | B2 |
| 9183412 | Bye et al. | Nov 2015 | B2 |
| 9183606 | Paczkowski et al. | Nov 2015 | B1 |
| 9185626 | Kunkel et al. | Nov 2015 | B1 |
| 9191388 | Paczkowski et al. | Nov 2015 | B1 |
| 9191522 | Krieger et al. | Nov 2015 | B1 |
| 9208339 | Paczkowski et al. | Dec 2015 | B1 |
| 9210576 | Cope et al. | Dec 2015 | B1 |
| 9215180 | Bertz et al. | Dec 2015 | B1 |
| 9226145 | Loman et al. | Dec 2015 | B1 |
| 9230085 | Paczkowski et al. | Jan 2016 | B1 |
| 9253589 | McCann et al. | Feb 2016 | B2 |
| 9268959 | Paczkowski et al. | Feb 2016 | B2 |
| 9282898 | McRoberts et al. | Mar 2016 | B2 |
| 9324016 | Cordes et al. | Apr 2016 | B1 |
| 9374363 | Paczkowski et al. | Jun 2016 | B1 |
| 9384498 | Benz et al. | Jul 2016 | B1 |
| 9443088 | Bye et al. | Sep 2016 | B1 |
| 9454723 | Cordes et al. | Sep 2016 | B1 |
| 9473945 | Marquardt et al. | Oct 2016 | B1 |
| 9560519 | McCracken, Jr. et al. | Jan 2017 | B1 |
| 9613208 | Paczkowski et al. | Apr 2017 | B1 |
| 9712999 | Cordes et al. | Jul 2017 | B1 |
| 9779232 | Paczkowski et al. | Oct 2017 | B1 |
| 9811672 | Bye et al. | Nov 2017 | B2 |
| 9817992 | Paczkowski et al. | Nov 2017 | B1 |
| 9819679 | Bertz et al. | Nov 2017 | B1 |
| 9838392 | Sainio et al. | Dec 2017 | B2 |
| 9838868 | Nelson et al. | Dec 2017 | B1 |
| 9838869 | Bye et al. | Dec 2017 | B1 |
| 9906958 | Katzer et al. | Feb 2018 | B2 |
| 9949304 | McCracken et al. | Apr 2018 | B1 |
| 10154019 | McRoberts et al. | Dec 2018 | B2 |
| 20010041591 | Carroll | Nov 2001 | A1 |
| 20020002468 | Spagna et al. | Jan 2002 | A1 |
| 20020007456 | Peinado et al. | Jan 2002 | A1 |
| 20020035697 | McCurdy et al. | Mar 2002 | A1 |
| 20020091569 | Kitaura et al. | Jul 2002 | A1 |
| 20020095389 | Gaines | Jul 2002 | A1 |
| 20020156911 | Croman et al. | Oct 2002 | A1 |
| 20020166070 | Mualem et al. | Nov 2002 | A1 |
| 20020174344 | Ting | Nov 2002 | A1 |
| 20020181503 | Montgomery | Dec 2002 | A1 |
| 20020184325 | Killcommons et al. | Dec 2002 | A1 |
| 20020194361 | Itoh et al. | Dec 2002 | A1 |
| 20020194496 | Griffin et al. | Dec 2002 | A1 |
| 20030045273 | Pyhalammi et al. | Mar 2003 | A1 |
| 20030092435 | Boivin | May 2003 | A1 |
| 20030093667 | Dutta et al. | May 2003 | A1 |
| 20030110046 | Cofta | Jun 2003 | A1 |
| 20030126225 | Camble et al. | Jul 2003 | A1 |
| 20030172163 | Fujita et al. | Sep 2003 | A1 |
| 20030182347 | Dehlinger | Sep 2003 | A1 |
| 20030216143 | Roese et al. | Nov 2003 | A1 |
| 20030229514 | Brown | Dec 2003 | A2 |
| 20030237002 | Oishi et al. | Dec 2003 | A1 |
| 20040036572 | Forster | Feb 2004 | A1 |
| 20040043788 | Mittal | Mar 2004 | A1 |
| 20040064351 | Mikurak | Apr 2004 | A1 |
| 20040093274 | Vanska et al. | May 2004 | A1 |
| 20040137890 | Kalke | Jul 2004 | A1 |
| 20040158840 | Rothman et al. | Aug 2004 | A1 |
| 20040202319 | Hussain et al. | Oct 2004 | A1 |
| 20040202328 | Hara | Oct 2004 | A1 |
| 20040233844 | Yu et al. | Nov 2004 | A1 |
| 20040234049 | Melideo | Nov 2004 | A1 |
| 20040243810 | Rindborg et al. | Dec 2004 | A1 |
| 20040264372 | Huang | Dec 2004 | A1 |
| 20050015601 | Tabi | Jan 2005 | A1 |
| 20050030898 | Furlong et al. | Feb 2005 | A1 |
| 20050044375 | Paatero et al. | Feb 2005 | A1 |
| 20050045719 | Yang | Mar 2005 | A1 |
| 20050052994 | Lee | Mar 2005 | A1 |
| 20050091505 | Riley et al. | Apr 2005 | A1 |
| 20050107068 | Smith et al. | May 2005 | A1 |
| 20050123596 | Kohane et al. | Jun 2005 | A1 |
| 20050125396 | Liu | Jun 2005 | A1 |
| 20050138433 | Linetsky | Jun 2005 | A1 |
| 20050145688 | Milenkovic et al. | Jul 2005 | A1 |
| 20050153741 | Chen et al. | Jul 2005 | A1 |
| 20050164680 | Gould | Jul 2005 | A1 |
| 20050181796 | Kumar et al. | Aug 2005 | A1 |
| 20050200478 | Koch et al. | Sep 2005 | A1 |
| 20050226468 | Deshpande et al. | Oct 2005 | A1 |
| 20050228892 | Riley et al. | Oct 2005 | A1 |
| 20050235166 | England et al. | Oct 2005 | A1 |
| 20050239481 | Seligmann | Oct 2005 | A1 |
| 20050258250 | Melick et al. | Nov 2005 | A1 |
| 20050272445 | Zellner | Dec 2005 | A1 |
| 20050280557 | Jha et al. | Dec 2005 | A1 |
| 20050283660 | McKeen et al. | Dec 2005 | A1 |
| 20050289355 | Kitariev et al. | Dec 2005 | A1 |
| 20060008256 | Khedouri et al. | Jan 2006 | A1 |
| 20060030291 | Dawson et al. | Feb 2006 | A1 |
| 20060036851 | DeTreville | Feb 2006 | A1 |
| 20060040641 | Dawson et al. | Feb 2006 | A1 |
| 20060053283 | Feinleib et al. | Mar 2006 | A1 |
| 20060074544 | Morariu et al. | Apr 2006 | A1 |
| 20060129488 | Vincent | Jun 2006 | A1 |
| 20060156026 | Utin | Jul 2006 | A1 |
| 20060161626 | Cardina et al. | Jul 2006 | A1 |
| 20060164978 | Werner et al. | Jul 2006 | A1 |
| 20060168637 | Vysotsky et al. | Jul 2006 | A1 |
| 20060171537 | Enright | Aug 2006 | A1 |
| 20060190605 | Franz et al. | Aug 2006 | A1 |
| 20060212853 | Sutardja | Sep 2006 | A1 |
| 20060218320 | Avraham et al. | Sep 2006 | A1 |
| 20060224901 | Lowe | Oct 2006 | A1 |
| 20060239131 | Nathan et al. | Oct 2006 | A1 |
| 20060245438 | Sajassi et al. | Nov 2006 | A1 |
| 20060258289 | Dua | Nov 2006 | A1 |
| 20060259790 | Asokan et al. | Nov 2006 | A1 |
| 20060261949 | Kim et al. | Nov 2006 | A1 |
| 20060277307 | Bernardin et al. | Dec 2006 | A1 |
| 20060277433 | Largman et al. | Dec 2006 | A1 |
| 20070006175 | Durham et al. | Jan 2007 | A1 |
| 20070011061 | East | Jan 2007 | A1 |
| 20070038648 | Chetwood et al. | Feb 2007 | A1 |
| 20070061535 | Xu et al. | Mar 2007 | A1 |
| 20070061570 | Holtzman et al. | Mar 2007 | A1 |
| 20070078988 | Miloushev et al. | Apr 2007 | A1 |
| 20070079120 | Bade et al. | Apr 2007 | A1 |
| 20070093246 | Adamany | Apr 2007 | A1 |
| 20070094273 | Fritsch et al. | Apr 2007 | A1 |
| 20070094691 | Gazdzinski | Apr 2007 | A1 |
| 20070104215 | Wang et al. | May 2007 | A1 |
| 20070118880 | Mauro | May 2007 | A1 |
| 20070143210 | Yeung et al. | Jun 2007 | A1 |
| 20070150730 | Conti | Jun 2007 | A1 |
| 20070156850 | Corrion | Jul 2007 | A1 |
| 20070162759 | Buskey et al. | Jul 2007 | A1 |
| 20070167167 | Jiang | Jul 2007 | A1 |
| 20070177771 | Tanaka et al. | Aug 2007 | A1 |
| 20070180120 | Bainbridge et al. | Aug 2007 | A1 |
| 20070186212 | Mazzaferri et al. | Aug 2007 | A1 |
| 20070188306 | Tethrake et al. | Aug 2007 | A1 |
| 20070192652 | Kao et al. | Aug 2007 | A1 |
| 20070197261 | Humbel | Aug 2007 | A1 |
| 20070214332 | Sonoda et al. | Sep 2007 | A1 |
| 20070226389 | Poortman | Sep 2007 | A1 |
| 20070261112 | Todd et al. | Nov 2007 | A1 |
| 20070276969 | Bressy et al. | Nov 2007 | A1 |
| 20070277223 | Datta et al. | Nov 2007 | A1 |
| 20070280245 | Rosberg | Dec 2007 | A1 |
| 20070283449 | Blum et al. | Dec 2007 | A1 |
| 20080005794 | Inoue et al. | Jan 2008 | A1 |
| 20080011825 | Giordano et al. | Jan 2008 | A1 |
| 20080014867 | Finn | Jan 2008 | A1 |
| 20080020745 | Bae et al. | Jan 2008 | A1 |
| 20080022374 | Brown et al. | Jan 2008 | A1 |
| 20080022389 | Calcev et al. | Jan 2008 | A1 |
| 20080034231 | Ginter et al. | Feb 2008 | A1 |
| 20080051142 | Calvet et al. | Feb 2008 | A1 |
| 20080068166 | Lauper et al. | Mar 2008 | A1 |
| 20080089517 | Bianco et al. | Apr 2008 | A1 |
| 20080092213 | Wei et al. | Apr 2008 | A1 |
| 20080097793 | Dicks et al. | Apr 2008 | A1 |
| 20080100419 | Jatschka et al. | May 2008 | A1 |
| 20080108321 | Taaghol et al. | May 2008 | A1 |
| 20080109662 | Natarajan et al. | May 2008 | A1 |
| 20080121687 | Buhot | May 2008 | A1 |
| 20080146280 | Sasse et al. | Jun 2008 | A1 |
| 20080155271 | Barck et al. | Jun 2008 | A1 |
| 20080159129 | Songhurst et al. | Jul 2008 | A1 |
| 20080159131 | Hoeflin et al. | Jul 2008 | A1 |
| 20080160997 | Kim | Jul 2008 | A1 |
| 20080162361 | Sklovsky et al. | Jul 2008 | A1 |
| 20080162637 | Adamczyk | Jul 2008 | A1 |
| 20080168515 | Benson et al. | Jul 2008 | A1 |
| 20080176538 | Terrill et al. | Jul 2008 | A1 |
| 20080188178 | Maugars et al. | Aug 2008 | A1 |
| 20080201212 | Hammad et al. | Aug 2008 | A1 |
| 20080201578 | Drake | Aug 2008 | A1 |
| 20080208681 | Hammad et al. | Aug 2008 | A1 |
| 20080212503 | Lipford et al. | Sep 2008 | A1 |
| 20080232259 | Thomson | Sep 2008 | A1 |
| 20080244758 | Sahita et al. | Oct 2008 | A1 |
| 20080271163 | Stillerman et al. | Oct 2008 | A1 |
| 20080274716 | Fok | Nov 2008 | A1 |
| 20080281953 | Blaisdell | Nov 2008 | A1 |
| 20080304640 | Reilly | Dec 2008 | A1 |
| 20080320577 | Larduinat | Dec 2008 | A1 |
| 20090047923 | Jain et al. | Feb 2009 | A1 |
| 20090049220 | Conti et al. | Feb 2009 | A1 |
| 20090055278 | Nemani | Feb 2009 | A1 |
| 20090070272 | Jain | Mar 2009 | A1 |
| 20090075592 | Nystrom et al. | Mar 2009 | A1 |
| 20090089449 | Day | Apr 2009 | A1 |
| 20090113425 | Ports et al. | Apr 2009 | A1 |
| 20090118839 | Accapadi et al. | May 2009 | A1 |
| 20090132381 | Gangi | May 2009 | A1 |
| 20090141713 | Beverly | Jun 2009 | A1 |
| 20090144161 | Fisher | Jun 2009 | A1 |
| 20090147958 | Calcaterra et al. | Jun 2009 | A1 |
| 20090154348 | Newman | Jun 2009 | A1 |
| 20090164800 | Johansson et al. | Jun 2009 | A1 |
| 20090182605 | Lappas et al. | Jul 2009 | A1 |
| 20090182634 | Park et al. | Jul 2009 | A1 |
| 20090192915 | Fernandez | Jul 2009 | A1 |
| 20090193491 | Rao | Jul 2009 | A1 |
| 20090204959 | Anand et al. | Aug 2009 | A1 |
| 20090215385 | Waters et al. | Aug 2009 | A1 |
| 20090224919 | Angell et al. | Sep 2009 | A1 |
| 20090227290 | Chien | Sep 2009 | A1 |
| 20090248445 | Harnick | Oct 2009 | A1 |
| 20090271321 | Stafford | Oct 2009 | A1 |
| 20090275364 | Morel et al. | Nov 2009 | A1 |
| 20090281947 | Erel | Nov 2009 | A1 |
| 20090289764 | Chiu | Nov 2009 | A1 |
| 20090300599 | Piotrowski | Dec 2009 | A1 |
| 20090312011 | Huomo et al. | Dec 2009 | A1 |
| 20090320028 | Gellerich et al. | Dec 2009 | A1 |
| 20090320048 | Watt et al. | Dec 2009 | A1 |
| 20100031325 | Maigne et al. | Feb 2010 | A1 |
| 20100052844 | Wesby | Mar 2010 | A1 |
| 20100064341 | Aldera | Mar 2010 | A1 |
| 20100066486 | Park et al. | Mar 2010 | A1 |
| 20100075669 | Sparks et al. | Mar 2010 | A1 |
| 20100077487 | Travis et al. | Mar 2010 | A1 |
| 20100082977 | Boyle et al. | Apr 2010 | A1 |
| 20100121156 | Yoo | May 2010 | A1 |
| 20100125512 | Jones et al. | May 2010 | A1 |
| 20100125904 | Nice et al. | May 2010 | A1 |
| 20100127868 | Hamilton et al. | May 2010 | A1 |
| 20100128598 | Gandhewar et al. | May 2010 | A1 |
| 20100130170 | Liu et al. | May 2010 | A1 |
| 20100142517 | Montemurro et al. | Jun 2010 | A1 |
| 20100146589 | Safa | Jun 2010 | A1 |
| 20100153513 | Zahran | Jun 2010 | A1 |
| 20100153721 | Mellqvist | Jun 2010 | A1 |
| 20100162028 | Frank et al. | Jun 2010 | A1 |
| 20100167755 | Kim | Jul 2010 | A1 |
| 20100190469 | Vanderveen et al. | Jul 2010 | A1 |
| 20100191613 | Raleigh | Jul 2010 | A1 |
| 20100198943 | Harrang et al. | Aug 2010 | A1 |
| 20100217709 | Aabye et al. | Aug 2010 | A1 |
| 20100223348 | Przybysz et al. | Sep 2010 | A1 |
| 20100228937 | Bae et al. | Sep 2010 | A1 |
| 20100241847 | van der Horst et al. | Sep 2010 | A1 |
| 20100246818 | Yao | Sep 2010 | A1 |
| 20100263029 | Tohmo et al. | Oct 2010 | A1 |
| 20100269156 | Hohlfeld et al. | Oct 2010 | A1 |
| 20100274726 | Florek et al. | Oct 2010 | A1 |
| 20100279653 | Poltorak | Nov 2010 | A1 |
| 20100281139 | Deprun | Nov 2010 | A1 |
| 20100291896 | Corda | Nov 2010 | A1 |
| 20100299313 | Orsini et al. | Nov 2010 | A1 |
| 20100306353 | Briscoe et al. | Dec 2010 | A1 |
| 20100318802 | Balakrishnan | Dec 2010 | A1 |
| 20100328064 | Rogel | Dec 2010 | A1 |
| 20110010720 | Smith et al. | Jan 2011 | A1 |
| 20110014948 | Yeh | Jan 2011 | A1 |
| 20110021175 | Florek et al. | Jan 2011 | A1 |
| 20110030030 | Terpening et al. | Feb 2011 | A1 |
| 20110035604 | Habraken | Feb 2011 | A1 |
| 20110050713 | McCrary et al. | Mar 2011 | A1 |
| 20110055084 | Singh | Mar 2011 | A1 |
| 20110063093 | Fung et al. | Mar 2011 | A1 |
| 20110072492 | Mohler et al. | Mar 2011 | A1 |
| 20110078081 | Pirzadeh et al. | Mar 2011 | A1 |
| 20110078760 | De Perthuis | Mar 2011 | A1 |
| 20110082711 | Poeze et al. | Apr 2011 | A1 |
| 20110107426 | Yen et al. | May 2011 | A1 |
| 20110112968 | Florek et al. | May 2011 | A1 |
| 20110113479 | Ganem | May 2011 | A1 |
| 20110130635 | Ross | Jun 2011 | A1 |
| 20110138064 | Rieger et al. | Jun 2011 | A1 |
| 20110145923 | Largman et al. | Jun 2011 | A1 |
| 20110145926 | Dalcher et al. | Jun 2011 | A1 |
| 20110151836 | Dadu et al. | Jun 2011 | A1 |
| 20110154032 | Mauro | Jun 2011 | A1 |
| 20110166883 | Palmer et al. | Jul 2011 | A1 |
| 20110173090 | Miller et al. | Jul 2011 | A1 |
| 20110202916 | VoBa et al. | Aug 2011 | A1 |
| 20110208797 | Kim | Aug 2011 | A1 |
| 20110212707 | Mahalal | Sep 2011 | A1 |
| 20110216701 | Patel et al. | Sep 2011 | A1 |
| 20110218849 | Rutigliano et al. | Sep 2011 | A1 |
| 20110225293 | Rathod | Sep 2011 | A1 |
| 20110226853 | Soh et al. | Sep 2011 | A1 |
| 20110237190 | Jolivet | Sep 2011 | A1 |
| 20110238573 | Varadarajan | Sep 2011 | A1 |
| 20110238992 | Jancula et al. | Sep 2011 | A1 |
| 20110246609 | Kim | Oct 2011 | A1 |
| 20110251892 | Laracey | Oct 2011 | A1 |
| 20110254687 | Arponen et al. | Oct 2011 | A1 |
| 20110258443 | Barry | Oct 2011 | A1 |
| 20110258462 | Robertson et al. | Oct 2011 | A1 |
| 20110269456 | Krishnaswamy et al. | Nov 2011 | A1 |
| 20110276677 | Osuga et al. | Nov 2011 | A1 |
| 20110281558 | Winter | Nov 2011 | A1 |
| 20110294418 | Chen | Dec 2011 | A1 |
| 20120003983 | Sherlock et al. | Jan 2012 | A1 |
| 20120011572 | Chew et al. | Jan 2012 | A1 |
| 20120021683 | Ma et al. | Jan 2012 | A1 |
| 20120023583 | Sallam | Jan 2012 | A1 |
| 20120028575 | Chen et al. | Feb 2012 | A1 |
| 20120029997 | Khan et al. | Feb 2012 | A1 |
| 20120036347 | Swanson et al. | Feb 2012 | A1 |
| 20120040662 | Rahman et al. | Feb 2012 | A1 |
| 20120052801 | Kulkarni | Mar 2012 | A1 |
| 20120072481 | Nandlall et al. | Mar 2012 | A1 |
| 20120072979 | Cha et al. | Mar 2012 | A1 |
| 20120079100 | McIntyre et al. | Mar 2012 | A1 |
| 20120083242 | Spitz et al. | Apr 2012 | A1 |
| 20120084211 | Petrov et al. | Apr 2012 | A1 |
| 20120084438 | Raleigh et al. | Apr 2012 | A1 |
| 20120084836 | Mahaffey et al. | Apr 2012 | A1 |
| 20120089700 | Safruti et al. | Apr 2012 | A1 |
| 20120102202 | Omar | Apr 2012 | A1 |
| 20120108295 | Schell et al. | May 2012 | A1 |
| 20120115433 | Young et al. | May 2012 | A1 |
| 20120123868 | Brudnicki et al. | May 2012 | A1 |
| 20120130839 | Koh et al. | May 2012 | A1 |
| 20120131178 | Zhu et al. | May 2012 | A1 |
| 20120137101 | Arcese et al. | May 2012 | A1 |
| 20120137117 | Bosch et al. | May 2012 | A1 |
| 20120137119 | Doerr et al. | May 2012 | A1 |
| 20120143703 | Wall et al. | Jun 2012 | A1 |
| 20120147750 | Pelletier et al. | Jun 2012 | A1 |
| 20120149327 | Raboisson et al. | Jun 2012 | A1 |
| 20120149338 | Roundtree | Jun 2012 | A1 |
| 20120150601 | Fisher | Jun 2012 | A1 |
| 20120154413 | Kim et al. | Jun 2012 | A1 |
| 20120158467 | Hammad et al. | Jun 2012 | A1 |
| 20120159163 | von Behren et al. | Jun 2012 | A1 |
| 20120159612 | Reisgies | Jun 2012 | A1 |
| 20120163206 | Leung et al. | Jun 2012 | A1 |
| 20120166806 | Zhang et al. | Jun 2012 | A1 |
| 20120168494 | Kim | Jul 2012 | A1 |
| 20120178365 | Katz et al. | Jul 2012 | A1 |
| 20120178366 | Levy et al. | Jul 2012 | A1 |
| 20120190332 | Charles | Jul 2012 | A1 |
| 20120191536 | Chen et al. | Jul 2012 | A1 |
| 20120196529 | Huomo et al. | Aug 2012 | A1 |
| 20120196586 | Grigg et al. | Aug 2012 | A1 |
| 20120198519 | Parla et al. | Aug 2012 | A1 |
| 20120202423 | Tiedemann et al. | Aug 2012 | A1 |
| 20120207165 | Davis | Aug 2012 | A1 |
| 20120218084 | Arponen et al. | Aug 2012 | A1 |
| 20120220269 | Feng | Aug 2012 | A1 |
| 20120226582 | Hammad | Sep 2012 | A1 |
| 20120226772 | Grube et al. | Sep 2012 | A1 |
| 20120238206 | Singh et al. | Sep 2012 | A1 |
| 20120252480 | Krutt et al. | Oct 2012 | A1 |
| 20120255016 | Sallam | Oct 2012 | A1 |
| 20120258690 | Chen et al. | Oct 2012 | A1 |
| 20120259722 | Mikurak | Oct 2012 | A1 |
| 20120266076 | Lockhart et al. | Oct 2012 | A1 |
| 20120266220 | Brudnicki et al. | Oct 2012 | A1 |
| 20120272306 | Benaloh et al. | Oct 2012 | A1 |
| 20120274444 | Micali et al. | Nov 2012 | A1 |
| 20120282924 | Tagg et al. | Nov 2012 | A1 |
| 20120284195 | McMillen et al. | Nov 2012 | A1 |
| 20120291095 | Narendra et al. | Nov 2012 | A1 |
| 20120295588 | Chen et al. | Nov 2012 | A1 |
| 20120297187 | Paya et al. | Nov 2012 | A1 |
| 20120297202 | Gallet et al. | Nov 2012 | A1 |
| 20120303961 | Kean et al. | Nov 2012 | A1 |
| 20120304286 | Croll et al. | Nov 2012 | A1 |
| 20120309345 | Wake et al. | Dec 2012 | A1 |
| 20120324293 | Grube et al. | Dec 2012 | A1 |
| 20120329425 | Velusamy et al. | Dec 2012 | A1 |
| 20130003543 | Ludwig | Jan 2013 | A1 |
| 20130010641 | Dinan | Jan 2013 | A1 |
| 20130014259 | Gribble et al. | Jan 2013 | A1 |
| 20130019323 | Arvidsson et al. | Jan 2013 | A1 |
| 20130031374 | Thom et al. | Jan 2013 | A1 |
| 20130034081 | Ban et al. | Feb 2013 | A1 |
| 20130035056 | Prasad et al. | Feb 2013 | A1 |
| 20130047197 | Saroiu et al. | Feb 2013 | A1 |
| 20130054474 | Yeager | Feb 2013 | A1 |
| 20130061055 | Schibuk | Mar 2013 | A1 |
| 20130062417 | Lee et al. | Mar 2013 | A1 |
| 20130067552 | Hawkes et al. | Mar 2013 | A1 |
| 20130074067 | Chowdhry | Mar 2013 | A1 |
| 20130086385 | Poeluev | Apr 2013 | A1 |
| 20130086684 | Mohler | Apr 2013 | A1 |
| 20130086695 | Lakshminarayanan | Apr 2013 | A1 |
| 20130097302 | Khedouri et al. | Apr 2013 | A9 |
| 20130097657 | Cardamore et al. | Apr 2013 | A1 |
| 20130105565 | Kamprath | May 2013 | A1 |
| 20130109307 | Reisgies et al. | May 2013 | A1 |
| 20130111095 | Mehrotra et al. | May 2013 | A1 |
| 20130117186 | Weinstein et al. | May 2013 | A1 |
| 20130124583 | Ferguson et al. | May 2013 | A1 |
| 20130125114 | Frascadore | May 2013 | A1 |
| 20130136126 | Wang et al. | May 2013 | A1 |
| 20130138521 | Want et al. | May 2013 | A1 |
| 20130138959 | Pelly et al. | May 2013 | A1 |
| 20130140360 | Graylin | Jun 2013 | A1 |
| 20130143489 | Morris et al. | Jun 2013 | A1 |
| 20130145429 | Mendel et al. | Jun 2013 | A1 |
| 20130159021 | Felsher | Jun 2013 | A1 |
| 20130159186 | Brudnicki et al. | Jun 2013 | A1 |
| 20130159710 | Khan | Jun 2013 | A1 |
| 20130160120 | Malaviya et al. | Jun 2013 | A1 |
| 20130174147 | Sahita et al. | Jul 2013 | A1 |
| 20130175984 | Yamazaki et al. | Jul 2013 | A1 |
| 20130191632 | Spector et al. | Jul 2013 | A1 |
| 20130212704 | Shablygin et al. | Aug 2013 | A1 |
| 20130231098 | Jonas et al. | Sep 2013 | A1 |
| 20130260791 | Malinovskiy et al. | Oct 2013 | A1 |
| 20130262264 | Karstoft | Oct 2013 | A1 |
| 20130263212 | Faltyn et al. | Oct 2013 | A1 |
| 20130290359 | Eronen et al. | Oct 2013 | A1 |
| 20130290709 | Muppidi et al. | Oct 2013 | A1 |
| 20130310003 | Sadhvani et al. | Nov 2013 | A1 |
| 20130313314 | Jeng et al. | Nov 2013 | A1 |
| 20130331067 | Coussemaeker et al. | Dec 2013 | A1 |
| 20130332456 | Arkin | Dec 2013 | A1 |
| 20130343181 | Stroud et al. | Dec 2013 | A1 |
| 20130347064 | Aissi | Dec 2013 | A1 |
| 20130347103 | Veteikis et al. | Dec 2013 | A1 |
| 20140007182 | Qureshi et al. | Jan 2014 | A1 |
| 20140007222 | Qureshi et al. | Jan 2014 | A1 |
| 20140052562 | Oliveira et al. | Feb 2014 | A1 |
| 20140059642 | Deasy et al. | Feb 2014 | A1 |
| 20140074508 | Ying et al. | Mar 2014 | A1 |
| 20140089243 | Oppenheimer | Mar 2014 | A1 |
| 20140089699 | OConnor et al. | Mar 2014 | A1 |
| 20140104287 | Nalluri et al. | Apr 2014 | A1 |
| 20140106709 | Palamara et al. | Apr 2014 | A1 |
| 20140141718 | Stromberg et al. | May 2014 | A1 |
| 20140143826 | Sharp et al. | May 2014 | A1 |
| 20140155025 | Parker et al. | Jun 2014 | A1 |
| 20140166745 | Graef et al. | Jun 2014 | A1 |
| 20140173747 | Govindaraju | Jun 2014 | A1 |
| 20140188412 | Mahajan et al. | Jul 2014 | A1 |
| 20140188738 | Huxharn | Jul 2014 | A1 |
| 20140200051 | Liu | Jul 2014 | A1 |
| 20140215196 | Berlin | Jul 2014 | A1 |
| 20140222955 | Islam | Aug 2014 | A1 |
| 20140245444 | Lutas et al. | Aug 2014 | A1 |
| 20140254381 | Racz et al. | Sep 2014 | A1 |
| 20140267332 | Chhabra et al. | Sep 2014 | A1 |
| 20140279523 | Lynam et al. | Sep 2014 | A1 |
| 20140279556 | Priebatsch et al. | Sep 2014 | A1 |
| 20140279558 | Kadi et al. | Sep 2014 | A1 |
| 20140298026 | Isozaki et al. | Oct 2014 | A1 |
| 20140331279 | Aissi | Nov 2014 | A1 |
| 20150032976 | Chapier et al. | Jan 2015 | A1 |
| 20150106805 | Melander et al. | Apr 2015 | A1 |
| 20150172928 | Katzer et al. | Jun 2015 | A1 |
| 20150358455 | Mosher et al. | Dec 2015 | A1 |
| 20160004876 | Bye et al. | Jan 2016 | A1 |
| 20160142396 | McRoberts et al. | May 2016 | A1 |
| 20160150478 | Li et al. | May 2016 | A1 |
| 20160323731 | Mohammed | Nov 2016 | A1 |
| 20170026840 | Eyal | Jan 2017 | A1 |
| 20170180395 | Stransky-Heilkron | Jun 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 1933252 | May 2016 | EP |
| 2456754 | Jul 2009 | GB |
| 6171245 | Aug 2017 | JP |
| 6332766 | May 2018 | JP |
| WO2011025433 | Mar 2011 | WO |
| WO2012064171 | May 2012 | WO |
| WO2012085593 | Jun 2012 | WO |
| WO2013170228 | Nov 2013 | WO |
| WO2014004590 | Jan 2014 | WO |
| WO2014018575 | Jan 2014 | WO |
| WO2014025687 | Feb 2014 | WO |
| WO2014158431 | Oct 2014 | WO |
| Entry |
|---|
| FAIPP Pre-Interview Communication dated Mar. 24, 2015, U.S. Appl. No. 13/964,112, filed Aug. 12, 2013. |
| Notice of Allowance dated Aug. 3, 2015, U.S. Appl. No. 13/964,112, filed Aug. 12, 2013. |
| Office Action dated Aug. 25, 2016, U.S. Appl. No. 13/860,338, filed Apr. 10, 2013. |
| Final Office Action dated Mar. 9, 2017, U.S. Appl. No. 13/860,338, filed Apr. 10, 2013. |
| Advisory Action dated Jun. 1, 2017, U.S. Appl. No. 13/860,338, filed Apr. 10, 2013. |
| Notice of Allowance dated Jul. 28, 2017, U.S. Appl. No. 13/860,338, filed Apr. 10, 2013. |
| Restriction Requirement dated Jan. 12, 2016, U.S. Appl. No. 13/912,190, filed Jun. 6, 2013. |
| FAIPP Pre-Interview Communication dated Mar. 11, 2016, U.S. Appl. No. 13/912,190, filed Jun. 6, 2013. |
| Notice of Allowance dated Aug. 24, 2016, U.S. Appl. No. 13/912,190, filed Jun. 6, 2013. |
| FAIPP Pre-Interview Communication dated Oct. 12, 2017, U.S. Appl. No. 15/365,934, filed Nov. 30, 2016. |
| Notice of Allowance dated Dec. 7, 2017, U.S. Appl. No. 15/365,934, filed Nov. 30, 2016. |
| FAIPP Pre-Interview Communication dated Apr. 15, 2015, U.S. Appl. No. 14/085,474, filed Nov. 20, 2013. |
| Notice of Allowance dated May 29, 2015, U.S. Appl. No. 14/085,474, filed Nov. 20, 2013. |
| FAIPP Pre-Interview Communication dated Feb. 4, 2015, U.S. Appl. No. 14/075,663, filed Nov. 8, 2013. |
| First Action Interview Office Action dated Apr. 10, 2015, U.S. Appl. No. 14/075,663, filed Nov. 8, 2013. |
| Notice of Allowance dated Jul. 1, 2015, U.S. Appl. No. 14/075,663, filed Nov. 8, 2013. |
| FAIPP Pre-Interview Communication dated Feb. 24, 2015, U.S. Appl. No. 14/163,047, filed Jan. 24, 2014. |
| Notice of Allowance dated Apr. 9, 2015, U.S. Appl. No. 14/163,047, filed Jan. 24, 2014. |
| Notice of Allowance dated Jul. 22, 2015, U.S. Appl. No. 14/229,532, filed Mar. 28, 2014. |
| Notice of Allowance dated Aug. 28, 2015, U.S. Appl. No. 14/446,330, filed Jul. 29, 2014. |
| FAIPP Pre-Interview Communication dated Apr. 27, 2017, Application U.S. Appl. No. 14/606,011, filed Jan. 26, 2015. |
| Notice of Allowance dated Aug. 7, 2017, U.S. Appl. No. 14/606,011, filed Jan. 26, 2015. |
| FAIPP Pre-Interview Communication dated Aug. 8, 2016, U.S. Appl. No. 14/596,218, filed Jan. 14, 2015. |
| FAIPP Office Action dated Apr. 5, 2017, U.S. Appl. No. 14/596,218, filed Jan. 14, 2015. |
| Notice of Allowance dated May 30, 2017, U.S. Appl. No. 14/596,218, filed Jan. 14, 2015. |
| FAIPP Pre-Interview Communication dated Nov. 18, 2015, U.S. Appl. No. 14/681,077, filed Apr. 7, 2015. |
| First Action Interview Office Action dated Mar. 28, 2016, U.S. Appl. No. 14/681,077, filed Apr. 7, 2015. |
| Notice of Allowance dated Jun. 15, 2016, U.S. Appl. No. 14/681,077, filed Apr. 7, 2015. |
| FAIPP Pre-Interview Communication dated May 9, 2017, U.S. Appl. No. 14/853,492, filed Sep. 14, 2015. |
| Notice of Allowance dated Jul. 7, 2017, U.S. Appl. No. 14/853,492, filed Sep. 14, 2015. |
| Office Action dated Mar. 8, 2017, U.S. Appl. No. 14/947,257, filed Nov. 20, 2015. |
| Notice of Allowance dated Jul. 24, 2017, U.S. Appl. No. 14/947,257, filed Nov. 20, 2015. |
| FAIPP Pre-Interview Communication dated Aug. 5, 2015, U.S. Appl. No. 13/857,141, filed Apr. 4, 2013. |
| Notice of Allowance dated Dec. 17, 2015, U.S. Appl. No. 13/857,141, filed Apr. 4, 2013 . |
| FAIPP Pre-Interview Communication dated Oct. 5, 2016, U.S. Appl. No. 15/069,921, filed Mar. 14, 2016. |
| Notice of Allowance dated Mar. 10, 2017, U.S. Appl. No. 15/069,921, filed Mar. 14, 2016. |
| Restriction Requirement dated Jan. 5, 2015, U.S. Appl. No. 13/857,139, filed Apr. 4, 2013. |
| FAIPP Pre-Interview Communication dated Jun. 2, 2015, U.S. Appl. No. 13/857,139, filed Apr. 4, 2013. |
| Office Action dated Nov. 19, 2015, U.S. Appl. No. 13/857,139, filed Apr. 4, 2013. |
| Notice of Allowance dated May 26, 2016, U.S. Appl. No. 13/857,139, filed Apr. 4, 2013. |
| FAIPP Pre-Interview Communication dated Mar. 2, 2015, U.S. Appl. No. 13/857,138, filed Apr. 4, 2013. |
| First Action Interview Office Action dated Apr. 20, 2015, U.S. Appl. No. 13/857,138, filed Apr. 4, 2013. |
| FAIPP Pre-Interview Communication dated Dec. 27, 2011, U.S. Appl. No. 12/486,873, filed Jun. 18, 2009. |
| First Action Interview Office Action dated Feb. 13, 2012, U.S. Appl. No. 12/486,873, filed Jun. 18, 2009. |
| Office Action dated Jul. 5, 2012, U.S. Appl. No. 12/486,873, filed Jun. 18, 2009. |
| Final Office Action dated Feb. 1, 2013, U.S. Appl. No. 12/486,873, filed Jun. 18, 2009. |
| Notice of Allowance dated Jan. 28, 2014, U.S. Appl. No. 12/486,873, filed Jun. 18, 2009. |
| Zimmerman, Ann, “Check Out the Future of Shopping”, The Wall Street Journal, Business, May 18, 2011, http://online.wsj,com/article/SB10001424052748703421204576329253050634700.html. |
| Garry, Michael, Kroger Test Prepares for Mobile Future:, SN, Supermarket News, Jun. 13, 2011, http://supermarketnews.com/technology/kroger-test-prepares-mobile-future. |
| Jones, Sally, “Industry Trends in POS Hardware for Mobile Devices”, Aug. 31, 2011, http://pointofsale.com/20110831734/Mobile-POS-News/industry-trends-in-pos-hardware-for-mobile-devices.html. |
| Notice of Allowance dated Sep. 21, 2015, U.S. Appl. No. 14/148,714, filed Jan. 6, 2014. |
| European Examination Report dated Mar. 3, 2016, EPC Application Serial No. 13822974.5, filed on Jan. 8, 2015. |
| Japanese Decision for Grant dated Jun. 6, 2017, JP Application Serial No. 2015-524404. |
| FAIPP Pre-Interview Communication dated Aug. 4, 2014, U.S. Appl. No. 13/844,357, filed Mar. 15, 2013. |
| Notice of Allowance dated Oct. 6, 2014, U.S. Appl. No. 13/844,357, filed Mar. 15, 2013. |
| FAIPP Pre-Interview Communication dated Nov. 12, 2014, U.S. Appl. No. 13/844,145, filed Mar. 15, 2013. |
| Final Office Action dated Apr. 7, 2015, U.S. Appl. No. 13/844,145, filed Mar. 15, 2013. |
| Notice of Allowance dated Jul. 6, 2015, U.S. Appl. No. 13/844,145, filed Mar. 15, 2013. |
| FAIPP Pre-Interview Communication dated Mar. 1, 2016, U.S. Appl. No. 13/863,376, filed Apr. 15, 2013. |
| Notice of Allowance dated May 2, 2016, U.S. Appl. No. 13/863,376, filed Apr. 15, 2013. |
| FAIPP Pre-Interview Communication dated Apr. 3, 2014, U.S. Appl. No. 13/802,383, filed Mar. 13, 2013. |
| First Action Interview Office Action dated May 23, 2014, U.S. Appl. No. 13/802,383, filed Mar. 13, 2013. |
| Notice of Allowance dated Jul. 8, 2014, U.S. Appl. No. 13/802,383, filed Mar. 13, 2013. |
| FAIPP Pre-Interview Communication dated Feb. 12, 2015, U.S. Appl. No. 14/066,661, filed Oct. 29, 2013. |
| Notice of Allowance dated Jul. 6, 2015, U.S. Appl. No. 14/066,661, filed Oct. 29, 2013. |
| Restriction Requirement dated Aug. 14, 2014, U.S. Appl. No. 13/594,777, filed Aug. 25, 2012. |
| Notice of Allowance dated Dec. 3, 2014, U.S. Appl. No. 13/594,777, filed Aug. 25, 2012. |
| Notice of Allowance dated Nov. 9, 2015, U.S. Appl. No. 14/659,614, filed Mar. 17, 2015. |
| FAIPP Pre-Interview Communication dated Jul. 17, 2014, U.S. Appl. No. 13/594,778, filed Aug. 25, 2012. |
| Notice of Allowance dated Sep. 19, 2014, U.S. Appl. No. 13/594,778, filed Aug. 25, 2012. |
| FAIPP Pre-Interview Communication dated Jul. 17, 2014, U.S. Appl. No. 13/594,779, filed Aug. 25, 2012. |
| First Action Interview Office Action dated Dec. 3, 2014, U.S. Appl. No. 13/594,779, filed Aug. 25, 2012. |
| Notice of Allowance dated Aug. 14, 2015, U.S. Appl. No. 13/594,779, filed Aug. 25, 2012. |
| Office Action dated May 5, 2014, U.S. Appl. No. 13/786,450, filed Mar. 5, 2013. |
| Final Office Action dated Nov. 7, 2014, U.S. Appl. No. 13/786,450, filed Mar. 5, 2013. |
| Notice of Allowance dated Feb. 26, 2015, U.S. Appl. No. 13/786,450, filed Mar. 5, 2013. |
| FAIPP Pre-Interview Communication dated Aug. 6, 2014, U.S. Appl. No. 13/831,486, filed Mar. 14, 2013. |
| Notice of Allowance dated Sep. 26, 2014, U.S. Appl. No. 13/831,486, filed Mar. 14, 2013. |
| FAIPP Pre-Interview Communication dated Nov. 7, 2014, U.S. Appl. No. 13/802,404, filed Mar. 13, 2013. |
| First Action Interview Office Action dated Apr. 7, 2015, U.S. Appl. No. 13/802,404, filed Mar. 13, 2013. |
| Final Office Action dated Aug. 27, 2015, U.S. Appl. No. 13/802,404, filed Mar. 13, 2013. |
| Advisory Action dated Nov. 16, 2015, U.S. Appl. No. 13/802,404, filed Mar. 13, 2013. |
| Office Action dated May 17, 2016, U.S. Appl. No. 13/802,404, filed Mar. 13, 2013. |
| Notice of Allowance dated Nov. 18, 2016, U.S. Appl. No. 13/802,404, filed Mar. 13, 2013. |
| FAIPP Pre-Interview Communication dated Dec. 16, 2014, U.S. Appl. No. 13/898,435, filed May 20, 2013. |
| Notice of Allowance dated Feb. 20, 2015, U.S. Appl. No. 13/898,435, filed May 20, 2013. |
| FAIPP Pre-Interview Communication dated Mar. 26, 2015, U.S. Appl. No. 13/939,175, filed Jul. 10, 2013. |
| Notice of Allowance dated Jul. 7, 2015, U.S. Appl. No. 13/939,175, filed Jul. 10, 2013. |
| FAIPP Pre-Interview Communication dated Oct. 29, 2014, U.S. Appl. No. 13/844,282, filed Mar. 15, 2013. |
| Final Office Action dated Mar. 24, 2015, U.S. Appl. No. 13/844,282, filed Mar. 15, 2013. |
| Advisory Action dated Jun. 10, 2015, U.S. Appl. No. 13/844,282, filed Mar. 15, 2013. |
| Office Action dated Aug. 24, 2015, U.S. Appl. No. 13/844,282, filed Mar. 15, 2013. |
| Notice of Allowance dated Feb. 26, 2016, U.S. Appl. No. 13/844,282, filed Mar. 15, 2013. |
| FAIPP Pre-Interview Communication dated Oct. 21, 2014, U.S. Appl. No. 13/844,325, filed Mar. 15, 2013. |
| Notice of Allowance dated Dec. 19, 2014, U.S. Appl. No. 13/844,325, filed Mar. 15, 2013. |
| Notice of Allowance dated Jan. 2, 2015, U.S. Appl. No. 13/831,463, filed Mar. 14, 2013. |
| European Examination Report dated Jun. 1, 2016, EPC Application Serial No. 14775613.4, filed on Jul. 8, 2015. |
| European Examination Report dated Feb. 14, 2017, EPC Application Serial No. 14775613.4, filed on Jul. 8, 2015. |
| European Examination Report dated Sep. 20, 2017, EPC Application Serial No. 14775613.4, filed on Jul. 8, 2015. |
| Japanese Office Action dated Jan. 16, 2018, Japanese Application Serial No. 2-2016-500275, filed on Jun. 25, 2015. |
| FAIPP Pre-Interview Communication dated Mar. 20, 2014, U.S. Appl. No. 13/482,731, filed May 29, 2012. |
| Notice of Allowance dated May 27, 2014, U.S. Appl. No. 13/482,731, filed May 29, 2012. |
| FAIPP Pre-Interview Communication dated Oct. 24, 2012, U.S. Appl. No. 13/463,797, filed May 3, 2012. |
| Notice of Allowance dated Mar. 1, 2013, U.S. Appl. No. 13/463,797, filed May 3, 2012. |
| FAIPP Pre-Interview Communication dated Jun. 12, 2013, U.S. Appl. No. 13/440,980, filed Apr. 5, 2012. |
| Final Office Action dated Sep. 9, 2013, U.S. Appl. No. 13/440,980, filed Apr. 5, 2012. |
| Notice of Allowance dated Nov. 29, 2013, U.S. Appl. No. 13/440,980, filed Apr. 5, 2012. |
| FAIPP Pre-Interview Communication dated Oct. 24, 2012, U.S. Appl. No. 13/463,801, filed May 3, 2012. |
| Notice of Allowance dated Mar. 14, 2013, U.S. Appl. No. 13/463,801, filed on May 3, 2012. |
| FAIPP Pre-Interview Communication dated Jul. 25, 2013, U.S. Appl. No. 13/470,203, filed May 11, 2012. |
| Final Office Action dated Mar. 27, 2014, U.S. Appl. No. 13/470,203, filed May 11, 2012. |
| Advisory Action dated May 29, 2014, U.S. Appl. No. 13/470,203, filed May 11, 2012. |
| Office Action dated Aug. 29, 2014, U.S. Appl. No. 13/470,203, filed May 11, 2012. |
| Notice of Allowance dated Dec. 22, 2014, U.S. Appl. No. 13/470,203, filed May 11, 2012. |
| FAIPP Pre-Interview Communication dated Jul. 2, 2015, U.S. Appl. No. 14/632,850, filed Feb. 26, 2015. |
| Final Office Action dated Nov. 6, 2015, U.S. Appl. No. 14/632,850, filed Feb. 26, 2015. |
| Advisory Action dated Jan. 29, 2016, U.S. Appl. No. 14/632,850, filed Feb. 26, 2015. |
| Examiners Answer dated Nov. 16, 2016, U.S. Appl. No. 14/632,850, filed Feb. 26, 2015. |
| Decision on Appeal dated Sep. 15, 2017, U.S. Appl. No. 14/632,850, filed Feb. 26, 2015. |
| Notice of Allowance dated Oct. 18, 2017, U.S. Appl. No. 14/632,850, filed Feb. 26, 2015. |
| FAIPP Pre-Interview Communication dated May 12, 2014, U.S. Appl. No. 13/294,177, filed Nov. 11, 2011. |
| Notice of Allowance dated Oct. 8, 2014, U.S. Appl. No. 13/294,177, filed Nov. 11, 2011. |
| FAIPP Pre-Interview Communication dated Mar. 25, 2015, U.S. Appl. No. 13/532,588, filed Jun. 25, 2012. |
| FAIPP Office Action Sep. 15, 2015, U.S. Appl. No. 13/532,588, filed Jun. 25, 2012. |
| Notice of Allowance dated Nov. 5, 2015, U.S. Appl. No. 13/532,588, filed Jun. 25, 2012. |
| FAIPP Pre-Interview Communication dated Sep. 25, 2014, U.S. Appl. No. 13/533,969, filed Jun. 27, 2012. |
| Supplemental Notice of Allowance dated Nov. 16, 2015, U.S. Appl. No. 13/532,588, filed Jun. 25, 2012. |
| Notice of Allowance dated Feb. 5, 2015, U.S. Appl. No. 13/533,969, filed Jun. 27, 2012. |
| FAIPP Pre-Interview Communication dated Jun. 6, 2013, U.S. Appl. No. 13/571,348, filed Aug. 10, 2012. |
| Office Action dated Sep. 25, 2013, U.S. Appl. No. 13/571,348, filed Aug. 10, 2012. |
| Final Office Action dated Apr. 10, 2014, U.S. Appl. No. 13/571,348, filed Aug. 10, 2012. |
| Advisory Action dated Jun. 23, 2014, U.S. Appl. No. 13/571,348, filed Aug. 10, 2012. |
| Office Action dated Dec. 15, 2014, U.S. Appl. No. 13/571,348, filed Aug. 10, 2012. |
| Notice of Allowance dated Jun. 17, 2015, U.S. Appl. No. 13/571,348, filed Aug. 10, 2012. |
| FAIPP Pre-Interview Communication dated Mar. 21, 2017, U.S. Appl. No. 14/855,364, filed Sep. 15, 2015. |
| Notice of Allowance dated Jul. 6, 2017, U.S. Appl. No. 14/855,364, filed Sep. 15, 2015. |
| Restriction Requirement dated Jan. 2, 2015, U.S. Appl. No. 13/762,319, filed Feb. 7, 2013. |
| FAIPP Pre-Interview Communication dated Mar. 10, 2015, U.S. Appl. No. 13/762,319, filed Feb. 7, 2013. |
| Notice of Allowance dated Jun. 9, 2015, U.S. Appl. No. 13/762,319, filed Feb. 7, 2013. |
| Notice of Allowance dated Aug. 30, 2013, U.S. Appl. No. 13/540,437, filed Jul. 2, 2012. |
| FAIPP Pre-Interview Communication dated May 21, 2015, U.S. Appl. No. 14/090,667, filed Nov. 26, 2013. |
| Notice of Allowance dated Aug. 4, 2015, U.S. Appl. No. 14/090,667, filed Nov. 26, 2013. |
| Restriction Requirement dated Nov. 1, 2013, U.S. Appl. No. 13/557,213, filed Jul. 25, 2012. |
| Office Action dated Dec. 19, 2013, U.S. Appl. No. 13/557,213, filed Jul. 25, 2012. |
| Notice of Allowance dated Jun. 4, 2014, U.S. Appl. No. 13/557,213, filed Jul. 25, 2012. |
| FAIPP Pre-Interview Communication dated Nov. 27, 2013, U.S. Appl. No. 13/610,856, filed Sep. 11, 2012. |
| Notice of Allowance dated Jan. 31, 2014, U.S. Appl. No. 13/610,856, filed Sep. 11, 2012. |
| FAIPP Pre-Interview Communication dated Jun. 5, 2013, U.S. Appl. No. 13/556,200, filed Jul. 24, 2012. |
| First Action Interview Office Action dated Aug. 19, 2013, U.S. Appl. No. 13/556,200, filed Jul. 24, 2012. |
| Notice of Allowance dated Oct. 16, 2013, U.S. Appl. No. 13/556,200, filed Jul. 24, 2012. |
| Foreign Communication from a Related Counterpart—International Search Report and Written Opinion, dated Dec. 2, 2013, PCT/US13/40673, filed on May 10, 2013. |
| Foreign Communication from a Related Counterpart—International Preliminary Report on Patentability, dated Nov. 20, 2014, PCT/US13/40673, filed on May 10, 2013. |
| Giesecke & Devrient, “The OTA Platform in the World of LTE”, Jan. 2011, http://www.gi-de.com/gd_media/media/en/documents/brochures/mobile_security_2/cste_1/OTA-and-LTE.pdf. |
| Pesonen, Lauri, “Development of Mobile Payment Ecosystem—NFC Based Payment Services”, Aug. 27, 2008. |
| Foreign Communication from a Related Counterpart—International Search Report and Written Opinion, dated Feb. 1, 2014, PCT/US13/47729, filed on Jun. 25, 2013. |
| Foreign Communication from a Related Counterpart—International Preliminary Report on Patentability, dated Jan. 8, 2015, PCT/US13/47729, filed on Jun. 25, 2013. |
| Foreign Communication from a Related Counterpart—International Search Report and Written Opinion, dated Apr. 22, 2014, PCT/US13/53617, filed on Aug. 5, 2013. |
| Foreign Communication from a Related Counterpart—International Preliminary Report on Patentability, dated Feb. 19, 2015, PCT/US13/53617, filed on Aug. 5, 2013. |
| Foreign Communication from a Related Counterpart—International Search Report and Written Opinion, dated Feb. 1, 2014, PCT/US13/51750, filed on Jul. 24, 2013. |
| Foreign Communication from a Related Counterpart—International Preliminary Report on Patentability, dated Feb. 5, 2015, PCT/US13/51750, filed on Jul. 24, 2013. |
| Foreign Communication from a Related Counterpart—International Search Report and Written Opinion, dated Jul. 11, 2014, PCT/US14/16651, filed on Feb. 16, 2014. |
| Foreign Communication from a Related Counterpart—International Preliminary Report on Patentability, dated Sep. 24, 2015, PCT/US14/16651, filed on Feb. 16, 2014. |
| Ahmed, Farid, et al., “Correlation-based Watermarking Method for Imagine Authentication Applications”, Society of Photo-Optical Instrumentation Engineers, Feb. 17, 2004, pp. 1834-1838. |
| Perrig, Adrian, et al., “Spins: Security Protocols for Sensor Networks,” ACM, Sep. 2002, vol. 8, pp. 521-534. |
| Clark, CJ., et al. “Anti-tamper JTAG TAP design enables DRM to JTAG registers and P1687 on-chip instruments”, 2010 IEEE, International Symposium on Hardware-Oriented Security and Trust (HOST). Pub. Date: 2010. Relevant pp. 19-24. http://ieeexplore. ieee. org/stamp/stamp.jsp?tp=&arnumber=5513119. |
| Lee, Jeremy, et al., “A Low-Cost Solution for Protecting IPs Against Scan-Based Side Channel Attacks,” 24th IEEE VLSI Test Symposium. Pub. Date: 2006. http//ieeexplore. ieee. org/stamp/stamp.jsp?tp=&arnumber= 1617569. |
| Henderson, Tristan, et al., “On the Wire, Congestion Pricing: Paying Your Way in Communications Networks,” University College London, Sep./Oct. 2001, retrieved from: http://tristan.host.cs.st-andrews.ac.uk!research/pubs/ieeeic01.pdf. |
| Dietrich, Kurt, et al., “ Implementation Aspects of Mobile and Embedded Trusted Computing,” Institute for Applied Information Processing and Communications, Trusted Computing Interaction Conference, 2009. |
| Eastlake, 3rd Motorola labs T Hansen AT&T Labs D: “US Secure Hash Algorithms,” MPEG Meeting Mar. 16, 2011 to Mar. 23, 2011, Geneva, XP15047395A, ISSN: 0000-0003. |
| Hamdare, Safa, et al., “Securing SMS Based One Time Password Technique from Man in the Middle Attach,” IJETT, vol. 11 Issue 3, May 2014. |
| Twin Connect—“User Guide for Windows”; 30 pages; dated 2013. |
| WiseGEEK,“What is a USB Dongle?,” http://www.wisegeek.com/what-is-a-usb-dongle.htm, four pages, dated Jul. 25, 2017. (53400 FAIPC). |
| McCracken, Billy Gene, Jr., et al. “Mobile Communication Device Profound Identity Brokering Framework”, filed Nov. 30, 2016, U.S. Appl. No. 15/365,934. |
| Paczkowski, Lyle W., et al., “System and Method for Secure USIM Wireless Network Access,” filed Sep. 29, 2017, U.S. Appl. No. 15/719,813. |
| Marquardt, Ronald R., et al., “Data Link Layer Trust Signaling in Communication Network,” filed Jul. 11, 2017, U.S. Appl. No. 15/646,842. |
| Japanese Decision for Grant dated Apr. 3, 2018, Japanese Application Serial No. 2-2016-500275, filed on Jun. 25, 2015. |
| Office Action dated Jun. 11, 2018, U.S. Appl. No. 15/719,813, filed Sep. 29, 2017. |
| Notice of Allowance dated Aug. 15, 2018, U.S. Appl. No. 15/005,123, filed Jan. 25, 2016. |
| Notice of Allowance dated Feb. 6, 2019, U.S. Appl. No. 15/719,813, filed on Sep. 29, 2017 [IDF 11059A (4300-642011]. |
| FAIPP Pre-Interview Communication dated Feb. 11, 2019, U.S. Appl. No. 15/646,842, filed Jul. 11, 2017 [IDF 11637 (4300-71500)]. |
