CN101272519B - Method, device and base station for generating protocol data unit - Google Patents
Method, device and base station for generating protocol data unitDownload PDFInfo
- Publication number
- CN101272519B CN101272519BCN200710038488ACN200710038488ACN101272519BCN 101272519 BCN101272519 BCN 101272519BCN 200710038488 ACN200710038488 ACN 200710038488ACN 200710038488 ACN200710038488 ACN 200710038488ACN 101272519 BCN101272519 BCN 101272519B
- Authority
- CN
- China
- Prior art keywords
- data unit
- protocol data
- length
- segmentation
- indication field
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034methodMethods0.000titleclaimsabstractdescription33
- 230000011218segmentationEffects0.000claimsdescription61
- 230000014759maintenance of locationEffects0.000claimsdescription8
- 230000005540biological transmissionEffects0.000abstractdescription11
- 230000001360synchronised effectEffects0.000abstractdescription7
- 238000013508migrationMethods0.000abstract2
- 230000005012migrationEffects0.000abstract2
- 238000009826distributionMethods0.000description9
- 230000015572biosynthetic processEffects0.000description6
- 238000011084recoveryMethods0.000description6
- 238000010586diagramMethods0.000description4
- 238000005516engineering processMethods0.000description4
- 238000000638solvent extractionMethods0.000description4
- 238000004891communicationMethods0.000description1
- 230000000977initiatory effectEffects0.000description1
- 230000000630rising effectEffects0.000description1
Images
Classifications
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/02—Data link layer protocols
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
- H04L1/0056—Systems characterized by the type of code used
- H04L1/0071—Use of interleaving
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/0078—Avoidance of errors by organising the transmitted data in a format specifically designed to deal with errors, e.g. location
- H04L1/0083—Formatting with frames or packets; Protocol or part of protocol for error control
- 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
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/08—Access point devices
- 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
- H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
- Communication Control (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Technical field
The present invention relates generally to moving communicating field; More specifically, relate to a kind of method and equipment and base station that generates protocol Data Unit, be applied on the SFN (SFN); Can recover a plurality of groupings of losing in the service data transfer process, to guarantee the content synchronization between the different base station.
Background technology
In the wireless network transmission system that adopts SFN (SFN) technology, for example in the multimedia broadcasting and multicast (MBMS) system of LTE, all base stations (being designated hereinafter simply as eNB) all is synchronous fully on time and frequency.Like this, if each eNB sends same data in the same initial moment, and adopt same physical layer modulation coding techniques, then in spatial transmission, the signal that sends from each eNB has same waveform.Subscriber equipment (being designated hereinafter simply as UE), can regard the data that eNB sent as signal that same eNB sends.Because what UE received all is signals useful, the same data of transmission, this technology can greatly reduce neighbor cell interference (because this moment all being useful signal but not disturbing from neighbor cell), thereby is applicable to some broadcasting and multicast system.For example, in the multimedia broadcasting and multicast system of LTE, adopted such SFN technology.
Fig. 1 shows the network topology structure of LTE MBMS.Support the network element of MBMS mainly to comprise: BM-SC (broadcast/multi broadcast business center), SAE GW (SAE gateway), eNB (evolved base station), UE (subscriber equipment).Usually, the interface between UE and the eNB is called the S1 interface.
BM-SC is content provider's a inlet, be used for authorizing and initiating the MBMS bearer service at PLMN, and plan transmits the MBMS data to schedule.SAE GW carries out the control of MBMS bearer service to the user, and the MBMS data are sent to E-UTRAN.ENB is responsible for transmitting the MBMS data efficiently to the air interface of the MBMS of appointment service area.
Fig. 2 shows the schematic network structure of SFN.In Fig. 2, each base station adopts identical frequency to cover, and need not carry out multiplexing with time, frequency or sign indicating number between sub-district and the sub-district.Same business is all distributed same time and frequency resource in all base station region covered.Owing to adopt identical physical layer modulation and coding techniques, the signal of the identical data that sends from each base station is all the same at the waveform in space.From the UE receiver, similarly be the signal that sends from a base station, only had some multipaths than long time delay.SFN can come all standing with all base stations and normal base station transmitting power, also can come all standing with the base station transmitting power of part base station and rising.
In the LTE wireless communication system, the Radio interface protocols layer is divided into three layers.The bottom is a physical (L1), and the protocol layer that is positioned on the physical (L1) comprises data link layer (L2) and network layer (L3).In wave point, data link layer is divided into several sub-layer, comprising medium access control (MAC) protocol sublayers, Radio Link control (RLC) protocol sublayers, packet data convergence protocol (PDCP) sublayer.Network layer (L3) provides Radio Resource control (RRC) function.
In whole protocol architecture, because what arrive each eNB is the IP packet, the length of IP packet changes, from tens bytes to 1500 bytes of maximum.And, have nothing in common with each other owing to arrive the route of each eNB, in transmission course, the situation of a plurality of packet loss can appear.Therefore will guarantee the content synchronization of each eNB to the professional data of being sent of identical eMBMS, be a problem that must solve.Need realize the simple recovery of the wireless processing of eNB under the situation of eNB distributing data packet loss during.
Here; The implication of packet loss recovery is that pseudo-data are inserted in the Radio Link controller buffer; And the real data in need not recovering to divide into groups; This is because as long as eNB knows the length of the grouping that will send, the transmission that just can guarantee each grouping that lost packets is later all is synchronous in terms of content.
Fig. 3 shows the relation between the RLC SDU (service data unit) and RLCPDU (protocol Data Unit) under the existing unicast case, and its basic thought all has a Length Indication for each segmentation.As shown in Figure 3, suppose that at eNB the size of RLC PDU is 600 bytes, in RLC PDU header, comprise 2 bytes that are used for SN and SI, the size of each LI is 2 bytes.
As shown in Figure 3, the S1 interface lost two groupings (SN=i, i+1).When eNB received the grouping of sequence number SN=i+3, it knew that two groupings of front lose.But eNB only knows 2 packet loss, and the total length of grouping is 600 bytes, and does not know the distribution of lengths of 600 bytes in two groupings of losing.
Fig. 4 shows a kind of distribution of the byte length of two lost packets.As shown in Figure 4, lose two divide into groups one be 400 bytes, another is 200 bytes, and has been divided into three sections altogether, in different PDU, is indicated by separately LI respectively.For example in last PDU, two LI indicate 296 bytes of the SDU that is derived from sequence number SN=i respectively and are derived from 298 bytes of the SDU of sequence number SN=i+1.In one PDU of back, three LI indicate 102 bytes of the SDU that is derived from sequence number SN=i+1 respectively, be derived from sequence number SN=i+2SDU 200 bytes and be derived from 290 bytes of the SDU of sequence number SN=i+3.If recover in a manner mentioned above, then the start byte of next PDU will be 1286.
The another kind that Fig. 5 shows the byte length of two lost packets distributes.As shown in Figure 5, lose two divide into groups one be 298 bytes, another is 302 bytes, and the segmentation of respectively doing for oneself, and has formed two sections altogether, in different PDU, is indicated by separately LI respectively.For example in last PDU, two LI indicate 296 bytes of the SDU that is derived from sequence number SN=i respectively and are derived from 298 bytes of the SDU of sequence number SN=i+1.In one PDU of back, two LI indicate 302 bytes of the SDU that is derived from sequence number SN=i+2 respectively and are derived from 292 bytes of the SDU of sequence number SN=i+3.If recover in a manner mentioned above, then the start byte of next PDU is 1288.
Can find out that from top example because the hop count that the RLC SDU of sequence number SN=i+1 that recovers and sequence number SN=i+2 is divided is different, and each section have the LI of oneself, perhaps three LI of two LI promptly occurred, this has caused RLC PDU content asynchronous.
It is thus clear that; Because the section that single SDU divided has LI separately respectively, under the situation of many packet loss, eNB can't learn the distribution of the byte length in each grouping; Thereby can't correctly recover the grouping of losing, so caused content eNB can't be synchronous problem.And the asynchronous meeting of such content has influence on the content synchronization of follow-up grouping.Therefore, utilizing this clean culture RLC PDU structure is the grouping that can't recover to lose at eNB, and is easy to cause the asynchronous problem of content.
Summary of the invention
In view of the above problems, accomplished the present invention.The object of the present invention is to provide a kind of method and equipment and base station that generates protocol Data Unit; Utilize the protocol Data Unit that is generated; Can recover a plurality of groupings of losing in the service data transfer process, synchronous to guarantee the content delivery between the different base station.The present invention provides a kind of method that generates protocol Data Unit and equipment and base station thereof to be equally applicable to unicast transmission.
In one aspect of the invention, proposed a kind of method that generates protocol Data Unit, comprised step: the service data unit of input has been divided at least one segmentation, so that said at least one segmentation is distributed at least one protocol Data Unit; And offset field and at least one Length Indication field be set in the header of each protocol Data Unit; First section skew of first the new service data unit that occurs in the said offset field Presentation protocol data unit, and the Length Indication field is represented the total length of said new service data unit.
In another aspect of this invention, proposed a kind of method that generates protocol Data Unit, comprised step: the service data unit of input has been divided at least one segmentation, so that said at least one segmentation is distributed at least one protocol Data Unit; And in the header of each protocol Data Unit, being provided with at least one Length Indication field, said Length Indication field is represented the length of last segmentation in said at least one segmentation.
In still another aspect of the invention, proposed a kind of equipment that generates protocol Data Unit, having comprised: segmenting device is divided at least one segmentation with the service data unit of importing, so that said at least one segmentation is distributed at least one protocol Data Unit; Calculation element, first section the skew of calculating first the new service data unit that occurs in the protocol Data Unit; And setting device, offset field and at least one Length Indication field are set in the header of each protocol Data Unit, said offset field is represented said skew, and the Length Indication field is represented the total length of said new service data unit.
In still another aspect of the invention, proposed a kind of equipment that generates protocol Data Unit, having comprised: segmenting device is divided at least one segmentation with the service data unit of importing, so that said at least one segmentation is distributed at least one protocol Data Unit; Calculation element calculates the length of last segmentation in said at least one segmentation; And setting device, in the header of each protocol Data Unit, being provided with at least one Length Indication field, said Length Indication field is represented the length that said calculation element calculates.
Utilize said method of the present invention and equipment; Even only indicate with a LI because single SDU has divided a plurality of segmentations; And LI has indicated the end position of SDU in a PDU; Thereby guaranteed that the eNB in the SFN can recover to divide into groups under the situation of many packet loss, avoided the asynchronous problem of content delivery.
Description of drawings
Through below in conjunction with description of drawings the preferred embodiments of the present invention, will make above-mentioned and other purpose of the present invention, feature and advantage clearer, wherein:
Fig. 1 shows the network topology structure of LTE MBMS;
Fig. 2 shows the schematic network structure of SFN;
Fig. 3 shows the relation between the RLC SDU and RLC PDU under the existing unicast case;
Fig. 4 shows a kind of distribution of the byte length of two lost packets;
The another kind that Fig. 5 shows the byte length of two lost packets distributes;
Fig. 6 A shows a kind of example according to the data format of the formation PDU of first embodiment of the invention;
Fig. 6 B shows the another kind of example according to the data format of the formation PDU of first embodiment of the invention;
Fig. 7 shows the functional block diagram according to the equipment of the generation PDU of first embodiment of the invention;
Fig. 8 A shows a kind of example according to the data format of the formation PDU of second embodiment of the invention;
Fig. 8 B shows the another kind of example according to the data format of the formation PDU of second embodiment of the invention;
Fig. 9 shows the functional block diagram according to the equipment of the generation PDU of second embodiment of the invention;
Figure 10 A is the recovery sketch map of explanation according to a kind of distribution of the byte length of two lost packets of second embodiment of the invention; And
Figure 10 B is the recovery sketch map of explanation according to the another kind distribution of the byte length of two lost packets of second embodiment of the invention.
Embodiment
To a preferred embodiment of the present invention will be described in detail, in the description process, having omitted is unnecessary details and function for the present invention with reference to the accompanying drawings, obscures to prevent understanding of the present invention caused.
Fig. 6 A shows a kind of example according to the data format of the formation PDU of first embodiment of the invention; Shown in Fig. 6 A, in the header of each PDU, be provided with an OFFSET field and at least one L1 field.First section the skew of first new SDU that the OFFSET field is represented to occur among the PDU, each RLC PDU has and has only an OFFSET field, if first segmentation of a SDU is adjacent to after the L1 field just, the value of this this OFFSET field is set to 0.In addition, the L1 field is represented the total length of new SDU, if a plurality of new SDU are arranged in this PDU, a plurality of L1 fields is arranged then.Here the length of L1 field is 2 bytes, and the length of OFFSET field is 2 bytes.
The reason that the OFFSET field is set is; Work as receiving terminal, find that like UE a PDU loses, it can find the original position of next new SDU according to the OFFSET field; Do not have the OFFSET field else if, receiving terminal can't find the original position of complete SDU again.
In addition; In RLC PDU, have under the situation of two or a byte underfill; Must the data of the respective number byte of next RLC SDU be filled among the last RLC PDU, rather than L1 is filled among the last RLC PDU, thereby keep a SDU that a LI is only arranged.Fig. 6 B shows a such example.
Fig. 7 shows the functional block diagram according to the equipment of the generation PDU of first embodiment of the invention.As shown in Figure 7,equipment 100 comprises partitioningportion 110, calculations ofoffset part 120 withpart 130 is set.
In addition; In current RLC PDU, have under the situation of two or a byte underfill; The data of the respective number byte (being the byte number of underfill) of next RLC SDU are filled among the current RLC PDU, rather than the LI field of next RLC PDU is filled into the afterbody of current RLC PDU field.
Fig. 8 A shows a kind of example according to the data format of the formation PDU of second embodiment of the invention.Shown in Fig. 8 A; Comprised the LI field in the header according to the PDU data format of second embodiment of the invention; And do not comprise the OFFSET field, but the end position of the value representation SDU in a PDU in the LI field here, the just length of last segmentation of SDU.
If the length of last SDU segmentation than the little byte of the free space among the RLC PDU, also is filled into the last byte of next RLC SDU the afterbody of this RLC PDU, shown in Fig. 8 B.At this moment, the LI of this SDU segmentation need be filled among the back RLC PDU, and under other a kind of situation, promptly the length of last SDU segmentation equals the free space among the RLC PDU, also needs the LI value of this SDU segmentation is filled among the back RLC PDU.And this LI value is filled out in the LI field with the value that keeps.
Following table has provided retention and the implication of some special LI in particular cases.
| Bit | Describe |
| 0000，0000，0000，000 | Last RLC PDU is just in time filled up by the final stage of RLC SDU, and in last RLC PDU, does not have the LI of the end position of indicating RLCSDU. |
| 0100,0000,0000,000 | The final stage of RLC SDU is just in time to be full of last RLCPDU, but has more a byte, and in last RLC PDU, does not have the LI of the end position of indication RLC SDU.Remaining that byte is first byte of next RLCPDU in last RLC PDU. |
| 1000,0000,0000,000 | The final stage of RLC SDU is just in time to be full of last RLCPDU, but has more a byte, and in last RLC PDU, does not have the LI of the end position of indication RLC SDU.Remaining that byte is left in the basket in last RLC PDU. |
| 1100,0000,0000,000 | The remaining field of current RLC PDU is byte of padding (padding). |
Fig. 9 shows the functional block diagram according to the equipment of the generation PDU of second embodiment of the invention.As shown in Figure 9,equipment 200 comprises partitioningportion 210, calculatingsection 220 withpart 230 is set.
The RCL SDU that partitioningportion 200 receives outside input divides the RLC SDU of reception according to about measured length of RLC PDU, to form the data volume of different PDU.The length of last segmentation in each segmentation that the current SDU of calculatingsection 220 calculating is cut apart.Part 130 is set to be inserted into the length that calculatingsection 220 is calculated in the LI field.
Now, according to second embodiment of the invention, Figure 10 A and Figure 10 B show the synchronous recovery sketch map in the byte length different distributions of two packet loss.Based on shown in Figure 3, the S1 interface lost two groupings (SN=i, i+1).When eNB received the grouping of sequence number SN=i+3, it knew that two groupings of front lose.But eNB only knows 2 packet loss, and the total length of grouping is 600 bytes, and does not know the distribution of lengths of 600 bytes in two groupings of losing.
Figure 10 A shows a kind of distribution of the byte length of two lost packets.Shown in Figure 10 A, two one of groupings of losing are 400 bytes, and another is 200 bytes, and has been divided into three sections altogether, but only in back one PDU, has LI to indicate.For example in last PDU, a LI indication is derived from 296 bytes of the SDU of sequence number SN=i, and 300 bytes that are derived from the SDU of sequence number SN=i+1 do not have LI according to first segmentation of principle right and wrong of second embodiment of the invention.In one PDU of back; Two LI indicate 100 bytes of the SDU that is derived from sequence number SN=i+1 respectively; Be derived from 200 bytes of the SDU of sequence number SN=i+2,294 bytes that are derived from the SDU of sequence number SN=i+3 do not have LI according to first segmentation of principle right and wrong of second embodiment of the invention.That in these two RLC PDU, fills like this comprises SN, and the byte number of total RLC head of LI is:
4 byte SN+6 byte LI=10 bytes.
If recover in a manner mentioned above, then the start byte of next PDU will be:
(1200-10-296-600) byte+997-1=1290.
The another kind that Figure 10 B shows the byte length of two lost packets distributes.Shown in Figure 10 B, lose two divide into groups one be 298 bytes, another is 302 bytes, and the segmentation of respectively doing for oneself, and has formed two sections altogether, in different PDU, is indicated by separately LI respectively.For example in last PDU, two LI indicate 296 bytes of the SDU that is derived from sequence number SN=i respectively and are derived from 298 bytes of the SDU of sequence number SN=i+1.In one PDU of back, two LI indicate 302 bytes of the SDU that is derived from sequence number SN=i+2 respectively, and 294 bytes that are derived from the SDU of sequence number SN=i+3 do not have LI according to first segmentation of principle right and wrong of second embodiment of the invention.That in these two RLC PDU, fills like this comprises SN, and the byte number of total RLC head of LI is:
4 byte SN+6 byte LI=10 bytes.
If recover in a manner mentioned above, then the start byte of next PDU will be:
(1200-10-296-600) byte+997-1=1290.
From top example, can find out; No matter how the hop count that sequence number SN=i+1 that recovers and the RLC SDU of sequence number SN=i+2 are divided distributes; Owing to followed the principle of " LI of each SDU "; That is to say two LI only to occur, therefore after recovering 4byte LI+600bytes data, all can keep the synchronous of RLC PDU content.
Except being applied to multicast (MBMS) transmission; The present invention also can be applied to clean culture (unicast) transmission of LTE; At this moment; RLC PDU form to unicast transmission is consistent with the form of the service data unit that method and apparatus generated of first embodiment and second embodiment, but need not consider data packet recovery.
Therefore, according to the present invention, in the process of forming RLC PDU, for the segmentation of each SDU is provided with LI, be put among a plurality of PDU even if make SDU be divided into a plurality of SDU segmentations, each SDU also has only a LI.If Length Indication LI is placed on before first segmentation of SDU; In the header of each PDU, be provided with an OFFSET field and at least one LI field; First section the skew of first new SDU that the OFFSET field is represented to occur among the PDU, the LI field is represented the total length of new SDU.If Length Indication LI is placed on before last segmentation of SDU, in the header of each PDU, be provided with at least one LI field, the LI field is represented the length of last SDU segmentation.
So far invention has been described in conjunction with the preferred embodiments.Should be appreciated that those skilled in the art can carry out various other change, replacement and interpolations under the situation that does not break away from the spirit and scope of the present invention.Therefore, scope of the present invention is not limited to above-mentioned specific embodiment, and should be limited accompanying claims.
Claims (30)
1. method that generates protocol Data Unit comprises step:
The service data unit of input is divided at least one segmentation, so that said at least one segmentation is distributed at least one protocol Data Unit; And
For each service data unit is provided with a Length Indication field; Wherein, Offset field and at least one Length Indication field are set in the header of each protocol Data Unit; The skew of first segmentation of first the new service data unit that occurs in the said offset field Presentation protocol data unit, and be arranged on the total length that Length Indication field in the header of protocol Data Unit is represented said new service data unit.
2. method according to claim 1 wherein, is adjacent to after the Length Indication field if be filled in first segmentation in the protocol Data Unit, a service data unit, and the value of the offset field of said protocol Data Unit is set to 0.
3. method according to claim 1 wherein, has at protocol Data Unit under the situation of two or a byte underfill, and the byte of from next service data unit, getting the underfill number is filled in the last protocol Data Unit.
4. according to claim 2 or 3 described methods, wherein, the length of said Length Indication field is 2 bytes.
5. according to claim 2 or 3 described methods, wherein, the length of said offset field is 2 bytes.
6. method that generates protocol Data Unit comprises step:
The service data unit of input is divided at least one segmentation, so that said at least one segmentation is distributed at least one protocol Data Unit; And
For each service data unit is provided with a Length Indication field; Wherein, In the header of each protocol Data Unit, be provided with at least one said Length Indication field, be arranged on the length that said Length Indication field in the header of protocol Data Unit is represented last segmentation in said at least one segmentation.
7. method according to claim 6; Wherein, If the length of last segmentation of said service data unit than the little byte in the space of underfill in the protocol Data Unit, is filled into the last byte of next service data unit the afterbody of said protocol Data Unit.
8. method according to claim 6 wherein, if the length of last segmentation of said service data unit equals the free space in the last protocol Data Unit, is filled in the Length Indication field of said segmentation in the back protocol Data Unit.
9. according to claim 7 or 8 described methods, wherein, the length of said Length Indication field is 2 bytes.
10. according to claim 7 or 8 described methods, wherein, the length of said Length Indication field is 11 bits.
11. according to claim 7 or 8 described methods; Wherein, The value of said Length Indication field is defined as first retention; Represent that last protocol Data Unit is served last segmentation of data cell and just in time filled up, and in last protocol Data Unit, do not have the Length Indication field of the end position of indicating service data unit.
12. according to claim 7 or 8 described methods; Wherein, The value of said Length Indication field is defined as second retention; Last segmentation of expression service data unit is full of last protocol Data Unit, and has more a byte, and in last protocol Data Unit, does not have the Length Indication field of the end position of indicating service data unit; And a said byte that has more is as first byte of next protocol Data Unit.
13. according to claim 7 or 8 described methods; Wherein, The value of said Length Indication field is defined as the 3rd retention; Last segmentation of expression service data unit is full of last protocol Data Unit, and has more a byte, and in last protocol Data Unit, does not have the Length Indication field of the end position of indicating service data unit; And a said byte that has more is left in the basket.
14. according to claim 7 or 8 described methods, wherein, the value of said Length Indication field is defined as the 4th retention, representes that the remaining field in the current protocol Data Unit is a byte of padding.
15. an equipment that generates protocol Data Unit comprises:
Segmenting device is divided at least one segmentation with the service data unit of importing, so that said at least one segmentation is distributed at least one protocol Data Unit;
Calculation element, the skew of first segmentation of first the new service data unit that occurs in the calculating protocol Data Unit; And
Setting device; For each service data unit is provided with a Length Indication field; Wherein, Offset field and at least one Length Indication field are set in the header of each protocol Data Unit, and said offset field is represented said skew, and is arranged on the total length that Length Indication field in the header of protocol Data Unit is represented said new service data unit.
16. equipment according to claim 15; Wherein, Be adjacent to after the Length Indication field if be filled in first segmentation in the protocol Data Unit, a service data unit, the value of the offset field of the said protocol Data Unit of said setting device is set to 0.
17. equipment according to claim 15 wherein, has at protocol Data Unit under the situation of two or a byte underfill, the byte of from next service data unit, getting the underfill number is filled in the last protocol Data Unit.
18. according to claim 16 or 17 described equipment, wherein, the length of said Length Indication field is 2 bytes.
19. according to claim 16 or 17 described equipment, wherein, the length of said offset field is 2 bytes.
20. a base station comprises equipment as claimed in claim 15.
21. an equipment that generates protocol Data Unit comprises:
Segmenting device is divided at least one segmentation with the service data unit of importing, so that said at least one segmentation is distributed at least one protocol Data Unit;
Calculation element calculates the length of last segmentation in said at least one segmentation; And
Setting device; For each service data unit is provided with a Length Indication field; Wherein, In the header of each protocol Data Unit, be provided with at least one said Length Indication field, the said Length Indication field that is arranged in the header of protocol Data Unit is represented the length that said calculation element calculates.
22. equipment according to claim 21; Wherein, If the length of last segmentation of said service data unit than the little byte in the space of underfill in the protocol Data Unit, is filled into the last byte of next service data unit the afterbody of said protocol Data Unit.
23. equipment according to claim 21 wherein, if the length of last segmentation of said service data unit equals the free space in the last protocol Data Unit, is filled in the Length Indication field of said segmentation in the back protocol Data Unit.
24. according to claim 22 or 23 described equipment, wherein, the length of said Length Indication field is 2 bytes.
25. according to claim 23 or 24 described equipment, wherein, the length of said Length Indication field is 11 bits.
26. according to claim 23 or 24 described equipment; Wherein, Said Length Indication field value is defined as first and keeps value; Represent that last protocol Data Unit is served last segmentation of data cell and just in time filled up, and in last protocol Data Unit, do not have the Length Indication field of the end position of indicating service data unit.
27. according to claim 23 or 24 described equipment; Wherein, The value of said Length Indication field is defined as second retention; Last segmentation of expression service data unit is full of last protocol Data Unit, and has more a byte, and in last protocol Data Unit, does not have the Length Indication field of the end position of indicating service data unit; And a said byte that has more is as first byte of next protocol Data Unit.
28. according to claim 23 or 24 described equipment; Wherein, The value of said Length Indication field is defined as the 3rd retention; Last segmentation of expression service data unit is full of last protocol Data Unit, and has more a byte, and in last protocol Data Unit, does not have the Length Indication field of the end position of indicating service data unit; And a said byte that has more is left in the basket.
29. according to claim 23 or 24 described equipment, wherein, the value of said Length Indication field is defined as the 4th retention, representes that the remaining field in the current protocol Data Unit is a byte of padding.
30. a base station comprises equipment as claimed in claim 21.
Priority Applications (6)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200710038488ACN101272519B (en) | 2007-03-21 | 2007-03-21 | Method, device and base station for generating protocol data unit |
| EP08715017.3AEP2136525B1 (en) | 2007-03-21 | 2008-03-21 | Method, device and base station for generating protocol data unit |
| JP2009553893AJP5121854B2 (en) | 2007-03-21 | 2008-03-21 | Method and apparatus for generating PDUs, and base station of such method and apparatus |
| PCT/CN2008/000565WO2008113265A2 (en) | 2007-03-21 | 2008-03-21 | Method, device and base station for generating protocol data unit |
| US12/531,784US9756680B2 (en) | 2007-03-21 | 2008-03-21 | Method and apparatus for generating PDU and base station thereof |
| KR1020097021508AKR101554857B1 (en) | 2007-03-21 | 2008-03-21 | Method and apparatus for generating PDU and its base station |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200710038488ACN101272519B (en) | 2007-03-21 | 2007-03-21 | Method, device and base station for generating protocol data unit |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101272519A CN101272519A (en) | 2008-09-24 |
| CN101272519Btrue CN101272519B (en) | 2012-09-19 |
Family
ID=39766527
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200710038488AActiveCN101272519B (en) | 2007-03-21 | 2007-03-21 | Method, device and base station for generating protocol data unit |
Country Status (6)
| Country | Link |
|---|---|
| US (1) | US9756680B2 (en) |
| EP (1) | EP2136525B1 (en) |
| JP (1) | JP5121854B2 (en) |
| KR (1) | KR101554857B1 (en) |
| CN (1) | CN101272519B (en) |
| WO (1) | WO2008113265A2 (en) |
Families Citing this family (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| FR2943882A1 (en)* | 2009-03-27 | 2010-10-01 | Thomson Licensing | TRANSMITTING METHOD FOR WIRELESS NETWORK AND CORRESPONDING RECEPTION METHOD |
| US20120099468A1 (en)* | 2009-06-22 | 2012-04-26 | Alcatel Lucent | METHOD AND APPARATUS FOR CONTROLLING DOWNLINK DATA SYNCHRONIZATION IN AN eMBMS TRANSMISSION |
| CN102835150B (en)* | 2009-09-02 | 2015-07-15 | 苹果公司 | MAC packet data unit construction for wireless systems |
| US9414409B2 (en) | 2012-02-06 | 2016-08-09 | Samsung Electronics Co., Ltd. | Method and apparatus for transmitting/receiving data on multiple carriers in mobile communication system |
| CN108112067B (en)* | 2012-03-19 | 2021-05-11 | 三星电子株式会社 | Method and apparatus for establishing synchronization with added cells |
| CN103581168B (en)* | 2013-08-02 | 2016-06-22 | 中国科学技术大学苏州研究院 | Hidden information communication means based on IP fragmentation camouflage |
| CN104702576B (en)* | 2013-12-09 | 2018-02-09 | 腾讯科技（深圳）有限公司 | Voice transmission method, device and voice service system |
| JP2019502313A (en)* | 2015-12-23 | 2019-01-24 | ノキア ソリューションズ アンド ネットワークス オサケユキチュア | Method, apparatus and computer program product for PDU format setting by SDU segmentation |
| EP3449662A4 (en) | 2016-04-27 | 2019-12-18 | LG Electronics Inc. -1- | METHOD AND DEVICE FOR RECEIVING DATA UNITS |
| EP3469749B1 (en)* | 2016-06-09 | 2023-05-03 | Nokia Solutions and Networks Oy | Real-time segmentation |
| CN108012289B (en)* | 2016-11-01 | 2022-11-22 | 中兴通讯股份有限公司 | PDU (protocol data Unit) sending method and device and PDU receiving method and device |
| PL3537686T3 (en) | 2016-11-04 | 2023-09-25 | Beijing Xiaomi Mobile Software Co., Ltd. | Protocol data unit (pdu) packet generating method and apparatus |
| EP3782343B1 (en)* | 2018-04-19 | 2023-02-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Apparatuses and methods for handling data packets |
| WO2024007327A1 (en)* | 2022-07-08 | 2024-01-11 | Zte Corporation | Method of resource efficiency improvement |
| KR20250140586A (en)* | 2023-01-31 | 2025-09-25 | 삼성전자주식회사 | Method and device for handling segmentation in wireless communications |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1339903A (en)* | 2000-08-19 | 2002-03-13 | Lg电子株式会社 | Method of inserting length indicator in protocol data unit of radio link control |
| CN1913530A (en)* | 2005-08-09 | 2007-02-14 | 中兴通讯股份有限公司 | Sending and receiving method of non-conformation mode protocol data unit in radio link layer |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| FI106504B (en)* | 1998-10-06 | 2001-02-15 | Nokia Networks Oy | Procedure for segmenting data in a telecommunications system |
| US8880709B2 (en) | 2001-09-12 | 2014-11-04 | Ericsson Television Inc. | Method and system for scheduled streaming of best effort data |
| US8233462B2 (en)* | 2003-10-15 | 2012-07-31 | Qualcomm Incorporated | High speed media access control and direct link protocol |
| KR100913900B1 (en)* | 2005-05-04 | 2009-08-26 | 삼성전자주식회사 | Method and apparatus for transmitting and receiving packet data using predefined length indicator in mobile communication system |
| EP1764980B8 (en)* | 2005-09-20 | 2009-01-07 | Panasonic Corporation | Method and apparatus for packet segmentation and concatenation signaling in a communication system |
| US8503423B2 (en)* | 2007-02-02 | 2013-08-06 | Interdigital Technology Corporation | Method and apparatus for versatile MAC multiplexing in evolved HSPA |
- 2007
- 2007-03-21CNCN200710038488Apatent/CN101272519B/enactiveActive
- 2008
- 2008-03-21WOPCT/CN2008/000565patent/WO2008113265A2/enactiveApplication Filing
- 2008-03-21EPEP08715017.3Apatent/EP2136525B1/enactiveActive
- 2008-03-21KRKR1020097021508Apatent/KR101554857B1/enactiveActive
- 2008-03-21USUS12/531,784patent/US9756680B2/enactiveActive
- 2008-03-21JPJP2009553893Apatent/JP5121854B2/enactiveActive
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1339903A (en)* | 2000-08-19 | 2002-03-13 | Lg电子株式会社 | Method of inserting length indicator in protocol data unit of radio link control |
| CN1913530A (en)* | 2005-08-09 | 2007-02-14 | 中兴通讯股份有限公司 | Sending and receiving method of non-conformation mode protocol data unit in radio link layer |
Non-Patent Citations (2)
| Title |
|---|
| DIS 8473 Editor.Final Text of DIS 8473, Protocol for Providing the Connectionless- mode Network Service.《ISO TC97/SC6/N 3998》.1986,第6.7节,第7.4-7.4.3节.* |
| DIS8473Editor.FinalTextofDIS8473 Protocol for Providing the Connectionless- mode Network Service.《ISO TC97/SC6/N 3998》.1986 |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2008113265A2 (en) | 2008-09-25 |
| US20100111110A1 (en) | 2010-05-06 |
| EP2136525A4 (en) | 2011-08-03 |
| EP2136525A1 (en) | 2009-12-23 |
| JP5121854B2 (en) | 2013-01-16 |
| US9756680B2 (en) | 2017-09-05 |
| KR101554857B1 (en) | 2015-09-22 |
| JP2010521903A (en) | 2010-06-24 |
| CN101272519A (en) | 2008-09-24 |
| KR20090127350A (en) | 2009-12-10 |
| EP2136525B1 (en) | 2016-01-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101272519B (en) | Method, device and base station for generating protocol data unit | |
| US8005085B2 (en) | Method for distribution of data packets in a single frequency mobile communication network, an access network node, a base station and a single frequency mobile communication network therefor | |
| CN101247315B (en) | Content synchronization method and apparatus for single-frequency network transmission | |
| CN101529759B (en) | Distribution of broadcast/multicast data in telecommunications systems | |
| CN101741538B (en) | Synchronous dispatching method | |
| CN101395824A (en) | Quasi-synchronous transmission in cellular networks | |
| ES2404822T3 (en) | Procedure for sending and receiving multimedia operation data, base station device and user device | |
| CN101931884B (en) | A data synchronization method and system | |
| CN101651510A (en) | Method and device for recovery processing in service data synchronous transmission | |
| CN101651536A (en) | Method and system for realizing synchronization of control sequence numbers | |
| CN101370165A (en) | Data packet transmission method for multimedia broadcasting service | |
| CN101364990A (en) | A way to reduce data header overhead | |
| CN104754521A (en) | Message transmitting method, wireless access point, wireless controller and system | |
| CN101651517A (en) | Method and device for detecting loss of burst sequences | |
| CN101047492B (en) | Method and system for implementing synchronous RLC serial number between radio network controller | |
| CN101500193B (en) | Method for multimedia broadcast multicast service data synchronization between RNCs | |
| GB2447673A (en) | Identification of multiplexed multimedia broadcast multicast service from a central node to a UMTS evolved Node B (eNB) | |
| CN101414959B (en) | System, method and apparatus for synchronizing TDD multimedia broadcast and multicast service | |
| CN102014339A (en) | Method, device and system for configuring multimedia broadcast multicast service (MBMS) synchronization | |
| CN101651605A (en) | Method and system for transmitting and receiving data | |
| CN101662725B (en) | Method, system and device for implementing synchronous transmission between RNCs | |
| CN101267247B (en) | Iu interface time synchronization method and device | |
| CN100512254C (en) | Method for transmitting real-time information between indoor unit and outdoor unit | |
| CN103796039A (en) | Channel damage simulation device of terrestrial digital TV transmission distribution network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C53 | Correction of patent of invention or patent application | ||
| CB02 | Change of applicant information | Address after:201206 Pudong New Area Jinqiao Export Processing Zone, Nanjing Road, No. 388, Shanghai Applicant after:Shanghai Alcatel-Lucent Co., Ltd. Address before:201206 Pudong New Area Jinqiao Export Processing Zone, Nanjing Road, No. 388, Shanghai Applicant before:Beier Aerkate Co., Ltd., Shanghai | |
| COR | Change of bibliographic data | Free format text:CORRECT: APPLICANT; FROM: BEIER AERKATE CO., LTD., SHANGHAI TO: SHANGHAI ALCATEL-LUCENT CO., LTD. | |
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder | Address after:201206 Pudong New Area Jinqiao Export Processing Zone, Nanjing Road, No. 388, Shanghai Patentee after:Shanghai NOKIA Baer Limited by Share Ltd Address before:201206 Pudong New Area Jinqiao Export Processing Zone, Nanjing Road, No. 388, Shanghai Patentee before:Shanghai Alcatel-Lucent Co., Ltd. |