Address updating method, apparatus, device, and storage medium

Abstract

The application discloses an address updating method, device and equipment and a storage medium, and the method comprises the following steps: determining an address to be updated according to request information of address updating, and performing legality verification and validity verification on the address to be updated; when the legality verification and the validity verification are qualified, performing timeout verification on the address to be updated; and updating the address to be updated according to the request information of cache address updating and a verification result. According to the application, the legality verification and the validity verification are performed on the address to be updated, when the verification is qualified, if the address to be updated is not reported within the expected time, the timeout verification is performed on the address to be updated, and the address to be updated is updated according to the verification result and the request information of cache address updating, so that the flexibility of address updating management is improved.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to an address updating method, apparatus, device, and storage medium. Background Technology

[0002] With the rapid development of the mobile internet, the types and models of business in the telecommunications operator sector are also rapidly diversifying. Along with this diversification, the number of providers of various atomic capabilities is also increasing. Each atomic capability, when layered, provides differentiated capacity and deployment for different capability consumers, resulting in a massive number of capability addresses managed by the system. Adjustments to the deployments of each capability provider and the evolution of the system architecture lead to frequent address changes.

[0003] Currently, to address the diverse address change requests from capability providers, a combination of routing conditions and address lists is typically used. When addresses change, customized condition rules need to be designed based on the specific scenario, and collaboration with the provider is required to modify the specific address information at a specific time. However, this static address management approach suffers from a lack of simplistic management and cannot adapt to individualized needs.

[0004] The above content is only used to help understand the technical solution of the present invention and does not represent an admission that the above content is prior art. Summary of the Invention

[0005] The main objective of this invention is to provide an address update method, apparatus, device, and storage medium, aiming to solve the technical problem of how to improve the flexibility of address update management.

[0006] To achieve the above objectives, the present invention provides an address update method, the address update method comprising the following steps:

[0007] The address to be updated is determined based on the address update request information, and the address to be updated is subjected to legality and validity verification.

[0008] If the legality check and the validity check pass, the address to be updated will be subject to a timeout verification.

[0009] The address to be updated is updated based on the cache address update request information and verification results.

[0010] Optionally, the address to be updated includes a dynamic address to be updated;

[0011] The step of verifying the timeout of the reported address to be updated includes:

[0012] When the reporting time of the dynamic address to be updated exceeds the preset time, wait for the dynamic address to be updated to be reported according to the cache time window;

[0013] When the cache time window expires, the reporting time of the dynamic address to be updated is marked as reporting timeout;

[0014] The historical dynamic addresses are processed, and the dynamic addresses to be updated are verified.

[0015] Optionally, the address to be updated includes a static address to be updated;

[0016] The step of updating the address to be updated based on the request information and verification results of the cached address update includes:

[0017] Upon successful verification, the dynamic address to be updated is updated based on the verification results;

[0018] The dynamic address to be updated and the static address to be updated are updated according to the cache address update request information.

[0019] Optionally, the step of updating the dynamic address to be updated and the static address to be updated based on the cache address update request information includes:

[0020] The request information for updating the cached address is parsed, and the dynamic address to be updated and the static address to be updated are obtained based on the parsing result;

[0021] Perform rule validation on the dynamic address to be updated, and update the dynamic address to be updated to the dynamic address cache area if the rule validation is satisfied;

[0022] When the dynamic address to be updated fails the rule verification, a static rule judgment is performed on the static address to be updated.

[0023] Update the static addresses that meet the static rule criteria to the static address cache.

[0024] Optionally, after the step of updating the dynamic address to be updated based on the verification result when the verification is successful, the method further includes:

[0025] When verification fails, the status of the reported address to be updated will be marked as invalid, and active verification requests will be initiated periodically based on the backup link.

[0026] Optionally, after the step of updating the static address to be updated to the static address cache area that satisfies the static rule judgment, the method further includes:

[0027] The audit data is updated based on the updated static address and the updated dynamic address;

[0028] When the audit data update is completed, the status flag of the address update control table is switched.

[0029] Optionally, the step of determining the address to be updated based on the address update request information, and performing legality and validity checks on the address to be updated, includes:

[0030] The address to be updated is determined based on the address update request information, and the validity of the address to be updated is verified based on the request information and real-time detection information.

[0031] The address to be updated is validated according to the reporting rules.

[0032] In addition, to achieve the above objectives, the present invention also proposes an address updating device, which includes: a verification module, a verification module, and an updating module;

