DRA-based dynamic link management method and apparatus, device, medium, and product

Abstract

A DRA-based dynamic link management method and apparatus, a device, a medium, and a product. The method is executed by a DRA. The method comprises: receiving a first network element registration request, wherein registration information of a first network element comprises at least one of IP information, domain name information, load information, a network element type, an interface attribute, and a link information requirement; establishing a Diameter interface link on the basis of the registration information of the first network element, and storing the corresponding registration information of the first network element in a link library; and on the basis of the registration information of the first network element, making dynamic selection and forwarding a service request to a second network element. The present application can implement DRA-based intelligent dynamic link management, thereby improving link management efficiency.

Description

Methods, devices, equipment, media, and products based on DRA dynamic management links Technical Field

[0001] This application relates to the field of network communication technology, specifically to methods, devices, equipment, media, and products based on DRA dynamic link management. Background Technology

[0002] In current EPC (Evolved Packet Core) networks, DRA (Diameter Routing Agent) network elements determine upstream and downstream Diameter links through pre-configured policy rules, thereby enabling mutual forwarding of Diameter signaling between EPC network elements. Related technologies support dynamic adjustment of routing policies based on network conditions and load to ensure efficient message delivery, but this requires that these network elements and links be within the pre-configured range. Therefore, its dynamic management capabilities are limited by pre-configured information. In EPC network systems, the arrival of new network elements, the decommissioning of old network elements, or abnormal situations are all normal phenomena. Each link information requires manual configuration on the DRA by maintenance personnel. During network operation, whether for the purpose of removing abnormal link devices, removing some device links to save resources during low load, or adding link devices when demand increases, there is a huge challenge in processing link data. Whenever a new network element is added or an existing network element is decommissioned, manual addition or deletion operations are required, posing high risks and low timeliness, increasing maintenance costs.

[0003] Application content

[0004] In view of this, this application provides a method, apparatus, device, medium and product based on DRA dynamic link management to realize intelligent dynamic link management by DRA and improve link management efficiency.

[0005] Firstly, this application provides a dynamic management link method based on DRA, the method being executed by DRA, the method comprising: receiving a registration request for a first network element, wherein the registration information of the first network element includes at least one of IP information, domain name information, load information, network element type, interface attributes, and link information requirements; establishing a Diameter interface link based on the registration information of the first network element, and storing the corresponding first network element registration information in a link library; and dynamically selecting and forwarding service requests to a second network element based on the first network element registration information.

[0006] In one optional implementation, dynamically selecting and forwarding a service request to a second network element based on the registration information of the first network element includes: when receiving a service request from the first network element, parsing the registration information and service type of the second network element required in the service request; determining the second network element in the link library based on the registration information and service type of the second network element; and forwarding the service request to the second network element.

[0007] In one optional implementation, after forwarding the service request to the second network element, the process includes: receiving a service processing response from the second network element; and forwarding the service processing response to the first network element.

[0008] In an optional implementation, the method further includes: when the load of the first network element changes or the registration information changes, receiving a registration information update request from the first network element and updating the registration information of the first network element.

[0009] In an optional implementation, the method further includes: when the first network element goes offline, receiving a deregistration request from the first network element, deleting the corresponding first network element registration information in the link library, and disconnecting the link with the first network element.

[0010] Secondly, this application provides a dynamic management link device based on DRA, the device comprising: a network element registration module for receiving a first network element registration request, wherein the registration information of the first network element includes at least one of IP information, domain name information, load information, network element type, interface attributes, and link information requirements; a link establishment module for establishing a Diameter interface link based on the registration information of the first network element and storing the corresponding first network element registration information in a link library; and a service forwarding module for dynamically selecting and forwarding service requests to a second network element based on the registration information of the first network element.

[0011] In one optional implementation, the service forwarding module includes: a first service forwarding unit, configured to parse the registration information and service type of the second network element required in the service request when receiving a service request from the first network element; a second service forwarding unit, configured to determine the second network element in the link library based on the registration information and service type of the second network element; and a third service forwarding unit, configured to forward the service request to the second network element.

