A network system service change management method, device, equipment and storage medium

Abstract

The present invention relates to a network system service change management method, device, equipment and storage medium, the method comprising: judging whether there is mutual access between different services, determining the access path, control strategy and first mutual access relationship between the mutual access services; performing service changes according to the service change requirements, the access path and the control strategy, and determining a second mutual access relationship after the service change; verifying whether there are change errors or change omissions according to the first mutual access relationship, the second mutual access relationship and the service change requirements; rectifying the services with change errors or change omissions and updating the second mutual access relationship until the second mutual access relationship meets the service change requirements. The present invention provides a network system service change management method, device, equipment and storage medium, which determine the mutual access relationship between services, verify the changed services, avoid errors or omissions in service changes, and improve the accuracy of service changes.

Description

Technical Field

[0001] The present invention relates to the technical field of network management, and in particular to a method, device, equipment and storage medium for managing service changes in a network system. Background Art

[0002] With the rapid growth of enterprise IT systems, the shortcomings of traditional operations and maintenance models have become increasingly apparent. In particular, with the widespread adoption of new technologies like cloud computing and big data, the number of devices and operational complexity of enterprise information systems have increased significantly. When business changes occur, operations and maintenance administrators must ensure that access permissions remain consistent before and after the change, that business access remains normal after the change, and that relevant business departments are notified for verification. This manual operation model is increasingly unable to meet the safety and production requirements of data centers.

[0003] The service change management method of the network system in the existing technology needs to first determine the status of the network equipment, network interfaces and links, and then indirectly judge the operation status of each application in the network system, and then manage the network equipment according to the service change needs and the determined operation status of each application.

[0004] However, the business change management method of the network system in the existing technology is coarse-grained management, which makes business changes according to the business change needs and the operation status of each application in the system. However, the accuracy of the business changes is not high, and after the business changes are completed, the business conditions after the changes are not verified, which easily leads to omissions of business changes. Summary of the Invention

[0005] In view of this, it is necessary to provide a network system business change management method, device, equipment and storage medium to solve the problem that the existing technology only indirectly judges the operation status of each application in the network system, resulting in low accuracy of business changes and no verification of the changed business status after the business change is completed, which easily leads to omissions of business changes.

[0006] In order to achieve the above technical objectives, the present invention adopts the following technical solutions:

[0007] In a first aspect, the present invention provides a method for managing service changes in a network system, comprising:

[0008] Determine whether there is mutual access between different services, and determine the access path, control strategy and first mutual access relationship between the mutual access services;

[0009] Perform business changes based on business change requirements, access paths, and control policies, and determine the secondary access relationship after the business change;

[0010] Verify whether there are any change errors or omissions based on the first mutual visit relationship, the second mutual visit relationship and the business change requirements;

[0011] Rectify the business with change errors or omissions and update the second mutual visit relationship until the second mutual visit relationship meets the business change requirements.

[0012] In some possible implementations, determining whether mutual access exists between different services and determining a control strategy and a first mutual access relationship between the mutually accessed services include:

[0013] Query the traffic access status between hosts of different services and determine the mutual access services based on the traffic access status;

[0014] Obtain access paths and control policies between mutually accessed services and establish a first mutual access relationship;

[0015] The access path, control strategy and first mutual access relationship are saved to a preset database.

[0016] In some possible implementations, traffic access between hosts of different services is queried, and mutual access services are determined based on the traffic access, including: if traffic access exists between hosts of different services, setting the service with traffic access as a mutual access service.

[0017] In some possible implementations, a service change is performed based on service change requirements, access paths, and control policies, and a second mutual access relationship after the service change is determined, including:

[0018] Determine the business change type and the business IP to be changed based on business change requirements;

[0019] Perform business changes based on business change type, control policy, business IP to be changed, and access path;

[0020] Query the traffic access status between services after the change and determine the second mutual access relationship after the change.

[0021] In some possible implementations, service change types include service offline, service expansion, and service replacement. Service changes are performed based on the service change type, control policy, service IP address to be changed, and access path, including:

[0022] If the service change type is service offline, determine the network device offline based on the service IP and access path to be changed, and delete the control policy corresponding to the network device offline.

