Link configuration method, apparatus, storage medium and program product

Abstract

Embodiments of the present application provide a link configuration method and device, a storage medium and a program product. The method comprises: receiving an opening demand message of a micro cloud unit (SCU) link sent by a transmission network element; the opening demand message is sent by the transmission network element under the condition that a source node or a sink node of a user network interface perception sending message is determined as a first SCU network element according to the IP address of the source node or the sink node, and a transmission link corresponding to the message has not been established; an adaptive link configuration template is selected based on the opening demand message, and the required transmission link and protection link are configured according to the link configuration template. The scheme of the present application solves the problems of dynamic adaptation, resource utilization rate and opening efficiency of the transmission link in the 6G distributed micro cloud unit scene through the design logic of the dynamic link perception-templating configuration-protection mechanism linkage.

Description

Technical Field

[0001] This application relates to the field of communication technology, specifically to a link configuration method, apparatus, storage medium, and program product. Background Technology

[0002] As 5G networks evolve towards 6G, the core network architecture is undergoing a profound transformation from centralized to distributed autonomy. In the 5G era, the separation and decentralization of the user plane (UPF) and control plane (CP) have initially enabled flexible expansion of network functions. However, the existing network architecture reveals insufficient rigidity in response to the diversified, dynamic, and localized needs of 6G service scenarios. To address this, 6G proposes the Service Cloud Unit (SCU), which further decouples user plane and control plane functions and decentralizes them to the network edge, forming a flexible architecture that combines centralized and distributed approaches to support dynamic on-demand networking. SCUs are plug-and-play and flexibly deployable, dynamically created or destroyed in time and space according to service needs. For example, temporary SCUs can be quickly deployed in scenarios with sudden traffic surges, or SCUs can be deployed closer to terminals in edge computing scenarios. However, this change places extremely high demands on the transmission link: the backhaul link between the Radio Access Network (RAN) and the SCU needs to have dynamic adaptation capabilities to cope with challenges such as the high randomness of SCU location and real-time changes in affiliation.

[0003] Currently, the transmission links from base stations to the core network mainly employ pre-configured static connection technologies, such as fixed-path transmission using Segment Routing Transport Profile (SR-TP) and Time Division Multiplexing (TDM). This type of solution requires manual pre-setting of link parameters before service activation, and has the following drawbacks:

[0004] Insufficient flexibility: The dynamic deployment of SCUs leads to frequent changes in their affiliation with base stations, and pre-configured links cannot detect topology changes in real time, requiring manual rerouting, which prolongs service interruption time.

[0005] Low resource utilization: Static links reserve fixed bandwidth and time slots, which are difficult to match sudden fluctuations in SCU traffic, resulting in idle resources or congestion.

[0006] Low activation efficiency: When adding a new SCU, the transmission equipment needs to be configured hop by hop and the routing policy needs to be synchronized. There are many manual intervention steps, and the activation delay is as high as hours, which seriously restricts the realization of the goal of "minute-level elastic expansion and contraction" of 6G. Summary of the Invention

[0007] At least one embodiment of this application provides a link configuration method, apparatus, storage medium, and program product to address the problem that existing static connection technology for transmission links based on SR-TP / TDM cannot effectively support the dynamic deployment and elastic resource scheduling requirements of 6G distributed micro-cloud units, resulting in prolonged service interruptions, low resource utilization, and insufficient automation.

[0008] To solve the above-mentioned technical problems, this application is implemented as follows:

[0009] Firstly, embodiments of this application provide a link configuration method, including:

[0010] The transmission network element receives a micro-cloud unit (SCU) link activation request message sent by the transmission network element. The activation request message is sent by the transmission network element when it determines that the source node or the destination node is the first SCU network element based on the IP address of the source node or the destination node that sent the message through the user network interface, and the transmission link corresponding to the message has not yet been established.

[0011] Select an appropriate link configuration template based on the activation request message, and configure the required transmission link and protection link according to the link configuration template.

[0012] Optionally, after configuring the required transmission link and protection link according to the link configuration template, the method further includes:

[0013] Monitor the actual bandwidth utilization of the transmission link for transmitting services;

[0014] Based on the actual bandwidth utilization, the bandwidth of the configured transmission link and the protection link is dynamically adjusted.

[0015] Optionally, based on the actual bandwidth utilization, the bandwidth of the configured transmission link and the protection link is dynamically adjusted, including:

[0016] Set a threshold for bandwidth utilization;

[0017] If the peak value of the actual bandwidth utilization is less than the threshold value, the bandwidth of the transmission link and the protection link is reduced; if the peak value is greater than the threshold value, the bandwidth of the transmission link and the protection link is increased until the actual bandwidth utilization is equal to the threshold value.

[0018] Optionally, after dynamically adjusting the bandwidth of the configured transmission link and the protection link based on the actual bandwidth utilization, the method further includes:

[0019] Obtain the actual bandwidth value of all service transmissions after dynamic adjustment;

[0020] If each of the actual bandwidth values ​​is greater than or less than the corresponding preset value of the template, then the link configuration template is updated using the maximum bandwidth value among all the actual bandwidth values.

[0021] Optionally, before receiving the activation request message for the micro-cloud unit (SCU) link sent by the transmission network element, the method further includes:

[0022] Establish an IP address database; the IP address database includes a list of pre-stored IP addresses of SCU network elements;

[0023] When the IP address of the transmission network element appears for the first time, determine whether the transmission network element is an SCU network element based on the network element hostname and domain name of the transmission network element.

[0024] If the transmission network element is the SCU network element, then the IP address of the transmission network element is updated to the IP address list, and the IP address of the transmission network element is forwarded and synchronized to each transmission network element.

[0025] Optionally, the system receives a request message from the transmission network element to activate the SCU link, including:

[0026] If the IP address of the transmission network element is not appearing for the first time, and the IP address corresponding to the source node or destination node of the transmission network element is stored in the IP address list, the source node or destination node of the transmission network element is determined to be the first SCU network element.

[0027] When the source node or destination node of the transmission network element is the first SCU network element and a transmission link corresponding to the received message of the transmission network element has not yet been established, the micro-cloud unit SCU link activation request message sent by the transmission network element is received.

[0028] The activation request message carries at least one of the following: the IP address of the source node or the destination node, SCU network element information, and service identification information.

[0029] Optionally, based on the activation requirement message, a suitable link configuration template is selected, and the required transmission link and protection link are configured according to the link configuration template, including:

[0030] Based on the activation request message, obtain the service identification information and service configuration parameters;

[0031] Based on the service identification information, an appropriate link configuration template is selected, including: selecting a first configuration template for ordinary services; selecting a second configuration template for small-granularity Time Division Multiplexing (TDM) services; and selecting a third configuration template for large-granularity TDM services. The first configuration template corresponds to the segmented routing transmission configuration file (SR-TP) pipe; the second configuration template corresponds to the fine-grained metropolitan area network (fgMTN) pipe; and the third configuration template corresponds to the metropolitan area network (MTN) pipe.

[0032] Configure the required transmission link based on the template parameters of the selected link configuration template and the service configuration parameters; wherein, missing parameters are used with template preset values;

[0033] Configure the protection link according to the parameters of the transmission link, and allocate forwarding paths and pipeline resources to the transmission link and the protection link.

[0034] Secondly, embodiments of this application provide a link configuration apparatus, including:

[0035] The receiving module is used to receive the activation request message of the micro cloud unit (SCU) link sent by the transmission network element. The activation request message is sent by the transmission network element when it determines that the source node or the destination node is the first SCU network element based on the IP address of the source node or the destination node of the packet sent by the user network interface, and the transmission link corresponding to the packet has not yet been established.

[0036] The first processing module is used to select an appropriate link configuration template based on the activation requirement message, and configure the required transmission link and protection link according to the link configuration template.

[0037] Thirdly, embodiments of this application provide a computer-readable storage medium storing a program that, when executed by a processor, implements the steps of the method described in any of the first aspects.

[0038] Fourthly, embodiments of this application provide a computer program product, including computer instructions that, when executed by a processor, implement the steps of the method described in any of the first aspects.

[0039] Compared with existing technologies, the link configuration method, apparatus, storage medium, and program products provided in this application, when the transmission network element detects the identity of the source or destination node of a packet in real time through the user network interface, and when it discovers an SCU node with an unestablished link, it receives an activation request message sent by the transmission network element. Through automated link demand perception, it replaces manual pre-configuration, realizes real-time response to topology changes, and reduces service interruption time. Based on the activation request message, it determines the SCU service type and selects an appropriate link parameter template, dynamically generating the transmission link configuration, avoiding resource waste caused by static reservation, and matching the spatiotemporal fluctuation characteristics of SCU service volume. Attached Figure Description

[0040] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0041] Figure 1 A flowchart illustrating the link configuration method provided in an embodiment of this application;

[0042] Figure 2 This is a schematic diagram illustrating the specific process of the link configuration method provided in the embodiments of this application;

[0043] Figure 3 This is a schematic diagram of the link configuration device provided in an embodiment of this application. Detailed Implementation

[0044] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, without limiting the number of objects; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, "A or B" covers three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0045] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0046] As described in the background section, traditional static transmission links cannot perceive SCU dynamic topology in real time, flexibly match service traffic fluctuations, and automatically activate, resulting in prolonged service interruptions, low resource utilization, and hourly deployment latency, which violates the agility requirements of 6G micro-cloud units. To solve at least one of the above problems, this application provides a link configuration method, device, storage medium, and program product, which can reduce or avoid the occurrence of the above situations, effectively improve the activation efficiency of service transmission links, and meet the scenario requirements of plug-and-play SCU and flexible dynamic space and time.

[0047] Please refer to Figure 1 This application provides a link configuration method applied to the control function plane of a transmission network element device, comprising:

[0048] Step 11: Receive the activation request message of the micro cloud unit (SCU) link sent by the transmission network element; the activation request message is sent by the transmission network element when it determines that the source node or the destination node is the first SCU network element based on the IP address of the source node or the destination node of the packet sent by the user network interface, and the transmission link corresponding to the packet has not yet been established.

[0049] Step 12: Select an appropriate link configuration template based on the activation requirement message, and configure the required transmission link and protection link according to the link configuration template.

[0050] In this embodiment, the control and management plane of the transmission network element interacts with the transmission network element. When the transmission network element senses the IP address of the source or destination node sending the packet at the User Network Interface (UNI), if the IP address does not exist in the preset IP address database, the source or destination node is considered a non-SCU network element. If it exists in the preset IP address database, the source or destination node is considered a first SCU network element. For example, when receiving a packet from IP address 10.1.1.1 (source node) to 10.1.1.2 (destination node), the system checks whether the two IP addresses exist in the SCU address database of the control and management plane (e.g., belonging to a predefined IP segment of the micro-cloud unit resource pool) and queries whether the current transmission network element's transmission plane already has a service transmission link between the source and destination nodes. If not, a link activation request is triggered and an activation request message is reported. Here, the transmission network element can discover whether a service transmission link between the source and destination nodes already exists by looking up a table during forwarding.

[0051] Correspondingly, the control and management plane of the transmission network element receives the activation request message for the Micro Cloud Unit (SCU) link sent by the transmission network element. After receiving the activation request message, the control and management plane selects an appropriate template based on the service identification information (such as bandwidth requirements and latency levels) carried in the activation request message. For example: in low-latency scenarios, a tunnel template is selected, using a fixed path to avoid dynamic routing fluctuations; in high-reliability scenarios, a protection template is selected, configuring two physically separate transmission paths, primary and backup.

[0052] This application selects an appropriate link configuration template based on the activation requirement message and configures the transmission link and protection link. Through real-time matching of service identification information (such as bandwidth and latency level) with a pre-set template library, it can automatically select the optimal link type, reducing the error rate of manual configuration. Based on the bandwidth requirements of the SCU service identifier, it automatically allocates transmission channels and sets corresponding policies to avoid resource waste.

[0053] Optionally, after step 12 above, the method further includes:

[0054] Monitor the actual bandwidth utilization of the transmission link for transmitting services;

[0055] Based on the actual bandwidth utilization, the bandwidth of the configured transmission link and the protection link is dynamically adjusted.

[0056] In this embodiment, monitoring the actual bandwidth utilization of the transmission link for transmission services can be achieved through multi-dimensional data collection, including but not limited to: traffic probe injection: deploying traffic probe packets at the entry node of the transmission link, collecting bandwidth usage data every 500ms, and recording peak, average, and burst traffic characteristics; protocol-level monitoring: measuring end-to-end latency and packet loss rate through relevant protocols, and determining the compliance status of the current service based on priority marking; device-level statistics: periodically reporting port counter data by transmission network elements. For example, by using a preset protocol, the transmission network element reports data to the management and control function plane every few seconds to achieve the purpose of monitoring the actual bandwidth utilization of the service link. Based on the actual bandwidth utilization, the bandwidth of the configured transmission link and the protection link is dynamically adjusted, including but not limited to: rapid expansion triggering conditions: when the real-time bandwidth utilization exceeds the high water level (e.g., 85%), rapid expansion is triggered; when the average utilization is below the low water level (e.g., 35%) for one consecutive hour, intelligent capacity reduction is performed.

[0057] This application dynamically adjusts the bandwidth of the configured transmission link and protection link based on the actual bandwidth utilization rate, ensuring that the utilization rate of the adjusted transmission link and protection link remains within a preset reasonable range, and the protection link utilization rate is improved.

[0058] Optionally, based on the actual bandwidth utilization, the bandwidth of the configured transmission link and the protection link is dynamically adjusted, including:

[0059] Set a threshold for bandwidth utilization;

[0060] If the peak value of the actual bandwidth utilization is less than the threshold value, the bandwidth of the transmission link and the protection link is reduced; if the peak value is greater than the threshold value, the bandwidth of the transmission link and the protection link is increased until the actual bandwidth utilization is equal to the threshold value.

[0061] In this application, after the service transmission link is activated, the bandwidth resource allocation of the service transmission link and the protection link is dynamically adjusted according to the specific actual needs of the service. This application sets a bandwidth utilization threshold. When the peak actual bandwidth utilization of the service transmission link is less than this threshold, the bandwidth allocated to the transmission link and protection link for that service is reduced until the bandwidth utilization of the transmission link is exactly equal to the threshold; when the peak actual bandwidth utilization of the service transmission link is greater than this threshold, the bandwidth allocated to the transmission link and protection link for that service is increased until the bandwidth utilization of the transmission link is exactly equal to the threshold.

[0062] The transmission link can be understood as the link that carries daily business traffic, while the protection link is the link activated in fault scenarios. Due to the periodic fluctuations in business traffic (such as peak working hours and nighttime backup tasks), the bandwidth of the two links is dynamically adjusted according to the actual bandwidth utilization to balance resource utilization efficiency and cost.

[0063] Specifically, this application pre-sets a bandwidth utilization threshold, for example, a preset dynamic adjustment threshold of 70% (configurable). When the actual bandwidth utilization peak continuously exceeds or falls below the threshold for a certain period of time, the adjustment process is initiated. Bandwidth adjustment logic.

[0064] In capacity expansion scenarios, the bandwidth of transmission and protection links is increased in a tiered manner based on the percentage exceeding the threshold. (Example: initial expansion by 10%, followed by a second expansion of 15% if the threshold is still exceeded). Protection link bandwidth is increased synchronously to ensure consistent capacity between primary and backup links and avoid congestion during failover. Monitoring continues after expansion until the peak value falls back to near the threshold.

[0065] In scaling down scenarios, bandwidth is reduced gradually (e.g., by 5% each time) to avoid instantaneous congestion caused by sudden traffic surges. The lower limit of the protection link bandwidth is set to the minimum guaranteed bandwidth required for failover (e.g., 50% of the main link) to prevent excessive scaling down from affecting redundancy. If the peak value rises above the threshold after scaling down, reverse scaling up is triggered.

[0066] This application utilizes dynamic bandwidth adjustment, achieving results within minutes. If packet loss or latency anomalies occur on the link after adjustment, it automatically reverts to the previous stable configuration and triggers an alarm to notify operations and maintenance personnel. Through dynamic adjustment, bandwidth resource utilization can be stabilized around the threshold while ensuring that services meet service levels, reducing idle resource waste and avoiding performance degradation caused by sudden traffic surges.

[0067] Optionally, after dynamically adjusting the bandwidth of the configured transmission link and the protection link based on the actual bandwidth utilization, the method further includes:

[0068] Obtain the actual bandwidth value of all service transmissions after dynamic adjustment;

[0069] If each of the actual bandwidth values ​​is greater than or less than the corresponding preset value of the template, then the link configuration template is updated using the maximum bandwidth value among all the actual bandwidth values.

[0070] In this embodiment, the SR-TP / MTN / fgMTN link configuration template of the SCU is adjusted based on the actual stable SR-TP / MetroTransport Network (MTN) / fine granularity MTN (fgMTN) link configuration of the SCU. Specifically, if, after dynamic adjustment, the actual link bandwidth of all service transmission links in a certain SCU is greater than the default configuration template, the corresponding configuration template is updated to update the configuration bandwidth to the largest bandwidth among all links; if, after dynamic adjustment, the actual link bandwidth of all service transmission links is less than the default configuration template, the corresponding configuration template is updated to update the configuration bandwidth to the largest bandwidth among all links, which is then used as the configuration template for the SCU.

[0071] For example, the SCU constructs transmission links based on SR-TP, MTN, and fgMTN technologies, and predefines default link configuration templates (e.g., SR-TP link bandwidth = 1Gbps, MTN link bandwidth = 800Mbps, fgMTN link bandwidth = 500Mbps). The SCU continuously optimizes link capacity through a dynamic bandwidth adjustment mechanism. It needs to automatically update the link configuration template based on the comparison between the adjusted actual bandwidth and the default template to ensure that the template always adapts to the actual business needs.

[0072] After all service transmission links (including SR-TP / MTN / fgMTN types) associated with a certain SCU have completed dynamic bandwidth adjustment, the system collects the actual operating bandwidth of each link. If the actual bandwidth of all links is greater than the default template value, or less than the default template value, a template update is triggered. This application adopts an upward update strategy (actual bandwidth > default value): that is, the link bandwidth in the template is uniformly updated to the maximum actual bandwidth value among all links. Example: SR-TP link actual bandwidth = 1.2Gbps (default 1Gbps); MTN link actual bandwidth = 1.1Gbps (default 800Mbps); fgMTN link actual bandwidth = 600Mbps (default 500Mbps); updated template: SR-TP = 1.2Gbps, MTN = 1.2Gbps, fgMTN = 1.2Gbps (the maximum value is taken for uniform coverage).

[0073] This application updates downwards (actual bandwidth is less than the default value): The link bandwidth in the template is also updated to the maximum actual bandwidth value among all current links (even if this value is lower than the original default value). Example: SR-TP link actual bandwidth = 800Mbps (default 1Gbps); MTN link actual bandwidth = 700Mbps (default 800Mbps); fgMTN link actual bandwidth = 400Mbps (default 500Mbps); Updated template: SR-TP = 800Mbps, MTN = 800Mbps, fgMTN = 800Mbps.

[0074] This application requires strict consistency between the template updates for transmission links and protection links to avoid service interruptions due to bandwidth differences during handover. It checks whether the actual bandwidth of all links is either higher or lower than the default template value. Example: If the actual bandwidth of all links is higher than the default value during peak hours, an upward update is triggered. If the actual bandwidth of all links is lower than the default value during off-peak hours, a downward update is triggered. The updated template is automatically distributed to the SCU, and service performance indicators (such as latency and packet loss rate) are continuously monitored. If an anomaly occurs after the update (such as bandwidth overload or insufficient redundancy), it automatically reverts to the previous template version and generates an alarm log.

[0075] Optionally, during template updates, bandwidth for high-priority services (such as 5G slicing) must be prioritized through a hard isolation strategy to prevent updates from impacting core services. This application can also combine historical template update records to predict future bandwidth demand trends (such as quarterly traffic growth) and optimize the initial values ​​of the default template in advance.

[0076] This application avoids bandwidth resource waste (such as during off-peak hours at night) or capacity shortages (such as during periods of sudden business surges) caused by outdated default templates through dynamic template updates. Link templates are updated uniformly to ensure that the capacity of backup links perfectly matches that of the primary link during failover, eliminating failover risks. Manual intervention is reduced by achieving template self-optimization through a closed-loop detection-adjustment-update mechanism.

[0077] Optionally, before step 11 above, the method further includes:

[0078] Establish an IP address database; the IP address database includes a list of pre-stored IP addresses of SCU network elements;

[0079] When the IP address of the transmission network element appears for the first time, determine whether the transmission network element is an SCU network element based on the network element hostname and domain name of the transmission network element.

[0080] If the transmission network element is the SCU network element, then the IP address of the transmission network element is updated to the IP address list, and the IP address of the transmission network element is forwarded and synchronized to each transmission network element.

[0081] Optionally, the data storage format of this application can be a distributed key-value database, which supports high-concurrency read and write operations and fast queries.

[0082] In this application, the IP address database is a relational or key-value database specifically used to store and manage SCU network element IP addresses. When the control function plane (also known as the management plane) detects a network element IP address for the first time, such as a new device coming online or an IP change, the following process is initiated: The hostname and DNS domain name of the network element are extracted, and hostname and domain name resolution is performed. Regular expression matching rules are used to determine whether it is an SCU network element. If the hostname contains the prefix SCU- or SMART-CU-, it is determined to be an SCU network element. For example, if the domain name belongs to a predefined SCU-specific domain (such as *.scu.operator.com), it is determined to be an SCU network element. If it is determined to be an SCU network element, the control function plane writes fields such as "ip_address, hostname, domain" into the SCU address database and marks "status=active, sync_status=false". If it is determined to be a non-SCU network element, only a log is recorded, and no data is written to the database. The control function plane pushes updates to all transmission network elements through message queues or network management protocols.