[0012] In one optional implementation, the third service forwarding unit includes: a first service processing subunit, configured to receive a service processing response from a second network element; and a second service processing subunit, configured to forward the service processing response to the first network element.

[0013] In one optional embodiment, the device further includes a registration update module, configured to receive a registration information update request from the first network element and update the registration information of the first network element when the load of the first network element changes or the registration information changes.

[0014] In an optional implementation, the apparatus further includes a deregistration module, configured to receive a deregistration request from the first network element when the first network element goes offline, delete the corresponding first network element registration information in the link library, and disconnect the link with the first network element.

[0015] Thirdly, this application provides a computer device, including: a memory and a processor, which are communicatively connected to each other. The memory stores computer instructions, and the processor executes the computer instructions to perform a dynamic management link method based on DRA as described in the first aspect or any corresponding embodiment.

[0016] Fourthly, this application provides a computer-readable storage medium storing computer instructions for causing a computer to execute a DRA-based dynamic management link method according to the first aspect or any corresponding embodiment described above.

[0017] Fifthly, this application provides a computer program product, including computer instructions for causing a computer to execute a DRA-based dynamic management link method as described in the first aspect or any corresponding embodiment thereof.

[0018] The technical solution provided in this application may include the following beneficial effects:

[0019] The dynamic management link method based on DRA provided in this application is executed by DRA.

[0020] The process involves receiving a registration request from a first network element. The registration information for this first network element includes at least one of the following: IP address, domain name, load balancing, network element type, interface attributes, and link information requirements. Configuring this network element on the DRA is fundamental for subsequent link management. A Diameter interface link is established based on the first network element's registration information, and the corresponding registration information is stored in the link library, ensuring that network elements can interact via signaling through the DRA. When the DRA receives a service request from the first network element, it dynamically selects the most suitable second network element for forwarding based on the registration information in the link library. This process considers factors such as network element load and interface type to ensure efficient processing of service requests. This solution, by receiving network element registration requests, establishing Diameter interface links and storing registration information, and dynamically selecting and forwarding services, enables intelligent and dynamic link management by the DRA, improving link management efficiency. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the specific embodiments of this application or the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0022] Figure 1 is a flowchart illustrating a dynamic management link method based on DRA according to an embodiment of this application;

[0023] Figure 2 is a schematic diagram of a network element registering to the DRA according to an embodiment of this application;

[0024] Figure 3 is a schematic diagram of network element link binding and forwarding according to an embodiment of this application;

[0025] Figure 4 is a schematic diagram of the registration information update process according to an embodiment of this application;

[0026] Figure 5 is a schematic diagram of the deregistration process according to an embodiment of this application;

[0027] Figure 6 is a schematic diagram of the design flow of the DRA dynamic link management program according to an optional embodiment of this application;

[0028] Figure 7 is a structural block diagram of a DRA-based dynamic management link device according to an embodiment of this application;

[0029] Figure 8 is a schematic diagram of the hardware structure of a computer device according to an embodiment of this application. Detailed Implementation

[0030] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0031] According to an embodiment of this application, a dynamic management link method based on DRA is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0032] This embodiment provides a dynamic management link method based on DRA. Figure 1 is a flowchart illustrating a dynamic management link method based on DRA according to an embodiment of this application. The method is executed by DRA. As shown in Figure 1, the process includes the following steps:

[0033] Step S101: Receive a first network element registration request. The registration information of the first network element includes at least one of the following: IP information, domain name information, load information, network element type, interface attributes, and link information requirements.

[0034] The DRA receives registration requests from the first network element. The first network element is the network element that needs to access the DRA for communication. Registration information is the basis for the DRA to establish and manage links. IP information includes the network element's IP address and port information, used for link creation. Domain name information is the network element's domain name information. Load information can be combined with the DRA's load balancing strategy for more reasonable message forwarding. Network element types include MME (Mobility Management Entity), HSS (Home Subscriber Server), SGWServing Gateway, etc. Interface attributes represent the corresponding Diameter interface of the network element, such as S6A, GX, RX, etc. Link information requirements refer to the address or domain name of the specific network element that the network element service initiator wants the DRA to forward to, or a network element with corresponding attributes. Figure 2 is a schematic diagram of network element registration to the DRA according to an embodiment of this application, where network elements such as HSS_X, HSS_O, MME, and PCRF register with the DRA.

