Network slice creation method and apparatus, storage medium, and electronic device
By using the PCEP protocol for network slicing creation in low-Earth orbit satellite communication systems, the problem of slow network slice configuration response has been solved, enabling second-level resource reservation and dynamic management, thereby improving the resource utilization and service continuity of satellite networks.
Patent Information
- Application Number
- CN202610930729.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-06-25
- Publication Date
- 2026-07-24
Smart Images
Figure CN122457536A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of satellite communications, and more specifically, to a method and apparatus for creating network slices, a storage medium, and an electronic device. Background Technology
[0002] With the large-scale deployment of low-Earth orbit satellite internet, the demand for communication services with global coverage, low latency, and high bandwidth is increasing, especially in vertical fields such as emergency command and energy monitoring, which place higher demands on the isolation, reliability, and quality of service (QoS) of dedicated communication channels. Network slicing technology, as a core means of achieving differentiated service capabilities, can build logically isolated virtual private networks for different business scenarios on the basis of a shared satellite-ground collaborative physical network. However, due to the dynamic characteristics of satellites, such as high-speed movement, frequent switching of inter-satellite links, and periodic interruptions of power supply links, traditional network slice configuration and distribution mainly uses the Network Configuration Protocol (Netconf). This has problems such as large distribution delays, slow response times, and uncontrollable states. Resource configuration typically takes several minutes to complete, making it difficult to match the minute-level or even second-level changes in satellite network topology. This leads to slice path failures, redundant resource usage, and severely restricts service continuity and resource utilization efficiency.
[0003] Currently, no effective solution has been proposed to address the issue of slow response times in existing network slicing configurations.
[0004] Therefore, it is necessary to improve the relevant technology to overcome the aforementioned defects. Summary of the Invention
[0005] This disclosure provides a network slice creation method and apparatus, storage medium, and electronic device to at least solve the problem of slow response in existing network slice configurations.
[0006] According to one embodiment of this disclosure, a network slice creation method is provided, comprising: determining a first network slice path corresponding to a first time period; sending a first network slice creation message to each router on the first network slice path, wherein the first network slice creation message is a message based on the Path Calculation Unit Protocol, the central controller instruction object of the first network slice creation message carries first network slice configuration information and a first central controller identifier, and the first network slice creation message is used to instruct the router to create a network slice corresponding to the first central controller identifier according to the first network slice configuration information.
[0007] According to another embodiment of this disclosure, a network slice creation method is also provided, comprising: obtaining a first network slice creation message, wherein the first network slice creation message is a message based on the Path Computing Unit Protocol, and the central controller instruction object of the first network slice creation message carries first network slice configuration information and a first central controller identifier; and creating a network slice corresponding to the first central controller identifier according to the first network slice configuration information.
[0008] According to another embodiment of this disclosure, a network slice creation apparatus is also provided, comprising: a determining module, configured to determine a first network slice path corresponding to a first time period; and a sending module, configured to send a first network slice creation message to each router on the first network slice path, wherein the first network slice creation message is a message based on the Path Calculation Unit Protocol, the central controller instruction object of the first network slice creation message carries first network slice configuration information and a first central controller identifier, and the first network slice creation message is used to instruct the router to create a network slice corresponding to the first central controller identifier according to the first network slice configuration information.
[0009] According to another embodiment of this disclosure, a network slice creation apparatus is also provided, comprising: an acquisition module, configured to acquire a first network slice creation message, wherein the first network slice creation message is a message based on the Path Calculation Unit Protocol, and the central controller instruction object of the first network slice creation message carries first network slice configuration information and a first central controller identifier; and a creation module, configured to create a network slice corresponding to the first central controller identifier according to the first network slice configuration information.
[0010] According to yet another embodiment of this disclosure, a computer-readable storage medium is also provided, wherein a computer program is stored therein, wherein the computer program is configured to perform the steps in any of the above method embodiments when executed.
[0011] According to yet another embodiment of this disclosure, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.
[0012] According to yet another embodiment of this disclosure, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments. Attached Figure Description
[0013] Figure 1This is an architecture diagram of a low-Earth orbit satellite communication system according to an embodiment of the present disclosure;
[0014] Figure 2 This is a flowchart of a network slice creation method according to an embodiment of the present disclosure;
[0015] Figure 3 This is a schematic diagram of the structure of a message based on a path calculation unit protocol according to an embodiment of this disclosure;
[0016] Figure 4 This is a schematic diagram of the structure of a message carrying slice configuration information according to an embodiment of the present disclosure;
[0017] Figure 5 This is a schematic diagram of the structure of a stateful PCE request parameter object (SRP Object) according to an embodiment of the present disclosure;
[0018] Figure 6 This is a schematic diagram illustrating a process for creating, maintaining, and destroying a network slice according to an embodiment of this disclosure;
[0019] Figure 7 This is a flowchart of another method for creating network slices according to an embodiment of the present disclosure;
[0020] Figure 8 This is a schematic diagram of network slice path switching according to an embodiment of the present disclosure;
[0021] Figure 9 This is a structural block diagram of a network slicing creation apparatus according to an embodiment of the present disclosure;
[0022] Figure 10 This is a structural block diagram of another network slicing creation apparatus according to an embodiment of the present disclosure. Detailed Implementation
[0023] The embodiments of this disclosure will be described in detail below with reference to the accompanying drawings and examples.
[0024] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.
[0025] To better understand the network slice creation method disclosed in this embodiment, the low-Earth orbit satellite communication system to which this embodiment applies is first described below.
[0026] Please see Figure 1 , Figure 1This is an architecture diagram of a low-Earth orbit (LEO) satellite communication system according to an embodiment of this disclosure. The LEO satellite communication system includes a network controller 101, a ground router 102, and a spaceborne router 103. The network controller 101 establishes a stable and reliable bidirectional communication connection with the spaceborne router 103 and the ground router 102 via Transmission Control Protocol (TCP) / Internet Protocol (IP), serving as the core transmission technology between the space segment and the ground segment. This connection is based on a standard IP routing mechanism, supports end-to-end message transmission across satellite-to-ground links, and possesses congestion control, retransmission mechanisms, and connection keep-alive capabilities, effectively addressing the transmission uncertainties caused by link interruptions, latency jitter, and bandwidth fluctuations in satellite communication. Simultaneously, the broad compatibility of the TCP / IP protocol ensures interoperability between the network controller and heterogeneous routing nodes, providing the underlying communication foundation for the efficient and orderly interaction of subsequent Path Computation Element Protocol (PCEP) messages. The following is a brief description of the network controller 101, the ground router 102, and the spaceborne router 103:
[0027] Network Controller 101: Deployed at the ground control center, it serves as the central management unit for satellite network slicing, responsible for global topology awareness, slice path calculation, resource scheduling, and lifecycle management. Based on ephemeris data and link prediction models, it dynamically generates slice configuration strategies and issues precise resource reservation instructions to each node in the network via the PCEP protocol. Simultaneously, it receives status feedback to achieve closed-loop control, ensuring high availability of slice services and efficient resource reuse.
[0028] Ground Router 102: Deployed at the ground gateway station, it serves as the sole interface between the space network and the ground backbone network, handling both access and exit functions for sliced resources. Its main responsibilities include resource reservation and release based on the sliced resource reservation configuration information issued by Network Controller 101, and data routing and forwarding. It acts as a unified traffic exit device between the space segment and the ground segment of the network.
[0029] The onboard router 103, integrated into a low-Earth orbit satellite platform, is lightweight, radiation-resistant, and low-power. It is responsible for reserving and releasing resources based on the slice resource reservation configuration information issued by the network controller 101, as well as data routing and forwarding. In the absence of a direct satellite-to-ground link, it acts as a relay node, forwarding slice traffic to nearby satellites with power supply capabilities, achieving end-to-end transmission across satellite links. It is a key carrier for the implementation of space segment slice resources.
[0030] It is understood that the low-orbit satellite communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions provided in this disclosure. 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 this disclosure are also applicable to similar technical problems.
[0031] This embodiment provides a network slice creation method, applied to the aforementioned low-Earth orbit satellite communication system. Figure 2 This is a flowchart of a network slice creation method according to an embodiment of the present disclosure, such as... Figure 2 As shown, the process includes the following steps S202-S204:
[0032] Step S202: Determine the first network slice path corresponding to the first time period;
[0033] Optionally, the first time period is the time period following the current moment. The first network slice path contains multiple routers, including satellite routers and terrestrial routers.
[0034] In an exemplary embodiment, determining the first network slice path corresponding to the first time period can be achieved through the following steps S11-S12:
[0035] Step S11: Predict the network topology of the low-Earth orbit satellite network in the first time period based on the solar outage information and the satellite-to-ground feeder link establishment plan information in the first time period;
[0036] For example, the network controller comprehensively receives and parses solar outage information (such as the solar outage time window), satellite orbit parameters, and ground gateway station feeder link establishment plans from the ephemeris database. Combined with the real-time inter-satellite link availability prediction model, it predicts and constructs the network topology of the low-Earth orbit satellite network in the first time period. This network topology includes the relative positions of each satellite node, the on / off status of inter-satellite links, the time window distribution of satellite-to-ground feeder links, and channel quality (such as signal-to-noise ratio and bit error rate), thereby accurately depicting the set of passable end-to-end paths in the first time period.
[0037] Step S12: Determine the first network slice path corresponding to the first time period based on the network topology, communication link quality information and network communication demand information of the first time period.
[0038] Optionally, based on the network topology of the first time period, the network controller combines network communication demand information (such as slice bandwidth requirements, latency constraints, and security isolation levels) with communication link quality information (such as link stability, remaining bandwidth, and hop count) and uses a constraint-based shortest path algorithm or a multi-objective optimization model to calculate the optimal first network slice path.
[0039] The above steps S11-S12, by integrating solar outage and power supply link planning to predict the topology and dynamically calculating the slice path based on link quality and service requirements, achieve accurate pre-allocation of slice resources in the highly dynamic satellite network, significantly improve path availability and resource utilization, and avoid slice interruption or resource waste caused by topology changes.
[0040] Step S204: Send a first network slice creation message to each router on the first network slice path. The first network slice creation message is a message based on the Path Computing Unit Protocol. The central controller instruction object of the first network slice creation message carries the first network slice configuration information and the first central controller identifier (CC-ID). The first network slice creation message is used to instruct the router to create a network slice corresponding to the first central controller identifier according to the first network slice configuration information.
[0041] It should be noted that PCEP is a dynamic protocol design based on Variable Type Length Value (TLV) encoding, which supports efficient encoding and parsing at both ends of the communication, with an effective time of within seconds, meeting the requirements for rapid configuration and distribution of satellite network slice resource reservations. Furthermore, PCEP is a bidirectional interactive protocol that supports the distribution and status feedback of satellite network slice resource reservations, meeting the reliability requirements for satellite network slice distribution.
[0042] It should be noted that [RFC9050] extends the Stateful PCEP defined in [RFC8231]. This standard defines a new PCEP Central Controller Instructions Object (CCI Object) to carry instructions other than the Label Switched Path (LSP) of the central controller. That is, the first network slice configuration information of this disclosure is carried and distributed through the newly extended CCI object.
[0043] Optionally, a schematic diagram of the message structure based on the PCEP protocol is shown below. Figure 3 As shown, the first network slice configuration information and the first central controller identifier are set to... Figure 3 In CCI Objects.
[0044] In an exemplary embodiment, the first network slice configuration information is set in the extended type-length-value field of the central controller instruction object. The first network slice configuration information includes: the local interface address and remote interface address of the link corresponding to the network slice, the committed information rate and peak information rate of the network slice, and the network resource partition identifier used to identify the network slice.
[0045] It should be noted that this disclosure carries slice configuration information by carrying an extended-defined TLV in the CCI object, such as... Figure 4 As shown, the extended TLV field is defined as follows:
[0046] Type: The type, representing the type of a TLV (type-length-value) or a sub-object.
[0047] Length: The length of the TLV or sub-object value (in bytes).
[0048] It should be noted that the Type and Length fields in TLV will no longer be explained in the following explanations.
[0049] Slice type: Slice type code, indicating the slice resource reservation method. Currently, 1 is defined as a flex channel type slice, and other values are undefined (to be defined later). If the device receives an unknown Slice Type value, the TLV should be discarded and the error should be logged.
[0050] Flags: Reserved flags, another set of flags.
[0051] E: The E bit is the slice status flag. 1 indicates that the slice is active, and 0 indicates that the slice is not active. It should be set to 0 in the PCInit or PCUpd message.
[0052] Reserved: Reserved field, unused, reserved for future expansion, must be set to 0.
[0053] Local Interface Address: The local interface IPv6 address of the link corresponding to the tunnel slice.
[0054] Remote Interface Address: The remote interface IPv6 address of the link corresponding to the tunnel slice.
[0055] CIR: Committed Information Rate, which is the bandwidth reserved for the slice, measured in Kbps.
[0056] PIR: Peak Information Rate, which is the maximum rate at which a slice can be burst-transmitted, measured in Kbps.
[0057] NRP ID: Network Resource Slice Identifier, which identifies a network slice.
[0058] It should be noted that by extending the TLV structure in the CCI object to carry slice configuration information, the slice resources are dynamically distributed and precisely bound within seconds. It supports slice management based on IPv6 interface link identification, bandwidth isolation and NRP identification, which improves resource utilization and deployment efficiency, and ensures the rapid, reliable and traceable deployment of slice services in highly dynamic satellite networks.
[0059] Steps S202-S204 above determine the first network slice path corresponding to the first time period, and then send a first network slice creation message containing slice configuration and a unique central controller identifier (CC-ID) to all routers on the path via a single PCEP message. The PCEP protocol itself is a dynamic protocol that takes effect within seconds, significantly reducing the delivery latency compared to the minute-level persistent configuration of traditional NetConf. Simultaneously, the CC-ID carried in the message allows each router to instantly identify, parse, and bind resources without multiple interactions or configuration verifications. This mechanism avoids the node-by-node polling and configuration solidification process of traditional protocols, enabling slice resources to be reserved within seconds, thus solving the problem of slow response times in existing network slice configurations.
[0060] It should be noted that the network controller is the entity that performs the above steps S202-S204.
[0061] In an exemplary embodiment, after sending a first network slice creation message to each router on the first network slice path, the method further includes: sending a network slice update message to each router on the first network slice path, wherein the central controller instruction object of the network slice update message carries second network slice configuration information and the central controller identifier carried is the first central controller identifier, the information rate in the second network slice configuration information is different from the information rate in the first network slice configuration information, and the information rate includes at least one of the following: committed information rate, peak information rate.
[0062] It should be noted that, in terms of message content, the only difference between the network slice update message and the first network slice creation message is the information rate; the values of all other fields are the same.
[0063] In this embodiment, after successfully sending the first network slice creation message to all routers on the first network slice path and completing resource reservation, if service requirements or link quality change (such as a sudden increase in traffic or link congestion), the network controller will trigger dynamic slice optimization and send a network slice update message (PCUpd message) to each PCC device (spaceborne / terrestrial router) on the same path. The network slice update message reuses the original CCI object but carries updated second network slice configuration information. Its Central Controller Identifier (CC-ID) is consistent with the initial creation message, ensuring that the PCC device can accurately identify that the instruction is a modification to the same slice rather than a new one.
[0064] It should be noted that in the second network slice configuration information, the Committed Information Rate (CIR) or Peak Information Rate (PIR) is dynamically adjusted, for example, from 100Mbps to 150Mbps, to meet peak service demands. After receiving the information, the PCC device locates the existing slice based on the NRP ID, without releasing the original resources, and directly adjusts the queue bandwidth parameters in the local flexible sub-channel to achieve uninterrupted bandwidth elastic scaling.
[0065] It should be noted that this mechanism fully utilizes the stateful characteristics of PCEP, avoiding the full reconfiguration and minute-level latency of traditional NetConf, significantly improving network response agility, and supporting highly dynamic and varied service scenarios in low-Earth orbit satellite networks.
[0066] In an exemplary embodiment, after sending a first network slice creation message to each router on the first network slice path, the method further includes the following steps S21-S23:
[0067] Step S21: Determine the second network slice path corresponding to the second time period;
[0068] It should be noted that the second time period is the time period after the first time period. The method for determining the second network slice path is similar to the method for determining the first network slice path described above, and will not be repeated here.
[0069] Step S22: Send a second network slice creation message to each router on the second network slice path, wherein the central controller instruction object of the second network slice creation message carries third network slice configuration information and carries a central controller identifier as the second central controller identifier;
[0070] It should be noted that the identifier of the second central controller is different from that of the first central controller.
[0071] Step S23: Send a network slice destruction message to each router on the first network slice path, wherein the central controller identifier carried in the network slice destruction message is the first central controller identifier, and the removal flag in the stateful PCE request parameter object (SRP Object) of the network slice destruction message is a preset value, which is used to indicate the deletion of the network slice corresponding to the central controller identifier carried in the network slice destruction message.
[0072] It should be noted that the above-mentioned first network slice creation message, second network slice creation message, network slice update message, and network slice destruction message are all messages based on the PCEP protocol, and the removal flag in the Stateful PCE Request Parameter Object (SRP Object) of the first network slice creation message, second network slice creation message, and network slice update message is not a preset value.
[0073] Optional, Figure 5 The diagram illustrates the format of an SRP Object, in which... Figure 5 R in the message is the removal flag. When R is set to 1, it indicates that the message is a deletion request message, which can request the PCC (spaceborne router and ground router) to delete the corresponding slice resource reservation configuration.
[0074] In this embodiment, after resource reservation is completed for the first network slice path, the network controller predicts the optimal slice path (i.e., the second network slice path) for the next time period based on the satellite orbit prediction model and the inter-satellite topology change cycle. This path may partially or completely overlap with the original path due to satellite movement, link interruption, or load balancing. The network controller then performs seamless switching: it sends a second network slice creation message to all PCC devices on the second network slice path. The CCI object carries the third network slice configuration information and a brand-new CC-ID, triggering the reservation of new slice resources.
[0075] It should be noted that, to avoid resource redundancy and conflicts, the network controller sends a network slice destruction message to all nodes in the first network slice path. This message reuses the PCEP standard SRP (Stateful PCE Request Parameter Object) and sets the "removal flag (R-bit)" to 1, instructing the PCC device to release the old slice resources bound to the first CC-ID. After receiving the destruction instruction, the PCC device accurately locates the corresponding flexible sub-channel based on the CC-ID, releases bandwidth allocation, clears forwarding rules, and sends a confirmation message back to the network controller.
[0076] It should be noted that the above steps effectively utilize the predictability of satellite network topology, and continuously and dynamically create and release network slices through the efficient PCEP protocol. This ensures the availability of slice paths while improving network resource utilization, and avoids service interruptions or resource contention caused by releasing network slice resources first and then creating network slices in related technologies.
[0077] To better understand the above process, Figure 6 This diagram illustrates the creation, maintenance, and destruction processes of network slices. For example, the network controller acts as a Path Computation Element (PCE) device, while the satellite router and terrestrial router act as Path Computation Clients (PCC) devices. When a network slice is created via the PCE, the PCE needs to initiate a Path Computation Initiate (PCInitiate) request, carrying the network slice configuration information and setting a CC-ID. If the PCC successfully parses and loads the configuration information, it needs to report its status to the PCE, carrying the same CC-ID. Subsequently, when the PCE updates (corresponding to Update CCI) or deletes a path (corresponding to Delete CCI), this CC-ID needs to be specified for the operation.
[0078] This embodiment provides a method for creating network slices. Figure 7 This is a flowchart of another network slice creation method according to an embodiment of the present disclosure, such as... Figure 7 As shown, the process includes the following steps S702-S704:
[0079] Step S702: Obtain the first network slice creation message, wherein the first network slice creation message is a message based on the path calculation unit protocol, and the central controller instruction object of the first network slice creation message carries the first network slice configuration information and the first central controller identifier.
[0080] Step S704: Create a network slice corresponding to the first central controller identifier based on the first network slice configuration information.
[0081] For example, in this embodiment, after receiving a message based on the PCEP protocol, the satellite router or the ground router determines whether the removal flag in the stateful PCE request parameter object of the PCEP protocol message is a preset value. If it is a preset value, it means that the message is a network slice destruction message. If it is not a preset value, it is a network slice creation message or a network slice update message. If the CC-ID carried in the message has not been recorded by the router, the message is a network slice creation message; otherwise, it is a network slice update message.
[0082] The above steps obtain the first network slice creation message containing slice configuration and a unique CC-ID. The PCEP protocol itself is a dynamic protocol that takes effect within seconds, significantly reducing the delivery latency compared to the minute-level persistent configuration of traditional NetConf. Simultaneously, the CC-ID carried in the message allows the router to instantly identify, parse, and bind resources without multiple interactions or configuration verifications. This mechanism avoids the node-by-node polling and configuration solidification process of traditional protocols, enabling slice resources to be reserved within seconds and solving the problem of slow response times in existing network slice configurations.
[0083] It should be noted that the above steps are performed by either a satellite-borne router or a ground-based router.
[0084] In an exemplary embodiment, the first network slice configuration information is set in the extended type-length-value field of the central controller instruction object. The first network slice configuration information includes: the local interface address and remote interface address of the link corresponding to the network slice, the committed information rate and peak information rate of the network slice, and the network resource partition identifier used to identify the network slice.
[0085] In an exemplary embodiment, creating a network slice corresponding to the first central controller identifier based on the first network slice configuration information can be achieved through the following steps S31-S33:
[0086] Step S31: Create a flexible sub-channel on the communication link identified by the local interface address and the remote interface address, wherein the flexible sub-channel is a transmission channel for network slices;
[0087] In the embodiment shown in step S31, when the PCC device (spaceborne or ground router) receives the PCInitiate message carrying the CCI object, it first calls the underlying control interface on the inter-satellite or space-to-ground communication link identified by the local interface address and the remote interface address to dynamically create a flexible sub-channel. This channel is based on time-division multiplexing or wavelength isolation mechanism, and allocates independent logical bandwidth resources in the physical link as a dedicated transmission channel for this slice, which is completely isolated from the default Best-Effort traffic.
[0088] Step S32: Configure the bandwidth parameters of the flexible sub-channel according to the committed information rate and the peak information rate, and assign the network resource partition identifier to the flexible sub-channel;
[0089] In the embodiment shown in step S32, the PCC configures the Quality of Service (QoS) queue parameters of the flexible sub-channel based on the Committed Information Rate (CIR) and Peak Information Rate (PIR) carried in the CCI object: CIR serves as the guaranteed bandwidth to ensure the minimum transmission requirements of slice services; PIR serves as the burst limit to allow short-term traffic peaks to not be dropped, improving service experience. Simultaneously, the Network Resource Partition ID (NRP ID) is bound to the channel to achieve logical isolation of slices and resource ownership identification.
[0090] Step S33: Establish the correspondence between the network resource partition identifier and the first central controller identifier.
[0091] In the embodiment shown in step S33, the PCC establishes a bidirectional mapping relationship between NRP ID and CC-ID in the local resource management table to ensure that all subsequent update, query or destruction operations on the slice can accurately locate the corresponding flexible sub-channel.
[0092] It should be noted that steps S31–S33 achieve precise creation of network slices: by flexibly isolating resources through sub-channels, binding CIR / PIR to ensure QoS, and establishing NRP ID and CC-ID mapping, the slice configuration can be quickly deployed, accurately identified, and reliably managed.
[0093] In an exemplary embodiment, after creating a network slice corresponding to the first central controller identifier based on the first network slice configuration information, the method further includes: obtaining a network slice update message, wherein the central controller instruction object of the network slice update message carries second network slice configuration information and the central controller identifier carried is the first central controller identifier, the information rate in the second network slice configuration information is different from the information rate in the first network slice configuration information, and the information rate includes at least one of the following: committed information rate, peak information rate; updating the bandwidth parameters of the network slice corresponding to the first central controller identifier based on the second network slice configuration information.
[0094] It should be noted that if, after receiving a PCEP message, the router determines that the CC-ID carried in the message is the same as the CC-ID carried in the first network slice creation message, and the only difference between the message content of the received message and the first network slice creation message is the information rate, then the received message can be considered a network slice update message. In this case, the router can update the bandwidth parameters of the network slice corresponding to the first central controller identifier based on the information rate carried in the network slice update message.
[0095] For example, after successfully creating a network slice corresponding to the first central controller identifier, when the satellite network topology changes dynamically or service requirements are adjusted (such as an increase in emergency communication burst traffic), the network controller (PCE) will send a network slice update message (PCUpd message) to the same PCC device to update the committed information rate (CIR) and / or peak information rate (PIR) of the network slice, for example, increasing the CIR from 100Mbps to 200Mbps and the PIR from 300Mbps to 500Mbps. After receiving the message, the PCC device dynamically adjusts the bandwidth quota of the established flexible sub-channels.
[0096] It should be noted that by using the above method to dynamically update the CIR / PIR by reusing the same CC-ID, the network slice bandwidth can be adjusted online in seconds without rebuilding the channel, thus ensuring service continuity and overcoming the shortcomings of traditional static configuration, such as slow response and large interruptions.
[0097] In an exemplary embodiment, after creating a network slice corresponding to the first central controller identifier based on the first network slice configuration information, the method further includes: obtaining a second network slice creation message, wherein the central controller instruction object of the second network slice creation message carries third network slice configuration information and the central controller identifier carried is the second central controller identifier; and creating a network slice corresponding to the second central controller identifier based on the third network slice configuration information.
[0098] It should be noted that if, after receiving a PCEP message, the router determines that the CC-ID carried in the message has not been recorded in the router and the removal flag in the stateful PCE request parameter object of the message is not a preset value, then it means that the received message is a new network slice creation message (i.e., a second network slice creation message). Then, based on the third network slice configuration information carried in the second network slice creation message, a network slice corresponding to the second central controller identifier is created.
[0099] Optionally, based on the existing slice operation, the network controller can initiate new slice creation requests in parallel. By carrying a new CC-ID and independent third slice configuration information (such as new NRP, CIR / PIR, interface address), logically isolated new slices can be created on the same link for different services (such as emergency command and scientific data). PCC devices establish independent and flexible sub-channels and resource mappings based on the new CC-ID, realizing the concurrent deployment of multiple slices and improving the multi-tenant reuse capability and scheduling flexibility of satellite bandwidth resources.
[0100] In an exemplary embodiment, after creating a network slice corresponding to the first central controller identifier based on the first network slice configuration information, the method further includes: obtaining a network slice destruction message, wherein the central controller identifier carried in the network slice destruction message is the first central controller identifier, the removal flag bit in the stateful PCE request parameter object (SRP Object) of the network slice destruction message is a preset value, and the preset value is used to indicate the deletion of the network slice corresponding to the central controller identifier carried in the network slice destruction message; and destroying the network slice corresponding to the first central controller identifier.
[0101] It should be noted that if the router determines that the removal flag in the stateful PCE request parameter object (SRP Object) of the PCEP message is set to a preset value after receiving the PCEP message, then it determines that the message is a network slice destruction message, and then needs to destroy the corresponding network slice according to the central controller identifier carried in the message.
[0102] For example, when the satellite network topology changes or services end, the network controller sends a network slice destruction message to the corresponding PCC device. The removal flag (R bit) in its stateful PCE request parameter object (SRP Object) is set to "1", and the first CC-ID used is carried. The PCC device can then accurately locate the flexible sub-channel of the corresponding slice, release its bound CIR / PIR bandwidth resources, and unmap the NRP ID to the interface, ensuring that resources are reclaimed in a timely manner without occupying onboard cache and link bandwidth.
[0103] It should be noted that the above mechanism can support resource release at the second level, avoid resource residue, and improve the lifecycle management efficiency of network slices and the overall resource utilization rate in highly dynamic environments.
[0104] To better understand the above technical solution, the following explanation is provided:
[0105] The high dynamic changes in network topology in low-Earth orbit satellite internet are mainly caused by solar interference and the high-speed relative motion between satellite and ground, resulting in dynamic changes in inter-satellite / satellite-ground topology. The network controller can calculate the network topology for time period T based on solar interference information and satellite-ground feeder link establishment plan. Based on the network topology and link quality information for time period T, combined with service requirements (such as link bandwidth), the slice path is calculated and then the slice configuration information is sent to all PCC devices on the path through the PCEP protocol. After time T, the slice resource release information is sent to all PCC devices on the path to ensure that the resources occupied by PCC devices are released quickly after the slice path is switched.
[0106] It should be noted that by leveraging the predictability of satellite network topology, the network controller continuously and dynamically creates and releases network slices through the efficient PCEP protocol, ensuring the availability of slice paths while improving network resource utilization.
[0107] Figure 8 This is a schematic diagram of network slice path switching according to an embodiment of the present disclosure, with reference to... Figure 8 The specific steps for creating, updating, and destroying this publicly disclosed network slice are as follows:
[0108] Step 1: The network controller calculates the slice path P1 corresponding to the T0 time period based on information such as network topology, link bandwidth, and service requirements, which includes all satellite routers and ground routers along the path.
[0109] Step 2: The network controller (PCE device) initiates network slice creation to all satellite routers and terrestrial routers (PCC devices) on the P1 path: The PCE initiates a PCInitiate request (i.e., sends a network slice creation message), which carries slice configuration information and sets the CC-ID. The slice configuration information includes link identification information, slice NRP, and slice reserved bandwidth information, etc. The message format is as follows: Figure 4 As shown.
[0110] Step 3: After receiving this message, the onboard router and the ground router (PCC device) locate the slice master interface based on the specified local interface address and remote interface address, request a flexible sub-channel according to the configured CIR and PIR bandwidth, and bind the NRP ID as the slice identifier. Subsequently, when forwarding traffic matching this slice, it will be preferentially forwarded from the flexible sub-channel queue with reserved bandwidth, and will no longer share it with the default be / b traffic.
[0111] Step 4: The network controller (PCE device) sends network slice update messages to all satellite routers and terrestrial routers (PCC devices) on the P1 path. The network slice update messages differ from the network slice creation messages in Step 2 only in the committed information rate and / or peak information rate.
[0112] Step 5: The network controller calculates the slice path P2 corresponding to the T1 time period based on information such as network topology, link bandwidth, and service requirements, which includes all satellite routers and ground routers along the path.
[0113] Step Six: The network controller (PCE device) initiates network slice creation to all satellite routers and ground routers (PCC devices) on the P2 path: The PCE initiates a PCInitiate request, which carries slice configuration information and sets a CC-ID (different from the CC-ID carried in Step Two). The slice configuration information includes link identification information, slice NRP, and slice reserved bandwidth information, etc.
[0114] Step 7: Upon receiving this information, the relevant spaceborne routers and ground routers (PCC devices) locate the slice's main interface based on the specified address, request a flexible sub-channel according to the configured CIR and PIR bandwidth, and bind the NRP ID as the slice identifier. Subsequently, when forwarding traffic matching this slice, it will prioritize forwarding from the flexible sub-channel queue that reserves bandwidth, instead of sharing it with the default be / b traffic.
[0115] Step 8: The network controller (PCE device) initiates network slice destruction to all satellite routers and terrestrial routers (PCC devices) on the P1 path: The PCE initiates a PCInitiate request (i.e., sends a network slice destruction message), which carries slice resource release information and related CC-IDs. The slice resource release information disclosed in this disclosure is carried out by reusing the original SRP object of the PCEP. That is, when the R field (remove flag) in the SRP object of the PCEP message is set to 1, it indicates that this message is a deletion request, instructing the PCC to destroy the network slice corresponding to the CC-ID carried in the message.
[0116] Step Nine: Upon receiving the network slice destruction message (SRP object, R bit = 1), the relevant satellite-borne routers and ground routers (PCC devices) release resources, for example:
[0117] 1) Unbind bandwidth: Release the CIR / PIR bandwidth resources occupied by the Flexible Subchannel associated with this CC-ID and return them to the shared pool of the local link;
[0118] 2) Clear QoS mapping: Delete the traffic classification rules and queue priority configurations corresponding to this NRP ID, and stop dedicated scheduling for packets matching the slice identifier;
[0119] 3) Update the forwarding table: Clear the forwarding entries in the routing table related to this slice path to avoid misforwarding;
[0120] 4) Release memory and cache: Release the buffers, status table entries and counters allocated for this slice to reduce the resource overhead of onboard equipment;
[0121] 5) Feedback confirmation: Send a PCRpt response to the controller to confirm that the resource has been successfully released.
[0122] It should be noted that this disclosure designs a dynamic configuration and distribution mechanism for satellite network slice resources based on the PCEP protocol, and extends the existing PCEP message format by defining new CCI objects to carry resource reservation and configuration information. By utilizing the predictability of the highly dynamic topology of satellite networks, the dynamic reservation and release of network slice resources can be achieved, which can ensure the availability of slice paths while improving network resource utilization.
[0123] 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 disclosure, 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 disclosure.
[0124] This embodiment also provides a network slice creation apparatus for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that performs a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.
[0125] Figure 9 This is a structural block diagram of a network slicing creation apparatus according to an embodiment of the present disclosure, such as... Figure 9 As shown, the device includes:
[0126] The determination module 902 is used to determine the first network slice path corresponding to the first time period;
[0127] The sending module 904 is used to send a first network slice creation message to each router on the first network slice path. The first network slice creation message is a message based on the Path Calculation Unit Protocol. The central controller instruction object of the first network slice creation message carries first network slice configuration information and a first central controller identifier. The first network slice creation message is used to instruct the router to create a network slice corresponding to the first central controller identifier according to the first network slice configuration information.
[0128] The aforementioned device determines the first network slice path corresponding to the first time period, and then sends a first network slice creation message containing slice configuration and a unique CC-ID to all routers along the path via a single PCEP message. The PCEP protocol itself is a dynamic protocol that takes effect within seconds, significantly reducing the delivery latency compared to the minute-level persistent configuration of traditional NetConf. Simultaneously, the CC-ID carried in the message allows each router to instantly identify, parse, and bind resources without requiring multiple interactions or configuration verifications. This mechanism avoids the node-by-node polling and configuration solidification process of traditional protocols, enabling slice resources to be reserved within seconds, thus solving the problem of slow response times in existing network slice configurations.
[0129] In an exemplary embodiment, the determining module 902 is further configured to predict the network topology of the low-orbit satellite network in the first time period based on the solar outage information and the satellite-to-ground feeder link establishment plan information in the first time period; and determine the first network slice path corresponding to the first time period based on the network topology, communication link quality information and network communication demand information in the first time period.
[0130] In an exemplary embodiment, the first network slice configuration information is set in the extended type-length-value field of the central controller instruction object. The first network slice configuration information includes: the local interface address and remote interface address of the link corresponding to the network slice, the committed information rate and peak information rate of the network slice, and the network resource partition identifier used to identify the network slice.
[0131] In an exemplary embodiment, the sending module 904 is further configured to send a network slice creation message to each router on the first network slice path, and then send a network slice update message to each router on the first network slice path. The central controller instruction object of the network slice update message carries second network slice configuration information and carries a central controller identifier that is the first central controller identifier. The information rate in the second network slice configuration information is different from the information rate in the first network slice configuration information. The information rate includes at least one of the following: committed information rate and peak information rate.
[0132] In an exemplary embodiment, the determining module 902 is further configured to determine the second network slice path corresponding to the second time period after sending the first network slice creation message to each router on the first network slice path; the sending module 904 is further configured to send the second network slice creation message to each router on the second network slice path, wherein the central controller instruction object of the second network slice creation message carries third network slice configuration information and the central controller identifier carried is the second central controller identifier; and send a network slice destruction message to each router on the first network slice path, wherein the central controller identifier carried in the network slice destruction message is the first central controller identifier, and the removal flag bit in the stateful PCE request parameter object SRPObject of the network slice destruction message is a preset value, the preset value being used to indicate the deletion of the network slice corresponding to the central controller identifier carried in the network slice destruction message.
[0133] Figure 10 This is a structural block diagram of another network slicing creation apparatus according to an embodiment of the present disclosure, such as... Figure 10 As shown, the device includes:
[0134] The acquisition module 1002 is used to acquire a first network slice creation message, wherein the first network slice creation message is a message based on the path calculation unit protocol, and the central controller instruction object of the first network slice creation message carries the first network slice configuration information and the first central controller identifier.
[0135] The creation module 1004 is used to create a network slice corresponding to the first central controller identifier based on the first network slice configuration information.
[0136] The aforementioned device acquires a first network slice creation message containing slice configuration and a unique CC-ID. The PCEP protocol itself is a dynamic protocol that takes effect within seconds, significantly reducing the delivery latency compared to the minute-level persistent configuration of traditional NetConf. Simultaneously, the CC-ID carried in the message allows the router to instantly identify, parse, and bind resources without multiple interactions or configuration verifications. This mechanism avoids the node-by-node polling and configuration solidification process of traditional protocols, enabling slice resources to be reserved within seconds and solving the problem of slow response times in existing network slice configurations.
[0137] In an exemplary embodiment, the first network slice configuration information is set in the extended type-length-value field of the central controller instruction object. The first network slice configuration information includes: the local interface address and remote interface address of the link corresponding to the network slice, the committed information rate and peak information rate of the network slice, and the network resource partition identifier used to identify the network slice.
[0138] In an exemplary embodiment, the creation module 1004 is further configured to create a flexible sub-channel on the communication link identified by the local interface address and the remote interface address, wherein the flexible sub-channel is a transmission channel for network slices; configure the bandwidth parameters of the flexible sub-channel according to the committed information rate and the peak information rate, and assign the network resource partition identifier to the flexible sub-channel; and establish a correspondence between the network resource partition identifier and the identifier of the first central controller.
[0139] In an exemplary embodiment, the apparatus further includes: an update module, configured to create a network slice corresponding to the first central controller identifier based on the first network slice configuration information, and then obtain a network slice update message, wherein the central controller instruction object of the network slice update message carries second network slice configuration information and the central controller identifier carried is the first central controller identifier, the information rate in the second network slice configuration information is different from the information rate in the first network slice configuration information, and the information rate includes at least one of the following: committed information rate, peak information rate; and update the bandwidth parameters of the network slice corresponding to the first central controller identifier based on the second network slice configuration information.
[0140] In an exemplary embodiment, the acquisition module 1002 is further configured to acquire a second network slice creation message after creating a network slice corresponding to the first central controller identifier based on the first network slice configuration information, wherein the central controller instruction object of the second network slice creation message carries third network slice configuration information and the central controller identifier carried is the second central controller identifier; the creation module 1004 is further configured to create a network slice corresponding to the second central controller identifier based on the third network slice configuration information.
[0141] In an exemplary embodiment, the acquisition module 1002 is further configured to acquire a network slice destruction message after creating a network slice corresponding to the first central controller identifier according to the first network slice configuration information, wherein the central controller identifier carried in the network slice destruction message is the first central controller identifier, and the removal flag bit in the stateful PCE request parameter object (SRP Object) of the network slice destruction message is a preset value, the preset value being used to indicate the deletion of the network slice corresponding to the central controller identifier carried in the network slice destruction message; the device further includes: a destruction module, configured to destroy the network slice corresponding to the first central controller identifier.
[0142] Embodiments of this disclosure also provide a computer-readable storage medium storing a computer program configured to perform the steps in any of the above method embodiments when executed.
[0143] 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.
[0144] Embodiments of this disclosure also provide an electronic device including a memory and a processor, the memory storing a computer program and the processor being configured to run the computer program to perform the steps in any of the above method embodiments.
[0145] 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.
[0146] 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.
[0147] Embodiments of this disclosure also provide a computer program product, which includes a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.
[0148] Embodiments of this disclosure also provide another computer program product, including a non-volatile computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.
[0149] The embodiments described herein also provide a computer program that includes computer instructions stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the steps in any of the above method embodiments.
[0150] It is obvious to those skilled in the art that the modules or steps of this disclosure 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 herein, 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 disclosure is not limited to any particular combination of hardware and software.
[0151] The above description is merely a preferred embodiment of this disclosure and is not intended to limit this disclosure. Various modifications and variations can be made to this disclosure by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this disclosure should be included within the scope of protection of this disclosure.
Claims
1. A method for creating network slices, characterized in that, include: Determine the first network slice path corresponding to the first time period; A first network slice creation message is sent to each router on the first network slice path. The first network slice creation message is a message based on the Path Computing Unit Protocol. The central controller instruction object of the first network slice creation message carries the first network slice configuration information and the first central controller identifier. The first network slice creation message is used to instruct the router to create a network slice corresponding to the first central controller identifier according to the first network slice configuration information.
2. The method according to claim 1, characterized in that, Determine the path of the first network slice corresponding to the first time period, including: Based on the solar outage information and the satellite-to-ground feeder link establishment plan information in the first time period, predict the network topology of the low-Earth orbit satellite network in the first time period; The first network slice path corresponding to the first time period is determined based on the network topology, communication link quality information, and network communication demand information of the first time period.
3. The method according to claim 1, characterized in that, The first network slice configuration information is set in the extended type-length-value field of the central controller instruction object. The first network slice configuration information includes: the local interface address and remote interface address of the link corresponding to the network slice, the committed information rate and peak information rate of the network slice, and the network resource partition identifier used to identify the network slice.
4. The method according to claim 1, characterized in that, After sending a first network slice creation message to each router on the first network slice path, the method further includes: A network slice update message is sent to each router on the first network slice path. The central controller instruction object of the network slice update message carries second network slice configuration information and carries a central controller identifier that is the first central controller identifier. The information rate in the second network slice configuration information is different from the information rate in the first network slice configuration information. The information rate includes at least one of the following: committed information rate and peak information rate.
5. The method according to claim 1, characterized in that, After sending a first network slice creation message to each router on the first network slice path, the method further includes: Determine the second network slice path corresponding to the second time period; Send a second network slice creation message to each router on the second network slice path, wherein the central controller instruction object of the second network slice creation message carries third network slice configuration information, and the central controller identifier carried is the second central controller identifier; A network slice destruction message is sent to each router on the first network slice path. The central controller identifier carried in the network slice destruction message is the first central controller identifier. The removal flag in the stateful PCE request parameter object of the network slice destruction message is a preset value. The preset value is used to indicate the deletion of the network slice corresponding to the central controller identifier carried in the network slice destruction message.
6. A method for creating network slices, characterized in that, include: Obtain the first network slice creation message, wherein the first network slice creation message is a message based on the path calculation unit protocol, and the central controller instruction object of the first network slice creation message carries the first network slice configuration information and the first central controller identifier. A network slice corresponding to the first central controller identifier is created based on the first network slice configuration information.
7. The method according to claim 6, characterized in that, The first network slice configuration information is set in the extended type-length-value field of the central controller instruction object. The first network slice configuration information includes: the local interface address and remote interface address of the link corresponding to the network slice, the committed information rate and peak information rate of the network slice, and the network resource partition identifier used to identify the network slice.
8. The method according to claim 7, characterized in that, Creating a network slice corresponding to the first central controller identifier based on the first network slice configuration information includes: A flexible sub-channel is created on the communication link identified by the local interface address and the remote interface address, wherein the flexible sub-channel is a transmission channel for network slices; Configure the bandwidth parameters of the flexible sub-channel according to the committed information rate and the peak information rate, and assign the network resource partition identifier to the flexible sub-channel; Establish the correspondence between the network resource partition identifier and the first central controller identifier.
9. The method according to claim 6, characterized in that, After creating a network slice corresponding to the first central controller identifier based on the first network slice configuration information, the method further includes: Obtain a network slice update message, wherein the central controller instruction object of the network slice update message carries second network slice configuration information, and the central controller identifier carried is the first central controller identifier, and the information rate in the second network slice configuration information is different from the information rate in the first network slice configuration information, and the information rate includes at least one of the following: committed information rate, peak information rate; Update the bandwidth parameters of the network slice corresponding to the first central controller identifier based on the second network slice configuration information.
10. The method according to claim 6, characterized in that, After creating a network slice corresponding to the first central controller identifier based on the first network slice configuration information, the method further includes: Obtain the second network slice creation message, wherein the central controller instruction object of the second network slice creation message carries the third network slice configuration information, and the central controller identifier carried is the second central controller identifier; A network slice corresponding to the second central controller identifier is created based on the third network slice configuration information.
11. The method according to claim 6 or 10, characterized in that, After creating a network slice corresponding to the first central controller identifier based on the first network slice configuration information, the method further includes: Obtain a network slice destruction message, wherein the central controller identifier carried in the network slice destruction message is the first central controller identifier, and the removal flag bit in the stateful PCE request parameter object of the network slice destruction message is a preset value, the preset value is used to indicate the deletion of the network slice corresponding to the central controller identifier carried in the network slice destruction message. Destroy the network slice corresponding to the first central controller identifier.
12. A network slicing creation device, characterized in that, include: The determination module is used to determine the first network slice path corresponding to the first time period; The sending module is used to send a first network slice creation message to each router on the first network slice path. The first network slice creation message is a message based on the Path Calculation Unit Protocol. The central controller instruction object of the first network slice creation message carries first network slice configuration information and a first central controller identifier. The first network slice creation message is used to instruct the router to create a network slice corresponding to the first central controller identifier according to the first network slice configuration information.
13. A network slicing creation device, characterized in that, include: The acquisition module is used to acquire the first network slice creation message, wherein the first network slice creation message is a message based on the path calculation unit protocol, and the central controller instruction object of the first network slice creation message carries the first network slice configuration information and the first central controller identifier. A creation module is used to create a network slice corresponding to the first central controller identifier based on the first network slice configuration information.
14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps of the method described in any one of claims 1 to 11.
15. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 11.
16. 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 claims 1 to 11.