KR101002908B1 - Generating method and apparatus of protocol data unit for supporting multiple service in wireless packet data communication system - Google Patents

Abstract

The present invention relates to a wireless packet data communication system, and more particularly, to a wireless packet data communication system in which a terminal can transmit two or more traffics to a base station through one reverse physical channel among a reverse packet data channel, a reverse basic channel, and a reverse dedicated control channel. A method for generating a protocol data unit using non-signaling traffic and / or signaling traffic for one of the reverse physical channels, the service identifier indicating a service type during service negotiation between the terminal and the base station. Determining a multiplexing option for defining a traffic format having a field, a length indicator field indicating whether a length field is present, a header including the length field indicating a length of traffic data, and a payload including the traffic data; Above determination Generating a protocol data unit by configuring reverse traffic to include the header and the payload according to a predetermined multiplexing option, and connecting at least one protocol data unit according to the type and data rate of the reverse physical channel Generating a frame; and transmitting the generated physical channel frame through the reverse physical channel.

MuxPDU Type 7, MULTIPLE SERVICE, SIGNALLING TRAFFIC, PRIMARY TRAFFIC, SECONDARY TRAFFIC.

Description

TECHNICAL METHODS AND APPARATUS OF PROTOCOL DATA UNIT FOR SUPPORTING MULTIPLE SERVICE IN WIRELESS PACKET DATA COMMUNICATION SYSTEM}

1 is a hierarchical configuration diagram according to an OSI reference model of a CDMA system applied to the present invention;

2 is a diagram schematically illustrating formats of multiplexing types used in a CDMA system;

3 illustrates in more detail the structure of a protocol data unit according to multiplexing type 5;

4 illustrates multiplexing schemes of packet multiplexing types 1 and 2;

5 is a diagram illustrating a protocol data unit of multiplex type 7 according to an embodiment of the present invention;

6 is a diagram illustrating setting of a service identifier of multiplex type 7 according to an embodiment of the present invention;

7 illustrates a physical channel frame configured using multiplexing type 7 according to an embodiment of the present invention;

8 illustrates a rule for setting multiplexing options for multiplexing type 7 according to an embodiment of the present invention;

9 illustrates in more detail the structure of a multiplexing option for multiplexing type 7 according to an embodiment of the present invention;

10 is a message flow diagram illustrating a procedure in which a terminal and a base station establish a call and negotiate a physical channel and multiplexing option according to an embodiment of the present invention;

11A illustrates a structure of mixed mode multiplexing type 1 according to another embodiment of the present invention;

Figure 11B illustrates a structure of mixed mode multiplexing type 2 in accordance with another embodiment of the present invention.

The present invention relates to a wireless packet data communication system, and more particularly, to a method and apparatus for generating a protocol data unit capable of supporting the transmission of signaling and control information for multiple services.

In general, the mobile communication system of the Code Division Multiple Access (CDMA) method has been developed from the second generation standard focused on voice, and the third generation CDMA standard capable of transmitting high speed data as well as voice ( Hereinafter referred to as CDMA 2000). Since the third generation CDMA mobile communication system can support transmission speeds up to 3 megabit per second (Mbps), more data than the second generation CDMA mobile communication systems supporting transmission speeds of 9.6 kbps or 14.4 kbps Can be transmitted. Therefore, various data such as high quality voice, moving picture, and internet search are available through this data transmission capability.

In the earlier developed CDMA 2000 mobile communication system (hereinafter referred to as CDMA 2000 1x system), the packet data is mainly transmitted through a supplemental channel (SCH). However, voice or signaling information requiring high reliability is specified to be transmitted only through a fundamental channel (FCH) or a dedicated control channel (DCCH). This is because the basic channel or the dedicated control channel is designed to have better quality than the additional channel.

More advanced third generation CDMA mobile communication system, especially in the CDMA 2000 1xEV-DV (EVolution in Data and Voice) system proposed for simultaneous support of voice service and high-speed packet data service, high speed and stable transmission of voice and packet data To use the Packet Data Channel (PDCH). The packet data channel has the same channel quality as the basic channel or the dedicated control channel. Therefore, the packet data channel has a high transmission probability such as call control and radio link protocol (RPL) control of the CDMA 2000 1xEV-DV system. Signaling information may be transmitted together with voice and packet data.

