WO2005006599A1 - Method and apparatus for generating packet data to support multiple services in a wireless packet data communication system - Google Patents
Method and apparatus for generating packet data to support multiple services in a wireless packet data communication system Download PDFInfo
- Publication number
- WO2005006599A1 WO2005006599A1 PCT/KR2004/001752 KR2004001752W WO2005006599A1 WO 2005006599 A1 WO2005006599 A1 WO 2005006599A1 KR 2004001752 W KR2004001752 W KR 2004001752W WO 2005006599 A1 WO2005006599 A1 WO 2005006599A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- traffic
- pdu
- reverse
- length
- header
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13098—Mobile subscriber
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13216—Code signals, frame structure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13294—CDMA, code division multiplexing, i.e. combinations of H04Q2213/13291 and/or H04Q2213/13292 with space division
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/16—Performing reselection for specific purposes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/04—Interfaces between hierarchically different network devices
- H04W92/10—Interfaces between hierarchically different network devices between terminal device and access point, i.e. wireless air interface
Definitions
- the present invention relates generally to a wireless packet data communication system, and in particular, to a packet data generating method and apparatus for supporting the transmission of signaling and control information for multiple services.
- CDMA Code Division Multiple Access
- 2G 2 nd generation
- 3G 3 rd generation CDMA standards
- the 3G CDMA mobile communication system supports data rates of up to 3Mbps (Mega bit per second).
- the 3G CDMA can transmit more data than the 2G CDMA mobile communication system that supports 9.6kbps or 14.4kbps. This data transmission capability enables the provisioning of multiple services including high-quality voice service, transmission of moving pictures, Internet browsing, etc.
- CDMA2000 mobile communication system CDMA2000 l system
- packet data is transmitted mainly on a supplemental channel (SCH)
- SCH supplemental channel
- voice or signaling information requiring high reliability is to be transmitted on a fundamental channel (FCH) or dedicated control channel (DCCH) because the FCH and DCCH are designed to have a better quality.
- FCH fundamental channel
- DCCH dedicated control channel
- CDMA2000 lxEV-DV Evolution-Data and Voice
- CDMA2000 lxEV-DV Evolution-Data and Voice
- the PDCH having a channel quality as good as the FCH or DCCH, can deliver information requiring a high transmission probability, for example, signaling information for call control and RLP (Radio Link Protocol) control in CDMA2000 lxEV-DV, along with voice and packet data.
- RLP Radio Link Protocol
- the MAC (Media Access Control) layer uses a plurality of MuxPDU (Multiplex sub-layer Protocol Data Unit) types to support a variety of physical channel types.
- MuxPDU Types allow MuxPDUs to be generated through the multiplexing of various services.
- Conventional PDU generation methods define some available multiplexing methods. Information about the multiplexing method used is written in the header of a PDU.
- signaling traffic and non-signaling traffic primary and secondary traffic
- the three services that is, the signaling traffic, the primary traffic and the secondary traffic, can be multiplexed in one PDU.
- the multiplexing is available only in the predefined methods, thereby decreasing efficiency in transmitting data of a variable length.
- An object of the present invention is to substantially solve at least the above problems and/or disadvantages and to provide at least the advantages below. Accordingly, an object of the present invention is to provide a method and apparatus for generating a PDU according to the MuxPDU Type supporting a variable length.
- Another object of the present invention is to provide a method and apparatus for generating a PDU having in its header a length field to support a variable length.
- a further object of the present invention is to provide a method and apparatus for generating a PDU, including in its header a service identifier for identifying a service, in which different types of service data can be multiplexed.
- Still another object of the present invention is to provide a method and apparatus for defining a MuxPDU type using a multiplex option to provide multiple services.
- the above objects are achieved by providing a method and apparatus for supporting multiple services in a wireless packet data communication system where an MS (mobile station) transmits two or more traffic types to a BS (base station) on one of a reverse PDCH, a reverse FCH, and a reverse DCCH.
- an MS mobile station
- BS base station
- a reverse PDCH reverse PDCH
- a reverse FCH reverse FCH
- a reverse DCCH reverse DCCH
- the multiplex option defines a traffic format having a header and a payload including traffic data, and the header includes a service reference identifier field, a length indicator field indicating the presence or absence of a length field, and the length field indicating the length of the traffic data.
- a PDU is generated by formatting a reverse traffic to have a header and a payload according to the determined multiplex option.
- FIG. 1 illustrates a layered protocol architecture in an OSI (Open System Interconnection) reference model of a CDMA system to which the present invention is applied;
- FIG. 2 illustrates the formats of MuxPDU Types in a typical CDMA system;
- FIG. 3 illustrates in detail the format of a typical PDU of MuxPDU Type 5;
- FIG. 4 illustrates multiplexing methods for MuxPDU Type 1 and MuxPDU Type 2;
- FIG. 5 illustrates the format of a PDU of MuxPDU Type 7 according to an embodiment of the present invention;
- FIG. 1 illustrates a layered protocol architecture in an OSI (Open System Interconnection) reference model of a CDMA system to which the present invention is applied
- FIG. 2 illustrates the formats of MuxPDU Types in a typical CDMA system
- FIG. 3 illustrates in detail the format of a typical PDU of MuxPDU Type 5
- FIG. 4 illustrates multiplexing methods for MuxPDU Type 1 and MuxPDU Type 2
- FIG. 6 illustrates values of SRJD in the PDU of MuxPDU Type 7 according to the embodiment of the present invention
- FIG. 7 illustrates the format of an exemplary physical channel frame of MuxPDU Type 7 according to the embodiment of the present invention
- FIG. 8 illustrates a rule by which a multiplex option is set for MuxPDU Type 7 according to the embodiment of the present invention
- FIG. 9 illustrates in detail the structures of multiplex options for MuxPDU Type 7 according to the embodiment of the present invention
- FIG. 10 is a diagram illustrating a signal flow for setting up a call and negotiating a physical channel and a multiplex option between a mobile station (MS) and a base station (BS) according to the embodiment of the present invention
- FIG. 11 A illustrates the format of mixed-mode MuxPDU Type 1 according to another embodiment of the present invention
- FIG. 11B illustrates the format of mixed-mode MuxPDU Type 2 according to the second embodiment of the present invention.
- the header of a PDU includes a length field for supporting a variable length and a service ID field for identifying a service, to thereby adapt to various service situations.
- CDMA2000 system particularly a CDMA2000 lxEV-DV system proposed by 3GPP2 (3 rd Generation Partnership Project 2).
- 3GPP2 3 rd Generation Partnership Project 2
- the present invention is applicable to any other mobile communication system based on similar technology and channel structure.
- FIG. 1 illustrates a layered protocol architecture in an OSI reference model of a CDMA2000 system to which the present invention is applied.
- the CDMA2000 system is used to refer to both the CDMA2000 lx system and the CDMA2000 lxEV-DV system.
- the term "layer” used herein refers to software or hardware responsible for performing the functions of a corresponding layer.
- the CDMA2000 system is composed of an upper signaling layer 10, a data service layer 11, and a voice service layer 12, which correspond to the OSI layer 3 to layer 7.
- the CDMA2000 system further includes an LAC (Link Access Control) layer 13, an RLP layer 14, and a MAC layer 15 in OSI layer 2, and a PHY (PHYsical) layer 16 in OSI layer 1.
- the CDMA2000 system separates by layers the functionalities of aBS wirelessly connected directly to an MS from those of a base station controller (BSC). That is, the BS takes charge of the functionalities of layer 1, and the BSC takes charge of the functionalities of layer 2 to layer 7.
- BSC base station controller
- the upper signaling layer 10 processes signaling information for call control and PHY layer interfacing.
- the data service layer 11 and the voice service layer 12 process data traffic and voice traffic, respectively.
- the LAC layer 13 creates a control message by attaching a header related to authentication, sequencing, and addressing, a report field related to radio link quality, and a length field to signaling information generated from the upper layer signaling layer 10.
- the LAC layer 13 then segments to a transmittable size for the MAC layer 15 the control message and adds a start of message (SOM) bit indicating the start or continuation of a message to each segment, thereby producing a data unit.
- SOM start of message
- the RLP layer 14 creates a data unit by segmenting to a transmittable size for the
- PHY layer 16 a data stream generated from the data service layer 11 and numbering the segments with sequence numbers. Also, the RLP layer 14 generates a data unit out of control information about a data service in progress in RLP. The data units generated by both the LAC layer 13 and the RLP layer 14 are called
- SDUs Service Datagram Units
- An SDU is classified into signaling traffic or non-signaling traffic according to its characteristics.
- the non-signaling traffic is service data or control information from the RLP layer 14.
- the non-signaling traffic is further divided into primary traffic and secondary traffic according to its service type.
- the MAC layer 15 adds a multiplexing header to an SDU received from the LAC layer 13 or the RLP layer 14 according to the type of a physical channel.
- the MAC layer 15 has a multiplex sub-layer for multiplexing signaling data and traffic data.
- a data unit with a multiplexing header is called a MuxPDU.
- the MAC layer 15 constructs a physical channel frame with one or more MuxPDUs according to the type and data rate of a currently connected physical channel and transmits it to the PHY layer 16.
- the PHY layer 16 processes the physical channel frame by coding, modulation, etc., and transmits the processed frame to another party.
- the PHY layer 16 also transmits to the MAC layer 15 at least one PDU included in a physical channel frame received from another party.
- the MAC layer 15 then extracts an SDU from the at least one PDU by analyzing the header of the PDU and transmits the SDU to a corresponding layer.
- Physical channels used for a packet data service in the PHY layer 16 are as follows.
- FCH delivers low-rate traffic data and control information like an existing FCH ofIS-95
- SCH delivers mainly low-rate traffic data like an existing SCH of IS-95
- PDCH stably delivers traffic data at high rate.
- the MAC layer 15 uses a plurality of MuxPDU Types to support the above different physical channels.
- the MuxPDU Types will be described with reference to FIG.
- FIG. 2 illustrates the formats of MuxPDU Types in a CDMA system.
- a full rate (rate 1) is 9600bps, rate 1/2 is 4800bps, rate 1/4 is 2400bps, and rate 1/8 is 1200bps.
- the data rates determine physical channel frame sizes.
- MuxPDU Type 1 transmits signaling information, primary traffic and secondary traffic on a physical channel that supports 1200 to 9600bps.
- MuxPDU Type 2 supports data rates up to 14400bps for similar usages to MuxPDU Type 1.
- Both MuxPDU Type 1 and MuxPDU Type 2 are used to transmit control information and traffic data on the FCH and the DCCH.
- the primary traffic and secondary traffic are service data, or RLP control information from the RLP layer, discriminated from signaling information for call control from the upper signaling layer.
- the primary and secondary traffic are separated according to the service type of data or control information.
- MuxPDU Type 3 transmits traffic data from the RLP layer on the SCH at or below 14400bps.
- MuxPDU Type 4 transmits particular (relatively short) control messages on the FCH.
- the size of the payload in a MuxPDU Type 1, 2, 3, and 4 is fixedly determined according to the size of the signaling information or the RLP control information.
- a receiver can detect the payload size from a received PDU, especially its header.
- the PDCH proposed for the CDMA2000 lxEN-DV system supports only the MuxPDU Type 5 having a field indicating a payload length in order to support a variable data rate.
- MuxPDU Type 5 is used to transmit traffic data from the RLP layer on the PDCH.
- a PDU of the MuxPDU Type 5 includes a field indicating a payload length.
- FIG. 3 illustrates the structure of a PDU of MuxPDU Type 5 in detail.
- the PDU of MuxPDU Type 5 comprises a Header having a length of 6, 14 or 22 bits, a 0- or 10-bit Extension Header, and a Payload.
- the Header includes 3-bit SR_ID (Service Reference Identifier), 1-bit Extension
- the Extension Indicator indicates the presence or absence of the following Extension Header.
- the Length Indicator indicates the presence or absence of the following LE ⁇ and describes the LE ⁇ if the LE ⁇ exists.
- the LE ⁇ is 8 or 16 bits, representing the length of the Payload in bytes.
- the length of the Header of the MuxPDU Type 5 is 6, 14 (8-bit
- a service index identifies the type of a service maintained through a single call connection.
- Length Indicator is "00" it implies the absence of the LE ⁇ . If it is "01”, the LE ⁇ is 8 bits, if it is 10, the LE ⁇ is 16 bits, and if it is "11", the Payload has a fixed length.
- the Length Indicator indicates whether or not the following LE ⁇ exists and, if the LE ⁇ exists, describes the LE ⁇ .
- the LE ⁇ provides the length of the Payload in bytes.
- the Extension Header exists only when the Extension Indicator is 1.
- the extension header is used to expand the usage of the PDU of the MuxPDU Type 5.
- Extension Header If the Extension Header is "01", it includes a 2-bit Encapsulation MuxPDU Type, 2-bit Encapsulated MuxPDU Size, and a 4-bit Reserved for byte arrangement.
- Encapsulation MuxPDU Type Encapsulated MuxPDU Size, and Reserved are collectively called the Encapsulation Header.
- the Encapsulation MuxPDU Type indicates the MuxPDU Type of the following Payload. As for the meaning of the Encapsulation MuxPDU Type, "01" indicates
- MuxPDU Type 1 "10” indicates MuxPDU Type 2
- MuxPDU Type 4 "11" indicates MuxPDU Type 4
- "00" is a reserved value.
- the Encapsulated MuxPDU Size indicates the size of a service unit in the Payload for the FCH supporting the full rate, rate 1/2, rate 1/4 and rate 1/8. That is, "00" indicates the full rate, "01” indicates rate 1/2, JO" indicates rate 1/4, and "11" indicates rate 1/8.
- the size of the service unit is 168 bits. If the data is transmitted on the FCH or the DCCH, the MuxPDU Type 1, 2 or 4 is used.
- the MuxPDU Type 4 delivers relatively short data on the FCH or DCCH for a short time of 5ms.
- a PDU is formed with only one SDU, without multiplexing.
- the MuxPDU Type 1 and the MuxPDU Type 2 allow for signaling traffic and up to two non-signaling traffic (primary and secondary traffic) to be multiplexed in one PDU.
- FIG. 4 illustrates multiplexing methods for the MuxPDU Type 1 and the MuxPDU Type 2.
- the MuxPDU Type 1 with a multiplex option set to "0x1”, defines 12 multiplexing methods.
- a header "H01" indicates a combination of 40-bit primary traffic and 128-bit secondary traffic.
- a header "1100" indicates a combination of 20-bit primary traffic and 101-bit secondary traffic.
- this multiplexing method decreases multiplexing efficiency.
- the size of the header is increased as much as the number of available combinations of the traffic types.
- the present invention adopts the MuxPDU Type 7 supporting a variable length to efficiently multiplex the SDUs having diverse characteristics.
- FIG. 5 illustrates the structure of a PDU of the MuxPDU Type 7 according to an embodiment of the present invention.
- the PDU of the MuxPDU Type 7 is composed of a Header and a Payload.
- the Payload includes at least part of the signaling traffic or the non-signaling traffic.
- the MuxPDU Type 7 Header includes a 3-bit SR_ID (Service Reference Identifier), a 1-bit Length Indicator indicating the presence or absence of Length, and a 0- or 4-bit Length.
- the SRJQD of the MuxPDU Type 7 discriminates the signaling traffic and six different non-signaling traffic, compared to the SR_ TD of the MuxPDU Type 5. The values of the SRJQD of the MuxPDU Type 7 will be described below with reference to FIG. 6. Referring to FIG.
- the SR_ID identifies signaling traffic by "000” and six different non-signaling traffics by "001" to "HO". If the SR ID is "111", it indicates a null service, implying that the MuxPDU is full. As described above, "001" to "HO" of the SR_ID identify packet data services maintained through a single call connection.
- the Length Indicator is a 1-bit flag indicating whether the Length field follows.
- the Length is included in the MuxPDU Type 7 Header.
- the header is a 0- or 4-bit field representing the size in octets of the Payload.
- the length of the Payload is 2 octets greater than the value of the Length.
- FIG. 7 illustrates the format of an exemplary MuxPDU Type 7 physical channel frame with six non-signaling traffic and one signaling traffic according to the embodiment of the present invention.
- the Length is 4 bits and the size of a PDU for a 20-ms FCH frame at 9.6kbps is 172 bits except a CRC (Cyclic Redundancy Code) for error correction.
- CRC Cyclic Redundancy Code
- the 172-bit PDU has six non-signaling traffic and one signaling traffic multiplexed therein.
- the six non-signaling traffic have SR_ID set to "001" to "HO", respectively, and the non-signaling traffic has SR_ID set to "000".
- a MuxPDU Type for a physical channel is set according to the multiplex option information exchanged between an MS and a BS during a service setup.
- the multiplex option information is a value that indicates a set (rate set) of a MuxPDU type, the PDU sizes, and the data rates for a corresponding service.
- the MS and the BS exchange information about a preset multiplex option, to thereby determine a MuxPDU Type for use during the communications.
- the MS and the BS exchange a multiplex option of "0x01" (rate set 1) or a multiplex option of "0x02" (rate set 2). It is preferable to set a multiplex option greater than "0x10" for the MuxPDU Type 7 of the present invention in order to avoid confusion between the MuxPDU Type 7 and existing other MuxPDU Types. Formation of the multiple option for MuxPDU Type 7 will be described below with reference to FIGs. 8 and 9.
- FIG. 8 illustrates a rule by which a multiplex option greater than "0x10" is set according to the embodiment of the present invention.
- a 3-bit Format_Descriptor describes the format of the multiplex option. It is set to only "000” indicating Format 1. That is, without additionally setting a particular format that discriminates this multiplex option from other multiplex options, only Format 1 is used.
- the MuxPDU_Type is 3 bits long to identify the MuxPDU Type 7 from the MuxPDU Type 1 to the MuxPDU Type 6. Therefore, the 3-bit MuxPDUJType is set to "100" indicating the MuxPDU Type 7.
- the following 2-bit field, Data_Block_Size is set to "11" indicating a variable length because the MuxPDU Type 7 has a variable length.
- the 6-bit Max_Data_Blocks is set to "000000” indicating no limit in the number of blocks, or one of "000001" to "001000". "000001” means that only one block is included in the PDU and "001000” means that eight blocks are included in the PDU.
- the two least significant bits (LSBs: Rate Set) indicate a rate set. It is set to "01" for rate set 1 (9.6kbps family) and "10" for rate set 2 (14.4kbps family). Hence, final available multiplex options are 0x1301, 0x1302, 0x1305, and 0x1306. Since two values are variable as Rate_Set and Max_Data_Blocks each, a total of four multiplex options become available.
- FIG. 9 illustrates in detail the structures of the multiplex options 0x1301 and
- 0x1302 from among the final available multiplex options, 0x1301, 0x1302, 0x1305, and 0x1306.
- the multiplex option 0x1301 is composed of a Format_Descriptor set to "000" as the MSBs, a MuxPDU_Type set to "100”, a Data_Block_Size set to "11”, a Max_Data_Blocks set to "000000” indicating the maximum number of MuxPDUs in a physical SDU, and a Rate_Set set to "01".
- the multiplex option 0x1301 has Rate_Set set to "01” indicating rate set 1 (9.6kbps family).
- step (a) upon arrival of traffic destined for the MS from a network to the BS, the BS transmits a General Page Message to the MS to establish a call for a packet data service in step (a).
- step (b) the MS tells the BS if it accepts the call and which channel it supports by a Page Response Message.
- the MS supports the PDCH and a common power control channel (CPCCH) on a forward link (FL) and the FCH or DCCH on a reverse link (RL).
- CPCCH common power control channel
- step (c) the transmits to the MS FL and RL channel assignment information by an Extended Channel Assignment Message (ECAM).
- the MS and the BS acquire the assigned channels in step (d).
- step (e) the MS and the BS set information about a service to be provided by exchanging a Service Request Message, a Service Comiect Message, and a Service Connect Complete Message, h the above messages, the MS or the BS sets a service configuration record (SCR) that provides a multiplex option, a physical channel, the size of a physical channel frame, and the radio configuration (RC) information required for the provisioning of the service.
- SCR service configuration record
- the BS or MS determines if the service can be supported as configured in the SCR, by analyzing the SCR and, if it can be supported, transmits the Service Connect Complete Message to the MS or BS.
- the MS and the BS establish RLP and PPP (Point-to-Point Protocol) synchronization and exchanges user traffic according to the SCR in step (f).
- RLP and PPP Point-to-Point Protocol
- MuxPDU Type 7 While the multiplex option of the MuxPDU Type 7 is so configured as not to be identical to other MuxPDU Types in the above embodiment, it is further contemplated as another embodiment that a mixed-mode MuxPDU Types are created by mixing the basic multiplex options, the MuxPDU Type 1 and the MuxPDU Type 2, with the MuxPDU Type 7.
- the mixed-mode MuxPDU Types will be described with reference to FIGs. 11 A and 11B.
- FIG. HA illustrates the format of mixed-mode the MuxPDU Type 1 according to another embodiment of the present invention
- FIG. 11B illustrates the format of the mixed-mode MuxPDU Type 2 according to the second embodiment of the present invention.
- the mixed-mode MuxPDU Type 1 defines 12 multiplexing methods. Three service types are available: primary traffic, signaling traffic, and the MuxPDU Type 7. These three services are transmitted in one PDU.
- a Header of the mixed-mode MuxPDU Type 1 includes a Mixed Mode (MM), a Traffic Type (TT), and a Traffic Mode (TM). For example, if MM is "1", TT is "1", and TM is "01" for the full rate
- the primary traffic is 40 bits and the MuxPDU Type 7 is 128 bits. According to this setting, the MS combines the traffic in one PDU for transmission.
- the FCH and the DCCH are used.
- rate 1/2 (4800bps), rate 1/4 (2400/2700bps), and rate 1/8 (1200/1500bps)
- only the FCH is used without the DCCH and only 80-, 40- and 16-bit primary traffic are available, respectively.
- the mixed-mode MuxPDU Type 2 defines 17 multiplexing methods.
- Three service types are available: primary traffic, signaling traffic, and the MuxPDU Type 7 like mixed-mode MuxPDU Type 1.
- MuxPDU Type 2 includes an MM and a Frame Mode (FM). For example, if the MM is “1" and the FM is "0110" for the fall rate (14400bps), primary traffic is 20 bits and the MuxPDU Type 7 is 242 bits. According to this setting, the MS combines the traffics in one PDU for transmission.
- FM Frame Mode
- the FCH and the DCCH are used.
- rate 1/2 (7200bps), rate 1/4 (3600/2700bps), and rate 1/8 (1800bps) only the FCH is used without the DCCH.
- the primary traffic is 20 bits and the signaling traffic is 101 bits.
- the MM is "1" and the FM is "00" for rate 1/4 (3600bps) the primary traffic is 20 bits and the signaling traffic is 32 bits. According to this setting, the
- MS combines the traffics in one PDU for transmission.
- the MS and the BS establish a call and negotiate a physical channel and a multiplex option using the mixed-mode MuxPDU Type 1 and the mixed-mode MuxPDU Type 2 in the same manner as described with reference to FIG. 10.
- One thing to note in relation to the mixed-mode MuxPDU Type 1 and the mixed-mode MuxPDU Type 2 is that the MS and the BS must agree on the mixed-mode MuxPDU Type 1 and the mixed-mode MuxPDU Type 2 at a service setup to use the mixed-mode MuxPDU Type 1 and the mixed-mode MuxPDU Type 2.
- the major effect of the present invention as described above is that the use of a MuxPDU Type of a variable length, allowing up to seven different services to be multiplexed, easily adapts to various service situations.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2004300830A AU2004300830B2 (en) | 2003-07-14 | 2004-07-14 | Method and apparatus for generating packet data to support multiple services in a wireless packet data communication system |
JP2006520119A JP4295320B2 (en) | 2003-07-14 | 2004-07-14 | Method and apparatus for generating protocol data for supporting multiple services in a wireless packet data communication system |
CN2004800168948A CN1806401B (en) | 2003-07-14 | 2004-07-14 | Method and apparatus for generating packet data to support multiple services in a wireless packet data communication system |
CA 2529171 CA2529171C (en) | 2003-07-14 | 2004-07-14 | Method and apparatus for generating packet data to support multiple services in a wireless packet data communication system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR20030048097 | 2003-07-14 | ||
KR10-2003-0048097 | 2003-07-14 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2005006599A1 true WO2005006599A1 (en) | 2005-01-20 |
Family
ID=36712781
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2004/001752 WO2005006599A1 (en) | 2003-07-14 | 2004-07-14 | Method and apparatus for generating packet data to support multiple services in a wireless packet data communication system |
Country Status (6)
Country | Link |
---|---|
JP (1) | JP4295320B2 (en) |
CN (1) | CN1806401B (en) |
AU (1) | AU2004300830B2 (en) |
CA (1) | CA2529171C (en) |
RU (1) | RU2319320C2 (en) |
WO (1) | WO2005006599A1 (en) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1804530A1 (en) * | 2004-10-13 | 2007-07-04 | Huawei Technologies Co., Ltd. | Method for transmitting data in digital cluster system |
WO2008049472A1 (en) * | 2006-10-27 | 2008-05-02 | Telefonaktiebolaget Lm Ericsson (Publ) | Length indicator optimization |
WO2008081882A1 (en) | 2006-12-28 | 2008-07-10 | Ntt Docomo, Inc. | Transmitter, receiver, mobile station and wireless base station |
WO2008081881A1 (en) * | 2006-12-28 | 2008-07-10 | Ntt Docomo, Inc. | Transmitter, receiver, mobile station, wireless base station, mobile communication system and mobile communication method |
JP2008259038A (en) * | 2007-04-06 | 2008-10-23 | Ntt Docomo Inc | Packet communication system, mobile station, and radio base station |
CN102237948A (en) * | 2010-04-22 | 2011-11-09 | 华为终端有限公司 | Methods and devices for transmitting and receiving service data |
RU2461987C2 (en) * | 2007-10-01 | 2012-09-20 | Квэлкомм Инкорпорейтед | Medium access control header format |
WO2012154601A1 (en) * | 2011-05-06 | 2012-11-15 | Qualcomm Incorporated | Apparatus and method for wireless communication using a packet structure |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101154972B (en) * | 2006-09-26 | 2011-09-21 | 中兴通讯股份有限公司 | Multiplexing method for part of special physical channel |
US8693688B2 (en) * | 2009-03-03 | 2014-04-08 | Intel Corporation | Adaptive packet ciphering |
CN102835150B (en) * | 2009-09-02 | 2015-07-15 | 苹果公司 | MAC packet data unit construction for wireless systems |
CN102045880B (en) * | 2009-10-09 | 2015-03-25 | 大唐移动通信设备有限公司 | Data transmission method, system and device based on CPRI (Common Public Radio Interface) protocol |
CN103052045B (en) * | 2011-10-17 | 2019-03-12 | 中兴通讯股份有限公司 | A kind of indicating means of type of message, system and device |
CA3095641C (en) | 2017-06-16 | 2023-03-21 | Zte Corporation | Methods for transmission and reception of control information in a coordinated system |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2000074344A1 (en) * | 1999-05-27 | 2000-12-07 | Samsung Electronics Co., Ltd. | Apparatus and method for transmitting variable-length data according to a radio link protocol in a mobile communication system |
WO2002045279A2 (en) * | 2000-11-30 | 2002-06-06 | Qualcomm Incorporated | Method and apparatus for determining optimum data rate on the reverse supplemental channel in wireless communications |
WO2003039057A2 (en) * | 2001-11-01 | 2003-05-08 | Qualcomm, Incorporated | Inner coding of higher priority data within a digital message |
-
2004
- 2004-07-14 JP JP2006520119A patent/JP4295320B2/en active Active
- 2004-07-14 WO PCT/KR2004/001752 patent/WO2005006599A1/en active Search and Examination
- 2004-07-14 AU AU2004300830A patent/AU2004300830B2/en not_active Ceased
- 2004-07-14 RU RU2005140651A patent/RU2319320C2/en not_active IP Right Cessation
- 2004-07-14 CN CN2004800168948A patent/CN1806401B/en not_active Expired - Fee Related
- 2004-07-14 CA CA 2529171 patent/CA2529171C/en not_active Expired - Fee Related
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2000074344A1 (en) * | 1999-05-27 | 2000-12-07 | Samsung Electronics Co., Ltd. | Apparatus and method for transmitting variable-length data according to a radio link protocol in a mobile communication system |
WO2002045279A2 (en) * | 2000-11-30 | 2002-06-06 | Qualcomm Incorporated | Method and apparatus for determining optimum data rate on the reverse supplemental channel in wireless communications |
WO2003039057A2 (en) * | 2001-11-01 | 2003-05-08 | Qualcomm, Incorporated | Inner coding of higher priority data within a digital message |
Non-Patent Citations (1)
Title |
---|
"Medium access control (MAC) standard for cdma2000 spread spectrum systems - release C", 3GPP2 C.S0003-C VERSION 1.0, 28 May 2002 (2002-05-28), pages 2 - 50, Retrieved from the Internet <URL:http://www.3gpp2.com/public_html/specs/C.S0003-C_v1.0.pdf> * |
Cited By (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1804530A1 (en) * | 2004-10-13 | 2007-07-04 | Huawei Technologies Co., Ltd. | Method for transmitting data in digital cluster system |
EP1804530A4 (en) * | 2004-10-13 | 2008-01-23 | Huawei Tech Co Ltd | Method for transmitting data in digital cluster system |
WO2008049472A1 (en) * | 2006-10-27 | 2008-05-02 | Telefonaktiebolaget Lm Ericsson (Publ) | Length indicator optimization |
US8619770B2 (en) | 2006-10-27 | 2013-12-31 | Telefonaktiebolaget Lm Ericsson (Publ) | Length indicator optimization |
KR101128732B1 (en) | 2006-12-28 | 2012-03-23 | 가부시키가이샤 엔티티 도코모 | Transmitter, receiver, mobile station and wireless base station |
EP2124467A1 (en) * | 2006-12-28 | 2009-11-25 | NTT DoCoMo, Inc. | Transmitter, receiver, mobile station and wireless base station |
WO2008081881A1 (en) * | 2006-12-28 | 2008-07-10 | Ntt Docomo, Inc. | Transmitter, receiver, mobile station, wireless base station, mobile communication system and mobile communication method |
US8400962B2 (en) | 2006-12-28 | 2013-03-19 | Ntt Docomo, Inc. | Transmitter apparatus, receiver apparatus, mobile station, radio base station, mobile communication system and mobile communication method |
EP2124467A4 (en) * | 2006-12-28 | 2013-10-02 | Ntt Docomo Inc | Transmitter, receiver, mobile station and wireless base station |
WO2008081882A1 (en) | 2006-12-28 | 2008-07-10 | Ntt Docomo, Inc. | Transmitter, receiver, mobile station and wireless base station |
JP2008259038A (en) * | 2007-04-06 | 2008-10-23 | Ntt Docomo Inc | Packet communication system, mobile station, and radio base station |
RU2461987C2 (en) * | 2007-10-01 | 2012-09-20 | Квэлкомм Инкорпорейтед | Medium access control header format |
US8902927B2 (en) | 2007-10-01 | 2014-12-02 | Qualcomm Incorporated | Medium access control header format |
US9516547B2 (en) | 2007-10-01 | 2016-12-06 | Qualcomm Incorporated | Medium access control header format |
CN102237948A (en) * | 2010-04-22 | 2011-11-09 | 华为终端有限公司 | Methods and devices for transmitting and receiving service data |
WO2012154601A1 (en) * | 2011-05-06 | 2012-11-15 | Qualcomm Incorporated | Apparatus and method for wireless communication using a packet structure |
US8902894B2 (en) | 2011-05-06 | 2014-12-02 | Qualcomm Incorporated | Apparatus and methods for wireless communication using a packet structure that indicates whether payload length field and payload are included in the packet |
Also Published As
Publication number | Publication date |
---|---|
JP4295320B2 (en) | 2009-07-15 |
CA2529171A1 (en) | 2005-01-20 |
RU2319320C2 (en) | 2008-03-10 |
AU2004300830A1 (en) | 2005-01-20 |
AU2004300830B2 (en) | 2008-01-31 |
CA2529171C (en) | 2011-11-15 |
RU2005140651A (en) | 2006-06-10 |
CN1806401A (en) | 2006-07-19 |
JP2007528633A (en) | 2007-10-11 |
CN1806401B (en) | 2010-10-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7817663B2 (en) | Method and apparatus for generating packet data to support multiple services in a wireless packet data communication system | |
US7349434B2 (en) | Method and apparatus for transmitting different data types in a wireless packet data communication system | |
US7898980B2 (en) | Method and apparatus for supporting voice service through radio channel in mobile telecommunication system | |
AU750516B2 (en) | Subnetwork dependent convergence protocol for a mobile radio network | |
CA2529171C (en) | Method and apparatus for generating packet data to support multiple services in a wireless packet data communication system | |
KR101002908B1 (en) | Generating method and apparatus of protocol data unit for supporting multiple service in wireless packet data communication system | |
FI106088B (en) | Method of transmitting data between the network portion of a General Packet Radio Service and a subscriber terminal | |
JP2002527945A (en) | Data segmentation method for telecommunications systems | |
US9629019B2 (en) | Enhanced multiplexing for single RLC entity | |
AU5110100A (en) | Apparatus and method for transmitting variable-length data according to a radio link protocol in a mobile communication system | |
JP2001516179A (en) | Method and apparatus for processing data in certain layers according to certain protocols in a mobile communication system | |
JP2002542660A (en) | Method and communication system for balancing and rate matching the bit rate of a transport channel with the bit rate of a physical channel | |
KR100514144B1 (en) | Method For Simultaneous Voice And Data Service In Mobile Communication System | |
KR100876723B1 (en) | Method and apparatus for session negotiation in mobile communication system and system thereof | |
EP1234426B1 (en) | Method and system for identifying encoding/decoding information in a mobile radio network | |
KR20040074141A (en) | Method for designating type of packet data unit in wireless packet data telecommunication system | |
WO2001022679A2 (en) | Method and apparatus for multiplexing packet data flows | |
JP2004501550A (en) | Method and apparatus for multiplexing multiple data connections into a single provisional block flow | |
KR20040017189A (en) | Method for transmitting and receiving packet data unit in wireless packet data telecommunication system | |
Chen et al. | GPRS-PACS: evolution of T-PACS towards third generation wireless services | |
KR20070050746A (en) | Method and apparatus for negotiating session between access terminal and access network in a mobile communication system and system thereof |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2004300830 Country of ref document: AU |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2405/KOLNP/2005 Country of ref document: IN |
|
ENP | Entry into the national phase |
Ref document number: 2004300830 Country of ref document: AU Date of ref document: 20040714 Kind code of ref document: A |
|
WWP | Wipo information: published in national office |
Ref document number: 2004300830 Country of ref document: AU |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2529171 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: 20048168948 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2006520119 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2005140651 Country of ref document: RU |
|
122 | Ep: pct application non-entry in european phase | ||
DPE2 | Request for preliminary examination filed before expiration of 19th month from priority date (pct application filed from 20040101) |