[0023] If the service change type is service expansion, determine the network device for service expansion based on the service IP and access path to be changed, and add control policies based on the network device for service expansion.

[0024] If the service change type is service replacement, determine the network device for service replacement based on the service IP and access path to be changed, and modify the control policy based on the network device for service replacement.

[0025] In some possible implementations, verifying whether a change error or omission occurs based on the first mutual access relationship, the second mutual access relationship, and the service change requirement includes:

[0026] Determine changes in the business mutual visit relationship based on the first mutual visit relationship and the second mutual visit relationship;

[0027] Verify whether there are any change errors or omissions based on changes in business visit relationships and business change requirements.

[0028] In some possible implementations, the business with the change error or omission is rectified and the second mutual access relationship is updated until the second mutual access relationship meets the business change requirements, including:

[0029] Identify the incorrect business IPs that were changed and / or the business IPs that were omitted;

[0030] Perform business changes based on business change type, control policy, access path, incorrect business IP changed, and / or omitted business IP changed;

[0031] Update the second mutual access relationship and repeatedly verify whether there are any change errors or omissions until the second mutual access relationship meets the business change requirements.

[0032] In a second aspect, the present invention further provides a network system service change management device, comprising:

[0033] A judgment module, used to judge whether there is mutual access between different services, and determine the access path, control strategy and first mutual access relationship between the mutual access services;

[0034] The change module is used to make business changes according to business change requirements, access paths and control policies, and to determine the second mutual access relationship after the business change;

[0035] A verification module is used to verify whether a change error or change omission occurs based on the first mutual visit relationship, the second mutual visit relationship and the business change requirement;

[0036] The rectification module is used to rectify the business with change errors or omissions and update the second mutual visit relationship until the second mutual visit relationship meets the business change requirements.

[0037] In a third aspect, the present invention further provides an electronic device comprising a memory and a processor, wherein:

[0038] Memory, used to store programs;

[0039] The processor is coupled to the memory and is used to execute the program stored in the memory to implement the steps in the network system service change management method in any of the above implementations.

[0040] In a fourth aspect, the present invention also provides a computer-readable storage medium for storing computer-readable programs or instructions. When the program or instructions are executed by a processor, the steps in the network system service change management method in any of the above-mentioned implementation methods can be implemented.

[0041] The beneficial effects of adopting the above embodiment are as follows: the present invention relates to a network system service change management method, device, equipment and storage medium, the method comprising: judging whether there is mutual access between different services, determining the access path, control strategy and first mutual access relationship between the mutual access services; performing service changes according to the service change requirements, the access path and the control strategy, and determining the second mutual access relationship after the service change; verifying whether there are change errors or change omissions according to the first mutual access relationship, the second mutual access relationship and the service change requirements; rectifying the services with change errors or change omissions and updating the second mutual access relationship until the second mutual access relationship meets the service change requirements. The present invention provides a network system service change management method, device, equipment and storage medium, first judging whether there is mutual access between services, determining the access path, control strategy and mutual access relationship between the mutual access services, performing service changes according to the access path and control strategy, and verifying the changed services according to the mutual access relationship, finding errors or omissions in the service changes and rectifying them, thereby improving the accuracy of the service changes. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 A flowchart of an embodiment of a method for managing network system service changes provided by the present invention;

[0043] Figure 2 for Figure 1 A flow chart of an embodiment of step S101;

[0044] Figure 3 for Figure 1 A flow chart of an embodiment of step S102;

[0045] Figure 4 for Figure 1 A flow chart of an embodiment of step S104;

[0046] Figure 5 A schematic structural diagram of an embodiment of a network system service change management device provided by the present invention;

[0047] Figure 6A schematic structural diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0048] The preferred embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings, wherein the accompanying drawings constitute a part of this application and are used together with the embodiments of the present invention to illustrate the principles of the present invention, and are not used to limit the scope of the present invention.

[0049] In the description of the present application, “plurality” means two or more, unless otherwise clearly defined.

[0050] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present invention. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute a separate or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0051] The present invention provides a network system service change management method, apparatus, device and storage medium, which are described below respectively.