The media access control (MAC) layer of the CDMA 2000 1x and CDMA 2000 1xEV-DV systems uses a plurality of multiplexing types to support various types of physical channels. These multiplexing types make it possible to multiplex various services to create a Protocol Data Unit (PDU) for the multiplexing type.

In the conventional protocol data unit generation method, several possible multiplexing methods are specified, and information on the multiplexing method is recorded in the header of the protocol data unit. In particular, the protocol data unit used in the base channel was able to multiplex signaling traffic and non-signaling traffic (primary and secondary traffic) in only a few predefined formats by standard. In the conventional protocol unit generation method, up to three services of signaling traffic, primary traffic, and secondary traffic can be mixed and transmitted in one protocol data unit.

In recent years, as the needs of users are diversified, the provision of multiple services over the same connection has become an important issue. However, as mentioned above, since the generation method of the conventional protocol data unit specifies that only up to three types of services can be multiplexed, it cannot support more various types of services required by the user. In addition, since multiplexing is possible only in a predetermined format, there is a problem of inefficient efficiency in transmitting data having a variable length.

 Accordingly, the present invention, which was devised to solve the problems of the prior art operating as described above, provides a method and apparatus for generating a protocol data unit according to a multiplex packet multiplexing type having a variable length.

The present invention provides a method and apparatus for generating a protocol data unit having a length field in a header to support variable lengths.

The present invention provides a method and apparatus for generating a protocol data unit capable of multiplexing a plurality of different services, including a service identifier for service definition in a header.

The present invention provides a method and apparatus for formatting protocol data units for multiple services using multiplexing options.

According to an embodiment of the present invention, the present invention provides a wireless packet data communication system in which a terminal can transmit two or more traffic to a base station through one reverse physical channel of a reverse packet data channel, a reverse basic channel and a reverse dedicated control channel. A method for generating a protocol data unit using non-signaling traffic and / or signaling traffic for one of the reverse physical channels, the method comprising: a service identifier field indicating a service type during a service negotiation between the terminal and the base station; Determining a multiplexing option for defining a traffic format having a length indicator field indicating the presence or absence of a length field and a header including the length field indicating the length of the traffic data and a payload including the traffic data; According to the multiplexing option Generating a protocol data unit by configuring reverse traffic to include the header and the payload, and generating a physical channel frame by connecting at least one protocol data unit according to the type and data rate of the reverse physical channel; And transmitting the generated physical channel frame through the reverse physical channel.

In the following description of the present invention, detailed descriptions of well-known functions or configurations will be omitted if it is determined that the detailed description of the present invention may unnecessarily obscure the subject matter of the present invention. Terms to be described later are terms defined in consideration of functions in the present invention, and may be changed according to intentions or customs of users or operators. Therefore, the definition should be made based on the contents throughout the specification.

The present invention described below is to multiplex signaling and non-signaling traffic when three or more services are provided in a wireless packet data communication system. The protocol data unit according to the present invention adapts to various service situations by including a length field for supporting variable length and a service identifier field for service definition in a header.

In the following description, a 1xEV-DV (Evolution in data and voice) system, which is a synchronous CDMA 2000 communication scheme proposed in the 3rd Generation Partnership Project (3GPP2), will be used. However, the present invention can be applied to other mobile communication systems having a similar technical background and channel configuration with a slight modification without departing from the scope of the present invention. It will be possible in the judgment of those who have

1 illustrates a hierarchical configuration diagram according to an Open Systems Interconnection (OSI) reference model of a CDMA system according to the present invention. The CDMA 2000 system is referred to collectively as the CDMA 2000 1x system and the CDMA 2000 1xEV-DV system. The layer referred to below should be understood to mean software or hardware that performs the functions of the layer.

Referring to FIG. 1, the CDMA 2000 system includes an upper signaling layer 10, a data service layer 11, and a voice service layer 12 corresponding to OSI layers 3 to 7. In addition, the CDMA 2000 system includes a link access control (LAC) layer 13 corresponding to an OSI layer 2, a radio link protocol (hereinafter referred to as RLP) layer 14, and Media Access Control (hereinafter referred to as MAC) layer 14 and a Physical (PHY) layer 16 corresponding to the OSI 1 layer.

A conventional CDMA 2000 system hierarchically separates functions of a base station connected directly to a mobile terminal through a wireless channel and a base station controller connected to a network. That is, the base station performs the functions of the first layer, and the base station controller performs the functions of the second to seventh layers.

The upper signaling layer 10 processes signaling information for call control and physical layer interfaces, and the data service layer 11 and the voice service layer 12 process traffic for data service and voice service, respectively. .

The link access control layer 13 reports on the quality of the radio link and header related to authentication, sequencing, addressing, etc., to the signaling information generated by the higher signaling layer 10. Field and a length field are added to generate a control message. Thereafter, the link access control layer 13 segments the generated control message into a size that can be transmitted from the medium access control layer 15 and starts a message indicating the beginning or continuation of the message for each divided unit. Create a data unit by adding the Start Of Message (SOM) bit.
The radio link protocol layer 14 generates a data unit by dividing the data stream generated in the data service layer 11 into a size that can be transmitted in the physical layer and adding a sequence number for each divided unit. In addition, the radio link protocol layer 14 generates a data unit with control information for the data service in progress in the radio link protocol.

The data generated by the link access control layer 13 and the radio link protocol layer 14 will be collectively referred to as a service data unit (hereinafter referred to as a SDU). The service data unit is then divided into signaling traffic or non-signalling traffic according to its characteristics. The signaling traffic represents a signaling message of the link access control layer 13. The non-signaling traffic represents control data generated in the service data or the radio link protocol layer 14 and may be classified into primary traffic and secondary traffic according to the type of the service.

The media access control layer 15 adds a multiplex header according to the transmission type of the physical channel to the service data unit generated by the link access control layer 13 or the radio link protocol layer 14. The media access control layer 15 includes a multiplexing sub-layer for multiplexing signaling and traffic data, and the data unit including the multiplexing header is referred to as a multiplex sublayer protocol data unit (hereinafter referred to as MuxPDU). It will be called.).

The media access control layer 15 configures a physical channel frame with at least one protocol data unit according to the type and transmission rate of the physical channel to which it is currently connected, and transmits the physical channel frame to the physical layer 16. Then, the physical layer 16 transmits the physical channel frame transferred from the media access control layer 15 to the counterpart through encoding, modulation, and the like.

In addition, the physical layer 16 transmits at least one protocol data unit included in the physical channel frame received from the counterpart to the media access control layer 15. Then, the media access control layer 15 analyzes the multiplex header in the extracted at least one protocol data unit, extracts a service data unit, and delivers the service data unit to the corresponding layer.

The physical channels used for the packet data service in the physical layer 16 are summarized as follows.                     

A dedicated control channel (hereinafter referred to as DCCH) is dedicated to a specific mobile terminal to carry control information of layers 3 and 2.

The fundamental channel (hereinafter referred to as FCH) carries low-speed traffic data and control information like the basic channel of the existing IS-95.

The supplemental channel (hereinafter, referred to as SCH) mainly carries low-speed traffic data like the supplementary channel of the existing IS-95.

The Packet Data Channel (hereinafter referred to as PDCH) carries traffic data stably and at high speed.

The media access control layer of the CDMA 2000 system uses a plurality of multiplex types (MuxPDU Types) to support the various types of physical channels. Such multiplexing types (MuxPDU Types) will be described with reference to the accompanying drawings.
2 is a diagram schematically illustrating formats of multiplex types used in a CDMA system. Here, the maximum data rate (Rate 1) is 9600bps, 1/2 data rate (Rate 1/2) is 4800bps, 1/4 data rate (Rate 1/4) is 2400bps, and 1/8 data rate (Rate 1/8) is It was set to 1200bps. The rates determine the size of the physical channel frame.

Referring to FIG. 2, the multiplex type 1 (MuxPDU Type 1) transmits signaling information, primary traffic, and secondary traffic through a physical channel supporting a transmission rate of 1200 to 9600bps. Here, the multiplex type 2 (MuxPDU Type 2) supports a speed up to 14400bps for a similar purpose as the multiplex type 1. These multiplexing types 1 and 2 are used to transmit control information and traffic data in the basic channel and the dedicated control channel. Here, the primary traffic and the secondary traffic mean control information of the radio link protocol provided from the service data or the radio link protocol layer, and are distinguished from signaling information provided from the higher signaling layer for call control. Primary and secondary are classified according to service type of data or control information.

MuxPDU Type 3 is used to transmit traffic data from the radio link protocol layer through an additional channel at a transmission rate of 14400bps or less. MuxPDU Type 4 is used to send certain (relatively short) control messages over the base channel.

The payload size according to the multiplexing types 1, 2, 3, and 4 is fixedly determined according to the size of signaling information or control information of a radio link protocol. Etc.) can detect the size of the payload. On the other hand, in order to support variable data rates in the packet data channel proposed in the CDMA 2000 1xEV-DV system, multiplexing type 5 having fields for indicating the length of an included payload (MuxPDU Type) 5) Only support.

Finally, multiplexing type 5 is used to transmit traffic data provided from the radio link protocol layer through a packet data channel. This multiplexing type 5 protocol data unit has fields for indicating the length of the payload.

3 is a diagram showing in more detail the structure of a protocol data unit according to multiplexing type 5. FIG.
Referring to FIG. 3, the multiplexing type 5 protocol data unit includes a header of the multiplexing type 5 having a length of 6, 14 or 22 bits, an extension indicator having a 10 bit length, and a payload.

The header of the multiplex type 5 includes a 3-bit Service Identifier (SID) field, a 1-bit Extension Indicator field, a 2-bit Length Indicator field, and a length of 0, 8, or 16 bits. It consists of fields. The extension indication field indicates whether a subsequent extension header exists. The length indication field indicates whether a following length (LEN) field exists and its meaning. The length field is 8 bits or 16 bits and indicates the length of the payload in bytes. Accordingly, the length of the multiplex type 5 header is 6, 14 (when an 8-bit length field is included) or 22 bits (when a 16-bit length field is included).

When describing the meaning of the service identifier field, '000' represents signaling, '001' to '110' represents a corresponding service index, and '111' represents a null service. In this case, the service index is used to distinguish the types of services maintained through one call connection. When describing the meaning of the length indication field, '00' indicates that the length field is omitted, '01' means that the length field is 8 bits, '10' means that the length field is 16 bits, and '11' means payload. Means that it has a fixed length.

The length indication field indicates whether there is a following length (LEN) field and its meaning. The length field indicates the length of the payload in bytes. The extension header exists only when the value of the extension indication field is 1 and is used to extend the use of a protocol data unit according to multiplexing type 5.

When the value of the extension type field is '01', the extension header includes a 2-bit encapsulated MuxPDU type field, a 2-bit encapsulated MuxPDU Size field, and 4-bit encapsulation. It further includes a spare field. In this case, when the value of the extension type field is '01', the encapsulation type field, the encapsulation unit size field, and the preliminary field are called an encapsulation header.

The encapsulation type field indicates which multiplexing type of service unit the following payload contains. That is, '01' represents a multiplexing type 1, '10' represents a multiplexing type 2, 11 represents a multiplexing type 4, and '00' represents a preliminary value.

The encapsulation unit size field indicates the size of a service unit carried in a payload for a basic channel capable of supporting multiple transmission rates of maximum, 1/2, 1/4, and 1/8. In other words, '00' represents full rate, '01' represents half rate, '10' represents 1/4 rate, and 11 represents 1/8 rate. rate 1/8). For example, suppose that a multiplexing type 1 service unit is created to support a basic channel of up to 9.6kbps, the size of the service unit is 168 bits at the maximum transmission rate.                     

Multiplexing type 1, 2 or 4 is used when transmitting data on the base channel or on a dedicated control channel. The multiplexing type 4 is used to deliver a relatively small size of data through a basic channel or a dedicated control channel in a short time of 5 ms. The protocol data unit is composed of only one service data unit without considering multiplexing. Using packet multiplexing type 1 or 2, it is possible to multiplex signaling traffic and up to two non-signaling traffic (primary and secondary traffic) into one protocol data unit.

4 is a diagram illustrating multiplexing schemes of packet multiplexing types 1 and 2. FIG.

As shown in FIG. 4, the multiplexing type 1 designated as the multiplexing option '0x1' defines 12 multiplexing schemes. For example, when the maximum data rate is used, the header value '1101' means a combination of 40 bits of primary traffic and 128 bits of secondary traffic. Multiplex type 2, specified with the multiplex option '0x2', defines 25 multiplexing schemes. For example, when 1/2 rate is used, the header value '1100' means a combination of 20 bits of primary traffic and 101 bits of secondary traffic.

