Transmission channel creation method, device, and storage medium

Abstract

The present application provides a transmission channel creation method, a device, and a storage medium. The transmission channel creation method is applied to a network node, and comprises: acquiring neighbor information of the network node; reporting the neighbor information to a network controller; and according to path configuration information and channel configuration information issued by the network controller, and by means of signaling transmission between network nodes, completing transmission channel creation, wherein the path configuration information is determined on the basis of the neighbor information.

Description

Methods, equipment, and storage media for creating transmission channels Technical Field

[0001] This application relates to the field of communication technology, specifically to a method, device, and storage medium for creating a transmission channel. Background Technology

[0002] In the field of network control, Metro Transport Networks (MTNs) employ a centralized management and control approach. When calculating paths using Metro Transport Network Paths (MTNPs) and fine-grained MTNPs (fgMTNPs), centralized management and control performs the calculations based on pre-planned network topology information and distributes the results to all relevant MTN network nodes along the path. This is a static approach, suitable for scenarios where MTNP / fgMTNP paths are relatively stable and do not change frequently. With the development of business needs, some intelligent computing networks and data express services require hard-isolated and deterministic delay paths like MTNPs / fgMTNPs. However, they also require flexible, on-demand creation of service paths and dynamic path updates in response to network changes. Therefore, a dynamic control plane solution needs to be considered. Summary of the Invention

[0003] In view of this, embodiments of this application provide a method, device, and storage medium for creating transmission channels, thereby achieving the effect of dynamically creating transmission channels in an MTN network.

[0004] This application provides a method for creating a transmission channel, applied to network nodes in a network architecture, including:

[0005] Obtain the neighbor information of this network node; wherein, the neighbor information includes: neighbor node information and connection port information;

[0006] The neighbor information is reported to the network controller;

[0007] The transmission channel is created by transmitting the path configuration information and channel configuration information issued by the network controller and through signaling between network nodes; wherein the path configuration information is calculated based on the network topology constructed from the neighbor information.

[0008] This application provides a method for creating a transmission channel, applied to a network controller in a network architecture, including:

[0009] Receive neighbor information reported by network nodes; wherein, the neighbor information includes: neighbor node information and connection port information;

[0010] Network topology information is constructed based on the neighbor information, and path configuration information is determined based on the network topology information and service requirement information;

[0011] The path configuration information and channel configuration information are sent to the network nodes.

[0012] This application provides a transmission channel creation apparatus, applied to a network node in a network architecture, comprising:

[0013] The acquisition module is configured to acquire neighbor information of the current network node; wherein, the neighbor information includes: neighbor node information and connection port information;

[0014] The reporting module is configured to report the neighbor information to the network controller;

[0015] The creation module is configured to create a transmission channel by transmitting path configuration information and channel configuration information issued by the network controller and through signaling between network nodes; wherein the path configuration information is calculated based on the network topology constructed from the neighbor information.

[0016] This application provides a transmission channel creation apparatus, applied to a network controller in a network architecture, comprising:

[0017] The receiving module is configured to receive neighbor information reported by network nodes; wherein the neighbor information includes: neighbor node information and connection port information;

[0018] The determination module is configured to construct network topology information based on the neighbor information, and determine path configuration information based on the network topology information and service requirement information;

[0019] The sending module is configured to send the path configuration information and channel configuration information to the network node.

[0020] This application provides a communication device, including: a memory, and one or more processors;

[0021] The memory is configured to store one or more programs;

[0022] When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any of the above embodiments.

[0023] This application provides a storage medium storing a computer program, which, when executed by a processor, implements the methods described in any of the above embodiments. Attached Figure Description

[0024] Figure 1 is a schematic diagram of a network architecture for a single-level controller provided in an embodiment of this application;

[0025] Figure 2 is a schematic diagram of a network architecture for a multi-level controller architecture provided in an embodiment of this application;

[0026] Figure 3 is a flowchart of a method for creating a transmission channel according to an embodiment of this application;

[0027] Figure 4 is a flowchart of another method for creating a transmission channel provided in an embodiment of this application;

[0028] Figure 5 is a schematic diagram of the hierarchical relationship of an MTN network provided in an embodiment of this application;

[0029] Figure 6 is a flowchart illustrating the implementation of a network controller distributing channel configuration information according to an embodiment of this application.

[0030] Figure 7 is a flowchart illustrating the implementation of a network node creating a transmission channel according to an embodiment of this application;

[0031] Figure 8 is a schematic diagram illustrating the implementation of path configuration information and channel configuration information distribution and signaling transmission according to an embodiment of this application;

[0032] Figure 9 is a schematic diagram illustrating the implementation of another path configuration information and channel configuration information distribution and signaling transmission provided in an embodiment of this application;

[0033] Figure 10 is a schematic diagram of the creation of a transmission channel in an MTN network according to an embodiment of this application;

[0034] Figure 11 is a schematic diagram of an OAM code block format provided by related technologies;

[0035] Figure 12 is a schematic diagram of the format of an OAM extended code block provided in an embodiment of this application;

[0036] Figure 13 is a schematic diagram of the configuration of an MTNS / MTNP / fgMTNP network layer provided in an embodiment of this application;

[0037] Figure 14 is a structural block diagram of a transmission channel creation device provided in an embodiment of this application;

[0038] Figure 15 is a structural block diagram of another transmission channel creation device provided in an embodiment of this application;

[0039] Figure 16 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0040] The embodiments of this application will be described below with reference to the accompanying drawings. The examples given are for illustrative purposes only and are not intended to limit the scope of this application.

[0041] Generalized Multiprotocol Label Switching (GMPLS) is a typical dynamic control plane solution and the closest technical solution to this application. This architecture allows for the deployment of a centralized controller and centralized routing through Path Computation Element (PCE) nodes. It also allows for the deployment of distributed control plane protocols to establish, tear down, and maintain tunnels. However, GMPLS involves numerous protocols, making the overall solution complex. Specifically, GMPLS requires the use of Link Management Protocol (LMP) for link and control channel management and maintenance, Interior Gateway Protocol (IGP) (Intermediate System to Intermediate System (IS-IS) or Open Shortest Path First-Traffic Engineering (OSPF-TE)) for topology and resource acquisition and maintenance, and Resource Reservation Protocol-Traffic Engineering (RSVP-TE) for signaling interaction between network nodes, enabling the management and operation of forwarding plane tunnels. Since MTNP and fgMTNP in the MTN network are Time Division Multiplexing (TDM) type connections, which are transport network connections rather than data network connections, they do not require certain dynamic connection features (such as connection state refresh mechanisms based on control plane protocols, automatic connection teardown mechanisms based on fault awareness, etc.). Therefore, a simpler technical solution is desired to implement the control plane of the MTN network.

[0042] The network architectures involved in this application include a single-level controller architecture and a multi-level controller architecture. Figure 1 is a schematic diagram of the network architecture of a single-level controller architecture provided in this application embodiment; Figure 2 is a schematic diagram of the network architecture of a multi-level controller architecture provided in this application embodiment. As shown in Figure 1, a global network controller is deployed in the MTN network, and the global network controller directly interacts with each network node (network node A, B, C, D, E, M, N, P, Q, and Z) in the MTN network through signaling. As shown in Figure 2, a global network controller and two sub-network controllers (SNCs) are deployed in the MTN network. The global network controller interacts with each SNC through signaling, and each SNC interacts with each network node in its sub-network through signaling. That is, SNC1 interacts with each network node (network node A, B, C, D, and E) in its sub-network through signaling, and SNC2 interacts with each network node (network node M, N, P, Q, and Z) in its sub-network through signaling.

[0043] In one embodiment, Figure 3 is a flowchart of a method for creating a transmission channel according to an embodiment of this application. This embodiment is applied to the case of dynamically creating an end-to-end transmission channel in an MTN network. This embodiment can be executed by a network node. As shown in Figure 3, this embodiment includes: S110-S130.

[0044] S110. Obtain the neighbor information of this network node.

[0045] In one example, neighbor information includes: neighbor node information and connection port information. Neighbor information characterizes the neighbor connection relationship between this network node and its adjacent network nodes. Neighbor node information characterizes information about all other network nodes adjacent to this network node; for example, neighbor node information may include: the node identifier of the neighbor network node. Connection port information characterizes the ports of other network nodes that have established connections with this network node. In one example, this network node can act as a receiver, receiving extended messages or network overhead sent by its adjacent network nodes, and parsing the sender's network node identifier and network identifier from the extended message or network overhead to obtain the neighbor information of this network node.

[0046] S120. Report neighbor information to the network controller.

[0047] In one example, the network controller includes: a network global controller, or a network global controller and at least two subnet controllers.

[0048] In an MTN network, each network node can report the obtained neighbor information to the network controller (i.e., the global network controller or subnet controller) through the interface between the node and the network controller. After the network controller receives the neighbor information reported by all network nodes, it analyzes and processes it to construct the network topology. In one example, if the MTN network includes a global network controller, each network node in the MTN network will directly report its own neighbor information to the global network controller. In one example, if the MTN network contains a network global controller and at least two subnet controllers, each network node in the MTN network can report its own neighbor information to the subnet controller within its subnet. The subnet controller reports the network topology information formed within its subnet to the network global controller as needed (i.e., in the MTN network shown in Figure 2, the network topology information between nodes A, B, C, D, and E is reported to SNC1, and the network topology information between nodes M, N, P, Q, and Z is reported to SNC2); or, the subnet controller reports the network topology information of the boundaries within its subnet to the network global controller (in the MTN network shown in Figure 2, the network topology information between nodes D and M is reported to the network global controller, and the network topology information between nodes E and N is reported to the network global controller).

[0049] S130. The transmission channel is created by following the path configuration information and channel configuration information issued by the network controller and through signaling transmission between network nodes; wherein, the path configuration information is calculated based on the network topology constructed from the neighbor information.

[0050] In one example, path configuration information describes the hop-by-hop path between each network node in the MTN network; it can also be understood as the information forwarding path for each network node. In another example, the network controller can construct corresponding network topology information based on neighbor information and determine path configuration information based on the network topology information and service requirement information; the service requirement information carries the start and end nodes of the transmission channel and bandwidth requirements. In another example, if a global network controller is deployed in the MTN network, the global network controller can directly calculate the path configuration information based on the network topology information and service requirement information. In yet another example, if a global network controller and a subnet controller are deployed in the MTN network, the global network controller can perform network-wide path calculation, and the subnet controller can distribute the path configuration information to each network node within its subnet; alternatively, the global network controller can calculate and distribute paths at subnet boundaries, and the subnet controller can calculate and distribute paths within its own subnet.

[0051] In one example, if the MTN network includes a network global controller, the first node in the MTN network receives path configuration information and channel configuration information issued by the network global controller, completes its own time slot cross-connect configuration, bandwidth configuration, and path configuration, and then finds the next-hop network node based on the path configuration information, and sends the path configuration information and channel configuration information to the next-hop network node to complete the time slot cross-connect configuration, bandwidth configuration, and path configuration of the next-hop network node. This process continues until the path configuration information and channel configuration information are passed to the tail node, completing the end-to-end transmission channel creation process.

[0052] In one example, if the MTN network includes a network global controller and a subnet controller, the process of creating an end-to-end transmission channel can be completed according to the cooperation strategy between the network global controller and the subnet controller in the MTN network.

[0053] In one embodiment, obtaining the neighbor information of the network node includes one of the following:

[0054] Obtain the neighbor information of this network node at the first network layer;

[0055] Obtain the neighbor information of this network node in the second network layer.

[0056] In one example, the first network layer can be the MTNS (Metro Transport Network Section) layer; the second network layer can be the MTNP layer. In another example, if a transport channel is created for the MTNP layer, according to the MTN network hierarchy, the service layer for the MTNP layer is the MTNS layer, meaning it's necessary to obtain the neighbor information of each network node at the MTNS layer. Similarly, in another example, if a transport channel is created for the fgMTNP layer, according to the MTN network hierarchy, the service layer for the fgMTNP layer is the MTNP layer, also requiring the acquisition of the neighbor information of each network node at the MTNP layer.

[0057] In one embodiment, obtaining the neighbor information of the network node at the first network layer includes:

[0058] Obtain the first network cost carrying the first network identifier sent by other network nodes adjacent to this network node;

[0059] The first network identifier and the node identifiers of other network nodes are parsed from the first network overhead to obtain the neighbor information of this network node at the first network layer. In one example, other network nodes acting as senders can encapsulate the first network identifier in the first network overhead and send the first network overhead to the network node acting as a receiver. The receiving network node parses the first network overhead to obtain the first network identifier and the node identifiers of the other network nodes acting as senders, thus obtaining the neighbor connection relationship of this network node at the first network layer, which serves as the neighbor information.

[0060] In one example, the first network identifier can be the MTNS identifier; the first network overhead can be the MTNS overhead, for example, the MTNS overhead can be the management channel overhead of the MTNS layer.

[0061] In one embodiment, resolving the first network identifier from the first network overhead includes:

[0062] The first extended message is parsed from the first network overhead, and the first network identifier is parsed from the first extended message; or,

[0063] The first network identifier is obtained directly from the first network overhead.

[0064] In one example, other network nodes acting as senders can directly encapsulate the first network identifier in the first network overhead and send the first network overhead to the receiving network node. The receiving network node then parses the first network overhead to obtain the first network identifier. Alternatively, other network nodes acting as senders can first encapsulate the first network identifier in a first extended message, then encapsulate the first extended message in the first network overhead, and send the first network overhead to the receiving network node. The receiving network node then parses the first network overhead to obtain the first extended message, and then parses the first extended message to obtain the first network identifier. For example, the first extended message can be a Link Layer Discovery Protocol (LLDP) message.

[0065] In one embodiment, obtaining the neighbor information of the network node at the first network layer includes:

[0066] Obtain the first extended data frame carrying the first network identifier sent by other network nodes adjacent to this network node;

[0067] The first network identifier and the node identifiers of other network nodes are obtained by parsing the first extended data frame, thus obtaining the neighbor information of this network node in the first network layer. In one example, the first extended data frame refers to a fixed-length data frame in an MTN network; the first extended data frame can also be called a first extended data code block. Other network nodes acting as senders can encapsulate the first network identifier in the first extended data frame and send the first extended data frame to the network nodes acting as receivers. The receiving network nodes parse the first extended data frame to obtain the first network identifier and the node identifiers of the other network nodes acting as senders, thereby obtaining the neighbor connection relationship of this network node in the first network layer, which serves as neighbor information. For example, the first extended data frame can be an Operation Administration and Maintenance (OAM) extended code block.

[0068] In one embodiment, obtaining the neighbor information of the current network node at the second network layer includes:

[0069] Obtain the second network overhead carried by the second network identifier sent by other network nodes adjacent to this network node;

[0070] The second network identifier and the node identifiers of other network nodes are parsed from the second network overhead to obtain the neighbor information of this network node in the second network layer. In one example, other network nodes acting as senders can encapsulate the second network identifier in the second network overhead and send the second network overhead to the network node acting as a receiver. The receiving network node parses the second network overhead to obtain the second network identifier and the node identifiers of the other network nodes acting as senders, thus obtaining the neighbor connection relationship of this network node in the second network layer, which serves as the neighbor information.

[0071] In one example, the second network identifier can be an MTNP identifier; the first network overhead can be MTNP overhead, for example, MTNP overhead can be the general communication channel overhead of the MTNP layer.

[0072] In one embodiment, resolving the second network identifier from the second network overhead includes:

[0073] The first extended message is parsed from the second network overhead, and the second network identifier is parsed from the first extended message; or,

[0074] The second network identifier is obtained directly from the second network overhead.

[0075] In one example, other network nodes acting as senders can directly encapsulate the second network identifier within the second network overhead and send this second network overhead to the receiving network node. The receiving network node then parses the second network overhead to obtain the second network identifier. Alternatively, other network nodes acting as senders can first encapsulate the second network identifier within a first extended message, then encapsulate this first extended message within the second network overhead, and send this second network overhead to the receiving network node. The receiving network node then parses the second network overhead to obtain the first extended message, and then parses the first extended message to obtain the second network identifier. For example, the first extended message can be an LLDP protocol message.

[0076] In one embodiment, obtaining the neighbor information of the current network node at the second network layer includes:

[0077] Obtain the first extended data frame carrying the second network identifier sent by other network nodes adjacent to this network node;

[0078] The second network identifier and the node identifiers of other network nodes are obtained by parsing the first extended data frame, thus obtaining the neighbor information of this network node in the second network layer. In one example, other network nodes acting as senders can encapsulate the second network identifier in the first extended data frame and send the first extended data frame to the network node acting as a receiver. The receiving network node parses the first extended data frame to obtain the second network identifier and the node identifiers of the other network nodes acting as senders, thereby obtaining the neighbor connection relationship of this network node in the second network layer, which serves as the neighbor information.

