IP Library Granted Patent US 9,063,963
Granted Patent B2
US 9,063,963 · App. 12/984,047 · Granted Jun 23, 2015

Method and system for migration of managed devices

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 9,063,963
App. No.
12/984,047
Granted
Jun 23, 2015
Kind
B2
Abstract

A system and method for migrating a managed subscriber device from an incumbent managing server to a new managing server. Registration data for the subscriber device and authentication certificates are transferred to the new managing server or an associated memory device, and a DNS name and IP address mapping request is transmitted to a DNS server. When the name change is implemented, a DNS lookup for the managing server performed by the subscriber device returns an IP address associated with the new managing server. The new managing server may then assume the management functions with respect to the subscriber device. The migration may be performed for a number of subscriber devices simultaneously.

Claims (32)

1. A method for migrating a managed subscriber device from an incumbent managing server to a new managing server, comprising:

transferring registration data related to the subscriber device from a database associated with the incumbent managing server to a database associated with the new managing server, wherein:

the incumbent and new managing servers monitor the subscriber device to ensure the subscriber device is on-line, available, and operational; and

the registration data includes profile information of a subscriber using the subscriber device and current settings or capabilities of the subscriber device;

transferring the security certificates related to the subscriber device from the incumbent managing server to the new managing server; and

requesting that a DNS server affect a name change such that a subsequent DNS lookup by the subscriber device to determine an address of a managing server will return an address of the new managing server instead of an address of the incumbent managing server, wherein the requesting is not performed by the subscriber device.

2. The method of claim 1 , further comprising receiving in the new managing server a communication from the subscriber device.

3. The method of claim 2 , further comprising responding to the communication from the subscriber device to the new managing server.

4. The method of claim 3 , further comprising management of the subscriber device by the new managing server.

5. A method of migrating at least one subscriber device from an incumbent managing server to a new managing server, comprising:

requesting, by the new managing server, registration data associated with the at least one subscriber device from a database associated with the incumbent managing server;

receiving, at the new managing server, registration data associated with the at least one subscriber device from the database associated with the incumbent managing server;

requesting, by the new managing server, authentication certificates from the incumbent managing server;

receiving, at the new managing server, authentication certificates from the incumbent managing server; and

requesting that a DNS server affect a name change such that a subsequent DNS lookup by the subscriber device to determine an address of a managing server will return an address of the new managing server instead of an address of the incumbent managing server, wherein the requesting is not performed by the subscriber device; and wherein:

the incumbent and new managing servers monitor the subscriber device to ensure the managed subscriber device is on-line, available, and operational; and

the registration data includes profile information of a subscriber using the subscriber device and current settings or capabilities of the subscriber device.

6. The method of claim 5 , further comprising assuming management of the at least one subscriber device by the new managing server.

7. The method of claim 6 , wherein the assumption of the at least one subscriber device management does not occur until a management message is received in the new managing server from the subscriber device.

8. The method of claim 6 , further comprising sending a management message to the at least one subscriber device from the new managing server prior to receiving a communication from the subscriber device.

9. The method of claim 8 , wherein requesting a DNS name change request requesting a DNS name and IP address mapping periodically until an acknowledgement has been received indicated that the name change has been effected.

10. The method of claim 5 , wherein the new managing server is associated with a different database than the incumbent managing server and further comprising storing the registration data in a database associated with the new managing server.

11. The method of claim 5 , wherein the DNS name change request is sent by the new managing server.

12. The method of claim 5 , wherein the at least one subscriber device is a plurality of subscriber devices.

13. The method of claim 12 , wherein the request for registration data comprises a request for registration data associated with each of the plurality of devices.

14. A system for migrating management of at least one subscriber device, comprising,

a new managing server for assuming management of the at least one subscriber device from an incumbent managing server wherein the assumption of management includes at least receiving registration data associated with the at least one subscriber device from a database associated with the incumbent managing server,

a memory device accessible by the new managing server, and

a DNS name and IP address mapping requester comprising software instructions executable on a processor requesting that a DNS server affect a name change such that a subsequent DNS lookup by the at least one subscriber device to determine an address of a managing server will return an address of the new managing server instead of an address of the incumbent managing server wherein the requesting does not involve the subscriber device; and wherein:

the incumbent and new managing servers monitor the subscriber device to ensure the subscriber device is on-line, available, and operational; and

the registration data includes profile information of a subscriber using the subscriber device and current settings or capabilities of the subscriber device.

15. The system of claim 14 , wherein the processor is resident in the managing server.

Assignments (10)
RELEASE OF SECURITY INTEREST Recorded Jun 3, 2021
From: TERRIER SSC, LLC
To: WSOU INVESTMENTS, LLC
Reel/Frame 056526/0093 →
SECURITY INTEREST Recorded Jun 1, 2021
From: WSOU INVESTMENTS, LLC
To: OT WSOU TERRIER HOLDINGS, LLC
Reel/Frame 056990/0081 →
RELEASE OF SECURITY INTEREST Recorded May 21, 2019
From: OCO OPPORTUNITIES MASTER FUND, L.P. (F/K/A OMEGA CREDIT OPPORTUNITIES MASTER FUND LP
To: WSOU INVESTMENTS, LLC
Reel/Frame 049246/0405 →
SECURITY INTEREST Recorded May 20, 2019
From: WSOU INVESTMENTS, LLC
To: BP FUNDING TRUST, SERIES SPL-VI
Reel/Frame 049235/0068 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 25, 2017
From: ALCATEL LUCENT
To: WSOU INVESTMENTS, LLC
Reel/Frame 044000/0053 →
SECURITY INTEREST Recorded Sep 21, 2017
From: WSOU INVESTMENTS, LLC
To: OMEGA CREDIT OPPORTUNITIES MASTER FUND, LP
Reel/Frame 043966/0574 →
RELEASE OF SECURITY INTEREST Recorded Oct 9, 2014
From: CREDIT SUISSE AG
To: ALCATEL-LUCENT USA INC.
Reel/Frame 033949/0016 →
SECURITY INTEREST Recorded Mar 7, 2013
From: ALCATEL-LUCENT USA INC.
To: CREDIT SUISSE AG
Reel/Frame 030510/0627 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 20, 2012
From: ALCATEL-LUCENT USA INC.
To: ALCATEL LUCENT
Reel/Frame 027729/0802 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 4, 2011
From: YANG, JIGANG (ERIC)
To: ALCATEL-LUCENT USA INC.
Reel/Frame 025579/0197 →