Bandwidth configuration method, electronic device, and storage medium

Abstract

The present application relates, but is not limited, to the technical field of communications, and provides a bandwidth configuration method, an electronic device, and a storage medium. The bandwidth configuration method comprises: sending a request message to a management and control system, the request message carrying bandwidth requirement information; receiving an acknowledgement message returned by the management and control system, the acknowledgement message carrying bandwidth confirmation information generated by the management and control system on the basis of the bandwidth requirement information; and on the basis of the bandwidth confirmation information, generating a slot configuration message, and sending the slot configuration message to a downstream device, so that the downstream device performs a slot configuration operation on the basis of the slot configuration message.

Description

Bandwidth configuration method, electronic device, and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is based on the Chinese patent application with application number 2023112944554 and application date September 28, 2023, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby introduced into this application as a reference. Technical Field

[0003] The embodiments of the present application relate to the field of communication technologies, and in particular to a bandwidth configuration method, an electronic device, and a storage medium. Background Art

[0004] A frame structure is usually used in communication networks to carry customer services. Specifically, time slots are divided in the bearer frame and used to carry services. In related technologies, lossless bandwidth adjustment technology requires control and distribution of time slot adjustment information to all network elements involved in the adjustment, including PE nodes and P nodes. Specifically, the existing lossless bandwidth adjustment requires multiple negotiations on the forwarding plane for the time slot configuration request indication information (Configuration Request, CR) / time slot configuration response indication information (Configuration Acknowledge, CA) / time slot configuration effective indication information (Configuration come into force, C). Especially for scenarios where the adjustment cannot be successful, multiple collaborations and fallbacks between the equipment and the network management are involved, which places high demands on the network management. Since there is no control plane, the network management needs to issue it node by node, which places high demands on control. Therefore, in scenarios where the time slot granularity is small and the number of time slots is large, the bandwidth configuration method of the related technology has a high complexity on the forwarding plane and low service deployment efficiency.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a bandwidth configuration method, an electronic device, and a storage medium, which can provide a bandwidth configuration method suitable for scenarios with small time slot granularity and a large number of time slots, reduce the complexity of the forwarding plane, increase the bandwidth configuration rate, and improve service deployment efficiency.

[0007] In a first aspect, an embodiment of the present application provides a bandwidth configuration method, which is applied to a source device and includes:

[0008] Sending a request message to the management and control system, wherein the request message carries bandwidth demand information;

[0009] receiving a response message returned by the management and control system, wherein the response message carries bandwidth confirmation information generated by the management and control system according to the bandwidth demand information;

[0010] A timeslot configuration message is generated according to the bandwidth confirmation information, and the timeslot configuration message is sent to a downstream device, so that the downstream device performs a timeslot configuration operation according to the timeslot configuration message.

[0011] In a second aspect, an embodiment of the present application provides a bandwidth configuration method, which is applied to a management and control system, and includes:

[0012] receiving a request message sent by a source device, wherein the request message carries bandwidth requirement information;

[0013] generating bandwidth confirmation information according to the bandwidth demand information, and encapsulating the bandwidth confirmation information into response information;

[0014] The response message is returned to the source device, wherein the response message carries the bandwidth confirmation information, so that the source device generates a time slot configuration message according to the bandwidth confirmation information and sends the time slot configuration message to the downstream device.

[0015] In a third aspect, an embodiment of the present application provides an electronic device, including:

[0016] one or more processors;

[0017] A memory having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the bandwidth configuration method as described in the first aspect above; or the bandwidth configuration method as described in the second aspect above.

[0018] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the bandwidth configuration method as described in the first aspect above; or, the bandwidth configuration method as described in the second aspect above.

[0019] In an embodiment of the present application, a request message is sent to the management and control system through the source device, wherein the request message carries bandwidth demand information. The source device receives a response message returned by the management and control system, wherein the response message carries bandwidth confirmation information generated by the management and control system based on the bandwidth demand information, thereby achieving accurate connection between the source device and the management and control system. Afterwards, the source device generates a time slot configuration message based on the bandwidth confirmation information, and sends a time slot configuration message to the downstream device, so that the downstream device performs the time slot configuration operation according to the time slot configuration message. Therefore, compared with the related art, the embodiment of the present application can provide a bandwidth configuration method suitable for PCE scenarios with small time slot granularity and a large number of time slots, which reduces the complexity of the forwarding plane, increases the bandwidth configuration rate, and improves the efficiency of service deployment. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The accompanying drawings are used to provide a further understanding of the technical solution of the present application and constitute a part of the specification. Together with the embodiments of the present application, they are used to explain the technical solution of the present application and do not constitute a limitation on the technical solution of the present application.

[0021] FIG1 is a schematic diagram of transmission of a bearer frame between nodes in the related art;

[0022] 2A-2C are schematic diagrams of frame structures in related art;

[0023] FIG3 is a schematic diagram of a time slot negotiation and adjustment process under reduced time slot requirements in the related art;

[0024] FIG4 is a schematic diagram of a time slot negotiation and adjustment process under increased time slot requirements in the related art;

[0025] FIG5 is a schematic diagram of a process for broadband configuration according to an embodiment of the present application;

[0026] FIG6 is a schematic diagram of the interaction between a source device, a management and control system, and a downstream node for broadband configuration according to an embodiment of the present application;

[0027] FIG7 is a schematic diagram of a format of a request parameter RP provided in an embodiment of the present application;

[0028] FIG8 is a schematic diagram of a format of a bandwidth specification object provided in an embodiment of the present application;

[0029] FIG. 9 is a schematic diagram of a format of a signal type object provided in an embodiment of the present application.

[0030] 10 is a schematic diagram of the interaction between the source device, the control system and the downstream node for performing broadband configuration according to the next embodiment of the present application in which the corresponding time slot configuration operation is added;

[0031] FIG11 is a schematic diagram of a format of time slot configuration information provided by an embodiment of the present application;

[0032] FIG12 is a schematic diagram of interaction between a source device, a management and control system, and a downstream node for performing broadband configuration according to another embodiment of the present application;

[0033] 13 is a schematic diagram of the interaction between the source device, the management and control system, and the downstream node for broadband configuration according to the next embodiment of the present application in which encapsulation response information is added;

[0034] FIG14 is a schematic diagram of the device structure of the electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0035] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0036] It should be understood that in the description of the embodiments of the present application, if there is a description of "first", "second", etc., it is only for the purpose of distinguishing technical features, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features or implicitly indicating the order of the indicated technical features. "At least one" means one or more, and "more" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent the existence of A alone, the existence of A and B at the same time, and the existence of B alone. Among them, A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" and similar expressions refer to any group of these items, including any group of single or plural items. For example, at least one of a, b and c can represent: a, b, c, a and b, a and c, b and c, or a, b and c, where a, b, c can be single or multiple.

[0037] In addition, the technical features involved in each embodiment of the present application described below can be combined with each other as long as they do not conflict with each other.

[0038] To facilitate understanding of the solutions of the embodiments of the present application and to provide a clear and concise description of the following embodiments, a brief introduction to the relevant technologies is first given:

[0039] Path Computation Element (PCE): A component that calculates constrained paths based on network topology information. A PCE can be deployed in a routing device or on a standalone server. Most often, the PCE and management system are integrated.