In this manner, different traffics are multiplexed according to a predetermined multiplexing rule and carried in one packet data unit, and information on the multiplexing rule used is recorded in the header of the corresponding protocol data unit. However, such a multiplexing method has a disadvantage in that the multiplexing method reduces the efficiency of the multiplexing due to a predetermined size of data, and in order to increase the maximum number of types of traffic that can be multiplexed, the header size must be increased by the number of possible combinations of the mixed methods.

The present invention uses a variable length multiplexing type 7, which can be used to efficiently multiplex service data units having various characteristics.

5 illustrates a protocol data unit of multiplex type 7 according to an embodiment of the present invention.

Referring to FIG. 5, a multiplexed packet according to multiplexing type 7 includes a header part and a payload part. The payload portion includes at least a portion of signaling traffic or non-signaling traffic. The header of the multiplexing type 7 includes an SR_ID field indicating a 3-bit service reference identifier, a 1-bit length indicator field indicating whether a length field exists, and a length field of 0 or 4 bits. It consists of.

Unlike the service identifier field of the multiplexing type 5, the service identifier field of the multiplex type 7 may distinguish signaling traffic and six different non-signaling traffic. The setting of the service identifier of the multiplex type 7 will be described with reference to FIG. 6.
6 is a diagram illustrating setting of a service identifier of multiplex type 7 according to an embodiment of the present invention.
As shown in FIG. 6, service identifier '000' represents signaling traffic, '001' to '110' represents six different non-signaling traffic, and '111' is full of multiplex type protocol data units. Represents a null service used to indicate a cold case. As mentioned above, '001' to '110' among the values of the service identifier field identify packet data services maintained through one call connection.

The length indicator field is a bit flag indicating whether the length field is present. The length field is included in the multiplex type 7 header only when the length indicator has a value of '1', and is a 0-bit or 4-bit field representing the size of the payload portion in octets. The length of the data portion is the length. 2 octets larger than the field. That is, the data size is finally determined by the length field + 2. Since the payload length is expressed in octets, if the 4-bit length field is used, 4 bits can be represented by 0 to 15. As described above, the data size is "length field + 2", so the maximum length is 17 bytes. You can specify a length of (15 + 2), which is 136 bits (17x8).
On the other hand, when the length indicator has a value of 0, the length field is omitted so that the length of the header becomes 4 bits, and the length of the payload is considered to occupy the remaining portion of the physical layer frame.

FIG. 7 illustrates a physical channel frame configured using multiplexing type 7 according to an embodiment of the present invention, and illustrates a physical channel frame configured by mixing non-signaling traffic and one signaling traffic of six different services. The length field is 4 bits in size, and the size of a packet data unit for a 20ms basic channel frame transmitted at 9.6kbps is 172 bits except for cyclic redundancy codes (CRCs) used for error correction.
As shown in FIG. 7, the 172-bit protocol data unit is configured by multiplexing six non-signaling traffics having SR_IDs '001' to '110' and one signaling traffic having SR_IDs '000'.

The multiplexing type used in the physical channel is specified by the multiplexing option information. The multiplexing option information exchanged by the terminal and the base station in the service setting process is a value that specifies the type of multiplexing to be used in the corresponding service, the size of the corresponding protocol data unit, and applied rate set information. As a result, the terminal and the base station exchange a predetermined multiplexing option when setting up a service to determine the type of multiplexing to use during communication.

When using multiplexing type 1 or 2, the terminal and the base station exchange the multiplexing option '0x01' (rate set 1) or the multiplexing option '0x02' (rate set 2) to set the multiplexing type to be used during communication. . The multiplexing type 7 according to the present invention preferably has a multiplexing option having a value greater than '0x10' so as not to overlap with the multiplexing option for other multiplexing types previously used. The configuration of the multiplexing option for the multiplexing type 8 will now be described with reference to the drawings.
8 is a diagram illustrating a rule for setting a multiplexing option larger than '0x10' according to an embodiment of the present invention.
Referring to FIG. 8, the case of "multiplexing type 7" is described from the most significant bit (MSB). The 3-bit format descriptor (Format_Descriptor) indicates the format of the multiplexing option. Only the value of 000 'is set. That is, only format 1 is used without setting a format so that it can be distinguished from other multiplexing options.
"MuxPDU_Type" sets the length to 3 bits to distinguish between the existing multiplex types 1 to 6 and the new multiplex type 7. Therefore, the value corresponding to the multiplex type 7 of the multiplex packet multiplex type (MuxPDU_Type) of 3 bits length is set to '100'.

