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

Abstract

The present invention relates to the technical field of network communications, and discloses a DRA-based dynamic link management method, apparatus, device, medium and product, the method being executed by DRA, the method comprising: receiving a first network element registration request, the registration information of the first network element comprising at least one of IP information, domain name information, load information, network element type, interface attribute and link information requirement; establishing a Diameter interface link according to the registration information of the first network element, and storing the corresponding registration information of the first network element in a link library; and dynamically selecting and forwarding the service request to the second network element according to the first network element registration information. According to the invention, intelligent dynamic link management by the DRA can be realized, and the link management efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the field of network communication technology, and in particular to a method, device, equipment, medium and product for dynamically managing links based on DRA. Background Art

[0002] In the current EPC (Evolved Packet Core) network, the DRA (Diameter Routing Agent) network element determines the upstream and downstream Diameter links through pre-configured policy rules to achieve mutual forwarding of Diameter signaling of EPC network elements. In related technologies, DRA supports dynamic adjustment of routing policies according to network conditions and load conditions to ensure efficient message transmission, but the premise is that these network elements and links must be within the pre-configured range. Therefore, its dynamic management capability is limited by pre-configured information. In the EPC network system, it is normal for new network elements to be online, old network elements to be offline, or abnormal conditions to occur. Each link information needs to be manually configured on the DRA by the operation and maintenance personnel. In the process of network operation, whether it is for the purpose of eliminating abnormal link devices, or removing some device links to save resources when the load is low, or adding link devices when demand increases, there are huge link data processing challenges. Whenever a new network element is added or an existing network element is offline, it is necessary to manually add or delete operations, which has high risks and low timeliness, and increases the operation and maintenance costs. Summary of the invention

[0003] In view of this, the present invention provides a method, apparatus, device, medium and product for dynamically managing links based on DRA, so as to realize intelligent dynamic management of links by DRA and improve link management efficiency.

[0004] In a first aspect, the present invention provides a method for dynamically managing links based on DRA, the method being executed by DRA, and the method comprising: receiving a first network element registration request, the registration information of the first network element comprising 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 according to 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 a service request to a second network element according to the first network element registration information.

[0005] In an optional implementation, dynamically selecting and forwarding a service request to a second network element based on registration information of a first network element includes: when receiving a service request from a first network element, parsing registration information and a service type of the second network element required in the service request; determining the second network element in a 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.

[0006] In an optional implementation, after forwarding the service request to the second network element, the method includes: receiving a service processing response sent by the second network element; and forwarding the service processing response to the first network element.

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

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

[0009] In a second aspect, the present invention provides a dynamic link management device based on DRA, the device comprising: a network element registration module, used to receive a first network element registration request, the registration information of the first network element comprising at least one of IP information, domain name information, load information, network element type, interface attributes and link information requirements; a link establishment module, used to establish a Diameter interface link according to the registration information of the first network element, and store the corresponding first network element registration information in a link library; a service forwarding module, used to dynamically select and forward the service request to a second network element according to the first network element registration information.

[0010] In an 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 the service request of 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.

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

[0012] In an optional implementation, the device further includes: a registration update module, configured to receive a registration information update request sent by 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 is changed.

[0013] In an optional implementation, the device further includes: a deregistration module, configured to receive a deregistration request sent by the first network element when the first network element goes offline, delete the responsive first network element registration information in the link library, and disconnect the link with the first network element.

[0014] In a third aspect, the present invention provides a computer device, comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the computer instructions to execute a DRA-based dynamic link management method according to the first aspect or any corresponding embodiment thereof.

[0015] In a fourth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute a DRA-based dynamic link management method according to the first aspect or any corresponding embodiment thereof.

[0016] In a fifth aspect, the present invention provides a computer program product, including computer instructions, where the computer instructions are used to enable a computer to execute a DRA-based dynamic link management method according to the first aspect or any corresponding embodiment thereof.

[0017] The technical solution provided by this application may have the following beneficial effects:

[0018] The present invention provides a DRA-based dynamic link management method which is executed by DRA.

