Patent Grant
9374363
None.
Not applicable.
Not applicable.
A portable electronic device such as a tablet, laptop computer, personal digital assistant (PDA), mobile phone, or multi-functional portable electronic device may comprise a user interface. The user interface may present icons for selection that provide access to local and network applications, data, and systems. The portable electronic device may also comprise audio, video, or other recording technology that a user of the device may be able to access through either the user interface and/or physical components of the device such as volume control, locking features, and power features. Due to the increasing processing power of portable electronic devices, these devices may be used in personal and professional capacities by the device owners.
In an embodiment, a method of protecting information on a hospital network comprising: activating, by an application on a portable electronic device, in response to a first trigger, a hospital persona accessible through a hospital network, wherein the first trigger comprises at least one of a manual or a dynamic trigger, wherein activating the hospital persona comprises deactivating access to an original persona on the portable electronic device. The embodiment further comprising: wherein the hospital persona comprises a first plurality of data, a first plurality of applications, and a plurality of access rights to at least one of the hospital network and a first plurality of software, hardware, and firmware on the portable electronic device; and accessing, by the portable electronic device, a plurality of data associated with the hospital persona, wherein accessing the plurality of data comprises creating or modifying the data. The embodiment further comprising, deactivating, by the application, in response to a second trigger comprising at least one of the manual or the dynamic trigger, at least a portion of the plurality of data associated with the hospital persona, wherein the portion of the plurality of data was one of created or modified while the hospital persona was activating on the portable electronic device, wherein deactivating comprises: determining if the second trigger is the manual trigger or the dynamic trigger; activating, in response to a determination that the second trigger is the manual trigger, at least the portion of the plurality of data to the hospital network; activating, in response to the determination that the second trigger is the dynamic trigger, at least the portion of the plurality of data to a trusted security zone on the portable electronic device; reactivating, in response to the second trigger, the original persona on the portable electronic device.
In an embodiment, a system for protecting access to information on a hospital network comprising: a plurality of personas accessible through a hospital network; a portable electronic device on a telecommunications service provider network comprising an application and an original persona. The embodiment further comprising: wherein the original persona is not a persona of the plurality of the personas on the hospital network, wherein each persona of the plurality of personas on the hospital network comprises a first plurality of data, a first plurality of applications, and a first plurality of access rights to the hospital network and at least one of software, hardware, and firmware on the portable electronic device, and wherein the original persona comprises a second plurality of data, a second plurality of applications, and a second plurality of access rights to at least one of software, hardware, and firmware on the portable electronic device and the telecommunications service provider network. The embodiment further comprising: wherein the application: activates, in response to a first trigger, a first hospital persona of the plurality of personas, wherein the first trigger is one of a manual trigger or a dynamic trigger, and wherein activating the first hospital persona deactivates access to the original persona; deactivates, in response to a second trigger, the first hospital persona and activates a second hospital persona, and wherein the second trigger is one of the manual trigger or the dynamic trigger; and deactivates, in response to a third trigger, the second hospital persona and reactivates the first hospital persona or reactivates the original persona, wherein the third trigger is one of the manual trigger or the dynamic trigger.
In an alternate embodiment, a method of protecting information a network comprising: activating, by the application on a portable electronic device, in response to a trigger, a first persona of a plurality of personas, wherein the trigger comprises at least one of a manual or a dynamic trigger, wherein the portable electronic device comprises an original persona, wherein activating the first persona deactivates access to the original persona, wherein the original persona is not a persona of the plurality of personas, wherein each persona of the plurality of personas and the original persona comprise a first plurality of data, a first plurality of applications, and a first plurality of access rights to the telecommunications service provider network and a plurality of software, hardware, and firmware on the portable electronic device, and wherein the original persona comprises a second plurality of data, a second plurality of applications, and a second plurality of access rights to at least one of software, hardware, and firmware on the portable electronic device and the telecommunications service provider network. The embodiment further comprising: activating, by the application, at least a portion of the first persona to at least one of a remote network and a trusted security zone in response to deactivating the second persona, wherein the remote network is not the network that supports the original persona; and reactivating the original persona on the portable electronic device.
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.
Businesses including hospitals, manufacturing environments, finance centers, and research & development centers may have an interest in protecting confidential data and the systems on which that data is generated and stored. As such, these businesses may want to restrict access that a portable communication device has to confidential data or applications. This may be accomplished by using a remote network where the restriction is based on event triggers generated by the portable communication device. Hospitals in particular may have a variety of confidential information concerning patients and prescription inventory that the hospital may not want accessed by unauthorized individuals and/or under uncontrolled conditions. In some cases, the information that the hospital or other business seeks to protect may be protected by state and/or federal law. For example, the Health Insurance Portability and Accountability Act of 1996 (HIPAA) was enacted to provide federal protections for personal health information and provide patients a plurality of rights associated with those protections. Among other provisions, HIPAA mandates the protection of patient data and appropriate authorization to access that data. Protected data, in some cases, may only be accessed by an authorized party such as an employee or vendor of the hospital or a relative of the patient who has the appropriate access authorization given by a patient or other competent party. Portable electronic devices capable of accessing this sort of information—with or without authorization—may be owned by hospital employees, visitors, patients, and vendors. The hospital or other business may want people, in particular its authorized employees, to be able to access hospital information and resources on portable electronic devices. Portable electronic devices such as tablets, notebooks, mobile phones, laptops, and portable digital assistants (PDA) may be provided by the hospital to all or some of its employees. In that scenario, the hospital may incur the cost of the device, plus the cost of the data, voice, and other support of services used on the device.
One alternative to this arrangement may be that employees, as well as vendors, patients, and visitors, can bring their own devices to the hospital and use those devices to conduct hospital-related business. However, these personal devices may not have adequate protection in order to isolate the hospital's data to prevent accidental or deliberate unauthorized transmission of confidential information by the user or intentional hacking of the device. As such, there remains a need in the art for methods and systems of isolating and protecting a plurality of personas, for example, hospital personas related to different departments or employee roles in the hospital. In another example, a manufacturer may want to protect trade secrets as well as employee and client or vendor records and may use a similar method. For visitors to or employees of a research or manufacturing facility, this may mean that once they enter the facility with their personal portable electronic device, features that could be used to capture and misappropriate information such as audio, video, camera, hard lines into ports, and internet access may be disabled. In an embodiment, this protection of confidential data may be accomplished by having shared devices within a business such as a hospital that are used by employees on different shifts which may reduce the cost of providing devices for the employees to use during their shifts. In an embodiment, even if the hospital provides its own devices and has a policy discouraging or prohibiting the use or presence of personal devices on premises, users may still do just that. In that case, the methods described herein may be used simultaneously, that is, an employee-owned device may have its functionality limited or disabled while in the hospital even if the employee (or patient, visitor, or vendor) is using a hospital-owned device while at work instead of their personal device.
The plurality of protected personas discussed herein may be generated by a business including its employees such as healthcare and IT professionals, or by a third party such as a consulting group. A persona may define access to a plurality of information on a remote network other than the telecommunication service provider's network that supports the device either as a primary provider or as a roaming provider. Each persona of the plurality of hospital personas and the original persona comprises a plurality of data, a plurality of applications, and a plurality of access rights to at least one of software, hardware, and firmware on the portable electronic device and the telecommunications service provider network. For example, an orthopedic surgery persona may comprise data regarding scheduled surgeries, patient post-operative results, patient pre-operative scans and tests, implant inventory, instrument inventory, monitoring inventory, and access to information regarding what other hospital resources both human and machine are scheduled for the scheduled surgeries. In another example, a patient persona in a children's ward may provide access to a plurality of games, electronic coloring books, fiction and non-fiction books, children's programming, and interactive surveys that may be used by clinicians to determine the location and severity of pain and other ailments that someone in a pediatric wing may otherwise have trouble communicating. In an embodiment, this type of diagnostic information may be sent from the patient's device to another device on the hospital network or may be otherwise stored in the patient's file.
In an embodiment, a user of a portable electronic device enters a hospital with their personal device that comprises a personal persona which may also be referred to as an original persona in this embodiment. The original persona may be a persona that is the factory (default) persona or may be a persona that has been modified or created by the user or a third party. The user may be a patient, hospital employee, vendor, visitor, or other party. The personal persona may provide or define access to a plurality of applications as well as access to hardware, software, firmware, and other networks and systems depending upon the type and configuration of the personal device. A hospital persona may be caused to be activated when an application on the portable electronic device receives a first trigger that indicates that the portable electronic device is within a predetermined proximity of a signal. In some embodiments, this activation may also be referred to as the loading of a hospital persona.
In an embodiment, the triggering may be in response to, and the hospital persona session established based on, a time and location limited token associated with the device. This token may be loaded on to the device so that the device can access the hospital's network when the application receives the trigger discussed above. The token may be a permanent access token or a limited access token such as a temporary token. A temporary token may be desired when a visitor or a vendor will be in the hospital for a limited amount of time. For example, if a medical device sales representative is on site to watch a series of surgeries over a period of a few days or a week, a limited-access token may be provided to the device of that sales representative or on a hospital-supported and owned device. In another example, a device user—regardless of whether that device is owned by the user or by the hospital—may only be allowed limited access to a generic hospital persona or a specific hospital persona. In that example, the token on the device used by that limited-access party may be a limited-access token. In some embodiments, the application on the portable electronic device or on the hospital (remote) network may check to see if the token on the device is still active. This check may be done on a periodic or dynamic basis or manually. If the token is determined to be inactive or nonexistent, the device's access to the hospital network may be terminated, for example, by deactivating any active hospital persona.
In an embodiment, the first trigger that activates a hospital persona may be one of a manual log-in or a dynamic process wherein the portable device receives a signal, for example, a Wi-Fi signal that triggers the activation of the hospital persona. In the case of a manual log-in as the first trigger, the log-in may be due to a push that occurs in response to the device sensing a signal or in response to the time and location limited token discussed above. This push may present the user of the device with the option to log into the hospital network, once logged in to the hospital network, even if they are logged in as a generic profile user without access to confidential information, access to the original persona may be restricted while the hospital persona is active.
In an embodiment, this hospital persona may be one of a plurality of hospital personas on a hospital network, which may be a generic hospital persona that is not specific to a department or a department-specific persona. A generic hospital persona may provide information for visitors such as maps, hours, services, a hospital directory, and other non-confidential information. This generic hospital persona may be made optional or mandatory because of concerns that parties who are not employees or vendors of the hospital may witness, capture, and distribute confidential information accidentally or intentionally and without authorization. In an embodiment, the generic hospital persona may also comprise games and reading materials, for example, if the device is intended for use in a children's hospital or other setting where it may be appropriate to provide a device to patients or other visitors who may spend extended periods of time in the hospital. The generic hospital persona may, in some embodiments, allow a user to log-in to other departments, applications, and/or systems on the hospital network. In some embodiments, the generic hospital persona may comprise confidential information and there may be a separate authorization used to access that portion of the generic hospital persona. In an embodiment, the first hospital persona may be activated on a device because of a token or agent that is pre-loaded on to the device, or the first hospital persona may be activated to every device that either logs in or receives a signal as described above. This activation may be an automatic switching to the hospital persona or may be received as a prompt for the device user to log in to the hospital persona. This may be because the hospital does not want to have devices on its premises that have active access to camera, audio, internet, or other features that may compromise—intentionally or unintentionally—patient or other confidentiality or that may distract other patients and employees in the hospital or interfere with hospital equipment or overall operations.
Activating this first hospital persona, regardless of whether it is generic or department-specific, restricts access to the personal (original) persona and all hardware, firmware, and software accessible while the personal persona is active. This restriction may also be referred to as partially or completely blocking access to different features that are accessible when the first persona is active. This may mean that features such as camera, audio, the web gateway, and other software, hardware, and firmware that could be used to capture and/or transmit confidential information in an unauthorized manner are disabled. In some embodiments, the first hospital persona may provide access to patient information, surgery schedules, outpatient schedules, and the ability to further log in or otherwise request information from systems and applications accessed through the generic hospital persona. While the first hospital persona is activated on the device, the user may create, delete, or otherwise modify data on the hospital's network that can be accessed from the hospital persona which cannot be accessed when the personal (original) persona is enabled. The first hospital persona may remain active on the portable device until it is unloaded in response to a second trigger. The second trigger may comprise a manual log out by the user, or may be based upon the portable device no longer receiving a signal, for example, the Wi-Fi signal that led to activating the first hospital persona. The signal may no longer be received, in one example, because that device has moved out of a location or out of a predetermined proximity of a location where the signal is available. In one example, a portable electronic device may have the first hospital persona activated in response to a first dynamic trigger and may be able to access this first hospital persona within the physical boundaries of the hospital, i.e. within the walls of the hospital. The device may also be able to access the first hospital persona in courtyards of the hospital, in restaurants or shops adjacent to and/or affiliated with the hospital, and in the parking lot or lots associated with or within a predetermined radius and/or perimeter around the hospital which may be referred to as the predetermined area. However, once the device leaves this area, the first hospital persona would be deactivated as discussed below.
Once the user either logs out manually or leaves the predetermined area of the first trigger, the second trigger may remove the generic hospital persona and restore access to the personal persona. Restoring access to the personal persona, which may also be referred to as reactivating the personal persona, may also restore access to restricted hardware, software, and firmware including web browsers, cameras, audio, other physical ports and sensors, infrared, Bluetooth®, etc. Prior to the portable electronic device receiving the second trigger, while the first hospital persona is activated on the device, a plurality of data on the hospital network and accessed applications and systems associated with the first hospital persona may be created, deleted, or otherwise modified. The data that may be created and or modified may concern patient records, machine maintenance, and medical supplies and delivery schedules. The plurality of data may be uploaded dynamically, at predetermined intervals, or manually to a server on the hospital network. It may be preferable to capture any created or modified data prior to deactivating the persona under which the data was accessed/created/modified. A portion of data that is accessed/created/modified while a particular hospital persona is active may be temporarily stored in the trusted security zone. For example, a device is used during a twelve-hour shift where a number of patients are treated. If the data that is accessed, modified, or created is uploaded and the respective access to that data logged, every thirty minutes, some of the data may not be uploaded to the hospital network before the shift ends. In that example, the data would remain in the trusted security zone on the device until any hospital persona is loaded at which point the data is uploaded to the hospital network. Alternatively, the data may be accessed by an authorized party, for example, in IT at the hospital. In an embodiment, if the first hospital persona is logged out manually, any modifications made may be uploaded to a server on the hospital network. In an alternate embodiment, if the first hospital persona is deactivated because the signal that triggered the activation of the first hospital persona is no longer received by the portable electronic device, the modified data may be loaded to a trusted security zone on the device that may not be accessed when the personal persona is loaded.
A trusted security zone provides chipsets with a hardware root of trust and a secure execution environment for applications, and secures 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. For more details on establishing trusted end-to-end communication links relying on hardware assisted security, 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. 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. 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.
In that embodiment, wherein a trusted security zone is used, the information created and/or modified may remain on the device until the first hospital persona, or any hospital persona from the plurality of hospital personas, is reactivated, at which point it may be automatically loaded to the server on the hospital network. Alternatively, an IT professional from the hospital may access the information on the device and upload it manually to the server. In another embodiment, if the first hospital persona is logged out because the signal that triggered activation of the first hospital persona is no longer received by the operating system or application on the device, a portion of the data modified while the first hospital persona was activated may have been dynamically or manually uploaded to the server on the hospital network, and a portion of the data modified may be stored in the trusted security zone on the device. Information stored in the trusted security zone may be uploaded to the hospital's network automatically the next time that the portable electronic device has a hospital persona activated, regardless of whether the hospital persona activated is the same as the first hospital persona.
In an alternate embodiment, a user may begin with a device owned and/or maintained by the hospital. This portable electronic device may be assigned to a particular party, employee role, department, or may be for general use as needed by employees and visitors. The portable electronic device may comprise a generic hospital persona which also may be referred to as the original persona. Upon entering a department, for example, the cosmetic surgery department, a first trigger that may be a manual log-on or a dynamic trigger as discussed above may activate the cosmetic surgery persona on the device and access to the generic hospital persona may be restricted. If the portable electronic device then migrates to another department, for example, orthopedics, the cosmetic surgery persona may be unloaded and an orthopedics persona, that is also a persona of the plurality of hospital personas, may be activated in response to a second trigger that may be similar to the first trigger discussed above. A device may migrate because an employee, vendor, or other visitor is physically located in another department, or because the device is re-appropriated to a new department.
In an embodiment, the orthopedics persona may provide access to a plurality of applications and other systems access that may overlap in part with the cosmetic surgery persona, or the accessible areas may be completely different from those associated with the cosmetic surgery persona. The data modified during the period when either the cosmetic surgery persona or the orthopedics persona is activated may be stored in a trusted security zone or on the hospital network in a fashion similar to what is described above and may be dependent upon how the persona is deactivated. In an embodiment, when the orthopedics persona is deactivated in response to one of a manual or an automatic trigger, either the cosmetic surgery persona or the generic hospital persona may be activated and/or have access restored. When a persona is restored, access is restored to the applications, systems, and data on the hospital network, and data stored in the trusted security zone on the portable electronic device that may not have been uploaded when the previous hospital persona was active may be uploaded to the hospital network without user interaction or awareness.
In an embodiment, confidential or sensitive data that is accessed, created, or modified while the persona 108 is active may be stored on the mobile device 106 temporarily. This access, as well as the storage, may be done according to a plurality of rules and/or policies 108b as well as logic 108c associated with the persona 108. The plurality of rules and/or policies 108b and logic 108c may comprise information about what information may be accessed, how it may be accessed, if/how it may be modified, and when this access and/or modification can occur. The mobile device 106 may comprise an application 124 and be configured in a manner similar to what is described below with respect to
A network 120 may be the network of a telecommunications service provider that provides voice and/or data services to the mobile device 106. The network 120 may comprise one or more public communication networks, one or more private networks, and/or a combination thereof. The system may further comprise a base transceiver station (BTS) 102 in communication with the wireless network 120 in communication that is also in communication with a wireless access point 104. The network 120 may also be in communication with a server computer 122 and a data store 112. A remote network 114, for example, a hospital's network, may not be in communication with the network 120 but may communicate with the mobile device 106 to activate and deactivate a plurality of virtual machines that may be similar to virtual machine 110. Alternatively, the network 114 may be communicatively coupled to the remote network 120, via security gateways in the remote network 114 that restrict communication traffic both into and out of the remote network 114. The remote network 114 may comprise a wireless network access node 116 and a data store 118. The data store 118 may comprise a plurality of personas, for example, hospital personas. Each hospital persona may be associated with at least one of a hospital department, a role within a hospital, or a combination of department and role. The hospital departments may comprise an emergency department, radiology, cosmetic surgery, orthopedics, dermatology, pediatrics, purchasing, receiving, maintenance and facilities, administration, which may also be a role, as well as other departments such as surgical, operating room, post-operative, intensive care, neo-natal, neo-natal intensive care, ambulatory, triage, neurosurgery, neuroscience, and combinations thereof. The hospital roles may comprise doctors, medical students, interns, residents, fellows, support staff, nursing, physician's assistants, administrative staff, board, chief-level employees, and other roles as appropriate that may be part time, full time, contract-based, or volunteer.
The persona(s) activated on a user's device may depend on the location of the device within the hospital, the role of the user and/or of the device in the hospital, or combinations thereof. For example, the information seen by a doctor in an operating room or theater may not be the same information seen by a vendor who is in the operating room to watch a surgery even though both devices in the possession of the doctor and the vendor have activated an operating room persona. Activation of the hospital persona may be accomplished by a log-in, or, in some embodiments, by an association of a device identifier with a role of the owner or user of that device by the hospital network. In some embodiments, the remote network 114 may connect to the telecommunication service provider's network 120 by a secure connection comprising firewalls and other protections to prevent unauthorized access to confidential and other protected hospital information. In some embodiments, these protections may restrict or disable the ability of a user to send data out from remote network 114 to the telecommunications service provider's network 120 and may, conversely, prevent receiving data sent from the network 120 when the persona 108 in communication with the remote network 114 is active on the mobile device 106.
In an embodiment, the mobile device 106 also comprises an operating system (not pictured) and is owned and/or used by an individual user visiting the hospital. The individual user may be a doctor, nurse, patient, visitor, vendor, support staff, or administrator. The application 124 on the mobile device 106 may receive a signal from the wireless access point 104 upon coming within a pre-determined proximity of the hospital, or may log-in to the hospital network manually with the proper authorization. Either event may be referred to as a first trigger, and may cause a persona 108 to activate on the mobile device 106. The other persona 108 may comprise access to a plurality of systems and applications on the remote network 114 which may store data, including confidential data, in a data store 112. This data may be accessed, modified, created, or deleted while the other persona 108 is activated on the mobile device 106. In addition to providing access to confidential data on the hospital network, activating the persona 108 on the mobile device 106 may restrict access to applications, systems, hardware, firmware, and other software on the mobile device 106 that could be accessed while the an original persona (not pictured) was activated.
In an embodiment, when access is restricted or disabled, the user of the device may not be able to access the telecommunications service provider's network 120. In addition, access to applications, systems, and physical ports of the mobile device 106 may be limited. In one example, the camera function may be restricted, but the audio port may remain active when the other persona 108 is active and the personal persona is deactivated. Thus, original persona is deactivated while the other persona 108 is activated on the device. The data from the data store 112 that is used, created, and/or modified while the persona 108 is activated on the mobile device 106 may be stored on the remote network 114 or in a trusted security zone (not pictured) on the mobile device 106 or on a combination of both. In one example, the data associated with the other persona 108 that is used, created, modified, or otherwise accessed while the other persona 108 is activated on the mobile device 106 is backed up and/or loaded on the remote network 114. This upload may occur dynamically, manually, or in response to a predetermined amount of time passing, a predetermined amount of data being accessed or modified, or by a combination of methods. If a user manually logs out of the hospital persona 108, all of the data may be uploaded to the remote network 114.
If a user is logged out of the persona 108 because of a trigger wherein the wireless signal for the persona is no longer received by the mobile device 106, a portion of the data may be stored in a trusted security zone on the mobile device 106. This portion of the data may be uploaded automatically the next time the persona 108, or any persona of the plurality of personas of the remote network 114, is activated on the mobile device 106, or may be manually uploaded by an IT administrator of the hospital if the device is given to the IT administrator or another party authorized to transfer data to the remote network 114. When the persona 108 is unloaded, whether by manual or automatic trigger, the private persona may be restored to the mobile device 106 which may reestablish access to the applications, systems, hardware, software, and firmware associated with the private persona on the mobile device 106. In an alternate embodiment, the mobile device 106 may be owned by the hospital, and the private persona may be a generic hospital profile. This embodiment is discussed below in
Access records that reflect the date and time that various records were viewed and/or modified in addition to the device that accessed the data may also be stored on the remote network 114 in addition to any data created or modified while a hospital persona is active based on in-house policies or governing law. The access records and data created or modified may be saved dynamically, by manual trigger, based on a predetermined amount of data being modified or accessed, or based on a predetermined amount of time spent in the hospital personal, or combinations thereof. At block 208, the first hospital persona is deactivated in response to a second trigger comprising at least one of a manual trigger at block 212 or a dynamic trigger at block 210. The manual trigger 212 may be, for example, logging out of the first hospital persona, or a Bluetooth® or other trigger wherein the device is passed over a signal source upon exiting the hospital. The dynamic trigger 210 may be, for example, the device no longer receiving the wireless signal that triggered the loading of the first hospital persona at block 202. In another embodiment, a GPS signal may be received by the device to activate the first hospital persona at block 202.
In an embodiment, if the manual trigger 212 is used, the data that was modified/created during the time the hospital persona was activated on the device may be saved to the remote network at block 206. If the first hospital persona is deactivated at block 208 by the dynamic trigger 210, a portion of the data that was modified/accessed may have been saved to the remote hospital network at block 206, and a portion of the data may be saved to a trusted security zone on the device at block 214. This trusted security zone may be accessed by the hospital network the next time the hospital persona is activated on that device so that the accessed/modified data can be uploaded to the network. Alternatively, a hospital employee with appropriate credentials may manually unload the information from the device. At block 216, subsequent to the first hospital persona being deactivated at block 208, regardless of how the deactivation is triggered, access to the original persona may be restored. Restoring access to the original persona at block 216 may comprise restoring access to applications, applets, audio functions, camera and video functions, as well as physical ports. A business such as a hospital may want to disable access to these types of functions because they do not want hospital records or pictures of patients or other information being copied and distributed.
The DSP 502 or some other form of controller or central processing unit operates to control the various components of the mobile device 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 mobile device 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 mobile device 400 to communicate wirelessly with other nearby handsets and/or wireless base stations.
The keypad 528 couples to the DSP 502 via the interface 518 to provide one mechanism for the user to make selections, enter information, and otherwise provide input to the mobile device 400. Another input mechanism may be the touch screen LCD 530, which may also display text and/or graphics to the user. The touch screen LCD controller 532 couples the DSP 502 to the touch screen LCD 530. The GPS receiver 538 is coupled to the DSP 502 to decode global positioning system signals, thereby enabling the mobile device 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.
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 such as code division multiple access (CDMA), global system for mobile communications (GSM), long-term evolution (LTE), worldwide interoperability for microwave access (WiMAX), 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), 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 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 |
| 6131024 | Boltz | Oct 2000 | A |
| 6177860 | Cromer et al. | Jan 2001 | B1 |
| 6219712 | Mann et al. | Apr 2001 | B1 |
| 6363150 | Bhagavath et al. | Mar 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 |
| 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 |
| 7043241 | Sladek et al. | May 2006 | B1 |
| 7069234 | Cornelius et al. | Jun 2006 | B1 |
| 7366806 | Milenkovic et al. | Apr 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 |
| 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 |
| 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 |
| 8316237 | Felsher et al. | Nov 2012 | B1 |
| 8331337 | Kambe 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 |
| 8443420 | Brown et al. | May 2013 | B2 |
| 8447983 | Beck et al. | May 2013 | B1 |
| 8494576 | Bye et al. | Jul 2013 | B1 |
| 8504097 | Cope | Aug 2013 | B1 |
| 8583091 | Delker et al. | Nov 2013 | B1 |
| 8588749 | Sadhvani et al. | Nov 2013 | B1 |
| 8631247 | O'Loughlin 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 |
| 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 |
| 8737965 | McCown et al. | May 2014 | B2 |
| 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 |
| 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 |
| 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 |
| 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 |
| 9268959 | Paczkowski et al. | Feb 2016 | B2 |
| 9271110 | Fultz et al. | Feb 2016 | B1 |
| 9282898 | McRoberts et al. | Mar 2016 | B2 |
| 20010041591 | Carroll | Nov 2001 | 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, Jr. | 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 |
| 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 |
| 20030216143 | Roese et al. | Nov 2003 | A1 |
| 20030229514 | Brown | Dec 2003 | A2 |
| 20030237002 | Oishi et al. | Dec 2003 | A1 |
| 20040064351 | Mikurak | Apr 2004 | A1 |
| 20040158840 | Rothman et al. | Aug 2004 | A1 |
| 20040202328 | Hara | Oct 2004 | A1 |
| 20040233844 | Yu et al. | Nov 2004 | A1 |
| 20040234049 | Melideo | Nov 2004 | A1 |
| 20040243810 | Ringborg et al. | Dec 2004 | A1 |
| 20040264372 | Huang | Dec 2004 | A1 |
| 20050015601 | Tabi | Jan 2005 | A1 |
| 20050045719 | Yang | Mar 2005 | A1 |
| 20050052994 | Lee | Mar 2005 | A1 |
| 20050091505 | Riley et al. | Apr 2005 | A1 |
| 20050123596 | Kohane et al. | Jun 2005 | A1 |
| 20050125396 | Liu | Jun 2005 | A1 |
| 20050138433 | Linetsky | Jun 2005 | A1 |
| 20050181796 | Kumar et al. | Aug 2005 | A1 |
| 20050228892 | Riley et al. | Oct 2005 | A1 |
| 20050235166 | England et al. | Oct 2005 | A1 |
| 20050239481 | Seligmann | Oct 2005 | A1 |
| 20050272445 | Zellner | Dec 2005 | A1 |
| 20050289355 | Kitariev et al. | Dec 2005 | A1 |
| 20060030291 | Dawson et al. | Feb 2006 | A1 |
| 20060036851 | DeTreville | Feb 2006 | A1 |
| 20060040641 | Dawson et al. | Feb 2006 | A1 |
| 20060074544 | Morariu et al. | Apr 2006 | A1 |
| 20060129488 | Vincent | Jun 2006 | A1 |
| 20060156026 | Utin | 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 |
| 20060212589 | Hayer et al. | Sep 2006 | A1 |
| 20060212853 | Sutardja | Sep 2006 | A1 |
| 20060224901 | Lowe | 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 |
| 20070011061 | East | Jan 2007 | A1 |
| 20070038648 | Chetwood et al. | Feb 2007 | A1 |
| 20070061535 | Xu et al. | Mar 2007 | A1 |
| 20070078988 | Miloushev et al. | Apr 2007 | A1 |
| 20070079120 | Bade et al. | Apr 2007 | A1 |
| 20070094273 | Fritsch et al. | Apr 2007 | A1 |
| 20070094691 | Gazdzinski | Apr 2007 | A1 |
| 20070104215 | Wang et al. | May 2007 | A1 |
| 20070118880 | Mauro, II | May 2007 | A1 |
| 20070143210 | Yeung et al. | Jun 2007 | A1 |
| 20070150730 | Conti | Jun 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 |
| 20070197261 | Humbel | Aug 2007 | A1 |
| 20070214332 | Sonoda et al. | Sep 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 |
| 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 |
| 20080051142 | Calvet et al. | Feb 2008 | A1 |
| 20080092213 | Wei et al. | Apr 2008 | A1 |
| 20080097793 | Dicks et al. | Apr 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 |
| 20080162361 | Sklovsky | 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 |
| 20090047923 | Jain et al. | Feb 2009 | A1 |
| 20090049220 | Conti | 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 |
| 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 | Aug 2009 | A1 |
| 20090227290 | Chien | Sep 2009 | A1 |
| 20090248445 | Harnick | Oct 2009 | A1 |
| 20090271321 | Stafford | Oct 2009 | A1 |
| 20090281947 | Erel | Nov 2009 | A1 |
| 20090300599 | Piotrowski | Dec 2009 | A1 |
| 20090312011 | Huomo et al. | Dec 2009 | A1 |
| 20090320028 | Gellerich et al. | Dec 2009 | A1 |
| 20100031325 | Maigne et al. | Feb 2010 | A1 |
| 20100052844 | Wesby | Mar 2010 | A1 |
| 20100075669 | Sparks et al. | Mar 2010 | A1 |
| 20100077487 | Travis et al. | Mar 2010 | A1 |
| 20100082977 | Boyle et al. | Apr 2010 | A1 |
| 20100125512 | Jones et al. | May 2010 | A1 |
| 20100125904 | Nice 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 |
| 20100153721 | Mellqvist | Jun 2010 | A1 |
| 20100162028 | Frank et al. | Jun 2010 | A1 |
| 20100190469 | Vanderveen et al. | 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 |
| 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 |
| 20110082711 | Poeze et al. | Apr 2011 | A1 |
| 20110107426 | Yen et al. | May 2011 | A1 |
| 20110112968 | Floreck 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, II | 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 |
| 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 |
| 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 |
| 20120083242 | Spitz | 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 | 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 |
| 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 |
| 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 |
| 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 |
| 20130252583 | Brown et al. | Sep 2013 | A1 |
| 20130262264 | Karstoft | Oct 2013 | A1 |
| 20130263212 | Faltyn et al. | Oct 2013 | A1 |
| 20130290709 | Muppidi et al. | Oct 2013 | A1 |
| 20130305333 | Katzer et al. | Nov 2013 | A1 |
| 20130310003 | Sadhvani Rita et al. | Nov 2013 | A1 |
| 20130331067 | Coussemaeker et al. | Dec 2013 | A1 |
| 20130332456 | Arkin | Dec 2013 | A1 |
| 20130343181 | Stroud et al. | Dec 2013 | A1 |
| 20130345530 | McRoberts 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 | Jan 2014 | A1 |
| 20140033316 | Paczkowski et al. | Jan 2014 | A1 |
| 20140047548 | Bye 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 | O'Connor 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 |
| 20140155025 | Parker et al. | Jun 2014 | A1 |
| 20140173747 | Govindaraju | Jun 2014 | A1 |
| 20140188412 | Mahajan et al. | Jul 2014 | A1 |
| 20140188738 | Huxham | Jul 2014 | A1 |
| 20140215196 | Berlin | Jul 2014 | A1 |
| 20140245444 | Lutas et al. | Aug 2014 | A1 |
| 20140254381 | Racz et al. | Sep 2014 | A1 |
| 20140267332 | Chhabra et al. | Sep 2014 | A1 |
| 20140279558 | Kadi et al. | Sep 2014 | A1 |
| 20140281544 | Paczkowski et al. | Sep 2014 | A1 |
| 20140298026 | Isozaki et al. | Oct 2014 | A1 |
| 20150106805 | Melander et al. | Apr 2015 | A1 |
| 20150169885 | Paczkowski et al. | Jun 2015 | A1 |
| 20150172928 | Katzer et al. | Jun 2015 | A1 |
| 20160004876 | Bye et al. | Jan 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| WO2011025433 | Mar 2011 | WO |
| WO2012064171 | May 2012 | WO |
| 2013170228 | Nov 2013 | WO |
| 2014004590 | Jan 2014 | WO |
| 2014018575 | Jan 2014 | WO |
| 2014025687 | Feb 2014 | WO |
| WO2014158431 | Oct 2014 | WO |
| Entry |
|---|
| Trusted Computing Second International Conference, Trust 2009 “Implementation Aspects of Mobile and Embedded Trusted Computing” Kurt Dietrich and Johannes Winter. |
| Advisory Action dated Jun. 23, 2014, U.S. Appl. No. 13/571,348, filed Aug. 10, 2012. |
| Notice of Allowance dated Jun. 4, 2014, U.S. Appl. No. 13/557,213, filed Jul. 25, 2012. |
| FAIPP Pre-Interview Communication dated Aug. 4, 2014, U.S. Appl. No. 13/844,357, filed Mar. 15, 2013. |
| Notice of Allowance dated Jul. 8, 2014, U.S. Appl. No. 13/802,383, filed Mar. 13, 2013. |
| Restriction Requirement dated Aug. 14, 2014, U.S. Appl. No. 13/594,777, filed Aug. 25, 2012. |
| FAIPP Pre-Interview Communication dated Jul. 17, 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. |
| Office Action dated May 5, 2014, 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. |
| Ahmed, Farid, et al., “Correlation-based Watermarking Method for Imagine Authentication Applications”, Society of Photo-Optical Instrumentation Engineers, Feb. 17, 2004, pp. 1834-1838. |
| Foreign Communication from a Related Counterpart—International Search Report and Written Opinion, dated Jul. 11, 2014, PCT/US14/16651, filed on Feb. 16, 2014. |
| Kunkel, Philip M., et al., “Secure Peer-to-Peer Call Forking Facilitated by Trusted 3rd Party Voice Server Provisioning”, filed Oct. 29, 2013, U.S. Appl. No. 14/066,661. |
| Bertz, Lyle T., et al., “Framework for Real-Time Brokering of Digital Content Delivery,” filed Aug. 25, 2012, U.S. Appl. No. 13/594,777. |
| Bertz, Lyle T., et al.,“Reservations in Real-Time Brokering of Digital Content Delivery,” filed Aug. 25, 2012, U.S. Appl. No. 13/594,778. |
| Bertz, Lyle T., et al., “File Retrieval in Real-Time Brokering of Digital Content Delivery,” filed Aug. 25, 2012, U.S. Appl. No. 13/594,779. |
| Paczkowski, Lyle W., et al., “Trusted Security Zone Watermark”, filed Mar. 5, 2013, U.S. Appl. 13/786,450. |
| Paczkowski, Lyle W., et al., “Trusted Processing Location Within a Graphics Processing Unit”, filed Jul. 10, 2013, U.S. Appl. No. 13/939,175. |
| McCracken, Billy Gene, Jr., et al. “Mobile Communication Device Profound Identity Brokering Framework”, filed Jun. 6, 2013, U.S. Appl. No. 13/912,190. |
| Urbanek, Robert E., Subscriber Identity Module Virtualization:, filed Nov. 20, 2013, U.S. Appl. No. 14/085,474. |
| Krieger, Michael D., et al., “Billing Varied Service Based on Tier”, filed Nov. 8, 2013, U.S. Appl. No. 14/075,663. |
| Paczkowski, Lyle W., et al., “Trusted Display and Transmission of Digital Ticket Documentation”, filed Jan. 24, 2014, U.S. Appl. No. 14/163,047. |
| Loman, Clint H., et al., “Verification of Mobile Device Integrity During Activation”, filed Mar. 28, 2014, U.S. Appl. No. 14/229,532. |
| Paczkowski, Lyle W., et al., “Network Based Temporary Trust Extension to a Remote or Mobile Device Enabled via Specialized Cloud Services”, filed Jul. 29, 2014, U.S. Appl. No. 14/446,330. |
| Cordes, Kevin R., et al., “Digest of Biographical Information for an Electronic Device with Static and Dynamic Portions”, filed Apr. 4, 2013, U.S. Appl. No. 13/857,141. |
| Cordes, Kevin R., et al., “Radio Frequency Identity (RFID) Chip Electrically and Communicatively Coupled to Motherboard of Mobile Communication Device”, filed Apr. 4, 2013, U.S. Appl. No. 13/857,139. |
| Cordes, Kevin R., et al., “System for Managing a Digest of Biographical Information Stored in a Radio Frequency Identity Chip Coupled to a Mobile Communication Device”, filed Apr. 4, 2013, U.S. Appl. No. 13/857,138. |
| Final Office Action dated Sep. 9, 2013, U.S. Appl. No. 13/440,980, filed Apr. 5, 2012. |
| Office Action dated Sep. 25, 2013, U.S. Appl. No. 13/571,348, filed Aug. 10, 2012. |
| Notice of Allowance dated Aug. 30, 2013; U.S. Appl. No. 13/540,437, filed Jul. 2, 2012. |
| Restriction Requirement dated Nov. 1, 2013, U.S. Appl. No. 13/557,213, filed Jul. 25, 2012. |
| Notice of Allowance dated Oct. 16, 2013, U.S. Appl. No. 13/556,200, filed Jul. 24, 2012. |
| Notice of Allowance dated May 27, 2014, U.S. Appl. No. 13/482,731, filed May 29, 2012. |
| Advisory Action dated May 29, 2014, U.S. Appl. No. 13/470,203, filed May 11, 2012. |
| FAIPP Pre-Interview Communication dated May 12, U.S. Appl. No. 13/294,177, filed Nov. 11, 2011. |
| Final Office Action dated Apr. 10, 2014, U.S. Appl. No. 13/571,348, filed Aug. 10, 2012. |
| 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. |
| Foreign Communication from a Related Counterpart—International Search Report and Written Opinion, dated Apr. 22, 2014, PCT/US13/53617, filed Aug. 5, 2013. |
| 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. |
| 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 May 3, 2012. |
| FAIPP Pre-Interview Communication dated Jul. 25, 2013, U.S. Appl. No. 13/470,203, filed May 11, 2012. |
| FAIPP Pre-Interview Communication dated Jun. 6, 2013, U.S. Appl. No. 13/571,348, filed Aug. 10, 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. |
| First Action Interview 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. |
| Cope, Warren B., et al., “Electronic Purchase Transaction Trust Infrastructure”, filed May 29, 2012, U.S. Appl. No. 13/482,731. |
| Cope, Warren B., et al., “Alternative hardware and Software Configuration for Near Field Communication”, filed May 4, 2012, U.S. Appl. No. 13/463,797. |
| Cope, Warren B., et al., “Multiple Secure Elements in Mobile Electronic Device with Near Field Communication Capability”, filed Apr. 5, 2012, U.S. Appl. No. 13/440,980. |
| Bye, Stephen James, et al., “Near Field Communication Authentication and Validation to Access Corporate Data”, filed May 3, 2012, U.S. Appl. No. 13/463,801. |
| Katzer, Robin D., et al., “Web Server Bypass of Backend Process on Near Field Communications and Secure Elements Chips”, filed May 11, 2012, U.S. Appl. No. 13/470,203. |
| Katzer, Robin D., et al., “Web Server Bypass of Backend Process on Near Field Communications and Secure Elements Chips”, filed May 10, 2013, PCT Application No. PCT/US13/40673. |
| Katzer, Robin D., et al., “Secure Placement of Centralized Media Controller Application in Mobile Access Terminal”, filed Nov. 11, 2011, U.S. Appl. No. 13/294,177. |
| McRoberts, Leo Michael, et al., “End-to-End Trusted Communications Infrastructure”, filed Jun. 25, 2012, U.S. Appl. No. 13/532,588. |
| McRoberts, Leo Michael, et al., “End-to-End Trusted Communications Infrastructure”, filed on Jun. 25, 2013, PCT Serial No. PCT/US13/47729. |
| Paczkowski, Lyle W., et al., “Trusted Policy and Charging Enforcement Function”, filed Jun. 27, 2012, U.S. Appl. No. 13/533,969. |
| Bye, Stephen James, et al., “Systems and Methods for Provisioning and Using Multiple Trusted Security Zones on an Electronic Device”, filed Aug. 10, 2012, U.S. Appl. No. 13/571,348. |
| Bye, Stephen James, et al., “Systems and Methods for Provisioning and Using Multiple Trusted Security Zones on an Electronic Device”, filed on Aug. 5, 2013, PCT Serial No. PCT/US13/53617. |
| Bye, Stephen James, et al., “Trusted Signaling in Long Term Evolution (LTE) 4G Wireless Communication”, filed Feb. 7, 2013, U.S. Appl. No. 13/762,319. |
| Cope, Warren B., et al., “Extended Trusted Security Zone Radio Modem”, filed Jul. 2, 2012, U.S. Appl. No. 13/540,437. |
| Katzer, Robin D., et al., “Trusted Access to Third Party Applications Systems and Methods”, filed Jul. 25, 2012, U.S. Appl. No. 13/557,213. |
| Paczkowski, Lyle W., et al., “System and Methods for Trusted Internet Domain Networking”, filed Sep. 11, 2012, U.S. Appl. No. 13/610,856. |
| Paczkowski, Lyle W., et al., “Trusted Security Zone Access to Peripheral Devices”, filed Jul. 24, 2012, U.S. Appl. No. 13/556,200. |
| Paczkowski, Lyle W., et al., “Trusted Security Zone Access to Peripheral Devices”, filed Jul. 24, 2013, PCT Application No. PCT/US13/51750. |
| Paczkowski, Lyle W., et al., Enablement of a Trusted Security Zone Authentication for Remote Mobile Device Management Systems and Methods, filed Mar. 15, 2013, U.S. Appl. No. 13/844,357. |
| Paczkowski, Lyle W., et al., “Trusted Security Zone Communication Addressing on an Electronic Device”, filed Mar. 15, 2013, U.S. Appl. No. 13/844,145. |
| Bye, Stephen James, et al., “Protection for Multimedia Files Pre-Downloaded to a Mobile Device”, filed Apr. 15, 2013, U.S. Appl. No. 13/863,376. |
| Paczkowski, Lyle W., et al., “Point-of-Sale and Automated Teller Machine Transactions Using Trusted Mobile Access Device”, filed Mar. 13, 2013, U.S. Appl. No. 13/802,383. |
| Paczkowski, Lyle W., et al., “Trusted Security Zone Re-Provisioning and Re-Use Capability for Refurbished Mobile Devices”, filed Mar. 14, 2013, U.S. Appl. No. 13/831,486. |
| Paczkowski, Lyle W., et al., “Trusted Security Zone Enhanced with Trusted Hardware Drivers”, filed Mar. 13, 2013, U.S. Appl. No. 13/802,404. |
| Paczkowski, Lyle W., et al., “JTAG Fuse Vulnerability Determination and Protection Using a Trusted Execution Environment”, filed Mar. 15, 2013, U.S. Appl. No. 13/844,325. |
| Paczkowski, Lyle W., et al., “Trusted Security Zone Containers for the Protection and Confidentiality of Trusted Service Manager Data”, filed Mar. 14, 2013, U.S. Appl. No. 13/831,463. |
| Bye, Stephen James, et al., “Delivering Digital Content to a Mobile Device via a Digital Rights Clearing House”, filed Apr. 10, 2013, U.S. Appl. No. 13/860,338. |
| Paczkowski, Lyle W., et al., “Method for Enabling Hardware Assisted Operating System Region for Safe Execution of Untrusted Code Using Trusted Transitional Memory”, filed May 20, 2013, U.S. Appl. No. 13/898,435. |
| Paczkowski, Lyle W., et al., “Verifying Applications Using a Trusted Security Zone”, filed Aug. 12, 2013, U.S. Appl. No. 13/964,112. |
| Paczkowski, Lyle W., et al., “Mobile Access Terminal with Local Call Session Control Function”, filed Jun. 18, 2009, U.S. Appl. No. 12/486,873. |
| 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 Nov. 29, 2013, U.S. Appl. No. 13/440,980, filed Apr. 5, 2012. |
| Office Action dated Dec. 19, 2013, 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 date Jan. 31, 2014, U.S. Appl. No. 13/610,856, filed Sep. 11, 2012. |
| Cope, Warren B., et al., “Extended Trusted Security Zone Radio Modem”, filed Nov. 26, 2013, U.S. Appl. No. 14/090,667. |
| Paczkowski, Lyle W., et al., “Trusted Security Zone Containers for the Protection and Confidentiality of Trusted Service Manager Data”, filed Feb. 16, 2014, PCT Application No. PCT/US14/16651. |
| Foreign Communication from a Related Counterpart—International Search Report and Written Opinion, dated Dec. 2, 2013, 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. 4, 2014, PCT/US13/47729, filed on Jun. 25, 2013. |
| Foreign Communication from a Related Counterpart—International Search Report and Written Opinion, dated Feb. 4, 2014, PCT/US13/51750, filed on Jul. 24, 2013. |
| FAIPP Pre-Interview Communication dated Mar. 20, 2014, U.S. Appl. No. 13/482,731, filed May 29, 2012. |
| Final Office Action dated Mar. 27, 2014, U.S. Appl. No. 13/470,203, filed May 11, 2012. |
| Notice of Allowance dated Jan. 28, 2014, U.S. Appl. No. 12/486,873, filed Jun. 18, 2009. |
| Paczkowski, Lyle W., et al., “Trusted Security Zone Access to Peripheral Devices”, filed Jan. 6, 2014, U.S. Appl. No. 14/148,714. |
| Notice of Allowance dated Dec. 22, 2014, U.S. Appl. No. 13/470,203, filed May 11, 2012. |
| Notice of Allowance dated Feb. 5, 2015, U.S. Appl. No. 13/533,969, filed Jun. 27, 2012. |
| Office Action dated Dec. 15, 2014, U.S. Appl. No. 13/571,348, filed Aug. 10, 2012. |
| Restriction Requirement dated Jan. 2, 2015, U.S. Appl. No. 13/762,319, filed Feb. 7, 2013. |
| FAIPP Pre-Interview Communication dated Feb. 12, 2015, U.S. Appl. No. 14/066,661, filed Oct. 29, 2013. |
| Notice of Allowance dated Dec. 3, 2014, U.S. Appl. No. 13/594,777, 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 Feb. 26, 2015, U.S. Appl. No. 13/786,450, filed Mar. 5, 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. |
| 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. |
| FAIPP Pre-Interview Communication dated Feb. 4, 2015, U.S. Appl. No. 14/075,663, filed Nov. 8, 2013. |
| FAIPP Pre-Interview Communication dated Feb. 25, 2015, U.S. Appl. No. 14/163,047, filed Jan. 24, 2014. |
| Restriction Requirement dated Jan. 5, 2015, U.S. Appl. No. 13/857,139, filed Apr. 4, 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 Preliminary Report on Patentability, dated Feb. 19, 2015, PCT/US13/53617, filed on Aug. 5, 2013. |
| Foreign Communication from a Related Counterpart—International Preliminary Report on Patentability, dated Feb. 5, 2015, PCT/US13/51750, filed on Jul. 24, 2013. |
| Katzer, Robin D., et al., “Web Server Bypass of Backend Process on Near Field Communications and Secure Elements Chips”, filed Feb. 26, 2015, U.S. Appl. No. 14/632,850. |
| Neson, Tracy L., et al., “Mated Universal Serial Bus (USB) Wireless Dongles Configured with Destination Addresses”, filed Jan. 26, 2015, U.S. Appl. No. 14/606,011. |
| Paczkowski, Lyle W., et al., “Trusted Code Generation and Verification to Prevent Fraud from Maleficent External Devices that Capture Data”, filed Jan. 14, 2015, U.S. Appl. No. 14/592,218. |
| FAIPP Pre-Interview Communication dated Jan. 22, 2015, U.S. Appl. No. 13/544,802, filed Jul. 9, 2012. |
| Office Action dated Aug. 29, 2014, U.S. Appl. No. 13/470,203, filed May 11, 2012. |
| Notice of Allowance dated Oct. 8, 2014, U.S. Appl. No. 13/294,177, filed Nov. 11, 2011. |
| FAIPP Pre-Interview Communication dated Sep. 25, 2014, U.S. Appl. No. 13/533,969, filed Jun. 27, 2012. |
| 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. |
| Notice of Allowance dated Sep. 19, 2014, U.S. Appl. No. 13/594,778, filed Aug. 25, 2012. |
| Final Office Action dated Nov. 7, 2014, U.S. Appl. No. 13/786,450, filed Mar. 5, 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. |
| FAIPP Pre-Interview Communication dated Oct. 21, 2014, U.S. Appl. No. 13/844,325, filed Mar. 15, 2013. |
| Foreign Communication from a Related Counterpart—International Preliminary Report on Patentability, dated Nov. 20, 2014, PCT/US13/40673, filed on May 10, 2013. |
| 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. |
| Fultz, David K., et al., “Location Awareness Session Management and Cross Application Session Management,” filed Jul. 9, 2012, U.S. Appl. No. 13/544,802. |
| Final Office Action dated Nov. 6, 2015, U.S. Appl. No. 14/632,850, filed Feb. 26, 2015. |
| 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. |
| Supplemental Notice of Allowance dated Nov. 16, 2015, U.S. Appl. No. 13/532,588, filed Jun. 25, 2012. |
| Notice of Allowance dated Sep. 21, 2015, U.S. Appl. No. 14/148,714, filed Jan. 6, 2014. |
| Notice of Allowance dated Nov. 9, 2015, U.S. Appl. No. 14/659,614, filed Mar. 17, 2015. |
| Advisory Action dated Nov. 16, 2015, U.S. Appl. No. 13/802,404, filed Mar. 13, 2013. |
| FAIPP Pre-Interview Communication dated Nov. 18, 2015, U.S. Appl. No. 14/681,077, filed Apr. 7, 2015. |
| Office Action dated Nov. 19, 2015, U.S. Appl. No. 13/857,139, filed Apr. 4, 2013. |
| Foreign Communication from a Related Counterpart—International Preliminary Report on Patentability, dated Sep. 24, 2015, PCT/US14/16651, filed on Feb. 16, 2014. |
| Bye, Stephen James, et al., “Systems and Methods for Provisioning and Using Multiple Trusted Security Zones on an Electronic Device,” filed Sep. 15, 2015, U.S. Appl. No. 14/855,364. |
| Notice of Allowance dated Oct. 19, 2015, U.S. Appl. No. 13/544,802, filed Jul. 9, 2012. |
| FAIPP Pre-Interview Communication dated Mar. 25, 2015, U.S. Appl. No. 13/532,588, filed Jun. 25, 2012. |
| FAIPP Pre-Interview Communication dated Mar. 10, 2015, U.S. Appl. No. 13/762,319, filed Feb. 7, 2013. |
| FAIPP Pre-Interview Communication dated May 21, 2015, U.S. Appl. No. 14/090,667, filed Nov. 26, 2013. |
| Final Office Action dated Apr. 7, 2015, U.S. Appl. No. 13/844,145, filed Mar. 15, 2013. |
| First Action Interview Office Action dated Apr. 7, 2015, U.S. Appl. No. 13/802,404, filed Mar. 13, 2013. |
| FAIPP Pre-Interview Communication dated Mar. 26, 2015, U.S. Appl. No. 13/939,175, filed Jul. 10, 2013. |
| FAIPP Pre-Interview Communication dated Mar. 24, 2015, U.S. Appl. No. 13/964,112, filed Aug. 12, 2013. |
| FAIPP Pre-Interview Communication dated Apr. 15, 2015, U.S. Appl. No. 14/085,474, filed Nov. 20, 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 Apr. 9, 2015, U.S. Appl. No. 14/163,047, filed Jan. 24, 2014. |
| 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. |
| Bertz, Lyle T., et al., “Framework for Real-Time Brokering of Digital Content Delivery,” filed Mar. 17, 2015, U.S. Appl. No. 14/659,614. |
| Marquard, et al., “Infrastructure for Secure Short Message Transmission,” filed Apr. 7, 2015, U.S. Appl. No. 14/681,077. |
| Office Action dated Apr. 14, 2015, U.S. Appl. No. 13/544,802, filed Jul. 9, 2012. |
| Notice of Allowance dated May 29, 2015, U.S. Appl. No. 14/085,474, filed Nov. 20, 2013. |
| FAIPP Pre-Interview Communication dated Jul. 2, 2015, U.S. Appl. No. 14/632,850, filed Feb. 26, 2015. |
| Notice of Allowance dated Jun. 17, 2015, U.S. Appl. No. 13/571,348, filed Aug. 10, 2012. |
| Notice of Allowance dated Jun. 9, 2015, U.S. Appl. No. 13/762,319, filed Feb. 7, 2013. |
| Notice of Allowance dated Aug. 4, 2015, U.S. Appl. No. 14/090,667, filed Nov. 26, 2013. |
| Notice of Allowance dated Jul. 6, 2015, U.S. Appl. No. 13/844,145, filed Mar. 15, 2013. |
| Notice of Allowance dated Jul. 6, 2015, U.S. Appl. No. 14/066,661, filed Oct. 29, 2013. |
| Notice of Allowance dated Aug. 14, 2015, U.S. Appl. No. 13/594,779, filed Aug. 25, 2012. |
| Final Office Action dated Aug. 27, 2015, U.S. Appl. No. 13/802,404, filed Mar. 13, 2013. |
| Notice of Allowance dated Jul. 7, 2015, U.S. Appl. No. 13/939,175, filed Jul. 10, 2013. |
| Notice of Allowance dated Aug. 3, 2015, U.S. Appl. No. 13/964,112, filed Aug. 12, 2013. |
| Notice of Allowance dated Jul. 1, 2015, U.S. Appl. No. 14/075,663, filed Nov. 8, 2013. |
| 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 Aug. 5, 2015, U.S. Appl. No. 13/857,141, filed Apr. 4, 2013. |
| FAIPP Pre-Interview Communication dated Jun. 2, 2015, U.S. Appl. No. 13/857,139 filed Apr. 4, 2013. |
| Notice of Allowance dated Jun. 11, 2015, U.S. Appl. No. 13/857,138, filed Apr. 4, 2013. |
| 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. |
| Advisory Action dated Jan. 29, 2016, U.S. Appl. No. 14/632,850, filed Feb. 26, 2015. |
| FAIPP Pre-Interview Communication dated Mar. 1, 2016, U.S. Appl. No. 13/863,376, filed Apr. 15, 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 Dec. 17, 2015, U.S. Appl. No. 13/857,141, filed on Apr. 4, 2013. |
| McRoberts, Leo Michael, et al., “End-to-End Trusted Communications Infrastructure,” filed Jan. 25, 2016, U.S. Appl. No. 15/005,123. |
| Cordes, Kevin R., et al., “Digest of Biographical Information for an Electronic Device with Static and Dynamic 3ortions,” filed on Mar. 14, 2016, U.S. Appl. No. 15/069,921. |