[0033] The verification module is used to determine the address to be updated based on the address update request information, and to perform legality and validity verification on the address to be updated.

[0034] The verification module is used to perform a timeout verification on the address to be updated when the legality check and the validity check are both passed.

[0035] The update module is used to update the address to be updated based on the cache address update request information and verification results.

[0036] In addition, to achieve the above objectives, the present invention also proposes an address update device, the address update device including a memory, a processor, and an address update program stored in the memory and capable of running on the processor, the address update program being configured to implement the address update method as described above.

[0037] In addition, to achieve the above objectives, the present invention also proposes a storage medium storing an address update program, which, when executed by a processor, implements the address update method as described above.

[0038] This invention discloses an address update method, apparatus, device, and storage medium. The method includes: determining the address to be updated based on address update request information, and performing legality and validity checks on the address to be updated; if the legality and validity checks are successful, verifying the reporting timeout of the address to be updated; and updating the address to be updated based on the cached address update request information and the verification result. This invention improves the flexibility of address update management by performing legality and validity checks on the address to be updated. If the address to be updated is not reported within the expected time after passing the checks, a reporting timeout verification is performed on the address to be updated, and the address to be updated is updated based on the verification result and the cached address update request information. Attached Figure Description

[0039] Figure 1 This is a schematic diagram of the structure of the address update device in the hardware operating environment involved in the embodiments of the present invention;

[0040] Figure 2 This is a flowchart illustrating the first embodiment of the address update method of the present invention;

[0041] Figure 3 This is a flowchart illustrating the second embodiment of the address update method of the present invention;

[0042] Figure 4 This is a flowchart illustrating the third embodiment of the address update method of the present invention;

[0043] Figure 5 This is a diagram of the address update management architecture according to an embodiment of the address update method of the present invention;

[0044] Figure 6 This is a service capability deployment architecture diagram of an embodiment of the address update method of the present invention;

[0045] Figure 7 This is a framework diagram of the reporting capability registration and discovery unit according to an embodiment of the address update method of the present invention;

[0046] Figure 8 This is a flowchart of the verification process of the capability information verification unit in an embodiment of the address update method of the present invention.

[0047] Figure 9 This is a diagram of an address data maintenance module according to an embodiment of the address update method of the present invention;

[0048] Figure 10 This is a structural block diagram of the first embodiment of the address updating device of the present invention.

[0049] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0050] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0051] Reference Figure 1 , Figure 1 This is a schematic diagram of the address update device structure of the hardware operating environment involved in the embodiments of the present invention.

[0052] like Figure 1As shown, the address update device may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen, and optionally, it may also include a standard wired interface or a wireless interface. In this invention, the wired interface of the user interface 1003 may be a USB interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wireless-Fidelity (Wi-Fi) interface). The memory 1005 may be high-speed random access memory (RAM) or non-volatile memory (NVM), such as a disk storage device. The memory 1005 may also optionally be a storage device independent of the aforementioned processor 1001.

[0053] Those skilled in the art will understand that Figure 1 The structure shown does not constitute a limitation on the address update device and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0054] like Figure 1 As shown, the memory 1005, which is identified as a computer storage medium, may include an operating system, a network communication module, a user interface module, and an address update program.

[0055] exist Figure 1 In the address update device shown, the network interface 1004 is mainly used to connect to the backend server and communicate with the backend server; the user interface 1003 is mainly used to connect to the user equipment; the address update device calls the address update program stored in the memory 1005 through the processor 1001 and executes the address update method provided in this embodiment of the invention.

[0056] Based on the above hardware structure, an embodiment of the address update method of the present invention is proposed.

[0057] Reference Figure 2 , Figure 2 This is a flowchart illustrating the first embodiment of the address update method of the present invention, which presents the first embodiment of the address update method of the present invention.

[0058] Step S10: Determine the address to be updated based on the address update request information, and perform legality and validity checks on the address to be updated.

[0059] It should be noted that the execution subject of this embodiment may be a computer software service device with data processing, network communication and program running functions, such as an address update management architecture, or other electronic devices that can achieve the same or similar functions. This embodiment does not limit this.

[0060] It should be noted that this solution uses a two-way interactive dynamic address management mechanism, combined with static addresses as a foundation, to achieve the management of capability provider deployment and architecture, dynamic registration and adjustment of address and routing relationships, and realize the self-service capability of the capability management system. At the same time, it solves the problem of smooth system service capability in environments with poor communication stability, such as cross-center and cross-WAN, where the traditional one-way registration and discovery mechanism is used.

