US20170126693A1 - Passive based security escalation to shut off of application based on rules event triggering - Google Patents
Passive based security escalation to shut off of application based on rules event triggering Download PDFInfo
- Publication number
- US20170126693A1 US20170126693A1 US14/928,154 US201514928154A US2017126693A1 US 20170126693 A1 US20170126693 A1 US 20170126693A1 US 201514928154 A US201514928154 A US 201514928154A US 2017126693 A1 US2017126693 A1 US 2017126693A1
- Authority
- US
- United States
- Prior art keywords
- mobile device
- applications
- user
- security
- event
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/629—Protecting access to data via a platform, e.g. using keys or access control rules to features or functions of an application
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/105—Multiple levels of security
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
- H04L63/205—Network architectures or network communication protocols for network security for managing network security; network security policies in general involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/08—Access security
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/08—Access security
- H04W12/082—Access security using revocation of authorisation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/30—Security of mobile devices; Security of mobile applications
- H04W12/37—Managing security policies for mobile devices or for controlling mobile applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/60—Context-dependent security
- H04W12/61—Time-dependent
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/60—Context-dependent security
- H04W12/67—Risk-dependent, e.g. selecting a security level depending on risk profiles
Definitions
- Embodiments of the present invention address the above needs and/or achieve other advantages by providing apparatuses (e.g., a system, computer program product and/or other devices) and methods for providing a passive based security escalation to shut off of applications on a mobile device based on rules event triggering.
- the system may identify, passively, via extraction of data such as social media data, transaction data, or the like, time periods that the user may be offline or inactive with respect to his/her mobile device. These periods may include when the user is on a flight, in a meeting, in class, traveling abroad, or the like. Once these time periods are identified, information about the time period and the time leading up to and after the offline time period may be identified.
- the generated rules may include one or more security escalations to a single application, one or more security escalations to multiple applications, application functionality shut downs, or the like based on the location of the user during the leading and trailing time as well as the offline time period.
- the system may identify a time period of inactivity or offline status for the user in the future.
- the system may integrate a passive based security escalation to shut off for the time leading up to the offline time period, the offline time period, and the time directly after the time period.
- the system may trigger the passive based security escalation based on determined rules for the specific offline time period.
- the system may initiate the security escalation by increasing mobile application security in a time frame leading up to the offline period.
- the security escalation may target specific applications, such as financial applications or applications with personal information associated therewith.
- the security escalation may apply to all applications. The security escalation may require a user to input additional security information prior to allowing the application functionality.
- the system may shut down one or more applications based on the rules. In this way, the user has the additional security of the application being shut down and thus, no one has the ability to access the applications or user data for misappropriation.
- the system may shut down all applications associated with the user's mobile device.
- the system may shut down specific applications, such as financial applications or applications with personal information associated therewith.
- the user may be able to override the shutdown of the applications via security authorization if needed.
- the system may restore the application functionality.
- the system may, for a predetermined period of time after the offline period, continue to include escalated security for one or more applications.
- the security escalation may target specific applications, such as financial applications or applications with personal information associated therewith.
- the security escalation may apply to all applications. The security escalation may require a user to input additional security information prior to allowing the application functionality.
- Embodiments of the invention relate to systems, methods, and computer program products for passive based security escalation implementation on a mobile device, the invention comprising: extracting historical user data associated with a user from one or more external sources; identifying from the historical user data, one or more indications of offline periods of time for the mobile device associated with the user, wherein the identified indications include one or more events that the user is attending at a future time; generating a security escalation plan for the event; accessing and integrating into the mobile device an increase to security requirements for authorizing one or more applications on the mobile device based on a triggering of a time period leading up to the event; integrating into the mobile device a shutdown of the one or more applications on the mobile device during the offline period of time for the mobile device during the event; restoring functionality of the one or more applications after the offline period of time for the mobile device with an increase to the security requirements for authorizing the one or more applications on the mobile device based on a triggering of a time period after the offline time period associated with the event;
- integrating into the mobile device the shutdown of the one or more applications on the mobile device further comprises shutting down the functionality of the one or more applications such that external devices cannot activate the one or more applications during the offline period of time.
- the increase security requirements for authorizing one or more applications on the mobile device further comprises increasing the security requirements to one or more applications that contain financial data and personal data of the user, wherein the increased security requirements include requiring additional authentication to allow access to the one or more applications via the mobile device.
- generating a security escalation plan for the event further comprises generating rules for security level requirements for each event and security level requirements for a time period prior to and after a duration of the event.
- indications of offline periods of time for the mobile device associated with the user further comprise an indication of a purchase of a ticket or pass to the event.
- the event is an airplane flight.
- the invention further comprising identifying a duration of the offline period based on a request for the duration from a venue of the event.
- historical user data comprises user transaction data extracted from a financial institution, user social network data extracted from a social networking website, and user account data extracted from one or more merchants.
- FIG. 1 provides a passive based security escalation system environment, in accordance with one embodiment of the present invention
- FIG. 2 provides a high level process flow illustrating the passive based security escalation process, in accordance with one embodiment of the present invention
- FIG. 3 provides a process map illustrating extracting historical data for the passive based security escalation system, in accordance with one embodiment of the present invention
- FIG. 4 provides a process map illustrating generating rules for the passive based security escalation system, in accordance with one embodiment of the present invention.
- FIG. 5 provides a process map illustrating an example of the passive based security escalation system, in accordance with one embodiment of the present invention.
- the term “user device” or “mobile device” may refer to mobile phones, personal computing devices, tablet computers, wearable devices, and/or any portable electronic device capable of receiving and/or storing data therein.
- portable multi-function devices such as laptop computers, tablet computers, mobile phones and the like are common.
- individuals may have a user device on them when in public.
- These devices have the capability to hold large amounts of information, including personal information. Misappropriation of these devices may cause the transfer of personal information from one individual to another.
- Embodiments of the present invention address the above needs and/or achieve other advantages by providing apparatuses (e.g., a system, computer program product and/or other devices) and methods for providing a passive based security escalation to shut off of applications on a mobile device based on rules event triggering.
- the system may identify, passively, via extraction of data such as social media data, transaction data, or the like, time periods that the user may be offline or inactive with respect to his/her mobile device. These periods may include when the user is on a flight, in a meeting, in class, traveling abroad, or the like. Once these time periods are identified, information about the time period and the time leading up to and after the offline time period may be identified.
- the system may prevent the access, thus preventing misappropriation of the information on the device.
- Embodiments of the invention are directed to a system, method, or computer program product for a distributive network system with specialized data feeds associated with the distributive network and specific triggering events associated with the data feeds for coding and generating a passive based security escalation to shut off system for application security on a mobile device.
- the system may communicate with, store, and execute code on a mobile device for completion of the security speculation programs.
- the system may manipulate and transform currently stored applications on a user device for passive security escalation.
- FIG. 1 illustrates a passive based security escalation system environment, in accordance with one embodiment of the present invention 200 , in accordance with one embodiment of the present invention.
- FIG. 1 provides the system environment 200 for which the distributive network system with specialized data feeds associated with the distributive network and specific triggering events associated with the data feeds for passive based security escalation associated with applications on a user mobile device.
- FIG. 1 provides a unique system that includes specialized servers and system communicably linked across a distributive network of nodes required to perform the functions of identifying applications on a user device, identifying offline time periods for a user, initiating a rules based security escalation program for one or more applications on a user's mobile device based on the offline time periods, and imputing security escalation or application shut off for the time periods identified.
- the system may be, as described below, run on a diffusion network of specialized nodes meant for passive based security escalation.
- the application server 208 is operatively coupled, via a network 201 to the user system 204 , and to the network system 206 .
- the application server 208 can send information to and receive information from the user device 204 and the network system 206 .
- FIG. 1 illustrates only one example of an embodiment of the system environment 200 , and it will be appreciated that in other embodiments one or more of the systems, devices, or servers may be combined into a single system, device, or server, or be made up of multiple systems, devices, or servers.
- the network 201 may be a system specific distributive network receiving and distributing specific network feeds and identifying specific network associated triggers.
- the network 201 may also be a global area network (GAN), such as the Internet, a wide area network (WAN), a local area network (LAN), or any other type of network or combination of networks.
- GAN global area network
- the network 201 may provide for wireline, wireless, or a combination wireline and wireless communication between devices on the network 201 .
- the user 202 is an individual that has a user device, such as a mobile phone, tablet, or the like.
- FIG. 1 also illustrates a user system 204 .
- the user device 204 may be, for example, a desktop personal computer, a mobile system, such as a cellular phone, smart phone, personal data assistant (PDA), laptop, or the like.
- the user device 204 generally comprises a communication device 212 , a processing device 214 , and a memory device 216 .
- the user device 204 is a computing system that allows a user 202 to interact through the network 201 with the application server 208 to request an identifier, authorize the storage of the identifier on the user device 204 , and to activate the identifier.
- the processing device 214 is operatively coupled to the communication device 212 and the memory device 216 .
- the processing device 214 uses the communication device 212 to communicate with the network 201 and other devices on the network 201 , such as, but not limited to the network system 206 and the application server 208 .
- the communication device 212 generally comprises a modem, server, or other device for communicating with other devices on the network 201 .
- the user device 204 comprises computer-readable instructions 220 and data storage 218 stored in the memory device 216 , which in one embodiment includes the computer-readable instructions 220 of a user application 222 .
- the user application 222 allows a user 202 to activate and utilize applications via the user device 204 . Furthermore, the user application 222 allows the user to sign onto using the passive based security system. In this way, the user application 222 may allow the user to accept and log into using the passive based security system for securing the applications on the user device 204 associated with the user 204 . Furthermore, the user application 222 allows a user to input additional security authentications at the user device 204 to allow activation of the applications that are part of the security escalation program generated by the system.
- the application server 208 generally comprises a communication device 246 , a processing device 248 , and a memory device 250 .
- processing device generally includes circuitry used for implementing the communication and/or logic functions of the particular system.
- a processing device may include a digital signal processor device, a microprocessor device, and various analog-to-digital converters, digital-to-analog converters, and other support circuits and/or combinations of the foregoing. Control and signal processing functions of the system are allocated between these processing devices according to their respective capabilities.
- the processing device may include functionality to operate one or more software programs based on computer-readable instructions thereof, which may be stored in a memory device.
- the processing device 248 is operatively coupled to the communication device 246 and the memory device 250 .
- the processing device 248 uses the communication device 246 to communicate with the network 201 and other devices on the network 201 , such as, but not limited to the network system 206 and the user system 204 .
- the communication device 246 generally comprises a modem, server, or other device for communicating with other devices on the network 201 .
- the application server 208 comprises computer-readable instructions 254 stored in the memory device 250 , which in one embodiment includes the computer-readable instructions 254 of a security application 258 .
- the memory device 250 includes data storage 252 for storing data related to the system environment, but not limited to data created and/or used by the security application 258 .
- the security application 258 may extract historical user data, identify one or more offline time periods for a user's user device 204 , generate a security escalation program, and activate the security escalation program on the user device 204 based on a trigger.
- the security application 258 may extract historical user data.
- the historical user data extracted by the security application 258 may include user transaction data, user social network data, and/or user account data.
- User transaction data comprises data associated with financial institution accounts, payment accounts, or the like that may provide information about transactions the user 202 may have completed with a credit card, debit card, or the like.
- the security application 258 may request or extract transaction data via the network 201 .
- User social networking data is extracted by the security application 258 from social networking sites and includes accessing and extracting information from user social networking sites that may provide an indication of a user 202 being offline from a mobile device for a period of time.
- User account data is extracted from one or more payment accounts, merchant accounts, rewards accounts, frequent flier accounts, or the like that the user 202 has set up that may provide an indication of one or more offline period.
- the security application 258 may identify one or more offline time periods for a user's user device 204 . As such, the security application 258 reviews the historical user data for indications of future offline periods for a user device 204 . While the term historical user data is used throughout this application, one will appreciate that the data may be extracted from one or more sources in real-time or near real-time in order to provide the system with an up to date view of potential offline periods of the user device 204 in the future. In this way, the security application 258 reviews the data extracted from one or more sources to identify potential offline periods of time for the user device 204 .
- These offline periods may include classes, flights, movies, events, plays, or the like that may provide an indication of one or more periods of offline time of the user and his/her mobile device.
- the data identified by the security application 258 may specifically indicate the purchase of tickets, passes, or the like for an event that will be an offline period for the user device 204 .
- the data extracted and identified by the security application 258 may be ancillary data that the security application 258 may combine to provide a confidence level that a specific event will occur and the user device 204 will be offline.
- the security application 258 may generate a security escalation program.
- the program for each event requires the generation of rules for that event.
- the security application 258 may create the one or more rules for each even that is associated with an offline time period based on the identified reason for the offline time period. As such, the rules may be based on whether the offline time period requires true shut off of the user device 204 or a silencing of the user device 204 .
- the security application 258 may generate rules for the time period leading up to the offline time period, the offline time period, and a time period after the offline time period. Once the rules are created for the specific event the security application 258 may be stored and utilized in the future for subsequent similar events for other users.
- the security application 258 generates a security escalation program for a time period leading up to the offline time period based on the reasons for the offline time period. As such, if the offline time includes potential security issues, such as being in a crowded public place, or the like prior to the offline period, the security application 258 may escalate security for one or more applications on the user device 204 during the period of time leading up to the offline period. In this way, the security application 258 may integrate into the user device 204 and may require additional security authorization to allow access to one or more applications on the user device 204 . In some embodiments, the security escalation integrated from the security application 258 may target specific applications, such as financial applications or applications with personal information associated therewith. In some embodiments, the security escalation integrated from the security application 258 may apply to all applications. The security escalation may require a user 202 to input additional security information prior to allowing the application functionality.
- the security application 258 may generate a security escalation program or application shut down program for the offline time period based on the reasons for the offline time period. As such, if it is identified that the user device 204 is going to have an offline time period, such as during a flight, the security application 258 may shut down the functionality of one or more of the applications via integration into the user device 204 . In some embodiments, the security application 258 may shut down all applications associated with the user device 204 . In some embodiments, the security application 258 may shut down specific applications, such as financial applications or applications with personal information associated therewith associated with the user device 204 . In some embodiments, the user 202 may be able to override the shutdown of the applications from the security application 258 via security authorization if needed.
- the security application 258 may generate a security escalation program for a time period after the offline time period based on reasons for the offline time period. As such, after the offline time period has expired, the security application 258 may restore the application functionality on the user device 204 . In some embodiments, the security application 258 may, for a predetermined period of time after the offline period, continue to include escalated security for one or more applications. In some embodiments, the security escalation may target specific applications on the user device 204 , such as financial applications or applications with personal information associated therewith. In some embodiments, the security escalation may apply to all applications on the user device 204 . The security escalation may require a user 202 to input additional security information on the user device 204 prior to the security application 258 allowing the application functionality.
- the network system 206 is connected to the application server 208 and is associated with a mobile device network. In this way, while only one network system 206 is illustrated in FIG. 1 , it is understood that multiple network systems may make up the system environment 200 .
- the network system 206 generally comprises a communication device 236 , a processing device 238 , and a memory device 240 .
- the network system 206 comprises computer-readable instructions 242 stored in the memory device 240 , which in one embodiment includes the computer-readable instructions 242 of a network application 244 .
- FIG. 2 provides a high level process flow illustrating the passive based security escalation process 100 , in accordance with one embodiment of the present invention.
- the process 102 is initiated by extracting historical user data. This historical data may include transaction data, social networking data, or the like.
- the process 100 continues by identifying potential offline periods of time the user may have in the future based on the historical user data.
- the system may identify based on user data, such as transaction data, social media data, or the like, potential future periods of time that the user may be offline with his/her mobile device.
- Offline periods may include flights, meetings, classes, or the like when a user may have his/her mobile device turned off. Identifying the offline periods includes identifying airline tickets purchased, books for classes, or the like via transaction data and/or reviewing social networking data for indications of vacations, meetings, or other indicators suggesting the user may have his/her mobile device turned off.
- the system may generate rules for security of mobile applications before, during, and/or after the identified offline time periods. These rules may include a security level for before, during, and/or after the offline time period. For before and after the offline time period, the system may generate rules for requiring additional security authentication for one or more applications on the user's mobile device. For the offline time periods, the system may shut off functionality of one or more applications on the user's mobile device. In this way, in public places or while the user is not online with the mobile device, the user is provided additional misappropriation protection.
- the process 100 continues by increasing the mobile application security leading up to the offline time period based on the rules associated with the identified offline time period, as illustrated in block 108 .
- some embodiments may require additional security authentication for one or more selected applications.
- additional security authentication for all applications may be implemented.
- the system may temporarily shut down the mobile application functions of one or more applications based on the rules.
- the applications may be shut off or shut down from access for the duration of the offline time period. As such, the system may not allow access from any location to applications on the mobile device during the offline period.
- the system may restore the mobile applications once the offline tie period has passed, as illustrated in block 112 .
- FIG. 3 illustrates a process map for extracting historical data for the passive based security escalation system 400 , in accordance with one embodiment of the present invention.
- the process 400 is initiated by the system extracting historical user data.
- the historical user data extracted in block 402 may include user transaction data 403 , user social network data 405 , and user account data 407 .
- the user data may be user transaction data 403 .
- User transaction data 403 comprises accessing and extracting information from financial institutions or the like that has information about transactions the user may have completed with a credit card, debit card, or the like.
- the system may identify if the user has purchased books, airline tickets, or the like that may be associated with an offline time period of the user's mobile device.
- User social networking data 405 comprises accessing and extracting information from user social networking sites that may provide an indication of a user being offline from a mobile device for a period of time.
- User account data 407 is data extracted from one or more payment accounts, merchant accounts, rewards accounts, frequent flier accounts, or the like that the user has set up that may provide an indication of one or more offline periods. For example, a user may have an account with a movie theater for purchasing movie tickets, the system may identify the account and movies that the user may attend, thus leading to offline periods. In another example, the system may identify that the user has a frequent flyer account with an airline, based on this account the system may be able to identify one or more upcoming flights that the user may have, which will lead to offline time periods for the user during the flight.
- the process 400 continues when the system gathers the extracted historical user data from block 402 and reviews the historical user data for indications of future offline periods for a user's mobile devices, as illustrated in block 404 .
- historical user data is used throughout this application, one will appreciate that the data may be extracted from one or more sources in real-time or near real-time in order to provide the system with an up to date view of potential offline periods of the user in the future.
- the system may review the data extracted from one or more sources to identify potential offline periods of time for the user's mobile device. These offline periods may include classes, flights, movies, events, plays, or the like that may provide an indication of one or more periods of offline time of the user and his/her mobile device.
- the data extracted may specifically indicate the purchase of tickets, passes, or the like for an event that will be an offline period for the user's mobile device.
- the data extracted may be ancillary data that the system may combine to provide a confidence level that a specific event will occur and the user's mobile device will be offline.
- ancillary data may include the purchase of books and school supplies from one source and a social networking trend indicating the user is attending a class or school.
- the data may be extracted from various sources, but be combined to provide a confidence that one or more of the events that may lead to an offline time period of the user's mobile device may occur.
- the system may next predict the duration of the offline time period.
- the system may use the data extracted to identify that a flight, event ticket or the like has been purchased. Subsequently, the system may access the airline or the event venue and determine a duration of the event such that the system may only initiate shut off of the application functionality during that event.
- the system may store the data for passive based security escalation, as illustrated in block 408 .
- the storing may include a triggering of the passive based security escalation at a specific time period prior to the offline time period.
- the process 400 is completed by initiating the passive based security escalation upon identifying the upcoming predicted offline time period and/or a triggering time prior to the offline time period.
- FIG. 4 illustrates a process map for generating rules for the passive based security escalation system 500 , in accordance with one embodiment of the present invention.
- the process 500 is initiated by creating one or more rules for each offline time period based on the identified reason for the offline time period.
- the rules may be based on whether the offline time period requires a true shut off of the mobile device or a silencing of the mobile device.
- the offline time period may be a complete turn off of the mobile device, such as on a flight or the like.
- the offline time period may be a period of inactivity when the mobile device may be silent, such as at an event, in a meeting, or the like.
- the rules may be based on how public the location is with respect to the offline time and/or the time leading up to the offline time.
- the rules may be stored and utilized in the future for subsequent similar events for other users.
- the system may then generate a security escalation program for the event, thus for the time period leading up to the offline time period, the offline time period, and a time period after the offline time period.
- the process 500 continues by generating a security escalation program for a time period leading up to the offline time period based on the reasons for the offline time period.
- the system may escalate security for one or more applications on the mobile device during the period of time leading up to the offline period. In this way, the system may require additional security authorization to allow access to one or more applications with financial information, personal information, or the like.
- the security escalation may target specific applications, such as financial applications or applications with personal information associated therewith.
- the security escalation may apply to all applications. The security escalation may require a user to input additional security information prior to allowing the application functionality.
- the system may generate a security escalation program or application shut down program for the offline time period based on the reasons for the offline time period. As such, if the user is going to have an offline time period, such as during a flight, the system may shut down the functionality of one or more of the applications. Thus, once the offline time period has begun, the system may shut down one or more applications based on the rules. In this way, the user has the additional security of the application being shut down and thus, no one has the ability to access the applications or user data for misappropriation. In some embodiments, the system may shut down all applications associated with the user's mobile device. In some embodiments, the system may shut down specific applications, such as financial applications or applications with personal information associated therewith. In some embodiments, the user may be able to override the shutdown of the applications via security authorization if needed.
- the process 500 continues by generating a security escalation program for a time period after the offline time period based on reasons for the offline time period.
- the system may restore the application functionality.
- the system may, for a predetermined period of time after the offline period, continue to include escalated security for one or more applications.
- the security escalation may target specific applications, such as financial applications or applications with personal information associated therewith.
- the security escalation may apply to all applications. The security escalation may require a user to input additional security information prior to allowing the application functionality.
- the system may store the generated security escalation program for the event associated with the rules for each reason for an offline time period.
- the system may build a database of rules and escalation parameters for each of the potential events leading to an offline time period.
- the system may continually learn and adjust the security escalation programs for each event based on prior events and prior programs generated.
- FIG. 5 illustrates a process map of an example of the passive based security escalation system 300 , in accordance with one embodiment of the present invention.
- the process 300 is initiated by the identification of travel plans of the user from extracted historical user data.
- the system may have identified and extracted the data from a user account, such as a frequent flyer account or the like, user transaction history, such as credit card data from a financial institution, and/or from user social network data, such as from a post or blog from the user indicating travel plans.
- one data source may have been used to identify travel plans of the user.
- a combination of one or more data sources may have been used to identify travel plans of the user.
- the system may generate a confidence score, indicating a confidence of the travel plans being authentic.
- the system may identify the actual duration of offline time of a mobile device associated with the user, as illustrated in block 304 .
- the system may reach out to external sources to determine a duration of the event leading to the offline time period.
- the system may reach out to the airlines to determine the duration of the flight of the user.
- the system may begin to map and generate a security escalation program for the travel, as illustrated in block 306 .
- the security escalation program may include a selection of all or some applications for security escalation prior to and after the offline time period and a selection of all or some applications for security escalation or application shut off during the offline time period.
- the system may identify the time period the user may be at the airport prior to and after the flight. In this way, the system may identify security escalations that may require additional authorization or passwords for access to one or more applications on the user's mobile device while he/she is at the airport.
- the applications associated with the security escalation may include any that has financial or personal information about the user. In other embodiments, all applications on the mobile device may be associated with security escalations.
- the process may continue by increasing mobile application security parameters during the user's time in the airport or other public place associated with the user's travel plans.
- the system may require additional security authorization or password protection for accessing application functionality during time periods prior to the user's flight.
- the applications associated with the security escalation may include any that has financial or personal information about the user. In other embodiments, all applications on the mobile device may be associated with security escalations.
- the system may temporarily shut down mobile application functionality during the flight.
- This application functionality that is shut down may be directed specifically to one or more mobile devices identified as being associated with the user and/or on the flight with the user.
- the system may reinstate mobile application functionality to the user's mobile device with increased security parameters, as illustrated in block 312 .
- the system may, for a predetermined period of time after the offline period, continue to include escalated security for one or more applications.
- the security escalation may target specific applications, such as financial applications or applications with personal information associated therewith.
- the security escalation may apply to all applications. The security escalation may require a user to input additional security information prior to allowing the application functionality.
- the process 300 is completed by restoring full mobile application functionality after the user has left the airport or public place associated with travel plans.
- the present invention may be embodied as an apparatus (including, for example, a system, a machine, a device, a computer program product, and/or the like), as a method (including, for example, a business process, a computer-implemented process, and/or the like), or as any combination of the foregoing.
- embodiments of the present invention may take the form of an entirely software embodiment (including firmware, resident software, micro-code, and the like), an entirely hardware embodiment, or an embodiment combining software and hardware aspects that may generally be referred to herein as a “system.”
- embodiments of the present invention may take the form of a computer program product that includes a computer-readable storage medium having computer-executable program code portions stored therein.
- a processor may be “configured to” perform a certain function in a variety of ways, including, for example, by having one or more special-purpose circuits perform the functions by executing one or more computer-executable program code portions embodied in a computer-readable medium, and/or having one or more application-specific circuits perform the function.
- the computer device and application-specific circuits associated therewith are deemed specialized computer devices capable of improving technology associated with the in authorization and instant integration of a new credit card to digital wallets.
- the computer-readable medium may include, but is not limited to, a non-transitory computer-readable medium, such as a tangible electronic, magnetic, optical, infrared, electromagnetic, and/or semiconductor system, apparatus, and/or device.
- a non-transitory computer-readable medium such as a tangible electronic, magnetic, optical, infrared, electromagnetic, and/or semiconductor system, apparatus, and/or device.
- the non-transitory computer-readable medium includes a tangible medium such as a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a compact disc read-only memory (CD-ROM), and/or some other tangible optical and/or magnetic storage device.
- the computer-readable medium may be transitory, such as a propagation signal including computer-executable program code portions embodied therein.
- one or more computer-executable program code portions for carrying out the specialized operations of the present invention may be required on the specialized computer include object-oriented, scripted, and/or unscripted programming languages, such as, for example, Java, Perl, Smalltalk, C++, SAS, SQL, Python, Objective C, and/or the like.
- the one or more computer-executable program code portions for carrying out operations of embodiments of the present invention are written in conventional procedural programming languages, such as the “C” programming languages and/or similar programming languages.
- the computer program code may alternatively or additionally be written in one or more multi-paradigm programming languages, such as, for example, F#.
- These one or more computer-executable program code portions may be provided to a processor of a special purpose computer for the authorization and instant integration of credit cards to a digital wallet, and/or some other programmable data processing apparatus in order to produce a particular machine, such that the one or more computer-executable program code portions, which execute via the processor of the computer and/or other programmable data processing apparatus, create mechanisms for implementing the steps and/or functions represented by the flowchart(s) and/or block diagram block(s).
- the one or more computer-executable program code portions may be stored in a transitory or non-transitory computer-readable medium (e.g., a memory, and the like) that can direct a computer and/or other programmable data processing apparatus to function in a particular manner, such that the computer-executable program code portions stored in the computer-readable medium produce an article of manufacture, including instruction mechanisms which implement the steps and/or functions specified in the flowchart(s) and/or block diagram block(s).
- a transitory or non-transitory computer-readable medium e.g., a memory, and the like
- the one or more computer-executable program code portions may also be loaded onto a computer and/or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer and/or other programmable apparatus.
- this produces a computer-implemented process such that the one or more computer-executable program code portions which execute on the computer and/or other programmable apparatus provide operational steps to implement the steps specified in the flowchart(s) and/or the functions specified in the block diagram block(s).
- computer-implemented steps may be combined with operator and/or human-implemented steps in order to carry out an embodiment of the present invention.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Computing Systems (AREA)
- Theoretical Computer Science (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Health & Medical Sciences (AREA)
- Telephonic Communication Services (AREA)
- Telephone Function (AREA)
Abstract
Embodiments of the invention are directed to a system, method, or computer program product for a passive based security escalation to shut off of applications on a mobile device based on rules. As such, the system may identify, via extraction of data, time periods correlating to events that the user may be offline or inactive with respect to his/her mobile device. Once the time periods are identified, rules are created for the level of security escalation required based on the event. Subsequently, a trigger is identified at a time leading up to the event, where the system integrates with the mobile device and requires additional authentication to access one or more applications. Once the offline event starts, the system initiates a shutdown of the functions of one or more applications on the user's mobile device. The system then reinstates the application functionality after the offline event has ended.
Description
- Advancements in technology have made mobile devices with multi-faceted functionality available to large numbers of individuals. With the continued addition of new functions to these mobile devices, more and more information about the individuals that own the device is being carried on the mobile device. In this way, security of the mobile device has been important, providing key locks and password protection to the information stored on the mobile device.
- The following presents a simplified summary of one or more embodiments of the invention in order to provide a basic understanding of such embodiments. This summary is not an extensive overview of all contemplated embodiments, and is intended to neither identify key or critical elements of all embodiments, nor delineate the scope of any or all embodiments. Its sole purpose is to present some concepts of one or more embodiments in a simplified form as a prelude to the more detailed description that is presented later.
- Embodiments of the present invention address the above needs and/or achieve other advantages by providing apparatuses (e.g., a system, computer program product and/or other devices) and methods for providing a passive based security escalation to shut off of applications on a mobile device based on rules event triggering. As such, the system may identify, passively, via extraction of data such as social media data, transaction data, or the like, time periods that the user may be offline or inactive with respect to his/her mobile device. These periods may include when the user is on a flight, in a meeting, in class, traveling abroad, or the like. Once these time periods are identified, information about the time period and the time leading up to and after the offline time period may be identified. As such, for example, if the user is on a flight, the time leading up to the flight and after the flight, the user may be in the airport or another public place. The identification of the offline time and information about the time leading up to and after the offline time period may all lead to the system generation of rules associated with each specific case. In some embodiments, the generated rules may include one or more security escalations to a single application, one or more security escalations to multiple applications, application functionality shut downs, or the like based on the location of the user during the leading and trailing time as well as the offline time period.
- In this way, the system may identify a time period of inactivity or offline status for the user in the future. In order to prevent any misappropriation of the data on the user's device during the offline time period, the system may integrate a passive based security escalation to shut off for the time leading up to the offline time period, the offline time period, and the time directly after the time period.
- Once the offline time period is approaching, the system may trigger the passive based security escalation based on determined rules for the specific offline time period. In this way, in some embodiments, the system may initiate the security escalation by increasing mobile application security in a time frame leading up to the offline period. In some embodiments, the security escalation may target specific applications, such as financial applications or applications with personal information associated therewith. In some embodiments, the security escalation may apply to all applications. The security escalation may require a user to input additional security information prior to allowing the application functionality.
- Next, once the offline time period has begun, the system may shut down one or more applications based on the rules. In this way, the user has the additional security of the application being shut down and thus, no one has the ability to access the applications or user data for misappropriation. In some embodiments, the system may shut down all applications associated with the user's mobile device. In some embodiments, the system may shut down specific applications, such as financial applications or applications with personal information associated therewith. In some embodiments, the user may be able to override the shutdown of the applications via security authorization if needed.
- Finally, after the offline time period has expired, the system may restore the application functionality. In some embodiments, the system may, for a predetermined period of time after the offline period, continue to include escalated security for one or more applications. In some embodiments, the security escalation may target specific applications, such as financial applications or applications with personal information associated therewith. In some embodiments, the security escalation may apply to all applications. The security escalation may require a user to input additional security information prior to allowing the application functionality.
- Embodiments of the invention relate to systems, methods, and computer program products for passive based security escalation implementation on a mobile device, the invention comprising: extracting historical user data associated with a user from one or more external sources; identifying from the historical user data, one or more indications of offline periods of time for the mobile device associated with the user, wherein the identified indications include one or more events that the user is attending at a future time; generating a security escalation plan for the event; accessing and integrating into the mobile device an increase to security requirements for authorizing one or more applications on the mobile device based on a triggering of a time period leading up to the event; integrating into the mobile device a shutdown of the one or more applications on the mobile device during the offline period of time for the mobile device during the event; restoring functionality of the one or more applications after the offline period of time for the mobile device with an increase to the security requirements for authorizing the one or more applications on the mobile device based on a triggering of a time period after the offline time period associated with the event; and restoring standard security requirements of the one or more applications.
- In some embodiments, integrating into the mobile device the shutdown of the one or more applications on the mobile device further comprises shutting down the functionality of the one or more applications such that external devices cannot activate the one or more applications during the offline period of time.
- In some embodiments, the increase security requirements for authorizing one or more applications on the mobile device, further comprises increasing the security requirements to one or more applications that contain financial data and personal data of the user, wherein the increased security requirements include requiring additional authentication to allow access to the one or more applications via the mobile device.
- In some embodiments, generating a security escalation plan for the event further comprises generating rules for security level requirements for each event and security level requirements for a time period prior to and after a duration of the event.
- In some embodiments, indications of offline periods of time for the mobile device associated with the user further comprise an indication of a purchase of a ticket or pass to the event. In some embodiments, the event is an airplane flight.
- In some embodiments, the invention further comprising identifying a duration of the offline period based on a request for the duration from a venue of the event.
- In some embodiments, historical user data comprises user transaction data extracted from a financial institution, user social network data extracted from a social networking website, and user account data extracted from one or more merchants.
- The features, functions, and advantages that have been discussed may be achieved independently in various embodiments of the present invention or may be combined with yet other embodiments, further details of which can be seen with reference to the following description and drawings.
- Having thus described embodiments of the invention in general terms, reference will now be made to the accompanying drawings, wherein:
-
FIG. 1 provides a passive based security escalation system environment, in accordance with one embodiment of the present invention; -
FIG. 2 provides a high level process flow illustrating the passive based security escalation process, in accordance with one embodiment of the present invention; -
FIG. 3 provides a process map illustrating extracting historical data for the passive based security escalation system, in accordance with one embodiment of the present invention; -
FIG. 4 provides a process map illustrating generating rules for the passive based security escalation system, in accordance with one embodiment of the present invention; and -
FIG. 5 provides a process map illustrating an example of the passive based security escalation system, in accordance with one embodiment of the present invention. - Embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments of the invention are shown. Indeed, the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like numbers refer to elements throughout. Where possible, any terms expressed in the singular form herein are meant to also include the plural form and vice versa, unless explicitly stated otherwise. Also, as used herein, the term “a” and/or “an” shall mean “one or more,” even though the phrase “one or more” is also used herein.
- Furthermore, as used herein the term “user device” or “mobile device” may refer to mobile phones, personal computing devices, tablet computers, wearable devices, and/or any portable electronic device capable of receiving and/or storing data therein.
- With advancements in technology infrastructures and wireless communication implementation, portable multi-function devices, such as laptop computers, tablet computers, mobile phones and the like are common. Typically, individuals may have a user device on them when in public. These devices have the capability to hold large amounts of information, including personal information. Misappropriation of these devices may cause the transfer of personal information from one individual to another.
- Embodiments of the present invention address the above needs and/or achieve other advantages by providing apparatuses (e.g., a system, computer program product and/or other devices) and methods for providing a passive based security escalation to shut off of applications on a mobile device based on rules event triggering. As such, the system may identify, passively, via extraction of data such as social media data, transaction data, or the like, time periods that the user may be offline or inactive with respect to his/her mobile device. These periods may include when the user is on a flight, in a meeting, in class, traveling abroad, or the like. Once these time periods are identified, information about the time period and the time leading up to and after the offline time period may be identified.
- In this way, if a mobile device or information on the mobile device is accessed without authorization while a user is offline, the system may prevent the access, thus preventing misappropriation of the information on the device.
- Embodiments of the invention are directed to a system, method, or computer program product for a distributive network system with specialized data feeds associated with the distributive network and specific triggering events associated with the data feeds for coding and generating a passive based security escalation to shut off system for application security on a mobile device. Thus, the system may communicate with, store, and execute code on a mobile device for completion of the security speculation programs. Furthermore, the system may manipulate and transform currently stored applications on a user device for passive security escalation.
-
FIG. 1 illustrates a passive based security escalation system environment, in accordance with one embodiment of thepresent invention 200, in accordance with one embodiment of the present invention.FIG. 1 provides thesystem environment 200 for which the distributive network system with specialized data feeds associated with the distributive network and specific triggering events associated with the data feeds for passive based security escalation associated with applications on a user mobile device. -
FIG. 1 provides a unique system that includes specialized servers and system communicably linked across a distributive network of nodes required to perform the functions of identifying applications on a user device, identifying offline time periods for a user, initiating a rules based security escalation program for one or more applications on a user's mobile device based on the offline time periods, and imputing security escalation or application shut off for the time periods identified. Furthermore, in some embodiments, the system may be, as described below, run on a diffusion network of specialized nodes meant for passive based security escalation. - As illustrated in
FIG. 1 , theapplication server 208 is operatively coupled, via anetwork 201 to the user system 204, and to thenetwork system 206. In this way, theapplication server 208 can send information to and receive information from the user device 204 and thenetwork system 206.FIG. 1 illustrates only one example of an embodiment of thesystem environment 200, and it will be appreciated that in other embodiments one or more of the systems, devices, or servers may be combined into a single system, device, or server, or be made up of multiple systems, devices, or servers. - The
network 201 may be a system specific distributive network receiving and distributing specific network feeds and identifying specific network associated triggers. Thenetwork 201 may also be a global area network (GAN), such as the Internet, a wide area network (WAN), a local area network (LAN), or any other type of network or combination of networks. Thenetwork 201 may provide for wireline, wireless, or a combination wireline and wireless communication between devices on thenetwork 201. - In some embodiments, the user 202 is an individual that has a user device, such as a mobile phone, tablet, or the like.
FIG. 1 also illustrates a user system 204. The user device 204 may be, for example, a desktop personal computer, a mobile system, such as a cellular phone, smart phone, personal data assistant (PDA), laptop, or the like. The user device 204 generally comprises acommunication device 212, aprocessing device 214, and amemory device 216. The user device 204 is a computing system that allows a user 202 to interact through thenetwork 201 with theapplication server 208 to request an identifier, authorize the storage of the identifier on the user device 204, and to activate the identifier. Theprocessing device 214 is operatively coupled to thecommunication device 212 and thememory device 216. Theprocessing device 214 uses thecommunication device 212 to communicate with thenetwork 201 and other devices on thenetwork 201, such as, but not limited to thenetwork system 206 and theapplication server 208. As such, thecommunication device 212 generally comprises a modem, server, or other device for communicating with other devices on thenetwork 201. - The user device 204 comprises computer-
readable instructions 220 anddata storage 218 stored in thememory device 216, which in one embodiment includes the computer-readable instructions 220 of a user application 222. - In some embodiments, the user application 222 allows a user 202 to activate and utilize applications via the user device 204. Furthermore, the user application 222 allows the user to sign onto using the passive based security system. In this way, the user application 222 may allow the user to accept and log into using the passive based security system for securing the applications on the user device 204 associated with the user 204. Furthermore, the user application 222 allows a user to input additional security authentications at the user device 204 to allow activation of the applications that are part of the security escalation program generated by the system.
- As further illustrated in
FIG. 1 , theapplication server 208 generally comprises acommunication device 246, aprocessing device 248, and amemory device 250. As used herein, the term “processing device” generally includes circuitry used for implementing the communication and/or logic functions of the particular system. For example, a processing device may include a digital signal processor device, a microprocessor device, and various analog-to-digital converters, digital-to-analog converters, and other support circuits and/or combinations of the foregoing. Control and signal processing functions of the system are allocated between these processing devices according to their respective capabilities. The processing device may include functionality to operate one or more software programs based on computer-readable instructions thereof, which may be stored in a memory device. - The
processing device 248 is operatively coupled to thecommunication device 246 and thememory device 250. Theprocessing device 248 uses thecommunication device 246 to communicate with thenetwork 201 and other devices on thenetwork 201, such as, but not limited to thenetwork system 206 and the user system 204. As such, thecommunication device 246 generally comprises a modem, server, or other device for communicating with other devices on thenetwork 201. - As further illustrated in
FIG. 1 , theapplication server 208 comprises computer-readable instructions 254 stored in thememory device 250, which in one embodiment includes the computer-readable instructions 254 of asecurity application 258. In some embodiments, thememory device 250 includesdata storage 252 for storing data related to the system environment, but not limited to data created and/or used by thesecurity application 258. - In the embodiment illustrated in
FIG. 1 and described throughout much of this specification, thesecurity application 258 may extract historical user data, identify one or more offline time periods for a user's user device 204, generate a security escalation program, and activate the security escalation program on the user device 204 based on a trigger. - In some embodiments, the
security application 258 may extract historical user data. The historical user data extracted by thesecurity application 258 may include user transaction data, user social network data, and/or user account data. User transaction data comprises data associated with financial institution accounts, payment accounts, or the like that may provide information about transactions the user 202 may have completed with a credit card, debit card, or the like. As such, thesecurity application 258 may request or extract transaction data via thenetwork 201. User social networking data is extracted by thesecurity application 258 from social networking sites and includes accessing and extracting information from user social networking sites that may provide an indication of a user 202 being offline from a mobile device for a period of time. User account data is extracted from one or more payment accounts, merchant accounts, rewards accounts, frequent flier accounts, or the like that the user 202 has set up that may provide an indication of one or more offline period. - In some embodiments, the
security application 258 may identify one or more offline time periods for a user's user device 204. As such, thesecurity application 258 reviews the historical user data for indications of future offline periods for a user device 204. While the term historical user data is used throughout this application, one will appreciate that the data may be extracted from one or more sources in real-time or near real-time in order to provide the system with an up to date view of potential offline periods of the user device 204 in the future. In this way, thesecurity application 258 reviews the data extracted from one or more sources to identify potential offline periods of time for the user device 204. These offline periods may include classes, flights, movies, events, plays, or the like that may provide an indication of one or more periods of offline time of the user and his/her mobile device. In some embodiments, the data identified by thesecurity application 258 may specifically indicate the purchase of tickets, passes, or the like for an event that will be an offline period for the user device 204. In other embodiments, the data extracted and identified by thesecurity application 258 may be ancillary data that thesecurity application 258 may combine to provide a confidence level that a specific event will occur and the user device 204 will be offline. - In some embodiments, the
security application 258 may generate a security escalation program. The program for each event requires the generation of rules for that event. Thesecurity application 258 may create the one or more rules for each even that is associated with an offline time period based on the identified reason for the offline time period. As such, the rules may be based on whether the offline time period requires true shut off of the user device 204 or a silencing of the user device 204. Thesecurity application 258 may generate rules for the time period leading up to the offline time period, the offline time period, and a time period after the offline time period. Once the rules are created for the specific event thesecurity application 258 may be stored and utilized in the future for subsequent similar events for other users. - In some embodiments, the
security application 258 generates a security escalation program for a time period leading up to the offline time period based on the reasons for the offline time period. As such, if the offline time includes potential security issues, such as being in a crowded public place, or the like prior to the offline period, thesecurity application 258 may escalate security for one or more applications on the user device 204 during the period of time leading up to the offline period. In this way, thesecurity application 258 may integrate into the user device 204 and may require additional security authorization to allow access to one or more applications on the user device 204. In some embodiments, the security escalation integrated from thesecurity application 258 may target specific applications, such as financial applications or applications with personal information associated therewith. In some embodiments, the security escalation integrated from thesecurity application 258 may apply to all applications. The security escalation may require a user 202 to input additional security information prior to allowing the application functionality. - In some embodiments, the
security application 258 may generate a security escalation program or application shut down program for the offline time period based on the reasons for the offline time period. As such, if it is identified that the user device 204 is going to have an offline time period, such as during a flight, thesecurity application 258 may shut down the functionality of one or more of the applications via integration into the user device 204. In some embodiments, thesecurity application 258 may shut down all applications associated with the user device 204. In some embodiments, thesecurity application 258 may shut down specific applications, such as financial applications or applications with personal information associated therewith associated with the user device 204. In some embodiments, the user 202 may be able to override the shutdown of the applications from thesecurity application 258 via security authorization if needed. - In some embodiments, the
security application 258 may generate a security escalation program for a time period after the offline time period based on reasons for the offline time period. As such, after the offline time period has expired, thesecurity application 258 may restore the application functionality on the user device 204. In some embodiments, thesecurity application 258 may, for a predetermined period of time after the offline period, continue to include escalated security for one or more applications. In some embodiments, the security escalation may target specific applications on the user device 204, such as financial applications or applications with personal information associated therewith. In some embodiments, the security escalation may apply to all applications on the user device 204. The security escalation may require a user 202 to input additional security information on the user device 204 prior to thesecurity application 258 allowing the application functionality. - As illustrated in
FIG. 1 , thenetwork system 206 is connected to theapplication server 208 and is associated with a mobile device network. In this way, while only onenetwork system 206 is illustrated inFIG. 1 , it is understood that multiple network systems may make up thesystem environment 200. Thenetwork system 206 generally comprises acommunication device 236, aprocessing device 238, and amemory device 240. Thenetwork system 206 comprises computer-readable instructions 242 stored in thememory device 240, which in one embodiment includes the computer-readable instructions 242 of anetwork application 244. - It is understood that the servers, systems, and devices described herein illustrate one embodiment of the invention. It is further understood that one or more of the servers, systems, and devices can be combined in other embodiments and still function in the same or similar way as the embodiments described herein.
-
FIG. 2 provides a high level process flow illustrating the passive basedsecurity escalation process 100, in accordance with one embodiment of the present invention. As illustrated inblock 102, theprocess 102 is initiated by extracting historical user data. This historical data may include transaction data, social networking data, or the like. Next, as illustrated inblock 104, theprocess 100 continues by identifying potential offline periods of time the user may have in the future based on the historical user data. In this way, the system may identify based on user data, such as transaction data, social media data, or the like, potential future periods of time that the user may be offline with his/her mobile device. Offline periods may include flights, meetings, classes, or the like when a user may have his/her mobile device turned off. Identifying the offline periods includes identifying airline tickets purchased, books for classes, or the like via transaction data and/or reviewing social networking data for indications of vacations, meetings, or other indicators suggesting the user may have his/her mobile device turned off. - As illustrated in
block 106, the system may generate rules for security of mobile applications before, during, and/or after the identified offline time periods. These rules may include a security level for before, during, and/or after the offline time period. For before and after the offline time period, the system may generate rules for requiring additional security authentication for one or more applications on the user's mobile device. For the offline time periods, the system may shut off functionality of one or more applications on the user's mobile device. In this way, in public places or while the user is not online with the mobile device, the user is provided additional misappropriation protection. - Once the rules are generated in
block 106, theprocess 100 continues by increasing the mobile application security leading up to the offline time period based on the rules associated with the identified offline time period, as illustrated inblock 108. In this way, some embodiments may require additional security authentication for one or more selected applications. In other embodiments, additional security authentication for all applications may be implemented. - As illustrated in
block 110, the system may temporarily shut down the mobile application functions of one or more applications based on the rules. The applications may be shut off or shut down from access for the duration of the offline time period. As such, the system may not allow access from any location to applications on the mobile device during the offline period. Once, the system determines that the offline period is over based on a determination of the time frame of the offline time period based on the user historical data, the system may restore the mobile applications once the offline tie period has passed, as illustrated inblock 112. -
FIG. 3 illustrates a process map for extracting historical data for the passive basedsecurity escalation system 400, in accordance with one embodiment of the present invention. As illustrated inblock 402, theprocess 400 is initiated by the system extracting historical user data. The historical user data extracted inblock 402 may include user transaction data 403, usersocial network data 405, anduser account data 407. In some embodiments, the user data may be user transaction data 403. User transaction data 403 comprises accessing and extracting information from financial institutions or the like that has information about transactions the user may have completed with a credit card, debit card, or the like. As such, the system may identify if the user has purchased books, airline tickets, or the like that may be associated with an offline time period of the user's mobile device. Usersocial networking data 405 comprises accessing and extracting information from user social networking sites that may provide an indication of a user being offline from a mobile device for a period of time.User account data 407 is data extracted from one or more payment accounts, merchant accounts, rewards accounts, frequent flier accounts, or the like that the user has set up that may provide an indication of one or more offline periods. For example, a user may have an account with a movie theater for purchasing movie tickets, the system may identify the account and movies that the user may attend, thus leading to offline periods. In another example, the system may identify that the user has a frequent flyer account with an airline, based on this account the system may be able to identify one or more upcoming flights that the user may have, which will lead to offline time periods for the user during the flight. - Next, the
process 400 continues when the system gathers the extracted historical user data fromblock 402 and reviews the historical user data for indications of future offline periods for a user's mobile devices, as illustrated inblock 404. While the term historical user data is used throughout this application, one will appreciate that the data may be extracted from one or more sources in real-time or near real-time in order to provide the system with an up to date view of potential offline periods of the user in the future. In this way, the system may review the data extracted from one or more sources to identify potential offline periods of time for the user's mobile device. These offline periods may include classes, flights, movies, events, plays, or the like that may provide an indication of one or more periods of offline time of the user and his/her mobile device. In some embodiments, the data extracted may specifically indicate the purchase of tickets, passes, or the like for an event that will be an offline period for the user's mobile device. In other embodiments, the data extracted may be ancillary data that the system may combine to provide a confidence level that a specific event will occur and the user's mobile device will be offline. For example, ancillary data may include the purchase of books and school supplies from one source and a social networking trend indicating the user is attending a class or school. As such, in some embodiments, the data may be extracted from various sources, but be combined to provide a confidence that one or more of the events that may lead to an offline time period of the user's mobile device may occur. - As illustrated in
block 406, once the system has reviewed the historical user data and identified future offline periods of a user's mobile device, the system may next predict the duration of the offline time period. In some embodiments, the system may use the data extracted to identify that a flight, event ticket or the like has been purchased. Subsequently, the system may access the airline or the event venue and determine a duration of the event such that the system may only initiate shut off of the application functionality during that event. Once the predicted offline time is identified and the time frame of the offline time is predicted, the system may store the data for passive based security escalation, as illustrated inblock 408. The storing may include a triggering of the passive based security escalation at a specific time period prior to the offline time period. As such, as illustrated inblock 410, theprocess 400 is completed by initiating the passive based security escalation upon identifying the upcoming predicted offline time period and/or a triggering time prior to the offline time period. -
FIG. 4 illustrates a process map for generating rules for the passive basedsecurity escalation system 500, in accordance with one embodiment of the present invention. As illustrated inblock 502, theprocess 500 is initiated by creating one or more rules for each offline time period based on the identified reason for the offline time period. As such, the rules may be based on whether the offline time period requires a true shut off of the mobile device or a silencing of the mobile device. In some embodiments, the offline time period may be a complete turn off of the mobile device, such as on a flight or the like. In some embodiments, the offline time period may be a period of inactivity when the mobile device may be silent, such as at an event, in a meeting, or the like. Furthermore, the rules may be based on how public the location is with respect to the offline time and/or the time leading up to the offline time. - Once the rules are created for the specific event they may be stored and utilized in the future for subsequent similar events for other users. Once created, the system may then generate a security escalation program for the event, thus for the time period leading up to the offline time period, the offline time period, and a time period after the offline time period.
- As such, as illustrated in
block 504, theprocess 500 continues by generating a security escalation program for a time period leading up to the offline time period based on the reasons for the offline time period. As such, if the offline time includes potential security issues, such as being in a crowded public place, or the like prior to the offline period, the system may escalate security for one or more applications on the mobile device during the period of time leading up to the offline period. In this way, the system may require additional security authorization to allow access to one or more applications with financial information, personal information, or the like. In some embodiments, the security escalation may target specific applications, such as financial applications or applications with personal information associated therewith. In some embodiments, the security escalation may apply to all applications. The security escalation may require a user to input additional security information prior to allowing the application functionality. - Next, as illustrated in
block 506, the system may generate a security escalation program or application shut down program for the offline time period based on the reasons for the offline time period. As such, if the user is going to have an offline time period, such as during a flight, the system may shut down the functionality of one or more of the applications. Thus, once the offline time period has begun, the system may shut down one or more applications based on the rules. In this way, the user has the additional security of the application being shut down and thus, no one has the ability to access the applications or user data for misappropriation. In some embodiments, the system may shut down all applications associated with the user's mobile device. In some embodiments, the system may shut down specific applications, such as financial applications or applications with personal information associated therewith. In some embodiments, the user may be able to override the shutdown of the applications via security authorization if needed. - Next, as illustrated in
block 508, theprocess 500 continues by generating a security escalation program for a time period after the offline time period based on reasons for the offline time period. Thus, after the offline time period has expired, the system may restore the application functionality. In some embodiments, the system may, for a predetermined period of time after the offline period, continue to include escalated security for one or more applications. In some embodiments, the security escalation may target specific applications, such as financial applications or applications with personal information associated therewith. In some embodiments, the security escalation may apply to all applications. The security escalation may require a user to input additional security information prior to allowing the application functionality. - Finally, as illustrated on
block 510, the system may store the generated security escalation program for the event associated with the rules for each reason for an offline time period. In this way, the system may build a database of rules and escalation parameters for each of the potential events leading to an offline time period. The system may continually learn and adjust the security escalation programs for each event based on prior events and prior programs generated. -
FIG. 5 illustrates a process map of an example of the passive basedsecurity escalation system 300, in accordance with one embodiment of the present invention. As illustrated inblock 302, theprocess 300 is initiated by the identification of travel plans of the user from extracted historical user data. In this way, the system may have identified and extracted the data from a user account, such as a frequent flyer account or the like, user transaction history, such as credit card data from a financial institution, and/or from user social network data, such as from a post or blog from the user indicating travel plans. In some embodiments, one data source may have been used to identify travel plans of the user. In some embodiments, a combination of one or more data sources may have been used to identify travel plans of the user. Once identified, the system may generate a confidence score, indicating a confidence of the travel plans being authentic. - Next, once the travel plans of the user have been identified based on the historical user data, the system may identify the actual duration of offline time of a mobile device associated with the user, as illustrated in
block 304. In this way, the system may reach out to external sources to determine a duration of the event leading to the offline time period. In this example, the system may reach out to the airlines to determine the duration of the flight of the user. - Once the system has identified that the user has travel plans associated with flying, where there is an offline period associated with the travel plans, such as being in the airplane in flight and once the system has identified the duration of those plans, the system may begin to map and generate a security escalation program for the travel, as illustrated in
block 306. The security escalation program may include a selection of all or some applications for security escalation prior to and after the offline time period and a selection of all or some applications for security escalation or application shut off during the offline time period. - In the example illustrated in
FIG. 5 , the system may identify the time period the user may be at the airport prior to and after the flight. In this way, the system may identify security escalations that may require additional authorization or passwords for access to one or more applications on the user's mobile device while he/she is at the airport. The applications associated with the security escalation may include any that has financial or personal information about the user. In other embodiments, all applications on the mobile device may be associated with security escalations. - As illustrated in
block 308, the process may continue by increasing mobile application security parameters during the user's time in the airport or other public place associated with the user's travel plans. As such, the system may require additional security authorization or password protection for accessing application functionality during time periods prior to the user's flight. The applications associated with the security escalation may include any that has financial or personal information about the user. In other embodiments, all applications on the mobile device may be associated with security escalations. - As illustrated in
block 310, once the system is triggered that the offline period of time has begun, the system may temporarily shut down mobile application functionality during the flight. This application functionality that is shut down may be directed specifically to one or more mobile devices identified as being associated with the user and/or on the flight with the user. - Once the offline time period has passed, the system may reinstate mobile application functionality to the user's mobile device with increased security parameters, as illustrated in
block 312. In thisexample process 300, once the system identifies that the user's airplane has landed at the second airport, the mobile application functionality is reinstated. In some embodiments, the system may, for a predetermined period of time after the offline period, continue to include escalated security for one or more applications. In some embodiments, the security escalation may target specific applications, such as financial applications or applications with personal information associated therewith. In some embodiments, the security escalation may apply to all applications. The security escalation may require a user to input additional security information prior to allowing the application functionality. - Finally, as illustrated in
block 314, theprocess 300 is completed by restoring full mobile application functionality after the user has left the airport or public place associated with travel plans. - As will be appreciated by one of ordinary skill in the art, the present invention may be embodied as an apparatus (including, for example, a system, a machine, a device, a computer program product, and/or the like), as a method (including, for example, a business process, a computer-implemented process, and/or the like), or as any combination of the foregoing. Accordingly, embodiments of the present invention may take the form of an entirely software embodiment (including firmware, resident software, micro-code, and the like), an entirely hardware embodiment, or an embodiment combining software and hardware aspects that may generally be referred to herein as a “system.” Furthermore, embodiments of the present invention may take the form of a computer program product that includes a computer-readable storage medium having computer-executable program code portions stored therein. As used herein, a processor may be “configured to” perform a certain function in a variety of ways, including, for example, by having one or more special-purpose circuits perform the functions by executing one or more computer-executable program code portions embodied in a computer-readable medium, and/or having one or more application-specific circuits perform the function. As such, once the software and/or hardware of the claimed invention is implemented the computer device and application-specific circuits associated therewith are deemed specialized computer devices capable of improving technology associated with the in authorization and instant integration of a new credit card to digital wallets.
- It will be understood that any suitable computer-readable medium may be utilized. The computer-readable medium may include, but is not limited to, a non-transitory computer-readable medium, such as a tangible electronic, magnetic, optical, infrared, electromagnetic, and/or semiconductor system, apparatus, and/or device. For example, in some embodiments, the non-transitory computer-readable medium includes a tangible medium such as a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a compact disc read-only memory (CD-ROM), and/or some other tangible optical and/or magnetic storage device. In other embodiments of the present invention, however, the computer-readable medium may be transitory, such as a propagation signal including computer-executable program code portions embodied therein.
- It will also be understood that one or more computer-executable program code portions for carrying out the specialized operations of the present invention may be required on the specialized computer include object-oriented, scripted, and/or unscripted programming languages, such as, for example, Java, Perl, Smalltalk, C++, SAS, SQL, Python, Objective C, and/or the like. In some embodiments, the one or more computer-executable program code portions for carrying out operations of embodiments of the present invention are written in conventional procedural programming languages, such as the “C” programming languages and/or similar programming languages. The computer program code may alternatively or additionally be written in one or more multi-paradigm programming languages, such as, for example, F#.
- It will further be understood that some embodiments of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of systems, methods, and/or computer program products. It will be understood that each block included in the flowchart illustrations and/or block diagrams, and combinations of blocks included in the flowchart illustrations and/or block diagrams, may be implemented by one or more computer-executable program code portions. These one or more computer-executable program code portions may be provided to a processor of a special purpose computer for the authorization and instant integration of credit cards to a digital wallet, and/or some other programmable data processing apparatus in order to produce a particular machine, such that the one or more computer-executable program code portions, which execute via the processor of the computer and/or other programmable data processing apparatus, create mechanisms for implementing the steps and/or functions represented by the flowchart(s) and/or block diagram block(s).
- It will also be understood that the one or more computer-executable program code portions may be stored in a transitory or non-transitory computer-readable medium (e.g., a memory, and the like) that can direct a computer and/or other programmable data processing apparatus to function in a particular manner, such that the computer-executable program code portions stored in the computer-readable medium produce an article of manufacture, including instruction mechanisms which implement the steps and/or functions specified in the flowchart(s) and/or block diagram block(s).
- The one or more computer-executable program code portions may also be loaded onto a computer and/or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer and/or other programmable apparatus. In some embodiments, this produces a computer-implemented process such that the one or more computer-executable program code portions which execute on the computer and/or other programmable apparatus provide operational steps to implement the steps specified in the flowchart(s) and/or the functions specified in the block diagram block(s). Alternatively, computer-implemented steps may be combined with operator and/or human-implemented steps in order to carry out an embodiment of the present invention.
- While certain exemplary embodiments have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative of, and not restrictive on, the broad invention, and that this invention not be limited to the specific constructions and arrangements shown and described, since various other changes, combinations, omissions, modifications and substitutions, in addition to those set forth in the above paragraphs, are possible. Those skilled in the art will appreciate that various adaptations and modifications of the just described embodiments can be configured without departing from the scope and spirit of the invention. Therefore, it is to be understood that, within the scope of the appended claims, the invention may be practiced other than as specifically described herein.
- To supplement the present disclosure, this application further incorporates entirely by reference the following commonly assigned patent applications:
-
U.S. Patent Appli- cation Filed Docket Number Ser. No. Title On 6017US1CIP1.014033.2560 To be DETERMINING Concur- assigned USER rently AUTHENTICATION here- BASED ON USER/ with DEVICE INTERACTION 6017US1CIP2.014033.2561 To be DETERMINING Concur- assigned USER rently AUTHENTICATION here- BASED ON USER with PATTERNS WITHIN APPLICATION 6930US1.014033.2563 To be PERMANENTLY Concur- assigned AFFIXED UN- rently DECRYPTABLE here- IDENTIFIER with ASSOCIATED WITH MOBILE DEVICE 6932US1.014033.2564 To be INTEGRATED FULL Concur- assigned AND PARTIAL rently SHUTDOWN here- APPLICATION with PROGRAMMING INTERFACE 6933US1.014033.2565 To be TIERED Concur- assigned IDENTIFICATION rently FEDERATED here- AUTHENTICATION with NETWORK SYSTEM
Claims (20)
1. A system for passive based security escalation implementation on a mobile device, the system comprising:
a memory device with computer-readable program code stored thereon;
a communication device;
a processing device operatively coupled to the memory device and the communication device, wherein the processing device is configured to execute the computer-readable program code to:
extract historical user data associated with a user from one or more external sources;
identify from the historical user data, one or more indications of offline periods of time for the mobile device associated with the user, wherein the identified indications include one or more events that the user is attending at a future time;
generate a security escalation plan for the event;
access and integrate into the mobile device an increase to security requirements for authorizing one or more applications on the mobile device based on a triggering of a time period leading up to the event;
integrate into the mobile device a shutdown of the one or more applications on the mobile device during the offline period of time for the mobile device during the event;
restore functionality of the one or more applications after the offline period of time for the mobile device with an increase to the security requirements for authorizing the one or more applications on the mobile device based on a triggering of a time period after the offline time period associated with the event; and
restore standard security requirements of the one or more applications.
2. The system of claim 1 , wherein integrating into the mobile device the shutdown of the one or more applications on the mobile device further comprises shutting down the functionality of the one or more applications such that external devices cannot activate the one or more applications during the offline period of time.
3. The system of claim 1 , wherein the increase security requirements for authorizing one or more applications on the mobile device, further comprises increasing the security requirements to one or more applications that contain financial data and personal data of the user, wherein the increased security requirements include requiring additional authentication to allow access to the one or more applications via the mobile device.
4. The system of claim 1 , wherein generating a security escalation plan for the event further comprises generating rules for security level requirements for each event and security level requirements for a time period prior to and after a duration of the event.
5. The system of claim 1 , wherein indications of offline periods of time for the mobile device associated with the user further comprise an indication of a purchase of a ticket or pass to the event.
6. The system of claim 5 , wherein the event comprises an airplane flight.
7. The system of claim 1 , further comprising identifying a duration of the offline period based on a request for the duration from a venue of the event.
8. The system of claim 1 , wherein historical user data comprises user transaction data extracted from a financial institution, user social network data extracted from a social networking website, and user account data extracted from one or more merchants.
9. A computer program product for passive based security escalation implementation on a mobile device, the computer program product comprising at least one non-transitory computer-readable medium having computer-readable program code portions embodied therein, the computer-readable program code portions comprising:
an executable portion configured for extracting historical user data associated with a user from one or more external sources;
an executable portion configured for identifying from the historical user data, one or more indications of offline periods of time for the mobile device associated with the user, wherein the identified indications include one or more events that the user is attending at a future time;
an executable portion configured for generating a security escalation plan for the event;
an executable portion configured for accessing and integrating into the mobile device an increase to security requirements for authorizing one or more applications on the mobile device based on a triggering of a time period leading up to the event;
an executable portion configured for integrating into the mobile device a shutdown of the one or more applications on the mobile device during the offline period of time for the mobile device during the event;
an executable portion configured for restoring functionality of the one or more applications after the offline period of time for the mobile device with an increase to the security requirements for authorizing the one or more applications on the mobile device based on a triggering of a time period after the offline time period associated with the event;
an executable portion configured for restoring standard security requirements of the one or more applications.
10. The computer program product of claim 9 , wherein integrating into the mobile device the shutdown of the one or more applications on the mobile device further comprises shutting down the functionality of the one or more applications such that external devices cannot activate the one or more applications during the offline period of time.
11. The computer program product of claim 9 , wherein the increase security requirements for authorizing one or more applications on the mobile device, further comprises increasing the security requirements to one or more applications that contain financial data and personal data of the user, wherein the increased security requirements include requiring additional authentication to allow access to the one or more applications via the mobile device.
12. The computer program product of claim 9 , wherein generating a security escalation plan for the event further comprises generating rules for security level requirements for each event and security level requirements for a time period prior to and after a duration of the event.
13. The computer program product of claim 9 , wherein indications of offline periods of time for the mobile device associated with the user further comprise an indication of a purchase of a ticket or pass to the event.
14. The computer program product of claim 13 , wherein the event comprises an airplane flight.
15. The computer program product of claim 9 , further comprising an executable portion configured for identifying a duration of the offline period based on a request for the duration from a venue of the event.
16. The computer program product of claim 9 , wherein historical user data comprises user transaction data extracted from a financial institution, user social network data extracted from a social networking website, and user account data extracted from one or more merchants.
17. A computer-implemented method for passive based security escalation implementation on a mobile device, the method comprising:
providing a computing system comprising a computer processing device and a non-transitory computer readable medium, where the computer readable medium comprises configured computer program instruction code, such that when said instruction code is operated by said computer processing device, said computer processing device performs the following operations:
extracting historical user data associated with a user from one or more external sources;
identifying from the historical user data, one or more indications of offline periods of time for the mobile device associated with the user, wherein the identified indications include one or more events that the user is attending at a future time;
generating a security escalation plan for the event;
accessing and integrating into the mobile device an increase to security requirements for authorizing one or more applications on the mobile device based on a triggering of a time period leading up to the event;
integrating into the mobile device a shutdown of the one or more applications on the mobile device during the offline period of time for the mobile device during the event;
restoring functionality of the one or more applications after the offline period of time for the mobile device with an increase to the security requirements for authorizing the one or more applications on the mobile device based on a triggering of a time period after the offline time period associated with the event; and
restoring standard security requirements of the one or more applications.
18. The computer-implemented method of claim 17 , wherein integrating into the mobile device the shutdown of the one or more applications on the mobile device further comprises shutting down the functionality of the one or more applications such that external devices cannot activate the one or more applications during the offline period of time.
19. The computer-implemented method of claim 17 , wherein the increase security requirements for authorizing one or more applications on the mobile device, further comprises increasing the security requirements to one or more applications that contain financial data and personal data of the user, wherein the increased security requirements include requiring additional authentication to allow access to the one or more applications via the mobile device.
20. The computer-implemented method of claim 17 , wherein generating a security escalation plan for the event further comprises generating rules for security level requirements for each event and security level requirements for a time period prior to and after a duration of the event.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/928,154 US9641539B1 (en) | 2015-10-30 | 2015-10-30 | Passive based security escalation to shut off of application based on rules event triggering |
US15/460,951 US9794299B2 (en) | 2015-10-30 | 2017-03-16 | Passive based security escalation to shut off of application based on rules event triggering |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/928,154 US9641539B1 (en) | 2015-10-30 | 2015-10-30 | Passive based security escalation to shut off of application based on rules event triggering |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/460,951 Continuation US9794299B2 (en) | 2015-10-30 | 2017-03-16 | Passive based security escalation to shut off of application based on rules event triggering |
Publications (2)
Publication Number | Publication Date |
---|---|
US9641539B1 US9641539B1 (en) | 2017-05-02 |
US20170126693A1 true US20170126693A1 (en) | 2017-05-04 |
Family
ID=58615730
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/928,154 Active 2035-12-13 US9641539B1 (en) | 2015-10-30 | 2015-10-30 | Passive based security escalation to shut off of application based on rules event triggering |
US15/460,951 Active US9794299B2 (en) | 2015-10-30 | 2017-03-16 | Passive based security escalation to shut off of application based on rules event triggering |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/460,951 Active US9794299B2 (en) | 2015-10-30 | 2017-03-16 | Passive based security escalation to shut off of application based on rules event triggering |
Country Status (1)
Country | Link |
---|---|
US (2) | US9641539B1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20180040036A1 (en) * | 2016-08-04 | 2018-02-08 | Samsung Electronics Co., Ltd. | Offline Cards |
US11190537B2 (en) * | 2019-06-18 | 2021-11-30 | International Business Machines Corporation | Vulnerability management of disconnected endpoints |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9760116B2 (en) | 2012-12-05 | 2017-09-12 | Mobile Tech, Inc. | Docking station for tablet device |
US10251144B2 (en) | 2015-12-03 | 2019-04-02 | Mobile Tech, Inc. | Location tracking of products and product display assemblies in a wirelessly connected environment |
US10517056B2 (en) | 2015-12-03 | 2019-12-24 | Mobile Tech, Inc. | Electronically connected environment |
US11109335B2 (en) | 2015-12-03 | 2021-08-31 | Mobile Tech, Inc. | Wirelessly connected hybrid environment of different types of wireless nodes |
US10728868B2 (en) | 2015-12-03 | 2020-07-28 | Mobile Tech, Inc. | Remote monitoring and control over wireless nodes in a wirelessly connected environment |
US10168696B2 (en) * | 2016-03-31 | 2019-01-01 | International Business Machines Corporation | Dynamic analysis of real-time restrictions for remote controlled vehicles |
US10101770B2 (en) | 2016-07-29 | 2018-10-16 | Mobile Tech, Inc. | Docking system for portable computing device in an enclosure |
US11075946B2 (en) * | 2017-12-19 | 2021-07-27 | T-Mobile Usa, Inc. | Honeypot adaptive security system |
US20210055902A1 (en) * | 2018-03-30 | 2021-02-25 | Mobile Tech, Inc. | Wirelessly connected environment of wireless nodes |
US20220070620A1 (en) | 2018-10-25 | 2022-03-03 | Mobile Tech, Inc | Proxy nodes for expanding the functionality of nodes in a wirelessly connected environment |
US10614682B1 (en) | 2019-01-24 | 2020-04-07 | Mobile Tech, Inc. | Motion sensing cable for tracking customer interaction with devices |
Family Cites Families (160)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3256670A (en) | 1962-07-23 | 1966-06-21 | Tersigni Ennio | Prefabricated steel joist adapted for the reinforcement of floors |
DE1643735A1 (en) | 1968-01-09 | 1971-07-15 | Basf Ag | Process for the production of heptenes |
US5437346A (en) | 1994-05-11 | 1995-08-01 | Dumont; Charles | Station for price scanning verifying and selectively bagging purchase items |
US6058420A (en) | 1998-02-27 | 2000-05-02 | Netsolve, Inc. | Alarm server systems, apparatus, and processes |
PT1080415T (en) | 1998-05-21 | 2017-05-02 | Equifax Inc | System and method for authentication of network users |
US7783299B2 (en) | 1999-01-08 | 2010-08-24 | Trueposition, Inc. | Advanced triggers for location-based service applications in a wireless location system |
US6651168B1 (en) | 1999-01-29 | 2003-11-18 | International Business Machines, Corp. | Authentication framework for multiple authentication processes and mechanisms |
US7239226B2 (en) | 2001-07-10 | 2007-07-03 | American Express Travel Related Services Company, Inc. | System and method for payment using radio frequency identification in contact and contactless transactions |
US7260724B1 (en) | 1999-09-20 | 2007-08-21 | Security First Corporation | Context sensitive dynamic authentication in a cryptographic system |
US7231202B2 (en) | 1999-12-10 | 2007-06-12 | Ntt Docomo, Inc. | Method for inhibiting use of mobile communication terminal having memory where card information is stored, mobile communication network, and mobile communication terminal |
US20020111907A1 (en) | 2000-01-26 | 2002-08-15 | Ling Marvin T. | Systems and methods for conducting electronic commerce transactions requiring micropayment |
US7441263B1 (en) | 2000-03-23 | 2008-10-21 | Citibank, N.A. | System, method and computer program product for providing unified authentication services for online applications |
JP3498678B2 (en) | 2000-05-31 | 2004-02-16 | 日本電気株式会社 | Pipeline processing type shaping apparatus and method |
US10185936B2 (en) | 2000-06-22 | 2019-01-22 | Jpmorgan Chase Bank, N.A. | Method and system for processing internet payments |
WO2002001376A1 (en) | 2000-06-28 | 2002-01-03 | Yozan Inc. | Host computer, mobile communication device, program, and recording medium |
US7487112B2 (en) | 2000-06-29 | 2009-02-03 | Barnes Jr Melvin L | System, method, and computer program product for providing location based services and mobile e-commerce |
US7428411B2 (en) | 2000-12-19 | 2008-09-23 | At&T Delaware Intellectual Property, Inc. | Location-based security rules |
US7340438B2 (en) | 2001-05-21 | 2008-03-04 | Nokia Corporation | Method and apparatus for managing and enforcing user privacy |
US20020186845A1 (en) | 2001-06-11 | 2002-12-12 | Santanu Dutta | Method and apparatus for remotely disabling and enabling access to secure transaction functions of a mobile terminal |
US7111323B1 (en) | 2001-08-31 | 2006-09-19 | Oracle International Corporation | Method and apparatus to facilitate a global timeout in a distributed computing environment |
US7373515B2 (en) | 2001-10-09 | 2008-05-13 | Wireless Key Identification Systems, Inc. | Multi-factor authentication system |
JP4082028B2 (en) | 2001-12-28 | 2008-04-30 | ソニー株式会社 | Information processing apparatus, information processing method, and program |
US7697920B1 (en) | 2006-05-05 | 2010-04-13 | Boojum Mobile | System and method for providing authentication and authorization utilizing a personal wireless communication device |
JP4612416B2 (en) | 2002-08-09 | 2011-01-12 | ヴィスト・コーポレーション | System and method for preventing access to data on compromised remote devices |
US7546276B2 (en) | 2006-01-23 | 2009-06-09 | Randle William M | Common authentication service for network connected applications, devices, users, and web services |
US7599287B2 (en) | 2002-11-15 | 2009-10-06 | Cisco Technology, Inc. | Tokens in token buckets maintained among primary and secondary storages |
FR2867881B1 (en) | 2004-03-17 | 2006-06-30 | Sagem | METHOD FOR CONTROLLING IDENTIFICATION OF PERSONS AND SYSTEM FOR IMPLEMENTING THE METHOD |
US7783281B1 (en) | 2004-04-22 | 2010-08-24 | Sprint Spectrum L.P. | Method and system for securing a mobile device |
US7467401B2 (en) | 2004-08-12 | 2008-12-16 | Avatier Corporation | User authentication without prior user enrollment |
EP1829283A2 (en) | 2004-12-20 | 2007-09-05 | Proxense, LLC | Biometric personal data key (pdk) authentication |
US7738382B2 (en) | 2004-12-21 | 2010-06-15 | Cisco Technology, Inc. | Hierarchical multi-rate multi-precedence policer |
US8768838B1 (en) | 2005-02-02 | 2014-07-01 | Nexus Payments, LLC | Financial transactions using a rule-module nexus and a user account registry |
EP1708527A1 (en) | 2005-03-31 | 2006-10-04 | BRITISH TELECOMMUNICATIONS public limited company | Location based authentication |
US7630924B1 (en) | 2005-04-20 | 2009-12-08 | Authorize.Net Llc | Transaction velocity counting for fraud detection |
EP1725056B1 (en) | 2005-05-16 | 2013-01-09 | Sony Ericsson Mobile Communications AB | Method for disabling a mobile device |
CA2518010A1 (en) | 2005-09-01 | 2007-03-01 | Davis + Henderson, Limited Partnership | Method and system for assisting a client in the transfer of usage of accounts at one or more financial institutions |
US20070094152A1 (en) | 2005-10-20 | 2007-04-26 | Bauman Brian D | Secure electronic transaction authentication enhanced with RFID |
US8104081B2 (en) | 2005-11-15 | 2012-01-24 | Avaya Inc. | IP security with seamless roaming and load balancing |
CN1992596A (en) | 2005-12-27 | 2007-07-04 | 国际商业机器公司 | User authentication device and method |
US7716180B2 (en) | 2005-12-29 | 2010-05-11 | Amazon Technologies, Inc. | Distributed storage system with web services client interface |
US8290433B2 (en) | 2007-11-14 | 2012-10-16 | Blaze Mobile, Inc. | Method and system for securing transactions made through a mobile communication device |
US8352323B2 (en) | 2007-11-30 | 2013-01-08 | Blaze Mobile, Inc. | Conducting an online payment transaction using an NFC enabled mobile communication device |
US7698443B2 (en) | 2006-03-02 | 2010-04-13 | International Business Machines Corporation | Multi-protocol authentication and authorization in computer network environments |
US7739280B2 (en) | 2006-03-06 | 2010-06-15 | Veveo, Inc. | Methods and systems for selecting and presenting content based on user preference information extracted from an aggregate preference signature |
US9817963B2 (en) | 2006-04-10 | 2017-11-14 | International Business Machines Corporation | User-touchscreen interaction analysis authentication system |
US7693771B1 (en) | 2006-04-14 | 2010-04-06 | Intuit Inc. | Method and apparatus for identifying recurring payments |
US7552467B2 (en) | 2006-04-24 | 2009-06-23 | Jeffrey Dean Lindsay | Security systems for protecting an asset |
US7895646B2 (en) | 2006-05-25 | 2011-02-22 | International Business Machines Corporation | IKE daemon self-adjusting negotiation throttle |
US20070100773A1 (en) | 2006-08-11 | 2007-05-03 | Regions Asset Company | Transaction security system having user defined security parameters |
GB0621189D0 (en) | 2006-10-25 | 2006-12-06 | Payfont Ltd | Secure authentication and payment system |
US8838481B2 (en) | 2011-07-26 | 2014-09-16 | Golba Llc | Method and system for location based hands-free payment |
US8838477B2 (en) | 2011-06-09 | 2014-09-16 | Golba Llc | Method and system for communicating location of a mobile device for hands-free payment |
US20080167965A1 (en) | 2007-01-09 | 2008-07-10 | Von Nothaus Bernard | Apparatus, system, and method for extracting real world value from a virtual account |
US8270995B1 (en) | 2007-04-26 | 2012-09-18 | Nextel Communications, Inc. | Composite application for group-based activity reservations |
US7988045B2 (en) | 2007-05-31 | 2011-08-02 | International Business Machines Corporation | Portable device-based shopping checkout |
US7739169B2 (en) | 2007-06-25 | 2010-06-15 | Visa U.S.A. Inc. | Restricting access to compromised account information |
US8230490B2 (en) | 2007-07-31 | 2012-07-24 | Keycorp | System and method for authentication of users in a secure computer system |
EP2176808A2 (en) | 2007-08-01 | 2010-04-21 | Nxp B.V. | Mobile communication device and method for disabling applications |
US8950001B2 (en) | 2007-08-01 | 2015-02-03 | Avaya Inc. | Continual peer authentication |
US20090076965A1 (en) | 2007-09-17 | 2009-03-19 | Microsoft Corporation | Counteracting random guess attacks against human interactive proofs with token buckets |
US20090100060A1 (en) | 2007-10-11 | 2009-04-16 | Noam Livnat | Device, system, and method of file-utilization management |
US20090119170A1 (en) | 2007-10-25 | 2009-05-07 | Ayman Hammad | Portable consumer device including data bearing medium including risk based benefits |
KR20090056908A (en) | 2007-11-29 | 2009-06-03 | 삼성전자주식회사 | Method for destructive readout of data in case of mobile theft |
US7930264B2 (en) | 2007-12-06 | 2011-04-19 | First Data Corporation | Multi-module authentication platform |
US20090150286A1 (en) | 2007-12-10 | 2009-06-11 | Blain Barton | Point of sale automatic savings program contribution system using biometrics payment and authentication with smart cards, electronic payment, and wireless mechanisms |
US20100049615A1 (en) | 2008-01-24 | 2010-02-25 | Qualcomm Incorporated | Mobile commerce authentication and authorization system |
US7472081B1 (en) | 2008-01-27 | 2008-12-30 | International Business Machines Corporation | Method for shopping using wireless communication |
US8635662B2 (en) | 2008-01-31 | 2014-01-21 | Intuit Inc. | Dynamic trust model for authenticating a user |
US20090217346A1 (en) | 2008-02-22 | 2009-08-27 | Manring Bradley A C | Dhcp centric network access management through network device access control lists |
US8261093B1 (en) | 2008-03-27 | 2012-09-04 | Mcafee, Inc. | System, method, and computer program product for disabling a communication channel during authentication |
WO2009139928A2 (en) | 2008-05-16 | 2009-11-19 | The United States Of America As Represented By The Secretary Of The Navy | Recombinant chimeric antigens for diagnosis and prevention of scrub typhus |
US8201232B2 (en) | 2008-06-26 | 2012-06-12 | Samsung Electronics Co., Ltd. | Authentication, identity, and service management for computing and communication systems |
CN101631290B (en) * | 2008-07-16 | 2012-09-19 | 鸿富锦精密工业(深圳)有限公司 | Mobile communication system and key setting method thereof |
US8295898B2 (en) | 2008-07-22 | 2012-10-23 | Bank Of America Corporation | Location based authentication of mobile device transactions |
DE102008035391A1 (en) | 2008-07-29 | 2010-02-04 | Deutsche Telekom Ag | Procedure for authentication |
US8095112B2 (en) * | 2008-08-21 | 2012-01-10 | Palo Alto Research Center Incorporated | Adjusting security level of mobile device based on presence or absence of other mobile devices nearby |
US8156335B2 (en) | 2008-09-02 | 2012-04-10 | F2Ware, Inc. | IP address secure multi-channel authentication for online transactions |
US8307412B2 (en) | 2008-10-20 | 2012-11-06 | Microsoft Corporation | User authentication management |
US8281379B2 (en) | 2008-11-13 | 2012-10-02 | Vasco Data Security, Inc. | Method and system for providing a federated authentication service with gradual expiration of credentials |
US8483194B1 (en) | 2009-01-21 | 2013-07-09 | Aerohive Networks, Inc. | Airtime-based scheduling |
US8312157B2 (en) | 2009-07-16 | 2012-11-13 | Palo Alto Research Center Incorporated | Implicit authentication |
US9424368B2 (en) | 2009-09-18 | 2016-08-23 | International Business Machines Corporation | Storing and retrieving tags |
US10438194B2 (en) | 2009-10-27 | 2019-10-08 | Ncr Corporation | Methods and apparatus for stored value token creation |
US20110137804A1 (en) | 2009-12-03 | 2011-06-09 | Recursion Software, Inc. | System and method for approving transactions |
US8280791B2 (en) | 2009-12-08 | 2012-10-02 | At&T Mobility Ii Llc | Devices, systems and methods for identifying and/or billing an individual in a vehicle |
US8412626B2 (en) | 2009-12-10 | 2013-04-02 | Boku, Inc. | Systems and methods to secure transactions via mobile devices |
US20110142234A1 (en) | 2009-12-15 | 2011-06-16 | Michael Leonard Rogers | Multi-Factor Authentication Using a Mobile Phone |
US20100100897A1 (en) | 2009-12-18 | 2010-04-22 | Manuel-Devadoss Johson Smith J | Method and system to provide live entertainment digital content to the home viewers |
US8649766B2 (en) | 2009-12-30 | 2014-02-11 | Securenvoy Plc | Authentication apparatus |
US9729930B2 (en) | 2010-01-05 | 2017-08-08 | CSC Holdings, LLC | Enhanced subscriber authentication using location tracking |
US20110166992A1 (en) | 2010-01-06 | 2011-07-07 | Firethorn Holdings, Llc | System and method for creating and managing a stored value account associated with a client unique identifier |
WO2011103432A2 (en) | 2010-02-19 | 2011-08-25 | Finshphere Corporation | System and method for financial transaction authentication using travel information |
US8380177B2 (en) | 2010-04-09 | 2013-02-19 | Paydiant, Inc. | Mobile phone payment processing methods and systems |
US9286733B2 (en) | 2010-04-13 | 2016-03-15 | Locomobi Inc. | Location based systems for entry and exit |
US20110270618A1 (en) | 2010-04-30 | 2011-11-03 | Bank Of America Corporation | Mobile commerce system |
US10121137B2 (en) | 2010-06-29 | 2018-11-06 | Ncr Corporation | Methods and apparatus for self-service checkout |
US8571986B2 (en) | 2010-07-28 | 2013-10-29 | Bank Of America Corporation | Dependent payment device |
US8601602B1 (en) | 2010-08-31 | 2013-12-03 | Google Inc. | Enhanced multi-factor authentication |
CA2882602A1 (en) | 2010-09-20 | 2012-03-29 | Rick L. Orsini | Systems and methods for secure data sharing |
US9619797B2 (en) | 2010-10-13 | 2017-04-11 | Square, Inc. | Payment methods with a payment service and tabs selected by a first party and opened by a second party at an geographic location of the first party's mobile device |
US8295812B1 (en) | 2010-10-15 | 2012-10-23 | Sprint Communications Company L.P. | Reducing mobile-phone fraud |
US8514703B2 (en) | 2010-11-11 | 2013-08-20 | Qualcomm Incorporated | Scheduling of logical channels in a wireless communication system |
US20120137340A1 (en) | 2010-11-29 | 2012-05-31 | Palo Alto Research Center Incorporated | Implicit authentication |
US8504831B2 (en) | 2010-12-07 | 2013-08-06 | At&T Intellectual Property I, L.P. | Systems, methods, and computer program products for user authentication |
CA2819696A1 (en) | 2010-12-23 | 2012-06-28 | Paydiant, Inc. | Mobile phone atm processing methods and systems |
US20120174237A1 (en) | 2010-12-31 | 2012-07-05 | Openpeak Inc. | Location aware self-locking system and method for a mobile device |
US8385981B2 (en) | 2011-01-23 | 2013-02-26 | YouSendIt | System and method for capturing augmented reality electronic signatures |
US20120197794A1 (en) | 2011-01-31 | 2012-08-02 | Bank Of America Corporation | Shared mobile wallet |
US8666895B2 (en) | 2011-01-31 | 2014-03-04 | Bank Of America Corporation | Single action mobile transaction device |
US8660358B1 (en) | 2011-02-18 | 2014-02-25 | Google Inc. | Rank-based image piling |
US20120230539A1 (en) | 2011-03-08 | 2012-09-13 | Bank Of America Corporation | Providing location identification of associated individuals based on identifying the individuals in conjunction with a live video stream |
US20120254941A1 (en) | 2011-03-30 | 2012-10-04 | Elwha LLC, a limited liability company of the State of Delaware | Providing particular level of access to one or more items in response to determining primary control of a computing device |
CN102148830B (en) | 2011-03-31 | 2014-03-26 | 杭州华三通信技术有限公司 | Method for controlling flow of authentication server and authentication access device |
US8752127B2 (en) | 2011-05-26 | 2014-06-10 | First Data Corporation | Systems and methods for identifying devices by a trusted service manager |
US8813248B2 (en) | 2011-06-28 | 2014-08-19 | Bank Of America Corporation | System and method for authenticating a user |
SG187283A1 (en) | 2011-07-27 | 2013-02-28 | goodwin Russell | Intelligent payment system |
US9864851B2 (en) | 2011-07-28 | 2018-01-09 | Blackberry Limited | System, device, and method for authentication of a user accessing an on-line resource |
US8752154B2 (en) | 2011-08-11 | 2014-06-10 | Bank Of America Corporation | System and method for authenticating a user |
US8485438B2 (en) | 2011-09-19 | 2013-07-16 | Google Inc. | Mobile computing device authentication using scannable images |
US8869305B1 (en) | 2011-09-22 | 2014-10-21 | Symantec Corporation | Systems and methods for implementing password-protection policies based on physical locations of mobile devices |
US8869241B2 (en) | 2011-09-24 | 2014-10-21 | Elwha Llc | Network acquired behavioral fingerprint for authentication |
US8688980B2 (en) | 2011-09-24 | 2014-04-01 | Elwha Llc | Trust verification schema based transaction authorization |
US20130085927A1 (en) | 2011-10-04 | 2013-04-04 | Research In Motion Limited | Providing Increased Ability To Perform A Transaction Based On Locale |
US9021565B2 (en) | 2011-10-13 | 2015-04-28 | At&T Intellectual Property I, L.P. | Authentication techniques utilizing a computing device |
KR101851398B1 (en) | 2011-10-14 | 2018-04-23 | 삼성전자주식회사 | Apparus and method for authorizing combining code using quick response code |
US8892461B2 (en) | 2011-10-21 | 2014-11-18 | Alohar Mobile Inc. | Mobile device user behavior analysis and authentication |
US8943320B2 (en) | 2011-10-31 | 2015-01-27 | Novell, Inc. | Techniques for authentication via a mobile device |
EP2774098B1 (en) | 2011-10-31 | 2024-02-28 | CosmoKey Solutions GmbH & Co. KG | Authentication method |
US8682802B1 (en) | 2011-11-09 | 2014-03-25 | Amazon Technologies, Inc. | Mobile payments using payment tokens |
US8595808B2 (en) * | 2011-12-16 | 2013-11-26 | Daon Holdings Limited | Methods and systems for increasing the security of network-based transactions |
US9306905B2 (en) | 2011-12-20 | 2016-04-05 | Tata Consultancy Services Ltd. | Secure access to application servers using out-of-band communication |
US8850575B1 (en) | 2011-12-30 | 2014-09-30 | Emc Corporation | Geolocation error tracking in transaction processing |
US20130173456A1 (en) | 2012-01-01 | 2013-07-04 | Bank Of America Corporation | Presentation of mobile payment transactionhistory on a mobile communication device |
US20130178233A1 (en) | 2012-01-10 | 2013-07-11 | Bank Of America Corporation | Dynamic Geo-Fence Alerts |
US9100448B2 (en) | 2012-01-20 | 2015-08-04 | Blackberry Limited | Communication device for throttling transmitted data |
US20130198056A1 (en) | 2012-01-27 | 2013-08-01 | Verizon Patent And Licensing Inc. | Near field communication transaction management and application systems and methods |
US20130212007A1 (en) | 2012-02-10 | 2013-08-15 | Protegrity Corporation | Tokenization in payment environments |
US8302152B1 (en) | 2012-02-17 | 2012-10-30 | Google Inc. | Location-based security system for portable electronic device |
US9100825B2 (en) | 2012-02-28 | 2015-08-04 | Verizon Patent And Licensing Inc. | Method and system for multi-factor biometric authentication based on different device capture modalities |
US8930271B1 (en) | 2012-04-25 | 2015-01-06 | Wells Fargo Bank, N.A. | System and method for a mobile wallet |
US20130290361A1 (en) | 2012-04-30 | 2013-10-31 | Eric A. Anderson | Multi-geography cloud storage |
US8973102B2 (en) | 2012-06-14 | 2015-03-03 | Ebay Inc. | Systems and methods for authenticating a user and device |
US8584219B1 (en) | 2012-11-07 | 2013-11-12 | Fmr Llc | Risk adjusted, multifactor authentication |
US8881306B2 (en) | 2012-11-20 | 2014-11-04 | Barnes And Noble, Inc. | Architecture system for in-store reading |
US10049361B2 (en) | 2012-12-14 | 2018-08-14 | Accenture Global Services Limited | Dynamic authentication technology |
US9100387B2 (en) | 2013-01-24 | 2015-08-04 | Oracle International Corporation | State driven orchestration of authentication components in an access manager |
US9772766B2 (en) | 2013-01-29 | 2017-09-26 | Wells Fargo India Solutions Private Limited | Banking services experience center |
US20140244503A1 (en) | 2013-02-27 | 2014-08-28 | Mastercard International Incorporated | System and method for automatic thresholding for payment card spend control |
US8744968B1 (en) | 2013-03-13 | 2014-06-03 | Bank Of America Corporation | Providing automated initial and final payment for an activity based on determining the location of an activity participant's mobile communication device |
US20140279270A1 (en) | 2013-03-14 | 2014-09-18 | Bank Of America Corporation | Pre-ordering based on location of a customer |
US20140279476A1 (en) | 2013-03-15 | 2014-09-18 | Visa International Service Association | Multiple Account Dynamic Card Apparatuses, Methods and Systems |
US9367676B2 (en) | 2013-03-22 | 2016-06-14 | Nok Nok Labs, Inc. | System and method for confirming location using supplemental sensor and/or location data |
US20140310764A1 (en) | 2013-04-12 | 2014-10-16 | Verizon Patent And Licensing Inc. | Method and apparatus for providing user authentication and identification based on gestures |
US20140250009A1 (en) | 2013-05-09 | 2014-09-04 | Daniel Edward Carlson | Debit/Credit Card Fraud Prevention Software and Smart Phone Application System and Process |
US20150032621A1 (en) | 2013-07-24 | 2015-01-29 | Mastercard International Incorporated | Method and system for proximity fraud control |
EP3028241A4 (en) | 2013-07-31 | 2017-04-19 | Opanga Networks, Inc. | Pre-delivery of content to a user device |
US20150120572A1 (en) | 2013-10-25 | 2015-04-30 | Nitro Mobile Solutions, LLC | Location based mobile deposit security feature |
US9483765B2 (en) | 2013-12-09 | 2016-11-01 | Mastercard International Incorporated | Systems and methods for monitoring payment transactions for fraud using social media |
US9165902B2 (en) | 2013-12-17 | 2015-10-20 | Kulicke And Soffa Industries, Inc. | Methods of operating bonding machines for bonding semiconductor elements, and bonding machines |
US20150213474A1 (en) | 2014-01-27 | 2015-07-30 | Mastercard International Incorporated | Apparatus, method, and computer program product for transit pooling using payment card data |
-
2015
- 2015-10-30 US US14/928,154 patent/US9641539B1/en active Active
-
2017
- 2017-03-16 US US15/460,951 patent/US9794299B2/en active Active
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20180040036A1 (en) * | 2016-08-04 | 2018-02-08 | Samsung Electronics Co., Ltd. | Offline Cards |
US11190537B2 (en) * | 2019-06-18 | 2021-11-30 | International Business Machines Corporation | Vulnerability management of disconnected endpoints |
Also Published As
Publication number | Publication date |
---|---|
US9794299B2 (en) | 2017-10-17 |
US20170187754A1 (en) | 2017-06-29 |
US9641539B1 (en) | 2017-05-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9794299B2 (en) | Passive based security escalation to shut off of application based on rules event triggering | |
US20220245630A1 (en) | Method and system for secure authentication of user and mobile device without secure elements | |
US10015156B2 (en) | System for assessing network authentication requirements based on situational instance | |
US10535047B1 (en) | Systems and methods for financial operations performed at a contactless ATM | |
US10068226B2 (en) | System for authorization and instant integration of credit card to digital wallet | |
US10404675B2 (en) | Elastic authentication system | |
US20150254648A1 (en) | Managed digital wallets | |
US20170091759A1 (en) | Token provisioning for non-account holder use with limited transaction functions | |
US20140214640A1 (en) | Parental management of digital assets | |
US9292849B2 (en) | Mobile one-time card number generator for ATM usage | |
US20150032621A1 (en) | Method and system for proximity fraud control | |
US11087312B2 (en) | Account tokenization for virtual currency resources | |
US10002387B2 (en) | Pre-contracted, staged, currency exchange system | |
CA2933336A1 (en) | Method and system for generating an advanced storage key in a mobile device without secure elements | |
US20150254663A1 (en) | Token usage scaling based on determined level of exposure | |
US20160180330A1 (en) | Method and system for recovery of a lost payment card | |
US11700259B2 (en) | Authentication and tracking system for secondary users of a resource distribution processing system | |
US11188919B1 (en) | Systems and methods for contactless smart card authentication | |
US20160027000A1 (en) | Mobile one-time bank card number generator for digital wallet | |
US20150019426A1 (en) | Method and system for applying spending limits to payment accounts involving installment transactions | |
US20180322473A1 (en) | System for atypical third party channel utilization for resource distribution completion | |
US9639835B2 (en) | Method to enable consumers to make purchases at e-Commerce websites using their mobile number | |
US20160027104A1 (en) | Smart form | |
US20190139036A1 (en) | Method, apparatus, and computer-readable medium for securely performing digital asset transactions | |
US20240171582A1 (en) | Systems and methods for validating network operations between user accounts through access tokens |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: BANK OF AMERICA CORPORATION, NORTH CAROLINA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:VOTAW, ELIZABETH S.;JONES-MCFADDEN, ALICIA C.;SIGNING DATES FROM 20151025 TO 20151029;REEL/FRAME:036925/0418 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |