KR20000059636A - The composition of service data units into protocol data units in datalink layer - Google Patents

Abstract

The present invention provides one service data unit (SDU) transmitted from a higher layer in a data link layer in an open system interface (OSI) protocol structure defined by the International Standard for Organization (ISO). The present invention relates to a method of configuring protocol data units (PDUs).

The proposed scheme for the protocol data unit proposed in the present invention is one-to-one, one-to-many, one-to-one and padding depending on the size of the service data unit transmitted from the upper layer and the size of the protocol data unit configured in the data link layer. It is divided into configuration method and one-to-many and padding configuration method. In addition, in order to support the schemes of the protocol data unit proposed in the present invention, parameters included in the PDU header of the protocol data unit are defined.

The proposed scheme can be applied to all cases that may occur according to the size of the service data unit transmitted from the upper layer and the size of the protocol data unit configured in the data link layer, and the protocol data configured in the data link layer. PDU Payload enables efficient transmission of upper layer data by minimizing resource waste, and by using headers of protocol data units appropriately proposed for each configuration method. Minimization of efficiency can be minimized.

Description

TECHNICAL COMPOSITION OF SERVICE DATA UNIT IN PROTOCOL DATA UNIT {THE COMPOSITION OF SERVICE DATA UNITS INTO PROTOCOL DATA UNITS IN DATALINK LAYER}

The present invention provides one service data unit (SDU) transmitted from a higher layer in the data link layer in an Open System Interface (OSI) protocol structure defined by the International Standard for Organization (ISO). The present invention relates to a method of configuring protocol data units (PDUs).

The proposed scheme for the protocol data unit proposed in the present invention is one-to-one, one-to-many, one-to-one and padding depending on the size of the service data unit transmitted from the upper layer and the size of the protocol data unit configured in the data link layer. It is divided into configuration method and one-to-many and padding configuration method. In order to support the configuration method of proposed protocol data unit, sequence number (SN), configuration included in PDU header of protocol data unit CP (Concatenation _Padding), number of service data units (CN: Concatenation Number), service data unit start position indication (CI: Concatenation Indicator), filling start position indication (PI: Padding Indicator) parameter Define them.

According to the present invention, the service data units transmitted from the higher layer are determined by the size of the service data unit transmitted from the upper layer in the data link layer and the size of the protocol data unit configured in the data link layer in the open system interface protocol structure. We propose schemes that consist of data units, and we propose header parameters of protocol data units that are required for each scheme.

The proposed scheme can be applied to all cases that may occur according to the size of the service data unit transmitted from the upper layer and the size of the protocol data unit configured in the data link layer, and the protocol data configured in the data link layer. PDU Payload enables efficient transmission of upper layer data by minimizing resource waste, and by using headers of protocol data units appropriately proposed for each configuration method. Minimization of efficiency can be minimized.

The present invention relates to a method of configuring service data units transmitted from an upper layer in one or more protocol data units at a data link layer in an open system interface protocol structure.

In general, the open-system interface protocol architecture is a network-independent session layer, presentation layer, application layer, and network-dependent transport layer to facilitate the design, implementation, analysis, testing, modification, modification, and supplementation of the protocol stack. It is divided into seven layers: network layer, data link layer, and physical layer order. In the data link layer, a data link layer service data unit configured of upper layer protocol data units is configured as a data link layer protocol data unit. The protocol data unit is composed of a payload portion in which actual data is transmitted and a header portion representing a data organization method in the payload. The size of the payload portion should be determined appropriately in consideration of the requirements of the services available in the protocol structure used and the efficient use of resources, and the header portion sufficiently represents the composition of the payload portion and overhead in terms of efficient use of resources. There is a need for a design that minimizes

Accordingly, the present invention proposes a payload configuration method of a protocol data unit from a service data unit that satisfies service requirements and enables efficient use of allocated resources in the datalink layer, and proposes header parameters that minimize overhead. A method of configuring a header is proposed for each method of configuring a payload.

FIG. 1 shows a case in which the size of one service data unit is exactly matched with the payload size of one protocol data unit (FIG. 1-1), and one service data unit is divided into a plurality of protocol data units. When the size of the divided service data unit exactly matches the payload size of the protocol data unit (Fig. 1-2), a one-to-one configuration scheme from the service data unit to the protocol data unit,

