WO2021196774A1 - 发送和处理信息的方法、以太网设备、计算机可读介质 - Google Patents

发送和处理信息的方法、以太网设备、计算机可读介质 Download PDF

Info

Publication number
WO2021196774A1
WO2021196774A1 PCT/CN2020/139944 CN2020139944W WO2021196774A1 WO 2021196774 A1 WO2021196774 A1 WO 2021196774A1 CN 2020139944 W CN2020139944 W CN 2020139944W WO 2021196774 A1 WO2021196774 A1 WO 2021196774A1
Authority
WO
WIPO (PCT)
Prior art keywords
oam
block
blocks
information
66bit
Prior art date
Application number
PCT/CN2020/139944
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 WO2021196774A1 publication Critical patent/WO2021196774A1/zh

Links

Images

Classifications

    • 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/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0823—Errors, e.g. transmission errors
    • H04L43/0847—Transmission error
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0852—Delays

Definitions

  • the embodiments of the present disclosure relate to the technical field of bearer operation management and maintenance ((Operation Administration and Maintenance, referred to as OAM)) information, and in particular to a method for sending and processing information, an Ethernet device, and a computer-readable medium.
  • OAM Operaation Administration and Maintenance
  • OAM operation, management and maintenance
  • PCS physical coding sublayer
  • the embodiments of the present disclosure provide a method for sending and processing information, an Ethernet device, and a computer-readable medium.
  • the embodiments of the present disclosure provide a method for sending information, which is used in the Ethernet physical coding sublayer.
  • the method includes: sending multiple 64/66Bit block business packets, and sending between at least part of the business packets
  • the 64/66Bit block that bears the OAM information for operation, management and maintenance; the 64/66Bit block that bears the OAM information is an OAM block.
  • the embodiments of the present disclosure provide a method for processing information, which is used in the Ethernet physical encoding sublayer.
  • the method includes: receiving multiple 64/66Bit block business packets and 64 bits between at least part of the business packets. /66Bit block; determine that at least part of the 64/66Bit block between the service packets is an OAM block that carries OAM information; extract the OAM block to obtain the OAM information.
  • an embodiment of the present disclosure provides an Ethernet device, which includes: a sending module configured to send multiple 64/66 Bit block business packets in the Ethernet physical encoding sublayer, and between at least part of the business packets A 64/66Bit block carrying OAM information is sent; the 64/66Bit block carrying OAM information is an OAM block.
  • an embodiment of the present disclosure provides an Ethernet device, which includes: a receiving module configured to receive a plurality of 64/66 Bit block business packets and a packet between at least some of the business packets in the Ethernet physical encoding sublayer 64/66Bit block; at least one processor, configured to determine that at least part of the 64/66Bit block between the service packets is an OAM block carrying OAM information; extract the OAM block to obtain the OAM information.
  • embodiments of the present disclosure provide a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, any one of the foregoing methods for sending information is implemented.
  • embodiments of the present disclosure provide a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, any one of the foregoing methods for processing information is implemented.
  • the OAM block that carries OAM information is sent between service packets, thereby providing a method for sending OAM information, and realizing functions such as service quality monitoring of the end-to-end channel of customer services; at the same time, the above OAM information
  • the transmission will not affect the transmission of normal service packets.
  • FIG. 1 is a flowchart of a method for sending information provided by an embodiment of the disclosure
  • FIG. 3 is a flowchart of a method for processing information provided by an embodiment of the disclosure
  • FIG. 4 is a block diagram of the composition of an Ethernet device provided by an embodiment of the disclosure.
  • FIG. 5 is a block diagram of another Ethernet device provided by an embodiment of the present disclosure.
  • FIG. 6 is a block diagram of a computer-readable medium provided by an embodiment of the present disclosure.
  • Figure 7 is a schematic diagram of the structure of the service flow
  • Figure 8 is a schematic diagram of the format of a 64/66B block
  • FIG. 9 is a schematic structural diagram of an OAM block (control block) in an embodiment of the disclosure.
  • FIG. 10 is a schematic structural diagram of an OAM block that independently carries OAM information in an embodiment of the disclosure.
  • FIG. 11 is a schematic diagram of a structure of multiple OAM blocks carrying OAM information in an embodiment of the disclosure
  • FIG. 12 is a schematic diagram of a structure in which all OAM blocks carry feature identifiers in an embodiment of the disclosure
  • FIG. 13 is a schematic structural diagram of a feature identifier carried by some OAM blocks in an embodiment of the disclosure.
  • FIG. 14 is a schematic diagram of a process of adding an OAM block in an embodiment of the disclosure.
  • FIG. 15 is a schematic structural diagram of a service flow after adding an OAM block in an embodiment of the disclosure.
  • FIG. 16 is a schematic diagram of a desired position when a fixed period is adopted in an embodiment of the disclosure.
  • FIG. 17 is a schematic diagram of a desired position when a variable period is adopted in an embodiment of the disclosure.
  • the embodiments of the present disclosure provide a method for sending information, which is used in the Ethernet physical coding sublayer.
  • the physical coding sublayer (PCS, Physical Coding Sublayer) is one of the physical layers of the Ethernet, and the physical layer is implemented by the physical interface transceiver (PHY). Specifically, the physical coding sublayer (PCS) is connected to the coordination sublayer (RS, Reconciliation Sublaye) at the top, and connected to the physical media access (PMA, Physical Media Attachment) layer at the bottom, and is used to implement data encoding and decoding.
  • PCS Physical Coding Sublayer
  • RS coordination sublayer
  • PMA Physical Media Attachment
  • the embodiments of the present disclosure are used for sending information in the physical coding sublayer, especially for sending Operation-Administration-Maintenance (OAM, Operation-Administration-Maintenance) information.
  • OAM Operation-Administration-Maintenance
  • OAM information refers to all information used to implement the operation, management, and maintenance process of the customer service channel in the Ethernet.
  • the method of the embodiment of the present disclosure includes:
  • S101 Send multiple 64/66 Bit blocks of business packets, and send 64/66 Bit blocks that carry OAM information between at least some of the business packets; 64/66 Bit blocks that carry OAM information are OAM blocks.
  • the service stream sent by the physical coding sublayer includes multiple service packages (customer service packages) corresponding to customer services.
  • Each business package is composed of multiple 64/66Bit blocks (that is, a business package of 64/66Bit blocks).
  • Multiple 64/66Bit blocks usually include a start block (a type of control block, which is used in Figure 7) to indicate the start of the business package. S indicates), the end block (a type of control block, indicated by T in FIG. 7) that indicates the end of the service packet, and the data block between the start block and the end block (indicated by D in FIG. 7).
  • there may be free blocks between different service packages (indicated by I in Figure 7).
  • a 64/66Bit block is also called a 64B/66B block, which refers to a 66Bit block used for transmission obtained by encoding 64Bit (bit) data or control information.
  • a 64/66Bit block structure defined in the related art can refer to FIG. 8, where the first two bits represent a synchronization header (sync), when it is 01, it represents a data block, and when it is 10, it represents a control block.
  • the following 8 bits represent the Block Type Field, such as 0x1E, 0x78, Ox4B, 0x87, 0x99, etc.
  • Different block type field values indicate different control blocks.
  • a 64/66Bit block carrying OAM information is added between different service packages, which is specifically called an OAM block (indicated by O in the figure), that is, OAM is sent between different service packages information.
  • control block with a block type field of 0x4B is taken as an example of an OAM block.
  • the OAM block is located between the business package means that for any OAM block, the first block that belongs to the business package before it must be the end block; and the first block that belongs to the business package after it must be the start block. ; In other words, the OAM block cannot be located "inside" the business package.
  • the OAM block is usually only located between part of the service packets, that is, there are OAM blocks between some adjacent service packets, but there are also some adjacent service packets without OAM blocks.
  • the OAM block that carries OAM information is sent between service packets, thereby providing a method for sending OAM information, and realizing functions such as service quality monitoring of the end-to-end channel of customer services; at the same time, the above OAM information
  • the transmission will not affect the transmission of normal service packets.
  • the OAM information includes at least one of the following OAM messages: connectivity check (CC), bit interleaved parity (BIP), remote error indication (REI), remote defect indication (RDI), Protection switching protocol (APS), delay measurement (DM, Delay Measurement), connectivity verification (CV, Connectivity Verification), client signal type.
  • connectivity check CC
  • bit interleaved parity BIP
  • REI remote error indication
  • RDI remote defect indication
  • Protection switching protocol APS
  • delay measurement DM, Delay Measurement
  • connectivity verification CV, Connectivity Verification
  • client signal type client signal type.
  • the specific content of the OAM information may include one or more of the above contents, each of which is referred to as an "OAM message".
  • OAM messages are only exemplary, rather than limiting the scope of OAM messages.
  • Other OAM messages can also be added as needed.
  • OAM information is carried by one OAM block.
  • each piece of OAM information may be completely carried by one OAM block, that is, each OAM block is one piece of OAM information.
  • the OAM block can be a designated single control block or data block (of course, no matter what block it is, it must be located between service packages).
  • the specific content of the OAM information can be carried by the bits after the block type field in the control block, or by the bits after the synchronization header of the data block.
  • Figure 10 is an example of a single OAM block carrying OAM information, where a control block with a block type field of 0x4B is used to carry bit interleaved parity (BIP), remote error indication (REI), and remote defect.
  • OAM messages such as indication (RDI).
  • OAM information is carried by multiple OAM blocks.
  • each piece of OAM information may also be carried by multiple OAM blocks respectively, that is, each OAM block separately carries part of the content of the OAM information.
  • multiple OAM blocks carrying OAM information can be multiple control blocks, multiple data blocks, a combination of one control block plus one or more data blocks, or multiple control blocks plus multiple data blocks. A combination of data blocks, etc.
  • Figure 11 is an example of multiple OAM blocks carrying OAM information, in which 5 data blocks (OAM block 1, OAM block 2, OAM block 3, OAM block 4, OAM block 5) are used to carry connectivity verification (CV ) Message.
  • the CV message is composed of source identification information SAPI and sink identification information DAPI. Both SAPI and DAPI are 16-byte characters.
  • each OAM block must be located between service packets, but it does not mean that multiple OAM blocks that carry one piece of OAM information must be between two specific service packets. , But multiple OAM blocks that carry a piece of OAM information can be distributed among multiple different service packages.
  • At least part of the OAM blocks carry feature identifiers; the feature identifiers are used to identify OAM information.
  • OAM blocks must be located between business packages, but the blocks between business packages are not necessarily OAM blocks (for example, there are free blocks), so some methods are needed to allow the receiving end to confirm which blocks between business packages are OAM Block and perform subsequent processing.
  • a feature identifier may be added to at least part of the OAM blocks.
  • the feature identifier can indicate the identity of the OAM block, that is, which block (including at least itself) is an OAM block that carries OAM information, Therefore, the receiving end can determine the OAM block by analyzing the feature identifier (such as whether there is a feature identifier and the meaning of the feature identifier) in the received block.
  • the feature identifier includes at least one of the following:
  • Feature identification can include specific data, that is, feature value, or "feature pattern”.
  • the feature identifier can also include a check value calculated based on other data, that is, by analyzing the relationship between the check value and other data, the type of the block (whether it is an OAM block) can be determined, and it can be found when the data has errors Errors, and even error correction.
  • the above check value can be a CRC check value (indicated by CRC in the figure), or other types of check values such as BIP and FEC.
  • the feature identifier may also include the above feature value and the check value at the same time.
  • Figure 9 is an example of an OAM block with a check value, which is a control block with a block type field of 0x4B and carries a CRC (or BIP, FEC) check value, so that it can pass "0x4B" and / Or "check value" to identify it.
  • CRC or BIP, FEC
  • the receiving end can also correct the errors of the OAM block under certain error conditions.
  • the above feature identifier can be directly carried in the OAM block.
  • OAM information is carried by multiple OAM blocks, and all OAM blocks carry feature identifiers.
  • all OAM blocks may carry the same characteristic identifier (if they have the same characteristic pattern), or each OAM block may carry its own characteristic identifier (such as its own check value), or each The OAM block carries a part of the feature identifier, that is, the sum of the feature identifiers carried by all OAM blocks is a complete feature identifier.
  • FIG. 12 shows a case where all OAM blocks carry feature identifiers, where OAM block 1, OAM block 2, and OAM block 3 carry feature value 1, feature value 2, and feature value 3 respectively.
  • OAM information is carried by multiple OAM blocks, and some OAM blocks carry feature identifiers, and some OAM blocks only carry OAM messages.
  • OAM blocks when a piece of OAM information is carried by multiple OAM blocks, it is also possible that only part (at least one) of the OAM blocks carry the feature identifier, and other OAM blocks only carry the content of the OAM information , Such as carrying only OAM messages.
  • OAM block 1 carries feature values
  • OAM block 2, OAM block 3, OAM block 4, and OAM block 5 do not carry feature values, and only carry OAM messages (contents of OAM information).
  • OAM block 1 and OAM block 2 respectively carry feature value 1 and feature value 2
  • OAM block 3 does not carry feature value, but only carries OAM message (content of OAM information).
  • the feature identifiers carried by these OAM blocks need to be able to indicate the identities of other OAM blocks.
  • the first OAM block that carries OAM information can carry a feature identifier, and it indicates which of the subsequent blocks are OAM blocks that carry the OAM information; or, it can also be the first and last OAM blocks that carry OAM information.
  • Carrying a characteristic identifier indicates that the block between two OAM blocks with a characteristic identifier is an OAM block that carries the same OAM information.
  • sending a 64/66Bit block (S101) carrying OAM information between at least some service packets includes:
  • the OAM block can also be sent every other predetermined period; in this way, the receiving end can determine whether the block is received in the predetermined period. To determine whether it is an OAM block.
  • the predetermined period can be limited by a specific time (such as how many seconds), but it is more preferably limited by the number of blocks.
  • the above method of sending OAM blocks according to the predetermined period and the method of adding feature identifiers to the OAM block may be used only one or at the same time, that is, the OAM block may be sent according to a certain period, and At the same time, at least part of the OAM blocks carry feature identifiers.
  • the predetermined period is a fixed period.
  • the predetermined period may be a constant period.
  • the predetermined period can be fixed to 16K blocks, and the blocks corresponding to each predetermined period are determined (represented by oblique blocks in the figure).
  • the predetermined period is a variable period determined according to a predetermined algorithm or a predetermined strategy.
  • the predetermined period may also be variable, that is, the specific length of each predetermined period is determined according to a predetermined algorithm or a predetermined strategy, so that the specific length of the predetermined period of different times can be changed. different.
  • the predetermined algorithm refers to calculating the specific length of the corresponding predetermined period in a predetermined manner in each period.
  • the predetermined strategy refers to determining the specific length of the predetermined period according to the corresponding strategy (or method) according to the situation of each period. For example, different predetermined periods can be set for different OAM message types according to a predetermined strategy. For example, the predetermined period of certain types of OAM messages is 16K blocks, and the predetermined period of certain types of OAM messages is 32K blocks, etc. .
  • the first predetermined period may be 16K blocks
  • the second predetermined period may be 32K blocks, etc.
  • the blocks corresponding to each predetermined period are determined (shown by diagonal blocks in the figure).
  • sending an OAM block carrying OAM information between service packets according to a predetermined period includes:
  • S10111 Determine the nominal position according to the predetermined period.
  • a position where the OAM block theoretically starts to be added can be determined according to each predetermined period, that is, the "nominal position", or the position strictly corresponding to the period (the oblique in Fig. 16 and Fig. 17).
  • the position of the line block may be between the service packets or inside the service packet.
  • the embodiments of the present disclosure require that the OAM block cannot be sent in the service packet, therefore:
  • the nominal position can be used as the joining position and directly added to the OAM block.
  • Figure 17 corresponds to the data block (indicated by D in Figure 7, Figure 14, Figure 15) or the start block (indicated by S in Figure 7, Figure 14, Figure 15), you need Find the first end block backwards (indicated by T in Figure 7, Figure 14, Figure 15), and then find the first start block after the end block, and after the first end block and the first An OAM block is added between the start blocks; and if the nominal position is the end block, the first start block is searched backwards, and the OAM block is added after the end block and between the first start block.
  • sending OAM blocks carrying OAM information between service packets according to a predetermined period includes sending one OAM block in each predetermined period.
  • only one OAM block may be added.
  • sending OAM blocks carrying OAM information between service packets according to a predetermined period includes sending multiple OAM blocks in each predetermined period.
  • more OAM blocks can also be added in each of the above predetermined cycles, that is, multiple OAM blocks are sent in each predetermined cycle.
  • multiple OAM blocks added in the same predetermined period can carry the same piece of OAM information, or can carry different OAM information.
  • the above predetermined period only determines the timing of sending OAM blocks, and does not limit the number and content of OAM blocks sent (such as whether there is a feature identifier), etc.
  • the timing of sending the OAM block can also be determined in other ways. For example, it can be when there is a need to send OAM information (if there is a fault that triggers the generation of OAM information, or when a user's command is received) , That is, send the OAM block (for example, between the current service package and the next service package).
  • sending a 64/66 Bit block (S101) carrying OAM information between at least part of the service packets includes: replacing at least one free block between the service packets with an OAM block and sending it.
  • OAM blocks are sent between service packets, and there may be blocks that do not carry any information between service packets, that is, there are "free blocks". Therefore, referring to Figures 14 and 15, as a way of the embodiments of the present disclosure, when it is determined that there is a free block between two adjacent service packets to be added to the OAM block, the free block can be directly replaced with the OAM block ( It is represented by O1 in the figure), that is, the free block is deleted and the OAM block is added at the same position.
  • sending a 64/66 Bit block carrying OAM information between at least part of the service packets (S101) includes: inserting at least one OAM block between the service packets.
  • OAM block (indicated by O2 in the figure) is directly inserted between two adjacent service packets, or "newly added" OAM blocks between two adjacent service packets; and each subsequent 64 in the original service flow /66Bit block, after the inserted OAM block, continue to send.
  • the above methods of inserting the OAM block and replacing the OAM block can be used in only one, or can be mixed. For example, it can be inserted into the OAM block regardless of whether there is a free block; or, it can be added to the OAM block only by replacement (if there is no free block between the service packages, wait for the free block to appear); or, It may also be that when there is a free block, the replacement method is preferentially used to add the OAM block, and when there is no free block or the free block is insufficient, the insertion method is used to add the OAM block.
  • a predetermined position of each OAM block carries a predetermined OAM message.
  • OAM blocks need to carry OAM information, and the specific methods for each OAM block to carry OAM information are diverse.
  • a Bit encoding method can be used, that is, an OAM message (specific content of OAM information) carried at each position is defined in the OAM block, so that a specific position of the OAM block carries a specific OAM message (if When there is no corresponding OAM message, the corresponding position can be a specific value representing "empty").
  • each OAM block carries one or more pre-classified OAM messages.
  • a message encoding method can also be adopted, that is, different OAM messages are classified, and each OAM block carries one or more classified OAM messages, or multiple OAM blocks carry the same An OAM message.
  • the embodiments of the present disclosure provide a method for processing information, which is used in the Ethernet physical coding sublayer.
  • the embodiments of the present disclosure are used for processing information in the physical coding sublayer (PCS) of the Ethernet, especially for processing the received operation management and maintenance (OAM) information.
  • PCS physical coding sublayer
  • OAM operation management and maintenance
  • the method of the embodiment of the present disclosure includes:
  • S201 Receive a plurality of 64/66 Bit blocks of business packets and 64/66 Bit blocks located between at least some of the business packets.
  • S202 Determine that at least part of the 64/66 Bit blocks located between the service packets are OAM blocks that carry OAM information.
  • the receiving end will receive multiple service packets and blocks between the service packets (may be OAM blocks, or free blocks and other blocks), so the receiving end needs to distinguish services Which of the blocks between packets are OAM blocks that carry OAM information, and extract these OAM blocks to obtain OAM information.
  • OAM blocks may be OAM blocks, or free blocks and other blocks
  • determining that at least part of the 64/66Bit blocks located between the service packets are the OAM blocks that carry OAM information (S202) includes: determining at least a feature identifier carried in the 64/66Bit blocks located between the service packets Part of the 64/66Bit blocks between the service packets are OAM blocks that carry OAM information; the feature identifier is used to identify OAM information.
  • the receiver can search for the feature identifier in the block located between the service packets, and determine which feature identifier is found based on the found feature identifier. Which are OAM blocks.
  • determining that at least part of the 64/66 Bit blocks between the service packets are OAM blocks that carry OAM information (S202) includes: determining at least the 64/66 Bit blocks between the service packets and a predetermined period of time. Part of the 64/66Bit blocks between the service packets are OAM blocks that carry OAM information.
  • the receiving end when the sending end sends OAM blocks according to a predetermined period, the receiving end can determine which of the blocks are OAM blocks according to whether the receiving timing of the received blocks located between the service packets meets the predetermined period.
  • the way the receiving end judges the predetermined period should correspond to the way the sending end sends the OAM block.
  • the block after the end of the service packet and before the start of the next service packet should be the OAM block.
  • the receiving end can determine the OAM block based on only one of the characteristic identifier and the predetermined period, or determine the OAM block based on both at the same time. For example, it is required that the receiving timing meets the predetermined period and carries the characteristic identifier at the same time.
  • the block is the OAM block.
  • the OAM block is discarded; and/or an alarm is reported.
  • the corresponding OAM block can be discarded, and an alarm can also be reported, while continuing to identify the OAM block in the subsequent predetermined period.
  • extracting an OAM block includes: extracting at least one OAM block, and replacing the extracted OAM block with a free block.
  • the receiver when the sender uses a replacement method to add an OAM block, correspondingly, the receiver can use "reverse replacement", that is, the OAM block is extracted and replaced with a free block.
  • reverse replacement that is, the OAM block is extracted and replaced with a free block.
  • OAM information is dedicated to the physical coding sublayer (PCS) and cannot be recognized by other layers.
  • extracting an OAM block (S203) includes: extracting at least one OAM block.
  • the sending end joins the OAM block in an inserting manner
  • the receiving end needs to extract (equivalent to deleting it from the service stream) the OAM block.
  • the receiving end may also need to insert some new free blocks into the service stream after extracting the inserted OAM blocks, and the specific insertion positions, quantities, methods, etc. are no longer Qualify.
  • PCS physical coding sublayer
  • the device involving the Ethernet technology at the sending end generates OAM information of the customer service.
  • a device involving Ethernet technology at the sending end adds an OAM block carrying OAM information between service packets in a predetermined period (fixed periodicity or variable period), and can add a feature identifier to at least part of the OAM block.
  • the device at the receiving end involving Ethernet technology recognizes the OAM block according to the feature identifier of the pre-appointed OAM information, the expected position of the predetermined period, etc., and extracts the OAM block to obtain the OAM information from the service flow, and give the customer service channel The test results.
  • Example 1 OAM information is carried by a 64/66Bit block (OAM block), such as a control block with a block type field of 0x4B.
  • OAM block is sent at the sending end according to a fixed cycle, for example, at a frequency of sending once every 16K blocks.
  • the method of replacing the OAM block can be adopted when sending, or the method of directly inserting the OAM block can be adopted.
  • the receiving end recognizes the OAM block by the position and/or characteristic value of a fixed period. Among them, if the OAM block received by the receiving end is wrong, it will be discarded; otherwise, the OAM information in the OAM block will be extracted, and the detection result of the customer service channel will be given.
  • the sender uses the method of replacing the OAM block to send, after extracting the OAM block, the receiver needs to add a free block in the corresponding position, and then send the service stream to the codec module of the physical coding sublayer (PCS).
  • PCS physical coding sublayer
  • Example 2 The OAM information is carried by two 64/66Bit blocks (OAM blocks), specifically one control block plus one data block.
  • the sending end sends the two OAM blocks according to a fixed period, such as sending two OAM blocks every 32K blocks. When sending, it can be added by replacing the OAM block, or by directly inserting the OAM block.
  • the receiving end recognizes the OAM block by the position and/or characteristic value of a fixed period. Among them, if the OAM block received by the receiving end is wrong, it will be discarded; otherwise, the OAM information in the OAM block will be extracted, and the detection result of the customer service channel will be given.
  • Example 3 The OAM information is carried by two 64/66Bit blocks (OAM blocks), specifically one control block plus one data block.
  • the sending end sends the two OAM blocks separately according to a fixed period, for example, one OAM block is sent every 16K blocks. When sending, it can be added by replacing the OAM block, or by directly inserting the OAM block.
  • the receiving end can identify the OAM block by the position and/or characteristic value of a fixed period. Therefore, every time the receiving end receives 32K blocks, a total of two OAM blocks (one control block plus one data block) will be received, and then OAM information can be processed. Among them, if the OAM block received by the receiving end is wrong, it will be discarded; otherwise, the OAM information in the OAM block will be extracted, and the detection result of the customer service channel will be given.
  • Example 4 OAM information is carried by three 64/66Bit blocks (OAM blocks), specifically two control blocks plus one data block.
  • the sending end sends the three OAM blocks according to a fixed cycle, for example, sending three OAM blocks every 48K blocks. When sending, it can be added by replacing the OAM block, or by directly inserting the OAM block.
  • the receiving end can identify the OAM block by the position and/or characteristic value of a fixed period. Among them, if the OAM block received by the receiving end is wrong, it will be discarded; otherwise, the OAM information in the OAM block will be extracted, and the detection result of the customer service channel will be given.
  • OAM information is carried by three 64/66Bit blocks (OAM blocks), specifically two control blocks plus one data block.
  • the sending end sends the three OAM blocks according to a variable cycle. For example, the first and second OAM blocks are sent together every 32K blocks, and the third OAM block is sent every 48K blocks.
  • OAM blocks can be used to replace free blocks to add OAM information or directly inserted between customer service packets to send. Therefore, every time the receiving end receives 48K blocks, a total of three OAM blocks (two control blocks plus one data block) will be received, and then OAM information can be processed. Among them, if the OAM block received by the receiving end is wrong, it will be discarded; otherwise, the OAM information in the OAM block will be extracted, and the detection result of the customer service channel will be given.
  • the embodiments of the present disclosure provide an Ethernet device.
  • the Ethernet device in the embodiment of the present disclosure is configured to implement any one of the above methods for sending information.
  • the Ethernet device in the embodiment of the present disclosure is a device involving Ethernet technology, that is, any device that can be connected to an Ethernet or other network and has the ability to send, receive, and process information in the network, such as a personal computer , Smart phones, tablet computers, servers, routers, gateways, optical transmission equipment, etc.
  • the Ethernet device of the embodiment of the present disclosure can realize the above method of sending information, so it can realize the physical coding sublayer (PCS).
  • PCS physical coding sublayer
  • the Ethernet device of the embodiment of the present disclosure may also implement other layers such as a coordination sublayer and a physical medium additional layer.
  • the Ethernet device of the embodiment of the present disclosure includes:
  • the sending module is configured to send multiple 64/66Bit block business packets in the Ethernet physical encoding sublayer, and send 64/66Bit blocks carrying OAM information between at least some of the business packets; 64/66Bit blocks carrying OAM information It is an OAM block.
  • an embodiment of the present disclosure provides an Ethernet device.
  • the Ethernet device in the embodiment of the present disclosure is configured to implement any one of the above information processing methods.
  • the Ethernet device in the embodiment of the present disclosure is a device involving Ethernet technology, that is, any device that can be connected to an Ethernet or other network and has the ability to send, receive, and process information in the network, such as a personal computer , Smart phones, tablet computers, servers, routers, gateways, optical transmission equipment, etc.
  • the Ethernet device of the embodiment of the present disclosure can implement the above method for processing information, so it can implement the physical coding sublayer (PCS).
  • PCS physical coding sublayer
  • the Ethernet device of the embodiment of the present disclosure may also implement other layers such as a coordination sublayer and a physical medium additional layer.
  • the Ethernet device of the embodiment of the present disclosure includes:
  • a receiving module configured to receive a plurality of 64/66Bit block business packets and a 64/66Bit block located between at least some of the business packets in the Ethernet physical encoding sublayer;
  • At least one processor is configured to determine that at least part of the 64/66 Bit blocks located between the service packets are OAM blocks that carry OAM information; extract the OAM blocks to obtain OAM information.
  • Ethernet device can have both a receiving module and a sending module, that is, the Ethernet device can achieve the above two functions. .
  • an embodiment of the present disclosure provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, any one of the foregoing methods for sending information is implemented.
  • an embodiment of the present disclosure provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, any one of the foregoing information processing methods is implemented.
  • the processor is a device with data processing capabilities, including but not limited to a central processing unit (CPU), etc.
  • the memory is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically such as SDRAM). , DDR, etc.), read-only memory (ROM), charged erasable programmable read-only memory (EEPROM), flash memory (FLASH);
  • the I/O interface read and write interface
  • the information exchange of the processor includes, but is not limited to, a data bus (Bus), etc.
  • the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may consist of several physical components. The components are executed cooperatively.
  • Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit (CPU), digital signal processor, or microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as Application specific integrated circuit.
  • a processor such as a central processing unit (CPU), digital signal processor, or microprocessor
  • Such software may be distributed on a computer-readable medium, and the computer-readable medium may include a computer storage medium (or a non-transitory medium) and a communication medium (or a 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). Sexual, removable and non-removable media.
  • Computer storage media include but are not limited to random access memory (RAM, more specifically DRAM, DDR, etc.), read only memory (ROM), charged erasable programmable read only memory (EEPROM), flash memory (FLASH) or other disk storage ; CD-ROM, digital versatile disk (DVD) or other optical disk storage; magnetic cassette, tape, magnetic disk storage or other magnetic storage; any other that can be used to store desired information and can be accessed by a computer medium.
  • a communication medium usually contains computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本公开实施例提供了一种发送信息的方法，该方法包括：发送多个64/66Bit块的业务包，并在至少部分业务包之间发送承载操作管理维护OAM信息的64/66Bit块；所述承载OAM信息的64/66Bit块为OAM块。本公开实施例还提供了一种处理信息的方法、以太网设备、计算机可读介质。

Description

发送和处理信息的方法、以太网设备、计算机可读介质 技术领域
本公开实施例涉及承载操作管理维护((Operation Administration and Maintenance，简称为OAM))信息技术领域，特别涉及一种发送和处理信息的方法、以太网设备、计算机可读介质。
背景技术
在以太网中，需要对客户业务通道进行操作管理维护(OAM)，例如需要检测客户业务通道的服务质量，如误码率、延迟时间、业务丢弃等情况。
但现有技术未对以太网中的物理编码子层(PCS)承载的各客户业务通道如何操作、管理、维护进行规定。
发明内容
本公开实施例提供一种发送和处理信息的方法、以太网设备、计算机可读介质。
第一方面，本公开实施例提供一种发送信息的方法，用于以太网物理编码子层，所述方法包括：发送多个64/66Bit块的业务包，并在至少部分业务包之间发送承载操作管理维护OAM信息的64/66Bit块；所述承载OAM信息的64/66Bit块为OAM块。
第二方面，本公开实施例提供一种处理信息的方法，用于以太网物理编码子层，所述方法包括：接收多个64/66Bit块的业务包以及位于至少部分业务包之间的64/66Bit块；确定至少部分位于业务包之间的64/66Bit块 为承载OAM信息的OAM块；提取所述OAM块，以获取所述OAM信息。
第三方面，本公开实施例提供一种以太网设备，其包括：发送模块，配置为在以太网物理编码子层中发送多个64/66Bit块的业务包，并在至少部分业务包之间发送承载OAM信息的64/66Bit块；所述承载OAM信息的64/66Bit块为OAM块。
第四方面，本公开实施例提供一种以太网设备，其包括：接收模块，配置为在以太网物理编码子层中接收多个64/66Bit块的业务包以及位于至少部分业务包之间的64/66Bit块；至少一个处理器，配置为确定至少部分位于业务包之间的64/66Bit块为承载OAM信息的OAM块；提取所述OAM块，以获取所述OAM信息。
第五方面，本公开实施例提供一种计算机可读介质，其上存储有计算机程序，所述程序被处理器执行时实现上述任意一种发送信息的方法。
第六方面，本公开实施例提供一种计算机可读介质，其上存储有计算机程序，所述程序被处理器执行时实现上述任意一种处理信息的方法。
本公开实施例中，将承载有OAM信息的OAM块在业务包之间发送，从而提供了发送OAM信息的方法，实现客户业务端到端通道的服务质量监控等功能；同时，以上OAM信息的传送又不会对正常的业务包的传输造成影响。
附图说明
附图用来提供对本公开实施例的进一步理解，并且构成说明书的一部分，与本公开实施例一起用于解释本公开，并不构成对本公开的限制。通过参考附图对详细示例实施例进行描述，以上和其它特征和优点对本领域技术人员将变得更加显而易见，在附图中：
图1为本公开实施例提供的一种发送信息的方法的流程图；
图2为本公开实施例提供的另一种发送信息的方法中部分步骤的流程 图；
图3为本公开实施例提供的一种处理信息的方法的流程图；
图4为本公开实施例提供的一种以太网设备的组成框图；
图5为本公开实施例提供的另一种以太网设备的组成框图；
图6为本公开实施例提供的一种计算机可读介质的组成框图；
图7为业务流的结构示意图；
图8为64/66B块的格式示意图；
图9为本公开实施例中一种OAM块(控制块)的结构示意图；
图10为本公开实施例中一种单独承载OAM信息的OAM块的结构示意图；
图11为本公开实施例中一种承载OAM信息的多个OAM块的结构示意图；
图12为本公开实施例中一种所有OAM块均携带特征标识的结构示意图；
图13为本公开实施例中一种部分OAM块携带特征标识的结构示意图；
图14为本公开实施例中加入OAM块的过程的示意图；
图15为本公开实施例中加入OAM块后业务流的结构示意图；
图16为本公开实施例中采用固定周期时期望位置的示意图；
图17为本公开实施例中采用可变周期时期望位置的示意图。
具体实施方式
为使本领域的技术人员更好地理解本公开实施例的技术方案，下面结合附图对本公开实施例提供的发送和处理信息的方法、以太网设备、计算机可读介质进行详细描述。
在下文中将参考附图更充分地描述本公开实施例，但是所示的实施例可以以不同形式来体现，且不应当被解释为限于本公开阐述的实施例。反之，提供这些实施例的目的在于使本公开透彻和完整，并将使本领域技术人员充分理解本公开的范围。
本公开实施例可借助本公开的理想示意图而参考平面图和/或截面图进行描述。因此，可根据制造技术和/或容限来修改示例图示。
在不冲突的情况下，本公开各实施例及实施例中的各特征可相互组合。
本公开所使用的术语仅用于描述特定实施例，且不意欲限制本公开。如本公开所使用的术语“和/或”包括一个或多个相关列举条目的任何和所有组合。如本公开所使用的单数形式“一个”和“该”也意欲包括复数形式，除非上下文另外清楚指出。如本公开所使用的术语“包括”、“由……制成”，指定存在所述特征、整体、步骤、操作、元件和/或组件，但不排除存在或添加一个或多个其它特征、整体、步骤、操作、元件、组件和/或其群组。
除非另外限定，否则本公开所用的所有术语(包括技术和科学术语)的含义与本领域普通技术人员通常理解的含义相同。还将理解，诸如那些在常用字典中限定的那些术语应当被解释为具有与其在相关技术以及本公开的背景下的含义一致的含义，且将不解释为具有理想化或过度形式上的含义，除非本公开明确如此限定。
第一方面，本公开实施例提供一种发送信息的方法，用于以太网物理编码子层。
物理编码子层(PCS，Physical Coding Sublayer)是以太网的物理层中的一层，而物理层由物理接口收发器(PHY)用于实现。具体的，物理编码子层(PCS)上与协调子层(RS，Reconciliation Sublaye)连接，而下与物理介质接入(PMA，Physical Media Attachment)层连接，用于实现数据的编码、解码。
本公开实施例用于在物理编码子层中发送信息，尤其用于发送操作管理维护(OAM，Operation-Administration-Maintenance)信息。
其中，OAM信息是指用于实现以太网中客户业务通道的操作、管理、维护过程的所有信息。
参照图1，本公开实施例的方法包括：
S101、发送多个64/66Bit块的业务包，并在至少部分业务包之间发送承载OAM信息的64/66Bit块；承载OAM信息的64/66Bit块为OAM块。
参照图7，在物理编码子层发送的业务流中包括多个对应客户业务的业务包(客户业务包)。每个业务包由多个64/66Bit块构成(即为64/66Bit块的业务包)，多个64/66Bit块通常包括表示业务包开始的开始块(控制块的一种，图7中用S表示)，表示业务包结束的结束块(控制块的一种，图7中用T表示)，以及在开始块和结束块间的数据块(图7中用D表示)。另外，不同业务包间还可有空闲块(图7中用I表示)。
其中，64/66Bit块也称64B/66B块，是指将64Bit(比特)的数据或控制信息编码得到的66Bit的用于进行传输的块(Block)。
例如，相关技术中定义的一种64/66Bit块结构可参照图8，其中前两位表示同步头(sync)，其为01时表示数据块，为10时表示控制块。对控制块，随后的8位表示块类型域(Block Type Field)，如0x1E、0x78、Ox4B、0x87、0x99等，不同的块类型域值表示不同的控制块。
本公开实施例中，在不同的业务包之间，加入了承载有OAM信息的64/66Bit块，其具体称为OAM块(图中用O表示)，即在不同业务包之间发送了OAM信息。
例如，OAM块的具体形式可参照图9，其中以块类型域为0x4B的控制块作为OAM块的一种例子。
其中，OAM块位于业务包之间是指，对任意一个OAM块，其之前的第一个属于业务包的块必然是结束块；而其之后的第一个属于业务包的块必然是开始块；或者说，OAM块不能位于业务包的“内部”。
当然，OAM块位于业务包之间的具体方式是多样的。
其中，OAM块通常仅位于部分业务包之间，即部分相邻的业务包之间有OAM块，但也有部分相邻的业务包之间没有OAM块。
其中，当两个相邻业务包之间有OAM块时，可仅有一个OAM块，也可有多个OAM块。
其中，当两个相邻业务包之间有OAM块时，可只有OAM块而无其它的块(如空闲块)，也可同时有OAM块和其它的块(如空闲块)。
本公开实施例中，将承载有OAM信息的OAM块在业务包之间发送，从而提供了发送OAM信息的方法，实现客户业务端到端通道的服务质量监控等功能；同时，以上OAM信息的传送又不会对正常的业务包的传输造成影响。
在一些实施例中，OAM信息包括以下至少一项OAM消息：连通性检测(CC)、比特间插奇偶校验(BIP)、远端误码指示(REI)、远端缺陷指示(RDI)、保护倒换协议(APS)、时延测量(DM，Delay Measurement)、连通性验证(CV，Connectivity Verification)、客户信号类型。
示例性的，OAM信息的具体内容可包括以上各内容中的一项或多项，其中每一项称为一项“OAM消息”。
当然，以上所列举的具体OAM消息只是示例性的，而不是对OAM消息范围的限定，根据需要，也可增加其它的OAM消息。
在一些实施例中，OAM信息由一个OAM块承载。
作为本公开实施例的一种方式，每条OAM信息可完全由一个OAM块承载，即每个OAM块就是一个OAM信息。
例如，OAM块可为是指定的单个控制块或数据块(当然不论具体是什么块均必须位于业务包之间)。OAM信息的具体内容(OAM消息)可 由控制块中块类型域后的各比特承载，或由数据块的同步头后的各比特承载。
例如，图10为单个OAM块承载OAM信息一种示例，其中采用块类型域为0x4B的控制块，承载了比特间插奇偶校验(BIP)、远端误码指示(REI)、远端缺陷指示(RDI)等OAM消息。
在一些实施例中，OAM信息由多个OAM块承载。
作为本公开实施例的另一种方式，每条OAM信息也可由多个OAM块分别承载，即每各OAM块分别承载OAM信息的一部分内容。
例如，承载OAM信息的多个OAM块可以是多种控制块，也可以是多个数据块，也可以是一个控制块加上一个或多个数据块的组合，或是多个控制块加多个数据块的组合等。
例如，图11为多个OAM块承载OAM信息一种示例，其中采用5个数据块(OAM块1、OAM块2、OAM块3、OAM块4、OAM块5)承载了连通性验证(CV)消息，CV消息由源点标识信息SAPI和宿点标识信息DAPI组成，SAPI和DAPI均是16字节长的字符。
应当理解，当OAM信息由多个OAM块承载时，其中每个OAM块都必须位于业务包之间，但不代表承载一条OAM信息的多个OAM块必须在都在两个特定业务包之间，而是承载一条OAM信息的多个OAM块可分别分布在不同的多个业务包之间。
在一些实施例中，至少部分OAM块携带特征标识；特征标识用于标识OAM信息。
OAM块必然位于业务包之间，但业务包之间的块不一定都是OAM块(比如还可有空闲块)，故需要通过一些方式让接收端能确认业务包之间的哪些块是OAM块，并进行后续处理。
作为本公开实施例的一种方式，可以是在至少部分OAM块中增设置 特征标识，特征标识能表明OAM块的身份，即可以表明哪些块(至少包括自身)是承载OAM信息的OAM块，从而接收端可通过分析收到的块中的特征标识(如是否有特征标识，以及特征标识的含义)，确定出OAM块。
在一些实施例中，特征标识包括以下至少一者：
特征值；
校验值。
特征标识可包括特定的数据，即为特征值，或称“特征图案”。
或者，特征标识也可包括根据其它的数据计算得到的校验值，即通过分析校验值与其它数据的关系，可确定块的类型(是否为OAM块)，并可在数据有错误时发现错误，甚至进行纠错。
例如，以上校验值可为CRC校验值(图中以CRC表示)，也可为BIP、FEC等其它类型的校验值。
当然，参照图11至图13等，特征标识也可同时包括以上特征值和校验值。
例如，图9为一种带有校验值的OAM块的示例，其是块类型域为0x4B的控制块，并携带了CRC(或BIP、FEC)校验值，从而可通过“0x4B”和/或“校验值”对其进行识别。而且，当采用FEC校验值时，接收端还可在某些错误情况下，对OAM块的错误进行纠错。
在一些实施例中，当OAM信息仅由一个OAM块承载时，该OAM块中可直接携带以上特征标识。
在一些实施例中，OAM信息由多个OAM块承载，且所有OAM块均携带特征标识。
作为本公开实施例的一种方式，当OAM信息由多个OAM块承载时，则必然有多个OAM块，从而这些OAM块可共同携带携带特征标识，即 其中每个OAM块均携带有特征标识。
其中，所有OAM块共同携带携带特征标识的具体方式是多样的。
例如，可以是所有的OAM块都携带相同的特征标识(如有相同的特征图案)，也可以是每个OAM块携带各自的特征标识(如携带各自的校验值)，也可以是每个OAM块携带特征标识的一部分，即所有OAM块携带的特征标识的总和为完整的特征标识。
例如，图12示出了所有OAM块均携带特征标识的一种情况，其中OAM块1、OAM块2、OAM块3中分别携带特征值1、特征值2、特征值3。
在一些实施例中，OAM信息由多个OAM块承载，且部分OAM块携带特征标识，部分OAM块仅携带OAM消息。
作为本公开实施例的另一种方式，当一条OAM信息由多个OAM块承载时，也可以是只有部分(至少一个)OAM块携带有特征标识，而其它的OAM块仅携带OAM信息的内容，如仅携带OAM消息。
例如，可参照图11，其中OAM块1携带了特征值，OAM块2、OAM块3、OAM块4、OAM块5未携带特征值，仅携带OAM消息(OAM信息的内容)。或者，也可参照图13，OAM块1和OAM块2分别携带特征值1和特征值2，OAM块3不携带特征值，仅携带OAM消息(OAM信息的内容)。
其中，当仅有部分OAM块携带特征标识时，则这些OAM块携带的特征标识需要能表明其它OAM块的身份。
例如，可以是承载OAM信息的第一个OAM块携带特征标识，并表明其后的哪些块是承载该OAM信息的OAM块；或者，也可以是承载OAM信息的第一个和最后一个OAM块携带特征标识，表明两个有特征标识的OAM块之间的块是承载同一OAM信息的OAM块。
在一些实施例中，在至少部分业务包之间发送承载有OAM信息的64/66Bit块(S101)包括：
S1011、根据预定周期在业务包之间发送承载有OAM信息的OAM块。
如前，为让接收端识别OAM块，作为本公开实施例的另一种方式，也可以是每隔一个预定周期发送一次OAM块；这样，接收端可根据块是否是在预定周期收到的，确定其是否为OAM块。
其中，预定周期可用具体时间(如多少秒)限定，但更优选用块的数量限定。例如，预定周期可为16K(1K＝1024)个块，即每发送16*1024个块达到一次预定周期，更具体的，从上一个周期加入的第一个OAM块开始计算，第16K+1个块的位置即为下一个预定周期的开始，故理论上应在该位置发送OAM块。
当然，应当理解，以上根据预定周期发送OAM块的方式，和在OAM块中加入特征标识的方式，可以仅采用一种，也可以是同时采用的，即可以既按照一定周期发送OAM块，且同时有至少部分OAM块中携带有特征标识。
在一些实施例中，预定周期为固定周期。
作为本公开实施例的一种方式，预定周期可以是一个不变的固定周期。
例如，参照图16，预定周期可固定为16K个块，进而确定对应各预定周期的块(图中斜线块表示)。
在一些实施例中，预定周期为根据预定算法或预定策略确定的可变周期。
作为本公开实施例的另一种方式，预定周期也可以是可变的，即每次预定周期的具体长度，是根据预定的算法或预定策略确定的，从而不同次的预定周期的具体长度可不同。
其中，预定算法是指，每次周期中，按照预定的方式计算相应预定周期的具体长度。
而预定策略是指，根据每次周期的情况，按照相应的策略(或者说方式)确定预定周期的具体长度。例如，可按照预定的策略，为不同的OAM消息类型设定不同的预定周期，如某些类型的OAM消息的预定周期是16K个块，某些类型的OAM消息的预定周期是32K个块等。
例如，参照图17，第一次的预定周期可为16K个块，第二次的预定周期则为32K个块等，进而确定对应各预定周期的块(图中斜线块表示)。
在一些实施例中，参照图2，根据预定周期在业务包之间发送承载有OAM信息的OAM块(S1011)包括：
S10111、根据预定周期确定标称位置。
S10112、若标称位置位于业务包之间，则在标称位置发送OAM块；若标称位置位于业务包中，则在该业务包与下一业务包之间发送OAM块。
当根据预定周期发送OAM块时，根据每个预定周期都可确定一个理论上开始加入OAM块的位置，即“标称位置”，或者说是严格对应周期的位置(图16、图17中斜线块的位置)。但由于业务包长度的不确定性，故以上标称位置可能是正好在业务包之间，也可能位于业务包内部，但本公开实施例又要求OAM块不能在业务包中发送，因此：
(1)当标称位置正好在业务包之间时，则可用标称位置为加入位置，直接加入OAM块。
(2)若标称位置位于一个业务包的内部，则需以该业务包结束后、下一个业务包开始前的位置为加入位置，加入OAM块。
例如，若图16、图17中的标称位置对应数据块(图7、图14、图15中用D表示)或开始块(图7、图14、图15中用S表示)，则需要向后寻找到第一个结束块(图7、图14、图15中用T表示)，再找到该结束块后的第一个开始块，并在该第一个结束块之后及第一个开始块之间加入OAM块；而若标称位置是结束块，则要向后寻找到第一个开始块，并在该结束块后及第一个开始块间加入OAM块。
在一些实施例中，根据预定周期在业务包之间发送承载有OAM信息的OAM块(S1011)包括在每个预定周期中发送一个OAM块。
作为本公开实施例的一种方式，在以上每个预定周期中，可仅加入一个OAM块。
在一些实施例中，根据预定周期在业务包之间发送承载有OAM信息的OAM块(S1011)包括在每个预定周期中发送多个OAM块。
也就是说，作为本公开实施例的另一种方式，也可以在以上每个预定周期中加入更多的OAM块，即在每个预定周期发送多个OAM块。
当然，同一个预定周期中加入的多个OAM块，可承载同一条OAM信息，也可承载不同的OAM信息。
也就是说，以上预定周期仅决定发送OAM块的时机，而不限定发送的OAM块的数量、内容(如是否有特征标识)等。
当然，除根据预定周期发送外，发送OAM块的时机也可通过其它的方式确定，例如，可以是在有发送OAM信息的需求(如有故障触发OAM信息产生，或接收到用户的命令)时，即发送OAM块(如在本业务包与下一业务包之间发送)。
在一些实施例中，在至少部分业务包之间发送承载有OAM信息的64/66Bit块(S101)包括：将业务包之间的至少一个空闲块替换为OAM块并发送。
本公开实施例中，OAM块是在业务包之间发送的，而业务包之间可能存在不承载任何信息的块，即存在“空闲块”。因此，参照图14、图15，作为本公开实施例的一种方式，当确定要加入OAM块的两个相邻业务包之间具有空闲块时，则可直接将空闲块替换为OAM块(图中用O1表示)，即删除空闲块并在相同位置加入OAM块。
当然，两个相邻的业务包之间的空闲块可能有多个，当要进行OAM 块替换时，可以是将多个空闲块都替换为OAM块，也可仅将其中的一部分空闲块都替换为OAM块。
在一些实施例中，在至少部分业务包之间发送承载有OAM信息的64/66Bit块(S101)包括：在业务包之间插入至少一个OAM块。
参照图14、图15，作为本公开实施例的另一种方式，确定要加入OAM块的两个相邻业务包之间，可能没有空闲块，或者是没有足够的空闲块，则此时可将OAM块(图中用O2表示)直接插入到两个相邻业务包之间，或者说是在两个相邻业务包之间“新增”OAM块；而原业务流中后续的各64/66Bit块，则在插入的OAM块后，继续发送。
其中，在插入新的OAM块后，可能还要在业务流中删除一些其它的空闲块，但其具体的删除位置、数量、方式等都是多样的，本公开实施例不对其进行具体限制。
当然，以上插入OAM块和替换OAM块的方式可仅采用一种，也可混合使用。例如，可以是不论是否有空闲块，均采用插入方式加入OAM块；或者，也可以是仅采用替换方式加入OAM块(若业务包之间无空闲块，则等待空闲块的出现)；或者，也可以是在有空闲块时优先采用替换方式加入OAM块，而无空闲块或空闲块不足时，再采用插入方式加入OAM块。
在一些实施例中，每个OAM块的预定位置承载预定的OAM消息。
OAM块需要承载OAM信息，而各OAM块承载OAM信息的具体方式是多样的。
作为本公开实施例的一种方式，可以采用Bit编码方式，即在OAM块中定义每个位置承载的OAM消息(OAM信息的特定内容)，从而OAM块的特定位置承载特定的OAM消息(若无相应OAM消息时，相应位置可为表示“空”的特定值)。
在一些实施例中，每个OAM块承载一个或多个预定分类的OAM消 息。
作为本公开实施例的另一种方式，也可采取消息编码方式，即将不同的OAM消息进行分类，而每个OAM块承载一个或多个分类的OAM消息，也可以是多个OAM块承载同一个OAM消息。
第二方面，本公开实施例提供一种处理信息的方法，用于以太网物理编码子层。
本公开实施例用于在以太网的物理编码子层(PCS)中处理信息，尤其用于处理接收到的操作管理维护(OAM)信息。
参照图3，本公开实施例的方法包括：
S201、接收多个64/66Bit块的业务包以及位于至少部分业务包之间的64/66Bit块。
S202、确定至少部分位于业务包之间的64/66Bit块为承载OAM信息的OAM块。
S203、提取OAM块，以获取OAM信息。
对应以上实施例的发送方式，接收端则会接收到多个业务包和位于业务包之间的块(可能为OAM块，也可能为空闲块等其它的块)，从而接收端需要分辨出业务包之间的块哪些是承载OAM信息的OAM块，并提取这些OAM块，以获取OAM信息。
在一些实施例中，确定至少部分位于业务包之间的64/66Bit块为承载OAM信息的OAM块(S202)包括：根据位于业务包之间的64/66Bit块中携带的特征标识，确定至少部分位于业务包之间的64/66Bit块为承载OAM信息的OAM块；特征标识用于标识OAM信息。
作为本公开实施例的一种方式，当发送端在OAM块中加入了以上特征标识时，则接收端可在位于业务包之间的块中查找特征标识，并根据找到的特征标识，确定其中哪些是OAM块。
在一些实施例中，确定至少部分位于业务包之间的64/66Bit块为承载OAM信息的OAM块(S202)包括：根据位于业务包之间的64/66Bit块与预定周期的关系，确定至少部分位于业务包之间的64/66Bit块为承载OAM信息的OAM块。
作为本公开实施例的另一种方式，当发送端根据预定周期发送OAM块时，则接收端可根据接收到的位于业务包间的块的接收时机是否符合预定周期，确定其中哪些是OAM块。
当然，接收端判断预定周期的方式应当是与发送端发送OAM块的方式对应的。例如，当预定周期的期望位置位于接收到的业务包内部时，则应当以该业务包结束后，而下一业务包开始前的块为OAM块。
当然，与发送端对应，接收端可以仅根据特征标识和预定周期中的一者确定OAM块，也可同时根据两者确定OAM块，例如要求必须接收时机符合预定周期，且同时携带有特征标识的块才是OAM块。
在一些实施例中，若任意一个预定周期内提取的OAM块承载的OAM信息错误，则：丢弃OAM块；和/或，上报告警。
当本预定周期内识别到错误的OAM信息时，则可将相应的OAM块丢弃处理，并且还可上报告警，同时继续在后续的预定周期进行OAM块的识别。
在一些实施例中，提取OAM块(S203)包括：提取至少一个OAM块，并将被提取的OAM块替换为空闲块。
作为本公开实施例的一种方式，当发送端采用替换方式加入OAM块时，相应的，接收端则可采用“相反的替换”，既将OAM块提取并替换为空闲块。之所以如此，是因为OAM信息是物理编码子层(PCS)专用的，其它层无法识别。
在一些实施例中，提取OAM块(S203)包括：提取至少一个OAM块。
作为本公开实施例的另一种方式，当发送端采用插入方式加入OAM块时，接收端需要提取(相当于从业务流中获取后删除)OAM块。
当然，与发送信息时删除空闲块相对应，接收端在提取插入的OAM块后，也可能需要再向业务流中插入一些新的空闲块，其具体的插入位置、数量、方式等也不再进行限定。
以下对本公开实施例中一种在以太网物理编码子层(PCS)实现客户业务通道的OAM功能的具体方法进行介绍，其可包括：
S301、发送端涉及以太网技术的设备生成客户业务的OAM信息。
S302、发送端涉及以太网技术的设备，以预定周期(固定周期性或可变周期)在业务包之间加入承载OAM信息的OAM块，并可在至少部分OAM块中加入特征标识。
S302、接收端涉及以太网技术的设备，根据预先约定的OAM信息的特征标识、预定周期的期望位置等识别出OAM块，并提取OAM块以从业务流中获取OAM信息，给出客户业务通道的检测结果。
其中，若在本预定周期内识别到错误的OAM信息，则进行丢弃处理和/或上报告警，并继续在后续的预定周期进行OAM识别。
下面对一些更具体的例子进行介绍。
例子1：OAM信息由一个64/66Bit块(OAM块)承载，如由块类型域为0x4B的控制块承载。在发送端按照固定周期发送OAM块，如按照每16K个块发送一次的频率进行发送。发送时可采用替换OAM块的方式，也可采用直接插入OAM块的方式。接收端通过固定周期的位置和/或特征值来识别OAM块。其中，接收端若接收到的OAM块错误，则丢弃，反之则提取出OAM块中的OAM信息，给出客户业务通道的检测结果。而 且，若发送端采用替换OAM块的方式发送，则接收端在提取OAM块后，还要在相应位置加入空闲块，之后将业务流发送到物理编码子层(PCS)的编解码模块。
例子2：OAM信息由两个64/66Bit块(OAM块)承载，具体为由一个控制块加一个数据块承载。发送端将该两个OAM块按照固定周期发送，如每32K个块发送两个OAM块。发送时可采用替换OAM块的方式加入，也可采用直接插入OAM块的方式。接收端通过固定周期的位置和/或特征值来识别OAM块。其中，接收端若接收到的OAM块错误，则丢弃，反之则提取出OAM块中的OAM信息，给出客户业务通道的检测结果。
例子3：OAM信息由两个64/66Bit块(OAM块)承载，具体为由一个控制块加一个数据块承载。发送端将该两个OAM块按照固定周期分别发送，如每16K个块发送一个OAM块。发送时可采用替换OAM块的方式加入，也可采用直接插入OAM块的方式。接收端可通过固定周期的位置和/或特征值来识别OAM块。从而接收端每接收到32K个块时，总共会收到两个OAM块(一个控制块加一个数据块)，之后可进行OAM信息的处理。其中，接收端若接收到的OAM块错误，则丢弃，反之则提取出OAM块中的OAM信息，给出客户业务通道的检测结果。
例子4：OAM信息由三个64/66Bit块(OAM块)承载，具体为由两个控制块加一个数据块承载。发送端将该三个OAM块按照固定周期发送，如每48K个块发送三个OAM块。发送时可采用替换OAM块的方式加入，也可采用直接插入OAM块的方式。接收端可通过固定周期的位置和/或特征值来识别OAM块。其中，接收端若接收到的OAM块错误，则丢弃，反之则提取出OAM块中的OAM信息，给出客户业务通道的检测结果。
例子5：OAM信息由三个64/66Bit块(OAM块)承载，具体为两个控制块加一个数据块承载。发送端将该三个OAM块按照可变周期发送，如第一、第二个OAM块每隔32K个块一起发送，第三个OAM块间隔48K个块发送。发送时可以采用OAM块替换空闲块的方式加入OAM信息或 者采用直接插入客户业务包之间方式发送。从而接收端每接收到48K个块时，总共会收到三个OAM块(两个控制块加一个数据块)，之后可进行OAM信息的处理。其中，接收端若接收到的OAM块错误，则丢弃，反之则提取出OAM块中的OAM信息，给出客户业务通道的检测结果。
第三方面，本公开实施例提供一种以太网设备。
本公开实施例的以太网设备设置为实现以上任意一种发送信息的方法。
其中，本公开实施例的以太网设备是涉及以太网技术的设备，也就是任何可以接入以太网或其它网络中，并具有在网络中进行信息发送、接收、处理能力的设备，例如个人电脑、智能手机、平板电脑、服务器、路由器、网关、光传送设备等。
本公开实施例的以太网设备可实现以上发送信息的方法，故可实现物理编码子层(PCS)。当然，应当理解，本公开实施例的以太网设备也可实现协调子层、物理介质附加层等其它的层。
参照图4，本公开实施例的以太网设备包括：
发送模块，配置为在以太网物理编码子层中发送多个64/66Bit块的业务包，并在至少部分业务包之间发送承载OAM信息的64/66Bit块；承载OAM信息的64/66Bit块为OAM块。
第四方面，本公开实施例提供一种以太网设备。
本公开实施例的以太网设备设置为实现以上任意一种处理信息的方法。
其中，本公开实施例的以太网设备是涉及以太网技术的设备，也就是任何可以接入以太网或其它网络中，并具有在网络中进行信息发送、接收、处理能力的设备，例如个人电脑、智能手机、平板电脑、服务器、路由器、 网关、光传送设备等。
本公开实施例的以太网设备可实现以上处理信息的方法，故可实现物理编码子层(PCS)。当然，应当理解，本公开实施例的以太网设备也可实现协调子层、物理介质附加层等其它的层。
参照图5，本公开实施例的以太网设备包括：
接收模块，配置为在以太网物理编码子层中接收多个64/66Bit块的业务包以及位于至少部分业务包之间的64/66Bit块；
至少一个处理器，配置为确定至少部分位于业务包之间的64/66Bit块为承载OAM信息的OAM块；提取OAM块，以获取OAM信息。
当然，应当理解，虽然以上限定的两种以太网设备分别具有接收模块和发送模块，但通常而言，以太网设备中可同时具有接收模块和发送模块，即以太网设备可实现以上两种功能。
第五方面，参照图6，本公开实施例提供一种计算机可读介质，其上存储有计算机程序，所述程序被处理器执行时实现上述任意一种发送信息的方法。
第六方面，参照图7，本公开实施例提供一种计算机可读介质，其上存储有计算机程序，所述程序被处理器执行时实现上述任意一种处理信息的方法。
其中，处理器为具有数据处理能力的器件，其包括但不限于中央处理器(CPU)等；存储器为具有数据存储能力的器件，其包括但不限于随机存取存储器(RAM，更具体如SDRAM、DDR等)、只读存储器(ROM)、带电可擦可编程只读存储器(EEPROM)、闪存(FLASH)；I/O接口(读写接口)连接在处理器与存储器间，能实现存储器与处理器的信息交互，其包括但不限于数据总线(Bus)等。
本领域普通技术人员可以理解，上文中所公开的全部或某些步骤、系 统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。
在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。
某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器(CPU)、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其它数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于随机存取存储器(RAM，更具体如DRAM、DDR等)、只读存储器(ROM)、带电可擦可编程只读存储器(EEPROM)、闪存(FLASH)或其它磁盘存储器；只读光盘(CD-ROM)、数字多功能盘(DVD)或其它光盘存储器；磁盒、磁带、磁盘存储或其它磁存储器；可以用于存储期望的信息并且可以被计算机访问的任何其它的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其它传输机制之类的调制数据信号中的其它数据，并且可包括任何信息递送介质。
本公开已经公开了示例实施例，并且虽然采用了具体术语，但它们仅用于并仅应当被解释为一般说明性含义，并且不用于限制的目的。在一些实例中，对本领域技术人员显而易见的是，除非另外明确指出，否则可单独使用与特定实施例相结合描述的特征、特性和/或元素，或可与其它实施例相结合描述的特征、特性和/或元件组合使用。因此，本领域技术人员将理解，在不脱离由所附的权利要求阐明的本公开的范围的情况下，可进行各种形式和细节上的改变。