[0079] In one embodiment, the network controller includes: a network global controller; and the creation of a transmission channel by receiving path configuration information and channel configuration information issued by the network global controller and transmitting them through signaling between network nodes, including: receiving path configuration information and channel configuration information issued by the network global controller; performing time slot cross-configuration and path configuration according to the path configuration information and channel configuration information; sending the path configuration information and channel configuration information to the next network node, and returning to the steps of performing time slot cross-configuration and path configuration according to the path configuration information and channel configuration information, until the transmission reaches the last network node, thus obtaining an end-to-end transmission channel. In one example, when the MTN network includes a network global controller, the first node in the MTN network receives path configuration information and channel configuration information from the network global controller, and performs time slot cross-configuration and path configuration according to the path configuration information and channel configuration information. Then, it sends the path configuration information and channel configuration information to the next-hop network node, and performs time slot cross-configuration and path configuration for that network node according to the path configuration information and channel configuration information. Then, it sends the path configuration information and channel configuration information to the next-hop network node again, and performs time slot cross-configuration and path configuration for that network node according to the path configuration information and channel configuration information, and so on, until the path configuration information and channel configuration information are sent to the tail node, thus completing the creation of an end-to-end transmission channel between each network node on the channel path formed by the first node and the tail node in the MTN network.

[0080] In one embodiment, the network controller includes a global network controller and at least two subnet controllers. The creation of a transmission channel is achieved by transmitting path configuration information and channel configuration information issued by the network controller and through signaling between network nodes. This includes: receiving subnet boundary channel configuration information, path configuration information, and channel configuration information issued by the corresponding subnet controller through a first type of network node; wherein each subnet controller receives path configuration information, subnet boundary channel configuration information, and channel configuration information issued by the global network controller; the first type of network node is the first network node in the subnet to which each subnet controller belongs; and sending the subnet boundary channel configuration information, path configuration information, and channel configuration information to a second type of network node within the subnet on the corresponding channel path through the first type of network node, thereby creating an end-to-end transmission channel within the corresponding subnet; wherein the second type of network node is not the first network node in the subnet to which the subnet controller belongs. In one example, the network global controller in the MTN network calculates the complete channel path and sends the channel configuration information to all relevant subnet controllers on the channel path. The subnet controller sends the channel configuration information within its own subnet and at its subnet boundary to the first type of network node within the corresponding subnet. The first type of network node in the MTN network then transmits the channel configuration information to the other network nodes (i.e., second type of network nodes) on the channel path via signaling, thus completing the creation of the transmission channel within its own subnet and at its subnet boundary.

[0081] In one embodiment, the network controller includes: a global network controller, a first type subnet controller, and at least one second type subnet controller. The creation of a transmission channel is achieved by transmitting path configuration information and channel configuration information issued by the network controller and through signaling between network nodes. This includes: receiving subnet boundary channel configuration information, path configuration information, and channel configuration information issued by the corresponding first type subnet controller or second type subnet controller through a first type network node; wherein, the first type subnet controller receives path configuration information, subnet boundary channel configuration information, and channel configuration information issued by the global network controller; each second type subnet controller receives subnet boundary channel configuration information, path configuration information, and channel configuration information issued by the first type subnet controller; the first type network node is the first network node in the subnet to which each subnet controller belongs; the first type network node sends the subnet boundary channel configuration information, path configuration information, and channel configuration information to the second type network node within the subnet on the corresponding channel path through the first type network node, thereby creating an end-to-end transmission channel within the corresponding subnet; wherein, the second type network node is not the first network node in the subnet to which the subnet controller belongs. In an MTN network, the global network controller calculates the complete channel path and distributes the channel configuration information to the SNC (Type 1 Subnet Controller) of the subnet containing the first node of the path. This first-type subnet controller then distributes the channel configuration information to the first-type network nodes (i.e., the first nodes) within the MTN network along the channel path. Simultaneously, this SNC passes the channel configuration information to the SNC (Type 2 Subnet Controller) of the next subnet along the channel path. The next subnet's SNC then distributes the channel configuration information within that subnet to the first node of the MTN network within its own subnet. Each SNC distributes the channel configuration information within its subnet and at its subnet boundaries to the first node of the corresponding MTN network within that subnet. The first node of the MTN network within its own subnet then transmits the channel configuration information to the remaining nodes (i.e., Type 2 network nodes) along the channel path via signaling, completing the creation of the transmission channel within its subnet and at its subnet boundaries. Once all subnets have been configured, the complete channel creation is complete.

[0082] In one embodiment, the network controller includes: a global network controller and at least two subnet controllers; the creation of a transmission channel is completed according to the path configuration information and channel configuration information issued by the network controller and through signaling transmission between network nodes, including: receiving the path configuration information and channel configuration information issued by the subnet controllers through a first type of network node; wherein, each subnet controller receives subnet boundary channel configuration information issued by the global network controller; the first type of network node is the first network node in the subnet to which each subnet controller belongs; the path configuration information is determined by the subnet controller associated with the first type of network node based on network topology information and service requirement information; sending the subnet boundary channel configuration information, path configuration information and channel configuration information to the second type of network node in the subnet to which the channel path belongs through the first type of network node, thereby creating an end-to-end transmission channel in the corresponding subnet; wherein, the second type of network node is not the first network node in the subnet to which the subnet controller belongs. In one example, the network global controller in the MTN network calculates the connectivity between subnets along the channel path (excluding the channel paths within each subnet), and sends the channel configuration information to all relevant subnet controllers along that channel path. Each subnet controller, based on the received information, calculates the channel path within its own subnet and sends the channel configuration information (path information within its own subnet and at subnet boundaries, etc.) to the MTN network head node (i.e., the first type of network node) along the channel path within its subnet. The MTN network head node within its own subnet, based on the channel configuration information sent by the SNC and the signaling from the MTNS / MTNP overhead channel of the upstream node (signaling messages are only received from the overhead channel of the upstream node if the MTN network head node within its own subnet is not the MTNP / fgMTPN path head node), completes the time slot cross-connect configuration of its node and transmits the channel configuration information to the remaining nodes within its own subnet along the channel path via signaling, thus completing the creation of the transmission channels within its own subnet and at subnet boundaries. Once all subnets have been configured, the complete channel creation is finished.

[0083] In one embodiment, the channel configuration information includes at least one of the following: channel identifier; timeslot information; bandwidth information.

[0084] In one embodiment, FIG4 is a flowchart of another method for creating a transmission channel provided by an embodiment of this application. This embodiment is applied to the case of dynamically creating an end-to-end transmission channel in an MTN network. This embodiment can be executed by a network controller. As shown in FIG4, this embodiment includes: S210-S230.

[0085] S210. Receive neighbor information reported by network nodes; wherein, the neighbor information includes: neighbor node information and connection port information.

[0086] S220. Construct network topology information based on neighbor information, and determine path configuration information based on network topology information and service requirement information.

[0087] S230: Send the path configuration information and channel configuration information to the network nodes.

[0088] In one embodiment, the channel configuration information includes at least one of the following: channel identifier; timeslot information; bandwidth information.

[0089] In one embodiment, receiving neighbor information reported by a network node includes one of the following:

[0090] Receive neighbor information reported by network nodes at the first network layer;

[0091] Receive neighbor information reported by network nodes at the second network layer.

[0092] In one embodiment, the method for obtaining neighbor information at the first network layer includes:

[0093] By obtaining the first network overhead carrying the first network identifier sent by other network nodes adjacent to this network node;

[0094] The first network identifier and the node identifiers of other network nodes are parsed from the first network overhead to obtain the neighbor information of this network node in the first network layer.

[0095] In one embodiment, resolving the first network identifier from the first network overhead includes:

[0096] The first extended message is parsed from the first network overhead, and the first network identifier is parsed from the first extended message; or,

[0097] The first network identifier is obtained directly from the first network overhead.

[0098] In one embodiment, the method for obtaining neighbor information at the first network layer includes:

[0099] Obtain the first extended data frame carrying the first network identifier sent by other network nodes adjacent to this network node;

[0100] The first network identifier and the node identifiers of other network nodes are obtained by parsing the first extended data frame, thus obtaining the neighbor information of this network node in the first network layer.

[0101] In one embodiment, the method for obtaining neighbor information at the second network layer includes:

[0102] Obtain the second network overhead carried by the second network identifier sent by other network nodes adjacent to this network node;

[0103] The second network identifier and the node identifiers of other network nodes are parsed from the second network overhead to obtain the neighbor information of this network node in the second network layer.

[0104] In one embodiment, resolving the second network identifier from the second network overhead includes:

[0105] The first extended message is parsed from the second network overhead, and the second network identifier is parsed from the first extended message; or,

[0106] The second network identifier is obtained directly from the second network overhead.

