Method for realizing high-availability converged communication system code number resource management

Abstract

The invention discloses a high-availability converged communication system code number resource management method, and relates to the technical field of converged communication system code number resource management, which comprises the following steps: S1, distributed storage; s2, roll locking is carried out; s3, carrying out fault transfer; s4, routing the instance graph; s5, carrying out block-level fault diagnosis and recovery; s6, hardware or software vulnerable parts; s7, reconfiguration; and S8, global device configuration. According to the high-availability converged communication system code number resource management method, through unified management and dynamic allocation, limited code number resources can be utilized to the maximum extent, the requirements of different communication technologies and services are met, interconnection and intercommunication between different communication systems and networks are facilitated through unified code number resource management, the overall cooperative capacity is improved, and the communication efficiency is improved. According to the technical scheme, a user can use a unified code number to communicate on different networks and terminals, the user experience is improved, and through continuous data failure recovery, the management stability of code number resources can be maintained, and meanwhile, the security risk can be reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of converged communication system code number resource management, and in particular to a converged communication system code number resource management method for achieving high availability. Background Art

[0002] Converged communication system number resource management refers to the process of planning, allocating, using and managing all types of number resources in the converged communication system. It aims to efficiently and reasonably utilize limited number resources, ensure the accessibility, uniqueness and security of numbers, and support the normal operation of various services in the converged communication system.

[0003] However, the consistency and reliability of the existing code resource management methods of converged communication systems are difficult to ensure, and there is data redundancy between code resources.

[0004] Therefore, in view of this, the existing structure and defects are studied and improved, and a code resource management method for a high-availability converged communication system is proposed. Summary of the invention

[0005] In view of the deficiencies in the prior art, the present invention provides a method for managing code resources in a converged communication system to achieve high availability, thereby solving the problems raised in the above-mentioned background technology.

[0006] To achieve the above objectives, the present invention is implemented through the following technical solutions: a method for managing code resources of a fusion communication system to achieve high availability, the method comprising the following steps:

[0007] S1. Distributed storage:

[0008] Design a distributed storage architecture, then select a storage engine to implement data replication;

[0009] S2, Volume Lock:

[0010] Design volume locking mechanism, select locking algorithm, monitor and release volume lock;

[0011] S3, Failover:

[0012] Select the replication mode, monitor the replication status, and automatically switch to the backup node when a failure occurs to ensure continuous business operation;

[0013] S4, routing example diagram:

[0014] Distribute the representation instance graph to each representative instance to ensure the consistency of the stored data copies, implement view generation between these representations to ensure the instance graph remains consistent, and then monitor the routing instance view to ensure the consistency and reliability of the instance view;

[0015] S5. Block-level fault diagnosis and recovery:

[0016] Monitor each block-level fault to detect the fault early, perform fault diagnosis after the block-level fault is discovered to determine the cause of the fault, and perform fault recovery after fault diagnosis to restore block-level functions;

[0017] S6. Hardware or software consumable parts:

[0018] Monitor equipment status to detect whether the equipment has any faults, implement equipment monitoring when the equipment status changes to detect faults early, and implement fault management to solve fault problems when they occur;

[0019] S7, reconfiguration:

[0020] Allocate blocks to volumes by designing reconfiguration mechanisms, use reconfiguration algorithms to implement configuration and release, monitor and release reconfiguration when events occur to prevent excessive resource usage or difficult matching of resource Rama on both sides, configure database parameters, optimize database performance, and ensure data reliability and consistency, which includes configuration of database backup, recovery and monitoring mechanisms, configuration of interfaces with other systems, and ensuring data interoperability and consistency;

[0021] S8. Global device configuration:

[0022] Device configuration information is stored in a central location, device configuration management is implemented when the device configuration information is stored in the central location to ensure consistency of device configuration, and device configuration is monitored to ensure consistency and reliability of device configuration.

[0023] Furthermore, in step S1, the distributed storage architecture refers to dividing the data into small blocks, and storing each block on a different physical machine.

[0024] Furthermore, in step S1, the storage engine refers to using a valid storage engine, and the storage engine is HDFS (Hadoop Distributed File System) or Ceph.

[0025] Furthermore, in step S1, data replication refers to implementing data replication in distributed storage.

[0026] Furthermore, in step S2, the volume locking mechanism refers to introducing a hook (or binding mark) in the code resource to mark the blocks used or allocated to the volume.

[0027] Furthermore, in step S2, the locking algorithm refers to an API leading the magnetic barrier to achieve locking and releasing.

[0028] Furthermore, in step S2, monitoring and releasing volume locks refers to monitoring and releasing volume locks when an event occurs to prevent excessive resource usage or resource overflows, which would make both sides of the RAM difficult to match.

[0029] Furthermore, in step S3, the replication mode refers to using a master-slave replication (Master-Slave Replication) or a peer-to-peer replication (Peer-to-Peer Replication) mode to achieve failover.

[0030] Furthermore, in step S7, the reconfiguration mechanism refers to introducing a hook (or binding mark) in the code resource to mark the blocks used or allocated to the volume.

[0031] Furthermore, in step S7, the reconfiguration algorithm is the Leader Ghost Fault old API to achieve reconfiguration and release.

[0032] The present invention provides a method for managing code number resources of a fusion communication system to achieve high availability, which has the following beneficial effects:

[0033] 1. The method for managing number resources of a high-availability converged communication system can maximize the use of limited number resources through unified management and dynamic allocation to meet the needs of different communication technologies and services. Unified number resource management is conducive to the interconnection between different communication systems and networks and improves the overall coordination capability. Users can use unified numbers to communicate on different networks and terminals to improve user experience. Through continuous data fault recovery, the management of number resources can be kept stable while reducing security risks. Centralized management is conducive to the effective supervision and scheduling of number resources by regulatory authorities, and information management can greatly improve the efficiency and accuracy of number resource management. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 A schematic diagram of the overall steps of a method for managing code resources in a converged communication system to achieve high availability according to the present invention;

[0035] Figure 2 The present invention is a schematic diagram of a specific operation flow of a method for managing code number resources in a converged communication system to achieve high availability. DETAILED DESCRIPTION

[0036] The following embodiments of the present invention are described in further detail in conjunction with the accompanying drawings and examples. The following examples are used to illustrate the present invention, but are not intended to limit the scope of the present invention.

[0037] like Figure 1-Figure 2As shown, the present invention provides a technical solution: a method for managing code number resources of a high-availability converged communication system, which specifically includes the following steps:

[0038] S1. Distributed storage:

[0039] Design a distributed storage architecture, then select a storage engine to implement data replication. In step S1, the distributed storage architecture refers to dividing the data into small blocks and storing each block on a different physical machine. In step S1, the storage engine refers to using an effective storage engine, and the storage engine is HDFS (Hadoop Distributed File System) or Ceph. In step S1, data replication refers to implementing data replication in distributed storage, which can improve data redundancy and availability.

[0040] S2, Volume Lock:

[0041] Design a volume locking mechanism, select a locking algorithm, monitor and release volume locking, in step S2, the volume locking mechanism refers to introducing a hook (or binding mark) in the code resource to mark the block used or allocated to the volume, in step S2, the locking algorithm refers to the leading magnetic barrier API to achieve locking and releasing, in step S2, monitoring and releasing volume locking refers to monitoring and releasing volume locking when an event occurs to prevent excessive resource occupation or resource failure, which will cause both sides of the rama to match the boundary;

[0042] S3, Failover:

[0043] Select a replication mode, then monitor the replication status, and automatically switch to a standby node when a failure occurs to ensure continuous business operation. In step S3, the replication mode refers to using a master-slave replication (Master-Slave Replication) or peer-to-peer replication (Peer-to-Peer Replication) mode to achieve failover;

[0044] S4, routing example diagram:

[0045] Distribute the representation instance graph to each representative instance to ensure the consistency of the stored data copies, implement view generation between these representations to ensure the instance graph remains consistent, and then monitor the routing instance view to ensure the consistency and reliability of the instance view;

[0046] S5. Block-level fault diagnosis and recovery:

[0047] Monitor each block-level fault to detect the fault early, perform fault diagnosis after the block-level fault is discovered to determine the cause of the fault, and perform fault recovery after fault diagnosis to restore block-level functions;

[0048] S6. Hardware or software consumable parts:

[0049] Monitor equipment status to detect whether the equipment has any faults, implement equipment monitoring when the equipment status changes to detect faults early, and implement fault management to solve fault problems when they occur;

[0050] S7, reconfiguration:

[0051] By designing a reconfiguration mechanism to allocate blocks to the volume, using a reconfiguration algorithm to implement configuration and release, monitoring and releasing reconfiguration when an event occurs to prevent excessive resource usage or difficult matching boundaries on both sides of the resource Rama, configuring database parameters, optimizing database performance, and ensuring data reliability and consistency, this includes configuration of database backup, recovery and monitoring mechanisms, configuring interfaces with other systems, and ensuring data interoperability and consistency. In step S7, the reconfiguration mechanism refers to introducing a hook (or binding tag) in the code number resource to mark the blocks used or allocated to the volume. In step S7, the reconfiguration algorithm is the Leader Ghost Fault old API to implement reconfiguration and release;

[0052] S8. Global device configuration:

[0053] Device configuration information is stored in a central location, device configuration management is implemented when the device configuration information is stored in the central location to ensure consistency of device configuration, and device configuration is monitored to ensure consistency and reliability of device configuration.

[0054] In summary, the method for managing code number resources of a high-availability converged communication system is used to design a distributed storage architecture, which means dividing data into small blocks and storing each block on a different physical machine. Then, a storage engine is selected, which means using an effective storage engine, such as HDFS (Hadoop Distributed FileSystem) or Ceph, to achieve data replication, which means implementing data replication in distributed storage, and can improve data redundancy and availability.

[0055] Design volume locking mechanism, which refers to introducing a hook (or binding mark) in the code resource to mark the blocks used or allocated to the volume, select locking algorithm, which refers to the API leading the magnetic barrier to implement locking and releasing, apply locking strategy in task management through API interface and task management (TMM), monitor and release volume locks when events occur to prevent excessive resource occupation or resource failure, and both sides of the rama will match difficult boundaries;

[0056] Select the replication mode, monitor the replication status, and automatically switch to the backup node when a failure occurs to ensure business continuity. The replication mode refers to the use of Master-Slave Replication or Peer-to-Peer Replication mode to achieve failover;

[0057] Distribute the representation instance graph to each representative instance to ensure the consistency of the stored data copies, realize view generation between these representations to ensure the consistency of the instance graph, and then monitor the routing instance view to ensure the consistency and reliability of the instance view; monitor each block-level fault to detect the fault early, implement fault diagnosis after the block-level fault is discovered to determine the cause of the fault, and implement fault recovery after fault diagnosis to restore the block-level function; monitor the device status to detect whether the device fails, implement device monitoring when the device status changes, detect the fault early, and implement fault management when the fault occurs to solve the fault problem; design a reconfiguration mechanism to allocate blocks to the volume. The reconfiguration mechanism refers to introducing a hook (or binding mark) in the code number resource to mark the blocks used or allocated to the volume, using the reconfiguration algorithm to implement configuration and release, monitoring and releasing reconfiguration when an event occurs to prevent excessive resource occupation or difficult matching boundaries on both sides of the resource Rama, where the reconfiguration algorithm is the Leader Ghost Fault old API to implement reconfiguration and release;

[0058] Finally, the device configuration information is stored in a central location, and device configuration management is implemented when the device configuration information is stored in the central location to ensure the consistency of the device configuration, and the device configuration is monitored to ensure the consistency and reliability of the device configuration.