[0061] It should be noted that the address update management architecture in this embodiment includes an address management unit for capability providers, a capability registration and discovery unit for reporting capabilities, and a capability information verification unit for issuing capabilities. Firstly, the address management unit for capability providers, taking into account the multi-center, multi-cluster architecture of commonly used systems, the characteristics of multi-dimensional keyword routing in business operations, multi-scenario and multi-environment concepts, and an integrated rule engine, implements a flexible deployment management model for capability providers. This facilitates rapid switching, smooth rolling upgrades, and flexible management for capability providers, and is constituted by a flexible provider deployment architecture and routing policy management model built on an expression engine. It allows for flexible definition of the number of capability provider clusters, their locations, service lists, routing policies, address element composition, and rules, etc. This allows for the formation of a set of static address rules, enabling rapid location of the primary, backup, and emergency addresses for specific requests based on the interface name and element parameters. Secondly, the capability registration and discovery unit enables capability providers to proactively report access address information for each cluster and environment via standard API interfaces. This reported information automatically and smoothly overwrites static management information, distributing address update management across capability providers. Several reporting modes are included: a) routing parameter reporting, b) capability list updates, c) capability metadata updates, and d) instantiated address reporting. These reported information supplements, overwrites, and revises static rules, forming a dynamic address and rule list. Thirdly, the capability information verification unit addresses the shortcomings of traditional one-way registration and discovery mechanisms, reducing dynamic service interruptions caused by network or congestion anomalies. It supports proactive verification capabilities across multiple network routes. When proactive reporting and heartbeats are abnormally interrupted due to network issues, verification requests can be proactively initiated. Independent network routing strategies are supported to avoid misjudgments leading to abnormal interruptions, forming a two-way closed-loop capability to ensure system stability.

[0062] For ease of understanding, please refer to Figure 5 To explain, Figure 5The address update management architecture diagram shows that the processing functions of the capability information verification unit and the capability registration discovery unit include reporting information processing, proactive information verification, dynamic session management, and dynamic information caching. The address management unit of the capability provider integrates address policy management, cluster management, and routing management based on the expression engine.

[0063] It is understandable that the address management unit of the capability provider calculates the configured static address or obtains the addressing information of the dynamic address based on the routing calculation, that is, it obtains the configured static address or obtains the addressing information of the dynamic address based on the address update request information combined with the static policy information.

[0064] It is understood that the request information for address update can be request information such as IP address, port and service name, and the static policy information configuration can be policy information such as some rate limiting rules. This embodiment does not limit this.

[0065] For ease of understanding, please refer to Figure 6 To explain, Figure 6 The service capability deployment architecture diagram shows three central services: Center A, Center B, and Center C. Center A, Center B, and Center C respectively contain Service A, Service B, and Service C. The service capability deployment architecture diagram also includes the management capabilities for address proactive registration and verification services.

[0066] It should be noted that the address management unit of the capability provider includes a deployment architecture management module, a routing policy element management module, a routing policy expression engine module, and a routing calculation module.

[0067] The deployment architecture management module includes:

[0068] The center consists of: center A, center B, and center C.

[0069] Service List: Center A: Service A, Service B.

[0070] Center B: Service B, Service C.

[0071] Center C: Service A, Service C.

[0072] Center information: center description, center location, average latency, center capacity.

[0073] Central relationship: peer takeover, zoned service.

[0074] Central address: Address A, Address B, etc.

[0075] The routing policy element management module includes:

[0076] Version number: Acquisition method: URI, location 1, key elements.

[0077] Service name: Acquisition method: URL, location 2, key elements.

[0078] User Area: Acquisition Method: Message, Parameters: UserArea, Key Elements.

[0079] Environment identifier: Acquisition method: Message, Parameter: EnvFlag, Non-critical element.

[0080] The routing policy expression engine module utilizes an expression engine based on a "service flow definition language" to support dynamic judgment and flexible definition of routing rules, for example:

[0081] If the requested service name is A, and the region is A1, A2, or A3, then access center A.

[0082] The requested service name is A, and the regions are A3, A4, and A5, which are access centers C.

[0083] The requested service name is B, the region is B1, and the access center is A.

[0084] ...