[0052] See also Figure 1 , Figure 1 This is a flow chart of an embodiment of a network system service change management method provided by the present invention. A specific embodiment of the present invention discloses a network system service change management method, including:

[0053] S101, determining whether there is mutual access between different services, and determining the access path, control strategy and first mutual access relationship between the mutual access services;

[0054] S102: Perform business changes according to business change requirements, access paths, and control policies, and determine a second mutual access relationship after the business change;

[0055] S103. Verify whether there are any change errors or omissions based on the first mutual visit relationship, the second mutual visit relationship, and the business change requirements;

[0056] S104: rectify the business with change errors or omissions and update the second mutual visit relationship until the second mutual visit relationship meets the business change requirements.

[0057] In the above embodiment, before making a business change, it is first necessary to determine the mutual visit relationship between the businesses. For businesses that have a mutual visit relationship, the business change needs to be made based on the mutual visit relationship before the change, so that the mutual visit relationship after the change satisfies the mutual visit relationship before the change, so as to avoid errors or omissions in the mutual visit relationship between the businesses after the business change.

[0058] When making business changes, first obtain the business change requirements, determine how to change the business based on the business change requirements, then complete the business change through access paths and control policies, and obtain the second mutual access relationship after the business change so that the changed business can be verified later.

[0059] Verifying whether there are any change errors or omissions based on the first mutual visit relationship, the second mutual visit relationship and the business change requirements is to avoid abnormalities in the business after the change, improve the results of the business change, and improve the accuracy of the business change.

[0060] Rectify businesses with change errors or omissions so that the changed businesses meet the change requirements and prevent system problems after the business changes. When a network system that meets the business change requirements fails, it can also better locate the location and cause of the failure and repair it in a timely manner.

[0061] Compared with the prior art, the present embodiment provides a network system service change management method, which includes: judging whether there is mutual access between different services, determining the access path, control strategy and first mutual access relationship between the mutual access services; performing service changes according to the service change requirements, the access path and the control strategy, and determining the second mutual access relationship after the service change; verifying whether there are change errors or change omissions according to the first mutual access relationship, the second mutual access relationship and the service change requirements; rectifying the services with change errors or change omissions and updating the second mutual access relationship until the second mutual access relationship meets the service change requirements. The present invention provides a network system service change management method, device, equipment and storage medium, which first judges whether there is mutual access between services, determines the access path, control strategy and mutual access relationship between the mutual access services, performs service changes according to the access path and control strategy, and verifies the changed services according to the mutual access relationship, finds out errors or omissions in the service changes and rectify them, thereby improving the accuracy of the service changes.

[0062] See also Figure 2 , Figure 2 for Figure 1 In a flow chart of an embodiment of step S101, in some embodiments of the present invention, determining whether there is mutual access between different services and determining a control strategy and a first mutual access relationship between the mutual access services include:

[0063] S201, querying traffic access between hosts of different services, and determining the mutually accessed services based on the traffic access;

[0064] S202: Obtain access paths and control policies between mutually accessed services and establish a first mutual access relationship;

[0065] S203: Save the access path, control strategy, and first mutual access relationship to a preset database.

[0066] In the above embodiment, before performing a service change, traffic access between hosts of different services is first queried. Hosts of services with mutual access relationships must have traffic access, so that services with mutual access can be determined.

[0067] For businesses with mutual access relationships, it is necessary to obtain the access paths between them, understand the nodes of the access paths, determine the control strategies between them, and establish the first mutual access relationship, so as to better complete the transformation between businesses when the businesses change.

[0068] The obtained access path, control strategy and first mutual access relationship are saved in a preset database, which can be easily retrieved in subsequent use. It should be noted that the preset database can be selected according to actual needs.

[0069] In some embodiments of the present invention, traffic access between hosts of different services is queried, and mutual access services are determined based on the traffic access, including: if traffic access exists between hosts of different services, setting the service with traffic access as a mutual access service.

[0070] In the above embodiment, it is determined whether there is actual traffic access between all hosts under a service and all hosts under another service. If there is actual traffic access, it indicates that there is traffic access between the two current services.

