WO2010124563A1

WO2010124563A1 - Management method and system for controlling data transmission

Info

Publication number: WO2010124563A1
Application number: PCT/CN2010/071891
Authority: WO
Inventors: 袁立权; 叶宇煦
Original assignee: 中兴通讯股份有限公司
Priority date: 2009-04-27
Filing date: 2010-04-19
Publication date: 2010-11-04
Also published as: CN101873247B; CN101873247A

Abstract

The present invention discloses a management method for controlling data transmission. The method includes: data transmission is controlled with a management message transmitted between the physical layer and the link layer; said management message is a management message for controlling said data transmission. The present invention also discloses a management system for controlling data transmission. The system comprises a control unit for transmitting, between the link layer and the physical layer, a management message for controlling data transmission, to control the data transmission corresponding to said management message. With the method and system of the present invention, the bi-directional data transmission between the link layer and the physical layer can be effectively managed; and both of the uplink traffic and downlink traffic are controlled, thus leading to more comprehensive control and management of data transmission.

Description

Management method and system for controlling data transmission

The present invention relates to the field of data communications, and in particular, to a management method and system for controlling digital subscriber line (DSL) data transmission. Background technique

The DSL chip and the upper layer processor generally carry data through a physical interface (UMTIA, Universal Test & Operations PHY Interface for ATM) bus for asynchronous transfer mode (ATM), or synchronous optical network (SONET). The physical interface (POS-PHY, Packet Over SONET PHYsical) bus is connected, and a set of buses can be connected to multiple user ports on the DSL chip to communicate with the DSL chip through the address and data lines. Taking into account the limitations of the electrical characteristics defined by the bus standard, such as the clock frequency not exceeding 50Mhz and the bus width being 16 bits, the maximum bandwidth is 800Mbits per second, which can support up to 64 DSL users. The UTOPIA bus/POS-PHY bus has an address polling function that determines the source port of user data and provides a basis for subsequent forwarding.

With the development of DSL technology, the services currently opened generally require more than 25M of bandwidth. Therefore, when 64 DSL users use the service at the same time, the bandwidth of the UTOPIA bus/POS-PHY bus 800M is obviously not enough. At the same time, due to the electrical characteristics of the bus, the transmission distance and rate of the UTOPIA bus/POS-PHY bus are inversely proportional, requiring dozens of signal lines, so wiring is also difficult. Therefore, an improved serial bus is proposed for the UTOPIA bus/POS-PHY bus to solve the problem of rate and wiring. The International Telecommunication Union (ITU-T) defines the corresponding data transmission protocol, mainly by identifying the data flow. The data is encapsulated and transmitted over the serial bus, so that when the data is serially transmitted, each data stream can be distinguished by the identification.

Specifically, the ITU-T standard G.int defines the header shown in Figure 1, which is defined for The header encapsulation format of an existing packet that transports a data stream. The SID in Figure 1 refers to the data flow identifier, which is used to distinguish data flows of different users, as shown by SID0~SID9; EOF refers to the start identifier of the data flow, which is used to identify the start position of the data flow; SOF refers to the end identifier of the data flow. , used to identify the end of the data stream. Moreover, the ITU-T standard G.int also provides an interrupt frame for controlling the data stream, so that when the downlink data traffic is greater than the physical layer receiving capability, the link layer is notified to stop transmitting the corresponding data stream. In the ITU-T standard G.int, for uplink data, it is considered that congestion does not occur and does not provide flow control capability. However, for the uplink data of the physical layer, since the serial bus is connected to multiple DSL lines, The rate of different lines may be different, and there is an urgent need for flow control.

In summary, the problems existing in the prior art are as follows: Since the downlink traffic control is only processed by using an interrupt frame, the control mode is single and inflexible, and the control mode cannot be customized for actual needs, thereby failing to link layer and The data transmission between the physical layers is effectively managed; in particular, the flow control is not provided for the upstream traffic, and the control method is not comprehensive enough. In response to these issues, no effective solutions have yet been provided. Summary of the invention