[0085] The routing calculation involves using the relevant information of the request, combined with static policy information, to calculate and retrieve the configured static address or obtain the addressing information for the dynamic address.

[0086] Furthermore, to ensure the security of address updates, step S10 in this embodiment may include:

[0087] The address to be updated is determined based on the address update request information, and the validity of the address to be updated is verified based on the request information and real-time detection information.

[0088] The address to be updated is validated according to the reporting rules.

[0089] It should be noted that the reporting capability registration and discovery unit verifies the validity and legality of the address to be updated. That is, it verifies the validity of the address to be updated based on the request information and heartbeat information (real-time detection information) as references. According to the reporting data rules, it verifies the legality of the format, value range, and completeness of the reported data. Non-compliant address information is not entered into the database and abnormal information is recorded.

[0090] Step S20: When the legality check and the validity check are passed, the reporting timeout of the address to be updated is checked.

[0091] It should be noted that the address provider will proactively report the address information to be updated on a regular basis. If the reporting time is exceeded, the reporting timeout verification will be carried out according to the capability information verification unit.

[0092] It should be noted that the capability information verification unit performs reporting timeout verification based on the call management module of the reporting capability registration discovery unit.

[0093] It should be noted that the reporting capability registration and discovery unit includes a two-level address management system, reporting element information, session state management, reporting information verification, and address policy management.

[0094] The two-tier address management system distinguishes between static and dynamic addresses. Static addresses are generated by the deployment architecture in conjunction with address rules and can be permanently defined based on special circumstances. Dynamic addresses consist of element parameters and address information reported in real time by the capability provider.

[0095] The reported information includes:

[0096] Routing parameter reporting: Reports routing parameter information for each cluster to update or override static routing rules. For example, if partner A adjusts the routing parameters of center C, the uploaded content would be: Center C, Regions: A3, A4, A5, A6.

[0097] Capability List Update: Report the service capability list for each cluster, supporting the addition or deletion of capabilities. For example, if service D is added to center A, the following should be reported: Center A: Service A, Service B, Service C, and related center changes.

[0098] Capability metadata update: Reports the description, protocol, and constraint information of newly added or revised interfaces, supporting both adding and revising interfaces. For example, if center A adds service D, it reports the interface name, version number, interface protocol, and interface description of service D.

[0099] Instantiated address reporting: Directly reports the specific address containing the specified elements, achieving high-priority coverage of static routing rules and supporting differentiated deployments across multiple centers. For example, if service D forces routing to center A and uses a special address, then report service D: address A1.

[0100] Among them, session state management: manages the status of the capability provider for connection reporting, and uses the reporting request and heartbeat information as a reference to ensure that the reporting address is valid and automatically marks the expired address.

[0101] Among them, the reporting information verification: based on the reporting data rules, the legality of the reported data format, value range, integrity, etc. is verified, and non-compliant address information is not entered into the database and abnormal information is recorded.

[0102] Address policy management: Based on the different address management policies of each capability provider, it supports multiple modes such as static management, asynchronous reporting, and hybrid management, and supports different address applications and routing policies when the session fails due to timeout.

[0103] For ease of understanding, please refer to Figure 7 To explain, Figure 7 The diagram shows the framework for reporting capability registration and discovery units. Address registration in the diagram includes dynamic address information and static address information. Dynamic address information includes service list, routing rules, metadata, and instance address. Static address information includes deployment cluster, routing elements, expressions, and expression rule engine.

[0104] Step S30: Update the address to be updated according to the cache address update request information and verification results.

[0105] Understandably, the verification result can be a callback message used to determine the current state of the service, and the status of the address to be updated can be updated based on the verification result.

[0106] It should be noted that the address update management architecture also includes an address data maintenance module, used to keep data updates synchronized with the cache. The dynamic and static address rule data in the address data maintenance module together form the basic data for address routing. The data in the cache consists of two sets of data, A and B, and control data. The control data determines which set of data, A or B, is providing service and which is being maintained, ensuring the isolation of data during maintenance. Simultaneously, the control data also stores audit information to ensure consistency between the cached and stored data.

[0107] This embodiment determines the address to be updated based on the address update request information and performs legality and validity checks on the address to be updated. If the legality and validity checks pass, a timeout verification is performed on the address to be updated. The address to be updated is then updated based on the cached address update request information and the verification results. This embodiment improves the flexibility of address update management by performing legality and validity checks on the address to be updated. If the address to be updated is not reported within the expected time after passing the checks, a timeout verification is performed on the address to be updated, and the address is updated based on the verification results and the cached address update request information.