delete

The next two bits of the data block size (Data_Block Size) are set to '11' which means a variable length because the multiplexing type 7 has a variable length. The maximum number of 6-bit data blocks (Max_Data Blocks) is '000000' indicating that there is no limit on the number of blocks, or '000001' to 8 blocks included in the protocol data unit. 001000 '. The least significant two bits represent the rate set. The options available for the rate combination 1 (9.6kbps Family) and the rate combination 2 (14.4kbps Family) are set to '01' and '10', respectively. 0x1301, 0x1302, 0x1305, and 0x1306. In this case, a total of four types of options can be generated, because a total of four types of options can be generated because there are two "rate combinations" and "maximum number of data blocks".

FIG. 9 illustrates the structure of the multiplexing option for the multiplexing type 7 according to an embodiment of the present invention in more detail. It is shown.
The dual multiplexing option 0x1301 is described in detail below.
"1301" is a hexadecimal number. If it is converted to binary number, it becomes "1001100000001", and if "000" is added to the beginning, it becomes "0001001100000001".
As shown in FIG. 9, a format description (Format_Descriptor) field set to "highest bit" 0001 ", a multiplexing type (MuxPDU_Type) field set to '00', and a variable data block size (Data_Block_Size) set to '11'. ) Field, a field indicating the maximum number of multiplexing protocol data units (MuxPDUs) in a physical service data unit (SDU) set to '000000', and a rate combination field set to '01'. In this case, the rate combination field of the multiplex option 0x1301 is set to '01' for a rate set 1 of the 9.6 Kbps family.

Hereinafter, a procedure for establishing a call and negotiating a physical channel and a multiplexing option will be described with reference to FIG. 10. Although the names and flows of the messages related to the configuration of the physical channel and the multiplexing option are shown in detail, this may vary depending on the system, system design, or operator's intention.

10 is a message flow diagram illustrating a procedure for establishing a call and negotiating a multiplexing option with a physical channel according to an embodiment of the present invention.
Referring to FIG. 10, when traffic to be transmitted to the user terminal arrives from the network to the base station in step (a), the base station delivers the call to the terminal through a general page message to establish a call for a packet data service. . Accordingly, in step (b), the terminal responds to the base station through the page response message whether the call acceptance and support channel information. Here, the terminal supports a packet data channel (PDCH) and a common power control channel (CPCCH) for the forward link (FL), and a base channel (FCH) for the reverse link (RL). Or it supports a dedicated control channel (DCCH).

Then, the base station receiving the response from the terminal in step (c) notifies the terminal of the allocation information of the forward and reverse channels through an Extended Channel Assignment Message (ECAM). In step (d), the terminal and the base station acquire the allocated channels.

In step (e), the terminal and the base station according to the service setting procedure, the service request message (Service Request Message), the service response message (Service Response Message), the service connection message (Service Connect Message), the service connection complete message (Service Connect Complete Message) ) To set the information on the service to be used. The terminal or the base station includes a service configuration record (SCR) that specifies the multiplexing option to be used in the service, the physical channel, the size of the physical channel frame, and radio configuration (RC) information to the messages exchanged in this process. Let's do it. The counterparty checks the contents of the service configuration record to determine if it is supported and sends a completion response if it is supported.

In step (f), the terminal and the base station establish a radio link protocol (RLP) and a point to point protocol (PPP) synchronization, and exchange user traffic according to the service configuration record set in step (e). .

In the above-described embodiment, the multiplexing option 7 is configured not to overlap with the multiplexing option for other multiplexing types. However, in another embodiment of the present invention, the multiplexing type 7 (along with the frame using the multiplexing types 1 and 2, which are the basic multiplexing options) Mux PDU Type 7) is configured in mixed mode. The structure of the mixed mode multiplexing type 7 will now be described with reference to the accompanying drawings.                     

