Bandwidth configuration method, electronic equipment and storage medium
The bandwidth requirement information is sent to the management and control system through the source device, the returned bandwidth confirmation information is processed, and the time slot configuration message is generated, which solves the problems of high bandwidth configuration complexity and low service deployment efficiency in the prior art, and realizes efficient bandwidth configuration and service deployment.
Patent Information
- Application Number
- CN202311294455.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-09-28
- Publication Date
- 2025-03-28
AI Technical Summary
In the scenario where the time slot granularity and the number of time slots is small, the bandwidth configuration method is complex, the service deployment efficiency is low, and lossless bandwidth adjustment requires multiple negotiations, which increases the work burden of network management.
The source device sends a request message for bandwidth demand information to the management and control system, receives and processes the bandwidth confirmation information returned by the management and control system, generates and sends a time slot configuration message to the downstream device, and realizes bandwidth configuration operations.
It reduces the complexity of the forwarding surface, improves bandwidth configuration rate, improves business deployment efficiency, and reduces the work burden of network management.
Smart Images

Figure CN119728436A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of communication technology, and in particular to a bandwidth configuration method, an electronic device, and a storage medium. Background Art
[0002] A frame structure is usually used in communication networks to carry customer services, specifically by dividing time slots in the bearer frame and using time slots to carry services. In the related art, lossless bandwidth adjustment technology requires control to send 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, involving multiple collaborations and fallbacks between equipment and network management, and high requirements for network management. Due to the lack of a control plane, the network management needs to send it down node by node, which has high requirements for control. Therefore, in the scenario where the time slot granularity is small and the number of time slots is large, the bandwidth configuration method of the related art has a high complexity of the forwarding plane and low service deployment efficiency. Summary of the invention
[0003] 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 the service deployment efficiency.
[0004] In a first aspect, an embodiment of the present application provides a bandwidth configuration method, which is applied to a source device, and the method includes:
[0005] Sending a request message to the management and control system, wherein the request message carries bandwidth demand information;
[0006] 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;
[0007] 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.
[0008] 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 the method includes:
[0009] Receiving a request message sent by a source device, wherein the request message carries bandwidth requirement information;
[0010] Generate bandwidth confirmation information according to the bandwidth demand information, and encapsulate the bandwidth confirmation information into response information;
[0011] 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.
[0012] In a third aspect, an embodiment of the present application provides an electronic device, including:
[0013] one or more processors;
[0014] 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.
[0015] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the bandwidth configuration method as described in the first aspect above is implemented; or, the bandwidth configuration method as described in the second aspect above is implemented.
[0016] In an embodiment of the present application, a request message is sent 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 according to 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 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, improves the bandwidth configuration rate, and improves the efficiency of service deployment. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] The accompanying drawings are used to provide a further understanding of the technical solution of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the technical solution of the present invention and do not constitute a limitation on the technical solution of the present invention.
[0018] Figure 1 It is a schematic diagram of the transmission of a bearer frame between nodes in the related art;
[0019] Figure 2A-2C It is a schematic diagram of a frame structure in the related art;
[0020] Figure 3 It is a schematic diagram of the time slot negotiation and adjustment process under the condition of reducing the time slot demand in the related art;
[0021] Figure 4 It is a schematic diagram of the time slot negotiation and adjustment process when the time slot requirement is increased in the related art;
[0022] Figure 5 It is a schematic diagram of a process of broadband configuration provided by an embodiment of the present application;
[0023] Figure 6 This 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 an embodiment of the present application;
[0024] Figure 7 This is a schematic diagram of a format of a request parameter RP provided in an embodiment of the present application;
[0025] Figure 8 This is a schematic diagram of a format of a bandwidth specification object provided in an embodiment of the present application;
[0026] Fig. 9 This is a schematic diagram of a format of a signal type object provided in an embodiment of the present application.
[0027] Fig.10 This is a schematic diagram of the interaction between the source device, the control system and the downstream node for performing broadband configuration in the next embodiment of the present application in which the corresponding time slot configuration operation is added;
[0028] Fig.11 This is a schematic diagram of the format of time slot configuration information provided by an embodiment of the present application;
[0029] Fig.12 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;
[0030] Fig.13 This is a schematic diagram of the interaction between the source device, the control system and the downstream node for broadband configuration provided by the next embodiment of the present application for adding encapsulation response information;
[0031] Fig.14 It is a schematic diagram of the device structure of the electronic device provided in the embodiment of the present application. DETAILED DESCRIPTION
[0032] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.
[0033] 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 used for the purpose of distinguishing technical features, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of indicated technical features or implicitly indicating the order of the indicated technical features. "At least one" means one or more, and "multiple" 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 situation where A exists alone, A and B exist at the same time, and B exists 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 and b and c, where a, b, c can be single or multiple.
[0034] In addition, the technical features involved in the various embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.
[0035] In order 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 related technologies is first given:
[0036] Path Computation Element (PCE): refers to a component that can calculate paths that meet constraints based on network topology information. PCE can be deployed in a routing device or in a separate server. Most of the time, PCE and the management and control system can be integrated together.
[0037] Path Computation Client (PCC): refers to the client application that requests the path computation unit to perform path computation. The PCC sends a path request to the PCE and receives the path computation result returned by the PCE. Therefore, the routing device can be considered as a device that integrates the PCC function, or the routing device can be considered as the PCC.
[0038] Path Computation Element Protocol (PCEP): refers to the communication protocol between PCC and PCE. PCEP defines a set of messages and objects used to manage PCEP sessions and send paths for Traffic Engineering Label Switched Path (TE LSP) requests.
[0039] A frame structure is usually used in communication networks to carry customer services. Specifically, time slots are divided in a bearer frame and used to carry services. When dividing time slots, many time slots can be divided in a bearer frame, or time slots can be divided over multiple bearer frames. Figure 1 FIG. 1 is a schematic diagram of the transmission of a bearer frame between nodes in the related technology. Figure 1 As shown, the nodes carrying customer services are the source node 100, the destination node 300 and two intermediate nodes 200. Each node can be a node supporting international standard protocols, a slice packet network node supporting relevant technical definitions, and other types of bearing nodes. The bearing frame 410-440 consists of a frame header, a container and a frame tail. The time slots are divided in the container of the bearing frame, and the time slot positions are fixed and transmitted in the network with the bearing frame. Each customer service can be transmitted in a fixed time slot, and different customers use different time slot positions for service bearing. According to the time slot granularity of the service layer, several time slots are divided. When the customer bandwidth is large, multiple time slot positions are selected for bearing, and when the customer bandwidth is small, a small number of time slot positions are selected for bearing. When carrying customer services, the customer service is mapped to the corresponding time slot of the bearer frame on the source node 100 and sent out. The intermediate node 200 completes the time slot forwarding, and the customer service is extracted from the corresponding time slot at the destination node 300 to restore the original customer service.
[0040] Figure 2A-2C It is a schematic diagram of a frame structure in the related art. Figure 2A and Figure 2B Figure 1 is a schematic diagram of the time slot division method of fg-BU. One time slot of fg-BU occupies 65 bytes (Byte, B). Figure 2CAs shown in the figure, 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 application 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).
[0041] In actual business applications, at the beginning, the customer bandwidth is small, the required bearer pipe bandwidth is small, and only a small number of bearer time slots are needed to meet customer needs. After a period of time, the customer's business volume increases, the bandwidth increases, and more time slots are needed to carry customer services. Therefore, it is necessary to increase the number of time slots without affecting or interrupting customer services to complete the operation of increasing time slots. Conversely, for customers with declining business volume, after a period of time, the customer business bandwidth decreases, and the number of time slots carrying business needs to be reduced. Therefore, it is necessary to dynamically adjust the number of time slots carrying customer services without affecting customer services.
[0042] 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-to-end perform time slot negotiation and time slot adjustment with each other in turn; and because each time slot negotiation is performed for a single adjusted time slot, it is necessary to respond to the increase or decrease in customer service demand requests only after each time slot negotiation and time slot adjustment is completed. However, in actual applications, there is uncertainty in the increase or decrease in customer service demand, 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, 2), especially for scenarios where the adjustment cannot be successful, involving 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 the scenario 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 in the forwarding plane and a low efficiency in service deployment.
[0043] In the bandwidth adjustment in 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 did not consider the time division multiplexing of fine granularity (fg). For example, the optical distribution network (ODN) of the optical transport network (OTN) has a large granularity of multiplexing time slots 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 more service layer time slots, general labels are not fully applicable. For example, due to bandwidth increase or bandwidth decrease, the current label switching path (Lable Switch Path, LSP) needs to be deleted on the control plane and a new LSP needs to be established, so that the bandwidth change requirements can be confirmed according to the new and old service parameters, and then the full time slot is carried in the universal label to compare the local full time slot with the full time slot in the universal label on the device side. Therefore, in the scenario 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 of the forwarding plane and a low service deployment efficiency.
[0044] Based on this, the present application provides a bandwidth configuration method, an electronic device, and a storage medium, which adopts a control plane to assist in the establishment of services and bandwidth adjustment solutions on the forwarding plane, thereby releasing the requirements on 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.
[0045] Figure 3 This is a schematic diagram of the time slot negotiation and adjustment process in the related art to reduce the time slot demand by using the hop-by-hop negotiation and hop-by-hop adjustment method to negotiate and adjust the time slot. Figure 3As shown, the nodes carrying services include a source node 100, a sink node 300, and two intermediate nodes 200, wherein the two intermediate nodes 200 are respectively a node P1 and a node P2; wherein the sink node 300, the node P1, and the node P2 are downstream nodes of the source node 100; when it is necessary to reduce the time slot, the source node 100 sends a time slot configuration application indication CR signal to the node P1, and carries the time slot number to be reduced and adjusted in the sent CR signal, prompting the node P1 to reduce the time slot number to be adjusted, and after receiving the time slot configuration application indication CR signal, the node P1 sends a time slot configuration response indication CA signal to the source node 100 after completing the preparation work. After the source node 100 receives the time slot configuration response indication CA signal from the node P1, the negotiation process of time slot reduction adjustment between the source node 100 and the node P1 is completed, and the source node 100 sends a time slot configuration effective indication C signal to the node P1, and then the source node 100 and the node P1 carry the customer service according to the reduced and adjusted time slot position. When node P1 receives the time slot configuration effective indication C signal from the source node 100, node P1 starts to send a time slot configuration application indication CR signal to node P2, and sends the time slot number to be reduced and adjusted at the same time when sending the time slot configuration application indication CR signal. After node P2 receives the time slot configuration application indication CR signal, it sends a time slot configuration response indication CA signal to node P1 after completing the preparation work. After node P1 receives the time slot configuration response indication CA signal from node P2, the negotiation process of time slot reduction adjustment between node P1 and node P2 is completed. After node P1 receives the time slot configuration response indication CA signal from node P2, it sends a time slot configuration effective indication C signal to node P2, and then node P1 and node P2 carry customer services at the reduced and adjusted time slot position. By analogy, node P2 and the host node 300 also complete the negotiation and time slot reduction adjustment process of time slot reduction adjustment, so that all time slot adjustment processes are completed. At the same time, during the time slot reduction adjustment process, the number of time slots between the adjacent nodes located upstream is first reduced. After the number of time slots of the adjacent nodes upstream is reduced, the time slot reduction operation of the downstream nodes of the adjusted nodes is started, and the number of time slots between the upstream nodes is always kept less than the number of time slots between the downstream nodes, that is, the service bandwidth between the upstream nodes is less than the service bandwidth between the downstream nodes. This can avoid the situation where the service overflows at some node locations due to the upstream service bandwidth in the pipeline being greater than the downstream service bandwidth. Therefore, during the adjustment process, the end-to-end bandwidth reduction adjustment of the service is completed only after the last two nodes complete the time slot reduction adjustment. Therefore, it is impossible to continue to respond to time slot negotiation and time slot adjustment before the time slot reduction request of the current customer service demand is completed.
[0046] Figure 4The figure is a schematic diagram of the time slot negotiation and adjustment process under the condition of increasing the time slot demand in the time slot negotiation and adjustment by hop-by-hop negotiation and adjustment. There are two intermediate nodes 200 arranged between the source node 100 and the sink node 300, namely, the node P1 and the node P2; wherein the source node 100, the node P1 and the node P2 are the upstream nodes of the sink node 300; Figure 4As shown, when adding time slots, in order to ensure that the service bandwidth between upstream nodes is less than the service bandwidth between downstream nodes, the relevant technology stipulates that when adding and adjusting time slots, the time slot addition and adjustment starts from the sink node 300, and the sink node 300 sends a time slot increase adjustment notification S signal to the node P2. After receiving the time slot increase adjustment notification S signal, the node P2 starts the increase adjustment and sends a time slot configuration application indication CR signal to the sink node 300, and sends the number of the time slot to be increased and adjusted at the same time. After receiving the time slot configuration application indication CR signal, the sink node 300 returns a time slot configuration response indication CA signal to the node P2 after completing the preparation work. After receiving the time slot configuration response indication CA signal from the sink node 300, the negotiation process of the time slot increase and adjustment between the node P2 and the sink node 300 is completed, and the node P2 sends a time slot configuration effective indication C signal to the sink node 300, and then the node P2 and the sink node 300 carry the customer service according to the time slot after the increase and adjustment of the time slot. At the same time, node P2 sends a time slot increase adjustment notification S signal to node P1. After node P1 receives the time slot increase adjustment notification S signal, node P1 starts the time slot increase adjustment negotiation work, sends a time slot configuration application indication CR signal to node P2, and sends the time slot number to be increased and adjusted at the same time. After node P2 receives the time slot configuration application indication CR signal, it returns the time slot configuration response indication CA signal to node P1 after completing the preparation work. After node P1 receives the time slot configuration response indication CA signal from node P2, the negotiation process of time slot increase adjustment between node P1 and node P2 is completed. Node P1 sends a time slot configuration effectiveness indication C signal to node P2, and then node P1 and node P2 carry customer services according to the time slot after the increase of the time slot adjustment. At the same time, node P1 sends a time slot increase adjustment notification S signal to the source node 100. By analogy, after the source node 100 and node P1 complete the negotiation of time slot increase adjustment and the time slot increase adjustment process, all time slot increase adjustment processes are completed. The adjustment process is negotiated and completed section by section. In the process of increasing time slots, the number of time slots is always increased between downstream nodes first, and the number of time slots is increased between upstream nodes later. The number of time slots between upstream nodes is always kept less than the number of time slots between downstream nodes, that is, the service bandwidth between upstream nodes is less than the service bandwidth between downstream nodes, to avoid the upstream service bandwidth in the pipeline being greater than the downstream service bandwidth, resulting in service overflow. In the process of increasing time slots, the end-to-end bandwidth increase adjustment of the service is completed only after the last two nodes complete the time slot increase adjustment. Therefore, the end-to-end time slot negotiation requires the completion of time slot negotiation and time slot adjustment between each two adjacent nodes in turn, and the end-to-end time slot negotiation time is relatively long.
[0047] according to Figure 3 and Figure 4It can be seen from the corresponding time slot negotiation and adjustment process that the bandwidth adjustment process in the relevant technology is negotiated and adjusted section by section. After one section of adjustment is completed, the adjustment work of the next section is started, and the adjustment process is very time-consuming; at the same time, the section-by-section negotiation and section-by-section adjustment bring a disadvantage, that is, some nodes have completed the adjustment, while some nodes encounter unexpected situations during the adjustment process. For example, in some cases, the CR signal and CA signal of the node are lost due to interference during the adjustment process; or in some cases, the node encounters difficulties and cannot send the response CA signal in time, resulting in the failure of negotiation between upstream and downstream nodes; in the above case, when the time slot adjustment negotiation between some nodes fails, the subsequent time slot adjustment work cannot be carried out, so that some nodes that have successfully adjusted on the network carry services according to the new number of time slots, and some nodes carry services according to the old number of time slots, resulting in inconsistent end-to-end bearer bandwidth of the service. It can be seen from this that the existing lossless bandwidth adjustment requires multiple CR / CA / C negotiations on the forwarding plane, especially for scenarios where the adjustment cannot be successful, involving multiple collaborations and fallbacks between equipment and network management, and high requirements for network management.
[0048] Based on this, an embodiment of the present application provides a bandwidth configuration method, an electronic device, and a storage medium, wherein a request message is sent to a control system through a source device, wherein the request message carries bandwidth demand information. The source device receives a response message returned by the control system, wherein the response message carries bandwidth confirmation information generated by the control system according to the bandwidth demand information, thereby realizing accurate connection between the source device and the control system. Afterwards, the source device generates a time slot configuration message according to the bandwidth confirmation information, and sends a time slot configuration message to a downstream device, so that the downstream device performs a time slot configuration operation according to the time slot configuration message. Therefore, compared with the related art, the embodiment of the present application can be applied to a bandwidth adjustment method for a path calculation 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 plane, improving the bandwidth configuration rate, and improving the efficiency of service deployment.
[0049] The bandwidth configuration method provided in the embodiment of the present application can be applied to Figure 5In the scenario shown in FIG. 1 , the nodes that carry customer services are the source node 100, the destination node 300, and two intermediate nodes 200. The device where the source node 100 is located is the source device, and the source device at this time is also the PCC. The source device and the control system 500 are connected in communication according to 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 through the interaction 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 is used to centrally calculate the path to achieve global optimality of the path, thereby achieving the purpose of making full use of network resources.
[0050] 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 exemplary illustration.
[0051] 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 the 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 of RSVP-TE. The embodiment of the present application considers a fine-grained type of bandwidth adjustment and service establishment control method dedicated to the TDM mechanism, which can be applied to both the fine-grained metropolitan area transport network (Fine Grain MetroTransport Network, fgMTN) and the fine-grained optical transport network (Fine Grain Optical Transport Network, fgOTN).
[0052] In the bandwidth configuration method of the embodiment of the present application, refer to Figure 6 As shown, the implementation process of a bandwidth configuration method provided in an embodiment of the present application applied to a source device (ie, source node 100) may include but is not limited to the following steps S610 to S630, and each step is introduced in turn below:
[0053] Step S610: Send a request message to the management and control system, where the request message carries bandwidth demand information.
[0054] It should be noted that the bandwidth requirement information includes time slot granularity indication information and time slot quantity indication information.
[0055] It is understandable that the time slot granularity indication information is information used to indicate the time slot granularity of a path in the fgMTN or fgOTN scenario. For example, in fgOTN, an optical path refers to a path of an optical signal transmitted through an optical fiber. An optical path can be divided into different time slots, each of which can be used to transmit different data streams or communication services. The time slot granularity indication information is used to indicate the time slot division granularity of each optical path, that is, the size of the time slot.
[0056] It is understandable that the time slot number indication information refers to information used to indicate the number of time slots of a path in a fgMTN or fgOTN scenario. For example, in fgOTN, the time slot number indication information is used to indicate the number of time slot divisions of each optical path.
[0057] 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.
[0058] It is understandable that the embodiment of the present application defines a bandwidth specification object of an fg layer network, which is applied to the bandwidth specific object of the PCEP interaction between the PCC (also called the source device) and the PCE (also called the controller).
[0059] Exemplarily, the PCC (also called the source device) initiates a request message PCReq to the PCE (also called the controller) to achieve a better time slot path configuration. When requesting path calculation, request parameters (RP) or SRP (Stateful PCE Request Parameters) are usually carried in each PCReq. Figure 7 A schematic diagram of the format of the RP provided in an embodiment of the present application is shown. Figure 7The first line in 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 time slot 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 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. It is usually generated by the system or application for each request and remains unchanged throughout the life cycle of the request.
[0060] 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.
[0061] It should be noted that RP refers to the parameters or information carried when sending a request. When the PCC sends a request message to the PCE, it can provide additional information by including parameters in the request. These parameters can be used to specify specific requirements of the request, filter the returned results, control the behavior of the request, etc.
[0062] For example, Figure 8 A format diagram of a bandwidth specification object provided in an embodiment of the present application is shown. The field length of the bandwidth specification length (Bandwidth Specification Length) is 16 bits, the field length of the bandwidth specification type BwSpec 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 (GeneralizedBandwidth) is 32 bits, the field length of the optional reverse generalized bandwidth field (Reverse GeneralizedBandwidth (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.
[0063] It should be noted that the 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 at this time 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.
[0064] 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.
[0065] It should be noted that the general bandwidth represents the transmission capability and is used to describe the capability of signal or data transmission, such as the flow parameter in RSVP-TE. The reserved field can be used to meet more functions in subsequent application scenarios.
[0066] 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.
[0067] 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.
[0068] For example, Fig. 9 A format diagram of a signal type object provided in an embodiment of the present application is shown. 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 slot 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.
[0069] It is understandable that multiplexing can improve transmission efficiency and bandwidth utilization and save communication resources. By merging multiple independent signals or data streams into one channel, multiple signals can be transmitted simultaneously, reducing transmission overhead. At the receiving end, the merged signal or data stream can be demultiplexed according to the specific multiplexing protocol and mechanism to restore the original independent signal or data stream.
[0070] 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.
[0071] It is understandable that after the PCC (also called the source device) initiates a request message PCReq to the PCE (also called the controller), the PCE (also called the controller) will return a response message (referred to as PCRep) to the PCC (also called the source device). Bandwidth confirmation information refers to a message used to confirm the available bandwidth of the network connection between the PCC and the PCE.
[0072] It is understandable that the bandwidth confirmation information includes time slot granularity confirmation information and time slot quantity confirmation information.
[0073] 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.
[0074] It is understandable that when the connection between the PCC (also called the source device) and the PCE (also called the controller) is successful, the content of the response message PCRep returned by the PCE (also called the controller) to the PCC (also called the source device) is the same as the request message PCReq. Therefore, 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.
[0075] 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.
[0076] 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.
[0077] 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.
[0078] 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 confirmation client signal type.
[0079] 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.
[0080] It is understandable that when the PCC (also called the source device) contains an existing service path, fine-grained lossless bandwidth adjustment can be performed based on TDM in the PCE scenario. At this time, 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 an 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 a time slot configuration deletion on the service path.
[0081] It is understandable 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 called the source device) and the PCE (also called 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.
[0082] For example, please refer to Figure 7 , R represents the rerouting flag, the path identifier is used to indicate the service path for requesting rerouting, and O represents the operation type information. At this time, the field length of the rerouting flag R is 1 bit, and the field length of the operation type information O is 1 bit. It should be noted that the lengths of different fields in the format are not specifically limited, and in practical applications, they can be flexibly adjusted according to actual needs.
[0083] It should be noted that the first preset value is used to represent the value of rerouting the existing service path, such as 0, 1, etc., which is not specifically limited here. For example, the first preset value is 1, and when the rerouting flag bit R=1, it means 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, it is necessary to carry the reported route object (RRO) in the request message PCReq to describe the path of the currently existing TE LSP, that is, RRO is used to represent the specific path. It should be noted that RRO is used to carry the actual path information of the PCC. In addition, when the rerouting flag bit R=1, the bandwidth of the existing TE LSP must be carried in the bandwidth specification object, and the bandwidth also needs to include the bandwidth expected by the rerouted LSP. However, this method cannot adjust for lossless bandwidth, that is, regardless of whether the route changes, the existing RRO needs to be carried in PCReq, thereby reducing the bandwidth configuration rate and service deployment efficiency.
[0084] Based on this, it is understandable that please refer to Figure 7The time slot adjustment request message of the present application 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 time slot adjustment request message carries RRO.
[0085] It is understandable that the present application adds a lossless bandwidth adjustment flag bit H in RP to represent the way of performing lossless bandwidth adjustment, and the lossless bandwidth adjustment flag bit H can be used together with the rerouting flag bit R to determine whether to start the lossless bandwidth method. The second preset value is used to represent the value of enabling lossless bandwidth adjustment, such as 1, 2, etc., which is not specifically limited here.
[0086] Exemplarily, the first preset value and the second value are both 1. When 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), the lossless bandwidth adjustment method is enabled. Therefore, the route does not change in this lossless bandwidth adjustment method, and the time slot adjustment request message does not need to carry RRO to describe the current TE LSP path.
[0087] The PCC (also called source device) of the present application can determine whether the time slot adjustment request message carries the record routing object RRO based on the judgment of the lossless bandwidth adjustment flag by adding a lossless bandwidth adjustment flag in the time slot adjustment request message. Therefore, for scenarios where lossless bandwidth is considered, the time slot adjustment request message does not carry RRO, that is, the routing does not change when the lossless bandwidth adjustment is enabled, and there is no need to carry RRO to describe the current TE LSP path. For scenarios where lossless bandwidth is considered, RRO must be carried to describe the current TE LSP path, which can effectively improve the bandwidth configuration rate and service deployment efficiency in lossless bandwidth scenarios.
[0088] It is understandable that when the request message is a path establishment request message, the path establishment request message also carries source address information and destination address information. At this time, the response message also carries path information, and the path information is used to indicate the business path generated by the management and control system according to the source address information, the destination address information and the bandwidth requirement information. The business path includes multiple devices that meet the bandwidth requirement information.
[0089] In other words, after the PCC (also called the source device) initiates a path establishment request message to the PCE (also called the controller), the PCE (also called the controller) will return a response message to the PCC (also called the source device). At this time, the path establishment request message also carries the source address information and the destination address information. The PCE (also called the controller) will generate a service path based on the source address information, the destination address information and the bandwidth requirement information in the path establishment request message. The service path is used to indicate the path information of the PCC (also called the source device) hop by hop in the downstream device.
[0090] It should be noted that the source address information refers to the starting address information of the service path, and the destination address information refers to the ending address information of the service path. Figure 5 As shown, 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. At this time, the downstream devices of the PCC (also called the source device) include the sink node 300 and two intermediate nodes 200.
[0091] It should be noted that since this application is requesting to calculate the optimized path of a current LSP, and the bandwidth requirements after optimization are different, such as Figure 7 The RP has already clarified 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 original process is followed to carry the current bandwidth and target bandwidth. In order to maintain compatibility with the original process, for the request 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 calculates whether the current resource demand can be met. The PCE only calculates the demand that can be met, and the PCC (also called the source device) completes the specific time slot negotiation.
[0092] It is understandable that the time slot quantity indication information includes the service occupied time slot quantity information, and the time slot quantity confirmation information includes the service occupied time slot quantity confirmation information. It should be noted that when the connection between the PCC (also called the source device) and the PCE (also called the management and control system) is successful, the service occupied time slot quantity information and the service occupied time slot quantity confirmation information are the same.
[0093] Understandably, please refer 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 also includes: step 1010, performing corresponding time slot configuration operations according to the bandwidth confirmation information.
[0094] The embodiment of the present application is a fine-grained TDM-based lossless bandwidth adjustment in a PCE scenario, that is, by carrying a lossless bandwidth adjustment flag in PCReq, a request is made to enter a 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 called the source device) and the PCE (also called 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.
[0095] Step 630: Generate a time slot configuration message according to the bandwidth confirmation information, and send the time slot configuration message to the downstream device, so that the downstream device performs a time slot configuration operation according to the time slot configuration message.
[0096] It is understandable that the time slot configuration information carries the following information:
[0097] Customer signal identification, used to identify customer information;
[0098] A bit map, including a plurality of bits, each bit corresponding to a state of a time slot in a service signal;
[0099] Bitmap length information, used to indicate the length of the bitmap;
[0100] 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.
[0101] For example, Fig.11 A format diagram of the time slot configuration information is shown. The field length of the client signal identifier is 10 bits, the field length of the bitmap is 32 bits, the field length of the bitmap length information is 10 bits, the field length of the start time slot position information is 10 bits, the field length of the reserved field is 2 bits, and the field length of the variable padding bit (PaddingBits (Variable)) is 32 bits. 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.
[0102] 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.
[0103] Exemplarily, the client signal identifier is consistent with the forwarding plane encoding, and for fgMTN, the encoding is 1-480, of which 0b0000000001 and 0b1111000000 are valid values, and 0b0000000000 indicates no occupancy. For fgOTN, the value range of the client signal identifier varies with the service layer carried. When carried on Optical Processing Unit 0 (OPU0), the client signal identifier takes a value of 1-119; when carried on OPU1, the client signal identifier takes a value of 1-238; when carried on OPU2, the client signal identifier takes a value of 1-8*119. Whether it is fgMTN or fgOTN, the client signal identifier will be carried on the forwarding plane, encapsulated in the OH frame for fgMTN, and encapsulated as MSI for fgOTN to indicate the specific time slot position in the overhead. When fg is multiplexed to a service layer and occupies one or more time slots, a new client signal identifier and specific occupied time slots are allocated at both ends of the fg link, usually allocated at the downstream node and carried to the upstream node through the control plane. On the forwarding plane, the upstream client signal identifier and bitmap are encapsulated and written into the service layer overhead to facilitate detection and verification by the sink. Therefore, the control plane can be negotiated in advance for use by the forwarding plane.
[0104] It should be noted that variable padding bits refer to extra bits added during data transmission or storage to meet specific requirements or regulations. Padding bits are usually used to align, protect or fill data to ensure data integrity and correctness.
[0105] It should be noted that, since the number of time slots occupied by the fg type is large, it is considered to add the starting time slot position information as the starting position to indicate the starting position of the bitmap, and by default it is 0, that is, starting from time slot 1. The bitmap is a variable, indicating the entire time slot list or time slot list fragment of the bottom layer to be changed in the current fg layer.
[0106] It is understandable that after each node of the downstream device receives the time slot configuration message, it 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.
[0107] It is understandable that the management and control system in the embodiment of the present application is a path computation unit PCE, and the source device is a path computation client PCC.
[0108] It should be noted that if Figure 5As shown, after the source node 100 corresponding to the PCC (also called the source device or source node 100) receives the response message returned by the PCE (also called the management and control system), the PCC (also called the source device or source node 100) generates a time slot configuration message according to the bandwidth confirmation information, that is, it carries the number of time slots to be changed to indicate the label of the downstream device of each hop along the way. And send the 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, at this time, node P1, node P2 and host node 300 are downstream nodes of the source node 100. After node P1 receives the request message sent by the source node 100, it processes it in turn and downstream to node P2. The downstream node sends a response message and carries the time slot configuration message to be allocated. After the upstream node receives the confirmation message of the downstream node, the upstream node decides and confirms the specific time slots added / deleted on the final downstream inlet and upstream outlet links.
[0109] Therefore, after the signaling negotiation is completed, the upstream node sends a message on the next forwarding plane to complete the lossless bandwidth adjustment along the way. This embodiment does not limit the specific control signaling carrying protocol type. Since it is a control plane negotiation, the forwarding plane processing is not limited. This application can simultaneously meet the time slot adjustment problem of negotiating multiple customers.
[0110] It is understandable that in the bandwidth configuration method of the embodiment of the present application, referring to Fig.12 As shown, the implementation process of a bandwidth configuration method provided in an embodiment of the present application applied to a management and control system may include but is not limited to the following steps S1210 to S1230, and each step is introduced in turn below:
[0111] Step 1210: Receive a request message sent by a source device, where the request message carries bandwidth requirement information.
[0112] It should be noted that the bandwidth requirement information has been described in the above embodiment and will not be repeated here.
[0113] Step 1220: Generate bandwidth confirmation information according to the bandwidth demand information, and encapsulate the bandwidth confirmation information into the response information.
[0114] It should be noted that the response information refers to the information generated by the management and control system after confirming the received request information. The bandwidth confirmation information has been described in the above embodiment and will not be repeated here.
[0115] Step 1230: Return a response message to the source device, wherein 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.
[0116] It should be noted that the time slot configuration message has been described in the above embodiment and will not be repeated here.
[0117] Understandably, please refer 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:
[0118] Step 1310: Determine at least one candidate service path according to the source address information and the destination address information.
[0119] It is understandable that there are multiple candidate service paths between the source address information and the destination address information.
[0120] Step 1320: Determine a service path from at least one candidate service path according to the bandwidth requirement information, and each device in the service path meets the bandwidth requirement information.
[0121] It can be understood that the service path refers to a path that can meet the bandwidth demand information for the problem of a large number of fg time slots and is generated by a lossless bandwidth adjustment mechanism without rerouting.
[0122] Step 1330: Generate path information according to the service path, and encapsulate the path information into the response information.
[0123] It is understandable that the path information refers to the information of the downstream devices passed in sequence. The source device can generate the time slot configuration information according to the hard answer information returned by the management and control system, so that the downstream device can perform the time slot configuration operation according to the time slot configuration information.
[0124] 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 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; the response message carries a path confirmation identifier corresponding to the path identifier and operation type confirmation information corresponding to the operation type information.
[0125] It is understandable that when there is no service path in the PCC (also called 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 the present application is divided into two parts, the first part is the PCEP interaction. When the PCC (also called the source device or the 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 the 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 the PCE receives the PCReq message sent by the PCC, the path calculation process is triggered. 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 way. 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.
[0126] The embodiment of the present application can propose a non-rerouting lossless bandwidth configuration method to address the problem of a large number of fg time slots in the PCE scenario, that is, by reducing the CR / CA mechanism of the forwarding plane, lossless adjustment can be completed by only transmitting the time slot configuration information on the forwarding plane. The present application can effectively unify the process of TDM-based path establishment and bandwidth adjustment in the PCE scenario. Therefore, the embodiment 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, which reduces the complexity of the forwarding plane, improves the bandwidth configuration rate, and improves the efficiency of service deployment.
[0127] It should be noted that although the operations are described in a specific order in the drawings in the embodiments of the present application, it should not be understood as requiring the operations to be performed in the specific order or serial order shown, or requiring the execution of all the operations shown to obtain the desired results. In certain environments, multitasking and parallel processing may be advantageous.
[0128] 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.
[0129] The present application also provides an electronic device, such as Fig.14 As shown, the electronic device 1400 includes:
[0130] one or more processors 1410;
[0131] 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:
[0132] For example, a bandwidth configuration method applied to a source device (also referred to as a source node 100); or,
[0133] Such as the bandwidth configuration method applied to the management and control system.
[0134] The memory 1420, as a non-transient network system, 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 arranged 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.
[0135] 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 by software or firmware, the relevant program codes are stored in the memory 1420, and the processor 1410 calls and executes the methods of the embodiments of this application.
[0136] The processor 1410 can be implemented by 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.
[0137] In some embodiments, reference Fig.14 As shown, the electronic device also includes:
[0138] Input / output interface, used to realize information input and output;
[0139] Communication interface, used to realize communication interaction between this device and other devices, which can be realized through wired mode (such as USB, network cable, etc.) or wireless mode (such as mobile network, WIFI, Bluetooth, etc.);
[0140] A bus that transmits information between various components of the device (e.g., processor 1410, memory 1420, input / output interface, and communication interface);
[0141] The processor 1410 , the memory 1420 , the input / output interface and the communication interface can be connected to each other in communication within the device via a bus.
[0142] An embodiment of the present application further provides a computer-readable storage medium storing computer-executable instructions for executing:
[0143] For example, a bandwidth configuration method applied to a source device (also referred to as a source node 100); or,
[0144] Such as the bandwidth configuration method applied to the management and control system.
[0145] An embodiment of the present application further provides a computer program product, including a computer program or a computer instruction, wherein the computer program or the computer instruction is stored in a computer-readable storage medium, and a processor of a computer device reads the computer program or the computer instruction from the computer-readable storage medium, and the processor executes the computer program or the computer instruction, so that the computer device executes and implements:
[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 applied to the management and control system.
[0148] 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.
[0149] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and 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. As an illustration and not limitation, RAM is available in many 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).
[0150] It will be appreciated by those skilled in the art that all or some of the steps and systems in the disclosed method above may be implemented as software, firmware, hardware and appropriate combinations thereof. Some physical components or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor or a microprocessor, or may be implemented as hardware, or may be implemented as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or a non-transitory medium) and a communication medium (or a temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, 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 may be used to store desired information and may be accessed by a computer. Furthermore, it is well known to those skilled in the art that 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.
[0151] The above describes some embodiments of the present application with reference to the accompanying drawings, but does not limit the scope of the present invention. Any modification, equivalent substitution and improvement made by those skilled in the art without departing from the scope and essence of the present invention 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, characterized in that: The bandwidth requirement information includes time slot granularity indication information and time slot quantity indication information.
3. The method according to claim 2, characterized in that 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, characterized in 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 a value of the quantity indication field.
5. The method according to claim 4, characterized in that 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, characterized in that The bandwidth confirmation information includes time slot granularity confirmation information and time slot quantity confirmation information.
7. The method according to claim 6, characterized in that 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, characterized in 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.
9. The method according to claim 8, characterized in that 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, characterized in that 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, characterized in that 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, characterized in 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 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, characterized in that 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, characterized in 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.
15. The method according to claim 1, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that The bandwidth requirement information includes time slot granularity indication information and time slot quantity indication information.
20. The method according to claim 19, characterized in that 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, characterized in 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 a value of the quantity indication field.
22. The method according to claim 21, characterized in that 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, characterized in that The bandwidth confirmation information includes time slot granularity confirmation information and time slot quantity confirmation information.
24. The method according to claim 23, characterized in that 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, characterized in 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.
26. The method according to claim 25, characterized in that 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, characterized in that 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, characterized in that 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 according to claim 23, characterized in that 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 according to claim 29, characterized in that 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 according to claim 29, characterized in 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.
32. The method according to claim 18, characterized in that 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.