WO2024001370A1 - 细粒度能力的洪泛方法、细粒度的配置方法，节点及介质 - Google Patents

细粒度能力的洪泛方法、细粒度的配置方法，节点及介质 Download PDF

Info

Publication number
WO2024001370A1
WO2024001370A1 PCT/CN2023/085692 CN2023085692W WO2024001370A1 WO 2024001370 A1 WO2024001370 A1 WO 2024001370A1 CN 2023085692 W CN2023085692 W CN 2023085692W WO 2024001370 A1 WO2024001370 A1 WO 2024001370A1
Authority
WO
WIPO (PCT)
Prior art keywords
fine
grained
client
network
interface
Prior art date
Application number
PCT/CN2023/085692
Other languages
English (en)
French (fr)
Inventor
周瑾
王其磊
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2024001370A1 publication Critical patent/WO2024001370A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/32—Flooding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery

Definitions

  • This application relates to the field of communication technology, for example, to flooding methods of fine-grained capabilities, fine-grained configuration methods, nodes and media.
  • MTN metro transport network
  • OTN optical transport network
  • the embodiment of the present application provides a fine-grained capability flooding method, which is suitable for communication nodes that support fine-grained capabilities.
  • the method includes:
  • the fine-grained interface information includes fine-grained interface switching capability description information.
  • the fine-grained interface switching capability description information includes fine-grained interface switching capabilities, fine-grained encoding types and fine-grained timing. gap particle size.
  • the embodiment of this application provides a fine-grained configuration method, which is suitable for communication nodes that support fine-grained capabilities.
  • the method includes:
  • the fine-grained path is used to transmit low-rate services.
  • the fine-grained information is used to instruct the communication node located on the fine-grained path to allocate fine-grained resources;
  • An embodiment of the present application provides a communication node, including: a processor; the processor is configured to implement the method of any of the above embodiments when executing a computer program.
  • Embodiments of the present application also provide a computer-readable storage medium that stores a computer program.
  • the computer program is executed by a processor, the method of any of the above embodiments is implemented.
  • Figure 1 is a schematic diagram of a network of a communication system provided by an embodiment
  • Figure 2 is a schematic diagram of a communication interface for transmitting services provided by an embodiment
  • Figure 3 is a schematic flowchart of a fine-grained capability flooding method provided by an embodiment
  • FIG. 4 is a schematic diagram of a TLV carrying fine-grained interface exchange capability description information provided by an embodiment
  • FIG. 5 is a schematic diagram of another TLV carrying fine-grained interface exchange capability description information provided by an embodiment
  • FIG. 6 is a schematic diagram of a TLV carrying fine-grained interface exchange capability specific information provided by an embodiment
  • Figure 7 is a schematic flowchart of a fine-grained configuration method provided by an embodiment
  • Figure 8 is an architectural diagram between a management and control system and a forwarding network element provided in an embodiment
  • Figure 9 is a schematic structural diagram of a flooding device with fine-grained capabilities provided by an embodiment
  • Figure 10 is a schematic structural diagram of a fine-grained configuration method device provided by an embodiment
  • Figure 11 is a schematic structural diagram of a communication node provided by an embodiment.
  • Slicing packet network is a new generation of converged bearer network architecture for the fifth generation communication system (5th generation, 5G). It has the advantages of low latency, large bandwidth, ultra-high precision synchronization, and flexible management and control. Among them, the slicing channel layer (SCL) is MTN. Flexible Ethernet (FlexE) technology time slot crossing based on Time Division Multiplexing (TDM) realizes 5Gbps granular slicing technology, which has initially met the needs of 5G commercial use.
  • FlexE Flexible Ethernet
  • TDM Time Division Multiplexing
  • MTN has proposed fine granularity unit (FGU) technology to refine the granularity of hard slicing from 5Gbps to 10Mbps to meet business scenarios such as 5G+ vertical industry applications and dedicated lines.
  • FGU fine granularity unit
  • OSU optical service unit
  • Figure 1 shows a schematic networking diagram of a communication system provided by an embodiment. As shown in Figure 1, it includes at least one edge node, such as E1 and E2 in Figure 1, and may also include at least one intermediate node (also called a forwarding node or routing node), such as P1, P2, and Pn in Figure 1.
  • edge node such as E1 and E2 in Figure 1
  • intermediate node also called a forwarding node or routing node
  • FIG. 1 shows a schematic diagram of a communication interface of a transmission service provided by an embodiment.
  • a method of flooding fine-grained capabilities, a fine-grained configuration method, nodes and media that can run on the above communication system are provided, which can flood the fine-grained capabilities of links and achieve fine-grained unification. Management and control to meet the fine-grained processing capabilities of forwarding plane interfaces of different forwarding technologies.
  • Figure 3 shows a schematic flow chart of a fine-grained capability flooding method provided by an embodiment. As shown in Figure 3, the method provided by this embodiment is suitable for communication nodes (also called nodes) that support fine-grained capabilities. ). The method includes the following steps.
  • the fine-grained interface information includes fine-grained interface switching capability description information.
  • the fine-grained interface switching capability description information includes fine-grained interface switching capability, fine-grained encoding type and fine-grainedness. time slot granularity.
  • ITU-T International Telecommunications Union Telecommunications Standardization Sector
  • MTN and OTN can serve as the service layer of the sub-1G network layer and provide hard pipe services for sub-1G customers.
  • the fine-grained interface switching capability description information is located in a sub-TLV (sub-TLV) of the routing protocol link network type-length-value (TLV).
  • each fine-grained traffic engineering link status release carries a top-level link TLV.
  • the top-level link TLV includes the node TLV and the traffic engineering link TLV.
  • the top-level link TLV is included in the package. Contains one or more nested sub-TLVs.
  • this application may exemplarily choose to extend Open Shortest Path First with Traffic Engineering (OSPF-TE) in related technologies.
  • OSPF-TE Open Shortest Path First with Traffic Engineering
  • the fine-grained interface switching capability is the interface switching capability of TDM.
  • TDM types in related technologies such as Synchronous Digital Hierarchy (SDH)
  • SDH Synchronous Digital Hierarchy
  • fine granularity is used as a general TDM interface, which can reuse the TDM interface switching capabilities (such as TDM forwarding capabilities) in related technologies.
  • TDM interface switching capabilities such as TDM forwarding capabilities
  • the fine-grained interface switching capability can directly reuse the interface switching capability with a TDM of 100 defined in RFC4203 in related technologies, or it can also assign a specific TDM value.
  • this application can express the fine-grained encoding type by creating a new comfgu.
  • the fine-grained encoding type is the encoding type of the requested LSP. As described in RFC4328, the LSP encoding type is specified according to the network layer. If the fine-grained requested LSP encoding type is not supported on the interface, the intermediate/egress node MUST generate a path error message with an unsupported encoding indication.
  • setting the Encoding field in comfgu is used to represent fine-grained encoding types.
  • the fine-grained interface switching capability description information can also include fine-grained signal types; the fine-grained signal types are any of FGU based on metropolitan area transmission network MTN technology, OSU based on OTN technology, and sub-1G. item.
  • the SignalType field is set in comfgu to represent fine-grained signal types.
  • the OSU's base rate is 2.6Mb/s. Whether it is a fixed-rate constant bit rate (CBR) service or a service without a fixed rate, the C* base rate can be used, that is, C* 2.6Mb/s, to represent the bit rate of OSU.
  • CBR constant bit rate
  • the MTN FGU is based on a 5Gbps channel, demarcating 480 10M time slots to carry customer signals respectively.
  • the fine-grained interface exchange capability description information also includes fine-grained time slot granularity.
  • setting the Granularity field in comfgu is used to represent fine-grained slot granularity.
  • the fine-grained interface switching capability description information includes fine-grained interface switching capabilities, Fine-grained coding types and fine-grained time slot granularity can also be understood as the TDM interface switching capability supports three types of fine-grained signal types, and the time slot granularity currently supported by each signal type.
  • FIG 4 shows a schematic diagram of a TLV carrying fine-grained interface switching capability description information provided by an embodiment
  • Figure 5 shows another TLV carrying fine-grained interface switching capability description information provided by an embodiment
  • Figure 6 shows a schematic diagram of a TLV carrying fine-grained interface exchange capability specific information provided by an embodiment. From the TLV shown in Figure 4, or combined with the TLV shown in Figure 5 and Figure 6, fine-grained interface switching capability description information can be obtained: fine-grained interface switching capability TDM, fine-grained encoding type, fine-grained signal Type and fine-grained slot granularity.
  • path calculation requires selecting an appropriate route for a fine-grained connection request, in order to facilitate management and control of path calculation, it is necessary for this application to clarify the available bandwidth of each candidate link. That is, extending the routing protocol to support passing enough information to identify fine-grained traffic engineering topology.
  • MTN FGU MTN FGU
  • OSU 10G
  • Operators can deploy policies to freely decide the priorities supported in the network. If priorities are set in the network, all devices that support fine-grained granularity need to comply with different priorities and enter different sorting queues for processing, clarifying the fine-grained links.
  • the maximum available bandwidth on each priority level can be supported individually based on priority.
  • RFC4202 defines the Interface Switching Capability Descriptor (ISCD), which describes the resource availability under eight priority levels and is used to present the constraints of LSP path calculation.
  • ISCD Interface Switching Capability Descriptor
  • each priority level in the network should be published independently of the number of priorities.
  • the maximum LSP bandwidth is published according to priority in ISCD.
  • Fine-grained links with the same rate between a pair of nodes are bundled together and published, and the unreserved bandwidth of the bundled link and the maximum bandwidth of a single LSP supported by the bundled link can be centrally published.
  • the routing protocol is Open Shortest Path First (OSPF) routing protocol, Intermediate System-to-Intermediate System (IS-IS) routing protocol, Border Gateway Protocol-Chain Border Gateway Protocol- Any one of the LinkState (BGP-LS) routing protocol and the Path Computation Element rotocol-LinkState (PCEP-LS) routing protocol.
  • OSPF Open Shortest Path First
  • IS-IS Intermediate System-to-Intermediate System
  • PCEP-LS Path Computation Element rotocol-LinkState
  • RFC5305 describes that one or more IS-IS link state protocol data units can be published in routing information.
  • RFC5307 describes the interface switching capability description of type 21.
  • the fine-grained interface exchange capability description information provided by this application can be used as a type 21 interface capability to describe fine-grained interface capabilities.
  • BGP-LS is a BGP multi-protocol extension that delivers Interior Gateway Protocol (IGP) link status through the BGP protocol. Relevant topology information of multiple IGP domains can be obtained through BGP-LS.
  • the source of link description TLVs in BGP-LS can come from OSPF and IS-IS. Using BGP-LS, you can learn the link state topology during path calculation, but you do not need to know any OSPF or IS-IS protocol-specific information.
  • the fine-grained interface switching capability description information provided by this application can be used as a sub-TLV of an opaque link attribute TLV to describe the fine-grained interface capabilities at both ends of the link.
  • fine-grained interface switching capability description information can also be applied to the extended link attribute TLV in the PCEP-LS extension described in draft-dhodylee-pce-pcep-ls-23, as a
  • the fine-grained interface exchange capability TLV for specific applications is used to complete the interaction of fine-grained interface capabilities between the device and the PCE.
  • Figure 7 shows a schematic flowchart of a fine-grained configuration method provided by an embodiment. As shown in Figure 7, the method provided by this embodiment is suitable for communication nodes that support fine-grained capabilities. The method includes the following steps.
  • the fine-grained path is used to transmit low-rate services.
  • the fine-grained information is used to instruct the communication node located on the fine-grained path to allocate fine-grained resources.
  • S220 Configure communication nodes according to fine-grained information.
  • Fine-grained information can also be understood as a fine-grained processing capability model, which is modeled directly at the OTN OSU network level or MTN FGU level.
  • the fine-grained information includes: fine-grained client identification code client-id, client layer type, mapping method, customer requirements, fine-grained signal type, fine-grained granularity, at least one of the service layer interfaces item.
  • the fine-grained client-id is the current fine-grained time slot allocation identifier
  • the fine-grained client-id is used to indicate that the time slot is allocated according to the client-id in MTN technology, or is used to indicate that the time slot is allocated based on the tributary port number TPN in OSU technology, or is used to indicate that the time slot is allocated based on the client in sub-1G Identifies the allocated time slot.
  • the fine-grained client-id occupies two bytes, and the first 12 bits of the two bytes are valid bits.
  • the fine-grained signal type is any one of FGU based on MTN technology, OSU based on OTN technology, and sub-1G.
  • the fine-grained granularity can be configured according to actual requirements, for example, the fine-grained granularity is 2.6M or 10M.
  • client-type represents the current fine-grained client layer message type, that is, the payload identifier carried by the fine-grained LSP, indicating whether it is a standard Ethernet service or a service type such as CBR;
  • mapping-type represents It is the way in which upper-layer services are mapped to fine-grained network messages. It currently includes bit-synchronous mapping procedure (BMP), general mapping procedure (Generic mapping procedure, GMP) and idle mapping procedure (Idle).
  • BMP requires the customer's clock to be synchronized with the device's clock.
  • GMP is usually used for CBR services.
  • IMP can be used for Ethernet services of packet switching technology; client-demand represents the current business requirements, which can include bandwidth requirements.
  • time slot allocation requirements where the time slot allocation requirements may include information such as a delay requirement flag and whether a two-way delay difference is required.
  • the fine-grained configuration method further includes: receiving service request information.
  • the service request information includes service requirements carried by the current fine-grained network.
  • the service requirements include at least one of bandwidth requirements and time slot allocation requirements.
  • the time slots The allocation requirement includes at least one of a delay requirement flag and whether a two-way delay difference is required.
  • the fine-grained configuration method is applicable to the southbound NETCONF protocol between the communication node and the network management device, or to the path calculation unit protocol PCEP between the circuit calculation unit and the network element.
  • Fine-grained networks generally deploy centralized and distributed management and control architectures that coexist.
  • the network element can support the flooding method of fine-grained capabilities in the above embodiment, and the flooded fine-grained interface information is reported to the centralized management and control system.
  • the management and control system maintains fine-grained topology and completes centralized path calculation.
  • the path calculation results can be converted into multiple comfgu-client information in the above embodiments and delivered to each forwarding node on the connection, or can be delivered only to the entry node, which will deliver it according to the centralized management and control system.
  • the path information is used to complete connection establishment and resource reservation.
  • FIG. 8 shows an architectural diagram between a management and control system and a forwarding network element provided in an embodiment. As shown in Figure 8, two modules, fine-grained topology management and fine-grained path calculation, are deployed in the management and control system, and two modules, resource allocation and route flooding, are deployed in the forwarding network element.
  • Figure 9 shows a schematic structural diagram of a fine-grained capability flooding device provided by an embodiment.
  • the device can be configured in a communication node.
  • the device includes: a flooding module 10.
  • the flooding module 10 is configured to flood the fine-grained interface information of the communication node.
  • the fine-grained interface information includes fine-grained interface switching capability description information.
  • the fine-grained interface switching capability description information includes fine-grained interface switching capabilities, fine-grained Encoding type and fine-grained slot granularity.
  • the fine-grained capability flooding device provided by this embodiment is a flooding method for realizing the fine-grained capability of the embodiment shown in Figure 3.
  • the implementation principles and technical effects of the fine-grained capability flooding device provided by this embodiment are the same as those of the above-mentioned embodiments. Similar, will not be repeated here.
  • the fine-grained interface exchange capability description information also includes fine-grained signal types
  • the fine-grained signal type is any of the small granular unit FGU based on the metropolitan area transmission network MTN technology, the optical service unit OSU based on the optical transport network OTN technology, or the general sub-1G with a bandwidth below 1G.
  • the fine-grained interface switching capability is the interface switching capability of time division multiplexing TDM.
  • the fine-grained interface switching capability description information is located in a sub-network type-length-value sub-TLV of the routing protocol link network type-length-value TLV.
  • the routing protocol is Open Shortest Path First OSPF routing protocol, intermediate system To any one of the intermediate system IS-IS routing protocol, border gateway protocol-link state BGP-LS routing protocol, and path calculation unit protocol-link state PCEP-LS routing protocol.
  • Figure 10 shows a schematic structural diagram of a fine-grained configuration method device provided by an embodiment.
  • the device can be configured in a communication node.
  • the device includes: an acquisition module 20 and a configuration module 21.
  • the acquisition module 20 is configured to obtain fine-grained information on the fine-grained path, the fine-grained path is used to transmit low-rate services, and the fine-grained information is used to instruct the communication node located on the fine-grained path to allocate fine-grained resources;
  • the configuration module 21 is configured to configure communication nodes according to fine-grained information.
  • the fine-grained configuration device provided by this embodiment is to implement the fine-grained configuration method of the embodiment shown in Figure 7.
  • the implementation principles and technical effects of the fine-grained configuration device provided by this embodiment are similar to those of the above embodiment, and will not be discussed here. Repeat.
  • the fine-grained information includes: fine-grained client identification code client-id, client layer type, mapping method, customer requirements, fine-grained signal type, fine-grained granularity, at least one of the service layer interfaces item.
  • the fine-grained client-id is the current fine-grained time slot allocation identifier
  • the fine-grained client-id is used to indicate that the time slot is allocated according to the client-id in MTN technology, or is used to indicate that the time slot is allocated based on the tributary port number TPN in OSU technology, or is used to indicate that the time slot is allocated based on the client in sub-1G Identifies the allocated time slot.
  • the fine-grained client-id occupies two bytes, and the first 12 bits of the two bytes are valid bits.
  • the acquisition module 20 is further configured to receive service request information.
  • the service request information includes the service requirements carried by the current fine-grained network.
  • the service requirements include at least one of bandwidth requirements and time slot allocation requirements.
  • the time slot allocation requirements include at least one of a delay requirement flag and whether a two-way delay difference is required.
  • the method is applicable to the southbound NETCONF protocol between the communication node and the network management device, or to the path calculation unit protocol PCEP between the path calculation unit and the network element.
  • FIG. 11 shows a schematic structural diagram of a communication node provided by an embodiment.
  • the communication node includes a processor 60, a memory 61 and a communication interface 62; the number of processors 60 in the communication node can be one or more,Fig.
  • a processor 60 is taken as an example; the processor 60, memory 61, and communication interface 62 in the communication node can be connected through a bus or other means.
  • the connection through a bus is taken as an example.
  • a bus represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of a variety of bus structures.
  • the memory 61 can be configured to store software programs, computer-executable programs and modules, such as program instructions/modules corresponding to the methods in the embodiments of the present application.
  • the processor 60 executes software programs, instructions and modules stored in the memory 61 to execute at least one functional application and data processing of the communication node, that is, to implement the above method.
  • the memory 61 may include a program storage area and a data storage area, where the program storage area may store an operating system and an application program required for at least one function; the storage data area may store data created according to the use of the terminal, etc.
  • the memory 61 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device.
  • memory 61 may include memory located remotely relative to processor 60, and these remote memories may be connected to communication nodes through a network. Examples of the above-mentioned networks include but are not limited to the Internet, intranets, networks, mobile communication networks and combinations thereof.
  • the communication interface 62 may be configured to receive and send data.
  • Embodiments of the present application also provide a computer-readable storage medium.
  • a computer program is stored on the computer-readable storage medium.
  • the computer program is executed by a processor, the method provided by any embodiment of the present application is implemented.
  • the computer storage medium in the embodiment of the present application may be any combination of one or more computer-readable media.
  • the computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium.
  • the computer-readable storage medium may be, for example, but not limited to: an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination thereof.
  • Computer-readable storage media include (non-exhaustive list): electrical connections having one or more conductors, portable computer disks, hard drives, random access memory (RAM), read-only memory (Read-Only Memory) , ROM), electrically erasable, programmable Read-Only Memory (EPROM), flash memory, optical fiber, portable compact disk read-only memory (Compact Disc Read-Only Memory, CD-ROM), optical storage components, magnetic storage devices, or any suitable combination of the above.
  • a computer-readable storage medium may be any tangible medium that contains or stores a program for use by or in connection with an instruction execution system, apparatus, or device.
  • a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, the data signal carrying computer-readable program code. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above.
  • a computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device .
  • Computer program code for performing operations of the present disclosure may be written in one or more programming languages, or a combination of programming languages, including object-oriented programming languages such as Java, Smalltalk, C++, Ruby, Go), and also includes conventional procedural programming languages (such as the "C" language or similar programming languages).
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer can be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or it can be connected to an external computer (e.g. Use an Internet service provider to connect via the Internet).
  • LAN Local Area Network
  • WAN Wide Area Network
  • user terminal covers any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser or a vehicle-mounted mobile station.
  • the various embodiments of the present application may be implemented in hardware or special purpose circuitry, software, logic, or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, although the application is not limited thereto.
  • Embodiments of the present application may be implemented by a data processor of the mobile device executing computer program instructions, for example in a processor entity, or by hardware, or by a combination of software and hardware.
  • Computer program instructions may be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages source code or object code.
  • ISA Instruction Set Architecture
  • Any block diagram of a logic flow in the figures 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.
  • Computer programs can be stored on memory.
  • the memory may be of any type appropriate 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 versatile discs, DVDs or CDs), etc.
  • Computer-readable media may include non-transitory storage media.
  • the data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (Digital Signal Processing, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC ), programmable logic devices (Field-Programmable Gate Array, FGPA) and processors based on multi-core processor architecture.
  • DSP Digital Signal Processing
  • ASIC Application Specific Integrated Circuit
  • FGPA programmable logic devices

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Communication Control (AREA)

Abstract

本申请公开了细粒度能力的洪泛方法、细粒度的配置方法，节点及介质。细粒度能力的洪泛方法包括：洪泛通信节点的细粒度接口信息，细粒度接口信息包括细粒度的接***换能力描述信息，细粒度的接***换能力描述信息包括细粒度的接***换能力、细粒度的编码类型和细粒度的时隙颗粒度(S110)。

Description

细粒度能力的洪泛方法、细粒度的配置方法，节点及介质 技术领域
本申请涉及通信技术领域，例如涉及细粒度能力的洪泛方法、细粒度的配置方法，节点及介质。
背景技术
大量小带宽、软硬隔离结合、确定性低时延、高安全和高可靠的承载需求的不断出现，使得城域传输网络(metro transport network，MTN)技术和光传送网(optical transport network，OTN)技术面向带宽较小而且需要随时灵活调整的高效承载方案的研究趋于迫切。其中，如何部署面向细粒度的统一管控以满足不同转发技术的转发面接口细粒度处理能力成为了当前亟需解决的问题。
发明内容
本申请实施例提供一种细粒度能力的洪泛方法，适用于支持细粒度能力的通信节点，方法包括：
洪泛通信节点的细粒度接口信息，细粒度接口信息包括细粒度的接***换能力描述信息，细粒度的接***换能力描述信息包括细粒度的接***换能力、细粒度的编码类型和细粒度的时隙颗粒度。
本申请实施例提供一种细粒度的配置方法，适用于支持细粒度能力的通信节点，方法包括：
获取细粒度路径上的细粒度信息，细粒度路径用于传输低速率业务，细粒度信息用于指示位于细粒度路径上的通信节点分配细粒度资源；
根据细粒度信息，配置通信节点。
本申请实施例提供一种通信节点，包括：处理器；处理器用于在执行计算机程序时实现上述任一实施例的方法。
本申请实施例还提供一种计算机可读存储介质，存储有计算机程序，计算机程序被处理器执行时实现上述任一实施例的方法。
关于本申请的以上实施例和其他方面以及其实现方式，在附图说明、具体实施方式和权利要求中提供更多说明。
附图说明
图1是一实施例提供的一种通信***的组网示意图；
图2是一实施例提供的一种传输业务的通信接口的示意图；
图3是一实施例提供的一种细粒度能力的洪泛方法的流程示意图；
图4是一实施例提供的一种携带细粒度的接***换能力描述信息的TLV的示意图；
图5是一实施例提供的另一种携带细粒度的接***换能力描述信息的TLV的示意图；
图6是一实施例提供的一种携带细粒度的接***换能力特定信息的TLV的示意图；
图7是一实施例提供的一种细粒度的配置方法的流程示意图；
图8是一实施例提供的一种管控***与转发网元之间的架构图；
图9是一实施例提供的一种细粒度能力的洪泛装置的结构示意图；
图10是一实施例提供的一种细粒度的配置方法装置的结构示意图；
图11是一实施例提供的一种通信节点的结构示意图。
具体实施方式
应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。下文中将结合附图对本申请的实施例进行详细说明。
切片分组网(slicing packet network，SPN)是面向第五代通信***(5th generation，5G)承载的新一代融合承载网络架构，具有低时延、大带宽、超高精度同步、灵活管控等优点，其中切片通道层(slicing channel layer，SCL)即MTN。基于时分复用(Time Division Multiplexing，TDM)的灵活以太网(Flex Ethernet，FlexE)技术时隙交叉，实现了5Gbps颗粒切片技术，已初步满足5G商用的需求。
目前，MTN又提出了小颗粒技术(Fine Granularity Unit，FGU)，将硬切片的颗粒度从5Gbps细化为10Mbps，以此来满足5G+垂直行业应用和专线等业务场景。另一方面，随着OTN网络逐步覆盖城域边缘并下沉到末端，OTN网络提出了光业务单元(optical service unit，OSU)，相比于传统的光通路数据单元ODU0-3以及ODU Flex面向大速率业务，OSU可提供支持Mbit/s及以上速率业务的承载容器。
因此，面对MTN和OTN都在提出细粒度处理能力，如何部署面向细粒度的统一管控以满足不同转发技术的转发面接口细粒度处理能力成为了当前亟需解决的问题。
本申请提供的细粒度能力的洪泛方法、细粒度的配置方法可以应用于各类通信***中。图1示出了一实施例提供的一种通信***的组网示意图。如图1所示，包括至少一个边缘节点，如图1中的E1、E2，还可以包括至少一个中间节点(或称为转发节点、路由节点)，如图1中的P1、P2、Pn。
本申请提供的方案可以应用到支持以太网、灵活以太网、OTN等接口的网络设备，网络设备产品形态包括典型的SPN传输设备、OTN传输设备等。传输设备的接口可以是FlexE接口、OTN接口等，或是这些接口划分出的管道，图2示出了一实施例提供的一种传输业务的通信接口的示意图。
在本申请实施例中，提供一种可运行于上述通信***的细粒度能力的洪泛方法、细粒度的配置方法，节点及介质，能够洪泛链路的细粒度能力，实现细粒度的统一管控，满足不同转发技术的转发面接口细粒度处理能力。
下面，对细粒度能力的洪泛方法、细粒度的配置方法，通信节点及其技术效果进行描述。
图3示出了一实施例提供的一种细粒度能力的洪泛方法的流程示意图，如图3所示，本实施例提供的方法适用于支持细粒度能力的通信节点(又可称为节点)。该方法包括如下步骤。
S110、洪泛通信节点的细粒度接口信息，细粒度接口信息包括细粒度的接***换能力描述信息，细粒度的接***换能力描述信息包括细粒度的接***换能力、细粒度的编码类型和细粒度的时隙颗粒度。
面对MTN和OTN都在提出细粒度处理能力，国际电信联盟电信标准分局(ITU-T for ITU Telecommunication Standardization Sector)提出建立统一的带宽在1G以下的通用(sub-1G)客户层，sub-1G客户层可同时应用在MTN和OTN网络。MTN和OTN可作为sub-1G网络层的服务层，为sub-1G的客户提供硬管道服务。
在一实施例中，细粒度的接***换能力描述信息位于路由协议链路网络类型-长度-值(type-length-value，TLV)的子TLV(sub-TLV)中。
在细粒度网络中，每个细粒度的流量工程链路状态发布携带一个顶级链路TLV，顶级链路TLV包括节点TLV和流量工程链路TLV，顶级链路TLV中包 含一个或多个嵌套的子TLV。
由于细粒度网络需要支持不同类型的细粒度技术以及不同的颗粒度，因此本申请可以示例性地选择扩展相关技术中的带流量工程的开放最短路径优先(OSPF-TE)。
在一实施例中，细粒度的接***换能力为TDM的接***换能力。相关技术中的TDM类型，如同步数字体系(Synchronous Digital Hierarchy，SDH)表示节点通过TDM接口接收到的数据可以复用或者解复用SDH有效载荷内的信道。在本申请中，细粒度作为一种通用的TDM接口，可以复用相关技术中的TDM的接***换能力(如TDM的转发能力)。细粒度网络中只有一个细粒度层，不支持细粒度层的嵌套，那么在细粒度网络中不需要支持层次化的标签转发路径(Labeled Switched Path，LSP)。
例如，细粒度的接***换能力可以直接复用相关技术中的RFC4203中定义的TDM为100的接***换能力，也可以分配特定的TDM取值。
在一实施例中，由于细粒度是一种独立的网络，因此本申请可以通过新建一个comfgu表达细粒度的编码类型。
细粒度的编码类型为请求的LSP的编码类型。按照RFC4328的描述，LSP编码类型是按照网络层指定的。如果接口上不支持细粒度请求的LSP编码类型，中间/出口节点必须生成带有不支持编码指示的路径错误消息。
例如，在comfgu中设置Encoding字段用于表示细粒度的编码类型。
可选的，细粒度的接***换能力描述信息还可以包括细粒度的信号类型；细粒度的信号类型为基于城域传输网络MTN技术的FGU、基于OTN技术的OSU、sub-1G中的任意一项。
例如，在comfgu中设置SignalType字段用于表示细粒度的信号类型。
在一实施例中，OSU的基准速率是2.6Mb/s，无论是固定速率的恒定比特率(Constant Bit Rate，CBR)业务还是无固定速率的业务，都可以使用C*基准速率，即C*2.6Mb/s，来表示OSU的比特速率。而MTN FGU是基于5Gbps的通道，划定480个10M时隙，分别承载客户信号的。在本申请中，为支持相关技术中的不同技术以及后续sub-1G可能复用或者新增颗粒度，细粒度的接***换能力描述信息还要包括细粒度的时隙颗粒度。
例如，在comfgu中设置Granularity字段用于表示细粒度的时隙颗粒度。
在本申请中，细粒度的接***换能力描述信息包括细粒度的接***换能力、 细粒度的编码类型和细粒度的时隙颗粒度，也可以理解为在TDM的接***换能力下，支持三种类型的细粒度的信号类型，每个信号类型当前支持的时隙颗粒度。
图4示出了一实施例提供的一种携带细粒度的接***换能力描述信息的TLV的示意图；图5示出了一实施例提供的另一种携带细粒度的接***换能力描述信息的TLV的示意图；图6示出了一实施例提供的一种携带细粒度的接***换能力特定信息的TLV的示意图。从图4所示的TLV中，或者结合图5和图6所示的TLV，可以得到细粒度的接***换能力描述信息：细粒度的接***换能力TDM、细粒度的编码类型、细粒度的信号类型和细粒度的时隙颗粒度。
另外，由于路径计算时需要为某个细粒度的连接请求选择合适的路由，为方便管控路径计算，本申请有必要明确每个候选链路的可用带宽。即在路由协议中扩展支持传递足够的信息来标识细粒度的流量工程拓扑。目前一个MTN FGU可支持的最大带宽是5G，一个OSU支持的最大带宽为10G。运营商可部署策略自由决策网络中支持的优先级，如果在网络中设置了优先级，那么所有支持细粒度的设备中需要遵守不同优先级分别进入不同的排序队列处理，明确细粒度链路上可基于优先级分别支持每个优先级上的最大可用带宽。
例如，RFC4202定义了接***换能力描述符(ISCD)，描述了八个优先级下的资源可用性，用于呈现LSP路径计算的约束。根据定义，网络中的每一个优先级都应该独立于优先级的数目独立进行发布。最大LSP带宽在ISCD中按照优先级发布。
考虑到细粒度支持以兆级别的链路，链路数目较多，因此在分布式架构下，为减少网络带宽以及路由协议的链路处理数量，细粒度需要支持链路绑定的方式来满足在一对节点之间持相同速率的细粒度链路捆绑在一起发布，可集中发布捆绑链路的未保留带宽以及捆绑链路能支持的单条LSP的最大带宽。
例如，对于一个MTN的5G颗粒，将整个5G上的所有细粒度链路绑定发布，以绑定链路的ID发布当前5G管道中的最大LSP带宽和未保留带宽；同样，对于一个OTU链路上的所有同一业务类型的细粒度，可以绑定一起发布最大LSP带宽和未保留带宽。
在一实施例中，路由协议为开放最短路径优先(Open Shortest Path First，OSPF)路由协议、中间***到中间***(Intermediate System-to-Intermediate System，IS-IS)路由协议、边界网关协议-链路状态(Border Gateway Protocol- LinkState，BGP-LS)路由协议、路径计算单元协议-链路状态(Path Computation Element rotocol-LinkState，PCEP-LS)路由协议中的任意一项。
对于IS-IS协议，RFC5305中描述可以在路由信息中发布一个或者多个IS-IS链路状态协议数据单元。其中RFC5307中描述了类型为21的接***换能力描述。本申请提供的细粒度的接***换能力描述信息可作为一种类型为21的接口能力，用于描述细粒度接口能力。
BGP-LS是通过BGP协议传递内部网关协议(IGP)链路状态的一种BGP多协议扩展。通过BGP-LS可以获取多IGP域的相关拓扑信息，其中BGP-LS中链路描述TLVs的源可以来自OSPF和IS-IS。使用BGP-LS可以在算路时学习到链路状态拓扑，但是又不需要了解任何OSPF或者IS-IS协议特定的信息。本申请提供的细粒度的接***换能力描述信息可作为一种不透明的链路属性TLV的一个sub-TLV描述链路两端的细粒度接口能力。
还需要说明的是，本申请提供的细粒度的接***换能力描述信息也可以应用在draft-dhodylee-pce-pcep-ls-23中描述的PCEP-LS扩展中扩展链路属性TLV，作为一种特定应用在细粒度的接***换能力TLV，用于设备和PCE之间完成细粒度接口能力的交互。
图7示出了一实施例提供的一种细粒度的配置方法的流程示意图，如图7所示，本实施例提供的方法适用于支持细粒度能力的通信节点。该方法包括如下步骤。
S210、获取细粒度路径上的细粒度信息，细粒度路径用于传输低速率业务，细粒度信息用于指示位于细粒度路径上的通信节点分配细粒度资源。
S220、根据细粒度信息，配置通信节点。
细粒度信息又可以理解为细粒度处理能力模型，直接在OTN OSU网络层次或者MTN FGU层次上建模，可以支持的细粒度能力和细粒度能处理的客户层类型以及客户层映射方式。建模可以如下表示：