[0071] It should be noted that if there is only traffic access from one party to the other, but no traffic access between the two parties, it also indicates that there is traffic access between the two current businesses. The lack of traffic access from the other party can also be an access relationship.

[0072] See also Figure 3 , Figure 3 for Figure 1 In a flow chart of an embodiment of step S102, in some embodiments of the present invention, performing a service change according to a service change requirement, an access path, and a control policy, and determining a second mutual access relationship after the service change includes:

[0073] S301. Determine the service change type and the service IP to be changed according to the service change requirements;

[0074] S302: Perform service changes based on the service change type, control policy, service IP to be changed, and access path;

[0075] S303: Query the traffic access status between the services after the change, and determine the second mutual access relationship after the change.

[0076] In the above embodiment, the service change requirement can be generated according to actual needs. The service change type and the service IP to be changed can be determined through the service change requirement, thereby determining how to perform the service change and locate the service to be changed.

[0077] Determine the service change method based on the service change type, control policy, service IP to be changed, and access path, and locate the network equipment that needs to be changed. Complete the service change based on the service change method and the location of the network equipment.

[0078] The method of determining the second mutual visiting relationship is the same as the method of determining the first mutual visiting relationship, which will not be described in detail in the present invention. The second mutual visiting relationship is determined for comparison with the first mutual visiting relationship determined previously after the service change.

[0079] In some embodiments of the present invention, service change types include service offline, service expansion, and service replacement. Service changes are performed based on the service change type, control policy, service IP to be changed, and access path, including:

[0080] If the service change type is service offline, determine the network device offline based on the service IP and access path to be changed, and delete the control policy corresponding to the network device offline.

[0081] If the service change type is service expansion, determine the network device for service expansion based on the service IP and access path to be changed, and add control policies based on the network device for service expansion.

[0082] If the service change type is service replacement, determine the network device for service replacement based on the service IP and access path to be changed, and modify the control policy based on the network device for service replacement.

[0083] In the above embodiment, service change types include service offline, service expansion, and service replacement. Additional service change types can be added as needed. When the service change type is offline, the network device associated with the offline service is identified using the IP address and access path of the service to be changed. The offline service is then deleted according to the established control policy. The processing for service expansion and service replacement is similar to that for service offline, and will not be further described in this disclosure.

[0084] In some embodiments of the present invention, verifying whether a change error or a change omission occurs based on the first mutual visit relationship, the second mutual visit relationship, and the service change requirement includes:

[0085] Determine changes in the business mutual visit relationship based on the first mutual visit relationship and the second mutual visit relationship;

[0086] Verify whether there are any change errors or omissions based on changes in business visit relationships and business change requirements.

[0087] In the above embodiment, for some business changes, the first mutual visit relationship and the second mutual visit relationship will change, and the first mutual visit relationship and the second mutual visit relationship are completely different. Only the first mutual visit relationship and the second mutual visit relationship can be used as a reference to further verify the accuracy of the business change according to the business change requirements, that is, to verify whether there are any change errors or omissions.

[0088] See also Figure 4 , Figure 4 for Figure 1 In a flowchart of an embodiment of step S104, in some embodiments of the present invention, rectifying the business with the change error or omission and updating the second mutual visit relationship until the second mutual visit relationship meets the business change requirements includes:

[0089] S401, determining the service IP that was incorrectly changed and / or the service IP that was omitted from the change;

[0090] S402. Perform a service change based on the service change type, control policy, access path, incorrectly changed service IP, and / or omitted service IP.

[0091] S403: Update the second mutual visit relationship and repeatedly verify whether there is a change error or change omission until the second mutual visit relationship meets the business change requirement.

[0092] In the above embodiment, the purpose of determining the service IP address of the service to be changed incorrectly and / or the service IP address of the service to be changed is to locate the network device of the service to be changed again, so as to rectify the omission and error of the change.

[0093] The subsequent processing is the same as the process of the first business change. The abnormal business change is rectified, that is, the business change with the abnormality is corrected again to meet the business change requirements.

[0094] In order to better implement the network system service change management method in the embodiment of the present invention, based on the network system service change management method, correspondingly, please refer to Figure 5 , Figure 5 This is a schematic diagram of the structure of an embodiment of a network system service change management device provided by the present invention. The embodiment of the present invention provides a network system service change management device 500, including:

