IP Library Granted Patent US 10,158,982
Granted Patent B2
US 10,158,982 · App. 15/496,255 · Granted Dec 18, 2018

Message-based management service enrollment

Inventors: Azhar Faiz Samdani (Bangalore, IN); Subhrajit Bhowmik (Bangalore, IN); Anantha Raman B R (Bangalore, IN); Bhyruva S Gangadharaiah (Bangalore, IN)
Assignee: VMWARE, INC.
H04W4/14H04L51/04H04L51/28H04L67/16
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,158,982
App. No.
15/496,255
Granted
Dec 18, 2018
Kind
B2
Abstract

Disclosed are various examples for message-based management service enrollment. In one example, a map is generated that associates an identifier with an enterprise within the map. The identifier identifies a network endpoint of an enrollment service. A message with client data is received from a client device, which sends the message to the enrollment service using the identifier. A username is generated with the client data and a user account is created having the username. Enrollment data is obtained from the management service and an enrollment of the client device is initiated by sending a message with the enrollment data to the client device.

Claims (43)

1. A system, comprising:

at least one computing device; and

an enrollment service executable in the at least one computing device that, when executed, causes the at least one computing device to:

generate a map that associates a first identifier with an enterprise within the map, wherein the first identifier identifies a first network endpoint associated with the enrollment service;

receive a first message transmitted from a client device using the first identifier, the first message including client data comprising a device identifier and a second identifier, wherein the second identifier identifies a second network endpoint associated with the client device;

generate a username using the device identifier and the second identifier;

transmit a request for account creation to a management service, the request for account creation comprising the username, wherein the request for account creation causes the management service to create a user account having the username within a directory associated with the enterprise;

transmit a request for enrollment data to the management service, the request for the enrollment data comprising the username;

receive enrollment data from the management service, the enrollment data comprising an enrollment token that authenticates the client device with the management service; and

transmit a second message to the client device using the second identifier, the second message comprising the enrollment data, wherein the second message initiates an enrollment of the client device with the management service using the enrollment data.

2. The system of claim 1 , wherein the first identifier is a first telephone number, and the first network endpoint is a first telephonic endpoint associated with the enrollment service.

3. The system of claim 1 , wherein the second identifier is a second telephone number, and the second network endpoint is a second telephonic endpoint associated with the client device.

4. The system of claim 1 , wherein the enrollment data comprises a URI that includes the enrollment token.

5. The system of claim 1 , wherein the first message is a first SMS message and the second message is a second SMS message.

6. The system of claim 1 , wherein the first message is a first instant message and the second message is a second instant message.

7. The system of claim 1 , wherein when executed the enrollment service further causes the at least one computing device to transmit the second message to the client device in response to an instant message being unsuccessful, wherein the second message is an SMS message.

8. A computer-implemented method, comprising:

generating, by at least one computing device, a map that associates a first identifier with an enterprise within the map, wherein the first identifier identifies a first network endpoint associated with an enrollment service;

receiving, by the at least one computing device, a first message transmitted from a client device using the first identifier, the first message including client data comprising a device identifier and a second identifier, wherein the second identifier identifies a second network endpoint associated with the client device;

generating, by the at least one computing device, a username using the device identifier and the second identifier;

transmitting, by the at least one computing device, a request for account creation to a management service, the request for account creation comprising the username, wherein the request for account creation causes the management service to create a user account having the username within a directory associated with the enterprise;

transmitting, by the at least one computing device, a request for enrollment data to the management service, the request for the enrollment data comprising the username;

receiving, by the at least one computing device, enrollment data from the management service, the enrollment data comprising an enrollment token that authenticates the client device with the management service; and

transmitting, by the at least one computing device, a second message to the client device using the second identifier, the second message comprising the enrollment data, wherein the second message initiates an enrollment of the client device with the management service using the enrollment data.

9. The computer-implemented method of claim 8 , wherein the first identifier is a first telephone number, and the first network endpoint is a first telephonic endpoint associated with the enrollment service.

10. The computer-implemented method of claim 8 , wherein the second identifier is a second telephone number, and the second network endpoint is a second telephonic endpoint associated with the client device.

11. The computer-implemented method of claim 8 , wherein the enrollment data comprises a URI that includes the enrollment token.

12. The computer-implemented method of claim 8 , wherein the first message is a first SMS message and the second message is a second SMS message.

13. The computer-implemented method of claim 8 , wherein the first message is a first instant message and the second message is a second instant message.

14. The computer-implemented method of claim 8 , further comprising transmitting, by the at least one computing device, the second message to the client device in response to an instant message being unsuccessful, wherein the second message is an SMS message.

15. A non-transitory computer-readable medium embodying an enrollment service executable in at least one computing device that, when executed, causes the at least one computing device to:

generate a map that associates a first identifier with an enterprise within the map, wherein the first identifier identifies a first network endpoint associated with the enrollment service;

receive a first message transmitted from a client device using the first identifier, the first message including client data comprising a device identifier and a second identifier, wherein the second identifier identifies a second network endpoint associated with the client device;

generate a username using the device identifier and the second identifier;

transmit a request for account creation to a management service, the request for account creation comprising the username, wherein the request for account creation causes the management service to create a user account having the username within a directory associated with the enterprise;

transmit a request for enrollment data to the management service, the request for the enrollment data comprising the username;

receive enrollment data from the management service, the enrollment data comprising an enrollment token that authenticates the client device with the management service; and

transmit a second message to the client device using the second identifier, the second message comprising the enrollment data, wherein the second message initiates an enrollment of the client device with the management service using the enrollment data.

16. The non-transitory computer-readable medium of claim 15 , wherein the first identifier is a first telephone number, and the first network endpoint is a first telephonic endpoint associated with the enrollment service.

17. The non-transitory computer-readable medium of claim 15 , wherein the second identifier is a second telephone number, and the second network endpoint is a second telephonic endpoint associated with the client device.

18. The non-transitory computer-readable medium of claim 15 , wherein the enrollment data comprises a URI that includes the enrollment token.

19. The non-transitory computer-readable medium of claim 15 , wherein the first message is a first SMS message and the second message is a second SMS message.

20. The non-transitory computer-readable medium of claim 15 , wherein the first message is a first instant message and the second message is a second instant message.

Assignments (4)
PATENT ASSIGNMENT Recorded Aug 5, 2024
From: VMWARE LLC
To: OMNISSA, LLC
Reel/Frame 068327/0365 →
SECURITY INTEREST Recorded Jul 3, 2024
From: OMNISSA, LLC
To: UBS AG, STAMFORD BRANCH
Reel/Frame 068118/0004 →
CHANGE OF NAME Recorded Apr 15, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067102/0395 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 23, 2018
From: SAMDANI, AZHAR FAIZ; BHOWMIK, SUBHRAJIT; RAMAN B R, ANANTHA; GANGADHARAIAH, BHYRUVA S
To: VMWARE, INC.
Reel/Frame 046676/0808 →
Continuity (1)
Related Publication 20180310142A1 · Oct 25, 2018
Cited By (1)
US 12,489,736