Methods, apparatus and systems for configuring satellite network slice resources

Abstract

This application provides a method, apparatus, and system for configuring satellite network slice resources, applied to a path calculation client (PCC) device. The method includes: receiving a configuration instruction sent by a path calculation unit (PCE) device, wherein the configuration instruction is generated by the PCE device based on network topology information and service requirement information within a service time period, and includes at least a target slice path corresponding to the target slice resource required by the PCE device, and a target timing activation parameter for reserving the target slice resource; reserving the target slice resource within the service time period according to the target slice path and the target timing activation parameter.

Description

Technical Field

[0001] This application relates to the field of low-Earth orbit satellite communication, and more specifically, to a method, apparatus, and system for configuring satellite network slicing resources. Background Technology

[0002] Currently, low-Earth orbit (LEO) satellite networks adopt a multi-satellite coverage and space-to-ground integration networking approach. During the networking process, network slicing technologies are used to ensure service quality. These technologies include terrestrial network slicing and space network slicing. For terrestrial network slicing, to adapt to the relatively fixed topology and configuration of terrestrial networks, a persistently configurable Network Configuration Protocol (Netconf) is generally used to complete the deployment of traditional terrestrial network slices. Space network slicing, on the other hand, uses the PCEP (Path Computation Element Communication Protocol) to meet the high-frequency configuration requirements of satellite network slicing.

[0003] However, the PCEP protocol relies heavily on continuous online interaction at the control plane. In satellite network environments, if the control unit goes offline due to satellite-to-ground link interruptions, delays, or node failures, the reliability of the slice configuration information issued by the PCEP protocol will decrease, leading to slice management interruptions and affecting the timely activation and recycling efficiency of slices. In summary, traditional methods suffer from the technical problem of inefficient slice resource management due to low efficiency in slice resource configuration.

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

[0005] This application provides a method, apparatus, and system for configuring satellite network slice resources, in order to at least solve the technical problem of poor slice resource management efficiency caused by low slice resource configuration efficiency in related technologies.

[0006] According to one embodiment of this application, a method for configuring satellite network slice resources is provided, applied to a path computing client (PCC) device, comprising: receiving a configuration instruction sent by a path computing element (PCE) device, wherein the configuration instruction is generated by the PCE device based on network topology information and service requirement information within a service time period, and includes at least a target slice path corresponding to the target slice resource required by the PCE device, and a target timing activation parameter for reserving the target slice resource; reserving the target slice resource within the service time period according to the target slice path and the target timing activation parameter.

[0007] According to another embodiment of this application, a method for configuring satellite network slice resources is provided, applied to a path calculation unit (PCE) device, comprising: generating a configuration instruction based on network topology information and service requirement information within a service time period, wherein the configuration instruction includes at least a target slice path corresponding to the target slice resource required by the PCE device, and a target timing activation parameter for reserving the target slice resource; and sending the configuration instruction to a PCC device, so that the PCC device reserves the target slice resource within the service time period according to the target slice path and the target timing activation parameter.

[0008] According to another embodiment of this application, a satellite network slice resource configuration device is provided, applied to a PCC device. The device includes: a receiving module, configured to receive a configuration instruction sent by a PCE device, wherein the configuration instruction is generated by the PCE device based on network topology information and service requirement information within a service time period, and includes at least a target slice path corresponding to the target slice resource required by the PCE device, and a target timing activation parameter for reserving the target slice resource; and a reservation module, configured to reserve the target slice resource within the service time period according to the target slice path and the target timing activation parameter.

[0009] According to another embodiment of this application, a satellite network slice resource configuration device is provided, applied to a PCE device. The device includes: a generation module, configured to generate configuration instructions based on network topology information and service requirement information within a service time period, wherein the configuration instructions include at least a target slice path corresponding to the target slice resource required by the PCE device, and a target timing activation parameter for reserving the target slice resource; and a sending module, configured to send the configuration instructions to a PCC device, so that the PCC device reserves the target slice resource within the service time period according to the target slice path and the target timing activation parameter.

[0010] According to another embodiment of this application, a satellite network slice resource configuration system is provided. The system includes a PCC device and a PCE device. The PCC device includes a satellite-borne router deployed on a satellite and a ground-based router deployed on the ground. The PCE device includes a ground-based network controller. The PCE device is used to generate configuration instructions based on network topology information and service requirement information within a service time period. The configuration instructions include at least a target slice path corresponding to the target slice resource required by the PCE device, and a target timing activation parameter for reserving the target slice resource. The PCC device is used to receive the configuration instructions sent by the PCE device and reserve the target slice resource within the service time period according to the target slice path and the target timing activation parameter.

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

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

[0013] This application allows a PCC device to receive instructions from a PCE device, generated by the PCE device based on network topology information and service requirements within a service time period. These instructions include at least the target slice path corresponding to the target slice resources required by the PCE device, and target timing parameters for reserving the target slice resources. The PCC device then reserves the target slice resources within the service time period according to the target slice path and the target timing parameters. In other words, this application embodiment allows the PCC device to perform the activation operation for target slice resource reservation without relying on continuous online interaction capabilities at the control plane. This application embodiment solves the problem of poor slice resource management efficiency caused by low slice resource configuration efficiency in related technologies, thereby improving slice resource management efficiency. Attached Figure Description

[0014] Figure 1 This is a schematic diagram of the architecture of a satellite communication system according to an embodiment of this application;

[0015] Figure 2 This is a flowchart of a method for configuring satellite network slice resources according to an embodiment of this application;

[0016] Figure 3 This is a schematic diagram of a CCI object management process according to an embodiment of this application;

[0017] Figure 4 This is a schematic diagram of the CCI object message format according to an embodiment of this application;

[0018] Figure 5 This is a flowchart of another method for configuring satellite network slice resources according to an embodiment of this application;

[0019] Figure 6 This is an architecture diagram of a system for the timed activation of satellite network slice resource reservation according to an optional embodiment of this application;

[0020] Figure 7 This is a schematic diagram of the management process of a CCI object in related technologies;

[0021] Figure 8 This is a schematic diagram of the structure of the timed effective slice resource reservation configuration message according to an optional embodiment of this application;

[0022] Figure 9 This is a schematic diagram of the dynamic slice resource reservation instruction interaction process between the PCE device and the PCC device, which is led by the PCC device according to an optional embodiment of this application.

[0023] Figure 10 This is a structural block diagram of a satellite network slice resource configuration device according to an embodiment of this application;

[0024] Figure 11 This is a structural block diagram of a configuration apparatus for satellite network slice resources according to an embodiment of this application;

[0025] Figure 12 This is an architecture diagram of a satellite network slice resource configuration system according to an embodiment of this application. Detailed Implementation

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

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

[0028] According to one aspect of the embodiments of this application, a method for configuring satellite network slice resources is provided. Optionally, in this embodiment, the above-described method for configuring satellite network slice resources may include, but is not limited to, applications such as... Figure 1 The diagram shows the architecture of a satellite communication system. This satellite communication system may include a satellite 101, terminal equipment 102, and gateway station 103.

[0029] In this application, satellite 101 is an entity used for transmitting or receiving signals, and there can be multiple satellites. The embodiments of this application do not limit the specific technology or equipment form used in the satellites.

[0030] In this application's embodiments, the terminal device 102 refers to a processing device used for communication with a satellite within the satellite's coverage beam range. For example, the terminal can be a car, smart car, mobile phone, wearable device, tablet computer, etc., equipped with satellite communication capabilities. This application's embodiments do not limit the specific technology or device form used in the terminal. It should be noted that... Figure 1 The example uses two terminal devices 102.

