A message transmission method, device, apparatus and medium

Abstract

The application provides a message transmission method, device and equipment and medium. A public prefix is planned for a network domain and a computing power domain corresponding to a ground segment and a space segment respectively, so that the limited bandwidth resources of inter-satellite and satellite-ground can be effectively adapted, and the influence of unstable bandwidth on message transmission can be avoided. By obtaining a message transmission path, dynamic topology changes of inter-satellite and satellite-ground can be flexibly coped with, and the transmission efficiency of message payload can be improved. By allocating a segment identifier to each routing node on each message transmission path according to the public prefix, each routing node can be sequentially jumped to in the message transmission process to perform corresponding services according to the planned path, without additional information announcement between the routing nodes, so that the announcement overhead caused by the limited bandwidth and dynamic topology changes of inter-satellite and satellite-ground can be significantly reduced. While guaranteeing network path forwarding, the collaborative scheduling demand of computing power resources and network resources can be met, and integrated routing message transmission of satellite-ground can be effectively realized.

Description

Technical Field

[0001] This application relates to the field of satellite network technology, and more specifically, to a message transmission method, apparatus, device, and medium. Background Technology

[0002] Segment Routing IPv6 (SRv6) is a protocol designed based on source routing principles for forwarding IPv6 packets over a network. SRv6 forwards segments by inserting a Segment Routing Header (SRH) into the IPv6 packet, pushing an explicit IPv6 address stack onto the SRH, and having intermediate nodes continuously update the destination and offset address stacks. SRv6 is based on IPv6 forwarding and is fully compatible with existing IPv6 networks. Intermediate (transit) nodes may not support SRv6 and can forward IPv6 packets containing SRHs using normal routing.

[0003] However, SRv6 often focuses only on network path forwarding, which makes it difficult to meet the requirements of coordinated scheduling of computing and network resources, resulting in difficulty in realizing packet transmission on routing nodes between satellite and ground. Summary of the Invention

[0004] In view of this, this application provides a message transmission method, apparatus, device and medium that, while ensuring network path forwarding, meets the collaborative scheduling request of computing resources and network resources, and effectively realizes integrated satellite-ground routing message transmission.

[0005] Specifically, this application is implemented through the following technical solution:

[0006] According to a first aspect of this application, a message transmission method is provided, applied to a controller, the method comprising:

[0007] Obtain the message transmission path and the common prefixes planned for the network domain and computing domain corresponding to the ground segment and space segment, respectively.

[0008] The message transmission path includes various routing nodes through which the message transmission passes. Each routing node includes ground-based computing power routing nodes and non-computing power routing nodes, as well as satellite-based computing power routing nodes and non-computing power routing nodes. The computing power routing nodes are used to provide computing power services, and the non-computing power routing nodes are used to provide forwarding services.

[0009] The common prefix is ​​used to locate the transmission position of the message; the network domain is a set of multiple network devices; and the computing power domain is a set of multiple computing devices.

[0010] For each of the aforementioned routing nodes,

[0011] Assign segment identifiers to the routing nodes according to the public prefix, and

[0012] The segment identifier assigned to the routing node is notified to all other routing nodes in the message transmission path;

[0013] The segment identifier includes a type indicator, which indicates the segment type and service type to which the corresponding routing node belongs. The segment type includes a ground segment or a space segment, and the service type includes computing power service or forwarding service.

[0014] In one optional implementation, the common prefix is ​​planned through the following steps:

[0015] Pre-plan the common prefixes for the network domain and computing power domain corresponding to the ground segment and space segment, respectively;

[0016] Alternatively, dynamically program the common prefixes of the network domain and computing power domain corresponding to the ground segment and the space segment, respectively;

[0017] Alternatively, a portion of the common prefixes of the network domain and computing power domain corresponding to the ground segment and space segment can be pre-planned, and the other portion can be dynamically planned.

[0018] In one optional implementation, the message transmission path is obtained through the following steps:

[0019] Obtain the destination address of the message, and calculate the message transmission path to the destination address based on the destination address of the message. The destination address is the address of the computing device or network device determined according to the computing power service and forwarding service requirements of the message.

[0020] According to a second aspect of this application, a message transmission method is provided, applied to a routing node, the method comprising:

[0021] The receiver receives the message transmission path issued by the controller, the segment identifier assigned by the controller to the current routing node, and the segment identifiers assigned by the controller to other routing nodes on the message transmission path. The segment identifier is assigned by the controller based on a common prefix planned for the network domain and computing power domain corresponding to the ground segment and space segment, respectively. The common prefix is ​​used to locate the transmission position of the message. The network domain is a set of multiple network devices, and the computing power domain is a set of multiple computing devices. The routing nodes in the message transmission path include ground-based computing power routing nodes and non-computing power routing nodes, as well as satellite-based computing power routing nodes and non-computing power routing nodes. The computing power routing nodes provide computing power services, and the non-computing power routing nodes provide forwarding services. The segment identifier includes a type indicator, which indicates the segment type and service type to which the corresponding routing node belongs. The segment type includes a ground segment or a space segment, and the service type includes computing power services or forwarding services.

[0022] Upon receiving any message, the segment identifiers of each routing node in the message transmission path corresponding to the message are encapsulated in the routing extension header of the message, and the corresponding service is executed according to the segment identifier assigned to the current routing node.

[0023] In one optional implementation, the step of encapsulating the segment identifier of each routing node in the packet transmission path corresponding to the packet in the routing extension header of any packet includes:

[0024] The segment identifier of each routing node in the message transmission path corresponding to any message is compressed to obtain the compressed segment identifier.

[0025] The compressed segment identifier is encapsulated in the routing extension header of any of the packets;

[0026] The method further includes:

[0027] Based on the planning method of the public prefix, construct the association between the type indicator and the public prefix.

[0028] In one optional implementation, the step of compressing the segment identifier of each routing node in the packet transmission path corresponding to any given packet to obtain a compressed segment identifier includes:

[0029] For each segment identifier of the routing node in the message transmission path corresponding to any message, the type indicator identifier and other data required for compression are extracted from the segment identifier to generate a compressed segment identifier.

[0030] In one optional implementation, the step of constructing the association between the type indicator and the public prefix according to the planning method of the public prefix includes:

[0031] If the public prefix is ​​pre-planned, the type indicator identifier and its associated public prefix are pre-stored;

[0032] When the common prefix is ​​dynamically planned, the type indicator and its associated common prefix are dynamically carried in the header of the received message.

[0033] In one optional implementation, the step of performing the corresponding service based on the segment identifier assigned to the current routing node includes:

[0034] Based on the segment identifier assigned to the current routing node, determine the position of the current routing node in the message transmission path and the corresponding service type;

[0035] Based on the current location of the routing node in the message transmission path and the corresponding service type, the corresponding service is executed.

[0036] In one optional implementation, the step of executing the corresponding service based on the current position of the routing node in the packet transmission path and the corresponding service type includes:

[0037] If the current routing node is not the last node in the message transmission path, update the target destination address of the message transmission, and execute the corresponding service according to the updated target destination address and the corresponding service type. The target destination address is the address of the next routing node.

[0038] If the current routing node is the last node in the message transmission path, the corresponding service is executed locally according to the corresponding service type.

[0039] In one optional implementation, the target destination address of the update message transmission includes:

[0040] Extract the segment identifier corresponding to the next routing node from the segment identifiers of each routing node in the packet transmission path encapsulated in the routing extension header of the packet, and use the segment identifier corresponding to the next routing node as the updated target destination address.

[0041] In one optional implementation, the target destination address of the update message transmission includes:

[0042] If the routing extension header of the message encapsulates a compressed segment identifier, extract the compressed segment identifier and type indicator corresponding to the next routing node from the compressed segment identifiers of each routing node in the message transmission path encapsulated in the routing extension header of the message.

[0043] Based on the type indicator corresponding to the next routing node and the pre-built association between the type indicator and the common prefix, the common prefix corresponding to the next routing node is obtained;

[0044] Based on the compressed segment identifier corresponding to the next routing node and the common prefix, the updated target destination address is determined.

[0045] According to a third aspect of this application, a message transmission apparatus is provided, applied to a controller, the apparatus comprising:

[0046] The data acquisition module is used to acquire the message transmission path and the common prefixes planned for the network domain and computing power domain corresponding to the ground segment and space segment, respectively. The message transmission path includes various routing nodes through which the message passes. Each routing node includes ground-based computing power routing nodes and non-computing power routing nodes, as well as satellite-based computing power routing nodes and non-computing power routing nodes. The computing power routing nodes provide computing power services, and the non-computing power routing nodes provide forwarding services. The common prefix is ​​used to locate the transmission position of the message. The network domain is a set of multiple network devices, and the computing power domain is a set of multiple computing devices.

[0047] The identifier allocation module is used to allocate a segment identifier to each routing node according to the common prefix, and to notify other routing nodes in the message transmission path of the segment identifier allocated to the routing node; wherein, the segment identifier includes a type indicator identifier, which is used to indicate the segment type and service type to which the corresponding routing node belongs, the segment type includes a ground segment or a space segment, and the service type includes a computing power service or a forwarding service.

[0048] According to a fourth aspect of this application, a message transmission apparatus is provided, applied to a routing node, the apparatus comprising:

[0049] The identification receiving module is used to receive the message transmission path issued by the controller, and to receive the segment identifier assigned by the controller to the current routing node, as well as the segment identifiers assigned by the controller to other routing nodes on the message transmission path. The segment identifier is assigned by the controller based on a common prefix planned for the network domain and computing power domain corresponding to the ground segment and space segment, respectively. The common prefix is ​​used to locate the transmission position of the message. The network domain is a set of multiple network devices, and the computing power domain is a set of multiple computing devices. The routing nodes in the message transmission path include ground-based computing power routing nodes and non-computing power routing nodes, as well as satellite-based computing power routing nodes and non-computing power routing nodes. The computing power routing nodes provide computing power services, and the non-computing power routing nodes provide forwarding services. The segment identifier includes a type indicator identifier, which indicates the segment type and service type to which the corresponding routing node belongs. The segment type includes a ground segment or a space segment, and the service type includes computing power services or forwarding services.

[0050] The service execution module is used to, upon receiving any message, encapsulate the segment identifiers of each routing node in the message transmission path corresponding to the message in the routing extension header of the message, and execute the corresponding service according to the segment identifier assigned to the current routing node.

[0051] According to a third aspect of this application, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the message transmission method described in the first aspect or the steps of the message transmission method described in the second aspect.

[0052] According to a fourth aspect of this application, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the steps of the message transmission method described in the first aspect or the steps of the message transmission method described in the second aspect.

[0053] The message transmission method, apparatus, device, and medium provided in this application, by planning common prefixes for the network domain and computing power domain corresponding to the ground segment and space segment respectively, can effectively adapt to the limited bandwidth resources between satellites and between satellite and ground, avoiding the impact of unstable bandwidth on message transmission. Simultaneously, by obtaining the message transmission path, it can flexibly respond to dynamic topology changes between satellites and between satellite and ground, improving the transmission efficiency of the message payload. Furthermore, by assigning segment identifiers to each routing node on each message transmission path according to the common prefix, during message transmission, it can sequentially jump to each routing node according to the planned path to execute the corresponding service, without the need for additional announcements between routing nodes, thereby significantly reducing the announcement overhead caused by limited bandwidth between satellites and between satellite and ground and dynamic topology changes. While ensuring network path forwarding, it meets the collaborative scheduling requirements of computing power resources and network resources, and can be compatible with different types of routing nodes, effectively realizing integrated satellite-ground routing message transmission, which helps improve the efficiency and reliability of integrated computing and network message transmission between satellites / between satellites and ground.

[0054] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory, and are not intended to limit the technical solutions of this disclosure.

[0055] To make the above-mentioned objects, features and advantages of this disclosure more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0056] Figure 1 This is a flowchart illustrating a message transmission method according to an exemplary embodiment of this application;

[0057] Figure 2 This is a schematic diagram of a traditional segment identifier format;

[0058] Figure 3 This is a schematic diagram illustrating the format of a segment identifier according to an exemplary embodiment of this application;

[0059] Figure 4 This is a flowchart illustrating another message transmission method according to an exemplary embodiment of this application;

[0060] Figure 5 This is a schematic diagram illustrating the encapsulation of a routing extension header according to an exemplary embodiment of this application;

[0061] Figure 6 This is a schematic diagram illustrating the format of a compressed segment identifier according to an exemplary embodiment of this application;

[0062] Figure 7 This is a schematic diagram illustrating the format of a pre-stored type indicator and its associated public prefix, as shown in an exemplary embodiment of this application;

[0063] Figure 8 This is a schematic diagram illustrating an exemplary embodiment of this application of a format in which a type indicator identifier and its associated public prefix are dynamically carried in the header of a received message;

[0064] Figure 9 yes Figure 8 The format diagram of the public prefix information shown;

[0065] Figure 10 This is a schematic diagram illustrating the association between a construction type indicator and a public prefix, as shown in an exemplary embodiment of this application;

[0066] Figure 11 This is a schematic diagram illustrating an exemplary embodiment of this application for updating a target destination address;

[0067] Figure 12 This is a schematic diagram illustrating an exemplary embodiment of the present application of a satellite-ground integrated message transmission process;

[0068] Figure 13 This is a schematic diagram of a message transmission device illustrated in an exemplary embodiment of this application;

[0069] Figure 14 This is a schematic diagram of another message transmission apparatus illustrated in an exemplary embodiment of this application;

[0070] Figure 15 This is a schematic diagram of the structure of a computer device shown in an exemplary embodiment of this application. Detailed Implementation

[0071] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0072] The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The singular forms “a,” “the,” and “the” used in this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0073] It should be understood that although the terms first, second, third, etc., may be used in this application to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0074] Research has found that SRv6 often focuses only on network path forwarding, which makes it difficult to meet the requirements of coordinated scheduling of computing and network resources, resulting in difficulty in achieving packet transmission on routing nodes between satellite and ground.

[0075] With the development of technology, some link-state protocols allow the carrying of computing resources. For example, the China Communications Standards Association (CCSA) industry standard draft for approval, "Technical Requirements for Computing Power Routing Protocol in Computing Power Networks: OSPF (Open Shortest Path First) Protocol Extension," specifies the extension of the traditional OSPF Link-State Advertisement (LSA) to carry computing power resources and computing power service information. The CCSA industry standard draft for approval, "Technical Requirements for Computing Power Routing Based on SRv6 in Computing Power Networks," specifies that in SRv6 computing power service function programming, it supports the combination of a Segment Identifier (SID) identifying the computing power service and a SID identifying the SRv6 forwarding path, and supports multiple SID combinations identifying computing power services, so that computing power service traffic can achieve network layer (L3) service function chaining (SFC) between SRv6 computing power routing nodes.

[0076] In large-scale inter-satellite networks and integrated space-ground networks, there are often multiple types of nodes, including network device nodes, computing device nodes, computing power nodes, and forwarding nodes. How to achieve compatibility with multiple types of nodes, adapt to the limited bandwidth of inter-satellite / space-ground networks and dynamic topology changes of inter-satellite / space-ground networks, so as to realize end-to-end integrated computing and network message transmission based on SRv6, has become an urgent problem to be solved.

[0077] Based on the above research, this application provides a message transmission method, apparatus, device and medium that, while ensuring network path forwarding, meets the collaborative scheduling request of computing resources and network resources, and is compatible with different types of routing nodes, effectively realizing integrated satellite-to-ground routing message transmission, which helps to improve the efficiency and reliability of inter-satellite / satellite-to-ground end-to-end integrated computing and network message transmission.

[0078] The following description, in conjunction with the accompanying drawings, illustrates a message transmission method provided by an embodiment of this application.

[0079] See Figure 1 The diagram shown is a flowchart illustrating a message transmission method according to an exemplary embodiment of this application. The method is applied to a controller; in practical applications, the controller can be a ground control center, a space-ground computing network management center, or a satellite controller, etc.

[0080] like Figure 1 As shown in the figure, the message transmission method provided in this embodiment includes steps S101 to S102, wherein:

[0081] S101: Obtain the message transmission path and the common prefixes planned for the network domain and computing power domain corresponding to the ground segment and space segment, respectively. The message transmission path includes each routing node through which the message passes. Each routing node includes a ground-based computing power routing node and a non-computing power routing node, as well as a satellite-based computing power routing node and a non-computing power routing node. The computing power routing node is used to provide computing power services, and the non-computing power routing node is used to provide forwarding services. The common prefix is ​​used to locate the transmission position of the message. The network domain is a set of multiple network devices, and the computing power domain is a set of multiple computing devices.

[0082] Here, the message transmission path can be planned by the controller or by any node in the message transmission path.

[0083] The non-computing power routing node is a traditional node with network routing and forwarding functions.

[0084] It should be noted that all nodes in the embodiments of this disclosure are nodes that support SRv6.

[0085] In some possible implementations, the message transmission path is obtained through the following steps:

[0086] Obtain the destination address of the message, and calculate the message transmission path to the destination address based on the destination address of the message. The destination address is the address of the computing device or network device determined according to the computing power and forwarding service requirements of the message.

[0087] Here, the destination address of the message can be the address of the destination network device corresponding to a traditional path forwarding message, or the address of the destination computing device corresponding to a computing power service message.

[0088] For example, taking computing power services including artificial intelligence (AI) computing services as an example, the final destination address of an AI computing message is unknown at the message origin. The controller or computing power routing entry node needs to specify the node address of a computing device that can meet the computing power service requirements of the AI ​​computing message as the final destination address of the AI ​​computing message based on the computing power requirements of the message. The computing device can be located in the space segment or the ground segment.

[0089] In practical applications, space-ground integrated networks are often composed of two parts: the space segment and the ground segment. The ground segment refers to all infrastructure deployed on the Earth's surface, including earth stations, telemetry and control facilities, and management units. The space segment refers to the orbital space segment built outside of geostationary orbit, which is layered according to orbital altitude (Low Earth Orbit (LEO), Medium Earth Orbit (MEO), Geostationary Earth Orbit (GEO), etc.).

[0090] The common prefix planned for the network domain and computing power domain corresponding to the space segment can specifically include the common prefix planned for the network domain and computing power domain corresponding to different orbital layers of the space segment.