[0040] Path Computation Client (PCC): A client application that requests a path computation element (PCE) to perform path computation. The PCC sends path requests to the PCE and receives the path computation results back from the PCE. Therefore, a routing device can be considered a device with integrated PCC functionality, or a routing device can be considered a PCC.

[0041] Path Computation Element Protocol (PCEP): This is the communication protocol between the PCC and PCE. PCEP defines a set of messages and objects used to manage PCEP sessions and to request paths for Traffic Engineering Label Switched Paths (TE LSPs).

[0042] Communication networks typically use a frame structure to carry customer services. Specifically, time slots are divided within a bearer frame, and these slots are used to carry services. The time slots can be divided into multiple slots within a bearer frame, or they can be divided across multiple bearer frames. Figure 1 is a schematic diagram of the transmission of bearer frames between nodes in related art. As shown in Figure 1, the nodes carrying customer services are a source node 100, a sink node 300, and two intermediate nodes 200. Each node can be a bearer node that supports international standard protocols, a sliced ​​packet network node that supports related technical definitions, or other types of bearer nodes. Bearer frames 410-440 consist of a header, a container, and a trailer. Time slots are divided within the container of the bearer frame, and the time slot positions are fixed, traveling with the bearer frame within the network. Each customer service can choose to be carried in a fixed time slot, with different customers using different time slot positions for service carrying. Time slots are divided according to the time slot granularity of the service layer. When customer bandwidth is high, multiple time slot positions are used for service carrying, while when customer bandwidth is low, a smaller number of time slot positions are used for service carrying. When carrying customer services, the source node 100 maps the customer services to the corresponding time slots of the bearer frame and sends them out. The intermediate node 200 completes the time slot forwarding, and the destination node 300 extracts the customer services from the corresponding time slots and restores the original customer services.

[0043] Figures 2A-2C are schematic diagrams of the frame structure in the related art. Figures 2A and 2B are schematic diagrams of the time slot division method of fg-BU. One time slot of fg-BU occupies 65 bytes (Byte, B). As shown in Figure 2C, the bearer frame generally has a fixed frame structure. According to the frame structure in the standard document "Technical Requirements for Fine-Grained Slicing of Sliced ​​Packet Networks", the bearer frame consists of 1 S code block, 195 D code blocks, and 1 T code block. The S code block, D code block, and T code block are 66-bit code block formats defined by the 802.3 standard specification. In addition to defining the S code block, D code block, and T code block, the standard also defines the O code block and IDLE code block (idle code block). Overhead bytes and 24 time slots are divided on the D code block in the bearer frame. Every 20 frames form a multiframe, so there are 480 time slots in one cycle. The overhead bytes in the bearer frame may include the following information: multi-frame indicator (MFI), general communication channel information (GCC), time slot number information (Slot num), time slot configuration request indication information (Configuration Request, CR), time slot configuration response indication information (Configuration Acknowledge, CA), time slot configuration effective indication information (Configuration come into force, C), and time slot increase adjustment notification information (Send notice, S).

[0044] In actual business applications, initially, customer bandwidth is low, requiring a small amount of bearer channel bandwidth, and only a small number of bearer time slots are needed to meet customer needs. Over time, as customer traffic increases, bandwidth increases, and more time slots are needed to carry customer traffic. Therefore, the number of time slots must be increased without disrupting or interrupting customer traffic. Conversely, for customers experiencing declining traffic, bandwidth decreases over time, requiring a reduction in the number of time slots used to carry traffic. Therefore, the number of time slots required to carry customer traffic must be dynamically adjusted without disrupting customer traffic.

[0045] In the related art, time slot negotiation and adjustment are performed in a hop-by-hop negotiation and hop-by-hop adjustment manner, that is, all nodes between the end and the end perform time slot negotiation and time slot adjustment with each other in turn; and since each time slot negotiation is performed for a single adjusted time slot, it is necessary to complete each time slot negotiation and time slot adjustment before responding to the increase or decrease in customer service needs. However, in actual applications, there is uncertainty in the increase or decrease in customer service needs, and each time slot negotiation and time slot adjustment between two adjacent nodes takes a certain amount of time, resulting in low efficiency of end-to-end time slot negotiation. In addition, the lossless bandwidth adjustment technology in the related art requires the control and distribution of time slot adjustment information to all network elements involved in the adjustment, including PE nodes and P nodes. Specifically, the existing lossless bandwidth adjustment requires multiple negotiations on the forwarding plane for the timeslot configuration request indication information (Configuration Request, CR) / time slot configuration response indication information (Configuration Acknowledge, CA) / time slot configuration effective indication information (Configuration come into force, C). Especially for scenarios where the adjustment cannot be successful, it involves multiple collaborations and fallbacks between the equipment and the network management, which places high demands on the network management. Since there is no control plane, the network management needs to issue it node by node, which places high demands on management and control. Therefore, in scenarios where the time slot granularity is small and the number of time slots is large, the bandwidth configuration method of the related technology has a high complexity on the forwarding plane and low service deployment efficiency.

[0046] In the bandwidth adjustment under the Path Computation Element (PCE) scenario, by adding general bandwidth objects and general bandwidth objects carried during re-optimization, multiple bandwidth specific types can be reused. However, the bandwidth configuration party of the related technology does not consider time division multiplexing of fine granularity (fg). For example, the optical distribution network (ODN) of the Optical Transport Network (OTN) has a large multiplexing time slot granularity and a small number of time slots. The general label defined in the Resource Reservation Protocol-Traffic Engineering (RSVP-TE) based on the traffic engineering extension can be used directly. However, for scenarios such as fg with a large number of service layer time slots, general labels are not fully applicable. For example, due to bandwidth increase or decrease, the current Label Switch Path (LSP) needs to be deleted on the control plane and a new LSP needs to be established. This allows the bandwidth change requirement to be confirmed based on the new and old service parameters. The full time slot is then carried in the universal label so that the local full time slot can be compared with the full time slot in the universal label on the device side. Therefore, in scenarios where the time slot granularity is small and the number of time slots is large, the bandwidth configuration method of the related technology has a high forwarding plane complexity and low service deployment efficiency.

[0047] Based on this, the present application provides a bandwidth configuration method, electronic device, and storage medium, which uses the control plane to assist in the service establishment and bandwidth adjustment scheme of the forwarding plane, thereby reducing the requirements for the management plane. The present application can provide a bandwidth adjustment method suitable for the Path Computation Element (PCE) scenario, which can effectively implement bandwidth configuration in scenarios with small time slot granularity and a large number of time slots, reduce the complexity of the forwarding plane, and increase the bandwidth configuration rate, that is, improve the end-to-end time slot negotiation efficiency and improve the service deployment efficiency.