[0031] In one embodiment of this application, the gateway station 103 in this example is connected to satellite 101.

[0032] In this application's embodiments, the gateway station 103 is a ground-based node in a satellite communication system used for transmitting and receiving data. The embodiments of this application do not limit the specific technology or equipment form employed by the gateway station.

[0033] It is understood that the satellite communication system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0034] This embodiment provides a method for configuring satellite network slice resources running on the aforementioned mobile terminal, applied to PCC devices. Figure 2 This is a flowchart of a satellite network slice resource configuration method according to an embodiment of this application, such as... Figure 2 As shown, the process includes the following steps:

[0035] Step S202: Receive a configuration instruction sent by the path calculation unit PCE device, wherein the configuration instruction is generated by the PCE device based on network topology information and service requirement information within the service time period, and includes at least the target slice path corresponding to the target slice resource required by the PCE device, and the target timed activation parameter for reserving the target slice resource.

[0036] In this context, the PCE device is a network controller, and the PCC device is a spaceborne router and a ground router. The target timing activation parameter indicates the reserved timing activation configuration information for the target slice resources. The target slice path is the slice path corresponding to the service time period calculated by the PCE device based on network topology, link bandwidth, power supply switching, and other information within the service time period (e.g., the future T0 time period, where T0 time period is a time period from start to end, and T0 time period is the service time period). For example, the PCE device uses the Constraint-Based Shortest Path First (CSPF) algorithm combined with network topology, link bandwidth, latency, and power supply switching information to calculate the required slice path, and then determines the slice resources corresponding to the slice path based on protocol rules.

[0037] Step S204: Reserve the target slice resources within the business time period according to the target slice path and the target timed activation parameters.

[0038] Through the above steps, the PCC device receives an instruction from the PCE device, generated by the PCE device based on network topology information and service requirements within the service time period. This instruction includes at least the target slice path corresponding to the target slice resource required by the PCE device, and target timing activation parameters for reserving the target slice resource. The PCC device then reserves the target slice resource within the service time period according to the target slice path and target timing activation parameters. In other words, in this embodiment, the PCC device performs the activation operation for target slice resource reservation without relying on continuous online interaction capabilities at the control plane. This embodiment solves the problem of poor slice resource management efficiency caused by low slice resource configuration efficiency in related technologies, thereby improving slice resource management efficiency.

[0039] In an exemplary embodiment, the configuration instruction includes slice resources corresponding to all slice paths within the business time period under different time windows, and the slice resources corresponding to all slice paths within the business time period under different time windows include at least the target slice resource.

[0040] It is understandable that a business requirement may require the use of multiple slice paths in segments to ensure business continuity due to dynamic changes in satellite topology during the business period (e.g., inter-satellite link switching, power supply link reconstruction, solar interference, etc.). Therefore, the above configuration instructions need to include: the slice resources corresponding to all slice paths that need to be activated sequentially within the business period covered by a business requirement.

[0041] In an exemplary embodiment, reserving the target slice resources within a service time period based on the target slice path and the target timing activation parameter includes: determining the target slice resources based on the network bandwidth resources corresponding to the target slice path before reaching the reservation start time corresponding to the target timing activation parameter, and reserving the target slice resources for the target slice path in advance.

[0042] It is understandable that after receiving the target slice path and the target timing activation parameters, the PCC device can reserve bandwidth resources in advance before the agreed time (i.e., the reserved start time).

[0043] In one exemplary embodiment, the method further includes: when it is necessary to switch the target slice path, switching the target slice path to a preset slice path based on the target slice resource, wherein the preset slice path represents the slice path to which the target slice path is about to be switched.

[0044] Understandably, when a slice path switch is required, the PCC device automatically enables resource reservation protection according to the timed effective configuration, switches the target slice path to the preset slice path, and achieves lossless service switching when the power supply link is switched, without having to rely on the PCE device.

[0045] In one exemplary embodiment, the method further includes: determining a configuration relationship between a slice path and network bandwidth resources according to a resource configuration protocol; and determining the network bandwidth resources corresponding to the target slice path according to the configuration relationship.

[0046] It is understood that the above resource configuration protocol is the PCEP protocol. The PCEP protocol is a bidirectional interactive protocol, a dynamic protocol based on the variable type-length-value (TLV) encoding. The PCEP protocol supports the reservation, distribution, and status feedback of satellite network slice resources, and supports efficient encoding and parsing at both ends of the communication, with an effective time of seconds, meeting the requirements for rapid configuration and distribution of satellite network slice resource reservations.

[0047] In an exemplary embodiment, the target timing activation parameter is carried by a Central Controller Instruction (CCI) object in the configuration instruction. The method further includes: determining the total timing activation parameter carried by the CCI object, wherein the total timing activation parameter represents the timing activation parameter corresponding to all slice paths in different time windows within the business time period, and all slice paths include at least the target slice path; and determining the target timing activation parameter from the total timing activation parameter.

[0048] Understandable, Figure 3 This is a schematic diagram of a CCI object management process according to an embodiment of this application, such as... Figure 3 As shown:

[0049] (1) CCI object creation process led by PCC device: After the PCC device receives the CCI object issued by the PCE device, which includes timing parameters (Start-Time = T0) and autonomous execution flag (C-bit = 1) (the issued instruction is: Initiate LSP.CCI: PCInitiate, A = 0, C = 1, Start-Time = T0), it autonomously completes the LSP establishment and resource reservation operation (PCRpt, PLSP_ID = 1, D = 1) at time T0. After completing the operation, it reports to the PCE device that the operation has been completed (Confirm Initiate) to achieve state synchronization between the control plane and the execution plane.

[0050] (2) CCI object activation process led by PCC device: PCC device automatically activates CCI at T0 and feeds back the status of CCI object to PCE device (feedback status is: PCRpt, A=1).

[0051] (3) PCC device-led CCI object deletion process: PCC automatically deletes CCI objects after the expiration period and reports the status of the deleted CCI objects to PCE device (the reported status is: PCRpt (No SCHED-LSP-ATTRIBUTE TLV)).

[0052] Figure 4 This is a schematic diagram of the CCI object message format according to an embodiment of this application, such as... Figure 4 As shown, a CCI object includes: a general CCI object header, a CCI object message carrying slice configuration information, and a CCI object message carrying time-varying slice configuration information. The following is an explanation of each field in the relevant CCI object messages:

[0053] (1) Object-Class: Identifies the class to which an object belongs.

[0054] (2) OT (Object Type): Combined with the object class, it precisely defines the object type.

[0055] For example, OT can be represented as: 1) OT=1, which means creation and timed activation; 2) OT=2, which means deletion and timed release; 3) OT=3, which means updating the timed activation parameters.

[0056] (3) Res (reserved bit): It must usually be set to 0 and is ignored by the receiver.

[0057] (4) P (Processing Rule Bit): When the P flag is set (e.g., set to 1), the object must be considered by the PCE (i.e., must be processed). Conversely, when the P flag is cleared, the object is optional and the PCE can ignore it.

[0058] In the embodiments of this application, for all timed CCI instructions, the P-bit must be set (e.g., P is set to 1) to ensure that even if the controller is offline, the PCC must remember the instruction and execute it at the specified time.

[0059] (5) I (Ignore bit): When the I flag is set (e.g., set to 1), the object should be ignored. Conversely, when the I flag is cleared, the receiver needs to process the object.

[0060] (6) Object Length: The total length of the entire object (in bytes).

[0061] (7) CC-ID (CCI identifier): A globally unique central controller identifier assigned by PCEP, assigned by PCE, unique within PCE, with a value range of 1-0xFFFFFFFE.

[0062] (8) Reserved1: A reserved bit field in the general header of CCI objects with no defined purpose. In this application embodiment, no function of Reserved1 is used. It is reserved for future expansion and must be set to 0.

[0063] (9) Flags: A set of bits used to indicate specific options or states, used to carry optional control semantics, such as whether to require confirmation, whether to encrypt, whether to have high priority, whether to forward across satellites, etc.

[0064] For example: Flag[0]=1 means that the PCC device is required to send an ACK (Acknowledgment) to the PCE device after execution; Flag[2]=1 means that the resource reservation operation needs to be bound to the power switching policy.

[0065] (10) C (PCC allocation bit): When the allocation bit (i.e. C) is the preset allocation bit value, the tag is allocated.

[0066] The preset allocation bit value can be 1.

[0067] In other words, if C is set to 1, it indicates that for CCI instructions, tag allocation needs to be completed by the PCC. The PCE device sets C to request the PCC to allocate a tag from the tag space in the PCC device. The PCC device sets C to indicate that the PCC device has allocated the tag and reports the allocated tag to the PCE.

[0068] (11) O (Outgoing Tag Position): If O is set to 1, it indicates that this tag is an outgoing tag and the next-hop information must be encoded in the CCI object. If O is not set (i.e., O=0), it indicates that this tag is an incoming tag and the local interface information can be encoded in the CCI object via the address TLV.

[0069] The incoming label is the label carried by the data packet received from the upstream node, which is used to determine which interface to forward from; the outgoing label is the new label that will be replaced when the current node sends the data packet to the downstream node, which is used to determine which next hop to forward to.

[0070] (12) Label: Usually refers to the label in the data plane, which is used to carry the label value actually used for packet forwarding. For example: when C=1: the Label field is optional, because the PCC will allocate the label automatically, and the Label field can be empty at this time; when C=0: the Label field must exist, the label is specified by the PCE, and the PCC applies it directly.

[0071] (13) Reserved2: Unused, reserved bits for future expansion. This application embodiment does not use Reserved2 and must set Reserved2 to 0. If new functions are needed in the future (e.g., whether to encrypt, whether to cross domain, etc.), Reserved2 can be reused.

[0072] (14) Type: Indicates the type of TLV (type-length-value) or sub-object.

[0073] Type identifies the semantics of TLV, for example: Type=1: Start-Time, Type=2: Duration, etc.

[0074] (15) Length: Represents the length of the TLV or sub-object value (in bytes).

[0075] (16) Flags: Another set of flags.

[0076] (17) B (Executor Identifier): When the executor identifier is a preset execution bit value, the target slice resource is reserved.

[0077] The preset execution bit value is 1. That is, if B is set to 1, it means that the PCC device is responsible for establishing and dismantling the reserved resource configuration according to the start time and duration. If B is set to 0, it means that the PCE device is responsible for establishing and dismantling the reserved resource configuration according to the start time and duration.

[0078] (18) R (time reference bit): When the time reference bit is a preset reference bit value, clock calibration is performed on the PCC device and the PCE device.

[0079] The default reference value can be 1. That is, if R is set to 1, the start time is a relative time, i.e., the number of seconds counted from the current time. When using relative time, PCE and PCC devices need to synchronize their clocks. Network Time Protocol (NTP) can be used to ensure clock synchronization between PCE and PCC devices. If R is set to 0, the start time is an absolute time, i.e., the number of seconds elapsed since the origin time. For example, the origin time is defined as January 1, 1970, 00:00 UTC (Coordinated Universal Time). This 32-bit field cycles approximately every 232 seconds (about 136 years), with the next cycle occurring in 2106. If the received start time value, after the cycle (i.e., the calculated result), is less than the current time, the start time will be considered to be the time since the last cycle point (because the start time always points to a future point in time).

[0080] (19) Start-Time: The time when the CCI object is scheduled to be created and activated. When the R flag is 1, transmission delay needs to be considered.

[0081] (20) Duration: The duration for which a CCI object remains active and has its resources reserved. After the duration expires, the CCI object will be demolished and deleted. Duration must not be 0 and should be greater than the minimum duration (e.g., 5 seconds).

[0082] Optionally, a start-time field and a duration field are determined from the time-varying information message, wherein the start-time field indicates the start time of the service time period, and the duration field indicates the duration for reserving the target slice resources required by the PCE device; the reserved start time corresponding to the target timing activation parameter is determined based on the start time and the duration, wherein the time period between the start time and the reserved start time is greater than the duration.

[0083] (21) A (Activation status bit): If A is set to 1, it means that the CCI object is activated.

[0084] (22) G (boundary type bit): This is not used in the embodiments of this application, and G is set to 0.

[0085] (23) Reserved: This is not used in the embodiments of this application and must be set to 0. The receiving end must ignore Reserved.

[0086] In one exemplary embodiment, the method further includes: automatically deleting the target timing parameter and releasing the target slice resource when the reserved end time corresponding to the target timing parameter is reached.

[0087] It is understandable that all PCC devices along the route will automatically delete the resource reservation configuration and release network bandwidth resources after the effective time of the configuration expires (i.e., the reservation end time is reached) during the business period.

[0088] This embodiment also provides another method for configuring satellite network slice resources running on the aforementioned mobile terminal, applied to PCE devices. Figure 5 This is a flowchart of another satellite network slice resource configuration method according to an embodiment of this application, such as... Figure 5 As shown, the process includes the following steps:

[0089] Step S502: Generate a configuration instruction based on the network topology information and service requirement information within the service time period. The configuration instruction includes at least the target slice path corresponding to the target slice resource required by the PCE device, and the target timed activation parameter for reserving the target slice resource.

[0090] Step S504: Send the configuration command to the PCC device so that the PCC device reserves the target slice resources during the service time period according to the target slice path and the target timing activation parameters.

[0091] Through the above steps, based on the network topology information and service requirement information within the service period, a configuration instruction is generated that includes at least the target slice path corresponding to the target slice resources required by the PCE device, and a timed activation parameter for reserving the target slice resources. The configuration instruction is then sent to the PCC device, enabling the PCC device to reserve the target slice resources within the service period according to the target slice path and the target timed activation parameter. In other words, this embodiment of the application involves the PCE device sending a configuration instruction to the PCC device to enable the PCC device to perform the activation operation of the target slice resource reservation, without relying on continuous online interaction capabilities at the control plane. This embodiment of the application solves the problem of poor slice resource management efficiency caused by low slice resource configuration efficiency in related technologies, thereby improving slice resource management efficiency.

[0092] In an exemplary embodiment, the network topology information includes at least the network topology between the PCC device and the PCE device, and the service requirement information includes at least one of the following: link bandwidth, link latency, link attribute information, and power supply switching information. Generating configuration instructions based on the network topology information and service requirement information within a service time period includes: combining a path algorithm with the network topology and at least one of the link bandwidth, link latency, link attribute information, and power supply switching information to generate the configuration instructions.

[0093] The aforementioned network topology is used to indicate the connection relationships and path reachability between PCC devices and PCE devices during the service period.