[0095] A determination module 510 is configured to determine whether mutual access exists between different services, and to determine an access path, a control strategy, and a first mutual access relationship between the mutual access services;

[0096] The change module 520 is used to perform a service change according to the service change requirements, access path and control policy, and determine the second mutual access relationship after the service change;

[0097] A verification module 530 is configured to verify whether a change error or change omission occurs based on the first mutual visit relationship, the second mutual visit relationship, and the business change requirement;

[0098] The rectification module 540 is configured to rectify the business with the change error or the change omission and update the second mutual visit relationship until the second mutual visit relationship meets the business change requirement.

[0099] It should be noted here that the device 500 provided in the above embodiment can implement the technical solutions described in the above method embodiments. The specific implementation principles of the above modules or units can be found in the corresponding contents in the above method embodiments, which will not be repeated here.

[0100] See also Figure 6 , Figure 6 This is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. Based on the aforementioned network system service change management method, the present invention also provides a network system service change management device. The network system service change management device can be a computing device such as a mobile terminal, desktop computer, notebook, PDA, or server. The network system service change management device includes a processor 610, a memory 620, and a display 630. Figure 6 Only some of the components of the electronic device are shown, but it should be understood that it is not required to implement all of the shown components, and more or fewer components may be implemented instead.

[0101] In some embodiments, the memory 620 may be an internal storage unit of the network system service change management device, such as a hard disk or memory of the network system service change management device. In other embodiments, the memory 620 may also be an external storage device of the network system service change management device, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped with the network system service change management device. Furthermore, the memory 620 may include both an internal storage unit of the network system service change management device and an external storage device. The memory 620 is used to store application software installed in the network system service change management device and various data, such as program code for installing the network system service change management device. The memory 620 may also be used to temporarily store data that has been output or is about to be output. In one embodiment, the memory 620 stores a network system service change management program 640, which can be executed by the processor 610 to implement the network system service change management method of each embodiment of the present application.

[0102] In some embodiments, the processor 610 may be a central processing unit (CPU), a microprocessor, or other data processing chip, configured to execute program codes or process data stored in the memory 620, such as executing a network system service change management method.

[0103] In some embodiments, the display 630 can be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, or an OLED (Organic Light-Emitting Diode) touchscreen. The display 630 is used to display information on the network system service change management device and to display a visual user interface. The components 610-630 of the network system service change management device communicate with each other via a system bus.

[0104] In one embodiment, when the processor 610 executes the network system service change management program 640 in the memory 620 , the steps in the above network system service change management method are implemented.

[0105] This embodiment further provides a computer-readable storage medium storing a network system service change management program. When the network system service change management program is executed by a processor, the following steps are implemented:

[0106] Determine whether there is mutual access between different services, and determine the access path, control strategy and first mutual access relationship between the mutual access services;

[0107] Perform business changes based on business change requirements, access paths, and control policies, and determine the secondary access relationship after the business change;

[0108] Verify whether there are any change errors or omissions based on the first mutual visit relationship, the second mutual visit relationship and the business change requirements;

[0109] Rectify the business with change errors or omissions and update the second mutual visit relationship until the second mutual visit relationship meets the business change requirements.

[0110] In summary, the present embodiment provides a network system service change management method, device, equipment and storage medium, the method comprising: judging whether there is mutual access between different services, determining the access path, control strategy and first mutual access relationship between the mutual access services; performing service changes according to the service change requirements, the access path and the control strategy, and determining the second mutual access relationship after the service change; verifying whether there are change errors or change omissions according to the first mutual access relationship, the second mutual access relationship and the service change requirements; rectifying the services with change errors or change omissions and updating the second mutual access relationship until the second mutual access relationship meets the service change requirements. The present invention provides a network system service change management method, device, equipment and storage medium, first judging whether there is mutual access between services, determining the access path, control strategy and mutual access relationship between the mutual access services, performing service changes through the access path and control strategy, and verifying the changed services according to the mutual access relationship, finding errors or omissions in the service changes and rectifying them, thereby improving the accuracy of the service changes.