FIG. 11A illustrates a structure of mixed mode multiplexing type 1 according to another embodiment of the present invention, and FIG. 11B illustrates a structure of mixed mode multiplexing type 2 according to another embodiment of the present invention.

The UE configures the multiplexing types 1 and 2 of the mixed mode by setting a newly defined multiplexing type 7 instead of the secondary traffic in the multiplexing types 1 and 2 including the signaling traffic, the primary traffic, and the secondary traffic.

As shown in FIG. 11A, mixed mode multiplexing type 1 defines twelve multiplexing schemes. Service types are divided into primary traffic, signaling traffic, and multiplex type 7. These three services are mixed and transmitted in one protocol data unit. The header value is classified into a mixed mode (MM), a traffic type (TT), and a traffic mode (TM). For example, if the mixed mode value is "1" and the traffic type value is "1" and the traffic mode value is "01" at the maximum transmission rate 9600, the primary traffic is set to 40 bits and the multiplexing type 7 is set to 128 bits. According to this configuration, the terminal combines the set traffic values and transmits them in one protocol data unit.

At the maximum data rate, the base channel (FCH) and dedicated control channel (DCCH) are used, and at 1/2 (4800 bps), 1/4 (2400/2700 bps), and 1/8 (1200/1500 bps) data rates, only the base channel (FCH) is used. The dedicated control channel (DCCH) is not used and only primary traffic is set to 80, 40, and 16 bits, respectively.

As shown in FIG. 11B, Mixed Mode Multiplexing Type 2 defines 17 multiplexing schemes. Like the mixed mode multiplexing type 1, service types are classified into primary traffic, signaling traffic, and multiplexing type 7, and header values are divided into mixed mode (MM) and frame mode (FM). For example, if the mixed mode (MM) value is "1" and the frame mode (FM) value is "0110" at the maximum data rate (14400bps), the primary traffic is set to 20 bits and the multiplexing type 7 is set to 242 bits. According to this configuration, the terminal combines the set traffic values and transmits them in one protocol data unit.

At the maximum baud rate, the base channel (FCH) and dedicated control channel (DCCH) are used. At 1/2 (7200 bps), 1/4 (3600 bps), and 1/8 (1800 bps), only the base channel (FCH) is used. The control channel (DCCH) is not used. For example, if the mixed mode value is "1" and the frame mode value is "001" at 1/2 transmission rate, the primary traffic is set to 20 bits and the signaling traffic is set to 101 bits. If the mixed mode (MM) value is "1" and the frame mode (FM) value is "00" at 1/4 data rate, the primary traffic is set to 20 bits and the signaling traffic is set to 32 bits. According to this configuration, the terminal combines the set traffic values into one protocol data unit and transmits them.

The procedure for establishing a call and negotiating a physical channel and a multiplexing option by the terminal and the base station by using the mixed mode multiplexing types 1 and 2 configured as described above is the same as the procedure of the embodiment of the present invention as described above, and thus a detailed description thereof is omitted. Let's do it. However, in order to use mixed mode multiplexing types 1 and 2, the base station and the terminal must agree on whether to use the mixed mode when setting up a service.

While the present invention has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the invention is not limited to the disclosed embodiments, but is capable of various modifications within the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims, but also by those equivalent to the scope of the claims.

In the present invention operating as described in detail above, the effects obtained by the representative ones of the disclosed inventions will be briefly described as follows.

The present invention can be easily adapted to various service environments by using a variable length multiplexing type capable of multiplexing up to seven different services in a CDMA 2000 mobile communication system.

Claims (13)

