Long connection reconstruction method and device, computer device, storage medium and product

Abstract

The application relates to a long connection reconstruction method and device, computer equipment, a storage medium and a product. The method comprises the following steps: receiving a first change message sent by a cloud platform, wherein the first change message is used for indicating that the instance network address of a target virtualized network function instance has been changed; according to the first change message, a second change message is sent to a management and control system of the target virtualized network function instance, wherein the second change message is used for instructing the management and control system to reestablish a long connection with the target virtualized network function instance. By using the method, the long connection can be reestablished.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a long-connection reconstruction method, apparatus, computer equipment, storage medium, and product. Background Technology

[0002] With the continuous application of cloud-native and virtualization technologies, network equipment is increasingly virtualizing and cloudifying. Core network services such as the 5G Core Network (5GC), Virtualized IP Multimedia Subsystem (vIMS), and Virtual Broadband Remote Access Server (vBRAS), as well as communication technology (CT) service platforms such as 5G messaging and fraud prevention, are all being virtualized and deployed in the cloud. To achieve awareness and control of cross-vendor Virtualized Network Function (VNF) instances, operators typically use acquisition and control systems to establish long-lived connections with VNF instances. Through these systems, they can configure and control VNF instances, perform intelligent anomaly handling, and ultimately achieve a closed loop of self-awareness, self-optimization, and self-adjustment of services, ensuring high availability.

[0003] In related technologies, cloud platforms decouple computing resources from network resources such as IP addresses, enabling resource scheduling for VNF instances and achieving extremely high flexibility and resource utilization. However, once the lifecycle state of a VNF instance changes, such as instance restart after being stopped, instance elastic scaling (creating new instances), or fault recovery (migration), the original IP address of the VNF instance returns to the resource pool, thereby interrupting the long-term connection between the acquisition and control system and the VNF instance. This makes it impossible to achieve acquisition and control configuration of the VNF instance, intelligent anomaly handling, etc., thus affecting business processing. Summary of the Invention

[0004] Therefore, it is necessary to provide a long connection reconstruction method, apparatus, computer equipment, storage medium, and product capable of re-establishing long connections to address the aforementioned technical problems.

[0005] In a first aspect, this application provides a long-connection reconstruction method applied to a proxy server, the method comprising:

[0006] Receive a first change message sent by the cloud platform, the first change message being used to indicate that the instance network address of the target virtualized network function instance has changed;

[0007] Based on the first change message, a second change message is sent to the acquisition and control system that manages the target virtualized network function instance. The second change message is used to instruct the acquisition and control system to re-establish a long connection with the target virtualized network function instance.

[0008] In one embodiment, the first change message includes an instance identifier of the target virtualized network function instance and a new instance network address; the step of sending a second change message to the acquisition and control system that manages the target virtualized network function instance according to the first change message includes: if the new instance network address is different from the current instance network address corresponding to the instance identifier, sending the second change message to the acquisition and control system according to the instance identifier.

[0009] In one embodiment, sending the second change message to the acquisition and control system based on the instance identifier includes: obtaining the acquisition and control network address of the acquisition and control system corresponding to the pre-stored instance identifier; sending the second change message to the acquisition and control system based on the acquisition and control network address, wherein the second change message includes the new instance network address, and the new instance network address is used for the acquisition and control system to re-establish a long connection with the target virtualized network function instance.

[0010] In one embodiment, the first change message includes an instance identifier of the target virtualized network function instance and a new instance network address; the method further includes: querying a target correspondence from a database based on the instance identifier, and updating the current instance network address in the target correspondence to the new instance network address; storing the updated target correspondence in the database; wherein the target correspondence includes the correspondence between the instance identifier of the target virtualized network function instance, the current instance network address, and the acquisition and control network address of the acquisition and control system.

[0011] In one embodiment, the method further includes: receiving a scheduling message sent by the cloud platform, the scheduling message indicating that the cloud platform has completed the initial scheduling of the target virtualized network function instance; receiving a connection message sent by the acquisition and control system, the connection message indicating that an initial long connection has been established between the acquisition and control system and the target virtualized network function instance; establishing and storing a target correspondence based on the scheduling message and the connection message, the target correspondence including the correspondence between the instance identifier of the target virtualized network function instance, the current instance network address, and the acquisition and control network address of the acquisition and control system.

[0012] In one embodiment, the scheduling message includes the instance identifier and the current instance network address, and the connection message includes the acquisition and control network address and the current instance network address; establishing and storing the target correspondence based on the scheduling message and the connection message includes: upon receiving the scheduling message, establishing an initial correspondence between the instance identifier and the current instance network address, and storing the initial correspondence in a database; upon receiving the connection message, querying the initial correspondence from the database based on the current instance network address in the connection message, and writing the acquisition and control network address into the acquisition and control system field in the database corresponding to the initial correspondence, thereby obtaining the target correspondence.

[0013] In one embodiment, receiving the first change message sent by the cloud platform includes: receiving the first change message published by the cloud platform through a publish-subscribe model.

[0014] In one embodiment, sending the second change message to the acquisition and control system that manages the target virtualized network function instance includes: sending the second change message to the acquisition and control system via a publish-subscribe model.

[0015] Secondly, this application also provides a long-connection reconstruction method, applied to a data acquisition and control system, the method comprising:

[0016] Receive a second change message sent by the proxy server based on the first change message, wherein the first change message is used to indicate that the instance network address of the target virtualization network function instance has changed, and the second change message includes the new instance network address of the target virtualization network function instance;

[0017] Based on the new instance network address, a long-lived connection is re-established with the target virtualized network function instance.

[0018] In one embodiment, the method further includes: sending a connection message to the proxy server when an initial long connection has been established with the target virtualized network function instance; the connection message includes the acquisition and control network address of the acquisition and control system and the current instance network address of the target virtualized network function instance; the connection message is used to instruct the proxy server to establish a target correspondence, the target correspondence includes the instance identifier of the target virtualized network function instance, and the correspondence between the current instance network address and the acquisition and control network address.

