EP4093075A1 - System und verfahren für speicherung, abruf, hinzufügung und überwachung von anwendungen auf geräten - Google Patents

System und verfahren für speicherung, abruf, hinzufügung und überwachung von anwendungen auf geräten Download PDF

Info

Publication number
EP4093075A1
EP4093075A1 EP22180829.8A EP22180829A EP4093075A1 EP 4093075 A1 EP4093075 A1 EP 4093075A1 EP 22180829 A EP22180829 A EP 22180829A EP 4093075 A1 EP4093075 A1 EP 4093075A1
Authority
EP
European Patent Office
Prior art keywords
application
mobile device
appliance
permission
server
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.)
Pending
Application number
EP22180829.8A
Other languages
English (en)
French (fr)
Inventor
Aashin Nagpal
Ken C. Singer
Holger Assenmacher
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
BlackBerry Ltd
Original Assignee
BlackBerry Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by BlackBerry Ltd filed Critical BlackBerry Ltd
Publication of EP4093075A1 publication Critical patent/EP4093075A1/de
Pending legal-status Critical Current

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
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H04W12/069—Authentication using certificates or pre-shared keys
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H04W8/245—Transfer of terminal data from a network towards a terminal
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2143—Clearing memory, e.g. to prevent the data from being stolen
    • 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/102—Entity profiles