[0048] Figure 3 is a schematic diagram of the time slot negotiation and adjustment process for reducing time slot demand in the related art using a hop-by-hop negotiation and adjustment method. As shown in Figure 3, the nodes carrying services include a source node 100, a sink node 300, and two intermediate nodes 200, where the two intermediate nodes 200 are nodes P1 and P2. The sink node 300, nodes P1, and nodes P2 are downstream nodes of the source node 100. When a time slot needs to be reduced, the source node 100 sends a Time Slot Configuration Request Indication (CR) signal to node P1. The CR signal carries the number of the time slot to be reduced, prompting node P1 to reduce the number of the time slot to be adjusted. After receiving the Time Slot Configuration Request Indication (CR) signal, node P1 completes preparations and sends a Time Slot Configuration Acknowledgement (CA) signal to the source node 100. After source node 100 receives the Time Slot Configuration Response Indication (CA) signal from node P1, the negotiation process for time slot reduction adjustment between source node 100 and node P1 is completed. Source node 100 sends a Time Slot Configuration Effectiveness Indication (C) signal to node P1. Then, source node 100 and node P1 carry customer services based on the reduced time slot positions. After node P1 receives the Time Slot Configuration Effectiveness Indication (C) signal from source node 100, it begins sending a Time Slot Configuration Request Indication (CR) signal to node P2, simultaneously sending the number of the time slot to be reduced. After receiving the Time Slot Configuration Request Indication (CR) signal, node P2 completes its preparations and sends a Time Slot Configuration Response Indication (CA) signal to node P1. After node P1 receives the Time Slot Configuration Response Indication (CA) signal from node P2, the negotiation process for time slot reduction adjustment between nodes P1 and P2 is completed. After receiving the time slot configuration response indication signal (CA) from node P2, node P1 sends a time slot configuration validation indication signal (C) to node P2. Nodes P1 and P2 then carry customer services in the reduced and adjusted time slots. Similarly, node P2 and sink node 300 also complete the time slot reduction negotiation and adjustment process, completing all time slot adjustment processes. During the time slot reduction adjustment process, the number of time slots between upstream adjacent nodes is first reduced. Only after the number of time slots of the upstream adjacent nodes is reduced does the time slot reduction operation begin for the nodes downstream of the adjusted nodes. This ensures that the number of time slots between upstream nodes is always less than that between downstream nodes, meaning that the service bandwidth between upstream nodes is less than that between downstream nodes. This prevents service overflow at certain nodes due to the upstream service bandwidth being greater than the downstream service bandwidth in the pipeline. Therefore, during the adjustment process, the end-to-end bandwidth reduction adjustment for the service is completed only after the last two nodes complete the time slot reduction adjustment. Therefore, it is not possible to continue responding to time slot negotiation and time slot adjustment before the time slot reduction request of the current customer service demand is completed.

[0049] Figure 4 is a schematic diagram of the time slot negotiation and adjustment process for increasing time slots during time slot negotiation and adjustment using a hop-by-hop negotiation and adjustment approach. Two intermediate nodes 200, namely, node P1 and node P2, are provided between the source node 100 and the sink node 300. Source node 100, node P1, and node P2 are upstream nodes of sink node 300. As shown in Figure 4 , to ensure that the service bandwidth between upstream nodes is less than the service bandwidth between downstream nodes, the relevant art stipulates that the time slot increase adjustment begins at sink node 300. Sink node 300 sends a time slot increase adjustment notification signal (S) to node P2. Upon receiving the time slot increase adjustment notification signal, node P2 initiates the time slot increase adjustment and sends a time slot configuration request indication signal (CR) to sink node 300, along with the number of the time slot to be increased. After receiving the time slot configuration request indication signal (CR), sink node 300 completes its preparations and sends a time slot configuration response indication signal (CA) back to node P2. After receiving the Slot Configuration Response Indication (CA) signal from sink node 300, node P2 completes the time slot adjustment negotiation process between node P2 and sink node 300. Node P2 then sends a Slot Configuration Validation Indication (C) signal to sink node 300. Node P2 and sink node 300 then carry customer services using the adjusted time slots. Simultaneously, node P2 sends a Slot Increase Adjustment Notification (S) signal to node P1. After receiving the Slot Increase Adjustment Notification (S), node P1 initiates the time slot increase negotiation process and sends a Slot Configuration Request Indication (CR) signal to node P2, along with the number of the time slot to be increased. After receiving the Slot Configuration Request Indication (CR) signal, node P2 completes its preparations and returns a Slot Configuration Response Indication (CA) signal to node P1. After node P1 receives the timeslot configuration response indication (CA) signal from node P2, the negotiation process for increasing timeslots between nodes P1 and P2 is completed. Node P1 then sends a timeslot configuration validation indication (C) signal to node P2. Nodes P1 and P2 then carry customer services using the adjusted timeslots. Simultaneously, node P1 sends a timeslot increase adjustment notification (S) signal to source node 100. Similarly, only after source node 100 and node P1 complete the timeslot increase negotiation and timeslot increase adjustment process are all timeslot increase and adjustment processes complete. The adjustment process is negotiated and completed segment by segment. During the timeslot increase and adjustment process, the number of timeslots between downstream nodes is always increased first, followed by that between upstream nodes. The number of timeslots between upstream nodes is always kept smaller than that between downstream nodes. This means that the service bandwidth between upstream nodes is smaller than that between downstream nodes. This prevents the upstream service bandwidth from being greater than the downstream service bandwidth in the pipeline, which could lead to service overflow. During the time slot increase adjustment process, the end-to-end bandwidth increase adjustment of the service is completed only after the time slot increase adjustment of the last two nodes is completed.Therefore, the completion of end-to-end time slot negotiation requires that time slot negotiation and time slot adjustment be completed in sequence between every two adjacent nodes, and the end-to-end time slot negotiation takes a long time.

[0050] According to the corresponding time slot negotiation and adjustment processes in Figures 3 and 4, the bandwidth adjustment process in related technologies is negotiated and adjusted segment by segment. The adjustment of the next segment is initiated only after the adjustment of one segment is completed, which is very time-consuming. Furthermore, this segment-by-segment negotiation and adjustment process has a drawback: some nodes have already completed the adjustment, while others encounter unexpected situations during the adjustment process. For example, in some cases, the CR signal or CA signal of a node is lost due to interference during the adjustment process; or in some cases, a node encounters difficulties and is unable to send a response CA signal in time, resulting in negotiation failure between upstream and downstream nodes. In these cases, when the time slot adjustment negotiation fails between some nodes, subsequent time slot adjustment cannot be carried out. As a result, some nodes on the network that have successfully adjusted carry services according to the new number of time slots, while some nodes carry services according to the old number of time slots, resulting in inconsistent end-to-end bandwidth. Therefore, existing lossless bandwidth adjustment requires multiple CR / CA / C negotiations on the forwarding plane. Especially in scenarios where the adjustment fails, this involves multiple coordination and fallbacks between devices and network management, placing high demands on network management.

[0051] Based on this, an embodiment of the present application provides a bandwidth configuration method, an electronic device, and a storage medium, which sends a request message to the management and control system through a source device, wherein the request message carries bandwidth demand information. The source device receives a response message returned by the management and control system, wherein the response message carries bandwidth confirmation information generated by the management and control system based on the bandwidth demand information, thereby achieving accurate connection between the source device and the management and control system. Afterwards, the source device generates a time slot configuration message based on the bandwidth confirmation information, and sends a time slot configuration message to the downstream device, so that the downstream device performs a time slot configuration operation based on the time slot configuration message. Therefore, compared with the related art, the embodiment of the present application can be applied to the bandwidth adjustment method for the Path Computation Element (PCE) scenario, and can effectively realize bandwidth configuration in scenarios with small time slot granularity and a large number of time slots, reducing the complexity of the forwarding surface, improving the bandwidth configuration rate, and improving the efficiency of service deployment.