[0107] In one embodiment, the method for obtaining neighbor information at the second network layer includes:

[0108] Obtain the first extended data frame carrying the second network identifier sent by other network nodes adjacent to this network node;

[0109] The second network identifier and the node identifiers of other network nodes are obtained by parsing the first extended data frame, thus obtaining the neighbor information of this network node in the second network layer.

[0110] In one embodiment, the network controller includes: a network global controller; network nodes create transmission channels based on path configuration information and channel configuration information, and through signaling transmission between network nodes, including:

[0111] Receive path configuration information and channel configuration information issued by the network global controller through network nodes;

[0112] Time slot cross-configuration and path configuration are performed through network nodes according to path configuration information and channel configuration information;

[0113] The path configuration information and channel configuration information are sent from one network node to the next, and the steps of time slot cross-configuration and path configuration according to the path configuration information and channel configuration information are returned until the transmission reaches the last network node, thus obtaining an end-to-end transmission channel.

[0114] In one embodiment, the network controller includes: a global network controller and at least two subnet controllers; network nodes create transmission channels based on path configuration information and channel configuration information, and through signaling transmission between network nodes, including:

[0115] The first type of network node receives subnet boundary channel configuration information, path configuration information, and channel configuration information issued by the corresponding subnet controller; wherein, each subnet controller receives path configuration information, subnet boundary channel configuration information, and channel configuration information issued by the global network controller; the first type of network node is the first network node in the subnet to which each subnet controller belongs;

[0116] The first type of network node sends the subnet boundary channel configuration information, path configuration information, and channel configuration information to the second type of network node in the subnet on the corresponding channel path, thereby creating an end-to-end transmission channel within the corresponding subnet; wherein, the second type of network node is not the first network node in the subnet to which the subnet controller belongs.

[0117] In one embodiment, the network controller includes: a network global controller, a first type subnet controller, and at least one second type subnet controller; network nodes create transmission channels based on path configuration information and channel configuration information, and through signaling transmission between network nodes, including:

[0118] Each type of network node receives subnet boundary channel configuration information, path configuration information, and channel configuration information from the corresponding type of subnet controller or type of subnet controller. Specifically, each type of subnet controller receives path configuration information, subnet boundary channel configuration information, and channel configuration information from the network global controller; each type of subnet controller receives subnet boundary channel configuration information, path configuration information, and channel configuration information from the type of subnet controller; and each type of network node is the first network node in the subnet to which each subnet controller belongs.

[0119] The first type of network node sends the subnet boundary channel configuration information, path configuration information, and channel configuration information to the second type of network node in the subnet on the corresponding channel path, thereby creating an end-to-end transmission channel within the corresponding subnet; wherein, the second type of network node is not the first network node in the subnet to which the subnet controller belongs.

[0120] In one embodiment, the network controller includes: a global network controller and at least two subnet controllers; network nodes create transmission channels based on path configuration information and channel configuration information, and through signaling transmission between network nodes, including:

[0121] The first type of network node receives path configuration information and channel configuration information issued by the subnet controller; wherein, each subnet controller receives subnet boundary channel configuration information issued by the global network controller; the first type of network node is the first network node in the subnet to which each subnet controller belongs; the path configuration information is determined by the subnet controller associated with the first type of network node based on network topology information and service requirement information;

[0122] The first type of network node sends the subnet boundary channel configuration information, path configuration information, and channel configuration information to the second type of network node in the subnet on the corresponding channel path, thereby creating an end-to-end transmission channel within the corresponding subnet; wherein, the second type of network node is not the first network node in the subnet to which the subnet controller belongs.

[0123] It should be noted that the explanations of parameters such as neighbor information, path configuration information, channel configuration information, first network identifier, first network cost, first extended message, second network identifier, second network cost, first extended data frame, network global controller, and subnet controller in the method for creating transmission channels applied to network controllers can be found in the descriptions of the corresponding parameters in the method for creating transmission channels applied to network nodes, and will not be repeated here.

[0124] In the following embodiments, the first network layer is the MTNS layer, the second network layer is the MTNP layer, the first network identifier is the MTNS identifier, the second network identifier is the MTNP identifier, the first network overhead is the MTNS overhead, the second network overhead is the MTNP overhead, the first extended message is the LLDP protocol message, and the first extended data frame is the OAM extended code block, to illustrate the process of creating the transmission channel. Figure 5 is a schematic diagram of the hierarchical relationship of an MTN network provided in an embodiment of this application. As shown in Figure 5, the service layer of the MTNP layer is the MTNS layer, and the service layer of the fgMTNP layer is the MTNP layer.

[0125] The overall solution for the MTN network control plane involved in this application is as follows: Network nodes in the MTN network can exchange frame overhead or OAM code blocks at the MTNS / MTNP layer to obtain neighbor information, and report the neighbor information to the network controller (e.g., the network global controller or subnet controller (SNC)) in the MTN network. The network controller in the MTN network integrates and analyzes the neighbor information from all MTN network nodes (referred to as network nodes) to construct network topology information. When there is a service requirement, the network controller in the MTN network calculates the MTNP / fgMTNP channel path based on the service requirement information and the network topology information, and sends the generated path configuration information to the first node of the MTNP / fgMTNP channel. The first nodes of the MTNP / fgMTNP channel use MTNS / MTNP frame overhead to transmit signaling along the channel path to complete the creation of the MTNP / fgMTNP channel.

[0126] Figure 6 is a flowchart illustrating the implementation of a network controller issuing channel configuration information according to an embodiment of this application; Figure 7 is a flowchart illustrating the implementation of a network node creating a transmission channel according to an embodiment of this application. The flowcharts for the network controller and network node in this scheme are shown in Figures 6 and 7. The steps involved in this scheme include:

[0127] Step 1, Neighbor Discovery: Neighbor relationships at the Ethernet physical layer can be implemented using the LLDP protocol. However, in an MTN network, neighbor relationships at the MTNS or MTNP layers need to be discovered. The following two methods can be used to achieve this:

[0128] The first implementation method uses an LLDP protocol extension, adding an MTNS ID TLV and an MTNP ID TLV for advertising MTNS and MTNP identifiers. The sending network node can encapsulate the LLDP protocol message into either the MTNS overhead or the MTNP overhead (LLDP protocol messages advertising the MTNS identifier are encapsulated in the MTNS overhead, typically in the management channel overhead of the MTNS layer; LLDP protocol messages advertising the MTNP identifier are encapsulated in the MTNP overhead, typically in the general communication channel overhead of the MTNP layer). The receiving network node, based on the LLDP protocol message received in a specific MTNS or MTNP overhead, parses out the node identifier and MTNS / MTNP identifier of the peer MTN network node, obtaining the neighbor connection relationship of that network node as neighbor information.

[0129] The second implementation method is to use the OAM extension code block of the MTN network. The MTN network node as the sender announces its MTNS identifier or MTNP identifier to the other party in the extended OAM message (announcing the MTNS identifier in the OAM extension message of MTNS and the MTNP identifier in the OAM extension code block of MTNP). The MTN network node as the receiver extracts the MTN network node identifier and MTNS / MTNP identifier of the other end according to the OAM extension code block received by a certain MTNS or MTNP, and obtains the neighbor connection relationship of the network node as the neighbor information.

[0130] Step 2, collect and report network topology information: MTN network nodes report the MTNS / MTNP neighbor information obtained by the above method to the network controller (e.g., the global network controller or subnet controller) through the interface between the network node and the network controller. After obtaining the neighbor information reported by all network nodes, the network controller analyzes and processes the neighbor information to construct the network topology information.

[0131] When a network global controller is deployed in an MTN network, MTN network nodes only need to report neighbor information to the network global controller.

[0132] When both a global network controller and a subnet controller exist in an MTN network, MTN network nodes report neighbor information to the designated network controller (usually the subnet controller of the corresponding network area). The subnet controller can report the network topology information it forms to the global network controller as needed, or the subnet controller can only report the topology information of its own subnet boundary to the global network controller.

[0133] Step 3, Path Calculation: After receiving the path calculation request, the network controller calculates the path based on the constructed network topology information.

[0134] When an MTN global controller is deployed in an MTN network, the routing is performed by the global controller.

[0135] When both an MTN global controller and a subnet controller exist in the MTN network, the global controller can perform network-wide path calculation, while the subnet controller can distribute the path calculation results to the MTN network nodes in its local area. Alternatively, the global controller can perform path calculation and distribution at the subnet boundaries, while the subnet controller can perform path calculation and distribution within its own subnet.

[0136] Step 4, Channel Configuration: The network controller distributes MTNP / fgMTNP to the MTN network nodes according to the calculated path.