[0035] Step S102: Establish a Diameter interface link based on the registration information of the first network element, and store the corresponding registration information of the first network element in the link library.

[0036] Based on the received registration information of the first network element, the DRA establishes a Diameter interface link with that network element and stores the corresponding registration information in the link library. The Diameter interface link is a communication channel established based on the Diameter protocol, used to connect different network elements to achieve signaling interaction. The link is a key component in the EPC network for realizing signaling interaction and service processing. Signaling interaction refers to the behavior of different network entities (such as network elements) coordinating and controlling the communication process by sending and receiving messages of a specific format in a communication network. In the EPC network of this application embodiment, signaling interaction refers to the exchange of user information, status information, control commands, and other information between different network elements.

[0037] Step S103: Dynamically select and forward service requests to the second network element based on the registration information of the first network element.

[0038] A service request refers to a request initiated by a first network element (such as MME, HSS, etc.) that needs to be forwarded by the DRA to another network element (i.e., the second network element) for processing. Service requests typically contain user data or instructions, aiming to implement a specific network function or service. First, the DRA parses the registration information of the first network element to understand its current status, interface attributes, and load conditions. Then, based on the characteristics and requirements of the service request, the DRA selects the most suitable second network element from the link library to receive and process the request. Finally, the DRA forwards the service request to the selected second network element through the established Diameter interface link.

[0039] Figure 3 is a schematic diagram of network element link binding and forwarding according to an embodiment of this application. Taking MME and HSS as examples, after MME successfully registers, an S6A Diameter interface link is established between MME and DRA. Similarly, after HSS successfully registers, an S6A Diameter interface link is established with DRA. MME initiates a service request to DRA. Upon receiving the request, DRA knows that it needs to find an HSS, so it searches for the corresponding HSS in the link library and selects a more suitable link based on the information carried by the HSS network element registration (e.g., load). The request is then sent to this link. After receiving and processing the request, HSS sends a service processing response to DRA, which then forwards the result to MME.

[0040] This embodiment provides a dynamic link management method based on DRA. By receiving network element registration requests, establishing Diameter interface links and storing registration information, and dynamically selecting and forwarding services, the method enables intelligent dynamic link management by DRA, thereby improving link management efficiency.

[0041] In an optional implementation, the process of step S103 above includes:

[0042] Step S1031: When receiving a service request from the first network element, parse the registration information and service type of the second network element required in the service request.

[0043] When the DRA receives a service request from the first network element, it first parses the request. The purpose of parsing is to extract the key information required in the service request, including the registration information of the second network element and the service type. By parsing the service request, the DRA can clearly understand the specific requirements of this service request, providing accurate information support for subsequent dynamic selection and forwarding.

[0044] Step S1032: Based on the registration information and service type of the second network element, determine the second network element in the link library.

[0045] After obtaining the registration information and service type of the second network element required in the service request, the DRA searches for and determines a suitable second network element in its maintained link library. It considers the registration information of the second network element (such as IP address, port number, load status, interface attributes, etc.) and the type of service request to select a second network element that meets the service requirements.

[0046] Step S1033: Forward the service request to the second network element.

[0047] After identifying the second network element, the DRA forwards the service request to the second network element for processing. Forwarding means sending the service request from the DRA to the second network element through the established Diameter interface link.

[0048] In an optional implementation, the process following step S1033 includes:

[0049] Step S1041: Receive the service processing response sent by the second network element.

[0050] When the second network element receives a service request forwarded by the DRA, it will process it accordingly. After processing, the second network element will generate a service processing response and send this response to the DRA. The DRA receives the service processing response to ensure the accurate transmission of the service processing result.

[0051] Step S1042: Forward the service processing response to the first network element.

[0052] After receiving the service processing response from the second network element, the DRA forwards the service processing response to the first network element that initially initiated the service request, which is a key step to ensure that the service request receives a complete response.

[0053] In one optional implementation, when the load of the first network element changes or its registration information changes, a registration information update request is received from the first network element, and the registration information of the first network element is updated.