[0019] Thirdly, this application also provides a long-connection reconstruction device for use in a proxy server, the device comprising:

[0020] The first receiving module is used to receive a first change message sent by the cloud platform, wherein the first change message is used to indicate that the instance network address of the target virtualized network function instance has been changed;

[0021] The first sending module is configured to send a second change message to the acquisition and control system that manages the target virtualized network function instance based on the first change message. The second change message is used to instruct the acquisition and control system to re-establish a long connection with the target virtualized network function instance.

[0022] Fourthly, this application also provides a long-connection reconstruction device for use in a data acquisition and control system, the device comprising:

[0023] The second receiving module is configured to receive a second change message sent by the proxy server according to the first change message, wherein the first change message is used to indicate that the instance network address of the target virtualization network function instance has changed, and the second change message includes the new instance network address of the target virtualization network function instance.

[0024] The reconstruction module is used to re-establish a long-lived connection with the target virtualized network function instance based on the new instance network address.

[0025] Fifthly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the long connection reconstruction method provided in the first and / or second aspects of this application.

[0026] Sixthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the long-connection reconstruction method provided in the first and / or second aspects of this application.

[0027] In a seventh aspect, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the long connection reconstruction method provided in the first and / or second aspects of this application.

[0028] The aforementioned long-connection reconstruction method, apparatus, computer equipment, computer-readable storage medium, and computer program product involve a proxy server receiving a first change message from a cloud platform. This first change message indicates that the instance network address of the target virtualized network function instance has changed. Based on the first change message, the proxy server sends a second change message to the acquisition and control system managing the target virtualized network function instance. This second change message instructs the acquisition and control system to re-establish the long-connection with the target virtualized network function instance. Therefore, in this application, the proxy server learns that the instance network address of the target virtualized network function instance has changed by receiving the first change message from the first cloud platform, and can send a second change message to the acquisition and control system managing the target virtualized network function instance to notify the acquisition and control system that the instance network address of the target virtualized network function instance has changed, and instruct the acquisition and control system to re-establish the long-connection with the target virtualized network function instance. Therefore, by using a proxy server, the acquisition and control system can promptly detect changes in instance network addresses and proactively trigger a long-connection reconstruction process. This reconstruction avoids prolonged interruptions to long-connections caused by instance network address changes, ensuring the acquisition and control system can continue to manage the target virtualized network function instance and thus guaranteeing business continuity. Furthermore, this application does not require disabling high-availability features of the cloud platform or developing a high-availability mechanism for the instance, leveraging the advantages of the cloud platform while avoiding additional R&D costs. Attached Figure Description

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

[0030] Figure 1 This is a diagram illustrating the application environment of a long-connection reconstruction method in one embodiment.

[0031] Figure 2 This is a flowchart illustrating the long-connection reconstruction method in the first embodiment;

[0032] Figure 3 This is a flowchart illustrating the long-connection reconstruction method in the second embodiment;

[0033] Figure 4 This is a flowchart illustrating the third method for reconstructing medium- and long-term connections.

[0034] Figure 5 This is a flowchart illustrating a long-connection reconstruction method in a specific example.

[0035] Figure 6 This is a schematic diagram illustrating how a proxy server interacts with the scheduler and the acquisition and control system to achieve long-term connection reconstruction in an example.

[0036] Figure 7 This is a flowchart illustrating the long-connection reconstruction method in the fourth embodiment;

[0037] Figure 8 This is a structural block diagram of the long-connection reconstruction device in the first embodiment;

[0038] Figure 9 This is a structural block diagram of the long connection reconstruction device in the second embodiment;

[0039] Figure 10 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0040] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0041] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the embodiments, or any combination of multiple embodiments.

[0042] Explanation of terms used in this application:

[0043] Persistent connection: After the two communicating parties complete a handshake, the link remains open. There is no need to re-establish the connection for each transmission. Data can be sent and received repeatedly in both directions in real time with low latency until it is explicitly closed or abnormally disconnected. It is often used in scenarios that require high-frequency and continuous data exchange, such as data acquisition and control, push notifications, IM, and IoT.

[0044] VNF instances are business processes that run on cloud infrastructure after the functions of traditional physical network devices (such as routers, firewalls, broadband gateways, etc.) are implemented in software. They can be understood as "virtual network devices in operation" and are the objects of operation and maintenance management of the acquisition and control system.

[0045] Data Acquisition and Control System: A platform used by operators for operation and maintenance management of VNF instances, including configuration distribution, status acquisition, and anomaly handling.

[0046] While cloud platforms enable resource scheduling for VNF instances, achieving high flexibility and resource utilization, they also present challenges. In high-availability VNF instance scenarios, if the lifecycle state of a VNF instance changes and its original IP address returns to the resource pool, the instance's IP address changes. However, the acquisition and control system cannot detect this change, making it impossible to re-establish long connections or perform intelligent configuration and anomaly handling for subsequent VNF ​​instances.

[0047] To avoid this problem, one option is to disable the high availability-related functions of the cloud platform, but this would prevent cloud-native technologies from taking full advantage. Another option is to ensure high availability, where equipment manufacturers need to develop high availability mechanisms for VNF instances, but this requires a significant investment of additional R&D costs, which is time-consuming and labor-intensive.

[0048] To address this, this application proposes a long-connection reconstruction method. This method involves adding a proxy service to maintain the correspondence between the virtualized network function instance IP, instance ID, and the long-connection acquisition and control system IP. It also incorporates a publish-subscribe mechanism to transmit IP address change messages between the proxy server, cloud platform scheduler, and acquisition and control system. This enables the acquisition and control system to be aware of instance IP address changes, laying the foundation for subsequent long-connection reconstruction.

[0049] The following describes a long-connection reconstruction method according to an embodiment of this application.

[0050] The long-connection reconstruction method provided in this application can be applied to, for example... Figure 1 In the application environment shown, the proxy server 101 communicates with the schedulers of the acquisition and control system 102 and the cloud platform 103. The cloud platform 103 includes a scheduler and at least one host. The host (i.e., the server) is used to host the operation of at least one VNF instance. The scheduler is used to perform lifecycle scheduling operations such as creation, migration, and elastic scaling of the VNF instance. For example, when a failure or maintenance occurs, the VNF instance may be migrated to another host by the scheduler. The acquisition and control system 102 (as a client) is used for operation and maintenance management of the VNF instance, such as configuration distribution, status collection, and anomaly handling.