[0019] Receiving the registration request of the first network element, 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, and configuring the network element to the DRA is the basis for subsequent link management. Establishing a Diameter interface link according to the registration information of the first network element, and storing the corresponding first network element registration information in the link library, ensure that network elements can interact with each other through DRA. When the DRA receives a service request from the first network element, it dynamically selects the most suitable second network element for forwarding according to the registration information in the link library. Factors such as the load condition and interface type of the network element are taken into consideration to ensure efficient processing of service requests. The above scheme realizes intelligent dynamic management of links by DRA by receiving network element registration requests, establishing Diameter interface links and storing registration information, and dynamically selecting and forwarding services, thereby improving link management efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0021] Figure 1is a flowchart of a method for dynamically managing links based on DRA according to an embodiment of the present invention;

[0022] Figure 2 is a schematic diagram of a network element registering with a DRA according to an embodiment of the present invention;

[0023] Figure 3 is a schematic diagram of network element link binding and forwarding according to an embodiment of the present invention;

[0024] Figure 4 is a schematic diagram of a registration information update process according to an embodiment of the present invention;

[0025] Figure 5 is a schematic diagram of a deregistration process according to an embodiment of the present invention;

[0026] Figure 6 is a schematic diagram of a DRA dynamic link management program design process according to an optional embodiment of the present invention;

[0027] Figure 7 is a structural block diagram of a DRA-based dynamic link management device according to an embodiment of the present invention;

[0028] Figure 8 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0029] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0030] According to an embodiment of the present invention, an embodiment of a dynamic link management method based on DRA is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0031] In this embodiment, a dynamic link management method based on DRA is provided. Figure 1 is a flow chart of a method for dynamically managing links based on DRA according to an embodiment of the present invention, the method is executed by DRA, such as Figure 1 As shown, the process includes the following steps:

[0032] Step S101, receiving a first network element registration request, where 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.

[0033] DRA receives a registration request from the first network element. The first network element is a network element that needs to access DRA for communication. Registration information is the basis for DRA to establish and manage links. IP information is information such as the IP and port of the network element, which is used for link creation. Domain name information is the domain name information of the network element. Load information can be combined with DRA's load balancing strategy to forward messages more reasonably. Network element types include MME (Mobility Management Entity), HSS (Home Subscriber Server), SGW Serving Gateway, etc. Interface attributes indicate 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 DRA to forward to, or the network element with corresponding attributes. Figure 2 It is a schematic diagram of network elements registering with DRA according to an embodiment of the present invention, where network elements such as HSS_X, HSS_O, MME, and PCRF are registered with DRA.

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

[0035] DRA establishes a Diameter interface link with the network element based on the received registration information of the first 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, which is used to connect different network elements to achieve signaling interaction. The link is a key component for implementing signaling interaction and business processing in the EPC network. Among them, signaling interaction refers to the behavior of coordinating and controlling the communication process by sending and receiving messages in a specific format between different network entities (such as network elements) in the communication network. In the EPC network of the embodiment of the present invention, signaling interaction refers to the exchange of user information, status information, control instructions and other information between different network elements.

[0036] Step S103: dynamically select and forward the service request to the second network element according to the registration information of the first network element.

[0037] A service request refers to a request initiated by the first network element (such as MME, HSS, etc.) that needs to be forwarded to another network element (i.e., the second network element) for processing through DRA. A service request usually contains user data or instructions, and is intended to implement a specific network function or service. First, DRA parses the registration information of the first network element to understand the current status, interface properties, and load conditions of each network element. Then, based on the characteristics and requirements of the service request, DRA will select the most suitable second network element in the link library to receive and process the request. Finally, DRA will forward the service request to the selected second network element through the established Diameter interface link.

[0038] Figure 3 This is a schematic diagram of network element link binding and forwarding according to an embodiment of the present invention. Taking MME and HSS as examples of network elements, after MME registration is successful, the S6A Diameter interface link will be established between MME and DRA. Similarly, after HSS registration is successful, it will establish an S6A Diameter interface link with DRA. MME initiates a service request to DRA. After receiving the request, DRA knows that it needs to find HSS, so it searches for the corresponding HSS from the link library and selects a more suitable link based on the information carried by the HSS network element registration (such as load). And send it to this link. After receiving the request, HSS sends a service processing response to DRA, and DRA forwards the result to MME.