[0083] Add a record: Send an ADD operation command, carrying complete field information.

[0084] Update log: Send an UPDATE operation command, carrying only the changed fields (such as IP address or status).

[0085] After receiving the instruction, the transmission network element updates its local cache or sub-database and returns an acknowledgment response.

[0086] After receiving confirmation from all network elements, the control function plane will mark "sync_status" as true.

[0087] For example, a full database verification is performed every morning to ensure that the local SCU address database of all transmission network elements is consistent with the control plane. New or modified SCU network element records are pushed in real time through an event-driven mechanism (such as database triggers).

[0088] Optionally, if multiple control plane nodes modify the same IP address simultaneously, a versioning mechanism is used: each record contains a version field, the version number is verified during updates, and old version data is rejected from being overwritten. If synchronization fails (e.g., due to network interruption), the failure event is recorded and added to the retry queue, and an alarm is triggered after a maximum of a preset number of retries.

[0089] Furthermore, the system receives a request message from the transmission network element to activate the micro-cloud unit (SCU) link, including:

[0090] If the IP address of the transmission network element is not appearing for the first time, and the IP address corresponding to the source node or destination node of the transmission network element is stored in the IP address list, the source node or destination node of the transmission network element is determined to be the first SCU network element.

[0091] When the source node or destination node of the transmission network element is the first SCU network element and a transmission link corresponding to the received message of the transmission network element has not yet been established, the micro-cloud unit SCU link activation request message sent by the transmission network element is received.

[0092] The activation request message carries at least one of the following: the IP address of the source node or the destination node, SCU network element information, and service identification information.

[0093] Correspondingly, the client side of the transmission network element (e.g., using UNI) monitors the source / destination node IP addresses of service packets in real time. If the IP address of the source or destination node exists in the SCU address database and there is currently no established transmission link, it is determined to be a new SCU service transmission link opening requirement.

[0094] In this application, the control function plane receives the reported activation request message, which carries at least one of the following: the IP address of the source node or the destination node, SCU network element information, and service identification information; if the IP address of the source node or the destination node is not in the SCU address database, the SCU identification process is triggered first, and then the service request is processed.

[0095] Specifically, the newly deployed SCU network element (IP = 10.2.2.100, hostname = SCU-NE-03, domain name = scu.regionB.operator.com) connects to the transport network for the first time. The control plane detects the new IP, determines it as an SCU network element based on hostname and domain name rules, and writes it into the SCU address database. Real-time synchronization: The control plane sends synchronization commands to all transport network elements via Kafka, and the transport network elements update their local SCU address databases.

[0096] Service link activation trigger: The user-side device (IP=10.2.2.100) sends a service packet to another SCU network element (IP=10.2.2.200). The transmission network element UNI detects that the source IP=10.2.2.100 is in the SCU address database and that there is no existing link, and reports a service activation request. The control plane automatically creates an SR-TP transmission link and synchronously configures it to the primary and backup links.

[0097] The above-described process in this application supports the dynamic allocation of SCU network element IP addresses, updating the hostname-IP binding relationship periodically through DNS reverse resolution. Access to the SCU address database is subject to role-based access control, allowing only the control plane and authorized network elements to read and write. The database adopts a master-slave replication architecture to ensure no data loss in the event of a single point of failure. Through the above mechanism, automated identification, storage, and synchronization of SCU network element IP addresses, as well as intelligent activation of service links, can be achieved, improving network operation and maintenance efficiency.

[0098] Optionally, step 12 above includes:

[0099] Based on the activation request message, obtain the service identification information and service configuration parameters;

[0100] Based on the service identification information, an appropriate link configuration template is selected, including: selecting a first configuration template for ordinary services; selecting a second configuration template for small-granularity Time Division Multiplexing (TDM) services; and selecting a third configuration template for large-granularity TDM services. The first configuration template corresponds to the segmented routing transmission configuration file (SR-TP) pipe; the second configuration template corresponds to the fine-grained metropolitan area network (fgMTN) pipe; and the third configuration template corresponds to the metropolitan area network (MTN) pipe.

[0101] Configure the required transmission link based on the template parameters of the selected link configuration template and the service configuration parameters; wherein, missing parameters are assumed to be preset template values.

[0102] Configure the protection link according to the parameters of the transmission link, and allocate forwarding paths and pipeline resources for the transmission link and the protection link.

[0103] In this embodiment, dynamic configuration of transmission and protection links based on service type can be achieved. Based on the activation request message, service identification information is obtained, and different service types are identified through this information. These service types include, but are not limited to, ordinary 2C services, small-granularity TDM services, and large-granularity TDM services. According to the service identification information, an appropriate link configuration template is selected. This application sets three configuration templates: the first template corresponds to the segmented routing transmission configuration file SR-TP pipe; the second template corresponds to the fine-grained metropolitan area network fgMTN pipe; and the third template corresponds to the metropolitan area network MTN pipe.

[0104] The application dynamically selects the appropriate link configuration template (SR-TP / fgMTN / MTN) based on service identification information, and configures primary and backup links and allocates path resources. The specific implementation process is as follows: For example, based on service identification information, the current business scenario requires the activation of a large-granularity TDM service. Its service identification information is service_type = large_TDM, and the service configuration parameters include: Required parameters: bandwidth = 2Gbps, latency ≤ 20ms; Missing parameters: jitter tolerance, protection switching time (not specified in the request). This application parses the service identification information service_type = large_TDM and determines it to be a large-granularity TDM service. It selects the corresponding MTN link configuration template and configures the required transmission link using the service configuration parameters and the template default parameters. Required parameters are directly used, such as bandwidth = 2Gbps (specified in the service request, overriding the template default of 1Gbps); latency = 20ms (specified in the service request, but inferior to the template default of 10ms, requiring an alarm); missing parameters use the template default values: jitter tolerance = 2ms (taken from the template). Protection switching time = 50ms (taken from template).

[0105] Configure the protection link with parameters that are completely identical to the primary link (bandwidth, latency, jitter, etc.) to ensure that the primary and backup capacities match.

[0106] After configuring the transmission link and protection link, this application selects the optimal latency path (such as a direct fiber optic connection path) for the transmission link to ensure that the service latency requirement (≤20ms) is met. For the protection link, a path physically isolated from the main link (such as a different optical cable or transmission equipment) is selected to avoid single-point failures affecting the main and backup links. The configurations of the transmission link and the protection link are then distributed to the source and destination network elements using a preset model. An MTN pipeline is established between the transmission network elements, and a unique pipeline ID is assigned to each service.

[0107] Optionally, test traffic is sent to verify whether the transmission link latency and bandwidth utilization meet expectations. A simulated transmission link failure (such as fiber optic cable disconnection) is performed to verify that the protection link switching time is ≤50ms and that service is uninterrupted. Here, if the actual service bandwidth is subsequently detected to consistently exceed 2Gbps, a template update process is triggered (refer to the template update process described above), increasing the MTN template bandwidth to 3Gbps. The link configuration template in this application allocates transmission and protection links, assigning high-priority queues to large-granularity TDM services to ensure that large-granularity service data is forwarded preferentially during congestion. Sufficient redundant bandwidth is reserved for the MTN pipeline during path calculation to cope with sudden traffic surges.

[0108] This application utilizes templated configuration to quickly respond to the differentiated needs of various business types (such as low cost for general services and high reliability for TDM services). The design of consistent primary and backup link parameters and physical isolation ensures availability. The entire process from business request to link activation is automated, reducing manual intervention and configuration errors.

[0109] Specifically, when a transmission network element senses a service transmission link activation requirement and reports it to the control plane, it dynamically triggers the establishment of SR-TP / MTN / fgMTN pipelines: The control plane selects the corresponding link configuration template based on the service identification information of the SCU transmission link activation request; when the service identification information is a normal 2C service (voice, data), the SR-TP link configuration template is selected; when the service identification information is a small-granularity TDM service, the fgMTN link configuration template is selected; when the service identification information is a large-granularity TDM service, the MTN link configuration template is selected.

[0110] Obtain reference configuration parameters (delay, bandwidth, etc.) for at least one item to be configured from the corresponding SR-TP / MTN / fgMTN link configuration template, and complete the service transmission link parameter configuration in combination with the SCU network element's own service requirements.

[0111] For example, the service type matches the template: if the service type is a regular 2C service with characteristics of high bandwidth and low latency (such as video streaming), the link template should be the SR-TP template, which is based on segmented routing and supports dynamic path optimization; if the service type is a small-granularity TDM service with characteristics of fixed bandwidth and high reliability (such as voice leased lines), the link template should be the fgMTN template to achieve fine-grained resource allocation (1Mbps granularity); if the service type is a large-granularity TDM service with characteristics of ultra-large bandwidth and strict SLA (such as medical imaging), the link template should be the MTN template to achieve rigid pipe isolation and ensure end-to-end performance.

[0112] Specifically, existing configuration parameters in the service identification information are directly adopted, while missing configuration parameters are configured using the default parameters of the configuration template. Based on the determined service transmission link parameters, the same link parameter configuration is applied to the protection link. The control plane, based on the determined service transmission link and protection link configuration parameters, determines reasonable forwarding paths and pipeline resources, and opens the transmission and protection links for the target service between the source and destination network elements.

[0113] Optionally, this application also includes: the process of SCU removal and template reset. That is, when an SCU needs to be removed, it is reported to the control plane through the transmission network element, the IP address corresponding to the SCU network element in the SCU network element IP address database is deleted, and the link configuration template of the SCU is initialized.

[0114] Reference Figure 2As shown in the figure, this application embodiment also provides a specific flowchart of a link configuration method, including: identifying newly added SCU network elements in the network based on the network element hostname and DNS domain name, and distributing the IP addresses of all newly added SCU network elements to each transmission network element through the forwarding plane or the control plane; the transmission network element senses the source node and destination node IP addresses of the sent packets in real time on the UNI side; when the IP address of the source node or destination node corresponds to an SCU network element, and there is currently no available established transmission link, the link activation requirement is reported to the control plane. The service activation request carries source and destination node information, as well as service identification information. Based on the service identification information, a corresponding link configuration template is selected, and reference configuration parameters (pipe type, bandwidth, etc.) for at least one item to be configured are obtained from the link configuration template to complete the configuration of the service transmission link and protection link parameters. The control plane determines reasonable forwarding paths and pipe resources based on the determined service transmission link and protection link configuration parameters, and activates the transmission link and protection link for the target service between the source and destination network elements. The bandwidth resource allocation of the service transmission link and protection link is dynamically adjusted according to the specific actual needs of the service, and the template is also dynamically adjusted.

[0115] This application utilizes three main components: service transmission link activation demand awareness, allocation of transmission links and protection links according to link configuration templates, and dynamic adjustment of bandwidth allocation based on service transmission conditions. Specifically, it is manifested in at least one of the following aspects:

[0116] (1) Identify and establish the IP address database corresponding to the SCU. The transmission network element senses the IP addresses of the source node and the destination node of the sent message on the UNI side. When the IP address of the source node or the destination node corresponds to the SCU network element, a link opening request is triggered.

[0117] (2) When the transmission network element senses that there is a need to open a service transmission link and reports it to the control plane, it dynamically triggers the establishment of SR-TP / MTN / fgMTN pipelines as service transmission links and protection links based on the service identification information and the link configuration template.

[0118] (3) Dynamically adjust the bandwidth allocation of the service transmission link and protection link according to the service transmission situation, and adjust the link configuration template according to the actual link situation.

[0119] This application, based on the perception of the IP address of the UNI-side message, determines the service connection request connected to the SCU and dynamically configures the transmission path between the base station and the SCU. This solves the problem of previous transmission links requiring pre-configuration and lacking flexibility, effectively improving the activation efficiency of service transmission links and meeting the needs of plug-and-play SCUs with flexible spatial and temporal scenarios.

[0120] In summary, this application implements a full-cycle management process. Link activation: SCU network element IP identification → template selection → parameter configuration → primary / backup link establishment. Bandwidth adjustment: real-time monitoring → threshold triggering → dynamic expansion / contraction → configuration synchronization. Link teardown: releasing bandwidth resources after service termination → deleting link configuration → updating IP address database status.

[0121] The templated configuration in this application reduces human error and effectively improves the accuracy of link parameter matching; the bandwidth adjustment response time is shortened, ensuring service quality under business fluctuations; the dynamic resource pool improves bandwidth utilization and reduces static reservation waste.

[0122] The various methods of the embodiments of this application have been described above. Apparatus for implementing the above methods will now be provided.

[0123] Please refer to Figure 3 This application also provides a link configuration device, including:

[0124] The receiving module 31 is used to receive the activation request message of the micro cloud unit (SCU) link sent by the transmission network element. The activation request message is sent when the source node or the destination node of the user network interface senses the IP address of the sending message, determines that the source node or the destination node is the first SCU network element, and the transmission link corresponding to the message has not yet been established.

[0125] The first processing module 32 is used to select an appropriate link configuration template based on the activation requirement message, and configure the required transmission link and protection link according to the link configuration template.

[0126] Optionally, the link configuration device provided in this application embodiment further includes:

[0127] The monitoring module is used to monitor the actual bandwidth utilization of the transmission link for transmitting services.

[0128] The second processing module is used to dynamically adjust the bandwidth of the configured transmission link and the protection link based on the actual bandwidth utilization.

[0129] Optionally, the second processing module described above includes:

[0130] The first processing unit is used to set the threshold for bandwidth utilization.

[0131] The second processing unit is configured to reduce the bandwidth of the transmission link and the protection link if the peak value of the actual bandwidth utilization is less than the threshold value, and increase the bandwidth of the transmission link and the protection link if the peak value is greater than the threshold value, until the actual bandwidth utilization is equal to the threshold value.

[0132] Optionally, the link configuration device provided in this application embodiment further includes:

[0133] The acquisition module is used to obtain the actual bandwidth value of all service transmissions after dynamic adjustment.

[0134] The third processing module is used to update the link configuration template by using the maximum bandwidth value among all the actual bandwidth values ​​if each of the actual bandwidth values ​​is greater than or less than the corresponding preset value of the corresponding template.

[0135] Optionally, the link configuration device provided in this application embodiment further includes:

[0136] The fourth processing module is used to establish an IP address database; the IP address database includes a list of pre-stored IP addresses of SCU network elements;

[0137] The first determining module is used to determine whether the transmission network element is an SCU network element when the IP address of the transmission network element appears for the first time, based on the network element hostname and domain name of the transmission network element.

[0138] The fifth processing module is used to update the IP address of the transmission network element to the IP address list if the transmission network element is the SCU network element, and to forward and synchronize the IP address of the transmission network element to each transmission network element.

[0139] Optionally, the receiving module 31 described above includes:

[0140] The third processing unit is used to determine that the source node or destination node of the transmission network element is the first SCU network element, since the IP address of the transmission network element is not appearing for the first time and the IP address corresponding to the source node or destination node of the transmission network element is stored in the IP address list.

[0141] The receiving unit is configured to receive the micro-cloud unit SCU link activation request message sent by the transmission network element when the source node or destination node of the transmission network element is the first SCU network element and the transmission link corresponding to the received message of the transmission network element has not yet been established.

[0142] The activation request message carries at least one of the following: the IP address of the source node or the destination node, SCU network element information, and service identification information.

[0143] Optionally, the first processing module 32 described above includes:

[0144] The acquisition unit is used to acquire service identification information and service configuration parameters based on the activation request message;

[0145] The fourth processing unit is configured to select an appropriate link configuration template based on the service identification information, including: selecting a first configuration template in the case of ordinary services; selecting a second configuration template in the case of small-granularity time-division multiplexing (TDM) services; and selecting a third configuration template in the case of large-granularity TDM services. The first configuration template corresponds to the segmented routing transmission configuration file (SR-TP) pipe; the second configuration template corresponds to the fine-grained metropolitan area network (fgMTN) pipe; and the third configuration template corresponds to the metropolitan area network (MTN) pipe.

