Patent Grant
10972468
Enterprises increasingly rely on management systems—such as an Enterprise Mobility Management (“EMM”) or Mobile Device Management (“MDM”) system—to manage the mobile devices of their employees. These systems can competently manage both enterprise-owned and user-owner devices. But in order to manage a device, that device must first be enrolled with the management system. The enrollment process can be inefficient, leading to productivity losses or even discouraging employees from enrolling at all.
One example inefficiency of some management systems is the lack of fine control over when enrollment is required. For example, a device assigned to a Research Engineer probably needs the security provided by immediately enrolling in the management system, while a device assigned to a sales intern may not need that level of security from day one. But current management systems are blind to these differences when it comes to the timing of enrollment, applying blanket requirements to different groups having distinct security needs.
Another inefficiency of some management systems is the requirement of a dedicated application, such as an agent application, that must be downloaded to a device to perform enrollment. Injecting this application into the enrollment process slows the enrollment process, decreases employee productivity, and can discourage some employees from enrolling at all. While these dedicated applications may have been necessary for older operating systems executed by mobile devices, newer operating systems can potentially perform enrollment without such application. But the current management systems lack the ability to recognize these distinctions or take advantage of them.
As a result, a need exists for improved systems and methods of adaptively providing device enrollment into an EMM or MDM system. More specifically, needs exist for these systems and methods to adaptively select enrollment workflows based on information specific to the device and its user, and perform enrollment directly from an application that increases, rather than decreases, employee productivity.
Examples described herein include systems and methods for dynamically determining enrollment requirements and enrolling a user device into a management system. The systems and methods can differ based on the type and version of operating system executing on the user device. In one example, a method can include receiving user credentials at a user interface (UI) of an application installed on the user device. The credentials can be entered manually by the user, for example. The method can also include receiving, at the application, an access token based on the user credentials. The access token can be received from an identity management service or other service that manages access tokens.
The method can also include receiving, at the application, an identification of an organizational group to which the user belongs. The user can manually select the organizational group, or the organizational group can be looked up by a separate service, such as an auto-discover service. The auto-discover service can identify an organizational group based on the user's email address, for example. The method can include determining whether the identified organizational group enables the user device to directly enroll with the management system.
If the organizational group is not enabled, the method can include requesting a list of child organizational groups available for the identified organizational group and receiving an indication of at least one of the child organizational groups to which the user belongs. The method can then include determining whether the child organizational group enables the user device to directly enroll with the management system. If so, the method can include requesting the assessment by the management server that the user device is allowed to enroll at the management server. If the child organizational group does not enable the user device to directly enroll, then enrollment may require downloading and installing an agent application.
If the identified organizational group enables the user device to directly enroll with the management system, the method can also include requesting an assessment by a management server that the user device is allowed to enroll at the management server. The assessment can be based on restrictions stored at the management server. One assessment allows for a user device to receive direct enrollment. Direct enrollment allows a user device to receive full management capabilities without having to go through an agent-based enrollment process, in which a management agent is first installed on the user device. In one example, when a user logs into an enterprise application, the management server can determine the user device should receive direct enrollment based on, for example, an organizational group associated with the user. Even where the selected organizational group enables direct enrollment, the device may not pass the assessment based on one or more restrictions set at the management server, such as when the device is jailbroken.
In one example, direct enrollment includes presenting a screen to the user to allow the user to select which elements of a full enrollment package to install. This can allow all the selected apps to be pushed to the user device as part of one transaction, in an example, rather than the user having to cancel each installation of apps they do not want. This can decrease the number of prompts presented to the user compared to normal enrollment.
The method can include receiving the assessment that the user device is allowed to enroll at the management server. The method can also include prompting the user to provide a selection indicating whether the user device is corporate owned, and based on the selection, presenting a terms-of-use agreement to the user. The application UI can then display a prompt for the user to proceed with enrollment, and upon selection, the user device can be enrolled with the management server by the application. The application UI can then display a prompt to select one or more managed applications to install on the user device. The method can include downloading the managed applications selected by the user at the application UI.
The method can also include determining whether the operating system of the user device requires an enterprise feature to be enabled in order to perform direct enrollment. If so, the method can include confirming that the enterprise feature has been enabled for the user device.
Another example method can be applied in some situations, such as the user device is not able to directly enroll with the management system through the application, for example, based on the capabilities of the operating system installed on the user device. That example method can include receiving user credentials at a UI of an application installed on the user device, receiving an access token based on the user credentials, and receiving an identification of an organizational group to which the user belongs. Receiving the identification or an organizational group can also include requesting a list of child organizational groups available for the identified organizational group and receiving an indication of at least one of those child organizational groups to which the user belongs. The method can also include determining that the user device is not able to directly enroll with the management system through the application.
If the user device is not able to directly enroll, the method can include pausing the UI of the application and redirecting the user to download an agent application. The user device can download and install the agent application and then pass the user credentials from the application to the agent application. The method can also include prompting the user to provide a selection at a UI of the agent application indicating whether the user device is corporate owned, and based on the selection, presenting a terms-of-use agreement to the user.
The agent can enroll the user device with the management server. The method can then include unpausing the UI of the application and displaying, on the UI, a prompt for the user to select one or more managed applications to install on the user device. The selected managed applications can then be downloaded.
Determining that the device is not able to directly enroll can include determining that the operating system of the user device requires an enterprise feature to be enabled in order to perform direct enrollment, and that the enterprise features has not been enabled for the user device. In another example, determining that the user device is not able to directly enroll with the management system through the application can include determining that the identified organizational group does not enable the user device to directly enroll.
In another example, a method is provided for enrolling a user device with a management system using a portal application. The portal application can be an application that provides varying levels of access to multiple other applications that may or may not be installed on the user device. The portal application can display application icons for any icons the user can access, or could potentially access. The portal application can store a user's credentials and provide access to any of the applications represented by the icons on the display by authenticating the user to the applications. For example, the portal application can utilize SSO services to provide access to the applications.
Some applications can require enrollment with a management system in order to access. The portal application can assist in the enrollment process by communicating with a management server—such as by exchanging tokens—obviating the need to download a management-dedicated application, such as an agent application. After enrolling the user device with the management system through the portal application, the portal application can be provided with access to enterprise data. For example, the portal application can provide access to an enterprise application.
Enrolling the user device with the management server can establish management control over the user device. For example, the management server can send policies to the portal application. Those policies can provide restrictions or other requirements for the user device, including remedial actions for when those restrictions or requirements are not met. Similarly, the portal application can receive and enforce compliance rules sent by the management server. If a compliance rule is broken, the portal application can take remedial action as instructed by the management server.
In another example, a method is provided for determining organizational-group-based enrollment requirements for enrolling a user into a management system. The example method can include receiving, at a portal application installed on the user device, an identification of an organizational group to which the user belongs. The identification can be obtained by the portal application requesting a lookup of the organizational group at an auto-discover service, for example. It can also be obtained by prompting the user for manual input regarding their organizational group.
The method can also include receiving a determination as to whether the identified organizational group enables the portal application to enroll with the management system. If enrollment by the portal application is enabled for that organizational group, then the portal application can request enrollment. If enrollment is not enabled for that organizational group, then the portal application can request a list of child organizational groups available for the identified organizational group.
The portal application can then receive an indication of at least one of the child organizational groups. For example, the user can manually select one of the child organizational groups. In another example, a lookup is performed based on information associated with the user and the results are returned to the portal application. Having narrowed down a particular child organizational group, the portal application can then receive a determination as to whether that child organizational group allows for direct enrollment by the portal application. If so, the portal application can request enrollment at the management server.
As part of the enrollment process, the portal application can prompt the user to provide a selection indicating whether the user device is corporate owned. Based on that selection, the portal application can present a terms-of-use agreement to the user.
The example methods summarized above can be incorporated into a non-transitory, computer-readable medium having instructions that, when executed by a processor associated with a computing device, cause the processor to perform stages for dynamically determining enrollment requirements and enrolling a user device into a management system. Additionally, the example methods summarized above can be implemented in a system including, for example, a user device, management server, identity management service, auto-discover service, orchestration server, or any combination thereof.
Both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the examples, as claimed.
Reference will now be made in detail to the present examples, including examples illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.
In a first set of examples, systems and methods are provided for dynamically determining enrollment requirements and enrolling a user device into a management system using a single application on the user device. These examples can be useful in situations where a user device includes an operating system that is configured to perform direct enrollment. They can also be useful in situations where the user is associated with an organizational group that allows for direct enrollment.
In a second set of examples, systems and methods are provided for dynamically determining enrollment requirements and enrolling a user device into a management system by pausing the UI of a first application and directing the user to install and use an agent application to continue enrollment. These examples can be useful where a user device includes an operating system that is not configured to perform direct enrollment, or in situations where the user is associated with an organizational group that does not allow for direct enrollment.
Additional examples are also provided, describing variations of the systems and methods provided in the first and second sets of examples. An administrator console is also described. The administrator console can allow an administrator to configure the functionality described herein on a device-specific, organizational-group-specific, or operating-system-specific basis.
The user device 110 can include an orchestration user interface (UI) 120 (associated with an orchestration server 160) and an application 130. The application 130 can be any application available based on the operating system (OS) executing on the user device 110. The application 130, also referred to interchangeably as a “portal application,” can provide a user with a virtual portal to a variety of other applications. In some examples, the other applications need not be installed on the user device 110, because the application 130 can launch browser-based applications in a browser application.
The application 130 can provide a “portal” by, for example, displaying multiple icons associated with different applications. For example, one icon can be associated with BOXER, another icon can be associated with MICROSOFT EXCEL, and yet another icon can be associated with SALESFORCE. By selecting one of these icons through the graphical user interface (“GUI”) presented by the application 130, a user can access the applications associated with those icons. An example application 130 is VMWARE's WORKSPACE ONE.
The application 130 can provide access to the displayed applications by authenticating the user and/or user device 110 with the selected application on behalf of the user. For example, the application 130 can store a user's credentials and other pertinent information. When the user selects an application displayed in the portal, the application 130 can authenticate the user by using an SSO service. As a result, the user only needs to login to the portal application 130 in order to access a variety of other applications without additional logins required.
In some examples, the application 130 provides access to enterprise data, such as secure applications (such as an enterprise email account through BOXER), virtual applications, and virtual computer desktops. Enterprise data can be any data associated with an enterprise that is confidential. In some examples, enterprise data is any data that can only be accessed if the user device 110 is enrolled in the EMM or MDM system associated with that enterprise. If a user logs into the application 130 before the device 110 is enrolled, then the application 130 can perform enrollment. Previously, a stand-alone, device-management-based application—typically referred to as an “agent application” and described in more detail later—was required in order to perform enrollment. The present disclosure describes novel ways of performing enrollment directly from a portal application 130. This allows the user to login to a single application 130 and gain access to secure enterprise data as well as a host of other applications, all of which are easily accessible through a single portal.
The system of
The system can also include an auto-discover service 150. The auto-discover service 150 can be a server, computing device, or network of multiple servers or computing devices, having one or more processors and memory stores. The auto-discover server 150 can route requests to an appropriate environment based on information contained in the request. For example, the auto-discover server 150 can receive a request that includes an email address and then route the request—or provide other information—based on that email address. As an example, a request including an email address of jsmith@vmware.com can cause the auto-discover server 150 to identify a VMWARE environment based on the “@vmware.com” portion of the email address. The auto-discover server 150 can then look up information regarding that environment and provide the information to the user device 110 through the application 130.
The system includes a management server 170 that performs management functions as part of an overall EMM or MDM system. It can be a server, computing device, or network of multiple servers or computing devices, having one or more processors and memory stores. The management server 170 can include various components for enrollment and compliance monitoring and enforcement. An administrator can establish or change enrollment criteria at the management server 170, such that a user device can only enroll at the management server 170 if those criteria are met. An administrator can also set compliance rules at the management server 170 that an enrolled user device must follow. The administrator can also set remedial actions for breaching a compliance rule. These functions are discussed in more detail later in this disclosure.
The system of
One or more of the orchestration server 160, management server 170, and identity management service 170 can be combined into one or more servers, in an example.
The functionality of the system of
Additionally, the information gathered at stages 202 or 204 can be used to request an organizational-group lookup. In one example, the auto-discover service 150 can identify an environment based on the email address or server URL and look up a list or organizational groups corresponding to that email address or server URL. In another example, the auto-discover service 150, management server 170, or another server can identify a specific organizational group corresponding to the user identified and authenticated at stage 204.
At stage 206, a determination is made as to whether the user needs to select an organizational group. This determination can be made by the auto-discover service 150 or management server 170, for example. The user may need to select an organizational group when the environment identified by the email address or server URL identifies multiple potential organizational groups. On the other hand, the user may not need to select an organizational group when only one exists for the identified environment, or when the auto-discover service 150 or management server 170 identifies a particular organizational group for the user in advance, based on the credentials obtained on stage 204.
If the user does not need to select an organizational group, then at stage 209 the user is automatically placed in the organizational group. If the user needs to select an organizational group, then at stage 208 the application 130 can present the user with a prompt to select a group. For example, the prompt can include a drop-down menu that is populated with available organizational groups identified by the auto-discover service 150. After selecting an organizational group at stage 208 or determining that no selection is necessary at stage 209, stage 210 includes determining whether direct enrollment is enabled. Direct enrollment, in this context, can mean enrolling the user device 110 through the application 130, rather than requiring a separate application to perform the enrollment.
The determination of whether direct enrollment is enabled is discussed in more detail later, but can include, for example, determining the type and version of operating system executing on the user device 110, and determining whether an enterprise feature allowing direct enrollment is enabled. If direct enrollment is not enabled, then at stage 212 enrollment can be performed through an agent application, described later. If direct enrollment is enabled, then at stage 214 the management server 170 can perform an assessment as to whether the user device 110 is allowed to enroll. The assessment can include assessing restrictions, such as whether the user device 110 is restricted based on its platform, model, manufacturer, or operating system, or whether the user is restricted based on the organizational group, geographic location, or other factors.
At stage 216, the result of the assessment is received. If the device is not approved to enroll, then at stage 218 the application 130 can display a notice to the user that the device is not approved for enrollment. The notice can include reasons why the device is not approved, such as failed rules or restrictions as determined by the management server 170. If the device is approved to enroll, then at stage 220 (shown in
When the user chooses to proceed with enrollment, stage 224 can include an assessment of whether the device 110 is ownership-selection enabled. In other words, the assessment can determine whether the use is able to select between ownership types, or whether the ownership type is already established. In some examples, the user may not be allowed to make such a selection. For example, a corporate-owned device 110 may be set up such that the selection is not allowed. In another example, the auto-discover service 150 or management server 170 can include a rule that the corporate-owned device 110 does not allow such a selection. If no selection is allowed, the default or indicated ownership is applied at stage 228. If selection is allowed, then at stage 226 the application 130 provides a prompt for the user to select between “employee owned” or “corporate owned.”
Based on the selection made at stage 226 or applied at stage 228, a Terms of Use can be tailored to the user device 110. If the system determines that no Terms of Use is needed at stage 230, then the method can proceed to stage 234. If the system determines that a Terms of Use is needed at stage 230, then at stage 232 the Terms of Use can be presented to the user, along with a mechanism for the user to accept the terms. After acceptance, the method can proceed to stage 234.
At stage 234, the device 110 is enrolled with the management server 170. This process is discussed in more detail later in this disclosure. As a result of enrollment, an MDM or management profile can be installed on the user device 110. At stage 236 (shown in
At stage 310, a determination is made as to whether the auto-discover service 150 is available for assisting in determining the user's organizational group. If it is not, the method can proceed to stage 320, where the user is registered in association with the organizational group to which the application programming interface (“API”) is configured. For example, the API can use a standard organizational group for all users, or a standard organizational group for all users within a particular enterprise environment. In that case, the group can be assigned and at stage 345, the method can include registering the user using that organizational group.
If, on the other hand, the auto-discover service 150 is available for assisting in determining the user's organizational group, then at stage 315 a search can be conducted. The search can be a request to the auto-discover service 150, for example. In another example, the search can be a request sent to the management server 170 or another server or database. In either case, the request can seek information regarding whether the user should register at a default group, select an organizational group, or select a child organizational group. A child organizational group can be considered a sub-group of an organizational group. For example, an organizational group entitled “staff” can include multiple child organizational groups, such as “administrator,” “secretary,” and “accounting.”
A determination is made at stage 325, based on information received in response to the search at stage 315, regarding whether to register the user at the default organizational group identified by the auto-discover service 150. If so, then the method can proceed to stages 330 and 345, where the user is registered at the default organizational group identified by the auto-discover service 150. If not, then the method can proceed to stage 335, where the user is prompted to provide input regarding the appropriate child organizational group. For example, the user can select from a list of child organizational groups using any suitable method, such as a drop-down menu.
At stage 340, the system can determine that only a subset of child organizational groups is available for enrolling the device. In that case, the user can be returned to stage 335 or an error message can be generated. In another example, a filter is applied such that the user is assigned to a child organizational group based on the selection at stage 335.
At stages 350 and 345, the child organizational group selected at stage 335 is determined to be the registration group for the user's enrollment. Enrollment can then proceed from there.
At stage 406, the application 130 can request an organizational group lookup from the auto-discover service 150. The auto-discover service 150 can perform the lookup based on an email address, server URL, user credentials, or some combination thereof. For example, the auto-discover service 150 can identify that the email address contains “@vmware.com” and look up an entry for the enterprise environment associated with that email address. The entry may specify one or more organizational groups associated with that enterprise environment. At stage 408, the auto-discover service 150 can return one or more organizational groups back to the user device 110.
At stage 410, the application 130 can request registration. This can occur by, for example, a user logging into the application 130 for the first time. In another example, stage 410 is triggered by an attempt to use an enterprise application or access an enterprise resource. The request can be routed to the orchestration server 160, which forwards the request to the management server 170. Alternatively, the request at stage 410 can be sent directly to the management server 170.
At stage 414, the management server 170 can determine whether the organizational group to which the user belongs, identified at stage 408, allows for direct enrollment to proceed. For example, an organization can enforce finer control over the enrollment process by requiring a specific child organizational group to be selected, rather than allowing enrollment under a more general organizational group. The determination at stage 414 can be made at the user device 110 or orchestration server 160 in some examples. In the example of
If, as a result of the determination at stage 414, it is determined that the user must register with a child organizational group in order to proceed with enrollment, then at stage 416 the user device 110 can request a list of child organizational groups from which to choose. The request can be sent to the orchestration server 160 which can then forward the request along to the management server 170 at stage 418. Alternatively, the request can be sent directly to the management server 170.
The management server 170 can perform a look-up at stage 420 to pull a list of child organizational groups. The look-up can be performed based on information regarding the user device 110, user, relevant enterprise environment, selected organizational group, rules set by an administrator, or any combination thereof. The list of child organizational groups can be sent to the orchestration server 160 at stage 422 and, from there, to the user device 110 and stage 424.
The user can select a child organizational group through the application 130 at stage 426. The selection can include, for example, selecting from a drop-down list of available child organizational groups. The available groups can also be presented in a different format, such as multiple buttons, where the user simply selects the button corresponding to the desired child organizational group. When the selection has been made, the application 130 requests registration under the selected child organizational group at stage 428. The request can be routed through the orchestration server 160 which forwards the request to the management server 170 at stage 430.
Continuing to
If stage 432 results in a determination that the operating system allows for direct enrollment through the application 130, then at stage 434 the management server 170 can perform an assessment to determine whether the device 110 meets any enterprise restrictions, compliance rules, or management policies set by an administrator.
A compliance rule can set forth one or more conditions that must be satisfied in order for a user device 110 to be deemed compliant. They can be applied before enrollment, at stage 434, or any time after that. If compliance is broken after enrollment, the management server 170 can take steps to control access of the user device to enterprise files, applications, and email. Compliance rules can be assigned differently to the different organizational groups or child organizational groups. In addition, compliance rules can be assigned differently to different devices 110 assigned to the same user. Compliance rules can control access to enterprise files to the user device 110 based on the user's organizational group or other criteria. Meanwhile, compliance rules can cause the user device 110 to be wiped if it leaves a geographic area, is jailbroken, or if certain software is removed or disabled.
A management policy can specify that a user device 110 has permission to perform or access certain functionality. For example, the user device 110 can be restricted to certain enterprise repositories and functions within applications. A management policy can also specify that a user device 110 has permission according to its organizational group.
Other restrictions can also be applicable at stage 434. For example, enrollment can be restricted based on the device type, device manufacturer, operating system, or any other restriction established by an administrator. The restrictions, compliance rules, and management policies can be stored at the management server 170 and accessed to perform the assessment at stage 434.
If the assessment determines that the user device 110 is allowed to enroll, then at stage 436 the management server 170 can send an enrollment URL to the orchestration server 160. The orchestration server 160 can provide the enrollment URL and any other relevant enrollment instructions to the application 130 at stage 438.
At stage 440, the application 130 can display an enrollment prompt to the user, similar to that shown by element 220 of
At stage 442, the application 130 can request a refreshed access token from the identity management service 140. The identity management service 140 can send a refreshed token at stage 444. The refreshed access token can be used for the enrollment process. Refreshing the access token can ensure that the token is not expired by the time the enrollment process begins.
At stage 446, the application 130 can initiate enrollment with the management server 170. Enrollment can include interacting with an enrollment component or administrator component at the management server 170, or both. The enrollment component can authenticate the access token and can provide to the device 110 any additional credentials required for enrollment. The enrollment component can also provide information regarding how to access and communicate with the administrator component in order to continue the enrollment process.
In some examples, the administrator component can request a token, such as the refreshed access token, from the user device 110, indicating that the user device 110 has been authenticated and is permitted to continue the enrollment process with the administrator component. Upon receiving the token, the administrator component can continue the enrollment process. The administrator component can also provide a console for an administrator to configure and monitor the status of the user device 110 and the enrollment process. In some examples, the administrator component can be dedicated to a particular enterprise or group of enterprises, while the enrollment component can be shared across multiple different enterprises.
Upon successful enrollment, the management server 170 can send a notice to the application 130 at stage 448, informing the application 130 that enrollment was successful. At stage 450, the management server 170—or as shown in
In some examples, the enrollment token is an HMAC token. The application 130 can send a request to the orchestration server 160 requesting enrollment information, such as an HMAC token and MDM device ID. Though not shown in
At stage 452, the application 130 can load an orchestration UI 120 associated with the orchestration server 160. The orchestration UI 120 allows the management system to present a UI to the user based on information stored at the management system, such as at the orchestration server 160 or management server 170. In one example, the orchestration UI 120 is the UI of the application 130. In another example, the orchestration UI 120 is a UI displayed within the UI of the application 130 but generated by the orchestration server 160. In yet another example, the orchestration UI 120 is a UI displayed in lieu of, or in addition to, the application's 130 UI, such as within a box displayed on top of the application 130 UI. Using the orchestration UI 120, the device 110 can present the user with an End User License Agreement (“EULA”) to which the user can agree at stage 454. The EULA can be a blanket agreement that applies to the use of the management system, or it can be specific to applications that the user wants to install on the user device 110. In the latter case, stage 454 can follow stage 456.
At stage 456, the user selects one or more managed applications that he or she wishes to download and install on the user device 110. For example, the orchestration UI 120 can present a list of managed applications, such that the user can select only those applications that are desired. The request can be delivered to the orchestration server 160 at stage 456, and to the management server 170 at stage 458. The request can also be delivered directly to the management server 170. The management server 170, in turn, can provision the selected applications to the user device at stage 460.
The early stages shown in
At stage 532 the management server 170 performs a determination as to whether enrollment is enabled for the device 110 and the user. The determination can include various stages. For example, it can include confirming that the selected child organizational group is enabled for direct enrollment through the application 130. The determination can also include verifying that the operating system executing on the device 110 allows for direct enrollment through the application 130. This can include identifying the version of the operating system and comparing it to a whitelist of allowed operating systems and versions.
The determination at stage 532 can also include obtaining information about the operating system as it relates to an enterprise feature that enables enrollment. In the case of an ANDROID operating system, for example, certain versions can include an optional ANDROID FOR WORK enterprise feature that can be enabled at the operating-system level. In that example, the enterprise feature must be enabled in order to perform direct enrollment. Information regarding the operating system of the user device 110, the version of the operating system, and the settings applied to the operating system can be stored at stage 532. It can also be gathered and stored at other stages, such as at stage 534.
If stage 532 results in a determination that the operating system allows for direct enrollment through the application 130, then at stage 534 the management server 170 can perform an assessment to determine whether the device 110 meets any enterprise restrictions, compliance rules, or management policies set by an administrator.
At stage 536 of the example method, after the assessment at stage 534 determines that the user device 110 is allowed to enroll, the management server 170 can send an enrollment URL to the orchestration server 160. The orchestration server 160 can provide the enrollment URL and any other relevant enrollment instructions to the application 130 at stage 538. The management server 170 can provide the enrollment URL and instructions directly to the application 130 in some examples.
At stage 540, the orchestration server 160 can ensure that an enterprise feature, required for direct enrollment, is enabled at the user device 110. As mentioned above, some operating systems, such as ANDROID, can include an optional enterprise feature, such as ANDROID FOR WORK, that can be enabled at the operating-system level. In that example, the enterprise feature must be enabled in order to perform direct enrollment. The management server 170 and/or orchestration server 160 can be aware of the enterprise feature based on information about the operating system obtained at stages 532 or 534.
Stage 540 can include confirming that the operating system is certified for the enterprise feature, confirming that the version of the operating system present on the user device 110 can run the enterprise feature, and confirming that an administrator set up or enabled the enterprise feature for the device 110. If this stage fails, the process can proceed as detailed in
At stage 542, enrollment can begin with the application 130 sending an enrollment initiation request to the management server 170. The management server 170 can respond with a device ownership prompt, as shown with element 226 of
Based on the device ownership selection, the management server 170 can configure an enrollment EULA tailored to the selected device type. For example, a corporate-owned device 110 may correspond to an enrollment EULA that includes restrictions on what the user can do with the device 110. At stage 548, the management server 170 can provide the enrollment EULA to the application 130, and at stage 550 the application 130 can return an acceptance from the user.
Stage 552 can include a third-party registration, if required, based on the operating system. In the example of an ANDROID operation system, for example, stage 554 includes registering the device with GOOGLE.
After the third-party registration, the application 130 can obtain an access token from the orchestration server 160 at stage 554. In some examples, the access token is an HMAC token. The application 130 can send a request to the orchestration server 160 or management server 170 requesting enrollment information, such as an HMAC token and MDM device ID. If sent to the orchestration server 160, the orchestration server 160 can send a request to the management server 170 on behalf of the application 130. The management server 170 can check the status of the user device 110 and—if the device 110 is successfully enrolled—retrieve or create an HMAC token.
The HMAC token and MDM device ID can then be send to the orchestration server 160, which then provides both to the application 130, or they can be sent directly to the application 130 from the management server 170. If, on the other hand, the device is not successfully enrolled, the management server 170 can return an error. In some examples, the orchestration server 160, rather than the management server 170, can perform the enrollment check and retrieve the HMAC token and MDM device ID. The application 130 can use the access token to perform enrollment at stage 556. Enrollment can occur through the orchestration server 160, or directly with the management server 170.
At stage 558, the application 130 can load an orchestration UI 120 associated with the orchestration server 160. The orchestration UI 120 allows the management system to present a UI to the user based on information stored at the management system, such as at the orchestration server 160 or management server 170. Using the orchestration UI 120, the device 110 can present the user with a post-enrollment screen at stage 560. The post-enrollment screen can be, for example, the screen shown at element 242 of
At stage 562, the user can provide a selection of one or more managed applications that he or she wishes to download and install on the user device 110. For example, the orchestration UI 120 can present a list of managed applications, such that the user can select only those applications that are desired. The request can be delivered to the orchestration server 160 at stage 562, and to the management server 170 at stage 564. The request can also be delivered directly to the management server 170. The management server 170, in turn, can provision the selected applications to the user device at stage 566.
Stage 802 can include receiving user credentials at an application 130 installed on the user device 110. For example, a user can login using the application 130 installed on the user device 110. The login credentials can be sent to the identity management service 140, which after authenticating the user, can send an access token back to the user device 110. The access token can be an HMAC token, for example. At stage 804, the application 130 can receive the access token based on the user credentials.
Stage 806 can include receiving, at the application 130, an identification of an organizational group to which the user belongs. In one example, the identification can be in response to the application 130 requesting an organizational-group lookup from the auto-discover service 150. The auto-discover service 150 can perform the lookup based on an email address, server URL, user credentials, or some combination thereof. For example, the auto-discover service 150 can identify that the email address contains “@vmware.com” and look up an entry for the enterprise environment associated with that email address. The entry may specify one or more organizational groups associated with that enterprise environment. The auto-discover service 150 can return one or more organizational groups back to the user device 110.
Stage 808 can include receiving a determination as to whether the identified organizational group enables the user device to directly enroll with the management system. For example, the management server 170 can determine whether the organizational group to which the user belongs, received at stage 806, allows for direct enrollment to proceed. For example, an organization can enforce finer control over the enrollment process by requiring a specific child organizational group to be selected, rather than allowing enrollment under a more general organizational group. The determination at stage 808 can be made at the user device 110 or orchestration server 160 in some examples. In other examples, the management server 170 makes the determination and provides it to the orchestration server 160, which can then communicate the determination to the user device 110. Alternatively, the management server 170 can provide the determination directly to the user device 110.
At stage 810, if the identified organizational group enables the user device 110 to directly enroll with the management system, a request can be made for an assessment, by the management server 170, that the user device is allowed to enroll at the management server 170. The assessment can be based, at least in part, on restrictions stored at the management server 170. For example, the management server 170 can perform an assessment to determine whether the device 110 meets any enterprise restrictions, compliance rules, or management policies set by an administrator and stored at the management server 170. The assessment can be received by the user device at stage 812.
Stage 814 can include displaying, at the user device 110, a prompt for the user to proceed with enrollment. For example, the application 130 can display an enrollment prompt to the user, similar to that shown by element 220 of
Stage 816 can include enrolling, by the application 130, the user device 110 with the management server 170. The application 130 can initiate enrollment with the management server 170. Enrollment can include interacting with an enrollment component or administrator component at the management server 170, or both. The enrollment component can authenticate the access token and can provide to the device 110 any additional credentials required for enrollment. The enrollment component can also provide information regarding how to access and communicate with the administrator component in order to continue the enrollment process.
In some examples, the administrator component can request a token, such as the refreshed access token, from the user device 110, indicating that the user device 110 has been authenticated and is permitted to continue the enrollment process with the administrator component. Upon receiving the token, the administrator component can continue the enrollment process.
Stage 818 can include displaying, at the user device 110, a prompt for the user to select one or more managed applications to install on the user device 110. The application 130 can load an orchestration UI 120 associated with the orchestration server 160. The user can select one or more managed applications that he or she wishes to download and install on the user device 110. For example, the orchestration UI 120 can present a list of managed applications, such that the user can select only those applications that are desired. The request can be delivered to the orchestration server 160 and to the management server 170. The request can also be delivered directly to the management server 170. The management server 170, in turn, can provision the selected applications to the user device at stage 460 at stage 820.
As mentioned above, some operating systems are not able to perform direct enrollment from a single application that also provides single-sign on and access to enterprise applications. For example, some versions of ANDROID require an enterprise feature, such as ANDROID FOR WORK, to be enabled in order to perform direct enrollment through the application 130. If the operating system is not certified for the enterprise feature, the version of the operating system cannot run the enterprise feature, or an administrator has not set up or enables the enterprise feature, then agent enrollment is required. One example of requiring agent enrollment is provided at element 212 of
The user device 610 can also include an agent application 680. The agent application 680 can be an application installed on the user device 610 as part of an enrollment process. The agent application 680 can include device-level components and application-level components. The agent application 680 can also include system-level privileges, such as privileges to communicate directly with a management server 670. The agent 680 can enforce settings, such as compliance rules, that are specified at the management server 670. It can also enforce the compliance rules by carrying out actions specified by the management server 670.
In one example, the agent application 680 does not provide a “portal” through which a user can access other applications. That is, the agent application 680 does not present the user with an interface including icons for applications that can be accessed through the agent application 680. In some examples, the user does not interact with the agent application 680 at all. Additionally, the agent application 680 does not provide SSO-based services for accessing applications, as described with respect to the application 630.
The management server 670 can performs management functions as part of an overall EMM or MDM system. It can be a server, computing device, or network of multiple servers or computing devices, having one or more processors and memory stores. The management server 670 can include various components for enrollment and compliance monitoring and enforcement. An administrator can establish or change enrollment criteria at the management server 670, such that a user device can only enroll at the management server 670 if those criteria are met. An administrator can also set compliance rules at the management server 670 that an enrolled user device must follow. The administrator can also set remedial actions for breaching a compliance rule. These functions are discussed in more detail later in this disclosure.
The system of
The system can also include an auto-discover service 650. The auto-discover service 650 can be a server, computing device, or network of multiple servers or computing devices, having one or more processors and memory stores. The auto-discover server 650 can route requests to an appropriate environment based on information contained in the request. For example, the auto-discover server 650 can receive a request that includes an email address and then route the request—or provide other information—based on that email address.
The system of
The early stages shown in
At stage 732, the management server 670 performs a determination as to whether enrollment is available for the device 610 and the user. The determination can include various stages. For example, it can include confirming that the selected child organizational group is enabled for enrollment with the management server 670. The determination at stage 732 can also include obtaining information about the operating system as it relates to an enterprise feature that enables enrollment. In the case of an ANDROID operating system, for example, certain versions can include an optional ANDROID FOR WORK enterprise feature that can be enabled at the operating-system level. In that example, the enterprise feature must be enabled in order to perform direct enrollment. Information regarding the operating system of the user device 610, the version of the operating system, and the settings applied to the operating system can be stored at stage 732. It can also be gathered and stored at other stages, such as at stage 734.
At stage 734, the management server 670 can perform an assessment to determine whether the device 610 meets any enterprise restrictions, compliance rules, or management policies set by an administrator. At stage 736 of the example method, after the assessment at stage 734 determines that the user device 610 is allowed to enroll, the management server 670 can send an enrollment URL to the orchestration server 660. The orchestration server 660 can provide the enrollment URL and any other relevant enrollment instructions to the application 630 at stage 738. The management server 670 can provide the enrollment URL and instructions directly to the application 630 in some examples.
At stage 740, the orchestration server 660 can determine that an enterprise feature, required for direct enrollment, is not enabled at the user device 610. As mentioned above, some operating systems, such as ANDROID, can include an optional enterprise feature, such as ANDROID FOR WORK, that can be enabled at the operating-system level. In that example, the enterprise feature must be enabled in order to perform direct enrollment. The management server 670 and/or orchestration server 660 can be aware of the enterprise feature based on information about the operating system obtained at stages 732 or 734.
Stage 740 can include determining that at least one of the following conditions is true: the operating system is not certified for the enterprise feature, the version of the operating system present on the user device 610 cannot run the enterprise feature, or the enterprise feature has not been set up or enabled by an administrator. If one or more of those conditions are true, then the method can proceed to stage 742.
At stage 742, the application 630 can present a pre-enrollment screen to the user, informing the user that an agent application 680 is required in order to complete enrollment. The pre-enrollment screen can optionally explain to the user why their device is not able to perform direct enrollment through the application 630, such as by explaining that the operating-system version is incompatible or that an administrator has not enabled an enterprise feature necessary for direct enrollment. The pre-enrollment screen can also provide the user with an option to continue the enrollment process by downloading an agent application.
At stage 744, the application 630 UI is paused and the user is redirected to a page associated with the agent application 680. The page can automatically cause the agent application 680 to be downloaded, or it can present a selection mechanism for the user to elect to download the agent application 680. At stage 746, the agent application 680 is downloaded and the application 630 passes the user's enrollment credentials to the agent application 680.
At stage 748, enrollment can begin with the agent application 680 sending an enrollment initiation request to the management server 670. The management server 670 can respond with a device ownership prompt at stage 750. The agent application 680 can make the selection at stage 752, either automatically or by prompting the user to make a selection. In some examples, the agent application 680 can automatically determine device ownership based on information about the device, such as a device identifier. The ownership selection can be provided to the management server 670 from the agent application 680 at stage 754.
Based on the device ownership selection, the management server 670 can configure an enrollment EULA tailored to the selected device type. For example, a corporate-owned device 610 may correspond to an enrollment EULA that includes restrictions on what the user can do with the device 610. At stage 756, the management server 670 can provide the enrollment EULA to the agent application 680. At stage 758, the agent application 680 can present the EULA to the user and receive an acceptance, and then return the acceptance to the management server 670 at stage 760.
At stage 762, the management server 670 can provide settings to the agent application 680. The settings can include, for example, management policies and compliance rules set at the management server 670. At stage 764, the agent application 680 can request and receive an access token, such as an HMAC token, from the management server 670. The agent application 680 can then complete the enrollment process and ensure that a passcode is set up for the user.
After enrollment is successfully completed, the agent application 680 can return control back to the application 630 by sending an instruction to the application 630 at stage 768. The application 630, in turn, can unpause its UI at stage 770 and load an orchestration UI 620 at stage 772. The orchestration UI 620 allows the management system to present a UI to the user based on information stored at the management system, such as at the orchestration server 660 or management server 670. Using the orchestration UI 620, the device 610 can present the user with a post-enrollment screen at stage 774. The screen can congratulate the user on a successful enrollment process and provide information regarding obtaining managed applications from the management system.
At stage 776, the user can provide a selection of one or more managed applications that he or she wishes to download and install on the user device 610. For example, the orchestration UI 620 can present a list of managed applications, such that the user can select only those applications that are desired. The request can be delivered to the orchestration server 160 at stage 776, and to the management server 670 at stage 778. The request can also be delivered directly to the management server 670. The management server 670, in turn, can provision the selected applications to the user device at stage 780.
Stage 852 can include receiving user credentials at an application 630 installed on the user device 610. For example, a user can login using the application 630 installed on the user device 610. The login credentials can be sent to the identity management service 640, which after authenticating the user, can send an access token back to the user device 610. The access token can be an HMAC token, for example. At stage 854, the application 630 can receive the access token based on the user credentials.
Stage 856 can include receiving, at the application 630, an identification of an organizational group to which the user belongs. In one example, the identification can be in response to the application 630 requesting an organizational-group lookup from the auto-discover service 650. The auto-discover service 650 can perform the lookup based on an email address, server URL, user credentials, or some combination thereof. For example, the auto-discover service 650 can identify that the email address contains “@vmware.com” and look up an entry for the enterprise environment associated with that email address. The entry may specify one or more organizational groups associated with that enterprise environment. The auto-discover service 650 can return one or more organizational groups back to the user device 610.
Stage 858 can include receiving a determination that the user device 610 is not able to directly enroll with the management system through the application 630. For example, the orchestration server 660 can determine that an enterprise feature, required for direct enrollment, is not enabled at the user device 610. As mentioned above, some operating systems, such as ANDROID, can include an optional enterprise feature, such as ANDROID FOR WORK, that can be enabled at the operating-system level. In that example, the enterprise feature must be enabled in order to perform direct enrollment. Stage 858 can include determining that at least one of the following conditions is true: the operating system is not certified for the enterprise feature, the version of the operating system present on the user device 610 cannot run the enterprise feature, or the enterprise feature has not been set up or enabled by an administrator. If one or more of those conditions are true, then the method can proceed to stage 860.
Stage 860 can include pausing a UI of the application 630 and redirecting the user to download an agent application 680. A page associated with the agent application 680 can automatically cause the agent application 680 to be downloaded, or it can present a selection mechanism for the user to elect to download the agent application 680. At stage 862, the agent application 680 is downloaded and installed, and the application 630 passes the user's enrollment credentials to the agent application 680 at stage 864.
Stage 866 can include enrolling, by the agent application 680, the user device 610 with the management server 670. Enrollment can begin with the agent application 680 sending an enrollment initiation request to the management server 670. The management server 670 can respond with a device ownership prompt. The agent application 680 can make a device-ownership selection, either automatically or by prompting the user to make a selection. In some examples, the agent application 680 can automatically determine device ownership based on information about the device, such as a device identifier. The ownership selection can be provided to the management server 670 from the agent application 680.
Based on the device ownership selection, the management server 670 can configure an enrollment EULA tailored to the selected device type. For example, a corporate-owned device 610 may correspond to an enrollment EULA that includes restrictions on what the user can do with the device 610. The management server 670 can provide the enrollment EULA to the agent application 680. The agent application 680 can present the EULA to the user and receive an acceptance, and then return the acceptance to the management server 670.
The management server 670 can also provide settings to the agent application 680. The settings can include, for example, management policies and compliance rules set at the management server 670. The agent application 680 can request and receive an access token, such as an HMAC token, from the management server 670. The agent application 680 can then complete the enrollment process and ensure that a passcode is set up for the user.
Stage 868 can include unpausing the UI of the application 630. The agent application 680 can return control back to the application 630 by sending an instruction to the application 630. The application 630, in turn, can unpause its UI and load an orchestration UI 620. The orchestration UI 620 allows the management system to present a UI to the user based on information stored at the management system, such as at the orchestration server 660 or management server 670. Using the orchestration UI 620, the device 610 can present the user with a post-enrollment screen. The screen can congratulate the user on a successful enrollment process and provide information regarding obtaining managed applications from the management system. For example, at stage 870, the device 610 can present the user with a prompt for the user to select one or more managed applications to install on the user device 610.
The user can provide a selection of one or more managed applications that he or she wishes to download and install on the user device 610. The request can be delivered to the orchestration server 160 and the management server 670. The request can also be delivered directly to the management server 670. The management server 670, in turn, can provision the selected applications to the user device at stage 872.
The example method can include, at stage 910, receiving an enrollment request from the portal application 130. The enrollment request can be received at the management server 170 or received at the orchestration server 160 and then routed to the management server 170.
At stage 920, the management server 170 can enroll the user device by interacting with the portal application 130. This can include, for example, having the management server 170 determine that the device 110 is able to enroll through the portal application 130, as explained with respect to stage 432 of
If the device 110 meets the relevant requirements set at the management server 170, the management server 170 can provide an enrollment URL, along with any other enrollment instructions, to the portal application 130. The portal application 130 can request a refreshed access token, if necessary, before continuing with enrollment. Enrollment can include interacting with an enrollment component or administrator component at the management server 170, or both. The enrollment and administrator components can authenticate tokens associated with the user device 110 and provide further instructions for continuing enrollment.
Upon successful enrollment, the management server 170 can send a notice to the portal application 130, informing that enrollment was successful. The management server 170 can also send an enrollment token to the user device 110. In some examples, the enrollment token is an HMAC token. In an example, the portal application 130 can request the HMAC token from the management server 170. The management server 170 can check the status of the user device 110 and—if the device 110 is successfully enrolled—retrieve or create an HMAC token. The HMAC token and MDM device ID can then be sent to the portal application 130.
At stage 930, the management server 170 can provide the portal application 130 with access to enterprise data. For example, the portal application 130 can be authorized to access secure applications, such as CONTENT LOCKER or the BOXER email application. The portal application 130 can authenticate the user and user device 110 to these applications, using one or more credentials provided as a result of the enrollment process. The user can then access enterprise data by launching a secure application through the portal application 130, without having to provide additional credentials or login information.
Stage 1020 can include receiving a determination as to whether the organizational group enables the portal application 130 to enroll with the management system. The management server 170 can determine whether the organizational group to which the user belongs allows for direct enrollment to proceed. For example, an organization can enforce finer control over the enrollment process by requiring a specific child organizational group to be selected, rather than allowing enrollment under a more general organizational group. The determination can be made at the user device 110 or orchestration server 160 in some examples.
If the organizational group allows for enrollment by the portal application 130, the portal application 130 can request enrollment at the management server 170 at stage 1030. The portal application 130 can request a refreshed access token, if necessary, before continuing with enrollment. Enrollment can include interacting with an enrollment component or administrator component at the management server 170, or both. The enrollment and administrator components can authenticate tokens associated with the user device 110 and provide further instructions for continuing enrollment.
If, on the other hand, the organizational group does not allow enrollment by the portal application 130, then the portal application 130 can request a list of child organizational groups. The request can be sent to the orchestration server 160 which can then forward the request along to the management server 170. Alternatively, the request can be sent directly to the management server 170.
The management server 170 can perform a look-up to pull a list of child organizational groups. The look-up can be performed based on information regarding the user device 110, user, relevant enterprise environment, selected organizational group, rules set by an administrator, or any combination thereof. The list of child organizational groups can be sent to the user device 110 at stage 1050.
At stage 1050, the user device 110 can receive an indication of at least one of the child organizational groups. For example, the user can select a child organizational group through the portal application 130. The selection can include, for example, selecting from a drop-down list of available child organizational groups. The available groups can also be presented in a different format, such as multiple buttons, where the user simply selects the button corresponding to the desired child organizational group. In another example, the management server 170 provides a selection of the appropriate child organizational group based on information stored at the management server 170.
At stage 1060, the user device 110 can receive a determination as to whether the child organizational group enables the portal application 130 to enroll with the management system. The determination can include various stages. For example, it can include confirming that the selected child organizational group is enabled for direct enrollment through the portal application 130. The determination can also include verifying that the operating system executing on the device 110 allows for direct enrollment through the portal application 130. This can include identifying the version of the operating system and comparing it to a whitelist of allowed operating systems and versions.
If enrollment is allowed through the portal application 130 for the selected child organizational group, then at stage 1070 the portal application 130 can request enrollment. The portal application 130 can request a refreshed access token, if necessary, before continuing with enrollment. Enrollment can include interacting with an enrollment component or administrator component at the management server 170, or both. The enrollment and administrator components can authenticate tokens associated with the user device 110 and provide further instructions for continuing enrollment
A user-group assignment field 1120 is also provided at the administrator console. The user-group assignment field 1120 can allow an administrator to enable or disable enrollment by the portal application 130 for a particular organizational group. In the example of
The administrator console can also allow an administrator to tailor direct enrollment settings based on the operating system of the user device 110. For example, the console includes an iOS selection 1130, legacy ANDROID selection 1140, and ANDROID enterprise selection 1150. The buttons associated with the iOS selection 1130 are temporarily blocked from view due to the drop-down menu 1160, but are provided in a similar relative location and format to the “enable” and “disable” buttons associated with the legacy ANDROID selection 1140 and ANDROID enterprise selection 1150. With each of these selections 1130, 1140, 1150, an administrator can tailor the ability to use a portal application 130 to enroll a user device 110 with the management system by allowing or not allowing particular operating systems.
An administrator can create, edit, and delete group policies. A group policy can set forth various parameters for allowing direct enrollment by the portal application 130. For example, a group policy can enable direct enrollment for users in the “engineering” organizational group with user devices 110 that run the iOS operating system. In that example, the administrator would select “enable” at the enable WORKSPACE ONE prompt 1110, navigate the drop-down menu 1160 for the assigned user group selection 1120 to select “engineering,” select “enable” at the iOS selection 1130 and “disable” at both the legacy ANDROID selection 1140 and ANDROID enterprise selection 1150. That group policy can appear in the list of policies shown in the console, and can be edited by using the edit-group-policies button 1170. The administrator can also determine whether a child organizational group should inherit group assignment settings without overriding other settings, or inherit the settings and override as necessary, by toggling the child permission setting 1180.
Other examples of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the examples disclosed herein. Though some of the described methods have been presented as a series of steps, it should be appreciated that one or more steps can occur simultaneously, in an overlapping fashion, or in a different order. The order of steps presented are only illustrative of the possibilities and those steps can be executed or performed in any suitable fashion. Moreover, the various features of the examples described here are not mutually exclusive. Rather any feature of any example described here can be incorporated into any other suitable example. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 8166529 | O'Donoghue | Apr 2012 | B2 |
| 8201232 | Zhang | Jun 2012 | B2 |
| 8479263 | Liu | Jul 2013 | B1 |
| 8600058 | Verma | Dec 2013 | B2 |
| 8613070 | Borzycki | Dec 2013 | B1 |
| 8849978 | Batson | Sep 2014 | B1 |
| 9143530 | Qureshi | Sep 2015 | B2 |
| 9413745 | Rowley | Aug 2016 | B1 |
| 10445106 | Roszak | Oct 2019 | B2 |
| 10620965 | Roszak | Apr 2020 | B2 |
| 10628149 | Sharma | Apr 2020 | B2 |
| 10771337 | Das | Sep 2020 | B1 |
| 20020174238 | Sinn | Nov 2002 | A1 |
| 20030055652 | Nichols | Mar 2003 | A1 |
| 20050081055 | Patrick | Apr 2005 | A1 |
| 20060031683 | Marion | Feb 2006 | A1 |
| 20060184654 | Melo | Aug 2006 | A1 |
| 20070096894 | Lemmon | May 2007 | A1 |
| 20070208744 | Krishnaprasad | Sep 2007 | A1 |
| 20100100925 | Hinton | Apr 2010 | A1 |
| 20110276396 | Rathod | Nov 2011 | A1 |
| 20120226813 | Ragusa | Sep 2012 | A1 |
| 20120254957 | Fork | Oct 2012 | A1 |
| 20120291090 | Srinivasan | Nov 2012 | A1 |
| 20140040979 | Barton | Feb 2014 | A1 |
| 20140066015 | Aissi | Mar 2014 | A1 |
| 20140195927 | DeWeese | Jul 2014 | A1 |
| 20140331060 | Hayton | Nov 2014 | A1 |
| 20140344446 | Rjeili | Nov 2014 | A1 |
| 20150244711 | Venkataraman | Aug 2015 | A1 |
| 20150249617 | Chang | Sep 2015 | A1 |
| 20160087957 | Shah | Mar 2016 | A1 |
| 20160285875 | Lenz | Sep 2016 | A1 |
| 20160328577 | Howley | Nov 2016 | A1 |
| 20170018007 | DeFrank | Jan 2017 | A1 |
| 20170064549 | Rykowski | Mar 2017 | A1 |
| 20170094509 | Mistry | Mar 2017 | A1 |
| 20170118211 | Murthy | Apr 2017 | A1 |
| 20170149795 | Day | May 2017 | A1 |
| 20170230848 | Brouillette | Aug 2017 | A1 |
| 20170339564 | Momchilov | Nov 2017 | A1 |
| 20180054434 | Lingamallu | Feb 2018 | A1 |
| 20180074469 | Ishizaka | Mar 2018 | A1 |
| 20180109636 | Hardy | Apr 2018 | A1 |
| 20180276386 | Roszak | Sep 2018 | A1 |
| 20190068373 | Konduru | Feb 2019 | A1 |
| 20190132307 | Pitchaimani | May 2019 | A1 |
| 20190132321 | Pitchaimani | May 2019 | A1 |
| 20190158476 | Brouillette | May 2019 | A1 |
| 20190158498 | Brouillette | May 2019 | A1 |
| 20190158500 | Brouillette | May 2019 | A1 |
| 20190158506 | Brouillette | May 2019 | A1 |
| 20200342089 | Mummadi | Oct 2020 | A1 |
| 20200371764 | Sousa | Nov 2020 | A1 |
| Entry |
|---|
| International Search Report dated Feb. 21, 2019 for International Application No. PCT/US2018/062147. |
| Number | Date | Country | |
|---|---|---|---|
| 20190158500 A1 | May 2019 | US |