[0094] It is understandable that the process of generating configuration instructions relies on a path algorithm, such as the CSPF algorithm. In this embodiment, the PCE device generates configuration instructions based on the CSPF algorithm, combined with network topology and service requirement information.

[0095] Among them, the CSPF algorithm intelligently selects the shortest path from the source node to the destination node under the premise of meeting hard constraints such as bandwidth, latency and power supply switching, providing a highly reliable and low-latency transmission channel for network slicing.

[0096] Constraints include, but are not limited to: 1) Available bandwidth: The remaining bandwidth of each link on the slice path is ≥ the required bandwidth; 2) Maximum latency: The total latency of the slice path is ≤ the preset maximum latency threshold; 3) Link attributes (e.g., whether it is fiber optic, whether it crosses regions, whether it is a high-reliability link, etc.); Power Feeding Switching Info (special scenarios): For example, in 5G wireless access networks or energy sensing networks, the path must support power switching (e.g., switching from main power to backup power / battery power) to ensure that critical services can still operate when power is lost.

[0097] The execution process of the CSPF algorithm includes: 1) Initialization: Starting from the source node, set the distance to 0, and set other nodes to infinity; 2) Constraint filtering: Exclude all links with available_bandwidth < 100Mbps and all links with power_switching_support == false; 3) Shortest path search: Use an improved Dijkstra algorithm, considering only links that meet the above constraints; accumulate the link costs (e.g., total latency) to find the shortest path from source to destination; 4) Path verification: Calculate the total latency of the entire slice path, ensuring the total latency of the slice path is ≤ 10ms, and verify that all links on the slice path meet the bandwidth and power switching requirements; 5) Output results: If a slice path that meets the conditions exists, return that slice path as the logical transmission path of the slice; if no slice path that meets the conditions exists, trigger resource reallocation, link expansion, or request service degradation; 6) Path binding and resource reservation: Bind the selected slice path through a software-defined network (Software-Defined Networking)... The Networking (SDN) controller distributes information to network devices, reserving bandwidth, latency priority queues, and power switching policies on the slice path; and establishing end-to-end network slice instances (e.g., SRv6 tunnels + QoS policies (tunnel encapsulation mechanism based on IPv6 segmented routing and corresponding quality of service policies)).

[0098] In one exemplary embodiment, the configuration instructions include slice resources corresponding to all slice paths within the business time period under different time windows, and timed activation parameters corresponding to all slice paths within the business time period under different time windows.

[0099] Understandably, the configuration command includes not only the slice resources corresponding to all slice paths within the business time period, but also the timed activation parameters for each slice path under different time windows. After receiving the configuration command, the PCC device activates or releases resources at the specified time point according to the timed activation parameters, without requiring the control plane to be continuously online.

[0100] In an exemplary embodiment, each slice path in all slice paths has a mapping relationship with a topology node in the network topology structure, and all slice paths include at least the target slice path corresponding to the topology node where the PCC device is located. The slice resources corresponding to all slice paths in different time windows during the service time period include at least the target slice resources.

[0101] It is understood that, within a business time period, all slice paths must include at least one target slice path with a PCC device as the starting point, ending point, or key node. Target slice resources are allocated to the target slice path within the corresponding time window. Through the embodiments of this application, it is ensured that the PCC device can obtain complete slice resource support during the effective period of the slice path it participates in, achieving continuous and reliable transmission of business data under highly dynamic topologies.

[0102] In an exemplary embodiment, the configuration instruction carries a Central Controller Instruction (CCI) object and sends the configuration instruction to the PCC device, including: sending the configuration instruction to the PCC device through the CCI object, wherein the CCI object carries a total timing activation parameter, wherein the total timing activation parameter represents the timing activation parameter corresponding to all slice paths under different time windows within the service time period, and the total timing activation parameter includes at least the target timing activation parameter.

[0103] The aforementioned total timed activation parameter is: in the CCI object, it centrally carries all timed activation information corresponding to all slice paths within the business time period.

[0104] In one exemplary embodiment, the CCI object also carries the allocation bit of the PCC device, and the method further includes: setting the allocation bit value of the allocation bit for the PCC device to instruct the PCC device to perform tag allocation.

[0105] Among them, the above-mentioned allocation bits are Figure 4 C in the middle.

[0106] In an exemplary embodiment, the CCI object also carries a time-varying information message, and the method further includes: setting the execution bit value of the executor identifier bit for the PCC device to instruct the PCC device to reserve the target slice resource.

[0107] Among them, the aforementioned executor identifier is Figure 4 B in the middle.

[0108] For example, when B=1, it means that the PCC device is responsible for establishing and dismantling the reserved resource configuration according to the start time and duration, that is, the PCC device reserves the target slice resources; when B=0, it means that the PCE device is responsible for establishing and dismantling the reserved resource configuration according to the start time and duration.

[0109] In one exemplary embodiment, the method further includes: setting a start time field and a duration segment field in the time-varying information message, wherein the start time field is used to indicate the start time of the service time period, and the duration segment field is used to indicate the duration for reserving the target slice resources required by the PCE device.

[0110] Among them, the above-mentioned start time field is Figure 4 In the context of Start-Time, the aforementioned duration field is... Figure 4 The word in the text is "Duration".

[0111] In one exemplary embodiment, the method further includes setting a time reference bit in the time-varying information message to instruct the PCC device and the PCE device to perform clock calibration.

[0112] The aforementioned time base is namely Figure 4 R in the text.

[0113] For example, when R=1, it means that clock calibration is required for both the PCC device and the PCE device to synchronize their clocks.

[0114] Obviously, the embodiments described above are only some embodiments of this application, and not all embodiments. To better understand the above method for configuring satellite network slice resources, the process is described below with reference to embodiments, but this is not intended to limit the technical solutions of the embodiments of this application. Specifically:

[0115] The following problems exist in related technologies: Space networks are characterized by large spatiotemporal scales, high-frequency and time-varying topologies, and limited onboard resources such as bandwidth and switching. To ensure the availability of slice paths, reduce the CPU utilization of onboard routers, and improve network resource utilization, efficient deployment and recycling of satellite network slices are required. The Network Configuration Protocol (NetConf), due to its persistent configuration method, has an effective time on the order of minutes, which cannot meet the high-frequency deployment requirements of satellite network slices. Although the PCEP protocol can achieve dynamic high-frequency deployment of satellite network slice configurations, it highly relies on continuous online interaction of the control plane. In a satellite network environment, if the control unit goes offline due to satellite-to-ground link interruption, delay, or node failure, the PCEP protocol will be unable to reliably deploy and maintain the configuration, leading to slice management interruption and affecting the timely effectiveness and recycling efficiency of slices.

[0116] To address the issues of slow NetConf protocol activation and inability to adapt to the highly dynamic characteristics of satellites, while the standard PCEP protocol supports dynamic deployment, it relies on the continuous online status of the control plane, making it unsuitable for satellite-to-ground link terminal scenarios. This application proposes an optional embodiment of a method and system for the timed activation of satellite network slice resource reservation. This optional embodiment uses the PCEP protocol as its underlying framework, extending it to meet the requirements of space network slicing. This enables the deployment of satellite network slice resource configurations that can automatically activate at a specified time, and supports autonomous execution by the control party in offline scenarios, thus adapting to the network characteristics of space scenarios. Specifically:

[0117] Figure 6 This is an architecture diagram of a system for the timed activation of satellite network slice resource reservation according to an optional embodiment of this application, such as... Figure 6 As shown, the system includes network elements such as a network controller (a PCE device), spaceborne routers, and terrestrial routers (PCC devices). The network controller establishes connections with the spaceborne and terrestrial routers using Transmission Control Protocol / Internet Protocol (TCP / IP) as the network transmission technology for the space and terrestrial bearer networks.

[0118] (1) Network Controller: Deployed at the ground operation and control center, responsible for distributing network slice-related configurations to each routing node;

[0119] (2) Satellite-borne router: Deployed on the satellite, it is mainly responsible for reserving and releasing resources according to the slice resource reservation configuration information issued by the network controller, and routing and forwarding data. When the satellite cannot directly land through the feeder link, the satellite-borne router forwards the data to the satellite that can land and sends it to the ground network.

[0120] (3) Ground router: Deployed in the ground gateway station, it is mainly responsible for reserving and releasing resources according to the slice resource reservation configuration information issued by the network controller, and routing and forwarding data. It serves as a unified traffic exit device between the network space segment and the ground segment.

[0121] In an optional embodiment of this application, the PCE device can proactively initiate a timed activation creation process for network slice resource reservation based on the Stateful PCE (Stateful Path Calculation Unit) mechanism. It is responsible for centrally calculating the optimal path for the network slice based on information such as the satellite network topology, link bandwidth, and power supply switching plan for a future time period T (i.e., the service time period), and generating a resource reservation instruction (i.e., a configuration instruction) containing timed activation information.

[0122] PCC devices (PCC devices are execution nodes in the network) can receive slice resource reservation configuration instructions sent by PCE devices through extended CCI objects, and autonomously activate or release resources at specified time points.

[0123] The maintenance and teardown process for resource reservations varies depending on the setting of the executor identifier bit (C-bit):

[0124] (1) When C-bit is set to 0, the activation and removal process of resource reservation is led by the PCE device, such as Figure 7 As shown:

[0125] 1) PCE devices can generate Label Switched Paths (LSPs) based on future topology predictions. Establishing LSPs enables network slice resource reservation. Specifically, the process for establishing a Label Switched Path (LSP) initiated by a PCE device is as follows:

[0126] First, the PCE device actively requests the PCC device to establish an LSP (Initiate LSP): the PCE device actively sends a message (PCInitiate) to the PCC device.

[0127] Secondly, the PCE device confirms the initiation of the LSP establishment process: the PCC device establishes the LSP and reports the established message to the PCE device (PCRpt, PLSP_ID=1, D=1).

[0128] 2) LSP maintenance process initiated by PCE equipment:

[0129] First, the PCE device updates the tag exchange path: the PCE device sends an update message (PCUpd, PLSP_ID=1) to the PCC device.

[0130] Secondly, the PCE device confirms the update of the LSP: the PCC device sends a report message (PCRpt, PLSP_ID=1, D=1) to the PCE device to confirm that the LSP has been executed according to the timed instructions.

[0131] 3) LSP removal process initiated by PCE equipment:

[0132] First, the PCE device initiates the deletion of the tag exchange path (Delete LSP): The PCE device sends a message to the PCC device to report the LSP to be deleted on a scheduled basis. The path LSP identifier is 1 and the scheduled deletion confirmation bit is 1 (PCInitiate, PLSP_ID=1, R=1).

[0133] Secondly, the PCE device confirms the deletion (Confirm delete) LSP: The PCC device reports a message to the PCE device to confirm that the timed deletion is complete. The path LSP identifier is 1, and the timed deletion confirmation bit is 1 (PCRpt, PLSP_ID=1, R=1).

[0134] (2) When C-bit is set to 1, the PCC device is responsible for performing the activation and teardown operations of resource reservations and feeding back the execution results to the PCE device through the PCInitiate message. By setting C-bit to 1, the PCC device's autonomous control capability in dynamic network environments is enhanced, and the adaptability and response efficiency of slice deployment are improved.

[0135] In the current standardized (RFC8281 defined) Stateful Path Computation Element (SPCE model), the PCE device can proactively initiate the creation, modification, and deletion of LSPs. These operations are executed entirely by the PCE device issuing commands directly to the PCC device via the PCEP protocol. The PCC device itself does not need to pre-configure any LSP parameters (e.g., source address, destination address, bandwidth, etc.) locally. The optional embodiment of this application extends the PCEP protocol, utilizing the Stateful PCE model to implement a dynamic slice resource reservation command interaction process initiated by the PCC device between the PCE and PCC devices (the PCC device has the ability to execute autonomously at a set time when C-bit=1). Furthermore, by adding a timed activation mechanism (e.g., CCI object and timed activation attribute type-length-value (SCHED-LSP-ATTRIBUTE TLV)), it supports automatic resource reservation and release at predetermined times even in highly dynamic satellite networks and environments prone to satellite-to-ground link interruptions, thereby achieving reliable, efficient, and autonomous management of slice resources.

[0136] The following is a description of the newly added timed activation mechanism in the optional embodiments of this application:

[0137] In an optional embodiment of this application, a new PCELSP Object (LSP object of PCE device) SCHED-LSP-ATTRIBUTE TLV ("Timed Effectiveness Attribute" type-length-value) is defined in [RFC8934] (Standard Carrier for Timed Effectiveness Function) to issue timed effectiveness configuration. Meanwhile, [RFC9050] (CCI for PCEP) extends the Stateful PCEP defined in [RFC8231] (Stateful PCEP Extension), defining a new PCEP Object CCI object (CCI object of PCEP) to carry instructions other than the central controller LSP. Figure 8 This is a schematic diagram of the structure of the timed-effective slice resource reservation configuration message according to an optional embodiment of this application, such as... Figure 8 As shown, the timed-effective slice resource reservation configuration message includes: Ethernet header, IP header, TCP header, PCEP header, and PCEP body (i.e., the PCEP message body, which includes: SRP OBJECT (standard object for requesting identification), LSP OBJECT (label switching path object), and CCI OBJECT (central controller instruction object)). The PCEP message body carries the extended CCI object.

[0138] The timed activation configuration for reserved satellite network slice resources is carried out and distributed through a newly extended CCI object. Timed activation is achieved by reusing the SCHED-LSP-ATTRIBUTE TLV format in the newly defined CCI object to carry time-varying information.

[0139] For example, the following is an example of the dynamic slice resource reservation instruction interaction process initiated by the PCC device between the PCE device and the PCC device, such as... Figure 9 As shown:

[0140] (1) PCE equipment is based on the future T0 time period (i.e. Figure 9 The network topology, link bandwidth, and power supply switching information of the T0 time slice in the system are used to calculate all slice paths corresponding to a time period (T0 time period) of a service requirement. Each path consists of multiple satellite routers and ground router nodes.

[0141] For example, the highly dynamic changes in network topology in low-Earth orbit satellite internet are mainly caused by solar outages and the high-speed relative motion between satellite and ground, leading to dynamic changes in inter-satellite / satellite-ground topology. PCE devices can calculate the network topology for time period T based on solar outage information and satellite-to-ground feeder link establishment plans. Based on the network topology of time period T (i.e., the service time period), and combined with service requirements (such as link bandwidth and latency), slice paths are calculated. Within a service time period, there may be N slice paths (the number of slice paths is positively correlated with the length of time period T; a one-hour service requirement may require changes to 20 slice paths to ensure availability). By leveraging the predictability of satellite network topology, PCE devices can distribute N network slice resource configurations for time period T at once and make them effective on a scheduled basis, ensuring the availability of slice paths, reducing the CPU utilization of onboard routers, and improving network resource utilization.

[0142] (2) The PCE device sends slice resource reservation timed activation configuration information (i.e. slice resources) for different time windows to all nodes along the route during the T0 time period through PCEP. The slice resource reservation timed activation configuration information for different time windows is sent to the PCC device based on CCI. CCI includes at least: timed activation parameters.

[0143] (3) After receiving the information sent by the PCE device, the PCC device reserves bandwidth resources in advance before the agreed time (i.e., the reserved start time). When path switching is required, the PCC device will automatically enable resource reservation guarantee according to the timed effective configuration.

[0144] (4) All PCC devices along the route during the T0 time period will automatically delete the resource reservation configuration and release network bandwidth resources after the effective time of the configuration expires (i.e., the reservation end time).

[0145] In summary, compared to the standard PCEP protocol's dynamic slice distribution, which heavily relies on the control plane remaining online, the optional embodiments of this application, by introducing extended mechanisms such as effective time, grant PCC devices autonomous execution rights in specific scenarios. When the PCE device is offline, the PCC device can still autonomously complete resource reservation or release operations at an agreed time point according to pre-issued instructions. Thus, the optional embodiments of this application significantly improve the robustness and reliability of slice management in intermittent connection environments.

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

[0147] This embodiment also provides a satellite network slice resource configuration device, which is used to implement the above embodiments and preferred embodiments, and will not be repeated as already described. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0148] Figure 10 This is a structural block diagram of a satellite network slicing resource configuration device according to an embodiment of this application, applied to a PCC device, such as... Figure 10 As shown, the device includes:

[0149] The receiving module 1002 is used to receive a configuration instruction sent by the PCE device. The configuration instruction is generated by the PCE device based on the network topology information and service requirement information within the service time period. It includes at least the target slice path corresponding to the target slice resource required by the PCE device, and the target timed activation parameter for reserving the target slice resource.

[0150] The reservation module 1004 is used to reserve the target slice resources within the business time period according to the target slice path and the target timed activation parameters.

[0151] Through the aforementioned apparatus, the PCC device receives an instruction from the PCE device, generated by the PCE device based on network topology information and service requirement information within a service time period. This instruction includes at least the target slice path corresponding to the target slice resource required by the PCE device, and target timing activation parameters for reserving the target slice resource. The PCC device then reserves the target slice resource within the service time period according to the target slice path and the target timing activation parameters. In other words, in this embodiment, the PCC device performs the activation operation for the target slice resource reservation without relying on continuous online interaction capabilities at the control plane. This embodiment solves the problem of poor slice resource management efficiency caused by low slice resource configuration efficiency in related technologies, thereby improving slice resource management efficiency.

[0152] In an exemplary embodiment, the configuration instruction includes slice resources corresponding to all slice paths within the business time period under different time windows, and the slice resources corresponding to all slice paths within the business time period under different time windows include at least the target slice resource.

[0153] In an exemplary embodiment, the reservation module 1004 is further configured to reserve the target slice resources within a service time period according to the target slice path and the target timing activation parameter, including: determining the target slice resources according to the network bandwidth resources corresponding to the target slice path before reaching the reservation start time corresponding to the target timing activation parameter, and reserving the target slice resources for the target slice path in advance.

[0154] In an exemplary embodiment, the reservation module 1004 is further configured to switch the target slice path to a preset slice path based on the target slice resource when it is necessary to switch the target slice path, wherein the preset slice path represents the slice path to which the target slice path is about to be switched.

[0155] In an exemplary embodiment, the reservation module 1004 is further configured to determine the configuration relationship between the slice path and the network bandwidth resources according to the resource configuration protocol; and determine the network bandwidth resources corresponding to the target slice path according to the configuration relationship.

[0156] In an exemplary embodiment, the reservation module 1004 is further configured to determine the total timing activation parameters carried by the CCI object, wherein the total timing activation parameters represent the timing activation parameters corresponding to all slice paths under different time windows within the business time period, and all slice paths include at least the target slice path; and determine the target timing activation parameter from the total timing activation parameters.

[0157] In an exemplary embodiment, the reserved module 1004 is further configured to perform tag allocation when the allocation bit is a preset allocation bit value.

[0158] In an exemplary embodiment, the reservation module 1004 is further configured to determine the executor identifier bit of the PCC device from the time-varying information message; and reserve the target slice resource if the executor identifier bit is a preset execution bit value.

[0159] In an exemplary embodiment, the reservation module 1004 is further configured to determine a start time field and a duration field from the time-varying information message, wherein the start time field is used to indicate the start time of the service time period, and the duration field is used to indicate the duration for reserving the target slice resources required by the PCE device; and to determine the reservation start time corresponding to the target timing activation parameter based on the start time and the duration, wherein the time period between the start time and the reservation start time is greater than the duration.

[0160] In an exemplary embodiment, the reserved module 1004 is further configured to determine a time reference bit from the time-varying information message; and, if the time reference bit is a preset reference bit value, to perform clock calibration on the PCC device and the PCE device.

[0161] In one exemplary embodiment, the apparatus further includes a deletion module, configured to automatically delete the target timing parameter and release the target slice resource when the reserved end time corresponding to the target timing parameter is reached.

[0162] Figure 11 This is a structural block diagram of another satellite network slice resource configuration apparatus according to an embodiment of this application, applied to a PCE device, such as... Figure 11 As shown, the device includes:

[0163] The generation module 1102 is used to generate configuration instructions based on network topology information and service requirement information within the service time period. The configuration instructions include at least the target slice path corresponding to the target slice resources required by the PCE device, and the target timed activation parameters for reserving resources for the target slice resources.

[0164] The sending module 1104 is used to send the configuration instruction to the PCC device so that the PCC device reserves the target slice resources during the service time period according to the target slice path and the target timed activation parameter.

[0165] According to the aforementioned apparatus, a configuration instruction is generated based on network topology information and service demand information within a service period. This instruction includes at least a target slice path corresponding to the target slice resources required by the PCE device, and a timed activation parameter for reserving the target slice resources. The configuration instruction is then sent to the PCC device, causing the PCC device to reserve the target slice resources within the service period according to the target slice path and the target timed activation parameter. In other words, this embodiment of the application involves the PCE device sending a configuration instruction to the PCC device to enable the PCC device to perform the activation operation of the target slice resource reservation, without relying on continuous online interaction capabilities at the control plane. This embodiment of the application solves the problem of poor slice resource management efficiency caused by low slice resource configuration efficiency in related technologies, thereby improving slice resource management efficiency.

[0166] In an exemplary embodiment, the network topology information includes at least the network topology structure between the PCC device and the PCE device, and the service requirement information includes at least one of the following: link bandwidth, link latency, link attribute information, and power supply switching information; the generation module 1102 is further configured to combine a path algorithm with the network topology structure and at least one of the link bandwidth, link latency, link attribute information, and power supply switching information to generate the configuration instruction.

[0167] In one exemplary embodiment, the configuration instructions include slice resources corresponding to all slice paths within the business time period under different time windows, and timed activation parameters corresponding to all slice paths within the business time period under different time windows.

[0168] In an exemplary embodiment, each slice path in all slice paths has a mapping relationship with a topology node in the network topology structure, and all slice paths include at least the target slice path corresponding to the topology node where the PCC device is located. The slice resources corresponding to all slice paths in different time windows during the service time period include at least the target slice resources.