[0091] Specifically, the common prefix can be planned by the controller.

[0092] In some possible implementations, the common prefix is ​​planned through the following steps:

[0093] Pre-plan the common prefixes for the network domain and computing power domain corresponding to the ground segment and space segment, respectively;

[0094] Alternatively, dynamically program the common prefixes of the network domain and computing power domain corresponding to the ground segment and the space segment, respectively;

[0095] Alternatively, a portion of the common prefixes of the network domain and computing power domain corresponding to the ground segment and space segment can be pre-planned, and the other portion can be dynamically planned.

[0096] Here, the pre-planning can refer to configuration in advance before message transmission, while the dynamic planning can refer to real-time distribution during message transmission.

[0097] Specifically, a portion of the common prefixes of the network domain and computing power domain corresponding to the pre-planned ground segment and space segment are used to dynamically plan another portion, including:

[0098] The common prefixes of the network domain and computing power domain corresponding to the ground segment are pre-planned, and the common prefixes of the network domain and computing power domain corresponding to the spatial segment are dynamically planned.

[0099] Alternatively, pre-plan the common prefixes of the network domain and computing power domain corresponding to the spatial segments, and dynamically plan the common prefixes of the network domain and computing power domain corresponding to the ground segments.

[0100] Alternatively, pre-plan the common prefixes of the network domains corresponding to the ground segment and the space segment, and dynamically plan the common prefixes of the computing power domains corresponding to the ground segment and the space segment.

[0101] Alternatively, pre-plan the common prefixes of the computing domains corresponding to the ground segment and the space segment, and dynamically plan the common prefixes of the network domains corresponding to the ground segment and the space segment.

[0102] Optionally, the format of the public prefix for the ground segment planning can be ground-country-region-city-computer room, and the format of the public prefix for the space segment planning can be satellite-LEO / MEO / GEO-constellation.

[0103] For example, the common prefix for the network domain of the space segment is 2001:fc0:: / 32, the common prefix for the computing power domain of the space segment is 2001:fe0:: / 32, the common prefix for the network domain of the ground segment is 2002:fc0:: / 32, and the common prefix for the computing power domain of the ground segment is 2002:fe0:: / 32.

[0104] In this context, 2001 represents the spatial segment, 2002 represents the ground segment, fc0 represents the network domain, fe0 represents the computing power domain, :: represents all zeros that are omitted, and / 32 represents the length of the common prefix as 32 bits.

[0105] The length of the common prefix can be set according to actual needs, for example, it can be 48 bits or 64 bits. In this case, more bits can be added as a common prefix after the fields representing the space segment / ground segment and the computing domain / network domain. For example, for the space segment, fields representing the orbital layer and constellation (such as the ZJ constellation or the XW constellation) can be added; for the ground segment, fields representing the country and region can be added; for the network domain, fields representing different parts of the network (such as the access network, core network, or bearer network) can be added.

[0106] In this way, by pre-planning or dynamically planning the common prefixes of the network domain and computing domain corresponding to the ground segment and space segment respectively, or by combining pre-planning and dynamic planning, we can flexibly adapt to different network environments and topology changes. Pre-planning some common prefixes can ensure the stable operation and efficient configuration of the network in the initial stage, while dynamic planning can be adjusted according to the real-time network status and needs, which helps to improve the adaptability and scalability of message transmission and enhance the efficiency of message transmission.

[0107] S102: For each of the routing nodes, a segment identifier is assigned to the routing node according to the common prefix, and the segment identifier assigned to the routing node is notified to each of the other routing nodes in the message transmission path; wherein, the segment identifier includes a type indicator identifier, which is used to indicate the segment type and service type to which the corresponding routing node belongs, the segment type includes a ground segment or a space segment, and the service type includes computing power service or forwarding service.

[0108] In this step, after assigning a segment identifier to a certain routing node, the segment identifier can be notified to other routing nodes in the message transmission path so that during message transmission, the corresponding services can be executed sequentially by jumping to each routing node according to the planned path, without the need for additional notification information between routing nodes.

[0109] Specifically, for each routing node in the message transmission path, a segment identifier can be dynamically generated or manually statically allocated for the routing node through the Interior Gateway Protocol (IGP) based on the common prefix, and the segment identifier allocated for the routing node can be notified to the other routing nodes in the message transmission path through the IGP or the Border Gateway Protocol (BGP) extension protocol.

[0110] When notifying each routing node in the message transmission path of the segment identifier assigned to the routing node, in addition to the segment identifier value, the composition and size of each field in the segment identifier, as well as other attributes, such as compression mechanism, endpoint behavior, etc.

[0111] Please see Figure 2 This is a schematic diagram of a traditional segment identifier format. For example... Figure 2As shown, a traditional segment identifier includes a common prefix field, a node ID field, a function ID field, an arguments field, and a padding field, with a total of 128 bits. Specifically, the number of bits for each field can be set according to actual needs; no specific limitation is made here. For example, the common prefix field is 64 bits, the node ID and common ID fields together are 32 bits, and the arguments and padding fields together are 32 bits.

[0112] In this embodiment, the traditional segment identifier is extended by adding a type indicator identifier. Specifically, the type indicator identifier includes a domain and a type indicator (DTI) field. See also Figure 3 This is a schematic diagram illustrating the format of a segment identifier, as shown in an exemplary embodiment of this application. Figure 3 As shown, the field and type indicator fields are new fields added after extending the traditional segment identifier format.

[0113] The DTI field can be represented in hexadecimal or equivalently in binary. For example, in hexadecimal, when the DTI value is 0, the associated common prefix is ​​2001:fc0:: / 32; when the DTI value is 1, the associated common prefix is ​​2001:fe0:: / 32; when the DTI value is 2, the associated common prefix is ​​2002:fc0:: / 32; when the DTI value is 3, the associated common prefix is ​​2002:fe0:: / 32; when the DTI value is 4, the associated common prefix is ​​2001:fc0:1:: / 48; when the DTI value is 5, the associated common prefix is ​​2001:fc0:2:: / 48; when the DTI value is 6, the associated common prefix is ​​2001:fc0:3:: / 48; and when the DTI value is 7, the associated common prefix is ​​2001:fe0:1:: / 48; When the DTI value is 8, the associated common prefix is ​​2001:fe0:2:: / 48; When the DTI value is 9, the associated common prefix is ​​2001:fe0:3:: / 48; When the DTI value is a, the associated common prefix is ​​2002:fc0:1:: / 48; When the DTI value is b, the associated common prefix is ​​2002:fc0:2:: / 48; When the DTI value is c, the associated common prefix is ​​2002:fc0:3:: / 48; When the DTI value is d, the associated common prefix is ​​2002:fe0:1:: / 48; When the DTI value is e, the associated common prefix is ​​2002:fe0:2:: / 48; When the DTI value is f, the associated common prefix is ​​2002:fe0:3:: / 48.

[0114] Here, 32 indicates that there are 32 bits before the :: symbol, and 48 indicates that there are 48 bits before the :: symbol. The number of bits in the common prefix can be set according to actual needs, for example, it can also be 64 bits. When there is a high degree of repetition in the common prefix part of the segment identifier list (SID list), the segment identifier list can be compressed to a greater extent, and a larger common prefix length can be set.

[0115] The DTI field can indicate not only the segment type and service type of the corresponding routing node, but also which part of the network domain its corresponding segment identifier belongs to, such as the access network, core network, or bearer network. If the DTI field indicates that the corresponding routing node belongs to a spatial segment, the DTI field can also indicate which part of the spatial segment its corresponding segment identifier belongs to, such as which constellation it belongs to. In this example, when the DTI values ​​are 4, 5, and 6, the associated public prefixes are 2001:fc0:1:: / 48, 2001:fc0:2:: / 48, and 2001:fc0:3:: / 48, respectively. Here, the 1, 2, and 3 before the :: can represent different constellations (such as ZJ constellation, XW constellation, etc.) or different parts of the network (such as access network, core network, or bearer network, etc.).

[0116] Taking a DTI value of 4 as an example, the associated public prefix is ​​2001:fc0:1:: / 48. This public prefix uses the abbreviation of IPv6, omitting the leading zeros. The complete form is 2001:0fc0:0001:: / 48, and both representations are equivalent. Each part can be converted from hexadecimal to binary; for example, 2001 becomes 00100000 00000001, 0fc0 becomes 00001111 11000000, and 0001 becomes 00000000 00000001.

[0117] The length of the DTI field can be set as needed, for example, it can be 4 bits. Assuming L represents the length of the DTI field, and the unit is the number of binary bits, then L=4, which can be used to indicate 2^L=16 common prefixes. By reasonably designing the length of the DTI field, the length of the segment identifier to be carried can be compressed as needed, thereby improving the forwarding efficiency of the packet.

[0118] like Figure 3 As shown in the example, the field and type indicator fields are positioned after the common prefix field and before the node identifier field. In other examples, the field and type indicator fields may be positioned before the common prefix field.