FIG. 2 shows the case where a plurality of service data units exactly match the payload size of one protocol data unit (FIG. 2-1), and the rest of the previously divided service data unit and the next plurality of service data units. In the case where the sum is exactly the same as the payload size of the protocol data unit (FIGURE 2-2), and in the case of the plurality of service data units and the next service data unit that occurs, the sum of only the first portion of the divided data is the protocol data unit. If the payload size is exactly matched (FIGURE 2-3), the remaining portion of the previously divided service data unit, the next plurality of service data units, and the next service data unit occurring next, only the first portion of the divided portion If the combined size exactly matches the payload size in the protocol data unit (Fig. 2-4), and the size of the sum of only the first part of the partition that is the same as the rest of the previously divided service data unit and the currently generated service data unit is exactly the same as the payload size of the protocol data unit (FIGURE 2-5). In a one-to-many configuration scheme from service data units to protocol data units,

FIG. 3 illustrates a case in which the size of one service data unit is smaller than the payload size of one protocol data unit to fill the remaining payload portion (FIG. 3-1), and one service data unit includes a plurality of protocol data. When divided into units, the size of the last portion of the divided service data unit is smaller than the payload size of the protocol data unit to fill the remaining payload portion (FIG. 3-2). One-to-one and padding schematics in data units,

4 shows a case in which the sum of the plurality of service data units is smaller than the payload size of one protocol data unit to fill the remaining payload portion (FIG. 4-1), and the rest of the previously divided service data units. One-to-many from the service data unit to the protocol data unit in the case where the size of the portion and the next plurality of service data units is smaller than the payload size of the protocol data unit to fill the remaining payload portion (FIG. 4-2), and Schematic of the filling scheme.

* Description of the symbols for the main parts of the drawings *

1: Upper Layer Protocol Data Unit (Upper Layer PDU)

2: Datalink Layer Service Data Unit (Datalink Layer SDU)

3: Datalink Layer Protocol Data Unit (Datalink Layer PDU)

4: PDU header of data link layer protocol data unit

5: Payload portion of the data link layer protocol data unit (PDU Payload)

6: Sequence number parameter (SN) of each divided data link layer service data unit

7: Protocol data unit configuration method display parameter (CP: Concatenation _Padding)

8: Segmented SDU of data link layer service data unit

9: in the case of one-to-many or one-to-many and padding configuration, the number of data link layer service data units composed of one data link layer protocol data unit (CN: Concatenation Number)

10: In the case of one-to-many or one-to-many and padding configuration method, a start position indication parameter (CI) for each of datalink layer service data units constituted by one datalink layer protocol data unit.

11: Indication of starting position of padding in data link layer protocol data unit in case of one-to-one padding or one-to-many and padding configuration (PI: Padding Indicator)

12: Padding

In order to solve the above problems, the present invention provides a one-to-one configuration method, one-to-many configuration method, one-to-one configuration method and a configuration method depending on the size of the service data unit transmitted from the upper layer and the protocol data unit configured in the data link layer. It is divided into one-to-many and padding configurations. In the case of one-to-one configuration, the payload part consists of one service data unit or divided service data unit, and the header part consists of sequence number (SN) and configuration method indication (CP) parameters. Is a combination of the remainder of the previous service data unit, a plurality of service data units, and a portion of the next service data unit, and the header portion includes a sequence number (SN), a configuration method indication (CP), and the number of service data units ( CN), service data unit start position indication (CI) parameters, and in case of one-to-one and padding configuration, it consists of one service data unit or divided service data unit and padding part, and the header part is sequence Consists of number (SN), configuration mark (CP), fill start position (PI) parameters, one-to-many and fill In the case of forming method, it consists of a combination of the rest of the previous service data unit and a plurality of service data units, and the header part includes a sequence number (SN), a configuration method indication (CP), a number of service data units (CN), and service data. It consists of the unit start position display (CI) and fill start position display (PI) parameters.

(Example)

Hereinafter, the configuration and embodiment of the present invention will be described in detail with reference to the drawings.

The datalink layer protocol data unit 3 proposed in the present invention is a header portion 4 of the datalink layer protocol data unit and a payload portion of the datalink layer protocol data unit as shown in FIGS. 1, 2, 3, and 4. It consists of (5).

The header portion 4 of the datalink layer protocol data unit proposed by the present invention is a sequence number (6), a configuration type indication (7), a number of service data units (9), a service data unit start position indication (10), and a fill. Insertion start position indication (11) In the order of the parameters, with the appropriate combination of the proposed parameters for each case according to the configuration of the payload portion 5 of the protocol data unit proposed in the present invention Figures 1, 2, 3 and It is configured as 4.

The sequence number (6) parameter is a number for a divided service data unit constituting part or all of the payload portion of the datalink layer protocol data unit. The receiving side can resynthesize the divided service data units in order by using the sequence number parameter of the header portion of the data link layer protocol data unit, and in case of an error, enables partial retransmission request of the service data unit.

Configuration method indication (7) The parameter has a size of 2 bits, and indicates the configuration method of the service data units included in the payload portion of the data link layer protocol data unit. Configuration method display Parameter value '00' indicates one-to-one configuration method, '01' indicates one-to-one and fill configuration method, '10' indicates one-to-many configuration method, and '11' Represent one-to-many and fill configurations, respectively.

