Service flow transmission method, satellite management and control system, and storage medium and electronic apparatus

Abstract

Provided in the embodiments of the present application are a service flow transmission method, a satellite management and control system, and a storage medium and an electronic apparatus. The method comprises: a first TSN switch in a platform side receiving a plurality of service flows from a plurality of components in the platform side, wherein each component in the platform side is connected to the first TSN switch; on the basis of a destination address of a target service flow, the first TSN switch determining a transmission type of the target service flow, wherein the plurality of service flows comprise the target service flow; and the first TSN switch sending the target service flow to a destination component on the basis of the transmission type, wherein the first TSN switch and a central controller maintain clock synchronization, a satellite management system comprises the platform side and a load side, and the platform side and the load side are connected by means of the central controller. The present application solves the technical problem in the related art of the efficiency of intra-satellite service data transmission in a space-borne switching architecture being low, thereby achieving the effect of improving the intra-satellite service data transmission efficiency.

Description

Methods for transmitting service flows, satellite control systems, storage media and electronic devices

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411595833.7, filed on November 8, 2024, entitled “Method for transmitting service flow, satellite control system, storage medium and electronic device”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communications, and more specifically, to a method for transmitting service flows, a satellite control system, a storage medium, and an electronic device. Background Technology

[0004] Satellite hardware can be divided into two parts: the platform side and the payload side. The platform side includes components that provide support services for the payload (the components within the satellite that perform tasks), such as power supplies, orbit control systems, payload detection and control systems, and propulsion systems. The payload side includes components used by the satellite to perform its tasks, such as antenna baseband, onboard laser terminals, and onboard routers. Data exchange within the satellite mainly includes two types: platform data exchange and payload data exchange. Platform-side data exchange generally has low bandwidth requirements but high QoS control requirements regarding data transmission latency, jitter, and packet loss rate. Conversely, the payload side typically has low QoS requirements for data exchange but high bandwidth requirements.

[0005] As the number of onboard payloads continues to increase, the number of connected devices that traditional onboard switching architectures can support is limited. Furthermore, the significant differences in data exchange requirements between satellite platforms, payloads, and intra-satellite traffic increase the development difficulty of routing and switching components and reduce their efficiency as intra-satellite service data transmission devices.

[0006] There is currently no effective solution to the above problems. Summary of the Invention

[0007] This application provides a method for transmitting service flows, a satellite control system, a storage medium, and an electronic device to at least solve the technical problem of low efficiency in intra-satellite service data transmission in satellite switching architectures in related technologies.

[0008] According to one embodiment of this application, a method for transmitting service flows is provided, applied to a satellite management system. The satellite management system includes a platform side and a payload side. The platform side includes service components for providing services to payload components, and the payload side includes payload components for performing tasks. The platform side and the payload side are connected through a central controller. The method includes: a first TSN switch within the platform side receiving multiple service flows from multiple components within the platform side, wherein each component within the platform side is respectively connected to the first TSN switch; the first TSN switch determining the transmission type of the target service flow based on the destination address of the target service flow, wherein the multiple service flows include the target service flow; and the first TSN switch sending the target service flow to the destination component according to the transmission type.

[0009] In an exemplary embodiment, the first TSN switch determines the transmission type of the target service flow based on the destination address of the target service flow, including: determining that the transmission type of the target service flow is intra-domain transmission when the destination address is a component address within the platform side; or determining that the transmission type of the target service flow is inter-domain transmission when the destination address is a component address within the payload side.

[0010] In an exemplary embodiment, the first TSN switch sends the target service flow to the destination component according to the transmission type, including: when the transmission type is intra-domain transmission, the first TSN switch determines the transmission priority of the target service flow according to the virtual LAN information of the service flow, and adds the target service flow to the target queue corresponding to the transmission priority; the first TSN switch performs shaping and gating scheduling operations on the service flows in the target queue, transmits the service flows in the target queue sequentially, and transmits the target service flow to the destination component when it arrives to transmit the target service flow.

[0011] In an exemplary embodiment, the first TSN switch sends the target service flow to the destination component according to the transmission type, including: when the transmission type is inter-domain transmission, the first TSN switch determines the transmission priority of the target service flow according to the virtual LAN information of the target service flow, and adds the target service flow to the target queue corresponding to the transmission priority; the first TSN switch performs shaping and gating scheduling operations on the service flows in the target queue, transmits the service flows in the target queue sequentially, and when the target service flow is about to be transmitted, sends the target service flow to the second TSN switch in the load side, so as to send the target service flow to the destination component through the second TSN switch, wherein the second TSN switch in the load side is connected to each component in the load side.