Definitions

  • the present invention relates to the management of applications on an appliance. More specifically the invention relates to controlling the use of applications on appliances such as mobile devices according to permissions set on an external server system.
  • the appliance in some embodiments, may be subservient to the server.
  • the second way a mobile appliance may be enabled for remote working is for the application in use to be physically resident and enabled on the appliance (i.e., stored locally on the appliance).
  • This solution has a strong advantage in that it permits a user to work with the application locally without the need for a sustained connection.
  • To implement this second solution requires that the applications be downloaded to the appliance and then enabled.
  • Applications for mobile devices may already be stored and retrieved from application repositories and delivered to mobile appliances using a wireless network. Such examples can be found with Apple's AppStore for the iPhone and the RIM Blackberry family of products.
  • Such a system may manage applications by individually approving them for execution, functionally augmenting them by adding validity checking and user confirmation, and monitoring them for permitted networks and connection targets.
  • applications may be restricted from access to locally stored persistent data or the data may itself be removed.
  • the present invention provides a novel system for securely regulating information exchange on an appliance, without requiring a constant connection between the appliance and an external server.
  • the present invention discloses a system and method for managing applications on an appliance. More particularly, the present invention teaches systems and methods for securely regulating information exchanges on an appliance without requiring a persistent connection to company resources.
  • a server is in communication with one or more appliances.
  • the appliances are typically mobile devices, such as cellular phones; however, any suitable electronic device is considered within the scope of the invention.
  • the server is coupled to one or more databases which include device information as well as an application database.
  • a user may authenticate using the appliance.
  • a set of permissions may be associated with the user.
  • the server then supervises information exchanged between the appliance and the server, as well as application functionality on the appliance.
  • the server may likewise be enabled to record transactions of any information exchange with the appliance.
  • the appliance is subservient to the server.
  • Control over application functionality and information exchange may be accomplished, in some embodiments, by supplementing the applications downloaded to the appliance with supplemental code, referred to hereafter as an AppGuard.
  • the AppGuard is tailored, using information related to the appliance, to the appliance type in order to ensure proper functionality.
  • the user searches for applications using a web based platform.
  • An arbitrary keyword matching system may be utilized to find applications of interest. Only applications that the user has authority to use are generally presented to the user.
  • the user may then download the application from the server to the appliance.
  • the server first adds the supplemental AppGuard to ensure management of the application.
  • a developer may directly add the supplemental AppGuard to the application prior to uploading to the server. Once downloaded, the AppGuard is executed upon installation.
  • the AppGuard may collect device information.
  • the AppGuard may require validation from the server prior to installation. Validation of permissions may utilize the collected data. After validation, the application may be run.
  • further functionalities may be included within the application using the AppGuard. For example, if the appliance is lost, the user may be able to notify the server that the appliance has been misplaced. The AppGuard may then disable the application in order to limit release of any sensitive information. Likewise, the server may be enabled to collect information regarding the appliance's environment and base management decisions upon environmental indicators. An example of this includes where the appliance determines if it is in the presence of certain devices, such as a particular Bluetooth headset.
  • Management of the applications may include augmenting, deleting, disabling or authorizing the application. Augmentation, for the purposes of this application, includes any functional modification to the application.
  • the server may also, in some embodiments, be enabled to disable the appliance itself. For example, if permission validation fails, the AppGuard may prevent the usage of an application, or may even purge the persistent memory of the application.
  • FIG. 1 is an example illustration 100 of the application management system in accordance with some embodiments.
  • a User 110 is seen interacting with an Appliance 120.
  • the Appliance 120 is illustrated as being a smart cell phone type device, such as a Blackberry.
  • any type of electronic appliance capable of supporting an application may be utilized with the application management system.
  • the Appliance 120 may be in periodic wireless connectivity with a Cellular Tower 130. Likewise, in some embodiments, the Appliance 120 may instead be configured to have connectivity through a WiFi base station, satellite connection, or even wired connection such as through a modem.
  • the Cellular Tower 130 may be coupled to a back end Server 140.
  • the Server 140 in some embodiments, may be an independent third party system accessible by developers, IT professionals and end users via a web based portal or other host platform.
  • the Server 140 may require authentication prior to access.
  • the Server 140 may be an internal corporate server, only accessible by authorized corporate personnel.
  • the Server 140 may have access to a number of databases. These may include an Application Database 150 and one or more Management Databases 160.
  • the Application Database 150 may include source code for any number of applications. These applications may include commercially available applications, such as Microsoft Office products, or may be internally developed, or modified, applications.
  • the Management Databases 160 in comparison, may include information on particular devices, user information, and corporate access permissions.
  • the Server 140 may function in a similar fashion.
  • the applications may be externally developed and subsequently uploaded to via the Server 140 to the Application Database 150. Permissions may then be configured within Management Databases 160.
  • applications may be designed in and updated from a web browser based environment.
  • U.S. patent application 12/032,093 published as U.S. 2008/0201453 , which is incorporated by reference, is an example of such a web based development platform.
  • the Server 140 may be accessed by a developer via a web based browser in such a manner for the development of applications. These applications may then be managed, functionally augmented, and monitored by the application management system described herein.
  • applications which have been created and modified in the aforesaid web browser based design environment may be changed and these changes to an existing application may then be automatically propagated to devices on which they have been already installed.
  • an application server whose stored applications comprise more than one "CellAuthor" or externally sourced application, one or more related programs may be automatically included.
  • the related programs may comprise programs that allow selection of one or more applications and, further, programs that permit related applications to share common data. This latter feature eliminates wasteful duplication of information which is a significant deficiency of separate, stand-alone applications.
  • Applications generally comprise one or more machine or computer instructions for causing an appliance to perform certain actions. These applications may be distributed in an application marketplace using an application Server 140 which may have stored one or more applications as discussed above.
  • Applications may be uploaded to the Server 140 by authenticated providers (i.e., developers). Authentication may be achieved by any of a number of methods well known in the art. For example a simple challenge-response method may require a user to enter a valid password prior to the connection permission being set to allow such upload actions.
  • Figure 2A provides an example flow chart of the process for the distribution and management of applications.
  • the Server 140 provides one or more applications to the Appliance 120 at step 202.
  • a check for permission to access the application is performed at step 204.
  • An invalid permission may result in the deletion of persistent data within the Appliance 120, at step 212.
  • sensitive or confidential information may remain secure in the situation where the Appliance 120 is stolen or in the possession of a User 110 without permission to access the particular application/information.
  • a valid permission enables the User 110 to access/run the application at step 206. This continues until, at step 208, the application is terminated. After termination of the application, an initial default message may be displayed, at step 210.
  • This default message may include the dashboard for the Appliance 120, a web browser page, advertisement, personalized message or similar display.
  • Figure 2B provides an example of a more detailed process flow for providing the application(s) from the Server 140 to the Appliance 120, as indicated at step 202.
  • the User 110 initiates a session, at step 214.
  • a session may include access through a web browser portal, or access through a secure program interface.
  • the user may typically be authenticated in the same manner that the developer required authentication, at step 216. Note, however, that while authentication is being discussed at this point in the process, it is equally possible that authentication may be performed at a later time.
  • the application may be installed prior to authentication without any ill effect.
  • a corporation may provide an authentication key to its employees; single users may have a private arrangement for downloading and use of an application.
  • Various users may, in some embodiments, have different levels of accessibility, as indicated by profile permissions stored within the Management Databases 160.
  • End Users 110 may only have the ability to download particular applications based upon rank and division within a company.
  • a sales professional within Corporation A may be restricted to general clerical applications and proprietary negotiation applications exclusive to Company A.
  • high level engineers within the same company may have access to a whitepaper viewer pertaining to detailed technical documents about the products of the company.
  • Developer users may have additional permissions including the ability to upload/generate applications. Likewise, high level developers may further have the ability to access existing applications and further modify them to meet particular purposes.
  • IT management users may have permissions relating to setting the permissions of other users.
  • an IT manager may be empowered to select which end users are capable of downloading particular applications.
  • the process may continue to step 218 where the User 110 may search for an application.
  • the server may provide a search utility that allows a user to locate the application desired by one or more of a number of attributes. For example an application may be located by name or, for a corporate user, by searching the name or identification code of the corporation. Search results may be presented as a list of available applications for download. An application may then be selected and downloaded at step 220.
  • the server may first acquire information about the mobile client to which the application is destined. This may be in any of a number of ways known in the art. For example, the authorizing corporation may have set a flag indicating which type of appliance the target is, such as an iPhone or a Symbian OS based product.
  • AppGuard may supplement the application in order to ensure future management of the application once locally installed on the Appliance 120.
  • AppGuard may contain information needed by the target device to install the application.
  • AppGuard may simply be a program, or series of instructions, that allow the application to operate successfully in the target appliance.
  • an AppGuard normally comprises source code that has been compiled into executable code matching the requirements of the target device.
  • Target device platforms include, but are not limited to, J2ME, Windows Mobile, Android, iPhone, and LiMo.
  • the AppGuard classes maybe added to the jar (Java ARchive) tile, the midlet entry point in the manifest changed to point to the wrapper itself, which, when executed, performs initialization and check actions, and then continues to execute the original application midlet.
  • a midlet is a Java application framework for a Mobile Information Device profile, and midlets are normally applications themselves. Signed applications may require a new signature key to be applied by the Server 140.
  • the AppGuard may add actions, for instance, at startup, when the midlet is paused or when the application is terminated.
  • the application with AppGuard is installed upon the Appliance 120.
  • the User 110 may see and respond to information, resulting from the action of the AppGuard, presented at the time of installation of the application.
  • Such information may be delivered in a user friendly fashion to automate the process and minimize the need for expertise on the part of the user 110.
  • Use cases include data gathering, information bulletins, device status control and advice, and other management or supervisory functions.
  • These supplemental programs are often referred to as installation wizards, or launch pads, and may allow some residual functionality to remain after the installation process has completed. This residue may be invoked later when other interactions are required from a user. For example, a failed permission request at a later date may result in the application itself being denied access to local persistent data.
  • the data may have been eliminated from the appliance, may have been locked, or the application itself may have been locked.
  • the residual function may comprise displaying to the user an interactive alert screen which may take the form of a help screen, a questionnaire or an advertisement inviting the user to consider other offers for services.
  • the AppGuard may collect and report data regarding the Appliance 120 to the Server 140, at step 224. This collected data may be utilized by the Server 140 to determine if the User 110 may receive permission to access the underlying Application. Thus, at step 226, AppGuard may receive permission data from the Server 140. AppGuard may then display an auxiliary screen or other message, at step 228, and start the application, at step 230.
  • the application may be started as originally designed, or may be started in a modified manner. For example, instead of starting Excel in a blank document, as the original application does, an AppGuard supplemented Excel application may be started by opening the most recent price listings for a given product line for the company that the user is affiliated with.
  • opening an HTTP connection may cause it to be rerouted by changing its method name. Every time an HTTP connection is initiated, some server action may be imposed. Its destination may be recorded, or a secure protocol may replace an unencrypted protocol. This may be achieved in one or more ways.
  • the existing application code may be decompiled, new source code added and then the composite code recompiled, in some embodiments. In some cases, new or replacement binary code may be directly injected into the application without the steps of de-compilation and recompilation.
  • the AppGuard may augment online versus offline functionality of the application.
  • the AppGuard may allow the user to access the application some set number of times with a password. When the allowable uses have been exceeded, the application may then be disabled for further use unless the session is online and authenticated.
  • the AppGuard may merely restrict some of the data (i.e., particular Excel spreadsheets) in a similar manner.
  • AppGuard may be likewise utilized to enforce user actions, such as installation of updates. For example, if a mandatory update is received, the AppGuard may display a message requiring its installation. If the user does not perform the necessary action, the application may be forced to exit or otherwise be disabled.
  • AppGuard may display informative messages, as desired. This may include advertisements, offers for service improvement upgrades, thank-you pages, or customer service outreach.
  • user Appliance 120 may also be managed in some embodiments.
  • the Server 140 may be a single server or may have multiple instances or replicas in accordance with methods known in the art. Servers may maintain a record of all transactions within the Management Databases 160. These may include properties of target appliances, applications already accessed by any appliance, appliance approval status and information that allows a device or application lock to be actuated. Users may be authenticated prior to, during or after installation, or any combination of these. Authentication information may be used to qualify a user for one or more roles. For example, a user may be one or more of a device and application User 110, an application approver (i.e., IT manager), or be permitted to upload applications (i.e., developer).
  • an application approver i.e., IT manager
  • applications i.e., developer
  • FIG. 3 a process flow diagram is provided illustrating the typical operating sequence of some embodiments of the system. Additionally, arrows are illustrated indicating flow of information between the Appliance 120 client device and the Server 140.
  • a browser is first invoked.
  • the Appliance 120 communicates with the Server 140 that a session has been initiated, and the Server 140 may return information including a logon screen or the like.
  • the user may be authenticated, as discussed above. Again the Appliance 120 and Server 140 interact to ensure authentication.
  • the User 110 may search the applications using a browser, search function or the like. Again the Appliance 120 and Server 140 require communication such that only applications that the User 110 has permission to use are displayed as available applications. The application with AppGuard wrapper may then be downloaded to the Appliance 120 from the Server 140.
  • the User 110 may then start the AppGuard supplemented application. This step is restricted to the Appliance 120 and does not require information from the Server 140.
  • the AppGuard collects information and transmits it back to the Server 140.
  • the Server 140 may then return permission to the Appliance 120.
  • the AppGuard supplement may display an auxiliary screen, such as an installation wizard. If permission is valid, the application may be run. If permissions are invalid, persistent data may be killed (disabled or deleted). This, functionally, protects information a company considers confidential from access by non-permissible persons. Display of auxiliary screens, running of the application or deletion/disabling of persistent data may be performed on the Appliance 120 without further input from the Server 140.
  • advertisements or other messages may be displayed on the Appliance 120. Content for these messages may be provided by the Server 140.
  • the AppGuard may then start the application in an original or modified form without any further interaction with the Server 140.
  • the application running on the Appliance 120 may interact with the Server 140. Once completed, the application terminates and then a default screen may be displayed.
  • the default screen may include an initial browser screen.
  • FIG. 4A illustrates an embodiment of the server side operation of the application management system.
  • This process begins with the receipt of a user authentication, at step 410.
  • user credentials may be stored within one or more databases which the Server 140 may access.
  • Authentication may be performed by a challenge and response or other known authentication scheme.
  • the Server 140 may receive an application request from the Appliance 120, at step 420.
  • An application request may include any of a search request, or a request to download a particular application.
  • the Server 140 receives a search request, the permissions of the User 110 may be queried such that only applications the user has permission to access are displayed in response to the search. Likewise, applications may only be selected for download if the user has permission to access the particular application.
  • the Server 140 may acquire information regarding the Appliance 120, at step 430. This may include accessing information stored about the device on the management Database 160, or may include sending an information request to the Appliance 120 directly. Information regarding the appliance may be utilized in order to ensure the AppGuard supplement is capable of executing on the target Appliance 120, as well as ensuring that the application will function on the Appliance 120.
  • FIG. 440 the application is supplemented with an AppGuard.
  • Figure 4B illustrates an example of a more detailed flow chart for the supplementing of the application with an AppGuard, as indicated at step 440.
  • the appropriate AppGuard source code is selected, at step 442.
  • the source code may be compiled into executable code matching the requirements of the target Appliance 120, at step 444.
  • the executable code may be affixed to the application at step 446.
  • FIG. 4A after supplementing the application, it may be deployed to the Appliance 120, at step 450.
  • an existing email reader application for iOS mobile devices may be augmented by the original vendor using an AppGuard supplement.
  • the original vendor's developer must, in some embodiment, download the iOS AppGuard supplement and incorporate the supplement into the existing email reader applications.
  • the developer may then make minor modifications to the original application and rebuild the augmented application using an Apple-issues cryptographic keys to produce a final augmented binary.
  • the application becomes augmented with additional functionalities using an AppGuard supplement; in this example "approve individual application” and "lock device” could be the extended capabilities.
  • a user with the up-loader permission role may enter the augmented application binary into one or more Server 140 using a web browser.
  • the code contained by the AppGuard causes the appliance to contact the server and verifies the status of both the example properties. Only the augmented code needs to be stored by the server.
  • a user with an approving role may now label the application as generally executable for any or all devices.
  • a subsequent download by another ordinary User 110 would now result in the augmented version of the application being loaded on that user's Appliance 120 and subsequent access to the capabilities endowed by the application.
  • an approver might choose to disable this application only for certain users, leaving only a subset of the user community with working access. This might happen at any time, for example to restrict data changes during an audit period or to control account information for management purposes.
  • a User 110 loses control of the appliance (such as when stolen or misplaced)
  • the user may contact the server using a browser session and may cause the appliance to be disapproved for further use. This may result in the appliance being locked or the appliance being constrained in some way.
  • the application may be simply disabled and may no longer be invoked.
  • local data may be locked or permanently eliminated from the appliance and access to the server mav be nrohibited.
  • the appliance may report its environmental status and this data may be used by the appliance or the server to determine if the appliance is still in control of the user.
  • Location sensitive technologies may be used for this purpose. However, for a traveling user the changes in location generally introduce confusion.
  • a better method may be to consider the user's local environment as a key, for example the user's Bluetooth headset or other normally present components may be required to be active before the application can be enabled.
  • the application wrapper may invoke a function which determines the appliance's supplementary environment and uses this as a key to assure the security of the appliance.
  • Figures 5A-5D are example screenshots for an embodiment of the web based application management interface in accordance with an embodiment of the present invention.
  • Figure 5A illustrates a typical User's 110 application marketplace.
  • a listing of their applications may be seen, along with most popular suggestions and browsing links.
  • a search field may be seen for keyword searches for a particular application. The user may logout, select from the company catalog, make requests to IT management or manage the account.
  • Figure 5B illustrates the web based interface for an IT manager interface.
  • the IT manager is able to select users and actively manage the permissions for the user.
  • a summary of all user accounts may be seen including the ability to add additional users. Requests from individual users may be reviewed and approved or declined.
  • a user may be selected from the user summary list and be viewed in greater detail as seen at Figure 5C .
  • usage may be monitored, permissions set and applications may be approved for use.
  • Figure 5D illustrates an interface where an IT manager is able to review and test applications from the marketplace prior to performing a bulk purchase of the application and placing it within the company store.
  • a selected application is presented including a description, device support, pricing and status.
  • the IT manager has the option of testing prior to adding the application to the company catalog, or denying the submission.
  • FIG. 6 is an example illustration of the operation of the same browser based interface being accessed on a mobile device in accordance with an embodiment of the present invention.
  • a series of example screenshots are provided, beginning at screenshot 610 with the web application being distributed by email and downloading.
  • a link to execute the program is placed upon the phone home screen.
  • the web browser is launched and a logon/authentication screen is displayed. The user must then logon with a password.
  • Screenshot 630 illustrates searching for applications using different browsing modes or by search terms.
  • Screenshot 640 illustrates that an application has been selected and indicates the price the download may cost the particular department within the company. Once satisfied with the selection, the user may select the application and confirm the download, as seen at Screenshot 650. Download and installation then occurs with minimal user input to ensure ease of use.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Bioethics (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Information Transfer Between Computers (AREA)
  • Storage Device Security (AREA)
  • Stored Programmes (AREA)
EP22180829.8A 2009-09-08 2010-09-07 System und verfahren für speicherung, abruf, hinzufügung und überwachung von anwendungen auf geräten Pending EP4093075A1 (de)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US27612909P 2009-09-08 2009-09-08
US12/876,214 US9185554B2 (en) 2008-02-15 2010-09-06 System and methods to store, retrieve, manage, augment and monitor applications on appliances
PCT/US2010/047956 WO2011037741A2 (en) 2009-09-08 2010-09-07 System and methods to store, retrieve, manage, augment and monitor applications on appliances
EP10819226.1A EP2561689A4 (de) 2009-09-08 2010-09-07 System und verfahren für speicherung, abruf, hinzufügung und überwachung von anwendungen auf geräten

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
EP10819226.1A Division EP2561689A4 (de) 2009-09-08 2010-09-07 System und verfahren für speicherung, abruf, hinzufügung und überwachung von anwendungen auf geräten

Publications (1)

Publication Number Publication Date
EP4093075A1 true EP4093075A1 (de) 2022-11-23

Family

ID=43796432

Family Applications (2)

Application Number Title Priority Date Filing Date
EP22180829.8A Pending EP4093075A1 (de) 2009-09-08 2010-09-07 System und verfahren für speicherung, abruf, hinzufügung und überwachung von anwendungen auf geräten
EP10819226.1A Ceased EP2561689A4 (de) 2009-09-08 2010-09-07 System und verfahren für speicherung, abruf, hinzufügung und überwachung von anwendungen auf geräten

Family Applications After (1)

Application Number Title Priority Date Filing Date
EP10819226.1A Ceased EP2561689A4 (de) 2009-09-08 2010-09-07 System und verfahren für speicherung, abruf, hinzufügung und überwachung von anwendungen auf geräten

Country Status (3)

Country Link
US (1) US9185554B2 (de)
EP (2) EP4093075A1 (de)
WO (1) WO2011037741A2 (de)

Families Citing this family (102)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9544398B2 (en) * 2008-02-15 2017-01-10 Good Technology Holdings Limited System and methods to store, retrieve, manage, augment and monitor applications on appliances
US8745213B2 (en) 2008-12-19 2014-06-03 Openpeak Inc. Managed services platform and method of operation of same
US8615581B2 (en) 2008-12-19 2013-12-24 Openpeak Inc. System for managing devices and method of operation of same
US8856322B2 (en) 2008-12-19 2014-10-07 Openpeak Inc. Supervisory portal systems and methods of operation of same
US8612582B2 (en) 2008-12-19 2013-12-17 Openpeak Inc. Managed services portals and method of operation of same
US8650290B2 (en) 2008-12-19 2014-02-11 Openpeak Inc. Portable computing device and method of operation of same
US8788655B2 (en) 2008-12-19 2014-07-22 Openpeak Inc. Systems for accepting and approving applications and methods of operation of same
US20100159898A1 (en) 2008-12-19 2010-06-24 Openpeak, Inc. Services platform for networked devices that provide telephony and digital media services
US8713173B2 (en) 2008-12-19 2014-04-29 Openpeak Inc. System and method for ensuring compliance with organizational policies
WO2011039641A1 (en) * 2009-09-30 2011-04-07 France Telecom (Etablissement Autonome De Droit Public) Method and system to monitor equipment of an it infrastructure
US20120060123A1 (en) * 2010-09-03 2012-03-08 Hugh Smith Systems and methods for deterministic control of instant-on mobile devices with touch screens
US8650658B2 (en) 2010-10-25 2014-02-11 Openpeak Inc. Creating distinct user spaces through user identifiers
US9225766B2 (en) * 2010-10-29 2015-12-29 Sears Brands, L.L.C. Systems and methods for providing smart appliances
US8359016B2 (en) 2010-11-19 2013-01-22 Mobile Iron, Inc. Management of mobile applications
US20120254768A1 (en) * 2011-03-31 2012-10-04 Google Inc. Customizing mobile applications
US10089093B1 (en) 2011-05-24 2018-10-02 BlueStack Systems, Inc. Apparatuses, systems and methods of switching operating systems
US8924958B1 (en) 2011-05-24 2014-12-30 BlueStack Systems, Inc. Application player
US8527361B2 (en) * 2011-06-27 2013-09-03 Amazon Technologies, Inc. Service for adding in-application shopping functionality to applications
US10791538B1 (en) 2011-07-06 2020-09-29 BlueStack Systems, Inc. Cloud-based data synchronization
US9804864B1 (en) 2011-10-07 2017-10-31 BlueStack Systems, Inc. Method of mapping inputs and system thereof
US8695060B2 (en) 2011-10-10 2014-04-08 Openpeak Inc. System and method for creating secure applications
US9280377B2 (en) 2013-03-29 2016-03-08 Citrix Systems, Inc. Application with multiple operation modes
US9183380B2 (en) 2011-10-11 2015-11-10 Citrix Systems, Inc. Secure execution of enterprise applications on mobile devices
JP5890648B2 (ja) * 2011-10-21 2016-03-22 キヤノンイメージングシステムズ株式会社 情報処理装置、その制御方法、およびデバイス制御システム
US8713646B2 (en) 2011-12-09 2014-04-29 Erich Stuntebeck Controlling access to resources on a network
US9787655B2 (en) 2011-12-09 2017-10-10 Airwatch Llc Controlling access to resources on a network
US10257194B2 (en) 2012-02-14 2019-04-09 Airwatch Llc Distribution of variably secure resources in a networked environment
US9705813B2 (en) 2012-02-14 2017-07-11 Airwatch, Llc Controlling distribution of resources on a network
US10404615B2 (en) 2012-02-14 2019-09-03 Airwatch, Llc Controlling distribution of resources on a network
US9680763B2 (en) 2012-02-14 2017-06-13 Airwatch, Llc Controlling distribution of resources in a network
US8844032B2 (en) * 2012-03-02 2014-09-23 Sri International Method and system for application-based policy monitoring and enforcement on a mobile device
US8725124B2 (en) * 2012-03-05 2014-05-13 Enterproid Hk Ltd Enhanced deployment of applications
US9405723B2 (en) * 2012-05-02 2016-08-02 Kony, Inc. Mobile application management systems and methods thereof
US8910239B2 (en) 2012-10-15 2014-12-09 Citrix Systems, Inc. Providing virtualized private network tunnels
WO2014062804A1 (en) 2012-10-16 2014-04-24 Citrix Systems, Inc. Application wrapping for application management framework
US9971585B2 (en) 2012-10-16 2018-05-15 Citrix Systems, Inc. Wrapping unmanaged applications on a mobile device
US9247432B2 (en) 2012-10-19 2016-01-26 Airwatch Llc Systems and methods for controlling network access
US8978110B2 (en) 2012-12-06 2015-03-10 Airwatch Llc Systems and methods for controlling email access
US8826432B2 (en) 2012-12-06 2014-09-02 Airwatch, Llc Systems and methods for controlling email access
US8862868B2 (en) 2012-12-06 2014-10-14 Airwatch, Llc Systems and methods for controlling email access
US9021037B2 (en) 2012-12-06 2015-04-28 Airwatch Llc Systems and methods for controlling email access
US8832785B2 (en) 2012-12-06 2014-09-09 Airwatch, Llc Systems and methods for controlling email access
CN103941599A (zh) * 2013-01-21 2014-07-23 海尔集团公司 智能家电控制方法、智能家电及控制系统
CN103941653B (zh) * 2013-01-21 2017-10-31 广东美的制冷设备有限公司 智能家电主、从控制方法及系统
US20140280955A1 (en) 2013-03-14 2014-09-18 Sky Socket, Llc Controlling Electronically Communicated Resources
US9473417B2 (en) 2013-03-14 2016-10-18 Airwatch Llc Controlling resources used by computing devices
US9819682B2 (en) 2013-03-15 2017-11-14 Airwatch Llc Certificate based profile confirmation
US9275245B2 (en) 2013-03-15 2016-03-01 Airwatch Llc Data access sharing
US8997187B2 (en) 2013-03-15 2015-03-31 Airwatch Llc Delegating authorization to applications on a client device in a networked environment
US10652242B2 (en) 2013-03-15 2020-05-12 Airwatch, Llc Incremental compliance remediation
US9148416B2 (en) 2013-03-15 2015-09-29 Airwatch Llc Controlling physical access to secure areas via client devices in a networked environment
US9378350B2 (en) 2013-03-15 2016-06-28 Airwatch Llc Facial capture managing access to resources by a device
US9401915B2 (en) 2013-03-15 2016-07-26 Airwatch Llc Secondary device as key for authorizing access to resources
US9203820B2 (en) 2013-03-15 2015-12-01 Airwatch Llc Application program as key for authorizing access to resources
US9355223B2 (en) 2013-03-29 2016-05-31 Citrix Systems, Inc. Providing a managed browser
US9985850B2 (en) * 2013-03-29 2018-05-29 Citrix Systems, Inc. Providing mobile device management functionalities
US10284627B2 (en) 2013-03-29 2019-05-07 Citrix Systems, Inc. Data management for an application with multiple operation modes
US9787686B2 (en) 2013-04-12 2017-10-10 Airwatch Llc On-demand security policy activation
US10754966B2 (en) 2013-04-13 2020-08-25 Airwatch Llc Time-based functionality restrictions
US8914013B2 (en) 2013-04-25 2014-12-16 Airwatch Llc Device management macros
US9123031B2 (en) 2013-04-26 2015-09-01 Airwatch Llc Attendance tracking via device presence
US9426162B2 (en) 2013-05-02 2016-08-23 Airwatch Llc Location-based configuration policy toggling
US9246918B2 (en) 2013-05-10 2016-01-26 Airwatch Llc Secure application leveraging of web filter proxy services
US9058495B2 (en) 2013-05-16 2015-06-16 Airwatch Llc Rights management services integration with mobile device management
US9584437B2 (en) 2013-06-02 2017-02-28 Airwatch Llc Resource watermarking and management
US9900261B2 (en) 2013-06-02 2018-02-20 Airwatch Llc Shared resource watermarking and management
US20140358703A1 (en) 2013-06-04 2014-12-04 SkySocket, LLC Item Delivery Optimization
US9270777B2 (en) 2013-06-06 2016-02-23 Airwatch Llc Social media and data sharing controls for data security purposes
US20140365946A1 (en) * 2013-06-10 2014-12-11 Pugazhenthi Sankaralingham Systems and methods for operating and managing enterprise systems on a mobile electronic device
US9535857B2 (en) 2013-06-25 2017-01-03 Airwatch Llc Autonomous device interaction
US8924608B2 (en) 2013-06-25 2014-12-30 Airwatch Llc Peripheral device management
US8756426B2 (en) 2013-07-03 2014-06-17 Sky Socket, Llc Functionality watermarking and management
US8775815B2 (en) 2013-07-03 2014-07-08 Sky Socket, Llc Enterprise-specific functionality watermarking and management
US8806217B2 (en) 2013-07-03 2014-08-12 Sky Socket, Llc Functionality watermarking and management
US9226155B2 (en) 2013-07-25 2015-12-29 Airwatch Llc Data communications management
US9112749B2 (en) 2013-07-25 2015-08-18 Airwatch Llc Functionality management via application modification
US9665723B2 (en) 2013-08-15 2017-05-30 Airwatch, Llc Watermarking detection and management
US9516005B2 (en) 2013-08-20 2016-12-06 Airwatch Llc Individual-specific content management
US20220012346A1 (en) * 2013-09-13 2022-01-13 Vmware, Inc. Risk assessment for managed client devices
US10129242B2 (en) 2013-09-16 2018-11-13 Airwatch Llc Multi-persona devices and management
US9185099B2 (en) 2013-09-23 2015-11-10 Airwatch Llc Securely authorizing access to remote resources
US9258301B2 (en) 2013-10-29 2016-02-09 Airwatch Llc Advanced authentication techniques
US9544306B2 (en) 2013-10-29 2017-01-10 Airwatch Llc Attempted security breach remediation
AU2015255632A1 (en) * 2014-05-05 2016-08-18 Oliver Lloyd Pty Ltd Acn 108 899 323 Shared access appliance, device and process
US8938547B1 (en) 2014-09-05 2015-01-20 Openpeak Inc. Method and system for data usage accounting in a computing device
US9350818B2 (en) 2014-09-05 2016-05-24 Openpeak Inc. Method and system for enabling data usage accounting for unreliable transport communication
US9100390B1 (en) 2014-09-05 2015-08-04 Openpeak Inc. Method and system for enrolling and authenticating computing devices for data usage accounting
US20160071040A1 (en) 2014-09-05 2016-03-10 Openpeak Inc. Method and system for enabling data usage accounting through a relay
US9232013B1 (en) 2014-09-05 2016-01-05 Openpeak Inc. Method and system for enabling data usage accounting
US9785425B2 (en) 2014-09-30 2017-10-10 Airwatch Llc Managed clone applications
US9667715B2 (en) * 2014-11-07 2017-05-30 Sap Se Method for controlling changes in a computer system
US9584964B2 (en) 2014-12-22 2017-02-28 Airwatch Llc Enforcement of proximity based policies
US9413754B2 (en) 2014-12-23 2016-08-09 Airwatch Llc Authenticator device facilitating file security
CN104749961A (zh) * 2015-02-26 2015-07-01 青岛海尔股份有限公司 智能家电的数据通信系统和智能家电的数据通信方法
US20160294827A1 (en) * 2015-03-30 2016-10-06 Tangome, Inc. Account access authorizer
CN105718267B (zh) * 2016-01-19 2019-09-06 钱爱芬 一种多应用合并为单应用的实现方法及其实现系统
US10180834B2 (en) * 2016-02-29 2019-01-15 Airwatch Llc Provisioning of applications deployed on client devices
US9916446B2 (en) 2016-04-14 2018-03-13 Airwatch Llc Anonymized application scanning for mobile devices
US9917862B2 (en) 2016-04-14 2018-03-13 Airwatch Llc Integrated application scanning and mobile enterprise computing management system
EP3460657B1 (de) 2017-09-20 2021-09-08 Roche Diabetes Care GmbH Verfahren zur validierung einer medizinischen anwendung, endbenutzervorrichtung und medizinisches system
US10552136B2 (en) * 2018-06-29 2020-02-04 Alibaba Group Holding Limited One click application asset distribution
CN111665773B (zh) * 2020-07-02 2021-10-26 长沙钛合电子设备有限公司 物联网系统及构建方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3209308A (en) 1963-06-12 1965-09-28 Ark Les Switch Corp Printed circuit connector
US20020107809A1 (en) * 2000-06-02 2002-08-08 Biddle John Denton System and method for licensing management
US20070004393A1 (en) * 2005-06-29 2007-01-04 Nokia Corporation System and method for automatic application profile and policy creation
US20070136573A1 (en) * 2005-12-05 2007-06-14 Joseph Steinberg System and method of using two or more multi-factor authentication mechanisms to authenticate online parties
US20080201453A1 (en) 2007-02-19 2008-08-21 Ondeego, Inc. Methods and system to create applications and distribute applications to a remote device

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6021438A (en) * 1997-06-18 2000-02-01 Wyatt River Software, Inc. License management system using daemons and aliasing
US7415713B2 (en) * 2000-01-28 2008-08-19 Iona Technologies, Plc Method and system for dynamic configuration of interceptors in a client-server environment
TWI242725B (en) 2001-06-11 2005-11-01 Oce Tech Bv A method for executing a hot migrate operation through an incremental roll-over process that uses migration plug-in means for conversion during an upgrade transition, and a multiprocessing system and a system arranged for implementing such method
US7089259B1 (en) 2001-08-03 2006-08-08 Mcafee, Inc. System and method for providing a framework for network appliance management in a distributed computing environment
US20040002943A1 (en) 2002-06-28 2004-01-01 Merrill John Wickens Lamb Systems and methods for application delivery and configuration management of mobile devices
AU2003279246A1 (en) 2002-10-10 2004-05-04 Action Engine Corporation Method and apparatus for remote control and updating of wireless mobile devices
US8224750B1 (en) 2003-10-07 2012-07-17 Microsoft Corporation Method and system for upgrading licenses to installed software
US7516478B2 (en) 2005-06-03 2009-04-07 Microsoft Corporation Remote management of mobile devices
US20070271162A1 (en) 2005-11-07 2007-11-22 Shuster Gary S Invoice Management For Distributed Content
KR100829248B1 (ko) 2006-07-14 2008-05-14 엘지전자 주식회사 애드혹 통신을 이용한 이동통신단말기의 소프트웨어 패키지업데이트 방법,이를 수행하기 위한 이동통신단말기,애드혹 네트워크 상의 서빙 단말 설정방법, 및 애드혹네트워크 상의 서빙 단말을 이용한 클라이언트 단말의소프트웨어 패키지 업데이트 방법
US7917963B2 (en) * 2006-08-09 2011-03-29 Antenna Vaultus, Inc. System for providing mobile data security
US8793339B2 (en) * 2008-08-29 2014-07-29 Red Hat, Inc. Facilitating client server interaction
US8793398B2 (en) * 2008-08-29 2014-07-29 Red Hat, Inc. Facilitating client server interaction
US8250523B2 (en) * 2009-01-29 2012-08-21 Microsoft Corporation Source code wrapper generation
US20130117089A1 (en) 2011-11-04 2013-05-09 Alex Pachikov Software distribution on mobile networks

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3209308A (en) 1963-06-12 1965-09-28 Ark Les Switch Corp Printed circuit connector
US20020107809A1 (en) * 2000-06-02 2002-08-08 Biddle John Denton System and method for licensing management
US20070004393A1 (en) * 2005-06-29 2007-01-04 Nokia Corporation System and method for automatic application profile and policy creation
US20070136573A1 (en) * 2005-12-05 2007-06-14 Joseph Steinberg System and method of using two or more multi-factor authentication mechanisms to authenticate online parties
US20080201453A1 (en) 2007-02-19 2008-08-21 Ondeego, Inc. Methods and system to create applications and distribute applications to a remote device

Also Published As

Publication number Publication date
EP2561689A4 (de) 2016-11-16
US9185554B2 (en) 2015-11-10
WO2011037741A3 (en) 2011-08-04
WO2011037741A2 (en) 2011-03-31
US20110082900A1 (en) 2011-04-07
EP2561689A2 (de) 2013-02-27

Similar Documents

Publication Publication Date Title
US9185554B2 (en) System and methods to store, retrieve, manage, augment and monitor applications on appliances
US8984657B2 (en) System and method for remote management of applications downloaded to a personal portable wireless appliance
US20210405995A1 (en) Enterprise firmware management
US20210336942A1 (en) Managed domains for remote content and configuration control on mobile information devices
US9923902B2 (en) Remote processsing of mobile applications
US7865573B2 (en) Method, system and devices for communicating between an internet browser and an electronic device
US20120291103A1 (en) Permission-based administrative controls
US20120291102A1 (en) Permission-based administrative controls
CA2693723C (en) Automatic license key injection
CN104737175A (zh) 浏览器身份的方法及系统
CN103733663A (zh) 用于在移动装置上提供安全虚拟环境的方法和设备
CN101258505A (zh) 安全的软件更新
CN103713904A (zh) 在移动终端工作区内安装应用的方法、相关装置和系统
EP2761439A1 (de) Anwendungsauthentifizierungsrichtlinie für mehrere datenverarbeitungsvorrichtungen
CA2632510C (en) A method, system and devices for communicating between an internet browser and an electronic device
CN103763370B (zh) 一种更改移动终端工作区锁屏密码的方法、系统及装置
CN103036852A (zh) 一种实现网络登录的方法以及装置
WO2017120745A1 (zh) profile的处理方法、装置及系统
US20140282446A1 (en) Modification of compiled applications and application management using retrievable policies
US9544398B2 (en) System and methods to store, retrieve, manage, augment and monitor applications on appliances
CA2632509C (en) A method and system for performing a software upgrade on an electronic device connected to a computer
US10939297B1 (en) Secure unlock of mobile phone
KR102177764B1 (ko) 단말장치 및 그 제어 방법
US10798574B1 (en) Mobile communication device certification framework
KR100943126B1 (ko) 모듈형 무선 애플리케이션 프레임워크와 애플리케이션 업데이트 방법 및 이를 위한 기록매체

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

AC Divisional application: reference to earlier application

Ref document number: 2561689

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR

17P Request for examination filed

Effective date: 20221021

RBV Designated contracting states (corrected)

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS