A method for managing channel resource virtualization of a multi-beam satellite communication system

Abstract

The application discloses a kind of multi-beam satellite communication system channel resource virtualization management methods, belong to satellite communication resource management technical field.The application is by deploying system-level channel management server, real-time acquisition each chassis baseband board card state, constructs and maintains the channel resource linked list including equipment health state, baseband board card quantity and detailed parameter.This method supports centralized exchange of service data, and data intercommunication across equipment and across board card can be realized by service exchange server;Network control center applies control or service channel as needed, server dynamically looks up table matching resource, completes configuration and synchronously updates resource linked list;Service channel needs to be bound with service exchange server IP and port to realize data interaction;When resource is released, it is accurately positioned to specified channel, and resource linked list is modified.This method can improve resource management efficiency and flexibility, and is suitable for complex satellite communication scenarios.

Description

Technical Field

[0001] This invention belongs to the field of satellite communication technology, specifically relating to the virtualization management and dynamic allocation technology of ground station channel resources in multi-beam satellite communication systems, and in particular to a method for virtualization management of channel resources in multi-beam satellite communication systems, which can be used for efficient scheduling and optimized configuration of channel resources in scenarios with high complexity and multiple user requirements. Background Technology

[0002] With the development of satellite communications towards high spectrum reuse and wide-area coverage, multi-beam satellites have become a core infrastructure of modern communication networks. However, traditional multi-beam satellite communication systems have the following significant drawbacks:

[0003] (1) The ground station channel equipment adopts a physically isolated hardware architecture, and each chassis operates independently, resulting in dispersed resources and difficulty in overall coordination;

[0004] (2) Existing management relies on manual intervention or static pre-allocation strategies, which cannot dynamically respond to real-time changes in user demand, resulting in waste of spectrum resources and a decline in service quality;

[0005] (3) Lack of unified resource management capabilities makes it difficult to achieve cross-chassis and cross-board resource collaborative scheduling;

[0006] (4) The granularity of underlying resource monitoring is coarse, making it impossible to accurately grasp the health status and load capacity of equipment. These problems seriously restrict the system's resource utilization and operation and maintenance efficiency. Summary of the Invention

[0007] To address the aforementioned problems, this invention proposes a method for virtualizing channel resources management in multi-beam satellite communication systems. This method achieves efficient resource management and control for multi-beam satellite communication systems by constructing a system-level resource management platform and a dynamic scheduling mechanism.

[0008] To achieve the above objectives, the technical solution adopted by the present invention is as follows:

[0009] A method for virtualizing channel resources in a multi-beam satellite communication system includes the following steps:

[0010] Step 1: After the channel device starts up, it reports its own information to the channel management server, and the channel management server constructs a channel resource linked list based on this information.

[0011] Step 2: The network control center monitors user needs and analyzes the required channel types and quantities when initial network construction or service requirements arise.

[0012] Step 3: The network control center sends a resource request message to the channel management server;

[0013] Step 4: After receiving the resource request message, the channel management server searches the channel resource list, selects the suitable resource, and sends a resource usage confirmation message to the channel equipment chassis where the resource is located.

[0014] Step 5: After receiving the resource usage confirmation message, the channel equipment chassis returns the corresponding response;

[0015] Step 6: After receiving the response, the channel management server reports to the network control center as needed and updates the channel resource list.

[0016] Step 7: After receiving the response, the network control center configures the channel resources and sends a resource configuration message to the channel management server.

[0017] Step 8: After receiving the resource configuration message, the channel management server forwards it to the channel device. The channel device completes the configuration of the corresponding channel of the baseband board according to the instructions and returns a configuration success message.

[0018] Step 9: The channel management server forwards the configuration success message to the network control center;

[0019] Step 10: After the network control center confirms that the channel configuration is complete, data transmission will proceed.

[0020] Step 11: When the network control center releases channel resources, it specifies the channel device chassis, board, and channel in the release message it sends. The channel management server forwards the release message to the channel device and modifies the channel resource linked list after receiving the release response from the channel device.

[0021] Furthermore, the channel resource linked list includes:

[0022] Status information of the main control board, switching board, and intermediate frequency board in each channel equipment chassis.

[0023] The number of baseband cards equipped in the chassis of each channel device;