[0012] In one exemplary embodiment, the method further includes: when the target service flow is a service flow sent by a first component within the platform side, the first component sends the target service flow to a first TSN switch and a third TSN switch respectively, wherein the third TSN switch within the platform side is connected to each component within the platform side; the load side further includes a fourth TSN switch, and each component within the load side is connected to the fourth TSN switch; the first TSN switch is connected to the second TSN switch and the fourth TSN switch respectively, and the third TSN switch is connected to the second TSN switch and the fourth TSN switch respectively.

[0013] In one exemplary embodiment, the target service flow uses a target message format, which includes: an identifier on the platform side, an identifier of the first component, and a transmission mode of the target service flow.

[0014] In one exemplary embodiment, before the first TSN switch within the platform side receives multiple service flows from multiple components on the platform side, the method further includes: with the central controller, the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch clocked synchronously, the central controller sends data acquisition requests to the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch respectively; the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch respectively send their respective measurement data to the central controller; and the central controller sends TSN flows to the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch respectively to perform TSN configuration on the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch.

[0015] In an exemplary embodiment, before the first TSN switch within the platform side receives multiple service flows from multiple components on the platform side, the method further includes: with the central controller, the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch, as well as the first TSN controller and the second TSN controller clocked synchronized, the central controller sends data acquisition requests to the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch, as well as the first TSN controller and the second TSN controller, respectively; the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch, as well as the first TSN controller and the second TSN controller, respectively send data acquisition requests to the central controller. Each sends its own measurement data; the central controller sends TSN streams to the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch, as well as the first TSN controller and the second TSN controller, to configure the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch, as well as the first TSN controller and the second TSN controller; wherein, the platform side also includes the first TSN controller, and the load side also includes the second TSN controller; the first TSN controller is connected to the central controller, the first TSN switch, and the third TSN switch, and the second TSN controller is connected to the central controller, the second TSN switch, and the fourth TSN switch.

[0016] According to another embodiment of this application, a satellite control system is provided, comprising: a platform side, a payload side, and a central controller, wherein a first TSN controller in the platform side and a second TSN controller in the payload side are respectively connected to the central controller; the first TSN controller in the platform side is connected to a first TSN switch and a third TSN switch, and each component in the platform side is respectively connected to the first TSN switch and the third TSN switch; the second TSN controller in the payload side is connected to a second TSN switch and a fourth TSN switch, and each component in the payload side is respectively connected to the second TSN switch and the fourth TSN switch.

[0017] According to another embodiment of this application, a satellite control system is provided, comprising: a platform side, a payload side, and a central controller, wherein a first TSN switch and a third TSN switch in the platform side, and a second TSN switch and a fourth TSN switch in the payload side are respectively connected to the central controller; each component in the platform side is respectively connected to the first TSN switch and the third TSN switch; and each component in the payload side is respectively connected to the second TSN switch and the fourth TSN switch.

[0018] According to yet another embodiment of this application, a computer-readable storage medium is also provided, wherein a computer program is stored therein, wherein the computer program, when executed by a processor, implements the steps of the method described in any of the preceding claims.

[0019] According to yet another embodiment of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0020] According to yet another embodiment of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps of the method described in any of the preceding claims.

[0021] Through this application, the first TSN switch on the platform side obtains service flows from the connected components, determines the transmission type of the target service flow based on the destination address of the service flow, and can send the target service flow to the corresponding destination component based on the transmission type.

[0022] By leveraging mechanisms such as time synchronization, resource reservation, and stream filtering within the TSN (Transmission Management System), differentiated services for satellite platform control commands and data streams between different onboard payloads can be ensured, effectively improving the transmission efficiency of the onboard switching architecture. Therefore, this addresses the problem of low data transmission efficiency for intra-satellite service data within the onboard switching architecture, achieving the goal of improving the overall efficiency of intra-satellite service data transmission within the onboard switching architecture. Attached Figure Description

[0023] Figure 1 is a schematic diagram of a satellite control system architecture according to an embodiment of this application;

[0024] Figure 2 is a schematic diagram of the satellite control system architecture according to an embodiment of this application;

[0025] Figure 3 is a flowchart of a method for transmitting service flow according to an embodiment of this application;

[0026] Figure 4 is a schematic diagram of a spaceborne switching logic architecture based on TSN technology according to an embodiment of this application;

[0027] Figure 5 is a schematic diagram of the functional architecture of the TSN controller according to an embodiment of this application;

[0028] Figure 6 is a functional architecture diagram of the TSN switch in the spaceborne switching architecture according to an embodiment of this application;

[0029] Figure 7 is a schematic diagram of the platform-side internal traffic TSN exchange process according to an embodiment of this application;

[0030] Figure 8 is a schematic diagram of the load-side internal flow TSN exchange process according to an embodiment of this application;

[0031] Figure 9 is a schematic diagram of the traffic TSN exchange process from the platform side to the load side according to an embodiment of this application;

[0032] Figure 10 is a flowchart of platform-side instruction master / backup transmission according to an embodiment of this application;

[0033] Figure 11 is a schematic diagram of the TSN carrying lightweight message format according to an embodiment of this application;

[0034] Figure 12 is a flowchart of the configuration of a spaceborne switching architecture based on TSN switching technology according to an embodiment of this application.

[0035] Figure 13 is a second flowchart of the configuration of a spaceborne switching architecture based on TSN switching technology according to an embodiment of this application. Detailed Implementation

[0036] The embodiments of this application will be described in detail below with reference to the accompanying drawings and examples.

[0037] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0038] Figure 1 shows a schematic diagram of a satellite control system architecture according to an embodiment of this application, including: a platform side, a payload side, and a central controller. A first TSN controller on the platform side and a second TSN controller on the payload side are respectively connected to the central controller. The first TSN controller on the platform side is connected to a first TSN switch and a third TSN switch, and each component on the platform side is respectively connected to the first TSN switch and the third TSN switch. The second TSN controller on the payload side is connected to a second TSN switch and a fourth TSN switch, and each component on the payload side is respectively connected to the second TSN switch and the fourth TSN switch.

[0039] Figure 2 shows a schematic diagram of another satellite control system architecture according to an embodiment of this application, including: a platform side, a payload side, and a central controller. The first TSN switch and the third TSN switch in the platform side, and the second TSN switch and the fourth TSN switch in the payload side are respectively connected to the central controller to form a switching network. Each component in the platform side is respectively connected to the first TSN switch and the third TSN switch. Each component in the payload side is respectively connected to the second TSN switch and the fourth TSN switch.

[0040] The method embodiments provided in this application can be applied to the satellite control system architecture shown in Figure 1 or Figure 2.

[0041] This embodiment provides a method for transmitting service flows. Figure 3 is a flowchart of the method for transmitting service flows according to an embodiment of this application, which is applied to a satellite control system. The satellite includes a platform side and a payload side. The platform side includes a service component for providing services to the payload component. The payload side includes a payload component, which is a component for performing tasks. The platform side and the payload side are connected through a central controller.

[0042] The platform side includes, but is not limited to, the following service components: power supply, orbit control system, payload detection and control system, propulsion system, etc. The payload side includes, but is not limited to, the following payload components: antenna baseband, onboard laser terminal, and onboard router, etc.

[0043] As shown in Figure 3, the process includes the following steps:

[0044] In step S202, the first TSN switch on the platform side receives multiple service flows from multiple components on the platform side, wherein each component on the platform side is connected to the first TSN switch.

[0045] Step S204: The first TSN switch determines the transmission type of the target service flow based on the destination address of the target service flow, wherein the plurality of service flows include the target service flow;

[0046] Step S206: The first TSN switch sends the target service flow to the destination component according to the transmission type.

[0047] The first TSN switch and the central controller maintain clock synchronization.

[0048] In the above embodiments, the satellite control system can be a communication satellite system. Since current satellite systems can be divided into a satellite platform side and a payload side, the aforementioned platform side and payload side can correspond to the platform side and payload side, respectively. Referring to Figure 1, TSN can be understood as Time-Sensitive Networking technology, mainly composed of three parts: clock synchronization, data flow scheduling strategy, and TSN network and user configuration. A schematic diagram of the onboard switching logic architecture based on TSN technology can be seen in Figure 4. As shown in Figure 4, the TSN controller is used to issue configuration commands to the TSN switch. Time-sensitive traffic between the satellite platform and onboard payloads can be exchanged through the TSN interface to the TSN switch. During the exchange process, the TSN switch performs queue scheduling and traffic filtering to ensure that the latency of time-sensitive traffic is bounded. Other non-time-sensitive traffic can be connected to the TSN switch through non-TSN interfaces. Therefore, the satellite platform onboard can realize highly deterministic control information and large-capacity data exchange between payloads. Among them, time-sensitive traffic can be control signaling, but is not limited to this.

