[go: up one dir, main page]

WO2018036137A1 - Procédé de gestion d'opération et de maintenance d'appareil gtm, terminal, support de stockage lisible par ordinateur et dispositif de gestion - Google Patents

Procédé de gestion d'opération et de maintenance d'appareil gtm, terminal, support de stockage lisible par ordinateur et dispositif de gestion Download PDF

Info

Publication number
WO2018036137A1
WO2018036137A1 PCT/CN2017/076520 CN2017076520W WO2018036137A1 WO 2018036137 A1 WO2018036137 A1 WO 2018036137A1 CN 2017076520 W CN2017076520 W CN 2017076520W WO 2018036137 A1 WO2018036137 A1 WO 2018036137A1
Authority
WO
WIPO (PCT)
Prior art keywords
request
domain name
gtm
modification
record
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2017/076520
Other languages
English (en)
Chinese (zh)
Inventor
李波
谭毅
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Publication of WO2018036137A1 publication Critical patent/WO2018036137A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements

Definitions

  • the present invention relates to the field of operation and maintenance management technologies, and in particular, to a GTM device operation and maintenance management method, a terminal, a computer readable storage medium, and a management device.
  • GTM Global Traffic Manager Global Traffic Management ()
  • GTM Global Traffic Manager Global Traffic Management
  • the embodiment of the invention provides a GTM device operation and maintenance management method, a terminal, a computer readable storage medium and a management device, which can implement automatic operation and maintenance management, improve efficiency, and improve user experience of the GTM device.
  • an embodiment of the present invention provides a GTM device operation and maintenance management method, where the method includes: if an operation request input by a user is received, determining whether the operation request is an increase request, a delete request, or a modification request; The operation request is an add request, and a record is added to the GTM device, where the record is used to identify a mapping relationship between a domain name and an IP address; if the operation request is a delete request, the record is deleted on the GTM device; The operation request is a modification request, and the configuration information is modified on the GTM device, and the configuration information corresponds to the domain name.
  • the embodiment of the present invention provides a terminal, where the terminal includes: a first determining unit, configured to: if receiving an operation request input by a user, determine whether the operation request is an increase request, a delete request, or a modify request Adding a unit, if the operation request is an increase request, adding a record on the GTM device, the record is used to identify a mapping relationship between a domain name and an IP address; and the deleting unit is configured to: if the operation request is a deletion request, Deleting the record on the GTM device; modifying the unit, if the operation request is a modification request, modifying the configuration information on the GTM device, where the configuration information corresponds to the domain name.
  • an embodiment of the present invention provides a computer readable storage medium having one or more programs, the one or more programs being executable by one or more processors to implement the following steps If the operation request input by the user is received, determining whether the operation request is an increase request, a delete request, or a modification request; if the operation request is an increase request, adding a record on the GTM device, where the record is used to identify the domain name a mapping relationship with the IP address; if the operation request is a deletion request, deleting the record on the GTM device; if the operation request is a modification request, modifying the configuration information on the GTM device, where the configuration information corresponds to the domain name .
  • an embodiment of the present invention provides a GTM operation and maintenance device management apparatus, where the memory includes a memory and a processor, the memory is used to store an instruction, and the processor reads an instruction in the memory and according to the The instruction performs the following operations: if an operation request input by the user is received, determining whether the operation request is an increase request, a delete request, or a modification request; if the operation request is an increase request, adding a record on the GTM device, Recording a mapping relationship between the domain name and the IP address; if the operation request is a deletion request, deleting the record on the GTM device; if the operation request is a modification request, modifying the configuration information on the GTM device, the configuration The information corresponds to the domain name.
  • the embodiment of the present invention determines whether the operation request is an increase request, a delete request, or a modification request, and if the operation request is an increase request, adding a record on the GTM device, if the operation request is deleted Request to delete the record on the GTM device. If the operation request is a modification request, modify the configuration information corresponding to the domain name on the GTM device.
  • the embodiment of the present invention divides an operation request into an increase request, a delete request, or a modify request, and performs corresponding processing operations on different operation requests, thereby implementing automatic operation and maintenance management, improving efficiency, and improving user experience of the GTM device. .
  • FIG. 1 is a schematic flowchart of a GTM device operation and maintenance management method according to an embodiment of the present invention
  • FIG. 2 is a schematic flow chart corresponding to step S102 when the operation request in FIG. 1 is an increase request;
  • step S103 is a schematic flow chart corresponding to step S103 when the operation request in FIG. 1 is a deletion request;
  • step S104 is a schematic flow chart corresponding to step S104 when the operation request in FIG. 1 is a modification request;
  • FIG. 5 is a schematic flowchart of a GTM device operation and maintenance management method according to another embodiment of the present invention.
  • FIG. 6 is a schematic block diagram of a terminal according to an embodiment of the present disclosure.
  • Figure 7 is a schematic block diagram of the adding unit of Figure 6;
  • Figure 8 is a schematic block diagram of the deleting unit of Figure 6;
  • Figure 9 is a schematic block diagram of the modification unit of Figure 6;
  • FIG. 10 is a schematic block diagram of a terminal according to another embodiment of the present invention.
  • FIG. 11 is a schematic block diagram of a management apparatus according to an embodiment of the present invention.
  • FIG. 1 is a schematic flowchart of a GTM device operation and maintenance management method according to an embodiment of the present invention.
  • the GTM Global Traffic Manager Global Traffic Management ()
  • the GTM device operation and maintenance management method in the embodiment of the present invention can be used in a terminal such as a PC to process operations such as adding, modifying, and deleting domain name records.
  • the GTM device operation and maintenance management method includes steps S101 to S104.
  • the operation request includes an increase request, a delete request, and a modification request.
  • the user is requested to input the request information corresponding to the operation request through the human-computer interaction interface for different operations.
  • the add request is used to add a record on the GTM device
  • the delete request is used to delete the record on the GTM device
  • the modify request is used to modify the configuration information on the GTM device, the configuration information corresponding to the domain name.
  • the record is used to identify the mapping between the domain name and the IP address.
  • a GTM cluster is usually formed by multiple GTM devices to provide services.
  • the GTM cluster is configured with a primary GTM device and multiple subordinate GTM devices. After the operation and maintenance configuration is performed on the primary GTM device, the operation and maintenance configuration information on the primary GTM device and the operation and maintenance configuration information on the secondary GTM device are implemented. Synchronize backups. Since the synchronous backup technology between GTM devices belongs to the prior art, it will not be described here.
  • the database is usually set in the database independently of the GTM device.
  • the database is used to store the operation and maintenance configuration information on the GTM device.
  • the domain name or IP address query operation is performed through the database.
  • the operation request is an increase request, add a record on the GTM device, where the record is used to identify a mapping relationship between a domain name and an IP address.
  • FIG. 1 is a schematic flow chart corresponding to step S102 when the operation request is an increase request. As shown in the figure, step S102 specifically steps S201 to S207.
  • S201 Determine whether the increase request is a dynamic increase request or a static increase request, where the dynamic increase request includes a domain name, at least one IP address corresponding to the domain name, and the static increase request includes a domain name, and the domain name A corresponding IP address, and record type.
  • the dynamic record and the static record are formed according to the mapping relationship between the domain name and the IP address corresponding to the domain name, and the dynamic record corresponds to the dynamic operation request, and the static record corresponds to the static operation request.
  • the request for the increase of the user input it is necessary to determine whether the request for the increase is a dynamic increase request or a static request, because the operation request of the dynamic operation request and the static operation request are different on the GTM device. Increase the request.
  • the increase request is a dynamic increase request, determine whether the domain name exists on the GTM device.
  • the dynamic increase request is set by the user.
  • the dynamic increase request includes at least a domain name and a plurality of IP addresses corresponding to the domain name.
  • the dynamic increase request may further include increasing the type of the request, the port number corresponding to the IP address, and the like.
  • increasing the type of the request such as dynamic increase/static increase, can also be selected by the user through the human-computer interaction interface, for example, a drop-down box can be set on the human-computer interaction interface for the user to make a type selection of the increase request.
  • the comparison can be made one by one, the domain name on the GTM device and the IP address corresponding to each domain name are listed to form a mapping relationship between the domain name and the IP address, and the domain name in the request and the mapping are dynamically added.
  • the domain names in the relationship table are compared one by one to determine whether the domain name should exist on the GTM device. It is to be understood that the manner of determining whether the domain name already exists on the GTM device is not limited thereto, and is not limited herein.
  • the GTM device Adding the domain name and the record formed by the IP address corresponding to the domain name, so as to perform domain name resolution according to the access request of the visitor and find the network resource corresponding to the domain name.
  • a domain name can correspond to multiple IP addresses
  • the domain name in the dynamic increase request already exists on the GTM device, it indicates that the domain name and its corresponding IP address already exist on the GTM device, in order to prevent the GTM.
  • the same IP address is added to the same domain name on the device, you need to determine whether the IP address corresponding to the domain name in the dynamic request is already on the GTM device.
  • the IP address can be compared with the IP address in the mapping table between the domain name and the IP address on the GTM device. It is to be understood that the manner of determining whether the IP address corresponding to the domain name in the dynamic increase request is already present on the GTM device is not limited thereto, and is not limited herein.
  • the domain name in the dynamic increase request corresponds to multiple IP addresses, it is necessary to determine whether each IP address exists on the GTM device one by one, thereby avoiding repeatedly adding the same IP address to the same domain name on the GTM device. .
  • whether the multiple IP addresses corresponding to the domain name exist on the GTM device include the following three situations: (1) the IP addresses corresponding to the domain name all exist on the GTM device, and (2) The IP address corresponding to the domain name does not exist on the GTM device. (3) A part of the IP address corresponding to the domain name already exists on the GTM device, and another part does not exist on the GTM device. After determining, according to step S204, whether each IP address corresponding to the domain name already exists on the GTM device, adding the record formed by the IP address corresponding to the domain name not existing on the GTM device to the GTM device, thereby dynamically adding the domain name record. .
  • the increase request is a static increase request, determine whether the domain name in the static increase request exists on the GTM device.
  • the static increase request is set by the user.
  • the static increase request includes at least a domain name, an IP address corresponding to the domain name, and a record type.
  • the record type refers to the resources related to each domain name.
  • the static increase request may further include increasing the type of the request, the port number corresponding to the IP address, and TTL (Time). To Live Retention time) and so on.
  • TTL Time To Live Retention time
  • the domain name on the GTM device and the IP address corresponding to each domain name are listed to form a mapping relationship between the domain name and the IP address.
  • the domain name in the static addition request is compared with the domain name in the mapping relationship table to determine whether the domain name should exist on the GTM device. It is to be understood that the manner of determining whether the domain name already exists on the GTM device is not limited thereto, and is not limited herein.
  • the record type includes an A record and a CNAME record
  • the A (Address) record is a record for specifying an IP address corresponding to the domain name.
  • a CNAME record is an alias record that is used to record multiple domain names to the same computer. Since the static addition operation corresponding to the A record and the CNAME record is different, if the domain name does not exist on the GTM device, the record formed by the domain name and the corresponding IP address is added to the GTM device according to the corresponding record type.
  • the domain name already exists on the GTM device it is necessary to further determine whether the IP address corresponding to the domain name in the static increase request already exists on the GTM device, and if the IP address already exists, there is no need to repeatedly add, if If the IP address does not exist on the GTM device, the record formed by adding the corresponding IP address to the domain name on the GTM device is required, so that the static addition of the domain name record is implemented.
  • the dynamic/static increase completion prompt is displayed to facilitate the user. Understand the completion status of the operation and maintenance configuration operations on the GTM device. It can be understood that, in order to facilitate the user to grasp the real-time progress of the dynamic/static increase operation, a progress bar, a percentage of completion, and the like may be set on the human-computer interaction interface to prompt the user to complete the progress.
  • step S103 it is a schematic flowchart corresponding to step S103 when the operation request in FIG. 1 is a deletion request. As shown in the figure, step S103 specifically steps S301 to S303.
  • S301 Determine whether the deletion request is a dynamic deletion request or a static deletion request, where the dynamic deletion request includes a domain name, and at least one IP address corresponding to the domain name, where the static deletion request includes a domain name, and the The IP address of the domain name one by one.
  • the domain name may be confirmed by querying whether the domain name exists on the GTM device. If the domain name exists on the GTM device, the configuration information corresponding to the query result may be selected. The IP address corresponding to the domain name is selected, or a pull-down menu is set in the configuration information corresponding to the query result for the user to select the type of the deletion request, etc., thereby forming a deletion request.
  • the deletion request is a dynamic deletion request and a static deletion request.
  • deletion request is a dynamic deletion request, clear the record formed by the domain name and the IP address on the GTM device.
  • the dynamic deletion request is set by the user.
  • the dynamic deletion request includes a domain name, an IP address corresponding to the domain name, and a record type.
  • the IP address corresponding to the domain name may be multiple.
  • the mapping between the domain name and the IP address forms a record. Therefore, according to the mapping relationship between the domain name and the IP address, the record corresponding to a domain name can include static records and dynamic records, and dynamic records are generated at the same time, so static records are generated.
  • the deletion request is a dynamic deletion request, it is required to determine whether the record corresponding to the domain name contains a static record.
  • the static record in the record corresponding to the domain name needs to be dynamically recorded on the GTM device.
  • the static record can be separated from the dynamic record by the record type.
  • the domain name on the GTM device and the IP address corresponding to each domain name are listed to form a mapping relationship between the domain name and the IP address, and the domain name and IP address in the request and the domain name and IP in the mapping relationship table are dynamically deleted. The addresses are compared one by one, thereby separating the static record from the dynamic record, and deleting the separated static record and dynamic record.
  • the dynamic deletion request includes three records corresponding to the domain name A, and the three records respectively correspond to the three IP addresses B, C, and D of the domain name A.
  • the mapping relationship between the domain name A and the IP addresses B and C forms a dynamic record
  • the mapping relationship between the domain name A and the IP address D forms a static record.
  • the IP address B and C corresponding to the domain name A on the GTM device are separated from the IP address D corresponding to the domain name A by the mapping between the domain name and the IP address on the GTM device, so that the dynamic record includes the domain name A and the corresponding IP address.
  • Addresses B, C, and make the static record include the domain name A and the corresponding IP address D, and delete the domain name A and the corresponding IP address D from the GTM device, and the domain name A and the corresponding IP address B, C from the GTM device Delete on.
  • the record corresponding to the domain name in the dynamic deletion request may also be only in the dynamic record.
  • the dynamic deletion request includes only the domain name A and the two IP addresses B and C corresponding to the domain name A, and the domain name A and the IP address B and C. The mapping relationship between them forms a dynamic record. At this time, the dynamic deletion request does not contain static records, so there is no need to separate.
  • the number of IP addresses corresponding to the domain name A on the GTM device is usually greater than or equal to the number of IP addresses in the dynamic record.
  • the dynamic record corresponding to the domain name A in the dynamic deletion request input by the user includes the IP address B.
  • C and the dynamic record corresponding to the domain name A on the GTM device includes the IP address B, C, and E.
  • the dynamic deletion request input by the user needs to be partially deleted from the GTM device, that is, the IP address B corresponding to the domain name A is deleted.
  • C the IP address E corresponding to the domain name A is reserved.
  • the dynamic deletion request is to delete the IP addresses B, C, and E in all the dynamic records corresponding to the domain name A
  • the overall deletion is required according to the dynamic deletion request input by the user, that is, the IP address B corresponding to the domain name A is deleted. C, E.
  • deletion request is a static deletion request, clear the record formed by the domain name and the IP address on the GTM device.
  • the deletion request corresponds to the static record
  • the dynamic record generation process does not generate the dynamic record
  • the deletion request is a static deletion request
  • the static record and the corresponding The record formed by the IP address is directly deleted from the GTM device, and the IP address D corresponding to the domain name A is deleted from the GTM device.
  • the dynamic/static deletion completion prompt is displayed to facilitate the user. Understand the completion status of the operation and maintenance configuration operations on the GTM device. It can be understood that, in order to facilitate the user to grasp the real-time progress of the dynamic/static deletion operation, a progress bar, a percentage of completion, and the like may be set on the human-computer interaction interface to prompt the user to complete the progress.
  • the operation request is a modification request, modify configuration information on the GTM device, where the configuration information corresponds to a domain name.
  • step S104 it is a schematic flowchart corresponding to step S104 when the operation request in FIG. 1 is a modification request. As shown in the figure, step S104 specifically steps S401 to S403.
  • the domain name may be confirmed by querying whether the domain name exists on the GTM device. If the domain name exists on the GTM device, the query result may be selected by querying the query result. Corresponding to the domain name configuration item to select, or in the configuration information corresponding to the query result setting drop-down menu for the user to select the type of the modification request, etc. to form a modification request.
  • the modification request is a dynamic modification request and a static modification request.
  • the domain name or the IP address is confirmed to exist on the GTM device.
  • the query result includes configuration information corresponding to the domain name, and the configuration information includes a plurality of configuration items and modification information of the corresponding configuration item.
  • the configuration item includes a plurality of IP addresses corresponding to the domain name, a record type, an analysis algorithm, and the like.
  • each configuration item is followed by a check box for the user to select.
  • the configuration information further includes modification information of the corresponding configuration item, so as to modify the configuration item in the domain name corresponding configuration information on the GTM device according to the modification information.
  • the configuration item includes the IP address B and C, and the modification information is to modify the IP address B to the IP address D and the IP address C to the IP address E, thereby completing the dynamic modification of the configuration information corresponding to the domain name.
  • the modification request is a static modification request
  • the configuration item corresponding to the domain name is modified on the GTM according to the modification item and the modification information in the static modification request, so as to complete the static modification of the configuration information corresponding to the domain name.
  • the configuration item that needs to be modified by the domain name is found on the GTM device according to the static modification request input by the user, and then the configuration item of the domain name on the GTM device is modified according to the modification information.
  • the dynamic/static modification completion prompt is displayed to facilitate the user. Understand the completion status of the operation and maintenance configuration operations on the GTM device. It can be understood that, in order to facilitate the user to grasp the real-time progress of the dynamic/static modification operation, a progress bar, a percentage of completion, and the like may be set on the human-computer interaction interface to prompt the user to complete the progress.
  • the embodiment of the present invention determines whether the operation request is an increase request, a delete request, or a modification request, and if the operation request is an increase request, adding a record on the GTM device, if the operation request is deleted Request to delete the record on the GTM device. If the operation request is a modification request, modify the configuration information corresponding to the domain name on the GTM device.
  • the embodiment of the present invention divides an operation request into an increase request, a delete request, or a modify request, and performs corresponding processing operations on different operation requests, thereby implementing automatic operation and maintenance management, improving efficiency, and improving user experience of the GTM device. .
  • FIG. 5 is a schematic flowchart of a GTM device operation and maintenance management method according to another embodiment of the present invention. As shown, the method includes steps S501-S506.
  • the query In order to facilitate the user to perform a domain name query operation on the GTM device, not only can the query be performed in a database other than the GTM device as described above, but the user can also query from the GTM device by inputting a query request. If the user can input a query request on the human-computer interaction interface, the query request may include key search information such as a domain name or an IP address, which is not limited herein. After receiving the query request input by the user, detecting whether the domain name in the query request exists on the GTM device to obtain a query result.
  • key search information such as a domain name or an IP address
  • the query result displays configuration information such as several IP addresses, parsing algorithms, and record types corresponding to the domain name for the user to view. It can be understood that if the domain name does not exist on the GTM device, the query result is blank. Further, in order to perform related operations such as adding, deleting, or modifying the domain name record, the user may perform related configurations of the IP address, the parsing algorithm, and the record type corresponding to the domain name in the query result. The item is set to a tick option for the user to select to generate an operation request to facilitate related operation and maintenance management operations on the GTM device.
  • the operation request is an increase request, add a record on the GTM device, where the record is used to identify a mapping relationship between a domain name and an IP address.
  • the operation request is a modification request, modify configuration information on the GTM device, where the configuration information corresponds to a domain name.
  • Steps S503 to S506 are as described above, and are not described herein again.
  • the query result is obtained according to the query request input by the user, and the query result is used for the user to operate to generate an operation request, and the query is performed on the GTM device according to the domain name in the query request to obtain the query result.
  • the configuration result of the domain name corresponding to the IP address, the resolution algorithm, and the record type will be displayed. For example, before the operation is added, the user can intuitively see whether the domain name of the added request and the IP address corresponding to the domain name already exist. On the GTM device, it can save the judgment process in the increased operation. For example, before deleting or modifying the operation, it is necessary to pre-query that the domain name exists on the GTM device for subsequent deletion or modification operations.
  • FIG. 6 is a schematic block diagram of a terminal according to an embodiment of the present invention.
  • the terminal 60 in this embodiment as shown in the figure includes a first judging unit 61, an adding unit 62, a deleting unit 63, and a modifying unit 64.
  • the first determining unit 61 is configured to determine, according to an operation request input by the user, a type of the operation request, where the type of the operation request includes a dynamic operation request and a static operation request.
  • the adding unit 62 is configured to: if receiving an operation request input by the user, determine whether the operation request is an increase request, a delete request, or a modification request;
  • the deleting unit 63 is configured to delete the record on the GTM device if the operation request is a deletion request;
  • the modifying unit 64 is configured to modify configuration information on the GTM device if the operation request is a modification request, where the configuration information corresponds to a domain name.
  • the adding unit 62 includes a second determining unit 621 and an adding unit 622.
  • the second determining unit 621 is configured to determine whether the increase request is a dynamic increase request or a static increase request, where the dynamic increase request includes a domain name, at least one IP address corresponding to the domain name, and the static increase request includes a domain name And an IP address corresponding to the domain name, and a record type, and if the increase request is a dynamic increase request, determining whether the domain name exists on the GTM device;
  • the adding unit 622 is configured to add a record formed by the domain name and the corresponding IP address on the GTM device if the domain name does not exist on the GTM device;
  • the second determining unit 621 is further configured to: if the domain name exists on the GTM device, determine whether each of the IP addresses exists on the GTM device;
  • the adding unit 622 is further configured to add, on the GTM device, a record formed by the domain name and an IP address that is not present on the GTM device;
  • the second determining unit 621 is further configured to: if the add request is a static add request, determine whether the domain name in the static increase request exists on the GTM device;
  • the adding unit 622 is further configured to: if the domain name does not exist on the GTM device, add a record formed by the domain name and the corresponding IP address on the GTM device according to the record type.
  • the deletion unit 63 includes a third determination unit 631, and a cleaning unit 632.
  • the third determining unit 631 is configured to determine whether the deletion request is a dynamic deletion request or a static deletion request, where the dynamic deletion request includes a domain name, and at least one IP address corresponding to the domain name, where the static deletion request includes a domain name, and an IP address corresponding to the domain name;
  • the cleaning unit 632 is configured to: if the deletion request is a dynamic deletion request, clear the record formed by the domain name and the IP address on the GTM device, and clean the GTM device if the deletion request is a static deletion request a record formed by the domain name and the IP address, if the deletion request is a static deletion request, the deleting unit is further configured to: use an IP address corresponding to the domain name in the static record from the GTM device delete.
  • the modification unit 64 includes a fourth determination unit 641 and a revision unit 642.
  • the fourth determining unit 641 is configured to determine whether the modification request is a dynamic modification request or a static modification request, where the dynamic modification request or the static modification request includes a modification item in the configuration information and a modification corresponding to the modification item. information;
  • the revising unit 642 is configured to, if the request is a dynamic modification, modify the configuration information corresponding to the domain name on the GTM device according to the modification item and the modification information, and if the request is a static modification, according to the modification item Modifying the configuration information corresponding to the domain name on the GTM device with the modification information.
  • the first determining unit 61 determines whether the operation request is an increase request, a delete request, or a modification request, and if the operation request is an increase request, the GTM device is added by the adding unit 62. The record is added. If the operation request is a deletion request, the deletion unit 63 deletes the record on the GTM device. If the operation request is a modification request, the modification unit 64 modifies the configuration information corresponding to the domain name on the GTM device.
  • the embodiment of the present invention divides an operation request into an increase request, a delete request, or a modify request, and performs corresponding processing operations on different operation requests, thereby implementing automatic operation and maintenance management, improving efficiency, and improving user experience of the GTM device. .
  • FIG. 10 is a schematic block diagram of a terminal according to another embodiment of the present invention.
  • the terminal 70 in this embodiment as shown in the figure includes a detecting unit 71, a display unit 72, a first judging unit 73, an adding unit 74, a deleting unit 75, and a modifying unit 76.
  • the detecting unit 71 is configured to: if receiving a query request input by the user, detecting whether a domain name in the query request exists on the GTM device to obtain a query result.
  • the displaying unit 72 is configured to display the query result for the user to operate to generate the operation request, and the query result includes configuration information corresponding to the domain name.
  • the first determining unit 73 is configured to: if receiving an operation request input by the user, determine whether the operation request is an increase request, a delete request, or a modification request;
  • the adding unit 74 is configured to add a record on the GTM device, where the operation request is an increase request, and the record is used to identify a mapping relationship between a domain name and an IP address;
  • the deleting unit 75 is configured to delete the record on the GTM device if the operation request is a deletion request;
  • the modifying unit 76 is configured to modify configuration information on the GTM device if the operation request is a modification request, where the configuration information corresponds to a domain name.
  • the query result obtained by the query unit 71 is obtained in advance according to the query request input by the user, and the query result is used for the user to operate to generate an operation request, and the query is performed on the GTM device according to the domain name in the query request.
  • the query result is obtained, and the configuration item and the configuration information such as the IP address, the parsing algorithm, and the record type of the domain name are displayed by the display unit 72 in the query result.
  • the user can intuitively see the domain name and the domain name of the added request. Whether the corresponding IP address already exists on the GTM device, thereby saving the judgment process in the increased operation. For example, before deleting or modifying the operation, it is necessary to pre-query that the domain name exists on the GTM device for subsequent deletion or modification operations.
  • the units described in the embodiments of the present invention may also be stored in a computer readable storage medium if they are implemented in the form of software functional modules and sold or used as separate products. Based on such understanding, the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions.
  • a computer device (which may be a personal computer, server, or network device, etc.) is caused to perform all or part of the methods described in various embodiments of the present invention.
  • the storage medium includes a USB flash drive, a removable hard disk, a read-only memory (ROM), and a random access memory (RAM, Random). Access Memory)
  • RAM random access memory
  • embodiments of the present invention also describe a computer readable storage medium having one or more programs, the one or more programs being executable by one or more processors to implement the following steps: Receiving an operation request input by the user, determining whether the operation request is an increase request, a delete request, or a modification request; if the operation request is an increase request, adding a record on the GTM device, where the record is used to identify a domain name and an IP address. The mapping relationship of the address; if the operation request is a deletion request, the record is deleted on the GTM device; if the operation request is a modification request, the configuration information is modified on the GTM device, and the configuration information corresponds to the domain name.
  • the adding a record on the GTM device includes the following steps: determining whether the increase request is a dynamic increase request or a static increase request, where the dynamic increase request includes a domain name, at least An IP address corresponding to the domain name, the static increase request includes a domain name, an IP address corresponding to the domain name, and a record type; if the increase request is a dynamic increase request, determining whether the domain name exists On the GTM device; if the domain name does not exist on the GTM device, add a record formed by the domain name and the corresponding IP address on the GTM device; if the domain name exists on the GTM device, determine each of the Whether the IP address exists on the GTM device; the record formed by the domain name and the IP address not existing on the GTM device is added to the GTM device; if the increase request is a static increase request, determining the static Adding whether the domain name in the request exists on the GTM device; if the domain name does not exist on the GTM
  • the deleting the record on the GTM device includes the following steps: determining whether the deletion request is a dynamic deletion request or a static deletion request, where the dynamic deletion request includes a domain name And at least one IP address corresponding to the domain name, the static deletion request includes a domain name, and an IP address corresponding to the domain name; if the deletion request is a dynamic deletion request, the device is cleaned on the GTM device. Recording the domain name and the IP address; if the deletion request is a static deletion request, clear the record formed by the domain name and the IP address on the GTM device.
  • the modifying the configuration information on the GTM device includes the following steps: determining whether the modification request is a dynamic modification request or a static modification request, where the dynamic modification request or the static modification request is And the modification information in the configuration information, and the modification information corresponding to the modification item; if the request is a dynamic modification, the configuration information corresponding to the domain name is revised on the GTM device according to the modification item and the modification information. And if it is a static modification request, the configuration information corresponding to the domain name is revised on the GTM device according to the modification item and the modification information.
  • the one or more programs are further executable by the one or more processors to implement the step of detecting whether a domain name in the query request exists in a GTM device if a query request input by a user is received Up to obtain a query result; displaying the query result for a user operation to generate the operation request, the query result including configuration information corresponding to the domain name.
  • FIG. 11 is a schematic block diagram of a GTM device operation and maintenance management apparatus according to an embodiment of the present invention.
  • the management device 80 includes a memory 81, one or several processors 82, one or several input devices 83, one or several output devices 84.
  • the processor 82, the input device 83, the output device 84, and the memory 81 are connected by a bus 85.
  • the memory 81 is used to store program data with various functions.
  • the data stored in the memory 81 in the embodiment of the present invention includes program data that can be called and run.
  • the memory 81 of the embodiment of the present invention may be a system memory such as volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.), or a combination of the two.
  • the memory 66 of the embodiment of the present invention may also be an external memory outside the system, such as a magnetic disk, an optical disk, a magnetic tape, or the like.
  • the input device 83 is for the user to input an operation request or a query request.
  • the input device 83 of the embodiment of the present invention may include a keyboard, a mouse, a photoelectric input device, a sound input device, a touch input device, and the like.
  • Output device 84 is used to display the results of the query, which may include a display, a display screen, a touch screen, and the like.
  • the processor 82 reads an instruction in the memory 81 and performs an operation according to the instruction: if an operation request input by a user is received, determining whether the operation request is an increase request, a delete request, or a modification request;
  • the operation request is an add request, and a record is added to the GTM device, where the record is used to identify a mapping relationship between a domain name and an IP address; if the operation request is a delete request, the record is deleted on the GTM device;
  • the operation request is a modification request, and the configuration information is modified on the GTM device, and the configuration information corresponds to the domain name.
  • adding the record on the GTM device includes: determining whether the increase request is a dynamic increase request or a static increase request, where the dynamic increase request includes a domain name, at least one The IP address corresponding to the domain name, the static increase request includes a domain name, an IP address corresponding to the domain name, and a record type; if the increase request is a dynamic increase request, determining whether the domain name exists in the GTM If the domain name does not exist on the GTM device, add a record formed by the domain name and the corresponding IP address on the GTM device; if the domain name exists on the GTM device, determine each of the IP addresses.
  • the deleting the record on the GTM device includes: determining whether the deletion request is a dynamic deletion request or a static deletion request, where the dynamic deletion request includes a domain name, and At least one IP address corresponding to the domain name, the static deletion request includes a domain name, and an IP address corresponding to the domain name; if the deletion request is a dynamic deletion request, the domain name is cleared on the GTM device And the record formed by the IP address; if the deletion request is a static deletion request, the record formed by the domain name and the IP address is cleared on the GTM device.
  • the modifying the configuration information on the GTM device includes: determining whether the modification request is a dynamic modification request or a static modification request, where the dynamic modification request or the static modification request includes a modification item in the configuration information and a modification information corresponding to the modification item; if the request is a dynamic modification, the configuration information corresponding to the domain name is revised on the GTM device according to the modification item and the modification information; For the static modification request, the configuration information corresponding to the domain name is revised on the GTM device according to the modification item and the modification information.
  • the processor 82 further performs the following operations: if a query request input by the user is received, detecting whether the domain name in the query request exists on the GTM device to obtain a query result; displaying the query result for the user to operate The operation request is thus generated, and the query result includes configuration information corresponding to the domain name.
  • the disclosed terminal and method may be implemented in other manners.
  • the device device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined. Or it can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device device or unit, or an electrical, mechanical or other form of connection.
  • the units in the terminal in the embodiment of the present invention may be combined, divided, and deleted according to actual needs.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present invention.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present invention contributes in essence or to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included to cause a computer device (which may be a personal computer, terminal, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: U Disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access
  • RAM Random Access

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Selon certains modes de réalisation, la présente invention concerne un procédé de gestion de fonctionnement et de maintenance d'appareil GTM, le procédé comprenant les étapes suivantes : à la réception d'une demande d'opération entrée par un utilisateur, déterminer si la demande d'opération est une demande d'ajout, une demande de suppression ou une demande de modification; si la demande d'opération est une demande d'ajout, ajouter alors, sur un appareil GTM, un enregistrement utilisé pour identifier une relation de mappage entre un nom de domaine et une adresse IP; si la demande d'opération est une demande de suppression, alors supprimer l'enregistrement sur l'appareil GTM; et si la demande d'opération est une demande de modification, alors modifier, sur l'appareil GTM, les informations de configuration correspondant au nom de domaine. Selon certains modes de réalisation, la présente invention concerne également un terminal, un support de stockage lisible par ordinateur et un dispositif de gestion. En classant des demandes d'opération en demandes d'ajout, en demandes de suppression et en demandes de modification, et en exécutant des opérations de traitement correspondant à différentes demandes d'opération, les modes de réalisation de l'invention permettent une gestion automatisée des opérations et de la maintenance, une amélioration de l'efficacité et une expérience utilisateur améliorée d'un appareil GTM.
PCT/CN2017/076520 2016-08-25 2017-03-14 Procédé de gestion d'opération et de maintenance d'appareil gtm, terminal, support de stockage lisible par ordinateur et dispositif de gestion Ceased WO2018036137A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610727301.3 2016-08-25
CN201610727301.3A CN106452831A (zh) 2016-08-25 2016-08-25 一种gtm设备运维管理方法及终端

Publications (1)

Publication Number Publication Date
WO2018036137A1 true WO2018036137A1 (fr) 2018-03-01

Family

ID=58181984

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/076520 Ceased WO2018036137A1 (fr) 2016-08-25 2017-03-14 Procédé de gestion d'opération et de maintenance d'appareil gtm, terminal, support de stockage lisible par ordinateur et dispositif de gestion

Country Status (2)

Country Link
CN (1) CN106452831A (fr)
WO (1) WO2018036137A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106452831A (zh) * 2016-08-25 2017-02-22 平安科技（深圳）有限公司 一种gtm设备运维管理方法及终端
CN113660359B (zh) * 2021-08-25 2024-01-19 北京搜房科技发展有限公司 域名解析记录的管理方法及装置、存储介质及电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090164661A1 (en) * 2007-12-21 2009-06-25 Hostway Corporation System and method for selecting an optimal authoritive name server
CN105354671A (zh) * 2015-11-06 2016-02-24 中国南方电网有限责任公司 通用配置管理系统以及包含该系统的企业级信息系统
CN105635345A (zh) * 2016-02-23 2016-06-01 华为技术有限公司 域名资源记录管理方法和装置
CN106452831A (zh) * 2016-08-25 2017-02-22 平安科技（深圳）有限公司 一种gtm设备运维管理方法及终端

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9864755B2 (en) * 2013-03-08 2018-01-09 Go Daddy Operating Company, LLC Systems for associating an online file folder with a uniform resource locator
CN104468575A (zh) * 2014-12-10 2015-03-25 深圳市共进电子股份有限公司 局域网上实现域名注册的方法与装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090164661A1 (en) * 2007-12-21 2009-06-25 Hostway Corporation System and method for selecting an optimal authoritive name server
CN105354671A (zh) * 2015-11-06 2016-02-24 中国南方电网有限责任公司 通用配置管理系统以及包含该系统的企业级信息系统
CN105635345A (zh) * 2016-02-23 2016-06-01 华为技术有限公司 域名资源记录管理方法和装置
CN106452831A (zh) * 2016-08-25 2017-02-22 平安科技（深圳）有限公司 一种gtm设备运维管理方法及终端

Also Published As

Publication number Publication date
CN106452831A (zh) 2017-02-22

Similar Documents

Publication Publication Date Title
WO2018107610A1 (fr) Procédé, système et dispositif de traitement de données de service, et support d'informations lisible par ordinateur
WO2018205376A1 (fr) Procédé d'interrogation d'informations d'association, terminal, système de gestion de serveur et support de stockage lisible par ordinateur
WO2019100638A1 (fr) Procédé, dispositif et équipement de synchronisation de données, et support d'informations
WO2019037396A1 (fr) Procédé, dispositif et équipement de suppression de compte et support d'informations
WO2018014567A1 (fr) Procédé servant à améliorer les performances d'une machine virtuelle, et terminal, dispositif et support de stockage lisible par ordinateur
WO2017143692A1 (fr) Téléviseur intelligent et son procédé de commande vocale
WO2018120430A1 (fr) Procédé de construction de page, terminal, support de stockage lisible par ordinateur et dispositif de construction de page
WO2019104876A1 (fr) Procédé et système de poussée de produit d'assurance, terminal, terminal client et support d'informations
WO2020224247A1 (fr) Procédé, appareil et dispositif de provenance de données basés sur la chaine de blocs, et support d'informations lisible
WO2015144089A1 (fr) Procédé et appareil de recommandation d'application
WO2018149300A1 (fr) Procédé, appareil et dispositif de détection de probabilité de maladie, et support de stockage lisible par ordinateur
WO2019109521A1 (fr) Procédé, appareil et dispositif de validation d'identité pour un entretien vidéo et support d'enregistrement lisible
WO2015103864A1 (fr) Procédé de gestion de mémoire et terminal linux
WO2019169814A1 (fr) Procédé, appareil et dispositif de génération automatique d'annotation en chinois, et support d'informations
WO2017215298A1 (fr) Procédé, appareil, système et support de stockage lisible par ordinateur de déploiement graphique sur le web
WO2019024219A1 (fr) Procédé et appareil de génération automatique de document, générateur automatique de document et support
WO2017054592A1 (fr) Terminal et procédé d'affichage d'interface
WO2016032021A1 (fr) Appareil et procédé de reconnaissance de commandes vocales
WO2018166314A1 (fr) Procédé, appareil et dispositif d'autorisation de plafond et support d'informations lisible par ordinateur
WO2018233301A1 (fr) Procédé, appareil et dispositif de recommandation de produit et support d'informations lisible par ordinateur
WO2019056733A1 (fr) Procédé de limitation de volume concurrent, serveur d'application, système, et support de stockage
WO2018188196A1 (fr) Procédé de commande de version de données, contrôleur de version de données, dispositif et support de stockage lisible par ordinateur
WO2018090585A1 (fr) Procédé et appareil de mémorisation pour virtualisation de données, serveur et support d'informations
WO2018214599A1 (fr) Procédé et système de rapport de données échelonnables, et support de stockage
WO2014048231A1 (fr) Procédé et appareil de traitement de texte pour dispositif intelligent à écran tactile

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17842563

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 25.6.19).

122 Ep: pct application non-entry in european phase

Ref document number: 17842563

Country of ref document: EP

Kind code of ref document: A1