[0054] When the load of the first network element reaches a certain preset threshold or its registration information (such as IP address, domain name, interface attributes, etc.) changes, the first network element will proactively initiate a registration information update request. The purpose of the registration information update request is to notify the DRA of the latest status of the current network element so that the DRA can dynamically manage the link based on the latest information.

[0055] The DRA receives a registration information update request from the first network element. This request includes the latest load information, changes to the registration information, and other data. Upon receiving the request, the DRA searches the link database and updates the registration information of the first network element, including updating the element's load status, IP address, domain name, interface attributes, and all other relevant information. Optionally, the DRA simultaneously updates its link selection strategy. In subsequent service request forwarding processes, the DRA will select the most suitable second network element for forwarding based on the latest registration information to ensure efficient service processing. This implementation method, by updating network element registration information in real time, enables timely adjustment of link strategies, improving the efficiency of link management.

[0056] Figure 4 is a schematic diagram of the registration information update process according to an embodiment of this application. Taking MME and HSS as examples, when the MME load reaches a certain indicator or the registration information changes, it will initiate a registration information update to DRA. After receiving the request, DRA updates the corresponding registration information and synchronizes it to the corresponding link selection strategy. When DRA receives a new request from MME, it will match the corresponding HSS link according to the latest registration information. Similarly, when HSS initiates a registration update, DRA updates the link information of the current HSS. When it receives a new request from the S6A interface related to MME, DRA will select the optimal HSS based on the latest HSS registration data (such as load) and forward the request to this HSS.

[0057] In one optional implementation, when the first network element goes offline, a deregistration request is received from the first network element, the corresponding first network element registration information is deleted from the link library, and the link with the first network element is disconnected.

[0058] When a network element needs to be taken offline due to maintenance, upgrades, faults, or other reasons, it proactively sends a deregistration request to the DRA. The purpose of the deregistration request is to notify the DRA that the network element will soon be removed from the network, and the DRA needs to update its link management information accordingly.

[0059] The DRA receives a deregistration request from the first network element. This request includes information such as the network element's identifier and the reason for its disconnection, allowing the DRA to process it further. Upon receiving the deregistration request, the DRA searches its link database and deletes all registration information related to that first network element, including the element's IP address, domain name, load information, and interface attributes. In addition to deleting the information from the link database, the DRA disconnects all Diameter interface links with the first network element; thereafter, that network element will no longer participate in signaling interactions within the network.

[0060] This implementation method avoids invalid routing requests and unnecessary resource consumption by promptly deleting the registration information of offline network elements and disconnecting their links, thus ensuring network efficiency and improving resource utilization.

[0061] Figure 5 is a schematic diagram of the deregistration process according to an embodiment of this application. Taking MME and HSS as examples, when an MME needs to go offline for some reason, the MME first removes the currently existing user session information, allowing the user to reconnect to another MME. After removing the session, the MME initiates deregistration with DRA. After receiving the MME's deregistration process, DRA disconnects the link with the MME and deletes the relevant link information of the corresponding MME. Similarly, when an HSS initiates deregistration, DRA removes the relevant link information and links with the HSS. When it receives a request from the S6A interface related to the MME, DRA will find a new HSS that meets its requirements for the MME and forward the request to this HSS.

[0062] Figure 6 is a schematic diagram of the DRA dynamic link management program design flow according to an optional embodiment of this application, including network element registration, link creation, dynamic adjustment, and data forwarding processes. First, the network element registers with the DRA. Next, the network element and the DRA create corresponding Diameter interface links, and the DRA creates an interface link library for each network element. If a network element initiates deregistration with the DRA, the DRA removes the data of that network element from the interface link library and deletes the corresponding resources and link information. If a network element initiates registration with the DRA midway, the DRA adds the data of that network element to the interface link library and creates the corresponding link resources. After network element service data arrives, a suitable link is selected and forwarded to the corresponding network element.

[0063] In summary, the dynamic link management method based on DRA proposed in this application can flexibly and intelligently expand or shrink links on DRA through registration and deregistration, with virtually no manual intervention required throughout the process. The entire operation is intelligently handled by the EPC core network, which greatly reduces maintenance costs and improves the stability of the EPC DRA system.