[0052] The bandwidth configuration method provided in the embodiment of the present application can be applied to the scenario of carrying customer services based on the time slot method as shown in Figure 5. Among them, the nodes carrying customer services are the source node 100, the destination node 300 and the two intermediate nodes 200. The device where the source node 100 is located is the source device, and the source device in this case is also the PCC. The source device and the control system 500 are connected in communication based on PCEP. The control system 500 refers to a device deployed with PCE, and the control system 500 (used as PCE) and the source node 100 (used as PCC) complete session establishment, maintenance, path calculation and update, etc. through the exchange of PCEP messages. The PCEP message consists of a PCEP message header and a message body of variable length, and the message body consists of one or more objects. The main content of the PCEP message is carried by different objects, and the control system 500 cooperates with the centralized path calculation to achieve global path optimization, thereby achieving the purpose of fully utilizing network resources.

[0053] It is understandable that in actual application scenarios, there may be a greater number of intermediate nodes 200 between the source node 100 and the destination node 300. In the embodiment of the present application, two intermediate nodes 200 are used as an example.

[0054] It should be noted that the control protocol family in the optical network of the related art is Generalized Multi-Protocol Label Switching (GMPLS), in which the signaling responsible for resource control is RSVP-TE. The GMPLS extension of RSVP-TE uses a series of codes such as RSVP-TE's Traffic Specification (TSpec) and flow specification (FlowSpec, which are parameters and attributes used to describe and define the characteristics and requirements of network traffic) objects. The embodiments of the present application consider a fine-grained type of bandwidth adjustment and service establishment control method dedicated to the TDM mechanism, and can be applied to both the fine-grain metropolitan transport network (fgMTN) and the fine-grain optical transport network (fgOTN).

[0055] In the bandwidth configuration method of the embodiment of the present application, as shown in FIG6 , the implementation process of a bandwidth configuration method provided in the embodiment of the present application applied to a source device (i.e., source node 100) may include but is not limited to the following steps S610 to S630. Each step is described in sequence below:

[0056] Step S610: Send a request message to the management and control system, where the request message carries bandwidth demand information.

[0057] It should be noted that the bandwidth requirement information includes time slot granularity indication information and time slot quantity indication information.

[0058] It is understood that the timeslot granularity indication information is used to indicate the timeslot granularity of a path in an fgMTN or fgOTN scenario. For example, in fgOTN, an optical path refers to the path of an optical signal transmitted through an optical fiber. An optical path can be divided into different timeslots, each of which can be used to transmit different data streams or communication services. The timeslot granularity indication information is used to indicate the timeslot division granularity of each optical path, that is, the size of the timeslot.

[0059] It is understood that the timeslot number indication information refers to information used to indicate the number of timeslots of a path in an fgMTN or fgOTN scenario. For example, in fgOTN, the timeslot number indication information is used to indicate the number of timeslot divisions of each optical path.

[0060] It should be noted that the request message includes a bandwidth specification object, the bandwidth specification object includes a bandwidth specification type field (Bandwidth Specification Type, Bw Spec Type), and the time slot granularity indication information is indicated by the value of the bandwidth specification type field.

[0061] It is understandable that the embodiment of the present application defines a bandwidth specification object of the fg layer network, which is applied to the bandwidth specific object of the PCEP interaction between the PCC (also known as the source device) and the PCE (also known as the controller).

[0062] In one example, the PCC (also known as the source device) initiates a request message PCReq to the PCE (also known as the controller) to achieve a better timeslot path configuration. When requesting path calculation, request parameters (RP) or SRP (Stateful PCE Request Parameters) are usually carried in each PCReq. Figure 7 shows a format diagram of the RP provided in an embodiment of the present application. The first line in Figure 7 is a bitmap, including multiple bits. For example, 0-9 are used to represent bits in TDM communication, and each bit corresponds to the state of a timeslot in the service signal. At this time, the field length of the flags is 25 bits, the field length of the optional type-length-value (Optional TLVs) field is 32 bits, the field length of the priority field (Pri) is 3 bits, and the field length of the request ID number (Request-ID-number) field is 32 bits. The request ID number is an identifier used to identify a specific request or transaction, usually generated by the system or application for each request, and remains unchanged throughout the life cycle of the request.

[0063] It should be noted that there is no specific limitation on the length of different fields in the format, and in practical applications, it can be flexibly adjusted according to actual needs.

[0064] It should be noted that RP refers to the parameters or information carried in a request. When the PCC sends a request message to the PCE, it can include parameters in the request to provide additional information. These parameters can be used to specify specific requirements of the request, filter the returned results, and control the behavior of the request.

[0065] In an example, Figure 8 shows a format diagram of the bandwidth specification object provided in an embodiment of the present application. The field length of the bandwidth specification length (Bandwidth Specification Length) is 16 bits, the field length of the bandwidth specification type Bw Spec Type is 8 bits, the field length of the reverse bandwidth specification length (Reverse Bandwidth Specification Length) is 16 bits, the field length of the reserved field is 24 bits, the field length of the generalized bandwidth field (Generalized Bandwidth) is 32 bits, the field length of the optional reverse generalized bandwidth field (Reverse Generalized Bandwidth (optional)) is 32 bits, and the field length of the optional type length value is 32 bits. It should be noted that, There is no specific limitation on the length of different fields in the format. In practical applications, it can be flexibly adjusted according to actual needs.

[0066] It should be noted that this embodiment of the present application defines a new bandwidth specification type for the fg type. For example, if Bw Spec Type is set to 9, the bandwidth specification type in this case specifically refers to fgTDM (i.e., fgMTN or fgOTN), which is used to indicate a specific bandwidth type dedicated to fg-TDM. The value corresponding to the bandwidth specification type can be flexibly set according to actual needs and is not specifically limited here.

[0067] It should be noted that the reverse bandwidth specification is used to describe the reverse transmission capability of a network or channel, that is, the transmission bandwidth from the receiving end to the sending end.

[0068] It should be noted that general bandwidth represents transmission capacity and is used to describe the ability to transmit signals or data, such as the traffic parameters in RSVP-TE. The reserved field can be used to meet more functions in future application scenarios.

[0069] It is understandable that the request message includes a signal type object, the signal type object includes a quantity indication field, and the time slot quantity indication information is indicated by the value of the quantity indication field.

[0070] It can be understood that the signal type object further includes a signal type field, and the signal type field is used to indicate the client signal type.

[0071] In an example, Figure 9 shows a format diagram of a signal type object provided by an embodiment of the present application. The field length of the signal type field (Signal Type) is 8 bits, and the field length of the reserved field at this time is 8 bits. The quantity indication field includes the number of components multiplexed in multiplexing (Number of Multiplexed Components, NMC) and the number of components required for lossless adjustment in multiplexing (Hitless Number of Multiplexed Components, HNMC). NMC is used to indicate the number of occupied fg time slots. HNMC is used to indicate the NMC required for lossless adjustment, that is, the number of time slots to be added or reduced losslessly. Operation type information (denoted as O) is used to indicate the type of operation to be performed, that is, to add or reduce the time slots of HNMC. It should be noted that there is no specific limitation on the length of different fields in the format. In practical applications, it can be flexibly adjusted according to actual needs.

[0072] It's understandable that multiplexing can improve transmission efficiency and bandwidth utilization, saving communication resources. By combining multiple independent signals or data streams into a single channel, multiple signals can be transmitted simultaneously, reducing transmission overhead. At the receiving end, the combined signal or data stream can be demultiplexed based on the specific multiplexing protocol and mechanism to restore the original independent signals or data streams.

[0073] Step 620: Receive a response message returned by the management and control system, wherein the response message carries bandwidth confirmation information generated by the management and control system according to the bandwidth demand information.

