Slice packet network and time slot adjustment method of slice packet network

Abstract

The application discloses a slice grouping network and a time slot adjustment method of the slice grouping network. The method comprises the following steps: a source end device sends first request information to a destination end device through a node device, wherein a first request flag in the first request information is set to 1, and time slot adjustment information is carried in a reserved field of the first request information; the source end device receives first response information sent by the destination end device through the node device, wherein a first response flag in the first response information is set to 1; in response to that the source end device receives the first response information within a preset time period, the source end device sends control information to the destination end device through the node device, wherein an enabling flag in the control information is set to 1. The application solves the technical problem of low adjustment accuracy of the time slot adjustment of the slice grouping network in the prior art.

Description

Technical Field

[0001] This invention relates to the field of computer processing, and more specifically, to a slice packet network and a method for adjusting the time slots of the slice packet network. Background Technology

[0002] A Slicing Packet Network (SPN) slice channel is a transmission path between source and destination nodes in a network, used to provide end-to-end Ethernet slice connections. It features low latency, transparent transmission, and hard isolation. Client-layer services are mapped to client programs at the source node, cross-connected at intermediate network nodes based on Ethernet 66B code block sequences, and then demapped from the client at the destination node. It enables functions such as client data access / recovery, adding / deleting Operation Administration and Maintenance (OAM) information, cross-connection of data streams, and channel monitoring and protection.

[0003] However, with the increasing variety of network applications, more and more high-value, low-bandwidth services have emerged. When using FlexE networks to transmit these service data, the smallest granularity of data slicing is 5 gigabits per second (bps). These low-bandwidth services cannot fully utilize the transmission bandwidth, resulting in bandwidth waste. Therefore, fine-grained slicing technology has emerged.

[0004] The existing fine-grained slicing technology not only has the problem of not being able to detect the location of abnormal nodes, but also causes the channel bandwidth to be occupied. This leads to inaccurate time slot adjustment of the slice packet network by the source and destination devices.

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

[0006] This invention provides a slice packet network and a method for adjusting the time slots of the slice packet network, so as to at least solve the technical problem of low adjustment accuracy in the prior art when adjusting the time slots of the slice packet network.

[0007] According to one aspect of the present invention, a time slot adjustment method for a sliced ​​packet network is provided, comprising: a source device sending first request information to a destination device through a node device, wherein a first request flag in the first request information is set, and a reserved field in the first request information carries time slot adjustment information, the time slot adjustment information being used to adjust the time slot table currently used by the node device and the destination device; the source device receiving first response information sent by the destination device through the node device, wherein a first response flag in the first response information is set; in response to the source device receiving the first response information within a preset time period, the source device sending control information to the destination device through the node device, wherein an enable flag in the control information is set, the control information being used to control the source device, the node device, and the destination device to use the adjusted time slot table in the next transmission of a multiframe.

[0008] Optionally, in response to the source device not receiving the first response information within a preset time period, the method further includes: the source device sending second request information to the destination device through the node device, wherein the second request flag in the second request information is set; the source device receiving the second response information sent by the node device and the destination device, wherein the second response flag in the second response information is set, and the reserved field of the second response information carries a target response status, the target response status being used to characterize the first status of the source device sending the first response information, and the second status of the node device sending and receiving the first response information; the source device sending the target response status to a preset device, wherein the target response status is processed by the preset device to determine the device that has an anomaly in the slice packet network.

[0009] Optionally, the second state is obtained by performing logical operations on the result of the node device receiving the first response information and the result of the node device sending the first response information, and the states corresponding to different devices are stored in different positions in the reserved field.

[0010] Optionally, the number of second response messages is related to the number of devices in the slice packet network.

[0011] Optionally, after the source device sends control information to the destination device through the node device, the method further includes: the source device receiving feedback information sent by the destination device after waiting for a preset time through the node device, wherein the completion flag in the feedback information is set, and the bit in the reserved field of the feedback information corresponding to the target device is set, the target device including the node device and the destination device; the source device sending feedback information to a preset device, wherein the feedback information is processed by the preset device to determine the device that has an anomaly in the slice packet network.

[0012] Optionally, the method further includes one of the following: after the source device sends control information to the destination device through the node device, the data bandwidth of the control slice packet network is increased; before the source device sends the first request information to the destination device through the node device in the slice packet network, the data bandwidth of the control slice packet network is decreased; before the source device sends the first request information to the destination device through the node device in the slice packet network, the source device receives time slot adjustment information sent by the destination device through the node device, wherein a preset flag is set in the time slot adjustment information.

[0013] According to another aspect of the present invention, a time slot adjustment method for a sliced ​​packet network is also provided, comprising: a node device receiving first request information sent by a source device and forwarding the first request information to a destination device, wherein a first request flag in the first request information is set, and a reserved field in the first request information carries time slot adjustment information, the time slot adjustment information being used to adjust the time slot table currently used by the node device and the destination device; the node device receiving first response information sent by the destination device and forwarding the first response information to the source device, wherein a first acknowledgment flag in the first response information is set; the node device receiving control information sent by the source device and forwarding the control information to the destination device, wherein an enable flag in the control information is set, the control information being used to control the source device, the node device, and the destination device to use the adjusted time slot table in the next transmission of a multiframe.

[0014] According to another aspect of the present invention, a time slot adjustment method for a sliced ​​packet network is also provided, comprising: a destination device receiving first request information sent by a source device through a node device, wherein a first request flag is set in the first request information, and a reserved field of the first request information carries time slot adjustment information, the time slot adjustment information being used to adjust the time slot table currently used by the node device and the destination device; the destination device sending first response information to the source device through the node device, wherein a first response flag is set in the first response information; and the destination device receiving control information sent by the source device through the node device, wherein an enable flag is set in the control information, the control information being used to control the source device, the node device, and the destination device to use the adjusted time slot table in the next transmission of a multiframe.

[0015] According to another aspect of the present invention, a slice packet network is also provided, comprising: a source device configured to send first request information, wherein a first request flag is set in the first request information, and a reserved field of the first request information carries time slot adjustment information, the time slot adjustment information being used to adjust the time slot table currently used by the node device and the destination device; a destination device configured to send first response information, wherein a first response flag is set in the first response information; the source device further configured to receive the first response information within a preset time period and send control information, wherein an enable flag is set in the control information, the control information being used to control the source device, the node device, and the destination device to use the adjusted time slot table in the next transmission of a multiframe; and a node device configured to forward the first request information and control information to the destination device, and forward the first response information to the source device.

[0016] Optionally, the source device includes: a first time slot scheduling module for scheduling raw data according to a time slot table; a first information insertion module for generating first request information; and a first data sending module for combining the raw data and the first request information into a first data stream and sending the first data stream to the node device.

[0017] Optionally, the destination device includes: a first data receiving module for receiving a second data stream sent by a node device, wherein the second data stream contains original data and first request information; a first information extraction module for extracting the first request information from the second data stream; a status judgment module for determining whether the time slot table currently used by the destination device has been successfully adjusted; and a first time slot recovery module for recovering the original data based on the time slot table.

[0018] Optionally, the node device includes: a second data receiving module for receiving a third data stream, wherein the third data stream contains original data and first request information; a second information extraction module for extracting the first request information from the third data stream; a second time slot recovery module for recovering the original data based on a time slot table; a second time slot scheduling module for scheduling the original data based on a time slot table; a second information insertion module for generating the first request information; and a second data sending module for combining the original data and the first request information into a second data stream and sending the second data stream to the destination device.

[0019] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored program, wherein, when the program is running, the device on which the computer-readable storage medium is located executes any of the above methods.

[0020] According to another aspect of the present invention, a processor is also provided, which is used to run a program, wherein the program executes any of the methods described above during runtime.

[0021] In this embodiment of the invention, a source device sends a first request message to a destination device via a node device. The first request message contains a first request flag set to a bit position, and a reserved field in the first request message carries time slot adjustment information. This time slot adjustment information is used to adjust the time slot tables currently used by the node device and the destination device. The source device receives a first response message from the destination device via the node device. The first response message contains a first acknowledgment flag set to a bit position. In response to the source device receiving the first response message within a preset time period, the source device sends control information to the destination device via the node device. The control information contains an enable flag set to a bit position. This control information is used to control the source device, node device, and destination device to use the adjusted time slot table in the next multiframe transmission process. It is noteworthy that by setting the first request flag and time slot adjustment information in the first request information, and setting the first response flag in the first response information, the source device, node device, and destination device can accurately obtain the time slot adjustment result and identify the location of the device where the time slot adjustment anomaly occurs. Consequently, the source device, node device, and destination device can use the adjusted time slot table in the subsequent transmission of multiframes based on the control information, achieving the goal of accurately adjusting the time slots. This improves the technical accuracy of time slot adjustment and solves the technical problem of low adjustment accuracy in the prior art for time slot adjustment in slice packet networks. Attached Figure Description

[0022] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0023] Figure 1 This is a flowchart of a time slot adjustment method for a sliced ​​packet network according to an embodiment of the present invention;

[0024] Figure 2 This is a schematic diagram of an optional FlexE overhead frame and multiframe format according to an embodiment of the present invention;

[0025] Figure 3 This is a schematic diagram of an optional fine-grained basic unit overhead frame format according to an embodiment of the present invention;

[0026] Figure 4 This is a flowchart of an optional FlexE channel time slot increase method according to an embodiment of the present invention;

[0027] Figure 5 This is a flowchart of an optional fine-particle channel time slot enlargement method according to an embodiment of the present invention;

[0028] Figure 6 This is a flowchart of an optional FlexE channel time slot reduction method according to an embodiment of the present invention;

[0029] Figure 7 This is a flowchart of an optional fine-particle channel time slot reduction method according to an embodiment of the present invention;

[0030] Figure 8 This is a schematic diagram of an optional channel timeslot enlargement process according to an embodiment of the present invention;

[0031] Figure 9 This is a schematic diagram of an optional channel time slot reduction process according to an embodiment of the present invention;

[0032] Figure 10 This is a flowchart of a time slot adjustment method for a sliced ​​packet network according to an embodiment of the present invention;

[0033] Figure 11 This is a flowchart of a time slot adjustment method for a sliced ​​packet network according to an embodiment of the present invention;

[0034] Figure 12 This is a schematic diagram of a sliced ​​group network according to an embodiment of the present invention;

[0035] Figure 13 This is an optional device applied to the SPN channel transmitter according to an embodiment of the present invention;

[0036] Figure 14 This is an optional device applied to the SPN channel receiver according to an embodiment of the present invention;

[0037] Figure 15 This is an optional device applied to an intermediate node of an SPN channel according to an embodiment of the present invention. Detailed Implementation

[0038] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0039] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0040] Example 1

[0041] According to an embodiment of the present invention, an embodiment of a time slot adjustment method for a sliced ​​packet network is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0042] Figure 1 This is a flowchart of a time slot adjustment method for a sliced ​​packet network according to an embodiment of the present invention, as shown below. Figure 1 As shown, the method includes the following steps:

[0043] In step S102, the source device sends the first request information to the destination device through the node device. The first request information contains a first request flag and a reserved field that carries time slot adjustment information. The time slot adjustment information is used to adjust the time slot table currently used by the node device and the destination device.

[0044] The aforementioned source device can be a network device that initiates time slot adjustment, such as a local network device, but is not limited to this. The aforementioned node device can be a device that forwards information. The aforementioned destination device can be a network device that receives time slot adjustment, such as a peer network device, but is not limited to this. The aforementioned first request information can be information from the source device requesting time slot adjustment of the time slot table, such as a Calendar Switch Request (CR) message, but is not limited to this. The aforementioned first request flag can be a flag that marks the CR request. A change in the first request flag from 0 to 1 or from 1 to 0 indicates that time slot adjustment information has been written. In this embodiment, the CR flag is used as an example for explanation, but it is not limited to this. The reserved field mentioned above can be a field that carries time slot adjustment information and is set in advance by the user. In this embodiment, in a 5Gbps time slot granularity Flexible Ethernet (FlexE) channel, the reserved field can be a third 66-bit code block using FlexE overhead. In a 10Mbps time slot granularity channel, the reserved field can be a 66-bit code block with a flag field of 4'b0011, but it is not limited to this.

[0045] In one alternative embodiment, Figure 2 This is a schematic diagram of an optional FlexE overhead frame and multiframe format according to an embodiment of the present invention, as shown below. Figure 2 As shown, in a FlexE channel with a 5Gbps time slot granularity, when it is necessary to adjust the time slots of the sliced ​​packet network, the source device can forward the first request information to the destination device through the node device. At this time, the first request flag is set. The first request information contains a CR flag (i.e., the first request flag is set) and a third 66-bit code block (i.e., the reserved field) using FlexE overhead. The reserved field carries time slot adjustment information, which is used to adjust the time slot table currently used by the node device and the destination device, such as by increasing or decreasing it.

[0046] In one alternative embodiment, Figure 3 This is a schematic diagram of an optional fine-grained basic unit overhead frame format (Fg-Bu) according to an embodiment of the present invention, as shown below. Figure 3As shown, in a channel with a 10Mbps timeslot granularity, when it is necessary to adjust the timeslots of the sliced ​​packet network, the source device can forward the first request information to the destination device through the node device. At this time, the first request flag is set. The first request information contains a CR flag (i.e., the first request flag is set) and a 66-bit code block with a Flag field of 4'b0011 (i.e., the reserved field). The reserved field carries timeslot adjustment information, which is used to adjust the timeslot table currently used by the node device and the destination device.

[0047] It should be noted that this invention uses reserved fields not yet used in the overhead information of FlexE and fine-grained slice Fg-Bu to transmit and process time slot reconfiguration status information and time slot reconfiguration completion status information. During and after the time slot reconfiguration process, the results of the entire network's time slot adjustment can be obtained, and the location of devices experiencing time slot adjustment anomalies can be identified, assisting network administrators in quickly locating and troubleshooting network faults.

[0048] In step S104, the source device receives the first response information sent by the destination device through the node device, wherein the first response flag in the first response information is set.

[0049] The aforementioned first response information can be information responding to the first request information. In this embodiment, a Calendar Switch Acknowledge (CA) message is used as an example, but it is not limited to this. The aforementioned first acknowledgement flag bit can be a flag bit marking the first response information. In response to the first response information flag bit changing from 0 to 1 or from 1 to 0, it indicates that the overhead information is the first response information. In this embodiment, a CA flag is used as an example, but it is not limited to this.

[0050] In one optional embodiment, in response to receiving the first request information, the destination device may send the first response information to the source device. At this time, the first response flag is set, and the source device can receive the first response information sent by the destination device through the node device. The first response information includes the first response flag being set.

[0051] In step S106, in response to the source device receiving the first response information within a preset time period, the source device sends control information to the destination device through the node device. The enable flag in the control information is set, and the control information is used to control the source device, node device and destination device to use the adjusted time slot table in the next transmission of multiframes.

[0052] The aforementioned preset time can be a time set by the user in advance to indicate that the source device has successfully received the first response information. If the source device receives the first response information within the preset time period, it indicates that the source device has successfully received the first response information. If the source device receives the first response information outside the preset time period, it indicates that the source device has failed to successfully receive the first response information. The aforementioned enable flag can be a flag that marks control information. If the enable flag changes from 0 to 1 or from 1 to 0, it indicates that control information has been written. In this embodiment, the Calendar configuration in use (CCC) is used as an example, but it is not limited to this. The CCC consists of C flags in three different code blocks.

[0053] In one optional embodiment, in response to the source device receiving the first response information within a preset time period, indicating that the source device has successfully received the first response information, the source device can send control information to the destination device through the node device. At this time, the enable flag is set. The control information enables the source device, node device and destination device to use the adjusted time slot table in the next transmission of multiframes.

[0054] Optionally, in response to the source device not receiving the first response information within a preset time period, the method further includes: the source device sending second request information to the destination device through the node device, wherein the second request flag in the second request information is set; the source device receiving the second response information sent by the node device and the destination device, wherein the second response flag in the second response information is set, and the reserved field of the second response information carries a target response status, the target response status being used to characterize the first status of the source device sending the first response information, and the second status of the node device sending and receiving the first response information; the source device sending the target response status to a preset device, wherein the target response status is processed by the preset device to determine the device that has an anomaly in the slice packet network.

[0055] The aforementioned second request information can be information for querying the time slot switching response result. In this embodiment, a Calendar Switch Acknowledge Result Request (CAR) is used as an example, but it is not limited to this. The aforementioned second request flag can be a flag that marks the second request information. A change in the second request flag from 0 to 1 or from 1 to 0 indicates that the second request information has been written. The aforementioned second response information can be information that responds to the second request information. In this embodiment, a Calendar Switch Acknowledge Result Acknowledge (CAA) is used as an example, but it is not limited to this. The aforementioned second response flag can be a flag that marks the second response information. A change in the second response flag from 0 to 1 or from 1 to 0 indicates that the target response status has been written. The aforementioned first status can be successful reception of the first request information, and the aforementioned second status can be unsuccessful reception of the first request information. However, it is not limited to this; it can also be that the first status is unsuccessful reception of the first request information, and the second status is successful reception of the first request information. The aforementioned preset device can be a device that the user has set in advance to identify abnormal devices in the slice packet network. In this embodiment, the Provider Edge (PE) device is used as an example for illustration, but it is not limited to this.

[0056] In an optional embodiment, in response to the source device not receiving the first response information within a preset time, the source device can send a second request information to the destination device through the node device. At this time, the second request flag is set. Then, the source device can receive the second response information sent by the destination device through the node device. At this time, the second response flag is set, and the reserved field of the second response information carries the target response status. The target response status is the first status of the destination device sending the first response information and the second status of the node device sending and receiving the first response information. Since the source device failed to successfully receive the first response information, the first status and the second status are inconsistent. Therefore, the source device can send the target response status to the preset device. The preset device can process the target response status, thereby determining the device that is abnormal in the slice packet network.

[0057] In another optional embodiment, after a time slot adjustment timeout event occurs, the source device of the channel can initiate a time slot table switching response result query. Whether this query needs to be initiated can be configured via an enable switch. If the current device is configured to enable this function, the source device of the channel sets the CAR flag in its FlexE overhead information or the Fg-Bu overhead information of the fine-grained slice. After receiving the overhead information with the CAR flag set, the intermediate node device of the channel forwards it to the next node in the channel, and so on, until the CAR information is passed to the destination device of the channel. After receiving the CAR information, the destination device of the channel queries the status of its own CA transmission and initiates time slot table switching response result feedback. It sets the CAA flag in its FlexE overhead information or the Fg-Bu overhead information of the fine-grained slice, and writes the status of its own CA transmission to the corresponding position in the SwitchMap. For the destination device of the channel, it needs to send a number of FlexE overhead information or Fg-Bu overhead information with the CAA flag set, and the number of times it sends is related to the total number of devices in the channel. After receiving the overhead information indicating that the CAA flag is set, the source device of the Slicing Packet Network (SPN) channel extracts the SwitchMap [0~N] from the overhead information and sends it to the management and control system to determine the abnormal location of time slot reconfiguration. This allows the system to identify the location where the CA timeout occurred and address it accordingly to eliminate network faults.

[0058] Optionally, the second state is obtained by performing logical operations on the result of the node device receiving the first response information and the result of the node device sending the first response information, and the states corresponding to different devices are stored in different positions in the reserved field.

[0059] The logical operations described above may include, but are not limited to, AND, OR, and NOT operations. In this embodiment, the AND operation is used as an example for explanation, but it is not limited to this.

[0060] In an optional embodiment, a second state can be obtained by performing a logical AND operation on the result of the node device receiving the first response information and the result of the node device sending the first response information. The states corresponding to different devices are stored in different positions in a reserved field. Specifically, in the FlexE channel, the number of FlexE overhead frames sent is equal to the total number of devices in the entire channel divided by 8 (rounded up); in the fine-grained channel, the number of Fg-Bu overhead frames sent is equal to the total number of devices in the entire channel divided by 16 (rounded up). After receiving overhead information with the CAA flag set, the intermediate node device in the channel queries the result of receiving the CA from the preceding device and the result of sending the CA to the following device, performs a logical AND operation, and writes it to the corresponding position in the Switch Map. The corresponding position in the Switch Map mentioned in this invention can be the position of each network element in the entire SPN channel, or it can be other agreed-upon methods. For example, the source device of the channel can be designated as 0, which occupies bit [0] of the Switch Map; its next-level intermediate node is designated as 1, which occupies bit [1] of the Switch Map; and the destination device of the channel is designated as N, which occupies bit [N] of the Switch Map.

[0061] Optionally, the number of second response messages is related to the number of devices in the slice packet network.

[0062] In one alternative embodiment, the number of second response messages is related to the number of devices in the slice packet network. Specifically, in the FlexE channel, the number of second response messages is equal to the total number of devices in the entire channel divided by 8 (rounded up); in the fine-grained channel, the number of second response messages is equal to the total number of devices in the entire channel divided by 16 (rounded up).

[0063] Optionally, the method further includes one of the following: after the source device sends control information to the destination device through the node device, the data bandwidth of the control slice packet network is increased; before the source device sends the first request information to the destination device through the node device in the slice packet network, the data bandwidth of the control slice packet network is decreased; before the source device sends the first request information to the destination device through the node device in the slice packet network, the source device receives time slot adjustment information sent by the destination device through the node device, wherein a preset flag is set in the time slot adjustment information.

[0064] The aforementioned time slot adjustment information can be information sent by the destination device that reflects the completion status of time slot adjustment. The aforementioned preset flag bit can be a flag bit that marks the time slot adjustment information. In response to the preset flag bit changing from 0 to 1 or from 1 to 0, it indicates that time slot adjustment information has been written.

[0065] In one alternative embodiment, Figure 4 This is a flowchart of an optional FlexE channel slot enlargement method according to an embodiment of the present invention, such as... Figure 4 As shown, after the source device sends control information to the destination device through the node device, the method includes:

[0066] Step S401: Set the CR flag in the FlexE overhead information of the channel source device, start the CA timeout protection timer, and carry the time slot information to be increased at the same time;

[0067] In step S402, the intermediate node device of the channel receives the FlexE overhead information with the CR flag set and forwards it to the next level node device;

[0068] Step S403: The channel destination device receives the FlexE overhead information with the CR flag set, completes the configuration of the local backup time slot table, and sends out the CA flag set in the FlexE overhead information;

[0069] In step S404, the intermediate node device of the channel receives the FlexE overhead information with the CA tag set, forwards it to the next-level node device, and records the results of receiving and sending the CA tag at this node.

[0070] Step S405: Determine whether the channel source device has received the CA tag sent by the channel destination device within a predetermined time. If yes, proceed to step S406; otherwise, proceed to step S414.

[0071] Step S406: The channel source device sends FlexE overhead information with the C flag set, and distributes customer services using the updated time slot table starting from the next multiframe.

[0072] In step S407, the intermediate node device of the channel receives the FlexE overhead information with the C flag set, and starts receiving and continuing to distribute customer services to the next level device using the updated time slot table from the next multiframe.

[0073] In step S408, the channel destination device receives the FlexE overhead information with the C flag set, and starts receiving and resuming customer services from the next multiframe using the updated time slot table.

[0074] Step S409: After a specific period of time, the destination device of the channel sets the time slot adjustment completed (Switch Done, SD) flag in the FlexE overhead information, and at the same time sets the bit corresponding to the device position in the Switch Map.

[0075] In step S410, the intermediate node device of the channel receives the FlexE overhead information with the SD flag set, queries the time slot adjustment result of this device, and if the time slot adjustment is successful, sets the bit of the corresponding device position in the Switch Map.

[0076] In step S411, the channel source device receives the FlexE overhead information with the SD flag set, and at the same time collects the time slot adjustment results of each node device in the channel and reports them to the control system.

[0077] Step S412: Determine whether all devices in the channel have completed the time slot increase adjustment. If yes, proceed to step S413; otherwise, proceed to step S419.

[0078] Step S413: Increase the bandwidth for business data;

[0079] Step S414: The channel source device sends FlexE overhead information with the CAR flag set;

[0080] In step S415, the intermediate node device in the channel receives the FlexE overhead information with the CAR flag set and forwards it to the next node device;

[0081] Step S416: The channel destination device receives the FlexE overhead information with the CAR flag set, queries the result of sending the CA flag, and sends the FlexE overhead information with the CAA flag set. At the same time, it sets the bit of the corresponding device position in the Switch Map.

[0082] Step S417: The channel node device receives the FlexE overhead information with the CAR tag set, queries the results of the device receiving and sending CA tags, and if the reception and transmission of CA tags are completed simultaneously, sets the bit at the corresponding device position in the Switch Map.

[0083] In step S418, the channel source device receives the FlexE overhead information with the CAA flag set, collects the CA feedback results from each node device in the channel, reports them to the management and control system, and generates a CA timeout reason.

[0084] Step S419: Adjustment failed. Based on the reported time slot adjustment results, diagnose the fault or re-initiate the adjustment.

[0085] In another alternative embodiment, Figure 5This is a flowchart of an optional fine-particle channel time slot enlargement method according to an embodiment of the present invention, such as... Figure 5 As shown, after the source device sends control information to the destination device through the node device, the method includes:

[0086] Step S501: The destination device of the channel sends the Fg-Bu overhead information with the S flag set, and initiates the time slot increase adjustment;

[0087] In step S502, the intermediate node device of the channel receives the Fg-Bu overhead information with the S flag set and forwards it to the next-level node device;

[0088] Step S503: The channel source device receives the Fg-Bu overhead information with the S flag set, sets the CR flag in the Fg-Bu overhead information, starts the CA timeout protection timer, and carries the time slot information to be increased at the same time.

[0089] In step S504, the intermediate node device of the channel receives the Fg-Bu overhead information with the CR flag set and forwards it to the next level node device;

[0090] In step S505, the destination device of the channel receives the Fg-Bu overhead information with the CR flag set, completes the configuration of the local backup time slot table, and sends out the Fg-Bu overhead information with the CA flag set.

[0091] In step S506, the intermediate node device of the channel receives the Fg-Bu overhead information with the CA tag set, forwards it to the next-level node device, and records the results of receiving and sending the CA tag at this node.

[0092] Step S507: Determine whether the channel source device receives the CA tag sent by the channel destination device within the predetermined time. If yes, proceed to step S508; otherwise, proceed to step S516.

[0093] In step S508, the channel source device sends the Fg-Bu overhead information with the C flag set, and distributes customer services using the updated time slot table starting from the next multiframe;

[0094] In step S509, the intermediate node device of the channel receives the Fg-Bu overhead information with the C flag set, and starts receiving and continuing to distribute customer services to the next level device using the updated time slot table from the next multiframe.

[0095] In step S510, the channel destination device receives the Fg-Bu overhead information with the C flag set, and starts receiving and resuming customer services from the next multiframe using the updated time slot table.

[0096] Step S511: After a specific period of time, the destination device of the channel sets the SD flag in the Fg-Bu overhead information. The number of Fg-Bus sent is related to the total number of devices in the channel. At the same time, the bit corresponding to the device position in the Switch Map is set.

[0097] In step S512, the intermediate node device of the channel receives the Fg-Bu overhead information with the SD flag set, queries the time slot adjustment result of the stupid device, and if the time slot adjustment is successful, sets the bit of the corresponding device position in the Switch Map.

[0098] In step S513, the channel source device receives the Fg-Bu overhead information with the SD flag set, and at the same time collects the time slot adjustment results of each node device in the channel and reports them to the control system.

[0099] Step S514: Determine whether all devices have completed the time slot increase adjustment. If yes, proceed to step S515; otherwise, proceed to step S21.

[0100] Step S515: Increase the bandwidth for business data.

[0101] Step S516: The channel source device sends Fg-Bu overhead information with the CAR flag set;

[0102] In step S517, the intermediate node device of the channel receives the Fg-Bu overhead information with the CAR flag set and forwards it to the next level node device;

[0103] In step S518, the destination device of the channel receives the Fg-Bu overhead information with the CAR flag set, queries the result of sending the CA flag of this device, and sends the Fg-Bu overhead information with the CAA flag set. The number of Fg-Bu sent is related to the total number of devices in the channel. At the same time, the bit of the corresponding device position in the Switch Map is set.

[0104] Step S519: The intermediate node device of the channel receives the Fg-Bu overhead information with the CAA flag set, queries the results of receiving and sending the CA flag, and if the reception and transmission of the CA flag are completed at the same time, sets the bit of the corresponding device position in the Switch Map.

[0105] In step S520, the source device of the channel receives the Fg-Bu overhead information with the CAA flag set, and at the same time, the CA feedback results of each node device in the mobile channel are reported to the management and control system to generate the CA timeout reason.

[0106] Step S521: Adjustment failed. Based on the reported time slot adjustment results, diagnose the fault or re-initiate the adjustment.

[0107] In another alternative embodiment, Figure 6This is a flowchart of an optional FlexE channel slot reduction method according to an embodiment of the present invention, such as... Figure 6 As shown, before the source device sends the first request information to the destination device through the node device in the sliced ​​packet network, the method includes:

[0108] Step S601: Reduce service data bandwidth;

[0109] Step S602: The channel source device sets the CR flag in the FlexE overhead information, starts the CA timeout protection timer, and carries the time slot information to be reduced at the same time.

[0110] In step S603, the intermediate node device of the channel receives the FlexE overhead information with the CR flag set and forwards it to the next level node device;

[0111] Step S604: The channel destination device receives the FlexE overhead information with the CR flag set, completes the configuration of the local backup time slot table, and sends out the CA flag set in the FlexE overhead information;

[0112] In step S605, the intermediate node device of the channel receives the FlexE overhead information with the CA tag set, forwards it to the next-level node device, and records the results of receiving and sending the CA tag at this node.

[0113] Step S606: Determine whether the channel source device receives the CA tag sent by the channel destination device within the predetermined time. If yes, proceed to step S607; otherwise, proceed to step S615.

[0114] Step S607: The channel source device sends FlexE overhead information with the C flag set, and distributes customer services using the updated time slot table starting from the next multiframe.

[0115] In step S608, the intermediate node device of the channel receives the FlexE overhead information with the C flag set, and starts receiving and continuing to distribute customer services to the next level device using the updated time slot table from the next multiframe.

[0116] In step S609, the channel destination device receives the FlexE overhead information with the C flag set, and starts receiving and resuming customer services from the next multiframe using the updated time slot table.

[0117] Step S610: After a specific time has elapsed, the channel destination device sets the SD flag in the FlexE overhead information and sets the bit corresponding to the device position in the Switch Map.

[0118] Step S611: The intermediate node device of the channel receives the FlexE overhead information with the SD flag set, queries the time slot adjustment result of this device, and if the time slot adjustment is successful, sets the bit of the corresponding device position in the Switch Map.