In view of this, the main object of the present invention is to provide a management method and system for controlling data transmission, which can effectively manage bidirectional data transmission between a link layer and a physical layer; and control both uplink traffic and downlink traffic. , Control and management of data transmission is more comprehensive.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

A management method for controlling data transmission, the method comprising: controlling data transmission by a management message transmitted between a link layer and a physical layer; the management message being a management message for controlling the data transmission.

The control mode for managing message transmission includes: a master-slave control mode or a symmetric control mode;

The master-slave control mode is: All transmissions of management messages are initiated by the link layer. The management message is sent to the physical layer, and the physical layer responds only to the management message delivered by the link layer.

The symmetric control mode is: the link layer actively initiates the transmission of the management message, and sends the management message to the physical layer, where the physical layer responds to the management message delivered by the link layer; or The physical layer actively initiates the transmission of the management message, and reports the management message to the link layer, where the link layer responds to the management message reported by the physical layer.

The management message is encapsulated by a management packet, and the data is encapsulated by using a data packet; the management packet and the data packet are transmitted by using the same physical link; wherein, when the management packet and the data packet are the same In the packet header encapsulation format, after the link layer or the physical layer receives the management packet and the data packet, the management packet and the data packet are distinguished by the distinguishing identifier in the packet header encapsulation format; the type of the distinguishing identifier includes: Or type field identifier; when the management packet and the data packet adopt different header encapsulation formats, the type domain identifiers identifying different service types are set in the packet header encapsulation format of the data packet, and the transmission and identification of at least one service type are supported; After receiving the data packet, the layer identifies data of different service types by using the type field identifier in the packet header encapsulation format.

Wherein, when the data packet is encapsulated by the data packet, at least one data is encapsulated into the same data packet.

The management message includes: a control policy for transmitting data of at least one service type; the physical layer reports the management message to the link layer, and the link layer according to the control policy in the management message, Send data of at least one service type to the physical layer.

The control policy specifically includes: sending data in turn according to a method of equally allocating bandwidth, or sending data according to a priority manner.

A management system for controlling data transmission, the system comprising: a control unit, configured to transmit a management message for controlling data transmission between a link layer and a physical layer to control data transmission corresponding to the management message. The control mode of the control unit includes: the link layer is a master device and the physical layer is a master-slave control mode of the slave device; or the link layer and the physical layer are symmetric control modes of devices of the same level. .

The system further includes: an encapsulating unit, configured to encapsulate the management message into a management package, and encapsulate the data packet into a data packet;

And in the state that the management packet and the data packet are in the same packet header encapsulation format, the differentiated identifiers of the management packet and the data packet are encapsulated into a packet header encapsulation format; the distinguishing identifier includes: a bit bit identifier or a type domain identifier;

In the state that the management packet and the data packet adopt different header encapsulation formats, the type domain identifiers identifying different service types are encapsulated into the packet header encapsulation format of the data packet.

The present invention controls data transmission through management messages transmitted between the link layer and the physical layer, and the management message is a management message that controls data transmission.

The present invention adopts a management message for controlling data transmission to control data transmission corresponding to the management message. Therefore, the present invention can be used to customize different control modes for uplink/downlink data transmission, and the control manner is diversified. The technology adopts a single control mode of interrupted frames to be more flexible, thereby effectively managing bidirectional data transmission between the link layer and the physical layer; and realizing the flow control of the upstream traffic, so that the control mode is more comprehensive, and thus the chain The control and management of data transmission between the road layer and the physical layer is more abundant and comprehensive. DRAWINGS

1 is a schematic diagram of a packet header encapsulation format of an existing data packet;

2 is a schematic diagram showing an implementation flow of a master-slave control method according to the present invention;

3 is a schematic diagram of an implementation process of a symmetric control mode according to the present invention;

4 is a schematic diagram of another implementation flow of a symmetric control mode according to the present invention;