[0064] This embodiment also provides a DRA-based dynamic management link device, which is used to implement the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0065] This embodiment provides a dynamic management link device based on DRA, as shown in Figure 7, including:

[0066] The network element registration module 701 is used to receive a first network element registration request. The registration information of the first network element includes at least one of the following: IP information, domain name information, load information, network element type, interface attributes, and link information requirements.

[0067] The link establishment module 702 is used to establish a Diameter interface link based on the registration information of the first network element, and store the corresponding registration information of the first network element in the link library;

[0068] The service forwarding module 703 is used to dynamically select and forward service requests to the second network element based on the registration information of the first network element.

[0069] In one optional implementation, the service forwarding module 703 includes:

[0070] The first service forwarding unit is used to parse the registration information and service type of the second network element required in the service request when receiving a service request from the first network element.

[0071] The second service forwarding unit is used to determine the second network element in the link library based on the registration information and service type of the second network element.

[0072] The third service forwarding unit is used to forward service requests to the second network element.

[0073] In one optional implementation, the third service forwarding unit includes:

[0074] The first service processing subunit is used to receive the service processing response sent by the second network element;

[0075] The second service processing subunit is used to forward the service processing response to the first network element.

[0076] In one alternative embodiment, the apparatus further includes:

[0077] The registration update module is used to receive a registration information update request from the first network element and update the registration information of the first network element when the load of the first network element changes or the registration information changes.

[0078] In one alternative embodiment, the apparatus further includes:

[0079] The deregistration module is used to receive a deregistration request from the first network element when the first network element goes offline, delete the corresponding first network element registration information in the link library, and disconnect the link with the first network element.

[0080] Further functional descriptions of the above modules and units are the same as those in the corresponding embodiments described above, and will not be repeated here.

[0081] In this embodiment, a DRA-based dynamic management link device is presented in the form of a functional unit. Here, a unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that execute one or more software or fixed programs, and / or other devices that can provide the above functions.

[0082] This application also provides a computer device having a DRA-based dynamic management link device as shown in FIG7 above.

[0083] Please refer to Figure 8, which is a schematic diagram of the structure of a computer device provided in an optional embodiment of this application. As shown in Figure 8, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting the various components, including high-speed interfaces and low-speed interfaces. The various components communicate with each other using different buses and can be installed on a common motherboard or otherwise as needed. The processor can process instructions executed within the computer device, including instructions stored in or on memory to display graphical information of a GUI on an external input / output device (such as a display device coupled to the interface). In some optional embodiments, multiple processors and / or multiple buses can be used with multiple memories and multiple memory modules, if desired. Similarly, multiple computer devices can be connected, each providing some of the necessary operations (e.g., as a server array, a group of blade servers, or a multiprocessor system). Figure 8 uses one processor 10 as an example.

[0084] Processor 10 may be a central processing unit, a network processor, or a combination thereof. Processor 10 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The programmable logic device may be a complex programmable logic device (CAMP), a field-programmable gate array (FPGA), a general-purpose array logic (GDA), or any combination thereof.

[0085] The memory 20 stores instructions executable by at least one processor 10 to cause at least one processor 10 to perform the method shown in the above embodiments.

[0086] The memory 20 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the computer device. Furthermore, the memory 20 may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some alternative embodiments, the memory 20 may optionally include memory remotely located relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0087] The memory 20 may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as flash memory, hard disk or solid-state drive; the memory 20 may also include a combination of the above types of memory.

[0088] The computer device also includes an input device 30 and an output device 40. The processor 10, memory 20, input device 30 and output device 40 can be connected via a bus or other means, as shown in Figure 8, which illustrates a connection via a bus.

[0089] Input device 30 can receive input numerical or character information, and generate key signal inputs related to user settings and function control of the computer device, such as a touchscreen, keypad, mouse, trackpad, touchpad, joystick, one or more mouse buttons, trackball, joystick, etc. Output device 40 may include display devices, auxiliary lighting devices (e.g., LEDs), and haptic feedback devices (e.g., vibration motors). The aforementioned display devices include, but are not limited to, liquid crystal displays, light-emitting diodes, displays, and plasma displays. In some alternative embodiments, the display device may be a touchscreen.