[0119] As can be seen from the foregoing, since the common prefixes are pre-planned, each common prefix corresponds to a unique type indicator. A type indicator indicates a segment type and a service type. If a routing node provides multiple services, such as both forwarding services and computing power services, multiple segment identifiers can be assigned to the routing node. That is, the routing node can correspond to multiple common prefixes and correspondingly multiple type indicator identifiers. For example, a routing node is assigned two segment identifiers, corresponding to two type indicator identifiers, namely 2001:fc0:1:: / 48 (corresponding to DTI value 4) and 2001:fe0:1:: / 48 (corresponding to DTI value 7). According to / 48, the length of the common prefix is ​​48 bits. The two common prefixes are 2001:0fc0:0001 and 2001:0fe0:0001. Here, 2001 represents the spatial segment, 0fc0 represents the network domain, 0fe0 represents the computing domain, and 0001 represents the constellation code ZJ. Thus, it can be known that the routing node belongs to the ZJ constellation of the spatial segment, that is, it belongs to both the computing domain and the network domain, and provides both forwarding services and computing services.

[0120] When the domain and type indication field is used to indicate that the corresponding routing node belongs to the space segment, the node identification field may include an orbital plane identifier (SatPlane ID) field, a satellite identifier (Sat ID) field, and an interface identifier (Interface ID) field. The orbital plane identifier field is used to indicate the orbital plane to which the node belongs, and the satellite identifier field is used to indicate the satellite to which the node belongs within the orbital plane. When the domain and type indication field is used to indicate that the corresponding routing node belongs to the ground segment, the node identification field may include an interface identifier field, etc. When the domain and type indication field is used to indicate that the corresponding routing node belongs to the computing power service, the function identification field may include a computing power service type identifier (ComputeService Type ID) field, etc. The computing power service type identifier field is used to indicate the type of computing power service; for example, 0x1001 represents AI computing service, 0x1002 represents AI model training service, 0x1003 represents storage service, etc. When the domain and type indication field is used to indicate that the corresponding routing node belongs to the computing power service, the function identification field may include a forwarding behavior type identification field, etc. The forwarding behavior type identification field is used to indicate the forwarding service type. For example, DT4 indicates decapsulating the packet and forwarding it by looking up the table in the specified Internet Protocol version 4 (IPv4) routing table, and DT6 indicates decapsulating the packet and forwarding it by looking up the table in the specified Internet Protocol version 6 (IPv6) routing table. For example, for the segment identifier 2001:0fe0:0001:0101:0001:: / 48, the common prefix is ​​2001:0fe0:0001, which represents the ZJ constellation of the space segment computing power domain. The 0101 after the common prefix represents satellite 01 located in orbital plane 01, and the 0001 after that represents interface Ethernet1. The common prefix of the segment identifier 2001:0fe0:0001:0208:0002:: / 48 is also 2001:0fe0:0001, which represents the ZJ constellation of the space segment computing power domain. The 0208 after the common prefix represents satellite 08 located in orbital plane 02, and the 0002 after that represents interface Ethernet2.

[0121] The message transmission method provided in this disclosure, by acquiring transmission paths including various routing nodes on the ground and satellite, can flexibly respond to dynamic topology changes between satellites and between satellite and ground, improving the transmission efficiency of message payloads. By planning common prefixes for the network domain and computing power domain corresponding to the ground segment and space segment respectively, it can effectively adapt to the limited bandwidth resources between satellites and between satellite and ground, avoiding the impact of unstable bandwidth on message transmission. According to the common prefix, segment identifiers containing domain and type indication fields are assigned to each routing node, realizing accurate positioning and efficient management of message transmission paths. This allows the message transmission process to jump to each routing node sequentially according to the planned path to perform corresponding services without the need for additional announcements between routing nodes, thereby significantly reducing the announcement overhead caused by limited bandwidth between satellites and between satellite and ground and dynamic topology changes. This effectively realizes integrated satellite-ground routing message transmission, helping to improve the efficiency and reliability of integrated network-computer communication message transmission between satellites / between satellites and ground.

[0122] The following describes the message transmission method provided in this embodiment, taking any routing node in the message transmission path as the execution subject.

[0123] See Figure 4 The diagram shown is a flowchart illustrating a message transmission method according to an exemplary embodiment of this application. The method is applied to a routing node, such as... Figure 4 As shown in the figure, the message transmission method provided in this embodiment includes steps S401 to S402, wherein:

[0124] S401: Receive the message transmission path issued by the controller, and receive the segment identifier assigned by the controller to the current routing node, and the segment identifiers assigned by the controller to other routing nodes on the message transmission path; the segment identifier is assigned by the controller based on the common prefix planned for the network domain and computing power domain corresponding to the ground segment and space segment respectively; the common prefix is ​​used to locate the transmission position of the message, the network domain is a set of multiple network devices, and the computing power domain is a set of multiple computing devices; the routing nodes in the message transmission path include ground computing power routing nodes and non-computing power routing nodes, and satellite computing power routing nodes and non-computing power routing nodes, the computing power routing nodes are used to provide computing power services, and the non-computing power routing nodes are used to provide forwarding services; the segment identifier includes a type indicator, the type indicator is used to indicate the segment type and service type to which the corresponding routing node belongs, the segment type includes ground segment or space segment, and the service type includes computing power service or forwarding service.

[0125] Here, the specific descriptions of the message transmission path and the segment identifier can be found in the foregoing embodiments, and will not be repeated here.

[0126] S402: Upon receiving any message, encapsulate the segment identifiers of each routing node in the message transmission path corresponding to the message in the routing extension header of the message, and execute the corresponding service according to the segment identifier assigned to the current routing node.

[0127] It is understood that, for the source node (i.e., the first node) in the message transmission path, this node can directly encapsulate the segment identifiers of each routing node in the message transmission path in the routing extension header of any received message. For other nodes in the message transmission path besides the source node, the messages they receive are sent by the previous routing node. Therefore, the routing extension header of the received messages encapsulates the segment identifiers of each routing node in the message transmission path. Based on actual service needs, these nodes can parse or even insert additional information into the received messages and then re-encapsulate them, which is equivalent to indirectly encapsulating the segment identifiers of each routing node in the message transmission path in the routing extension header of any received message.

[0128] Traditional schemes that do not encapsulate segment identifiers of each routing node in the packet transmission path in the routing extension header of the received packet require each node to query its routing table, thus necessitating a lookup operation at every hop. This makes it difficult to achieve an optimal end-to-end packet transmission path. This embodiment encapsulates segment identifiers of each routing node in the packet transmission path in the routing extension header of the transmitted packet. Each routing node in the packet transmission path can know the order of nodes traversed by the entire packet transmission path, effectively improving packet transmission efficiency. Even with a complex network structure, the location of packet transmission can be clearly determined, facilitating management.

[0129] See Figure 5 This is a schematic diagram illustrating the encapsulation of a routing extension header, as shown in an exemplary embodiment of this application. Figure 5As shown, the Segment Identifier List (SID list) encapsulated in the routing extension header includes the source address, destination address, next header, header length (Hdr Len), routing type, Segments Left (SL), last entry, flags, tags, multiple segment identifiers ordered according to the packet transmission path, and optional type length value (TLV) objects (variables). The following headers are used: Next Header indicates the type of the header immediately following the SRH; Hdr Len indicates the length of the SRH; Routing Type indicates the type of the routing extension header; SL indicates the number of remaining segments, i.e., the number of nodes that have not yet been traversed in the packet transmission path; Last Entry indicates the index of the last element in the Segment List; Flags are reserved flags; Tag indicates packets in the same group; The Segment List includes multiple segment identifiers ordered according to the packet transmission path, specifically including Space Segment Forwarding Service SID, Space Segment Computing Service SID, Ground Segment Forwarding Service SID, Ground Segment Computing Service SID, etc.

[0130] In the above embodiments, the routing extension header of any message encapsulates the complete segment identifier of each routing node in the message transmission path. In other embodiments, the routing extension header of any message may also encapsulate the compressed segment identifier of each routing node in the message transmission path.

[0131] Specifically, the step of encapsulating the segment identifier of each routing node in the packet transmission path corresponding to the packet in the routing extension header of any packet includes:

[0132] The segment identifier of each routing node in the message transmission path corresponding to any message is compressed to obtain the compressed segment identifier.

[0133] The compressed segment identifier is encapsulated in the routing extension header of any of the packets.

[0134] In the above steps, it is possible to perform actions such as... Figure 5The complete 128-bit segment identifiers in the segment list shown are compressed to obtain compressed segment identifiers, which are then encapsulated in the routing extension header of any packet.

[0135] In this way, by encapsulating and compressing the segment identifier, it helps to improve the efficiency of payload transmission, while reducing the requirements for onboard hardware forwarding capabilities, and can effectively adapt to onboard processing capabilities.

[0136] In some possible implementations, the step of compressing the segment identifier of each routing node in the packet transmission path corresponding to any given packet to obtain a compressed segment identifier includes:

[0137] For each segment identifier of the routing node in the message transmission path corresponding to any message, the type indicator identifier and other data required for compression are extracted from the segment identifier to generate a compressed segment identifier.

[0138] Here, when the type indicator includes the domain and the type indicator field, the other data required for compression may include other fields required for compression. These other fields can be determined according to actual compression needs and are not specifically limited here. For example, they may be node identifier fields, function identifier fields, etc.

