Satellite efficient inter-container communication method based on Unix socket
By using Unix domain socket technology in satellite communication systems, the problem that traditional network communication methods are difficult to meet the efficient and low-latency inter-container communication needs, achieving low-latency and high-throughput communication effects, improving satellite data Processing capacity and reduce energy consumption.
Patent Information
- Application Number
- CN202411753096.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-02
- Publication Date
- 2025-02-14
AI Technical Summary
In satellite communication systems, traditional network communication methods are difficult to meet the needs of efficient and low-latency inter-container communication due to the complexity and overhead of the network protocol stack.
Using a Unix socket-based communication method, efficient data exchange between containers is achieved by creating Unix domain sockets on a shared file system.
It realizes a low-latency and high-throughput inter-process communication mechanism, significantly improves the ability and response speed of satellite data processing, and effectively reduces energy consumption during communication.
Smart Images
Figure CN119449150A_ABST
Abstract
Description
Technical Field
[0001] The invention relates to the technical field of aerospace communication, and in particular to a satellite efficient inter-container communication method based on Unix sockets. Background Art
[0002] Satellite communication is to install a certain power transponder on the satellite, which processes the sound or television broadcast signal sent from the ground and broadcasts it to another place to achieve communication between two or more places. This kind of communication can transmit telephone, radio programs and television programs. Satellite communication emerged in the mid-1960s. At the beginning, this technology was mainly used to transmit information between continents and oceans.
[0003] With the continuous development of satellite communication technology, more and more satellite communication systems have begun to adopt containerization technology to deploy and manage applications. Containerization technology has become an important choice for application deployment in satellite communication systems due to its advantages such as lightweight, flexibility and scalability. However, in satellite communication systems, the communication efficiency between containers has become an urgent problem to be solved. Especially in scenarios where the processing logic is highly centralized, the communication between containers is frequent and the latency requirements are extremely high, the traditional network communication method is difficult to meet the communication requirements of high efficiency and low latency due to the complexity and overhead of the network protocol stack. Although the traditional network communication method, such as TCP / IP protocol, has wide applicability and good compatibility, its complex protocol stack and large overhead limit the improvement of communication efficiency in satellite communication systems. Therefore, a satellite efficient container communication method based on Unix sockets is proposed. Summary of the invention
[0004] The purpose of the present invention is to provide a satellite efficient inter-container communication method based on Unix sockets to solve the problems raised in the above background technology.
[0005] To achieve the above object, the present invention provides the following technical solution: a satellite efficient inter-container communication method based on Unix socket, comprising the following steps: S1. Unix domain socket basic construction; S2, creation of Unix domain socket in container; S3, shared volume configuration between containers; S4: Data transmission and connection closing.
[0006] Preferably, the above step S1 includes the following sub-steps: S101, using a system call to create a Unix domain socket file descriptor on the server side; S102, binding the Unix domain socket to a file system path, and entering a listening state to prepare to accept a connection request from a device end; S103, when receiving a connection request from the stand-alone device, accept the connection and create a new Unix domain socket file descriptor for subsequent communication; S104, transmitting data between the server and the device end through read and write operations; S105: After the communication is completed, the Unix domain socket is closed and related resources are cleaned up.
[0007] Preferably, in the above: in S102, the Unix domain socket is bound to a file system path in the same manner as a network socket is bound to an IP address and a port.
[0008] Preferably, the above step S2 includes the following sub-steps: S201. In container A that needs to communicate, its application first creates a Unix domain socket file; S202: The application of container A is bound to the Unix domain socket file and starts to listen for connection requests from other processes or containers.
[0009] Preferably, in the above: in S201, the Unix domain socket file is located in the file system of container A.
[0010] Preferably, the above step S3 includes the following sub-steps: S301, setting a shared volume, and sharing the directory containing the Unix domain socket file through the volume function of Docker when starting container A and container B; S302: The application of container B opens the Unix domain socket file and initiates a connection request to container A. S303: The connection is established, and container A and container B can start exchanging data through the Unix domain socket.
[0011] Preferably, the above step S4 includes the following sub-steps: S401, the communicating parties exchange data through send / recv or read / write system calls; S402: After the communication is completed, both parties normally close the Unix domain socket connection and clean up related resources.
[0012] Preferably, in the above: in S401, the Unix domain socket is a memory-based communication.
[0013] Compared with the prior art, the present invention adopts the above technical solution and has the following technical effects: The present invention proposes an innovative method for realizing efficient data exchange between containers in a satellite communication system by using Unix domain socket technology. The method is particularly suitable for scenarios where the processing logic is highly concentrated in a single high-performance processing unit, and the communication requirements between containers are frequent and the delay requirements are extremely strict. In such an environment, the use of Unix domain sockets as a means of communication between containers still shows excellent efficiency.
[0014] The present invention successfully constructs a low-latency, high-throughput inter-process communication mechanism by creating a Unix domain socket on a shared file system, which not only significantly improves the satellite data processing capability and response speed, but also effectively reduces the energy consumption during the communication process, thereby further extending the satellite's operating life. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0016] Figure 1 It is a schematic diagram of the process of the present invention. DETAILED DESCRIPTION
[0017] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0018] It should be noted that the structures, proportions, sizes, etc. illustrated in the drawings of this specification are only used to match the contents disclosed in the specification for people familiar with this technology to understand and read, and are not used to limit the conditions under which this application can be implemented. Therefore, they have no substantive technical significance. Any structural modification, change in proportional relationship or adjustment of size should still fall within the scope of the technical content disclosed in this application without affecting the effects and purposes that can be achieved by this application. Example
[0019] See also Figure 1 The present invention provides a technical solution: a satellite efficient inter-container communication method based on Unix socket, comprising the following steps: S1. Unix domain socket basic construction; The following sub-steps are included: S101, using a system call to create a Unix domain socket file descriptor on the server side; S102, binding the Unix domain socket to a file system path, and entering a listening state to prepare to accept a connection request from the device end; the Unix domain socket is bound to a file system path in the same manner as the network socket is bound to an IP address and port.
[0020] Bind the Unix domain socket to a specific file system path and put it into listening state, ready to receive connection requests from the device at any time. Although the way Unix domain sockets are bound to file system paths is similar to the way network sockets are bound to IP addresses and ports, the two are highly similar in the preparation phase, that is, the process of waiting and preparing to accept connection requests.
[0021] S103, when receiving a connection request from the stand-alone device, accept the connection and create a new Unix domain socket file descriptor for subsequent communication; S104, transmitting data between the server and the device through read and write operations; S105. After the communication is completed, the Unix domain socket is closed and related resources are cleaned up.
[0022] S2, creation of Unix domain socket in container; The following sub-steps are included: S201. In container A that needs to communicate, its application first creates a Unix domain socket file; The Unix domain socket file is located in the file system of container A, for example / tmp / app.socket, and the application of container A will then bind to this socket file.
[0023] S202: The application of container A is bound to the Unix domain socket file and starts to listen for connection requests from other processes or containers.
[0024] S3, shared volume configuration between containers; The following sub-steps are included: S301. Set a shared volume. When starting container A and container B, share the directory containing the Unix domain socket file through the volume function of Docker. Share the directory containing the socket file, such as / tmp, through the volume function of Docker. Even if the file systems of the two containers are isolated, they can share the same socket file.
[0025] S302: The application of container B opens the Unix domain socket file and initiates a connection request to container A. S303: The connection is established, and container A and container B can start exchanging data through the Unix domain socket.
[0026] S4: Data transmission and connection closing.
[0027] The following sub-steps are included: S401, the communicating parties exchange data through send / recv or read / write system calls; Unix domain sockets are memory-based communication, so data transfer is very fast.
[0028] S402: After the communication is completed, both parties normally close the Unix domain socket connection and clean up related resources.
[0029] Unix domain sockets are an inter-process communication (IPC) mechanism that is similar to TCP / IP sockets, but do not use network protocols. Instead, they use socket files in the file system for communication, eliminating the encapsulation and decapsulation process of data packets at the network layer, reducing latency and improving throughput.
[0030] In summary, the present invention proposes an innovative method for realizing efficient data exchange between containers in a satellite communication system by using Unix domain socket technology. This method is particularly suitable for scenarios where the processing logic is highly concentrated in a single high-performance processing unit, and the communication requirements between containers are frequent and the delay requirements are extremely strict. In such an environment, the use of Unix domain sockets as a means of communication between containers still shows excellent efficiency.
[0031] The present invention successfully constructs a low-latency, high-throughput inter-process communication mechanism by creating a Unix domain socket on a shared file system, which not only significantly improves the satellite data processing capability and response speed, but also effectively reduces the energy consumption during the communication process, thereby further extending the satellite's operating life.
[0032] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present invention may be combined and / or combined in various ways, even if such combinations and / or combinations are not explicitly described in the present invention. In particular, the features described in the various embodiments and / or claims of the present invention may be combined and / or combined in various ways without departing from the spirit and teachings of the present invention. All of these combinations and / or combinations fall within the scope of the present invention.
Claims
1. A satellite efficient inter-container communication method based on Unix sockets, characterized in that: The following steps are involved: S1. Unix domain socket basic construction; S2, creation of Unix domain socket in container; S3, shared volume configuration between containers; S4: Data transmission and connection closing.
2. The satellite efficient inter-container communication method based on Unix socket according to claim 1, characterized in that: In S1, the following sub-steps are included: S101, using a system call to create a Unix domain socket file descriptor on the server side; S102, binding the Unix domain socket to a file system path, and entering a listening state to prepare to accept a connection request from a device end; S103, when receiving a connection request from the stand-alone device, accept the connection and create a new Unix domain socket file descriptor for subsequent communication; S104, transmitting data between the server and the device end through read and write operations; S105: After the communication is completed, the Unix domain socket is closed and related resources are cleaned up.
3. The satellite efficient inter-container communication method based on Unix socket according to claim 2, characterized in that: In S102, the Unix domain socket is bound to a file system path in the same manner as a network socket is bound to an IP address and port.
4. The satellite efficient inter-container communication method based on Unix socket according to claim 1, characterized in that: In S2, the following sub-steps are included: S201. In container A that needs to communicate, its application first creates a Unix domain socket file; S202: The application of container A is bound to the Unix domain socket file and starts to listen for connection requests from other processes or containers.
5. The satellite efficient inter-container communication method based on Unix socket according to claim 4, characterized in that: In S201, the Unix domain socket file is located in the file system of container A.
6. The satellite efficient inter-container communication method based on Unix socket according to claim 1, characterized in that: In S3, the following sub-steps are included: S301, setting a shared volume, and sharing the directory containing the Unix domain socket file through the volume function of Docker when starting container A and container B; S302: The application of container B opens the Unix domain socket file and initiates a connection request to container A. S303: The connection is established, and container A and container B can start exchanging data through the Unix domain socket.
7. The satellite efficient inter-container communication method based on Unix socket according to claim 6, characterized in that: In S4, the following sub-steps are included: S401, the communicating parties exchange data through send / recv or read / write system calls; S402: After the communication is completed, both parties normally close the Unix domain socket connection and clean up related resources.
8. The satellite efficient inter-container communication method based on Unix socket according to claim 7, characterized in that: In S401, the Unix domain socket is memory-based communication.