[0039] This embodiment provides a DRA-based dynamic link management method, which implements intelligent dynamic link management by DRA by receiving a network element registration request, establishing a Diameter interface link and storing registration information, and dynamically selecting and forwarding services, thereby improving link management efficiency.

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

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

[0042] When 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 and service type of the second network element. By parsing the service request, DRA can clearly understand the specific requirements of this service request and provide accurate information support for subsequent dynamic selection and forwarding.

[0043] Step S1032: Determine the second network element in the link library based on the registration information and service type of the second network element.

[0044] After obtaining the registration information and service type of the second network element required in the service request, DRA searches and determines a suitable second network element in the link library it maintains. 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 can meet the service requirements.

[0045] Step S1033: forward the service request to the second network element.

[0046] After determining 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.

[0047] In an optional implementation, the process after the above step S1033 includes:

[0048] Step S1041: receiving a service processing response sent by the second network element.

[0049] When the second network element receives the service request forwarded by the DRA, it will perform corresponding processing. After the processing is completed, the second network element will generate a service processing response and send the response to the DRA. The DRA receives the service processing response to ensure the accurate transmission of the service processing results.

[0050] Step S1042: forward the service processing response to the first network element.

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

[0052] In an optional implementation, when the load of the first network element changes or the registration information is changed, a registration information update request sent by the first network element is received, and the registration information of the first network element is updated.

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

[0054] DRA receives a registration information update request from the first network element. The request includes the latest load information, registration information changes and other data. After receiving the request, DRA searches for and updates the registration information of the first network element in the link library, including updating all relevant information such as the load status, IP address, domain name, interface properties, etc. of the network element. Optionally, DRA synchronously updates its link selection strategy. In the subsequent service request forwarding process, DRA will select the most appropriate second network element for forwarding based on the latest registration information to ensure efficient processing of the service. This implementation method can adjust the link strategy in a timely manner and improve the efficiency of link management by updating the network element registration information in real time.

[0055] Figure 4 This is a schematic diagram of the registration information update process according to an embodiment of the present invention. Taking MME and HSS as examples, when the MME load reaches a certain index or the registration information changes, it will initiate a registration information update to DRA. After receiving the request, DRA will update the corresponding registration information and synchronize it to the corresponding link selection strategy. When DRA receives a new request from MME again, 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 a new S6A interface request related to MME is received, DRA will select the optimal HSS based on the latest HSS registration data (such as load) and forward the request to this HSS.

[0056] In an optional implementation, when the first network element goes offline, a deregistration request sent by the first network element is received, the responsive first network element registration information is deleted from the link library, and the link with the first network element is disconnected.

[0057] When the first network element needs to go offline due to maintenance, upgrade, failure or other reasons, it actively sends a deregistration request to the DRA. The purpose of the deregistration request is to notify the DRA that the network element is about to be removed from the network and the DRA needs to update its link management information accordingly.

[0058] The DRA receives a deregistration request from the first network element. The request includes information such as the network element's identification and offline reason, so that the DRA can perform subsequent processing. After receiving the deregistration request, the DRA searches its link library and deletes all registration information related to the first network element, including the network element's IP address, domain name, load information, interface attributes, etc. In addition to deleting the information in the link library, the DRA disconnects all Diameter interface links with the first network element, and the network element will no longer participate in signaling interactions in the network.

[0059] This implementation method can avoid invalid routing requests and unnecessary resource consumption by timely deleting the registration information of offline network elements and disconnecting the links therewith, thereby ensuring network efficiency and improving resource utilization.

[0060] Figure 5 This is a schematic diagram of the deregistration process according to an embodiment of the present invention. Taking MME and HSS as examples of network elements, when MME needs to go offline for some reason, MME first deletes the current user session information and allows the user to go back online to other MMEs. After MME deletes the session, it initiates deregistration to DRA. After receiving the MME deregistration process, DRA disconnects the link with MME and deletes the relevant link information of the corresponding MME. Similarly, when HSS initiates deregistration, DRA removes the link information and link related to HSS. When receiving a request for the S6A interface related to MME, DRA will re-search for an HSS that meets its requirements for MME and forward the request to this HSS.

