Network device, method, apparatus and storage medium for bandwidth adjustment

Abstract

Example embodiments of the present disclosure relate to a network device, method, apparatus, and storage medium for bandwidth adjustment. In an aspect, a first network device receives, from a second network device, adjustment control information for a bandwidth adjustment procedure between the second network device and the first network device, the adjustment control information associated with a fine-granularity time slot (fgTS) in an optical payload unit (OPU) to be adjusted. The first network device also updates, based on receiving the adjustment control information, an expected multiplex structure identifier (ExMSI) associated with the fgTS.

Description

Technical Field

[0001] Various example embodiments relate to the field of communications, and more specifically to an apparatus, method, and computer-readable storage medium for bandwidth adjustment. Background Technology

[0002] In modern communication networks, fiber optic technology has become mainstream, providing high-speed, high-bandwidth data transmission capabilities. An Optical Transport Network (OTN) is a transmission network based on fiber optic technology used to achieve reliable and efficient fiber optic communication.

[0003] Such optical communication networks operate according to standards such as those issued by the International Telecommunication Union Standardization Sector (ITU-T). Examples of such standards include so-called ITU-T standards. Summary of the Invention

[0004] In general, exemplary embodiments of this disclosure relate to a network device, method, apparatus, and storage medium for bandwidth adjustment.

[0005] In a first aspect of this disclosure, a first network device is provided. The first network device includes: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the first network device to at least: receive adjustment control information from a second network device for a bandwidth adjustment process between the second network device and the first network device, wherein the adjustment control information is associated with a fine-grained time slot (fgTS) to be adjusted in an OPU; and update the expected multiplexing structure identifier (ExMSI) associated with the fgTS based on the received adjustment control information.

[0006] In a second aspect of this disclosure, a method is provided. The method includes: receiving from a second network device adjustment control information for a bandwidth adjustment process between the second network device and a first network device, wherein the adjustment control information is associated with an fgTS to be adjusted in an OPU; and updating the ExMSI associated with the fgTS based on the received adjustment control information.

[0007] In a third aspect of this disclosure, an apparatus is provided. The apparatus includes: components for receiving adjustment control information from a second network device for a bandwidth adjustment process between the second network device and a first network device, wherein the adjustment control information is associated with an fgTS to be adjusted in an OPU; and components for updating an ExMSI associated with the fgTS based on the received adjustment control information.

[0008] In a fourth aspect of this disclosure, a computer-readable medium is provided, including program instructions that, when executed by a device, cause the device to perform at least the method according to the second aspect.

[0009] In a fifth aspect of this disclosure, a computer program is provided. The computer program includes instructions. When executed by a device, the instructions cause the device to perform at least the method of the second aspect.

[0010] In a sixth aspect of this disclosure, a first network device is provided. The first network device includes: a receiving circuitry configured to receive adjustment control information from a second network device for a bandwidth adjustment process between the second network device and the first network device, wherein the adjustment control information is associated with an fgTS to be adjusted in an OPU; and an updating circuitry configured to update the ExMSI associated with the fgTS based on the received adjustment control information.

[0011] It should be understood that the description in the Summary of the Invention section is not intended to limit the key or essential features of the embodiments of this disclosure, nor is it intended to restrict the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0012] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings, without exceeding the scope of protection claimed by this application.

[0013] Figure 1A A block diagram of an example communication system in which embodiments of the present disclosure may be implemented is shown;

[0014] Figure 1B It shows according to Figure 1A The diagram shows a schematic of the network structure of the example communication system.

[0015] Figure 2 A flowchart illustrating an example of a bandwidth adjustment process according to some embodiments is shown;

[0016] Figure 3 A schematic diagram illustrating the adjustment of control information according to some embodiments is shown;

[0017] Figure 4 A flowchart illustrating an example of a bandwidth adjustment process according to some embodiments is shown;

[0018] Figure 5 A flowchart illustrating an example of a bandwidth adjustment process according to some embodiments is shown;

[0019] Figure 6 A schematic diagram of a process executed by a first network device according to some embodiments of the present disclosure is shown;

[0020] Figure 7 A simplified block diagram of an electronic device suitable for implementing embodiments of the present disclosure is shown; and

[0021] Figure 8 A schematic diagram of a computer-readable medium suitable for implementing embodiments of the present disclosure is shown.

[0022] In all the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0023] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not impose any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various ways other than those described below.

[0024] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0025] It should be understood that although the terms “first” and “second” may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0026] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” used herein also include the plural forms. It should also be understood that the terms “comprising,” “having,” “owning,” “include,” and / or “including”, when used herein, specify the presence of the described features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. As used herein, phrases such as “at least one of the following elements: ” and “<at least one of a list of more than two elements>” and similar wording, where a list of two or more elements is connected by “and” or “or,” refer to at least any one element, or at least any two or more elements, or at least all elements.

[0027] As used in this application, the term "circuit system" may refer to one or more of the following:

[0028] (a) Hardware circuit implementation only (such as implementation only in analog and / or digital circuits), and (b) a combination of hardware circuits and software, such as (if applicable):

[0029] (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and

[0030] (ii) Any part of (multiple) hardware processors with software (including digital signal processors), software and (multiple) memories that work together to enable a device such as a mobile phone or server to perform various functions) and (c) (multiple) hardware circuits and / or processors, such as (multiple) microprocessors or a portion thereof, that require software (such as firmware) to run, but may be absent if the software is not required to run.

[0031] This definition of "circuit system" applies to all uses of the term in this application, including in any claim. As a further example, the term "circuit" as used in this application also encompasses implementations of hardware circuitry or processors (or processors in general) or a portion thereof and their accompanying software and / or firmware. For example, if applicable to a particular claim element, the term "circuit system" also encompasses baseband integrated circuits or processor integrated circuits in mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0032] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, wherein the list of two or more elements is connected by “and” or “or”, indicates at least any one element, or at least any two or more elements, or at least all elements.

[0033] The following embodiments are presented as examples only. Although this specification may refer to "an," "one," or "some" embodiments and / or examples in several places in the text, this does not necessarily mean that each reference refers to the same(s) embodiments(s) or examples(s), or that a particular feature applies only to a single embodiment and / or example. Individual features of different embodiments and / or examples may also be combined to provide other embodiments and / or examples.

