WO2009086654A1

WO2009086654A1 - Data processing method, apparatus and system for reducing redundant length information

Info

Publication number: WO2009086654A1
Application number: PCT/CN2007/003891
Authority: WO
Inventors: Tao Yang; Mingli You
Original assignee: Alcatel Shanghai Bell Company, Ltd.; Alcatel Lucent
Priority date: 2007-12-29
Filing date: 2007-12-29
Publication date: 2009-07-16
Also published as: CN101843042B; CN101843042A

Abstract

A data processing method for reducing redundant length information is provided. At the higher layer of the two adjacent layers of protocol layers, at least one higher layer data block is encapsulated to a higher layer frame. At the lower layer of the two adjacent layers, the data from at least one higher layer frame is encapsulated to a lower layer frame. The lower layer frame header only carries the necessary length information of every higher layer data block without the redundant length information that is the total length information of every higher layer frame. The corresponding data processing device, mobile terminal, base station and mobile communication system are provided. The redundant length information in the wireless transmission is reduced, thus the wireless resource is efficiently saved.

Description

Used to reduce redundant length information

Data processing method, device and system

Field of the Invention The present invention generally relates to mobile communication systems, and more particularly to a data processing method for reducing redundancy length information and a data processing apparatus, mobile terminal, base station, and mobile communication system using the same. Background technique

The third generation mobile communication technology is divided into two major technologies: CDMA and TDMA. Among them, the mainstream 4 technologies are three kinds of CDMA technologies: CDMA-DS (Direct Spread Spectrum), which is a WCDMA technology jointly proposed by Europe and Japan; CDMA- MC (Multi-Carrier) is the CDMA2000 technology proposed by the United States; CDMA-TDD (Time Division Duplex) includes TD-SCDMA proposed by China and UTRA TDD proposed by Europe. The development of these standards relies mainly on two international organizations, 3GPP and 3GPP2. Among them, 3GPP researches, develops and promotes the 3G standard based on the evolution of the GSM core network, namely WCDMA TDS-CDMA.

A viable mobile communication system needs to provide users with higher data rates, better coverage and greater capacity for the network. Driven by such considerations and technologies, the improvement and enhancement of the UMTS third-generation mobile communication system based on WCDMA/TD-SCDMA from its birth of the terrestrial radio access network has been continuously carried out within 3GPP. HSDPA (High Speed Downlink Packet Data Access) in 3GPP Rel5 is the first step, and HSUPA (High Speed Uplink Packet Access) is gradually becoming known and familiar in 3GPP Rel6.

Since 2003, broadband wireless access technology represented by IEEE 802.16e has received extensive attention. Especially for higher data rates, mobility support. Gradually formed a competition for the existing mobile communication system. In order to counter this competition, 3GPP launched the 3G Long Term Evolution (LTE) to evolve access technology. (evolved-UTRA, E-UTRA) and access networks (E-UTRAN) provide better support for the growing needs of operators and users. 3GPP officially established the LTE Research Project in December 2004. The goal of the research project is to: Develop 3GPP wireless access technology to evolve toward "high data rate, low latency and optimized packet data applications." The working groups responsible for the LTE research project are RANI (Radio Access Networks WG1), RAN2, RAN3 and RAN4. RAN2 is responsible for research on LTE MAC layer technology and L3 radio resource control.

In order to simplify the signaling process and shorten the delay, E-UTRAN discards the RNC-NodeB structure of UTRAN and is composed entirely of eNodeBs (base stations). The topology of the network is shown in Figure 1.

The air interface high-level protocol defines the use of physical layer resources. The control and management of communication through signaling messages is the basis for the full capacity of the physical layer transmission technology, and its role is indispensable. For the design of E-UTRAN air interface high-level protocol, it is necessary to meet the efficiency and control the complexity to a reasonable level, thus ensuring the system's achievability and reliability.

Based on this principle, E-UTRAN redesigned the original UMTS air interface high-level protocol. In the E-UTRAN network, because there is no RNC, the air interface protocol structure of the entire E-UTRAN is quite different from that of the original UTRAN, especially the location of different functional entities has changed a lot. The functions originally assumed by the RNC were distributed to the eNodeB and AGW.

Figure 2 shows the functions assumed by each network element in the E-UTRAN network. In the E-UTRAN network, the main functions of the eNodeB include the PHY, MAC, PLC, RRC layer entities of the air interface, the establishment, management and release of the control plane and user plane in the user communication process, and some radio resources. Management (RRM) aspects of functionality.

The E-UTRAN air interface protocol can be divided into a user plane (as shown in Figure 3) and a control plane (as shown in Figure 4). The control plane is responsible for the management of the user's radio resources, the establishment of the wireless connection, the QoS guarantee of the service, and the final resource release, while the user plane is mainly responsible for the normal transmission of data. As can be seen from Figure 3, in the user plane, the protocol stack is mainly divided into MAC, RLC, PDCP and security sublayer. Compared with the 3GPP Rel6, the functions of the MAC, RLC, and PDCP sublayers are similar, except that the network element responsible for the corresponding protocol changes.

As can be seen from Figure 4, the underlying protocol of the control plane is similar to the user plane.

