WO2017201953A1 - Procédé et dispositif de traitement de service client - Google Patents

Procédé et dispositif de traitement de service client Download PDF

Info

Publication number
WO2017201953A1
WO2017201953A1 PCT/CN2016/102740 CN2016102740W WO2017201953A1 WO 2017201953 A1 WO2017201953 A1 WO 2017201953A1 CN 2016102740 W CN2016102740 W CN 2016102740W WO 2017201953 A1 WO2017201953 A1 WO 2017201953A1
Authority
WO
WIPO (PCT)
Prior art keywords
code block
forwarding label
forwarding
label
service
Prior art date
Application number
PCT/CN2016/102740
Other languages
English (en)
Chinese (zh)
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 WO2017201953A1 publication Critical patent/WO2017201953A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B10/00—Transmission systems employing electromagnetic waves other than radio-waves, e.g. infrared, visible or ultraviolet light, or employing corpuscular radiation, e.g. quantum communication
    • H04B10/27—Arrangements for networking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H04J3/1605—Fixed allocated frame structures
    • H04J3/1652—Optical Transport Network [OTN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H04J3/1694—Allocation of channels in TDM/TDMA networks, e.g. distributed multiplexers
    • 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]
    • 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/44—Star or tree networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H04L45/502—Frame based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H04L45/507—Label distribution
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/54—Organization of routing tables
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/04—Selecting arrangements for multiplex systems for time-division multiplexing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/04—Selecting arrangements for multiplex systems for time-division multiplexing
    • H04Q11/0428—Integrated services digital network, i.e. systems for transmission of different types of digitised signals, e.g. speech, data, telecentral, television signals
    • H04Q11/0435—Details
    • H04Q11/0442—Exchange access circuits

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and device for processing a client service.
  • the Optical Internetworking Forum is discussing the expansion of traditional Ethernet technologies to support sub-rate, channelization, and reverse multiplexing applications for Ethernet services, and to expand Ethernet technology.
  • Flexible Ethernet FlexE
  • the application scenario of the sub-rate for the Ethernet service can support the transmission of the 250G Ethernet service by using three existing 100GE Physical Medium Dependent (PMD).
  • the application scenario of the reverse multiplexing of the Ethernet service can support the transmission of the 200G Ethernet service by using two existing 100GE PMDs.
  • a channelized application scenario for Ethernet services can support multiplexing multiple low-rate Ethernet services into high-speed flexible Ethernet.
  • a large number of Ethernet networks are used as the service bearer network in the access network and the metropolitan area network.
  • the FlexE technology supports the application scenarios of the sub-rate, channelization, and reverse multiplexing of the Ethernet service, which enhances the application flexibility of the Ethernet interface. .
  • FlexE technology only supports point-to-point applications as interface technology, but it has attracted the attention of the industry as a potential network transmission technology.
  • the development of FlexE into network transport technology will inevitably require the exchange of FlexE node devices.
  • the flexible Ethernet adopts a Cell (cell) unified switching scheme, that is, a unified switching is performed by using a Cell switching network for different types of services.
  • a Cell Cell
  • TDM Time Division Multiplexing
  • it is adapted to the Cell switching network, and the switching is completed according to the slot configuration information of the FlexE service layer slot (Calendar).
  • the Ethernet data service it is restored to the Ethernet frame, and then adapted to the Cell switching network, and the exchange is completed based on the Media Access Control (MAC) address.
  • MAC Media Access Control
  • L1 layer and L2 layer processing which is equivalent to designing two switching planes on the node device, which increases the design complexity, power consumption and cost of the device.
  • the embodiments of the present invention provide a method and a device for processing a customer service, which can solve the problem of design complexity, power consumption, and cost of service switching on a node device.
  • an embodiment of the present invention provides a method for processing a client service, including: receiving a client service, and mapping the client service to M time slots according to a first forwarding label carried in the client service, where The first forwarding label indicates a first forwarding destination address; the client service is sent to the target physical channel by using the M time slots, and the target physical channel has a corresponding relationship with the first forwarding destination address; M is a positive integer greater than or equal to 1.
  • the customer service may include a data service and a TDM service, and the customer service is mapped into the M time slots through the first forwarding label carried in the customer service, and the customer service is sent to the target physical channel through the M time slots, thereby realizing Multiple services are exchanged in the same switching plane of flexible Ethernet.
  • the mapping by the first forwarding label carried in the customer service, the customer service into the M time slots, including: the first forwarding label and the M time The slots have a corresponding relationship, and the customer service is mapped into the M time slots according to the first forwarding label.
  • the customer service can be mapped to the corresponding time slot according to the first forwarding label, so that multiple services are exchanged in the same switching plane of the flexible Ethernet.
  • the sending, by the M time slots, the customer service to the target physical channel includes: the M time slots and the target physical channel have a corresponding relationship.
  • the client service is encoded, and the client service forms a code block stream; and the first forwarding label is added in an S code block of the customer service, where the S code block is One of the code block types in the code block stream.
  • the first forwarding label is added in an L code block of the customer service, where the L code block is obtained by deleting an idle code block of the customer service, where the idle code block is obtained.
  • a type of code block in a code block stream is added in an L code block of the customer service, where the L code block is obtained by deleting an idle code block of the customer service, where the idle code block is obtained.
  • the method further includes: adding the first forwarding label to a frame header positioning overhead of the client service.
  • a second forwarding label is added to the client service, and the second forwarding label indicates a second forwarding destination address of the client service.
  • an embodiment of the present invention provides a method for processing a customer service, including: acquiring M time slots of a customer service from a target physical channel, and acquiring the customer service from the M time slots; a first forwarding label in the client service, deleting the first forwarding label and/or adding a third forwarding label; wherein the first forwarding label indicates a first forwarding destination address, the target physical channel and the first A forwarding destination address has a corresponding relationship; M is a positive integer greater than or equal to 1.
  • the exchange of multiple services in the same switching plane of the flexible Ethernet is realized.
  • the deleting the first forwarding label and/or adding the third forwarding label comprises: the first forwarding label is an inbound label, and the third forwarding label is an outgoing label; The first forwarding label acquires a third forwarding label; wherein the first forwarding label and the third forwarding label have a corresponding relationship.
  • the adding the third forwarding label includes: deleting an idle code block of the customer service, converting the S code block carrying the first forwarding label into an L code block, and increasing carrying The S code block of the third forwarding label; the idle code block, the S code block, and the L code block are respectively three code block types in the code block stream formed by the coding of the client service.
  • the deleting the first forwarding label includes: deleting the first forwarding label, and restoring the code block carrying the first forwarding label to a normal code block;
  • the normal code block includes any one of an S code block, an L code block, and a frame header positioning overhead, where the S code block and the L code block are respectively two code blocks in the code block stream formed by the coding of the client service. Types of.
  • an embodiment of the present invention provides a device for processing a client service, including: a receiving module, configured to receive a client service; and a mapping module, configured to: according to the first forwarding label carried in the client service The client service is mapped to the M time slots, the first forwarding label indicates the first forwarding destination address, and the sending module is configured to send the client service to the target physical channel by using the M time slots, where the target The physical channel has a corresponding relationship with the first forwarding destination address; where M is a positive integer greater than or equal to 1.
  • the customer service may include a data service and a TDM service, and the customer service is mapped into the M time slots through the first forwarding label carried in the customer service, and the customer service is sent to the target physical channel through the M time slots, thereby realizing Multiple services are exchanged in the same switching plane of flexible Ethernet.
  • the mapping module is configured to: the first forwarding label and the M time slots have a corresponding relationship, and map the client service to the In M time slots.
  • the customer service can be mapped to the corresponding time slot according to the first forwarding label, so that multiple services are exchanged in the same switching plane of the flexible Ethernet.
  • the M time slots and the target physical channel have a corresponding relationship.
  • the device further includes: an encoding module, configured to encode the client service, where the client service forms a code block stream; and a first adding module, configured to be in the client service The first forwarding label is added to the S code block, and the S code block is a type of code block in the code block stream.
  • the first adding module is further configured to: add the first forwarding label in an L code block of the customer service, where the L code block is deleted by deleting the customer service An idle code block is obtained, the idle code block being one of the code block types.
  • the device includes a second adding module, configured to: add the first forwarding label in a frame header positioning overhead of the client service.
  • the device further includes a third adding module, configured to: add a second forwarding label in the customer service, where the second forwarding label indicates a second forwarding destination of the customer service address.
  • an embodiment of the present invention provides a device for processing a customer service, including: a client service obtaining module, configured to acquire M time slots of a customer service from a target physical channel, and obtain the M time slots from the M time slots.
  • the client service a forwarding label obtaining module, configured to acquire a first forwarding label in the client service; and a forwarding label adding and deleting module, configured to delete the first forwarding label and/or add a third forwarding a label, where the first forwarding label indicates a first forwarding destination address, and the target physical channel has a corresponding relationship with the first forwarding destination address;
  • M is a positive integer greater than or equal to 1.
  • the first forwarding label is obtained from the customer service, the first forwarding label is deleted, and/or the third forwarding label is added, so that multiple services are exchanged in the same switching plane of the flexible Ethernet.
  • the forwarding label obtaining module is configured to: the first forwarding label is an inbound label, the third forwarding label is an outgoing label, and the third forwarding label is obtained according to the first forwarding label; The first forwarding label and the third forwarding label have a corresponding relationship.
  • the forwarding label addition and deletion module is configured to: delete an idle code block of the customer service, convert an S code block that carries the first forwarding label into an L code block, and increase carrying The S code block of the third forwarding label; the idle code block, the S code block, and the L code block are respectively three code block types in the code block stream formed by the coding of the client service.
  • the forwarding label addition and deletion module is configured to: delete the first forwarding label, and restore the code block carrying the first forwarding label to a normal code block; wherein the normal code
  • the block includes any one of an S code block, an L code block, and a frame header positioning overhead, where the S code block and the L code block are respectively two code block types in the code block stream formed by encoding the client service.
  • an embodiment of the present invention provides a computer device, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor and the memory are connected through a bus, and when the computer is running, the processor The computer executing the memory storage executes instructions to cause the computer to perform the method as described in the first aspect and any one of the possible implementations of the first aspect.
  • an embodiment of the present invention provides a computer device, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer to execute an instruction, and the processor and the memory are connected through a bus, and when the computer is running, the processor The computer executing the memory storage executes instructions to cause the computer to perform the method of any one of the second aspect and the second aspect.
  • the seventh aspect the embodiment of the present invention provides a network system, including the device in any one of the possible implementation manners of the third aspect or the third aspect, and any possible implementation of the fourth aspect or the fourth aspect The device in the way.
  • FIG. 1 is a schematic diagram of a layered structure of a flexible Ethernet according to an embodiment of the present invention
  • FIG. 2 is a data frame format of a flexible Ethernet according to an embodiment of the present invention.
  • FIG. 3 is a schematic structural diagram of a flexible Ethernet service processing according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a flexible Ethernet service processing according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a field format of an S code block according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic diagram of a format of a label defined by an MPLS according to an embodiment of the present disclosure
  • FIG. 7 is a schematic diagram of a field format of an L code block according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a FlexE overhead code block according to an embodiment of the present invention.
  • FIG. 9 is a network architecture diagram of a flexible Ethernet according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of an edge node device according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic diagram of an overhead structure of an OTN frame according to an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of a switching node device according to an embodiment of the present disclosure.
  • FIG. 13 is an exemplary flowchart of a method for processing customer services according to an embodiment of the present invention.
  • FIG. 14 is an exemplary flowchart of a method for processing a client service according to an embodiment of the present invention.
  • 15 is a schematic diagram of a logical structure of a device for processing a client service according to an embodiment of the present invention.
  • 16 is a schematic diagram of a logical structure of a device for processing a client service according to an embodiment of the present invention
  • FIG. 17 is a schematic structural diagram of a computer device according to an embodiment of the present invention.
  • FIG. 1 is a schematic diagram of a hierarchical structure of a flexible Ethernet according to an embodiment of the present invention.
  • the flexible Ethernet can include the FlexE client layer and the FlexE service layer.
  • FlexE client layer It is mainly used to support the aggregation of customer services, including, for example, the Media Access Control (MAC) layer, the Reconciliation Sublayer (RS), and the 64B/66B codec in the FlexE SHIM layer.
  • the FlexE client layer can include Ethernet interfaces with bandwidths of 10G, 25G, 40G, and N*50G.
  • the FlexE service layer is mainly used to support the bearer of FlexE client services, including functional layers other than 64B/66B codec in the FlexE SHIM layer, Physical Coding Sublayer (PCS), Forward Error Correction (Forward Error). Correction, FEC) layer, Physical Medium Attachment (PMA), Physical Medium Dependent (PMD).
  • PCS Physical Coding Sublayer
  • FEC Forward Error Correction
  • PMA Physical Medium Attachment
  • PMD Physical Medium Dependent
  • the FlexE service layer can be implemented by N-channel 100GE physical layer device (PHY), and can also be implemented by N-channel 400GE PHY.
  • FIG. 2 is a flexible Ethernet data frame format provided by an embodiment of the present invention.
  • the FlexE data frame is a data frame structure of 8 rows and (1+1023x20) columns, and is composed of 8x (1+1023x20) 66B code blocks.
  • the FlexE data frame includes a control code block, a data code block, and may also include an idle (IDLE) code block.
  • the control code block may include an overhead code block (O code block), a start code block (S code block), a tag code block (L code block), and the like.
  • the eight code blocks of the first column are O code blocks for carrying overhead information of the FlexE data frame.
  • S code blocks and L code blocks can be used to carry forwarding labels.
  • the data code block is used to carry data information of the customer service.
  • the IDLE code block may be a code block inserted when the client service performs rate adaptation.
  • FIG. 3 is a schematic structural diagram of a flexible Ethernet service process according to an embodiment of the present invention.
  • the service processing process may be a process of service multiplexing, and may be implemented on a transmitting end device of a flexible Ethernet.
  • the network device After receiving the multi-channel client customer service, for example, the customer service a, the customer service b, the customer service z, the network device performs 64B/66B encoding on the received multi-channel customer service.
  • a 66B code block stream is formed, and the code block stream of the client service is rate-fitted by inserting or deleting an idle (IDLE) code block.
  • IDLE idle
  • the code block stream of the customer service is sent to the FlexE service layer slot (Calendar) for exchange.
  • the code block stream of multiple client services is distributed into the sub-Calendar of the N-way PHY through the FlexE service layer time slot, and is in a certain interval period (for example, 20x66B) in the sub-Calendar of each PHY.
  • Insert FlexE overhead to identify the frame structure of FlexE or to identify the order of each PHY. Scrambling the sub-Calendar of each PHY, then The multiplexed PCS channel, which divides the sub-Calendar of each PHY, is inserted into the Alignment Marker (AM) and distributed to the PMA.
  • AM Alignment Marker
  • FIG. 4 is a schematic structural diagram of a flexible Ethernet service process according to an embodiment of the present invention.
  • the service processing process may be a process of demultiplexing a service, and may be implemented on a receiving end device of a flexible Ethernet.
  • the receiving device and the transmitting device of the flexible Ethernet can be different network devices or the same network device.
  • the process of service demultiplexing is opposite to the process of the service multiplexing process shown in FIG. 4, and the principle is similar, and details are not described herein again.
  • the first forwarding label may be added to the control code block of the customer service, for example, the S code block, for indicating the first forwarding destination address of the customer service.
  • the field format of the S code block is as shown in FIG. 5.
  • the S code block includes a synchronization header (10), a block type field (0x78), and data fields (D1 to D7).
  • the first forwarding label can be carried by the data fields (D1 to D7) in the S code block.
  • the first forwarding label can adopt a label format defined in Multiprotocol Label Switching (MPLS), as shown in FIG. 6.
  • MPLS Multiprotocol Label Switching
  • the total length of labels defined by MPLS is 32 bits, which can be divided into the following fields:
  • the length is 20 bits and is used to identify the forwarding relationship of the service.
  • the forwarding relationship of the service may include the forwarding destination address of the service, and may also include the forwarding source address of the service.
  • the forwarding relationship of the service includes the outgoing interface of the packet on a device, and may also include an inbound interface.
  • the label can include an outgoing label and an incoming label, respectively, for identifying the outgoing interface and the incoming interface of the service on a certain device.
  • the length is 3 bits and is used to identify the quality of service (QoS) of the service. For example, eight priority levels can be identified, including service types corresponding to different services such as voice, video, and data.
  • TTL The length is 8 bits, which is used to prevent loops when services are transmitted.
  • an S code block can carry at most one layer of labels, for example, the first forwarding label.
  • it can be implemented by deleting an idle (IDLE) code block in a code block stream of a client service and adding a control code block.
  • the added control code block is called L
  • the code block can also be a 66b code block.
  • the field format of the L code block is shown in FIG.
  • the format of the L code block and the S code block are similar, and the label is also carried by D1 to D7, except that the block type field is 0x79.
  • the L code block can carry a forwarding label, such as a second forwarding label.
  • the first forwarding label and the second forwarding label may be labels for different types of network devices, for example, the first forwarding label is for a network device of the access network, and the second forwarding label is for a network device of the transmission network.
  • the network device may include a control plane and a data plane.
  • the control plane is used for service control and configuration of the data plane, and the data plane transmits service data under the control of the control plane.
  • the transmission route and the label distribution signaling are used to configure a forwarding relationship of the service on the control plane of the network device.
  • the service is on the inbound interface and the outbound interface of a certain network device.
  • the forwarding relationship of the client service in the control plane is forwarded according to the forwarding label carried in the client service.
  • the FlexE overhead can be added when the code block stream of the customer service enters each FlexE physical interface (PHY), and the FlexE overhead can be represented by the O code block.
  • the structure diagram of the FlexE overhead code block is shown in Figure 8.
  • the signaling channel, label distribution and other signaling can be carried through the management channel in the FlexE overhead.
  • FIG. 9 is a network architecture diagram of a flexible Ethernet according to an embodiment of the present invention.
  • an edge node device and a switching node device may be included in the Ethernet.
  • the edge node device is used to connect to the client device and receive client traffic from the client device.
  • the switching node device and the edge node device and the different switching node devices are connected through interfaces, for example, P1, P2, P3, Pn, etc., for transmitting customer services.
  • the side where the edge node device is connected to the client device may be referred to as the client side, and the side to which the edge node device is connected to one side of the switching node device or the two switching node devices is referred to as the line side.
  • FIG. 10 is a schematic structural diagram of an edge node device according to an embodiment of the present invention.
  • the device may include a client signal processing module 101, a tag encapsulation module 102, a FlexE SHIM module 103, a tag assignment module 104, an overhead processing module 105, a routing table generation/update module 106, and at least one PHY module 107.
  • the modules may be circuit modules integrated on one chip, or Independent circuit module.
  • the functions implemented by the edge node device in the sending direction include:
  • the client signal processing module 101 is configured to receive a customer service from the client device and determine a service type of the client service.
  • the service type of the customer service received by the edge node device may include: a data service and a TDM service.
  • the data service may be a packet service, an Ethernet data service, an MPLS service, or an Internet Protocol (IP) service.
  • IP Internet Protocol
  • the TDM service may be a Synchronous Digital Hierarchy (SDH) service or an Optical Transport Network (OTN) service.
  • the label encapsulation module 102 is configured to perform 64B/66B encoding on the customer service to form a 66B code block stream.
  • the first forwarding label is obtained from the label distribution module 104, and the first forwarding label is added to the control code block in the 66B code block stream formed by the customer service.
  • the control code block can be an S code block.
  • the structure of the S code block and the first forwarding label refer to FIG. 5 and FIG. 6 respectively. How to add the first forwarding label to the S code block can also be referred to the foregoing embodiment, and details are not described herein again.
  • the client service If the received client service is a data service, such as an Ethernet data service, the client service itself carries the S code block. If the client service of the receiving is a TDM service, such as an OTN service, the client service itself does not carry the S code block.
  • the OTN service is taken as an example to describe how to increase the S code block for the OTN service.
  • the overhead structure of the OTN frame is shown in Figure 11.
  • the initial 6-byte frame alignment signal (FAS) of the OTN frame is the frame positioning overhead, and the fixed pattern is 0xf6f6f6282828.
  • FAS 6-byte frame alignment signal
  • the OTN service is stream sliced to divide the bit block, and the IDLE code block is rate-adjusted and adapted.
  • An implementation manner of adding an S code block in an OTN service may include:
  • Manner 1 When the OTN service is stream sliced, the 6 frame positioning overhead (FAS) of the OTN frame header is converted into an S code block. For example, when the OTN frame header indication comes, the 6-byte FAS of the OTN frame header is deleted, the S-code block is inserted, and the subsequent data stream continues to be sliced.
  • FAS frame positioning overhead
  • an S code block can be added to the OTN service. For example, when the OTN frame header indication comes, an S code block is inserted, and at the same time, an IDLE code block can be deleted to adapt to the signal rate after the S code block is added. The data stream is then sliced starting from the first byte of the OTN frame.
  • the second forwarding tag can also be added by deleting the IDLE code block in the client service and adding the L code block.
  • the structure diagram of the L code block refer to FIG. 7. How to add the second forwarding label to the L code block can also be referred to the foregoing embodiment, and details are not described herein again.
  • the client service Before adding the first forwarding label and/or the second forwarding label in the customer service, the client service may be 64B/66B encoded, the customer service is converted into a 66B code block stream, and then the 66B code block stream is rate-adapted, for example, The IDLE code block can be inserted or deleted in the 66B code block stream.
  • the rate adaptation of the 66B code block stream may also be performed after adding the first forwarding label and/or the second forwarding label, or may also add the first forwarding while performing rate adaptation on the 66B code block stream.
  • the label and/or the second forwarding label are not limited in the present invention.
  • the label distribution module 104 is configured to perform forwarding label allocation on the customer service.
  • the forwarding label includes the first forwarding label, the second forwarding label, and the like as described above, and the allocation principles of the forwarding labels of different levels may be the same.
  • the first forwarding label is taken as an example for description.
  • the label distribution module 104 may allocate the first forwarding label according to any one or more of the IP header, the MAC address, and the flow identifier of the customer service.
  • the first forwarding label can be assigned according to the principle of Forwarding Equivalence Class (FEC).
  • FEC Forwarding Equivalence Class
  • Forwarding equivalence classes refer to forwarding a group of services in the same way, for example, through the same channel or with the same forwarding destination address.
  • the same first forwarding label can be used if the subsequent client service belongs to the same stream as the previous client service, for example with a common IP or common quintuple information.
  • the client service encapsulation module 102 determines that the current client service can use the same first forwarding label as the previous client service, the forwarding label may not be obtained from the label distribution module 104, and the first customer service is directly added.
  • the label allocation module 104 can also allocate the number of time slots occupied by the customer service according to the bandwidth of the customer service and the bandwidth granularity of the network. For example, a FlexE service layer in flexible Ethernet has a slot granularity of 5G. For a 10G customer service, two slots can be allocated for the 10G customer service.
  • forwarding labels can be assigned based on pre-configured information.
  • the pre-configured information may include forwarding tag information, time slot information, and the like.
  • the TDM service can be pre-configured with forwarding label information, time slot information, and so on. For example, a 10G TDM The service allocates 2 slots and uses label 1 as the first forwarding label.
  • the FlexE SHIM module 103 is used to map customer services into FlexE service layer slots.
  • the client service may be mapped to the corresponding time slot according to the forwarding label information, and the customer service may be mapped into the corresponding time slot according to the time slot information.
  • the forwarding label has a correspondence relationship with N time slots occupied by the client service. For example, a 10G client service occupies slot 1 and slot 2, and the first forwarding label of the client service is label 1, and label 1 has a corresponding relationship with slot 1 and slot 2.
  • the FlexE SHIM module 103 can map the customer service to the time slot 1 and the time slot 2 according to the first forwarding label label 1 carried by the customer service, or according to the time slot information of the customer service (occupying the time slot 1 and the time slot 2). ), mapping customer traffic into slot 1 and slot 2.
  • the first forwarding label may indicate which one or more PHY modules are used to send the customer service. FlexE service layer time slots carrying customer traffic can be distributed to one or more PHY modules while inserting FlexE
  • the PHY module 107 is configured to send client traffic to a physical transmission link on the line side.
  • the edge node device has at least one physical interface, and the customer service is sent to the physical transmission link of the line side through the physical interface.
  • the customer service can be received or forwarded by the target device through the physical transmission link.
  • a physical interface may include at least one PHY module, each PHY module corresponding to a respective time slot.
  • a 100G PHY module corresponds to 20 5G granular FlexE time slots.
  • the client service is distributed to the corresponding PHY module according to the correspondence between the time slot and the PHY module. For example, slot 1 and slot 2 occupied by the 10G client service correspond to PHY1, and slot 1 and slot 2 of the customer service are distributed to PHY1.
  • the overhead processing module 105 is configured to insert a FlexE overhead.
  • FlexE overhead can also be inserted in each PHY module.
  • the FlexE overhead is used to monitor the link status, and the generation and update of the link status can direct the routing table generation/update module 106 to generate and/or update the routing table.
  • the routing table includes the topology information of the network and the forwarding relationship of the service, and can provide a basis for allocating forwarding labels for the customer service.
  • the signaling of the routing, label distribution, and the like may also be carried in the FlexE overhead. For details, refer to the embodiment shown in FIG. 8.
  • the functions implemented by the edge node device in the receiving direction include:
  • the PHY module 107 is configured to receive client services from the line side. Can pass one or more PHY modules Receive customer traffic from the physical transport link. For example, a 10G customer service is received from PHY1.
  • the FlexE SHIM module 103 is configured to receive customer traffic from one or more PHY modules 107.
  • the client service can be a 66B code block stream.
  • the FlexE overhead is extracted in the 66B code block stream and data alignment is performed.
  • the FlexE service layer time slot (Calendar) is restored, and each client service is recovered according to the time slot information. For example, the 10G client service corresponding to slot 1 and slot 2 is recovered from PHY1.
  • the FlexE SHIM module 103 can also send the FlexE overhead information to the overhead processing module 105, so that the overhead processing module 105 performs link state monitoring according to the FlexE overhead information.
  • the label encapsulating module 102 performs recovery processing on the first forwarding label information of the client signal.
  • the first forwarding label information in the S code block may be deleted and restored to the original S code block before the first forwarding label is added.
  • the rate adaptation is then performed by adding or deleting an IDLE code block, etc., and the 66B code block stream is decoded and then sent to the client signal processing module 101.
  • the S code block is added by deleting the IDLE code block, the S code block can be discarded; if the S code block is formed by the frame positioning overhead conversion, the S code block can be restored to the frame header positioning overhead.
  • the sync header of the 66B code block stream is then removed and sent to the client signal processing module 101.
  • the client signal processing module 101 is configured to receive the 64B/66B decoded code block stream and recover the original client service, for example, TDM service, data service, and the like.
  • the edge node device adds a first forwarding label to the client service, performs service switching according to the first forwarding label, and sends the client service to the target physical channel to implement the same switching plane on the flexible Ethernet. Exchange of various services.
  • FIG. 12 is a schematic structural diagram of a switching node device according to an embodiment of the present invention.
  • the device may include a PHY module 201/207, a FlexE SHIM module 202/206, a tag encapsulation module 203, a frame header alignment module 204, a switch module 205, a tag assignment module 208, and overhead.
  • the processing module 209 and the routing table generation/update module 210 may be circuit modules integrated on one chip, or may be independent circuit modules.
  • the switching node device has the same function in the sending direction and the signal in the receiving direction. The following functions are implemented in the sending direction as an example:
  • the PHY module 201 is configured to receive client services from the line side. For example, customer service is received from an edge node device or other switching node device through one or more PHY modules.
  • the FlexE SHIM module 202 is configured to receive client traffic from one or more PHY modules 201.
  • the client service can be a 66B code block stream.
  • the FlexE overhead is extracted in the 66B code block stream and data alignment is performed.
  • the FlexE service layer time slot (Calendar) is restored, and each client service is recovered according to the time slot information. For example, the 10G client service corresponding to slot 1 and slot 2 is recovered from PHY1.
  • the FlexE SHIM module 202 can also send the FlexE overhead information to the overhead processing module 209, so that the overhead processing module 209 performs link state monitoring according to the FlexE overhead information.
  • the label encapsulating module 203 is configured to apply for a new first forwarding label (such as a label) to the label distribution module 208 according to a customer service, for example, a first forwarding label (such as an inbound label) carried in the S code block, and may also apply for a labeling behavior. Instructions.
  • the label distribution module 208 can store the forwarding label information table. As shown in Table 1, the forwarding label information table can include information such as the node device identifier NE2, the inbound interface P2, the inbound label label 1, the outbound interface P3, and the outgoing label 2. It can also include tag behavior indications, such as tag nesting.
  • the function of the label distribution module 208 is similar to that of the label distribution module 104 in the edge node device, and details are not described herein again.
  • the inbound interface and/or the ingress label may indicate which one or which PHY modules on the node device NE2 the client service receives, and the outbound interface and the outbound label may indicate which PHY module of the client device is sent by the PHY module on the node device NE2.
  • the first forwarding label carried by the customer service may be an incoming label, and the new first forwarding label is an outgoing label.
  • the inbound label and the outbound label establish a corresponding relationship in the forwarding label information table. Therefore, the label can be obtained according to the inbound label, and the outbound interface can also be obtained.
  • Tag behavior indications can include tag nesting, tag popping, tag switching, and the like.
  • an IDLE code block may be deleted, and the S code block currently carrying the first forwarding label is converted into an L code block, and an S code block carrying a new first forwarding label is added in front of the L code block. . If the outer label needs to be ejected, the S code block carrying the outer label is discarded, and one L code block following the S code block is converted into an S code block.
  • a label is required to be popped up, if there is only one layer of label, the S code block in which the layer label is located is restored to the original S code block, that is, the label information is restored to the original data field.
  • the last layer of labels generally cannot be popped up in advance.
  • the frame header alignment module 204 is configured to align the 66B code block stream of each client service, and send the aligned code block stream to the switch module 205.
  • the switching module 205 is configured to perform data exchange according to the first forwarding label carried by the customer service.
  • the first forwarding label here may be that the label encapsulating module 203 applies to the label distribution module 208 for a new first forwarding label, that is, an outgoing label.
  • data exchange can also be performed according to the outbound interface.
  • the switching module 205 is equivalent to determining which PHY module 207 the client service is sent out from.
  • the FlexE SHIM module 206 is configured to map customer traffic into a time slot (Calendar) of the FlexE service layer.
  • the client service may be mapped to the corresponding time slot according to the forwarding label information, and the customer service may be mapped into the corresponding time slot according to the time slot information.
  • the forwarding label has a correspondence relationship with N time slots occupied by the client service. For example, a 10G client service occupies slot 1 and slot 2, and the first forwarding label of the client service is label 2, and label 2 has a corresponding relationship with slot 1 and slot 2.
  • the FlexE SHIM module 206 can map the customer service to the time slot 1 and the time slot 2 according to the first forwarding label 2 carried by the customer service, or according to the time slot information of the customer service (occupying the time slot 1 and the time slot 2). ), mapping customer traffic into slot 1 and slot 2.
  • the first forwarding label may indicate which one or more PHY modules are used to send the customer service.
  • FlexE service layer time slots carrying customer traffic can be distributed to one or more PHY modules while inserting FlexE overhead.
  • a certain buffer may also be added for QoS processing of data services.
  • the PHY module 207 is configured to send client traffic to the other side line side.
  • the functions of the PHY module 207 and the PHY 107 in the edge node device are similar and will not be described again.
  • the functions of the overhead processing module 209 and the routing table generation/update module 210 are similar to those of the overhead processing module 105 and the table generation/update module 106 in the edge node device, and are not described herein again.
  • the first forwarding label is carried in the customer service received by the switching node device, and the service is exchanged according to the first forwarding label, so that the exchange of multiple services in the same switching plane of the flexible Ethernet is implemented.
  • FIG. 13 is an exemplary flowchart of a method for processing customer services according to an embodiment of the present invention.
  • the method can be performed by an Ethernet device, an OTN device, a router, a switch, etc., and includes the following steps:
  • S1301 Receive a client service, and map the client service to the M timeslots according to the first forwarding label carried in the client service, where the first forwarding label indicates the first forwarding destination address.
  • the first forwarding label and the M time slots have a corresponding relationship, and the customer service is mapped into the M time slots according to the first forwarding label.
  • encoding the client service where the client service forms a code block stream; adding the first forwarding label to the S code block of the customer service, where the S code block is the code block stream A type of code block in .
  • the first forwarding label is added in an L code block of the customer service, where the L code block is obtained by deleting an idle code block of the customer service, where the idle code block is in the code block stream.
  • a type of code block is added in an L code block of the customer service, where the L code block is obtained by deleting an idle code block of the customer service, where the idle code block is in the code block stream.
  • the first forwarding label is added in a frame header positioning overhead of the client service.
  • a second forwarding label is added to the client service, and the second forwarding label indicates a second forwarding destination address of the client service.
  • S1302 Send the client service to the target physical channel by using the M time slots, where the target physical channel has a corresponding relationship with the first forwarding destination address; where M is a positive integer greater than or equal to 1.
  • the M time slots and the target physical channel have a corresponding relationship.
  • the first forwarding destination address may be the destination MAC address of the next hop node device forwarded by the client service, or the outbound port identifier of the node device that forwards the client service or the identifier of the PHY module.
  • the customer service is mapped into the M time slots by using the first forwarding label carried in the customer service, and the customer service is sent to the target physical channel through the M time slots, thereby realizing the flexible Ethernet. Exchange of multiple services in the same switching plane.
  • FIG. 14 is an exemplary flowchart of a method for processing customer services according to an embodiment of the present invention.
  • the method can be performed by an Ethernet device, an OTN device, a router, a switch, etc., and includes the following steps:
  • S1401 Obtain M time slots of the customer service from the target physical channel, and obtain the customer service from the M time slots.
  • S1402 Acquire a first forwarding label in the customer service, delete the first forwarding label, and/or add a third forwarding label, where the first forwarding label indicates a first forwarding destination address, and the target physical channel Corresponding to the first forwarding destination address; M is a positive integer greater than or equal to 1.
  • the first forwarding label is an inbound label
  • the third forwarding label is an outgoing label
  • the third forwarding label is obtained according to the first forwarding label, where the first forwarding label and the third forwarding label are Have a corresponding relationship.
  • deleting the idle code block of the customer service converting the S code block carrying the first forwarding label into an L code block, and adding an S code block carrying the third forwarding label; the idle code
  • the block, the S code block, and the L code block are respectively three code block types in the code block stream formed by the coding of the client service.
  • the first forwarding label is deleted, and the code block carrying the first forwarding label is restored to a normal code block, where the normal code block includes an S code block, an L code block, and a frame header positioning overhead.
  • the normal code block includes an S code block, an L code block, and a frame header positioning overhead.
  • Any one of the S code blocks and the L code blocks are respectively two code block types in the code block stream formed by the coding of the client service.
  • the first forwarding destination address may be a destination MAC address of a node device that receives the client service, or an ingress port identifier of the node device that receives the client service, or an identifier of the PHY module.
  • the third forwarding label may indicate the destination MAC address of the next hop node device forwarded by the client service, or may be the outbound port identifier of the node device that forwards the client service or the identifier of the PHY module.
  • the first forwarding label is obtained from the customer service, the first forwarding label is deleted, and/or the third forwarding label is added, so that the exchange of multiple services in the same switching plane of the flexible Ethernet is implemented.
  • FIG. 15 is a schematic diagram of a logical structure of a device for processing a client service according to an embodiment of the present invention.
  • the device may be implemented by an Ethernet device, an OTN device, a router, a switch, or the like, and includes: a receiving module 1501, a mapping module 1502, and a sending module 1503.
  • the receiving module 1501 is configured to receive a customer service.
  • the mapping module 1502 is configured to map the customer service into M time slots according to the first forwarding label carried in the customer service, where the first forwarding label indicates the first forwarding destination address.
  • the mapping module 1502 is configured to: the first forwarding label and the M time slots have a corresponding relationship, and map the customer service to the M time slots according to the first forwarding label. in.
  • the sending module 1503 is configured to send the client service to the target physical channel by using the M time slots, where the target physical channel has a corresponding relationship with the first forwarding destination address, where M is greater than or equal to 1 Positive integer.
  • the M time slots and the target physical channel have a corresponding relationship.
  • the device further includes: an encoding module, configured to encode the client service, where the client service forms a code block stream; and a first adding module, configured to add in the S code block of the customer service The first forwarding label, the S code block is a type of code block in the code block stream.
  • the first adding module is further configured to: add the first forwarding label in an L code block of the customer service, where the L code block is obtained by deleting an idle code block of the customer service,
  • the idle code block is one of the code block types in the code block stream.
  • the device includes a second adding module, configured to: add the first forwarding label in a frame header positioning overhead of the client service.
  • the device further includes a third adding module, configured to: add a second forwarding label in the customer service, where the second forwarding label indicates a second forwarding destination address of the customer service.
  • a third adding module configured to: add a second forwarding label in the customer service, where the second forwarding label indicates a second forwarding destination address of the customer service.
  • the customer service is mapped into the M time slots by using the first forwarding label carried in the customer service, and the customer service is sent to the target physical channel through the M time slots, thereby realizing the flexible Ethernet. Exchange of multiple services in the same switching plane.
  • FIG. 16 is a schematic diagram of a logical structure of a device for processing a client service according to an embodiment of the present invention.
  • the device can be executed by an Ethernet device, an OTN device, a router, a switch, and the like, and includes: a client service obtaining module 1601, a forwarding label obtaining module 1602, and a forwarding label adding and deleting module 1603.
  • the customer service obtaining module 1601 is configured to acquire M time slots of the customer service from the target physical channel, and obtain the customer service from the M time slots;
  • the forwarding label obtaining module 1602 is configured to acquire a first forwarding label in the customer service.
  • the forwarding label obtaining module 1602 is configured to: the first forwarding label is an inbound label, the third forwarding label is an outgoing label, and the third forwarding label is obtained according to the first forwarding label; The first forwarding label and the third forwarding label have a corresponding relationship.
  • the forwarding label addition and deletion module 1603 is configured to delete the first forwarding label and/or add a third forwarding label, where the first forwarding label indicates a first forwarding destination address, the target physical channel and the first forwarding The destination address has a corresponding relationship; M is a positive integer greater than or equal to 1.
  • the forwarding label addition and deletion module 1603 is configured to: delete an idle code block of the customer service, convert an S code block carrying the first forwarding label into an L code block, and increase carrying the third Forwarding the S code block of the tag; the idle code block, the S code block, and the L code block are respectively three code block types in the code block stream formed by the coding of the client service.
  • the forwarding label addition and deletion module 1603 is configured to: delete the first forwarding label, and restore the code block carrying the first forwarding label to a normal code block; where the normal code block includes an S code. Any one of a block, an L code block, and a frame header locating overhead, wherein the S code block and the L code block are respectively two code block types in the code block stream formed by the coding of the client service.
  • the first forwarding label is obtained from the customer service, the first forwarding label is deleted, and/or the third forwarding label is added, so that the exchange of multiple services in the same switching plane of the flexible Ethernet is implemented.
  • FIG. 17 is a schematic structural diagram of a computer device according to an embodiment of the present invention.
  • computer device 1700 includes a processor 1701, a memory 1702, an input/output interface 1703, a communication interface 1704, and a bus 1705.
  • the processor 1701, the memory 1702, the input/output interface 1703, and the communication interface 1704 implement a communication connection with each other through the bus 1705.
  • the processor 1701 can use a general-purpose central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or at least one integrated circuit for executing related programs to implement the present invention.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • the memory 1702 may be a read only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). Memory 1702 You can store operating systems and other applications.
  • ROM read only memory
  • RAM random access memory
  • the input/output interface 1703 is for receiving input data and information, and outputting data such as an operation result.
  • Communication interface 1704 enables communication between computer device 1700 and other devices or communication networks using transceivers such as, but not limited to, transceivers.
  • Bus 1705 can include a path for communicating information between various components of computer device 1700, such as processor 1701, memory 1702, input/output interface 1703, and communication interface 1704.
  • the computer device 1700 executes the code stored in the memory 1702 by the processor 1701, and implements the steps of: receiving a customer service, and mapping the customer service into M time slots according to the first forwarding label carried in the customer service,
  • the first forwarding label indicates a first forwarding destination address
  • the client service is sent to the target physical channel by using the M time slots, where the target physical channel has a corresponding relationship with the first forwarding destination address; Is a positive integer greater than or equal to 1.
  • the computer device 1700 executes the code stored in the memory 1702 by the processor 1701, and implements the steps of: acquiring M time slots of the customer service from the target physical channel, acquiring the customer service from the M time slots; acquiring the a first forwarding label in the customer service, deleting the first forwarding label and/or adding a third forwarding label; wherein the first forwarding label indicates a first forwarding destination address, the target physical channel and the first The forwarding destination address has a corresponding relationship; M is a positive integer greater than or equal to 1.
  • the steps in the method embodiments shown in FIGS. 13 and 14 can be implemented by the computer device 1700 shown in FIG.
  • the computer device 1700 shown in FIG. 17 only shows the processor 1701, the memory 1702, the input/output interface 1703, the communication interface 1704, and the bus 1705, those skilled in the art will understand in the specific implementation process.
  • Computer device 1700 also includes other devices necessary to achieve proper operation.
  • computer device 1700 can also include hardware devices that implement other additional functions, depending on the particular needs.
  • computer device 1700 may also only include the components necessary to implement embodiments of the present invention, and does not necessarily include all of the devices shown in FIG.
  • the customer service is mapped into the M time slots by using the first forwarding label carried in the customer service, and the customer service is sent to the target physical channel through the M time slots, thereby realizing the flexible Ethernet. Exchange of multiple services in the same switching plane.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computing Systems (AREA)
  • Physics & Mathematics (AREA)
  • Electromagnetism (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Des modes de réalisation de l'invention concernent un procédé et un dispositif permettant de traiter un service client. Le procédé de traitement d'un service client consiste : à recevoir un service client, à mettre en correspondance le service client avec M intervalles selon une première étiquette de transfert portée par le service client, la première étiquette de transfert indiquant une première adresse de destination de transfert ; à envoyer, au moyen des M intervalles, le service client à un canal physique cible, le canal physique cible correspondant à la première adresse de destination de transfert ; M est un nombre entier positif supérieur ou égal à 1. La solution technique de la présente invention met en œuvre la commutation de services multiples sur le même plan de commutation de l'Ethernet flexible.
PCT/CN2016/102740 2016-05-25 2016-10-20 Procédé et dispositif de traitement de service client WO2017201953A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610356192.9 2016-05-25
CN201610356192.9A CN107438028B (zh) 2016-05-25 2016-05-25 一种客户业务处理的方法和设备

Publications (1)

Publication Number Publication Date
WO2017201953A1 true WO2017201953A1 (fr) 2017-11-30

Family

ID=60412690

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/102740 WO2017201953A1 (fr) 2016-05-25 2016-10-20 Procédé et dispositif de traitement de service client

Country Status (2)

Country Link
CN (1) CN107438028B (fr)
WO (1) WO2017201953A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111147181A (zh) * 2018-11-02 2020-05-12 中兴通讯股份有限公司 业务发送方法、接收方法、装置及系统、存储介质
CN111278059A (zh) * 2018-12-04 2020-06-12 中兴通讯股份有限公司 一种报文转发方法和装置
EP3742637A4 (fr) * 2018-01-15 2021-10-13 Sanechips Technology Co., Ltd. Procédé et appareil de transmission de données et support de stockage
CN114430305A (zh) * 2022-03-02 2022-05-03 烽火通信科技股份有限公司 一种细粒度帧的定帧方法和系统

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111727589B (zh) * 2017-12-22 2022-05-27 瑞典爱立信有限公司 用于配置Flex以太网节点的方法和设备
CN109995434B (zh) * 2017-12-29 2020-09-08 华为技术有限公司 一种数据传输方法、通信设备及存储介质
CN110224949B (zh) * 2018-03-01 2022-05-20 中兴通讯股份有限公司 一种灵活以太网设备端口绑定的方法及装置、路径建立方法及装置
CN110266612B (zh) * 2018-03-12 2022-01-25 中兴通讯股份有限公司 数据传输方法及装置、网络设备及存储介质
CN110324110B (zh) * 2018-03-30 2020-10-27 华为技术有限公司 一种通信方法、通信设备及存储介质
CN110417542B (zh) * 2018-04-26 2022-03-18 中兴通讯股份有限公司 一种传输客户业务的方法、装置和系统
CN113645005A (zh) * 2018-04-28 2021-11-12 华为技术有限公司 报文处理方法及设备
CN111181848B (zh) * 2018-11-09 2022-02-15 中国电信股份有限公司 网络分片方法、系统、路由器和存储介质
CN112243019B (zh) * 2019-07-19 2021-09-07 烽火通信科技股份有限公司 一种灵活以太网管理通道建立方法及系统
CN113472826A (zh) * 2020-03-30 2021-10-01 中兴通讯股份有限公司 一种业务承载、提取方法、数据交换方法及设备
CN114615142B (zh) * 2020-12-03 2023-06-09 烽火通信科技股份有限公司 一种业务处理的方法和装置
CN114567542B (zh) * 2022-02-16 2023-09-15 烽火通信科技股份有限公司 硬管道专线逐跳业务检测方法、装置、设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1933362A (zh) * 2005-09-14 2007-03-21 展讯通信（上海）有限公司 Td－scdma系统中多业务下的无线承载映射方法
US20130232213A1 (en) * 2009-03-31 2013-09-05 Match.Com, L.L.C. System and method for providing calendar and speed dating features for matching users in a network environment
CN104919889A (zh) * 2013-01-11 2015-09-16 交互数字专利控股公司 在无线局域网中的范围扩展

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1330139C (zh) * 2003-07-31 2007-08-01 华为技术有限公司 多协议标签交换（mpls）支持多端口虚拟局域网（vlan）的方法
CN1791057B (zh) * 2004-12-15 2011-06-15 华为技术有限公司 在光传送网中传输数据业务的方法及其装置
JP5696957B2 (ja) * 2012-02-22 2015-04-08 日本電信電話株式会社 マルチレーン伝送装置及びマルチレーン伝送方法
CN102891813B (zh) * 2012-09-05 2015-09-23 盛科网络（苏州）有限公司 支持多传输模式的以太网端口架构
US9609400B2 (en) * 2013-08-22 2017-03-28 Nec Corporation Reconfigurable and variable-rate shared multi-transponder architecture for flexible ethernet-based optical networks

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1933362A (zh) * 2005-09-14 2007-03-21 展讯通信（上海）有限公司 Td－scdma系统中多业务下的无线承载映射方法
US20130232213A1 (en) * 2009-03-31 2013-09-05 Match.Com, L.L.C. System and method for providing calendar and speed dating features for matching users in a network environment
CN104919889A (zh) * 2013-01-11 2015-09-16 交互数字专利控股公司 在无线局域网中的范围扩展

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3742637A4 (fr) * 2018-01-15 2021-10-13 Sanechips Technology Co., Ltd. Procédé et appareil de transmission de données et support de stockage
CN111147181A (zh) * 2018-11-02 2020-05-12 中兴通讯股份有限公司 业务发送方法、接收方法、装置及系统、存储介质
US20220006745A1 (en) * 2018-11-02 2022-01-06 Zte Corporation Service sending and receiving methods, device, system and storage medium
CN111147181B (zh) * 2018-11-02 2022-12-09 中兴通讯股份有限公司 业务发送方法、接收方法、装置及系统、存储介质
US12040981B2 (en) 2018-11-02 2024-07-16 Xi'an Zhongxing New Software Co., Ltd. Service receiving methods, device, system and storage medium
CN111278059A (zh) * 2018-12-04 2020-06-12 中兴通讯股份有限公司 一种报文转发方法和装置
CN111278059B (zh) * 2018-12-04 2023-09-01 中兴通讯股份有限公司 一种报文转发方法和装置
CN114430305A (zh) * 2022-03-02 2022-05-03 烽火通信科技股份有限公司 一种细粒度帧的定帧方法和系统
CN114430305B (zh) * 2022-03-02 2023-06-09 烽火通信科技股份有限公司 一种细粒度帧的定帧方法和系统

Also Published As

Publication number Publication date
CN107438028A (zh) 2017-12-05
CN107438028B (zh) 2020-10-09

Similar Documents

Publication Publication Date Title
WO2017201953A1 (fr) Procédé et dispositif de traitement de service client
US11700083B2 (en) Method and apparatus for processing service data in optical transport network
US20210084383A1 (en) Service data processing method and apparatus
WO2017156987A1 (fr) Procédé et appareil d'établissement de chemin ethernet flexible (flexe)
US11477549B2 (en) Transmission network system, data switching and transmission method, apparatus and equipment
CN106803814B (zh) 一种灵活以太网路径的建立方法、装置及系统
JP6736701B2 (ja) サービス送信方法及び装置、サービス受信方法及び装置、並びにネットワーク・システム
US9825845B2 (en) Path computation method, path computation element, node device, and network system
WO2019062227A1 (fr) Procédé de transmission de données, dispositif de transmission, et système de transmission
WO2018090856A1 (fr) Procédé et dispositif de construction de groupe ethernet flexible
US11271668B2 (en) Data transmission methods, apparatuses, devices, and system
US9385943B2 (en) Encoding and processing of signaling messages for ODU SMP
US8416770B2 (en) Universal service transport transitional encoding
US8958701B2 (en) Methods and systems of preserving client overhead bytes in optical transport network tunneling applications
WO2019071369A1 (fr) Procédé de transmission de données dans un réseau optique et dispositif de réseau optique
EP2667552B1 (fr) Procédé de transmission de service sur un réseau de transport optique, dispositif et système pour sa mise en oeuvre
CN113557696B (zh) 在网络中路由FlexE数据
US20090103533A1 (en) Method, system and node apparatus for establishing identifier mapping relationship
EP4117237A1 (fr) Procédé de réglage de flux de service et dispositif de communication
AU2010230712A1 (en) Method and Device for Sending Data and Receiving Service Data
WO2017181675A1 (fr) Procédé, dispositif et système de traitement de données sur ethernet
WO2021027434A1 (fr) Procédé, dispositif et système de transmission de services
EP2093916B1 (fr) Interface de passerelle pour hiérarchie de transport optique
WO2021213225A1 (fr) Procédé de traitement de trame de signal et dispositif associé
WO2024001370A1 (fr) Procédé d'inondation basé sur une capacité à granularité fine, procédé de configuration à granularité fine, nœud et support

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 16902937

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16902937

Country of ref document: EP

Kind code of ref document: A1