[0074] It is understood that after the PCC (also known as the source device) initiates a request message PCReq to the PCE (also known as the controller), the PCE (also known as the controller) returns a response message (denoted as PCRep) to the PCC (also known as the source device). Bandwidth confirmation information is a message used to confirm the available bandwidth of the network connection between the PCC and PCE.

[0075] It is understandable that the bandwidth confirmation information includes time slot granularity confirmation information and time slot quantity confirmation information.

[0076] It should be noted that when the connection between the PCC (also known as the source device) and the PCE (also known as the controller) is successful, the time slot granularity confirmation information returned by the PCE (also known as the controller) is the same as the time slot granularity indication information in the above embodiment, and the time slot quantity confirmation information is also the same as the time slot quantity indication information in the above embodiment.

[0077] It is understood that when the connection between the PCC (also known as the source device) and the PCE (also known as the controller) is successful, the response message PCRep returned by the PCE (also known as the controller) to the PCC (also known as the source device) contains the same content as the request message PCReq. Therefore, the response message includes a bandwidth specification object, which includes a bandwidth specification type field. The timeslot granularity confirmation information is indicated by the value of the bandwidth specification type field.

[0078] It should be noted that the bandwidth specification type field at this time is the same as the bandwidth specification type field included in the request message in the above embodiment, and will not be repeated here.

[0079] It is understandable that the response message includes a signal type object, the signal type object includes a quantity indication field, and the time slot quantity confirmation information is indicated by the quantity indication field.

[0080] It should be noted that the quantity indication field at this time is the same as the quantity indication field included in the request message in the above embodiment, and will not be repeated here.

[0081] It is understandable that the signal type object further includes a signal type field, and the signal type field is used to indicate the type of the confirmed client signal.

[0082] It should be noted that the signal type field at this time is the same as the signal type field included in the request message in the above embodiment, and will not be repeated here.

[0083] It is understandable that when the PCC (also known as the source device) includes an existing service path, fine-grained lossless bandwidth adjustment can be performed based on TDM in the PCE scenario. In this case, the request message is a time slot adjustment request message, which also carries a rerouting flag, a path identifier, and operation type information. The rerouting flag indicates rerouting of the existing service path by using a first preset value, the path identifier is used to indicate the service path for which rerouting is requested, and the operation type information is used to indicate that the rerouting is to perform a time slot configuration operation on the service path or a time slot configuration operation to be deleted.

[0084] It is understood that the time slot quantity indication information includes service occupied time slot quantity information and adjusted time slot quantity information, and the time slot quantity confirmation information includes service occupied time slot quantity confirmation information and adjusted time slot quantity confirmation information. It should be noted that when the connection between the PCC (also known as the source device) and the PCE (also known as the controller) is successful, the service occupied time slot quantity information and the service occupied time slot quantity confirmation information are the same, and the adjusted time slot quantity information and the adjusted time slot quantity confirmation information are the same.

[0085] In one example, referring to Figure 7 , R represents the rerouting flag, the path identifier indicates the service path for which rerouting is requested, and O represents the operation type information. In this example, the rerouting flag R field is 1 bit long, and the operation type information O field is 1 bit long. It should be noted that the lengths of the various fields in the format are not specifically limited and can be flexibly adjusted based on actual needs in practical applications.

[0086] It should be noted that the first preset value, such as 0 or 1, represents the value for rerouting an existing service path, and is not specifically limited here. For example, if the first preset value is 1 and the rerouting flag bit R=1, it indicates that the PCC (also known as the source device) requests the PCE (also known as the controller) to reroute to optimize an existing TE LSP. For all TE LSPs, when the rerouting flag bit R=1, the request message PCReq must include a Reported Route Object (RRO) to describe the path of the existing TE LSP. That is, the RRO represents the specific path. It should be noted that the RRO carries the PCC's actual path information. Furthermore, when the rerouting flag bit R=1, the bandwidth of the existing TE LSP must be included in the bandwidth specification object, and the bandwidth must also include the expected bandwidth of the rerouted LSP. However, this approach cannot accommodate lossless bandwidth adjustment. That is, regardless of whether the route changes, the existing RRO must be included in the PCReq, reducing bandwidth configuration speed and service deployment efficiency.

[0087] Based on this, it can be understood that, referring to Figure 7, the time slot adjustment request message of the present application also carries a lossless bandwidth adjustment flag; when the lossless bandwidth adjustment flag is the second preset value, the time slot adjustment request message does not carry the record routing object RRO; when the lossless bandwidth adjustment flag is not the second preset value, the time slot adjustment request message carries RRO.

[0088] It is understood that this application adds a lossless bandwidth adjustment flag bit H to the RP to indicate the lossless bandwidth adjustment mode. The lossless bandwidth adjustment flag bit H can be used in conjunction with the rerouting flag bit R to determine whether to enable the lossless bandwidth mode. The second preset value is used to indicate the value of enabling lossless bandwidth adjustment, such as 1, 2, etc., and is not specifically limited here.

[0089] In one example, when both the first preset value and the second value are 1, and the rerouting flag bit R = 1 (i.e., the first preset value), the value of the lossless bandwidth adjustment flag bit H is confirmed. If the lossless bandwidth adjustment flag bit H = 0 (i.e., not the second preset value), the existing rerouting mechanism is used. If H = 1 (i.e., the second preset value), lossless bandwidth adjustment is enabled. Therefore, with this lossless bandwidth adjustment method, the route remains unchanged, and the timeslot adjustment request message does not need to carry an RRO to describe the current TE LSP path.

[0090] The PCC (also known as the source device) of this application adds a lossless bandwidth adjustment flag to the time slot adjustment request message. Based on the judgment of the lossless bandwidth adjustment flag, it can determine whether the time slot adjustment request message carries a record route object (RRO). Therefore, for scenarios where lossless bandwidth is considered, the time slot adjustment request message does not carry an RRO. That is, the routing does not change when lossless bandwidth adjustment is enabled, and there is no need to carry an RRO to describe the current TE LSP path. However, for scenarios where lossless bandwidth is considered, an RRO is required to describe the current TE LSP path, which can effectively improve the bandwidth configuration rate and service deployment efficiency in lossless bandwidth scenarios.

[0091] It is understood that when the request message is a path establishment request message, the path establishment request message also carries source and destination address information. In this case, the response message also carries path information, which indicates the service path generated by the management and control system based on the source and destination address information and bandwidth requirement information. The service path includes multiple devices that meet the bandwidth requirement information.

[0092] In other words, after the PCC (also known as the source device) initiates a path establishment request message to the PCE (also known as the controller), the PCE (also known as the controller) returns a response message to the PCC (also known as the source device). This path establishment request message also carries source and destination address information. The PCE (also known as the controller) then generates a service path based on the source and destination address information and bandwidth requirements in the path establishment request message. This service path indicates the hop-by-hop path information for the PCC (also known as the source device) to downstream devices.

[0093] It should be noted that source address information refers to the starting address information of the service path, and destination address information refers to the ending address information of the service path. Referring to Figure 5 , the source address information is the address information of the source node 100 (also called the source device), and the destination address information is the address information of the sink node 300. In this case, the downstream devices of the PCC (also called the source device) include the sink node 300 and two intermediate nodes 200.