[0090] This application also provides a computer-readable storage medium. The methods described in this application can be implemented in hardware or firmware, or implemented as recordable on a storage medium, or implemented as computer code downloaded over a network and originally stored on a remote storage medium or a non-transitory machine-readable storage medium and subsequently stored on a local storage medium. Thus, the methods described herein can be processed by software stored on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. The storage medium can be a magnetic disk, optical disk, read-only memory, random access memory, flash memory, hard disk, or solid-state drive, etc.; further, the storage medium can also include combinations of the above types of memory. It is understood that computers, processors, microprocessor controllers, or programmable hardware include storage components capable of storing or receiving software or computer code. When the software or computer code is accessed and executed by the computer, processor, or hardware, the methods shown in the above embodiments are implemented.

[0091] A portion of this application can be applied as a computer program product, such as computer program instructions, which, when executed by a computer, can invoke or provide the methods and / or technical solutions according to this application through the operation of the computer. Those skilled in the art will understand that the forms in which computer program instructions exist in a computer-readable medium include, but are not limited to, source files, executable files, installation package files, etc. Correspondingly, the ways in which computer program instructions are executed by a computer include, but are not limited to: the computer directly executing the instructions, or the computer compiling the instructions and then executing the corresponding compiled program, or the computer reading and executing the instructions, or the computer reading and installing the instructions and then executing the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium accessible to a computer.

[0092] Although embodiments of this application have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of this application, and all such modifications and variations fall within the scope defined by the appended claims.

Claims

1. A dynamic management link method based on DRA, characterized in that, The method is performed by the DRA, and the method includes: Receive a registration request for a first network element. The registration information of the first network element includes at least one of the following: IP information, domain name information, load information, network element type, interface attributes, and link information requirements. A Diameter interface link is established based on the registration information of the first network element, and the corresponding registration information of the first network element is stored in the link library; The service request is dynamically selected and forwarded to the second network element based on the registration information of the first network element.

2. The method according to claim 1, characterized in that, The step of dynamically selecting and forwarding service requests to the second network element based on the registration information of the first network element includes: When receiving a service request from the first network element, the registration information and service type of the second network element required in the service request are parsed. Based on the registration information and service type of the second network element, the second network element is determined in the link library; The service request is forwarded to the second network element.

3. The method according to claim 2, characterized in that, After forwarding the service request to the second network element, the process includes: Receive the service processing response sent by the second network element; The service processing response is forwarded to the first network element.

4. The method according to claim 3, characterized in that, The method further includes: When the load of the first network element changes or its registration information changes, the system receives a registration information update request from the first network element and updates the registration information of the first network element.

5. The method according to claim 4, characterized in that, The method further includes: When the first network element goes offline, the system receives a deregistration request from the first network element, deletes the corresponding first network element registration information from the link database, and disconnects the link with the first network element.

6. A dynamic management link device based on DRA, characterized in that, The device includes: The network element registration module is used to receive a first network element registration request. The registration information of the first network element includes at least one of the following: IP information, domain name information, load information, network element type, interface attributes, and link information requirements. The link establishment module is used to establish a Diameter interface link based on the registration information of the first network element, and store the corresponding registration information of the first network element in the link library; The service forwarding module is used to dynamically select and forward service requests to the second network element based on the registration information of the first network element.

7. The apparatus according to claim 6, characterized in that, The device further includes: The registration update module is used to receive a registration information update request from the first network element and update the registration information of the first network element when the load of the first network element changes or the registration information changes. The deregistration module is used to receive a deregistration request from the first network element when the first network element goes offline, delete the corresponding first network element registration information in the link library, and disconnect the link with the first network element.

8. A computer device, characterized in that, include: A memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, the processor executing the computer instructions to perform the method of any one of claims 1 to 5.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing a computer to perform the method of any one of claims 1 to 5.

10. A computer program product, characterized in that, Includes computer instructions for causing a computer to perform the method of any one of claims 1 to 5.

Images