[0139] See Figure 6 This is a schematic diagram illustrating a compressed segment identifier format, as shown in an exemplary embodiment of this application. Figure 6 As shown, the compressed segment identifier removes the common prefix and includes only the field and type indicator fields, as well as the compressed segment identifier (C-SID) field. The C-SID field includes the other fields required for compression. The compressed segment identifier is significantly shorter than the full segment identifier, for example, to 48 bits, effectively reducing storage space. By properly planning the common prefix and C-SID size, the number of C-SIDs that can be accommodated in a full 128-bit SID field can be limited to 2 or 4.

[0140] In this way, by compressing segment identifiers, the amount of data during message transmission can be effectively reduced, message transmission efficiency can be improved, and the processing logic of routing nodes can be simplified, thereby improving the overall performance of message transmission.

[0141] In some possible implementations, the method further includes:

[0142] Based on the planning method of the public prefix, construct the association between the type indicator and the public prefix.

[0143] Considering that SRH encapsulation supports combinations of space segment and ground segment forwarding service SIDs and / or computing power service SIDs, a complete segment identifier list (SID List) should support multiple different common prefixes. However, common prefixes are removed during segment identifier compression. To enable subsequent segment identifier recovery and address filling for the next routing node, it is necessary to know the common prefix corresponding to each compressed segment identifier. Therefore, the association between the type indicator and the common prefix is ​​constructed using the type indicator. Since the type indicator is added information after extending the original segment identifier format and is retained during segment identifier compression, the compressed segment identifier can be recovered through the common prefix associated with the type indicator. The method of constructing the association varies depending on the planning method of the common prefix.

[0144] In some possible implementations, constructing the association between the type indicator and the public prefix based on the planning method of the public prefix includes:

[0145] If the public prefix is ​​pre-planned, the type indicator identifier and its associated public prefix are pre-stored;

[0146] When the common prefix is ​​dynamically planned, the type indicator and its associated common prefix are dynamically carried in the header of the received message.

[0147] If all the public prefixes are pre-planned, as long as the pre-planned public prefixes do not change, the public prefix associated with the type indicator remains unchanged, and there is no need for announcement and dynamic updates between nodes. In actual deployment, the type indicator and its associated public prefixes can be pre-stored in tabular form in each routing node of the ground segment and / or space segment. See also Figure 7 This is a schematic diagram illustrating the format of a pre-stored type indicator and its associated public prefix, as shown in an exemplary embodiment of this application. Figure 7 As shown in the diagram, taking the type indicator identifier, which includes a domain and a type indicator field, as an example, when the domain and type indicator field values ​​are 0, the associated common prefix is ​​2001:fc0:: / 32; when the domain and type indicator field values ​​are 1, the associated common prefix is ​​2001:fe0:: / 32; when the domain and type indicator field values ​​are 2, the associated common prefix is ​​2002:fc0:: / 32; and when the domain and type indicator field values ​​are 3, the associated common prefix is ​​2002:fe0:: / 32. It should be noted that... Figure 7 The values ​​shown are for illustrative purposes only; the actual values ​​should be determined based on specific needs.

[0148] If all the common prefixes are dynamically planned, the field and type indicator field and their associated common prefixes can be dynamically carried in the header of the received message.

[0149] In some possible implementations, the type indicator identifier and its associated public prefix may be carried in the optional Type Length Value (TLV) of the routing extension header of the received message.

[0150] Specifically, a common prefix space TLV can be created, see [link to documentation]. Figure 8 This is a schematic diagram illustrating an exemplary embodiment of this application, showing a format in which a type indicator and its associated common prefix are dynamically carried in the header of a received message. Figure 8 As shown, the common prefix TLV includes a Type field, a Length field, a Count field, and a Common Prefix Space Sub-TLV table. The Count field records the number of different common prefixes carried in the common prefix TLV, i.e., the number of common prefix Sub-TLVs. The common prefix Sub-TLV table lists the type indicator and its associated common prefix in sequence.

[0151] See Figure 9 ,for Figure 8 The diagram illustrates the format of the common prefix information. (See attached diagram.) Figure 9 As shown, the PrefixSpace Sub-TLV includes a Domain and Type Indicator (DTI) field, a Length field, a Reserved Value (RSV) field, and a common prefix associated with the Domain and Type Indicator field. The DTI field corresponds to the DTI fields included in the SID list encapsulated by this SRH. The number of possible DTI values ​​is less than the number of SIDs in the SID list, depending on the planning of the common prefix and the actual path orchestration.

[0152] If a public prefix includes both a pre-planned public prefix and a dynamically planned public prefix, for the pre-planned public prefix, the type indicator and its associated public prefix are pre-stored; for the dynamically planned public prefix, the type indicator and its associated public prefix are dynamically carried in the header of the received message.

[0153] For example, if the common prefix of a spatial segment is pre-planned and the common prefix of a ground segment is dynamically planned, then for all segment identifiers related to a spatial segment, the type indicator identifier and its associated common prefix (e.g., ...) can be pre-stored. Figure 7The pre-stored association table shown in the image is used to query all ground segment-related segment identifiers. The type indicator identifier and its associated public prefix (e.g., ...) are dynamically carried in the header of the received message. Figure 8 The query Prefix Space TLV shown in the figure. In this case, the Prefix Space TLV encapsulated in the SRH only needs to carry the dynamically planned public prefix and its associated type indicator contained in the SID list encapsulated in the SRH, without carrying the pre-planned public prefix and its associated type indicator, further reducing the number of Prefix Space Sub-TLVs carried in the SRH.

[0154] See Figure 10 This is a schematic diagram illustrating the association between a construction type indicator and a common prefix, as shown in an exemplary embodiment of this application. In this example, the common prefix for spatial segments is pre-planned, while the common prefix for ground segments is dynamically planned. Figure 10 As shown, the SID list contains 8 compressed segment identifiers. Among them, the compressed segment identifiers of 3 space segment forwarding services share a common prefix. According to the DTI value 0, querying the pre-stored association table, the associated common prefix is ​​2001:fc0:: / 32. The compressed segment identifier of 1 space segment computing power service, according to the DTI value 1, querying the pre-stored association table, the associated prefix space is 2001:fe0:: / 32. The compressed segment identifiers of 3 ground segment forwarding services share a common prefix space. According to the DTI value 2, querying the prefix space TLV, the associated prefix space is 2002:fc0:: / 32. The compressed segment identifier of 1 ground segment computing power service, according to the DTI value 3, querying the prefix space TLV, the associated prefix space is 2002:fe0:: / 32.

[0155] Thus, compared to existing technologies, the NEXT-CSID Flavor compression scheme proposed in IETF RFC 9800 "Compressed SRv6 Segment List Encoding," while supporting the coexistence of multiple Locator-Blocks (i.e., common prefixes), has certain limitations: it requires that the CSID container must carry a Locator-Block, and all CSIDs in the container must share this common prefix; that is, CSIDs with the same common prefix must be included in the same container. However, in heterogeneous scenarios spanning network and computing domains, traffic paths may exhibit an alternating pattern of "network domain → computing domain → network domain → next computing domain." In this case, the SID list will show a structure where the same common prefix (such as the network domain prefix) is separated by other common prefixes (such as the computing domain prefix). However, existing technologies are not well-suited for such scenarios: because CSIDs with the same common prefix are blocked by other intermediate prefixes, a new CSID container must be opened to carry subsequent CSIDs with the same prefix, resulting in a decrease in compression efficiency.

[0156] This embodiment designs a segment identifier structure, adds a type indicator identifier and establishes its association with the common prefix. In heterogeneous scenarios across network domains and computing power domains, it can not only support multiple common prefixes, but also does not restrict their order of appearance, and does not require occupying segment identifier list space.

[0157] In some possible implementations, performing the corresponding service based on the segment identifier assigned to the current routing node includes:

[0158] Based on the segment identifier assigned to the current routing node, determine the position of the current routing node in the message transmission path and the corresponding service type;

[0159] Based on the current location of the routing node in the message transmission path and the corresponding service type, the corresponding service is executed.

[0160] In the above steps, the corresponding service can be executed based on the position of the current routing node in the message transmission path, determined by the segment identifier assigned to the current routing node, and the corresponding service type.

[0161] In this way, by determining the location and service type of the routing node in the message transmission path based on the allocated segment identifier, and executing the corresponding service accordingly, each routing node can accurately know its role and responsibility in the message transmission path, thereby executing computing power services or forwarding services more efficiently, improving the operating efficiency and reliability of the entire message transmission system, and realizing fine management and control of the message transmission process to ensure that messages can be transmitted accurately and efficiently.

[0162] In some possible implementations, the step of executing the corresponding service based on the current position of the routing node in the packet transmission path and the corresponding service type includes:

[0163] If the current routing node is not the last node in the message transmission path, update the target destination address of the message transmission, and execute the corresponding service according to the updated target destination address and the corresponding service type. The target destination address is the address of the next routing node.

[0164] If the current routing node is the last node in the message transmission path, the corresponding service is executed locally according to the corresponding service type.

[0165] Here, if the current routing node is not the last node in the packet transmission path, since the address of the next routing node changes with each hop, the destination address of the packet transmission is updated, and the corresponding service is executed according to the updated destination address and the corresponding service type. If the current routing node is the last node in the packet transmission path, the corresponding service is executed locally according to the corresponding service type.