[0049] In the above embodiments, as shown in Figure 1, the component can be an onboard computer, sensor A, or a power management and thermal control system. The central controller can configure cross-domain traffic between different management domains and send configuration commands to the TSN controllers in the source and destination management domains of the cross-domain traffic, ensuring the deterministic latency of cross-domain data transmission. The TSN controller manages the configuration of the TSN switch and can send the configuration commands sent by the central controller to the TSN controller to the TSN switch, realizing the reservation of transmission resources and traffic shaping of data traffic within the domain, ensuring real-time transmission. The TSN switch performs operations such as flow classification, flow scheduling, and flow shaping on the traffic data (i.e., the above-mentioned service flow) received from the component according to the controller's configuration commands. By determining the destination address of the target service flow, the transmission type is determined, and the target service flow is sent to the destination component according to the transmission type, providing deterministic transmission guarantee for latency-sensitive traffic.

[0050] In the above embodiments, in terms of data exchange, the TSN switching network replaces the traditional bus switching architecture. The TSN controller can perform functions such as resource reservation, traffic shaping, and wireless software / firmware updates in the satellite system, calculating and issuing configuration commands. This avoids contention for shared communication resources and improves network scalability. The functional architecture of the TSN controller is shown in Figure 5, which is a schematic diagram of the functional architecture of the TSN controller according to an embodiment of this application. As shown in Figure 5, the TSN controller is internally divided into a control layer and a configuration layer. The control layer is a central processing unit (CPU) pool, with different CPU cores responsible for different data tasks, including clock information database maintenance, synchronization tree updates, resource reservation, and software updates. The configuration layer is used for sending topology-related data and issuing TSN switch configurations.

[0051] In the above embodiments, the functional architecture diagram of the TSN switch in the spaceborne switching architecture can be referred to Figure 6. As shown in Figure 6, the functional architecture of the TSN switch includes a time synchronization module and an output scheduling module. The time synchronization module can use the 802.1As protocol to realize clock synchronization between TSN switches and between TSN switches and domain controllers. The output scheduling module can adjust the flow forwarding time through the 802.1Qbv protocol to ensure that time-sensitive traffic is sent in a timely manner within a certain delay.

[0052] Optionally, the entity performing the above steps can be a platform-side switch or a load-side switch, but is not limited to these.

[0053] Through this application, the first TSN switch within the platform obtains service flows from the connected components, determines the transmission type of the target service flow based on its destination address, and sends the target service flow to the corresponding destination component based on the transmission type. During the transmission of the target service flow, the first TSN switch and the central controller maintain clock synchronization. By utilizing TSN's time synchronization, resource reservation, and flow filtering mechanisms, differentiated services for satellite platform control commands and data flows between different onboard payloads can be guaranteed, effectively improving the transmission efficiency of the onboard switching architecture. Therefore, it can solve the problem of low data transmission efficiency for intra-satellite service data in the onboard switching architecture, achieving the effect of improving the data transmission efficiency of intra-satellite service data in the onboard switching architecture.

[0054] In an exemplary embodiment, the first TSN switch determines the transmission type of the target service flow based on the destination address of the target service flow, including: determining that the transmission type of the target service flow is intra-domain transmission when the destination address is a component address within the platform side; and determining that the transmission type of the target service flow is inter-domain transmission when the destination address is a component address within the payload side.

[0055] In the above embodiments, the destination address of the target service flow can be a component address within the platform or a component address within the payload. When the destination address is a component address within the platform, the transmission type of the target service flow can be determined as intra-domain transmission; when the destination address is a component address within the payload, the transmission type of the target service flow can be determined as inter-domain transmission.

[0056] In an exemplary embodiment, the first TSN switch sends the target service flow to the destination component according to the transmission type, including: when the transmission type is intra-domain transmission, the first TSN switch determines the transmission priority of the target service flow according to the virtual LAN information of the service flow, and adds the target service flow to the target queue corresponding to the transmission priority; the first TSN switch performs shaping and gating scheduling operations on the service flows in the target queue, transmits the service flows in the target queue sequentially, and transmits the target service flow to the destination component when it arrives to transmit the target service flow.