[0051] In one exemplary embodiment, such as Figure 2 As shown, a long-connection reconstruction method is provided, which is applied to Figure 1 The proxy server 101 includes the following steps 201 and 202. Wherein:

[0052] Step 201: Receive a first change message sent by the cloud platform. The first change message is used to indicate that the instance network address of the target virtualized network function instance has been changed.

[0053] The target virtualized network function instance refers to any one of the at least one virtualized network function instances. The instance network address includes the instance IP address.

[0054] It's important to note that the change of the instance network address of a virtualized network function (VNF) instance essentially refers to a low-level change triggered by the cloud platform's resource scheduling (a change imperceptible to the acquisition and control system). For example, taking VNF instance migration as an example, when the cloud platform's scheduler detects an anomaly or insufficient computing resources on a host, it will rebuild the same VNF instance on another host and assign it a new network address. Before and after the migration, the instance's physical location (i.e., the host it runs on) changes, but the instance's identity (i.e., ID) and business functions remain unchanged. Therefore, from the acquisition and control system's perspective, since the instance's identity remains unchanged, it identifies it as the same VNF instance. However, because the previous network address has been recycled to the resource pool, the acquisition and control system cannot use the previous network address to continue communicating with the VNF instance.

[0055] For example, the scheduler of cloud platform 103 schedules at least one virtualized network function instance, such as creating instances, migrating instances, and elastic scaling. If the instance network address of a target virtualized network function instance changes due to the scheduler's scheduling, the scheduler immediately generates a first change message and promptly sends the first change message to proxy server 101 to quickly notify proxy server 101 that the instance network address of the target virtualized network function instance has changed.

[0056] Step 202: Based on the first change message, send a second change message to the acquisition and control system that manages the target virtualized network function instance. The second change message is used to instruct the acquisition and control system to re-establish the long connection with the target virtualized network function instance.

[0057] It should be noted that the acquisition and control system and the virtualized network function instance have a one-to-many relationship, that is, one acquisition and control system can manage at least one virtualized network function instance, and one virtualized network function instance is managed by one acquisition and control system.

[0058] For example, the database of proxy server 101 pre-stores the correspondence between the acquisition and control system and the virtualized network function instance. After receiving the first change message, proxy server 101, since the first change message indicates that the instance network address of the target virtualized network function instance has changed, promptly queries the database for the acquisition and control system corresponding to the target virtualized network function instance, that is, the acquisition and control system managing the target virtualized network function instance, and determines the second change message according to the first change message, and promptly sends the second change message to acquisition and control system 102. The second change message is used to instruct the acquisition and control system to re-establish the long connection with the target virtualized network function instance. After receiving the second change message, acquisition and control system 102 detects that the instance network address of the target virtualized network function instance has changed, that is, its long connection with the target virtualized network function instance has been interrupted. Therefore, it immediately initiates a long connection request to the target virtualized network function instance according to the instruction of the second change message, thereby re-establishing the long connection with the target virtualized network function instance, so as to avoid the inability to detect the long connection interruption and cause the business to be unable to continue operation and maintenance management. After successful reconstruction, acquisition and control system 102 resumes control over the target virtualized network function instance.

[0059] It should be noted that during the long connection reconstruction process, the acquisition and control system 102 cannot effectively manage the target VNF ​​instance, but it retains management permissions and historical management information for the target VNF ​​instance. After successful reconstruction, management operations can be restored based on the historical management information to ensure the continuity and reliability of business processing. In one possible implementation, after receiving the second change message, the acquisition and control system 102, while actively triggering the reconnection, outputs a prompt message through the human-machine interface to inform the operator that a long connection reconstruction process is currently being performed, suspending the operation and maintenance management of the target virtualized network function instance. The prompt message may include the instance identifier of the target virtualized network function instance, the start time of the long connection reconstruction, the expected end time of the reconstruction, and the number of reconnection attempts.

[0060] In the aforementioned long-connection reconstruction method, the proxy server receives a first change message sent by the cloud platform. This first change message indicates that the instance network address of the target virtualized network function instance has changed. Based on the first change message, the proxy server sends a second change message to the acquisition and control system managing the target virtualized network function instance. This second change message instructs the acquisition and control system to re-establish the long-connection with the target virtualized network function instance. Therefore, in this application, the proxy server learns that the instance network address of the target virtualized network function instance has changed by receiving the first change message from the cloud platform. It can also send a second change message to the acquisition and control system managing the target virtualized network function instance to notify the system that the instance network address has changed and instruct the system to re-establish the long-connection with the target virtualized network function instance. Thus, the proxy server enables the acquisition and control system to promptly detect changes in the instance network address and proactively trigger the long-connection reconstruction process. This reconstruction avoids prolonged interruptions to the long-connection due to instance network address changes, ensuring that the acquisition and control system can continue to manage the target virtualized network function instance and thus ensuring the continuity of business processing. In addition, this application does not require disabling the high availability-related functions of the cloud platform, nor does it require developing a high availability mechanism for the instance. This allows us to leverage the advantages of the cloud platform while avoiding additional R&D costs.

[0061] The following is an example description of how proxy server 101 sends the second change message.

[0062] In one exemplary embodiment, the first change message includes the instance identifier of the target virtualized network function instance and the new instance network address. For example... Figure 3 As shown, step 201 includes: if the new instance network address is different from the current instance network address corresponding to the instance identifier, send a second change message to the acquisition and control system according to the instance identifier.

[0063] The database of proxy server 101 pre-stores the instance identifiers of each VNF instance and the corresponding current instance network address. The instance identifier (ID) identifies the logical identity of a VNF instance, is unique, and persists throughout the instance's entire lifecycle. The instance ID remains unchanged throughout its lifecycle; that is, it is typically preserved until the instance is deleted. The instance network address indicates the VNF instance's location in the network and is variable; it can be an Internet Protocol (IP) address.