[0137] Figure 8 is a schematic diagram illustrating the implementation of path configuration information and channel configuration information distribution and signaling transmission according to an embodiment of this application. As shown in Figure 8, when a network global controller is deployed in an MTN network, the network global controller distributes MTNP / fgMTNP channel configuration information (e.g., bandwidth, end-to-end path identifier, etc.) and path configuration information to the first node (i.e., node A) on the channel path. While completing the time slot cross-configuration, path information configuration, and bandwidth information configuration of its own network node, the first node finds the MTNS / MTNP to the next hop node (i.e., node B) according to the path configuration information description, and uses MTNS / MTNP frame overhead to transmit the MTNP / fgMTNP channel configuration information and path configuration information along the channel path to subsequent network nodes (i.e., nodes D, M, and P). Similarly, while completing the configuration of its own network node, subsequent network nodes continue to use MTNS / MTNP frame overhead to transmit the MTNP / fgMTNP channel configuration information and path configuration information along the channel path to subsequent nodes of its own node, until the tail node (i.e., node Z).

[0138] Figure 9 is a schematic diagram illustrating the implementation of another path configuration information and channel configuration information distribution and signaling transmission provided in an embodiment of this application. When both a network global controller and a subnet controller exist in the MTN network, there are multiple channel configuration methods based on the cooperation strategy between the network global controller and the subnet controller, as shown in Figure 9:

[0139] Method 1: The network global controller in the MTN network calculates the complete channel path and sends the channel configuration information to all relevant subnet controllers on the channel path. The subnet controller sends the channel configuration information within its subnet and at its subnet boundary to the first node in the corresponding subnet. The first node then transmits the channel configuration information to other network nodes in its subnet on the channel path via signaling, thus completing the creation of the transmission channel within its subnet and at its subnet boundary.

[0140] Method 2: The network global controller in the MTN network calculates the complete channel path and distributes the channel configuration to the SNC (Subnet Controller) of the subnet where the first node of the path is located. The subnet controller then distributes the channel configuration to the first node of the MTN network along the channel path. Simultaneously, this SNC passes the channel configuration information to the SNC of the next subnet along the channel path. The SNC of the next subnet then distributes the channel configuration within its subnet to the first node of the MTN network within its own subnet. Each SNC distributes the channel configuration within its subnet and at its subnet boundaries to the first node of the MTN network within its corresponding subnet. The first node of the MTN network within its subnet then transmits the channel configuration information to the remaining nodes along the channel path via signaling, completing the creation of channels within its subnet and at its subnet boundaries. Once all subnets have been configured, the complete channel creation is complete.

[0141] Method 3: The network global controller in the MTN network calculates the connection relationships between subnets in the channel path (excluding the channel paths within each subnet), and distributes the channel configuration to all relevant subnet controllers on that channel path. Each subnet controller calculates the channel path within its own subnet based on the received information and distributes the channel configuration (path information within its own subnet and at subnet boundaries, etc.) to the MTN network head node on the channel path within its subnet. The MTN network head node within its own subnet completes its time slot cross-connect configuration based on the configuration distributed by the SNC and the signaling from the MTNS / MTNP overhead channel of the upstream node (signaling messages will only be received from the overhead channel of the upstream node if the MTN network head node within its own subnet is not the head node of the MTNP / fgMTPN path). It then transmits the channel configuration information to the other nodes within its own subnet on the channel path via signaling, completing the creation of channels within its own subnet and at subnet boundaries. Once all subnets have completed their configurations, the complete channel creation is achieved.

[0142] In one embodiment, a single-level controller architecture is used to create the MTNP:

[0143] In this embodiment, the MTN network adopts a single-level controller architecture as shown in Figure 1 to realize channel creation in the MTNP layer.

[0144] Neighbor discovery: Using the LLDP protocol extension method, an MTNS-ID TLV is defined to identify the MTNS. MTN network nodes encapsulate LLDP protocol messages into the MTNS Management Channel Control (MCC) overhead, fill in their local MTNS identifier in the MTNS-ID TLV, and obtain the peer's node identifier (which can be an existing Media Access Control (MAC) address or network address in the LLDP protocol) and MTNS identifier through LLDP protocol interaction, thus obtaining neighbor information at the MTNS layer.

[0145] Topology information collection and reporting: All MTN network nodes report all neighbor information obtained by this node (local node identifier, local MTNS identifier, peer node identifier, peer MTNS identifier) ​​to the MTN network global controller via the Path Computation Element Protocol-Link State (PCEP-LS) protocol. The MTN network global controller constructs the network topology information for the entire network based on the neighbor information reported by all MTN network nodes.

[0146] Path calculation: After receiving the routing request from the MTNP (which specifies the first and last nodes and bandwidth requirements, etc.), the network global controller in the MTN network calculates the forwarding path of the MTNP based on the network topology information and routing policy requirements of the entire network, and uses it as path configuration information.