[0024] The slot number, number of carriers, carrier capability, health status, and usage status of each baseband board in each channel equipment chassis.

[0025] Furthermore, in step 5, it is determined whether the resource is available. If it is available, an availability response is returned; if it is not available, a channel resource that meets the requirements is selected again within the local chassis, and a resource update response is returned to the channel management server; if there is no suitable resource in the local chassis, an unavailable resource response is returned to the channel management server.

[0026] In step 6, if the channel management server receives a resource update response, it updates the channel resource list and forwards the resource update response to the network control center; if the channel management server receives a response that no resources are available, it replies to the network control center with a resource application failure message and ends the resource allocation; if the channel management server receives a response that resources are available, it modifies the channel resource list and reports the available response to the network control center.

[0027] Furthermore, the resource request message is marked with a channel resource type, which is either a control channel type or a service channel type;

[0028] In step 7, if the resource is a control channel type, the resource configuration message includes the frequency point number and information rate; if the resource is a service channel type, the resource configuration message includes the frequency point number, information rate, IP address of the service switching device, and the receiving service data port number.

[0029] In step 8, for control channel type, only a configuration success message is returned; for service channel type, a configuration success message, the local IP address of the channel device, and the port number for receiving service data are returned.

[0030] In step 10, for control channel type data, the network control center sends forward data to the baseband board channel corresponding to the channel device and receives reverse data; for service channel type data, the channel device sends and receives service data to and from the service switching device IP address and service data receiving port by binding the local IP address and local service data receiving port.

[0031] Furthermore, the channel equipment, channel management server, and network control center communicate using the TCP protocol.

[0032] The beneficial effects of this invention are as follows:

[0033] 1. Improved resource utilization: By using virtual resource aggregation and dynamic scheduling, the traditional physical isolation limitations are broken, enabling cross-chassis and cross-board resource collaboration, significantly improving spectrum and hardware resource utilization.

[0034] 2. Intelligent Management: The global resource view built by the channel management server supports automated decision-making, replacing manual intervention and static allocation, and quickly responding to changes in business needs.

[0035] 3. Enhanced ease of operation and maintenance: The centralized management platform provides fine-grained monitoring capabilities, reducing the complexity of equipment maintenance; the business exchange server simplifies data routing configuration.

[0036] 4. System stability optimization: The reliability of resource allocation is ensured through a three-party collaboration mechanism to avoid global paralysis caused by a single point of failure.

[0037] 5. Flexible expansion capability: Modular design and open protocol support seamless integration when adding beams or upgrading boards in the future. Attached Figure Description

[0038] Figure 1 This is a schematic diagram of the topological relationship of the devices in an embodiment of the present invention. Detailed Implementation

[0039] The technical solution of the present invention will be further described in detail below with reference to the accompanying drawings.

[0040] A method for virtualized management of channel resources in a multi-beam satellite communication system is disclosed. The channel equipment of the ground station of the multi-beam satellite communication system consists of multiple channel equipment chassis, each serving a specific beam. Each channel equipment chassis integrates a main control board, baseband board, intermediate frequency board, and switching board. This method sets up a system-level channel management server above all the channel equipment chassis. The channel management server is responsible for managing all the channel equipment chassis and their internal baseband boards. Based on the status information of the baseband boards reported by each channel equipment chassis, it locally constructs and continuously maintains a channel resource linked list. Communication between the channel equipment, the channel management server, and the network control center is achieved using the TCP protocol. The method includes the following steps:

[0041] Step 1: After the channel device starts up, it reports its own information to the channel management server. The channel management server then constructs a channel resource linked list based on this information. The channel resource linked list contains:

[0042] Status information of the main control board, switching board, and intermediate frequency board in each channel equipment chassis.

[0043] The number of baseband cards equipped in the chassis of each channel device;

[0044] The slot number, number of carriers, carrier capability, health status, and usage status of each baseband board in each channel equipment chassis;

[0045] Step 2: The network control center monitors user needs and analyzes the required channel types and quantities when initial network construction or service requirements arise.

[0046] Step 3: The network control center sends a resource request message to the channel management server. The resource request message indicates the channel resource type, which can be either a control channel or a service channel.

[0047] Step 4: After receiving the resource request message, the channel management server searches the channel resource list, selects the suitable resource, and sends a resource usage confirmation message to the channel equipment chassis where the resource is located.