For convenience of description, the following uses a WCDMA system as an example to illustrate the structure of the Uu interface (air interface) protocol stack (as shown in Figure 5). As can be seen from Figure 5, the Uu interface is divided into three protocol layers: physical layer (Ll), data link layer (L2), and network layer (L3). L2 is further divided into the following sublayers: Media Access (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Broadcast/Multicast Control (BMC). The RLC sublayers of L3 and L2 are divided into control plane and user plane, and PDCP and BMC sublayers exist only in the user plane. In the control plane, L3 is divided into different sublayers. The lowest layer is Radio Resource Control (RRC), which is located at the access layer, interfaces with L2, and terminates at UTRAN. Higher layer signaling, such as mobility management (MM) and connection management (CM), is a non-access layer.

The Media Access Control (MAC) layer is located above the physical layer. It uses the transport channel provided by the physical layer and provides a logical channel to the radio link layer. Therefore, the mapping between the logical channel and the transport channel is performed in the MAC layer. The MAC layer can also select the appropriate transport format (TF) for each transport channel based on the resource rate of the logical channel. The choice of transport format is based on the Transport Format Combination Set (TFCS) defined by the Access Control at Connection.

The MAC layer transmits data but does not guarantee proper delivery to the peer entity. Some important data streams can be guaranteed to be transmitted correctly by the upper layer functions. This will be done at the RLC layer, which is not available in the MAC layer. At the same time, the MAC layer does not segment the data. The segmentation/reassembly function is also done by the upper layer, the RLC layer. At the MAC layer, the data block of a certain size transmitted by the RLC layer is received according to the configured parameters. At the request of the RRC, the MAC layer can perform re-allocation of radio resources and change of MAC parameters. For example, reconfiguring the MAC entity, changing the UE identity, changing the transport format (combination) set, changing the transport channel type, and so on. At the same time, the MAC aggregates the local traffic and quality to the RRC under the control of the RRC, so that the RRC controls the resources according to the current service traffic and the quality of the service.

The MAC layer provides data transmission services on logical channels. The set of logical channel types corresponds to different types of data transmission services provided by the MAC. Each logical channel type is based on its The type definition of the input message. Logical channels can be divided into two broad categories: control channels for transmitting control plane information and traffic channels for transmitting user plane information.

The RLC layer provides segmentation and retransmission services for user and control data. Each RLC entity is configured by RRC and operates in three modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledge Mode (AM). In the control plane, the service provided by the RLC layer to the upper layer is a Signaling Radio Bearer (SRB). In the user plane, the service provided by the RLC to the upper layer is a radio bearer (RB).

Transparent mode service and non-acknowledge mode service have one transmission and one receiving entity, and the acknowledge mode service has only one entity that sends and receives a combination. The transmission of RLC PDUs may be on separate logical channels, such as the control PDU being sent on one logical channel and the data PDU being transmitted on another logical channel.

The acknowledgment mode data transmission service transmits the high layer PDU and guarantees delivery to the peer entity. When the RLC cannot pass the data correctly, the user at the sender will receive the notification. If RLC PDU retransmission is required, the receiving end sends a retransmission request to the transmitting end, and the request includes information about the RLC PDU that needs to be retransmitted. The sender then retransmits the RLC PDU or RLC PDU segment based on the retransmission request and network resource usage.

It should be noted that although the air interface protocol stacks of LTE systems based on different technologies are not identical, the protocol stack structure is substantially similar to the above structure. Further, in terms of data encapsulation methods of the RLC layer and the MAC layer, these LTE systems are substantially the same, and they all have the following common features: The length of the RLC PDU is variable in different ports; according to the scheduling result, RLC The PDU segmentation is dynamic; according to the scheduling result, the RLC SDU segmentation is dynamic.

In response to the above problems, a lot of research has been conducted on the data encapsulation formats of the RLC layer and the MAC layer within the RAN2 working group. Some members have proposed a solution for RLC PDUs and MAC data PDUs, in order to ensure that the RLC layer at the receiving end unambiguously unlinks each RLC SDU or RLC SDU segment, each RLC SDU or RLC must be The length information of the SDU segment is included in the RLC PDU header. Also, in order to ensure that the MAC layer of the receiving end extracts each RLC PDU or RLC PDU segment without errors, the length information of each RLC PDU or RLC PDU segment must be included in the MAC Data PDU header. The encapsulation process at the transmitting end is as shown in FIG. 6A, and the decapsulation process at the receiving end is as shown in FIG. 6B. It should be noted that although the MAC data PDUs in the MAC PDU are only schematically illustrated in the figure, other information may be included in the actual MAC PDU, such as a MAC Control PDU, padding bytes, and the like.

As shown in FIG. 6A, at the RLC layer of the transmitting end, RLC SDUs (Service Data Units) or segments from the same logical channel are connected, an RLC PDU header is added, and encapsulated into RLC length information and other RLC PDU headers. In the figure, LEN_R11, ..., LEN Rln respectively indicate the length information of n RLC SDUs or RLC SDU segments in RLC PDU1, LEN_Rm 1, ..., LEN_Rmn respectively indicate RLC PDUm The length information of one RLC SDU or RLC SDU segment in the middle.

At the MAC layer of the transmitting end, the RLC PDU or the RLC PDU segment is multiplexed, the MAC PDU header is added, and encapsulated into a MAC PDU, where the MAC PDU header includes length information of each RLC PDU or RLC PDU segment and other MAC PDU header. In the figure, LEN_Ml, ..., LEN_Mm respectively indicate the length information of m RLC PDUs or RLC PDU segments in the MAC data PDU.

The decapsulation process of Figure 6B is the reverse of the packaging process of Figure 6A and therefore will not be described again.

It can be clearly seen from Figure 6A that the length of the RLC PDU or RLC PDU segment = the RLC

The length of the PDU header. For example, in Figure 6A, the length of the RLC PDU 1 is LEN_M1 = (LEN_R11 + . , .+ LEN_Rln) + the length of the RLC PDU1 4 header, and so on. This means that the length information LEN_Ml, LEN_Mm in the MAC data PDU is actually redundant. For example, if the length of LEN_Rl 1 , ..., LEN_Rln and other RLC PDU headers can be known, the entire RLC PDU can be completely read at the receiving end, instead of having to calculate LEN_M1 and include LEN_M1 In the MAC data PDU header. Today, when information transmission tasks are so heavy, the transmission of such redundant length information will undoubtedly waste valuable wireless resources.

Therefore, there is a need to develop a new technique to reduce the transmission of such redundant length information. Summary of the invention

The object of the present invention is to reduce the redundancy length information carried in the MAC data PDU by a simple and effective method for the technical problem unsolved in the prior art.

According to a first aspect of the present invention, a data processing method for reducing redundancy length information is provided, wherein at least one upper layer data block is encapsulated as an upper layer data frame in an upper layer of adjacent two layers of a protocol layer, where The data from the at least one upper layer data frame is encapsulated into the lower layer data frame in the lower layer of the adjacent two layers, and the method includes:

On the sending end,

In the upper layer, each upper layer data frame includes an upper layer data frame header and an upper layer data block, and the length information of the upper layer data frame header is included in the length information of the first upper layer data block in the upper layer data frame;

And transmitting, to the lower layer, the length information of each upper layer data frame, and the length information of each upper layer data frame, the length information of each upper layer data block in the upper layer data frame;

In the lower layer, the received length information for each upper layer data frame is placed in the appropriate position of the lower layer data frame header, and the upper layer data frames are multiplexed accordingly;

At the receiving end,

In the lower layer, the length of the upper layer data frame is calculated based on the length information of each upper layer data frame included in the header of the lower layer data frame, and each upper layer data frame is correspondingly extracted from the lower layer data frame;

And transmitting the length information of each upper layer data frame and the upper layer data frame to the upper layer, where the length information for each upper layer data frame includes length information of each upper layer data block in the upper layer data frame;

In the upper layer, each upper layer number block is extracted from the upper layer data frame based on the length information of each upper layer data block.

According to a second aspect of the present invention, a data processing method for reducing redundancy length information is provided, wherein at least one upper layer data block is encapsulated as an upper layer data frame in an upper layer of adjacent two layers of a protocol layer, where The lower layer of the adjacent two layers will come from at least one upper layer The data according to the frame is encapsulated into a lower layer data frame, and the method includes:

On the sending end,

In the lower layer, the upper layer data frame is received from the upper layer, where each upper layer data frame includes an upper layer data block, length information of each upper layer data block in the upper layer data frame, and other upper layer data frame headers, and is extracted from the upper layer data frame. Length information of each upper data block;

The length information of the header of the other upper layer data frame is included in the length information of the first upper layer data block;

And multiplexing the upper layer data frame of the upper layer data frame header with the length information of each upper layer data frame, wherein the length information for each upper layer data frame includes each upper layer data block of the upper layer data frame. Length information;

At the receiving end,

In the lower layer, the length of the upper layer data frame is calculated based on the length information for each upper layer data frame included in the lower layer data frame header, and correspondingly, each of the upper layer data blocks is extracted from the lower layer data frame. Upper layer data frame of length information;

Extracting length information of other upper layer data frame headers from length information of the first upper layer data block;

The upper layer data frame is encapsulated and passed to the upper layer based on the length information of each upper layer data block and the length information of other upper layer data frame headers.

According to another aspect of the present invention, a data processing apparatus for reducing redundancy length information is provided, the apparatus comprising:

a transmission processing module for performing an operation at the transmitting end according to the present invention; and a receiving processing module for performing an operation at the receiving end according to the present invention.

According to another aspect of the present invention, there is provided a mobile terminal characterized by comprising a data processing apparatus according to the present invention.

According to another aspect of the present invention, a base station is provided, characterized by comprising a data processing apparatus according to the present invention. According to another aspect of the present invention, there is provided a mobile communication system characterized by comprising a mobile terminal according to the present invention and a base station according to the present invention.

The present invention effectively saves the fact that only the necessary length information of each RLC SDU or RLC SDU segment is carried in the MAC data PDU header, and no redundant length information, that is, the total length information of each RLC PDU, is carried. Wireless resources. At the same time, due to the length information of each RLC SDU or RLC SDU segment carried in the MAC data PDU header, decapsulation can still be performed correctly at the receiving end. For example, for a bit rate of 100 Mb/s and a TTI of 1 ms, assuming that m RLC PDUs are multiplexed in one MAC data PDU, according to the present invention, about 17 m bits can be saved regardless of the size of the MAC data PDU. how is it.

Other features and advantages of the present invention will become more apparent from the detailed description of the embodiments. DRAWINGS

FIG. 1 schematically shows a network topology of an LTE system;

FIG. 2 schematically shows a functional division of each network node of an LTE system;

Figure 3 is a schematic illustration of a user plane protocol stack structure of an LTE system air interface protocol;

Figure 4 is a schematic diagram showing the control plane protocol stack structure of the LTE system air interface protocol;

FIG. 5 is a schematic diagram showing a Uu interface protocol stack structure of a WCDMA system; FIG. 6A is a schematic diagram showing a RLC PDU and a MAC data PDU encapsulation process of a transmitting end in the prior art;

6B is a schematic diagram showing a RLC PDU and a MAC data PDU decapsulation process at the receiving end in the prior art;

FIG. 7A is a schematic diagram showing an RLC PDU and a MAC data PDU encapsulation process of a transmitting end according to a first embodiment of the present invention; FIG.

FIG. 7B is a schematic diagram showing a RLC PDU and a MAC data PDU decapsulation process at the receiving end according to the first embodiment of the present invention; FIG. FIG. 8 is a flowchart of a data processing method according to a first embodiment of the present invention; FIG.

FIG. 9A schematically shows an RLC of a transmitting end according to a second embodiment of the present invention.

PDU and MAC data PDU encapsulation process;

FIG. 9B schematically shows an RLC of a receiving end according to a second embodiment of the present invention.

PDU and MAC data PDU decapsulation process;

Figure 10 is a flowchart of a data processing method according to a second embodiment of the present invention; and Figure 11 is a schematic block diagram of a data processing apparatus according to the present invention. detailed description

The invention will now be described with reference to the drawings, wherein the same reference numerals are used to refer to the same or the like.

Figure 5 shows the network topology, network node function partitioning, and air interface protocol stack structure of the LTE system. Figures 6A and 6B show the prior art RLC PDU and MAC data PDU encapsulation formats. These contents have been described in the background art and will not be described again here.

It should be noted that the RLC SDU and RLC SDU segments are similar in terms of the processing of the length information, so in the following, when only the RLC SDU is mentioned, it should also be understood to include the RLC SDU segment. The case of RLC PDU and RLC PDU segmentation is similar.

A first embodiment of the present invention will be described below with reference to Figs. 7A, 7B and 8.

The RLC PDU and MAC Data PDU encapsulation formats of the first embodiment of the present invention will be described first with reference to Figs. 7A and 7B.

It will be understood by those skilled in the art that the package format in FIGS. 7A and 7B is different from the package format in FIGS. 6A and 6B except that the length information is processed differently and the related data processing is caused differently. Other aspects can be similar. Therefore, for the sake of brevity, the corresponding differences will be explained only when necessary.

According to the first embodiment of the present invention, the length information is included only in the MAC data PDU, and the length information is not carried in the RLC PDU. As shown in FIG. 7A, at the RLC layer, length information of other RLC PDU headers is included in the length information of the RLC SDU1. Then, divide The RLC PDU and the length information for each RLC PDU are not passed to the MAC layer, wherein the length information for each RLC PDU includes length information for each RLC SDU or segment in the RLC PDU. At the MAC layer, the MAC Data PDU header includes length information for each RLC PDU.

It should be noted that in the encapsulation process shown in FIG. 7A, the method of transmitting RLC PDUs from the RLC layer to the MAC layer and the length information for each RLC PDU is not unique, and it may pass through the original between the RLC layer and the MAC layer. The language can also be carried out by other means known in the art. The order of the transmission is not unique, but can be determined according to the different conditions of each system and application, as long as the length information can be associated with the corresponding LC PDU when encapsulating at the MAC layer.

More specifically, the length information for each RLC PDU is only one type of description information that can be transmitted as a whole from the RLC layer to the MAC layer, or separately. The order of arrangement is not unique, but can be determined according to different conditions of each system and application, as long as the length information can be associated with the corresponding RLC SDU or RLC SDU segment when encapsulating at the MAC layer. Just fine.

Similarly, at the MAC layer, the encapsulation order of each RLC PDU is not unique. As long as the length information can be associated with the corresponding RLC PDU, the decapsulation can be correctly performed at the receiving end. The LCID (Logical Channel Identifier) can be inserted prior to the length information for each RLC PDU or otherwise indicating which logical channel the RLC PDU is from.

The decapsulation process of Figure 7B is the reverse of the packaging process of Figure 7A and therefore will not be described again.

The encapsulation and decapsulation process shown in Figs. 7A and 7B will be described in detail below with reference to Fig. 8. Figure 8 is a flow chart of a data processing method in accordance with a first embodiment of the present invention.

As shown in FIG. 8, at the transmitting end, in step S801, at the RLC layer, length information of other RLC PDU headers is included in the length information of the RLC SDU 1.

In step S802, the RLC PDU and the length information for each RLC PDU are respectively delivered to the MAC layer. The length information for each RLC PDU includes length information of each RLC SDU or segment in the RLC PDU. About the way and arrangement of delivery For the order, please refer to the related description of FIG. 7A.

In step S803, at the MAC layer, the received length information for each RLC PDU is placed in the appropriate position of the MAC Data PDU header, and the associated RLC PDUs are multiplexed accordingly.

At the receiving end, in step S804, at the MAC layer, the length of each RLC PDU is calculated based on the associated length information in the MAC Data PDU header, and then each RLC PDU is extracted from the MAC Data PDU accordingly.

In step S805, each RLC PDU and length information for each RLC PDU are respectively delivered to the RLC layer. The length information for each RLC PDU includes length information of each RLC SDU or segment in the RLC PDU.

In step S806, at the RLC layer, each RLC SDU or RLC SDU segment is extracted from the RLC PDU based on the length information of each RLC SDU or segment.

Referring to the related description of FIG. 7A, it will be understood by those skilled in the art that in step S803 of FIG. 8, the LCID may be inserted or otherwise indicated before the length information for each RLC PDU. A logical channel. In this case, in step S804 of Fig. 8, sub-steps for identifying the LCID or other identification will be included accordingly.

It should be noted that since Fig. 8 is a further description of Figs. 7A and 7B, the above description of Fig. 7A is equally applicable to Fig. 8.

As mentioned before, the invention is based on the saving of radio resources. Since the RLC PDU transmission between the RLC layer and the MAC layer does not involve the use of radio resources, according to the second embodiment of the present invention, the length information is included in the RLC PDU transmitted between the RLC layer and the MAC layer. That is, similar to the prior art, the object of the present invention can be achieved as long as it can be guaranteed that the redundant length information is not included in the MAC data PDU.

Next, a second embodiment of the present invention will be described with reference to Figs. 9A, 9B and 10. The RLC PDU and MAC Data PDU encapsulation format of the second embodiment of the present invention will be described first with reference to Figs. 9A and 9B.

One of ordinary skill in the art will appreciate that the package format in Figures 9A and 9B is compared to the package format in Figures 6A and 6B except at the MAC layer pair length information. Other aspects can be similar, except for differences in the way they are handled and the resulting differences in data processing. Therefore, for the sake of brevity, the corresponding differences will be explained only when necessary.

According to the second embodiment of the present invention, at the MAC layer, length information is extracted from the RLC PDU. The length information of other RLC PDU headers is included in the length information of the RLC SDU1. The length information for each RLC PDU is placed in the appropriate location of the MAC Data PDU header, and the associated RLC PDUs are multiplexed accordingly, wherein the length information for each RLC PDU includes each RLC SDU in the RLC PDU Or segment length information. At the MAC layer, the MAC Data PDU header includes length information for each RLC PDU.

It should be noted that at the MAC layer, the encapsulation order of each RLC PDU is not unique, as long as each length information can be associated with the corresponding RLC PDU, so that the decapsulation can be correctly performed at the receiving end. The LCID (Logical Channel Identifier) can be inserted prior to the length information for each RLC PDU or otherwise indicating which logical channel the RLC PDU is from.

The decapsulation process of Figure 9B is the reverse of the packaging process of Figure 9A and therefore will not be described again.

The encapsulation and decapsulation process shown in Figs. 9A and 9B will be described in detail below with reference to Fig. 10. Figure 10 is a flow chart of a data processing method in accordance with a second embodiment of the present invention.

As shown in FIG. 10, at the transmitting end, in step S1001, at the MAC layer, an RLC PDU is received from the RLC layer, and length information is extracted from the RLC PDU.

In step S1002, the length information of the other RLC PDU headers is included in the length information of the RLC SDU1.

In step S1003, the length information for each RLC PDU is placed in the appropriate position of the MAC data PDU header, and the associated RLC PDUs are multiplexed accordingly. The length information for each RLC PDU includes length information of each RLC SDU or segment in the RLC PDU.

At the receiving end, in step S1004, at the MAC layer, the length of each RLC PDU is calculated based on the associated length information in the MAC Data PDU header, and then each RLC PDU is extracted from the MAC data PDU accordingly. The length information for each RLC PDU includes length information of each RLC SDU or segment in the RLC PDU, and And the length information of other RLC PDU headers is included in the length information of the RLC SDU1. In step S1005, length information of other RLC PDU headers is extracted from the length information of the RLC SDU 1.

In step S1006, based on the length information of each RLC SDU or segment, and others

The length information of the RLC PDU header, encapsulates the RLC PDU, and passes it to the RLC layer.

Referring to the related description of FIG. 9A, those skilled in the art can understand that in step S1003 of FIG. 10, it can be inserted before the length information for each RLC PDU.

The LCID or otherwise indicates which logical channel the RLC PDU is from. In this case, in step S1004 of Fig. 10, sub-steps for identifying the LCID or other identification will be included accordingly.

It should be noted that since Fig. 10 is a further description of Figs. 9A and 9B, the above description of Fig. 9A is equally applicable to Fig. 10.

Figure 11 is a schematic block diagram of a data processing apparatus in accordance with the present invention. Reference numeral 1100 denotes a data processing device according to the present invention; reference numeral 1001 denotes a transmission processing module 1101 for processing data to be transmitted; and reference numeral 1102 denotes a reception processing module for processing received data.

As shown in FIG. 11, when the data processing apparatus 1100 is acting as a transmitting end, the RLC SDU or RLC SDU segment arrives at the transmission processing module 1101. The Transmit Processing Module 1101 performs a series of processing on the RLC SDU or RLC SDU segments and finally encapsulates them into MAC Data PDUs.

When the data processing device 1100 is acting as a receiving end, the MAC data PDU arrives at the receiving processing module 1102. The receiving processing module 1102 performs a series of processing on the MAC data PDU, and finally decapsulates it into an RLC SDU or RLC SDU segment.

In the first embodiment of the present invention, the transmission processing means 1101 can execute the steps as described in steps S801 to S803 of Fig. 8, and the reception processing means 1102 can execute the steps as described in step S804 of step S804 of Fig. 8.

In the second embodiment of the present invention, the transmission processing module 1101 can perform the steps described in steps S1001 to S1003 of FIG. 10, and the reception processing module 1102 can perform the steps described in steps S1004 to S1006 of FIG. The processing modules shown in FIG. 11 can be implemented as separate functional modules, or can be combined into one functional module. The function module can adopt a fully hardware implementation form, a fully software implemented form, or an implementation form including both hardware and software units. According to one implementation, the processes described in the detailed description may be stored in a computer readable storage medium, which may be any device or medium that can store code and/or data for execution by a computer system. This includes, but is not limited to, application specific integrated circuits (ASICs) field programmable gate arrays (FPGAs), semiconductor memories, and the like. According to an implementation manner, each of the foregoing processing modules may be implemented by using a device that drives a general-purpose computer, and may also use other devices such as a microcontroller, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a combination thereof. The processor device is implemented.

In one embodiment of the invention, a mobile terminal includes a data processing device 1100.

In another embodiment of the invention, a base station includes a data processing apparatus 1100. It should be understood that the present invention is not limited to the RLC layer and the MAC layer of the 3GPP LTE system air interface protocol, but can be applied between any similar adjacent two protocol layers having redundant length information in a similar communication system.

It should be noted that in the above description, what has been apparently necessary to explain the principles of the present invention has been mainly described.

While the embodiments of the present invention have been described in the embodiments of the present invention, various modifications and changes may be made within the scope of the appended claims.

Claims

Claim

A data processing method for reducing redundancy length information, wherein at least one upper layer data block is encapsulated as an upper layer data frame in an upper layer of adjacent two layers of a protocol layer, in the adjacent two layers The data from the at least one upper layer data frame is encapsulated into a lower layer data frame in the lower layer, where the method includes:

On the sending end,

At the receiving end,

In the upper layer, each upper layer data block is extracted from the upper layer data frame based on the length information of each upper layer data block.

2. The data processing method according to claim 1, wherein the upper layer is an RLC layer, and the lower layer is a MAC layer.

The data processing method according to claim 2, wherein the upper layer data block is an RLC SDU or an RLC SDU segment, and the upper layer data frame is an RLC PDU or an RLC PDU. Segmented, and the lower layer data frame is a MAC data PDU.

4. The data processing method according to claim 3, wherein in the transmitting end, in the lower layer, the LCID is inserted before the appropriate position, and in the receiving end, in the lower layer, the location is judged based on the LCID. Which logical channel the upper layer data frame corresponding to the appropriate location comes from.

On the sending end,

At the receiving end,

6. The data processing method according to claim 5, wherein the upper layer is an RLC layer, and the lower layer is a MAC layer.

The data processing method according to claim 6, wherein the upper layer data block is an RLC SDU or an RLC SDU segment, the upper layer data frame is an RLC PDU or an RLC PDU segment, and the lower layer data frame is MAC data PDU.

8. The data processing method according to claim 7, wherein in the transmitting end, in the lower layer, an LCID is inserted before the appropriate position, and in the receiving end, in the lower layer, the LCID is judged according to the LCID. The upper layer data frame corresponding to the appropriate location is from which channel.

A data processing apparatus for reducing redundancy length information, the apparatus comprising: a transmission processing module for performing an operation at a transmitting end of claim 1; and a receiving processing module for performing the method of claim 1 Receiver operation.

A mobile terminal characterized by comprising the data processing apparatus according to claim 9.

A base station, comprising the data processing apparatus according to claim 9.

A mobile communication system characterized by comprising the mobile terminal according to claim 10 and the base station according to claim 11.

13. A data processing apparatus for reducing redundancy length information, the apparatus comprising: a transmission processing module for performing an operation at a transmitting end of claim 5; and a receiving processing module for performing the method of claim 5 Receiver operation.

A mobile terminal characterized by comprising the data processing apparatus according to claim 13.

A base station, comprising the data processing apparatus according to claim 13.

A mobile communication system comprising the mobile terminal according to claim 14 and the base station according to claim 15.