[0111] The above description is only a preferred specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by any technician familiar with this technical field within the technical scope disclosed by the present invention should be covered by the scope of protection of the present invention.

Claims

1. A network system service change management method, characterized in that: include: Determine whether there is mutual access between different services, and determine the access path, control strategy and first mutual access relationship between the mutual access services; Performing a business change according to the business change requirement, the access path, and the control policy, and determining a second mutual access relationship after the business change; Verify whether a change error or change omission occurs based on the first mutual visit relationship, the second mutual visit relationship, and the business change requirement; Rectify the business with change errors or omissions and update the second mutual visit relationship until the second mutual visit relationship meets the business change requirements.

2. The network system service change management method according to claim 1, characterized in that: The determining whether there is mutual access between different services and determining the control strategy and the first mutual access relationship between the mutual access services includes: Query traffic access status between hosts of different services, and determine the mutually accessed services based on the traffic access status; Obtain access paths and control policies between mutually accessed services and establish a first mutual access relationship; The access path, the control strategy and the first mutual access relationship are saved in a preset database.

3. The network system service change management method according to claim 2, characterized in that: The querying of traffic access conditions between hosts of different services and determining the mutual access service according to the traffic access conditions includes: if traffic access exists between hosts of different services, setting the service with traffic access as the mutual access service.

4. The network system service change management method according to claim 1, characterized in that: The performing of the service change according to the service change requirement, the access path, and the control policy, and determining the second mutual access relationship after the service change, includes: Determine the service change type and the service IP to be changed based on the service change requirements; Performing a service change according to the service change type, the control policy, the service IP to be changed, and the access path; Query the traffic access status between services after the change and determine the second mutual access relationship after the change.

5. The network system service change management method according to claim 4, characterized in that: The service change types include service offline, service expansion, and service replacement; performing service changes based on the service change type, the control policy, the service IP to be changed, and the access path includes: If the service change type is service offline, determine the network device that is offline based on the service IP to be changed and the access path, and delete the control policy corresponding to the network device that is offline; If the service change type is service expansion, determine the network device for service expansion based on the service IP to be changed and the access path, and add a control policy based on the network device for service expansion; If the service change type is service replacement, a network device for service replacement is determined according to the service IP to be changed and the access path, and a control policy is modified according to the network device for service replacement.

6. The network system service change management method according to claim 1, characterized in that: The verifying whether a change error or change omission occurs according to the first mutual visit relationship, the second mutual visit relationship, and the business change requirement includes: Determine a change in a business mutual visit relationship based on the first mutual visit relationship and the second mutual visit relationship; Verify whether there are any change errors or change omissions based on the changes in the business mutual visit relationship and the business change requirements.

7. The network system service change management method according to claim 4, characterized in that: The rectifying the business with the change error or the change omission and updating the second mutual visit relationship until the second mutual visit relationship meets the business change requirement includes: Identify the incorrect business IPs that were changed and / or the business IPs that were omitted; Performing a service change based on the service change type, the control policy, the access path, the service IP that was incorrectly changed, and / or the service IP that was omitted; The second mutual visit relationship is updated, and verification is repeated to determine whether a change error or change omission occurs until the second mutual visit relationship meets the service change requirement.

8. A network system service change management device, characterized in that: include: A judgment module, used to judge whether there is mutual access between different services, and determine the access path, control strategy and first mutual access relationship between the mutual access services; A change module, configured to perform a business change according to the business change requirements, the access path, and the control policy, and determine a second mutual access relationship after the business change; A verification module, configured to verify whether a change error or change omission occurs based on the first mutual visit relationship, the second mutual visit relationship, and the business change requirement; The rectification module is used to rectify the business with change errors or omissions and update the second mutual visit relationship until the second mutual visit relationship meets the business change requirements.

9. An electronic device, characterized in that: comprising a memory and a processor, wherein, The memory is used to store programs; The processor is coupled to the memory and is used to execute the program stored in the memory to implement the steps in the network system service change management method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that Used to store computer-readable programs or instructions, which, when executed by a processor, can implement the steps of the network system service change management method described in any one of claims 1 to 7.

Images