[0064] For example, the first change message includes the instance ID of the target VNF ​​instance and the new instance IP address, and may also include notification information (notifying that the IP address has changed) and a timestamp (indicating the moment the network address changed). After receiving the first change message, the proxy server 101 extracts the new instance IP address and instance ID. Since the database pre-stores the current instance IP address corresponding to the instance ID of each VNF instance, the proxy server 101 uses the extracted instance ID as an index to query the database for the current instance IP address corresponding to that instance ID, and compares the new instance IP address with the current instance IP address. If the two are inconsistent, it means that the first change message is correct and the IP address has indeed changed. Then, the proxy server 101 immediately determines the acquisition and control system corresponding to the target VNF ​​instance based on the instance IP, and immediately sends the second change message, which instructs to re-establish the long connection, to that acquisition and control system. If the two are consistent, it means that the first change message is incorrect or duplicated, so there is no need to send the second change message.

[0065] Therefore, in this embodiment, when the new instance network address is inconsistent with the current instance network address, a second change message is promptly sent to the corresponding acquisition and control system based on the instance identifier to instruct the acquisition and control system to re-establish a long connection to the target VNF ​​instance. This can verify whether the current instance network address has indeed changed. If so, the second change message is sent in a timely manner, improving the reliability of long connection reconstruction and avoiding accidental triggering of the reconstruction process.

[0066] In one example, in the previous embodiment, sending a second change message to the acquisition and control system based on the instance identifier includes: obtaining the acquisition and control network address of the acquisition and control system corresponding to the pre-stored instance identifier; and sending a second change message to the acquisition and control system based on the acquisition and control network address. The second change message includes a new instance network address, which is used by the acquisition and control system to re-establish a long connection with the target virtualized network function instance.

[0067] In the database of proxy server 101, the instance identifier of each VNF instance and the acquisition and control network address of the acquisition and control system corresponding to the instance identifier are pre-stored, such as the acquisition and control IP address.

[0068] For example, when the proxy server obtains the instance ID and the new instance IP address of the target VNF ​​instance, it uses the instance ID as an index to retrieve the pre-stored acquisition and control system IP address corresponding to the instance ID from the database, and sends the second change message to the acquisition and control system based on the acquisition and control IP address. The second change message includes a reconstruction instruction, the instance ID, and the new instance IP address. After receiving the second change message, the acquisition and control system can identify the long connection reconstruction target based on the instance ID, respond to the reconstruction instruction, and initiate a long connection reconstruction process with the target VNF ​​instance based on the new instance IP address. A long connection can be established based on the TCP protocol.

[0069] Therefore, this embodiment uses the instance identifier as an index to obtain the acquisition control network address of the acquisition control system of the target VNF ​​instance, and sends a second change message to the acquisition control system according to the acquisition control network address. This ensures that the second change message is accurately sent to the acquisition control system that has a management relationship with the instance, and avoids sending the second change message to an unrelated acquisition control system, thereby ensuring the accuracy and reliability of the long connection reconstruction command.

[0070] It should be noted that the proxy server 101, through interaction with the scheduler of the cloud platform 103 and the acquisition and control system 102, stores the mapping relationship between the instance ID of each VNF instance, the current instance IP address, and the acquisition and control IP address of the acquisition and control system managing the instance in its database, and updates it dynamically in real time. The specific implementation method is described below as an example.

[0071] In one exemplary embodiment, the first change message includes the instance identifier of the target virtualized network function instance and the new instance network address. For example... Figure 3 As shown, the method further includes steps 301 and 302. Wherein:

[0072] Step 301: Query the target mapping relationship from the database based on the instance identifier, and update the current instance network address in the target mapping relationship to the new instance network address.

[0073] The target correspondence includes the correspondence between the instance identifier of the target virtualized network function instance, the current instance network address, and the acquisition and control network address of the acquisition and control system.

[0074] Step 302: Store the updated target mapping relationship in the database.

[0075] For example, after receiving the first change message and extracting the instance ID and the new instance IP address from it, the proxy server 101, while sending the second change message, uses the instance ID as an index to query the target mapping relationship corresponding to the same instance ID from the database, and replaces the current instance IP address in the target mapping relationship with the new instance IP address to update the target mapping relationship, thereby obtaining the updated target mapping relationship. The updated target mapping relationship is then stored in the database for future queries.

[0076] Therefore, in this embodiment, the proxy server can update the target correspondence in the database in a timely manner, realize the dynamic maintenance of the correspondence between instance identifier, instance network address and acquisition control network address, ensure the accuracy of the correspondence, so as to query the accurate correspondence when rebuilding the long connection next time, and provide a reliable data foundation for subsequent queries.

[0077] It should be noted that the target mapping relationship can be established and stored by the proxy server after the scheduler has completed the initial scheduling of the target VNF ​​instance and the acquisition and control system has established the initial long connection with the target VNF ​​instance. "Initial" refers to the first time.

[0078] That is, in an exemplary embodiment, such as Figure 4 As shown, the method further includes steps 401 to 403. Wherein:

[0079] Step 401: Receive a scheduling message sent by the cloud platform. The scheduling message indicates that the initial scheduling of the target virtualized network function instance by the cloud platform has been completed.

[0080] For example, during the initial scheduling (such as creation) of the target VNF ​​instance, the scheduler determines in real time whether the initial scheduling of the target VNF ​​instance is complete. If yes, it immediately sends scheduling information to the proxy server 101 to notify the proxy server 101 that the initial scheduling of the target VNF ​​instance is complete; if no, it continues to perform the initial scheduling of the target VNF ​​instance until it is complete.

[0081] Step 402: Receive a connection message sent by the acquisition and control system. The connection message indicates that an initial long connection has been established between the acquisition and control system and the target virtualized network function instance.