[0166] In this way, by distinguishing whether the current routing node is the last node in the message transmission path, flexible control over the message transmission and service execution process can be achieved. When the routing node is not the last node, the target destination address of the message transmission is updated and the service is executed according to the updated address to ensure that the message can continue to be transmitted along the correct path. When the routing node is the last node, the corresponding service is executed directly on the local machine to ensure the final processing and delivery of the message. This helps to improve the accuracy and efficiency of message transmission, enhances the adaptability to complex transmission paths, and ensures the stability and reliability of the entire message transmission process.

[0167] In some possible implementations, the target destination address of the update message transmission includes:

[0168] Extract the segment identifier corresponding to the next routing node from the segment identifiers of each routing node in the packet transmission path encapsulated in the routing extension header of the packet, and use the segment identifier corresponding to the next routing node as the updated target destination address.

[0169] In this step, if the routing extension header of the message encapsulates the complete segment identifiers of each routing node in the message transmission path, the segment identifier corresponding to the next routing node can be directly extracted from the segment identifiers of each routing node in the message transmission path encapsulated in the routing extension header of the message. Since the segment identifier corresponding to the next routing node is also complete, the segment identifier corresponding to the next routing node can be used as the updated target destination address.

[0170] In this way, by extracting the segment identifier of the next routing node from the routing extension header of the message as the updated destination address, dynamic updates and flexible switching of the destination address can be achieved. Directly using the complete segment identifier as the destination address helps to reduce processing complexity and thus improve the efficiency of message transmission.

[0171] In some possible implementations, the target destination address of the update message transmission includes:

[0172] If the routing extension header of the message encapsulates a compressed segment identifier, extract the compressed segment identifier and type indicator corresponding to the next routing node from the compressed segment identifiers of each routing node in the message transmission path encapsulated in the routing extension header of the message.

[0173] Based on the type indicator corresponding to the next routing node and the pre-built association between the type indicator and the common prefix, the common prefix corresponding to the next routing node is obtained;

[0174] Based on the compressed segment identifier corresponding to the next routing node and the common prefix, the updated target destination address is determined.

[0175] Here, if the routing extension header of the message contains a compressed segment identifier, segment identifier recovery and destination address filling are required.

[0176] See Figure 11 This is a schematic diagram illustrating an exemplary embodiment of this application for updating a target destination address. Figure 11As shown, taking dynamic programming with a common prefix as an example, the compressed segment identifier corresponding to the next routing node can be extracted from the compressed segment identifiers of each routing node in the packet transmission path encapsulated in the routing extension header of the packet. The position of the Compressed Segment Identifier (C-SID) field can be determined from the compressed segment identifier corresponding to the next routing node, and the position of the Domain and Type Indicator (DTI) field can be determined based on the position of the C-SID field, thereby extracting the Domain and Type Indicator field corresponding to the next routing node. Optionally, by combining the Segments Left (SL) field and the Segment Identifier Index (SID Index, SI), the specific location of the C-SID field can be located from the compressed segment identifier corresponding to the next routing node. The DTI field is immediately before the C-SID field; the DTI field information, i.e., the type indicator, can be obtained based on the position of the C-SID field of the next routing node.

[0177] Then, based on the domain and type indicator fields corresponding to the next routing node and the pre-built association between the domain and type indicator fields and the public prefix, the public prefix corresponding to the next routing node is obtained. Specifically, for pre-planned public prefixes, the public prefix corresponding to the next routing node can be found from the pre-stored domain and type indicator fields and their associated public prefixes; for dynamically planned public prefixes, the public prefix corresponding to the next routing node can be found from the domain and type indicator fields dynamically carried in the packet header and their associated public prefixes.

[0178] Next, based on the compressed segment identifier (including the domain and type indicator fields and the compressed segment identifier field) corresponding to the next routing node and the common prefix, the updated target destination address is formed by concatenation.

[0179] Here, combined Figure 11 As can be seen, if the total number of bits in the common prefix, field and type indicator field, compressed segment identifier field and segment identifier index is less than 128 bits, padding fields can be used to fill the gaps, for example, by using 0 to fill the gaps, so that the total number of bits in each field is 128 bits.

[0180] In this way, by using the type indicator corresponding to the next routing node and the pre-built association between the type indicator and the common prefix, the common prefix corresponding to the next routing node is obtained. The target destination address is determined by using the compressed segment identifier and the common prefix, which ensures the accuracy and reliability of the target destination address update and improves the stability of message transmission.

[0181] The message transmission method provided in this disclosure, by planning common prefixes for the network domain and computing power domain corresponding to the ground segment and space segment respectively, can effectively adapt to the limited bandwidth resources between satellites and between satellite and ground, avoiding the impact of unstable bandwidth on message transmission. At the same time, by obtaining the message transmission path, it can flexibly respond to dynamic topology changes between satellites and between satellite and ground, improving the transmission efficiency of message payload. Furthermore, by assigning segment identifiers to each routing node on each message transmission path according to the common prefix, during message transmission, it can sequentially jump to each routing node to perform the corresponding service according to the planned path, without the need for additional announcement information between routing nodes, thereby significantly reducing the announcement overhead caused by limited bandwidth between satellites and between satellite and ground and dynamic topology changes. While ensuring network path forwarding, it meets the requirements for coordinated scheduling of computing power resources and network resources, and can be compatible with different types of routing nodes, effectively realizing integrated satellite-ground routing message transmission, which helps to improve the efficiency and reliability of integrated computing and network message transmission between satellites / between satellites and ground.

[0182] For a clearer illustration of the message transmission process, see [link to relevant documentation]. Figure 12 This is a schematic diagram illustrating an integrated satellite-to-ground message transmission process, as shown in an exemplary embodiment of this application. Figure 12 As shown, a computing power requesting node (which could be an operational satellite, such as a remote sensing satellite, meteorological satellite, or Earth observation satellite) sends a computing power request message to an onboard SRv6 computing power routing node (which could be a computing satellite equipped with an onboard router supporting SRv6 computing power routing). Here, the operational satellite and the computing satellite are directly connected via laser or microwave; or connected via a space-based access network; or the operational payload and the onboard router are both mounted on the same satellite and connected via fiber optic cable or cable.

[0183] The on-board SRv6 computing power routing node selects on-board and ground-based computing power service nodes that conform to the computing power routing and network routing policies as source nodes based on the computing power service identifier carried in the computing power request message. It encapsulates the segment identifiers of each routing node in the message transmission path in the routing extension header of the received message and sends it to the on-board computing power service node through the space-based bearer network.

[0184] An onboard computing service node can be a computing satellite or a space computing center, equipped with an onboard computer / server and an onboard router. The onboard computer / server deploys computing service instance A, which can provide some of the computing services required by the requesting node, such as feature extraction. The onboard router then re-encapsulates the routing extension header of the received packet and sends the packet to the ground station gateway via the satellite-to-ground link. If there is no direct satellite-to-ground link, the shortest path can be selected to forward the packet to the ground station gateway via a satellite in the same or different orbits, and then via the ground bearer network to the ground SRv6 computing routing node.

[0185] The ground-based SRv6 computing power routing node forwards the packet to the ground-based computing power service node. The ground-based computing power service node deploys computing power service instance B, which can provide the remaining computing power services required by the requesting node.

[0186] Controllers (such as ground control centers, space-ground computing network management centers, or onboard controllers) can plan common prefixes for the network domains and computing power domains corresponding to the ground and space segments, respectively. Onboard SRv6 computing power routing nodes and onboard computing power service nodes can be on the same track or on different tracks. Onboard nodes and ground nodes establish neighbor relationships through IGP / BGP extended protocols to allocate and distribute forwarding path SIDs and computing power service SIDs.

[0187] Corresponding to the embodiments of the aforementioned message transmission method, this application also provides embodiments of a message transmission apparatus.

[0188] Please see Figure 13 This is a schematic diagram illustrating a message transmission device according to an exemplary embodiment of this application, wherein the message transmission device is applied to a controller. Figure 13 As shown in the illustration, the message transmission apparatus 1300 provided in this application embodiment includes:

[0189] The data acquisition module 1301 is used to acquire the message transmission path and the common prefixes planned for the network domain and computing power domain corresponding to the ground segment and space segment, respectively. The message transmission path includes various routing nodes through which the message passes. Each routing node includes ground-based computing power routing nodes and non-computing power routing nodes, as well as satellite-based computing power routing nodes and non-computing power routing nodes. The computing power routing nodes provide computing power services, and the non-computing power routing nodes provide forwarding services. The common prefix is ​​used to locate the transmission position of the message. The network domain is a set of multiple network devices, and the computing power domain is a set of multiple computing devices.

[0190] The identifier allocation module 1302 is used to allocate a segment identifier to each routing node according to the common prefix, and notify the other routing nodes in the message transmission path of the segment identifier allocated to the routing node; wherein, the segment identifier includes a type indicator identifier, which is used to indicate the segment type and service type to which the corresponding routing node belongs, the segment type includes a ground segment or a space segment, and the service type includes a computing power service or a forwarding service.

