Protected data usage in third party software applications
By using sandbox environments and private software components in third-party software applications, restricting data access rights, the problem of user data protection in third-party software applications is solved, and the secure use of data and privacy protection is achieved.
Patent Information
- Application Number
- CN202380028072.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-16
- Filing Date
- 2023-03-15
- Publication Date
- 2024-11-08
AI Technical Summary
The prior art is difficult to effectively protect user data in third-party software applications, resulting in data breaches and unauthorized access.
Adopt sandbox environment and private software components to restrict data access rights of third-party software applications through container software applications and private data storage devices, ensure that protected data is readable only in private software environments and written only in public software environments, and Prevent data breaches.
Effectively protect user data, prevent unauthorized access and disclosure, allow third-party software applications to use protected data without directly sharing it with third-party developers, and maintain data security and user privacy.
Smart Images

Figure CN118922830A_ABST
Abstract
Description
[0001] Priority declaration
[0002] This patent application claims the benefit of priority to U.S. application serial number 17 / 655,111, filed on March 16, 2022, the entire contents of which are incorporated herein by reference. Technical Field
[0003] Implementations described herein relate to augmented reality and, more particularly, but not by way of limitation, to systems, methods, devices, and instructions for protected data usage in third-party software applications. Background Art
[0004] A company or organization storing data related to its users or data created by its users may wish to allow a third party (e.g., a third-party developer) to use the data in a software application (e.g., a software service) developed by the third party to build or enhance other software services. For example, a third party may develop a third-party software application, such as a software plug-in or an embedded software component, which uses user data from a company or organization to enhance the software application from the company or organization. Traditionally, various authorization mechanisms are used by data resource holders (e.g., companies or organizations) to obtain permission to share data with third parties from their users, and based on these permissions, user data can be shared with third parties. Typically, data resource holders allow their users to revoke such permission. Traditional methods of user data sharing mechanisms involve user data that is actually shared with a third party so that a third-party software application uses the user data. Once user data is shared, it is usually held by a third party, and can remain held by the third party even after the user revokes the permission to use its user data by a third party. BRIEF DESCRIPTION OF THE DRAWINGS
[0005] In the drawings, which are not necessarily drawn to scale, reference numerals may describe similar components in different views. To easily identify the discussion of any particular element or action, the highest digit or digits in the reference numeral refer to the figure number in which the element is first introduced. Some non-limiting examples are shown in the figures of the accompanying drawings, in which:
[0006] Figure 1 is a block diagram representing a networked environment in which the present disclosure may be deployed according to some implementations.
[0007] Figure 2 is a block diagram showing details about the system according to some implementations.
[0008] Figure 3 is a block diagram illustrating an example implementation of a client application that enables protected data usage in a third-party software application in accordance with some implementations.
[0009] Figure 4 is a block diagram illustrating an example system that implements protected data usage in third-party software applications according to some implementations.
[0010] Figure 5 is a block diagram illustrating an example system for use with protected data in a third-party software application with multiple clients in accordance with some implementations.
[0011] Figure 6 is a diagram illustrating an example user interface generated by a client application that implements protected data usage in a third-party software application, according to some implementations.
[0012] Figure 7 is a diagram illustrating an example user interface generated by a client application that implements protected data usage in a third-party software application, according to some implementations.
[0013] Figure 8 is a flow diagram illustrating an example method of a client application for implementing protected data usage in a third-party software application according to some implementations.
[0014] Fig. 9 is a block diagram illustrating a representative software architecture that can be used in conjunction with the various hardware architectures described herein.
[0015] Fig.10 is a block diagram illustrating machine components capable of reading instructions from a machine-readable medium (eg, a machine-readable storage medium) and performing any one or more of the methodologies discussed herein, according to some implementations. DETAILED DESCRIPTION
[0016] Various embodiments provide systems, methods, devices, and instructions for protected data usage in third-party software applications, wherein the usage can be achieved while maintaining (e.g., controlling or ensuring) protection of the protected data relative to the third-party software application. Specifically, various embodiments provide a software application architecture that allows owners of protected data to support a software development ecosystem in which third parties can develop third-party software applications that use the protected data while denying the third parties access to the protected data.
[0017] For example, an implementation may allow a software developer (e.g., a third party) to create a third-party software application that uses a user's social network data (e.g., a user's friend relationships or a user's friend list) through a private software component to provide a social experience to the user without providing the software developer with access to or ownership of the user's social network data. For example, within a third-party software application, the private software component may enable data across conversations between friends on a social network to be shared without providing the software developer (or the third-party software application) with access to or ownership of conversation identifiers associated with the conversations. Additionally, within a third-party software application, the private software component may enable the user's social network data to be used in conjunction with external accounts or data (e.g., accounts or data associated with a third party) while maintaining protection of the user's social network data.
[0018] According to some embodiments, a system (e.g., a client system) is provided that includes a private data storage device and a protected data storage device, wherein a container software application is executed on the system (e.g., in a container software environment (e.g., an operating system on the system)), wherein a third-party software application is executed in a sandbox environment of the container software application that implements a public software environment, and wherein a private software component is executed in a sandbox environment of the third-party software application that implements a private software environment. For various embodiments, the system is configured so that the private data storage device provides read and write data access to the private software environment, and the private data storage device provides write-only data access to the public software environment. In various embodiments, the system is configured so that the protected data storage device provides read and write data access to the container software application, and provides read-only data access to the private software environment, while denying all data access to the public software environment. In this way, the protected data storage device of the system can store protected data that can be accessed (e.g., read or written) by the container software application, and can be accessed (e.g., read or used) by the private software component (from the third-party software application) for the benefit of the third-party software application, while preventing the third-party software application from having any data access or ownership to the protected data. In addition, for some embodiments, the system is configured so that the private data storage device provides read and write data access to the private software environment, and write-only data access to the public software environment. In this way, the private data storage device can enable a third-party software application to transmit data unidirectionally to the private software component, while preventing the third-party software application from having data access or ownership of any private data that the private software component may write to the private data storage device. According to an embodiment, the system can form at least a part of a client device. In addition, the container software application can form at least a part of a client software application (e.g., a software application or a social network client operating on a computing device (e.g., a desktop computer or a mobile device), and the protected data (e.g., a user's social network data (e.g., graph data)) can be associated with a user of the client software application.
[0019] By using various embodiments described herein, the leakage of protected data (e.g., user's friend relationship data) can be limited or prevented. In addition, various embodiments prevent data used by private software components from being exported to third parties or third-party software applications.
[0020] As used herein, protected data may include data stored, owned, or maintained by a data party, such as a company or organization (e.g., a company that operates a social network). According to various embodiments, protected data may be used by a private software component in a third-party software application while not sharing (e.g., directly sharing) the protected data with a third party associated with the third-party software application. Examples of protected data may include, but are not limited to, social network data of a user, such as graph data associated with a user or a social network friend list of the user.
[0021] As used herein, private data storage device (or private storage device) can include a database or database application for storing data from a public software environment (e.g., public context) and a private software environment (e.g., private context). As used herein, private data refers to data stored on a private data storage device. Private data can include, for example, data written (e.g., generated) by a third-party software application in response to the interaction of a user with a third-party software application. In addition, private data can include, for example, data read or written by a private software component in response to the interaction of a user with a private software component. According to some embodiments, the private software environment has a read data access right and a write data access right to the private data storage device, and the public software environment has a write data access right to the private data storage device, but has a limited read data access right or does not have a read data access right to the private data storage device. For some embodiments, the private data storage device is used by a public software environment or one or more software applications (e.g., third-party software applications) executed in a public software environment to transmit data to the private software environment or one or more software applications (e.g., private software components) executed in the private software environment.
[0022] As used herein, a protected data storage device (or protected storage device) may include a database or database application for storing protected data. As used herein, protected data refers to data stored on a protected data storage device and intended to be protected from access or ownership by a third-party software application. Private data may include, for example, data read or written by a container software application, such as in response to a user's interaction with a third-party software application. Protected data may be considered as data owned or held by a data party. According to some embodiments, a protected data storage device is readable and accessible from within a private software environment (e.g., a private context), rather than readable and accessible from within a public software environment (e.g., a public context).
[0023] As used herein, a sandbox environment (or sandbox) may include an environment (e.g., a software execution environment) for executing one or more software applications such that the one or more executing software applications have one or more restrictions on accessing environments outside the sandbox environment. These restrictions may be controlled by the sandbox environment rather than by the one or more executing applications. These restrictions may include, but are not limited to, limiting access to stored data, limiting access to memory locations, limiting access to network functions, limiting access to specific network addresses, preventing access to some or all of an operating system or application program interface (API) (e.g., a local device API), etc.
[0024] As used herein, a third-party software application may include a software application developed or created by a third party. According to some embodiments, a third-party software application provides software services to users using protected data (e.g., social network data associated with a user, such as a user's friend list).
[0025] As used herein, a public software environment (e.g., a public context) includes a software environment configured to operate a software application (e.g., a third-party software application that may be written by a third party, or a third-party software component (e.g., a public software component). As used herein, a private software environment (e.g., a private context) includes a software environment configured to operate a software application (e.g., a private software component) that may access protected data (e.g., social network user data) and may output (e.g., render) graphics to a display of a client device.
[0026] As used herein, third-party application data may include data created or used by a third-party software application as described herein. As used herein, a third party (or third-party developer) includes an individual or entity that develops or creates a third-party software application as described herein. For various embodiments, a third party develops or creates a third-party software application that uses protected data via a protected software component, but does not provide the third party with direct access to the protected data (or does not provide the third-party software application with ownership of the protected data).
[0027] As used herein, a private software component may include a software component that can access and use protected data (e.g., provided by a third party) from a third-party software application without sharing the protected data with the third-party software application or causing the third-party software application to have the protected data. Elements of a private software component may include interface elements, such as user interface elements, that enable the use of protected data through the private software component. In addition, one or more elements of a private software component may be developed or created by a data party for use by a third party to develop or create a private software component for use in a third-party software application. For some embodiments, the private software component is executed in a private software environment (e.g., a private context) in a third-party software application.
[0028] As used herein, a container software application includes a software application (e.g., developed or created by a data party that owns or holds protected data) that is configured to execute third-party software in a sandbox environment of the container software application. Examples of container software applications may include, but are not limited to, social network software applications that include a sandbox environment for executing third-party software applications in the social network software application. For example, the third-party software application may be configured to provide a software service that uses a user's social network data via a private software component executed in the third-party software application.
[0029] As used herein, a container software environment (e.g., a container context) may include a software environment configured to operate a container software application. Examples of container software environments may include, but are not limited to, an operating system of a computing device (e.g., a desktop computer, a laptop computer, or a mobile device).
[0030] As used herein, a data party includes an individual entity that owns, stores, holds, or otherwise maintains protected data. A data party may include a data owner, a data holder, or a data maintainer. For some embodiments, a data party develops or creates a container software application. A data party may provide a set of software tools (e.g., an API or SDK) that a third party may use in developing private software components that use protected data owned, stored, or maintained by a data party.
[0031] As used herein, an inline frame (or iframe) may include an element of a first document that can load a second document within the first document, wherein the element is configured to (e.g., be capable of) operating as a sandbox or virtual machine for a software application of the second document, and wherein the second document (e.g., its software application) cannot access elements of the first document (e.g., the parent frame). For example, the first document may include a Hypertext Markup Language (HTML) document, and the second document may include a document (e.g., a script file) having executable code (e.g., JavaScript code). According to various embodiments described herein, a first document associated with a container software application includes (e.g., contains) an iframe that loads a second document, wherein the second document is associated with a third-party software application. According to various embodiments, a second document includes (e.g., contains) another iframe that loads a third document associated with a private software component, and the iframe may operate as a sandbox or virtual machine for a private software component as described herein.
[0032] The following description includes systems, methods, techniques, instruction sequences, and computing machine program products that embody illustrative embodiments of the present disclosure. In the following description, for the purpose of explanation, many specific details are set forth to provide an understanding of various embodiments. However, it will be apparent to those skilled in the art that embodiments may be practiced without these specific details. Typically, known instruction instances, protocols, structures, and techniques are not necessarily shown in detail.
[0033] Reference will now be made in detail to embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein.
[0034] Figure 1 1 is a block diagram representing a networked environment in which the present disclosure may be deployed according to some embodiments. Specifically, the block diagram illustrates an example system 100 for exchanging data (e.g., messages and associated content) over a network according to some embodiments, wherein the system 100 includes a client application 104 (hereinafter, client application 104) that implements protected data access for third-party software applications. The system 100 may include multiple instances of a client device 102, each of the multiple instances hosting several applications including the client application 104. The client application 104 is communicatively coupled to a messaging server system 108 via a network 106 (e.g., the Internet). The client application 104 may also communicate with applications hosted locally on the client device 102 using an application program interface (API).
[0035] The client application 104 is capable of communicating and exchanging data (e.g., protected data as described herein) with another client or a messaging server system 108 via a network 106. The data exchanged between the client application 104 and the messaging server system 108 may include functionality (e.g., commands to activate functionality) as well as payload data (e.g., text, audio, video, or other multimedia data).
[0036] The messaging server system 108 provides server-side functionality to the client application 104 via the network 106. Although certain functions of the system 100 are described herein as being performed by the client application 104 or by the messaging server system 108, the location of certain functions within the client application 104 or the messaging server system 108 may be a design choice. For example, it may be technically preferable to initially deploy certain technologies and functions within the messaging server system 108, but later migrate the technologies and functions to the client application 104 where the client device 102 has sufficient processing power.
[0037] The messaging server system 108 supports various services and operations provided to the client applications 104. Such operations include sending data to the client applications 104, receiving data from the client applications 104, and processing data generated by the client applications 104. As examples, the data may include message content, client device information, geolocation information, media enhancements and overlays, message content persistence conditions, social network information, and live event information. For various embodiments, the data provided to the client applications 104 by the messaging server system 108 may be considered protected data; the data will be used by private software components executing (e.g., operating) in third-party software applications operating in the client applications 104. Data exchange within the system 100 is activated and controlled by functions available via the user interface (UI) of the client applications 104.
[0038] Turning now specifically to the messaging server system 108, an application program interface (API) server 110 is coupled to and provides a programming interface to an application server 112. The application server 112 is communicatively coupled to a database server 118, which facilitates access to a database 120 that stores data associated with messages processed by the application server 112. Similarly, a web server 124 is coupled to and provides a web-based interface to the application server 112. To this end, the web server 124 processes incoming network requests via the Hypertext Transfer Protocol (HTTP) and several other related protocols.
[0039] The API server 110 receives and sends message data (e.g., commands and message payloads) between the client device 102 and the application server 112. Specifically, the API server 110 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the client application 104 to activate the functions of the application server 112. According to various embodiments, the API server 110 exposes various functions supported by the application server 112, including: account registration, login functions, sending messages from the client application 104 to another client application via the application server 112, sending media files (e.g., images or videos) from the client application 104 to the messaging server 114, adding and removing entities (e.g., friends) in an entity graph (e.g., a social graph), opening application events (e.g., related to the client application 104), and for possible access and retrieval of protected data by the client application 104 or another client application. The protected data may include: a collection of media data (e.g., stories), settings of a collection, a friend list of the user of the client device 102, messages and content, and the positioning of friends in the social graph.
[0040] The application server 112 hosts several server applications and subsystems, including, for example, a messaging server 114, an image processing server 116, and a social networking server 122. The messaging server 114 implements several message processing techniques and functions, particularly those related to the aggregation and other processing of content (e.g., text and multimedia content) included in messages received from multiple instances of the client application 104. As will be described in more detail, text and media content from multiple sources can be aggregated into collections of content (e.g., referred to as stories or galleries). These collections are then made available to the client application 104. In view of the hardware requirements for such processing, other processor- and memory-intensive processing of data can also be performed on the server side by the messaging server 114.
[0041] The application server 112 also includes an image processing server 116 that is dedicated to performing various image processing operations, typically with respect to images or videos within the payload of messages sent from or received at the messaging server 114 .
[0042] The social network server 122 supports various social networking functions and services and makes these functions and services available to the messaging server 114. To this end, the social network server 122 maintains and accesses protected data in the database 120, such as an entity graph that facilitates the social networking functions and services. Examples of functions and services supported by the social network server 122 include identifying other users of the system 100 who have a relationship with a particular user or who the particular user is "following", and identifying interests and other entities of a particular user.
[0043] Returning to the client application 104, the features and functionality of the external resource (e.g., another application or applet) are made available to the user via the interface of the client application 104. In this context, "external" refers to the fact that the other application or applet is separate from the client application 104, which may be executed externally or internally to the client application 104. For various embodiments, the external resource executes as a third-party software application in the sandbox environment of the client application 104. Additionally, for some embodiments, the other external resource executes as a private software component in the sandbox environment of the third-party software application.
[0044] External resources (e.g., third-party software applications or proprietary software components as described herein) may be provided by a third party, but may also be provided by the creator or provider of the client application 104. For example, the proprietary software component may be provided by the creator or provider of the client application 104, or developed by a third party using software tools or libraries (e.g., APIs or SDKs) provided by the creator / provider. Depending on the implementation, the client application 104 may receive a user selection of an option to launch or access a feature of such an external resource.
[0045] The external resource can be another application installed on the client device 102 (e.g., a "local app"), or a small-scale version of an application (e.g., a "mini program") hosted on the client device 102 or located remotely from the client device 102 (e.g., on a third-party server). The small-scale version of the application includes a subset of the features and functions of the application (e.g., the full-scale, local version of the application) and is implemented using a markup language document. In one example, the small-scale version of the application (e.g., a "mini program") is a web-based markup language version of the application and is embedded in the client application 104. In addition to using markup language documents (e.g., a.*ml file), the mini program can include a scripting language (e.g., a.*js file or a.json file) and a style sheet (e.g., a.*ss file).
[0046] In response to receiving a user selection of an option to launch or access a feature of an external resource, the client application 104 determines whether the selected external resource is a web-based external resource or a locally installed application. In some cases, an application locally installed on the client device 102 can be launched in the client application 104 (e.g., a third-party software application or a proprietary software component of an embodiment), or independently and separately from the client application 104, for example, by selecting an icon corresponding to the application on a home page of the client device 102. A small-scale version of such an application can be launched or accessed via the client application 104, and in some examples, no part of the small-scale application can be accessed outside the client application 104 or only a limited part of the small-scale application can be accessed outside the client application 104. The small-scale application can be launched by the client application 104 when the client application 104 receives a markup language document associated with the small-scale application, for example, from a third-party server and processes such a document.
[0047] In response to determining that the external resource is a locally installed application, the client application 104 instructs the client device 102 to launch the external resource by, for example, executing locally stored code corresponding to the external resource in a sandbox environment of the client application 104 in some embodiments. In response to determining that the external resource is a web-based resource, the client application 104 communicates with (for example) a third-party server to obtain a markup language document corresponding to the selected external resource. The client application 104 then processes the obtained markup language document to present the web-based external resource in the user interface of the client application 104.
[0048] The client application 104 may notify the user of the client device 102 or other users (e.g., "friends") associated with such a user of activities occurring in one or more external resources. For example, the client application 104 may provide a notification related to the current or recent use of an external resource by one or more members of a group of users to a participant in a conversation (e.g., a chat session) within the client application 104. One or more users may be invited to join an active external resource or to start an external resource that has been recently used but is currently inactive (in a group of friends). The external resource may provide the participants in the conversation who each use the corresponding client application with the ability to share items, conditions, states, or locations in the external resource with one or more members of a group of users entering the chat session. The shared item may be an interactive chat card that members of the chat may interact with, for example, to start the corresponding external resource, view specific information within the external resource, or bring members of the chat to a specific location or state within the external resource. Within a given external resource, a response message may be sent to a user on the client application 104. The external resource may selectively include different media items in the response based on the current context of the external resource.
[0049] The client application 104 can present a list of available external resources (e.g., applications or applets) to the user to launch or access a given external resource. The list can be presented in the form of a context-sensitive menu. For example, icons representing different applications (or applets) in the application (or applet) can change based on how the user launches the menu (e.g., from a dialog interface or from a non-dialog interface).
[0050] The client application 104 implements various embodiments described herein. According to various embodiments, the client application 104 implements protected data usage in a third-party software application while maintaining (e.g., controlling or ensuring) protection of the protected data from use by the third-party software application. Specifically, the client application 104 of some embodiments executes the third-party software application in a sandbox environment of the client application 104, wherein a private software component is executed in the sandbox environment of the third-party software application, and wherein the private software component is configured to access (e.g., use) protected data on behalf of the third-party software application (e.g., for the benefit of the third-party software application) while preventing the third-party software application from accessing the protected data (e.g., using the protected data or obtaining ownership of the protected data).
[0051] Figure 2 is an illustration of some embodiments with respect to Figure 110. In particular, the system 100 is shown to include a client application 104 and an application server 112. The system 100 includes several subsystems that are supported on the client side by the client application 104 and on the server side by the application server 112. These subsystems include, for example, a transient timer system 202, a collection management system 204, an enhancement system 206, a map system 208, and a game system 210. According to an embodiment, at least some portions of the transient timer system 202, the collection management system 204, the enhancement system 206, the map system 208, the game system 210, or the external resource system 214, or protected data provided therefrom, can be accessed or used by a private software component that executes (e.g., operates) in a sandbox of a third-party software application that executes (e.g., operates) in the sandbox of the client application 104.
[0052] The transient timer system 202 is responsible for implementing temporary or time-limited access to content by the client application 104 and the messaging server 114. The transient timer system 202 includes several timers that selectively enable access (e.g., for presentation and display) of messages and associated content via the client application 104 based on duration and display parameters associated with a message or collection of messages (e.g., a story). Additional details regarding the operation of the transient timer system 202 are provided below.
[0053] The collection management system 204 is responsible for managing collections or collections of media (e.g., collections of text, images, video, and audio data). Collections of content (e.g., messages, including images, video, text, and audio) can be organized into "event galleries" or "event stories." Such collections can be made available for a specified time period (e.g., the duration of the event to which the content relates). For example, content related to a concert can be made available as a "story" for the duration of the concert. The collection management system 204 can also be responsible for publishing icons that provide notification to the user interface of the client application 104 of the existence of a particular collection.
[0054] The enhancement system 206 provides various functions that enable users to enhance (e.g., annotate or otherwise modify or edit) media content associated with a message. For example, the enhancement system 206 provides functions related to generating and publishing media overlays (media overlays) for messages processed by the system 100. The enhancement system 206 can operably supply media overlays or enhancements (e.g., image filters) to the client application 104 based on the geographic location of the client device 102. In another example, the enhancement system 206 can operably supply media overlays to the client application 104 based on other information (e.g., social network information of the user of the client device 102). Media overlays can include audio and visual content and visual effects. Examples of audio and visual content include pictures, text, logos, animations, and sound effects. Examples of visual effects include color overlays. Audio and visual content or visual effects can be applied to media content items (e.g., photos) at the client device 102. For example, media overlays can include text or images that can be superimposed on photos taken by the client device 102. In another example, the media overlay includes a location identifier (e.g., Venice Beach) overlay, the name of a live event, or a business name (e.g., Beach Cafe) overlay. In another example, the augmentation system 206 uses the geolocation of the client device 102 to identify a media overlay that includes the name of the business at the geolocation of the client device 102. The media overlay may include other logos associated with the business. The media overlay may be stored in the database 120 and accessed through the database server 118.
[0055] In some examples, the enhancement system 206 provides a user-based publishing platform that enables a user to select a geolocation on a map and upload content associated with the selected geolocation. The user can also specify the context in which a particular media overlay should be provided to other users. The enhancement system 206 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geolocation.
[0056] In other examples, the enhancement system 206 provides a merchant-based publishing platform that enables merchants to select specific media overlays associated with a geographic location via a bidding process. For example, the enhancement system 206 associates the highest bidding merchant's media overlay with the corresponding geographic location for a predefined amount of time.
[0057] Map system 208 provides various geolocation functions and supports Figure 1The client application 104 of the presents map-based media content and messages. For example, the mapping system 208 enables the display of a user icon or avatar (e.g., stored in profile data) on a map to indicate the current location or past location of the user's "friends" and media content (e.g., a collection of messages including photos and videos) generated by such friends within the context of the map. For example, on the map interface of the client application 104, a message posted by the user to the system 100 from a particular geographic location can be displayed to the "friends" of the particular user within the context of that location on the map. The user can also share his or her location and status information with other users of the system 100 (e.g., using an appropriate status avatar) via the client application 104, where the location and status information is similarly displayed to selected users within the context of the map interface of the client application 104.
[0058] The gaming system 210 provides various gaming functions within the context of the client application 104. The client application 104 provides a gaming interface that provides a list of available games that can be launched by a user within the context of the client application 104 and played with other users of the system 100. The system 100 also enables a particular user to invite other users to participate in playing a particular game by sending invitations to such other users from the client application 104. The client application 104 also supports both voice messaging and text messaging (e.g., chat) within the context of gaming, provides leaderboards for gaming, and supports the provision of in-game rewards (e.g., gaming coins and items).
[0059] Each third-party server hosts, for example, an application or a small-scale version of an application (e.g., a game, utility, payment, or ride-sharing application) based on a markup language (e.g., HTML5). The client application 104 can launch a web-based resource (e.g., an application) by accessing an HTML5 file from a third-party server associated with the web-based resource. In some examples, the applications hosted by the third-party servers are programmed in JavaScript using a software development kit (SDK) provided by the messaging server 114. The SDK includes an application programming interface (API) having functions that can be called or activated by a web-based application. In some examples, the messaging server 114 includes a JavaScript library that provides access to certain user data of the client application 104 to a given external resource. HTML5 is used as an example technology for programming games, but applications and resources programmed based on other technologies can be used.
[0060] To integrate the functionality of the SDK into a web-based resource, the SDK is downloaded by the third-party server from the messaging server 114, or received by the third-party server in other ways. Once downloaded or received, the SDK is included as part of the application code of the web-based external resource. The code of the web-based resource can then call or activate certain functions of the SDK to integrate the features of the client application 104 into the web-based resource.
[0061] The SDK stored on the messaging server 114 effectively provides a bridge between external resources (e.g., applications or applets) and the client application 104. This provides users with a seamless experience of communicating with other users on the client application 104 while also preserving the look and feel of the client application 104. In order to bridge the communication between the external resources and the client application 104, in some examples, the SDK facilitates communication between a third-party server and the client application 104. In some examples, the WebViewJavaScriptBridge running on the client device 102 establishes two one-way communication channels between the external resources and the client application 104. Messages are sent asynchronously between the external resources and the client application 104 via these communication channels. Each SDK function activation is sent as a message and a callback. Each SDK function is implemented by constructing a unique callback identifier and sending a message with the callback identifier.
[0062] By using the SDK, not all information from the client application 104 is shared with the third-party server. The SDK limits which information is shared based on the needs of the external resource. In some examples, each third-party server sends Figure 1 The messaging server 114 provides an HTML5 file corresponding to the web-based external resource. The messaging server 114 can add a visual representation (e.g., box art or other graphics) of the web-based external resource in the client application 104. Once the user selects the visual representation or instructs the client application 104 to access a feature of the web-based external resource through the graphical user interface (GUI) of the client application 104, the client application 104 obtains the HTML5 file and instantiates the resources required to access the feature of the web-based external resource.
[0063] The client application 104 presents a graphical user interface (e.g., a login page or title screen) for an external resource. During, before, or after presenting the login page or title screen, the client application 104 determines whether the launched external resource has been previously authorized to access the user data of the client application 104. In response to determining that the launched external resource has been previously authorized to access the user data of the client application 104, the client application 104 presents another graphical user interface of the external resource including the functions and features of the external resource. In response to determining that the launched external resource has not been previously authorized to access the user data of the client application 104, after a threshold time period (e.g., 3 seconds) of displaying the login page or title screen of the external resource, the client application 104 slides a menu for authorizing the external resource to access the user data (e.g., animating the menu to emerge from the bottom of the screen to the middle or other part of the screen). The menu identifies the type of user data that the external resource will be authorized to use. In response to receiving a user selection of the accept option, the client application 104 adds the external resource to the list of authorized external resources and enables the external resource to access the user data from the client application 104. In some examples, client application 104 authorizes external resources to access user data according to the OAuth 2 framework.
[0064] The client application 104 controls the type of user data shared with the external resource based on the type of external resource that is authorized. For example, an external resource comprising a full-scale application is provided with access to a first type of user data (e.g., only a two-dimensional avatar of a user with or without different avatar characteristics). As another example, an external resource comprising a small-scale version of an application (e.g., a web-based version of the application) is provided with access to a second type of user data (e.g., payment information, a two-dimensional avatar of a user, a three-dimensional avatar of a user, and an avatar with various avatar characteristics). Avatar characteristics include different ways to customize the look and feel of an avatar (e.g., different poses, facial features, clothing, etc.).
[0065] Figure 3 1 is a block diagram illustrating an example implementation of a client application 104 that implements protected data usage in a third-party software application according to some embodiments. The client application 104 is illustrated as including: a protected data storage component 302 for implementing or otherwise facilitating access to a protected data storage (e.g., a storage space or storage device); a private data storage component 304 for implementing or otherwise facilitating access to a private data storage (e.g., a storage space or storage device); and a third-party software application 306 that executes a private software component 320 in a sandbox of the third-party software application. For various embodiments, the components and arrangements of the components of the client application 104 may be similar to those of the third-party software application 306. Figure 3Any component of the client application 104 may be implemented using one or more processors (e.g., by configuring such one or more computer processors to perform the functions described for the component), and thus may include one or more of the processors. In addition, according to various embodiments, Figure 3 Any of the components shown in can be implemented together or separately within a single machine, database, or device, or can be distributed across multiple machines, databases, or devices. For example, a private data store, a protected data store, or both can be implemented by one or more databases (e.g., database 120) or data stores. For various embodiments described herein, the client application 104 includes or otherwise operates as a container software application within which a third-party software application 306 can be executed (e.g., operated).
[0066] Figure 4 4 is a block diagram illustrating an example system 400 that implements protected data usage in a third-party software application according to some embodiments. As shown, the system 400 includes a protected data storage 402, a private data storage 404, a container software application 406, and a display 408 of a computing device (e.g., client device 102). The system 400 can represent an architecture in which multiple environments (e.g., containers, public and private software environments) are used to execute the container software application 406, the third-party software application 420, and the private software component 430. For some embodiments, two or more private software components can execute (e.g., operate) in parallel within the third-party software application 420, and two or more third-party software applications can execute (e.g., operate) in parallel within the container software application 406.
[0067] User input data 410 may include one or more user inputs received by a computing device via a hardware or software user interface (e.g., a graphical user interface presented on display 408 or a human interface device (HID) coupled to or included by the computing device). As shown, user input data may be received by container software application 406, third-party software application 420, and proprietary software component 430. In addition, one or more of container software application 406, third-party software application 420, and proprietary software component 430 may output data or information (e.g., a graphical user interface having one or more elements) to display 408, or cause data or information to be output to display 408. For some embodiments, container software application 406 includes a display mechanism that is capable of synthesizing output data from two or more of container software application 406, third-party software application 420, and proprietary software component 430 to present output on display 408.
[0068] exist Figure 4 In the example, a data party may own, build, or maintain a container software application 406. The container software application 406 may execute a third-party software application 420 (which may be downloaded) within a sandbox environment or virtual machine of the container software application 406, which represents a public software environment (e.g., a public context). The public software environment may limit the capabilities of the third-party software application 420 by limiting, for example, one or more of the following: hardware access to features, memory access, and network access. The limitations may be predefined by the container software application 406.
[0069] In addition to this limitation, the third-party software application 420 can be configured to perform general computing by running executable code written by a third party, and can display data to an end user via the display 408. The third-party software application 420 can execute the private software component 430 within a sandbox environment or virtual machine of the third-party software application 420 (which represents a private software environment (e.g., a private context)). The private software component 430 can be developed (e.g., coded) by a third party (e.g., the same third party as the third-party software application 420) using a template language defined by the container software application 406 that is configured with limited functions. The template language can support the creation of interactive programs by a third party (using protected data), but does not allow the execution of arbitrary code. The private software component 430 can be generated (e.g., compiled) by converting, compiling, or translating the written template language into software code that can be executed within the private software environment. Communication from the public software environment to the private software environment can be supported, while reverse communication from the private software environment to the public software environment can be limited to specific events (e.g., user or predefined timer). In addition, any data included in the communication from the private software environment to the public software environment can be predefined when the template defining the private software component 430 is compiled into executable code. In this way, the private software component 430 can be prevented from leaking data (e.g., protected data) from the private software environment to the public software environment. Figure 4 The presented infrastructure can do the following: enable a third party to develop a third party software application 420 using a programming language for application development, enable a third party to develop a private software component 430 using a template language, and enable a data party (within a third party software application 420) to execute the third party software application 420 and the private software component 430 with little or no risk of protected data or private data being leaked to the third party software application 420 or a third party.
[0070] In various embodiments, the container software application 406 may represent a client software application (e.g., the client application 104), such as a client messaging application or a client social network application. According to an embodiment, the container software application 406 executes (e.g., operates) within a container software environment (e.g., a container context). For some embodiments, the third-party software application 420 executes (e.g., operates) within a public software environment (e.g., a public context) of the container software application 406 (e.g., a sandbox of the container software application 406). For some embodiments, the private software component 430 executes (e.g., operates) within a private software environment (e.g., a private context) of the third-party software application 420 (e.g., a sandbox of the container software application 406). For example, the container software application 406 loads a first document (e.g., an HTML document), in which case the public software environment may include an iframe of the first document, the third-party software application 420 may load a second document (e.g., another HTML document), the private software environment may include an iframe of the second document, and the private software component 430 may include a JavaScript script document or JavaScript code. Each or both of the protected data storage device 402, the private data storage device 404 can be implemented by a data storage service, one or more databases (e.g., a single database with separate storage space for the protected data storage device 402 and the private data storage device 404), or one or more data stores.
[0071] The third-party software application 420 may be developed (e.g., created) by a third party to use a first set of APIs (e.g., public APIs) and private software components 430 provided by an individual or entity (e.g., a data party) that develops (e.g., creates) the container software application 406. The third-party software application 420 may be developed by a third party to use a second set of APIs (e.g., private APIs) provided by an individual or entity. For some embodiments, the first set of APIs cannot access or directly use the protected data, while the second set of APIs can access or use the protected data on behalf of the third-party software application 420 while preventing the third-party software application 420 from accessing or owning the protected data.
[0072] For some embodiments, the private software component 430 is coded or developed (e.g., by a third party) using a template language. In this way, the private software component 430 can be compiled according to the template, and then an executable version of the private software component 430 is placed (e.g., inserted) or started in the third-party software application 420. The template language used to define the private software component 430 can be configured so that the operation or function provided by the private software component 430 is restricted (e.g., limited or controlled), thereby ensuring that the private software component 430 operates or behaves as expected (particularly in terms of accessing or using protected data). For example, the template language may include a plurality of tags that can be used as code for defining the private software component 430 and compiled into templated executable code. For example, the template language may include an HTML-like language that uses custom tags, attributes, or both to access a set of predefined functions (e.g., templated JavaScript functions) or access one or more style files. The compilation process may include one or more of the following operations: validating the template defining the private software component 430, wherein the validation does not allow or reject dangerous tags or invalid attributes; rejecting functions in the template that may facilitate leakage of protected data (e.g., cascading style sheet functions); compiling the tags in the template into templated JavaScript functions; and organizing the resulting output (e.g., templated JavaScript functions) into an executable component representing the private software component 430, which can be referenced by a third-party software application (e.g., 420).
[0073] According to an embodiment, the code of the private software component 430 may be included in the code of the third-party software application 420 and compiled together with the third-party software application 420. Alternatively, the code of the private software component 430 may be compiled separately from the third-party software application 420 (e.g., compiled outside the third-party software application 420) and launched within the third-party software application 420. For example, the private software component 430 may be compiled by the data party and then provided (e.g., provided from one of the application servers 112) to the third-party software application 420. In doing so, the data party may further ensure that the private software component 430 operates or behaves as expected (particularly in terms of accessing or using protected data).
[0074] Table 1 below provides an example of code that defines a private software component (eg, private software component 430).
[0075]
[0076] Table 2 below provides an example of code for inserting or launching a proprietary software component (eg, proprietary software component 430 ) in a third-party software application (eg, third-party software application 420 ).
[0077]
[0078] Depending on the implementation, the third-party software application 420, the private software component 430, or both may use (e.g., call or reference) one or more pre-formulated network requests (e.g., shared network requests), such as pre-formulated network requests sent by the private software component 430 to retrieve or use protected data (e.g., a request for a user to share a conversation with another user). The pre-formulated network requests may be cached (e.g., cached responses to the requests), proxied, or both cached and proxied on one or more external servers (e.g., one or more of the application servers 112), which may speed up responses to such requests (e.g., provide services) and maintain privacy and security (e.g., requests may be anonymized so that third parties are prevented from knowing which user is making the request). In addition, the use of pre-formulated network requests may ensure that the private software component 430 is limited or prevented from making any network requests (e.g., any network requests that may otherwise implement the sending of data or use of session timing that would allow the third-party software application 420 to infer user information).
[0079] The private software component 430 can delegate the sharing path, payload information, or both to the private software environment in which the private software component 430 is executing or the public software environment in which the third-party software application 420 is executing. In this manner, a user using features provided by the private software component 430 can have private data accessed or used by the private software component 430 shared and linked with another user (e.g., another social network user) without the third-party software application 420 (or a third party developing the third-party software application) having knowledge of the sharing. For example, a user can interact with a user interface provided by the private software component 430 on the display 408 to trigger a sharing feature provided by the container software application 406, which can allow the user to share protected data, such as the user's conversations, media content items, ratings, or comments posted on a social network.
[0080] According to various embodiments, private data storage 404 is configured to provide read and write data access to one or more private software environments, and to provide write-only data access to one or more public software environments. For some embodiments, protected data storage 402 is configured to provide read and write data access to one or more container software applications, to provide read data access to one or more private software environments, and to deny data access to one or more public software environments.
[0081] When the container software application 406 is executed (e.g., launched) on a computing device (e.g., client device 102), the container software application 406 can execute the third-party software application 420 in the public software environment by loading a rendered page (e.g., an HTML document) associated with the container software application 406. The rendered page can be provided from the private software environment so that the third-party software application 420 can have at least write data access rights with respect to the private data storage device 404. The iframe (e.g., a full-screen iframe) of the rendered page can be configured to execute code associated with the third-party software application 420 in the public software environment. For example, the public software environment can include an iframe within the third-party software application 420. In the public software environment, the third-party software application 420 can include (e.g., insert) a private software component 430 (e.g., included in an HTML DOM associated with the third-party software application 420) and communicate with the private software component 430. For example, the private software component 430 can be included in an iframe of the third-party software application. In this manner, third-party software applications 420 may communicate data to private software component 430 by writing the data to private data storage 404, and private software component 430 may be hosted in a private software environment, thereby providing private software component 430 with read and write access to private data storage 404. Additionally, private software component 430 may use one or more APIs (e.g., private APIs) that enable private software component 430 to request protected data (e.g., sensitive social network data from backend resources such as application server 112), which may be written to protected data storage 402 by container software application 406 and subsequently read from protected data storage 402 by private software component 430, thereby preventing third-party software applications 420 from accessing the protected data.
[0082] Various embodiments use a network security model (eg, domain separation according to the model) to facilitate data access control with respect to protected data storage 402 devices and private data storage 404 devices. For example, container software application 406 may be associated with a first URL (e.g., a uniform resource locator (URL), such as https: / / container.example.com / application.html) (e.g., container software application 406 includes a component retrieved from or generally associated with the first URL), which enables read and write data access with respect to protected data storage device 402, private software component 430 may be associated with a second URL (e.g., https: / / private-component.example.com / application.html) (e.g., private software component 430 is retrieved from or generally associated with the second URL), which enables read data access from protected data storage device 402 and read and write data access with respect to private data storage device 404, and third-party software application 420 may be associated with a third URL (e.g., https: / / third-party.example.com / application.html) (e.g., third-party software application 420 is retrieved from or generally associated with the third URL), which enables write data access to private data storage device 404. In such an example, the first web address can be used as an identifier of the container software application 406, which can be associated with the container software environment. The second web address can be used as an identifier of the private software component 430, which can be associated with the private software environment. Similarly, the third web address can be used as an identifier of the third-party software application 420, which can be associated with the public software environment. For some embodiments, each of the container software application 406, the third-party software application 420, and the private software component 430 is implemented by a separate web document (e.g., HTML document) retrieved from its respective web address (e.g., URL). In addition, for some embodiments, the web document that implements the container software application 406 includes an iframe (e.g., HTML iframe) that loads the web document that implements the third-party software application 420, and the web document that implements the third-party software application 420 includes an iframe that loads the web document that implements the private software component 430.
[0083] During operation, container software application 406 may write first protected data to protected data storage 402 and read second protected data from protected data storage 402. The first protected data may include, for example, authentication information of a user owned by container software application 406, which container software application 406 may share (via protected data storage 402) with private software component 430 to enable private software component 430 to perform operations or provide services using the user's protected data (e.g., social network data stored on one of application servers 112). According to an embodiment, in response to a request from private software component 430 to container software application 406, container software application 406 may provide the user's authentication information using one or more APIs (e.g., private APIs) accessible to private software component 430. Within the private software environment of third-party software application 420, private software component may read third protected data from protected data storage 402 while preventing third-party software application 420 from accessing the third protected data. Within the private software environment of the third party software application 420, the private software component may write first private data to the private data storage 404 and read second private data from the private data storage 404. Additionally, the third party software application 420 may write third party data to the private data storage while being denied read access to any data stored on the private data storage 404. With write-only data access to the private data storage 404, the third party software application 420 is able to communicate data (e.g., data generated by the third party software application 420 based on portions of the user input data 410) to the private software component 430 in a manner while preventing the third party software application 420 from gaining access to any protected data that the private software component 430 may be reading (e.g., using) from the protected data storage 402.
[0084] Figure 5is a block diagram illustrating an example system 500 for using protected data in a third-party software application in the case of multiple clients according to some embodiments. As shown, the system 500 includes third-party software applications 502-1 to 502-N used by user-1 to user-N, respectively, and a third-party software application 502-M used by the current user. Each of the third-party software applications 502-1 to 502-N and the third-party software application 502-M can represent a copy of the same third-party software application (e.g., a book review software application). Although not shown, each of the third-party software applications 502-1 to 502-N and the third-party software application 506 can be executed by a corresponding container software application (e.g., software application 406) (e.g., a social network software application). In addition, each of the third-party software applications 502-1 to 502-N includes private software components 520-1 to 520-N, respectively, and the third-party software application 502-M includes private software components 520-M. Each of the private software components 520-1 through 520-N and the private software component 520-M may represent a copy of the same private software component (e.g., a component that enables the use of user social network data in conjunction with a book review software application). The system 500 is also shown to include a private data storage device 504 and a display 508 to which the third-party software application 502-M and the private software component 520-M may output data (e.g., rendered data).
[0085] According to some embodiments, one or more of User-1 to User-N interact with their respective third-party software applications (502-1 to 502-N), which may cause their respective third-party software applications to store private data (e.g., book reviews or ratings entered by one or more of User-1 to User-N) to the private data storage device 504. Subsequently, the private software component 520-M may read at least some of the private data stored on the private data storage device 504, and may merge the protected data (e.g., user data) accessed by the private software component 520-M to display information (e.g., the user's book reviews and the user's corresponding user information) to the current user on the display 508. For example, the private software component 520-M may perform the following operations: read protected data describing the current user's friend list from the protected data storage device (not shown); read book review data written by one or more friends on the current user's friend list from the private data storage device 504, and display the book review data on the display 508. According to various embodiments, third party software application 502-M is prevented from accessing protected data accessed by proprietary software component 520-M, merged data generated by proprietary software component 520-M, or information displayed on display 508 by proprietary software component 520-M.
[0086] Figure 6 is a diagram illustrating an example user interface generated by a client application implementing protected data usage in a third-party software application according to some embodiments. Figure 6 6, a mobile device 610 (e.g., a smart phone) includes a display 620 or is coupled to a display 620. The mobile device 610 can execute a container software application in a container software environment (e.g., on an operating system of the mobile device 610), wherein the container software application executes a third-party software application in a public software environment of the container software application, and wherein the third-party software application executes each of one or more private software components in a separate private software environment of the third-party software application. As shown, the third-party software application causes a user interface to be generated and presented on the display 620, wherein the user interface may include a graphical button 628 generated based on code executing the third-party software application and one or more conventional HTML elements 622. As shown, a first private software component executed in a first private software environment of the third-party software application causes a user interface element 624 to be generated, and a second private software component executed in a second private software environment of the third-party software application causes a user interface element 626 to be generated. The user interface presented on display 620 may represent display output generated by a display mechanism of the container software application that merges together display output of the container software application, the third-party software application, and one or more of the first private software component and the second private software component to generate a final display output of display 620.
[0087] Figure 7 is a set of diagrams illustrating example user interfaces generated by a client application that implements protected data usage in a third-party software application according to some embodiments. Specifically, the user interface represents a user interface generated by a third-party software application that is configured to share a restaurant reservation with friends on a social network. Figure 7, a mobile device 710 (e.g., a smart phone) has a display 720. The mobile device 710 may execute a container software application in a container software environment (e.g., on an operating system of the mobile device 710), wherein the container software application executes a third-party software application (for sharing restaurant reservations) in a public software environment of the container software application, and wherein the third-party software application executes a private software component in a private software environment of the third-party software application. As shown at 700, the third-party software application causes a user interface to be generated on the display 720 that allows a user of the mobile device 710 to generate one or more restaurant reservations, or to view / check one or more generated restaurant reservations. The private software component (executed by the third-party software application) may be configured to access protected data describing a user's friend list (e.g., the user's social network data), and allow the user of the mobile device 710 to share one or more restaurant reservations generated by the third-party software application with one or more of the other users on the user's friend list. As shown at 702, the private software component causes a user interface 730 to be generated and displayed on the display 720, through which the user of the mobile device 710 can interact with features or functionality provided by the private software component. For example, in Figure 7 , user interface 730 lists friends of a user who are associated with a restaurant reservation generated by a third-party software application.
[0088] Figure 8 is a flow chart illustrating an example method 800 for a client application to implement protected data usage in a third-party software application according to some embodiments. Figure 8 The various methods described can be embodied in machine-readable instructions executed by one or more computer processors so that the operations of the methods can be partially or fully performed by Figure 1 102 to perform. Therefore, various methods are described herein by way of example with reference to the hardware processor of the client device 102. At least some of the operations of method 800 may be deployed on various other hardware configurations, and the methods described herein are not intended to be limited to being operated by the client device 102. Although the steps of the methods described herein can be depicted and described in a certain order, the order in which the operations are performed may vary between implementations. For example, one operation may be performed before, after, or simultaneously with another operation. In addition, in some implementations, the components described with respect to the methods are merely examples of components that may be used with the methods, and other components may also be used.
[0089] Now refer to Figure 8 At operation 802, the client device 102 causes execution of a container software application (e.g., Figure 4Container software application 406), wherein the client device 102 includes a private data storage device (e.g., Figure 4 private data storage device 404) and protected data storage device (e.g., Figure 4 The public software environment may include a single sandbox environment or a virtual machine. For example, the public software environment may be a Hypertext Markup Language (HTML) inline frame (iframe) element of an HTML document (e.g., associated with or implementing a container software application).
[0090] At operation 804, the client device 102 enables a third-party software application (e.g., Figure 4 The third-party software application 420 of the container software application is executed in the public software environment of the container software application. The private software environment may include a single sandbox environment or a virtual machine. For some embodiments, the private software environment is configured to prevent the third-party software application from accessing any data within the private software environment. For example, the private software environment is an HTML iframe element of an HTML document (e.g., associated with or implementing a third-party software application), which can be embedded in a (first) HTML iframe element of the public software environment. For some embodiments, operation 804 includes causing a rendering page to be loaded, wherein the rendering page includes the public software environment, and the rendering page is configured to load the third-party software application in the public software environment.
[0091] Thereafter, at operation 806, the client device 102 enables the proprietary software component (eg, Figure 4 The container software application is configured to write the first protected data to the protected data storage device and read the second protected data from the protected data storage device. For some embodiments, the private software component is configured to read the third protected data from the protected data storage device while preventing the third party software application from accessing the second protected data. For some embodiments, the private software component is configured to write the first private data to the private data storage device and read the second private data from the private data storage device. Additionally, for some embodiments, the third party software application is configured to write the third private data to the private data storage device.
[0092] In various embodiments, the private software component is compiled separately from the third-party software application. For example, the private software component can be compiled from third-party code that defines the private software component, wherein the third-party code is based on a template language. The private software component can be compiled, for example, from third-party code that includes at least one custom tag, wherein the custom tag corresponds to a defined function that causes a first protected data to be written to a protected data storage device, or causes a second protected data to be read from a protected data storage device. After compiling the private software component, the private software component can be inserted into the third-party software application (or referenced by the third-party software application).
[0093] Finally, at operation 808, the client device 102 receives user input through the private software component, which can cause the client device 102 to perform subsequent operations, such as one or more operations in operations 810 to 816. For example, at operation 810, the container software application can read protected data from the protected data storage device or write protected data to the protected data storage device based on the user input. At operation 812, the private software component can read protected data from the protected data storage device based on the user input. For example, the private software component can cause at least a portion of the protected data (read from the protected data storage device) to be presented on the display of the client device 102 while preventing a third-party software application from accessing at least a portion of the third protected data. At operation 814, the third-party software application can write private data to the private data storage device based on the user input. For example, the third-party software application can transmit data to the private software component by writing the private data to the private data storage device. For example, the private data written by the third-party software application and then read by the private software component can describe an event (e.g., a user event or a timer event) detected by the third-party software application. Additionally or alternatively, the private software component may read private data from or write private data to the private data storage device based on the user input at operation 816. Depending on the implementation, the user input may be received via a user interface associated with (e.g., provided by) one or more of the container software application, the third-party software application, and the private software component.
[0094] Software Architecture
[0095] Fig. 9900 is a block diagram illustrating a representative software architecture 904 that can be used in conjunction with the various hardware architectures described herein. The software architecture 904 is supported by hardware such as a machine 902, which includes a processor 920, a memory 926, and an I / O component 938. In this example, the software architecture 904 can be conceptualized as a stack of layers, where each layer provides specific functionality. The software architecture 904 includes layers such as an operating system 912, a library 910, a framework 908, and an application 906. In operation, the application 906 activates an API call 950 through the software stack and receives a message 952 in response to the API call 950.
[0096] The operating system 912 manages hardware resources and provides public services. The operating system 912 includes, for example, a kernel 914, a service 916, and a driver 922. The kernel 914 serves as an abstraction layer between the hardware and other software layers. For example, the kernel 914 provides functions such as memory management, processor management (e.g., scheduling), component management, networking, and security settings. The service 916 can provide other public services for other software layers. The driver 922 is responsible for controlling or interfacing with the underlying hardware. For example, the driver 922 may include a display driver, a camera driver, or Low-power drivers, Flash drivers, Serial communication drivers (e.g., USB drivers), Drivers, audio drivers, power management drivers, etc.
[0097] The library 910 provides a common low-level infrastructure used by the application 906. The library 910 may include a system library 918 (e.g., a C standard library) that provides functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. In addition, the library 910 may include an API library 924, such as a media library (e.g., a library for supporting the presentation and manipulation of various media formats, such as Moving Picture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC), Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group (JPEG or JPG), or Portable Network Graphics (PNG)), a graphics library (e.g., an OpenGL framework for presenting in two dimensions (2D) and three dimensions (3D) in graphics content on a display), a database library (e.g., SQLite providing various relational database functions), a web library (e.g., WebKit providing web browsing functions), etc. The library 910 may also include various other libraries 928 to provide many other APIs to the application 906.
[0098] The framework 908 provides a common high-level infrastructure used by the applications 906. For example, the framework 908 provides various GUI functions, high-level resource management, and high-level positioning services. The framework 908 can provide a wide range of other APIs that can be used by the applications 906, some of which can be specific to a particular operating system or platform.
[0099] In an example, applications 906 may include a home application 936, a contacts application 930, a browser application 932, a book reader application 934, a positioning application 942, a media application 944, a messaging application 946, a game application 948, and a variety of other applications such as third-party applications 940. Application 906 is a program that executes the functions defined in the program. Various programming languages can be used to create one or more of the applications 906 constructed in various ways, such as an object-oriented programming language (e.g., Objective-C, Java, or C++) or a procedural programming language (e.g., C or assembly language). In a specific example, third-party application 940 (e.g., a third-party application created by an entity other than the vendor of a particular platform using ANDROID TM or IOS TM Software Development Kit (SDK) can be used to develop applications on platforms such as IOS TM ANDROID TM , Mobile software running on the mobile operating system of the phone or another mobile operating system. In this example, third-party applications 940 can activate API calls 950 provided by the operating system 912 to facilitate the functions described herein.
[0100] Processing components
[0101] Fig.10 1 is a block diagram illustrating components of a machine 1000 capable of reading instructions from a machine-readable medium (e.g., a computer-readable storage medium) and performing any one or more of the methods discussed herein, according to some embodiments. Specifically, Fig.10A graphical representation of a machine 1000 in the example form of a computer system is shown within which instructions 1008 (e.g., software, programs, applications, applet, app, or other executable code) for causing the machine 1000 to perform any one or more of the methods discussed herein may be executed. Thus, the instructions 1008 may be used to implement the modules or components described herein. The instructions 1008 convert a general purpose, unprogrammed machine 1000 into a specific machine 1000 that is programmed to perform the functions described and illustrated in the manner described. In alternative embodiments, the machine 1000 operates as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 1000 may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 1000 may include, but is not limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular phone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of executing instructions 1008 that specify actions to be taken by the machine 1000, either sequentially or otherwise. In addition, while only a single machine 1000 is shown, the term "machine" should also be taken to include a collection of machines that individually or jointly execute instructions 1008 to perform any one or more of the methodologies discussed herein.
[0102] The machine 1000 may include a processor 1002 (including a processor 1006 and a processor 1010), a memory 1004, and an I / O component 1038, which may be configured to communicate with each other, for example, via a bus 1040. The memory 1004 may include a main memory 1012, a static memory 1014, or a storage unit 1016 (which includes a machine-readable medium 1018), which may be accessed by the processor 1002, for example, via the bus 1040. The storage unit 1016, the main memory 1012, and the static memory 1014 store instructions 1008 that embody any one or more of the methods or functions described herein. The instructions 1008 may also reside, completely or partially, within the main memory 1012, within the static memory 1014, within the storage unit 1016, within at least one of the processors 1002 (e.g., within a cache memory of a processor), or within any suitable combination thereof during execution thereof by the machine 1000. Thus, the main memory 1012, the static memory 1014, the storage unit 1016, and the memory of the processor 1002 are examples of machine-readable media.
[0103] The I / O components 1038 may include various components for receiving input, providing output, generating output, sending information, exchanging information, capturing measurements, etc. The specific I / O components 1038 included in a particular machine 1000 will depend on the type of machine. For example, a portable machine such as a mobile phone will likely include a touch input device or other such input mechanism, while a headless server machine will likely not include such a touch input device. It will be appreciated that the I / O components 1038 may include Fig.101024 and 1026. The I / O components 1038 are grouped according to their functions only to simplify the following discussion, and the grouping is by no means limiting. In various embodiments, the I / O components 1038 may include user output components 1024 and user input components 1026. The user output components 1024 may include visual components (e.g., displays such as plasma display panels (PDPs), light emitting diode (LED) displays, liquid crystal displays (LCDs), projectors, or cathode ray tubes (CRTs)), auditory components (e.g., speakers), haptic components (e.g., vibration motors, resistance mechanisms), other signal generators, etc. The user input components 1026 may include alphanumeric input components (e.g., keyboards, touch screens configured to receive alphanumeric input, optical keyboards, or other alphanumeric input components), point-based input components (e.g., mice, touch pads, trackballs, joysticks, motion sensors, or other pointing instruments), tactile input components (e.g., physical buttons, touch screens or other tactile input components that provide the location and / or force of touch or touch gestures), audio input components (e.g., microphones), etc.
[0104] The biometric component 1028 may include components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body gestures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweating, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. The motion component 1030 may include: an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, a rotation sensor component (e.g., a gyroscope), etc. The environment component 1032 may include, for example, an illumination sensor component (e.g., a photometer), a temperature sensor component (e.g., one or more thermometers that detect ambient temperature), a humidity sensor component, a pressure sensor component (e.g., a barometer), a sound sensor component (e.g., one or more microphones that detect background noise), a proximity sensor component (e.g., an infrared sensor that detects nearby objects), a gas sensor (e.g., a gas detection sensor for detecting the concentration of dangerous gases to ensure safety or for measuring pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment. The location component 1034 may include a positioning sensor component (e.g., a global positioning system (GPS) receiver component), an altitude sensor component (e.g., an altimeter or barometer that detects air pressure that can obtain altitude), an orientation sensor component (e.g., a magnetometer), etc.
[0105] A variety of technologies may be used to achieve communication. The communication component 1036 may be operable to couple the machine 1000 to the network 1020 or the device 1022. For example, the communication component 1036 may include a network interface component or other suitable device for interfacing with the network 1020. In other examples, the communication component 1036 may include a wired communication component, a wireless communication component, a cellular communication component, a near field communication (NFC) component, Parts (e.g. Low power consumption), Device 1022 may be another machine or any of a variety of peripheral devices (eg, a peripheral device coupled via a universal serial bus (USB)).
[0106] In addition, the communication component 1036 can detect an identifier or include a component that is operable to detect an identifier. For example, the communication component 1036 can include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting the following items: a one-dimensional barcode such as a universal product code (UPC) barcode; a multi-dimensional barcode such as a Quick Response (QR) code, an Aztec code, a data matrix, a data glyph, a MaxiCode, a PDF417, a super code, a UCC RSS-2D barcode, and other optical codes), or an acoustic detection component (e.g., a microphone for an audio signal of an identification tag). In addition, various information can be obtained via the communication component 1036, such as a location via Internet Protocol (IP) geolocation, ... Signal triangulation to obtain location, location obtained via detection of NFC beacon signals that can indicate a specific location, etc.
[0107] Throughout this specification, multiple instances can implement components, operations or structures described as single instances. Although the individual operations of one or more methods are shown and described as separate operations, one or more individual operations can be performed simultaneously, and there is no requirement to perform these operations in the order shown. The structure and function presented as separate components in the example configuration can be implemented as a combined structure or component. Similarly, the structure and function presented as a single component can be implemented as a separate component. These and other variations, modifications, additions and improvements fall within the scope of the subject matter herein.
[0108] Although an overview of the various embodiments has been described with reference to specific embodiments, various modifications and changes may be made to these embodiments without departing from the broader scope of the embodiments of the present disclosure.
[0109] The embodiments shown herein are described in sufficient detail to enable those skilled in the art to practice the disclosed teachings. Other embodiments may be derived from the embodiments shown herein, and structural and logical substitutions and changes may be made without departing from the scope of the present disclosure. Therefore, the specific embodiments are not adopted in a limiting sense, and the scope of the various embodiments is limited only by the appended claims together with the full scope of equivalents to which such claims are entitled.
[0110] As used herein, the term "or" can be interpreted in an inclusive or exclusive sense. The term "a" or "an" should be interpreted to mean "at least one," "one or more," etc. The use of words and phrases such as "one or more," "at least," "but not limited to," or other similar phrases should not be interpreted to mean that a narrower case is intended or required where such an expanded phrase may not be present.
[0111] The boundaries between various resources, operations, components, modules, engines, and data stores are somewhat arbitrary, and specific operations are shown in the context of specific illustrative configurations. Other functional allocations are contemplated and may fall within the scope of various embodiments of the present disclosure. Typically, structures and functions presented as separate resources in the example configurations may be implemented as combined structures or resources. Similarly, structures and functions presented as single resources may be implemented as separate resources. These and other variations, modifications, additions, and improvements fall within the scope of embodiments of the present disclosure as represented by the appended claims. Therefore, the specification and drawings should be considered in an illustrative rather than a restrictive sense.
[0112] The above description includes systems, methods, devices, instructions and computer media (e.g., computing machine program products) that embody illustrative embodiments of the present disclosure. In the description, for the purpose of illustration, many specific details are set forth in order to provide an understanding of the various embodiments of the subject matter of the present invention. However, it will be apparent to those skilled in the art that the embodiments of the subject matter of the present invention can be practiced without these specific details. Typically, known instruction instances, protocols, structures and techniques are not necessarily shown in detail.
[0113] Glossary
[0114] "Carrier signal" refers to any intangible medium that can store, encode or carry instructions for execution by a machine and includes digital or analog communications signals or other intangible media that facilitates communication of such instructions. Instructions may be sent or received over a network using a transmission medium via a network interface device.
[0115] "Client Device" refers to any machine that interfaces with a communications network to obtain resources from one or more server systems or other client devices. A client device may be, but is not limited to, a mobile phone, a desktop computer, a laptop computer, a portable digital assistant (PDA), a smart phone, a tablet computer, an ultrabook, a netbook, a laptop computer, a multiprocessor system, a microprocessor-based or programmable consumer electronics, a game console, a set-top box, or any other communications device that a user may use to access a network.
[0116] "Communications network" means one or more parts of a network, which may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a part of the Internet, a part of the public switched telephone network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, A network, other type of network, or a combination of two or more such networks. For example, the network or a portion of the network may include a wireless network or a cellular network, and the coupling may be a code division multiple access (CDMA) connection, a global system for mobile communications (GSM) connection, or other type of cellular or wireless coupling. In this example, the coupling may implement any of various types of data transmission technologies, such as single carrier radio transmission technology (1xRTT), evolution data optimized (EVDO) technology, general packet radio service (GPRS) technology, enhanced data rates for GSM evolution (EDGE) technology, the third generation partnership project (3GPP) including 3G, fourth generation wireless (4G) networks, universal mobile telecommunications system (UMTS), high speed packet access (HSPA), world wide interoperability for microwave access (WiMAX), long term evolution (LTE) standards, other data transmission technologies defined by various standard setting organizations, other long distance protocols, or other data transmission technologies.
[0117] "Component" refers to a logic, device or physical entity with boundaries defined by function or subroutine calls, branch points, APIs or other technical definitions that provide partitioning or modularization for specific processing or control functions. Components can be combined with other components via their interfaces to perform machine processing. Components can be encapsulated functional hardware units designed for use with other components, and part of a program that generally performs a specific function of a related function. Components can constitute software components (e.g., codes implemented on machine-readable media) or hardware components. "Hardware components" are tangible units that can perform certain operations and can be configured or arranged in a certain physical manner. In various examples, one or more computer systems (e.g., independent computer systems, client computer systems, or server computer systems) or one or more hardware components (e.g., processors or processor groups) of a computer system can be configured to operate to perform certain operations as described herein by software (e.g., applications or application parts). Hardware components can also be implemented mechanically, electronically, or in any suitable combination thereof. For example, a hardware component may include a dedicated circuit or logic that is permanently configured to perform certain operations. The hardware component may be a dedicated processor, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). The hardware component may also include a programmable logic or circuit system that is temporarily configured to perform certain operations by software. For example, the hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, the hardware component becomes a specific machine (or a specific component of a machine) that is uniquely customized to perform the configured function, and is no longer a general-purpose processor. It should be recognized that it can be determined for cost and time considerations whether to mechanically implement the hardware component in a dedicated and permanently configured circuit system or in a temporarily configured (e.g., configured by software) circuit system to implement the hardware component. Therefore, the phrase "hardware component" (or "hardware-implemented component") should be understood to include a tangible entity, that is, an entity that is physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in some way or perform certain operations described herein. Considering an example in which a hardware component is temporarily configured (e.g., programmed), it is not necessary to configure or instantiate each hardware component in the hardware component at any time. For example, in the case where a hardware component includes a general-purpose processor that is configured by software to become a special-purpose processor, the general-purpose processor can be configured into different special-purpose processors (e.g., including different hardware components) at different times. The software configures one or more specific processors accordingly, for example, to constitute a specific hardware component at one time and to constitute different hardware components at different times. Hardware components can provide information to other hardware components and receive information from other hardware components. Therefore, the described hardware components can be considered to be communicatively coupled.In the case of multiple hardware components being present at the same time, communication can be achieved by signal transmission (e.g., by appropriate circuits and buses) between or among two or more hardware components. In examples where multiple hardware components are configured or instantiated at different times, communication between such hardware components can be achieved, for example, by storing information in a memory structure accessible to multiple hardware components and retrieving information in the memory structure. For example, a hardware component can perform an operation, and the output of the operation is stored in a memory device coupled in communication. Then, other hardware components can subsequently access the memory device to retrieve the stored output and process it. The hardware component can also initiate communication with an input device or an output device, and can operate on resources (e.g., a collection of information). The various operations of the example methods described herein can be performed at least in part by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform related operations. Whether it is temporarily configured or permanently configured, such a processor can constitute a processor-implemented component that operates to perform one or more operations or functions described herein. As used herein, "processor-implemented components" refer to hardware components implemented using one or more processors. Similarly, the method described in this article can be implemented at least in part by a processor, wherein one or more specific processors are examples of hardware. For example, at least some operations in the operation of the method can be performed by one or more processors 1002 or the parts implemented by the processor. In addition, one or more processors can also operate to support the execution of related operations in a "cloud computing" environment or as a "software as a service" (SaaS) operation. For example, at least some operations in the operation can be performed by a computer group (as an example of a machine including a processor), wherein these operations can be accessed via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., API). The execution of certain operations can be distributed between processors, and the processor not only resides in a single machine, but is also deployed on several machines. In some examples, a processor or a part implemented by a processor can be located in a single geographic location (e.g., in a home environment, an office environment, or a server cluster). In other examples, a processor or a part implemented by a processor can be distributed across several geographic locations.
[0118] "Computer-readable storage media" refers to both machine storage media and transmission media. Therefore, these terms include both storage devices / media and carrier / modulated data signals. The terms "machine-readable medium," "computer-readable medium," and "device-readable medium" mean the same thing and may be used interchangeably in this disclosure.
[0119] "Ephemeral messages" are messages that are accessible for a limited duration. Ephemeral messages can be text, images, videos, etc. The access time for ephemeral messages can be set by the sender of the message. Alternatively, the access time can be a default setting or a setting specified by the recipient. Regardless of the setting technique, the message is transient.
[0120] "Machine storage media" refers to a single or multiple storage devices and media (e.g., centralized or distributed databases, and associated caches and servers) that store executable instructions, routines, and data. Therefore, the term should be considered to include, but is not limited to, solid-state memory and optical and magnetic media, including memory internal or external to the processor. Specific examples of machine storage media, computer storage media, and device storage media include: non-volatile memory, including, for example, semiconductor memory devices, such as erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGA, and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms "machine storage media", "device storage media", and "computer storage media" mean the same thing and may be used interchangeably in this disclosure. The terms "machine storage media", "computer storage media", and "device storage media" explicitly exclude carrier waves, modulated data signals, and other such media, at least some of which are covered by the term "signal media". "Machine-readable media" may refer to a single storage device or device, as well as a "cloud-based" storage system or storage network that includes multiple storage devices or devices.
[0121] “Non-transitory computer-readable storage medium” refers to tangible media capable of storing, encoding, or carrying instructions to be executed by a machine.
[0122] "Signal medium" refers to any intangible medium that can store, encode or carry instructions executed by a machine and includes digital or analog communication signals or other intangible media that facilitate the communication of software or data. The term "signal medium" should be deemed to include any form of modulated data signals, carrier waves, etc. The term "modulated data signal" refers to a signal that has one or more of its characteristic sets set or changed in such a way as to encode information in the signal. The terms "transmission medium" and "signal medium" refer to the same thing and may be used interchangeably in this disclosure.
Claims
1. A system comprising: Private data storage device; protected data storage device; one or more hardware processors; as well as One or more machine-readable media storing instructions that, when executed by the one or more hardware processors, cause the system to perform operations comprising: enabling execution of a container software application; causing the container software application to execute a third-party software application within a common software environment of the container software application; and The third-party software application is caused to execute a private software component in a private software environment of the third-party software application, the container software application is configured to write first protected data to the protected data storage device and read second protected data from the protected data storage device, the private software component is configured to read third protected data from the protected data storage device while preventing the third-party software application from accessing the second protected data, the private software component is configured to write first private data to the private data storage device and read second private data from the private data storage device, and the third-party software application is configured to write third private data to the private data storage device.
2. The system according to claim 1, wherein: The private data storage device is configured to provide read and write data access to one or more private software environments and to provide write-only data access to one or more public software environments, and wherein the protected data storage device is configured to provide read and write data access to a container software application, to provide read data access to one or more private software environments, and to deny data access to one or more public software environments.
3. The system according to claim 1, comprising: A display, the proprietary software component being configured to cause at least a portion of the third protected data to be presented on the display while preventing the third party software application from accessing at least a portion of the third protected data.
4. The system according to claim 1, wherein: The private data storage device includes a database.
5. The system according to claim 1, wherein: The protected data storage device includes a database.
6. The system according to claim 1, wherein: The third party software application transfers data to the private software component by writing the third private data to the private data storage device.
7. The system according to claim 1, comprising: A display, the proprietary software component being configured to cause a user interface to be presented on the display and to receive user input through the user interface.
8. The system according to claim 1, wherein: The second private data describes an event detected by the third party software application.
9. The system according to claim 1, wherein: The public software environment includes at least one of a sandbox environment or a virtual machine.
10. The system according to claim 1, wherein: The private software environment includes at least one of a sandbox environment or a virtual machine.
11. The system according to claim 1, wherein: The common software environment is a Hypertext Markup Language (HTML) inline frame (iframe) element.
12. The system according to claim 11, wherein: The HTML iframe element is a first HTML iframe element, and wherein the proprietary software environment is a second HTML iframe element embedded in the first HTML iframe element.
13. The system of claim 1, wherein: The proprietary software environment is configured to prevent the third-party software application from accessing any data in the proprietary software environment.
14. The system of claim 1, wherein: The proprietary software component is compiled separately from the third party software application.
15. The system of claim 1, wherein: The proprietary software component is compiled from third-party code that defines the proprietary software component, the third-party code being based on a template language.
16. The system of claim 15, wherein: After the proprietary software component is compiled, the proprietary software component is inserted into the third-party software application.
17. The system of claim 1, wherein: The proprietary software component is compiled from third-party code including at least one custom tag, wherein the at least one custom tag corresponds to a defined function, wherein the defined function causes the first protected data to be written to the protected data storage device, or causes the second protected data to be read from the protected data storage device.
18. The system of claim 1, wherein: Causing the container software application to execute the third-party software application in the common software environment includes: The rendering page is caused to be loaded, the rendering page including the common software environment, the rendering page being configured to load the third-party software application in the common software environment.
19. A method comprising: causing, by one or more hardware processors of a client device, execution of a container software application on the client device, the client device comprising a private data storage device and a protected data storage device; causing the container software application to execute a third-party software application within a common software environment of the container software application; as well as The third-party software application is caused to execute a private software component within a private software environment of the third-party software application, the container software application is configured to write first protected data to the protected data storage device and read second protected data from the protected data storage device, the private software component is configured to read third protected data from the protected data storage device while preventing the third-party software application from accessing the second protected data, the private software component is configured to write first private data to the private data storage device and read second private data from the private data storage device, and the third-party software application is configured to write third private data to the private data storage device.
20. A non-transitory machine-readable medium storing instructions that, when executed by one or more hardware processors of a client device, cause the client device to perform operations comprising: causing execution of a container software application on the client device, the client device comprising a private data storage device and a protected data storage device; causing the container software application to execute a third-party software application within a common software environment of the container software application; as well as The third-party software application is caused to execute a private software component within a private software environment of the third-party software application, the container software application is configured to write first protected data to the protected data storage device and read second protected data from the protected data storage device, the private software component is configured to read third protected data from the protected data storage device while preventing the third-party software application from accessing the second protected data, the private software component is configured to write first private data to the private data storage device and read second private data from the private data storage device, and the third-party software application is configured to write third private data to the private data storage device.