在一实施例中，细粒度信息包括：细粒度的客户标识码client-id，客户层类型，映射方式，客户需求，细粒度的信号类型，细粒度的颗粒度，服务层接口中的至少一项。
在一实施例中，细粒度的client-id为当前细粒度的时隙分配标识；
细粒度的client-id用于指示根据MTN技术中的client-id分配时隙，或者用于指示根据OSU技术中的支路端口号TPN分配时隙，或者用于指示根据sub-1G中的客户标识分配时隙。
在一实施例中，细粒度的client-id占用两个字节、且两个字节中的前12个bit为有效比特。
在一实施例中，细粒度的信号类型为基于MTN技术的FGU、基于OTN技术的OSU、sub-1G中的任意一项。
在一实施例中，细粒度的颗粒度可以根据实际需求进行配置，例如细粒度的颗粒度为2.6M或者10M。
在一实施例中，client-type表示的是当前细粒度的客户层报文类型，即细粒度LSP承载的有效载荷标识符，表明是标准以太网业务，还是CBR等业务类型；mapping-type表示的是上层业务通过何种方式映射到细粒度的网络报文中，目前包括比特同步映射规程(Bit-synchronous mapping procedure，BMP)、通用映射规程(Generic mapping procedure，GMP)和闲置映射规程(Idle mapping procedure，IMP)三种，BMP需要客户的时钟跟设备的时钟同步，GMP通常应用于CBR业务，IMP可用于包交换技术的以太网业务；client-demand表示当前业务的要求，可包括带宽需求，时隙分配要求，其中时隙分配要求中可包括时延要求标志位和是否要求双向时延差等信息。
在一实施例中，细粒度的配置方法还包括：接收业务请求信息，业务请求信息包括当前细粒度网络承载的业务要求，业务要求包括带宽要求和时隙分配要求中的至少一项，时隙分配要求包括时延要求标志位和是否要求双向时延差中的至少一项。
在一实施例中，细粒度的配置方法适用于通信节点和网管设备之间的南向NETCONF协议，或者适用于算路单元和网元之间的路径计算单元协议PCEP。
细粒度网络中一般会部署集中式和分布式共存的管控架构。网元上可支持上述实施例中的细粒度能力的洪泛方法，洪泛的细粒度接口信息上报给集中式的管控***。管控***维护细粒度的拓扑，并完成集中式的路径计算。路径计算的结果可以转化成多个上述实施例中的comfgu-client信息，分别下发到连接上的各个转发节点，也可以只下发给入口节点，由入口节点按照集中式的管控***下发的路径信息完成连接建立和资源预留。
由于细粒度的时隙资源的粒度小，以兆为级别，如果都放在网管上维护不太现实，因此考虑将此功能下放到网元本地，管控***提出资源分配需求，由网元本地来完成本地时隙资源的分配。因此，图8示出了一实施例提供的一种管控***与转发网元之间的架构图。如图8所示，管控***中部署有细粒度拓扑管理和细粒度路径计算两个模块，转发网元中部署有资源分配和路由洪泛两个模块。
图9示出了一实施例提供的一种细粒度能力的洪泛装置的结构示意图，该装置可以配置于通信节点中，如图9所示，该装置包括：洪泛模块10。
洪泛模块10，设置为洪泛通信节点的细粒度接口信息，细粒度接口信息包括细粒度的接***换能力描述信息，细粒度的接***换能力描述信息包括细粒度的接***换能力、细粒度的编码类型和细粒度的时隙颗粒度。
本实施例提供的细粒度能力的洪泛装置为实现图3所示实施例的细粒度能力的洪泛方法，本实施例提供的细粒度能力的洪泛装置实现原理和技术效果与上述实施例类似，此处不再赘述。
在一实施例中，细粒度的接***换能力描述信息还包括细粒度的信号类型；
细粒度的信号类型为基于城域传输网络MTN技术的小颗粒单元FGU、基于光传送网OTN技术的光业务单元OSU、带宽在1G以下的通用sub-1G中的任意一项。
在一实施例中，细粒度的接***换能力为时分复用TDM的接***换能力。
在一实施例中，细粒度的接***换能力描述信息位于路由协议链路网络类型-长度-值TLV的子网络类型-长度-值sub-TLV中。
在一实施例中，路由协议为开放最短路径优先OSPF路由协议、中间*** 到中间***IS-IS路由协议、边界网关协议-链路状态BGP-LS路由协议、路径计算单元协议-链路状态PCEP-LS路由协议中的任意一项。
图10示出了一实施例提供的一种细粒度的配置方法装置的结构示意图，该装置可以配置于通信节点中，如图10所示，该装置包括：获取模块20和配置模块21。
获取模块20，设置为获取细粒度路径上的细粒度信息，细粒度路径用于传输低速率业务，细粒度信息用于指示位于细粒度路径上的通信节点分配细粒度资源；
配置模块21，设置为根据细粒度信息，配置通信节点。
本实施例提供的细粒度的配置装置为实现图7所示实施例的细粒度的配置方法，本实施例提供的细粒度的配置装置实现原理和技术效果与上述实施例类似，此处不再赘述。
在一实施例中，细粒度信息包括：细粒度的客户标识码client-id，客户层类型，映射方式，客户需求，细粒度的信号类型，细粒度的颗粒度，服务层接口中的至少一项。
在一实施例中，细粒度的client-id为当前细粒度的时隙分配标识；
细粒度的client-id用于指示根据MTN技术中的client-id分配时隙，或者用于指示根据OSU技术中的支路端口号TPN分配时隙，或者用于指示根据sub-1G中的客户标识分配时隙。
在一实施例中，细粒度的client-id占用两个字节、且两个字节中的前12个bit为有效比特。
在一实施例中，获取模块20，还设置为接收业务请求信息，业务请求信息包括当前细粒度网络承载的业务要求，业务要求包括带宽要求和时隙分配要求中的至少一项，时隙分配要求包括时延要求标志位和是否要求双向时延差中的至少一项。
在一实施例中，方法适用于通信节点和网管设备之间的南向NETCONF协议，或者适用于算路单元和网元之间的路径计算单元协议PCEP。
本申请实施例还提供了一种通信节点，包括：处理器，处理器用于在执行计算机程序时实现如本申请任意实施例所提供的方法。图11示出了一实施例提供的一种通信节点的结构示意图，如图11所示，该通信节点包括处理器60、存储器61和通信接口62；通信节点中处理器60的数量可以是一个或多个，图 11中以一个处理器60为例；通信节点中的处理器60、存储器61、通信接口62可以通过总线或其他方式连接，图11中以通过总线连接为例。总线表示几类总线结构中的一种或多种，包括存储器总线或者存储器控制器，***总线，图形加速端口，处理器或者使用多种总线结构中的任意总线结构的局域总线。
存储器61作为一种计算机可读存储介质，可设置为存储软件程序、计算机可执行程序以及模块，如本申请实施例中的方法对应的程序指令/模块。处理器60通过运行存储在存储器61中的软件程序、指令以及模块，从而执行通信节点的至少一种功能应用以及数据处理，即实现上述的方法。
存储器61可包括存储程序区和存储数据区，其中，存储程序区可存储操作***、至少一个功能所需的应用程序；存储数据区可存储根据终端的使用所创建的数据等。此外，存储器61可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储器61可包括相对于处理器60远程设置的存储器，这些远程存储器可以通过网络连接至通信节点。上述网络的实例包括但不限于互联网、企业内部网、网络、移动通信网及其组合。
通信接口62可设置为数据的接收与发送。
本申请实施例还提供了一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现如本申请任意实施例所提供的方法。
本申请实施例的计算机存储介质，可以采用一个或多个计算机可读的介质的任意组合。计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质。计算机可读存储介质例如可以是但不限于：电、磁、光、电磁、红外线、或半导体的***、装置或器件，或者任意以上的组合。计算机可读存储介质包括(非穷举的列表)：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机存取存储器(Random Access Memory，RAM)、只读存储器(Read-Only Memory，ROM)、可擦式可编程只读存储器(electrically erasable,programmable Read-Only Memory，EPROM)、闪存、光纤、便携式紧凑磁盘只读存储器(Compact Disc Read-Only Memory，CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。在本申请中，计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行***、装置或者器件使用或者与其结合使用。
计算机可读的信号介质可以包括在基带中或者作为载波一部分传播的数据信号，数据信号中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。计算机可读的信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读介质可以发送、传播或者传输用于由指令执行***、装置或者器件使用或者与其结合使用的程序。
可以以一种或多种程序设计语言或多种程序设计语言组合来编写用于执行本公开操作的计算机程序代码，程序设计语言包括面向对象的程序设计语言(诸如Java、Smalltalk、C++、Ruby、Go)，还包括常规的过程式程序设计语言(诸如“C”语言或类似的程序设计语言)。程序代码可以完全地在用户计算机上执行、部分地在用户计算机上执行、作为一个独立的软件包执行、部分在用户计算机上部分在远程计算机上执行、或者完全在远程计算机或服务器上执行。在涉及远程计算机的情形中，远程计算机可以通过任意种类的网络(包括网络(Local Area Network，LAN)或广域网(Wide Area Network，WAN))连接到用户计算机，或者，可以连接到外部计算机(例如利用因特网服务提供商来通过因特网连接)。
本领域内的技术人员应明白，术语用户终端涵盖任何适合类型的无线用户设备，例如移动电话、便携数据处理装置、便携网络浏览器或车载移动台。
一般来说，本申请的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如，一些方面可以被实现在硬件中，而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中，尽管本申请不限于此。
本申请的实施例可以通过移动装置的数据处理器执行计算机程序指令来实现，例如在处理器实体中，或者通过硬件，或者通过软件和硬件的组合。计算机程序指令可以是汇编指令、指令集架构(Instruction Set Architecture，ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一种或多种编程语言的任意组合编写的源代码或目标代码。
本申请附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于 只读存储器(ROM)、随机访问存储器(RAM)、光存储器装置和***(数码多功能光碟DVD或CD光盘)等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(Digital Signal Processing，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑器件(Field－Programmable Gate Array，FGPA)以及基于多核处理器架构的处理器。

Claims (13)

  1. 一种细粒度能力的洪泛方法，适用于支持细粒度能力的通信节点，所述方法包括：
    洪泛所述通信节点的细粒度接口信息，所述细粒度接口信息包括细粒度的接***换能力描述信息，所述细粒度的接***换能力描述信息包括细粒度的接***换能力、细粒度的编码类型和细粒度的时隙颗粒度。
  2. 根据权利要求1所述的方法，其中，所述细粒度的接***换能力描述信息还包括细粒度的信号类型；
    所述细粒度的信号类型为基于城域传输网络MTN技术的小颗粒单元FGU、基于光传送网OTN技术的光业务单元OSU、带宽在1G以下的通用sub-1G中的任意一项。
  3. 根据权利要求1所述的方法，其中，所述细粒度的接***换能力为时分复用TDM的接***换能力。
  4. 根据权利要求1所述的方法，其中，所述细粒度的接***换能力描述信息位于路由协议链路网络类型-长度-值TLV的子网络类型-长度-值sub-TLV中。
  5. 根据权利要求4所述的方法，其中，所述路由协议为开放最短路径优先OSPF路由协议、中间***到中间***IS-IS路由协议、边界网关协议-链路状态BGP-LS路由协议、路径计算单元协议-链路状态PCEP-LS路由协议中的任意一项。
  6. 一种细粒度的配置方法，适用于支持细粒度能力的通信节点，所述方法包括：
    获取细粒度路径上的细粒度信息，所述细粒度路径用于传输低速率业务，所述细粒度信息用于指示位于所述细粒度路径上的通信节点分配细粒度资源；
    根据所述细粒度信息，配置所述通信节点。
  7. 根据权利要求6所述的方法，其中，所述细粒度信息包括：细粒度的客户标识码client-id，客户层类型，映射方式，客户需求，细粒度的信号类型，细粒度的颗粒度，服务层接口中的至少一项。
  8. 根据权利要求7所述的方法，其中，所述细粒度的client-id为当前细粒度的时隙分配标识；
    所述细粒度的client-id用于指示以下之一：根据MTN技术中的client-id分配时隙，根据OSU技术中的支路端口号TPN分配时隙，以及根据sub-1G中的 客户标识分配时隙。
  9. 根据权利要求7所述的方法，其中，所述细粒度的client-id占用两个字节、且所述两个字节中的前12个比特为有效比特。
  10. 根据权利要求6所述的方法，还包括：
    接收业务请求信息，所述业务请求信息包括当前细粒度网络承载的业务要求，所述业务要求包括带宽要求和时隙分配要求中的至少一项，所述时隙分配要求包括时延要求标志位和是否要求双向时延差中的至少一项。
  11. 根据权利要求6-10中任一所述的方法，其中，所述方法适用于所述通信节点和网管设备之间的南向NETCONF协议，或者适用于算路单元和网元之间的路径计算单元协议PCEP。
  12. 一种通信节点，包括：处理器；所述处理器用于在执行计算机程序时实现如权利要求1-5中任一所述的细粒度能力的洪泛方法，或者实现如权利要求6-11中任一所述的细粒度的配置方法。
  13. 一种计算机可读存储介质，存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1-5中任一所述的细粒度能力的洪泛方法，或者实现如权利要求6-11中任一所述的细粒度的配置方法。
PCT/CN2023/085692 2022-06-30 2023-03-31 细粒度能力的洪泛方法、细粒度的配置方法，节点及介质 WO2024001370A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210771252.9 2022-06-30
CN202210771252.9A CN117376145A (zh) 2022-06-30 2022-06-30 细粒度能力的洪泛方法、细粒度的配置方法，节点及介质

Publications (1)

Publication Number Publication Date
WO2024001370A1 true WO2024001370A1 (zh) 2024-01-04

Family

ID=89382638

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/085692 WO2024001370A1 (zh) 2022-06-30 2023-03-31 细粒度能力的洪泛方法、细粒度的配置方法，节点及介质

Country Status (2)

Country Link
CN (1) CN117376145A (zh)
WO (1) WO2024001370A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1431834A (zh) * 2003-01-16 2003-07-23 上海交通大学 多粒度混合光网络的自动交换控制方法
CN101127628A (zh) * 2006-08-14 2008-02-20 华为技术有限公司 一种管理和传送细粒度业务的方法
WO2011029347A1 (zh) * 2009-09-08 2011-03-17 华为技术有限公司 实现节点发布链路信息的方法和装置
US20130202294A1 (en) * 2010-03-25 2013-08-08 Zte Corporation G.709 based multi-stages multiplexing routing control method and gateway network element
US20130294773A1 (en) * 2010-12-17 2013-11-07 Zte Corporation G.709 Based Multi-Level Multiplexing Routing Control Method and Gateway Network Element
CN104869021A (zh) * 2015-05-22 2015-08-26 清华大学 多粒度多域异构光网络资源配置方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1431834A (zh) * 2003-01-16 2003-07-23 上海交通大学 多粒度混合光网络的自动交换控制方法
CN101127628A (zh) * 2006-08-14 2008-02-20 华为技术有限公司 一种管理和传送细粒度业务的方法
WO2011029347A1 (zh) * 2009-09-08 2011-03-17 华为技术有限公司 实现节点发布链路信息的方法和装置
US20130202294A1 (en) * 2010-03-25 2013-08-08 Zte Corporation G.709 based multi-stages multiplexing routing control method and gateway network element
US20130294773A1 (en) * 2010-12-17 2013-11-07 Zte Corporation G.709 Based Multi-Level Multiplexing Routing Control Method and Gateway Network Element
CN104869021A (zh) * 2015-05-22 2015-08-26 清华大学 多粒度多域异构光网络资源配置方法

Also Published As

Publication number Publication date
CN117376145A (zh) 2024-01-09

Similar Documents

Publication Publication Date Title
CN106803814B (zh) 一种灵活以太网路径的建立方法、装置及***
WO2017156987A1 (zh) 一种灵活以太网路径建立的方法和装置
US10250459B2 (en) Bandwidth on-demand services in multiple layer networks
US9825845B2 (en) Path computation method, path computation element, node device, and network system
CN107438028B (zh) 一种客户业务处理的方法和设备
WO2018228420A1 (zh) 一种传输网络***、数据交换和传输方法、装置及设备
WO2011000310A1 (zh) 光网络中标签的分配处理方法、光通信装置及光通信***
CN102630384B (zh) 一种在光传送网中实现业务传送的方法及实现该方法的设备和***
US20090103533A1 (en) Method, system and node apparatus for establishing identifier mapping relationship
WO2017088495A1 (zh) 一种路由信息的获取方法及装置
Zhang et al. Framework for GMPLS and PCE Control of G. 709 Optical Transport Networks
JP5739960B2 (ja) パケット光ネットワークの宛先ノードに外部の光データパケットを提供する方法及びシステム
US20230078178A1 (en) Service resource preconfiguration method and device, and system
WO2022063196A1 (zh) 一种数据帧的发送方法和网络设备
CN117354305B (zh) 一种互通协同管控方法和架构
WO2021027434A1 (zh) 一种业务传输的方法、装置和***
WO2024001370A1 (zh) 细粒度能力的洪泛方法、细粒度的配置方法，节点及介质
JP2009089394A (ja) トラフィック管理リソースの利用可能性通知
CN1881940A (zh) 分组地址交换或标签交换通信网络中连接路径的资源预留
WO2013063751A1 (zh) 转发邻居-标签交换路径的连接建立方法及装置
WO2012149760A1 (zh) 一种时隙资源配置方法及装置
CN105357112A (zh) 一种软件定义网络中的通信方法及装置
WO2012088956A1 (zh) Oduflex无损调整能力路由洪泛方法、装置及节点
WO2022193751A1 (zh) 时隙配置方法、业务路径创建方法、装置、设备及介质
WO2022199276A1 (zh) 业务保护方法及网络节点

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23829560

Country of ref document: EP

Kind code of ref document: A1