[0108] Reference Figure 3 , Figure 3 This is a flowchart illustrating the second embodiment of the address update method of the present invention, based on the above. Figure 2 The first embodiment shown is followed by a second embodiment of the address update method of the present invention.

[0109] In the second embodiment, step S20 includes:

[0110] Step S201: When the reporting time of the dynamic address to be updated exceeds the preset time, wait for the dynamic address to be updated to be reported according to the cache time window;

[0111] Step S202: When the cache time window expires, mark the reporting time of the dynamic address to be updated as a reporting timeout;

[0112] Step S203: Process the historical dynamic address and verify the dynamic address to be updated.

[0113] Understandably, traditional address registration and discovery management methods rely on one-way communication. In scenarios with unstable networks, this makes it difficult to guarantee the stability of address management, easily leading to momentary outages due to short-term congestion timeouts. Proactive downlink address verification provides the control module with proactive management capabilities, overcoming the shortcomings of passive management methods that rely solely on timeouts. Furthermore, it offers backup solutions for independent network links or multi-address control, mitigating the network stability risks associated with a single registration link.

[0114] It should be noted that the session management module is based on active address reporting and heartbeat maintenance update timestamps. When the update time expires, the system will wait for another cache time window. When the window expires, the status of the corresponding provider will be marked as timed out.

[0115] It should be noted that when the address information proactively reported by the provider is marked as timed out, the historical dynamic addresses are either invalidated or retained according to the address policy, and at the same time, a verification operation is initiated against the address provider.

[0116] In this embodiment, when the reporting time of the dynamic address to be updated exceeds a preset time, the system waits for the dynamic address to be updated to be reported according to a cache time window; when the cache time window expires, the reporting time of the dynamic address to be updated is marked as a timeout; historical dynamic addresses are processed, and the dynamic address to be updated is verified. This embodiment, after waiting for one cache time window, if the address provider still does not actively report address information, marks the address provider's reporting time as timeout and autonomously verifies the dynamic address to be updated, thereby intelligentizing the address update management architecture and avoiding instability risks such as abnormal interruptions.

[0117] Reference Figure 4 , Figure 4 This is a flowchart illustrating the third embodiment of the address update method of the present invention, based on the above. Figure 2 The first embodiment shown is followed by a third embodiment of the address update method of the present invention.

[0118] In the third embodiment, step S30 further includes:

[0119] Step S301: When the verification is successful, update the dynamic address to be updated according to the verification result;

[0120] Step S302: Update the dynamic address to be updated and the static address to be updated according to the cache address update request information.

[0121] Understandably, after successful verification, the status of the dynamic address to be updated will be updated and address maintenance operations will be performed.

[0122] It should be noted that the request information for updating the cached address is parsed, and the dynamic address to be updated is matched according to the parsing result and the verification rules. If no match is found, the static address information to be updated is matched according to the execution expression, and the static address and dynamic address to be updated that meet the requirements are updated.

[0123] Furthermore, in order to achieve smooth updates of dynamic and static addresses and seamless switching of requests, step S302 in this embodiment may further include:

[0124] The request information for updating the cached address is parsed, and the dynamic address to be updated and the static address to be updated are obtained based on the parsing result;

[0125] Perform rule validation on the dynamic address to be updated, and update the dynamic address to be updated to the dynamic address cache area if the rule validation is satisfied;

[0126] When the dynamic address to be updated fails the rule verification, a static rule judgment is performed on the static address to be updated.

[0127] Update the static addresses that meet the static rule criteria to the static address cache.

[0128] It should be noted that the request information is parsed based on the metadata. Based on the parsed elements and the rule engine, the dynamic address to be updated is obtained. The dynamic address to be updated is then checked one by one according to the rule priority order until a dynamic address that meets the rule conditions is obtained. The dynamic address to be updated is then updated to the dynamic address cache.

[0129] It should be noted that when no dynamic address to be updated is matched, the static address to be updated is obtained based on the element, and the judgment is made according to the execution expression of the static rule until a static address to be updated is matched and the static address to be updated is updated to the static address cache.

[0130] Furthermore, to address the network stability risks posed by a single registration link, this embodiment may further include the following step after S301:

[0131] When verification fails, the status of the reported address to be updated will be marked as invalid, and active verification requests will be initiated periodically based on the backup link.

