WO2021012782A1 - 一种桥接网络信息通告方法、设备和公共属性管理组件 - Google Patents

一种桥接网络信息通告方法、设备和公共属性管理组件 Download PDF

Info

Publication number
WO2021012782A1
WO2021012782A1 PCT/CN2020/093031 CN2020093031W WO2021012782A1 WO 2021012782 A1 WO2021012782 A1 WO 2021012782A1 CN 2020093031 W CN2020093031 W CN 2020093031W WO 2021012782 A1 WO2021012782 A1 WO 2021012782A1
Authority
WO
WIPO (PCT)
Prior art keywords
lrp
attribute information
camc
public attribute
application
Prior art date
Application number
PCT/CN2020/093031
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 中兴通讯股份有限公司
Priority to KR1020217038277A priority Critical patent/KR20210151224A/ko
Priority to EP20844110.5A priority patent/EP3958518B1/en
Priority to JP2021569506A priority patent/JP7327767B2/ja
Priority to US17/620,112 priority patent/US20220368562A1/en
Publication of WO2021012782A1 publication Critical patent/WO2021012782A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/03—Protocol definition or specification 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462—LAN interconnection over a bridge based backbone
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2212/00—Encapsulation of packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/28—Timers or timing mechanisms used in protocols

Definitions

  • This article relates to, but is not limited to, a bridged network information notification method, device, public attribute management component, and computer-readable storage medium.
  • LRP Link-local Registration Protocol
  • TSN Time Sensitive Network, Time Sensitive Network
  • the fast and reliable protocol for hop-by-hop distribution of information in the network has the advantages of good scalability and supporting 1MByte level data transmission.
  • various application protocols or components can be defined. These applications are loosely coupled with LRP, and each defines attribute values and semantics. Only LRP is used as a data transmission channel to declare and propagate attributes by calling the service primitives provided by LRP.
  • LRP LRP
  • RAP Resource Allocate Protocol, resource allocation protocol
  • SR Stream Reservation Class
  • Queue transmission selection algorithm queue ClassMeasureInterval and other information are used to establish the SR domain, and then allocate resources based on the SR domain, and other protocols may also need to operate based on the SR domain.
  • SR domain information notification is coupled with RAP.
  • other protocols also use SR domain information, they need to define and advertise this information separately, which may cause inconsistencies in specifications and waste of network resources.
  • the embodiments of the present invention provide a method, a device, a common attribute management component, and a computer-readable storage medium for advertising bridge network information.
  • the embodiment of the present invention provides a bridged network information notification method.
  • a common attribute management component CAMC is set on each port of each node of the bridged network, and the CAMC is set between the link local registration protocol LRP application and LRP,
  • the method includes: CAMC receives the first public attribute information notified by the LRP application, writes the first public attribute information into the LRP database; and the CAMC receives the second public attribute information reported by the LRP database, and transfers the The second public attribute information is reported to the LRP application; wherein, the first public attribute information is the public attribute information that the LRP application needs to advertise, and the second public attribute information is the public that needs to be synchronized when the LRP database changes.
  • Property information is included in the first public attribute information is the public attribute information that the LRP application needs to advertise, and the second public attribute information is the public that needs to be synchronized when the LRP database changes.
  • the embodiment of the present invention also provides a CAMC, which is set between the LRP application and LRP of each port of each node of the bridge network, and includes an attribute declaration component CADE, an encoding and decoding component CCDE, and an attribute registration component CARE,
  • the CADE is set to receive the first public attribute information notified by the LRP application and send it to the CCDE
  • the CCDE is set to encapsulate the first public attribute information into a TLV format, and the encapsulation into a TLV format Write the first public attribute information in the LRP database
  • the CARE is set to report the second public attribute information to the LRP application; wherein, the first public attribute information is the public attribute information that the LRP application needs to advertise, and the second public attribute information is the The public attribute information that needs to be synchronized when the L
  • the embodiment of the present invention also provides a bridged network information notification device, including: a memory, a processor, and a computer program stored in the memory and running on the processor, and the processor implements the bridged network when the program is executed. Information notification method.
  • the embodiment of the present invention also provides a computer-readable storage medium storing computer-executable instructions for executing the bridged network information notification method.
  • each port of each node of the bridging network is provided with CAMC
  • the CAMC is set between the LRP application and the LRP
  • the CAMC receives the first public attribute information notified by the LRP application, and the first The public attribute information is written into the LRP database
  • the CAMC receives the second public attribute information reported by the LRP database, and reports the second public attribute information to the LRP application
  • the first public attribute information is the The public attribute information that the LRP application needs to advertise
  • the second public attribute information is the public attribute information that needs to be synchronized when the LRP database changes.
  • the common attribute information is uniformly transmitted and diffused through CAMC.
  • multiple LRP applications can share common attribute information without additional definition.
  • multiple LRP applications on the same port need to advertise the same When the attribute information is public, it only needs to be notified once to avoid waste of resources.
  • FIG. 1 is a schematic diagram of the encapsulation format of Record LRPDU according to an embodiment of the present invention
  • Figure 2 is a schematic diagram of the encoding format of each Record according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of the relationship between CAMC, LRP and LRP application in an embodiment of the present invention
  • Fig. 4 is a flowchart of a method for advertising bridged network information according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of step 101 of an embodiment of the present invention.
  • FIG. 6 is a flowchart of step 201 in an embodiment of the present invention.
  • FIG. 7 is a flowchart of a method for advertising bridged network information according to another embodiment of the present invention.
  • FIG. 8 is a flowchart of realizing diffusion in the method for advertising bridge network information according to an embodiment of the present invention.
  • FIG. 9 is a flowchart of realizing query in the method for advertising bridge network information according to an embodiment of the present invention.
  • Figure 10 is a query sequence diagram of an embodiment of the present invention.
  • FIG. 11 is a schematic diagram of the composition of CAMC according to an embodiment of the present invention.
  • FIG. 12 is a flowchart of an LRP application advertising attribute information through CAMC according to an embodiment of the present invention.
  • FIG. 13 is a flowchart of application example 1 of the present invention.
  • FIG. 14 is a flowchart of the second application example of the present invention.
  • Fig. 15 is a schematic diagram of TLV coding trellis in (a) and (b) of an embodiment of the present invention.
  • CAMC Common Attribute Management Component
  • This component is used as a public component specifically to In the bridged network, based on Record LRPDU (Link-local Registration Protocol Data Unit, link local registration protocol data unit) with TLV (Type, Length, Value, type, length and value) coding format to announce various public information
  • CAMC component Provide information notification services for other protocols or components.
  • CAMC is set on each port of each node of the bridge network, and the CAMC is set between the LRP application and the LRP.
  • the remaining available resources of port bandwidth can be used by RAP, or PCE (Path Computation Element, path calculation unit) can be used as a path calculation basis.
  • PCE Plane Computation Element, path calculation unit
  • the embodiment of the present invention lists various information that can be notified by the CAMC, including but not limited to the content listed in Table 1 below.
  • the information that needs to be notified is encoded in TLV format and carried by LRPDU.
  • Record LRPDU is used to carry Data (data).
  • the encapsulation format of Record LRPDU is shown in Figure 1.
  • Each Record LRPDU can carry 0 or more Records.
  • the encoding format of each Record is shown in Figure 2.
  • Each Application Data field can be used to carry Multiple information TLVs that need to be advertised.
  • the TLV encoding format of each type of information can be selected according to actual needs or existing technology, and will not be repeated in this embodiment of the present invention.
  • CAMC can provide public information notification services for multiple LRP applications, and these LRP applications can also advertise their specific attribute information.
  • the schematic diagram of the relationship between CAMC, LRP and other LRP application protocols or components is shown in Figure 3.
  • the common attributes of each LRP application can be advertised through CAMC (with arrow dashed line), and the specific attributes of each LRP application can be announced by itself (with (Arrow solid line), for example, the attributes of the SR domain of RAP can be advertised using the CAMC protocol, while the attributes related to RAP resource allocation are defined by themselves and announced by calling the LRP primitive.
  • CAMC The content defined by CAMC includes:
  • each public attribute and the associated semantics indicate various information that needs to be notified.
  • the attribute type is "queue transmission selection algorithm", and the attribute value is 1, which means Credit-Based Shaper (CBS). )algorithm;
  • TLV encoding format used to carry various attribute types and values in the Record LRPDU
  • RAP LRP applications or components
  • PCE information announcement service primitives, information query service primitives and information reporting primitives.
  • Applications such as RAP can call information query service primitives to query whether certain information on this port has been advertised and the information advertised by other ports. When multiple applications on the same port need to advertise the same information listed in Table 1, they only need to advertise once. So as to avoid waste of resources.
  • the method for advertising bridged network information in the embodiment of the present invention includes:
  • Step 101 The CAMC receives the first public attribute information notified by the LRP application, and writes the first public attribute information into the LRP database.
  • the first public attribute information is public attribute information that the LRP application needs to advertise.
  • the step 101 may include:
  • Step 201 The CAMC receives the first public attribute information announced by the LRP application through the CAMC information announcement service primitive.
  • Step 202 The CAMC encapsulates the first public attribute information into a TLV format, and calls the LRP Write Record Request primitive to write the first public attribute information into the LRP Applicant database.
  • the first public attribute information and the information of the port are encapsulated together, and sent to the Applicant database of LRP.
  • Step 102 The CAMC receives the second public attribute information reported by the LRP database, and reports the second public attribute information to the LRP application.
  • the second public attribute information is the public attribute information that needs to be synchronized when the LRP database changes.
  • step 102 includes:
  • Step 301 The CAMC receives the second public attribute information in the TLV encapsulation format reported by the Registrar database of the LRP through the LRP Record Write Indication primitive.
  • Step 302 The CAMC decapsulates the second public attribute information in the TLV encapsulation format, and reports the second public attribute information to all LRP applications of the port through the CAMC information reporting primitive.
  • the method further includes:
  • Step 103 The CAMC determines that the second public attribute information needs to be diffused, and diffuses the second public attribute information to the CAMC of other ports of the node.
  • CPFT cache control flag Table
  • attribute diffusion flag table attribute diffusion flag table
  • the CPFT is located in the CAMC and can be configured by the LRP application or statically configured by the user.
  • the method further includes:
  • Step 401 The CAMC receives third public attribute information diffused by the CAMC of other ports of the node, where the third public attribute information is public attribute information that needs to be diffused.
  • this step corresponds to step 103, which is the public attribute information diffused to this port by other ports.
  • Step 402 The CAMC writes the third public attribute information into the LRP database.
  • the CAMC receives the LRP database to send the third public attribute information, and the CAMC sends the third public attribute information to all LRP applications on the port.
  • the method further includes:
  • Step 501 The CAMC receives a query request sent by an LRP application, and the query request is used to query specified attribute information.
  • the CAMC receives the query request sent by the LRP application through the CAMC query service primitive.
  • Step 502 The CAMC queries the LRP database, and returns the query result to the LRP application.
  • the step 502 includes:
  • the CAMC invokes the LRP Database Request query primitive to query the LRP database to obtain the attribute information; the CAMC determines the query result according to the attribute information and the screening strategy, and returns the query result to the LRP application.
  • CAMC When providing query services for LRP applications, CAMC serves as a cushion, and LRP needs to provide the LRP Database Request primitive, which strips Record ID, checksum, sequenceNum, etc., and returns the Data content of the database Record.
  • LRP Database Request primitive which strips Record ID, checksum, sequenceNum, etc., and returns the Data content of the database Record.
  • Step 601 The LRP application calls the CAMC query service primitive to query certain attribute information, including whether the port has advertised the attribute and other ports advertised the attribute information to the port;
  • Step 602 CAMC calls the LRP Database Request query primitive to query the LRP database
  • Step 603 The LRP database returns the database query result, that is, Record Application Data information carrying the attribute information;
  • Step 604 CAMC extracts the attribute information, filters and integrates the attribute information according to certain policies (for example, filter the attributes of a certain node or port according to the upper-layer LRP application requirements, or the attributes of all nodes in the entire domain, or mark whether the port has been notified The attribute, etc.);
  • certain policies for example, filter the attributes of a certain node or port according to the upper-layer LRP application requirements, or the attributes of all nodes in the entire domain, or mark whether the port has been notified The attribute, etc.
  • Step 605 CAMC returns the query result to the upper LRP application.
  • the CAMC of the embodiment of the present invention includes the following components, and the functions and mutual cooperation processes of each component are as follows:
  • CADE Attribute Declaration Entity, Attribute Declaration Component
  • CPPE74 7 in the figure
  • CAMC service request primitive issued by applications such as RAP (1 in the figure)
  • the output of CADE is passed to CCDE (2 in the figure) 73;
  • CARE Content Content Attribute Registration Entity, attribute registration component 72, a per-Portal component, handles public attribute registration events that occur on the Portal, and is triggered by receiving attributes from CCDE 73 (5 in the figure).
  • the output of CARE72 is sent to applications such as RAP (8 in the figure), and CPFT (9 in the figure) is queried to determine whether it needs to be diffused through CPPE74 (6 in the figure);
  • CCDE (CAMC Coding and Decoding Entity, Encoding and Decoding Entity) 73, a per-Portal component, encodes CAMC attributes in the corresponding TLV format and sends it to LRP (3 in the figure) or receives information from LRP and performs TLV decoding ( Figure ⁇ 4);
  • CPPE ALC attribute Propagation and Processing Entity, attribute propagation component
  • CPPE per-Bridge component, propagates attribute declarations among per-Poral CAMC components; all ports of each node share a CPPE74;
  • CPFT (CAMC attribute Propagation Flag Table) 75 indicates whether the attribute registration statement received by a port needs to be diffused to other ports through CPPE74.
  • the table can be generated in two ways: configured by the LRP application or configured statically by the user.
  • the CADE71 is used to receive the first public attribute information notified by the LRP application and send it to the CCDE73;
  • the CCDE73 is configured to encapsulate the first public attribute information into a TLV format, write the first public attribute information encapsulated into the TLV format into the LRP database; and to receive the first TLV encapsulation format reported by the LRP database 2.
  • Public attribute information decapsulate the second public attribute information in the TLV encapsulation format, and send it to the CARE 72;
  • the CARE 72 is configured to report the second public attribute information to the LRP application;
  • the first public attribute information is the public attribute information that the LRP application needs to advertise
  • the second public attribute information is the public attribute information that needs to be synchronized when the LRP database changes.
  • the CARE 72 is further configured to determine that the second public attribute information needs to be diffused by querying the CPFT 75, and then send the second public attribute information to the CPPE 74;
  • the CPPE74 is set to diffuse the second public attribute information to the CADE in the CAMC of other ports of the node.
  • the CADE71 is further configured to receive the third public attribute information diffused by the CPPE74, and send the third public attribute information to the CCDE73, and the third public attribute information is the public information that needs to be diffused. Attribute information
  • the CCDE 73 is further configured to encapsulate the third public attribute information into a TLV format, and write the third public attribute information encapsulated into the TLV format into the LRP database.
  • the CADE71 is further configured to receive a query request sent by an LRP application, and send the query request to CCDE73, and the query request is used to query specified attribute information;
  • the CCDE73 is also configured to encapsulate the query request into a TLV format, query the LRP database, obtain the attribute information, and send it to the CARE72;
  • the CARE 72 is further configured to determine the query result according to the attribute information and the screening strategy, and return the query result to the LRP application.
  • the process of LRP application notification of attribute information through CAMC includes:
  • Step 801 the LRP application announces the attribute information by calling the CAMC information announcement service primitive
  • Step 802 CADE, the component responsible for information notification in CAMC, sends the request information to the CCDE component along with the port information;
  • Step 803 The CCDE component encapsulates the information in TLV format, and calls the LRP Write Record Request primitive to write the attributes into the Applicant database;
  • Step 804 LRP synchronizes the changed Record of the Applicant database to the neighbor Registrar database
  • Step 805 the change of the neighbor Registrar database is reported to the neighbor CCDE component through the LRP Record Write Indication primitive;
  • the neighbor CCDE component decapsulates the received information by TLV, obtains the attribute information, and delivers it to the CARE component.
  • the CARE component reports the attribute information to all LRP applications through the CAMC information reporting primitive;
  • Step 807 judge whether there are other ports, if not, end the process, if yes, go to step 808;
  • the CARE component queries the CPFT table to inquire whether the attribute needs to be diffused. If it needs to be diffused, it sends an attribute notification request to the CPPE component. The CPPE component further requests the CADE component of other port CAMC to advertise the attribute, and returns to step 801.
  • the common attribute information is uniformly transmitted and diffused through CAMC.
  • multiple LRP applications can share common attribute information without additional definition.
  • multiple LRP applications on the same port need to advertise the same When the attribute information is public, it only needs to be notified once to avoid waste of resources.
  • This application example illustrates the process of using CAMC to notify information, as shown in Figure 13.
  • System A there are two devices, System A and System B.
  • Port1 of A and Port1 of B establish a Portal association for component CAMC.
  • System B has two ports, and the other Port is Port2.
  • RAP requests CAMC to notify "System A's port Port1 remaining "Available bandwidth" information, System B Port1 CPFT table configuration information needs to be diffused, the notification process is as follows:
  • Step 901 the application on System A port1 invokes the CAMC primitive to announce the "remaining available bandwidth"
  • Step 902 the CADE component on System A port1 receives the "remaining available bandwidth" notification request primitive, and the notification attribute is the remaining available bandwidth value;
  • Step 903 the CADE component sends the request to the CCDE component.
  • the content of the request is ⁇ System A, port1, notification type (assuming type 001 represents the remaining available bandwidth), value>, CCDE encapsulates the request into TLV format, and calls LRP Write Record Request The primitive writes the TLV into the Record of the Applicant database of the Portal corresponding to System A port1;
  • step 904 the LRP synchronizes the Record changes of the System A port1 database to the System B port1 Registrar database through the Record LRPDU, and then advertises it to the System B Port1 CCDE component through the LRP Record Write Indication primitive;
  • Step 905 the CCDE component of System B port1 decapsulates the TLV contained in the received Record and submits it to the CARE component;
  • Step 906 The CARE component of System B Port 1 parses the available value of the remaining bandwidth of System A Port 1 and advertises it to the RAP application and other LRP applications on System B through an information reporting primitive;
  • step 907 the CARE component of System B Port1 receives the "System A port1 remaining available bandwidth information" and determines whether there are other ports. If there are no other ports, the process ends, and if there are, go to step 908;
  • step 908 the CARE component queries the CPFT table and finds that it needs to be diffused, and advertises to the CADE component of System B Port 2 through the CPPE component.
  • the further notification process of System B Port 2 CADE is the same as steps 902 to 907.
  • Step 1001 RAP queries whether the SR Class information of the port is advertised by calling the query service primitive provided by CAMC (the advertised attributes will be recorded in the Applicant library of the Portal);
  • Step 1002 CAMC queries the service primitive to determine whether the SR class information has been notified by other applications, if not, execute step 1003, if yes, execute step 1004;
  • Step 1003 The CAMC returns indicating that the information of this port has not been notified.
  • RAP uses the process in Application Example 1 to advertise the SR Class information of this port, and other device ports use the same method to advertise the SR Class information of each port to this port;
  • the RAP uses the query service primitive provided by CAMC to query the SR Class information recorded in the associated Portal (which may be the SR Class information of all or part of the port), and establish an SR domain (then perform resource allocation based on the SR domain).
  • PCE is to announce the SR Class information of this port. It first calls the CAMC query service primitive. The returned data indicates that the port attributes have been advertised. There is no need to repeatedly announce the SR Class information of this port. Port SR Class information, so that the SR domain can also be established (subsequent route calculation can be performed according to the SR domain information).
  • the following SR domain information illustrates the TLV coding lattice, as shown in Figure 15(a).
  • the Type field itself occupies 2 bytes, and the Length itself occupies 2 bytes.
  • the value of the Length field specifies the number of bytes occupied by the Data Value field. It is stipulated that the SR domain information, Type value, and the number of bytes occupied are as follows.
  • the format of each TLV is shown in Figure 15(b):
  • the maximum size of data that can be carried in the Application Data field is 65520 bytes, so one Record can carry multiple TLVs.
  • TLVs that advertise SR domain information can be carried by one Record.
  • the CCDE component of the CAMC in the embodiment of the present invention is responsible for the encoding and decoding of each public attribute TLV.
  • the embodiment of the present invention also provides a bridged network information notification device, including: a memory, a processor, and a computer program stored in the memory and running on the processor, and the processor implements the bridged network when the program is executed. Information notification method.
  • the embodiment of the present invention also provides a computer-readable storage medium storing computer-executable instructions for executing the bridged network information notification method.
  • the foregoing storage medium may include, but is not limited to: U disk, Read-Only Memory (ROM), Random Access Memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk, etc.
  • U disk Read-Only Memory
  • RAM Random Access Memory
  • RAM Random Access Memory
  • mobile hard disk magnetic disk or optical disk, etc.
  • Such software may be distributed on a computer-readable medium
  • the computer-readable medium may include a computer storage medium (or non-transitory medium) and a communication medium (or transitory medium).
  • the term computer storage medium includes volatile and non-volatile memory implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data).
  • Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassette, tape, magnetic disk storage or other magnetic storage device, or Any other medium used to store desired information and that can be accessed by a computer.
  • communication media usually contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as carrier waves or other transmission mechanisms, and may include any information delivery media .
  • each port of each node of the bridging network is provided with CAMC
  • the CAMC is set between the LRP application and the LRP
  • the CAMC receives the first public attribute information notified by the LRP application, and the first The public attribute information is written into the LRP database
  • the CAMC receives the second public attribute information reported by the LRP database, and reports the second public attribute information to the LRP application
  • the first public attribute information is the The public attribute information that the LRP application needs to advertise
  • the second public attribute information is the public attribute information that needs to be synchronized when the LRP database changes.
  • the common attribute information is uniformly transmitted and diffused through CAMC.
  • multiple LRP applications can share common attribute information without additional definition.
  • multiple LRP applications on the same port need to advertise the same When the attribute information is public, it only needs to be notified once to avoid waste of resources.

Landscapes

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

Abstract

本公开提供了一种桥接网络信息通告方法、设备、公共属性管理组件和计算机可读存储介质，其中，在桥接网络的每个节点的每个端口设置有CAMC，所述CAMC设置于LRP应用和LRP之间，所述方法包括：CAMC接收LRP应用通告的第一公共属性信息，将所述第一公共属性信息写入LRP的数据库；以及所述CAMC接收LRP的数据库上报的第二公共属性信息，将所述第二公共属性信息上报给LRP应用。通过本发明实施例，使得公共属性信息通过CAMC统一传递和扩散，一方面多个LRP应用可以共用公共属性信息，无需额外定义，另一方面，同一个端口上的多个LRP应用需要通告相同的公共属性信息时，只需要通告一次，从而避免资源浪费。

Description

一种桥接网络信息通告方法、设备和公共属性管理组件 技术领域
本文涉及但不限于一种桥接网络信息通告方法、设备、公共属性管理组件和计算机可读存储介质。
背景技术
LRP(Link-local Registration Protocol，链路本地注册协议)是由IEEE(Institute of Electrical and Electronics Engineers，电气和电子工程师协会)TSN(Time Sensitive Network,时间敏感网络)工作组提出的一种用于在网络中快速、可靠的逐跳分发信息的协议，具有可扩展性好，支持1MByte级别数据传输的优点。在LRP协议上，可以定义各种应用协议或组件，这些应用与LRP松耦合，各自定义属性值和语义，仅将LRP作为数据传输通道，通过调用LRP提供的服务原语声明和传播属性。
基于LRP的多种应用可能需要在桥接网络中通告一些公共信息，例如RAP(Resource Allocate Protocol,资源分配协议)需要在网络中各个节点间通告SR(Stream Reservation,流预留)Class(类)、队列传输选择算法、队列ClassMeasureInterval等信息来建立SR域，然后再基于SR域做资源分配，而其它协议也可能需要基于SR域做操作。然而目前，SR域信息通告是和RAP耦合在一起的，当其它协议也要使用SR域信息时，还需要自己额外定义和通告这些信息，可能造成规范的不一致和网络资源的浪费。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例提供了一种桥接网络信息通告方法、设备、公共属性管理组件和计算机可读存储介质。
本发明实施例提供了一种桥接网络信息通告方法，在桥接网络的每个节点的每个端口设置有公共属性管理组件CAMC，所述CAMC设置于链路本地注册协议LRP应用和LRP之间，所述方法包括：CAMC接收LRP应用通告的第一公共属性信息，将所述第一公共属性信息写入LRP的数据库；以及所述CAMC接收LRP的数据库上报的第二公共属性信息，将所述第二公共属性信息上报给LRP应用；其中，所述第一公共属性信息为所述LRP应用需要通告的公共属性信息，所述第二公共属性信息为所述LRP的数据库发生变化需要同步的公共属性信息。
本发明实施例还提供一种CAMC，所述CAMC设置于桥接网络的每个节点的每个端口的LRP应用和LRP之间，包括属性声明组件CADE、编码和解码组件CCDE以及属性注册组件CARE，其中，所述CADE设置为接收LRP应用通告的第一公共属性信息，并发送至所述CCDE；所述CCDE设置为将所述第一公共属性信息封装为TLV格式，将所述封装为TLV格式的第一公共属性信息写入LRP的数据库；以及，接收LRP的数据库上报的TLV封装格式的第二公共属性信息，将所述TLV封装格式的第二公共属性信息解封装，发送至所述CARE；所述CARE设置为将所述第二公共属性信息上报给LRP应用；其中，所述第一公共属性信息为所述LRP应用需要通告的公共属性信息，所述第二公共属性信息为所述LRP的数据库发生变化需要同步的公共属性信息。
本发明实施例还提供一种桥接网络信息通告设备，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现所述桥接网络信息通告方法。
本发明实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行所述桥接网络信息通告方法。
本发明实施例中，在桥接网络的每个节点的每个端口设置有CAMC，所述CAMC设置于LRP应用和LRP之间，CAMC接收LRP应用通告的第一公共属性信息，将所述第一公共属性信息写入LRP的数据库；以及 所述CAMC接收LRP的数据库上报的第二公共属性信息，将所述第二公共属性信息上报给LRP应用；其中，所述第一公共属性信息为所述LRP应用需要通告的公共属性信息，所述第二公共属性信息为所述LRP的数据库发生变化需要同步的公共属性信息。通过本发明实施例，使得公共属性信息通过CAMC统一传递和扩散，一方面多个LRP应用可以共用公共属性信息，无需额外定义，另一方面，同一个端口上的多个LRP应用需要通告相同的公共属性信息时，只需要通告一次，从而避免资源浪费。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图说明
图1是本发明实施例的Record LRPDU的封装格式示意图；
图2是本发明实施例的每个Record的编码格式示意图；
图3是本发明实施例的CAMC、LRP和LRP应用的关系示意图；
图4是本发明实施例的桥接网络信息通告方法的流程图；
图5是本发明实施例的步骤101的流程图；
图6是本发明实施例的步骤201的流程图；
图7是本发明另一实施例的桥接网络信息通告方法的流程图；
图8是本发明实施例的桥接网络信息通告方法中实现扩散的流程图；
图9是本发明实施例的桥接网络信息通告方法中实现查询的流程图；
图10是本发明实施例的查询时序图；
图11是本发明实施例的CAMC组成示意图；
图12是本发明实施例的LRP应用通过CAMC通告属性信息的流程图；
图13是本发明应用实例一的流程图；
图14是本发明应用实例二的流程图；
图15是本发明实施例的(a)和(b)是TLV编码格示意图。
具体实施方式
下文中将结合附图对本发明的实施例进行详细说明。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
为了给LRP应用提供各种应用无关的公共信息通告服务，本发明实施例基于LRP提出一种组件，称为CAMC(Common Attributes Management Component,公共属性管理组件)，该组件作为公用组件，专门用来在桥接网络中基于Record LRPDU(Link-local Registration Protocol Data Unit，链路本地注册协议数据单元)以TLV(Type，Length，Value，类型、长度和值)的编码格式通告各种公共信息，CAMC组件为其它协议或组件提供信息通告服务。
在桥接网络的每个节点的每个端口设置CAMC，所述CAMC设置于LRP应用和LRP之间。
在桥接网络中，可能需要通告的公共信息有很多，例如端口带宽剩余可用资源可以被RAP使用，也可以被PCE(Path Computation Element,路径计算单元)用来作为算路依据。本发明实施例列出各种可以由CAMC通告的信息，包括但不限于下表一列出的内容。
表一 可通过CAMC通告的公共信息列表
Figure PCTCN2020093031-appb-000001
Figure PCTCN2020093031-appb-000002
Figure PCTCN2020093031-appb-000003
对需要通告的信息，以TLV格式编码并通过LRPDU携带，在LRP已经定义的各种LRPDU中，使用Record LRPDU携带Data(数据)。Record LRPDU的封装格式如图1所示，每个Record LRPDU可以携带0个或多个Record，每个Record的编码格式如图2所示，其中每个Application Data(应用数据)字段可以用来携带多个需要通告的信息TLV。每种信息的TLV编码格式可根据实际需要或已有技术选取，本发明实施例不再赘述。
CAMC可以为多个LRP应用提供公共信息的通告服务，这些LRP应用也能够通告各自特定的属性信息。CAMC、LRP和其它各LRP的应用协议或组件的关系示意图如图3所示，各LRP应用的公共属性可以选择通过CAMC通告(带箭头虚线)，LRP应用各自特定的属性可以自己进行通告(带箭头实线)，例如RAP的SR域属性可以选择使用CAMC协议通告，而RAP资源分配相关的属性由自己定义并通过调用LRP原语进行通告。
CAMC定义的内容包括：
1、各公共属性的类型和值及关联的语义，表示需要通告的各种信息，例如属性类型为“队列传输选择算法”，属性值为1，表示基于信用的整 形(Credit-Based Shaper,CBS)算法；
2、用于在Record LRPDU中携带各种属性类型和值的TLV编码格式；
3、CAMC组件特定的appID；
4、在CAMC之上，为RAP、PCE等其它LRP应用或组件提供三种原语，分别为信息通告服务原语、信息查询服务原语和信息上报原语。RAP等应用可以调用信息查询服务原语查询本端口某信息是否已经通告以及其它端口通告的信息，当同一个端口上的多个应用需要通告附表一所列相同信息时，只需要通告一次，从而避免资源浪费。
如图4所示，本发明实施例的桥接网络信息通告方法，包括：
步骤101，CAMC接收LRP应用通告的第一公共属性信息，将所述第一公共属性信息写入LRP的数据库。
其中，所述第一公共属性信息为所述LRP应用需要通告的公共属性信息。
如图5所示，在一实施例中，所述步骤101可以包括：
步骤201，所述CAMC接收LRP应用通过CAMC信息通告服务原语通告的第一公共属性信息。
步骤202，所述CAMC将所述第一公共属性信息封装为TLV格式，调用LRP Write Record Request(写记录请求)原语将所述第一公共属性信息写入LRP的Applicant(申请)数据库。
其中，在封装时，将所述第一公共属性信息和本端口的信息一起进行封装，发送给LRP的Applicant数据库。
步骤102，所述CAMC接收LRP的数据库上报的第二公共属性信息，将所述第二公共属性信息上报给LRP应用。
其中，所述第二公共属性信息为所述LRP的数据库发生变化需要同步的公共属性信息。
如图6所示，在一实施例中，步骤102包括：
步骤301，所述CAMC接收LRP的Registrar数据库通过LRP Record Write Indication(记录写标识)原语上报的TLV封装格式的第二公共属性信息。
步骤302，所述CAMC将所述TLV封装格式的第二公共属性信息解封装，将所述第二公共属性信息通过CAMC信息上报原语上报给本端口的所有LRP应用。
需要说明的是，所述步骤101和102的执行没有先后顺序。本实施例是针对一个端口的CAMC进行的说明，在实际应用中，当LRP应用通过本端口的CAMC将公共属性信息写入LRP的Applicant数据库时，LRP将Applicant数据库变化的Record同步至邻居Registrar数据库中，该邻居Registrar数据库对应的CAMC会将该公共属性信息上报给该CAMC对应的所有LRP应用。
如图7所示，在一实施例中，步骤102之后，所述方法还包括：
步骤103，所述CAMC确定所述第二公共属性信息需要扩散，将所述第二公共属性信息扩散至本节点其他端口的CAMC。
其中，可以通过查询CPFT(CAMC attribute Propagation Flag Table,属性扩散标志表)确定所述第二公共属性信息需要扩散。
所述CPFT位于所述CAMC中，可以由LRP应用负责配置或由用户静态配置。
如图8所示，在一实施例中，所述方法还包括：
步骤401，所述CAMC接收本节点其他端口的CAMC扩散的第三公共属性信息，所述第三公共属性信息为需要扩散的公共属性信息。
其中，本步骤对应步骤103，为其他端口扩散至本端口的公共属性信息。
步骤402，所述CAMC将所述第三公共属性信息写入LRP的数据库。
其中，步骤402之后，当本地LRP的数据库更新后，所述CAMC接 收所述LRP的数据库发送所述第三公共属性信息，所述CAMC向本端口所有LRP应用发送所述第三公共属性信息。
如图9所示，在一实施例中，所述方法还包括：
步骤501，所述CAMC接收到LRP应用发送的查询请求，所述查询请求用于查询指定的属性信息。
其中，在一实施例中，所述CAMC接收所述LRP应用通过CAMC查询服务原语发送的查询请求。
步骤502，所述CAMC查询LRP数据库，向所述LRP应用返回查询结果。
在一实施例中，所述步骤502，包括：
所述CAMC调用LRP Database Request查询原语查询LRP数据库，获取所述属性信息；所述CAMC根据所述属性信息和筛选策略确定查询结果，向所述LRP应用返回所述查询结果。
为LRP应用提供查询服务时，CAMC作为垫层，LRP需提供LRP Database Request原语，该原语剥去Record ID、checksum、sequenceNum等内容，返回数据库Record的Data内容，总的查询时序图如图10所示，流程如下：
步骤601，LRP应用调用CAMC查询服务原语，查询某属性信息，包括本端口是否已通告该属性和其它端口通告到本端口的该属性信息；
步骤602，CAMC调用LRP Database Request查询原语，查询LRP数据库；
步骤603，LRP数据库返回数据库查询结果，即携带该属性信息的Record Application Data信息；
步骤604，CAMC提取该属性信息，并按照一定策略进行筛选、整合属性信息(如，根据上层LRP应用需求筛选某个节点或者端口的属性，或者整个域内所有节点属性，或者标记本端口是否已经通告该属性等)；
步骤605，CAMC向上层LRP应用返回查询结果。
如图11所示，本发明实施例的CAMC包括以下几个组件，各组件的功能和相互协作流程如下：
CADE(CAMC Attribute Declaration Entity,属性声明组件)71，一个per-Portal组件，处理该Portal上的公共属性声明事件，由bridge(桥)上通过CPPE74从其他端口注册的属性触发(图中⑦)，或由RAP等应用发出的CAMC服务请求原语触发(图中①)，CADE的输出被传递给CCDE(图中②)73；
CARE(CAMC Attribute Registration Entity,属性注册组件)72，一个per-Portal组件，处理发生在该Portal上的公共属性注册事件，通过接收来自CCDE73的属性而被触发(图中⑤)。CARE72的输出被发送到RAP等应用中(图中⑧)，查询CPFT(图中⑨)判断是否需要通过CPPE74扩散(图中⑥)；
CCDE(CAMC Coding and Decoding Entity,编码和解码组件)73，一个per-Portal组件，将CAMC属性做相应TLV格式的编码并发送到LRP(图中③)或从LRP接收信息并做TLV解码(图中④)；
CPPE(CAMC attribute Propagation and Processing Entity,属性传播组件)74，一个per-Bridge组件，在per-Poral CAMC组件之间传播属性声明；每个节点的所有端口共用一个CPPE74；
CPFT(CAMC attribute Propagation Flag Table,属性扩散标志表)75，表示端口收到的属性注册声明是否需要通过CPPE74扩散到其它端口，表有两种生成方式：由LRP应用负责配置或由用户静态配置。
在本发明实施例中，所述CADE71用于接收LRP应用通告的第一公共属性信息，并发送至所述CCDE73；
所述CCDE73设置为将所述第一公共属性信息封装为TLV格式，将所述封装为TLV格式的第一公共属性信息写入LRP的数据库；以及，接 收LRP的数据库上报的TLV封装格式的第二公共属性信息，将所述TLV封装格式的第二公共属性信息解封装，发送至所述CARE72；
所述CARE72设置为将所述第二公共属性信息上报给LRP应用；
其中，所述第一公共属性信息为所述LRP应用需要通告的公共属性信息，所述第二公共属性信息为所述LRP的数据库发生变化需要同步的公共属性信息。
在一实施例中，所述CARE72还设置为通过查询CPFT75确定所述第二公共属性信息需要扩散，则将所述第二公共属性信息发送给所述CPPE74；
所述CPPE74设置为将所述第二公共属性信息扩散至本节点其他端口的CAMC中的CADE。
在一实施例中，所述CADE71还设置为接收所述CPPE74扩散的第三公共属性信息，将所述第三公共属性信息发送至所述CCDE73，所述第三公共属性信息为需要扩散的公共属性信息；
所述CCDE73还设置为将所述第三公共属性信息封装为TLV格式，将所述封装为TLV格式的第三公共属性信息写入LRP的数据库。
在一实施例中，所述CADE71还设置为接收LRP应用发送的查询请求，将所述查询请求发送给CCDE73，所述查询请求用于查询指定的属性信息；
所述CCDE73还设置为将所述查询请求封装为TLV格式，查询LRP数据库，获取所述属性信息，发送至所述CARE72；
所述CARE72还设置为根据所述属性信息和筛选策略确定查询结果，向所述LRP应用返回所述查询结果。
如图12所示，LRP应用通过CAMC通告属性信息的流程包括：
步骤801，LRP应用通过调用CAMC信息通告服务原语通告属性信息；
步骤802，CAMC内部负责信息通告的组件CADE将请求信息连同本端口信息一同发送至CCDE组件；
步骤803，CCDE组件将信息封装为TLV格式，并调用LRP Write Record Request原语将属性写入Applicant数据库；
步骤804，LRP将Applicant数据库变化的Record同步至邻居Registrar数据库中；
步骤805，邻居Registrar数据库的变化通过LRP Record Write Indication原语上报给邻居CCDE组件；
步骤806，邻居CCDE组件将收到的信息做TLV解封，得到属性信息，交给CARE组件，CARE组件通过CAMC信息上报原语将属性信息上报给所有LRP应用；
步骤807，判断是否有其它端口，如果没有，结束流程，如果有，执行步骤808；
步骤808，CARE组件查询CPFT表，查询该属性是否需要扩散，若需要扩散，将属性通告请求发送至CPPE组件，CPPE组件进一步请求其它端口CAMC的CADE组件通告该属性，返回执行步骤801。
通过本发明实施例，使得公共属性信息通过CAMC统一传递和扩散，一方面多个LRP应用可以共用公共属性信息，无需额外定义，另一方面，同一个端口上的多个LRP应用需要通告相同的公共属性信息时，只需要通告一次，从而避免资源浪费。
下面以一些应用实例进行说明。
应用实例一：
本应用实例举例说明使用CAMC通告信息的流程，如图13所示。假设有两个设备System A和System B，A的Port1和B的Port1为组件CAMC建立Portal关联，System B共有两个Port，另一个Port为Port2，RAP请 求CAMC通告“System A的端口Port1的剩余可用带宽”信息，System B Port1的CPFT表配置该信息需扩散，则通告流程如下：
步骤901，System A port1上应用调用CAMC原语通告“剩余可用带宽”；
步骤902，System A port1上CADE组件收到“剩余可用带宽”通告请求原语，通告属性为剩余可用带宽值；
步骤903，CADE组件将请求发送至CCDE组件，请求内容为<System A,port1,通告类型(假设类型001表示剩余可用带宽)，值>，CCDE将请求封装为TLV格式，并调用LRP Write Record Request原语将TLV写入System A port1对应Portal的Applicant数据库的Record中；
步骤904，LRP将System A port1数据库Record变化通过Record LRPDU同步到System B port1Registrar数据库中，然后通过LRP Record Write Indication原语通告至System B Port1 CCDE组件；
步骤905，System B port1的CCDE组件将收到的Record包含的TLV解封装，并上交到CARE组件；
步骤906，System B Port1的CARE组件将解析得到的System A Port1剩余带宽可用值，通过信息上报原语通告给System B上的RAP应用和其它LRP应用；
步骤907，System B Port1的CARE组件收到“System A port1剩余可用带宽信息”，判断是否有其它端口，如果没有，结束流程，如果有，执行步骤908；
步骤908，CARE组件查询CPFT表发现需要扩散，通过CPPE组件通告给System B Port2的CADE组件，System B Port2 CADE进一步通告的流程和步骤902～907相同。
应用实例二：
本应用实例说明多个应用通过CAMC通告相同信息时的工作流程，如图14所示。假设RAP和PCE均需要通过CAMC通告端口SR class信息，假设此前未通告此属性，工作流程如下：
步骤1001，RAP通过调用CAMC提供的查询服务原语，查询本端口的SR Class信息是否通告(已通告的属性会记录在Portal的Applicant库中)；
步骤1002，CAMC查询服务原语判断该SR class信息是否已经被其它应用通告，若否，执行步骤1003，若是，执行步骤1004；
步骤1003，CAMC返回中指示本端口该信息未通告，RAP采用应用实例一中的流程，将本端口SR Class信息通告出去，其它设备端口采用同样方式，将各端口SR Class信息通告至本端口；
步骤1004，RAP使用CAMC提供的查询服务原语，查询关联的Portal中记录的SR Class信息(可以是全部或部分端口的SR Class信息)，建立SR域(然后可以根据SR域进行资源分配)。
PCE为通告本端口SR Class信息，首先调用CAMC查询服务原语，返回数据中指示本端口属性已通告，则不需重复通告本端口SR Class信息，返回的输出中携带了网络中已通告的各端口SR Class信息，从而亦可建立SR域(后续可以根据SR域信息进行算路)。
下面SR域信息举例说明TLV编码格，如图15(a)所示。
Type字段本身占2字节，Length本身占2字节，Length字段的值指定了Data Value字段所占的字节数。规定需要通告SR域信息、Type值和占用的字节数如下，各TLV格式如图15(b)所示：
SRclassId：Type＝1,Length＝1字节
SRclassPriority：Type＝2,Length＝1字节
TransmissionSelectioin：Type＝3,Length＝1字节
ClassMeasureInterval：Type＝4,Length＝1字节
SRClassMaxFrameSize：Type＝5,Length＝2字节
SRClassTargetMaxLatency：Type＝6,Length＝4字节
如图2所示，Application Data字段可携带数据的最大大小为65520字节，所以一个Record可以携带多个TLV，例如通告SR域信息的TLV均可以通过一个Record携带。本发明实施例的CAMC的CCDE组件负责各公共属性TLV的编码和解码。
本发明实施例还提供一种桥接网络信息通告设备，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现所述桥接网络信息通告方法。
本发明实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行所述桥接网络信息通告方法。
在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失 性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
工业实用性
本发明实施例中，在桥接网络的每个节点的每个端口设置有CAMC，所述CAMC设置于LRP应用和LRP之间，CAMC接收LRP应用通告的第一公共属性信息，将所述第一公共属性信息写入LRP的数据库；以及所述CAMC接收LRP的数据库上报的第二公共属性信息，将所述第二公共属性信息上报给LRP应用；其中，所述第一公共属性信息为所述LRP应用需要通告的公共属性信息，所述第二公共属性信息为所述LRP的数据库发生变化需要同步的公共属性信息。通过本发明实施例，使得公共属性信息通过CAMC统一传递和扩散，一方面多个LRP应用可以共用公共属性信息，无需额外定义，另一方面，同一个端口上的多个LRP应用需要通告相同的公共属性信息时，只需要通告一次，从而避免资源浪费。

Claims (14)

  1. 一种桥接网络信息通告方法，在桥接网络的每个节点的每个端口设置有公共属性管理组件CAMC，所述CAMC设置于链路本地注册协议LRP应用和LRP之间，所述方法包括：
    CAMC接收LRP应用通告的第一公共属性信息，将所述第一公共属性信息写入LRP的数据库；以及
    所述CAMC接收LRP的数据库上报的第二公共属性信息，将所述第二公共属性信息上报给LRP应用；
    其中，所述第一公共属性信息为所述LRP应用需要通告的公共属性信息，所述第二公共属性信息为所述LRP的数据库发生变化需要同步的公共属性信息。
  2. 如权利要求1所述的方法，其中，所述CAMC接收LRP应用通告的第一公共属性信息，将所述第一公共属性信息写入LRP的数据库，包括：
    所述CAMC接收LRP应用通过CAMC信息通告服务原语通告的第一公共属性信息；
    所述CAMC将所述第一公共属性信息封装为类型长度值TLV格式，调用LRP写记录请求原语将所述第一公共属性信息写入LRP的Applicant数据库。
  3. 如权利要求1所述的方法，其中，所述CAMC接收LRP的数据库上报的第二公共属性信息，将所述第二公共属性信息上报给LRP应用，包括：
    所述CAMC接收LRP的Registrar数据库通过LRP记录写标识原语上报的TLV封装格式的第二公共属性信息；
    所述CAMC将所述TLV封装格式的第二公共属性信息解封装，将所述第二公共属性信息通过CAMC信息上报原语上报给本端口的所有LRP应用。
  4. 如权利要求1所述的方法，其中，所述CAMC接收LRP的数据库上报的第二公共属性信息，将所述第二公共属性信息上报给LRP应用之后，所述方法还包括：
    所述CAMC确定所述第二公共属性信息需要扩散，将所述第二公共属性信息扩散至本节点其他端口的CAMC。
  5. 如权利要求4所述的方法，其中，所述确定所述第二公共属性信息需要扩散，包括：
    通过查询属性扩散标志表CPFT确定所述第二公共属性信息需要扩散。
  6. 如权利要求1所述的方法，其中，所述方法还包括：
    所述CAMC接收本节点其他端口的CAMC扩散的第三公共属性信息，所述第三公共属性信息为需要扩散的公共属性信息；
    所述CAMC将所述第三公共属性信息写入LRP的数据库。
  7. 如权利要求1所述的方法，其中，所述方法还包括：
    所述CAMC接收到LRP应用发送的查询请求，所述查询请求用于查询指定的属性信息；
    所述CAMC查询LRP数据库，向所述LRP应用返回查询结果。
  8. 如权利要求7所述的方法，其中，
    所述CAMC接收到LRP应用发送的查询请求，包括：所述CAMC接收所述LRP应用通过CAMC查询服务原语发送的查询请求；
    所述CAMC查询LRP数据库，向所述LRP应用返回查询结果，包括：所述CAMC调用LRP数据库查询原语查询LRP数据库，获取所述属性信息；所述CAMC根据所述属性信息和筛选策略确定查询结果，向所述LRP应用返回所述查询结果。
  9. 一种CAMC，所述CAMC设置于桥接网络的每个节点的每个端口的LRP应用和LRP之间，包括属性声明组件CADE、编码和解码组件CCDE以及属性注册组件CARE，其中
    所述CADE设置为接收LRP应用通告的第一公共属性信息，并发送至所述CCDE；
    所述CCDE设置为将所述第一公共属性信息封装为TLV格式，将所述封装为TLV格式的第一公共属性信息写入LRP的数据库；以及，接收LRP的数据库上报的TLV封装格式的第二公共属性信息，将所述TLV封装格式的第二公共属性信息解封装，发送至所述CARE；
    所述CARE设置为将所述第二公共属性信息上报给LRP应用；
    其中，所述第一公共属性信息为所述LRP应用需要通告的公共属性信息，所述第二公共属性信息为所述LRP的数据库发生变化需要同步的公共属性信息。
  10. 如权利要求9所述的CAMC，其中，还包括：属性扩散标志表CPFT和属性传播组件CPPE，每个节点的所有端口共用一个CPPE；
    所述CARE还设置为通过查询CPFT确定所述第二公共属性信息需要扩散，则将所述第二公共属性信息发送给所述CPPE；
    所述CPPE将所述第二公共属性信息扩散至本节点其他端口的CAMC中的CADE。
  11. 如权利要求10所述的CAMC，其中，
    所述CADE还设置为接收所述CPPE扩散的第三公共属性信息，将所述第三公共属性信息发送至所述CCDE，所述第三公共属性信息为需要扩散的公共属性信息；
    所述CCDE还设置为将所述第三公共属性信息封装为TLV格式，将所述封装为TLV格式的第三公共属性信息写入LRP的数据库。
  12. 如权利要求9所述的CAMC，其中，
    所述CADE还设置为接收LRP应用发送的查询请求，将所述查询请求发送给CCDE，所述查询请求用于查询指定的属性信息；
    所述CCDE还设置为将所述查询请求封装为TLV格式，查询LRP数据库，获取所述属性信息，发送至所述CARE；
    所述CARE还设置为根据所述属性信息和筛选策略确定查询结果，向所述LRP应用返回所述查询结果。
  13. 一种桥接网络信息通告设备，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现如权利要求1～8中任意一项所述桥接网络信息通告方法。
  14. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1～8中任意一项所述桥接网络信息通告方法。