[0057] In the above embodiments, when the transmission type is intra-domain transmission, as shown in Figure 1, it can include intra-domain transmission on the platform side and intra-domain transmission on the payload side. The intra-domain transmission process on the platform side can be referred to Figure 7, which is a schematic diagram of the TSN switching process for internal traffic on the platform side according to an embodiment of this application. As shown in Figure 7, the first management device generates a control command message, obtains the MAC address based on the destination device's encoding, encapsulates the upper-layer data service flow with an Ethernet frame header according to the destination MAC address, and forwards or broadcasts it to the TSN switch on the platform side. The first TSN switch identifies the service flow based on the VLAN ID (i.e., the aforementioned virtual LAN information), determines the transmission priority of the service flow, classifies the flow into different queues, and adds the target service flow to the target queue. The TSN switch can perform shaping operations on the traffic in different queues and ensure traffic latency determinism through gating scheduling, transmitting service flows sequentially. When transmitting target service flow data, the TSN switch performs Layer 2 forwarding of the target service flow to the destination component. The VLAN ID is a number used to identify virtual LANs and distinguish different virtual LANs. In a network, different devices can be assigned to different VLANs and distinguished and managed by VLAN ID.

[0058] In the above embodiments, since the internal traffic on the load side is mainly service traffic between load side communication components, there is essentially no TSN deterministic requirement. A TSN switching bus architecture can be introduced to meet the high-capacity forwarding of internal MAC unicast. The intra-domain transmission process on the load side can be referred to Figure 8, which is a schematic diagram of the TSN switching process for internal traffic on the load side according to an embodiment of this application. As shown in Figure 8, the platform device generates data packets, obtains the MAC address based on the destination device's encoding, encapsulates the upper-layer data service flow with an Ethernet frame header according to the destination MAC address, and forwards it to the TSN switch on the platform side. The TSN switch identifies the service flow based on the VLAN ID, determines the transmission priority of the service flow, classifies the flow into different queues, and adds the target service flow to the target queue. The TSN switch can perform shaping operations on the traffic in different queues and ensure traffic latency determinism through gating scheduling, transmitting service flows sequentially. When transmitting target service flow data, the TSN switch performs Layer 2 forwarding of the target service flow to the destination component.

[0059] In the above embodiments, as shown in Figure 6, the functional architecture of the TSN switch further includes: a priority module, a flow filtering module, and a forwarding control module. The priority module can use the 802.1Q protocol to classify traffic by device VLAN ID and PCP (Priority) and distribute traffic to different queues. The flow filtering module can use the 802.1Qav and 802.1Qcr protocols to perform CBS (Credit-based Shaping) or ATS (Asynchronous Traffic Shaping) traffic scheduling and shaping on the forwarded traffic to eliminate bursts and jitter in the transmission process. The forwarding control module can forward traffic data carrying Layer 3 services.

[0060] In an exemplary embodiment, the first TSN switch sends the target service flow to the destination component according to the transmission type, including: when the transmission type is inter-domain transmission, the first TSN switch determines the transmission priority of the target service flow according to the virtual LAN information of the target service flow, and adds the target service flow to the target queue corresponding to the transmission priority; the first TSN switch performs shaping and gating scheduling operations on the service flows in the target queue, transmits the service flows in the target queue sequentially, and when the target service flow is about to be transmitted, sends the target service flow to the second TSN switch in the load side, so as to send the target service flow to the destination component through the second TSN switch, wherein the second TSN switch in the load side is connected to each component in the load side.