The number of service data units 9 parameter indicates the number of service data units newly started in the payload portion of the datalink layer protocol data units in the one-to-many or one-to-many and padding scheme.

The service data unit start position indication 10 parameter indicates the start position of a service data unit that is newly started in the payload portion of the datalink layer protocol data unit in a one-to-many or one-to-many and padding configuration.

The Fill Start Position Indication (11) parameter indicates the start position of the fill portion in the payload portion of the datalink layer protocol data unit in one-to-one and fill or one-to-many and fill configurations. The payload portion of the protocol data unit after the location consists of all padding.

The sequence number and configuration method indication parameters are essential parameters included in the header part of the protocol data unit for all cases of the proposed configuration method. The number of service data units and the start position display parameter of the service data unit are used only when the values of the configuration method display parameters are '10' and '11', and the start position display parameter of the filling method is '01'. Optional parameter used only when and '11'. In addition, the service data unit start position indication parameter is successively repeated by the value of the number of service data units to indicate each start position for the plurality of service data units included in the payload portion of the protocol data unit.

The parameters proposed above are payloads of the data link protocol data unit proposed in the present invention for the case where the size of the data link protocol data units exchanged between the transmitting side and the receiving side is mutually known through proper signaling in advance. The minimum parameters required to configure On the other hand, when the size of the protocol data unit is not known between the sender and the receiver in advance, the present invention proposes a payload size parameter (PN: Payload Length) indicating the size of the payload portion of the protocol data unit. It must be included in each case where necessary. In addition, when providing the function of request mode (Ack Mode) and non-request (Unack Mode) according to the service provided from the upper layer in the data link layer, each method is represented. 1bit response method parameter (A / U: Ack / Unack) must be included. On the other hand, when the transmission and reception side knows in advance the response method used between the transmission and reception according to the service to be transmitted through appropriate signaling, the response method parameter is not included in the header portion of the protocol data unit. In addition, when a separate channel for transmitting control signaling generated in the datalink layer is not used, a header of 1-bit payload type indicator (PTI: Payload Type Indicator) is distinguished to distinguish control signaling and data transmitted through the same channel. It must be included at the beginning of the.

As shown in Fig. 1-1, one datalink layer service data unit 2 or a partitioned portion 8 of the datalink layer service data unit as shown in Figs. 1-2 has a payload of one protocol data unit. In the case of the portion 5, one-to-one configuration is applied as shown in FIG. In the case of one-to-one configuration, the header portion 4 of the protocol data unit is composed of the sequence number 6 and the configuration display 7 parameter. In the case of Figure 1 it can be seen that the one-to-one configuration method is applied to the payload portion 5 on the receiving side with the configuration method display 7 parameter value of '00'. In the case of Fig. 1-1, a sequence number (6) parameter value of a designated value is used to indicate that a part of the divided service data unit is not transmitted, and in the case of Figs. The sequence number (6) value for each service data unit is used in order from '0'.

When the plurality of data link layer service data units 2 are composed of payload portions 5 of one protocol data unit as shown in Fig. 2-1, the previous service divided as shown in Fig. 2-2. If the remainder of the data unit and the plurality of datalink layer service data units 2 are composed of the payload portion 5 of one protogol data unit, the plurality of datalink layer service data as shown in Figs. 2-3. When composed of the unit (2) and the payload portion (5) of one protocol data unit as a start part of the next service data unit, the remainder and many of the previous service data units divided as shown in Figs. 2-4. As a start of the next datalink layer service data unit (2) and the next service data unit, a payload of one protocol data unit And the payload portion 5 of one protocol data unit as the start portion of the current service data unit and the remainder of the previous service data unit divided as shown in FIGS. In case of construction, one-to-many configuration is applied as shown in FIG. In the case of the one-to-many configuration method, the header part of the protocol data unit (4) with the sequence number (6), the configuration method indication (7), the number of service data units (9), and the service data unit start position indication (10) parameters. This is made up. In the case of Fig. 2, it can be seen that the one-to-many configuration scheme is applied to the payload portion 5 at the receiving side with the configuration scheme display 7 parameter value of '10'. In the case of Fig. 2-1, the parameter number of the sequence number (6) of the designated value is used to indicate that a part of the divided service data unit is not transmitted. In the case of Fig. 2-2, the previous service data unit is divided. Using the sequence number (6) parameter value for the rest of the sequence, and in the case of Figures 2-3, the sequence number (6) parameter value of the specified value to indicate that the beginning portion of the next service data unit has been transmitted at the end of the payload. 2-4 and 2-5, a sequence for the remainder of the previous service data unit divided by a value indicating that the start portion of the next or current service data unit has been transmitted at the end of the payload. It is used in addition to the number (6) parameter. In the case of Fig. 2, each service data unit is reconstructed by the service data unit start position indication 10 parameter value and the sequence number (6) parameter value, which are successively indicated by the value of the number 9 parameter of the service data unit. can do.