FIG. 5 is a schematic diagram of the same packet header encapsulation format of the data packet and the management packet according to the present invention; FIG. 6 is a schematic diagram of a packet header encapsulation format of the data packet when supporting multi-service data transmission according to the present invention. DETAILED DESCRIPTION OF THE INVENTION The basic idea of the present invention is to control the data transmission corresponding to the management message between the link layer and the physical layer by using a management message for controlling data transmission.

The implementation of the technical solution will be further described in detail below with reference to the accompanying drawings.

A management method for controlling data transmission, the method comprising: controlling data transmission by a management message transmitted between a link layer and a physical layer; the management message is a management message for controlling data transmission.

Here, for the management message for interactive transmission between the link layer and the physical layer, the control method for managing the message transmission includes two cases, and the following two cases are respectively explained.

The first case is: master-slave control mode. At this time, the link layer and the physical layer are mainly master and slave devices. When the link layer is the master device and the physical layer is the slave device, as shown in Figure 2, the master-slave The control method specifically includes the following steps:

Step 101: All the management messages are actively initiated by the link layer and sent to the physical layer.

Step 102: The physical layer responds to the received management message sent by the link layer.

It should be noted that the master-slave control mode is used for communication between the link layer and the physical layer. When the management message is exchanged, the link layer is the master device and the physical layer is the slave device. All interactions are performed by the link. The layer initiates, and the physical layer only responds to the management message delivered by the received link layer. For example, when the management message includes the management configuration information, such as configuring the maximum packet length, configuring the SID, and the like, the management message including the management configuration information is sent from the link layer; the physical layer receives the management message, and parses the management in the management message. After the configuration information is configured, the corresponding configuration is performed, and then the corresponding configuration result is returned to the link layer. When the link layer needs to obtain related management configuration information or alarms of the physical layer, the physical layer can act as a slave device and cannot initiate and deliver the information. The link layer needs to initiate the information to the physical layer. The request is then responded to by the physical layer, and the information is encapsulated into a management message and reported to the link layer. The second case is: Symmetrical control mode. At this time, the link layer and the physical layer are not the primary or secondary devices, and are all devices of the same level. As shown in FIG. 3, a symmetric control method specifically includes the following steps: Step 201: The link layer actively initiates a management message and sends the message to the physical layer.

Step 202: The physical layer responds to the received management message sent by the link layer.

As shown in FIG. 4, another symmetric control method specifically includes the following steps:

Step 301: The physical layer actively initiates a management message and reports it to the link layer.

Step 302: The link layer responds to the received management message reported by the physical layer.

It should be noted that the symmetrical control mode is used for communication between the link layer and the physical layer. When the management message is transmitted and exchanged, both the link layer and the physical layer can initiate the management message interaction. In addition to the link layer actively initiating the management message interaction and delivering the management message, the physical layer can also initiate the management message interaction and report the management message. The use of symmetric control is different from the master-slave control mode, which reduces the number of requests initiated by the link layer, thereby improving the management efficiency of control data transmission.

The management messages mentioned above are encapsulated by management packets. The data involved above is encapsulated by data packets, and the management packets and data packets are transmitted using the same physical link. Since the same physical link is used, it is necessary to distinguish between management packets and data packets sent at both ends of the serial bus; moreover, for the transmission of the management packet, it can be understood as a bearer management message, that is, bearer The management packet of information such as the management configuration of the physical layer and the link layer is transmitted on the in-band management channel, and shares the same serial data channel with the transmission of the data packet. Among them, the in-band management channel is a virtual channel, which can be understood as a logical channel carried on a serial data channel.

In order to identify the management packets and data packets transmitted on the same physical link, the encapsulation and differentiation of the management package and the data packet include two cases, which are respectively described below.

The first case: When the management packet and the data packet adopt the same packet header encapsulation format, after the link layer or the physical layer receives the management packet and the data packet, the management packet and the data packet are distinguished by the distinguishing identifier in the packet header encapsulation format. . The type of the distinguishing identifier includes: a bit identifier or a class Domain ID.