[0034] Optical communication network (OTN) technology offers advantages such as long distance, large capacity, hard isolation, low latency jitter, and low power consumption per bit, making it suitable for long-distance trunk line scenarios. However, in industrial dedicated lines and dedicated network scenarios, small-particle services with bandwidth less than 1Gb / s remain the mainstream, such as power relay protection and railway train control.

[0035] OTN supports a minimum service granularity of 1.25Gb / s, which leads to bandwidth waste when carrying small-granularity services and cannot meet the needs of SDH network services migrating to OTN networks. Therefore, in subsequent technological developments, the industry has provided a small-granularity OTN (fgOTN) technology that offers isolated, secure, and reliable transmission capabilities to smoothly handle current SDH network services. fgOTN is a small-granularity hard pipe technology based on the OTN standard system. fgOTN is primarily positioned as a high-quality service carrier below 1Gb / s and can be widely used in operator-government-enterprise dedicated lines, as well as dedicated networks in industries such as power and transportation.

[0036] fgOTN defines a service-oriented fine-grained flexible optical data unit (fgODUflex) container and provides complete layer network functions, including service adaptation, overhead management and monitoring, cross-scheduling, multiplexing, lossless adjustment, and protection functions.

[0037] Figure 1A A block diagram of an example communication system 100A, in which embodiments of the present disclosure may be implemented, is shown.

[0038] In the communication system 100A, the first network device 101 and the second network device 102 can communicate and interact in the fgOTN 103 to realize service adaptation function, overhead management and monitoring function, cross scheduling function, multiplexing function, lossless adjustment function, protection function, etc.

[0039] Figure 1B It shows according to Figure 1A The diagram shows a communication network structure 100B of the example communication system 100A.

[0040] The communication system 100B may include fgOTN 107. fgOTN 107 defines a new fine-grained ODU layer network. fgOTN 107 carries multiple services with a granularity of less than 1G on the OTN network to provide isolated, secure, reliable, and time-division multiplexing (TDM) based transmission capabilities.

[0041] In the communication network structure 100B, user A's remote local area network LAN 104, user B's remote LAN 105, and user C's remote LAN 106 can be connected to fgOTN 107, which supports TDM sub1G granularity and has fgOTN layer network functionality, through corresponding fgOTN nodes 108 and 109. Then, such small-granularity services can be connected to corresponding user servers A 112, B 113, and C 114 through corresponding fgOTN nodes 110 and 111. fgOTN nodes 108 and 109 can respectively correspond to... Figure 1A The second network device 102 and the first network device 101 are mentioned. Alternatively, fgOTN node 110 and fgOTN node 111 can also correspond to... Figure 1A The second network device 102 and the first network device 101. Figure 1B The OTN network 107 that supports TDM sub1G granularity and has fgOTN layer network functionality can correspond to Figure 1A fgOTN 103 in the middle.

[0042] In some examples, sub1G services can be packet services or fixed bit rate (CBR) services.

[0043] Figure 1B An example of a simplified system architecture is depicted, showing only some elements and functional entities, which are logical units whose implementations may differ from those shown. Figure 1B The connections shown are logical connections; the actual physical connections may differ. It will be apparent to those skilled in the art that the system typically includes, in addition to... Figure 1B Other functions and structures besides those shown.

[0044] Understandable Figure 1B The number of user remote LANs, fgOTN nodes, and user servers shown is not limited to the examples above.

[0045] exist Figure 1A In fgOTN 103, the customer signal is mapped to the fgODUflex payload area. The generated adjustment control information is inserted into the fgOPUflex overhead area, generating fgODUflex path connection monitoring information, which is inserted into the fgODUflexPM (path monitoring or channel monitoring) overhead. Additionally, fgODUflex serial connection monitoring information is generated and inserted into the fgODUflex TCM (serial connection monitoring) segment overhead. The generated fgODUflex signal is then mapped to one or more fgTS of the server OPU. This adjustment control information can be adjustment control overhead (RCOH). Through this processing, the adjustment control information is associated with one or more fgTS mapped to the server OPU.

[0046] exist Figure 1A In the fgOTN 103, there is a multiplexing structure indication loss defect (dMSIM). When dMSIM occurs, it affects the lossless bandwidth adjustment process of the first network device 101 and the second network device 102 (e.g., increasing bandwidth from M*10 Mbit / s to (M+N)*10 Mbit / s or decreasing bandwidth from (M+N)*10 Mbit / s to M*10 Mbit / s), causing the lossless bandwidth adjustment process to be interrupted and affecting the communication process. Furthermore, after the dMSIM problem occurs, how to adjust parameters of, for example, the first network device 101 and the second network device 102 to avoid affecting subsequent lossless bandwidth adjustment processes remains a challenge.

[0047] Figure 2 A flowchart illustrating an example of a bandwidth adjustment process 200 according to some embodiments of the present disclosure is shown. For purposes of description, reference will be made to... Figure 1A Describe process 200. Process 200 may involve, for example, Figure 1A The first network device 101 and the second network device 102 are shown. The first network device 101 can be an ODUkP / fgODUflex destination, and the second network device 102 can be a corresponding ODUkP / fgODUflex source.

[0048] exist Figure 2 In the above, at point 210, the first network device 201 receives adjustment control information from the second network device 202 for the bandwidth adjustment process between the second network device 202 and the first network device 201. This adjustment control information is associated with the fgTS in the OPU that will be adjusted.