[0119] In step S612, the channel source device receives the FlexE overhead information with the SD flag set, and at the same time collects the time slot adjustment results of each node device in the channel and reports them to the control system.

[0120] Step S613: Determine whether all devices in the channel have completed the time slot reduction adjustment. If yes, proceed to step S614; otherwise, proceed to step S620.

[0121] Step S614, adjustment complete;

[0122] Step S615: The channel source device sends FlexE overhead information with the CAR flag set.

[0123] In step S616, the intermediate node device of the channel receives the FlexE overhead information with the CAR flag set and forwards it to the next level node device;

[0124] Step S617: The channel destination device receives the FlexE overhead information with the CAR flag set, queries the result of sending the CA flag, and sends the FlexE overhead information with the CAA flag set. At the same time, it sets the bit of the corresponding device position in the Switch Map.

[0125] In step S618, the intermediate node device of the channel receives the FlexE overhead information with the CAA flag set, queries the results of the device receiving and sending CA flags, and if the reception and transmission of CA flags are completed simultaneously, sets the bit of the corresponding device position in the Switch Map.

[0126] In step S619, the channel source device receives the FlexE overhead information with the CAA flag set, collects the CA feedback results from each node device in the channel, reports them to the management and control system, and generates a CA timeout reason.

[0127] Step S620: Adjustment failed. Based on the reported time slot adjustment results, diagnose the fault or re-initiate the adjustment.

[0128] In another alternative embodiment, Figure 7 This is a flowchart of an optional fine-particle channel time slot reduction method according to an embodiment of the present invention, such as... Figure 7 As shown, before the source device sends the first request information to the destination device through the node device in the sliced ​​packet network, the method includes:

[0129] Step S701: Reduce service data bandwidth;

[0130] Step S702: The channel source device sets the CR flag in the Fg-Bu overhead information, starts the CA timeout protection timer, and carries the time slot information to be reduced at the same time.

[0131] In step S703, the intermediate node device of the channel receives the Fg-Bu overhead information with the CR flag set and forwards it to the next level node device;

[0132] Step S704: The destination device of the channel receives the Fg-Bu overhead information with the CR flag set, completes the configuration of the local backup time slot table, and sends out the Fg-Bu overhead information with the CA flag set.

[0133] In step S705, the intermediate node device of the channel receives the Fg-Bu overhead information with the CA tag set, forwards it to the next-level node device, and records the results of receiving and sending the CA tag at this node.

[0134] Step S706: Determine whether the channel source device receives the CA tag sent by the channel destination device within the predetermined time. If yes, proceed to step S707; otherwise, proceed to step S715.

[0135] In step S707, the channel source device sends the Fg-Bu overhead information with the C flag set, and distributes customer services using the updated time slot table starting from the next multiframe;

[0136] In step S708, the intermediate node device of the channel receives the Fg-Bu overhead information with the C flag set, and starts receiving and continuing to distribute customer services to the next level device using the updated time slot table from the next multiframe.

[0137] In step S709, the channel destination device receives the Fg-Bu overhead information with the C flag set, and starts receiving and resuming customer services from the next multiframe using the updated time slot table;

[0138] Step S710: After a specific period of time, the destination device of the channel sets the SD flag in the Fg-Bu overhead information. The number of Fg-Bus sent is related to the total number of devices in the channel. At the same time, the bit corresponding to the device position in the Fg-Bu is set.

[0139] Step S711: The intermediate node device of the channel receives the Fg-Bu overhead information with the SD flag set, queries the time slot adjustment result of this device, and if the time slot adjustment is successful, sets the bit of the corresponding device position in the Switch Map.

[0140] In step S712, the channel source device receives the Fg-Bu overhead information with the SD flag set, and at the same time collects the time slot adjustment results of each node device in the channel and reports them to the control system.

[0141] Step S713: Determine whether all devices in the channel have completed the time slot reduction adjustment. If yes, proceed to step S714; otherwise, proceed to step S720.

[0142] Step S714, adjustment complete;

[0143] Step S715, the channel source device sends the Fg-Bu overhead information with the CAR flag set;

[0144] In step S716, the intermediate node device of the channel receives the Fg-Bu overhead information with the CAR flag set and forwards it to the next level node device;

[0145] In step S717, the destination device of the channel receives the Fg-Bu overhead information with the CAR flag set, queries the result of sending the CA flag of this device, and sends the Fg-Bu overhead information with the CAA flag set. The number of Fg-Bu sent is related to the total number of devices in the channel. At the same time, the bit of the corresponding device position in the Switch Map is set.

[0146] In step S718, the intermediate node device of the channel receives the Fg-Bu overhead information with the CAA flag set, queries the results of the device receiving and sending CA flags, and if the reception and transmission of CA flags are completed simultaneously, sets the bit of the corresponding device position in the Switch Map.

[0147] In step S719, the channel source device receives the Fg-Bu overhead information with the CAA flag set, collects the CA feedback results from each node device in the channel, reports them to the control system, and generates a CA timeout reason.

[0148] Step S720: Adjustment failed. Based on the reported time slot adjustment results, diagnose the fault or re-initiate the adjustment.

[0149] In another optional embodiment, before the source device sends the first request information to the destination device through the node device in the slice packet network, the source device can receive the time slot adjustment information sent by the destination device through the node device. At this time, the preset flag is set, wherein the time slot adjustment information is used to indicate the completion status of the time slot adjustment.

[0150] In another optional embodiment, after the time slot adjustment is completed, the present invention can also transmit the time slot adjustment completion status information through the time slot adjustment message mechanism. After the time slot adjustment process is completed, the source device or destination device of the channel initiates a time slot reconfiguration completion status announcement, sets the SD flag in the first response information (e.g., FlexE overhead information or fine-grained Fg-Bu overhead information), and writes the result of the device's time slot adjustment completion to the corresponding position in the Switch Map.

[0151] Optionally, after the source device sends control information to the destination device through the node device, the method further includes: the source device receiving feedback information sent by the destination device after waiting for a preset time through the node device, wherein the completion flag in the feedback information is set, and the bit in the reserved field of the feedback information corresponding to the target device is set, the target device including the node device and the destination device; the source device sending feedback information to a preset device, wherein the feedback information is processed by the preset device to determine the device that has an anomaly in the slice packet network.

[0152] The aforementioned preset time can be a time set by the user in advance to indicate that the source device has successfully received the feedback information. The aforementioned feedback information can be information indicating that the time slot adjustment is complete. In this embodiment, the time slot adjustment is completed (Switch Done, SD) as an example, but it is not limited to this. The aforementioned completion flag bit can be a flag bit that marks the feedback information. In response to the completion flag bit changing from 0 to 1 or from 1 to 0, it indicates that feedback information has been written.

[0153] In an optional embodiment, after the source device sends control information to the destination device through the node device, the source device can first receive feedback information sent by the destination device after waiting for a preset time through the node device. At this time, the completion flag is set, and the bit in the reserved field of the feedback information corresponding to the target device is set. The target device includes the node device and the destination device. Then, the source device can send feedback information to a preset device, which processes the feedback information to determine the device that has an anomaly in the slice packet network.

[0154] This invention proposes a process for end-to-end timeslot adjustment of slice packet network channels and a mechanism for network-wide announcement of timeslot adjustment results for FlexE scenarios with standard granularity of 5Gbps and SPN channel scenarios with fine granularity of 10Mbps, respectively.

[0155] This invention uses the reserved fields of the overhead code block in the current standard to transmit time slot adjustment results, which solves the problem of time slot adjustment messages conflicting with the IEEE 802.3 standard in the existing technical solution one, and also solves the problem of its occupying channel bandwidth. In addition, the information notification mechanism adopted by this invention can accurately identify the location of the abnormal node in the event of an anomaly in end-to-end time slot adjustment, improving network maintainability and reducing maintenance costs.