For the bit identifier, the bit identifier can be set by using one bit in the packet header encapsulation format. For example, when the bit is 1, the currently received packet is a management packet; when the bit is 0, , indicating that the currently received packet is a data packet. The header encapsulation format of the existing data packet can still be used, but modifying the fields in the packet header encapsulation format, the present invention uses a bit different from the existing data packet to identify whether the currently received packet is a management packet or a data packet. As an example, as shown in Fig. 5, in the control identifier (TCI) field, the sixth bit from SID0 is identified by a packet and marked with 0 as a management packet.

For a type field identifier, a type field identifier is used. For example, if the type field identifier is 1, the current received packet is a data packet. If the type field identifier is 2, the current received packet is a management package. The header encapsulation format of the existing data packet can still be used, but the field in the packet header encapsulation format is modified. The present invention modifies the length field in the packet header encapsulation format of the existing data packet, and adds a type field in the length field. And reduce the number of bits in the length field, and use the type field to identify whether the currently received packet is a management packet or a data packet. As an example, as shown in FIG. 5, the type fields added in the length field are T2, T1, and TO, respectively, and the identification manner is: You can use any one of T2, T1, and TO as the type field identifier. The way to identify whether the currently received packet is a management packet or a data packet. For example, when T2 is used as the type domain identifier, you can set the current received packet to be a data packet when the type domain identifier is 1, and the type domain identifier. When it is 2, it identifies the currently received package as a management pack. Another way of identifying is as follows: The combination of the field contents in T2, T1 and TO can be used as the type field identifier to identify whether the currently received packet is a management packet or a data packet, for example, in T2, T1 and TO. The combination of the contents of the field is: When the contents of the fields in T2, T1, and TO are all 0, the currently received packet is identified as a management pack.

It should be noted here that the management messages in the management pack are carried in the segment data field. The format of the management packet can be in the format of type, length, or value. If the receiving end determines that it is a management packet based on the sixth bit from SID0, it needs to determine the management packet according to the length of the management message. The length, and parse and respond to the management pack. Management packs and data use this same header encapsulation scheme, eliminating the need to make any changes to the header encapsulation format of existing packets.

The second case: when the management packet and the data packet adopt different packet encapsulation formats, the type domain identifiers that identify different service types are set in the packet header encapsulation format of the data packet, and the transmission and identification of multiple service types are supported; After receiving the data packet, the layer identifies the data of different service types by using the type field identifier in the packet header encapsulation format.

Here, the present invention is compared with the prior art, in the prior art, since the UTOPIA bus/POS-PHY bus can be used for both asynchronous digital subscriber line (ADSL) / asynchronous digital subscriber line 2 (ADLS2) / asynchronous digital User Line 2+ (ADSL2+) can be used for Very High Speed Digital Subscriber Line 2 (VDSL2). Among them, ADSL generally uses ATM to encapsulate data upper layer services; and VDSL2 can use ATM to encapsulate upper layer services or Ethernet. It can be seen that this UTOPIA bus/POS-PHY bus interface needs to be able to carry Ethernet packets as well as Ethernet packets. However, ITU-T standard G.int does not define the problem of how to carry data packets of multi-service type data, which causes the link layer to not recognize the currently received data packet bearer when processing the received data packet. Which type of business data is available. In summary, the problems of the prior art are: The transmission and identification of multi-service type data is not supported.

The present invention solves the problems existing in the prior art and supports transmission and identification of multi-service type data. In order to support the transmission and identification of multi-service type data, the data type is identified in the data packet header, and the type domain identifiers identifying different service types are set in the packet header encapsulation format of the data packet to support transmission and identification of multiple service types. For example, since the bearer part of the data packet includes ATM data and Ethernet data, in order to distinguish the two different service type data, a type field identifier field may be added to the data packet header to identify the two different service types. The data, and thus, the link layer can identify whether the currently received data packet carries ATM data or Ethernet data according to the type field identification field, and performs different processing. The following is an example of a packet header encapsulation format for a packet that supports transmission and identification of multi-service type data. Explain.