[0094] It should be noted that since this application is requesting the calculation of the optimized path of a current LSP, and the bandwidth requirements after optimization are different, the RP in Figure 7 has already made it clear whether it is a lossless bandwidth adjustment based on the lossless bandwidth adjustment flag. Therefore, if it is a lossless bandwidth adjustment process, it only carries the bandwidth change requirement. If it is not a lossless bandwidth adjustment, the current bandwidth and target bandwidth are carried according to the original process. In order to maintain compatibility with the original process, for requests for lossless bandwidth adjustment, the PCC can optionally carry the RRO object, that is, the path of the existing TE LSP is optional. When the PCE receives the PCReq message carrying the RP, it will calculate whether the current resource requirements can be met. The PCE only calculates the requirements that can be met, and the PCC (also known as the source device) completes the specific time slot negotiation.

[0095] It is understood that the time slot quantity indication information includes information about the number of time slots occupied by services, and the time slot quantity confirmation information includes information about the number of time slots occupied by services. It should be noted that when a connection is successfully established between the PCC (also known as the source device) and the PCE (also known as the management and control system), the information about the number of time slots occupied by services and the information about the number of time slots occupied by services are the same.

[0096] It is understandable that, referring to FIG. 10 , after receiving the response message returned by the management and control system, the bandwidth configuration method provided in the embodiment of the present application further includes: step 1010 , performing corresponding time slot configuration operations according to the bandwidth confirmation information.

[0097] The embodiment of the present application is a TDM-based fine-grained lossless bandwidth adjustment in a PCE scenario, that is, by carrying a lossless bandwidth adjustment flag in PCReq, a request is made to enter the lossless bandwidth adjustment process. In the lossless bandwidth adjustment process, the route does not change, and there is no need to carry RRO to describe the path information of the current TE LSP. The PCE determines whether to perform lossless adjustment through the lossless flag and bandwidth increment requirement in the PCReq request. The PCC (also known as the source device) and the PCE (also known as the management and control system) interact through the request message PCReq and the response message PCRep to complete the evaluation of the bandwidth adjustment demand, clarify that it can be adjusted, and carry the operable bandwidth and specific label list in the request message PCRep, and finally cooperate with the control plane and the forwarding plane to complete the fg 10-megabit level lossless bandwidth adjustment process of the path.

[0098] Step 630: Generate a timeslot configuration message according to the bandwidth confirmation information, and send the timeslot configuration message to the downstream device, so that the downstream device performs a timeslot configuration operation according to the timeslot configuration message.

[0099] It is understood that the timeslot configuration information carries the following information:

[0100] Customer signal identification, used to identify customer information;

[0101] A bit map, including multiple bits, each bit corresponding to a state of a time slot in a service signal;

[0102] Bitmap length information, used to indicate the length of the bitmap;

[0103] The starting time slot position information is used to indicate the position of the time slot corresponding to the starting bit of the bit map in the service signal.

[0104] In one example, Figure 11 shows a schematic diagram of the timeslot configuration information format. The client signal identifier field is 10 bits long, the bitmap field is 32 bits long, the bitmap length information field is 10 bits long, the starting timeslot position information field is 10 bits long, the reserved field is 2 bits long, and the variable padding bits (Padding Bits (Variable)) field is 32 bits long. It should be noted that the lengths of the various fields in the format are not specifically limited and can be flexibly adjusted based on actual needs in practical applications.

[0105] It should be noted that the client signal identifier is a fine-grained client identifier (ID). The client signal identifier is a unique identifier used to identify a specific fine-grained client application or device.

[0106] In one example, the client signal identifier (CSID) is consistent with the forwarding plane encoding. For fgMTN, the encoding range is 1-480, with 0b0000000001 and 0b1111000000 being valid values, and 0b0000000000 indicating unoccupied. For fgOTN, the CSI value range varies depending on the service layer being carried. When carried on Optical Processing Unit 0 (OPU0), the CSI ranges from 1-119; when carried on OPU1, the CSI ranges from 1-238; and when carried on OPU2, the CSI ranges from 1 to 8*119. For both fgMTN and fgOTN, the CSI is carried on the forwarding plane. For fgMTN, it is encapsulated in the OH frame, and for fgOTN, it is encapsulated as the MSI. It is carried in the overhead and indicates the specific timeslot location. When FG is multiplexed into a server layer and occupies one or more timeslots, a new client signal identifier and specific occupied timeslot are assigned at both ends of the FG link. This is typically assigned at the downstream node and carried to the upstream node via the control plane. On the forwarding plane, the upstream client signal identifier and bitmap are encapsulated and written into the server layer overhead for easy detection and verification by the sink. Therefore, the control plane can negotiate this in advance for use by the forwarding plane.

[0107] It should be noted that variable padding refers to extra bits added during data transmission or storage to meet specific requirements or regulations. Padding bits are typically used to align, protect, or fill data to ensure data integrity and correctness.

[0108] It should be noted that due to the large number of time slots occupied by the FG type, the starting time slot position information is added as the starting position to indicate the starting position of the bitmap. By default, it is 0, that is, starting from time slot 1. The bitmap is a variable that indicates the entire time slot list or time slot list fragment of the bottom layer to be changed in the current FG layer.

[0109] It is understandable that after receiving the timeslot configuration message, each node of the downstream device reuses the existing local client signal identifier to identify the current path, and allocates or releases resources along the path according to the number of bandwidth adjustments required for lossless bandwidth adjustment.

[0110] It is understandable that the management and control system in the embodiment of the present application is a path computation element PCE, and the source device is a path computation client PCC.

[0111] It should be noted that, as shown in Figure 5, after the source node 100 corresponding to the PCC (also known as the source device or source node 100) receives a response message from the PCE (also known as the management and control system), the PCC (also known as the source device or source node 100) generates a timeslot configuration message based on the bandwidth confirmation information. This message carries the number of timeslots to be changed, which serves as a label for each downstream device along the path. The timeslot configuration message is then sent to the downstream device, enabling the downstream device to perform timeslot configuration operations based on the timeslot configuration message. Therefore, at this point, nodes P1, P2, and the sink node 300 are downstream nodes of the source node 100. After receiving the request message from the source node 100, node P1 processes it in sequence and forwards it downstream to node P2. The downstream node sends a response message carrying the timeslot configuration message to be allocated. After the upstream node receives the confirmation message from the downstream node, it decides and confirms the specific timeslots to be added / deleted on the downstream inbound and outbound links.

[0112] Therefore, after the signaling negotiation is complete, the upstream node sends a message on the next forwarding plane to complete lossless bandwidth adjustment along the path. This embodiment does not limit the specific control signaling protocol type. Because the negotiation is carried out on the control plane, it does not restrict the forwarding plane processing. This application can simultaneously meet the time slot adjustment requirements of multiple clients.

[0113] It is understood that, in the bandwidth configuration method of the embodiment of the present application, as shown in FIG12 , the implementation process of the bandwidth configuration method provided in the embodiment of the present application applied to the management and control system may include but is not limited to the following steps S1210 to S1230. Each step is described in sequence below:

[0114] Step 1210: Receive a request message sent by a source device, where the request message carries bandwidth requirement information.

[0115] It should be noted that the bandwidth requirement information has been described in the above embodiment and will not be repeated here.

[0116] Step 1220: Generate bandwidth confirmation information according to the bandwidth demand information, and encapsulate the bandwidth confirmation information into the response information.

[0117] It should be noted that the response information refers to the information generated by the management and control system after confirming the information received according to the request information. The bandwidth confirmation information has been described in the above embodiment and will not be repeated here.