Claims (21)

  1. 一种发送信息的方法，用于以太网物理编码子层，所述方法包括：
    发送多个64/66Bit块的业务包，并在至少部分业务包之间发送承载操作管理维护OAM信息的64/66Bit块；所述承载OAM信息的64/66Bit块为OAM块。
  2. 根据权利要求1所述的方法，其中，
    所述OAM信息由一个OAM块承载；
    或者，所述OAM信息由多个OAM块承载。
  3. 根据权利要求2所述的方法，其中，
    至少部分所述OAM块携带特征标识；所述特征标识用于标识OAM信息。
  4. 根据权利要求3所述的方法，其中，所述特征标识包括以下至少一者：
    特征值；
    校验值。
  5. 根据权利要求4所述的方法，其中，所述OAM信息由多个OAM块承载；
    所有所述OAM块均携带特征标识；
    或者，部分所述OAM块携带特征标识，部分OAM块仅携带OAM消息。
  6. 根据权利要求1所述的方法，其中，所述在至少部分业务包之间发送承载有OAM信息的64/66Bit块包括：
    根据预定周期在业务包之间发送承载有OAM信息的OAM块。
  7. 根据权利要求6所述的方法，其中，所述预定周期为：
    固定周期；
    或者，根据预定算法或预定策略确定的可变周期。
  8. 根据权利要求6所述的方法，其中，所述根据预定周期在业务包之间发送承载有OAM信息的OAM块包括：
    根据所述预定周期确定标称位置；
    若标称位置位于业务包之间，则在标称位置发送OAM块；若标称位置位于业务包中，则在该业务包与下一业务包之间发送OAM块。
  9. 根据权利要求6所述的方法，其中，所述根据预定周期在业务包之间发送承载有OAM信息的OAM块包括：
    在每个预定周期中发送一个OAM块；
    或者，在每个预定周期中发送多个OAM块。
  10. 根据权利要求1所述的方法，其中，所述在至少部分业务包之间发送承载有OAM信息的64/66Bit块包括：
    将业务包之间的至少一个空闲块替换为OAM块并发送；
    或者，在业务包之间插入至少一个OAM块。
  11. 根据权利要求1所述的方法，其中，所述OAM信息包括以下至少一项OAM消息：
    连通性检测、比特间插奇偶校验、远端误码指示、远端缺陷指示、保护倒换协议、时延测量、连通性验证、客户信号类型。
  12. 根据权利要求1所述的方法，其中，
    每个所述OAM块的预定位置承载预定的OAM消息；
    或者，每个所述OAM块承载一个或多个预定分类的OAM消息。
  13. 一种处理信息的方法，用于以太网物理编码子层，所述方法包括：
    接收多个64/66Bit块的业务包以及位于至少部分业务包之间的64/66Bit块；
    确定至少部分位于业务包之间的64/66Bit块为承载OAM信息的OAM块；
    提取所述OAM块，以获取所述OAM信息。
  14. 根据权利要求13所述的方法，其中，所述确定至少部分位于业务包之间的64/66Bit块为承载OAM信息的OAM块包括：
    根据位于业务包之间的64/66Bit块中携带的特征标识，确定至少部分位于业务包之间的64/66Bit块为承载OAM信息的OAM块；所述特征标识用于标识OAM信息。
  15. 根据权利要求13所述的方法，其中，所述确定至少部分位于业务包之间的64/66Bit块为承载OAM信息的OAM块包括：
    根据位于业务包之间的64/66Bit块与预定周期的关系，确定至少部分位于业务包之间的64/66Bit块为承载OAM信息的OAM块。
  16. 根据权利要求15所述的方法，其中，若任意一个预定周期内提取的OAM块承载的OAM信息错误，则：
    丢弃所述OAM块；
    和/或，上报告警。
  17. 根据权利要求13所述的方法，其中，所述提取所述OAM块包括：
    提取至少一个OAM块，并将被提取的OAM块替换为空闲块；
    或者，提取至少一个OAM块。
  18. 一种以太网设备，其包括：
    发送模块，配置为在以太网物理编码子层中发送多个64/66Bit块的业务包，并在至少部分业务包之间发送承载OAM信息的64/66Bit块；所述承载OAM信息的64/66Bit块为OAM块。
  19. 一种以太网设备，其包括：
    接收模块，配置为在以太网物理编码子层中接收多个64/66Bit块的业务包以及位于至少部分业务包之间的64/66Bit块；
    至少一个处理器，配置为确定至少部分位于业务包之间的64/66Bit块为承载OAM信息的OAM块；提取所述OAM块，以获取所述OAM信息。
  20. 一种计算机可读介质，其上存储有计算机程序，所述程序被处理器执行时实现根据权利要求1至12中任意一项所述的发送信息的方法。
  21. 一种计算机可读介质，其上存储有计算机程序，所述程序被处理器执行时实现根据权利要求13至17中任意一项所述的处理信息的方法。