[0191] In some possible implementations, the data acquisition module 1301 plans the common prefix through the following steps:

[0192] Pre-plan the common prefixes for the network domain and computing power domain corresponding to the ground segment and space segment, respectively;

[0193] Alternatively, dynamically program the common prefixes of the network domain and computing power domain corresponding to the ground segment and the space segment, respectively;

[0194] Alternatively, a portion of the common prefixes of the network domain and computing power domain corresponding to the ground segment and space segment can be pre-planned, and the other portion can be dynamically planned.

[0195] In some possible implementations, the data acquisition module 1301 acquires the message transmission path through the following steps:

[0196] Obtain the destination address of the message, and calculate the message transmission path to the destination address based on the destination address of the message. The destination address is the address of the computing device or network device determined according to the computing power service and forwarding service requirements of the message.

[0197] Please see Figure 14 This is a schematic diagram illustrating another message transmission device according to an exemplary embodiment of this application, wherein the message transmission device is applied to a routing node. Figure 14 As shown in the illustration, the message transmission apparatus 1400 provided in this application embodiment includes:

[0198] The identifier receiving module 1401 is used to receive the message transmission path issued by the controller, and to receive the segment identifier assigned by the controller to the current routing node, and the segment identifier assigned by the controller to each other routing node on the message transmission path. The segment identifier is assigned by the controller based on the common prefix planned for the network domain and computing power domain corresponding to the ground segment and space segment, respectively. The common prefix is ​​used to locate the transmission position of the message. The network domain is a set of multiple network devices, and the computing power domain is a set of multiple computing devices. The routing nodes in the message transmission path include ground computing power routing nodes and non-computing power routing nodes, as well as satellite computing power routing nodes and non-computing power routing nodes. The computing power routing nodes are used to provide computing power services, and the non-computing power routing nodes are used to provide forwarding services. The segment identifier includes a type indicator identifier, which is used to indicate the segment type and service type to which the corresponding routing node belongs. The segment type includes a ground segment or a space segment, and the service type includes computing power services or forwarding services.

[0199] The service execution module 1402 is configured to, upon receiving any message, encapsulate the segment identifiers of each routing node in the message transmission path corresponding to the message in the routing extension header of the message, and execute the corresponding service according to the segment identifier assigned to the current routing node.

[0200] In some possible implementations, the service execution module 1402, when encapsulating the segment identifier of each routing node in the packet transmission path corresponding to the packet in the routing extension header of any packet, specifically uses the following methods:

[0201] The segment identifier of each routing node in the message transmission path corresponding to any message is compressed to obtain the compressed segment identifier.

[0202] The compressed segment identifier is encapsulated in the routing extension header of any of the packets;

[0203] The service execution module 1402 is also used for:

[0204] Based on the planning method of the public prefix, construct the association between the type indicator and the public prefix.

[0205] In some possible implementations, when the service execution module 1402 compresses the segment identifier of each routing node in the packet transmission path corresponding to any packet to obtain a compressed segment identifier, it specifically performs the following:

[0206] For each segment identifier of the routing node in the message transmission path corresponding to any message, the type indicator identifier and other data required for compression are extracted from the segment identifier to generate a compressed segment identifier.

[0207] In some possible implementations, when the service execution module 1402 constructs the association between the type indicator and the public prefix according to the planning method of the public prefix, it is specifically used for:

[0208] If the public prefix is ​​pre-planned, the type indicator identifier and its associated public prefix are pre-stored;

[0209] When the common prefix is ​​dynamically planned, the type indicator and its associated common prefix are dynamically carried in the header of the received message.

[0210] In some possible implementations, when the service execution module 1402 is used to execute the corresponding service based on the segment identifier assigned to the current routing node, it is specifically used for:

[0211] Based on the segment identifier assigned to the current routing node, determine the position of the current routing node in the message transmission path and the corresponding service type;

[0212] Based on the current location of the routing node in the message transmission path and the corresponding service type, the corresponding service is executed.

[0213] In some possible implementations, when the service execution module 1402 executes a corresponding service based on the current position of the routing node in the packet transmission path and the corresponding service type, it is specifically used for:

[0214] If the current routing node is not the last node in the message transmission path, update the target destination address of the message transmission, and execute the corresponding service according to the updated target destination address and the corresponding service type. The target destination address is the address of the next routing node.

[0215] If the current routing node is the last node in the message transmission path, the corresponding service is executed locally according to the corresponding service type.

[0216] In some possible implementations, the service execution module 1402, when updating the target destination address for message transmission, specifically performs the following:

[0217] Extract the segment identifier corresponding to the next routing node from the segment identifiers of each routing node in the packet transmission path encapsulated in the routing extension header of the packet, and use the segment identifier corresponding to the next routing node as the updated target destination address.

[0218] In some possible implementations, the service execution module 1402, when updating the target destination address for message transmission, specifically performs the following:

[0219] If the routing extension header of the message encapsulates a compressed segment identifier, extract the compressed segment identifier and type indicator corresponding to the next routing node from the compressed segment identifiers of each routing node in the message transmission path encapsulated in the routing extension header of the message.

[0220] Based on the type indicator corresponding to the next routing node and the pre-built association between the type indicator and the common prefix, the common prefix corresponding to the next routing node is obtained;

[0221] Based on the compressed segment identifier corresponding to the next routing node and the common prefix, the updated target destination address is determined.

[0222] The specific implementation process of the functions and roles of each unit in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0223] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this application according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0224] Based on the same technical concept, this application also provides a computer device 1500, referring to... Figure 15 The diagram shown is a schematic representation of the structure of a computer device according to an exemplary embodiment of this application, comprising:

[0225] The processor 1510, memory 1520, and bus 1530 are included. The memory 1520 is used to store execution instructions and includes main memory 1521 and external memory 1522. The main memory 1521, also known as internal memory, is used to temporarily store the operation data in the processor 1510 and the data exchanged with external memory 1522 such as hard disk. The processor 1510 exchanges data with external memory 1522 through main memory 1521.

[0226] In this embodiment, the memory 1520 is specifically used to store application code that executes the scheme of this application, and its execution is controlled by the processor 1510. That is, when the electronic device 1500 is running, the processor 1510 communicates with the memory 1520 through the bus 1530, or the processor 1510 communicates with the memory 1520 through other means, so that the processor 1510 executes the application code stored in the memory 1520, and then executes the steps of the message transmission method described in any of the foregoing embodiments.

[0227] The memory 1520 may be, but is not limited to, random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), etc.

[0228] Processor 1510 may be an integrated circuit chip with signal processing capabilities. The aforementioned processor can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this invention. The general-purpose processor can be a microprocessor or any conventional processor.

[0229] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 1500. In other embodiments of this application, the electronic device 1500 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0230] This disclosure also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the message transmission method described in the above-described method embodiments. The storage medium may be a volatile or non-volatile computer-readable storage medium.

[0231] This disclosure also provides a computer program product, which stores a computer program. When the computer program is run by a processor, it executes the steps of the message transmission method provided in any of the above embodiments of this disclosure. For details, please refer to the above method embodiments, which will not be repeated here.

[0232] The aforementioned computer program product can be implemented through hardware, software, or a combination thereof. In one optional embodiment, the computer program product is specifically embodied in a computer storage medium, which can be a volatile or non-volatile computer-readable storage medium. In another optional embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.

[0233] Furthermore, embodiments of the subject matter and functional operation described in this specification can be implemented in the following ways: digital electronic circuits, tangibly embodied computer software or firmware, computer hardware including the structures disclosed in this specification and their structural equivalents, or combinations thereof. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a tangible, non-transitory program carrier for execution by a data processing apparatus or for controlling the operation of a data processing apparatus. Alternatively or additionally, program instructions may be encoded on artificially generated propagation signals, such as machine-generated electrical, optical, or electromagnetic signals, which are generated to encode information and transmit it to a suitable receiving device for execution by the data processing apparatus. The computer storage medium may be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or combinations thereof.

[0234] The processing and logic flow described in this specification can be executed by one or more programmable computers that execute one or more computer programs to perform corresponding functions by operating on input data and generating output. The processing and logic flow can also be executed by dedicated logic circuitry—such as FPGAs (Field-Programmable Gate Arrays) or ASICs (Application-Specific Integrated Circuits), and the device can also be implemented as dedicated logic circuitry.

[0235] Suitable computers for executing computer programs include, for example, general-purpose and / or special-purpose microprocessors, or any other type of central processing unit. Typically, the central processing unit receives instructions and data from read-only memory and / or random access memory. The basic components of a computer include a central processing unit for implementing or executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include one or more mass storage devices for storing data, such as disks, magneto-optical disks, or optical disks, or the computer will be operatively coupled to such mass storage devices to receive data from or transfer data to them, or both. However, a computer is not required to have such devices. Furthermore, a computer can be embedded in another device, such as a mobile phone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a global positioning system (GPS) receiver, or a portable storage device such as a universal serial bus (USB) flash drive, to name a few.

[0236] Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, such as semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices), magnetic disks (e.g., internal hard disks or removable disks), magneto-optical disks, and CD-ROM and DVD-ROM disks. Processors and memory may be supplemented by or incorporated into dedicated logic circuitry.