[0048] Step 5: After receiving the resource usage confirmation message, the channel equipment chassis determines whether the resource is available. If it is available, it returns an availability response; if it is not available, it selects a suitable channel resource within the chassis and returns a resource update response to the channel management server; if there is no suitable resource in the chassis, it returns a no-available-resource response to the channel management server.

[0049] Step 6: The channel management server receives a response. If it receives a resource update response, it updates the channel resource list and forwards the resource update response to the network control center. If it receives a response that no resources are available, it replies to the network control center with a resource application failure message and ends the resource allocation. If it receives a response that resources are available, it modifies the channel resource list and reports the available response to the network control center.

[0050] Step 7: After receiving the response, the network control center configures the channel resources and sends a resource configuration message to the channel management server. If the resource is a control channel type, the resource configuration message includes the frequency point number and information rate. If the resource is a service channel type, the resource configuration message includes the frequency point number, information rate, IP address of the service switching equipment, and the receiving service data port number.

[0051] Step 8: After receiving the resource configuration message, the channel management server forwards it to the channel device. The channel device completes the configuration of the corresponding channel on the baseband board according to the instructions and returns a configuration success message. For control channel types, only a configuration success message is returned. For service channel types, a configuration success message, the local IP address of the channel device, and the port number for receiving service data are returned.

[0052] Step 9: The channel management server forwards the configuration success message to the network control center;

[0053] Step 10: After the network control center confirms that the channel configuration is complete, data transmission is performed. For control channel type data, the network control center sends forward data to the baseband board channel corresponding to the channel device and receives reverse data. For service channel type data, the channel device sends and receives service data to and from the service switching device IP address and service data receiving port by binding the local IP address and local service data receiving port.

[0054] Step 11: When the network control center releases channel resources, it specifies the channel device chassis, board, and channel in the release message it sends. The channel management server forwards the release message to the channel device and modifies the channel resource linked list after receiving the release response from the channel device.

[0055] This method has the function of centralized exchange of service data, and achieves service data exchange between different channel devices, between different baseband boards within the same channel device, and between different channels within the same baseband board by means of a service exchange server.

[0056] The core of this method lies in constructing a system-level channel resource virtualization management architecture. Specifically, the ground station consists of several channel equipment chassis, each corresponding to one beam. The chassis integrates main control boards, baseband boards, intermediate frequency boards, and switching boards. A channel management server is set up on top of all the chassis to assume global resource management responsibilities. This method overcomes the management bottlenecks of traditional systems through three major technological innovations: logical resource aggregation, dynamic scheduling, and centralized switching. Its principle is as follows:

[0057] I. System Architecture Design

[0058] 1. Physical layer structure

[0059] The ground station contains multiple channel equipment chassis, each dedicated to signal processing for a single beam;

[0060] The single chassis integrates four types of core boards: main control board (responsible for local control), baseband board (supports multi-waveform signal modulation and demodulation), intermediate frequency board (completes radio frequency conversion), and switching board (realizes internal data exchange).

[0061] 2. Management Structure

[0062] Add a channel management server as a system-level management center to uniformly manage all chassis and internal resources;

[0063] Establish a channel resource linked list to reflect the resource status of the entire system in real time, including key parameters such as chassis health status, number of baseband boards and slot number of each board, carrier capability, and usage status.

[0064] II. Resource Virtualization Management Mechanism

[0065] 1. Construction of virtual resource collection

[0066] The channel management server constructs a globally unified channel resource linked list by listening to the initialization information (such as board status and carrier capability) reported by each chassis.

[0067] The channel resource linked list is dynamically maintained, supporting the addition / deletion of resource nodes to ensure synchronization with actual physical resources.

[0068] 2. Fine-grained resource monitoring

[0069] Monitoring dimensions cover: chassis level (main control / switching / intermediate frequency board status), board level (slot number, number of carriers, health status), and channel level (usage status);

[0070] An active reporting mechanism is adopted, and each chassis automatically reports complete resource information to the channel management server after startup.

[0071] III. Centralized Data Exchange Function

[0072] By introducing a business exchange server as the business data exchange hub, three types of data exchange scenarios can be realized:

[0073] Cross-chassis data exchange: Service interoperability between chassis of equipment with different channels;

[0074] Intra-chassis cross-board switching: Data transfer between different baseband boards within the same chassis;