[0049] Figure 3A schematic diagram illustrating adjustment control information 300 according to some embodiments is shown. This adjustment control information 300 may correspond to the multiplexing overhead (fgTSMxOH) of fgTS(fgTS#k) and fgTS(fgTS#k+1). This adjustment control information 300 may also be the adjustment control overhead (fgLCR RCOH) of fgODUflex link connection adjustment.

[0050] The fgTSMxOH corresponding to fgTS (fgTS#k) in the adjustment control information 300 includes: RP (1 bit), TSCC (1 bit), CTRL (2 bits), and TSGS (2 bits), as well as the multiplexing structure indicator MSI (10 bits, used to indicate the time slot distribution and occupancy of the OPU, used to place the tributary port number TPID, indicating the TPID corresponding to the fgODUflex signal currently carried by fgTS#k). Table 1 below shows the values, commands, and tags of several fields in the adjustment control information.

[0051] Table 1

[0052]

[0053]

[0054] In some embodiments, the adjustment control information received by the first network device 201 may be fgLCR RCOH. The fgLCR RCOH includes: RP=1 (indicating that the adjustment protocol is enabled), a CTRL field (CTRL=01 or CTRL=10) indicating whether the fgTS will be added or removed, an MSI field indicating the tributary port identifier (TPID) involved in the addition or removal of the fgTS, and TSCC=0 (indicating that the connection status has not been confirmed).

[0055] Alternatively, the adjustment control information received by the first network device 201 may be fgLCR RCOH. The fgLCR RCOH includes: RP=1 (indicating that the adjustment protocol is enabled), a CTRL field (CTRL=01 or CTRL=10) indicating whether the fgTS will be added or removed, an MSI field indicating the tributary port identifier (TPID) involved in the addition or removal of the fgTS, and TSCC=1 (indicating that the connection status has been confirmed).

[0056] Now back Figure 2At 220, the first network device 201 updates the ExMSI associated with fgTS based on the received adjustment control information. In this way, during bandwidth adjustment (e.g., lossless bandwidth adjustment), when, for example, dMSIM occurs, by modifying the ExMSI to eliminate the mismatch between AcMSI and ExMSI, it is possible to reduce interruptions in the bandwidth adjustment process and prevent service loss due to dMSIM.

[0057] In one embodiment, the bandwidth adjustment process can be a bandwidth increase process. The first network device 201 can update ExMSI after receiving adjustment control information including CTRL=01, RP=1 and TSCC=0, or CTRL=01, RP=1 and TSCC=1.

[0058] Specifically, the first network device 201 first extracts the MSI value from the adjustment control information, and then determines the AcMSI through methods such as Cyclic Redundancy Check (CRC) or X-frame filtering. For CRC, if the CRC calculation is correct, the first network device 201 uses the received MSI value as the AcMSI. For X-frame filtering, if X consecutive frames receive the same MSI value, the first network device 201 uses the received MSI value as the AcMSI. The value of X can be 3.

[0059] Since the bandwidth adjustment process is a bandwidth increase process (CTRL=01), and assuming that the first network device 201 confirms that AcMSI is the received MSI (i.e., the TxMSI sent by the second network device 202) through either of the two verification methods, the value of ExMSI is all 1 (the value of all bits of TPID is 1), so the first network device 201 updates the value of ExMSI to AcMSI.

[0060] In another embodiment, the bandwidth adjustment process can be a bandwidth reduction process. The first network device 201 can update ExMSI after receiving adjustment control information including CTRL=10, RP=1 and TSCC=0, or CTRL=10, RP=1 and TSCC=1.

[0061] Since the bandwidth adjustment process is a bandwidth reduction process (CTRL=10), the first network device 201 updates the value of ExMSI to all 1s (the value of all bits of TPID is 1).

[0062] In some embodiments, if the bandwidth adjustment process fails or an instruction is received to enable the overhead of the adjustment protocol, the first network device 201 may perform a fallback process.

[0063] In some embodiments, the first network device 201 may perform the fallback procedure based on various conditions. For example, such conditions may include the first network device 201 issuing an fgLCR RCOH indicating rejection (TSGS = REJECT) via the TSGS field. Alternatively, such conditions may include the first network device 201 receiving an fgLCR RCOH indicating rejection (TSGS = REJECT) via the TSGS field from another network device (fgOTN node). Alternatively, such conditions may include the first network device 201 receiving an fgLCR RCOH indicating to enable the tuning protocol (RP = 0) via the RP field.

[0064] In some embodiments, during the bandwidth adjustment process, the first network device 201 de-enables the detection of dMSIM[p] of the fgODUflex tributary port p at the next adjustment multiframe boundary after receiving the adjustment control information.

[0065] In some embodiments, during bandwidth increase, the first network device 201 may, after receiving adjustment control information including CTRL=01, RP=1, and TSCC=0, or CTRL=01, RP=1, and TSCC=1, verify the MSI / TPID field carried in the adjustment control information for the fgODUflex tributary port p. If the verification is successful, the value of the MSI / TPID is confirmed as AcMSI. If the value of AcMSI does not match the ExMSI, at the boundary of the next adjustment multiframe after receiving the adjustment control information, the detection of dMSIM[p] for the fgODUflex tributary port p is deactivated.

[0066] In some embodiments, CRC is used to verify the received MSI[p] / TPID[p] of the fgODUflex tributary port p. During the bandwidth adjustment process, at the next adjustment multiframe boundary after receiving the RP field indicating to enable the adjustment protocol fgLCR RCOH, the detection of dMSIM[p] of the fgODUflex tributary port p is enabled.

[0067] In one example, MSI[p] / TPID[p] is protected by a CRC such as CRC-6. During the bandwidth adjustment process, at the boundary of the next adjustment multiframe after receiving the fgLCR RCOH indicating to enable the adjustment protocol (RP=0), the detection of dMSIM[p] for the fgODUflex tributary port p is enabled.

[0068] In some alternative embodiments, CRC is not used to verify the received MSI[p] / TPID[p] of fgODUflex tributary port p. During the bandwidth adjustment process, at the Nth adjustment multiframe boundary after receiving the RP field indication to enable the adjustment protocol fgLCR RCOH, the detection of dMSIM[p] of fgODUflex tributary port p is enabled, and the value of N is greater than 1.

[0069] In one example, MSI[p] / TPID[p] is not protected by CRC, such as CRC-6. During the bandwidth adjustment process, at the Nth adjustment multiframe boundary after receiving the fgLCR RCOH indicating to enable the adjustment protocol (RP=0), the detection of dMSIM[p] for the fgODUflex tributary port p is enabled, and the value of N is greater than 1 (e.g., the value of N can be equal to 3). The received MSI values ​​are the same across these N adjustment multiframes.

[0070] In this way, during bandwidth adjustment (e.g., lossless bandwidth adjustment), dMSIM is enabled and activated precisely at specific times, so that dMSIM is suppressed only during specific time periods in lossless bandwidth adjustment and can be restored during those specific time periods.

[0071] Figure 4 A flowchart illustrating an example of a bandwidth adjustment process 400 according to some embodiments of the present disclosure is shown. For purposes of description, reference will be made to... Figure 1A Describe process 400. Process 400 may involve, for example, Figure 1A The first network device 101 and the second network device 102 are shown. The ODUkP / fgODUflex destination 401 can be the first network device 101, and the ODUkP / fgODUflex source 402 can be the second network device 102.

[0072] Process 400 illustrates a lossless bandwidth increase adjustment process (e.g., bandwidth increases from M*10 Mbit / s to (M+N)*10 Mbit / s).

[0073] At 410, the ODUkP / fgODUflex source 402 enables [RP=1] and starts a timeout timer. It then sends [RP=1, TSCC=0, CTRL=ADD, TPID=#a] signals to the ODUkP / fgODUflex destination 401 via the fgLCR overhead of the fgTS#5 and fgTS#9 to be added, requesting the ODUkP / fgODUflex destination 401 to reserve the corresponding bandwidth resources. At 420, when all the fgTSs to be added (fgTS#5 and fgTS#9) have sent [CTRL=ADD, TPID=#a] signals, the ODUkP / fgODUflex source 402 will send [TSCC=1] signals on all the fgTSs (fgTS#5 and fgTS#9) to be added to the ODUkP / fgODUflex destination 401.

[0074] In some embodiments, due to the bandwidth increase process, all bits of the TPID field corresponding to fgTS#5 and fgTS#9 for the ODUkP / fgODUflex sink 401 may be 1 (TPID = all 1s). In this case, ExMSI is not equal to the MSI value corresponding to TPID = #a (assuming that the MSI value has been successfully verified by CRC or X-frame filtering). Therefore, ExMSI and AcMSI corresponding to fgTS#5 and fgTS#9 are not equal.

[0075] In some embodiments, at 410, when the ODUkP / fgODUflex receiver 401 receives the adjustment control information [RP=1, TSCC=0][CTRL=ADD, TPID=#a] corresponding to fgTS#5, the ODUkP / fgODUflex receiver 401 updates the ExMSI corresponding to fgTS#5, modifying the ExMSI corresponding to fgTS#5 to the AcMSI corresponding to fgTS#5. Then, when the ODUkP / fgODUflex receiver 401 receives the adjustment control information [RP=1, TSCC=0][CTRL=ADD, TPID=#a] corresponding to fgTS#9, the ODUkP / fgODUflex receiver 401 updates the ExMSI corresponding to fgTS#9, modifying the ExMSI corresponding to fgTS#9 to the AcMSI corresponding to fgTS#9.

[0076] Alternatively, at 420, when the ODUkP / fgODUflex receiver 401 receives the [TSCC=1] adjustment control information, the ODUkP / fgODUflex receiver 401 updates the ExMSI corresponding to fgTS#5, modifying the ExMSI corresponding to fgTS#5 to the AcMSI corresponding to fgTS#5, and the ODUkP / fgODUflex receiver 401 updates the ExMSI corresponding to fgTS#9, modifying the ExMSI corresponding to fgTS#9 to the AcMSI corresponding to fgTS#9.

[0077] Back Figure 4 During the intermediate process between 420 and 430, the ODUkP / fgODUflex source end 402 and the ODUkP / fgODUflex destination end 401 complete the fgODUflex link connection adjustment (fgLCR) and fgODUflex bandwidth adjustment (fgBWR).

[0078] At 430, the ODUkP / fgODUflex source 402 sends [RP=0, TSCC=0][CTRL=IDLE, TPID=#a] associated with fgTS#5 and fgTS#9 to the ODUkP / fgODUflex sink 401 and exits the lossless bandwidth adjustment process.

[0079] If the fgLCR operation fails in one of the multiplexed segment link connections during processes 410-430, subsequent fgLCR operations will cease.

[0080] In some embodiments, the ODUkP / fgODUflex receiver 401 can issue [TSGS=REJECT]. The ODUkP / fgODUflex receiver 401 can, for example, roll back the ExMSI values ​​for fgTS#5 and fgTS#9 to the values ​​before receiving the [RP=1, TSCC=0][CTRL=ADD, TPID=#a] signal (TPID=all 1s).

[0081] In some other embodiments, after receiving [TSGS=REJECT] from other fgOTN nodes, the ODUkP / fgODUflex destination 401 can, for example, roll back the ExMSI values ​​for fgTS#5 and fgTS#9 to the values ​​before receiving the [RP=1, TSCC=0][CTRL=ADD, TPID=#a] signal (TPID=all 1s).

[0082] In some other embodiments, when the timer in the ODUkP / fgODUflex source 402 times out, the ODUkP / fgODUflex source 402 sends [RP=0, TSCC=0] and exits the resizing process. Upon receiving [RP=0, TSCC=0], the ODUkP / fgODUflex sink 401 can roll back the ExMSI values ​​for, for example, fgTS#5 and fgTS#9 to the values ​​before receiving the [RP=1, TSCC=0][CTRL=ADD, TPID=#a] signal (TPID=all 1s).

[0083] Implementations regarding enabling or disabling dMSIM will continue to be combined. Figure 4 Describe it.

[0084] In some embodiments, at 410, when the ODUkP / fgODUflex sink 401 receives the [RP=1, TSCC=0][CTRL=ADD, TPID=#a] signal, it de-enables the detection of dMSIM[p] (corresponding to fgTS#5 and fgTS#9) of the fgODUflex tributary port p at the next adjustment multiframe boundary.

[0085] In some embodiments, CRC is used to verify the received MSI[p] (corresponding to fgTS#5 and fgTS#9) of the fgODUflex tributary port p. When the ODUkP / fgODUflex sink 401 receives [RP=0, TSCC=0] sent due to the timer timeout of the ODUkP / fgODUflex source 402, or [RP=0, TSCC=0][CTRL=IDLE, TPID=#a] at 430, it enables the detection of dMSIM[p] of the fgODUflex tributary port p at the next adjustment multiframe boundary.

[0086] Alternatively, CRC is not used to verify the received MSI[p] of the fgODUflex tributary port p (corresponding to fgTS#5 and fgTS#9). When the ODUkP / fgODUflex sink 401 receives [RP=0, TSCC=0] sent due to a timeout at the ODUkP / fgODUflex source 402, or [RP=0, TSCC=0][CTRL=IDLE, TPID=#a] at 430, it enables the detection of dMSIM[p] of the fgODUflex tributary port p at the immediately following Nth adjustment multiframe boundary. The AcMSI values ​​within these N adjustment multiframes are consecutive, and N is greater than 1.

[0087] Figure 5A flowchart illustrating an example of a bandwidth adjustment process 500 according to some embodiments of the present disclosure is shown. For purposes of description, reference will be made to... Figure 1A Describe process 500. Process 500 may involve, for example, Figure 1A The first network device 101 and the second network device 102 are shown. The ODUkP / fgODUflex destination 501 can be the first network device 101, and the ODUkP / fgODUflex source 502 can be the second network device 102.

[0088] Process 500 illustrates a lossless bandwidth reduction adjustment process (e.g., bandwidth is reduced from (M+N)*10 Mbit / s to M*10 Mbit / s).

[0089] At point 510, the ODUkP / fgODUflex source 502 enables [RP=1] and starts a timeout timer. It then sends [RP=1, TSCC=0][CTRL=REMOVE, TPID=#a] signals to the ODUkP / fgODUflex sink 501 via the fgLCR overhead of the fgTS#5 and fgTS#9 to be deleted, requesting the ODUkP / fgODUflex sink 501 to mark the corresponding bandwidth resources for future deletion. At point 520, when all fgTSs to be deleted (fgTS#5 and fgTS#9) have sent [CTRL=REMOVE, TPID=#a] signals, the ODUkP / fgODUflex source 502 will send [TSCC=1] signals on all fgTSs to be deleted (fgTS#5 and fgTS#9).

[0090] In some embodiments, at 410, when the ODUkP / fgODUflex receiver 501 receives the adjustment control information [RP=1, TSCC=0][CTRL=REMOVE, TPID=#a] corresponding to fgTS#5, the ODUkP / fgODUflex receiver 501 updates the ExMSI corresponding to fgTS#5, modifying the ExMSI corresponding to fgTS#5 to all 1s (TPID=all 1s). Then, when the ODUkP / fgODUflex receiver 501 receives the adjustment control information [RP=1, TSCC=0][CTRL=REMOVE, TPID=#a] corresponding to fgTS#9, the ODUkP / fgODUflex receiver 501 updates the ExMSI corresponding to fgTS#9, modifying the ExMSI corresponding to fgTS#9 to all 1s (TPID=all 1s).

[0091] Alternatively, at 520, when the ODUkP / fgODUflex receiver 501 receives the [TSCC=1] adjustment control information, the ODUkP / fgODUflex receiver 501 modifies the ExMSI corresponding to fgTS#5 to all 1s (TPID=all 1s) and the ODUkP / fgODUflex receiver 501 modifies the ExMSI corresponding to fgTS#5 to all 1s (TPID=all 1s).

[0092] Back Figure 5 During the intermediate process between 520 and 530, the ODUkP / fgODUflex source end 502 and the ODUkP / fgODUflex destination end 501 complete fgLCR and fgBWR.

[0093] At 530, the ODUkP / fgODUflex source 502 sends [RP=0, TSCC=0][CTRL=IDLE, TPID=all 1] associated with fgTS#5 and fgTS#9 to the ODUkP / fgODUflex sink 501 and exits the lossless bandwidth adjustment process.

[0094] If the fgLCR operation fails in one of the multiplexed segment link connections during procedures 510-530, subsequent fgLCR operations will cease.

[0095] In some embodiments, the ODUkP / fgODUflex receiver 501 can issue [TSGS=REJECT]. The ODUkP / fgODUflex receiver 501 can, for example, roll back the ExMSI values ​​for fgTS#5 and fgTS#9 to the values ​​before receiving the [RP=1, TSCC=0][CTRL=REMOVE, TPID=#a] signal.

[0096] In some other embodiments, after receiving [TSGS=REJECT] from other fgOTN nodes, the ODUkP / fgODUflex destination 501 can, for example, roll back the ExMSI values ​​for fgTS#5 and fgTS#9 to the values ​​before receiving the [RP=1, TSCC=0][CTRL=REMOVE, TPID=#a] signal.

[0097] In some other embodiments, when the timer in the ODUkP / fgODUflex source 502 times out, the ODUkP / fgODUflex source 502 sends [RP=0, TSCC=0] and exits the resizing process. Upon receiving [RP=0, TSCC=0], the ODUkP / fgODUflex sink 501 can roll back, for example, the ExMSI values ​​for fgTS#5 and fgTS#9 to the values ​​before receiving the [RP=1, TSCC=0][CTRL=REMOVE, TPID=#a] signal.

[0098] Implementations regarding enabling or disabling dMSIM will continue to be combined. Figure 5 Describe it.

[0099] In some embodiments, at 510, when the ODUkP / fgODUflex sink 501 receives the [RP=1, TSCC=0][CTRL=REMOVE, TPID=#a] signal, it de-enables the detection of dMSIM[p] (corresponding to fgTS#5 and fgTS#9) of the fgODUflex tributary port p at the next adjustment multiframe boundary.

[0100] In some embodiments, CRC is used to verify the received MSI[p] (corresponding to fgTS#5 and fgTS#9) of the fgODUflex tributary port p. When the ODUkP / fgODUflex sink 501 receives [RP=0, TSCC=0] sent due to the timer timeout of the ODUkP / fgODUflex source 502, or [RP=0, TSCC=0][CTRL=IDLE, TPID=all 1] at 530, it enables the detection of dMSIM[p] of the fgODUflex tributary port p at the next adjustment multiframe boundary.

[0101] Alternatively, CRC is not used to verify the received MSI[p] of the fgODUflex tributary port p (corresponding to fgTS#5 and fgTS#9). When the ODUkP / fgODUflex sink 501 receives [RP=0, TSCC=0] sent due to a timeout at the ODUkP / fgODUflex source 502, or [RP=0, TSCC=0][CTRL=IDLE, TPID=all 1] at 530, it enables the detection of dMSIM[p] of the fgODUflex tributary port p at the boundary of the immediately following Nth adjustment multiframe. The AcMSI values ​​within these N adjustment multiframes are consecutive, and N is greater than 1.

[0102] In this way, the mismatch between MSI / TPID values ​​between the ODUkP / fgODUflex sink and the ODUkP / fgODUflex source ends is eliminated during the lossless bandwidth adjustment process, thus avoiding service loss and improving communication performance.

[0103] Figure 6 A schematic diagram of a process executed by a first network device according to some embodiments of the present disclosure is shown. Figure 1A The first network device 101 shown can correspond to Figure 4 and Figure 5 The ODUkP / fgODUflex host terminal 401 and the ODUkP / fgODUflex host terminal 501 are mentioned.

[0104] In block 610, the first network device receives adjustment control information from the second network device for a bandwidth adjustment process between the second network device and the first network device, wherein the adjustment control information is associated with a fine-grained time slot (fgTS) to be adjusted in the optical payload unit (OPU).

[0105] In box 620, the first network device updates the ExMSI associated with fgTS based on the received adjustment control information.

[0106] According to some embodiments, the adjustment control information includes the fgLCR RCOH of the fgODUflex link connection adjustment, wherein the fgLCR RCOH includes at least the RP field, CTRL field, MSI field, and TSCC field.

[0107] According to some embodiments, the RP field indicates that the tuning protocol is enabled, the CTRL field indicates whether the fgTS will be added or removed, the MSI field indicates the tributary port identifier (TPID) involved in the addition or removal of the fgTS, and the TSCC field indicates that the connection status has not been acknowledged.

[0108] According to some embodiments, the RP field indicates that the tuning protocol is enabled, the CTRL field indicates whether the fgTS will be added or removed, the MSI field indicates the TPID involved in the addition or removal of the fgTS, and the TSCC field indicates that the connection status has been confirmed.

[0109] According to some embodiments, the bandwidth adjustment process includes a bandwidth increase process. The first network device updates the ExMSI by updating the ExMSI to the AcMSI.

[0110] According to some embodiments, the bandwidth adjustment process includes a bandwidth reduction process. The first network device updates the ExMSI by updating the ExMSI to all 1s.

[0111] According to some embodiments, the first network device also performs a rollback process based on the failure of the bandwidth adjustment process, and updates the ExMSI to the value before receiving the adjustment control information based on the execution of the rollback process.

[0112] According to some embodiments, the first network device performs the fallback process based on: issuing an fgLCR RCOH indicating rejection via the TSGS field, receiving an fgLCR RCOH indicating rejection via the TSGS field, or receiving an fgLCR RCOH indicating to enable the adjustment protocol via the RP field.

[0113] According to some embodiments, the first network device also enables the detection of dMSIM[p] of the fgODUflex tributary port p at the boundary of the next adjustment multiframe after receiving the adjustment control information during the bandwidth adjustment process.

[0114] According to some embodiments, CRC is used to verify the received MSI[p] of fgODUflex tributary port p. The first network device also enables the detection of dMSIM[p] of fgODUflex tributary port p at the next adjustment multiframe boundary after receiving the RP field indication to enable the adjustment protocol fgLCR RCOH during the bandwidth adjustment process.

[0115] According to some embodiments, CRC is not used to verify the received MSI[p] of fgODUflex tributary port p. The first network device also enables the detection of dMSIM[p] of fgODUflex tributary port p at the Nth adjustment multiframe boundary after receiving the RP field indication to enable the adjustment protocol fgLCR RCOH during the bandwidth adjustment process, and N is greater than 1.

[0116] According to some embodiments, the first network device includes an optical data unit k-path (ODUkP) / fgODUflex sink, the second network device includes an optical data unit k-path (ODUkP) / fgODUflex source, the bandwidth adjustment process includes a lossless bandwidth adjustment process of fgODUflex, or the foregoing can be combined arbitrarily.

[0117] In some example embodiments, the apparatus capable of performing method 600 (e.g., Figure 1A The first network device 101, and Figure 4 and Figure 5 The ODUkP / fgODUflex terminal 401 and ODUkP / fgODUflex terminal 501 in the method 600 may include components for performing the various steps of the method. These components may be implemented in any suitable form. For example, they may be implemented in a circuit or software module.

[0118] According to some embodiments, the apparatus includes components for receiving adjustment control information from a second network device for a bandwidth adjustment process between the second network device and a first network device, the adjustment control information being associated with an fgTS to be adjusted in an OPU. The apparatus also includes components for updating the ExMSI associated with the fgTS based on the received adjustment control information.

[0119] According to some embodiments, the adjustment control information includes the fgLCR RCOH of the fgODUflex link connection adjustment, wherein the fgLCR RCOH includes at least the RP field, CTRL field, MSI field, and TSCC field.

[0120] According to some embodiments, the RP field indicates that the tuning protocol is enabled, the CTRL field indicates whether the fgTS will be added or removed, the MSI field indicates the tributary port identifier (TPID) involved in the addition or removal of the fgTS, and the TSCC field indicates that the connection status has not been acknowledged.

[0121] According to some embodiments, the RP field indicates that the tuning protocol is enabled, the CTRL field indicates whether the fgTS will be added or removed, the MSI field indicates the TPID involved in the addition or removal of the fgTS, and the TSCC field indicates that the connection status has been confirmed.

[0122] According to some embodiments, the bandwidth adjustment process includes a bandwidth increase process. The components for updating the ExMSI include components for updating the ExMSI to an AcMSI.

[0123] According to some embodiments, the bandwidth adjustment process includes a bandwidth reduction process. The component for updating ExMSI includes a component for updating ExMSI to all 1s.

[0124] According to some embodiments, the apparatus further includes: a component for performing a rollback process based on the failure of the bandwidth adjustment process; and a component for updating the ExMSI to the value prior to receiving the adjustment control information based on the execution of the rollback process.

[0125] According to some embodiments, the device performs the fallback process based on: issuing an fgLCR RCOH indicating rejection via the TSGS field; receiving an fgLCR RCOH indicating rejection via the TSGS field; or receiving an fgLCR RCOH indicating to enable the adjustment protocol via the RP field.

[0126] According to some embodiments, the apparatus further includes a component for enabling the detection of dMSIM[p] of the fgODUflex tributary port p at the next adjustment multiframe boundary after receiving the adjustment control information during the bandwidth adjustment process.

[0127] According to some embodiments, CRC is used to verify the received MSI[p] of the fgODUflex tributary port p. The apparatus also includes components for enabling the detection of dMSIM[p] of the fgODUflex tributary port p at the next adjustment multiframe boundary after receiving the RP field indication to enable the adjustment protocol at the RP field indication to enable the adjustment protocol at the end of the bandwidth adjustment process.

[0128] According to some embodiments, CRC is not used to verify the received MSI[p] of the fgODUflex tributary port p. The apparatus also includes a component for enabling the detection of dMSIM[p] of the fgODUflex tributary port p at the Nth adjustment multiframe boundary after receiving the RP field indication to enable the adjustment protocol at the fgLCR RCOH during the bandwidth adjustment process, where N is greater than 1.

[0129] According to some embodiments, the first network device includes an optical data unit k-path (ODUkP) / fgODUflex sink, the second network device includes an optical data unit k-path (ODUkP) / fgODUflex source, the bandwidth adjustment process includes a lossless bandwidth adjustment process of fgODUflex, or the foregoing can be combined arbitrarily.

[0130] Figure 7 This is a simplified block diagram of an electronic device 700 suitable for implementing embodiments of the present disclosure. Device 700 can be provided to implement a first network device, such as... Figure 1A The first network device 101 is shown. As shown, device 700 includes one or more processors 710, one or more memories 720 coupled to processor 710, and one or more communication modules 740 coupled to processor 710.

[0131] The communication module 740 is used for bidirectional communication. For example, the communication module 740 may include a transmitter, receiver, or transceiver used in embodiments of this disclosure. The communication interface may represent any interface necessary for communication with other network elements.

[0132] Processor 710 can be any type suitable for a local technology network and can include, but is not limited to, one or more of a general-purpose computer, a special-purpose computer, a microcontroller, a digital signal controller (DSP), and a controller-based multi-core controller architecture. Device 700 can have multiple processors, such as application-specific integrated circuit chips, which are time-subordinate to a clock synchronized with the main processor.

[0133] Memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, erasable programmable read-only memory (EPROM), flash memory, hard disk, optical disc (CD), digital video disc (DVD), and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that do not persist during power-off periods.

[0134] Computer program 730 includes computer-executable instructions that are executed by associated processor 710. Program 730 may be stored in ROM 720. Processor 710 may perform any suitable actions and processes by loading program 730 into RAM 722.

[0135] The embodiments of this disclosure can be implemented by means of program 730, enabling device 700 to perform as described in the reference. Figures 2-5 Any process described in this disclosure. Embodiments of this disclosure may also be implemented by hardware or by a combination of software and hardware.

[0136] In some embodiments, program 730 may be tangibly contained in a computer-readable medium, which may include in device 700 (such as in memory 720) or other storage device accessible by device 700. Program 730 may be loaded from the computer-readable medium into RAM 722 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc.

[0137] Figure 8 An example of a computer-readable medium 800 in the form of a CD or DVD is shown. A program 730 is stored on the computer-readable medium.

[0138] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software, which can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are shown and described as block diagrams, flowcharts, or represented using some other illustration, it should be understood that the blocks, apparatuses, systems, techniques, or methods described herein can be implemented as, as in the non-limiting examples, hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0139] This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions included in program modules, which execute in a device on a target's real or virtual processor to perform the above-referenced... Figure 6 Method 600. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of program modules can be combined or divided among program modules as needed. The machine-executable instructions for a program module can execute within a local or distributed device. In a distributed device, program modules can reside in both local and remote storage media.

[0140] Computer program code used to implement the methods of this disclosure may be written in one or more programming languages. This computer program code may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, such that when executed by the computer or other programmable data processing apparatus, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be performed. The program code may be executed entirely on a computer, partially on a computer, as a stand-alone software package, partially on a computer and partially on a remote computer, or entirely on a remote computer or server.

[0141] In the context of this disclosure, computer program code or related data may be carried on any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, and so on. Examples of signals may include electrical, optical, radio, sound, or other forms of propagation signals, such as carrier waves, infrared signals, etc.

[0142] A computer-readable medium can be any tangible medium that contains or stores a program for or relating to an instruction execution system, apparatus, or device. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. More detailed examples of computer-readable storage media include electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical storage devices, magnetic storage devices, or any suitable combination thereof. As used herein, the terms “non-transient” or “non-signal” are a limitation on the medium itself (i.e., tangible, not signaling), and not a limitation on the persistence of data storage (e.g., RAM and ROM).

[0143] Furthermore, although the operation of the methods of this disclosure is described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all of the operations shown must be performed to achieve the desired result. Rather, the steps depicted in the flowcharts may be performed in a different order. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps. It should also be noted that the features and functions of two or more devices according to this disclosure may be embodied in one device. Conversely, the features and functions of one device described above may be further divided and embodied by multiple devices.

[0144] While this disclosure has been described with reference to several specific embodiments, it should be understood that this disclosure is not limited to the specific embodiments disclosed. This disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

[0145] Furthermore, although the operation of the methods of this disclosure is described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all of the operations shown must be performed to achieve the desired result. Rather, the steps depicted in the flowcharts may be performed in a different order. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps. It should also be noted that the features and functions of two or more devices according to this disclosure may be embodied in one device. Conversely, the features and functions of one device described above may be further divided and embodied by multiple devices.

[0146] While this disclosure has been described with reference to several specific embodiments, it should be understood that this disclosure is not limited to the specific embodiments disclosed. This disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

1. A first network device, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the first network device to at least: Receive adjustment control information from the second network device for a bandwidth adjustment process between the second network device and the first network device, wherein the adjustment control information is associated with a fine-grained time slot (fgTS) to be adjusted in the optical payload unit (OPU); and Based on the received adjustment control information, update the expected reuse structure identifier (ExMSI) associated with the fgTS.

2. The first network device according to claim 1, wherein the adjustment control information includes the adjustment control overhead (fgLCR RCOH) for flexible fine-grained optical data unit (fgODUflex) link connectivity adjustment, wherein the fgLCR RCOH includes at least a bandwidth adjustment protocol (RP) field, a control (CTRL) field, a multiplexing structure identifier (MSI) field, and a tributary time slot connectivity check (TSCC) field.

3. The first network device according to claim 2, wherein the RP field indicates that the adjustment protocol is enabled, the CTRL field indicates whether the fgTS will be added or removed, the MSI field indicates the tributary port identifier (TPID) involved in the addition or removal of the fgTS, and the TSCC field indicates that the connection status has not been confirmed.

4. The first network device according to claim 2, wherein the RP field indicates enabling the adjustment protocol, the CTRL field indicates whether the fgTS will be added or removed, the MSI field indicates the TPID involved in the addition or removal of the fgTS, and the TSCC field indicates that the connection status has been confirmed.

5. The first network device according to any one of claims 1-4, wherein the bandwidth adjustment process includes a bandwidth increase process, and the first network device updates the ExMSI by: Update the ExMSI to the accepted multiplexed structure identifier (AcMSI).

6. The first network device according to any one of claims 1-4, wherein the bandwidth adjustment process includes a bandwidth reduction process, and the first network device updates the ExMSI by: Update the ExMSI to all 1s.

7. The first network device according to any one of claims 1-4, wherein the first network device is further configured to: Since the bandwidth adjustment process failed to execute successfully, a rollback process is performed; and Based on the execution of the rollback process, the ExMSI is updated to the value prior to receiving the adjustment control information.

8. The first network device of claim 7, wherein the first network device is configured to perform the fallback process based on at least one of the following: The tributary slot group status (TSGS) field indicates a rejection of the fgLCR RCOH; Received an fgLCR RCOH indicating rejection from the TSGS field; or The RP field indicates that the fgLCR RCOH of the adjustment protocol should be enabled.

9. The first network device according to any one of claims 1-8, wherein the first network device is further configured to: During the bandwidth adjustment process, at the next adjustment multiframe boundary after receiving the adjustment control information, the detection of the multiplexing structure indication mismatch defect (dMSIM[p]) of the fgODUflex tributary port p is deenabled.

10. The first network device according to any one of claims 1-9, wherein Cyclic Redundancy Check (CRC) is used to verify the received MSI[p] of the fgODUflex tributary port p, and wherein the first network device is further configured to: During the bandwidth adjustment process, at the next adjustment multiframe boundary after receiving the RP field instruction to enable the adjustment protocol fgLCR RCOH, the detection of dMSIM[p] for the fgODUflex tributary port p is enabled.

11. The first network device according to any one of claims 1-9, wherein CRC is not used to verify the received MSI[p] of the fgODUflex tributary port p, and wherein the first network device is further configured to: During the bandwidth adjustment process, at the Nth adjustment multiframe boundary after receiving the RP field instruction to enable the adjustment protocol fgLCR RCOH, the detection of dMSIM[p] of the fgODUflex tributary port p is enabled, where N is greater than 1.

12. The first network device according to any one of claims 1-11, wherein at least one of the following: The first network device includes an optical data unit k-path (ODUkP) / fgODUflex destination; The second network device includes an optical data unit k-path (ODUkP) / fgODUflex source; or The bandwidth adjustment process includes the lossless bandwidth adjustment process of fgODUflex.

13. A method comprising: Receive adjustment control information from the second network device for a bandwidth adjustment process between the second network device and the first network device, wherein the adjustment control information is associated with a fine-grained time slot (fgTS) to be adjusted in the optical payload unit (OPU); and Based on the received adjustment control information.

14. The method of claim 13, wherein the adjustment control information includes adjustment control overhead (fgLCR RCOH) for flexible fine-grained optical data unit (fgODUflex) link connectivity adjustment, wherein the fgLCR RCOH includes at least a bandwidth adjustment protocol (RP) field, a control (CTRL) field, a multiplexing structure identifier (MSI) field, and a tributary time slot connectivity check (TSCC) field.

15. The method of claim 14, wherein the RP field indicates that the adjustment protocol is enabled, the CTRL field indicates whether the fgTS will be added or removed, the MSI field indicates the tributary port identifier (TPID) involved in the addition or removal of the fgTS, and the TSCC field indicates that the connection status has not been acknowledged.

16. The method of claim 14, wherein the RP field indicates that the adjustment protocol is enabled, the CTRL field indicates whether the fgTS will be added or removed, the MSI field indicates the TPID involved in the addition or removal of the fgTS, and the TSCC field indicates that the connection status has been confirmed.

17. The method according to any one of claims 13-16, wherein the bandwidth adjustment process includes a bandwidth increase process, and updating the ExMSI includes: Update the ExMSI to the accepted multiplexed structure identifier (AcMSI).

18. The method according to any one of claims 13-16, wherein the bandwidth adjustment process includes a bandwidth reduction process, and updating the ExMSI includes: Update the ExMSI to all 1s.

19. The method according to any one of claims 13-16, further comprising: Since the bandwidth adjustment process failed to execute successfully, a rollback process is executed. as well as Based on the execution of the rollback process, the ExMSI is updated to the value prior to receiving the adjustment control information.

20. The method of claim 19, wherein the rollback process is performed based on at least one of the following: The tributary slot group status (TSGS) field indicates a rejection of the fgLCR RCOH; Received an fgLCR RCOH indicating rejection from the TSGS field; or The RP field indicates that the fgLCR RCOH of the adjustment protocol should be enabled.

21. The method according to any one of claims 13-20, further comprising: During the bandwidth adjustment process, at the next adjustment multiframe boundary after receiving the adjustment control information, the detection of the multiplexing structure indication mismatch defect (dMSIM[p]) of the fgODUflex tributary port p is deenabled.

22. The method according to any one of claims 13-21, wherein Cyclic Redundancy Check (CRC) is used to verify the received MSI[p] of the fgODUflex tributary port p, and wherein the method further comprises: During the bandwidth adjustment process, at the next adjustment multiframe boundary after receiving the RP field instruction to enable the adjustment protocol fgLCR RCOH, the detection of dMSIM[p] for the fgODUflex tributary port p is enabled.

23. The method according to any one of claims 13-21, wherein CRC is not used to verify the received MSI[p] of the fgODUflex tributary port p, and wherein the method further comprises: During the bandwidth adjustment process, at the Nth adjustment multiframe boundary after receiving the RP field instruction to enable the adjustment protocol fgLCR RCOH, the detection of dMSIM[p] of the fgODUflex tributary port p is enabled, where N is greater than 1.

24. The method according to any one of claims 13-23, wherein at least one of the following: The first network device includes an optical data unit k-path (ODUkP) / fgODUflex destination; The second network device includes an optical data unit k-path (ODUkP) / fgODUflex source; or The bandwidth adjustment process includes the lossless bandwidth adjustment process of fgODUflex.

25. An apparatus comprising: Components for receiving adjustment control information from a second network device for a bandwidth adjustment process between the second network device and a first network device, wherein the adjustment control information is associated with a fine-grained time slot (fgTS) to be adjusted in an optical payload unit (OPU); and A component for updating the expected reuse structure identifier (ExMSI) associated with the fgTS based on the received adjustment control information.

26. A computer-readable medium comprising program instructions that, when executed by a device, cause the device to perform at least the method according to any one of claims 13-24.

Images