Cloud-based management service device registration using intermediate cloud storage
The use of intermediate cloud storage to decrypt encrypted data blobs with session and decryption keys via matrix barcodes addresses registration challenges in cloud-based management services, improving efficiency and reducing complexity and resource consumption.
Patent Information
- Application Number
- KR1020257013572
- Authority / Receiving Office
- KR · KR
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2020-06-30
- Filing Date
- 2021-03-24
- Publication Date
- 2026-11-06
- Estimated Expiration
- 2041-03-24
Smart Images

Figure R1020257013572_ABST
Abstract
Description
Background Technology
[0001] A cloud-based management service enables the management of computing devices using a network of servers referred to as the "cloud." Information Technology (IT) managers frequently use cloud-based management services to manage computing devices used by employees to access company resources. To enable computing devices to be managed using a cloud-based management service, IT managers register the computing devices with a tenant of the cloud-based management service. A tenant of a cloud-based management service is an entity (e.g., a customer) whose data remains isolated from and unknown to other tenants of the cloud-based management service. Typically, IT managers register the computing devices with the cloud-based management service tenant before providing them to users. Therefore, the aforementioned registration of computing devices is often referred to as "pre-registration."
[0002] IT administrators typically use data blobs located on respective computing devices to register each computing device with a tenant of a cloud-based managed service. For example, the IT administrator plugs a removable memory device (e.g., a thumb drive) into each computing device, runs a script to collect their respective data blobs, logs into the portal of the cloud-based managed service, and uploads their respective data blobs from the removable memory device to the cloud-based managed service.
[0003] It may be desirable to extract data blobs from each computing device by reading a matrix barcode, such as a Quick Response (QR) code. However, the amount of information that can be read from a matrix barcode may be limited by the capabilities of the reader used to extract the data blobs. An increase in the amount of data stored in a data blob corresponds to an increase in the resolution of the QR code representing the data blob. Noise associated with the QR code may result in the inability to replicate the data blobs represented by the matrix barcode.
[0004] Above all, various approaches for registering a user device with a cloud-based management service (also known as a cloud-based management system) using intermediate cloud storage are described in this document. For example, intermediate cloud storage may store an encrypted data blob containing information identifying the user device. Intermediate cloud storage or the registration system may decrypt the encrypted data blob, so that the registration system can use the decrypted data blob to register the user device with the cloud-based management service. For example, the registration system may retrieve the encrypted or decrypted data blob from the intermediate cloud storage by providing a required secret to the intermediate cloud storage. The required secret may be provided to the registration system by the user device (e.g., via a matrix barcode such as a QR code).
[0005] In the first exemplary approach, a matrix barcode identifying the user device is scanned. The matrix barcode includes a session identifier, a decryption key, and a correlation key. The session identifier identifies the session during which the user device is registered with the cloud-based management service as a session. The decryption key is configured to be used to decrypt an encrypted data blob to be received from the user device. The correlation key is available to correlate the user device to an action and / or record associated with the user device. By providing the session identifier, decryption key, and correlation key to the intermediate cloud storage, the intermediate cloud storage is triggered to decrypt an encrypted data blob containing information identifying the user device using the decryption key to provide the decrypted data blob. The decrypted data blob is received from the intermediate cloud storage. The user device is registered with the cloud-based management service using the decrypted data blob.
[0006] In the second exemplary approach, a matrix barcode identifying the user device is scanned. The matrix barcode includes a session identifier, a decryption key, and a correlation key. The session identifier identifies the session during which the user device is registered with the cloud-based management service. The decryption key is configured to be used to decrypt an encrypted data blob to be received from the user device. The correlation key is available to correlate the user device with actions and / or records associated with the user device. An encrypted data blob containing information identifying the user device is retrieved from an intermediate cloud storage receiving the encrypted data blob from the user device. The encrypted data blob retrieved from the intermediate cloud storage is decrypted using the decryption key included in the matrix barcode to provide a decrypted data blob. The user device is registered with the cloud-based management service using the decrypted data blob.
[0007] The approach described in this document can be applied to register user devices with a cloud-based management service for any appropriate number of user devices (e.g., 5, 20, hundreds, or thousands).
[0008] This overview is provided to introduce, in a simplified form, excerpts of concepts that are further described below in the detailed description. This overview is not intended to identify the core or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, it should be noted that the invention is not limited to the specific embodiments described in the detailed description and / or other parts of this document. Such embodiments are presented in this document solely for illustrative purposes. Additional embodiments will be apparent to those skilled in the relevant art(s) based on the teachings contained in this document. Brief explanation of the drawing
[0009] The attached drawings included in this document and forming part of the specification illustrate embodiments of the present invention and, together with the description, explain the accompanying principles and also contribute to enabling a person skilled in the relevant art(s) to make and use the disclosed art. FIG. 1 is a block diagram of an exemplary intermediate cloud storage-based device registration system according to an embodiment. FIGS. 2 and 3 are exemplary activity diagrams for registering a user device to a cloud-based management service using intermediate cloud storage according to an embodiment. FIGS. 4 to 6 and FIGS. 8 to 9 illustrate a flowchart of an exemplary method for registering a user device to a cloud-based management service using intermediate cloud storage according to an embodiment. FIGS. 7 and FIGS. 10 are block diagrams of an exemplary implementation of the admin system illustrated in FIG. 1 according to an embodiment. FIG. 11 is a system diagram of an exemplary mobile device according to an embodiment. FIG. 12 depicts an exemplary computer in which an embodiment can be implemented. The features and benefits of the disclosed technology will become more apparent from the detailed description set forth below when taken together with the drawings (where similar reference numerals identify corresponding elements throughout). In the drawings, similar reference numerals generally represent elements that are identical and / or functionally similar and / or structurally similar. The drawing in which the element first appears is indicated by the leftmost number(s) of the corresponding reference numeral. Specific details for implementing the invention
[0010] I. Introduction
[0011] The following detailed description refers to the accompanying drawings illustrating exemplary embodiments of the present invention. However, the scope of the present invention is not limited to these embodiments but is instead defined by the appended claims. Therefore, embodiments beyond those depicted in the accompanying drawings, such as modified versions of the illustrative embodiments, may nevertheless be encompassed by the present invention.
[0012] References in the specification to “one embodiment,” “one embodiment,” “exemplary embodiment,” or similar terms indicate that while the described embodiment may include specific features, structures, or characteristics, not every embodiment necessarily includes specific features, structures, or characteristics. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, where specific features, structures, or characteristics are described in relation to an embodiment, it is suggested that implementing such features, structures, or characteristics in relation to other embodiments, whether explicitly described or not, is within the knowledge of a person skilled in the relevant art(s).
[0013] Descriptors such as "first," "second," "third," etc., are used to refer to certain elements discussed in this document. Such descriptors are used to facilitate the discussion of exemplary embodiments and do not indicate the required order of the referenced elements unless an affirmative statement that such order is required is made in this document.
[0014] II. Exemplary Examples
[0015] The exemplary embodiments described in this document make it possible to register user devices to a cloud-based management service (also known as a cloud-based management system) using intermediate cloud storage. For example, the intermediate cloud storage may store an encrypted data blob containing information identifying the user device. The intermediate cloud storage or the registration system may decrypt the encrypted data blob so that the registration system may use the decrypted data blob to register the user device to the cloud-based management service. For example, the registration system may retrieve the encrypted or decrypted data blob from the intermediate cloud storage by providing a required secret to the intermediate cloud storage. The required secret may be provided to the registration system by the user device (e.g., via a matrix barcode such as a QR code). The exemplary techniques described in this document may be applied to register any appropriate number of user devices (e.g., 5, 20, hundreds, or thousands) to a common (e.g., the same) cloud-based management service.
[0016] The exemplary technique described in this document offers various advantages over conventional techniques for registering user device(s) to a cloud-based management service. For example, the exemplary technique may increase the likelihood of successful registration of user device(s) to a cloud-based management service. The exemplary technique may simplify the process for registering user device(s) and / or accelerate the process in a secure manner. The exemplary technique may be at least as secure as manual techniques for registering user device(s) to a cloud-based management service.
[0017] An exemplary technique may enable each user device to upload an encrypted data blob (which includes information identifying the user device) to non-authenticated intermediate cloud storage (which may make available to a caller providing the encrypted data blob (or its decrypted version) an expected session identifier and an expected correlation key). An exemplary technique may pre-authorize the uploading of each encrypted data blob from its respective user device to the intermediate cloud storage so that the caller can authenticate using the session identifier and / or correlation key. For example, the intermediate cloud storage may have been previously notified (e.g., by a registration system) to expect a call containing the session identifier and correlation key.
[0018] The exemplary technique can reduce the latency associated with registering user devices to a cloud-based management service and / or increase the reliability of the device registration process. The exemplary technique can automate at least some of the manual actions characteristic of conventional techniques for registering user devices to a cloud-based management service.
[0019] Exemplary techniques can reduce the amount of time and / or resources (e.g., processor cycles, memory, network bandwidth) consumed to register user devices with a cloud-based management service. Exemplary techniques can reduce the costs associated with registering user devices with a cloud-based management service. For example, by utilizing intermediate cloud storage, exemplary techniques can reduce the complexity of the device registration process and / or reduce IT administrator interactions (and the latency associated with such interactions), which can reduce the cost of registering user devices with a cloud-based management service. Reducing the complexity of device registration and / or the number of IT administrator interactions can reduce the time and / or resource consumption associated with registering user devices with a cloud-based management service. Exemplary techniques can increase the efficiency of the computing system used to register user devices with a cloud-based management service.
[0020] Exemplary techniques can increase the efficiency of IT administrators. For example, by utilizing intermediate cloud storage, exemplary techniques can reduce the amount of time, effort, and / or number of steps required by IT administrators to facilitate the registration of user devices with cloud-based managed services. Exemplary techniques can improve the user experience for IT administrators (e.g., by automating or streamlining the device registration process).
[0021] FIG. 1 is a block diagram of an exemplary intermediate cloud storage-based device registration system (100) according to an embodiment. Generally speaking, the intermediate cloud storage-based device registration system (100) operates to provide information to a user in response to a request received from a user (e.g., a HyperText Transfer Protocol (HTTP) request). The information may include documents (e.g., web pages, images, audio files, video files, etc.), executable outputs, and / or any other suitable type of information. According to an exemplary embodiment described herein, the intermediate cloud storage-based device registration system (100) registers a plurality of user devices (102A-102M) to a cloud-based management service (116).
[0022] As illustrated in FIG. 1, an intermediate cloud storage-based device registration system (100) includes a plurality of user devices (102A-102M), a network (104), a plurality of servers (106A-106N), and a management system (108). Communication between the user devices (102A-102M), servers (106A-106N), and management system (108) is performed on the network (104) using a well-known network communication protocol. The network (104) may be a wide-area network (e.g., the Internet), a local area network (LAN), other types of networks, or a combination thereof.
[0023] The user device (102A-102M) is a processing system capable of communicating with the server (106A-106N) and the management system (108). An example of a processing system is a system comprising at least one processor capable of manipulating data according to a set of instructions. For example, the processing system may be a computer, a personal digital assistant, etc. The user device (102A-102M) is configured to provide a request to the server (106A-106N) to request information stored on (or otherwise accessible through) the server (106A-106N). For example, the user may initiate a request to execute a computer program (e.g., an application) using a client (e.g., a web browser, a web crawler, or another type of client) placed on the user device (102) which is owned by the user or otherwise accessible to the user. According to some exemplary embodiments, a user device (102A-102M) may access a domain (e.g., a website) hosted by a server (106A-106N), and the user device (102A-102M) may access information accessible through the domain. Such a domain may include web pages, which may be provided, for example, as HyperText Markup Language (HTML) documents and objects (e.g., files) (linked thereto).
[0024] Each of the user devices (102A-102M) may include any client-enabled system or device, including but not limited to a desktop computer, a laptop computer, a tablet computer, a wearable computer, such as a smart watch or a head-mounted computer, a personal digital assistant, a cellular telephone, an Internet of Things (IoT) device, or similar. It will be recognized that any one or more of the user devices (102A-102M) can communicate with any one or more of the servers (106A-106N).
[0025] User devices (102A-102M) are illustrated to include their respective registration agents (110A-110M). The registration agents (110A-110M) are configured to provide their respective matrix barcodes (122A-122M) and their respective encrypted data blobs (124A-124M) to facilitate the registration of the user devices (102A-102M) to the cloud-based management service (116). The matrix barcodes (122A-122M) include their respective session identifiers, their respective decryption keys, and their respective correlation keys. Each session identifier is a session that identifies the session during which the user device is registered with the cloud-based management service (116). For example, the session identifier may be a random number or a string. In another example, the session identifier may be a semi-random number or a string. Each decryption key is configured to be used to decrypt the respective encrypted data blob provided by the respective user device. Each correlation key can be used to correlate the respective user device with actions and / or records associated with the respective user device. For example, each correlation key can be used to track, audit, and / or troubleshoot the respective user device, and / or generate reports regarding the respective user device. Each correlation key may include a product key associated with the respective user device. Each product key can identify the OS license of the operating system (OS) utilized by the respective user device (e.g., deployed on the respective user device).For example, the product key associated with each user device can serve as a convenient correlator because the product key may be available in the purchase order associated with the user device and / or included in a reference to the user device by the Original Equipment Manufacturer (OEM) that manufactured the user device and / or used in a support ticket for the user device and / or embedded within the user device (e.g., copied into its motherboard), so that the product key can be used by the OS of the user device. Each decryption key and / or each correlator may be a symmetric key or an asymmetric public key. For example, each decryption key and / or each correlator may be a cryptographic key generated according to the Advanced Encryption Standard (AES) established by the National Institute of Standards and Technology (NIST) in 2001. According to this example, each decryption key and / or each correlation key may be an AES-128, AES-192, or AES-256 key. Each encrypted data blob includes information identifying the user device providing each encrypted data blob.
[0026] A server (106A-106N) is a processing system capable of communicating with a user device (102A-102M). The server (106A-106N) is configured to execute a computer program that provides information to the user device (102A-102M). For example, the server (106A-106N) may push such information to the user device (102A-102M) or provide information in response to a request received from the user device (102A-102M). The request may be user-generated or generated without user involvement. The information provided by the server (106A-106N) may include documents (e.g., web pages, images, audio files, video files, etc.), outputs of executables, or any other appropriate type of information. According to some exemplary embodiments, the servers (106A-106N) are configured to host their respective websites so that the websites can be accessed by users of the intermediate cloud storage-based device registration system (100).
[0027] The first server(s) (106A) is illustrated to include an intermediate cloud storage (112) for the purpose of explanation. The intermediate cloud storage (112) is configured to receive encrypted data blobs (124A-124M) from their respective registration agents (110A-110M). In one exemplary implementation, the intermediate cloud storage (112) is configured to provide access to the encrypted data blobs (124A-124M) in response to receiving their respective designated secrets from entities requesting access to the encrypted data blobs (124A-124M). For example, the intermediate cloud storage (112) may provide access to the first encrypted data blob (124A) in response to receiving their respective first designated secrets. The intermediate cloud storage (112) may provide access to the second encrypted data blob (124B) in response to receiving their respective second designated secrets, and so on. Each secret may include a session identifier and a correlation key (which is contained within the matrix barcode provided by the user device that provided the respective matrix barcode). In another exemplary implementation, the intermediate cloud storage (112) is configured to decrypt the encrypted data blobs (124A-124M) to provide their respective decrypted data blobs. According to this implementation, the intermediate cloud storage (112) is configured to provide access to the decrypted data blobs in response to the receipt of their respective designated secrets from an entity requesting access to the decrypted data blobs.
[0028] The second server(s) (106B) is illustrated to include a cloud-based management service (116) for the purpose of explanation. The cloud-based management service (116) is configured to enable the management of user devices (102A-102M). For example, the cloud-based management service (116) may enable an IT administrator associated with the management system (108) to manage the user devices (102A-102M). To this end, the cloud-based management service (116) provides a deployment platform profile identifier to each of the user devices (102A-102M) in response to the receipt of a decrypted data blob and a designated secret identifying each user device. The designated secret for each user device may include a session identifier associated with each user device. The cloud-based management service (116) may receive the designated secret and the decrypted data blob from the management system (108). Each deployment platform profile identifier specifies the settings and policies to be applied to each user device for the purpose of configuring each user device.
[0029] The cloud-based management service (116) is configured to obtain a deployment platform profile identifier from the Device Directory Service (DDS) (118). For example, the cloud-based management service (116) may provide the decrypted data blob of each user device (102A-102M) to the DDS (118) in response to the receipt of each decrypted data blob and their respective designated secrets. The cloud-based management service (116) may receive the deployment platform profile identifier from the DDS (118) based on the cloud-based management service (116) providing the decrypted data blob of the user device (whereby each deployment platform profile identifier must be provided).
[0030] The Nth server(s) (106N) is illustrated to include a DDS (118) for the purpose of explanation. The DDS (118) is configured to provide a deployment platform profile identifier for each user device to the cloud-based management service (116) in response to the receipt of a decrypted data blob of each user device from the cloud-based management service (116). For example, the DDS (118) may maintain a cross-reference list that cross-references the decrypted data blob of user devices (102A-102M) with the deployment platform profile identifier of user devices (102A-102M). Upon receipt of a decrypted data blob of a user device, the DDS (118) may traverse the cross-reference list to determine which of the deployment platform profile identifiers cross-references the decrypted data blob of the user device. DDS (118) can provide a deployment platform profile identifier that is cross-referenced with the decrypted data blob of the user device to a cloud-based management service (116) for forwarding to the user device.
[0031] The management system (108) is a processing system capable of communicating with user devices (102A-102M) and servers (106A-106N). The management system (108) is configured to perform operations to facilitate the registration of user devices (102A-102M) to a cloud-based management service (116) (e.g., in response to commands received from an IT administrator associated with the IT management system (108)). The management system (108) includes a registration system (114), which is configured to communicate with the registration agents (110A-110M) of each user device (102A-102M), intermediate cloud storage (112), and the cloud-based management service (116) to facilitate the registration of user devices (102A-102M) to the cloud-based management service (116). The registration system (108) is configured to scan matrix barcodes (122A-122M) received from each registration agent (110A-110M). For example, the registration system (114) includes a matrix barcode scanner (120) configured to scan matrix barcodes (122A-122M). The matrix barcode scanner (120) can scan the matrix barcodes (122A-122M) using pairing between the matrix barcode scanner (120) and each user device (102A-102M). For example, pairing can be achieved using wireless technology standards, such as Bluetooth® or ZigBee®. According to this example, the registration system (114) can analyze the matrix barcodes (122A-122M) (which are scanned internally by the matrix barcode scanner to identify each session identifier, each decryption key, and each correlation key).
[0032] In a first exemplary implementation, the registration system (114) receives encrypted data blobs (124A-124M) from their respective registration agents (110A-110M). According to this implementation, the registration system (114) triggers the intermediate cloud storage (112) to decrypt the encrypted data blobs (124A-124M) using their respective decryption keys to provide their respective decrypted data blobs. For example, the registration system (114) may trigger the intermediate cloud storage (112) to decrypt each encrypted data blob by providing their respective session identifiers, their respective decryption keys, and their respective correlation keys to the intermediate cloud storage (112). According to this implementation, the registration system (114) also receives the decrypted data blobs from the intermediate cloud storage (112).
[0033] In a second exemplary implementation, the registration system (114) retrieves the encrypted data blobs (124A-124M) from the intermediate cloud storage (112) (e.g., in response to the intermediate cloud storage (112) receiving the encrypted data blobs (124A-124M) from their respective registration agents (110A-110M). According to this implementation, the registration system (114) decrypts the encrypted data blobs (124A-124M) using their respective decryption keys contained in their respective matrix barcodes (122A-122M) to provide their respective decrypted data blobs.
[0034] In both of these implementations, the registration system (114) registers user devices (102A-102M) to a cloud-based management service (116) using their respective decoded data blobs.
[0035] Each of the registration agent (110A-110M), intermediate cloud storage (112), registration system (114), cloud-based management service (116), and DDS (118) may be implemented in various ways to facilitate the registration of any one or more of the user devices (102A-102M) to the cloud-based management service (116), including being implemented in hardware, software, firmware, or any combination thereof. For example, each of the registration agent (110A-110M), intermediate cloud storage (112), registration system (114), cloud-based management service (116), and DDS (118) may be implemented as computer program code configured to run on one or more processors. In another example, each of the registration agent (110A-110M), intermediate cloud storage (112), registration system (114), cloud-based management service (116), and DDS (118) may be implemented at least partially as hardware logic / electrical circuits. For example, each of the registration agent (110A-110M), intermediate cloud storage (112), registration system (114), cloud-based management service (116) and DDS (118) may be implemented at least partially within a Field-Programmable Gate Array (FPGA), Application-Specific Integrated Circuit (ASIC), Application-Specific Standard Product (ASSP), System-on-a-Chip system (SoC), Complex Programmable Logic Device (CPLD), etc.Each SoC may include an integrated circuit chip comprising one or more of a processor (e.g., microcontroller, microprocessor, Digital Signal Processor (DSP)), memory, one or more communication interfaces, and / or additional circuitry and / or embedded firmware to perform its function.
[0036] Intermediate cloud storage (112), cloud-based management service (116), and DDS (118) are depicted as being included within separate servers or groups thereof for the purpose of description and are not intended to be limited. It will be recognized that intermediate cloud storage (112), cloud-based management service (116), and DDS (118) may be included within any one or more of servers (106A-106N). For example, any two or more of intermediate cloud storage (112), cloud-based management service (116), and / or DDS (118) may be included partially or wholly within a common (e.g., the same) server.
[0037] FIG. 2 is an exemplary activity illustration (200) for registering a user device to a cloud-based management service using intermediate cloud storage according to an embodiment. FIG. 2 depicts the registration agent (110), intermediate cloud storage (112), registration system (114), cloud-based management service (116), and device directory service (DDS) (118) illustrated in FIG. 1. Activities (222, 224, 226, 228, 230, 232, 234, 236, 238, 240, 242, 244, 246, 248, 250, 252, 254, and 256) will now be described with reference to the registration agent (110), intermediate cloud storage (112), registration system (114), cloud-based management service (116), and DDS (118).
[0038] In activity (222), the registration system (114) scans a matrix barcode (e.g., a QR code). The matrix barcode includes a session identifier (also known as a session ID), a decryption key, and a correlation key. The session ID identifies a session in which the user device is registered with the cloud-based management service (116). The decryption key is configured to be used to decrypt an encrypted data blob to be received from the user device. The decryption key may be a symmetric key or an asymmetric public key. The correlation key is configured to correlate the user device to a record associated with the user device. Activity (226) may include analyzing the matrix barcode to identify, for example, the session ID, the decryption key, and the correlation key.
[0039] In an exemplary embodiment, the registration system (114) displays a message on the display of a management system including the registration system (114). The message prompts a user of the management system (e.g., an IT administrator using the registration system (114) to pre-provision a user device as a cloud-based management service (116)) to initiate scanning of the matrix barcode. For example, the user may initiate scanning of the matrix barcode by providing user input that directs the matrix barcode scanner toward the display of the user device where the registration agent (110) is deployed and causes the matrix barcode scanner to scan the matrix barcode from the display of the user device.
[0040] In activity (224), the registration system (114) pre-authorizes a registration agent (110) (e.g., a user device including the registration agent (110)) to upload an encrypted data blob to intermediate cloud storage (112). Pre-authorizing the registration agent (110) to upload an encrypted data blob means that the registration agent (110) is authorized to upload the encrypted data blob before the registration agent (110) uploads the encrypted data blob. The registration system (114) may pre-authorize the registration agent (110) based at least partially on the fact that a matrix barcode (e.g., a correlation key therein) authenticates the registration agent (110) to the registration system (114). The registration system (114) may indicate that the user device is pre-authorized to upload an encrypted data blob to intermediate cloud storage (112) by providing a shared secret (e.g., a session ID) associated with the user device to the intermediate cloud storage (112). For example, the intermediate cloud storage (112) may be configured to ignore (and therefore not store) each data blob (whether encrypted or not) unless the user device providing the data blob is pre-authorized by the registration system (114). By pre-authorizing the user device in this way, the intermediate cloud storage (112) may avoid being subjected to a massive attack in which a malicious software application may bombard the intermediate cloud storage (112) with data blobs that may each be 4 kilobytes (kB) or more of data until the performance of the intermediate cloud storage (112) is substantially compromised.
[0041] In activity (226), the registration agent (110) provides the encrypted data blob and session ID to the intermediate cloud storage (112). For example, the registration agent (110) may provide the encrypted data blob and session ID using a POST command. The encrypted data blob serves as an identifier to identify the user device. For example, the encrypted data blob can uniquely identify the user device. The registration agent (110) may authenticate the intermediate cloud storage (112) before providing the encrypted data blob and session ID to the intermediate cloud storage (112).
[0042] In an exemplary embodiment, the registration agent (110) displays a webpage associated with the device pre-provisioning service of the cloud-based management service (116) on the display of the user device to which the registration agent (110) is deployed. The webpage triggers the user of the user device (e.g., an IT administrator using the registration system (114) to pre-provision the user device as the cloud-based management service (116)) to provide a specified input through the user interface of the user device (e.g., a display, keyboard, or mouse) to continue registering the user device to the cloud-based management service (116). For example, the user may provide the specified input by selecting a specified interface item on the user interface. According to this embodiment, the registration agent (110) provides an encrypted data blob and a session ID to the intermediate cloud storage (112) in response to the user providing the specified input (e.g., based on).
[0043] In activity (226), the intermediate cloud storage (112) provides confirmation to the registration agent (110) to confirm that the intermediate cloud storage has received the encrypted data blob and session ID.
[0044] In activity (230), the registration system (114) authenticates to the intermediate cloud storage (112) using a session ID. In activity (230), the registration system (114) also provides the intermediate cloud storage (112) with a hash and a decryption key of the correlation key. For example, the registration system (114) can generate a hash of the correlation key by performing a hash operation on the correlation key in response to receiving the correlation key from the registration agent (110) in activity (222).
[0045] In activity (232), the intermediate cloud storage (112) provides confirmation to the registration system (114) to confirm the authentication of the registration system (114) in activity (230) and the reception of the hash of the decryption key and the correlation key from the registration system (114).
[0046] In activity (234), the intermediate cloud storage (112) authenticates the registration agent (110) using the session ID received by the intermediate cloud storage (112) from the registration system (114) in activity (230).
[0047] In activity (236), the registration agent (110) provides a confirmation to the intermediate cloud storage (112) to verify the authentication of the intermediate cloud storage (112) in activity (234).
[0048] In activity (238), the registration system (114) provides a request to the intermediate cloud storage (112) to request that the intermediate cloud storage decrypt an encrypted data blob using a decryption key. The request includes a session ID and a correlation key.
[0049] In activity (240), the intermediate cloud storage (112) determines whether the session IDs are the same by comparing the session ID received in activity (230) with the session ID received in activity (238). In activity (240), the intermediate cloud storage (112) also determines whether the hashes are the same by comparing the hash of the correlated key received in activity (230) with the hash of the key received in activity (238). For example, the intermediate cloud storage (112) may generate the hash of the correlated key received in activity (238) by performing a hash operation on it. If the session IDs are the same and the hashes are the same, the intermediate cloud storage (112) decrypts the encrypted data blob using the decryption key. If the session IDs are not the same and / or the hashes are not the same, the intermediate cloud storage (112) does not decrypt the encrypted data blob. For the purpose of example, it is assumed that the session ID is the same and the hash is the same, and that the intermediate cloud storage (112) decrypts the encrypted data blob.
[0050] In activity (242), the intermediate cloud storage (112) provides the decrypted data blob to the registration system (114).
[0051] In activity (244), the registration system (114) authenticates to the cloud-based management service (116) using a session ID. In activity (244), the registration system (114) also registers the user device to the cloud-based management service (116) using a decrypted data blob.
[0052] In activity (248), the cloud-based management service (116) forwards the decrypted data blob to the DDS (118).
[0053] In activity (250), the DDS (118) provides a deployment platform profile ID to the cloud-based management service (116). The deployment platform profile ID identifies the configuration policy to be applied to the user device during the configuration of the user device. In an exemplary embodiment, the DDS (118) provides a hash-ID pair by cross-referencing the decrypted data blob associated with each user device with the deployment platform profile ID associated with each user device. Each deployment platform profile ID identifies the configuration policy to be applied to each user device. According to this embodiment, the DDS (118) examines the hash-ID pair to identify the hash-ID pair containing the decrypted data blob received in activity (248). According to this embodiment as well, the DDS (118) identifies the deployment platform profile ID to be provided to the cloud-based management service based on the fact that the deployment platform profile ID is cross-referenced with the decrypted data blob within the identified hash-ID pair.
[0054] In activity (252), the cloud-based management service (116) provides the registration agent (110) with the deployment platform profile ID received by the cloud-based management service in activity (250) to enable the configuration of the user device by using the configuration policy.
[0055] In activity (254), the registration agent (110) requests authorization from the user of the user device to configure the user device. For example, the registration agent (110) may request authorization by displaying a query on the display of the user device. The query may indicate that the user device is registered with the cloud-based management service (116) and is therefore authorized to be configured using a configuration policy identified by a deployment platform profile ID.
[0056] Activity (254) may include asking the user which of the policies and / or configurations identified by the deployment platform profile ID will be applied to the user device. For example, the registration agent (110) may present a list of configurations and / or policies and allow the user of the device to select which of the configurations and / or policies will be applied to the user device or to deselect configurations and / or policies that will not be applied to the user device. Thus, the user of the user device can make asynchronous changes to the configurations and / or policies to be applied to the user device.
[0057] In activity (256), the registration agent (110) configures the user device based on a configuration policy identified by a deployment platform profile ID. For example, the deployment platform profile ID may include a configuration policy, or a location indicator indicating a location (from which a configuration policy can be derived). Activity (256) is performed in response to a user of the user device providing authorization requested in activity (254). For example, the user may provide authorization by providing specified input through the user interface of the user device (e.g., a display, keyboard, or mouse).
[0058] Activities (222, 224, 226, 228, 230, 232, 234, 236, 238, 240, 242, 244, 246, 248, 250, 252, 254, and 256) may be performed for each user device to be registered with the cloud-based management service (116). It will be recognized that any one or more of the activities may be performed in a batch manner (e.g., for more than one user device at a time) to increase the speed and efficiency of the registration process. It will also be recognized that any one or more of the activities may be performed repeatedly so that the activity is performed for the user device in each iteration. Any two or more of the iterations may be performed consequentially.
[0059] In some exemplary embodiments, one or more of the steps illustrated in the activity diagram (200) may not be performed. Furthermore, steps added to or replacing the steps illustrated in the activity diagram (200) may be performed.
[0060] FIG. 3 is another exemplary activity illustration (300) for registering a user device to a cloud-based management service using intermediate cloud storage according to an embodiment. FIG. 3 depicts the registration agent (110), intermediate cloud storage (112), registration system (114), cloud-based management service (116), and device directory service (DDS) (118) shown in FIG. 1. The activity illustration (300) includes activities (222, 224, 226, 228, 230, 232, 234, 236, 244, 246, 248, 250, and 252), which are identical to the activities having the same reference numbers shown in FIG. 2. The activity illustration (300) does not include activities (238, 240, and 242) of the activity illustration (200) shown in FIG. 2. Instead, the activity diagram (300) of FIG. 3 includes activities (362, 364, 366, and 368). Activities (362, 364, 366, and 368) will now be described with reference to the intermediate cloud storage (112) and the registration system (114).
[0061] In activity (362), the registration system (114) requests an encrypted data blob by providing a request to the intermediate cloud storage (112). The request includes a session ID and a correlation key.
[0062] In activity (364), the intermediate cloud storage (112) determines whether the session IDs are the same by comparing the session ID received in activity (230) with the session ID received in activity (362). In activity (364), the intermediate cloud storage (112) also determines whether the hashes are the same by comparing the hash of the correlated key received in activity (230) with the hash of the correlated key received in activity (362). For example, the intermediate cloud storage (112) may generate the hash of the correlated key received in activity (362) by performing a hash operation on it. If the session IDs are the same and the hashes are the same, the intermediate cloud storage (112) provides an encrypted data blob. If the session IDs are not the same and / or the hashes are not the same, the intermediate cloud storage (112) does not provide an encrypted data blob. For the purpose of illustration, it is assumed that the session IDs are the same and the hashes are the same, and the intermediate cloud storage (112) provides an encrypted data blob.
[0063] In activity (366), the intermediate cloud storage (112) provides the encrypted data blob to the registration system (114).
[0064] In activity (368), the registration system (114) decrypts the encrypted data blob using a decryption key to provide the decrypted data blob.
[0065] In some exemplary embodiments, one or more of the steps illustrated in the activity diagram (300) may not be performed. Furthermore, steps in addition to or in place of the steps illustrated in the activity diagram (300) may be performed. For example, the activity diagram (300) may further include the activities (254 and 256) illustrated in the activity diagram (200) of FIG. 2.
[0066] FIGS. 4 through 6 depict flowcharts (400, 500, and 600) of an exemplary method for registering a user device to a cloud-based management service using intermediate cloud storage according to an embodiment. The flowcharts (400, 500, and 600) may be performed, for example, by the registration system (114) shown in FIGS. 1 through 3. For the purpose of explanation, the flowcharts (400, 500, and 600) are described with respect to the management system (700) shown in FIG. 7. The management system (700) includes a registration system (714) which is an exemplary implementation of the registration system (114) shown in FIGS. 1 through 3. The registration system (714) includes scan logic (732), trigger logic (734), and register logic (736). Based on the discussion regarding the flowcharts (400, 500, and 600), additional structural and operational embodiments will be apparent to those skilled in the relevant industry(s).
[0067] As illustrated in FIG. 4, the method of the flowchart (400) begins at step (402). In step (402), a matrix barcode identifying the user device is scanned. The matrix barcode includes a session identifier, a decryption key, and a correlation key. For example, the matrix barcode may be a QR code. In another example, the matrix barcode may include a JavaScript Object Notation (JSON) blob containing a session identifier and a correlation key. The session identifier identifies the session (during which the user device is registered with a cloud-based management service) (e.g., uniquely). The session identifier may be a Global Unique IDentifier (GUID). The decryption key is configured to be used to decrypt an encrypted data blob received from the user device. The correlation key is available to correlate the user device to a record associated with the user device. In an exemplary implementation, the scan logic (732) scans the matrix barcode (738) identifying the user device. According to this implementation, the matrix barcode (738) includes a session identifier (also known as a session ID) (748), a correlation key (750), and a decryption key (754). The scan logic (732) may generate a trigger instruction (742) based on the reception of the matrix barcode (738) (e.g., at least partially based). The trigger instruction (742) instructs the trigger logic (734) to provide a decryption request (744) to intermediate cloud storage.
[0068] In step (404), by providing the session identifier, decryption key, and correlation key to the intermediate cloud storage, the intermediate cloud storage is triggered to decrypt the encrypted data blob using the decryption key to provide the decrypted data blob. The encrypted data blob contains information identifying the user device. For example, the information within the encrypted data blob may identify the hardware included in the user device. The encrypted data blob may have been encrypted using the AES-256 encryption method. Accordingly, the intermediate cloud storage may trigger the intermediate cloud storage to decrypt the encrypted data blob according to the AES-256 encryption method. It will be recognized that any appropriate encryption method may be used to decrypt the encrypted data blob depending on the encryption method used to generate the encrypted data blob. For example, depending on whether the encrypted data was encrypted using an asymmetric private key corresponding to an asymmetric public key or using a symmetric key, the decryption key may be an asymmetric public key or a symmetric key. In an exemplary implementation, trigger logic (734) triggers intermediate cloud storage to decrypt an encrypted data blob using a decryption key (754) to provide a decrypted data blob (746). For example, trigger logic (734) may trigger intermediate cloud storage to decrypt an encrypted data blob based on the reception of a trigger command (742). According to this implementation, trigger logic (734) triggers intermediate cloud storage by providing intermediate cloud storage with a decryption request (744) containing a session identifier (748), a correlation key (750), and a decryption key (754). The decryption request (744) requests intermediate cloud storage to decrypt the encrypted data blob.
[0069] In an exemplary embodiment, triggering the intermediate cloud storage in step (404) includes providing the intermediate cloud storage with a session identifier, thereby enabling the intermediate cloud storage to use the session identifier to locate the encrypted data blob.
[0070] In step (406), the decrypted data blob is received from the intermediate cloud storage. In an exemplary implementation, in response to providing a decryption request (744) to the intermediate cloud storage, the registration logic (736) receives the decrypted data blob from the intermediate cloud storage.
[0071] In step (408), the user device is registered with the cloud-based management service using the decrypted data blob. In an exemplary implementation, the registration logic (736) registers the user device with the cloud-based management service using the decrypted data blob (746). For example, the registration logic (736) may provide the cloud-based management service with a registration command (752) containing the decrypted data blob (746). For example, the registration command (752) may instruct the cloud-based management service to confirm the registration of the user device with the cloud-based management service. In another example, the registration command (752) may instruct the cloud-based management service to request a deployment platform profile ID from the device directory service that identifies the configuration policy to be applied to the user device during the configuration of the user device.
[0072] In an exemplary embodiment, registering the user device in step (408) includes initiating the configuration of the user device as a configuration policy by triggering the provision of a deployment platform profile identifier to the user device. According to this embodiment, the deployment platform profile identifier is based on a decrypted data blob and identifies the policy. For example, the deployment platform profile identifier may include the policy or a pointer to the location where the policy is stored. The deployment platform profile identifier may also identify an application to be deployed on the user device. Initiating the configuration of the user device may include embedding information regarding the policy within a Unified Extensible Firmware Interface (UEFI) interface of the user device's motherboard.
[0073] In another exemplary embodiment, the intermediate cloud storage is authenticated to the user device using a session identifier.
[0074] In some exemplary embodiments, one or more steps (402, 404, 406 and / or 408) of the flowchart (400) may not be performed. Furthermore, steps added to or substituted for steps (402, 404, 406 and / or 408) may be performed. For example, in an exemplary embodiment, the method of the flowchart (400) further includes signing into a registration system that scans a matrix barcode to a tenant of a cloud-based management service. For example, the registration logic (736) may sign into the registration system (714) to a tenant. According to this embodiment, the decrypted data blob includes the serial number of the user device. According to this embodiment also, registering the user device to the cloud-based management service includes calling the Application Programming Interface (API) of the cloud-based management service and passing the serial number of the user device and the correlation key to the API.
[0075] In another exemplary embodiment, the method of the flowchart (400) further comprises pre-authorizing the user device to upload an encrypted data blob to the intermediate cloud storage before the user device uploads the encrypted data blob to the intermediate cloud storage, based at least partially on the reception of a matrix barcode from the user device. For example, the scan logic (732) may pre-authorize the user device to upload an encrypted data blob to the intermediate cloud storage, based at least partially on the reception of a matrix barcode (738) from the user device.
[0076] In another exemplary embodiment, the method of flowchart (400) includes one or more of the steps illustrated in the flowchart (500) of FIG. 5. As illustrated in FIG. 5, the method of flowchart (500) begins at step (502). In step (502), a registration system scanning a matrix barcode authenticates to the intermediate cloud storage using a session identifier. In an exemplary implementation, scan logic (732) authenticates the registration system (714) scanning the matrix barcode (738) to the intermediate cloud storage using a session ID (748). For example, scan logic (732) may provide authentication information (740) containing the session ID (748) to the intermediate cloud storage to authenticate the registration system (714) to the intermediate cloud storage.
[0077] In step (504), the hash of the correlated key is provided to the intermediate cloud storage. In an exemplary implementation, the scan logic (732) provides the intermediate cloud storage with a key hash (752), which is the hash of the correlated key (750). For example, the key hash (752) may be included in the authentication information (740) that the scan logic (732) provides to the intermediate cloud storage. According to this implementation, the scan logic (732) may generate the key hash (752) by performing a hash operation on the correlated key (750). For example, the scan logic (732) may generate the hash of the correlated key (750) using a Secure Hash Algorithm 2 (SHA-2) technique, such as SHA-256.
[0078] In step (506), a request is provided to the intermediate cloud storage. The request includes a session identifier, a decryption key, and a correlation key. The request asks the intermediate cloud storage to use the decryption key included in the request to decrypt the encrypted data blob. In an exemplary implementation, trigger logic (734) provides a decryption request (744) to the intermediate cloud storage. The decryption request (744) includes a session identifier (748), a correlation key (750), and a decryption key (754). The decryption request (744) asks the intermediate cloud storage to use the decryption key (754) included in the decryption request (744) to decrypt the encrypted data blob.
[0079] In step (508), the intermediate cloud storage is configured to verify that the session identifier used to authenticate the registration system and the session identifier included in the request are the same. For example, in step (508), causing the intermediate cloud storage to verify that the session identifier used to authenticate the registration system and the session identifier included in the request are the same may be the result of providing a request to the intermediate cloud storage in step (506). In an exemplary implementation, trigger logic (734) causes the intermediate cloud storage to verify that the session ID used to authenticate the registration system (714) and the session ID (748) included in the decryption request (744) are the same.
[0080] In step (510), the intermediate cloud storage is configured to verify that the correlation key on which the hash of the correlation key is based and the correlation key included in the request are identical. For example, the intermediate cloud storage may be configured to verify that the hash of the correlation key provided to the intermediate cloud storage in step (504) and the hash of the correlation key included in the request provided to the intermediate cloud storage in step (506) are identical. Causing the intermediate cloud storage to verify in step (510) that the correlation key on which the hash of the correlation key is based and the correlation key included in the request are identical may be the result of providing the request to the intermediate cloud storage in step (506). In an exemplary implementation, trigger logic (734) causes the intermediate cloud storage to verify that the correlation key on which the hash of the correlation key is based and the correlation key (750) included in the decryption request (744) are identical.
[0081] In an aspect of this embodiment, decryption of the encrypted data blob is based on the successful completion of steps (508 and 510).
[0082] In another exemplary embodiment, the method of flowchart (400) includes one or more of the steps illustrated in the flowchart (600) of FIG. 6. As illustrated in FIG. 6, the method of flowchart (600) begins at step (602). In step (602), a matrix barcode identifying each user device is scanned. Each matrix barcode includes a session identifier, a decryption key, and a correlation key. Each session identifier identifies a session (during which each user device is registered with a cloud-based management service). Each decryption key is configured to be used to decrypt an encrypted data blob to be received from each user device. Each correlation key is available to correlate each user device to an action and / or record associated with each user device. In an exemplary embodiment, scan logic (732) scans the matrix barcode.
[0083] In step (604), the intermediate cloud storage (which receives an encrypted data blob containing information identifying each user device from each user device) is triggered to decrypt the encrypted data blob using each decryption key to provide each decrypted data blob by providing each session identifier, each decryption key, and each correlation key to the intermediate cloud storage. In an exemplary implementation, the trigger logic (734) triggers the intermediate cloud storage to decrypt the encrypted data blob using each decryption key to provide each decrypted data blob.
[0084] In step (606), the decrypted data blob is received from the intermediate cloud storage. In an exemplary implementation, the registration logic (736) receives the decrypted data blob from the intermediate cloud storage.
[0085] In step (608), user devices are registered with a cloud-based management service using their respective decrypted data blobs. In an exemplary implementation, registration logic (736) registers user devices with a cloud-based management service using their respective decrypted data blobs.
[0086] In an aspect of this embodiment, the method of the flowchart (500) further includes signing in a registration system that scans a matrix barcode to a tenant of a cloud-based management service. For example, the registration logic (736) may sign in the registration system (714) to a tenant. According to this aspect, the decrypted data blob contains the respective serial number of each user device. According to this aspect also, in step (608), registering a user device to a cloud-based management service includes performing a batch call into the Application Programming Interface (API) of the cloud-based management service and passing the serial number and correlation key of each user device to the API.
[0087] It will be recognized that the management system (700) may not include one or more of the scan logic (732), trigger logic (734), and / or registration logic (736). Furthermore, the management system (700) may include components added to or replacing the scan logic (732), trigger logic (734), and / or registration logic (736).
[0088] FIGS. 8 and 9 depict flowcharts (800 and 900) of an exemplary method for registering a user device to a cloud-based management service using intermediate cloud storage according to an embodiment. The flowcharts (800 and 900) may be performed, for example, by the registration system (114) shown in FIGS. 1 through 3. For the purpose of explanation, the flowcharts (800 and 900) are described with respect to the management system (1000) shown in FIG. 10. The management system (1000) includes a registration system (1014) which is an exemplary implementation of the registration system (114) shown in FIGS. 1 through 3. The registration system (1014) includes scan logic (732), decryption logic (1056), and registration logic (736). Based on the discussion of the flowcharts (800 and 900), additional structural and operational embodiments will be apparent to those skilled in the relevant industry(s).
[0089] As illustrated in FIG. 8, the method of flowchart (800) begins at step (802). In step (802), a matrix barcode identifying a user device is scanned. The matrix barcode includes a session identifier, a decryption key, and a correlation key. The session identifier identifies the session (during which the user device is registered with a cloud-based management service) (e.g., uniquely identifying it). The decryption key is configured to be used to decrypt an encrypted data blob to be received from the user device. The correlation key can be used to correlate the user device to actions and / or records associated with the user device. In an exemplary implementation, the scan logic (1032) scans a matrix barcode (738) identifying a user device. According to this implementation, the matrix barcode (738) includes a session identifier (also known as a session ID) (748), a decryption key (754), and a correlation key (750).
[0090] In step (804), the registration system scanning the matrix barcode is authenticated to the intermediate cloud storage using a session identifier. In an exemplary implementation, the scan logic (732) authenticates the registration system (1014) to the intermediate cloud storage using a session ID (748). For example, the scan logic (732) may provide authentication information (740) containing the session ID (748) to the intermediate cloud storage to authenticate the registration system (1014) to the intermediate cloud storage. The authentication information may further include a key hash (752), which is a hash of a correlation key (750). The scan logic (732) may also use the key hash (752) to authenticate the registration system (1014) to the intermediate cloud storage.
[0091] In an exemplary embodiment, the intermediate cloud storage is authenticated to the user device using a session identifier.
[0092] In step (806), an encrypted data blob containing information identifying a user device is retrieved from an intermediate cloud storage that receives the encrypted data blob from the user device. In an exemplary implementation, decryption logic (1056) retrieves an encrypted data blob (1066) containing information identifying a user device from an intermediate cloud storage that receives the encrypted data blob (1066) from the user device. For example, decryption logic (1056) may receive a session ID (748) and a correlation key (750) from scan logic (732). According to this implementation, decryption logic (1056) may generate a blob request (1064) containing the session ID (748) and the correlation key (750). According to this implementation, decryption logic (1056) may also provide the blob request (1064) to the intermediate cloud storage. According to this implementation, in response to providing a blob request (1064) to the intermediate cloud storage, the decryption logic (1056) may receive an encrypted data blob (1066) from the intermediate cloud storage. For example, the decryption logic (1056) may receive the encrypted data blob (1066) from the intermediate cloud storage based on the intermediate cloud storage confirming that the session ID (748) in the authentication information (740) and the session ID (748) in the blob request (1064) are the same, and also based on the intermediate cloud storage confirming that the key hash (752) in the authentication information (740) and the hash of the correlation key (750) in the blob request (1064) are the same.
[0093] In an exemplary embodiment, retrieving the encrypted data blob in step (806) includes providing the intermediate cloud storage with a session identifier, thereby enabling the intermediate cloud storage to use the session identifier to determine the location of the encrypted data blob.
[0094] In step (808), the encrypted data blob withdrawn from the intermediate cloud storage is decrypted using a decryption key included in the matrix barcode to provide a decrypted data blob. In an exemplary implementation, the decryption logic (1056) decrypts the encrypted data blob (1066) using a decryption key (754) included in the matrix barcode (738) to provide a decrypted data blob (746). For example, the decryption logic (1056) may receive the decryption key (754) from the scan logic (732).
[0095] In step (810), the user device is registered with the cloud-based management service using the decrypted data blob. In an exemplary implementation, the registration logic (736) registers the user device with the cloud-based management service using the decrypted data blob (746). For example, the registration logic (736) may provide the cloud-based management service with a registration command (752) containing the decrypted data blob (746). For example, the registration command (752) may instruct the cloud-based management service to confirm the registration of the user device with the cloud-based management service. In another example, the registration command (752) may instruct the cloud-based management service to request a deployment platform profile ID from the device directory service that identifies the configuration policy to be applied to the user device during the configuration of the user device.
[0096] In an exemplary embodiment, registering the user device in step (810) includes initiating the configuration of the user device as a configuration policy by triggering the provision of a deployment platform profile identifier to the user device. According to this embodiment, the deployment platform profile identifier is based on a decrypted data blob and identifies the policy.
[0097] In some exemplary embodiments, one or more steps (802, 804, 806, 808 and / or 810) of the flowchart (800) may not be performed. Furthermore, steps added to or substituted for steps (802, 804, 806, 808 and / or 810) may be performed. For example, in an exemplary embodiment, the method of the flowchart (800) further includes signing into a registration system that scans a matrix barcode to a tenant of a cloud-based management service. For example, the registration logic (736) may sign into the registration system (1014) to a tenant. According to this embodiment, the decrypted data blob includes the serial number of the user device. According to this embodiment also, registering the user device to the cloud-based management service includes calling the Application Programming Interface (API) of the cloud-based management service and passing the serial number of the user device and the correlation key to the API.
[0098] In another exemplary embodiment, the method of the flowchart (800) further comprises pre-authorizing the user device to upload an encrypted data blob to the intermediate cloud storage before the user device uploads the encrypted data blob to the intermediate cloud storage, based at least partially on the reception of a matrix barcode from the user device. For example, the scan logic (732) may pre-authorize the user device to upload an encrypted data blob to the intermediate cloud storage, based at least partially on the reception of a matrix barcode (738) from the user device.
[0099] In another exemplary embodiment, the method of flowchart (800) includes one or more of the steps illustrated in the flowchart (900) of FIG. 9. As illustrated in FIG. 9, the method of flowchart (900) begins at step (902). In step (902), a matrix barcode identifying each user device is scanned. Each matrix barcode includes a session identifier, a decryption key, and a correlation key. Each session identifier identifies a session (during which each user device is registered with a cloud-based management service). Each decryption key is configured to be used to decrypt an encrypted data blob to be received from each user device. Each correlation key is available to correlate each user device to an action and / or record associated with each user device. In an exemplary embodiment, the scan logic (732) scans the matrix barcode.
[0100] In step (904), an encrypted data blob containing information identifying each user device is retrieved from an intermediate cloud storage that receives the encrypted data blob from each user device. In an exemplary implementation, decryption logic (1056) retrieves an encrypted data blob containing information identifying each user device from the intermediate cloud storage.
[0101] In step (906), the encrypted data blobs withdrawn from the intermediate cloud storage are decrypted using their respective decryption keys contained in their respective matrix barcodes to provide their respective decrypted data blobs. In an exemplary implementation, the decryption logic (1056) decrypts the encrypted data blobs using their respective decryption keys.
[0102] In step (908), user devices are registered with a cloud-based management service using their respective decrypted data blobs. In an exemplary implementation, registration logic (736) registers user devices with a cloud-based management service using their respective decrypted data blobs.
[0103] In an aspect of this embodiment, the method of the flowchart (900) further includes signing in a registration system that scans a matrix barcode to a tenant of a cloud-based management service. For example, the registration logic (736) may sign in the registration system (1014) to a tenant. According to this aspect, the decrypted data blob contains the respective serial number of each user device. According to this aspect also, in step (908), registering a user device to a cloud-based management service includes performing a batch call into the Application Programming Interface (API) of the cloud-based management service and passing the serial number and correlation key of each user device to the API.
[0104] It will be recognized that the management system (1000) of FIG. 10 may not include one or more of the scan logic (732), decoding logic (1056) and / or registration logic (736). Furthermore, the management system (1000) may include components added to or replacing the scan logic (732), decoding logic (1056) and / or registration logic (736).
[0105] FIG. 11 is a system illustration of an exemplary mobile device (1100) comprising various optional hardware and software components, generally referred to as 1102. Any component (1102) within the mobile device may communicate with any other component, but for ease of explanation, not all connections are illustrated. The mobile device (1100) may be any of various computing devices (e.g., cell phone, smartphone, handheld computer, Personal Digital Assistant (PDA), etc.) and may enable wireless bidirectional communication with one or more mobile communication networks (1104), such as a cellular or satellite network, or with a local area or wide area network.
[0106] A mobile device (1100) may include a processor (1110) (e.g., a signal processor, a microprocessor, an ASIC, or other control and processing logic circuit) for performing tasks such as signal coding, data processing, input / output processing, power control, and / or other functions. An operating system (1112) may control the allocation and use of the component (1102) and support for one or more applications (1114) (also known as application programs). Applications (1114) may include common mobile computing applications (e.g., an email application, a calendar, a contact manager, a web browser, a messaging application) and any other computing applications (e.g., a word processing application, a mapping application, a media player application).
[0107] A mobile device (1100) may include memory (1120). The memory (1120) may include non-removable memory (1122) and / or removable memory (1124). The non-removable memory (1122) may include RAM, ROM, flash memory, a hard disk, or other well-known memory storage technologies. The removable memory (1124) may include flash memory or a Subscriber Identity Module (SIM) card (which is well known in GSM communication systems), or other well-known memory storage technologies, such as a "smart card". The memory (1120) may store data and / or code for running an operating system (1112) and an application (1114). Exemplary data may include web pages, text, images, sound files, video data, or other data sets to be transmitted to and / or received from one or more network servers or other devices via one or more wired or wireless networks. The memory (1120) may store subscriber identifiers, such as an International Mobile Subscriber Identity (IMSI), and equipment identifiers, such as an International Mobile Equipment Identity (IMEI). Such identifiers may be transmitted to network servers to identify users and equipment.
[0108] A mobile device (1100) may support one or more input devices (1130), such as a touch screen (1132), a microphone (1134), a camera (1136), a physical keyboard (1138) and / or a trackball (1140), and one or more output devices (1150), such as a speaker (1152) and a display (1154). A touch screen, such as a touch screen (1132), may detect input in different ways. For example, a capacitive touch screen detects touch input when an object (e.g., a fingertip) distorts or blocks the current passing across the surface. As another example, the touch screen may use an optical sensor to detect touch input when a beam from the optical sensor is blocked. Physical contact with the surface of the screen is not required for input to be detected by some touch screens. For example, the touchscreen (1132) may support finger hover detection using capacitive sensing, as is well understood in the industry. Other detection techniques may be used, including but not limited to camera-based detection and ultrasonic-based detection. To implement a finger hover, the user's finger is typically within a predetermined distance of spaced apart on the touchscreen, for example, between 0.1 and 0.25 inches, or between 0.25 inches and 0.05 inches, or between 0.5 inches and 0.75 inches, or between 0.75 inches and 1 inch, or between 1 inch and 1.5 inches, etc.
[0109] A mobile device (1100) may include a registration system (1192). The registration system (1192) is configured to register user device(s) to a cloud-based management system according to any one or more of the techniques described in this document.
[0110] Other possible output devices (not shown) may include piezoelectric or other haptic output devices. Some devices may provide more than one input / output function. For example, a touch screen (1132) and a display (1154) may be combined within a single input / output device. The input device (1130) may include a Natural User Interface (NUI). An NUI is any interface technology that enables a user to interact with the device in a "natural" manner without artificial constraints imposed by input devices such as a mouse, keyboard, remote control, and similar ones. Examples of NUI methods include speech recognition, touch and stylus recognition, gesture recognition on and adjacent to the screen, air gestures, head and eye tracking, and reliance on speech and speech, vision, touch, gestures, and machine intelligence. Other examples of NUI include motion gesture detection using accelerometers / gyroscopes, facial recognition, 3D displays, head, eye, and gaze tracking, immersive augmented reality and virtual reality systems (all of which provide a more natural interface), and technologies for detecting brain activity using electric field sensing electrodes (EEG and related methods).Therefore, in one specific example, the operating system (1112) or application (1114) may include speech recognition software as part of a voice control interface that enables a user to operate the mobile device (1100) via voice commands. Furthermore, the mobile device (1100) may include software that enables user interaction through the user's spatial gestures, such as detecting and interpreting gestures to provide input to a gaming application, and an input device.
[0111] As is well understood in the industry, wireless modem(s) (1160) may be coupled to antenna(s) (not shown) and may support bidirectional communication between the processor (1110) and an external device. Modem(s) (1160) are generally illustrated and may include a cellular modem (1166) for communicating with a mobile communication network (1104) and / or other wireless-based modems (e.g., Bluetooth® and / or Wi-Fi (1162)). At least one of the wireless modem(s) (1160) is typically configured to communicate with one or more cellular networks, such as a GSM network, for data and voice communication within a single cellular network, between cellular networks, or between a mobile device and a Public Switched Telephone Network (PSTM).
[0112] The mobile device may further include at least one input / output port (1180), a power supply (1182), a satellite navigation system receiver (1184), such as a Global Positioning System (GPS) receiver, an accelerometer (1186), and / or a physical connector (1190) (which may be a USB port, an IEEE 1394 FireWire port, and / or an RS-232 port). As will be recognized by those skilled in the industry, any component may be omitted and other components may be added, so the exemplified components (1102) are not required or all-inclusive.
[0113] While the operations of some of the disclosed methods are described in a specific sequential order for convenience of presentation, it should be understood that this manner of description encompasses rearrangement unless a specific ordering is required by specific wording in this document. For example, operations described sequentially may be rearranged or performed simultaneously in some cases. Furthermore, for the sake of simplicity, the attached drawings may not illustrate the various ways in which the disclosed methods may be used in conjunction with other methods.
[0114] Any one or more of the registration agent (110A-110M), intermediate cloud storage (112), registration system (114), cloud-based management service (116), DDS (118), registration system (714), scan logic (732), trigger logic (734), registration logic (736), registration system (1014), decryption logic (1056), activity diagram (200), activity diagram (300), flowchart (400), flowchart (500), flowchart (600), flowchart (800) and / or flowchart (900) may be implemented in hardware, software, firmware, or any combination thereof.
[0115] For example, any one or more of a registration agent (110A-110M), intermediate cloud storage (112), registration system (114), cloud-based management service (116), DDS (118), registration system (714), scan logic (732), trigger logic (734), registration logic (736), registration system (1014), decryption logic (1056), activity diagram (200), activity diagram (300), flowchart (400), flowchart (500), flowchart (600), flowchart (800) and / or flowchart (900) may be implemented as computer program code configured to be executed within at least one processor, at least partially.
[0116] In other examples, any one or more of the registration agent (110A-110M), intermediate cloud storage (112), registration system (114), cloud-based management service (116), DDS (118), registration system (714), scan logic (732), trigger logic (734), registration logic (736), registration system (1014), decoding logic (1056), activity diagram (200), activity diagram (300), flowchart (400), flowchart (500), flowchart (600), flowchart (800), and / or flowchart (900) may be implemented at least partially as a hardware logic / electrical circuit. Such a hardware logic / electrical circuit may include one or more hardware logic components. Examples of hardware logic components include, but are not limited to, Field-Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application-Specific Standard Products (ASSPs), System-on-a-Chip systems (SoCs), Complex Programmable Logic Devices (CPLDs), etc. For example, an SoC may include an integrated circuit chip comprising one or more of a processor (e.g., a microcontroller, a microprocessor, a Digital Signal Processor (DSP), etc.), memory, one or more communication interfaces, and / or additional circuitry and / or embedded firmware to perform its function.
[0117] III. Further Discussion of Several Exemplary Examples
[0118] A first exemplary system for registering a user device to a cloud-based management system using intermediate cloud storage comprises memory and one or more processors coupled to the memory. One or more processors are configured to analyze a matrix barcode identifying a user device, the matrix barcode comprising a session identifier, a decryption key, and a correlation key. The session identifier identifies a session (during which the user device is registered with the cloud-based management service). The decryption key is configured to be used to decrypt an encrypted data blob to be received from the user device. The correlation key is available to correlate the user device to a record associated with the user device. One or more processors are also configured to trigger the intermediate cloud storage to decrypt an encrypted data blob containing information identifying the user device using the decryption key to provide the decrypted data blob by providing the session identifier, the decryption key, and the correlation key to the intermediate cloud storage. One or more processors are also configured to register the user device to the cloud-based management service using the decrypted data blob received from the intermediate cloud storage.
[0119] In a first aspect of the first exemplary system, one or more processors are configured to authenticate the first exemplary system to intermediate cloud storage using a session identifier. According to the first aspect, one or more processors are configured to provide the intermediate cloud storage with a hash of a correlation key. According also to the first aspect, one or more processors are configured to provide a request to the intermediate cloud storage. The request includes a session identifier, a decryption key, and a correlation key. The request asks the intermediate cloud storage to use the decryption key included in the request to decrypt an encrypted data blob. According also to the first aspect, one or more processors are configured to cause the intermediate cloud storage to verify that the session identifier used to authenticate the first exemplary system to the intermediate cloud storage and the session identifier included in the request are identical. According also to the first aspect, one or more processors are configured to cause the intermediate cloud storage to verify that the correlation key on which the hash of the correlation key is based and the correlation key included in the request are identical.
[0120] In the second aspect of the first exemplary system, the intermediate cloud storage is authenticated to the user device using a session identifier. The second aspect of the first exemplary system may be implemented in combination with the first aspect of the first exemplary system, provided that the exemplary embodiment is not limited to this point.
[0121] In a third aspect of the first exemplary system, one or more processors are configured to analyze a plurality of matrix barcodes that identify a plurality of respective user devices. Each matrix barcode includes a session identifier, a decryption key, and a correlation key. Each session identifier identifies a session (during which the respective user device is registered with a cloud-based management service). Each decryption key is configured to be used to decrypt an encrypted data blob to be received from the respective user device. Each correlation key is available to correlate the respective user device to a record associated with the respective user device. According to the third aspect, one or more processors are configured to trigger an intermediate cloud storage (which receives a plurality of encrypted data blobs containing information identifying the plurality of respective user devices) to decrypt a plurality of encrypted data blobs using their respective decryption keys in order to provide a plurality of respective decrypted data blobs by providing the respective session identifier, the respective decryption key, and the respective correlation key to the intermediate cloud storage. According to a third aspect, one or more processors are configured to register multiple user devices to a cloud-based management service using multiple respective decoded data blobs received from intermediate cloud storage. The third aspect of the first exemplary system may be implemented in combination with the first and / or second aspects of the first exemplary system, provided that the exemplary embodiment is not limited to this point.
[0122] In the implementation of the third aspect of the first exemplary system, one or more processors are configured to sign in the first exemplary system to a tenant of a cloud-based management service. According to this implementation, one or more processors are configured to perform batch calls into the Application Programming Interface (API) of the cloud-based management service. According to this implementation, one or more processors are also configured to pass multiple serial numbers and correlation keys of multiple user devices to the API, wherein multiple serial numbers are contained in multiple decrypted data blobs.
[0123] In a fourth aspect of the first exemplary system, one or more processors are configured to provide a session identifier to intermediate cloud storage so that the intermediate cloud storage can use the session identifier to determine the location of an encrypted data blob. The fourth aspect of the first exemplary system may be implemented in combination with the first, second, and / or third aspects of the first exemplary system, provided that the exemplary embodiment is not limited to this point.
[0124] In the fifth aspect of the first exemplary system, one or more processors are configured to initiate configuring the user device as a configuration policy by triggering the provision to the user device of a deployment platform profile identifier on which the decrypted data blob is based and which identifies the policy. The fifth aspect of the first exemplary system may be implemented in combination with the first, second, third, and / or fourth aspects of the first exemplary system, provided, however, that the exemplary embodiment is not limited to this point.
[0125] In the sixth aspect of the first exemplary system, one or more processors are configured to sign in the first exemplary system to a tenant of a cloud-based management service. According to the sixth aspect, one or more processors are configured to call an Application Programming Interface (API) of the cloud-based management service. Also according to the sixth aspect, one or more processors are configured to pass a serial number of a user device and a correlation key to the API, wherein the serial number of the user device is included in a decrypted data blob. The sixth aspect of the first exemplary system may be implemented in combination with the first, second, third, fourth, and / or fifth aspects of the first exemplary system, provided that the exemplary embodiment is not limited to this point.
[0126] In the seventh aspect of the first exemplary system, one or more processors are also configured to pre-authorize the user device to upload an encrypted data blob to intermediate cloud storage before the user device uploads the encrypted data blob to intermediate cloud storage, based at least partially on the reception of a matrix barcode from the user device. The seventh aspect of the first exemplary system may be implemented in combination with the first, second, third, fourth, fifth, and / or sixth aspects of the first exemplary system, provided that the exemplary embodiments are not limited to this point.
[0127] A second exemplary system for registering a user device to a cloud-based management system using intermediate cloud storage includes memory and one or more processors coupled to the memory. One or more processors are configured to analyze a matrix barcode that identifies the user device. The matrix barcode includes a session identifier, a decryption key, and a correlation key. The session identifier identifies a session (during which the user device is registered with the cloud-based management service). The decryption key is configured to be used to decrypt an encrypted data blob to be received from the user device. The correlation key is available to correlate the user device to a record associated with the user device. One or more processors are also configured to retrieve an encrypted data blob containing information identifying the user device from the intermediate cloud storage that receives the encrypted data blob from the user device. One or more processors are also configured to decrypt the encrypted data blob retrieved from the intermediate cloud storage using the decryption key contained in the matrix barcode to provide a decrypted data blob. One or more processors are also configured to register the user device to the cloud-based management service using the decrypted data blob.
[0128] In the first aspect of the second exemplary system, one or more processors are also configured to authenticate the second exemplary system to intermediate cloud storage using a session identifier.
[0129] In the second aspect of the second exemplary system, the intermediate cloud storage is authenticated to the user device using a session identifier. The second aspect of the second exemplary system may be implemented in combination with the first aspect of the second exemplary system, provided that the exemplary embodiment is not limited to this point.
[0130] In a third aspect of the second exemplary system, one or more processors are configured to analyze a plurality of matrix barcodes that identify a plurality of respective user devices. Each matrix barcode includes a session identifier, a decryption key, and a correlation key. Each session identifier identifies a session (during which the respective user device is registered with a cloud-based management service). Each decryption key is configured to be used to decrypt an encrypted data blob to be received from the respective user device. Each correlation key is available to correlate the respective user device to a record associated with the respective user device. According to the third aspect, one or more processors are configured to retrieve a plurality of encrypted data blobs containing information identifying a plurality of respective user devices from an intermediate cloud storage that receives a plurality of encrypted data blobs from the plurality of respective user devices. According to the third aspect, one or more processors are configured to decrypt the plurality of encrypted data blobs retrieved from the intermediate cloud storage using their respective decryption keys included in the plurality of respective matrix barcodes to provide a plurality of respective decrypted data blobs. According to a third aspect, one or more processors are configured to register multiple user devices to a cloud-based management service using multiple respective decoded data blobs. The third aspect of the second exemplary system may be implemented in combination with the first and / or second aspects of the second exemplary system, provided that the exemplary embodiments are not limited to this point.
[0131] In the implementation of the third aspect of the second exemplary system, one or more processors are configured to sign in the second exemplary system as a tenant of a cloud-based management service. According to this implementation, one or more processors are configured to perform batch calls into the Application Programming Interface (API) of the cloud-based management service. According to this implementation, one or more processors are also configured to pass multiple serial numbers and correlation keys of multiple respective user devices to the API, wherein multiple decrypted data blobs contain multiple respective serial numbers.
[0132] In a fourth aspect of the second exemplary system, one or more processors are configured to provide a session identifier to intermediate cloud storage so that the intermediate cloud storage can use the session identifier to determine the location of an encrypted data blob. The fourth aspect of the second exemplary system may be implemented in combination with the first, second, and / or third aspects of the second exemplary system, provided that the exemplary embodiments are not limited to this point.
[0133] In the fifth aspect of the second exemplary system, one or more processors are configured to initiate configuring the user device as a configuration policy by triggering the provision of to the user device a deployment platform profile identifier on which the decrypted data blob is based and which identifies the policy. The fifth aspect of the second exemplary system may be implemented in combination with the first, second, third, and / or fourth aspects of the second exemplary system, provided, however, that the exemplary embodiment is not limited to this point.
[0134] In the sixth aspect of the second exemplary system, one or more processors are configured to sign in the second exemplary system to a tenant of a cloud-based management service. According to the sixth aspect, one or more processors are configured to call an Application Programming Interface (API) of the cloud-based management service. Also according to the sixth aspect, one or more processors are configured to pass a serial number of a user device and a correlation key to the API, wherein the serial number of the user device is included in a decrypted data blob. The sixth aspect of the second exemplary system may be implemented in combination with the first, second, third, fourth, and / or fifth aspects of the second exemplary system, provided that the exemplary embodiment is not limited to this point.
[0135] In the seventh aspect of the second exemplary system, one or more processors are also configured to pre-authorize the user device to upload an encrypted data blob to intermediate cloud storage before the user device uploads the encrypted data blob to intermediate cloud storage, based at least partially on the reception of a matrix barcode from the user device. The seventh aspect of the second exemplary system may be implemented in combination with the first, second, third, fourth, fifth, and / or sixth aspects of the second exemplary system, provided that the exemplary embodiments are not limited to this point.
[0136] In a first exemplary method for registering a user device to a cloud-based management system using intermediate cloud storage, a matrix barcode identifying the user device is scanned. The matrix barcode includes a session identifier, a decryption key, and a correlation key. The session identifier identifies a session (during which the user device is registered with the cloud-based management service). The decryption key is configured to be used to decrypt an encrypted data blob to be received from the user device. The correlation key is available to correlate the user device to a record associated with the user device. By providing the session identifier, the decryption key, and the correlation key to the intermediate cloud storage, the intermediate cloud storage is triggered to decrypt an encrypted data blob containing information identifying the user device using the decryption key to provide the decrypted data blob. The decrypted data blob is received from the intermediate cloud storage. The user device is registered with the cloud-based management service using the decrypted data blob.
[0137] In the first aspect of the first exemplary method, a registration system scanning a matrix barcode is authenticated to intermediate cloud storage using a session identifier. According to the first aspect, a hash of a correlation key is provided to the intermediate cloud storage. According to the first aspect also, triggering the intermediate cloud storage to decrypt an encrypted data blob includes providing a request to the intermediate cloud storage. The request includes a session identifier, a decryption key, and a correlation key. The request requests that the intermediate cloud storage use the decryption key included in the request to decrypt the encrypted data blob. According to the first aspect also, triggering the intermediate cloud storage to decrypt an encrypted data blob includes causing the intermediate cloud storage to verify that the session identifier used to authenticate the registration system scanning the matrix barcode to the intermediate cloud storage is the same as the session identifier included in the request. According to the first aspect also, triggering the intermediate cloud storage to decrypt an encrypted data blob includes causing the intermediate cloud storage to verify that the correlation key on which the hash of the correlation key is based is the same as the correlation key included in the request.
[0138] In the second aspect of the first exemplary method, the intermediate cloud storage is authenticated to the user device using a session identifier. The second aspect of the first exemplary method may be implemented in combination with the first aspect of the first exemplary method, provided that the exemplary embodiments are not limited to this point.
[0139] In a third aspect of the first exemplary method, scanning a matrix barcode comprises scanning a plurality of matrix barcodes that identify a plurality of respective user devices. Each matrix barcode includes a session identifier, a decryption key, and a correlation key. Each session identifier identifies a session (during which each user device is registered with a cloud-based management service). Each decryption key is configured to be used to decrypt an encrypted data blob to be received from each user device. Each correlation key is available to correlate each user device to a record associated with each user device. According to the third aspect, triggering an intermediate cloud storage (which receives a plurality of encrypted data blobs containing information identifying a plurality of respective user devices from a plurality of respective user devices) triggers the intermediate cloud storage to decrypt a plurality of encrypted data blobs using their respective decryption keys to provide a plurality of respective decrypted data blobs by providing the intermediate cloud storage with their respective session identifiers, their respective decryption keys, and their respective correlation keys. According to a third aspect, receiving a decrypted data blob includes receiving a plurality of decrypted data blobs from an intermediate cloud storage. According to a third aspect, registering user devices includes registering a plurality of user devices to a cloud-based management service using a plurality of their respective decrypted data blobs. A third aspect of the first exemplary method may be implemented in combination with a first and / or second aspect of the first exemplary method, provided that the exemplary embodiment is not limited to this point.
[0140] In the implementation of the first aspect of the first exemplary method, the first exemplary method further comprises a registration system scanning a plurality of matrix barcodes to sign in to a tenant of a cloud-based management service. According to this implementation, a plurality of decrypted data blobs include a plurality of respective serial numbers of a plurality of respective user devices. According to this implementation also, registering a plurality of user devices to a cloud-based management service comprises performing a batch call into an Application Programming Interface (API) of the cloud-based management service. According to this implementation also, registering a plurality of user devices to a cloud-based management service comprises transmitting the serial numbers and correlation keys of each user device to the API.
[0141] In the fourth aspect of the first exemplary method, triggering the intermediate cloud storage to decrypt the encrypted data blob includes providing the intermediate cloud storage with a session identifier, thereby enabling the intermediate cloud storage to determine the location of the encrypted data blob using the session identifier. The fourth aspect of the first exemplary method may be implemented in combination with the first, second, and / or third aspects of the first exemplary method, provided that the exemplary embodiments are not limited to this point.
[0142] In the fifth aspect of the first exemplary method, registering the user device includes initiating to configure the user device as a configuration policy by triggering to provide the user device with a deployment platform profile identifier on which the decrypted data blob is based and which identifies the policy. The fifth aspect of the first exemplary method may be implemented in combination with the first, second, third, and / or fourth aspects of the first exemplary method, provided that the exemplary embodiments are not limited to this point.
[0143] In the sixth aspect of the first exemplary method, the first exemplary method further comprises a registration system scanning a matrix barcode to sign in to a tenant of a cloud-based management service. According to the sixth aspect, the decrypted data blob includes the serial number of the user device. According to the sixth aspect also, registering the user device with the cloud-based management service includes calling an Application Programming Interface (API) of the cloud-based management service. According to the sixth aspect also, registering the user device with the cloud-based management service includes passing the serial number of the user device and the correlation key to the API. The sixth aspect of the first exemplary method may be implemented in combination with the first, second, third, fourth, and / or fifth aspects of the first exemplary method, provided that the exemplary embodiments are not limited to this point.
[0144] In a seventh aspect of the first exemplary method, the first exemplary method further comprises pre-authorizing the user device to upload an encrypted data blob to intermediate cloud storage before the user device uploads the encrypted data blob to intermediate cloud storage, based at least partially on the reception of a matrix barcode from the user device. The seventh aspect of the first exemplary method may be implemented in combination with the first, second, third, fourth, fifth, and / or sixth aspects of the first exemplary method, provided that the exemplary embodiments are not limited to this point.
[0145] In a second exemplary method for registering a user device to a cloud-based management system using intermediate cloud storage, a matrix barcode identifying the user device is scanned. The matrix barcode includes a session identifier, a decryption key, and a correlation key. The session identifier identifies a session (during which the user device is registered with the cloud-based management service). The decryption key is configured to be used to decrypt an encrypted data blob to be received from the user device. The correlation key is available to correlate the user device to a record associated with the user device. An encrypted data blob containing information identifying the user device is retrieved from the intermediate cloud storage receiving the encrypted data blob from the user device. The encrypted data blob retrieved from the intermediate cloud storage is decrypted using the decryption key included in the matrix barcode to provide a decrypted data blob. The user device is registered with the cloud-based management service using the decrypted data blob.
[0146] In the first aspect of the second exemplary method, the second exemplary method further includes authenticating a registration system that scans a matrix barcode to intermediate cloud storage using a session identifier.
[0147] In the second aspect of the second exemplary method, the intermediate cloud storage is authenticated to the user device using a session identifier. The second aspect of the second exemplary method may be implemented in combination with the first aspect of the second exemplary method, provided that the exemplary embodiment is not limited to this point.
[0148] In a third aspect of the second exemplary method, scanning a matrix barcode involves scanning a plurality of matrix barcodes that identify a plurality of respective user devices. Each matrix barcode includes a session identifier, a decryption key, and a correlation key. Each session identifier identifies a session (during which each user device is registered with a cloud-based management service). Each decryption key is configured to be used to decrypt an encrypted data blob to be received from each user device. Each correlation key is available to correlate each user device to a record associated with each user device. According to the third aspect, retrieving an encrypted data blob involves retrieving a plurality of encrypted data blobs containing information identifying a plurality of respective user devices from an intermediate cloud storage that receives a plurality of encrypted data blobs from a plurality of respective user devices. According to the third aspect, decrypting an encrypted data blob involves decrypting a plurality of encrypted data blobs retrieved from the intermediate cloud storage using a respective decryption key included in a plurality of respective matrix barcodes to provide a plurality of respective decrypted data blobs. According to a third aspect, registering user devices also includes registering multiple user devices to a cloud-based management service using multiple respective decrypted data blobs. The third aspect of the second exemplary method may be implemented in combination with the first and / or second aspects of the second exemplary method, provided that the exemplary embodiments are not limited to this point.
[0149] In the implementation of the first aspect of the second exemplary method, the second exemplary method further comprises a registration system scanning a plurality of matrix barcodes to sign in to a tenant of a cloud-based management service. According to this implementation, a plurality of decrypted data blobs include a plurality of respective serial numbers of a plurality of respective user devices. According to this implementation also, registering a plurality of user devices to a cloud-based management service comprises performing a batch call into an Application Programming Interface (API) of the cloud-based management service. According to this implementation also, registering a plurality of user devices to a cloud-based management service comprises transmitting the serial numbers and correlation keys of each user device to the API.
[0150] In the fourth aspect of the second exemplary method, retrieving an encrypted data blob from intermediate cloud storage includes providing a session identifier to the intermediate cloud storage, thereby enabling the intermediate cloud storage to determine the location of the encrypted data blob using the session identifier. The fourth aspect of the second exemplary method may be implemented in combination with the first, second, and / or third aspects of the second exemplary method, provided that the exemplary embodiments are not limited to this point.
[0151] In the fifth aspect of the second exemplary method, registering the user device includes initiating to configure the user device as a configuration policy by triggering to provide the user device with a deployment platform profile identifier that identifies the policy on which the decrypted data blob is based. The fifth aspect of the second exemplary method may be implemented in combination with the first, second, third, and / or fourth aspects of the second exemplary method, provided that the exemplary embodiments are not limited to this point.
[0152] In the sixth aspect of the second exemplary method, the second exemplary method further comprises signing in a registration system that scans a matrix barcode to a tenant of a cloud-based management service. According to the sixth aspect, the decrypted data blob includes the serial number of the user device. According to the sixth aspect also, registering the user device to the cloud-based management service includes calling an Application Programming Interface (API) of the cloud-based management service. According to the sixth aspect also, registering the user device to the cloud-based management service includes passing the serial number of the user device and the correlation key to the API. The sixth aspect of the second exemplary method may be implemented in combination with the first, second, third, fourth, and / or fifth aspects of the second exemplary method, provided that the exemplary embodiments are not limited to this point.
[0153] In a seventh aspect of the second exemplary method, the second exemplary method further comprises pre-authorizing the user device to upload an encrypted data blob to intermediate cloud storage before the user device uploads the encrypted data blob to intermediate cloud storage, based at least partially on the reception of a matrix barcode from the user device. The seventh aspect of the second exemplary method may be implemented in combination with the first, second, third, fourth, fifth, and / or sixth aspects of the second exemplary method, provided that the exemplary embodiments are not limited to this point.
[0154] The first exemplary computer program product comprises a computer-readable storage medium having instructions recorded thereon that enable a processor-based system to register a user device to a cloud-based management system using intermediate cloud storage by performing an operation. The operation includes analyzing a matrix barcode that identifies the user device. The matrix barcode includes a session identifier, a decryption key, and a correlation key. The session identifier identifies a session (during which the user device is registered with the cloud-based management service). The decryption key is configured to be used to decrypt an encrypted data blob to be received from the user device. The correlation key is available to correlate the user device to a record associated with the user device. The operation further includes triggering the intermediate cloud storage to decrypt an encrypted data blob containing information identifying the user device using the decryption key to provide the decrypted data blob by providing the session identifier, the decryption key, and the correlation key to the intermediate cloud storage. The operation further includes registering the user device to the cloud-based management service using the decrypted data blob received from the intermediate cloud storage.
[0155] The second exemplary computer program product comprises a computer-readable storage medium having instructions recorded thereon that enable a processor-based system to register a user device to a cloud-based management system using intermediate cloud storage by performing an operation. The operation includes analyzing a matrix barcode that identifies the user device. The matrix barcode includes a session identifier, a decryption key, and a correlation key. The session identifier identifies a session (during which the user device is registered with the cloud-based management service). The decryption key is configured to be used to decrypt an encrypted data blob to be received from the user device. The correlation key is available to correlate the user device to a record associated with the user device. The operation further includes retrieving an encrypted data blob containing information identifying the user device from the intermediate cloud storage that receives the encrypted data blob from the user device. The operation further includes decrypting the encrypted data blob retrieved from the intermediate cloud storage using the decryption key contained in the matrix barcode to provide a decrypted data blob. The operation further includes registering the user device to the cloud-based management service using the decrypted data blob.
[0156] IV. Exemplary Computer Systems
[0157] FIG. 12 depicts an exemplary computer (1200) in which an embodiment may be implemented. Any one or more of the user devices (102A-102M) shown in FIG. 1, any one or more of the servers (106A-106N) and / or a management system (108); The management system (700) illustrated in FIG. 7; and / or the management system (1000) illustrated in FIG. 10 may be implemented using the computer (1200), including one or more features of the computer (1200) and / or alternative features. The computer (1200) may be a general-purpose computing device in the form of, for example, a conventional personal computer, a mobile computer, or a workstation, or the computer (1200) may be a special-purpose computing device. The description of the computer (1200) provided herein is provided for illustrative purposes only and is not intended to be limiting. Embodiments may be implemented in additional types of computer systems as would be known to those skilled in the relevant industry(s).
[0158] As illustrated in FIG. 12, the computer (1200) includes a processing unit (1202), system memory (1204), and a bus (1206) that couples various system components, including the system memory (1204), to the processing unit (1202). The bus (1206) represents any one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus, using any one of various bus architectures. The system memory (1204) includes Read Only Memory (ROM) (1208) and Random Access Memory (RAM) (1210). A Basic Input / Output System (BIOS) (1212) is stored in the ROM (1208).
[0159] The computer (1200) also has one or more of the following drives: a hard disk drive (1214) for reading from or writing to a hard disk, a magnetic disk drive (1216) for reading from or writing to a removable magnetic disk (1218), and an optical disk drive (1220) for reading from or writing to a removable optical disk (1222), such as a CD ROM, DVD ROM, or other optical media. The hard disk drive (1214), the magnetic disk drive (1216), and the optical disk drive (1220) are each connected to the bus (1206) by a hard disk drive interface (1224), a magnetic disk drive interface (1226), and an optical drive interface (1228). The drive and its associated computer-readable storage media provide nonvolatile storage of computer-readable instructions, data structures, program modules, and other data for the computer. Hard disks, removable magnetic disks, and removable optical disks are described, but other types of computer-readable storage media such as flash memory cards, digital video discs, random access memory (RAM), read-only memory (ROM), and similar ones may be used to store data.
[0160] A number of program modules may be stored on a hard disk, magnetic disk, optical disk, ROM, or RAM. These programs include an operating system (1230), one or more application programs (1232), other program modules (1234), and program data (1236). The application program (1232) or program module (1234) is, for example, as described in this document, a registration agent (110A-110M), intermediate cloud storage (112), a registration system (114), a cloud-based management service (116), a DDS (118), a registration system (714), a scan logic (732), a trigger logic (734), a registration logic (736), a registration system (1014), a decryption logic (1056), an activity diagram (200) (including any activity of the activity diagram (200)), an activity diagram (300) (including any activity of the activity diagram (300)), a flowchart (400) (including any step of the flowchart (400)), a flowchart (500) (including any step of the flowchart (500)), a flowchart (600) (including any step of the flowchart (600)), It may include computer program logic for implementing any one or more (e.g., at least a part) of flowchart (800) (including any step of flowchart (800)) and / or flowchart (900) (including any step of flowchart (900)).
[0161] The user can input commands and information into the computer (1200) through input devices such as a keyboard (1238) and a pointing device (1240). Other input devices (not shown) may include a microphone, a joystick, a game pad, a satellite dish, a scanner, a touch scanner, a camera, an accelerometer, a gyroscope, or similar. These and other input devices are commonly connected to the processing unit (1202) via a serial port interface (1242) coupled to a bus (1206), but may be connected via other interfaces such as a parallel port, a game port, or a Universal Serial Bus (USB).
[0162] A display device (1244) (e.g., a monitor) is also connected to the bus (1206) via an interface such as a video adapter (1246). In addition to the display device (1244), the computer (1200) may include other peripheral output devices (not shown), such as speakers and a printer.
[0163] The computer (1200) is connected to a network (1248) (e.g., the Internet) through a network interface or adapter (1250), a modem (1252), or other means for establishing communication through the network. The modem (1252), which may be internal or external, is connected to a bus (1206) through a serial port interface (1242).
[0164] As used in this document, the terms "computer program medium" and "computer-readable storage medium" are generally used to refer to media (e.g., non-transitory media) such as hard disks associated with hard disk drives (1214), removable magnetic disks (1218), and removable optical disks (1222), as well as other media such as flash memory cards, digital video discs, Random Access Memory (RAM), Read Only Memory (ROM), and similar ones. A computer-readable storage medium is not a signal such as a carrier signal or a propagating signal. For example, a computer-readable storage medium may not contain a signal. Therefore, a computer-readable storage medium is a signal The itself It does not constitute. Computer-readable storage media are distinct from and non-overlapping with communication media (not including communication media). Communication media embody computer-readable instructions, data structures, program modules, or other data within a modulated data signal, such as a carrier wave. The term “modulated data signal” means a signal in which one or more of its characteristics are set or altered in such a manner that the information within the signal is encoded. By example, but not by limitation, communication media include wireless media, e.g., acoustic, RF, infrared, and other wireless media, as well as wired media. Exemplary embodiments are also directed toward such communication media.
[0165] As noted above, computer programs and modules (including application programs (1232) and other program modules (1234)) may be stored on a hard disk, magnetic disk, optical disk, ROM, or RAM. Such computer programs may also be received via a network interface (1250) or a serial port interface (1242). Such computer programs, when executed or loaded by an application, enable the computer (1200) to implement the features of the embodiments discussed in this document. Thus, such computer programs represent a controller of the computer (1200).
[0166] Exemplary embodiments also relate to computer program products comprising software (e.g., computer-readable instructions) stored on any computer-readable medium. When such software is executed within one or more data processing devices, it causes the data processing device(s) to operate as described in this document. Embodiments may utilize any computer-readable or computer-readable medium known now or in the future. Examples of computer-readable media include, but are not limited to, storage devices such as RAM, hard drives, floppy disks, CD-ROMs, DVD-ROMs, zip disks, tapes, magnetic storage devices, optical storage devices, MEMS-based storage devices, nanotechnology-based storage devices, and similar devices.
[0167] It will be recognized that the disclosed technology is not limited to any particular computer or any particular type of hardware. Certain details of suitable computers and hardware are well known and do not need to be set forth in detail in this disclosure.
[0168] V. Conclusion
[0169] Although the subject matter has been described in terms specific to structural features and / or acts, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as examples of implementing the claims, and other equivalent features and acts are intended to be within the scope of the claims.
Claims
Claim 1 A method for registering a user device to a cloud-based management system using intermediate cloud storage, comprising: a step of analyzing a matrix barcode identifying the user device, wherein the matrix barcode includes a decryption key and a correlation key, wherein the decryption key is configured to decrypt an encrypted data blob from the user device and the correlation key is configured to correlate the user device to a record associated with the user device; a step of triggering the intermediate cloud storage to decrypt the encrypted data blob received from the user device, which includes information identifying the user device, by using the decryption key to provide a decrypted data blob, by providing the decryption key and the correlation key to the intermediate cloud storage; and a step of registering the user device to a cloud-based management service using the decrypted data blob received from the intermediate cloud storage. Claim 2 The method of claim 1 further comprises the step of pre-authorizing the user device to upload the encrypted data blob to the intermediate cloud storage before the user device uploads the encrypted data blob to the intermediate cloud storage, based at least partially on the reception of the matrix barcode from the user device. Claim 3 A method according to claim 1, further comprising the step of providing the hash of the correlation key to the intermediate cloud storage, wherein the step of triggering the intermediate cloud storage to decrypt the encrypted data blob comprises: the step of providing a request to the intermediate cloud storage—the request comprising the decryption key and the correlation key, and the request requesting the intermediate cloud storage to use the decryption key included in the request to decrypt the encrypted data blob—and the step of causing the intermediate cloud storage to verify that the correlation key on which the hash of the correlation key is based is the same as the correlation key included in the request. Claim 4 In claim 1, the step of analyzing the matrix barcode includes the step of analyzing a plurality of matrix barcodes that identify a plurality of user devices, wherein each matrix barcode includes a decryption key and a correlation key, wherein each decryption key is configured to decrypt an encrypted data blob from each user device, and each correlation key is configured to correlate each user device to a record associated with each user device, and the step of triggering the intermediate cloud storage includes the step of triggering the intermediate cloud storage, which receives a plurality of encrypted data blobs including information identifying each user device from each user device, to decrypt the plurality of encrypted data blobs using each decryption key to provide each decrypted data blobs, by providing each decryption key and each correlation key to the intermediate cloud storage, and receiving the decrypted data blobs includes registering each user device to the cloud-based management service using each decrypted data blob. Claim 5 A method according to claim 4, further comprising the step of signing a registration system that analyzes the plurality of matrix barcodes to a tenant of the cloud-based management service, wherein each of the plurality of decrypted data blobs includes each of the plurality of serial numbers of each of the plurality of user devices, and registering each of the plurality of user devices to the cloud-based management service comprises performing a batch call to an application programming interface (API) of the cloud-based management service and transmitting the serial number of each of the user devices and the correlation key to the API. Claim 6 The method of claim 1, wherein the step of registering the user device includes the step of initiating the configuration of the user device as a configuration policy by triggering the provision of a deployment platform profile identifier to the user device, wherein the deployment platform profile identifier is based on the decrypted data blob and identifies the policy. Claim 7 A method according to claim 1, further comprising the step of signing a registration system that analyzes the matrix barcode to a tenant of the cloud-based management service, wherein the decrypted data blob includes a serial number of the user device, and the step of registering the user device to the cloud-based management service comprises the step of calling an application programming interface (API) of the cloud-based management service and the step of transmitting the serial number of the user device and the correlation key to the API. Claim 8 A system for registering a user device to a cloud-based management system using intermediate cloud storage, comprising a memory and one or more processors coupled to the memory, wherein the one or more processors are configured to perform: analyzing a matrix barcode identifying the user device—the matrix barcode includes a decryption key and a correlation key, wherein the decryption key is configured to decrypt an encrypted data blob from the user device and the correlation key is configured to correlate the user device to a record associated with the user device—; and, from the intermediate cloud storage receiving the encrypted data blob from the user device, retrieving the encrypted data blob containing information identifying the user device; decrypting the encrypted data blob retrieved from the intermediate cloud storage using the decryption key included in the matrix barcode to provide the decrypted data blob; and registering the user device to a cloud-based management service using the decrypted data blob. Claim 9 A system according to claim 8, wherein the one or more processors are also configured to pre-authorize the user device to upload the encrypted data blob to the intermediate cloud storage before the user device uploads the encrypted data blob to the intermediate cloud storage, based at least partially on the reception of the matrix barcode from the user device. Claim 10 A system configured such that, in claim 8, the one or more processors perform the following: analyzing a plurality of matrix barcodes identifying a plurality of respective user devices—each matrix barcode including a decryption key and a correlation key, each decryption key configured to decrypt an encrypted data blob from the respective user device, and each correlation key configured to correlate the respective user device to a record associated with the respective user device; retrieving the plurality of encrypted data blobs containing information identifying the plurality of respective user devices from the intermediate cloud storage receiving the plurality of encrypted data blobs from the plurality of respective user devices; decrypting the plurality of encrypted data blobs retrieved from the intermediate cloud storage using the respective decryption key included in the plurality of respective matrix barcodes to provide the plurality of respective decrypted data blobs; and registering the plurality of respective user devices to the cloud-based management service using the plurality of respective decrypted data blobs. Claim 11 In claim 10, the system is configured such that one or more processors perform the following: signing the system to a tenant of the cloud-based management service; performing a batch call to an application programming interface (API) of the cloud-based management service; and transmitting to the API a plurality of respective serial numbers of the plurality of respective user devices and the correlation key, wherein the plurality of respective decrypted data blobs include the plurality of respective serial numbers. Claim 12 In claim 8, the one or more processors are configured to initiate the configuration of the user device as a configuration policy by triggering the provision of a deployment platform profile identifier to the user device, wherein the deployment platform profile identifier is based on the decoded data blob and identifies the policy. Claim 13 In claim 8, the system is configured such that one or more processors perform the following: sign the system to a tenant of the cloud-based management service; call an application programming interface (API) of the cloud-based management service; and transmit the serial number of the user device and the correlation key to the API, wherein the serial number of the user device is included in the decrypted data blob. Claim 14 A method for registering a user device to a cloud-based management system using intermediate cloud storage, comprising: a step of analyzing a matrix barcode identifying the user device, wherein the matrix barcode includes a session identifier and a decryption key, wherein the session identifier identifies a session in which the user device is registered to a cloud-based management service, and the decryption key is configured to decrypt an encrypted data blob from the user device; a step of retrieving the encrypted data blob containing information identifying the user device from the intermediate cloud storage that receives the encrypted data blob from the user device; a step of decrypting the encrypted data blob retrieved from the intermediate cloud storage using the decryption key included in the matrix barcode to provide the decrypted data blob; and a step of registering the user device to the cloud-based management service using the decrypted data blob. Claim 15 A method according to claim 14, further comprising the step of pre-authorizing the user device to upload the encrypted data blob to the intermediate cloud storage before the user device uploads the encrypted data blob to the intermediate cloud storage, based at least partially on the reception of the matrix barcode from the user device. Claim 16 A method according to claim 14, further comprising the step of authenticating a registration system that analyzes the matrix barcode in the intermediate cloud storage using the session identifier. Claim 17 In paragraph 14, the method wherein the intermediate cloud storage is authenticated to the user device using the session identifier. Claim 18 In claim 14, the step of analyzing the matrix barcode includes the step of analyzing a plurality of matrix barcodes that identify a plurality of user devices, each matrix barcode includes a session identifier and a decryption key, each session identifier identifies a session in which the respective user device is registered to the cloud-based management service, and each decryption key is configured to decrypt an encrypted data blob from the respective user device, the step of retrieving the encrypted data blob includes the step of retrieving the plurality of encrypted data blobs containing information identifying the respective user devices from the intermediate cloud storage that receives the plurality of encrypted data blobs from the plurality of user devices, the step of decrypting the plurality of encrypted data blobs retrieved from the intermediate cloud storage using the respective decryption key included in the plurality of matrix barcodes to provide the respective decrypted data blobs, and the step of registering the user device includes the step of registering the plurality of user devices to the cloud-based management service using the respective decrypted data blobs. Claim 19 In claim 14, the step of withdrawing the encrypted data blob from the intermediate cloud storage comprises the step of providing the session identifier to the intermediate cloud storage so that the intermediate cloud storage can determine the location of the encrypted data blob using the session identifier. Claim 20 In claim 14, the step of registering the user device comprises the step of initiating the configuration of the user device as a configuration policy by triggering the provision of a deployment platform profile identifier to the user device, wherein the deployment platform profile identifier is based on the decrypted data blob and identifies the policy.
Citation Information
Patent Citations
Identity authentication using barcode
JP2018186495A
Method and system for network-enabled account creation using optical detection
JP2020501443A
Offline user identification
KR1020190071752A
Cloud-based transactions methods and systems
US10402814B2
Simplified association of devices with a network using unique codes on the devices and side channel communication
US10547613B1