[0237] While this specification contains numerous specific implementation details, these should not be construed as limiting the scope of any invention or the scope of the claims, but rather are primarily intended to describe features of specific embodiments of a particular invention. Certain features described in the various embodiments herein may also be implemented in combination in a single embodiment. Conversely, various features described in a single embodiment may also be implemented separately in various embodiments or in any suitable sub-combination. Furthermore, while features may function in certain combinations as described above and even initially claimed in this way, one or more features from a claimed combination may be removed from that combination in some cases, and a claimed combination may refer to a sub-combination or a variation thereof.

[0238] Similarly, although the operations are depicted in a specific order in the accompanying drawings, this should not be construed as requiring these operations to be performed in the specific order shown or sequentially, or requiring all illustrated operations to be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Furthermore, the separation of various system modules and components in the above embodiments should not be construed as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

[0239] Thus, specific embodiments of the subject matter have been described. Other embodiments are within the scope of the appended claims. In some cases, the actions recited in the claims may be performed in a different order and still achieve the desired result. Furthermore, the processes depicted in the drawings are not necessarily shown in a specific order or sequence to achieve the desired result. In some implementations, multitasking and parallel processing may be advantageous.

[0240] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A message transmission method, characterized in that, Applied to a controller, the method includes: Obtain the message transmission path and the common prefixes planned for the network domain and computing domain corresponding to the ground segment and space segment, respectively. The message transmission path includes various routing nodes through which the message transmission passes. Each routing node includes ground-based computing power routing nodes and non-computing power routing nodes, as well as satellite-based computing power routing nodes and non-computing power routing nodes. The computing power routing nodes are used to provide computing power services, and the non-computing power routing nodes are used to provide forwarding services. The common prefix is ​​used to locate the transmission position of the message; the network domain is a set of multiple network devices; and the computing power domain is a set of multiple computing devices. For each of the aforementioned routing nodes, Assign segment identifiers to the routing nodes according to the public prefix, and The segment identifier assigned to the routing node is notified to all other routing nodes in the message transmission path; The segment identifier includes a type indicator, which indicates the segment type and service type to which the corresponding routing node belongs. The segment type includes a ground segment or a space segment, and the service type includes computing power service or forwarding service.

2. The method according to claim 1, characterized in that, The public prefix is ​​planned using the following steps: Pre-plan the common prefixes for the network domain and computing power domain corresponding to the ground segment and space segment, respectively; Alternatively, dynamically program the common prefixes of the network domain and computing power domain corresponding to the ground segment and the space segment, respectively; Alternatively, a portion of the common prefixes of the network domain and computing power domain corresponding to the ground segment and space segment can be pre-planned, and the other portion can be dynamically planned.

3. The method according to claim 1, characterized in that, The message transmission path is obtained through the following steps: Obtain the destination address of the message, and calculate the message transmission path to the destination address based on the destination address of the message. The destination address is the address of the computing device or network device determined according to the computing power service and forwarding service requirements of the message.

4. A message transmission method, characterized in that, Applied to routing nodes, the method includes: The receiver receives the message transmission path issued by the controller, the segment identifier assigned by the controller to the current routing node, and the segment identifiers assigned by the controller to other routing nodes on the message transmission path. The segment identifier is assigned by the controller based on a common prefix planned for the network domain and computing power domain corresponding to the ground segment and space segment, respectively. The common prefix is ​​used to locate the transmission position of the message. The network domain is a set of multiple network devices, and the computing power domain is a set of multiple computing devices. The routing nodes in the message transmission path include ground-based computing power routing nodes and non-computing power routing nodes, as well as satellite-based computing power routing nodes and non-computing power routing nodes. The computing power routing nodes provide computing power services, and the non-computing power routing nodes provide forwarding services. The segment identifier includes a type indicator, which indicates the segment type and service type to which the corresponding routing node belongs. The segment type includes a ground segment or a space segment, and the service type includes computing power services or forwarding services. Upon receiving any message, the segment identifiers of each routing node in the message transmission path corresponding to the message are encapsulated in the routing extension header of the message, and the corresponding service is executed according to the segment identifier assigned to the current routing node.

5. The method according to claim 4, characterized in that, The step of encapsulating the segment identifier of each routing node in the packet transmission path corresponding to the packet in the routing extension header of any packet includes: The segment identifier of each routing node in the message transmission path corresponding to any message is compressed to obtain the compressed segment identifier. The compressed segment identifier is encapsulated in the routing extension header of any of the packets; The method further includes: Based on the planning method of the public prefix, construct the association between the type indicator and the public prefix.

6. The method according to claim 5, characterized in that, The step of compressing the segment identifier of each routing node in the message transmission path corresponding to any message to obtain the compressed segment identifier includes: For each segment identifier of the routing node in the message transmission path corresponding to any message, the type indicator identifier and other data required for compression are extracted from the segment identifier to generate a compressed segment identifier.

7. The method according to claim 5, characterized in that, The step of constructing the association between the type indicator and the public prefix according to the planning method of the public prefix includes: If the public prefix is ​​pre-planned, the type indicator identifier and its associated public prefix are pre-stored; When the common prefix is ​​dynamically planned, the type indicator and its associated common prefix are dynamically carried in the header of the received message.

8. The method according to claim 4, characterized in that, The step of executing the corresponding service based on the segment identifier assigned to the current routing node includes: Based on the segment identifier assigned to the current routing node, determine the position of the current routing node in the message transmission path and the corresponding service type; Based on the current location of the routing node in the message transmission path and the corresponding service type, the corresponding service is executed.

9. The method according to claim 8, characterized in that, The step of executing the corresponding service based on the current position of the routing node in the message transmission path and the corresponding service type includes: If the current routing node is not the last node in the message transmission path, update the target destination address of the message transmission, and execute the corresponding service according to the updated target destination address and the corresponding service type. The target destination address is the address of the next routing node. If the current routing node is the last node in the message transmission path, the corresponding service is executed locally according to the corresponding service type.

10. The method according to claim 9, characterized in that, The target destination address of the update message transmission includes: Extract the segment identifier corresponding to the next routing node from the segment identifiers of each routing node in the packet transmission path encapsulated in the routing extension header of the packet, and use the segment identifier corresponding to the next routing node as the updated target destination address.

11. The method according to claim 9, characterized in that, The target destination address of the update message transmission includes: If the routing extension header of the message encapsulates a compressed segment identifier, extract the compressed segment identifier and type indicator corresponding to the next routing node from the compressed segment identifiers of each routing node in the message transmission path encapsulated in the routing extension header of the message. Based on the type indicator corresponding to the next routing node and the pre-built association between the type indicator and the common prefix, the common prefix corresponding to the next routing node is obtained; Based on the compressed segment identifier corresponding to the next routing node and the common prefix, the updated target destination address is determined.

12. A message transmission device, characterized in that, Applied to a controller, the device includes: The data acquisition module is used to acquire the message transmission path and the common prefixes planned for the network domain and computing power domain corresponding to the ground segment and space segment, respectively. The message transmission path includes various routing nodes through which the message passes. Each routing node includes ground-based computing power routing nodes and non-computing power routing nodes, as well as satellite-based computing power routing nodes and non-computing power routing nodes. The computing power routing nodes provide computing power services, and the non-computing power routing nodes provide forwarding services. The common prefix is ​​used to locate the transmission position of the message. The network domain is a set of multiple network devices, and the computing power domain is a set of multiple computing devices. The identifier allocation module is used to allocate a segment identifier to each routing node according to the common prefix, and notify the other routing nodes in the message transmission path of the segment identifier allocated to the routing node; wherein, the segment identifier includes a type indicator identifier, which is used to indicate the segment type and service type to which the corresponding routing node belongs, the segment type includes a ground segment or a space segment, and the service type includes computing power service or forwarding service.

13. A message transmission device, characterized in that, Applied to a routing node, the device includes: The identification receiving module is used to receive the message transmission path issued by the controller, and to receive the segment identifier assigned by the controller to the current routing node, as well as the segment identifiers assigned by the controller to other routing nodes on the message transmission path. The segment identifier is assigned by the controller based on a common prefix planned for the network domain and computing power domain corresponding to the ground segment and space segment, respectively. The common prefix is ​​used to locate the transmission position of the message. The network domain is a set of multiple network devices, and the computing power domain is a set of multiple computing devices. The routing nodes in the message transmission path include ground-based computing power routing nodes and non-computing power routing nodes, as well as satellite-based computing power routing nodes and non-computing power routing nodes. The computing power routing nodes provide computing power services, and the non-computing power routing nodes provide forwarding services. The segment identifier includes a type indicator identifier, which indicates the segment type and service type to which the corresponding routing node belongs. The segment type includes a ground segment or a space segment, and the service type includes computing power services or forwarding services. The service execution module is used to, upon receiving any message, encapsulate the segment identifiers of each routing node in the message transmission path corresponding to the message in the routing extension header of the message, and execute the corresponding service according to the segment identifier assigned to the current routing node.

14. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the message transmission method according to any one of claims 1 to 3, or the steps of the message transmission method according to any one of claims 4 to 11.

15. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the steps of the message transmission method according to any one of claims 1 to 3, or the steps of the message transmission method according to any one of claims 4 to 11.

Images