[0061] In the above embodiments, when the transmission type is inter-domain transmission (i.e., service flow between the platform side and the load side), the service traffic between the platform side and the load side is mixed with high real-time control command service traffic and low real-time load service traffic. All traffic needs to be transmitted across domains, and the determinism and reliability of the transmission need to be guaranteed. The inter-domain transmission process between the platform side and the load side can be referred to Figure 9. Figure 9 is a schematic diagram of the TSN switching process of traffic from the platform side to the load side according to the embodiment of this application. As shown in Figure 9, the first TSN switch performs duplicate frame checks on the data frames, eliminates duplicate frames, and adds the deduplicated data frames to the buffer. The first TSN switch identifies the service flow according to the VLAN tag, determines the transmission priority of the service flow, classifies the flow into different queues, and adds the target service flow to the target queue. The first TSN switch can shape traffic from different queues and ensure deterministic traffic latency through gating scheduling, transmitting service flows sequentially. When transmitting target service flow data, it determines the destination MAC address of the service flow data. For service flow data with a non-local destination MAC address, it performs frame duplication and forwards it to the second TSN switch on the load side. The second TSN switch then sends the target service flow data to the destination component on the load side. For data traffic with a local destination MAC address, it sends it to the corresponding destination component on the platform side. The VLAN tag is the aforementioned virtual LAN information, typically used in Ethernet frames to identify the virtual LAN to which the frame belongs. Furthermore, VLAN tags can help network administrators isolate and manage multiple virtual LANs within the physical network. The MAC address, or Media Access Control address, is the address used by network devices (such as computers, routers, printers, etc.) at the data link layer. A MAC address is a unique identifier, usually composed of 12 hexadecimal digits separated by colons or hyphens, used to identify the device's location and communication within the network.

[0062] In the above embodiments, as shown in Figure 6, the functional architecture of the TSN switch further includes: a time-sensitive MAC module and a redundant frame elimination module. The time-sensitive MAC module can use the MAC address to distinguish between time-sensitive traffic and non-time-sensitive traffic. The redundant frame elimination module is used to check for duplicate frames when traffic enters the TSN switch, and can perform deduplication processing on duplicate frames generated by the 802.1CB protocol.

[0063] In an exemplary embodiment, when the target service flow is a service flow sent by a first component within the platform side, the first component sends the target service flow to both the first TSN switch and the third TSN switch, wherein the third TSN switch within the platform side is connected to each component within the platform side; the load side further includes a fourth TSN switch, and each component within the load side is connected to the fourth TSN switch; the first TSN switch is connected to both the second TSN switch and the fourth TSN switch, and the third TSN switch is connected to both the second TSN switch and the fourth TSN switch.

[0064] In the above embodiments, different TSN switches are deployed in the platform-side and payload-side domains respectively. The frame replication module in the TSN switch can achieve primary and backup redundancy: by sending duplicate copies of critical traffic on disjoint paths between domains through the 802.1CB protocol (frame replication-elimination technology), seamless data redundancy transmission between domains can be achieved, ensuring that signaling can reach the destination device even if any link fails. As shown in Figure 1, when the target service flow is sent from the onboard computer (i.e., the first component mentioned above) on the platform side, the onboard computer sends the target service flow to the first TSN switch and the third TSN switch respectively.

[0065] In the above embodiments, the first TSN switch, the third TSN switch, the second TSN switch and the fourth TSN switch are connected in pairs. When the first TSN switch fails, the third TSN switch can transmit with the second TSN switch or the fourth TSN switch to ensure that the target service flow can reach the destination device in real time.

[0066] In the aforementioned embodiments, the internal service traffic on the platform side is mainly generated by the onboard control equipment, such as control commands sent from the onboard computer to the onboard equipment. These commands typically have high priority and high requirements for real-time performance and reliability. Since the port of the first management device is a dedicated control interface, congestion is unlikely. Furthermore, the primary and backup interfaces of the first management device are connected to primary and backup TSN switches, as shown in Figure 10. Figure 10 is a flowchart of the primary and backup command transmission process on the platform side according to the embodiments of this application. After the commands from the onboard computer are copied, they are sent to the first and third TSN switches via primary and backup paths 1 and 2, respectively. The primary command is sent to sensor A via 1-3-5, and the backup command is sent to the backup interface of sensor A via 2-4-6. A failure at any point on the path does not affect the transmission of commands to the destination device. Therefore, when the internal service flow on the platform side is exchanged at the TSN, frame segmentation and frame copying mechanisms are not required.

[0067] In one exemplary embodiment, the target service flow uses a target message format, which includes: an identifier on the platform side, an identifier of the first component, and a transmission mode of the target service flow.