As shown in FIG. 3-1, one datalink layer service data unit 2 and the filling portion 12 are composed of a payload portion 5 of one protocol data unit and a diagram in FIG. 3-2. As described above, when the last part and the fill part 12 of the divided service data unit are composed of the payload part 5 of one protocol data unit, one-to-one and filling configuration is applied as shown in FIG. In the case of the one-to-one and padding scheme, the header portion 4 of the protocol data unit is composed of the parameters of the sequence number 6, the plotting scheme 7 and the padding start position indicator 11. In the case of Fig. 3, it can be seen that the one-to-one and fill configuration scheme is applied to the payload portion 5 at the receiving side with the configuration method display 7 parameter value of '01'. In the case of Fig. 3-1, the parameter number of the sequence number (6) of the designated value is used to indicate that a part of the divided service data unit is not transmitted. In the case of Fig. 3-2, the previous service data unit is divided. Use the sequence number (6) parameter value for the rest of the. In the case of Fig. 3, the service data unit is reconstructed only by the payload portion by the value of the filling start position indication 11 parameter.

As shown in Fig. 4-1, a case where a plurality of data link layer service data units 2 and a filling portion 12 are composed of a payload portion 5 of one protocol data unit and a diagram in Fig. 4-2. As shown in FIG. 4, the remainder of the previous service data unit divided and the plurality of data link layer service data units 2 and the filling part 12 are composed of the payload part 5 of one protocol data unit. One-to-many and padding schemes are applied. In the case of one-to-many and fill configuration, the sequence number (6), the configuration method display (7), the number of service data units (9), the service data unit start position display (10), and the fill start position display (11) The parameters comprise the header part 4 of the protocol data unit. In the case of Fig. 4, it can be seen that the one-to-many and fill configuration scheme is applied to the payload portion 5 at the receiving side with the configuration method indication 7 parameter value of '11'. In the case of Fig. 4-1, the parameter number of the sequence number (6) of the designated value is used to indicate that a part of the divided service data unit is not transmitted. In the case of Fig. 4-2, the previous service data unit is divided. Use the sequence number (6) parameter value for the rest of the. In the case of Fig. 4, the service data unit start position indication 10 parameter value which is continuously displayed by the value of the payload portion as many as the filling start position indication 11 parameter value and the number of service data units 9 parameter is shown. And each service data unit can be reconstructed with the sequence number (6) parameter value.

The present invention relates to a method of configuring service data units transmitted from an upper layer in one or more protocol data units in a data link layer in an open system interface protocol structure. It can be applied irrespective of the size of the data unit to satisfy the service requirements at the data link layer and to efficiently use the allocated resources, and is essential and optional in the configuration of the header part used according to the proposed configuration. The overhead can be minimized by efficiently configuring the parameters.

Claims (3)

Regardless of the size of the service data unit and the size of the protocol data unit, the method of configuring the protocol data unit from the service data unit, One-to-one configuration method of constructing payload in one service data unit or divided service data unit, Construct payloads in multiple service data units, configure payloads in multiple service data units with the remainder of the previous split service data unit, or payloads as multiple service data units and start part of the next service data unit Configure the payload with the remainder of the previous split service data unit and multiple service data units and the beginning of the next service data unit, or start the remainder of the split previous service data unit and the current service data unit The one-to-many configuration of payloads, The one-to-one and padding configuration, in which the payload is composed of one service data unit or divided service data units and a filling part, One-to-many and fill configurations that consist of payloads with multiple service data units and fill parts, or with the remainder of previous split service data units and multiple service data units and fill parts. The method of claim 1, Sequence number and configuration method display parameters In the one-to-many configuration, the sequence number, configuration display, number of service data units and service data start position display parameters. In the one-to-one and padding configuration, the parameters for sequence number, configuration and display start position for filling, In the one-to-many and padding configuration, with parameters for sequence number, configuration, number of service data units, service data start position and fill start position display parameters, How to configure the header part appropriately for each configuration method The method of claim 2, In the case where the size of the protocol data unit is not known between the sender and the receiver in advance, a payload size parameter indicating the size of the payload portion of the protocol data unit is configured in the header, If the data link layer provides a function of requesting a response to reception of a protocol data unit and a method of not requesting a response, a response method parameter indicating each method is configured in the header. A method of configuring a payload classification parameter in a header to distinguish control signaling from data transmitted through the same channel when a separate channel for transmitting control signaling generated in the data link layer is not used.