[0156] This invention utilizes unused reserved fields in the FlexE and fine-grained slice Fg-Bu overhead information to transmit and process time slot reconfiguration status information and time slot reconfiguration completion status information. It allows for the acquisition of the entire network's time slot adjustment results during and after the reconfiguration process, and also identifies the location of devices experiencing time slot adjustment anomalies, assisting network administrators in quickly locating and troubleshooting network faults. In 5Gbps time slot granularity FlexE channels, reserved fields obtained from the third 66-bit code block of the FlexE overhead are used to carry the time slot reconfiguration status message. In 10Mbps time slot granularity channels, a 66-bit code block with a Flag field of 4'b0011 is used to carry the time slot reconfiguration status message. Figure 2 and Figure 3 These are the formats for the updated FlexE overhead information and the fine-grained Fg-Bu overhead information, respectively.

[0157] like Figure 2 and Figure 3 As shown, in the FlexE and fine-grained slicing technology standards, to prevent errors in the transmission of time slot adjustment information between devices, an internal timeout protection timer is started whenever the initiating end of the time slot adjustment sends a CR flag. If the initiating end of the time slot adjustment still has not received a CA flag from the destination end of the time slot adjustment when the timer reaches a preset threshold, it is determined that a time slot adjustment timeout event has occurred.

[0158] When a time slot adjustment timeout event occurs, the source device of the channel can initiate a time slot table switching response result query. Whether this query needs to be initiated can be configured via an enable switch. If the current device is configured to enable this function, the source device of the channel will set the CAR flag in its FlexE overhead information or the Fg-Bu overhead information of the fine-grained slice. After receiving the overhead information with the CAR flag set, the intermediate node device of the channel forwards it to the next node in the channel, and so on, until the CAR information is passed to the destination device of the channel.

[0159] After receiving the CAR information, the destination device in the channel queries the status of its own CA transmission and initiates a timeslot table switch to respond. It sets the CAA flag in its FlexE overhead information or the Fg-Bu overhead information of the fine-grained slice, and simultaneously writes the status of its own CA transmission to the corresponding position in the Switch Map. For the destination device in the channel, it needs to send several FlexE overhead information frames with the CAA flag set, or Fg-Bu overhead information frames of the fine-grained slice. The number of frames sent is related to the total number of devices in the channel. Specifically, in a FlexE channel, the number of FlexE overhead frames sent is equal to the total number of devices in the channel divided by 8 (rounded up); in a fine-grained channel, the number of Fg-Bu overhead frames sent is equal to the total number of devices in the channel divided by 16 (rounded up). The intermediate node devices in the channel, after receiving the overhead information with the CA flag set, query the result of receiving the CA from the preceding device and the result of sending the CA to the following device locally, perform a logical AND operation, and then write the result to the corresponding position in the Switch Map. The corresponding position of the Switch Map mentioned in this invention can be the position of each network element in the entire SPN channel, or it can be other agreed-upon methods. For example, it can be agreed that the channel source device number is 0, then it occupies bit [0] of the Switch Map; its next-level intermediate node number is 1, then it occupies bit [1] of the Switch Map; the channel destination device number is N, then it occupies bit [N] of the Switch Map.

[0160] After receiving the overhead information indicating that the CAA flag is set, the source device of the SPN channel extracts the SwitchMap[0~N] from the overhead information and sends it to the management and control system to determine the abnormal location of time slot reconfiguration. This allows the system to identify the location where the CA timeout occurred and address it accordingly, thereby eliminating network faults.

[0161] Besides querying the status after a time slot adjustment timeout event, this invention can also transmit time slot adjustment completion status information through a time slot adjustment message mechanism after the time slot adjustment is completed. After the time slot adjustment process is completed, the source or destination device of the channel initiates a time slot reconfiguration completion status announcement, sets the SD flag in the FlexE overhead information or fine-grained Fg-Bu overhead information, and writes the result of the device's time slot adjustment completion to the corresponding position in the Switch Map. The number of overhead information frames containing the time slot reconfiguration completion status sent is related to the total number of devices in the channel. In a FlexE channel, the number of FlexE overhead frames sent is equal to the total number of devices in the channel divided by 8 (rounded up); in a fine-grained channel, the number of Fg-Bu overhead frames sent is equal to the total number of devices in the channel divided by 16 (rounded up). After receiving the overhead information with the SD flag set, the intermediate node device of the channel queries the local time slot adjustment completion status and writes it to the corresponding position in the Switch Map. The corresponding location of the Switch Map mentioned in this invention can be the location of each network element in the entire SPN channel, or it can be another agreed-upon method. The destination or source device of the channel eventually receives the time slot adjustment completion status information of the entire channel, reports it to the management and control department, and learns the final result of the time slot adjustment and the location of the specific network element where the time slot adjustment failed.

[0162] Combining the aforementioned message notification mechanism, the present invention completes the time slot enlargement adjustment process in a FlexE channel with a 5Gbps time slot granularity as follows: Figure 4 As shown. The source device of the channel initiates a time slot adjustment, sets the CR flag in the FlexE overhead information, starts the CA timeout protection timer, and carries the time slot information to be increased; the intermediate node device of the channel receives the FlexE overhead information with the CR flag set, and forwards it to the next-level node device; the destination device of the channel receives the FlexE overhead information with the CR flag set, completes the configuration of the local backup time slot table, and sets the CA flag in the FlexE overhead information and sends it; the intermediate node device of the channel receives the FlexE overhead information with the CA flag set, forwards it to the previous-level node device, and records the results of receiving and sending the CA flag at this node.

[0163] If the source device receives FlexE overhead information with the CA flag set from the destination device within the predetermined time, time slot adjustment can continue. The source device sends FlexE overhead information with the C flag set and distributes customer services using the updated time slot table starting from the next multiframe. The intermediate node device receives the FlexE overhead information with the C flag set and receives and continues to distribute customer services to the next-level device using the updated time slot table starting from the next multiframe. The destination device receives the FlexE overhead information with the C flag set and receives and resumes customer services using the updated time slot table starting from the next multiframe. At this point, the entire time slot adjustment process is complete. To obtain the final result of the time slot adjustment in the channel, the destination device can initiate a time slot adjustment completion status announcement if the configuration is enabled. After a specific time interval, the destination device in the channel sets the SD flag in the FlexE overhead information and simultaneously sets the bit at the corresponding device location in the SwitchMap. The intermediate node devices in the channel receive the FlexE overhead information with the SD flag set, query the time slot adjustment result for their own devices, and if the time slot adjustment is successful, set the bit at the corresponding device location in the Switch Map. The source device in the channel receives the FlexE overhead information with the SD flag set, collects the time slot adjustment results from each node device in the channel, and reports them to management. If all devices in the current channel have successfully completed the time slot increase adjustment, then the customer's service bandwidth can be actually increased, completing the entire adjustment process. Otherwise, corresponding handling measures can be taken based on the location where the time slot adjustment failure occurred.

[0164] If the source device of the channel fails to receive the FlexE overhead information with the CA flag set from the destination device within the predetermined time, a time slot reconfiguration timeout event occurs. In addition to completing the status alarm, the source device can also trigger a time slot table switchover response query based on its configuration. The source device sends the FlexE overhead information with the CAR flag set; the intermediate node device receives the FlexE overhead information with the CAR flag set and forwards it to the next-level node device; the destination device receives the FlexE overhead information with the CAR flag set, queries the result of its own CA flag transmission, and sends the FlexE overhead information with the CAA flag set, while simultaneously setting the bit at the corresponding device position in the Switch Map; the intermediate node device receives the FlexE overhead information with the CAA flag set, queries the result of its own CA flag reception and transmission, and if both CA flag reception and transmission are completed simultaneously, sets the bit at the corresponding device position in the Switch Map; the source device receives the FlexE overhead information with the CAA flag set, collects the CA feedback results from each node device in the channel, reports it to management, and generates a CA timeout reason. Finally, the query for the time slot table switching response is completed to obtain the location of the anomaly and take corresponding measures to resolve it.