[0118] Step 1230: Return a response message to the source device, where the response message carries bandwidth confirmation information, so that the source device generates a time slot configuration message according to the bandwidth confirmation information and sends the time slot configuration message to the downstream device.

[0119] It should be noted that the time slot configuration message has been described in the above embodiment and will not be repeated here.

[0120] It is understood that, referring to FIG. 13 , when the request message is a path establishment request message, the path establishment request message also carries source address information and destination address information; before returning a response message to the source device, the bandwidth configuration method of the present application further includes:

[0121] Step 1310: Determine at least one candidate service path based on the source address information and the destination address information.

[0122] It is understandable that there are multiple candidate service paths between the source address information and the destination address information.

[0123] Step 1320: Determine a service path from at least one candidate service path according to the bandwidth requirement information, where each device in the service path meets the bandwidth requirement information.

[0124] It can be understood that the service path refers to a path that can address the problem of a large number of fg time slots, propose information that can meet bandwidth requirements, and is generated using a lossless bandwidth adjustment mechanism without rerouting.

[0125] Step 1330: Generate path information according to the service path, and encapsulate the path information into the response information.

[0126] It is understood that path information refers to information about downstream devices that are passed through in sequence. The source device can generate time slot configuration information based on the hard answer information returned by the management and control system, so that the downstream device can perform time slot configuration operations based on the time slot configuration information.

[0127] It can be understood that the request message is a time slot adjustment request message, and the time slot adjustment request message also carries a rerouting flag, a path identifier, and operation type information, wherein the rerouting flag indicates that the existing service path is rerouted through a first preset value, the path identifier is used to indicate the service path requested to be rerouted, and the operation type information is used to indicate that the rerouting is to perform an operation of adding a time slot configuration or deleting a time slot configuration on the service path; the response message carries a path confirmation identifier corresponding to the path identifier and operation type confirmation information corresponding to the operation type information.

[0128] It is understandable that when there is no service path in the PCC (also known as the source device), the fg path is established based on TDM in the PCE scenario. The fg-TDM path establishment in the PCE scenario of this application is divided into two parts. The first part is PCEP interaction. When the PCC (also known as the source device or source end node 100) requests to calculate one or more fg-TDM paths, one or more PCEs (i.e., the management and control system 500) are selected to request path calculation. After the PCEP session between the PCC and the PCE is established, the PCC sends a PCReq message to the PCE, requesting the PCE to calculate an fg-TDM path that meets the constraints. In the PCReq message, the PCC carries source address information, destination address information, and bandwidth requirement information. After receiving the PCReq message sent by the PCC, the PCE triggers the path calculation process. If the path calculation is successful, the PCE sends a PCRep message to the PCC. In the second part, after the PCC receives the PCRep, the time slot configuration message carried in the PCRep is established along the path. Therefore, the embodiment of the present application can generate a more optimal time slot configuration message according to the bandwidth requirement information, and enable the downstream device to perform the time slot configuration operation according to the time slot configuration message.

[0129] The embodiments of the present application can address the problem of a large number of FG time slots in PCE scenarios by proposing a non-rerouting lossless bandwidth configuration method. That is, by reducing the CR / CA mechanism on the forwarding plane, lossless adjustment can be completed by simply transmitting time slot configuration information on the forwarding plane. The present application can effectively unify the processes of TDM-based path establishment and bandwidth adjustment in PCE scenarios. Therefore, the embodiments of the present application can provide a bandwidth configuration method suitable for scenarios with small time slot granularity and a large number of time slots, reducing the complexity of the forwarding plane, increasing the bandwidth configuration rate, and improving service deployment efficiency.

[0130] It should be noted that although operations are described in a specific order in the drawings in the embodiments of the present application, this should not be construed as requiring that these operations be performed in the specific order shown or in a serial order, or that all of the operations shown be performed to obtain the desired result. In certain circumstances, multitasking and parallel processing may be advantageous.

[0131] In addition, in the embodiments of the present application, the description of each embodiment has its own focus. For parts that are not detailed or recorded in a certain embodiment, please refer to the relevant description of other embodiments.

[0132] The embodiment of the present application further provides an electronic device, as shown in FIG14 , wherein the electronic device 1400 includes:

[0133] one or more processors 1410;

[0134] The memory 1420 stores one or more programs. When the one or more programs are executed by the one or more processors 1410, the one or more processors 1410 implement the following:

[0135] For example, a bandwidth configuration method applied to a source device (also referred to as a source node 100); or

[0136] Such as the bandwidth configuration method used in the management and control system.

[0137] The memory 1420 is a non-transient network system that can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory 1420 may include a high-speed random access memory and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory 1420 may optionally include a memory 1420 remotely located relative to the processor 1410, and these remote memories 1420 may be connected to the processor 1410 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0138] The memory 1420 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1420 can store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 1420 and is called by the processor 1410 to execute the methods of the embodiments of this application.

[0139] The processor 1410 can be implemented using a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application.

[0140] In some embodiments, as shown in FIG14 , the electronic device further includes:

[0141] Input / output interface, used to realize information input and output;

[0142] Communication interface, used to realize communication interaction between this device and other devices, which can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, Wi-Fi, Bluetooth, etc.);

[0143] A bus that transmits information between various components of the device (e.g., the processor 1410, memory 1420, input / output interfaces, and communication interfaces);

[0144] The processor 1410 , the memory 1420 , the input / output interface, and the communication interface can be communicatively connected to each other within the device via a bus.

[0145] An embodiment of the present application further provides a computer-readable storage medium storing computer-executable instructions for executing:

[0146] For example, a bandwidth configuration method applied to a source device (also referred to as a source node 100); or

[0147] Such as the bandwidth configuration method used in the management and control system.

[0148] An embodiment of the present application further provides a computer program product, including a computer program or computer instructions, wherein the computer program or computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer program or computer instructions from the computer-readable storage medium, and the processor executes the computer program or computer instructions, so that the computer device performs the following operations:

[0149] For example, a bandwidth configuration method applied to a source device (also referred to as a source node 100); or

[0150] Such as the bandwidth configuration method used in the management and control system.

[0151] The system architecture and application scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of the system architecture and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.

[0152] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0153] Those skilled in the art will appreciate that all or some of the steps and systems in the method disclosed above can be implemented as software, firmware, hardware, and appropriate combinations thereof. Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, and the computer-readable medium can include computer storage media (or non-transitory media) and communication media (or temporary media). As known to those skilled in the art, the term computer storage media is included in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data) and is volatile and non-volatile, removable, and non-removable. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory, or other memory technology, CD-ROM, digital versatile disks (DVD), or other optical disk storage, magnetic cassettes, magnetic tapes, disk storage, or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, as is well known to those skilled in the art, communication media typically embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0154] The above description of some embodiments of the present application with reference to the accompanying drawings does not limit the scope of the present application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and essence of the present application shall be within the scope of the present application.

Claims

1. A bandwidth configuration method, the method being applied to a source device, the method comprising: Sending a request message to the management and control system, wherein the request message carries bandwidth demand information; Receiving a response message returned by the management and control system, wherein the response message carries bandwidth confirmation information generated by the management and control system according to the bandwidth demand information; A time slot configuration message is generated according to the bandwidth confirmation information, and the time slot configuration message is sent to a downstream device, so that the downstream device performs a time slot configuration operation according to the time slot configuration message.