[0061] Figure 6 It is a schematic diagram of the DRA dynamic link management program design process according to an optional embodiment of the present invention, including network element registration, link creation, dynamic adjustment and data forwarding processes. First, the network element registers with the DRA. Then, the network element and the DRA create corresponding Diameter interface links, and the DRA creates interface link libraries for each network element. If the network element initiates deregistration with the DRA, the DRA removes the data of the network element in the interface link library and removes the corresponding resources and link information. If a network element initiates registration with the DRA in the middle, the DRA adds the data of the network element in the interface link library and creates corresponding link resources. After the network element business data comes in, select the appropriate link to forward it to the corresponding network element.

[0062] In summary, the dynamic link management method based on DRA of the present invention can flexibly and intelligently expand or shrink the link on DRA through registration and deregistration. Basically, no manual intervention is required throughout the process, and all operations are performed intelligently by the EPC core network, which greatly reduces the operation and maintenance costs and improves the stability of the EPC DRA system.

[0063] In this embodiment, a dynamic link management device based on DRA is also provided, which is used to implement the above embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0064] This embodiment provides a DRA-based dynamic link management device, such as Figure 7 As shown, including:

[0065] The network element registration module 701 is used to receive a first network element registration request, where 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;

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

[0067] The service forwarding module 703 is used to dynamically select and forward the service request to the second network element according to the registration information of the first network element.

[0068] In an optional implementation, the service forwarding module 703 includes:

[0069] 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 the service request of the first network element.

[0070] 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;

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

[0072] In an optional implementation, the third service forwarding unit includes:

[0073] A first service processing subunit, configured to receive a service processing response sent by a second network element;

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

[0075] In an optional embodiment, the device further comprises:

[0076] The registration update module is used to receive a registration information update request sent by 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.

[0077] In an optional embodiment, the device further comprises:

[0078] The deregistration module is used to receive a deregistration request sent by 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.

[0079] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

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

[0081] The embodiment of the present invention also provides a computer device having the above Figure 7 A DRA-based dynamic link management device is shown.

[0082] See also Figure 8 , Figure 8 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 8 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 8 A processor 10 is taken as an example.

[0083] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0084] The memory 20 stores instructions executable by at least one processor 10, so that at least one processor 10 executes the method shown in the above embodiment.

[0085] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

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

[0087] The computer device also includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30 and the output device 40 may be connected via a bus or other means. Figure 8 The example of connecting through bus is taken in the following.

[0088] The input device 30 can receive input digital or character information, and generate key signal input related to the user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator bar, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 may include a display device, an auxiliary lighting device (e.g., an LED) and a tactile feedback device (e.g., a vibration motor), etc. The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display and a plasma display. In some optional embodiments, the display device can be a touch screen.

[0089] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0090] A part of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the existence of the computer program instruction in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc., and accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium accessible to the computer.

[0091] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A DRA-based dynamic link management method, characterized in that: The method is performed by a DRA, and comprises: 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; Establishing a Diameter interface link according to the registration information of the first network element, and storing the corresponding first network element registration information in a link library; Dynamically select and forward the service request to the second network element according to the registration information of the first network element.

2. The method according to claim 1, characterized in that: The dynamically selecting and forwarding the service request to the second network element according to the first network element registration information 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 the service type of the second network element; 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 method further comprises: receiving a service processing response sent by the second network element; Forward the service processing response to the first network element.

4. The method according to claim 3, characterized in that: The method further comprises: When the load of the first network element changes or the registration information is changed, a registration information update request sent by the first network element is received, and the registration information of the first network element is updated.

5. The method according to claim 4, characterized in that The method further comprises: When the first network element goes offline, a deregistration request sent by the first network element is received, the corresponding first network element registration information is deleted in the link library, and the link with the first network element is disconnected.

6. A dynamic link management device based on DRA, characterized in that: The device comprises: A network element registration module, configured to receive 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, configured to establish a Diameter interface link according to the registration information of the first network element, and store the corresponding first network element registration information in a link library; The service forwarding module is used to dynamically select and forward the service request to the second network element according to the registration information of the first network element.

7. The device according to claim 6, characterized in that The device also includes: A registration update module, configured to receive a registration information update request sent by 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 sent by 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, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the method according to any one of claims 1 to 5 by executing the computer instructions.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the method according to any one of claims 1 to 5.

10. A computer program product, characterized in that The method comprises computer instructions for causing a computer to execute the method according to any one of claims 1 to 5.

Images