Data migration using SMS simulator

• US 20050075856A1
• Filed: 10/01/2003
• Published: 04/07/2005
• Est. Priority Date: 10/01/2003
• Status: Abandoned Application

• Current Assignee: Sbc Knowledge Ventures, L.P.
• Original Assignee: Sbc Knowledge Ventures, L.P.
• Inventors: Voldman, Mikhail L., Wozniak, Daniel
• Application Number:
  US10/677,133
• Publication Number:
  US 20050075856A1
• Time in Patent Office: Days
• US Class Current: 703/22
• CPC Class Codes: G06F 16/214 Database migration support

Abstract

Migration to a service management system (SMS) is facilitated using an SMS simulator. Each of a plurality of provisioning requests is directed to the SMS simulator rather than the SMS. For each of a plurality of syntactically correct requests, the SMS simulator assigns a provisioning component identifier associated with the request, stores a command associated with the request and its associated provisioning component identifier in a transaction file, and sends a provisioning response based on the request. The requests in the transaction file are replayed to provision the SMS.

Claims

1. A method of migrating to a service management system (SMS), the method comprising:

providing an SMS simulator;

directing each of a plurality of provisioning requests to the SMS simulator instead of the SMS;

for each of a plurality of syntactically correct requests of the provisioning requests, using the SMS simulator to;

assign a provisioning component identifier associated with the request;

store a command associated with the request and its associated provisioning component identifier in a first transaction file; and

send a provisioning response based on the request; and

replaying the requests in the first transaction file to provision the SMS.

2. The method of claim 1 further comprising:

directing subsequent provisioning requests to the SMS instead of to the SMS simulator upon determining that no subsequent provisioning requests are made within a transaction-file-replay time period.

3. The method of claim 1 further comprising:

replacing SMS-simulator-generated provisioning information in a database with provisioning information for the SMS.

4. The method of claim 3 wherein said replacing comprises replacing the SMS-simulator-generated component identifiers in the database with a provisioning component identifier of the SMS.

5. The method of claim 3 wherein said replacing comprises replacing SMS-simulator-generated provisioning time information with provisioning time information for the SMS.

6. The method of claim 3 further comprising:

suppressing provisioning notification to a main billing and provisioning system during said replacing.

7. The method of claim 1 further comprising, while replaying the first transaction file:

directing a subsequent provisioning request to the SMS simulator; and

using the SMS simulator to;

assign a provisioning component identifier associated with the subsequent provisioning request;

store a command associated with the subsequent provisioning request and its associated provisioning component identifier in a second transaction file; and

send a provisioning response based on the subsequent provisioning request.

8. The method of claim 7 further comprising:

replaying the subsequent provisioning request in the second transaction file to provision the SMS.

9. The method of claim 8 wherein said replaying the second transaction file is performed a predetermined time period after said replaying the first transaction file.

10. The method of claim 9 wherein the predetermined time period is about one day.

11. A system for migrating to a service management system (SMS), the system comprising:

an SMS simulator;

a network element to redirect each of a plurality of provisioning requests to the SMS simulator instead of the SMS;

wherein for each of a plurality of requests of the provisioning requests, the SMS simulator is to;

assign a provisioning component identifier associated with the request;

store a command associated with the request and its associated provisioning component identifier in a first transaction file; and

send a provisioning response based on the request; and

a first utility to replay the requests in the first transaction file to provision the SMS.

12. The system of claim 11 wherein the network element is to direct subsequent provisioning requests to the SMS instead of the SMS simulator upon determining that no subsequent provisioning requests are made within a transaction-file-replay time period, and wherein each of the plurality of requests are syntactically correct.

13. The system of claim 11 further comprising a second utility to replace SMS-simulator-generated provisioning information in a database with provisioning information for the SMS.

14. The system of claim 13 wherein the second utility is to replace the SMS-simulator-generated component identifiers in the database with a provisioning component identifier of the SMS.

15. The system of claim 13 wherein the second utility is to replace SMS-simulator-generated provisioning time information with actual provisioning time information for the SMS.

16. The system of claim 13 wherein provisioning notification is suppressed to a main billing and provisioning system when the SMS-simulator-generated provisioning information is replaced.

17. The system of claim 11 wherein, while the first utility replays the first transaction file, the network element is to direct a subsequent provisioning request to the SMS simulator, and the SMS simulator is to:

assign a provisioning component identifier associated with the subsequent provisioning request;

store a command associated with the subsequent provisioning request and its associated provisioning component identifier in a second transaction file; and

send a provisioning response based on the subsequent provisioning request.

18. The system of claim 17 wherein the first utility is to replay the subsequent provisioning request in the second transaction file to provision the SMS.

19. The system of claim 18 wherein the first utility replays the second transaction file a predetermined time period after replaying the first transaction file.

20. The system of claim 19 wherein the predetermined time period is about one day.