[0169] In an exemplary embodiment, the sending module 1104 is further configured to send the configuration instruction to the PCC device through the CCI object, wherein the CCI object carries a total timing activation parameter, wherein the total timing activation parameter represents the timing activation parameter corresponding to each slice path in different time windows within the service time period, and the total timing activation parameter includes at least the target timing activation parameter.

[0170] In one exemplary embodiment, the CCI object also carries the allocation bit of the PCC device, and the apparatus further includes: an allocation module for setting the allocation bit value of the allocation bit for the PCC device to instruct the PCC device to perform tag allocation.

[0171] In an exemplary embodiment, the CCI object also carries a time-varying information message, and the allocation module is further configured to: set the execution bit value of the executor identifier bit for the PCC device to instruct the PCC device to reserve the target slice resource.

[0172] In an exemplary embodiment, the allocation module is further configured to: set a start time field and a duration segment field in the time-varying information message, wherein the start time field is used to indicate the start time of the service time period, and the duration segment field is used to indicate the duration for reserving the target slice resources required by the PCE device.

[0173] In an exemplary embodiment, the allocation module is further configured to: set a time reference bit in the time-varying information message to instruct the PCC device and the PCE device to perform clock calibration.

[0174] This embodiment also provides a satellite network slicing resource configuration system. Figure 12 This is an architecture diagram of a satellite network slicing resource configuration system according to an embodiment of this application, such as... Figure 12 As shown, the system includes: PCC device 1202 and PCE device 1204. The PCC device 1202 includes a satellite-borne router deployed on a satellite and a ground router deployed on the ground. The PCE device 1204 includes a network controller deployed on the ground.

[0175] The PCE device 1204 is used to generate configuration instructions based on network topology information and service requirement information within a service time period. The configuration instructions include at least the target slice path corresponding to the target slice resource required by the PCE device, and the target timed activation parameters for reserving the target slice resource.

[0176] The PCC device 1202 is used to receive configuration instructions sent by the PCE device; and to reserve the target slice resources within the service time period according to the target slice path and the target timing activation parameters.

[0177] According to the aforementioned system, based on network topology information and service requirement information within the service period, a configuration instruction is generated that includes at least the target slice path corresponding to the target slice resources required by the PCE device, and a timed activation parameter for reserving the target slice resources. The configuration instruction is then sent to the PCC device, causing the PCC device to reserve the target slice resources within the service period according to the target slice path and the target timed activation parameter. In other words, in this embodiment, the PCE device sends a configuration instruction to the PCC device to enable the PCC device to perform the activation operation of the target slice resource reservation, without relying on continuous online interaction capabilities at the control plane. This embodiment solves the problem of poor slice resource management efficiency caused by low slice resource configuration efficiency in related technologies, thereby improving slice resource management efficiency.

[0178] In an exemplary embodiment, the configuration instruction includes slice resources corresponding to all slice paths within the business time period under different time windows, and the slice resources corresponding to all slice paths within the business time period under different time windows include at least the target slice resource.

[0179] In an exemplary embodiment, the PCC device is further configured to determine the target slice resource based on the network bandwidth resource corresponding to the target slice path before the reserved start time corresponding to the target timing effective parameter is reached, and reserve the target slice resource for the target slice path in advance.

[0180] In an exemplary embodiment, the PCC device described above is further configured to switch the target slice path to a preset slice path based on the target slice resource when it is necessary to switch the target slice path, wherein the preset slice path represents the slice path to which the target slice path is about to be switched.

[0181] In an exemplary embodiment, the PCC device described above is further configured to determine the configuration relationship between the slice path and the network bandwidth resources according to the resource configuration protocol; and to determine the network bandwidth resources corresponding to the target slice path according to the configuration relationship.

[0182] In an exemplary embodiment, the PCC device described above is further configured to determine the total timing activation parameter carried by the CCI object, wherein the total timing activation parameter represents the timing activation parameter corresponding to all slice paths under different time windows within the service time period, and all slice paths include at least the target slice path; and determine the target timing activation parameter from the total timing activation parameter.

[0183] In one exemplary embodiment, the CCI object also carries the allocation bit of the PCC device, which is further configured to perform tag allocation when the allocation bit is a preset allocation bit value.

[0184] In an exemplary embodiment, the CCI object also carries a time-varying information message, and the PCC device is further configured to determine the executor identifier bit of the PCC device from the time-varying information message; and reserve the target slice resource when the executor identifier bit is a preset execution bit value.

[0185] In an exemplary embodiment, the PCC device is further configured to determine a start time field and a duration field from the time-varying information message, wherein the start time field is used to indicate the start time of the service time period, and the duration field is used to indicate the duration for reserving the target slice resources required by the PCE device; and to determine the reserved start time corresponding to the target timing activation parameter based on the start time and the duration, wherein the time period between the start time and the reserved start time is greater than the duration.

[0186] In an exemplary embodiment, the PCC device is further configured to determine a time reference bit from the time-varying information message; and, if the time reference bit is a preset reference bit value, to perform clock calibration on the PCC device and the PCE device.

[0187] In an exemplary embodiment, the PCC device is further configured to automatically delete the target timing parameter and release the target slice resource when the reserved end time corresponding to the target timing parameter is reached.

[0188] In an exemplary embodiment, the network topology information includes at least the network topology structure between the PCC device and the PCE device, and the service requirement information includes at least one of the following: link bandwidth, link latency, link attribute information, and power supply switching information. The PCE device is further configured to combine a path algorithm with the network topology structure and at least one of the link bandwidth, link latency, link attribute information, and power supply switching information to generate the configuration instruction.

[0189] In one exemplary embodiment, the configuration instructions include slice resources corresponding to all slice paths within the business time period under different time windows, and timed activation parameters corresponding to all slice paths within the business time period under different time windows.

[0190] In an exemplary embodiment, each slice path in all slice paths has a mapping relationship with a topology node in the network topology structure, and all slice paths include at least the target slice path corresponding to the topology node where the PCC device is located. The slice resources corresponding to all slice paths in different time windows during the service time period include at least the target slice resources.

[0191] In an exemplary embodiment, the PCE device is further configured to send the configuration instruction to the PCC device through the CCI object, wherein the CCI object carries a total timing activation parameter, wherein the total timing activation parameter represents the timing activation parameter corresponding to each slice path in different time windows within the service time period, and the total timing activation parameter includes at least the target timing activation parameter.

[0192] In one exemplary embodiment, the CCI object also carries the allocation bit of the PCC device, and the aforementioned PCE device is further configured to set the allocation bit value of the allocation bit for the PCC device to instruct the PCC device to perform tag allocation.

[0193] In an exemplary embodiment, the CCI object also carries a time-varying information message, and the PCE device is further configured to set the execution bit value of the executor identifier bit for the PCC device to instruct the PCC device to reserve the target slice resource.

[0194] In an exemplary embodiment, the PCE device described above is further configured to set a start time field and a duration segment field in the time-varying information message, wherein the start time field is used to indicate the start time of the service time period, and the duration segment field is used to indicate the duration for which the target slice resources required by the PCE device are reserved.

[0195] In one exemplary embodiment, the PCE device is further configured to set a time reference bit in the time-varying information message to instruct the PCC device and the PCE device to perform clock calibration.

[0196] It should be noted that the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to: all the above modules are located in the same processor; or, the above modules are located in different processors in any combination.

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

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

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

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

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

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

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

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

Claims