[0165] Combining the aforementioned message notification mechanism, the present invention completes the time slot reduction adjustment process in a FlexE channel with a 5Gbps time slot granularity as follows: Figure 6 As shown. The overall adjustment process is basically the same as the time slot increase process. The only difference is that in the time slot decrease adjustment process, the bandwidth of customer business data needs to be reduced before adjusting the time slots, and then the number of time slots is reduced using the same process as the time slot increase.

[0166] Based on the aforementioned message notification mechanism, the present invention completes the time slot enlargement adjustment process in a 10Mbps fine-grained channel as follows: Figure 5 As shown. The time slot increase process for the fine-grained channel is initiated by the destination device of the channel. The destination device first sends the Fg-Bu overhead information with the S flag set, initiating the time slot increase adjustment; the intermediate node device receives the Fg-Bu overhead information with the S flag set and forwards it to the next-level node device; the source device receives the Fg-Bu overhead information with the S flag set, sets the CR flag in the Fg-Bu overhead information, starts the CA timeout protection timer, and simultaneously carries the time slot information to be increased. The subsequent processing flow is completely consistent with the FlexE channel time slot increase process. If a CA timeout occurs, the channel's CA feedback status query can be initiated to determine the location of the timeout. If no CA timeout occurs, the time slot adjustment continues through the CCC flag, and after the time slot adjustment is completed, a time slot adjustment result announcement is executed within the channel.

[0167] Combining the aforementioned message notification mechanism, the present invention completes the time slot reduction adjustment process in a 10Mbps fine-grained channel as follows: Figure 7 As shown. Unlike the fine-grained channel timeslot increase, the adjustment for reducing fine-grained channel timeslots is initiated by the source device of the channel. The overall adjustment process is consistent with the timeslot reduction process of the FlexE channel.

[0168] Figure 8 This is a schematic diagram of an optional channel timeslot enlargement process according to an embodiment of the present invention, as shown below. Figure 8 As shown, assuming a FlexE channel or fine-grained slice channel consists of a source PE device, a destination PE device, and n intermediate node devices (P1 to Pn), the entire process can be divided into four stages according to time sequence. First: The spare time slot table information is announced through the S (fine-grained channel specific) / CR / CA / C tags in the overhead information, synchronizing the start of time slot adjustment. Synchronous time slot table switching begins in the next multiframe after the CCC tag is sent and received, achieving lossless time slot table switching within the channel. Second: After completing the time slot switching, the results of time slot adjustment for each node device within the channel are transmitted through the SD tag and SwitchMap information in the overhead information. If the channel time slot adjustment fails, the location of the abnormal network element can be identified, allowing network administrators to resolve the issue according to the specific situation. Third: Once all devices in the entire channel have successfully completed time slot adjustment, the bandwidth for customer services is increased. Fourth: If a CA timeout occurs, query the CA transmission and reception results through the CAR / CAA / SwitchMap information in the overhead information, determine the location of the timeout event, and respond to the fault resolution.

[0169] Figure 9 This is a schematic diagram of an optional channel time slot reduction process according to an embodiment of the present invention, as shown below. Figure 9As shown, assuming a FlexE channel or fine-grained slice channel consists of a source PE device, a destination PE device, and n intermediate node devices (P1 to Pn), the entire process can be divided into four stages according to time sequence. First, before initiating time slot reduction adjustment, customer service traffic is reduced. Second, the spare time slot table information is announced through the CR / CA / C tags in the overhead information, synchronizing the start of time slot adjustment. Synchronous time slot table switching begins in the next multiframe after the CCC tag is sent and received, achieving lossless time slot table switching within the channel. Third, after completing the time slot switching, the results of time slot adjustment for each node device within the channel are transmitted through the SD tag and SwitchMap information in the overhead information. If the channel time slot adjustment fails, the location of the abnormal network element can be identified, allowing network administrators to resolve the issue based on the specific circumstances. Fourth, if a CA timeout occurs, the CA transmission and reception results are queried through the CAR / CAA / SwitchMap information in the overhead information, the location of the timeout event is determined, and corresponding fault resolution is implemented.

[0170] Example 2

[0171] According to an embodiment of the present invention, an embodiment of a time slot adjustment method for a sliced ​​packet network is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0172] Figure 10 This is a flowchart of a time slot adjustment method for a sliced ​​packet network according to an embodiment of the present invention, as shown below. Figure 10 As shown, the method includes the following steps:

[0173] In step S1002, the node device receives the first request information sent by the source device and forwards the first request information to the destination device. The first request flag in the first request information is set, and the reserved field of the first request information carries time slot adjustment information. The time slot adjustment information is used to adjust the time slot table currently used by the node device and the destination device.

[0174] Step S1004: The node device receives the first response information sent by the destination device and forwards the first response information to the source device, wherein the first response flag in the first response information is set.

[0175] In step S1006, the node device receives the control information sent by the source device and forwards the control information to the destination device. The enable flag in the control information is set, and the control information is used to control the source device, node device and destination device to use the adjusted time slot table in the next transmission of multiframes.

[0176] Example 3

[0177] According to an embodiment of the present invention, an embodiment of a time slot adjustment method for a sliced ​​packet network is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0178] Figure 11 This is a flowchart of a time slot adjustment method for a sliced ​​packet network according to an embodiment of the present invention, as shown below. Figure 11 As shown, the method includes the following steps:

[0179] In step S1102, the destination device receives the first request information sent by the source device through the node device. The first request information contains a first request flag and a reserved field that carries time slot adjustment information. The time slot adjustment information is used to adjust the time slot table currently used by the node device and the destination device.

[0180] Step S1104: The destination device sends a first response message to the source device through the node device, wherein the first response flag in the first response message is set.

[0181] In step S1106, the destination device receives control information sent by the source device through the node device. The enable flag in the control information is set, and the control information is used to control the source device, node device and destination device to use the adjusted time slot table in the next transmission of multiframes.

[0182] Example 4

[0183] According to another aspect of the present invention, a slice packet network is also provided. Figure 12 This is a schematic diagram of a sliced ​​grouping network according to an embodiment of the present invention, as shown below. Figure 12As shown, the slice distribution network includes: a source device 1202, used to send a first request message, wherein the first request flag in the first request message is set, and the reserved field of the first request message carries time slot adjustment information, which is used to adjust the time slot table currently used by the node device and the destination device; a destination device 1204, used to send a first response message, wherein the first response flag in the first response message is set; the source device 1202 is also used to receive the first response message within a preset time period and send control information, wherein the enable flag in the control information is set, and the control information is used to control the source device, node device and destination device to use the adjusted time slot table in the next transmission of multiframes; a node device 1206 is used to forward the first request message and control information to the destination device, and forward the first response message to the source device.

[0184] Optionally, the source device includes: a first time slot scheduling module for scheduling raw data according to a time slot table; a first information insertion module for generating first request information; and a first data sending module for combining the raw data and the first request information into a first data stream and sending the first data stream to the node device.

[0185] Optionally, the destination device includes: a first data receiving module for receiving a second data stream sent by a node device, wherein the second data stream contains original data and first request information; a first information extraction module for extracting the first request information from the second data stream; a status judgment module for determining whether the time slot table currently used by the destination device has been successfully adjusted; and a first time slot recovery module for recovering the original data based on the time slot table.

[0186] Optionally, the node device includes: a second data receiving module for receiving a third data stream, wherein the third data stream contains original data and first request information; a second information extraction module for extracting the first request information from the third data stream; a second time slot recovery module for recovering the original data based on a time slot table; a second time slot scheduling module for scheduling the original data based on a time slot table; a second information insertion module for generating the first request information; and a second data sending module for combining the original data and the first request information into a second data stream and sending the second data stream to the destination device.