[0068] In the above embodiments, the TSN switching technology only defines a Layer 2 communication format, which cannot fully support upper-layer service data flows between some onboard payloads. Therefore, lightweight transport layer packets (i.e., the target packet format mentioned above) can be used during the transmission between the TSN switch and the controller. Figure 11 is a schematic diagram of the lightweight packet format carried by TSN according to an embodiment of this application. As shown in Figure 11, this packet adds Domain ID (i.e., the identifier on the platform side), Dev ID (i.e., the identifier of the first component), mode (i.e., the transmission mode of the target service flow), and reserved fields to the UDP packet. Among them, the Domain ID field occupies 4 bits; the Dev ID field occupies 1 byte; and the mode field occupies 4 bits. Through the supplemented target packet format, standards for the identity registration, device control, and data transmission modes of interconnected devices under different management domains can be defined.

[0069] In one exemplary embodiment, before the first TSN switch within the platform side receives multiple service flows from multiple components on the platform side, the method further includes: with the central controller, the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch clocked synchronously, the central controller sends data acquisition requests to the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch respectively; the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch respectively send their respective measurement data to the central controller; and the central controller sends TSN flows to the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch respectively to perform TSN configuration on the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch.

[0070] In the above embodiments, the configuration flowchart of the spaceborne switching architecture based on TSN switching technology can be referred to Figure 12. As shown in Figure 12, the central TSN controller performs clock synchronization on all TSN switches (i.e., the first TSN switch, the second TSN switch, the third TSN switch and the fourth TSN switch mentioned above) and sends service data acquisition requests. The TSN switches in the domain complete data acquisition and report the measurement data to the central TSN controller. The central TSN controller generates relevant TSN configurations based on the reported data and distributes the configurations to all TSN switches.

[0071] In an exemplary embodiment, before the first TSN switch within the platform side receives multiple service flows from multiple components on the platform side, the method further includes: with the central controller, the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch, as well as the first TSN controller and the second TSN controller clocked synchronized, the central controller sends data acquisition requests to the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch, as well as the first TSN controller and the second TSN controller, respectively; the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch, as well as the first TSN controller and the second TSN controller, respectively send data acquisition requests to the central controller. Each sends its own measurement data; the central controller sends TSN streams to the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch, as well as the first TSN controller and the second TSN controller, to configure the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch, as well as the first TSN controller and the second TSN controller; wherein, the platform side also includes the first TSN controller, and the load side also includes the second TSN controller; the first TSN controller is connected to the central controller, the first TSN switch, and the third TSN switch, and the second TSN controller is connected to the central controller, the second TSN switch, and the fourth TSN switch.

[0072] In the above embodiment, as shown in Figure 13, the central TSN controller synchronizes the clocks of all TSN controllers (i.e., the first and second TSN controllers mentioned above) and all TSN switches within the domain, and sends service data collection requests to different management domains. The TSN controllers within the management domain send service data collection requests to the TSN switches within the domain. All TSN switches within the domain complete data collection and report measurement data to the TSN controllers within the domain. All TSN controllers within the domain process traffic. For some intra-domain traffic, they perform traffic scheduling and filtering locally. For the remaining cross-domain traffic, they report it to the central TSN controller for processing. The central TSN controller generates relevant TSN configurations based on the reported data and distributes the configurations to all TSN switches and all TSN controllers.

[0073] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a component (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0074] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the steps of the method described in any of the preceding claims.

[0075] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0076] Embodiments of this application also provide an electronic device including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0077] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0078] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0079] Embodiments of this application also provide a computer program product, including a computer program that, when executed by a processor, implements the steps of the methods described in various embodiments of this application.

[0080] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this application is not limited to any particular combination of hardware and software.

[0081] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.

Claims

1. A method for transmitting service flows, applied to a satellite control system, the satellite comprising a platform side and a payload side, the platform side including service components for providing services to payload components, the payload side including payload components for performing tasks, the platform side and the payload side being connected via a central controller, comprising: The first TSN switch within the platform side receives multiple service flows from multiple components within the platform side, wherein each component within the platform side is connected to the first TSN switch. The first TSN switch determines the transmission type of the target service flow based on the destination address of the target service flow, wherein the plurality of service flows include the target service flow; The first TSN switch sends the target service flow to the destination component according to the transmission type.

2. The method according to claim 1, wherein, The first TSN switch determines the transmission type of the service flow based on the destination address of the target service flow, including: If the destination address is the address of a component within the platform, the transmission type of the target service flow is determined to be intra-domain transmission; or, If the destination address is the address of the component within the payload side, the transmission type of the target service flow is determined to be inter-domain transmission.