As shown in Figure 6, for the Type field, the 3-bit Type field is used to identify the type of payload. For example, you can use 010 to identify the payload as an Ethernet packet; use 100 to identify the payload as an ATM packet; use 001 to identify the payload as an Operation and Maintenance Management (OAM) message; and reserve 000 to the interrupt message for flow control. For the Type End (E) and Start (S) fields, the 2-bit Type E and S fields are used to identify the start and end of the Packet Transfer Mode (PTM) packet. For example, you can use 10 for the initial slice; 00 for the intermediate slice; 01 for the end slice; and 11 for the PTM packet without the slice. For the Priority Code Point (PCP) field, the 3-bit PCP field is reserved as the IEEE 802.1p PCP field for flow control. For the Virtual Circuit (VC) field, the 3-bit VC field is reserved to identify different service VCs from the user on each DSL subscriber line port in the ATM transport mode. For the 7-Band (BC, Bearer Channal) field, the 1-bit BC-field is reserved for identifying different BCs on the DSL subscriber line and is consistent with Gint. For the Priority (PR) field, the 1-bit PR field is reserved for different priorities on the BC used to identify the DSL subscriber line and is consistent with G.int. For the SID field, the 8-bit SID field is used to identify different subscriber line ports in different physical layers (PHYs). For the Length field, indicates the length of the payload, in bytes.

It should be noted that, when the data packet is encapsulated by the data packet, at least one data is encapsulated into the same data packet.

Here, the ATM data is taken as an example to compare the present invention with the prior art. In the prior art, for the data bearer of the ATM, the existing encapsulation mode only supports fragmentation or non-fragmentation, and the packet length of the ATM data. It is 53 bytes, and the data encapsulation is 4 bytes. It can be seen that there is redundancy in the existing encapsulation mode. The transmission of ATM data in the existing encapsulation mode will bring 7% overhead. If the current bandwidth is 1 Gbit, the bandwidth of the existing package will be removed due to the redundancy of the existing encapsulation mode. If the ATM itself is considered to be certain, The overhead, bandwidth utilization is even lower. In order to improve bandwidth utilization, the present invention adopts a packaging method for reducing data package redundancy, and can support ATM multi-cell encapsulation. Specifically, the encapsulation method of carrying multiple ATM data in one data packet, that is, the data encapsulation unit, can improve the bandwidth utilization of the ATM data transmission. For example, if the encapsulation mode supporting 4 data units is used, the encapsulation header is 4 bytes, and the data length of the ATM is 53 bytes, so that the bandwidth utilization can be increased from 92% to 98%.

It should be noted that, in the case of supporting the transmission of the multi-service type data, the foregoing management message of the present invention may include: management configuration information, alarm information, and the like, and may further include: a control strategy for transmitting data of at least one service type; The layer reports the management message to the link layer, and the link layer sends the data of the at least one service type to the physical layer according to the control policy in the management message.

The control policy specifically includes: sending data in turn according to a method of equally allocating bandwidth, or sending data based on a priority manner.

The following is an example of transmitting management messages between the link layer and the physical layer to support and control the transmission of multi-service type data, including the following:

The link layer generates a management message according to the requirements, for example, the management message is generated according to the data forwarding rules of the uplink users reported by the link layer, and the forwarding rule is carried in the management package and delivered by the inband management channel.

Here, the forwarding rules for uplink different user data include two methods. The first way is: Send data in turn based on the way the bandwidth is allocated. Specifically, each established DSL port uses equal round-trip transmission, for example, starting from the establishment of the link 1, if a packaged packet needs to be sent, a packet is sent, and if not, the next connection is sent. The encapsulated data packet of the DSL, and so on, until all the established DSL ports are sent. The second way is: Send data based on a priority. Specifically, the existing weighting algorithm can be used to send data of each DSL line to the serial port, for example, If a link has a large weight, it can preferentially send packets of this link.