[0082] For example, the acquisition and control system, acting as a client, establishes an initial long connection with the target VNF ​​instance. Upon successful establishment of the initial long connection, the acquisition and control system immediately sends connection information to the proxy server 101 to notify the proxy server 101 that its initial long connection with the target VNF ​​instance has been established. The establishment of the initial long connection may be actively triggered by the acquisition and control system under the instruction of the operator.

[0083] The initial long connection in step 402 and the initial scheduling in step 401 are independent of each other and do not affect each other. The execution order of steps 401 and 402 is not restricted. In practical applications, it may be that step 401 is executed first and then step 402, or step 402 is executed first and then step 401, or steps 401 and 402 are executed simultaneously.

[0084] Step 403: Establish and store the target correspondence based on the scheduling message and connection message. The target correspondence includes the correspondence between the instance identifier of the target virtualized network function instance, the current instance network address, and the acquisition and control network address of the acquisition and control system.

[0085] The scheduling message includes the instance identifier of the target VNF ​​instance and the current instance network address, while the connection message includes the acquisition and control network address of the acquisition and control system and the current instance network address of the target VNF ​​instance.

[0086] For example, when the proxy server 101 receives the scheduling message and the completion message, if the current instance IP address is the same in both, it establishes a correspondence between the instance ID, the current instance IP address and the acquisition and control IP address to obtain the target correspondence, and stores it in the database for querying when rebuilding the long connection later.

[0087] Specifically, after receiving the first change message, proxy server 101 uses the instance ID in the first change message as an index to query the current instance IP address in the target mapping relationship and compares it with the new instance IP address in the first change message. If the two are different, it can further confirm that the instance IP address has changed. Then, the proxy server sends a second change message to the acquisition and control system according to the acquisition and control IP address in the target mapping relationship to indicate that the long connection reconstruction should be actively triggered.

[0088] Therefore, in this embodiment, the proxy server promptly establishes and stores the target correspondence in the database upon initial scheduling and completion of the initial long connection, so as to query the target correspondence when re-establishing the long connection and reliably send the second change message.

[0089] In one example, step 403 includes: upon receiving a scheduling message, establishing an initial correspondence between the instance identifier and the current instance network address, and storing the initial correspondence in a database; upon receiving a connection message, querying the initial correspondence from the database based on the current instance network address in the connection message, and writing the acquisition and control network address into the acquisition and control system field in the database corresponding to the initial correspondence, thereby obtaining the target correspondence.

[0090] For example, when proxy server 101 receives a scheduling message, it parses and extracts the instance ID and the current instance IP address, establishes an initial mapping between the two, and stores it in the database. When proxy server 101 receives a connection message, it parses and extracts the acquisition and control IP address and the current instance IP address, uses the current instance IP address as an index to query the database for the initial mapping between the current instance IP address, and writes the acquisition and control network address into the acquisition and control system field corresponding to the initial mapping, thus obtaining the target mapping, thereby realizing the establishment and storage of the target mapping.

[0091] Therefore, this embodiment establishes a correspondence between the instance identifier, the instance network address, and the acquisition and control network address based on the received current instance network address. This ensures the accuracy of the correspondence and stores it in the database for easy subsequent querying and updating, thereby guaranteeing the reliability of long connection reconstruction.

[0092] It should be noted that the communication between the proxy server 101, the cloud platform 103, and the acquisition and control system 102 is based on a publish-subscribe mechanism. In this mechanism, the cloud platform's scheduler acts as the publisher, the proxy server acts as both a subscriber and a publisher, and the acquisition and control system acts as both a publisher and a subscriber. An exemplary description follows.

[0093] In one exemplary embodiment, step 201 includes: receiving a first change message published by the cloud platform via a publish-subscribe model.

[0094] For example, the scheduler and the proxy server 101 communicate via a publish-subscribe pattern. If the instance IP address of the target VNF ​​instance changes due to scheduling, the scheduler publishes a first change message including the new instance IP address and instance ID. The proxy server 101, as a subscriber, subscribes to the message in real time and updates the target mapping relationship in the database.

[0095] Similarly, after the scheduler performs the initial scheduling of the VNF instance (such as creation, migration, failure restart, etc.), it publishes a scheduling message, including the current instance IP address and instance ID. The proxy server subscribes to the scheduling message and saves the mapping between the current instance IP address and instance ID to the database.

[0096] Therefore, in this embodiment, the proxy server subscribes to the first change message published by the cloud platform through a publish-subscribe model, thereby decoupling the cloud platform and the proxy server. The two parties do not need to know each other's physical address or running status to complete the reliable transmission of information, which can ensure the efficiency and real-time nature of instance network address change perception and notification.

[0097] In an exemplary embodiment, step 201, sending a second change message to the acquisition and control system that manages the target virtualized network function instance, includes sending the second change message to the acquisition and control system via a publish-subscribe model.

[0098] For example, the proxy server 101 and the acquisition and control system 102 communicate through a publish-subscribe mode. When the proxy server 101 receives the first change message, it acts as a publisher and publishes a second change message including the instance ID and the new instance IP address according to the first change message. The acquisition and control system 102 acts as a subscriber, subscribes to the message in real time, and re-establishes a long connection between the target VNF ​​instance according to the message.

[0099] Similarly, after the acquisition and control system successfully establishes the initial long connection with the virtualization device instance, the acquisition and control system, as the publisher, publishes a connection message including the instance IP address and the acquisition and control IP address. The proxy server subscribes to this message and writes the acquisition and control IP address into the acquisition and control system IP field in the database.

[0100] In summary, if the instance IP address of the target VNF ​​instance changes due to scheduling, the proxy server receives the new instance IP address through the publish-subscribe mechanism, updates the instance IP address in the database, publishes the new instance IP address, and after the acquisition and control system subscribes to the instance IP address change, it initiates a long connection request with the new instance IP address to re-establish the long connection.

[0101] Therefore, in this embodiment, the proxy server publishes the second change message through the publish-subscribe model, thereby decoupling the proxy server and the acquisition and control system. The two parties do not need to know each other's physical address or operating status to complete the reliable transmission of information, which can ensure the efficiency and real-time nature of instance network address change perception and notification.

[0102] The long-connection reconstruction method of this application is described below with a detailed example.