[0147] Channel Configuration: Figure 10 is a schematic diagram of the creation of a transmission channel in an MTN network provided in an embodiment of this application. The network global controller in the MTN network sends the calculated forwarding path (assumed to be ABDMPZ) information (also known as path configuration information) to the first node A on the MTNP path. Node A completes the configuration of its network node according to the path configuration information (configuring the MTNP's outgoing MTNS and the occupied time slot number, etc., assuming that the outgoing MTNS of node A is identified as MTN Group01, and this MTNP occupies time slot 3 of this MTN Group, the time slot number can be allocated by this node, or allocated by the network global controller in the MTN network and sent in the path configuration information). At the same time, node A sends the MTNP's path configuration information to node B through the MCC overhead of MTN Group01. Assuming node B receives the MTNP path configuration information from MTN Group01 of its own network node, and the path configuration information indicates that the outgoing direction of node B is MTN Group05, then node B completes its own configuration based on this information (configuring the MTNP's inbound timeslot at this node to MTN Group01 timeslot 3 and the outbound timeslot to MTN Group05 timeslot 2). At the same time, node B sends the MTNP path configuration information to node D through the MCC overhead of MTN Group05. Subsequent nodes on the MTNP path repeat the above process until the path configuration information is passed to the tail node Z, and node Z completes its own configuration (node ​​Z only needs to configure the inbound MTN Group and timeslot), resulting in the MTNP channel path shown in Figure 10.

[0148] This completes the creation of the MTNP layer channel.

[0149] Note: The above process does not consider message response mechanisms. For message response mechanisms, you can refer to some existing solutions, which will not be elaborated here.

[0150] In one embodiment, a multi-level controller architecture is used to create the fgMTNP:

[0151] In this embodiment, the MTN network adopts a multi-level controller architecture as shown in Figure 2 to realize channel creation of the fgMTNP layer.

[0152] Neighbor Discovery: Based on the network hierarchy of the MTNP network, the service layer of fgMTNP is the MTNP layer. Here, it is necessary to discover the network topology information of the MTNP layer. This can be achieved by extending the LLDP protocol as described above, running LLDP in the General Communication Channel (GCC) of the MTNP layer to realize neighbor discovery. Since the LLDP protocol requires encapsulation of MAC / LLDP headers and a general Type-Length-Value (TLV) format, there is a lot of redundant information in the encapsulation format. Therefore, the MTNP OAM extension method can be used. Figure 11 is a schematic diagram of an OAM code block format provided by related technologies; Figure 12 is a schematic diagram of an OAM extended code block format provided by an embodiment of this application. As shown in Figure 12, a new OAM type is defined. The new OAM extended code block contains a node identifier and an MTNP identifier. MTN network nodes send their own node identifier and MTNP identifier in the MTNP OAM, and simultaneously receive the node identifier and MTNP identifier sent by the peer, thus forming a neighbor connection and obtaining neighbor information.

[0153] Network topology information collection and reporting: All MTN network nodes report all neighbor information (local node identifier, local MTNP identifier, peer node identifier, peer MTNP identifier) ​​obtained by this node to their corresponding SNC (subnet controller) via the PCEP-LS protocol. The SNC constructs the network topology information within the subnet based on the neighbor information reported by all MTN network nodes. The SNC then reports the subnet boundary topology information to the network global controller in the MTN network via PCEP-LS. Figure 13 is a configuration diagram of an MTNS / MTNP / fgMTNP network layer provided in an embodiment of this application. As shown in Figure 13, assuming that the MTNP layer network topology is constructed based on the MTNS layer network topology in the figure, SNC1 and SNC2 can respectively obtain the MTNP topology of the corresponding subnet area, and the network global controller in the MTN network can obtain the interconnection topology between the two subnets.

[0154] Path Calculation: After receiving a path calculation request, the network global controller in the MTN network performs path calculation based on the constructed subnet interconnection topology. Assuming the path request is AZ, the MTN global controller calculates that the path must pass through the subnet boundary DM (including the first and last nodes, the channel path calculated by the MTN network global controller is ADMZ). The network global controllers within the MTN network respectively request SNC1 and SNC2 to calculate the paths for AD and MZ, ultimately forming a complete end-to-end transmission channel (also known as the channel path) called ADMPZ.

[0155] Channel configuration: Assume that the channel configuration information is distributed using method three described above.

[0156] In an MTN network, the network global controller calculates the path from the first and last nodes plus the subnet boundary as ADMZ. The MTN network global controller then distributes this path to SNC1 and SNC2.

[0157] SNC1 calculates the channel path AD within its subnet area, and the result is AD. Therefore, it sends the path configuration information AD (including the outgoing direction information of D) to the first node A. Node A completes its configuration based on the path configuration information (configuring the fgMTNP in the outgoing direction MTNP of this node and the occupied time slot number, etc., assuming that the outgoing direction MTNP identifier of node A is MTN Client01, and this fgMTNP occupies time slots 1-10 of this MTN Group, here considering that the time slot number is allocated to this node). At the same time, node A sends the path configuration information of this fgMTNP to node D through the GCC overhead of MTN Client01 (note that here the MTNP of AD is directly cross-connected with time slots at node B, and at the MTNP layer, the next hop of node A is D).

[0158] Assuming node D receives the path configuration information of fgMTNP from its own MTN Client01, and the path configuration information indicates that the outgoing direction of node D is MTN Client03, then node D completes its own configuration based on this information (configuring the ingoing time slot of fgMTNP in this node to MTN Client01 time slots 1-10, and the outgoing time slot to MTN Client03 time slots 11-20). At the same time, node D sends the path configuration information of fgMTNP to node M through the GCC overhead of MTN Client03 (note that the path configuration information transmitted here does not include information after node D, only the fgMTNP identifier, bandwidth requirements, etc.).

[0159] SNC2 calculates the path of MZ within its subnet area, resulting in MPZ. Therefore, it sends the path configuration information MPZ to the first node M within the subnet. Node M completes its configuration based on the path configuration information and the information from the MTN Client overhead of node D (the information from the MTN Client overhead of node D is the inbound information of node M, and the path configuration information sent by SNC contains the outbound information of node M). Assuming node M receives information about a specified fgMTNP channel from MTN Client04 with timeslot numbers 11-20, and the outbound MTNP identifier of this node receiving the fgMTNP from SNC is MTN Client02 with outbound timeslot numbers 41-50, then node M configures the timeslot cross-connection relationship between timeslots 11-20 of the inbound MTN Client04 and timeslots 41-50 of the outbound MTN Client02. Meanwhile, node M sends the path configuration information of fgMTNP to node P through the GCC overhead of MTN Client02. Node P performs the same action as node M, continuing to send the path configuration information of fgMTNP to node Z through the MTN Client specified by SNC2. Ideally, node Z should complete the configuration of its own node to establish the transmission channel of the fgMTNP layer.

[0160] This application proposes a control plane architecture and implementation method for an MTN network. The architecture includes one or more network controllers. Each network controller acquires topology information through interaction with network nodes. After calculating the path based on the topology, the network controller distributes the generated path information to the first node along the channel path. Neighbor discovery and signaling interaction between network nodes are achieved based on the MTN frame overhead channel. The method utilizes the in-band OAM code blocks / overhead of the MTN network for neighbor discovery and for transmitting control signaling along the calculated path, thus eliminating the need for extended implementations and deployments of protocols such as LLDP / LMP / IGP / RSVP.

[0161] In one embodiment, FIG14 is a structural block diagram of a transmission channel creation device provided in this application embodiment. This embodiment is applied to a network node. As shown in FIG14, the transmission channel creation device in this embodiment includes: an acquisition module 310, a reporting module 320, and a creation module 330.

[0162] The acquisition module 310 is configured to acquire neighbor information of the local network node; wherein, the neighbor information includes: neighbor node information and connection port information;

[0163] The reporting module 320 is configured to report neighbor information to the network controller;

[0164] Module 330 is created and configured to create a transmission channel by transmitting path configuration information and channel configuration information issued by the network controller and through signaling between network nodes; wherein, the path configuration information is calculated based on the network topology constructed from neighbor information.

[0165] In one embodiment, obtaining the neighbor information of the network node includes one of the following:

[0166] Obtain the neighbor information of this network node at the first network layer;

[0167] Obtain the neighbor information of this network node in the second network layer.

[0168] In one embodiment, obtaining the neighbor information of the network node at the first network layer includes:

[0169] Obtain the first network cost carrying the first network identifier sent by other network nodes adjacent to this network node;

[0170] The first network identifier and the node identifiers of other network nodes are parsed from the first network overhead to obtain the neighbor information of this network node in the first network layer.

[0171] In one embodiment, resolving the first network identifier from the first network overhead includes:

[0172] The first extended message is parsed from the first network overhead, and the first network identifier is parsed from the first extended message; or,

[0173] The first network identifier is obtained directly from the first network overhead.

[0174] In one embodiment, obtaining the neighbor information of the network node at the first network layer includes:

[0175] Obtain the first extended data frame carrying the first network identifier sent by other network nodes adjacent to this network node;

[0176] The first network identifier and the node identifiers of other network nodes are obtained by parsing the first extended data frame, thus obtaining the neighbor information of this network node in the first network layer.

[0177] In one embodiment, obtaining the neighbor information of the current network node at the second network layer includes:

[0178] Obtain the second network overhead carried by the second network identifier sent by other network nodes adjacent to this network node;

[0179] The second network identifier and the node identifiers of other network nodes are parsed from the second network overhead to obtain the neighbor information of this network node in the second network layer.

[0180] In one embodiment, resolving the second network identifier from the second network overhead includes:

[0181] The first extended message is parsed from the second network overhead, and the second network identifier is parsed from the first extended message; or,

[0182] The second network identifier is obtained directly from the second network overhead.

[0183] In one embodiment, obtaining the neighbor information of the current network node at the second network layer includes:

[0184] Obtain the first extended data frame carrying the second network identifier sent by other network nodes adjacent to this network node;

[0185] The second network identifier and the node identifiers of other network nodes are obtained by parsing the first extended data frame, thus obtaining the neighbor information of this network node in the second network layer.

[0186] In one embodiment, the network controller includes: a network global controller; and the ability to create a transmission channel by transmitting path configuration information and channel configuration information issued by the network controller and through signaling between network nodes, including:

[0187] Receive path configuration information and channel configuration information issued by the network global controller;

[0188] Perform time slot cross-connection and path configuration according to path configuration information and channel configuration information;

[0189] The path configuration information and channel configuration information are sent to the next network node, and the steps of time slot cross-configuration and path configuration according to the path configuration information and channel configuration information are returned until the transmission reaches the last network node, thus obtaining an end-to-end transmission channel.

[0190] In one embodiment, the network controller includes: a global network controller and at least two subnet controllers; the creation of a transmission channel is completed according to the path configuration information and channel configuration information issued by the network controller, and through signaling transmission between network nodes, including:

[0191] The first type of network node receives subnet boundary channel configuration information, path configuration information, and channel configuration information issued by the corresponding subnet controller; wherein, each subnet controller receives path configuration information, subnet boundary channel configuration information, and channel configuration information issued by the global network controller; the first type of network node is the first network node in the subnet to which each subnet controller belongs;

[0192] The first type of network node sends the subnet boundary channel configuration information, path configuration information, and channel configuration information to the second type of network node in the subnet on the corresponding channel path, thereby creating an end-to-end transmission channel within the corresponding subnet; wherein, the second type of network node is not the first network node in the subnet to which the subnet controller belongs.

[0193] In one embodiment, the network controller includes: a global network controller, a first-type subnet controller, and at least one second-type subnet controller; the creation of a transmission channel is completed according to the path configuration information and channel configuration information issued by the network controller, and through signaling transmission between network nodes, including:

[0194] Each type of network node receives subnet boundary channel configuration information, path configuration information, and channel configuration information from the corresponding type of subnet controller or type of subnet controller. Specifically, each type of subnet controller receives path configuration information, subnet boundary channel configuration information, and channel configuration information from the network global controller; each type of subnet controller receives subnet boundary channel configuration information, path configuration information, and channel configuration information from the type of subnet controller; and each type of network node is the first network node in the subnet to which each subnet controller belongs.

[0195] The first type of network node sends the subnet boundary channel configuration information, path configuration information, and channel configuration information to the second type of network node in the subnet on the corresponding channel path, thereby creating an end-to-end transmission channel within the corresponding subnet; wherein, the second type of network node is not the first network node in the subnet to which the subnet controller belongs.

[0196] In one embodiment, the network controller includes: a global network controller and at least two subnet controllers; the creation of a transmission channel is completed according to the path configuration information and channel configuration information issued by the network controller, and through signaling transmission between network nodes, including:

[0197] The first type of network node receives path configuration information and channel configuration information issued by the subnet controller; wherein, each subnet controller receives subnet boundary channel configuration information issued by the global network controller; the first type of network node is the first network node in the subnet to which each subnet controller belongs; the path configuration information is determined by the subnet controller associated with the first type of network node based on network topology information and service requirement information;

[0198] The first type of network node sends the subnet boundary channel configuration information, path configuration information, and channel configuration information to the second type of network node in the subnet on the corresponding channel path, thereby creating an end-to-end transmission channel within the corresponding subnet; wherein, the second type of network node is not the first network node in the subnet to which the subnet controller belongs.

[0199] In one embodiment, the channel configuration information includes at least one of the following: channel identifier; timeslot information; bandwidth information.

[0200] The transmission channel creation device provided in this embodiment is configured to implement the transmission channel creation method applied to network nodes in the embodiment shown in Figure 3. The implementation principle and technical effect of the transmission channel creation device provided in this embodiment are similar, and will not be described again here.

[0201] In one embodiment, FIG15 is a structural block diagram of another transmission channel creation apparatus provided in this application embodiment. This embodiment is applied to a network controller. As shown in FIG15, the transmission channel creation apparatus in this embodiment includes: a receiving module 410, a determining module 420, and a sending module 430.

[0202] The receiving module is configured to receive neighbor information reported by network nodes; wherein the neighbor information includes: neighbor node information and connection port information;

[0203] The module is configured to construct network topology information based on neighbor information, and determine path configuration information based on network topology information and service requirements information;

[0204] The sending module is configured to send path configuration information and channel configuration information to network nodes.

[0205] In one embodiment, the channel configuration information includes at least one of the following: channel identifier; timeslot information; bandwidth information.

[0206] In one embodiment, receiving neighbor information reported by a network node includes one of the following:

[0207] Receive neighbor information reported by network nodes at the first network layer;

[0208] Receive neighbor information reported by network nodes at the second network layer.

[0209] In one embodiment, the method for obtaining neighbor information at the first network layer includes:

[0210] By obtaining the first network overhead carrying the first network identifier sent by other network nodes adjacent to this network node;

[0211] The first network identifier and the node identifiers of other network nodes are parsed from the first network overhead to obtain the neighbor information of this network node in the first network layer.

[0212] In one embodiment, resolving the first network identifier from the first network overhead includes:

[0213] The first extended message is parsed from the first network overhead, and the first network identifier is parsed from the first extended message; or,

[0214] The first network identifier is obtained directly from the first network overhead.

[0215] In one embodiment, the method for obtaining neighbor information at the first network layer includes:

[0216] Obtain the first extended data frame carrying the first network identifier sent by other network nodes adjacent to this network node;

[0217] The first network identifier and the node identifiers of other network nodes are obtained by parsing the first extended data frame, thus obtaining the neighbor information of this network node in the first network layer.

[0218] In one embodiment, the method for obtaining neighbor information at the second network layer includes:

[0219] Obtain the second network overhead carried by the second network identifier sent by other network nodes adjacent to this network node;

[0220] The second network identifier and the node identifiers of other network nodes are parsed from the second network overhead to obtain the neighbor information of this network node in the second network layer.

[0221] In one embodiment, resolving the second network identifier from the second network overhead includes:

[0222] The first extended message is parsed from the second network overhead, and the second network identifier is parsed from the first extended message; or,

[0223] The second network identifier is obtained directly from the second network overhead.

[0224] In one embodiment, the method for obtaining neighbor information at the second network layer includes:

[0225] Obtain the first extended data frame carrying the second network identifier sent by other network nodes adjacent to this network node;

[0226] The second network identifier and the node identifiers of other network nodes are obtained by parsing the first extended data frame, thus obtaining the neighbor information of this network node in the second network layer.

[0227] In one embodiment, the network controller includes: a network global controller; network nodes create transmission channels based on path configuration information and channel configuration information, and through signaling transmission between network nodes, including:

[0228] Receive path configuration information and channel configuration information issued by the network global controller through network nodes;

[0229] Time slot cross-configuration and path configuration are performed through network nodes according to path configuration information and channel configuration information;

[0230] The path configuration information and channel configuration information are sent from one network node to the next, and the steps of time slot cross-configuration and path configuration according to the path configuration information and channel configuration information are returned until the transmission reaches the last network node, thus obtaining an end-to-end transmission channel.

[0231] In one embodiment, the network controller includes: a global network controller and at least two subnet controllers; network nodes create transmission channels based on path configuration information and channel configuration information, and through signaling transmission between network nodes, including:

[0232] The first type of network node receives subnet boundary channel configuration information, path configuration information, and channel configuration information issued by the corresponding subnet controller; wherein, each subnet controller receives path configuration information, subnet boundary channel configuration information, and channel configuration information issued by the global network controller; the first type of network node is the first network node in the subnet to which each subnet controller belongs;

[0233] The first type of network node sends the subnet boundary channel configuration information, path configuration information, and channel configuration information to the second type of network node in the subnet on the corresponding channel path, thereby creating an end-to-end transmission channel within the corresponding subnet; wherein, the second type of network node is not the first network node in the subnet to which the subnet controller belongs.

[0234] In one embodiment, the network controller includes: a network global controller, a first type subnet controller, and at least one second type subnet controller; network nodes create transmission channels based on path configuration information and channel configuration information, and through signaling transmission between network nodes, including:

[0235] Each type of network node receives subnet boundary channel configuration information, path configuration information, and channel configuration information from the corresponding type of subnet controller or type of subnet controller. Specifically, each type of subnet controller receives path configuration information, subnet boundary channel configuration information, and channel configuration information from the network global controller; each type of subnet controller receives subnet boundary channel configuration information, path configuration information, and channel configuration information from the type of subnet controller; and each type of network node is the first network node in the subnet to which each subnet controller belongs.

[0236] The first type of network node sends the subnet boundary channel configuration information, path configuration information, and channel configuration information to the second type of network node in the subnet on the corresponding channel path, thereby creating an end-to-end transmission channel within the corresponding subnet; wherein, the second type of network node is not the first network node in the subnet to which the subnet controller belongs.

[0237] In one embodiment, the network controller includes: a global network controller and at least two subnet controllers; network nodes create transmission channels based on path configuration information and channel configuration information, and through signaling transmission between network nodes, including:

[0238] The first type of network node receives path configuration information and channel configuration information issued by the subnet controller; wherein, each subnet controller receives subnet boundary channel configuration information issued by the global network controller; the first type of network node is the first network node in the subnet to which each subnet controller belongs; the path configuration information is determined by the subnet controller associated with the first type of network node based on network topology information and service requirement information;

[0239] The first type of network node sends the subnet boundary channel configuration information, path configuration information, and channel configuration information to the second type of network node in the subnet on the corresponding channel path, thereby creating an end-to-end transmission channel within the corresponding subnet; wherein, the second type of network node is not the first network node in the subnet to which the subnet controller belongs.

[0240] The transmission channel creation device provided in this embodiment is configured to implement the transmission channel creation method applied to network nodes in the embodiment shown in Figure 4. The implementation principle and technical effect of the transmission channel creation device provided in this embodiment are similar, and will not be described again here.

[0241] In one embodiment, FIG16 is a schematic diagram of a communication device provided in an embodiment of this application. As shown in FIG16, the device provided in this application includes: a processor 1610, a memory 1620, and a communication module 1630. The number of processors 1610 in the device can be one or more; FIG16 shows one processor 1610 as an example. The number of memories 1620 in the device can be one or more; FIG16 shows one memory 1620 as an example. The processor 1610, memory 1620, and communication module 1630 of the device can be connected via a bus or other means; FIG16 shows a connection via a bus as an example. In this embodiment, the device can be a network node or a network controller.

[0242] The memory 1620, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the device in any embodiment of this application (e.g., the acquisition module 310, reporting module 320, and creation module 330 in a transmission channel creation device for a network node, or the receiving module 410, determining module 420, and sending module 430 in a transmission channel creation device for a network controller). The memory 1620 may include a program storage area and a data storage area, wherein the program storage area may store the operating system and at least one application program required for a function; the data storage area may store data created according to the use of the device, etc. Furthermore, the memory 1620 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 1620 may further include memory remotely located relative to the processor 1610, and these remote memories can be connected to the device via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0243] When the communication device is a network node, the device provided above can be configured to execute the method for creating a transmission channel for a network node provided in any of the above embodiments, and has the corresponding functions and effects.

[0244] When the communication device is a network controller, the device provided above can be configured to execute the method for creating a transmission channel for a network controller provided in any of the above embodiments, and has the corresponding functions and effects.

[0245] This application embodiment also provides a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to execute a method for creating a transmission channel applied to a network node. The method includes: obtaining neighbor information of the network node; reporting the neighbor information to the network controller; and completing the creation of the transmission channel according to the path configuration information and channel configuration information issued by the network controller and through signaling transmission between network nodes. The path configuration information is calculated based on the network topology constructed from the neighbor information.

[0246] This application embodiment also provides a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to execute a method for creating a transmission channel applied to a network controller. The method includes: receiving neighbor information reported by network nodes; wherein the neighbor information includes: neighbor node information and connection port information; constructing network topology information based on the neighbor information, and determining path configuration information based on the network topology information and service requirement information; and sending the path configuration information and channel configuration information to the network nodes; wherein the network nodes complete the creation of the transmission channel based on the path configuration information and the channel configuration information.

[0247] Those skilled in the art will understand that the term user equipment covers any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.

[0248] Generally, the various embodiments of this application can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although this application is not limited thereto.

[0249] Embodiments of this application can be implemented by executing computer program instructions through the data processor of a mobile device, for example, in a processor entity, or through hardware, or through a combination of software and hardware. The computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0250] Any block diagram of logical flow in the accompanying drawings of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored on memory. Memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (Digital Video Disc (DVD) or Compact Disk (CD)), etc. Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable to the local technical environment, such as, but not limited to, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and processors based on multi-core processor architectures.