[0075] Multi-channel switching within a single baseband board: data routing for different channels on a single baseband board.

[0076] This feature significantly reduces the complexity of data exchange and increases system throughput.

[0077] IV. Dynamic Resource Allocation Process

[0078] This invention designs a three-party collaborative resource allocation mechanism, the specific steps of which are as follows:

[0079] 1. Demand perception and initiation

[0080] The network control center monitors user needs in real time. When it detects initial network construction needs or new service needs, it analyzes the type (control channel / service channel) and quantity of the required channels to clarify the specific parameters of this application.

[0081] 2. Resource Request Submission

[0082] The network control center sends a resource request message to the channel management server. The message must clearly indicate the type of channel resource requested (such as control channel or service channel).

[0083] 3. Resource matching and pre-allocation

[0084] After receiving a request, the channel management server performs a quick search based on its locally maintained channel resource list to select available resources that meet the requirements. It then sends a resource usage confirmation message to the channel equipment chassis containing the resource, requesting verification of the resource's actual availability.

[0085] 4. Chassis-side resource verification

[0086] Upon receiving the confirmation message, the target channel equipment chassis immediately determines whether the specified resource is available. If available, it directly returns a response and proceeds to the subsequent configuration steps; if unavailable, it searches for a suitable alternative resource within its own chassis. If a new resource is found, it sends detailed information about the new resource to the channel management server and proceeds to the next step; if no suitable resource is available in the chassis, it returns a "no available resource" response to the channel management server.

[0087] 5. Resource Updates and Feedback

[0088] If the chassis provides new available resources, the channel management server will update the relevant records in the local resource list and forward this updated resource configuration information to the network control center, indicating that a resource that meets the conditions has been found.

[0089] 6. Handling Application Failures

[0090] If the channel management server confirms that there are no available resources in the entire system, it will return a "resource application failed" message to the network control center and terminate the current allocation process.

[0091] 7. Resource locking and logging

[0092] Once the channel management server receives the chassis's confirmation response for the resource, it modifies the status flag of the resource in the local resource list (marking it as occupied) and reports this change to the network control center, thus completing the temporary locking of the resource.

[0093] 8. Differentiated configuration distribution

[0094] The network control center issues specific configuration instructions based on the channel type:

[0095] Control channel: Only transmits basic parameters such as frequency point number and information rate;

[0096] Service Channel: In addition to the basic parameters, the IP address of the service exchange server and the port number for receiving service data are also required to establish a data interaction channel.

[0097] 9. Device-side configuration execution

[0098] The channel management server forwards the configuration commands from the network control center to the target channel devices. The devices then complete the configuration of the corresponding channels on the baseband boards according to the commands.

[0099] Once the control channel configuration is complete, a simple configuration success message is returned.

[0100] In addition to returning a success message, the service channel also needs to transmit the device's local IP address and the port number for receiving service data, for subsequent data interaction.

[0101] 10. Configuration result confirmation

[0102] The channel management server forwards the configuration success message returned by the device to the network control center, which then confirms that the channel configuration has been completed.

[0103] 11. Data Transmission Stage

[0104] Control Channel: The network control center can directly send forward data to the baseband board channel corresponding to the channel equipment and receive reverse data;

[0105] Service Channel: The channel device interacts with the service switching server through the service switching server IP address and the service data receiving port number issued by the network control center.

[0106] 12. Resource Release

[0107] When the network control center needs to release channel resources, it issues a release message and explicitly specifies the channel equipment chassis, boards, and channels to be released. The channel management server forwards this message to the target device. After receiving the release response from the device, it modifies the status of the resource in the local resource list to "idle," completing the resource reclamation.

[0108] V. Differentiated Channel Configuration Strategy

[0109] 1. Control Channel

[0110] Only the frequency number and information rate need to be configured;

[0111] A configuration success message will be returned after configuration is complete.

[0112] 2. Service Channel

[0113] The IP address of the business exchange server and the port number for receiving business data must be provided separately.

[0114] The channel device needs to return its local IP address and the port number for receiving service data to form a two-way data path.

[0115] VI. Communication Protocols and Extensibility

[0116] The devices within the system communicate using the TCP protocol to ensure reliable data transmission.

[0117] Although this method is illustrated using a standard business process as an example, it has good scalability and can be adapted to the needs of other business scenarios.