[0059] The embodiments of the present invention are given for the purpose of illustration and description, and are not intended to be exhaustive or to limit the invention to the disclosed forms. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiments are selected and described in order to better illustrate the principles and practical applications of the present invention and to enable those of ordinary skill in the art to understand the present invention and thereby design various embodiments with various modifications suitable for specific uses.

Claims

1. A method for managing code resources of a high-availability converged communication system, characterized in that: The specific steps include the following: S1. Distributed storage: Design a distributed storage architecture, then select a storage engine to implement data replication; S2, Volume Lock: Design volume locking mechanism, select locking algorithm, monitor and release volume lock; S3, Failover: Select the replication mode, monitor the replication status, and automatically switch to the backup node when a failure occurs to ensure continuous business operation; S4, routing example diagram: Distribute the representation instance graph to each representative instance to ensure the consistency of the stored data copies, implement view generation between these representations to ensure the instance graph remains consistent, and then monitor the routing instance view to ensure the consistency and reliability of the instance view; S5. Block-level fault diagnosis and recovery: Monitor each block-level fault to detect the fault early, perform fault diagnosis after the block-level fault is discovered to determine the cause of the fault, and perform fault recovery after fault diagnosis to restore block-level functions; S6. Hardware or software consumable parts: Monitor equipment status to detect whether the equipment has any faults, implement equipment monitoring when the equipment status changes to detect faults early, and implement fault management to solve fault problems when they occur; S7, reconfiguration: Allocate blocks to volumes by designing reconfiguration mechanisms, use reconfiguration algorithms to implement configuration and release, monitor and release reconfiguration when events occur to prevent excessive resource usage or difficult matching of resource Rama on both sides, configure database parameters, optimize database performance, and ensure data reliability and consistency, which includes configuration of database backup, recovery and monitoring mechanisms, configuration of interfaces with other systems, and ensuring data interoperability and consistency; S8. Global device configuration: Device configuration information is stored in a central location, device configuration management is implemented when the device configuration information is stored in the central location to ensure consistency of device configuration, and device configuration is monitored to ensure consistency and reliability of device configuration.

2. A method for managing code resources of a converged communication system to achieve high availability according to claim 1, characterized in that: In step S1, the distributed storage architecture refers to dividing the data into small blocks, and storing each block on a different physical machine.

3. A method for managing code resources of a high-availability converged communication system according to claim 1, characterized in that: In the step S1, the storage engine refers to using a valid storage engine, and the storage engine is HDFS (Hadoop Distributed File System) or Ceph.

4. A method for managing code resources of a converged communication system to achieve high availability according to claim 1, characterized in that: In the step S1, data replication refers to implementing data replication in distributed storage.

5. A method for managing code resources of a converged communication system to achieve high availability according to claim 1, characterized in that: In step S2, the volume locking mechanism refers to introducing a hook in the code resource to mark the blocks used or allocated to the volume.

6. A method for managing code resources of a converged communication system to achieve high availability according to claim 1, characterized in that: In step S2, the locking algorithm refers to an API leading the magnetic barrier to achieve locking and releasing.

7. A method for managing code resources of a converged communication system to achieve high availability according to claim 1, characterized in that: In step S2, monitoring and releasing volume locks refers to monitoring and releasing volume locks when an event occurs to prevent excessive resource usage or resource overflows, which would make both sides of the RAM difficult to match.

8. A method for managing code resources of a converged communication system to achieve high availability according to claim 1, characterized in that: In step S3, the replication mode refers to using a master-slave replication or a peer-to-peer replication mode to implement failover.

9. A method for managing code resources of a converged communication system to achieve high availability according to claim 1, characterized in that: In step S7, the reconfiguration mechanism refers to introducing a hook in the code resource to mark the blocks used or allocated to the volume.

10. The method for managing code resources of a converged communication system to achieve high availability according to claim 1, characterized in that: In step S7, the reconfiguration algorithm is the Leader Ghost Fault old API to achieve reconfiguration and release.

Images