Enabling user defined network change leveraging as-built data

• US 8,644,146 B1
• Filed: 08/02/2010
• Issued: 02/04/2014
• Est. Priority Date: 08/02/2010
• Status: Expired due to Fees

• Current Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Original Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Inventors: Lushear, Brian D., Szymanski, Todd M., Kurtz, Matthew D., Lobo, Shane A. Jr.
• Primary Examiner(s): Phillips, Hassan
• Assistant Examiner(s): Cattungal, Ajay
• Application Number:
  US12/848,818
• Time in Patent Office: 1,282 Days
• Field of Search: 370/230, 370/230.1, 370/231, 370/236, 370/237, 370/229, 370/252, 370/254, 370/255, 370/352, 370/389, 370/392, 370/400, 370/401, 709/227, 709/228, 709220-225, 709/241, 709/248
• US Class Current: 370/231
• CPC Class Codes: H04L 41/0813 characterised by the conditions triggering a change of settings
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components

Abstract

A system is provided that receives a first change request from a first enterprise network device to a first configuration used by the first device, identifies components of the first configuration impacted by the first request, and receives a second change request from a second network device to a second configuration used by the second device. The system identifies second configuration components impacted by the second request, filters second device information from the second request and components impacted by the request, and analyzes the unimplemented first request impacting at least one component impacted by the second request. The system presents the as-built configuration of the second configuration, describes the first request impact to the component, approves all or some of the second request based on analysis of filtering results and a commitment regarding the first request, and processes the approved portion of the second request based on second device response.

Claims

1. A network change management system, comprising:

a processor;

a memory; and

an application stored in the memory that, when executed by the processor,

receives a first change request message from a first customer device in an enterprise network, the first change request message containing a first change request to make a first change to a configuration of a network port;

identifies components of the configuration impacted by the first change request;

receives a second change request message from a second customer device in the enterprise network, the second change request message containing a second change request to make a second change to the configuration of the network port, wherein the network port is configured to be used by the first customer device and by the second customer device;

identifies components of the configuration impacted by the second change request;

filters information contained in the second change request about the second customer device and the components impacted by the second change request by applying at least one filtering criterion;

analyzes the first change request, wherein the first change request impacts at least one component impacted by the second change request, and wherein the first change request has not been implemented;

sends a notification message to the second customer device presenting the current as-built configuration of the network port and further describing the impact to the at least one component of the first change request;

approves one of the entirety or a portion of the second change request based on analysis of the results of the at least one applied filtering criterion and based on analysis of a previous commitment associated with the first change request;

sends an option message to the second customer device, the option message presenting at least one available option associated with the second change request, the at least one available option is based on the approved one of the entirety or the portion of the second change request;

receives a submission message from the second customer device, the submission message containing a selection by the second customer device of one of the at least one available option; and

processes the second change request based on receiving the submission message.

2. The system of claim 1, wherein the network port is on a telecommunications service provider network providing at least one of voice or data services.

3. The system of claim 1, wherein at least one filtering criterion is applied to rights or permissions associated with the first customer device to at least one of view, access, or make changes to the components of the network port configuration impacted by the first change request and the second change request.

4. The system of claim 1, wherein the components of the configuration impacted by the first change request and the second change request are at least one of software components or hardware components.

5. The system of claim 1, wherein the as-built configuration information presented to the second customer device comprises information relevant to the first change request and excludes information determined at least one of not relevant to the second change request or confidential.

6. The system of claim 1, wherein, upon receiving the notification message, the first customer device analyzes the impact to the at least one component of the second change request.

7. The system of claim 6, wherein, upon analyzing the impact to the at least one component of the second change request, the first customer device determines that the impact is acceptable.

8. The system of claim 6, wherein, upon analyzing the impact to the at least one component of the second change request, the first customer device determines that the impact is not acceptable and one of amends the first change request or cancels the first change request.

9. A processor-implemented network change management method, comprising:

receiving, by a server associated with a telecommunications service provider, a message from a first service requester associated with a first customer, the message requesting fulfillment of a change request to a component associated with a network port on a system provided by the telecommunications service provider, the system providing at least one of voice or data services;

based on the message, generating, by the server, information associated with the at least one of the voice or data services and further generating information about the status of the network port and policies associated with the network port;

generating, by the server, information about access rights associated with the first service requester regarding the network port;