[0103] like Figure 5 As shown, the long-connection reconstruction method includes the following steps:

[0104] Step 501: The scheduler performs the initial scheduling of the target VNF ​​instance;

[0105] Step 502: The scheduler determines in real time whether the initial scheduling is complete. If yes, proceed to step 503; otherwise, return to step 501.

[0106] Step 503: The scheduler publishes a scheduling message; the scheduling message is used to indicate that the scheduler has completed the initial scheduling of the target VNF ​​instance, and the scheduling message includes the instance ID of the target VNF ​​instance and the current instance IP address.

[0107] Step 504: The data acquisition and control system establishes an initial long connection with the target VNF ​​instance and publishes a connection message; the connection message includes the data acquisition and control IP address and the current instance IP address;

[0108] Step 505: After the proxy server subscribes to the scheduling message, it stores the initial mapping between the instance ID of the target VNF ​​instance and the current instance IP address in the database.

[0109] Step 506: After the proxy server subscribes to the connection message, it writes the acquisition and control IP address in it into the acquisition and control system field corresponding to the initial mapping relationship to obtain the target mapping relationship between the instance ID, the current instance IP address and the acquisition and control IP address.

[0110] Step 507: The scheduler determines whether the instance IP address of the target VNF ​​instance has changed. If yes, proceed to step 508; otherwise, end the process.

[0111] Step 508, the scheduler publishes a first change message; the first change message is used to indicate that the instance network address of the target virtualized network function instance has changed, and the first change message includes the instance ID of the target VNF ​​instance and the new instance IP address;

[0112] Step 509: When the proxy server subscribes to the first change message, it queries the target correspondence based on the instance ID to obtain the current instance IP address and acquisition control IP address corresponding to the instance ID;

[0113] Step 510: The proxy server determines whether the new instance IP address is different from the current instance IP address in the target mapping. If yes, proceed to step 511; otherwise, end the process.

[0114] Step 511: Update the current instance IP address in the target mapping to the new instance IP address;

[0115] Step 512: Send a second change message to the acquisition and control system based on the acquisition and control IP address. The second change message includes the instance ID and the new instance IP address.

[0116] Step 513: The acquisition and control system subscribes to the second change message and re-establishes a long connection with the target VNF ​​instance based on the new instance IP address.

[0117] In practical applications, changes occur during the lifecycle of a VNF instance. For example, if a VNF instance is migrated to a new host and restored by the cloud platform scheduler due to a host failure, the instance IP address of the VNF instance will change. Using the solution in this application embodiment, the acquisition and control system will promptly detect the address change and proactively trigger the long-connection reconstruction process, avoiding the phenomenon where the acquisition and control system fails to detect the address change, resulting in prolonged long-connection interruptions and ineffective instance management. The following section combines... Figure 6 The overall solution of this application embodiment is illustrated using fault recovery as an example.

[0118] like Figure 6 As shown, during the initialization phase, the scheduler completes the initial scheduling of VFN instance 1 deployed on host 1 (referred to as old VFN instance 1 for distinction), and publishes the instance ID and current instance IP address of the instance. The proxy server subscribes to the information and stores the correspondence between the two in the database. After the acquisition and control system establishes a long connection with VNF instance 1 on host 1, it publishes the acquisition and control IP address and the corresponding instance IP address. The proxy server subscribes to the information and completes or updates the three-way correspondence (instance ID, instance IP address, acquisition and control IP address) in the database accordingly. When VNF instance 1 on host 1 is migrated to host 2 by the scheduler after fault recovery and becomes a new VNF instance 1 (the new VNF instance 1 is the same instance as the old VNF instance 1), the long-lived connection between the acquisition and control system and this instance is interrupted (the red "×" in the diagram indicates a long-lived connection interruption). The IP address of this instance changes to a new IP address (e.g., from IP1 to IP2). The scheduler then publishes the instance ID and the new IP address. After subscribing, the proxy server uses the instance ID as an index to update the IP address in the three-way correspondence in the database from IP1 to IP2, and publishes a reconstruction command including IP2 to the acquisition and control system. Upon receiving the reconstruction command, the acquisition and control system actively triggers the TCP long-lived connection reconstruction process with VNF instance 1 on the migrated host 2 based on IP2. Thus, through the proxy server and the publish-subscribe mechanism, the system achieves the awareness of VNF instance IP address changes and the rapid reconstruction of long-lived connections. This solves the problem in related technologies where the acquisition and control system cannot detect IP changes leading to long-term or persistent interruptions of long-lived connections, without needing to disable the cloud platform's high availability mechanism or develop additional high availability mechanisms for the instance.

[0119] In summary, this application's embodiments add a proxy service to maintain the correspondence between VNF instance IP addresses, instance IDs, and the long-connection acquisition and control system IP addresses. Combined with a publish-subscribe mechanism, it transmits IP address change messages between the proxy server, cloud platform scheduler, and acquisition and control system, enabling the acquisition and control system to promptly detect instance IP address changes and re-establish long connections in response, laying the foundation for maintaining long connections. This long connection reconstruction method has minimal invasiveness to the cloud platform, acquisition and control system, and VNF instances, while also facilitating VNF instances to utilize the cloud platform's high availability capabilities such as fault recovery, elastic scaling, and self-healing, simplifying VNF instance development.

[0120] In one exemplary embodiment, such as Figure 7 As shown, a long-connection reconstruction method is provided, which is applied to Figure 1 The data acquisition and control system 102 includes the following steps 701 and 702. Wherein:

[0121] Step 701: Receive the second change message sent by the proxy server based on the first change message.

[0122] The first change message indicates that the instance network address of the target virtualized network function instance has changed, and the second change message indicates that the acquisition and control system re-establishes a long connection with the target virtualized network function instance. The second change message includes the new instance network address of the target virtualized network function instance and also includes the instance identifier.

[0123] Step 702: Re-establish a long connection with the target virtualized network function instance based on the new instance network address.