[0118] Here is a specific example:

[0119] I. System Hardware Deployment

[0120] Taking a multi-beam satellite ground station as an example, three channel equipment chassis (corresponding to three independent beams) are deployed. Each chassis adopts a standardized 4U rack-mount design, with internal integration of:

[0121] Main control board: Equipped with an ARM processor and running an embedded Linux system, it is responsible for the management of the boards in the chassis and the execution of instructions;

[0122] Baseband board: Each chassis is equipped with 4 high-performance FPGA baseband boards, each board supports 8 carrier channels and has QPSK modulation and demodulation capabilities;

[0123] Intermediate frequency board: Enables up and down conversion of 70MHz band signals, equipped with ADDA sampling rate up to 1GHz;

[0124] Switching board: Equipped with Gigabit Ethernet switching chip and CPS1848 serial RapidIO switching chip, providing high-speed data path between boards within the chassis.

[0125] System-level devices include:

[0126] Channel management server: It adopts an x86 architecture server, deploys resource management software, and is equipped with dual redundant power supplies;

[0127] Business exchange server: Dell 730xd model is selected, and business data exchange software is deployed.

[0128] Network control center: Inspur NF5280M6 model was selected to deploy network control software.

[0129] The topology of the network control center, service switching server, channel management server, and channel equipment is as follows: Figure 1 As shown in the diagram. The network control center and the channel management server exchange network control data, the service switching server and the channel management server exchange service data, and the network control center and the service switching server exchange switching configurations. Furthermore, the channel management server stores a channel resource linked list, and the channel management server and its subordinate channel devices together constitute a channel resource virtualization management unit.

[0130] II. Initialization and Resource Table Creation

[0131] 1. Power-on self-test: After each chassis is powered on, the main control board first performs a self-test, then checks the status of the intermediate frequency / switching board, and finally checks the status of the baseband board. After all boards have been tested, a "Chassis Resource Status Form" is generated (including board serial number, slot number, carrier capability of each baseband board, etc.).

[0132] 2. Resource Reporting: Report local chassis resource information to the channel management server via TCP / IP;

[0133] 3. Virtual Resource Set Construction: The channel management server parses the data reported by each chassis and establishes a three-level resource index linked list:

[0134] Primary Index: Chassis ID → Health Status (Main Controller / Switch / Intermediate Frequency Board Status);

[0135] Secondary index: Chassis ID → Baseband board list (slot number + number of carriers + health status);

[0136] Level 3 Index: Baseband board ID → List of available channels (carrier capability + usage status).

[0137] III. Example of Dynamic Resource Allocation

[0138] Scenario: An emergency communication mission requires the addition of 2 control channels (1 forward and 1 reverse) and 4 service channels.

[0139] 1. Requirements Analysis: The network control center analyzes the task requirements and sends a resource request containing the channel type to the channel management server;

[0140] 2. Intelligent matching: The channel management server traverses the virtual resource linked list and filters out baseband board A (3 remaining free channels) and baseband board B (5 remaining free channels) of chassis 1.

[0141] 3. Pre-occupancy verification: Send a pre-occupancy command to the target chassis, and the chassis main control board verifies the physical status of the channel (such as temperature and bit error rate).

[0142] 4. Configuration distribution:

[0143] Control Channel: The channel management server sends the forward frequency point number (1.201GHz), information rate (2Mbps), and reverse frequency point number (1.203GHz), information rate (100kbps) to the baseband board A of chassis 1.

[0144] Service Channel: The channel management server sends the forward and reverse service channel frequency point number and information rate (1.205-1.209 / 1.405-1.409GHz, 500kbps) to the baseband board B of chassis 1. In addition to the basic parameters, it also carries the service switching server IP (192.168.1.10) and the receiving service data port number (5000-5003).

[0145] 5. Execution feedback: After the baseband board completes the channel configuration, it returns the local IP (e.g., 192.168.1.20) and the port number for receiving service data (4000-4003) to the channel management server.

[0146] 6. Data connectivity: Business data is routed and exchanged through the business exchange server, while control commands are transmitted directly through a dedicated channel.

[0147] IV. Monitoring and Maintenance

[0148] Real-time monitoring: The channel management server polls the resource status of each chassis every 5 seconds and updates the resource list accordingly;