In a wireless packet data communication system in which a terminal can transmit two or more traffic to a base station through a reverse physical channel of one of a reverse packet data channel, a reverse basic channel, and a reverse dedicated control channel, a non-signal for one of the reverse physical channels. A method for generating a protocol data unit using at least one of signaling traffic and signaling traffic, the method comprising: During the service negotiation between the terminal and the base station, a header including the service identifier field indicating the service type, the length indicator field indicating the presence or absence of a length field, and the length field indicating the length of the traffic data, and the pay data including the traffic data. Determining the multiplexing option that defines the traffic format with load, Configuring reverse traffic to include the header and the payload according to the determined multiplexing option to generate a protocol data unit; Generating a physical channel frame by connecting at least one protocol data unit according to a type and a data rate of the reverse physical channel; Transmitting the generated physical channel frame on the reverse physical channel. delete The method of claim 1, wherein the generating of the physical channel frame comprises: Generating the physical channel frame such that a last protocol data unit does not include a length field. The method of claim 1, wherein the multiplexing option, And a 3-bit multiplex type format field identifying a plurality of multiplexing types, a 3-bit format descriptor field, a 2-bit data block size field, a 6-bit maximum data block field, and a 2-bit rate combination field. A method for generating a protocol data unit. In a wireless packet data communication system in which a terminal can transmit two or more traffic to a base station through a reverse physical channel of one of a reverse packet data channel, a reverse basic channel, and a reverse dedicated control channel, the non- An apparatus for generating a protocol data unit using at least one of signaling traffic and signaling traffic, the apparatus comprising: During the service negotiation between the terminal and the base station, a header including the service identifier field indicating the service type, the length indicator field indicating the presence or absence of a length field, and the length field indicating the length of the traffic data, and the pay data including the traffic data. A media access control layer for determining a multiplexing option defining a traffic format having a load, and configuring reverse traffic to include the header and the payload in accordance with the determined multiplexing option to generate a protocol data unit; And a physical layer that connects at least one protocol data unit according to the type and data rate of the reverse physical channel to generate a physical channel frame, and transmits the generated physical channel frame through the reverse physical channel. And an apparatus for generating a protocol data unit. The method of claim 5, wherein the physical layer, Generating the physical channel frame so as not to include a length field in a last protocol data unit. The method of claim 5, wherein the multiplexing option, And a 3-bit multiplex type format field identifying a plurality of multiplexing types, a 3-bit format descriptor field, a 2-bit data block size field, a 6-bit maximum data block field, and a 2-bit rate combination field. And an apparatus for generating a protocol data unit. In a wireless packet data communication system in which a terminal can transmit two or more traffic to a base station through a reverse physical channel of one of a reverse packet data channel, a reverse basic channel, and a reverse dedicated control channel, a non-signal for one of the reverse physical channels. A method for generating a protocol data unit using at least one of signaling traffic and signaling traffic, the method comprising: During the service negotiation between the terminal and the base station, a header including the service identifier field indicating the service type, the length indicator field indicating the presence or absence of a length field, and the length field indicating the length of the traffic data, and the pay data including the traffic data. Determining the multiplexing option that defines the traffic format with load, Generating a subprotocol data unit by configuring reverse traffic to include the header and the payload according to the determined multiplexing option; Defining a traffic format including a payload of the subprotocol data unit, a payload of different traffic, and a header providing information on the transmission method of the subprotocol data unit and the different traffic based on the multiplexing option; Determining multiplexing options for mixed-mode multiplexing types, And configuring reverse traffics to include a payload of the subprotocol data unit, a payload of different traffics, and the header according to the determined multiplexing option of the mixed mode multiplexing type to generate a multiplexing protocol data unit. Characterized by a method for generating a protocol data unit. The method of claim 8, Generating at least one physical channel frame by connecting at least one multiplexing protocol data unit according to the type and data rate of the reverse physical channel; And transmitting the generated physical channel frame over the reverse physical channel. The method of claim 9, wherein the generating of the physical channel frame comprises: Generating the physical channel frame such that a last protocol data unit does not include a length field. The method of claim 8, wherein the multiplexing option, And a 3-bit multiplex type format field, a 3-bit format descriptor field, a 2-bit data block size field, a 6-bit maximum data block field, and a 2-bit rate combination field to distinguish multiple multiplexing types. A method for generating a protocol data unit. 10. The method of claim 9, wherein the header of the mixed mode multiplexing type is: When the physical channel frame is transmitted through a physical channel supporting a data rate of up to 9600bps, protocol data, characterized in that it comprises a mixed mode field of 1 bit, a traffic type field of 1 bit, a traffic mode field of 2 bits Method for creating a unit. 10. The method of claim 9, wherein the header of the mixed mode multiplexing type is: And when the physical channel frame is transmitted through a physical channel supporting a transmission rate of up to 14400 bps, a mixed mode field of 1 bit and a frame mode field of 4 bits.

Images