[0132] It is understood that this embodiment provides a backup solution for independent network links or multi-address management, which solves the network stability risks caused by a single registration link.

[0133] For ease of understanding, please refer to Figure 8 To explain, Figure 8 The flowchart for the verification process of the capability information verification unit is shown. The flowchart shows the verification of dynamic address information after the reporting timeout, and the active verification is initiated again based on the backup link after the verification fails.

[0134] Furthermore, in order to achieve smooth updates of dynamic and static addresses and seamless switching of requests, this embodiment may further include the following after step S302:

[0135] The audit data is updated based on the updated static address and the updated dynamic address;

[0136] When the audit data update is completed, the status flag of the address update control table is switched.

[0137] It should be noted that the control data stores audit information to ensure the consistency of data in the cache and storage. When updating the dynamic address to be updated and the static address to be updated to their respective cache areas, the audit data in the control data is updated. When all data has been updated, the status flag of the address update control table is switched, and at this time, new requests will be routed to access the new data.

[0138] It should be noted that when the timeout period for a request to update the maximum cache address is twice the timeout period, the data maintenance will automatically clear the old data cache to prepare for the next data update.

[0139] For ease of understanding, please refer to Figure 9 To explain, Figure 9 The diagram shows the address data maintenance module. In the diagram, routing requests are parsed, scheduling is performed according to the rule engine, elements are parsed, dynamic address matching and static address matching are performed based on the parsing results, the matching results are cached and stored in data A or data B respectively, control data is updated, and data maintenance is performed to facilitate the next update.

[0140] In this embodiment, upon successful verification, the dynamic address to be updated is updated based on the verification result; and the dynamic address to be updated and the static address to be updated are updated based on the cache address update request information. This embodiment updates the status of the dynamic address to be updated based on the query result, and updates the dynamic address to be updated and the dynamic address to be updated based on the request information, thereby achieving smooth updates of dynamic and static addresses and seamless switching of requests.

[0141] Furthermore, this embodiment of the invention also proposes a storage medium storing an address update program, which, when executed by a processor, implements the address update method described above.

[0142] In addition, refer to Figure 10 The present invention also proposes an address updating device, which includes: a verification module 10, a verification module 20 and an updating module 30;

[0143] The verification module 10 is used to determine the address to be updated based on the address update request information, and to perform legality verification and validity verification on the address to be updated.

[0144] The verification module 20 is used to perform a timeout verification on the address to be updated when the legality verification and the validity verification are qualified.

[0145] The update module 30 is used to update the address to be updated based on the cache address update request information and the verification result.

[0146] This embodiment determines the address to be updated based on the address update request information and performs legality and validity checks on the address to be updated. If the legality and validity checks pass, a timeout verification is performed on the address to be updated. The address to be updated is then updated based on the cached address update request information and the verification results. This embodiment improves the flexibility of address update management by performing legality and validity checks on the address to be updated. If the address to be updated is not reported within the expected time after passing the checks, a timeout verification is performed on the address to be updated, and the address is updated based on the verification results and the cached address update request information.

[0147] Based on the first embodiment of the address update device of the present invention described above, a second embodiment of the address update device of the present invention is proposed.

[0148] In this embodiment, the verification module 20 is used to wait for the dynamic address to be updated to be reported according to the cache time window when the reporting time of the dynamic address to be updated exceeds a preset time.

[0149] Furthermore, the verification module 20 is also used to mark the reporting time of the dynamic address to be updated as a reporting timeout when the cache time window expires.

[0150] Furthermore, the verification module 20 is also used to process historical dynamic addresses and verify the dynamic address to be updated.

[0151] Furthermore, the update module 30 is also used to update the dynamic address to be updated based on the verification result when the verification is successful.

[0152] Furthermore, the update module 30 is also used to update the dynamic address to be updated and the static address to be updated according to the cache address update request information.

[0153] Furthermore, the update module 30 is also used to parse the request information for updating the cached address, and obtain the dynamic address to be updated and the static address to be updated based on the parsing result.

[0154] Furthermore, the update module 30 is also used to perform rule verification on the dynamic address to be updated, and update the dynamic address to be updated to the dynamic address cache area if the rule verification is satisfied.

[0155] Furthermore, the update module 30 is also used to perform static rule judgment on the static address to be updated when the dynamic address to be updated fails the rule verification.

[0156] Furthermore, the update module 30 is also used to update the static address to be updated to the static address cache area if it meets the static rule judgment.

