Cooperative switching method for onboard routing-UPF fusion equipment for low-Earth orbit satellite networks
By acquiring the current session and topology information of the low-Earth orbit satellite network, candidate cooperative objects are identified and the joint effective window is calculated to generate a cooperative rule group. This solves the problem of inconsistency between routing rules and UPF session rules in the low-Earth orbit satellite network, achieves efficient cooperative handover, and reduces packet dropping and interruption time.
Patent Information
- Application Number
- CN202611370611.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-04
- Publication Date
- 2026-11-17
AI Technical Summary
In low-Earth orbit satellite networks, the timing of the activation of inter-satellite routing rules and UPF session rules is inconsistent, which leads to packet loss because the target UPF is not ready while the route has been switched.
By acquiring the current session information, satellite topology information, and resource status information of the source fusion device, multiple candidate collaboration objects are identified, and the joint effective window of each candidate collaboration object is calculated. The target collaboration object is selected to generate a collaboration rule group, the collaboration rule group is pre-set to the target fusion device, and the current session information is synchronized to ensure the consistency between the routing rules and the UPF rules.
This solution addresses the issue of inconsistent timing of inter-satellite routing rules and UPF session rules taking effect during session handover, reducing packet loss, improving handover success rate, and shortening downtime.
Smart Images

Figure CN123122633A_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of mobile communication technology, and in particular relates to a collaborative handover method for a satellite-borne routing-UPF fusion device for low-Earth orbit satellite networks. Background Technology
[0002] With the rapid development of low-Earth orbit (LEO) satellite constellations and the evolution of 5G non-terrestrial network technologies, integrating satellite communication with terrestrial 5G core networks has become a crucial technological path to achieving seamless global coverage. The high-speed movement of LEO satellites leads to continuous changes in access satellites, inter-satellite links, ground gateways, and onboard computing resources. In satellite networks carrying user data from 5G, 5G-A, or subsequent mobile communication systems, the forwarding of a PDU session involves inter-satellite routing rules and UPF session rules. Currently, existing networks typically update topology routes via the controller, and then the core network control plane or UPF control module establishes, modifies, or releases UPF session rules. The calculation, distribution, state synchronization, and effective timing of these two types of rules are independent of each other. In scenarios where low-Earth orbit satellite environments are constantly changing, issues arise such as: new inter-satellite routes have already redirected to the target node, but the target UPF has not yet completed the rule installation or state recovery for the target session, resulting in packet loss or session interruption; the target UPF has pre-configured session rules, but the planned inter-satellite path fails prematurely due to orbital motion or link obstruction, making the target UPF unreachable; during the overlap of old and new paths, the original routing rules and the new UPF rules process the same service flow with inconsistent combinations, resulting in duplication, out-of-order delivery, or billing state breaks. Therefore, there is an urgent need for a collaborative handover method that can manage inter-satellite routing rules and UPF session rules as associated objects in a unified manner, to solve the problems of inconsistent activation timing of inter-satellite routing rules and UPF session rules during session handover, and packet loss caused by the target UPF not being ready before the route has been switched. Summary of the Invention
[0003] This application provides a collaborative handover method for onboard routing-UPF fusion devices in low-Earth orbit satellite networks. It aims to address the problems in existing technologies where the timing of the activation of inter-satellite routing rules and UPF session rules is inconsistent during session handover, and packet loss occurs when the target UPF is not ready but the route has already been switched. By acquiring the current session information, satellite topology information, and resource status information of the source fusion device, multiple candidate collaborative objects are determined based on the satellite topology and resource status information. A joint effective window for each candidate collaborative object is calculated. A target collaborative object is selected based on the joint effective window, and a collaborative rule group is generated. The collaborative rule group is pre-set to the target fusion device, and the current session information is synchronized from the source fusion device to the target fusion device. This solves the problems in existing technologies where the timing of the activation of inter-satellite routing rules and UPF session rules is inconsistent during session handover, and packet loss occurs when the target UPF is not ready but the route has already been switched.
[0004] In a first aspect, embodiments of the present invention provide a collaborative switching method for onboard routing-UPF fusion equipment for low-Earth orbit satellite networks, the method comprising the following steps: Obtain the current session information, satellite topology information, and resource status information of the source fusion device; Based on the satellite topology information and the resource status information, multiple candidate collaborative objects are identified, and the joint effective window for each candidate collaborative object is calculated. Each candidate collaborative object corresponds to a candidate fusion device. Based on the joint effective window, a target collaborative object is selected from multiple candidate collaborative objects, and a collaborative rule group is generated based on the target collaborative object; The collaborative rule group is preset into the target fusion device corresponding to the target collaborative object, and the current session information is synchronized from the source fusion device to the target fusion device.
[0005] Optionally, based on the satellite topology information and the resource status information, multiple candidate cooperation objects are determined, including: Based on the satellite topology information, the inter-satellite paths from candidate access satellites to candidate exit nodes and the exit nodes are determined; Based on the resource status information, a target UPF capable of supporting the current session is determined; Based on the inter-satellite path, the exit node, and the target UPF, multiple candidate cooperative objects are identified.
[0006] Optionally, calculating the joint effective window for each of the candidate collaborative objects includes: Obtain the predicted available interval of the inter-satellite path, the resource satisfaction interval of the target UPF, the reachability interval of the exit node, and the control plane policy allowed interval in the candidate cooperative objects; Obtain the estimated time when the session state synchronization, routing rule installation, verification, and resource reservation of the candidate collaboration objects will be completed; Based on the predicted availability interval, the resource satisfaction interval, the reachability interval, the control plane policy allowable interval, and the expected time, the joint effective window of the candidate collaborative objects is calculated.
[0007] Optionally, selecting the target collaborative object from the plurality of candidate collaborative objects according to the joint effective window includes: Candidate collaborative objects whose joint effective window duration is less than a preset threshold are removed to obtain a set of selectable collaborative objects; Calculate the joint cost of each candidate collaborative object in the set of optional collaborative objects; The candidate collaborative object with the lowest joint generation value is selected as the target collaborative object.
[0008] Optionally, generating a set of collaboration rules based on the target collaboration object includes: Assign a corresponding collaboration version identifier to the target collaboration object; A routing rule set is generated based on the inter-satellite path of the target collaborative object, and a target UPF rule set is generated based on the target UPF of the target collaborative object; The routing rule set, the target UPF rule set, and the collaboration version identifier are associated to obtain a collaboration rule group.
[0009] Optionally, synchronizing the current session information from the source fusion device to the target fusion device includes: The basic session state of the current session state information is sent from the source fusion device to the target fusion device. The basic session state includes UPF rule key fields, tunnel mapping, billing count and last acknowledgment message checkpoint. The source fusion device sends the incremental session status to the target fusion device according to the log sequence number.
[0010] Optionally, after presetting the collaboration rule group to the target fusion device corresponding to the target collaboration object and synchronizing the current session information from the source fusion device to the target fusion device, the method further includes: Perform consistency verification on the pre-set collaborative rule group and the synchronized session state; After the verification is passed, the collaborative rule group is activated according to the preset activation time, and the data plane processing of the current session information is switched from the current collaborative rule group to the collaborative rule group corresponding to the collaborative version identifier. After confirming that the collaborative rule group is successfully carrying the service data of the current session, the status of the collaborative rule group is changed to retired, and the resources occupied by the old rule group are released; and, In the event of a switching anomaly or the failure of the collaborative rule group, the entire collaborative rule group will be rolled back to the collaborative rule group before the switch, or the entire group will be switched to a pre-verified backup collaborative rule group.
[0011] Secondly, embodiments of the present invention also provide a collaborative switching device for a satellite-borne routing-UPF fusion device for low-Earth orbit satellite networks, the collaborative switching device for the satellite-borne routing-UPF fusion device for low-Earth orbit satellite networks comprising: The acquisition module is used to acquire the current session information, satellite topology information, and resource status information of the source fusion device; The first processing module is used to determine multiple candidate collaborative objects based on the satellite topology information and the resource status information, and to calculate the joint effective window for each candidate collaborative object, with each candidate collaborative object corresponding to a candidate fusion device; The second processing module is used to select a target collaborative object from multiple candidate collaborative objects according to the joint effective window, and generate a collaborative rule group according to the target collaborative object; The synchronization module is used to pre-set the collaboration rule group to the target fusion device corresponding to the target collaboration object, and to synchronize the current session information from the source fusion device to the target fusion device.
[0012] Thirdly, embodiments of the present invention provide a collaborative switching system for onboard routing-UPF fusion devices for low-Earth orbit (LEO) satellite networks, comprising: a user terminal, multiple LEO satellites, at least one ground gateway, at least one data network exit, and multiple onboard routing-UPF fusion devices; the onboard routing-UPF fusion devices are deployed in the payloads of the LEO satellites and are used as local user plane processing nodes for access satellites, or as routing and UPF collaborative nodes for relay satellites; the system is used to execute the collaborative switching device for onboard routing-UPF fusion devices for LEO satellite networks provided in embodiments of the present invention.
[0013] Fourthly, embodiments of the present invention provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in the collaborative switching method for a satellite routing-UPF fusion device for low-Earth orbit satellite networks provided in the embodiments of the present invention.
[0014] In this embodiment of the invention, the current session information, satellite topology information, and resource status information of the source fusion device are obtained. Based on the satellite topology information and resource status information, multiple candidate collaboration objects are identified, and a joint effective window for each candidate collaboration object is calculated. Each candidate collaboration object corresponds to a candidate fusion device. According to the joint effective window, a target collaboration object is selected from the multiple candidate collaboration objects, and a collaboration rule group is generated based on the target collaboration object. The collaboration rule group is pre-set in the target fusion device corresponding to the target collaboration object, and the current session information is synchronized from the source fusion device to the target fusion device. This invention solves the problems in the prior art where the timing of the inter-satellite routing rules and UPF session rules taking effect is inconsistent during session switching, and packet loss occurs when the target UPF is not ready but the route has already been switched.
[0015] Other beneficial effects of this application will be described in detail in the following detailed description section. Attached Figure Description
[0016] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0017] Figure 1 This is a flowchart of a collaborative switching method for a spaceborne routing-UPF fusion device for low-Earth orbit satellite networks, provided by an embodiment of the present invention. Figure 2 This is a schematic diagram of the structure of a collaborative rule group provided in an embodiment of the present invention; Figure 3 This is a schematic diagram of the structure of a collaborative rule group state machine provided in an embodiment of the present invention; Figure 4 This is a schematic diagram of a local autonomous switching process when satellite-to-ground control is limited, provided by an embodiment of the present invention; Figure 5 This is a schematic diagram of the structure of a collaborative switching device for a satellite routing-UPF fusion equipment for low-Earth orbit satellite networks provided in an embodiment of the present invention; Figure 6 This is a schematic diagram of the structure of a collaborative switching system for a satellite routing-UPF fusion device for low-Earth orbit satellite networks provided in an embodiment of the present invention; Figure 7 This is a schematic diagram of the structure of a spaceborne routing-UPF fusion device provided in an embodiment of the present invention. Detailed Implementation
[0018] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.
[0019] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.
[0020] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.
[0021] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."
[0022] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.
[0023] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.
[0024] like Figure 1 As shown, Figure 1 This is a flowchart of a collaborative handover method for a spaceborne routing-UPF fusion device for low-Earth orbit satellite networks, provided by an embodiment of the present invention. The collaborative handover method includes the following steps: 101. Obtain the current session information, satellite topology information, and resource status information of the source fusion device.
[0025] In this embodiment of the invention, the collaborative switching method for onboard routing-UPF fusion devices for low-Earth orbit satellite networks can be applied to a satellite communication platform. The satellite communication platform can be built on a server-based or distributed architecture. This platform includes a data interface (for sensors or users to upload data), a knowledge database, and a knowledge database construction program. The data interface can be used to obtain current session information, satellite topology information, and resource status information from the source fusion device. The knowledge database construction program can be used to construct the knowledge database, which is specifically designed to provide additional association information for identified data entities, thereby improving the depth of the data recognition system's understanding of the content.
[0026] The aforementioned spaceborne routing-UPF fusion device can be a computing and forwarding device deployed in a satellite payload, realizing inter-satellite data forwarding and UPF processing, as well as the coordinated control of the two, within the same physical device or tightly coupled hardware unit. The spaceborne routing-UPF fusion device can be a single-board device, which can be composed of multiple high-speed interconnected boards, chips, or processing units.
[0027] The aforementioned source fusion device can be the on-board routing-UPF fusion device currently carrying PDU sessions. The source fusion device includes the currently active source UPF instance and the currently used inter-satellite routing rules.
[0028] The aforementioned current session information may be the data plane status related to the PDU session currently carried by the source fusion device, including PDU session identifier, QoS flow identifier, packet detection rules, forwarding action rules, QoS execution rules, tunnel endpoint mapping, billing count, token bucket status, and last acknowledgment checkpoint, etc.
[0029] The aforementioned satellite topology information can describe the location of satellite nodes, inter-satellite link connections, link status, and ground gateway reachability in a low-Earth orbit satellite network.
[0030] The aforementioned resource status information can be information on the available resources of the source fusion device, including CPU utilization, memory usage, number of sessions carried, cache level, and inter-satellite link latency, available bandwidth, and bit error rate.
[0031] 102. Based on satellite topology information and resource status information, multiple candidate collaborative objects are identified, and the joint effective window of each candidate collaborative object is calculated.
[0032] In this embodiment of the invention, each candidate collaborative object corresponds to a candidate fusion device.
[0033] The aforementioned candidate collaboration objects can be data plane migration candidate schemes generated for the PDU session to be handed over. Candidate collaboration objects include inter-satellite paths, target UPFs, and egress nodes. The aforementioned inter-satellite paths can be predicted available forwarding paths consisting of source access satellites, one or more relay satellites, feeder link satellites, or ground egress nodes. The aforementioned target UPF can be a UPF instance that, after the handover, newly carries the user plane rules of the current session. The aforementioned egress nodes can be ground gateways or ground station nodes.
[0034] The aforementioned candidate fusion device can be a spaceborne routing-UPF fusion device used to carry the target UPF among the candidate collaborative objects.
[0035] The aforementioned joint effective window can be the predicted time interval in which the inter-satellite paths, target UPF resources, and egress nodes of the candidate cooperating objects simultaneously meet the availability conditions, and the effective intersection after considering the preparation time required for state synchronization. The joint effective window indicates that within this time interval, all conditions of the candidate cooperating objects are simultaneously met, making it feasible to perform a switchover.
[0036] It should be noted that by identifying multiple candidate cooperating objects based on satellite topology information and resource status information, and calculating the joint effective window for each candidate cooperating object, the selection of target inter-satellite paths and target UPFs is constrained by the same time window conditions, thus avoiding message drop due to inconsistent path and UPF switching timing.
[0037] 103. Based on the joint effective window, select the target collaboration object from multiple candidate collaboration objects, and generate a collaboration rule group based on the target collaboration object.
[0038] In this embodiment of the invention, the target coordination object can be the final switching scheme selected from multiple candidate coordination objects according to the joint effective window. The target coordination object includes the selected inter-satellite path, the target UPF, and the egress node.
[0039] The aforementioned collaborative rule group can be a whole of associated and stored routing rules, target UPF rules, session states, activation conditions, and fallback conditions for the same PDU session, the same QoS flow, or the same service flow.
[0040] It should be noted that by selecting the target collaboration object from multiple candidate collaboration objects based on the joint effective window, and generating collaboration rule groups based on the target collaboration object, the routing rules and UPF rules are ensured to maintain a consistent association in all subsequent operations such as presetting, synchronization, activation, and rollback.
[0041] 104. Preset the collaboration rule group to the target fusion device corresponding to the target collaboration object, and synchronize the current session information from the source fusion device to the target fusion device.
[0042] In this embodiment of the invention, the above-mentioned preset may be to install the collaborative rules into the candidate table or preparation table of the target fusion device before switching activation, so that it is in an installed but not activated state.
[0043] The target fusion device mentioned above can be a newly fused device that carries the user plane rules and routing forwarding of the current PDU session after the handover. The target fusion device includes the target UPF instance and the inter-satellite routing rules to be switched to.
[0044] The aforementioned synchronization can be used to transmit the basic and incremental states of the current session information from the source fusion device to the target fusion device, so that the target UPF can continue processing from the interrupted state of the source UPF when it is activated, without having to re-establish the session context.
[0045] It should be noted that by pre-setting the collaborative rule group to the target converged device and synchronizing the current session information to the target converged device, the target converged device has completed the installation of routing rules, UPF rules, and session state recovery before the handover. This ensures that the new path and the new UPF are ready when the handover is executed. When the handover command is issued, the data plane only needs to perform an atomic switch of the local rule pointer without waiting for the rule to be issued or the state to be synchronized. This significantly shortens the handover interruption time and improves the handover success rate.
[0046] In this embodiment of the invention, the current session information, satellite topology information, and resource status information of the source fusion device are obtained. Based on the satellite topology information and resource status information, multiple candidate collaboration objects are identified, and a joint effective window for each candidate collaboration object is calculated. Each candidate collaboration object corresponds to a candidate fusion device. According to the joint effective window, a target collaboration object is selected from the multiple candidate collaboration objects, and a collaboration rule group is generated based on the target collaboration object. The collaboration rule group is pre-set in the target fusion device corresponding to the target collaboration object, and the current session information is synchronized from the source fusion device to the target fusion device. This invention solves the problems in the prior art where the timing of the inter-satellite routing rules and UPF session rules taking effect is inconsistent during session switching, and packet loss occurs when the target UPF is not ready but the route has already been switched.
[0047] It is understood that in the specific implementation of this application, data such as session information data, resource data, and topology data are involved. When the embodiments in this application are applied to specific products or technologies, user permission or consent is required. Furthermore, the collection, use, and processing of related data, as well as the training, deployment, and invocation of algorithm models, must comply with the relevant laws, regulations, and standards of the relevant countries and regions.
[0048] Optionally, in the step of determining multiple candidate collaborative objects based on satellite topology information and resource status information, the inter-satellite path from the candidate access satellite to the candidate exit node and the exit node can be determined based on the satellite topology information; the target UPF that can carry the current session can be determined based on the resource status information; and multiple candidate collaborative objects can be determined based on the inter-satellite path, exit node, and target UPF.
[0049] In this embodiment of the invention, the aforementioned satellite topology information may be information describing the locations of satellite nodes, inter-satellite link connections, link status, and ground gateway reachability in a low-Earth orbit satellite network. Satellite topology information may originate from ephemeris data, orbit prediction, inter-satellite link measurements, and gateway visibility prediction, etc.
[0050] The aforementioned candidate access satellites can be low-Earth orbit satellites that can provide radio access services to the UE at the current time or at a future predicted time.
[0051] The aforementioned candidate egress nodes can be ground gateways or ground station nodes located at the end of the inter-satellite path, capable of routing data packets from the satellite network to the terrestrial data network. It is understood that one egress node corresponds to one or more available ground gateways, and different egress nodes may be visible to the same satellite at different times.
[0052] The aforementioned inter-satellite path can be a complete inter-satellite relay path that starts from a candidate access satellite, passes through zero or more relay satellites, and finally reaches the candidate exit node.
[0053] The aforementioned exit nodes can be ground gateways or ground station nodes.
[0054] The aforementioned resource status information can be information on the available resources of the source fusion device, including CPU utilization, memory usage, number of sessions carried, cache level, and inter-satellite link latency, available bandwidth, and bit error rate.
[0055] The target UPF mentioned above can be a UPF instance that carries the user plane rules of the PDU session after the handover.
[0056] The aforementioned candidate collaboration objects are data plane migration candidate schemes generated for the PDU session to be switched. These candidate collaboration objects can be determined based on the inter-satellite path, egress node, and target UP.
[0057] Specifically, candidate collaboration objects can be represented as: C(s) = {(P_i, U_j, G_k)}.
[0058] Where C(s) represents the candidate collaboration object, P_i represents the inter-satellite path from the candidate access satellite to the candidate egress node, U_j represents the target UPF capable of carrying the session, and G_k represents the egress node. It should be noted that the candidate collaboration object must meet preset policy constraints, including slice matching, geographical constraints, the set of UPFs allowed by the service, maximum latency, minimum bandwidth, and security domain constraints.
[0059] It should be noted that satellite topology information is used to determine the inter-satellite paths and exit nodes from candidate access satellites to candidate exit nodes. This ensures that the candidate generation phase comprehensively covers all possible routing options in the handover scenario, including diverse path schemes with different access satellites, different relay combinations, and different ground exits. Resource status information is used to determine the target UPF capable of carrying the current session. This ensures that the candidate generation phase only retains UPF instances with resources sufficient for the session, eliminating scenarios where insufficient target UPF resources lead to degraded service quality or handover failure after handover. This guarantees that each target UPF in the candidate set has the actual capacity to carry the session. Multiple candidate collaborating objects are determined through combinations of inter-satellite paths, exit nodes, and target UPFs, unifying the decision space for path selection, exit node selection, and UPF selection into a combined enumeration space.
[0060] Optionally, in the step of calculating the joint effective window of each candidate cooperative object, the predicted availability interval of the inter-satellite path, the resource satisfaction interval of the target UPF, the reachability interval of the egress node, and the control plane policy allowable interval of the candidate cooperative object can be obtained; the estimated time for completing the session state synchronization, routing rule installation, verification, and resource reservation of the candidate cooperative object can be obtained; and the joint effective window of the candidate cooperative object can be calculated based on the predicted availability interval, resource satisfaction interval, reachability interval, control plane policy allowable interval, and estimated time.
[0061] In this embodiment of the invention, the predicted availability interval can be the time interval during which the inter-satellite path meets preset availability conditions on the prediction time axis. Specifically, the start time of the predicted availability interval can be the earliest time when the path is predicted to become available, and the end time of the predicted availability interval can be the last time when the path is predicted to fail due to orbital motion, link obstruction, or congestion. The availability conditions include the geometric visibility of the inter-satellite link, link load below a link load threshold, and bit error rate below a bit error rate threshold, etc.
[0062] The resource satisfaction interval of the target UPF can be the time interval during which the target UPF meets the resource conditions required to support the current session on the predicted time axis. Specifically, the start time of the resource satisfaction interval of the target UPF starts from the current time or the moment when the resource conditions are first met, and the end time of the resource satisfaction interval of the target UPF is the predicted moment when the available resources of the target UPF drop to the threshold of resources required to support the current session.
[0063] The reachability interval of the aforementioned exit node can be the time interval during which the exit node is reachable from candidate access satellites or inter-satellite path terminus on the prediction time axis. Specifically, the start time of the reachability interval of the exit node is from the moment the exit node first becomes reachable, and the end time of the reachability interval of the exit node is the moment when the exit node is predicted to become unreachable due to satellite movement out of the ground station's field of view or changes in the state of the ground gateway.
[0064] The aforementioned control plane policy allowance range can be the time interval during which the control plane policy permits the migration of current PDU session information from the source UPF to the target UPF. It is understood that the control plane policy allowance range is influenced by operator policies, slice constraints, regional compliance requirements, billing policies, or core network management plans, and can be pre-authorized and provided by the ground control plane or orchestrator.
[0065] The aforementioned estimated timeframe can be the time required to complete all preparatory work, including session state synchronization, routing rule installation, verification, and resource reservation for candidate collaborative objects. The estimated timeframe is calculated from the current time, adding the basic state transmission duration, incremental state synchronization duration, rule installation and verification duration, and resource reservation confirmation duration. The estimated timeframe reflects the completion time required for a candidate solution to move from its current state to a ready state.
[0066] The aforementioned joint effective window can be a joint effective window of candidate collaborative objects calculated based on the predicted availability interval, resource satisfaction interval, reachability interval, control plane policy allowable interval, and expected preparation time. The joint effective window can be the effective intersection of the predicted time intervals in the candidate collaborative objects where the inter-satellite path, target UPF resource, and egress node simultaneously meet the availability conditions, taking into account the preparation time required for state synchronization.
[0067] In one possible embodiment, for any candidate cooperative object c=(P_i,U_j,G_k), the spaceborne routing-UPF fusion device obtains: • I_path(c): The predicted available range in the inter-satellite path; • I_upf(c): The resource satisfaction interval of the target UPF; • I_exit(c): The reachable range of the exit node; • I_policy(c): The allowed range of the control plane policy; • T_ready(c): The estimated time for completing session state synchronization, routing rule installation, verification, and resource reservation for candidate collaboration objects.
[0068] If Delta_guard is set to the preset protection duration, then the joint effective window for candidate cooperative objects is: W(c) = [max(start(I_path), start(I_upf), start(I_exit), start(I_policy), T_ready + Delta_guard), min(end(I_path), end(I_upf), end(I_exit),end(I_policy))].
[0069] It should be noted that by obtaining the predicted availability interval of inter-satellite paths, the resource satisfaction interval of the target UPF, the reachability interval of the egress node, and the control plane policy allowance interval for candidate collaborative objects, multi-dimensional time boundary inputs are provided for the calculation of the joint effective window. This allows the window calculation to simultaneously cover four key dimensions: path topology changes, UPF resource dynamics, ground gateway visibility, and control policy constraints, avoiding feasibility misjudgments caused by considering only a single dimension. By obtaining the estimated time for completing session state synchronization, routing rule installation, verification, and resource reservation for candidate collaborative objects, the time required for pre-switch preparation is included as a constraint condition for window calculation. This ensures that the target fusion device has the ability to immediately take over services when all conditions are met at the start of the window, avoiding handover failures due to incomplete preparation. By calculating the joint effective window of candidate collaborative objects based on the predicted availability interval, resource satisfaction interval, reachability interval, control plane policy allowance interval, and estimated preparation time, multi-dimensional time series constraints are integrated into a unified quantitative judgment window, providing a clear and comparable quantitative basis for judging the feasibility of candidate collaborative schemes.
[0070] Optionally, in the step of selecting the target collaborative object from multiple candidate collaborative objects based on the joint effective window, candidate collaborative objects whose joint effective window duration is less than a preset threshold can be eliminated to obtain a set of optional collaborative objects; the joint cost value of each candidate collaborative object in the set of optional collaborative objects can be calculated; and the candidate collaborative object with the smallest joint cost value can be selected as the target collaborative object.
[0071] In this embodiment of the invention, the aforementioned preset threshold can be a pre-set joint effective window duration threshold. The preset threshold is used to determine whether the candidate collaborative object has a minimum window duration requirement sufficient for the execution of the switch and subsequent service duration. The preset threshold can be configured differently according to the service quality requirements of different service types. The threshold for real-time services can simultaneously consider state synchronization margin and old rule release margin, while the threshold for non-real-time services can allow for longer waiting times.
[0072] The above-mentioned elimination can be a process of eliminating candidate collaborative objects whose joint effective window duration is less than a preset threshold.
[0073] Understandably, candidate collaboration objects with a combined effective window duration less than a preset threshold are eliminated, and only candidate collaboration objects with a combined effective window duration greater than or equal to the preset threshold are considered feasible solutions with actual execution switching value.
[0074] The aforementioned set of optional collaborative objects can be the set of candidate collaborative objects retained from all candidate collaborative objects after removing candidate collaborative objects whose joint effective window duration is less than a preset threshold.
[0075] The aforementioned joint cost value can be a comprehensive numerical score calculated for each candidate collaborative object in the set of optional collaborative objects. The joint cost value normalizes and weights multiple evaluation dimensions of the candidate collaborative objects to obtain a single numerical metric. These evaluation dimensions include predicted end-to-end latency, link interruption risk, target UPF load level, session state synchronization preparation time, handover failure risk, overlap period bandwidth consumption, and joint effective window stability.
[0076] Specifically, the joint cost value of candidate collaborative objects is calculated as follows: J(c) = a*D(c) + b*R_link(c) + c*L_upf(c) + d*T_sync(c) + e*R_switch(c) + f*B_copy(c) - g*H(c).
[0077] Where: J(c) is the joint cost; D(c) is the predicted end-to-end latency; R_link(c) is the risk of link interruption, congestion, or bit error; L_upf(c) is the load and resource stress of the target UPF2; T_sync(c) is the expected state synchronization and rule preparation time; R_switch(c) is the risk of session switching failure or rollback; B_copy(c) is the bandwidth and cache consumption caused by copying packets during the overlap period; H(c) is the joint effective window length or its stability score; a, bc, d, e, f, and g are weights configured according to service level, slicing strategy, or operation strategy.
[0078] In this embodiment of the invention, the candidate object that satisfies the constraints and has the minimum joint cost value is selected as the target collaborative rule group. The joint cost value can be calculated using enumeration, heuristic search, integer programming, dynamic programming, graph search, or a learning model.
[0079] Furthermore, this can be represented by the following pseudocode: for each session s to be migrated: candidates = generate_path_upf_gateway_tuples(s) feasible = [] for each candidate c in candidates: ready = estimate_state_sync(c) + install_rules(c) + validate(c) window = intersect(path_interval(c), upf_interval(c), gateway_interval(c), policy_interval(c)) window.start = max(window.start, now + ready + guard_time) if window.duration >= min_window(s): feasible.append((c, window, cost(c, window))) If feasible, then empty. retain_current_group_or_choose_authorized_fallback(s) else: target = candidate_with_lowest_cost(feasible) create_and_prepare_coordinated_rule_group(s, target) The aforementioned target collaboration object can be the candidate collaboration object with the lowest joint generation value. The lower the joint generation value, the better the overall quality of the candidate collaboration object; conversely, the higher the joint generation value, the worse the overall quality of the candidate collaboration object.
[0080] In this embodiment of the invention, a candidate collaboration object is included in the set of selectable collaboration objects only when length(W(c)) >= Theta_window. Theta_window can be set according to the service type; the threshold for real-time services can simultaneously consider state synchronization margin and old rule release margin, while non-real-time services can allow for longer waiting times.
[0081] It should be noted that by eliminating candidate collaboration objects whose joint effective window duration is less than a preset threshold, a set of optional collaboration objects is obtained. This ensures that candidate collaboration objects with insufficient window duration or lacking sufficient switchover execution and business duration windows are filtered out before entering cost comparison, avoiding the risk of re-migration or business interruption caused by candidate collaboration objects becoming invalid quickly after the switchover. By calculating the joint cost value of each candidate collaboration object in the set of optional collaboration objects, the candidate collaboration object with the smallest joint cost value is selected as the target collaboration object, ensuring that the final selected solution has the best overall quality among all candidate solutions that meet time feasibility requirements.
[0082] Optionally, in the step of generating a collaboration rule group based on the target collaboration object, a corresponding collaboration version identifier can be assigned to the target collaboration object; a routing rule set can be generated based on the inter-satellite path of the target collaboration object; a target UPF rule set can be generated based on the target UPF of the target collaboration object; and the routing rule set, the target UPF rule set, and the collaboration version identifier can be associated to obtain the collaboration rule group.
[0083] In this embodiment of the invention, the aforementioned collaborative version identifier can be a unique internal identifier assigned to the target collaborative object, used to uniquely bind and distinguish different collaborative rule groups in the control table, forwarding table metadata, status cache, or inter-device collaborative messages of the spaceborne routing-UPF fusion device. The collaborative version identifier can be implemented in the form of monotonically increasing count, timestamp plus node identifier, or random unique identifier, and is only used within the spaceborne routing-UPF fusion device and in collaborative control messages. The collaborative version identifier does not need to be added to the UE, GTP-U, or external IP packets. It can be implemented within the onboard routing-UPF converged device using one or more of the following methods: 1. Within the programmable data plane unit, query the local flow context table based on the PDU session identifier, TEID, QFI, 5-tuple, ingress port, or a combination thereof to obtain the rule pointer corresponding to the CEPoch; 2. Within the target converged device, select the activated target UPF session entry based on the ingress port, existing tunnel endpoint, route arrival interface, or session mapping; 3. Carry the CEPoch in the control / management messages between the source converged device, target converged device, and relay converged device for rule installation, status verification, and activation confirmation; 4. Store the CEPoch in the high-speed state storage. Associated with checkpoints, replication windows, and decommissioning timers, late messages can still be processed by the old rule group; 5. For services requiring replication and strict deduplication, prioritize utilizing existing tunnel sequence information or maintaining sequence checkpoints in the private control / bypass state between converged devices; when no available sequence information exists, use message length, key header fields, and payload digest to form a short fingerprint for duplicate identification. The above fingerprints are only cached internally by the device and do not change the message format.
[0084] The aforementioned routing rule set can be a set of forwarding rules generated based on the inter-satellite paths in the target cooperating object, used to guide the forwarding of data packets in the inter-satellite network. This routing rule set includes next-hop node identifiers, path segment descriptions, link resource reservation information, priority, and backup path information, etc.
[0085] The aforementioned target UPF rule set can be a set of rules generated based on the target UPF in the target collaboration object, used to carry current session information in the target converged device. The target UPF rule set includes packet detection rules, forwarding action rules, QoS enforcement rules, tunnel endpoint mapping, service offloading policies, and billing policies, etc.
[0086] The above association can be a process of mapping routing rule sets, target UPF rule sets, and cooperative version identifiers. By associating routing rule sets, target UPF rule sets, and cooperative version identifiers, these sets become a logical whole that can be uniformly addressed and manipulated; that is, the corresponding routing rule sets and target UPF rule sets can be indexed through the cooperative version identifier.
[0087] The aforementioned collaborative rule group can be a data structure that encapsulates the routing rule set, the target UPF rule set, the collaborative version identifier, and associated information together. The core of the collaborative rule group is that the routing rule set and the target UPF rule set share the same collaborative version identifier, which is used to associate the two types of rules. The collaborative rule group has a unified lifecycle state, with routing rules and UPF rules sharing the same state machine. The collaborative rule group also has unified commit and rollback information; activation and rollback operations are executed holistically at the rule group level. Figure 2 As shown, Figure 2 This is a schematic diagram of a collaborative rule group provided in an embodiment of the present invention. A collaborative rule group can be a collection of routing rules, target UPF rules, session states, activation conditions, and fallback conditions associated with the same PDU session, the same QoS flow, or the same service flow. Each collaborative rule group includes at least the fields shown in Table 1 below: Table 1
[0088] It should be noted that by assigning a corresponding collaboration version identifier to the target collaboration object, a unified association identifier is established between routing rules and UPF rules. This allows two types of rules, originally stored independently in different forwarding tables and session tables, to be queried and managed uniformly through the same identifier. By generating a routing rule set based on the inter-satellite path of the target collaboration object and a target UPF rule set based on the target UPF of the target collaboration object, routing rules and UPF rules are generated independently according to their respective data plane formats, without interfering with each other. At the same time, the dedicated formats and optimization capabilities of their respective data plane processing are preserved, avoiding the sacrifice of the expressive power of either type of rule for the sake of a unified format. By associating the routing rule set, the target UPF rule set, and the collaboration version identifier to obtain a collaboration rule group, routing rules and UPF rules belonging to the same target collaboration object are encapsulated in the same data structure from the beginning of generation, ensuring that all subsequent operations are atomically managed at the granularity of the collaboration rule group.
[0089] Optionally, in the step of synchronizing the current session information from the source fusion device to the target fusion device, the basic session state of the current session state information can be sent from the source fusion device to the target fusion device; the source fusion device sends the incremental session state to the target fusion device according to the log sequence number.
[0090] In this embodiment of the invention, the aforementioned basic session state can be static configuration information that changes very infrequently or not at all during the migration process of the current session. The aforementioned basic session state includes key UPF rule fields, tunnel mapping, billing count, and last acknowledgment checkpoint. The aforementioned key UPF rule fields can be core matching fields and action fields used to identify and classify packets in packet detection rules, forwarding action rules, and QoS execution rules, enabling the target UPF to correctly identify packets belonging to the current session and execute corresponding forwarding and QoS actions. The aforementioned tunnel mapping can be the endpoint identifier and mapping relationship of the current session in the core network user plane tunnel. The tunnel mapping includes uplink tunnel endpoint identifiers and downlink tunnel endpoint identifiers, enabling the target UPF to correctly decapsulate and encapsulate tunnel packets. The aforementioned billing count can be the number of uplink and downlink data traffic billing bytes currently accumulated in the current session. The billing count is used to ensure that the billing count is continuous after the handover, without billing breaks or duplicate billing. The aforementioned last acknowledgment checkpoint can be the sequence identifier of the last message received that the source UPF of the current session information has acknowledged to the core network control plane. The last acknowledgment checkpoint ensures that the target UPF will not reprocess acknowledged messages after takeover. The source UPF can be the UPF instance currently carrying the session's user plane rules.
[0091] The incremental session state mentioned above can be dynamic state change information that is continuously generated during the operation of the current session, based on the basic session state. The incremental session state can be arranged by log sequence number and records all state change events that have occurred since the snapshot time of the basic state, including newly added billing count increments, consumption and replenishment of QoS token buckets, changes in cache level, and processing records of newly received packets, etc.
[0092] The aforementioned log sequence number can be an incrementing sequence number assigned by the source fusion device to each incremental session state change event, used to identify the order in which state changes occur. The log sequence number ensures that the target fusion device can replay incremental state changes in a completely consistent chronological order with the source, avoiding state inconsistencies caused by out-of-order synchronization.
[0093] It should be noted that by sending the basic session state from the source fusion device to the target fusion device—including key fields of UPF rules, tunnel mapping, accounting counts, and last acknowledgment checkpoints—the amount of data transmitted on the inter-satellite control link is reduced. By having the source fusion device send incremental session state to the target fusion device according to log sequence numbers, the target fusion device is provided with a sequential basis for checking the continuity and integrity of incremental state, enabling it to detect packet loss and out-of-order delivery, thus improving the reliability of state synchronization.
[0094] Optionally, after pre-setting the collaborative rule group to the target fusion device corresponding to the target collaborative object and synchronizing the current session information from the source fusion device to the target fusion device, a consistency verification can be performed on the pre-set collaborative rule group and the synchronized session state. After the verification passes, the collaborative rule group is activated according to a preset activation time, and the data plane processing of the current session information is switched from the current collaborative rule group to the collaborative rule group corresponding to the collaborative version identifier. After confirming that the collaborative rule group has normally carried the business data of the current session, the state of the collaborative rule group is changed to the retired state and the resources occupied by the old rule group are released. In the event of a switching anomaly or a collaborative rule group failure, the entire collaborative rule group is rolled back to the collaborative rule group before the switch, or the entire group is switched to a pre-verified backup collaborative rule group.
[0095] In this embodiment of the invention, the aforementioned consistency verification can be a process of checking and confirming the preset results and synchronization status in the target fusion device after the collaborative rule group is preset and the session state is synchronized. Consistency verification includes checking whether the target routing rules have been correctly installed and reachable, whether the target UPF rules have been successfully installed, whether necessary resources have been reserved, whether the verification of the basic session state and the incremental session state is consistent, whether the remaining duration of the joint effective window is still greater than a preset threshold, and whether the local time deviation of the target fusion device is within the allowable range.
[0096] The aforementioned preset activation time can be a future activation point specified by the collaborative rule group after the consistency verification is completed. The preset activation time must meet constraints such as not being earlier than the sum of the current time plus the maximum message round-trip delay, the maximum clock skew, and the activation protection duration, and falling within the joint effective window range of the collaborative rule group.
[0097] The aforementioned switching can be a process of switching the data plane processing logic of the current session information from the current collaborative rule group to the collaborative rule group corresponding to the collaborative version identifier when the preset activation time arrives.
[0098] The aforementioned current coordination rule group can be the data plane processing group that is currently carrying the current session information before the switchover is executed, including the currently used routing rules and source UPF rules.
[0099] The aforementioned retirement state can be a transitional state for a collaborative rule group after it is replaced by a new collaborative rule group. In the retirement state, the collaborative rule group is only used to process late messages that have already been sent and as a fast rollback path, and no longer accepts new regular business messages.
[0100] The aforementioned release of resources occupied by old rule groups can be achieved by reclaiming various resources occupied by the collaborative rule group after it enters retirement and the late message processing window ends. These resources include routing table entries, UPF session table entries, cache space, and resource reservations.
[0101] The aforementioned switching anomalies can be various abnormal situations that occur during the switching of collaborative rule groups, causing the new collaborative rule group to be unable to carry out business normally, including target path failure, insufficient target UPF resources, inconsistent status, failure to receive activation confirmation, or continuous failure to meet service quality standards.
[0102] The aforementioned overall rollback can be an atomic revocation operation performed on a per-cooperative rule group basis when an anomaly occurs during a cooperative rule group switchover. This rollback reverts both the routing rule set and the target UPF rule set as a whole to their pre-switch state, rather than reverting routes or disabling UPF rules individually. Overall rollback ensures consistency between the routing and UPF states.
[0103] The aforementioned backup coordination rule group can be an alternative coordination rule group that has passed consistency verification but was not selected as the first priority scheme, and is retained simultaneously when selecting the target coordination object. The backup coordination rule group can be activated as a whole when the current coordination rule group fails, so as to shorten the fault recovery time.
[0104] In this embodiment of the invention, the invention can process duplicate, continuous, and late messages in overlapping windows in real time as follows: 1. The source fusion device uses a replication strategy to send the same message to both the old and new paths, or uses different replication ratios for messages of different priorities; 2. The target fusion device establishes a short-term deduplication cache for the session. The cache key may include an existing tunnel sequence number, or a fingerprint consisting of a session identifier, message length, key header fields, and payload digest; 3. For services that allow ordered delivery, out-of-order messages are cached according to sequence checkpoints or arrival windows. After exceeding the waiting threshold, the message is delivered, discarded, or retransmitted according to the strategy; 4. In the retired state, the old rule group only processes late messages that conform to the old session mapping and old checkpoint range, and no longer accepts new regular service messages; 5. If the target UPF does not observe continuous session data within the set confirmation time, or finds that the data plane hit is inconsistent with the state digest, it triggers a rollback or starts a backup collaborative rule group.
[0105] The rule states of the present invention are shown in Table 2 below: Table 2
[0106] like Figure 3 As shown, Figure 3 This is a schematic diagram of a collaborative rule group state machine provided in an embodiment of the present invention. Each onboard route-UPF fusion device can avoid unilateral switching when a new route is enabled but the target UPF is not ready by preparing the state transition through the preparation determination and submission token constraint.
[0107] like Figure 4 As shown, Figure 4 This is a schematic diagram of a local autonomous handover process under constrained space-to-ground control conditions provided by an embodiment of the present invention. Specifically, when the space-to-ground control link is unreachable, the round-trip delay exceeds a threshold, or a control plane failure occurs, the fusion device can autonomously perform a coordinated handover within a pre-authorized range. The pre-authorization includes at least: 1. The allowed set of target UPFs, the set of egress nodes, and the range of path resources; 2. The range of migrated sessions / slices; 3. The maximum bandwidth, the maximum replication ratio, the allowed QoS degradation range, and the cache limit; 4. The maximum autonomous duration and the maximum retention time of old rules; 5. The fallback priority and the backup coordinated rule group; 6. Hard restrictions on security domains, billing, and compliance policies.
[0108] In this embodiment of the invention, after autonomous triggering, the spaceborne routing-UPF fusion device still needs to perform joint window calculation, state verification, and condition submission, but it does not need to wait for real-time ground commands. After the control plane recovers, the spaceborne routing-UPF fusion device reports the actual used CEpoch, path, UPF2, state summary, billing differential, and anomaly records, and the control plane performs state convergence.
[0109] It should be noted that by performing consistency verification on the pre-configured collaborative rule groups and the synchronized session state, activation is only allowed after successful verification. This ensures that the pre-configured and synchronized results are confirmed before the switchover execution, preventing the risk of abnormal data plane processing after the switchover due to incomplete rule installation or inconsistent states. After successful verification, the collaborative rule group is activated according to a preset activation time, and the data plane processing of the current session information is switched from the current collaborative rule group to the collaborative rule group corresponding to the collaborative version identifier. This ensures that the new collaborative rule group takes effect atomically after meeting time constraints, and the routing rules and target UPF rules are activated simultaneously. This avoids the problem of packet drop due to the time difference between routing and UPF activation, where routing has switched but UPF is not ready. After confirming that the collaborative rule group is normally carrying business data, the state is changed to retired and the resources occupied by the old rule group are released. This allows the old rules to enter a transitional state that only processes late packets after a successful switchover and is eventually released in an orderly manner. This provides a smooth transition channel for packets already dispatched within the overlapping window, avoiding packet loss caused by the immediate clearing of old rules. By reverting to the original collaborative rule group or switching to a backup collaborative rule group as a whole when a switching failure occurs, the rollback operation is performed atomically on the routing rule set and the target UPF rule set. This avoids the inconsistency that occurs when routes are rolled back but UPF rules are not, or vice versa, resulting from separate rollbacks. This ensures the consistency of the state of routing rules and UPF rules under any abnormal scenario.
[0110] like Figure 5 As shown, this embodiment of the invention provides a collaborative switching device for a spaceborne routing-UPF fusion device for low-Earth orbit satellite networks. This collaborative switching device for a spaceborne routing-UPF fusion device for low-Earth orbit satellite networks includes: The acquisition module 501 is used to acquire the current session information, satellite topology information and resource status information of the source fusion device; The first processing module 502 is used to determine multiple candidate collaborative objects based on the satellite topology information and the resource status information, and to calculate the joint effective window of each candidate collaborative object, wherein each candidate collaborative object corresponds to a candidate fusion device; The second processing module 503 is used to select a target collaborative object from multiple candidate collaborative objects according to the joint effective window, and generate a collaborative rule group according to the target collaborative object; The synchronization module 504 is used to pre-set the collaboration rule group to the target fusion device corresponding to the target collaboration object, and to synchronize the current session information from the source fusion device to the target fusion device.
[0111] Optionally, the first processing module 502 is further configured to determine, based on the satellite topology information, the inter-satellite path from the candidate access satellite to the candidate exit node and the exit node; based on the resource status information, determine the target UPF that can carry the current session; and determine multiple candidate cooperative objects according to the inter-satellite path, the exit node, and the target UPF.
[0112] Optionally, the first processing module 502 is further configured to obtain the predicted availability interval, the resource satisfaction interval of the target UPF, the reachability interval of the egress node, and the control plane policy allowance interval in the inter-satellite path of the candidate collaborative object; obtain the estimated time for completing the session state synchronization, routing rule installation, verification, and resource reservation of the candidate collaborative object; and calculate the joint effective window of the candidate collaborative object based on the predicted availability interval, the resource satisfaction interval, the reachability interval, the control plane policy allowance interval, and the estimated time.
[0113] Optionally, the second processing module 503 is further configured to remove candidate collaborative objects whose joint effective window duration is less than a preset threshold to obtain a set of optional collaborative objects; calculate the joint cost value of each candidate collaborative object in the set of optional collaborative objects; and select the candidate collaborative object with the smallest joint cost value as the target collaborative object.
[0114] Optionally, the second processing module 503 is further configured to assign a corresponding collaboration version identifier to the target collaboration object; generate a routing rule set based on the inter-satellite path of the target collaboration object; generate a target UPF rule set based on the target UPF of the target collaboration object; and associate the routing rule set, the target UPF rule set, and the collaboration version identifier to obtain a collaboration rule group.
[0115] Optionally, the synchronization module 504 is further configured to send the basic session state of the current session state information from the source fusion device to the target fusion device, wherein the basic session state includes UPF rule key fields, tunnel mapping, billing count, and last acknowledgment message checkpoint; and the source fusion device sends incremental session state to the target fusion device according to the log sequence number.
[0116] Optionally, the device is further configured to perform consistency verification on the pre-set collaborative rule group and the synchronized session state; after the verification is passed, activate the collaborative rule group according to the preset activation time, switch the data plane processing of the current session information from the current collaborative rule group to the collaborative rule group corresponding to the collaborative version identifier; after confirming that the collaborative rule group has normally carried the service data of the current session, change the state of the collaborative rule group to the retired state and release the resources occupied by the old rule group; and, in the event of a switching anomaly or the collaborative rule group failing, revert the entire collaborative rule group to the collaborative rule group before the switch, or switch the entire collaborative rule group to a pre-verified backup collaborative rule group.
[0117] like Figure 6 As shown, Figure 6 This is a schematic diagram of a collaborative switching system for onboard routing-UPF fusion equipment for low-Earth orbit (LEO) satellite networks provided in an embodiment of the present invention. The collaborative switching system for onboard routing-UPF fusion equipment for LEO satellite networks includes: a user terminal, multiple LEO satellites, at least one ground gateway, at least one data network exit, and multiple onboard routing-UPF fusion devices. The onboard routing-UPF fusion devices are deployed in the payloads of the LEO satellites and are used as local user plane processing nodes for access satellites, or as routing and UPF collaboration nodes for relay satellites. The collaborative switching system for onboard routing-UPF fusion equipment for LEO satellite networks is used to execute the collaborative switching device for onboard routing-UPF fusion equipment for LEO satellite networks provided in this embodiment of the present invention.
[0118] like Figure 7 As shown, Figure 7This is a schematic diagram of the structure of the spaceborne routing-UPF fusion device provided in an embodiment of the present invention. The spaceborne routing-UPF fusion device includes an inter-satellite / satellite-to-ground high-speed interface unit, a programmable data plane unit, a cooperative control processing unit, a high-speed state storage unit, a time synchronization unit, and an inter-device cooperative interface unit. The aforementioned inter-satellite / satellite-to-ground high-speed interface unit includes one or more optical communication, radio frequency communication, Ethernet, SerDes, or corresponding satellite payload data interfaces for sending and receiving inter-satellite messages, feeder link messages, and ground gateway messages. The aforementioned programmable data plane unit can be implemented by an FPGA, ASIC, NPU, DPU, programmable switching chip, or a combination thereof, for high-speed execution of message parsing, classification, tunnel decapsulation / capsulation, route lookup, PDR / FAR / QER matching, queue scheduling, replication, caching, deduplication, and counting. The aforementioned cooperative control processing unit includes a general-purpose processor, an on-chip processor, or a dedicated controller for performing topology prediction, candidate combination generation, joint cost calculation, rule orchestration, session state synchronization, verification, submission, rollback, and autonomous decision-making. The aforementioned high-speed state storage unit includes high-speed memory and non-volatile storage for storing active session tables, candidate collaborative rule groups, session checkpoints, incremental state logs, message deduplication windows, rule hashes, and audit logs. The aforementioned time synchronization unit can obtain local time from satellite timing sources, GNSS, onboard clocks, ground timing sources, or inter-satellite timing protocols. This unit provides a unified time reference for collaborative activation and records allowable clock deviations. The aforementioned inter-device collaborative interface unit transmits state summaries, incremental states, preparation acknowledgments, commit tokens, and execution acknowledgments between the source and target fusion devices. This inter-device collaborative interface unit can reuse inter-satellite control channels, management channels, or secure tunnels. The aforementioned onboard routing-UPF fusion device also includes a security and trusted execution unit. The inter-device collaborative interface unit verifies rule sources, collaborative message integrity, version signatures, and access permissions to prevent erroneous or unauthorized rule activation.
[0119] In one possible embodiment, taking the migration of a PDU session source UPF to a target UPF as an example, the user terminal currently accesses the network via satellite A; the source UPF in the source fusion device on satellite A carries the current session; as the satellite moves, satellite B will become the access satellite, or the path via satellite D to ground gateway G2 will become a better path. The target fusion device on satellite B or satellite D pre-configures the target UPF session context and new routing rules. Once the coordination conditions are met, the data plane processing of the session is switched from the current path + source UPF to the target path + target UPF.
[0120] In this embodiment of the invention, the invention can interact with SMF, AMF, satellite network controller, orbit / ephemeris service, and ground orchestrator to receive session policies, candidate UPF grants, service QoS constraints, and topology information. This interaction can employ existing control interfaces, management interfaces, or proprietary satellite-to-ground control interfaces; the collaborative versioning, state machine, and commit mechanism of this invention do not depend on any single external interface.
[0121] In another possible embodiment, the example of access migration from satellite A to satellite B and the coordinated migration from source UPF to target UPF is used for illustration. The user terminal currently accesses via satellite A, and the service path is: user terminal -> satellite A (converged equipment / source UPF) -> satellite C -> ground gateway G1 -> data network.
[0122] This invention predicts that satellite A will leave the user terminal service area after 90 seconds, and satellite B will enter the service area after 70 seconds. Candidate solutions include: Option 1: After the user terminal is migrated to Satellite B, the path will be Satellite B -> Satellite C -> G1, and the source UPF will continue to be used; Option 2: After the user terminal is migrated to Satellite B, the path is Satellite B -> Satellite D -> G2, and the session is carried by the target UPF in the target fusion device on Satellite B or Satellite D.
[0123] In this embodiment of the invention, Option 1 has a lower current latency, but the predicted congestion risk from satellite C to G1 is high, and the effective window is insufficient to cover the required service duration; Option 2 has a slightly longer path, but the target UPF2 resource is sufficient, the status is expected to be synchronized before the handover, and the joint effective window is longer. Therefore, Option 2 is selected.
[0124] The converged device creates a collaborative version CEpoch=E105, which includes: 1. E105-Route: Entry mapping, next hop, and resource reservation rules from satellite B to satellite D and then to G2; 2. E105-UPF: The target UPF is the PDR, FAR, QER, and existing tunnel mapping for this PDU session; 3. E105-State: Session base state, billing count, token bucket state, last acknowledgment checkpoint, and incremental log sequence number; 4. E105-Window: The active window is determined based on the intersection of path, target UPF resource, G2 reachability, and policy. 5. E105-Rollback: Roll back to the old rule group E104 or switch to a pre-validated alternate group.
[0125] The source fusion device synchronizes the basic state of E105 to the target fusion device, and then sends incremental state. The target device installs routing rules and target UPF rules, and verifies the state hash. After successful verification, each device receives a commit token set to a future time. At the activation time, the local flow context of satellite B points to E105; the inter-satellite forwarding rule selects the BD-G2 path; and the target UPF enables session rules. All E105 identifiers exist only in the internal entries and control messages of the fusion device; external messages maintain their existing format.
[0126] In this embodiment of the invention, for high-reliability services, the invention can transmit via dual paths according to a strategy within a limited overlap period. The target device deduplicates messages based on existing sequence information or internal message fingerprints. After the target UPF confirms that the service flow continues to hit and the QoS conditions are met, the target UPF's rule group enters a retirement state and is released after the late message window ends.
[0127] In another possible embodiment, taking the interruption of the satellite-to-ground control link as an example, the fusion device of satellite A has obtained candidate cooperative objects UPF2 and UPF3 and their authorized resource ranges from the control plane, and has pre-set two cooperative rule groups, E201 and E202. After the satellite-to-ground control link is interrupted, satellite A finds that the interruption risk of the current path exceeds the threshold. The fusion device re-evaluates the joint effective window of E201 and E202, and finds that the path of E201 is available, but the cached resources of UPF2 are below the threshold, while the path of E202 and the resources of UPF3 both meet the conditions. The fusion device selects E202 within the authorized range, sends the final incremental status, and submits E202 at the preset activation time after completing local and target device verification. If E202 fails to establish a continuous data stream within the confirmation window, the current rule group is automatically restored; if the restoration fails, the authorized backup path is used and an anomaly is reported. After the control plane is restored, the fusion device reports the actually activated E202 and the session state difference.
[0128] Another possible implementation is illustrated by fast forwarding within the converged hardware. In the onboard routing-UPF converged device, the control processing unit downloads the CEpoch, local flow context index, PDR / FAR / QER pointers, and route pointers to the programmable data plane unit. When a packet arrives, the programmable data plane obtains the flow context index based on the TEID, QFI, 5-tuple, and ingress port; this index points to the currently active coordination rule group. Without modifying the packet header, the data plane sequentially performs UPF rule matching, QoS actions, and inter-satellite next-hop selection. When the activation time is reached, the data plane unit only needs to atomically update the rule pointer corresponding to the flow context index, or update the active table selection bit using a dual-table switching method. Thus, the control processing unit does not need to participate on a packet-by-packet basis, meeting the high-speed forwarding requirements of the satellite payload. Old tables are retained within the retirement window for use with late packets and rollback.
[0129] This invention also provides a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the various processes of the collaborative switching method for onboard routing-UPF fusion equipment for low-Earth orbit satellite networks provided in this invention, and achieves the same technical effect. To avoid repetition, it will not be described again here.
[0130] The above description is the preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principles described in this application, and these improvements and modifications should also be considered within the scope of protection of this application.
Claims
1. A collaborative switching method for onboard routing-UPF fusion equipment for low-Earth orbit satellite networks, characterized in that, The method includes the following steps: Obtain the current session information, satellite topology information, and resource status information of the source fusion device; Based on the satellite topology information and the resource status information, multiple candidate collaborative objects are identified, and the joint effective window for each candidate collaborative object is calculated. Each candidate collaborative object corresponds to a candidate fusion device. Based on the joint effective window, a target collaborative object is selected from multiple candidate collaborative objects, and a collaborative rule group is generated based on the target collaborative object; The collaborative rule group is preset into the target fusion device corresponding to the target collaborative object, and the current session information is synchronized from the source fusion device to the target fusion device. 2.The method of claim 1, wherein, Based on the satellite topology information and the resource status information, multiple candidate cooperation objects are identified, including: Based on the satellite topology information, the inter-satellite paths from candidate access satellites to candidate exit nodes and the exit nodes are determined; Based on the resource status information, a target UPF capable of supporting the current session is determined; Based on the inter-satellite path, the exit node, and the target UPF, multiple candidate cooperative objects are identified. 3.The method of claim 2, wherein, The calculation of the joint effective window for each of the candidate collaborative objects includes: Obtain the predicted available interval of the inter-satellite path, the resource satisfaction interval of the target UPF, the reachability interval of the exit node, and the control plane policy allowed interval in the candidate cooperative objects; Obtain the estimated time when the session state synchronization, routing rule installation, verification, and resource reservation of the candidate collaboration objects will be completed; Based on the predicted availability interval, the resource satisfaction interval, the reachability interval, the control plane policy allowable interval, and the expected time, the joint effective window of the candidate collaborative objects is calculated. 4.The method of claim 1, wherein, The step of selecting a target collaborative object from multiple candidate collaborative objects based on the joint effective window includes: Candidate collaborative objects whose joint effective window duration is less than a preset threshold are removed to obtain a set of selectable collaborative objects; Calculate the joint cost of each candidate collaborative object in the set of optional collaborative objects; The candidate collaborative object with the lowest joint generation value is selected as the target collaborative object. 5.The method of claim 1, wherein, The step of generating a set of collaboration rules based on the target collaboration object includes: Assign a corresponding collaboration version identifier to the target collaboration object; A routing rule set is generated based on the inter-satellite path of the target collaborative object, and a target UPF rule set is generated based on the target UPF of the target collaborative object; The routing rule set, the target UPF rule set, and the collaboration version identifier are associated to obtain a collaboration rule group. 6.The method of claim 1, wherein, The step of synchronizing the current session information from the source fusion device to the target fusion device includes: The basic session state of the current session state information is sent from the source fusion device to the target fusion device. The basic session state includes UPF rule key fields, tunnel mapping, billing count and last acknowledgment message checkpoint. The source fusion device sends the incremental session status to the target fusion device according to the log sequence number. 7.The method of claim 1, wherein, After presetting the collaborative rule group to the target fusion device corresponding to the target collaborative object, and synchronizing the current session information from the source fusion device to the target fusion device, the method further includes: Perform consistency verification on the pre-set collaborative rule group and the synchronized session state; After the verification is passed, the collaborative rule group is activated according to the preset activation time, and the data plane processing of the current session information is switched from the current collaborative rule group to the collaborative rule group corresponding to the collaborative version identifier. After confirming that the collaborative rule group is successfully carrying the service data of the current session, the status of the collaborative rule group is changed to retired, and the resources occupied by the old rule group are released; and, In the event of a switching anomaly or the failure of the collaborative rule group, the entire collaborative rule group will be rolled back to the collaborative rule group before the switch, or the entire group will be switched to a pre-verified backup collaborative rule group. 8.A method for coordinated handover of a spaceborne routing-UPF converged device for a low earth orbit satellite network, characterized in that, The collaborative switching method apparatus for the spaceborne routing-UPF fusion equipment for low-Earth orbit satellite networks includes: The acquisition module is used to acquire the current session information, satellite topology information, and resource status information of the source fusion device; The first processing module is used to determine multiple candidate collaborative objects based on the satellite topology information and the resource status information, and to calculate the joint effective window for each candidate collaborative object, with each candidate collaborative object corresponding to a candidate fusion device; The second processing module is used to select a target collaborative object from multiple candidate collaborative objects according to the joint effective window, and generate a collaborative rule group according to the target collaborative object; The synchronization module is used to pre-set the collaboration rule group to the target fusion device corresponding to the target collaboration object, and to synchronize the current session information from the source fusion device to the target fusion device. 9.A system for coordinated handover of a spaceborne routing-UPF converged device for a low earth orbit satellite network, the system comprising: include: User terminal, multiple low-Earth orbit satellites, at least one ground gateway, at least one data network exit, and multiple onboard routing-UPF fusion devices; The onboard routing-UPF fusion device is deployed in the payload of the low-Earth orbit satellite and is used as a local user plane processing node for access satellites or as a routing and UPF coordination node for relay satellites. The system is used to execute the collaborative switching device of the onboard routing-UPF fusion device for low-Earth orbit satellite networks as described in claim 8.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps in the collaborative switching method for a spaceborne routing-UPF fusion device for low-Earth orbit satellite networks as described in any one of claims 1 to 7.