[0149] Troubleshooting: If a baseband board malfunctions, the channel management server will automatically mark it as unavailable and trigger an alarm.

[0150] Load balancing: When the load on a baseband board exceeds a threshold (e.g., 80%), the channel management server prioritizes allocating new requests to boards with low load.

[0151] This invention deploys a system-level channel management server to collect the real-time status of baseband cards in each chassis, constructing and maintaining a channel resource linked list containing device health status, baseband card quantity, and detailed parameters. This method supports centralized exchange of service data, enabling data communication across devices and cards via a service switching server. The network control center requests control or service channels as needed, and the server dynamically looks up and matches resources, updating the resource linked list synchronously after configuration. Service channels must be bound to the service switching server's IP address and port for data interaction. When resources are released, the system precisely locates the designated channel and modifies the resource linked list.

[0152] This method achieves efficient resource management of multi-beam satellite communication systems through hardware standardization, centralized management, and dynamic scheduling. It can improve resource management efficiency and flexibility and can be widely applied to complex satellite communication scenarios such as emergency communication and aviation broadband.

Claims

1. A method for managing channel resource virtualization in a multi-beam satellite communication system, characterized in that, The method comprises the following steps: Step 1, after the channel device is started, the channel device reports its own information to the channel management server, and the channel management server constructs a channel resource chain table according to the information; Step 2, the network control center monitors user demand, and analyzes the required channel type and quantity when initial network building demand or service demand occurs; Step 3, the network control center sends a resource application message to the channel management server; Step 4, after receiving the resource application message, the channel management server searches the channel resource chain table, selects adaptive resources, and sends a resource use confirmation message to the channel device cabinet where the resources are located; Step 5, after receiving the resource use confirmation message, the channel device cabinet returns a corresponding response; Step 6, after receiving the response, the channel management server reports to the network control center as required, and updates the channel resource chain table; Step 7, after receiving the response, the network control center configures resources for the channel, and sends a resource configuration message to the channel management server; Step 8, after receiving the resource configuration message, the channel management server forwards the message to the channel device, and the channel device completes the configuration of the corresponding channel of the baseband board according to the instruction, and returns a configuration success message; Step 9, the channel management server forwards the configuration success message to the network control center; Step 10, after confirming that the channel configuration is completed, the network control center performs data transmission; Step 11, when the network control center releases the channel resources, the channel device cabinet, the board and the channel are specified in the released message; the channel management server forwards the released message to the channel device, and after receiving the release response of the channel device, modifies the channel resource chain table.

2. The method of claim 1, wherein, The channel resource chain table comprises: State information of the main control board, the switching board and the intermediate frequency board in each channel device cabinet, The number of baseband boards equipped in each channel device cabinet; Slot number, carrier number, carrier capacity, health status and use status of each baseband board in each channel device cabinet.

3. The method of claim 1, wherein, In step 5, it is determined whether the resources are available, if available, a usable response is returned; If not available, the channel resources that meet the demand are reselected in the cabinet range, and a resource update response is returned to the channel management server; If there is no suitable resource in the cabinet, a no available resource response is returned to the channel management server; In step 6, if the channel management server receives the resource update response, the channel resource chain table is updated, and the resource update response is forwarded to the network control center; if the channel management server receives the no available resource response, a resource application failure message is returned to the network control center, and the resource allocation is ended; if the channel management server receives the usable response, the channel resource chain table is modified, and the usable response is reported to the network control center.

4. The method of claim 1, wherein, The resource application message is marked with a channel resource type, and the channel resource type is a control channel type or a service channel type; In step 7, if the resource is a control channel type, the resource configuration message comprises a frequency point number and an information rate; if the resource is a service channel type, the resource configuration message comprises a frequency point number, an information rate, an IP address of a service switching device and a service data port number; In step 8, only a configuration success message is returned for the control channel type, and a configuration success message and a channel device local IP address and a service data receiving port number are returned for the service channel type; In step 10, the network control center sends forward data to the channel device corresponding baseband board card channel and receives reverse data for the control channel type data, and the channel device transmits service data to the service exchange device IP address and service data receiving port through binding the local IP address and the local service data receiving port for the service channel type data.

5. The method of claim 1, wherein, The channel device, the channel management server and the network control center communicate by using the TCP protocol.

Images