3. The method according to claim 2, wherein, The first TSN switch sends the target service flow to the destination component according to the transmission type, including: When the transmission type is intra-domain transmission, the first TSN switch determines the transmission priority of the target service flow based on the virtual LAN information of the service flow, and adds the target service flow to the target queue corresponding to the transmission priority; The first TSN switch performs shaping and gating scheduling operations on the service flows in the target queue, and transmits the service flows in the target queue sequentially. When the target service flow is about to be transmitted, the target service flow is transmitted to the destination component.

4. The method according to claim 2, wherein, The first TSN switch sends the target service flow to the destination component according to the transmission type, including: When the transmission type is the inter-domain transmission, the first TSN switch determines the transmission priority of the target service flow based on the virtual LAN information of the target service flow, and adds the target service flow to the target queue corresponding to the transmission priority; The first TSN switch performs shaping and gating scheduling operations on the service flows in the target queue, and transmits the service flows in the target queue sequentially. When the target service flow is about to be transmitted, the target service flow is sent to the second TSN switch in the load side, so that the target service flow can be sent to the destination component through the second TSN switch. The second TSN switch in the load side is connected to each component in the load side.

5. The method according to claim 1, wherein, The method further includes: When the target service flow is a service flow sent by the first component within the platform side, the first component sends the target service flow to the first TSN switch and the third TSN switch respectively, wherein the third TSN switch within the platform side is connected to each component within the platform side; The load side also includes a fourth TSN switch, and each component in the load side is connected to the fourth TSN switch; The first TSN switch is connected to the second TSN switch and the fourth TSN switch respectively, and the third TSN switch is connected to the second TSN switch and the fourth TSN switch respectively.

6. The method according to claim 5, wherein, The target service flow uses a target message format, which includes: the platform-side identifier, the identifier of the first component, and the transmission mode of the target service flow.

7. The method according to claim 5, wherein, Before the first TSN switch within the platform side receives multiple service flows from multiple components on the platform side, the method further includes: When the central controller, the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch are clocked in sync, the central controller sends data acquisition requests to the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch, respectively. The first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch each send their respective measurement data to the central controller; The central controller sends TSN flows to the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch respectively to configure the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch.

8. The method according to claim 5, wherein, Before the first TSN switch within the platform side receives multiple service flows from multiple components on the platform side, the method further includes: When the central controller, the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch, as well as the first TSN controller and the second TSN controller, are clock-synchronized, the central controller sends data acquisition requests to the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch, as well as the first TSN controller and the second TSN controller, respectively. The first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch, as well as the first TSN controller and the second TSN controller, respectively send their respective measurement data to the central controller; The central controller sends TSN flows to the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch, as well as the first TSN controller and the second TSN controller, to configure the first TSN switch, the third TSN switch, the second TSN switch, and the fourth TSN switch, as well as the first TSN controller and the second TSN controller. The platform side further includes the first TSN controller, and the load side further includes the second TSN controller; The first TSN controller is connected to the central controller, the first TSN switch and the third TSN switch respectively, and the second TSN controller is connected to the central controller, the second TSN switch and the fourth TSN switch respectively.

9. A satellite control system, comprising: Platform side, load side, and central controller, among which, The first TSN controller on the platform side and the second TSN controller on the load side are respectively connected to the central controller; The first TSN controller in the platform side is connected to the first TSN switch and the third TSN switch, and each component in the platform side is connected to the first TSN switch and the third TSN switch respectively; The second TSN controller in the load side is connected to the second TSN switch and the fourth TSN switch, and each component in the load side is respectively connected to the second TSN switch and the fourth TSN switch; The platform side includes a service component for providing services to the payload component, and the payload side includes a payload component for performing tasks.

10. A satellite control system, comprising: Platform side, load side, and central controller, among which, The first and third TSN switches on the platform side, and the second and fourth TSN switches on the load side, are respectively connected to the central controller. Each component on the platform side is connected to the first TSN switch and the third TSN switch, respectively. Each component in the load side is connected to the second TSN switch and the fourth TSN switch, respectively; The platform side includes a service component for providing services to the payload component, and the payload side includes a payload component for performing tasks.

11. A computer-readable storage medium storing a computer program, wherein, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 8.

12. An electronic device comprising a memory and a processor, the memory storing a computer program, the processor being configured to run the computer program to perform the method of any one of claims 1 to 8.

13. A computer program product comprising a computer program that, when executed by a processor, implements the steps of the method according to any one of claims 1 to 8.

Images