2. The inband management channel of the bearer management packet is a virtual channel. The management packet and the data packet are carried on the same physical link. The management packet and the data packet use the same header encapsulation format, and the type domain identifier or bit is used to identify Whether the current package is a management pack or a data packet.

The physical layer responds to the management message sent by the link layer, including the status query, and may also generate related management messages to be reported to the link layer; the link layer processes the related management message sent from the physical layer, for example, according to The bandwidth utilization information is reported, and the physical layer generation mechanism is adjusted. In addition, it can also include packet related statistics, such as packet loss rate, number of packets that occur, and so on.

A management system for controlling data transmission, the system comprising: a control unit, configured to transmit a management message for controlling data transmission between a link layer and a physical layer to control data transmission corresponding to the management message.

Here, the control mode of the control unit includes: a link layer as a master device and a physical layer as a master and slave control mode of the slave device; or, both the link layer and the physical layer are symmetric control modes of the same level device.

Here, the system further includes: a packaging unit, configured to encapsulate the management message into the management package, and encapsulate the data packet into the data package.

The management packet and the data packet are encapsulated into a packet header encapsulation format in a state in which the management packet and the data packet are in the same packet header encapsulation format. The distinguishing identifier includes: a bit identifier or a type domain identifier.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim

A management method for controlling data transmission, the method comprising: controlling data transmission by a management message transmitted between a link layer and a physical layer; wherein the management message is to control management of the data transmission Message.

2. The method according to claim 1, wherein the control method for managing message transmission comprises: a master-slave control mode, or a symmetric control mode;

The master-slave control mode is: all the transmission of the management message is initiated by the link layer, and the management message is sent to the physical layer, and the physical layer responds only to the management message delivered by the link layer;

The method according to claim 1 or 2, wherein the management message is encapsulated by a management packet, and the data is encapsulated by using a data packet; the management packet and the data packet adopt the same physical chain. Road transmission; among them,

When the management packet and the data packet adopt the same packet header encapsulation format, after the link layer or the physical layer receives the management packet and the data packet, the management packet and the data packet are distinguished by the distinguishing identifier in the packet header encapsulation format; The type of the distinguishing identifier includes: a bit identifier or a type field identifier; when the management packet and the data packet adopt different header encapsulation formats, the type domain identifier that identifies different service types is set in the packet header encapsulation format of the data packet, and at least one is supported. The transmission and identification of the service type; after receiving the data packet, the link layer identifies the data of different service types by using the type domain identifier in the packet header encapsulation format.

4. The method according to claim 3, wherein when the data packet is encapsulated by the data packet, at least one data is encapsulated into a same data packet.

The method according to claim 3, wherein the management message includes: a control policy for transmitting data of at least one service type; the physical layer reporting the management message to the link layer, The link layer sends data of at least one service type to the physical layer according to the control policy in the management message.

The method according to claim 5, wherein the controlling the policy specifically comprises: transmitting data in turn according to a method of equally allocating bandwidth, or transmitting data based on a priority manner.

A management system for controlling data transmission, the system comprising: a control unit, configured to transmit a management message for controlling data transmission between a link layer and a physical layer, to control corresponding to the management message Data transfer.

The system according to claim 7, wherein the control mode of the control unit comprises: the link layer is a master device and the physical layer is a master-slave control mode of the slave device; or, a link Both the layer and the physical layer are symmetrically controlled by the same level of equipment.

The system according to claim 7 or 8, wherein the system further comprises: a packaging unit, configured to encapsulate the management message into a management package, and encapsulate the data packet into a data packet; The management packet and the data packet are encapsulated into a packet header encapsulation format by using the same packet header encapsulation format; the distinguishing identifier includes: a bit identifier or a type domain identifier;