[0124] For example, the acquisition and control system 102 subscribes to messages in real time. After subscribing to the second change message sent by the proxy server 101, it parses and extracts the instance ID and the new instance IP address, and re-establishes a long connection with the target VNF ​​instance based on the new instance IP address.

[0125] In the aforementioned long-connection reconstruction method, the acquisition and control system receives a second change message sent by the proxy server based on a first change message. The first change message indicates that the instance network address of the target virtualized network function instance has changed, and the second change message includes the new instance network address of the target virtualized network function instance. Based on the new instance network address, a new long-connection is established with the target virtualized network function instance. Therefore, in this application, the acquisition and control system, in response to the received second change message, detects that the instance network address of the target virtualized network function instance has changed and re-establishes a long-connection with the target virtualized network function instance. Thus, the acquisition and control system can promptly detect changes in the instance network address and proactively trigger the long-connection reconstruction process. This reconstruction avoids prolonged interruptions to the long-connection due to instance network address changes, ensuring that the acquisition and control system can continue to manage the target virtualized network function instance, thereby ensuring the continuity of business processing. Furthermore, this application does not require disabling the high-availability features of the cloud platform or developing a high-availability mechanism for instances, leveraging the advantages of the cloud platform while avoiding additional R&D costs.

[0126] In one exemplary embodiment, the method further includes sending a connection message to a proxy server if an initial long connection has been established with the target virtualized network function instance.

[0127] The connection message instructs the proxy server to establish a target mapping relationship. This mapping relationship includes the instance identifier of the target virtualized network function instance, the mapping between the current instance network address and the acquisition and control network address, and the acquisition and control system's acquisition and control network address.

[0128] For example, the acquisition and control system, acting as a client, establishes an initial long connection with the target VNF ​​instance. Upon successful establishment of the initial long connection, the acquisition and control system immediately sends connection information to the proxy server 101 to notify the proxy server 101 that its initial long connection with the target VNF ​​instance has been established. The establishment of the initial long connection may be actively triggered by the acquisition and control system under the instruction of the operator.

[0129] After receiving the connection message, proxy server 101 establishes and stores the three-way correspondence between the instance ID, instance IP address, and acquisition control IP address based on the connection message and the scheduling message sent by the cloud platform, for subsequent querying when rebuilding the long connection.

[0130] Therefore, by sending an initial long connection success message to the proxy server, this embodiment can ensure that the proxy server establishes and stores accurate and reliable target correspondence.

[0131] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0132] Based on the same inventive concept, this application also provides a long connection reconstruction apparatus for implementing the long connection reconstruction method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in one or more long connection reconstruction apparatus embodiments provided below can be found in the limitations of the long connection reconstruction method described above, and will not be repeated here.

[0133] In one exemplary embodiment, such as Figure 8 As shown, a long-connection reconstruction device is provided, which is applied to... Figure 1 The proxy server 101 in the device includes: a first receiving module 801 and a first sending module 802, wherein:

[0134] The first receiving module 801 is used to receive a first change message sent by the cloud platform, wherein the first change message is used to indicate that the instance network address of the target virtualized network function instance has been changed;

[0135] The first sending module 802 is used to send a second change message to the acquisition and control system that manages the target virtualized network function instance according to the first change message. The second change message is used to instruct the acquisition and control system to re-establish a long connection with the target virtualized network function instance.

[0136] In one embodiment, the first change message includes an instance identifier of the target virtualized network function instance and a new instance network address; the first sending module 802 includes: a sending unit, configured to send the second change message to the acquisition and control system according to the instance identifier when the new instance network address is different from the current instance network address corresponding to the instance identifier.

[0137] In one embodiment, the sending unit is specifically configured to: obtain the acquisition control network address of the acquisition control system corresponding to the pre-stored instance identifier; send the second change message to the acquisition control system according to the acquisition control network address, wherein the second change message includes the new instance network address, and the new instance network address is used for the acquisition control system to re-establish a long connection with the target virtualized network function instance.

[0138] In one embodiment, the first change message includes an instance identifier of the target virtualized network function instance and a new instance network address; the apparatus further includes: a query module, configured to query a target correspondence from a database based on the instance identifier and update the current instance network address in the target correspondence to the new instance network address; and a storage module, configured to store the updated target correspondence in the database; wherein the target correspondence includes the correspondence between the instance identifier of the target virtualized network function instance, the current instance network address, and the acquisition and control network address of the acquisition and control system.

[0139] In one embodiment, the apparatus further includes: a third receiving module, configured to receive a scheduling message sent by the cloud platform, the scheduling message indicating that the cloud platform has completed the initial scheduling of the target virtualized network function instance; a fourth receiving module, configured to receive a connection message sent by the acquisition and control system, the connection message indicating that an initial long connection has been established between the acquisition and control system and the target virtualized network function instance; and an establishment and storage module, configured to establish and store a target correspondence based on the scheduling message and the connection message, the target correspondence including the correspondence between the instance identifier of the target virtualized network function instance, the current instance network address, and the acquisition and control network address of the acquisition and control system.

[0140] In one embodiment, the scheduling message includes the instance identifier and the current instance network address, and the connection message includes the acquisition and control network address and the current instance network address. The establishment and storage module is specifically configured to: upon receiving the scheduling message, establish an initial correspondence between the instance identifier and the current instance network address, and store the initial correspondence in a database; upon receiving the connection message, query the initial correspondence from the database based on the current instance network address in the connection message, and write the acquisition and control network address into the acquisition and control system field in the database corresponding to the initial correspondence, thereby obtaining the target correspondence.

[0141] In one embodiment, the first receiving module 801 is specifically used to: receive the first change message published by the cloud platform through a publish-subscribe mode.

[0142] In one embodiment, when the first sending module 802 sends a second change message to the acquisition and control system that manages the target virtualized network function instance, it is specifically used to: send the second change message to the acquisition and control system through a publish-subscribe mode.

[0143] In one exemplary embodiment, such as Figure 9 As shown, a long-connection reconstruction device is provided, which is applied to... Figure 1 The acquisition and control system 102 includes: a second receiving module 901 and a reconstruction module 902, wherein:

[0144] The second receiving module 901 is used to receive a second change message sent by the proxy server according to the first change message, wherein the first change message is used to indicate that the instance network address of the target virtualization network function instance has changed, and the second change message includes the new instance network address of the target virtualization network function instance.

[0145] Reconstruction module 902 is used to re-establish a long connection with the target virtualized network function instance based on the new instance network address.

[0146] In one embodiment, the apparatus further includes: a second sending module, configured to send a connection message to the proxy server when an initial long connection has been established with the target virtualized network function instance; the connection message includes the acquisition and control network address of the acquisition and control system and the current instance network address of the target virtualized network function instance; the connection message is used to instruct the proxy server to establish a target correspondence, the target correspondence including the instance identifier of the target virtualized network function instance, and the correspondence between the current instance network address and the acquisition and control network address.

[0147] Each module in the aforementioned long-connection reconstruction device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0148] In one exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 10As shown, the computer device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores the operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage medium. The database stores long-connection reconstruction data. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When the computer program is executed by the processor, it implements the long-connection reconstruction method described in the above embodiment.

[0149] Those skilled in the art will understand that Figure 10 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0150] In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement a long-connection reconstruction method.

[0151] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements a long-connection reconstruction method.

[0152] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements a long-connection reconstruction method.

[0153] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0154] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0155] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for reconstructing long-connections, characterized in that, Applied to a proxy server, the method includes: Receive a first change message sent by the cloud platform, the first change message being used to indicate that the instance network address of the target virtualized network function instance has changed; Based on the first change message, a second change message is sent to the acquisition and control system that manages the target virtualized network function instance. The second change message is used to instruct the acquisition and control system to re-establish a long connection with the target virtualized network function instance.

2. The method according to claim 1, characterized in that, The first change message includes the instance identifier of the target virtualized network function instance and the new instance network address; The step of sending a second change message to the acquisition and control system managing the target virtualized network function instance based on the first change message includes: If the new instance network address is different from the current instance network address corresponding to the instance identifier, the second change message is sent to the acquisition and control system according to the instance identifier.

3. The method according to claim 2, characterized in that, Sending the second change message to the acquisition and control system based on the instance identifier includes: Obtain the acquisition and control network address of the acquisition and control system corresponding to the pre-stored instance identifier; The second change message is sent to the acquisition and control system according to the acquisition and control network address. The second change message includes the new instance network address, which is used by the acquisition and control system to re-establish a long connection with the target virtualized network function instance.

4. The method according to claim 1, characterized in that, The first change message includes the instance identifier of the target virtualized network function instance and the new instance network address; the method further includes: Based on the instance identifier, query the target correspondence from the database and update the current instance network address in the target correspondence to the new instance network address; Store the updated target mapping relationship in the database; The target correspondence includes the correspondence between the instance identifier of the target virtualized network function instance, the current instance network address, and the acquisition and control network address of the acquisition and control system.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: The system receives a scheduling message sent by the cloud platform, which indicates that the cloud platform has completed the initial scheduling of the target virtualized network function instance. Receive a connection message sent by the acquisition and control system, the connection message being used to indicate that an initial long connection has been established between the acquisition and control system and the target virtualized network function instance; The target correspondence is established and stored based on the scheduling message and connection message. The target correspondence includes the correspondence between the instance identifier of the target virtualized network function instance, the current instance network address, and the acquisition and control network address of the acquisition and control system.

6. The method according to claim 5, characterized in that, The scheduling message includes the instance identifier and the current instance network address, and the connection message includes the acquisition and control network address and the current instance network address; The step of establishing and storing the target correspondence based on the scheduling message and the connection message includes: Upon receiving the scheduling message, an initial mapping relationship is established between the instance identifier and the current instance network address, and the initial mapping relationship is stored in the database; Upon receiving the connection message, the initial correspondence is queried from the database based on the current instance network address in the connection message, and the acquisition and control network address is written into the acquisition and control system field in the database corresponding to the initial correspondence to obtain the target correspondence.

7. The method according to claim 1, characterized in that, The first change message sent by the cloud platform includes: The first change message is received by the cloud platform through a publish-subscribe model.

8. The method according to claim 1, characterized in that, Sending the second change message to the acquisition and control system that manages the target virtualized network function instance includes: The second change message is sent to the acquisition and control system via a publish-subscribe model.

9. A method for reconstructing long-connections, characterized in that, Applied to a data acquisition and control system, the method includes: Receive a second change message sent by the proxy server based on the first change message, wherein the first change message is used to indicate that the instance network address of the target virtualization network function instance has changed, and the second change message includes the new instance network address of the target virtualization network function instance; Based on the new instance network address, a long-lived connection is re-established with the target virtualized network function instance.

10. The method according to claim 9, characterized in that, The method further includes: If an initial long connection has been established with the target virtualized network function instance, a connection message is sent to the proxy server; the connection message includes the acquisition and control network address of the acquisition and control system and the current instance network address of the target virtualized network function instance; The connection message is used to instruct the proxy server to establish a target mapping relationship. The target mapping relationship includes the instance identifier of the target virtualized network function instance, the mapping relationship between the current instance network address and the acquisition and control network address.

11. A long-connection reconstruction device, characterized in that, Applied to a proxy server, the device includes: The first receiving module is used to receive a first change message sent by the cloud platform, wherein the first change message is used to indicate that the instance network address of the target virtualized network function instance has been changed; The first sending module is configured to send a second change message to the acquisition and control system that manages the target virtualized network function instance based on the first change message. The second change message is used to instruct the acquisition and control system to re-establish a long connection with the target virtualized network function instance.

12. A long-connection reconstruction device, characterized in that, The device, used in a data acquisition and control system, includes: The second receiving module is configured to receive a second change message sent by the proxy server according to the first change message, wherein the first change message is used to indicate that the instance network address of the target virtualization network function instance has changed, and the second change message includes the new instance network address of the target virtualization network function instance. The reconstruction module is used to re-establish a long-lived connection with the target virtualized network function instance based on the new instance network address.

13. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 10.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 10.

15. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 10.

Images