PCT/CN2020/093031 2019-07-22 2020-05-28 一种桥接网络信息通告方法、设备和公共属性管理组件 WO2021012782A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020217038277A KR20210151224A (ko) 2019-07-22 2020-05-28 브리지 네트워크 정보 통보 방법, 기기 및 공통 속성 관리 컴포넌트
EP20844110.5A EP3958518B1 (en) 2019-07-22 2020-05-28 Information announcement on a bridge network
JP2021569506A JP7327767B2 (ja) 2019-07-22 2020-05-28 ブリッジネットワーク情報アドバタイズ方法、デバイス、およびパブリック属性管理コンポーネント
US17/620,112 US20220368562A1 (en) 2019-07-22 2020-05-28 Method and device for advertising information in bridge network and common attributes management component

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910662470.7 2019-07-22
CN201910662470.7A CN112260923B (zh) 2019-07-22 2019-07-22 一种桥接网络信息通告方法和设备

Publications (1)

Publication Number Publication Date
WO2021012782A1 true WO2021012782A1 (zh) 2021-01-28

Family

ID=74193198

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/093031 WO2021012782A1 (zh) 2019-07-22 2020-05-28 一种桥接网络信息通告方法、设备和公共属性管理组件

Country Status (6)

Country Link
US (1) US20220368562A1 (zh)
EP (1) EP3958518B1 (zh)
JP (1) JP7327767B2 (zh)
KR (1) KR20210151224A (zh)
CN (1) CN112260923B (zh)
WO (1) WO2021012782A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104620550A (zh) * 2012-07-20 2015-05-13 哈曼国际工业有限公司 在多个音频视频桥接网络上的流的服务质量
CN108293072A (zh) * 2015-11-30 2018-07-17 西门子股份公司 经由tsn进行工业通讯的方法
WO2018162071A1 (de) * 2017-03-10 2018-09-13 Siemens Aktiengesellschaft Verfahren und vorrichtung zur modularen lenkung eines avb-streams

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3846625B2 (ja) * 2001-10-23 2006-11-15 Ｋｄｄｉ株式会社 モバイルｉｐを利用したデータ転送方式
EP1569384B1 (en) * 2004-02-25 2007-05-23 Sony Deutschland GmbH Method for wireless data transfer
MX2009006147A (es) * 2007-01-19 2009-06-26 Ericsson Telefon Ab L M Metodo y aparato para manejo de arbol de red.
EP1976195B1 (en) * 2007-03-30 2014-05-07 Alcatel-Lucent Method and apparatus for Mac address learning
CN101252514B (zh) * 2008-02-29 2011-02-23 中兴通讯股份有限公司 基于多对一接入方式的骨干桥接网络中的数据转发方法
US9705653B2 (en) * 2009-05-04 2017-07-11 Qualcomm Inc. Downlink control transmission in multicarrier operation
US8675689B2 (en) * 2011-02-15 2014-03-18 General Electric Company Method of time synchronization of free running nodes in an avionics network
CN106445588B (zh) * 2016-09-08 2018-05-04 腾讯科技（深圳）有限公司 属性信息的更新方法及装置
CN108737454B (zh) * 2017-04-13 2020-11-06 上海诺基亚贝尔股份有限公司 用于在虚拟网关服务器间进行信息同步的方法和设备
CA3159276A1 (en) * 2018-04-10 2019-10-17 Huawei Technologies Co., Ltd. Point-to-point database synchronization over a transport protocol
CN111970137B (zh) * 2019-05-20 2022-04-05 华为技术有限公司 Tsn中控制器间通信的方法、装置及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104620550A (zh) * 2012-07-20 2015-05-13 哈曼国际工业有限公司 在多个音频视频桥接网络上的流的服务质量
CN108293072A (zh) * 2015-11-30 2018-07-17 西门子股份公司 经由tsn进行工业通讯的方法
WO2018162071A1 (de) * 2017-03-10 2018-09-13 Siemens Aktiengesellschaft Verfahren und vorrichtung zur modularen lenkung eines avb-streams

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
TAO HUANG, SHUO WANG, YUDONG HUANG, YAO ZHENG, JIANG LIU, YUNJIE LIU: "Survey of the deterministic network", JOURNAL ON COMMUNICATIONS, vol. 40, no. 6, 25 June 2019 (2019-06-25), pages 160 - 176, XP055778370, ISSN: 1000-436x, DOI: 10.11959/j.issn.1000−436x.2019119 *
TIME-SENSITIVE NETWORKING TASK GROUP OF IEEE 802.1 OF THE LAN MAN STANDARDS COMMITTEE OF THE IEEE COMPUTER SOCIETY: "IEEE P802.1 CS/D2.0 Draft Standard for Local and metropolitan area networks — Link-local Registration Protocol", IEEE DRAFT; 802-1CS-D2-0, 6 December 2018 (2018-12-06), XP068135283 *