providing, by the server, a change request form to the first service requester based on the information generated, the change request form containing as-built configuration information about the network port and containing populated information fields, wherein the change request form presents at least one available configuration option based on at least one of the change request, the as-built information, the access rights, or the policies;

receiving, by the server, the completed change request form from the first service requester, the completed change request form including a selection of one of the at least one available configuration option;

analyzing, by the server, at least one previously issued commitment associated with at least one previously received change request from at least a second service requester associated with a second customer;

identifying, by the server, based on the analyzing, a conflict between the at least one previously issued commitment and specifications in the completed change request form received from the first service requester;

resolving, by the server, the conflict and notifying the first service requester of an adjustment to the completed change request form, the adjustment arising from the resolution of the conflict;

receiving, by the server, acknowledgment of the adjustment and confirmation of the request to proceed with the change request from the first service requester; and

processing, by the server, the completed change request form, the completed change request form containing the adjustment.

10. The method of claim 9, wherein the conflict is related to at least one of a software component of the network port or a hardware component of the network port.

11. The method of claim 9, wherein the conflict is related to the availability of technical resources to implement the change request submitted by the first service requester and the at least one previously received change request.

12. The method of claim 9, wherein the conflict is resolved by amending at least one specification in at least one of the change request or the at least one previously received change request regarding at least one of a hardware change, a software change, a work schedule, or an allocation of resources to address at least one of the change request or the at least one previously received change request.

13. The method of claim 9, wherein the policies describe at least one of the permitted changes to the component associated with the network port.

14. The method of claim 9, wherein in determining the at least one available option and presenting information in the change request form to the first service requester, the server filters out information about the network port that is unrelated to the at least one of the voice or data services and configuration associated with the first service requester.

15. A processor-implemented network change management method, comprising:

a server associated with a telecommunications service provider providing information about a first as-built configuration for a network port to a first service requester and a second service requester, wherein the first service requester and the second service requester are associated with the same customer entity;

the server receiving a first change request from the first service requester and receiving a second change request from the second service requester wherein each of the first change request and the second change request is associated with the network port;

the server identifying a higher level of importance for the first change request in relation to the second change request and determining that the first change request is to be executed prior to the second change request;

the server determining that implementing the first change request results in the network port having a second as-built configuration and further determining that the second as-built configuration necessitates a first adjustment to the second change request;

the server notifying the second service requester of the necessity of the first adjustment to the second change request;

the server receiving instruction from the second service requester to proceed with the second change request modified for the first adjustment;

the server implementing the first change request, the implementation of the first change request resulting in the network port having the second as-built configuration;

the server receiving a third change request from a third service requester wherein the third change request is associated with the network port and is based on the second as-built configuration;

the server determining that the third change request takes priority over the second change request;

the server determining that implementing the third change request prior to the second change request results in the network port having a third as-built configuration and further determining that the third as-built configuration necessitates a second adjustment to the second change request;

the server notifying the second service requester of the necessity of the second adjustment to the second change request;

the server receiving a message from the second service requester canceling the second change request;

the server implementing the third change request, the implementation of the third change request resulting in the network port having the third as-built configuration;

the server receiving a fourth change request from the second service requester;

the server implementing the fourth change request, the implementation of the fourth change request resulting in the network port having a fourth as-built configuration; and

the server sending a message to each of the first service requester, the second service requester, and the third service requester, the message describing the fourth as-built configuration and further describing the chronology of changes made to the network port in fulfilling the first change request, the third change request, and the fourth change request.

16. The method of claim 15, wherein the chronology of changes made to the network port provide one of full and partial descriptions of at least one of the first as-built configuration, the second as-built configuration, the third as-built configuration, and the fourth as-built configuration.

17. The method of claim 15, wherein when a service requester submits a change request, one of a full and partial description of outstanding change requests regarding the subject network port is presented to the service requester.

18. The method of claim 15, wherein the determination of at least one of the importance and the order of execution of change requests is based on at least one of the severity of a problem to be addressed by a change request and the cost of implementing the change request.

19. The method of claim 15, further comprising providing change request forms to the first service requester, the second service requester, and the third service requester, the change request forms containing at least one of as-built configuration information and fields populated with information specific to each of the first service requester, the second service requester, and the third service requester.

20. The method of claim 19, wherein the information populated into the fields comprises at least one of information identifying one of the first service requester, the second service requester, and the third service requester and information about the network port, the information provided about the network port based on at least one of the permission levels of one of the first service requester, the second service requester, and the third service requester and policies regarding the network port.