1. A method for configuring satellite network slice resources, characterized in that, Applied to path calculation client PCC devices, including: The PCE device receives a configuration instruction, which is generated by the PCE device based on network topology information and service requirement information within the service time period. The configuration instruction includes at least the target slice path corresponding to the target slice resource required by the PCE device, and the target timed activation parameter for reserving the target slice resource. Reserve the target slice resources within the business time period based on the target slice path and the target time-based activation parameters.

2. The method according to claim 1, characterized in that, The configuration instructions include the slice resources corresponding to all slice paths within the business time period under different time windows, and the slice resources corresponding to all slice paths within the business time period under different time windows include at least the target slice resource.

3. The method according to claim 1, characterized in that, Based on the target slice path and the target timing activation parameters, reserve the target slice resources within the business time period, including: Before the reserved start time corresponding to the target timed effective parameter is reached, the target slice resource is determined according to the network bandwidth resource corresponding to the target slice path, and the target slice resource is reserved in advance for the target slice path.

4. The method according to claim 3, characterized in that, The method further includes: When it is necessary to switch the target slice path, the target slice path is switched to a preset slice path based on the target slice resource, wherein the preset slice path represents the slice path to which the target slice path is about to be switched.

5. The method according to claim 3 or 4, characterized in that, The method further includes: The configuration relationship between slice paths and network bandwidth resources is determined according to the resource configuration protocol; The network bandwidth resources corresponding to the target slice path are determined based on the configuration relationship.

6. The method according to claim 3 or 4, characterized in that, The target timed activation parameter is carried by the Central Controller Instruction (CCI) object in the configuration instruction, and the method further includes: The total timing activation parameters carried by the CCI object are determined, wherein the total timing activation parameters represent the timing activation parameters corresponding to all slice paths under different time windows within the business time period, and all slice paths include at least the target slice path; The target timing activation parameter is determined from the total timing activation parameters.

7. The method according to claim 6, characterized in that, The CCI object also carries the allocation bits of the PCC device, and the method further includes: Tag allocation is performed when the allocation bit is a preset allocation bit value.

8. The method according to claim 6, characterized in that, The CCI object also carries a time-varying information message, and the method further includes: The execution identifier bit of the PCC device is determined from the time-varying information message; If the executor identifier is a preset execution bit value, the target slice resource is reserved.

9. The method according to claim 8, characterized in that, The method further includes: The start time field and duration segment field are determined from the time-varying information message, wherein the start time field is used to indicate the start time of the service time period, and the duration segment field is used to indicate the duration for reserving the target slice resources required by the PCE device; The reserved start time corresponding to the target timing activation parameter is determined based on the start time and the duration, wherein the time period between the start time and the reserved start time is greater than the duration.

10. The method according to claim 9, characterized in that, Before determining the reserved start time corresponding to the target timing activation parameter based on the start time and the duration, the method further includes: Determine the time reference bit from the time-varying information message; When the time reference position is a preset reference position value, clock calibration is performed on the PCC device and the PCE device.

11. The method according to claim 1, characterized in that, The method further includes: If the reserved end time corresponding to the target timed activation parameter is reached, the target timed activation parameter is automatically deleted and the target slice resource is released.

12. A method for configuring satellite network slice resources, characterized in that, Applied to path calculation unit (PCE) devices, including: Configuration instructions are generated based on network topology information and service requirement information within the service time period. The configuration instructions include at least the target slice path corresponding to the target slice resources required by the PCE device, and the target timed activation parameters for reserving resources for the target slice resources. The configuration command is sent to the PCC device so that the PCC device reserves the target slice resources during the service time period according to the target slice path and the target time-effective parameters.

13. The method according to claim 12, characterized in that, The network topology information includes at least the network topology between the PCC device and the PCE device, and the service requirement information includes at least one of the following: link bandwidth, link latency, link attribute information, and power supply switching information. Configuration instructions are generated based on the network topology information and service requirement information within the service time period, including: The configuration command is generated by combining the path algorithm with the network topology and at least one of the link bandwidth, link delay, link attribute information, and power supply switching information.

14. The method according to claim 13, characterized in that, The configuration instructions include the slice resources corresponding to all slice paths within the business time period under different time windows, and the timed activation parameters corresponding to all slice paths within the business time period under different time windows.

15. The method according to claim 14, characterized in that, Each slice path in all slice paths has a mapping relationship with a topology node in the network topology structure. All slice paths include at least the target slice path corresponding to the topology node where the PCC device is located. The slice resources corresponding to all slice paths in different time windows during the service period include at least the target slice resources.

16. The method according to claim 12, characterized in that, The configuration instruction carries a Central Controller Instruction (CCI) object and sends the configuration instruction to the PCC device, including: The configuration command is sent to the PCC device through the CCI object, wherein the CCI object carries a total timing effect parameter, wherein the total timing effect parameter represents the timing effect parameter corresponding to each slice path in different time windows within the service time period, and the total timing effect parameter includes at least the target timing effect parameter.

17. The method according to claim 16, characterized in that, The CCI object also carries the allocation bits of the PCC device, and the method further includes: Set the allocation bit value of the allocation bit for the PCC device to instruct the PCC device to perform tag allocation.

18. The method according to claim 16, characterized in that, The CCI object also carries a time-varying information message, and the method further includes: Set the execution bit value of the executor identifier bit for the PCC device to instruct the PCC device to reserve the target slice resources.

19. The method according to claim 18, characterized in that, The method further includes: The time-varying information message is configured with a start time field and a duration field, wherein the start time field is used to indicate the start time of the service time period, and the duration field is used to indicate the duration for reserving the target slice resources required by the PCE device.

20. The method according to claim 18, characterized in that, The method further includes: A time reference bit is set in the time-varying information message to instruct the PCC device and the PCE device to perform clock calibration.

21. A device for configuring satellite network slice resources, characterized in that, Applied to PCC devices, including: The receiving module is used to receive configuration instructions sent by the PCE device. The configuration instructions are generated by the PCE device based on network topology information and service requirement information within the service time period. They include at least the target slice path corresponding to the target slice resources required by the PCE device, and target timed activation parameters for reserving resources for the target slice resources. The reservation module is used to reserve the target slice resources within the business time period based on the target slice path and the target time-based activation parameters.

22. A device for configuring satellite network slice resources, characterized in that, Applied to PCE equipment, including: The generation module is used to generate configuration instructions based on network topology information and service requirement information within the service time period. The configuration instructions include at least the target slice path corresponding to the target slice resources required by the PCE device, and the target timed activation parameters for reserving resources for the target slice resources. The sending module is used to send the configuration command to the PCC device so that the PCC device reserves the target slice resources during the service time period according to the target slice path and the target timed activation parameters.

23. A satellite network slicing resource configuration system, characterized in that, The system includes PCC devices and PCE devices. The PCC devices include a satellite-based router deployed on a satellite and a ground-based router deployed on the ground. The PCE devices include a network controller deployed on the ground. The PCE device is used to generate configuration instructions based on network topology information and service requirement information within the service time period. The configuration instructions include at least the target slice path corresponding to the target slice resource required by the PCE device, and the target timed activation parameters for reserving the target slice resource. The PCC device is used to receive configuration instructions sent by the PCE device; and to reserve the target slice resources within the service time period according to the target slice path and the target timing activation parameters.

24. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein the program, when executed, performs the method described in any one of claims 1 to 20.

25. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method described in any one of 1 to 20.

Images