[0187] Optionally, Figure 13 This is an optional device applied to the SPN channel transmitter according to an embodiment of the present invention, such as... Figure 13As shown, the device includes: a time slot scheduling module 1302, which schedules customer service data according to a time slot table and starts scheduling customer service data using a new time slot table in the next multiframe after the CCC mark is issued; an overhead information insertion module 1304, which inserts FlexE overhead information or fine-grained Fg-Bu overhead information at certain intervals and in a pre-defined format; and a data transmission module 1306, which combines the customer service data scheduled by the time slot scheduling module and the overhead information data generated by the overhead information insertion module into a data stream and sends it out from the corresponding channel.

[0188] Optionally, Figure 14 This is an optional device applied to the SPN channel receiver according to an embodiment of the present invention, such as... Figure 14 As shown, the device includes: a data receiving module 1402, which receives data streams from the channel's front-end equipment, containing valid customer service data and channel overhead information; an overhead information extraction module 1404, which identifies and extracts overhead information, including information related to time slot adjustments; a time slot reconfiguration status judgment module 1406, which determines the completion status of the current device's time slot adjustment; and a time slot recovery module 1408, which, according to the time slot table configuration, restores the customer service data in the data stream to the corresponding customer, and, starting from the next multiframe received from CCC, uses the new time slot table to restore the customer service data in the data stream to the corresponding customer.

[0189] Optionally, Figure 15 This is an optional device applied to an intermediate node of an SPN channel according to an embodiment of the present invention, such as... Figure 15 As shown, in addition to the time slot scheduling module 1302, overhead information insertion module 1304, data transmission module 1306, data reception module 1402, overhead information extraction module 1404, and time slot recovery module 1408 included in both the channel transmitting and receiving devices, the device also includes a status recording module 1502. This module can record not only the completion status of time slot adjustment but also the status of the device's CA tag transmission and reception for information retrieval. The time slot cross-connect module 1504 enables data exchange at the Path layer.

[0190] Example 5

[0191] According to another aspect of the present invention, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored program, wherein, when the program is running, the device on which the computer-readable storage medium is located executes any of the above methods.

[0192] Example 6

[0193] According to another aspect of the present invention, a processor is also provided, which is used to run a program, wherein the program executes any of the methods described above during runtime.

[0194] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0195] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0196] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0197] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0198] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0199] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0200] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method for adjusting time slots of a slice packet network, characterized in that, include: The source device sends a first request message to the destination device through the node device. The first request message contains a first request flag and a reserved field that carries time slot adjustment information. The time slot adjustment information is used to adjust the time slot tables currently used by the node device and the destination device. The source device receives first response information sent by the destination device through the node device, wherein the first response flag in the first response information is set to bit; In response to the source device receiving the first response information within a preset time period, the source device sends control information to the destination device through the node device. The enable flag in the control information is set, and the control information is used to control the source device, the node device, and the destination device to use the adjusted time slot table in the next transmission of multiframes.

2. The method of claim 1, wherein, In response to the source device not receiving the first response information within a preset time period, the method further includes: The source device sends the second request information to the destination device through the node device, wherein the second request flag in the second request information is set to bit; The source device receives second response information sent by the node device and the destination device, wherein the second response flag in the second response information is set, and the reserved field of the second response information carries a target response status, the target response status being used to characterize the first state of the source device sending the first response information, and the second state of the node device sending and receiving the first response information; The source device sends the target response status to a preset device, wherein the target response status is processed by the preset device to determine the device that has an anomaly in the slice packet network.

3. The method according to claim 2, characterized in that, The second state is obtained by performing logical operations on the result of the node device receiving the first response information and the result of the node device sending the first response information. The states corresponding to different devices are stored in different positions in the reserved field.

4. The method according to claim 2, characterized in that, The number of the second response messages is related to the number of devices in the slice packet network.

5. The method according to claim 1, characterized in that, After the source device sends control information to the destination device through the node device, the method further includes: The source device receives feedback information sent by the destination device after waiting for a preset time through the node device. The completion flag in the feedback information is set, and the bit in the reserved field of the feedback information corresponding to the target device is set. The target device includes the node device and the destination device. The source device sends the feedback information to a preset device, wherein the feedback information is processed by the preset device to determine the device that has an anomaly in the slice packet network.

6. The method according to claim 1, characterized in that, The method also includes one of the following: After the source device sends control information to the destination device through the node device, it controls the increase of the data bandwidth of the slice packet network; Before the source device sends the first request information to the destination device through the node device in the slice packet network, the data bandwidth of the slice packet network is reduced. Before the source device sends the first request information to the destination device through the node device in the slice packet network, the source device receives the time slot adjustment information sent by the destination device through the node device, wherein the preset flag in the time slot adjustment information is set.

7. A method for adjusting time slots in a sliced ​​grouping network, characterized in that, include: The node device receives a first request information sent by the source device and forwards the first request information to the destination device. The first request information contains a first request flag and carries time slot adjustment information in the reserved field. The time slot adjustment information is used to adjust the time slot table currently used by the node device and the destination device. The node device receives the first response information sent by the destination device and forwards the first response information to the source device, wherein the first response flag in the first response information is set; The node device receives control information sent by the source device and forwards the control information to the destination device. The enable flag in the control information is set, and the control information is used to control the source device, the node device and the destination device to use the adjusted time slot table in the next transmission of multiframes.

8. A method for adjusting time slots in a sliced ​​packet network, characterized in that, include: The destination device receives a first request message sent by the source device through the node device. The first request message contains a first request flag and a reserved field that carries time slot adjustment information. The time slot adjustment information is used to adjust the time slot table currently used by the node device and the destination device. The destination device sends a first response information to the source device through the node device, wherein the first response flag in the first response information is set; The destination device receives control information sent by the source device through the node device. The enable flag in the control information is set. The control information is used to control the source device, the node device and the destination device to use the adjusted time slot table in the next transmission of multiframes.

9. A slice packet network system, characterized in that, include: The source device is used to send a first request information, wherein the first request flag in the first request information is set, and the reserved field of the first request information carries time slot adjustment information, which is used to adjust the time slot table currently used by the node device and the destination device. The destination device is used to send first response information, wherein the first response flag in the first response information is set; The source device is also used to receive the first response information within a preset time period and send control information, wherein the enable flag in the control information is set, and the control information is used to control the source device, the node device and the destination device to use the adjusted time slot table in the next transmission of multiframes; The node device is used to forward the first request information and the control information to the destination device, and to forward the first response information to the source device.

10. The slice packet network system according to claim 9, characterized in that, The source-end device includes: The first time slot scheduling module is used to schedule raw data according to the time slot table; The first information insertion module is used to generate the first request information; The first data sending module is used to combine the original data and the first request information into a first data stream, and send the first data stream to the node device.

11. The slice packet network system according to claim 9, characterized in that, The destination device includes: The first data receiving module is used to receive the second data stream sent by the node device, wherein the second data stream contains the original data and the first request information; The first information extraction module is used to extract the first request information from the second data stream; The status determination module is used to determine whether the time slot table currently used by the destination device has been successfully adjusted; The first time slot recovery module is used to recover the original data based on the time slot table.

12. The slice packet network system according to claim 9, characterized in that, The node device includes: The second data receiving module is used to receive the third data stream, wherein the third data stream contains the original data and the first request information; The second information extraction module is used to extract the first request information from the third data stream; The second time slot recovery module is used to recover the original data based on the time slot table; The second time slot scheduling module is used to schedule the original data based on the time slot table; The second information insertion module is used to generate the first request information; The second data sending module is used to combine the original data and the first request information into a second data stream, and send the second data stream to the destination device.

13. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein, when the program is executed, it controls the device on which the computer-readable storage medium is located to perform the method according to any one of claims 1 to 8.

14. A processor, characterized in that, The processor is used to run a program, wherein the program, when running, performs the method according to any one of claims 1 to 8.

Images