[0251] This application also provides a computer program product, including a computer program that, when executed by a processor, can implement the method for creating a transmission channel as provided in any embodiment of this application.

[0252] In the implementation of the computer program product, computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0253] The above are merely optional embodiments of this application and are not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for creating a transmission channel, applied to network nodes in a network architecture, comprising: Obtain the neighbor information of this network node; wherein, the neighbor information includes: neighbor node information and connection port information; The neighbor information is reported to the network controller; The transmission channel is created by transmitting the path configuration information and channel configuration information issued by the network controller and through signaling between network nodes; wherein the path configuration information is calculated based on the network topology constructed from the neighbor information.

2. The method according to claim 1, wherein, Obtaining the neighbor information of this network node includes one of the following: Obtain the neighbor information of this network node at the first network layer; Obtain the neighbor information of this network node in the second network layer.

3. The method according to claim 2, wherein, The step of obtaining the neighbor information of this network node at the first network layer includes: Obtain the first network cost carrying the first network identifier sent by other network nodes adjacent to this network node; The first network identifier and the node identifiers of the other network nodes are parsed from the first network overhead to obtain the neighbor information of this network node in the first network layer.

4. The method according to claim 3, wherein, The step of parsing the first network identifier from the first network overhead includes: The first extended message is parsed from the first network overhead, and the first network identifier is parsed from the first extended message; or, The first network identifier is obtained directly from the first network overhead.