PCT/CN2020/139944 2020-04-04 2020-12-28 发送和处理信息的方法、以太网设备、计算机可读介质 WO2021196774A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010261670.4A CN112511328A (zh) 2020-04-04 2020-04-04 发送和处理信息的方法、以太网设备、计算机可读介质
CN202010261670.4 2020-04-04

Publications (1)

Publication Number Publication Date
WO2021196774A1 true WO2021196774A1 (zh) 2021-10-07

Family

ID=74953237

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/139944 WO2021196774A1 (zh) 2020-04-04 2020-12-28 发送和处理信息的方法、以太网设备、计算机可读介质

Country Status (2)

Country Link
CN (1) CN112511328A (zh)
WO (1) WO2021196774A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116346654A (zh) * 2021-12-24 2023-06-27 中国电信股份有限公司 网络遥测方法、装置、系统、电子设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106612220A (zh) * 2015-10-27 2017-05-03 中兴通讯股份有限公司 灵活以太网的通道管理方法和装置
CN108123813A (zh) * 2016-11-28 2018-06-05 华为技术有限公司 操作、管理和维护oam数据的传输方法和装置
WO2019119389A1 (en) * 2017-12-22 2019-06-27 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatus for configuring a flex ethernet node
CN110768742A (zh) * 2018-07-27 2020-02-07 中兴通讯股份有限公司 Oam消息的传输方法、发送设备、接收设备及可读存储介质
CN110830143A (zh) * 2018-08-13 2020-02-21 中兴通讯股份有限公司 一种业务传输方法及装置、光传送网设备、存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106612220A (zh) * 2015-10-27 2017-05-03 中兴通讯股份有限公司 灵活以太网的通道管理方法和装置
CN108123813A (zh) * 2016-11-28 2018-06-05 华为技术有限公司 操作、管理和维护oam数据的传输方法和装置
WO2019119389A1 (en) * 2017-12-22 2019-06-27 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatus for configuring a flex ethernet node
CN110768742A (zh) * 2018-07-27 2020-02-07 中兴通讯股份有限公司 Oam消息的传输方法、发送设备、接收设备及可读存储介质
CN110830143A (zh) * 2018-08-13 2020-02-21 中兴通讯股份有限公司 一种业务传输方法及装置、光传送网设备、存储介质