[0157] Furthermore, the update module 30 is also used to mark the status of the reported address to be updated as invalid when the verification fails, and to periodically initiate active verification requests based on the backup link.

[0158] Furthermore, the update module 30 is also used to update the audit data based on the updated static address and the updated dynamic address.

[0159] Furthermore, the update module 30 is also used to switch the status flag of the address update control table when the audit data update is completed.

[0160] Furthermore, the verification module 10 is also used to determine the address to be updated based on the address update request information, and to detect the validity of the address to be updated based on the request information and real-time detection information.

[0161] Furthermore, the verification module 10 is also used to perform a legality verification on the address to be updated according to the reporting rules.

[0162] Other embodiments or specific implementations of the address update device described in this invention can be found in the above-described method embodiments, and will not be repeated here.

[0163] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0164] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0165] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as a read-only memory image (ROM) / random access memory (RAM), magnetic disk, optical disk), and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0166] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. An address update method, characterized in that, The address update method includes the following steps: The address to be updated is determined based on the address update request information, and the address to be updated is verified for legality and validity. If the legality check and the validity check pass, the address to be updated will be subject to a timeout verification. The address to be updated is updated based on the cache address update request information and verification results; The address to be updated includes a dynamic address to be updated and a static address to be updated. The step of updating the address to be updated based on the cached address update request information and verification results includes: Upon successful verification, the dynamic address to be updated is updated based on the verification results; The request information for updating the cached address is parsed, and the dynamic address to be updated and the static address to be updated are obtained based on the parsing result; Perform rule validation on the dynamic address to be updated, and update the dynamic address to be updated to the dynamic address cache area if the rule validation is satisfied; When the dynamic address to be updated fails the rule verification, a static rule judgment is performed on the static address to be updated. Update the static addresses that meet the static rule criteria to the static address cache.

2. The address update method as described in claim 1, characterized in that, The address to be updated includes the dynamic address to be updated; The step of verifying the timeout of the reported address to be updated includes: When the reporting time of the dynamic address to be updated exceeds the preset time, wait for the dynamic address to be updated to be reported according to the cache time window; When the cache time window expires, the reporting time of the dynamic address to be updated is marked as reporting timeout; The historical dynamic addresses are processed, and the dynamic addresses to be updated are verified.

3. The address update method as described in claim 1, characterized in that, After the step of updating the dynamic address to be updated based on the verification result upon successful verification, the method further includes: When verification fails, the status of the reported address to be updated will be marked as invalid, and active verification requests will be initiated periodically based on the backup link.

4. The address update method as described in claim 1, characterized in that, After the step of updating the static address to be updated to the static address cache area that meets the static rule judgment, the method further includes: The audit data is updated based on the updated static address and the updated dynamic address; When the audit data update is completed, the status flag of the address update control table is switched.

5. The address update method as described in claim 1, characterized in that, The steps of determining the address to be updated based on the address update request information, and performing legality and validity checks on the address to be updated, include: The address to be updated is determined based on the address update request information, and the validity of the address to be updated is verified based on the request information and real-time detection information. The legality of the address to be updated is verified according to the reporting rules.

6. An address updating device, characterized in that, The address update device includes: a verification module, a checking module, and an update module; The verification module is used to determine the address to be updated based on the address update request information, and to perform legality and validity verification on the address to be updated. The verification module is used to perform a timeout verification on the address to be updated when the legality check and the validity check are both passed. The update module is used to update the address to be updated based on the cache address update request information and verification results; The address to be updated includes a dynamic address to be updated and a static address to be updated. The update module is further configured to update the dynamic address to be updated based on the verification result when the verification is successful; parse the cache address update request information and obtain the dynamic address to be updated and the static address to be updated based on the parsing result; perform rule verification on the dynamic address to be updated and update the dynamic address to be updated that meets the rule verification to the dynamic address cache area; when the dynamic address to be updated fails the rule verification, perform static rule judgment on the static address to be updated; and update the static address to be updated that meets the static rule judgment to the static address cache area.

7. An address update device, characterized in that, The address update device includes: a memory, a processor, and an address update program stored in the memory and executable on the processor, wherein the address update program, when executed by the processor, implements the steps of the address update method as described in any one of claims 1 to 5.

8. A storage medium, characterized in that, The storage medium stores an address update program, which, when executed by a processor, implements the steps of the address update method as described in any one of claims 1 to 5.

Images