5. The method according to claim 2, wherein, The step of obtaining the neighbor information of this network node at the first network layer includes: Obtain the first extended data frame carrying the first network identifier sent by other network nodes adjacent to this network node; The first network identifier and the node identifiers of the other network nodes are obtained by parsing the first extended data frame, and the neighbor information of this network node in the first network layer is obtained.

6. The method according to claim 2, wherein, The process of obtaining the neighbor information of this network node at the second network layer includes: Obtain the second network overhead carried by the second network identifier sent by other network nodes adjacent to this network node; The second network identifier and the node identifiers of the other network nodes are parsed from the second network overhead to obtain the neighbor information of this network node in the second network layer.

7. The method according to claim 6, wherein, The step of parsing the second network identifier from the second network overhead includes: The first extended message is parsed from the second network overhead, and the second network identifier is parsed from the first extended message; or, The second network identifier is obtained directly from the second network overhead.

8. The method according to claim 2, wherein, The process of obtaining the neighbor information of this network node at the second network layer includes: Obtain the first extended data frame carrying the second network identifier sent by other network nodes adjacent to this network node; The second network identifier and the node identifiers of the other network nodes are obtained by parsing the first extended data frame, thus obtaining the neighbor information of this network node in the second network layer.

9. The method according to claim 1, wherein, The network controller includes: a network global controller; the creation of the transmission channel according to the path configuration information and channel configuration information issued by the network controller, and through signaling transmission between network nodes, includes: Receive path configuration information and channel configuration information issued by the network global controller; Perform time slot crossover configuration and path configuration according to the path configuration information and the channel configuration information; The path configuration information and the channel configuration information are sent to the next network node, and the time slot cross-configuration and path configuration are performed according to the path configuration information and the channel configuration information until the transmission reaches the last network node, thus obtaining an end-to-end transmission channel.

10. The method according to claim 1, wherein, The network controller includes: a global network controller and at least two subnet controllers; the creation of the transmission channel according to the path configuration information and channel configuration information issued by the network controller, and through signaling transmission between network nodes, includes: The first type of network node receives subnet boundary channel configuration information, path configuration information, and channel configuration information issued by the corresponding subnet controller; wherein, each subnet controller receives path configuration information, subnet boundary channel configuration information, and channel configuration information issued by the network global controller; the first type of network node is the first network node in the subnet to which each subnet controller belongs; The first type of network node sends the subnet boundary channel configuration information, the path configuration information, and the channel configuration information to the second type of network node in the subnet on the corresponding channel path, thereby creating an end-to-end transmission channel within the corresponding subnet; wherein, the second type of network node is not the first network node in the subnet to which the subnet controller belongs.

11. The method according to claim 1, wherein, The network controller includes: a global network controller, a first-type subnet controller, and at least one second-type subnet controller; the creation of the transmission channel according to the path configuration information and channel configuration information issued by the network controller, and through signaling transmission between network nodes, includes: The first type of network node receives subnet boundary channel configuration information, path configuration information, and channel configuration information issued by the corresponding first type of subnet controller or second type of subnet controller; wherein, the first type of subnet controller receives path configuration information, subnet boundary channel configuration information, and channel configuration information issued by the network global controller; each second type of subnet controller receives subnet boundary channel configuration information, path configuration information, and channel configuration information issued by the first type of subnet controller; the first type of network node is the first network node in the subnet to which each subnet controller belongs; The first type of network node sends the subnet boundary channel configuration information, the path configuration information, and the channel configuration information to the second type of network node in the subnet on the corresponding channel path, thereby creating an end-to-end transmission channel within the corresponding subnet; wherein, the second type of network node is not the first network node in the subnet to which the subnet controller belongs.

12. The method according to claim 1, wherein, The network controller includes: a global network controller and at least two subnet controllers; the creation of the transmission channel according to the path configuration information and channel configuration information issued by the network controller, and through signaling transmission between network nodes, includes: The first type of network node receives path configuration information and channel configuration information issued by the subnet controller; wherein, each subnet controller receives subnet boundary channel configuration information issued by the network global controller; the first type of network node is the first network node in the subnet to which each subnet controller belongs; the path configuration information is determined by the subnet controller associated with the first type of network node based on network topology information and service requirement information; The first type of network node sends the subnet boundary channel configuration information, the path configuration information, and the channel configuration information to the second type of network node in the subnet on the corresponding channel path, thereby creating an end-to-end transmission channel within the corresponding subnet; wherein, the second type of network node is not the first network node in the subnet to which the subnet controller belongs.

13. The method according to any one of claims 1-12, wherein, The channel configuration information includes at least one of the following: channel identifier; time slot information; bandwidth information.

14. A method for creating a transmission channel, applied to a network controller in a network architecture, comprising: Receive neighbor information reported by network nodes; wherein, the neighbor information includes: neighbor node information and connection port information; Network topology information is constructed based on the neighbor information, and path configuration information is determined based on the network topology information and service requirement information; The path configuration information and channel configuration information are sent to the network node; wherein, the network node completes the creation of the transmission channel based on the path configuration information and the channel configuration information.

15. A communication device, comprising: Memory, and one or more processors; The memory is configured to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors perform the method as described in any one of claims 1-13 or 14.

16. A storage medium storing a computer program that, when executed by a processor, implements the method as described in any one of claims 1-13 or 14.

Images