2. The method according to claim 1, wherein: The bandwidth requirement information includes time slot granularity indication information and time slot quantity indication information.

3. The method according to claim 2, wherein: The request message includes a bandwidth specification object, the bandwidth specification object includes a bandwidth specification type field, and the time slot granularity indication information is indicated by the value of the bandwidth specification type field.

4. The method according to claim 2, wherein: The request message includes a signal type object, the signal type object includes a quantity indication field, and the time slot quantity indication information is indicated by a value of the quantity indication field.

5. The method according to claim 4, wherein: The signal type object further includes a signal type field, and the signal type field is used to indicate the client signal type.

6. The method according to claim 2, wherein: The bandwidth confirmation information includes time slot granularity confirmation information and time slot quantity confirmation information.

7. The method according to claim 6, wherein: The response message includes a bandwidth specification object, the bandwidth specification object includes a bandwidth specification type field, and the time slot granularity confirmation information is indicated by the value of the bandwidth specification type field.

8. The method according to claim 6, wherein: The response message includes a signal type object, the signal type object includes a quantity indication field, and the time slot quantity confirmation information is indicated by the quantity indication field.

9. The method according to claim 8, wherein: The signal type object further includes a signal type field, and the signal type field is used to indicate the confirmation client signal type.

10. The method according to claim 6, wherein: The request message is a path establishment request message, and the path establishment request message also carries source address information and destination address information; The response information also carries path information, where the path information is used to indicate a service path generated by the management and control system according to the source address information, the destination address information and the bandwidth requirement information, where the service path includes multiple devices that meet the bandwidth requirement information.

11. The method according to claim 10, wherein: The time slot quantity indication information includes service occupied time slot quantity information, and the time slot quantity confirmation information includes service occupied time slot quantity confirmation information.

12. The method according to claim 6, wherein: The request message is a time slot adjustment request message, and the time slot adjustment request message also carries a rerouting flag, a path identifier, and operation type information, wherein the rerouting flag indicates rerouting of an existing service path through a first preset value, the path identifier is used to indicate the service path requested to be rerouted, and the operation type information is used to indicate that the rerouting is to perform an operation of adding a time slot configuration or a operation of deleting a time slot configuration on the service path.

13. The method according to claim 12, wherein: The time slot adjustment request message also carries a lossless bandwidth adjustment flag; When the lossless bandwidth adjustment flag is a second preset value, the time slot adjustment request message does not carry a record routing object RRO; When the lossless bandwidth adjustment flag is not a second preset value, the timeslot adjustment request message carries the RRO.

14. The method according to claim 12, wherein: The time slot quantity indication information includes service occupied time slot quantity information and adjusted time slot quantity information, and the time slot quantity confirmation information includes service occupied time slot quantity confirmation information and adjusted time slot quantity confirmation information.

15. The method according to claim 1, wherein: The timeslot configuration message carries the following information: Customer signal identification, used to identify customer information; A bit map, including a plurality of bits, each bit corresponding to a state of a time slot in a service signal; Bitmap length information, used to indicate the length of the bitmap; The starting time slot position information is used to indicate the position of the time slot corresponding to the starting bit of the bit map in the service signal.

16. The method according to claim 1, wherein: After receiving the response message returned by the management and control system, the method further includes: performing a corresponding time slot configuration operation according to the bandwidth confirmation information.

17. The method according to claim 1, wherein: The management and control system is a path computation element PCE, and the source device is a path computation client PCC.

18. A bandwidth configuration method, the method being applied to a management and control system, the method comprising: Receiving a request message sent by a source device, wherein the request message carries bandwidth requirement information; Generate bandwidth confirmation information according to the bandwidth demand information, and encapsulate the bandwidth confirmation information into response information; The response message is returned to the source device, wherein the response message carries the bandwidth confirmation information, so that the source device generates a time slot configuration message according to the bandwidth confirmation information, and sends the time slot configuration message to a downstream device.

19. The method according to claim 18, wherein: The bandwidth requirement information includes time slot granularity indication information and time slot quantity indication information.

20. The method according to claim 19, wherein: The request message includes a bandwidth specification object, the bandwidth specification object includes a bandwidth specification type field, and the time slot granularity indication information is indicated by the value of the bandwidth specification type field.

21. The method according to claim 19, wherein: The request message includes a signal type object, the signal type object includes a quantity indication field, and the time slot quantity indication information is indicated by a value of the quantity indication field.

22. The method according to claim 21, wherein: The signal type object further includes a signal type field, and the signal type field is used to indicate the client signal type.

23. The method according to claim 19, wherein: The bandwidth confirmation information includes time slot granularity confirmation information and time slot quantity confirmation information.

24. The method according to claim 23, wherein: The response message includes a bandwidth specification object, the bandwidth specification object includes a bandwidth specification type field, and the time slot granularity confirmation information is indicated by the value of the bandwidth specification type field.

25. The method according to claim 23, wherein: The response message includes a signal type object, the signal type object includes a quantity indication field, and the time slot quantity confirmation information is indicated by the quantity indication field.

26. The method according to claim 25, wherein: The signal type object further includes a signal type field, and the signal type field is used to indicate the confirmation client signal type.

27. The method according to claim 23, wherein: The request message is a path establishment request message, and the path establishment request message also carries source address information and destination address information; Before returning the response message to the source device, the method further includes: Determine at least one candidate service path according to the source address information and the destination address information; Determine a service path from the at least one candidate service path according to the bandwidth requirement information, wherein each device in the service path meets the bandwidth requirement information; Generate path information according to the service path, and encapsulate the path information into the response information.

28. The method according to claim 27, wherein: The time slot quantity indication information includes service occupied time slot quantity information, and the time slot quantity confirmation information includes service occupied time slot quantity confirmation information.

29. The method of claim 23, wherein: The request message is a time slot adjustment request message, and the time slot adjustment request message further carries a rerouting flag, a path identifier, and operation type information, wherein the rerouting flag indicates rerouting an existing service path through a first preset value, the path identifier is used to indicate a service path for which rerouting is requested, and the operation type information is used to indicate that the rerouting is to perform an operation of adding a time slot configuration or a operation of deleting a time slot configuration on the service path; The response message carries a path confirmation identifier corresponding to the path identifier and operation type confirmation information corresponding to the operation type information.

30. The method of claim 29, wherein: The time slot adjustment request message also carries a lossless bandwidth adjustment flag; When the lossless bandwidth adjustment flag is a second preset value, the time slot adjustment request message does not carry a record routing object RRO; When the lossless bandwidth adjustment flag is not a second preset value, the timeslot adjustment request message carries the RRO.

31. The method of claim 29, wherein: The time slot quantity indication information includes service occupied time slot quantity information and adjusted time slot quantity information, and the time slot quantity confirmation information includes service occupied time slot quantity confirmation information and adjusted time slot quantity confirmation information.

32. The method of claim 18, wherein: The management and control system is a path computation element PCE, and the source device is a path computation client PCC.

33. An electronic device comprising: one or more processors; A memory having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the bandwidth configuration method as described in any one of claims 1-17; or, the bandwidth configuration method as described in any one of claims 18-32.

34. A computer-readable storage medium having a computer program stored thereon, wherein: When the program is executed by a processor, the bandwidth configuration method according to any one of claims 1 to 17 is implemented; or, the bandwidth configuration method according to any one of claims 18 to 32 is implemented.

Images