Also Published As

Publication number Publication date
US20220368562A1 (en) 2022-11-17
EP3958518A4 (en) 2022-06-08
CN112260923A (zh) 2021-01-22
EP3958518A1 (en) 2022-02-23
JP2022541711A (ja) 2022-09-27
CN112260923B (zh) 2023-05-02
JP7327767B2 (ja) 2023-08-16
EP3958518B1 (en) 2023-06-21
KR20210151224A (ko) 2021-12-13

Similar Documents

Publication Publication Date Title
WO2015081786A1 (zh) 订阅通知的实现方法和装置
WO2019029320A1 (zh) 一种配置管理方法、装置及设备
WO2020164290A1 (zh) 策略控制方法、装置及系统
TW202106072A (zh) 路由器的ｓｓｉｄ獲取方法、裝置、設備和系統
WO2018090191A1 (zh) 网络功能的管理方法、管理单元及系统
US11963124B2 (en) Entities for providing an external service to a network
WO2020248996A1 (zh) QoS处理及控制方法及网络接口控制器
CN110519388B (zh) 区块链请求的处理方法、装置、电子设备及可读存储介质
WO2021012782A1 (zh) 一种桥接网络信息通告方法、设备和公共属性管理组件
CN110505478A (zh) 解码资源的管理方法、装置、设备和介质
CN114760197A (zh) 算力节点管理方法、装置、设备及可读存储介质
US11405766B2 (en) Connecting computer processing systems and transmitting data
WO2019007403A1 (zh) 业务配置驱动流表的方法及装置
WO2017000540A1 (zh) 数据查询方法及装置
US20210250962A1 (en) Connecting computer processing systems and transmitting data
US20210250425A1 (en) Connecting computer processing systems and transmitting data
CN113051202A (zh) 接口适配方法、装置、电子设备和计算机可读存储介质
WO2020220987A1 (zh) 数据包传输、管理方法、装置及数据转发设备、存储介质
TWI682647B (zh) 提升智慧電錶至伺服器間效能的方法及裝置
WO2021103009A1 (zh) 上行pdr的生成方法、装置及系统
WO2014183525A1 (zh) 报文的处理方法和级联芯片
WO2024011669A1 (zh) 消息编码及解码方法、处理装置和存储介质
WO2021115447A1 (zh) 会话管理网元发现的方法、设备及系统
WO2024034057A1 (ja) ネットワーク管理装置、ネットワーク管理方法及びプログラム
CN116527738A (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: 20844110

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021569506

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2020844110

Country of ref document: EP

Effective date: 20211119

NENP Non-entry into the national phase

Ref country code: DE