Also Published As

Publication number Publication date
CN112511328A (zh) 2021-03-16

Similar Documents

Publication Publication Date Title
CN112134651B (zh) Oam消息传输方法、传输设备及存储介质
US11539607B2 (en) Detection block sending and receiving method, and network device and system
EP3065329B1 (en) Aggregated data frame structures
WO2021115452A1 (zh) 灵活以太网开销复帧接收方法、装置、设备及介质
US20230155715A1 (en) Rate adaptation method and apparatus
WO2021244660A1 (zh) 64b/66b码流发送方法、64b/66b码流接收方法及设备
US11082348B2 (en) Network device and queue management method for network device
US20230119339A1 (en) Block group loss determining method and apparatus
EP3541088B1 (en) Method, device and system for bearing a frame sequence number in a multichannel passive optical network
WO2021196774A1 (zh) 发送和处理信息的方法、以太网设备、计算机可读介质
US20220200722A1 (en) Slot negotiation method and device
WO2019015462A1 (zh) 一种检测块发送和接收的方法、网络设备和系统
US20090210770A1 (en) Method, system and computer program product for end to end error checking in ethernet
CN113162855B (zh) 组播报文检测方法、网络设备和系统
WO2023051050A1 (zh) 网络监测方法、装置及计算机存储介质
US9008077B2 (en) Method for quick map recovery in case of error in MoCA
WO2020253791A1 (zh) 一种故障传输方法和装置
JP5698107B2 (ja) ネットワーク評価方法、および、ネットワーク評価システム
JP5158689B2 (ja) 系切替装置および方法
WO2021047483A1 (zh) 一种保护倒换的方法、节点设备和存储介质
CN117728920A (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: 20929218

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 03/03/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 20929218

Country of ref document: EP

Kind code of ref document: A1