[0146] The fifth processing unit is used to configure the required transmission link according to the template parameters of the selected link configuration template and the service configuration parameters; wherein, the missing parameters adopt the template preset value;

[0147] The sixth processing unit is used to configure the protection link according to the parameters of the transmission link, and to allocate forwarding paths and pipeline resources for the transmission link and the protection link.

[0148] It should be noted that the device in this embodiment corresponds to the method applied to the management surface described above. The implementation methods in each of the above embodiments are also applicable to the embodiments of this device and can achieve the same technical effect. The device provided in this application embodiment can implement all the method steps implemented in the above method embodiments and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiments and the beneficial effects will not be described in detail.

[0149] This application also provides a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the various processes of the above-described link configuration method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0150] This application also provides a computer program product, including computer instructions. When the computer instructions are executed by a processor, they implement the various processes of the above-described link configuration method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0151] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0152] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of 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. The 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 (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0153] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A link configuration method, characterized in that, The transmission network element receives a micro-cloud unit (SCU) link activation request message sent by the transmission network element. The activation request message is sent by the transmission network element when it determines that the source node or the destination node is the first SCU network element based on the IP address of the source node or the destination node that sent the message through the user network interface, and the transmission link corresponding to the message has not yet been established. Select an appropriate link configuration template based on the activation request message, and configure the required transmission link and protection link according to the link configuration template.

2. The method according to claim 1, characterized in that, After configuring the required transmission link and protection link according to the link configuration template, the method further includes: Monitor the actual bandwidth utilization of the transmission link for transmitting services; Based on the actual bandwidth utilization, the bandwidth of the configured transmission link and the protection link is dynamically adjusted.

3. The method according to claim 2, characterized in that, Based on the actual bandwidth utilization, dynamic bandwidth adjustment is performed on the configured transmission link and protection link, including: Set a threshold for bandwidth utilization; If the peak value of the actual bandwidth utilization is less than the threshold value, the bandwidth of the transmission link and the protection link is reduced; if the peak value is greater than the threshold value, the bandwidth of the transmission link and the protection link is increased until the actual bandwidth utilization is equal to the threshold value.

4. The method according to claim 2, characterized in that, Based on the actual bandwidth utilization, after dynamically adjusting the bandwidth of the configured transmission link and the protection link, the method further includes: Obtain the actual bandwidth value of all service transmissions after dynamic adjustment; If each of the actual bandwidth values ​​is greater than or less than the corresponding preset value of the template, then the link configuration template is updated using the maximum bandwidth value among all the actual bandwidth values.

5. The method according to claim 1, characterized in that, Before receiving the activation request message for the micro-cloud unit (SCU) link sent by the transmission network element, the method further includes: Establish an IP address database; the IP address database includes a list of pre-stored IP addresses of SCU network elements; When the IP address of the transmission network element appears for the first time, determine whether the transmission network element is an SCU network element based on the network element hostname and domain name of the transmission network element. If the transmission network element is the SCU network element, then the IP address of the transmission network element is updated to the IP address list, and the IP address of the transmission network element is forwarded and synchronized to each transmission network element.

6. The method according to claim 5, characterized in that, Receive the activation request message for the Micro Cloud Unit (SCU) link sent by the transmission network element, including: If the IP address of the transmission network element is not appearing for the first time, and the IP address corresponding to the source node or destination node of the transmission network element is stored in the IP address list, the source node or destination node of the transmission network element is determined to be the first SCU network element. When the source node or destination node of the transmission network element is the first SCU network element and a transmission link corresponding to the received message of the transmission network element has not yet been established, the micro-cloud unit SCU link activation request message sent by the transmission network element is received. The activation request message carries at least one of the following: the IP address of the source node or the destination node, SCU network element information, and service identification information.

7. The method according to claim 1, characterized in that, Based on the activation request message, a suitable link configuration template is selected, and the required transmission link and protection link are configured according to the link configuration template, including: Based on the activation request message, obtain the service identification information and service configuration parameters; Based on the service identification information, an appropriate link configuration template is selected, including: selecting a first configuration template for ordinary services; selecting a second configuration template for small-granularity Time Division Multiplexing (TDM) services; and selecting a third configuration template for large-granularity TDM services. The first configuration template corresponds to the segmented routing transmission configuration file (SR-TP) pipe; the second configuration template corresponds to the fine-grained metropolitan area network (fgMTN) pipe; and the third configuration template corresponds to the metropolitan area network (MTN) pipe. Configure the required transmission link based on the template parameters of the selected link configuration template and the service configuration parameters; wherein, missing parameters are used with template preset values; Configure the protection link according to the parameters of the transmission link, and allocate forwarding paths and pipeline resources to the transmission link and the protection link.

8. A link configuration device, characterized in that, include: The receiving module is used to receive the activation request message for the SCU link sent by the transmission network element; The activation request message is sent by the transmission network element when it determines that the source node or the destination node is the first SCU network element based on the IP address of the source node or the destination node that sent the message through the user network interface, and the transmission link corresponding to the message has not yet been established. The first processing module is used to select an appropriate link configuration template based on the activation requirement message, and configure the required transmission link and protection link according to the link configuration template.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method as described in any one of claims 1 to 7.

10. A computer program product, characterized in that, Includes computer instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1 to 7.

Images