CN1780291B - A Method for Segmentation Concatenation and Reorganization of Data - Google Patents

Abstract

The present invention discloses a method for segmented and concatenated data. The key is that when the process of segmenting and cascading the current service data unit SDU into a packet data unit PDU needs to be interrupted, the sender will instruct the current SDU to be interrupted. The interrupted special identifier is encapsulated in the PDU and sent. The method includes: interrupting the segmented concatenation of the current SDU, segmenting and concatenating the SDUs that need to be inserted into a PDU for transmission, and then sending the interrupted current SDU The remaining data is segmented and concatenated, assembled into PDUs and sent. The invention also discloses a data recombination method at the same time. By adopting the data segmentation cascading and recombination method of the invention, the receiver can reorganize the data correctly, thereby improving the reliability of information transmission.

Description

A Method for Segmentation Concatenation and Reorganization of Data

technical field

The invention relates to information transmission technology, in particular to a method for cascading and recombining data segments.

Background technique

With the development of third-generation mobile communication technology, people's demand for mobile communication is no longer satisfied with voice services. Since the third-generation mobile communication can provide services with higher data rates than the second-generation mobile communication, a large number of multimedia services Emerged, such as: video calls, picture downloads, high-speed browsing Internet services and other services. Among them, some application services require multiple users to receive the same data at the same time, such as: video on demand, TV broadcast, video conferencing, online education, interactive games and so on.

In order to effectively utilize the resources of the mobile communication network, the third-generation mobile communication introduces the concepts of multicast and broadcast. Multicast and broadcast are technologies for transmitting data from one data source to multiple targets. Specifically, the WCDMA/GSM global standardization organization 3GPP proposed a multimedia broadcast/multicast service (MBMS, Multimedia Broadcast/Multicast Service). The so-called MBMS is to provide a data source in a mobile communication network to send data to multiple users. Multi-point service realizes network resource sharing and improves the utilization rate of network resources, especially air interface resources. The MBMS defined by 3GPP can not only realize multicast and broadcast of plain text low-rate messages, but also realize multicast and broadcast of high-speed multimedia services.

FIG. 1 is a schematic diagram of a wireless network structure supporting broadcast/multicast services. As shown in FIG. 1, in the existing 3GPP, the wireless network structure supporting broadcast/multicast services is a broadcast/multicast service server (BM-SC) 101, BM-SC 101 is connected with TPF gateway GPRS support node (GGSN, Gateway GPRS Support Node) 102 through Gmb interface or Gi interface, one BM-SC 101 can be connected with multiple TPF GGSN102; TPF GGSN 102 is connected with service through Gn/Gp interface GPRS support node (SGSN, ServingGPRS Support Node) 103 links to each other, and a GGSN 102 can link to each other with a plurality of SGSN 103; 104 is connected with User Terminal (UE) 106 through Uu interface, and SGSN 103 also can be connected with Global System for Mobile Communications (GSM) Enhanced Radio Access Network (GERAN) 105 through Iu/Gb interface, and then GERAN 105 is connected with UE 107 through Um interface connected. Wherein, the GGSN and the SGSN belong to the nodes in the core network (CN) in the wireless network.

From the network structure shown in Figure 1, it can be seen that in order to support MBMS services, a mobile network functional entity—broadcast and multicast service center, namely BM-SC, is added in the third generation mobile communication system, and the BM-SC is The content provider's entrance is used to authorize and initiate the MBMS bearer service in the mobile network, and transmit MBMS content according to the predetermined time plan. In addition, MBMS-related functions are added to functional entities such as UE, UTRAN, GERAN, SGSN, and GGSN.

MBMS includes a multicast mode and a broadcast mode. In the multicast mode, a user is required to subscribe to a corresponding multicast group, activate a service, and generate corresponding charging information. Due to the difference in business requirements between the multicast mode and the broadcast mode, the respective business processes are also different, as shown in Figure 2 and Figure 3, Figure 2 is a schematic diagram of the business process of the MSMS multicast mode, and Figure 3 is a schematic diagram of the MSMS broadcast mode Business process diagram.

As shown in Figure 2, the processing process involved in the MBMS multicast service includes: Subscription, Service announcement, Joining, Session Start, MBMS notification, data transmission (Data transfer), session end (SessionStop) and user exit (Leaving). Among them, the subscription process is used to allow users to subscribe to the required MBMS services in advance; the service announcement process is used to announce the currently available services by the BM-SC; the user joining process is the MBMS multicast service activation process. During the joining process, the UE notifies The network itself is willing to become a member of the current multicast group and receive multicast data of the corresponding service. The joining process will create an MBMS UE context for recording UE information in the network and UEs joining the multicast group; during the session start process, the BM-SC Prepare for data transmission, notify the network to establish the bearer resources of the corresponding core network and access network; the MBMS notification process is used to notify the UE that the MBMS multicast session is about to start; during the data transmission process, the BM-SC passes the bearer resources established during the session start process Resources transmit data to UE. There are two modes of MBMS service transmission between UTRAN and UE: point-to-multipoint (PTM) mode and point-to-point (PTP) mode. The PTM mode sends the same data through the MTCH logical channel. The broadcast service or the UE interested in the broadcast service can receive it. The PTP mode sends data through the DTCH logical channel, and only one corresponding UE can receive it; the session end process is used to release the bearer resources established in the session start process; the user exit process Make the subscribers in the group leave the multicast group, that is, the user no longer receives multicast data, and this process will delete the corresponding MBMS UE context.

As shown in Fig. 3, the process involved in the MBMS broadcast service is similar to that of the MBMS multicast service, except that before the session starts, there is no need to execute the subscription process and the user join process, and after the session ends, the user logout process does not need to be performed.

In the data transmission stage of multicast and broadcast services, there are two modes for MBMS service to transmit information between UTRAN and UE: point-to-multipoint (PTM) mode and point-to-point (PTP) mode. Among them, the PTM mode sends the same data through the MBMS point-to-multipoint traffic channel (MTCH), and all UEs that join the multicast service or are interested in the broadcast service can receive it; the PTP mode sends data through the dedicated traffic channel (DTCH), and only A corresponding UE can receive it.

In the MBMS PTM transmission mode, related radio control information includes service information, access information, radio bearer information, frequency layer convergence (FLC) information, etc. point control channel (MCCH) transmission. MCCH information is transmitted based on a fixed scheduling method, and in order to improve reliability, UTRAN will repeat MCCH information. Figure 4 is a schematic diagram of the transmission scheduling of MCCH information, as shown in Figure 4, all the blocks in the figure are MCCH information, the cycle of repeatedly sending MCCH information is a repetition period, and complete MCCH information will be sent periodically in the repetition period; The modification cycle is defined as an integer multiple of the repetition cycle, and the MCCH information must be modified in each modification cycle; MBMS access information can be sent periodically in the access information cycle, and the access information cycle is repeated Integer division of period.

MCCH information is further divided into critical information (Critical Info) and non-critical information. The critical information is composed of MBMS neighboring cell information, MBMS service information, and MBMS radio bearer information, and is information that needs to be sent repeatedly periodically. The content sent in the cycle remains unchanged, and can only be modified when the MCCH information is sent for the first time in the modification cycle; non-standard information refers to access information, which does not need to be sent repeatedly periodically, and can be modified in any Time modification. In Figure 4, the black-filled squares are non-standard information, the unfilled squares are standard information, and the squares filled with forward and backward slashes are non-standard information and standard information with changed content.

The protocol stack structure of the MCCH is shown in Figure 5. The protocol units of the MCCH from top to bottom are: RRC layer, radio link control layer (RLC), medium access control layer (MAC), and physical layer (PHY). Among them, the mapping relationship between the MAC layer logic channel and the physical layer FACH channel is shown in Figure 6. In the existing system, MCCH information, that is, MBMS control information, is mapped to the forward access channel (FACH) for transmission. The RLC layer uses the unacknowledged mode (UM) to transmit MCCH information. In the prior art, the data transmission process of the UM mode is shown in FIG. 7. The transmission method of MBMS control information mainly includes the transmission process of the sender (Sender) RLCUM entity And the receiving process of the receiver (Receiver) RLCUM entity. One or several PDUs can be sent in each transmission time interval, and the MAC determines the size and number of PDUs in each transmission time interval.

The sending process of the existing unacknowledged mode data protocol data unit (UMD PDU) is: after the sender RLC UM entity receives the unacknowledged mode data transmission request from the upper layer, the sender schedules the RLC service data unit (SDU) received from the upper layer If one or more RLC SDUs have been scheduled to be sent, the RLC UM entity first notifies the lower layer to receive data including the number and size of SDUs from the upper layer; then the RLC UM entity segments the SDU according to the PDU size indicated by the lower layer, If possible, cascading is also performed; after that, set the sequence number field to be VT(US), and set the length indication field for each SDU ending in the UMD PDU; finally, submit the requested number of UMD PDUs to the lower layer, that is, the MAC layer, and VT(US) is updated for each UMD PDU submitted to lower layers, while buffering SDUs not submitted to lower layers.

The receiving process of UMD PDU is: after receiving a group of UMD PDUs from the lower layer, the receiving RLC UM entity updates VR(US) according to the received UMD PDUs; if the update step of VR(US) is not equal to 1 , then discard the segmented SDU in the lost UMD PDU, otherwise, reassemble the received UMD PDU into an RLC SDU, and submit the reassembled RLC SDU to the upper layer, namely the RRC layer.

Among them, the format of UMD PDU is shown in Table 1:

Table I

In the UMD PDU format of the RLC protocol, the length indicator (LI, Length Indicator) is used to mark the end position of the RLC SDU in the PDU. In addition to some predefined special values, LI indicates the end position of the RLC header in the UMD PDU to the RLC SDU is the number of bytes in the last byte of this PDU, and LI is 7 or 15 bits. For UM mode, if the maximum UMD PDU size <= 125 bytes, use 7-bit LI, otherwise use 15-bit LI. The meaning of each special value of 7-bit LI and 15-bit LI is shown in Table 2 and Table 3 respectively, Table 2 is the description of the meaning of each special value of 7-bit LI, and Table 3 is the description of the meaning of each special value of 15-bit LI .

bit describe 0000000 The previous RLC PDU was exactly filled by an RLC SDU, and there was no length indicator in the previous RLC PDU to mark the end of the SDU 1111100 UMD PDU: The first byte of this RLC PDU is the first byte of an RLC SDU; AMD PDU: Reserved (in the current version, PDUs with this value are discarded) 1111101 Reserved (in the current version, PDUs with this value are discarded) 1111110 AMD PDU: The rest of the PDU contains a cascade status protocol data unit (piggybacked STATUS PDU); UMD PDU: Reserved (currently In the version of , PDUs with this value are discarded) 1111111 The rest of the RLC PDU is padding bits, and the padding bit length can be zero

Table II

bit describe 000000000000000 The previous RLC PDU was exactly filled by an RLC SDU, and there was no LI in the previous RLC PDU to mark the end of the SDU 111111111111011 There is one byte left after the last segment of the RLC SDU fills the previous RLC PDU, there is no LI in the previous RLC PDU to mark the end of the RLC SDU, and the last byte in the previous PDU is ignored 11111111111100 AMD PDU: The rest of the PDU contains a cascade status protocol data unit (piggybacked STATUS PDU); UMD PDU: Reserved (in the current version, PDUs with this value are discarded) 11111111111101 Reserved (in the current version, PDUs with this value are discarded) 111111111111110 AMD PDU: The rest of the PDU contains a cascade status protocol data unit (piggybacked STATUS PDU); UMD PDU: Reserved (in the current version, PDUs with this value are discarded) 111111111111111 The rest of the RLC PDU is padding bits, and the padding bit length can be zero

Table three

At present, according to the scheduling method of MCCH information, in order to ensure the periodic transmission of access information, and when both standard information and non-standard information need to be processed by RLC UM at the same time, non-standard information may interrupt the transmission of standard information, as shown in the figure 8. In Figure 8, each block represents a PDU, the blocks with sequence numbers 0 and 8 are PDUs containing non-standard information SDUs, the blocks with sequence numbers 1 to 6 are PDUs containing standard information SDUs, and the blocks with sequence numbers 7, Blocks with sequence numbers 9 to 14 are PDUs containing the same criterion information SDU. In order to ensure that the non-standard information in the second access information cycle is sent in time, when the RLC UM receives an SDU containing non-standard information, it will segment the SDU, encapsulate it into an RLC PDU with a sequence number of 8, and send it. The criteria information that has not been transmitted continues to be sent in subsequent PDUs, that is, they are encapsulated into RLC PDUs with sequence numbers 9, 10, 11, 12, 13, and 14, respectively.

However, for this process of interrupting the transmission of standard information and inserting non-standard information transmission, some problems will occur at the receiver: if the PDU with the serial number 8 is not received correctly by the receiver because of a transmission error, even if the serial number is The PDUs of 7, 9, 10, 11, 12, 13, and 14 are all received correctly, and the criterion information SDU contained in these PDUs cannot be reassembled, because the receiver does not know whether the lost No. 8 PDU is other SDUs or the criterion A segment of an Information SDU. In this way, the receiver cannot correctly identify and reassemble, thereby reducing the reliability of information transmission.

Contents of the invention

In view of this, the main purpose of the present invention is to provide a method for cascading data segments, which is convenient for the receiver to determine whether reassembly can be performed, thereby improving the reliability of information transmission.

Another object of the present invention is to provide a data reorganization method so that the receiver can reorganize the data correctly, thereby improving the reliability of information transmission.

In order to achieve the above object, technical solution of the present invention is achieved in that way:

The present invention provides a method for data segmentation and concatenation. When the process of segmenting and concatenating the current service data unit SDU into a packet data unit PDU needs to be interrupted, the sender will indicate the special mark that the current SDU is interrupted. Encapsulated and sent in a PDU, the method includes: interrupting the segmented concatenation of the current SDU, segmenting and concatenating the SDU to be inserted into a PDU for transmission, and then dividing the remaining data of the interrupted current SDU The segments are concatenated and assembled into PDUs for transmission.

Wherein, the special identification is a length indication field whose value is a reserved special value in the PDU, and different reserved special values represent different numbers of inserted PDUs; or one or more length indications in the PDU that take the same reserved special value field, the number of length indication fields is equal to the number of inserted PDUs; or for more than one length indication field with different reserved special values in the PDU, the number of length indication fields is equal to the number of inserted PDUs; The value is a length indicator field with an undefined special value, and different undefined special values indicate different numbers of inserted PDUs; or one or more length indicator fields that take the same undefined special value in a PDU, and the number of length indicator fields Equal to the number of inserted PDUs; or more than one length indication field with different undefined special values in the PDU, the number of length indication fields is equal to the number of inserted PDUs; or the value in the PDU is reserved for special values and undefined A combination of special values indicates the length of the field.

The method further includes: setting in the PDU an interrupt number field indicating the number of PDUs assembled from SDUs to be inserted, and the special identification is the length indication field and the interrupt number field in the PDU that take special values. Wherein, the special value of the length indication field is a special value reserved for the length indication field in the PDU; or a special value not defined for the length indication field in the PDU.

In the above solution, the reserved special value is 1111101 or 11111111111101.

In the above scheme, the encapsulation of the special identifier in the PDU is specifically: encapsulating the special identifier in the PDU after the PDU assembled from the SDU that needs to be inserted; or, encapsulating the special identifier in the PDU assembled from the SDU that needs to be inserted in the previous PDU.

In the above-mentioned scheme, the method also includes:

The receiver judges whether the currently received PDU carries a special identifier. If so, it determines the PDU required to recombine the SDU according to the special identifier, and completes the reassembly of the SDU according to the determined PDU; otherwise, the data in the received PDU is SDUs are reassembled in sequence.

Wherein, said encapsulating the special identifier in the PDU is specifically: encapsulating the special identifier in the PDU after the PDU assembled from the SDU that needs to be inserted; or, said encapsulating the special identifier in the PDU is specifically: encapsulating the special identifier in the PDU Encapsulated in the PDU before the PDU assembled from the SDU that needs to be inserted.

The present invention also provides a method for data reorganization, the method comprising:

The receiver judges whether the currently received PDU carries a special identifier. If it carries it, it determines the PDU that is not related to the SDU corresponding to the reorganized current PDU according to the special identifier, and then ignores the determined PDU to complete the reorganization of the SDU corresponding to the current PDU; otherwise, Reassemble the data in the received PDU into SDU in order.

Wherein, the special identifier is one or more length indication fields that take special values in the PDU; then the receiver determines the number of PDUs that are not related to the SDU corresponding to the reorganized current PDU according to the number of length indication fields that take special values in the PDU or a length indication field with a special value in the PDU; then the receiver determines the number of PDUs that have nothing to do with the SDU corresponding to the recombined current PDU according to the special value of the length indication field in the PDU; or the length indication field in the PDU The combination of the length indication field of a special value and the interrupt number field; then the receiver determines the number of PDUs that are not related to the SDU corresponding to the reassembled current PDU according to the value of the interrupt number field in the PDU. Wherein, the special value of the length indication field is a special value reserved for the length indication field, or a special value not defined for the length indication field, or a combination of both. The reserved special value is 1111101 or 11111111111101.

In the above solution, the PDU not related to the SDU corresponding to the recombined current PDU is located before the current PDU, or located after the current PDU.

In the data segment concatenation and reassembly method provided by the present invention, the sender indicates whether the adjacent PDU before the current PDU or the adjacent PDU after the current PDU is a segment containing other SDUs through a special identification after or before the inserted PDU; Yes, when the receiver reassembles the data, it judges whether each PDU carries a special identifier, and if so, determines how to perform data reassembly according to the instruction of the special identifier. The invention can ensure that the receiver correctly identifies and reassembles data, avoids the problem that other correctly received PDUs cannot be reassembled because the inserted PDU has not been received, and thus improves the reliability of information transmission.

The method of the present invention can use the special value LI in the PDU format as the special mark, and the special value can directly use the special value reserved by LI, or use the special value not defined in LI; the special mark can be carried before inserting the PDU , the special identification can also be carried behind the inserted PDU; the special identification can further indicate the number of inserted PDUs. In a word, there are various ways to use it. Therefore, the implementation of the method of the present invention is flexible, convenient and simple.

In addition, the method of the present invention is not limited to the transmission of MBMS information, as long as the environment that requires the RLC UM entity to complete data transmission can adopt the above implementation scheme, and the scope of application is wider.

Description of drawings

Fig. 1 is a schematic structural diagram of a wireless network supporting broadcast/multicast services;

Fig. 2 is a schematic diagram of the service flow of the MSMS multicast mode;

FIG. 3 is a schematic diagram of a service flow in the MSMS broadcast mode;

FIG. 4 is a schematic diagram of transmission scheduling of MCCH information;

Fig. 5 is the protocol stack structural diagram of MCCH;

Fig. 6 is a mapping relationship diagram of the logical channel of the MAC layer and the FACH channel of the physical layer;

FIG. 7 is a transmission mode diagram of MBMS control information;

FIG. 8 is a transmission schematic diagram of sending PDUs containing different information in the prior art;

Fig. 9 is a processing flowchart of the sender in the transmission method of the present invention;

Fig. 10 is a flow chart of the receiver's processing in the transmission method of the present invention.

Detailed ways

The core idea of the present invention is to use a method of carrying a special identifier in the PDU to indicate whether the current concatenated SDU is interrupted. For the sender, if the current segmented concatenated SDU is interrupted, it will carry a special identifier for indication; for the receiver, it is necessary to detect whether each PDU contains a special identifier to determine how to reassemble the segmented SDU. associated SDUs.

Wherein, the special identifier may use a length indication field with a special value in the PDU format, and the special identifier may be carried in a PDU before the inserted PDU, or in a PDU after the inserted PDU. When the special value of LI is used, the special value reserved by LI can be used directly, or the special value not defined in LI can be used, or the combination of reserved special value and undefined special value can be used; if more than one PDU is inserted, the special identification The number of inserted PDUs may be further indicated.

Based on the above ideas, the processing flow of the sender is shown in Figure 9, including the following steps:

Steps 901-904: The sender RLC UM entity receives the SDU sent by the upper layer, and in the process of segmenting and concatenating the received SDU into a PDU, judges whether there is currently an SDU that needs to be inserted, such as a non-standard information SDU , if there is, interrupt the segmentation concatenation of the SDU currently being processed, and at the same time assemble the SDUs that need to be inserted into PDUs through segmentation concatenation processing and send them out. After sending the PDUs that need to be inserted into the SDUs, then The remaining data of the interrupted segmented concatenated SDU is segmented and concatenated, assembled into a PDU and sent out; and, during the interrupt insertion process, the sender RLC UM entity uses a special identifier to indicate that the current SDU is interrupted, specifically: Encapsulate the special identifier indicating that the current SDU is interrupted into a PDU and send it to the receiver; if there is no SDU to be inserted, the RLC UM entity of the sender performs normal segment concatenation on the received SDU, assembles it into a PDU and sends it , that is: sequentially segment and concatenate the received SDUs, assemble them into PDUs and send them. Here, the PDU assembled from the SDUs that need to be inserted may be referred to as an inserted PDU.

The processing flow of the receiver is shown in Figure 10, including the following steps:

Steps 1001-1003: Determine whether the currently received PDU carries a special identifier. If so, determine which PDUs are irrelevant to recombining the current SDU according to the special identifier, then ignore the determined PDU, and complete the current SDU with the relevant PDU. Reassemble; otherwise, reassemble the data in the received PDU into the SDU in sequence. Here, the number of inserted PDUs can be determined first according to the special identifier, and then it can be determined which PDUs are unrelated to reassembling the current SDU.

In the processing process of the receiver in the present invention, the receiver can determine whether the data in the unreceived PDU belongs to the SDU that needs to be reassembled according to the special identification. Specifically, if you find an unreceived PDU, you can first judge whether a PDU carries a special identifier. If there is a special identifier, it means that there is an inserted PDU. Then, according to the special identifier, it is further judged whether the unreceived If the inserted PDU belongs to, the SDU that needs to be reassembled will not be affected, and the reassembly can continue to be completed. If it does not belong, it means that some data of the SDU that needs to be reassembled is lost, and the corresponding SDU cannot be reassembled; if there is no special mark, it means that reassembly is required Part of the data in the SDU is lost, and the corresponding SDU cannot be reassembled.

The specific implementation of the method of the present invention is further described below by taking the special value reserved by LI in the PDU format as an example.

Embodiment one:

In this embodiment, the special identifier is located in the PDU after the inserted PDU, the special identifier is the length indication field in the UMD PDU, and the value of the length indication field is a reserved special value 1111101 or 11111111111101 to indicate that the length is included The previous PDU of the indicated PDU contains segments inserted into other SDUs, that is to say, the PDU carrying a special identifier does not need to be reassembled with its previous PDU. Here, the previous PDU refers to a PDU whose sequence number is one less than the current PDU.

When the sender encapsulates the UMD PDU, if it finds that the previous PDU contains segments inserted into other SDUs, the sender sets the value of the first length indication field of the current PDU to 1111101 or 11111111111101.

Correspondingly, when the receiver reassembles the UMD PDU into an SDU, if it finds that the value of the first length indication field of a received PDU is 1111101 or 11111111111101, it considers ignoring the previous PDU of the PDU for reassembly operation.

As a specific example, a 7-bit LI is used in this example. RLC sends at most one UMDPDU per TTI. The UMD PDU size is 128bit. RLC first receives a 200bit SDU1. In the first TTI, a PDU is assembled and the first segment of SDU1 is sent. The sequence number (SN) is 10. The E field of the PDU is 0, indicating that there is no length indication field, and the Data field contains the first segment of SDU1 with a length of 120 bits. The format of the PDU is shown in Table 4.

Table four

In the second TTI, due to the arrival of a new high-priority SDU2, it is necessary to interrupt the sending of SDU1 and send SDU2 first. Assuming that the size of SDU2 is 48 bits, the content of the PDU with the sequence number 11 sent in the second TTI is shown in Table 5, where the E field is 1, indicating that the next field is a length indication field.

Table five

In the third TTI, continue to send the content of SDU1. Since the PDU with the sequence number 11 is an inserted PDU, the content of the PDU with the sequence number 12 is shown in Table 6.

SN='0001100' E='1' LI='1111101' E='1'

SN='0001100' E='1' LI='0001010' E='1' LI='1111111' E='0'

Data(80bits) PAD(24bits)

Table six

According to the above sending method, even if the receiver does not receive the PDU with the serial number 11, as long as the PDU with the serial number 10 and the serial number 12 are received correctly, then according to the length of the PDU with the serial number 12, the indicated domain value is 1111101, It can be judged that the PDU with the serial number 11 is an inserted PDU, regardless of its reassembly with the PDU with the serial number 10 and the serial number 12, so the 120bits and sequence of the Data part in the PDU with the serial number 10 The 80 bits of the Data part in the PDU numbered 12 are reassembled into one SDU, and SDU1 is obtained.

The size of the SDU inserted in this embodiment is limited to: the SDU that can be accommodated by the data field part of a UMD PDU.

Embodiment two:

The implementation principle of this embodiment is basically the same as that of Embodiment 1, except that the value in the length indication field is different. In this embodiment, the value of the length indication field is a reserved special value 1111110 or 111111111111110 to indicate the PDU containing the length indication The previous PDU contains segments that are inserted into other SDUs.

Alternatively, use other special LI values such as the currently undefined value 0000001 or 0000000000000001 to indicate that the previous PDU containing the PDU indicated by the length contains segments inserted into other SDUs.

Embodiment three:

In this embodiment, on the basis of the first and second embodiments, the limit of the size of the inserted SDU is expanded to: SDUs that can be accommodated by the data fields of two UMD PDUs.

This embodiment uses two special values of LI at the same time to indicate that the previous PDU containing the PDU indicated by the length contains the segment inserted into other SDUs, and the second PDU before the PDU containing the indicated length contains the is a segment inserted into other SDUs. That is to say, in this embodiment, the special identifiers are two length indication fields that respectively take these two special values. Specifically: for the 7-bit LI, use 1111101 to indicate that the previous PDU of the PDU containing the special identifier contains the segment inserted into other SDUs, and use 1111110 to indicate that the second PDU in front of the PDU containing the special identifier contains the inserted Segmentation of other SDUs; for 15-bit LI, use 11111111111101 to indicate that the previous PDU of the PDU containing the special identifier contains a segment inserted into other SDUs, and use 11111111111110 to indicate that the second PDU in front of the PDU containing the special identifier contains is inserted into segments of other SDUs.

For the receiver, it will know that two PDUs containing other SDUs are inserted before the currently received PDU according to the two special values of LI, and ignore the two PDUs in front of the current PDU during reassembly.

Still taking the specific example in Embodiment 1 as an example, if the size of SDU2 exceeds the length that the data field of a PDU can accommodate, but within the length range that the data fields of two PDUs can accommodate, the sequence number 11 and the sequence The PDU with the number 12 will be used to send the segment of SDU2, and the segment with the sequence number 13 will continue to send the segment of SDU1. Then, the content of the PDU with the sequence number 13 is shown in Table 7.

Table seven

Correspondingly, according to the special identification, the receiver will know that the PDUs with sequence numbers 11 and 12 should be ignored, and only the PDUs with sequence numbers 10 and 13 should be reassembled to obtain SDU1.

Embodiment four:

The implementation principle of this embodiment is basically the same as that of the third embodiment, except that the values in the length indication field adopted have different meanings. In this embodiment, for the 7-bit LI, 1111110 is used to indicate that the previous PDU of the PDU containing the special identifier contains a segment inserted into other SDUs, and 1111101 is used to indicate that the previous second PDU of the PDU containing the special identifier contains It is a segment inserted into other SDUs; for 15-bit LI, use 11111111111110 to indicate that the previous PDU of the PDU containing the special identifier contains segments inserted into other SDUs, and use 111111111111101 to indicate the second preceding PDU containing the special identifier PDUs contain segments that are inserted into other SDUs.

Or, use any other two special length indicator field values such as currently undefined special values to indicate that the previous PDU of the PDU containing the special identifier contains segments inserted into other SDUs, and the PDU containing the special identifier The second PDU in front of the PDU contains segments that are inserted into other SDUs.

Of course, a special value reserved by LI and an undefined special value can also be used at the same time.

Embodiment five:

Since the SDUs to be inserted may be segmented and assembled into two or more PDUs, that is to say, the number of inserted PDUs is two or more. In view of this situation, in this embodiment, a reserved special value or an undefined special value of a certain length indication field can be directly used to indicate the number of PDUs inserted before the current PDU. For example: use 1111101 to indicate that one PDU is inserted before the current PDU; use 1111110 to indicate that two PDUs are inserted before the current PDU; use 0000001 to indicate that three PDUs are inserted before the current PDU, and so on. In this embodiment, the special identifier is a length indication field whose value is a reserved special value, or a length indication field whose value is an undefined special value, and different special values represent different numbers of inserted PDUs.

Embodiment six:

Since the SDUs to be inserted may be segmented and assembled into two or more PDUs, that is to say, the number of inserted PDUs is two or more. In view of this situation, this embodiment may indicate the number of PDUs inserted before the current PDU by repeatedly using a length indication field with a reserved special value. In this embodiment, the special identifier is a plurality of length indication fields that take the same reserved special value, for example: the value of the length indication field is a reserved special value 1111110, and there are four inserted PDUs, then, in the format of the current PDU, After the serial number SN, LI="1111101" is repeated four times.

Of course, special values reserved in other length indication fields can also be reused, for example: 1111110 or 111111111111110. Alternatively, reuse the length to indicate any one of the undefined special values in the field.

Then, after receiving the current PDU, the receiver determines the number of PDUs that can be ignored before the current PDU according to the number of reserved special values or undefined special values used in the length indication field.

Embodiment seven:

Since the SDUs to be inserted may be segmented and assembled into two or more PDUs, that is to say, the number of inserted PDUs is two or more. In view of this situation, in this embodiment, by using more than two undefined special values in the length indication fields, or a combination of reserved special values and undefined special values in more than two length indication fields, each special value It is used to indicate a PDU inserted before the current PDU. In this embodiment, the special identifier is a plurality of length indication fields that take different undefined special values, or a plurality of length indication fields that take different combinations of undefined special values and reserved special values.

Then, after receiving the current PDU, the receiver determines the number of PDUs that can be ignored before the current PDU according to the number of reserved special values or undefined special values used in the length indication field.

Embodiment eight:

Since the SDUs to be inserted may be segmented and assembled into two or more PDUs, that is to say, the number of inserted PDUs is two or more. In view of this situation, the present embodiment adds a new domain in the UMD PDU, and the newly added domain is used to identify the number of PDUs inserted in front of it. , the special identifier is located in the PDU following the inserted PDU. For example: add an interrupt number (Interrupt number) field, then the modified UMD PDU format is shown in Table 8:

table eight

The meaning of the modified E field is shown in Table 9:

bit describe 0 The next field is data, piggybacked status PDU or padding bits 1 The next field is the length indication and extension bits or the number of interrupts and extension bits

Table nine

At the same time, a special length indication value is required to indicate that the next field is the number of interruption field. For example: 1111101 or 111111111111101 is used to indicate that the next field is the interrupt number field.

When the sender encapsulates the UMD PDU, if it finds that there is a PDU containing segments inserted into other SDUs, the sender will set the first length indication field value of the current PDU to 1111101 or 111111111111101; at the same time, the next encapsulation interrupt number field, The value of this field is equal to the number of previously inserted PDUs.

Correspondingly, when the receiver reassembles the SDU according to the UMD PDU, if it finds that the value of the first length indication field of a received PDU is 1111101 or 111111111111101, it will read the next field at the same time, that is, the interrupt number field, and determine How many PDUs are inserted in the front, and the PDUs inserted in front of the PDU are ignored when the current PDU is reassembled.

Embodiment nine:

The implementation principle of this embodiment is basically the same as that of the eighth embodiment, except that the reserved special value in the length indication field is used to indicate that the next field is the interrupt number field.

Or, use any other special length indication field value such as currently undefined value to indicate that the next field is the number of breaks field.

Embodiment ten:

The implementation principle of this embodiment is basically the same as that of Embodiment 1, except that the special identifier used to identify the inserted PDU is located in the PDU before the inserted PDU, and other settings and processing procedures are completely the same.

Embodiment eleven:

The implementation principle of this embodiment is basically the same as that of Embodiment 2, except that the special identifier used to identify the inserted PDU is located in the PDU before the inserted PDU, and other settings and processing procedures are completely the same.

Embodiment 12:

The implementation principle of this embodiment is basically the same as that of Embodiment 3, except that the special identifier used to identify the inserted PDU is located in the PDU before the inserted PDU, and other settings and processing procedures are completely the same.

Embodiment thirteen:

The implementation principle of this embodiment is basically the same as that of Embodiment 4, except that the special identifier used to identify the inserted PDU is located in the PDU before the inserted PDU, and other settings and processing procedures are completely the same.

Embodiment 14:

The implementation principle of this embodiment is basically the same as that of Embodiment 5, except that the special identifier used to identify the inserted PDU is located in the PDU before the inserted PDU, and other settings and processing procedures are completely the same.

Embodiment fifteen:

The implementation principle of this embodiment is basically the same as that of Embodiment 6, except that the special identifier used to identify the inserted PDU is located in the PDU before the inserted PDU, and other settings and processing procedures are completely the same.

Embodiment sixteen:

The implementation principle of this embodiment is basically the same as that of Embodiment 7, except that the special identifier used to identify the inserted PDU is located in the PDU before the inserted PDU, and other settings and processing procedures are completely the same.

Embodiment seventeen:

The implementation principle of this embodiment is basically the same as that of the eighth embodiment, except that the special identifier used to identify the inserted PDU is located in the PDU before the inserted PDU, and other settings and processing procedures are completely the same.

Embodiment eighteen:

The implementation principle of this embodiment is basically the same as that of Embodiment 9, except that the special identifier used to identify the inserted PDU is located in the PDU before the inserted PDU, and other settings and processing procedures are completely the same.

The above scheme is applicable to GPRS, EDGE, WCDMA, TD-SCDMA and other wireless communication systems, and is applicable to many processes, such as: ordinary UMD PDU transmission process, UMDPDU transmission process with out-of-order transmission function, etc. The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention.

Claims (24)

1. A method for segmented data concatenation, characterized in that, when the current service data unit SDU is segmented and concatenated and assembled into a packet data unit PDU, the process needs to be interrupted, and the sender will indicate that the current SDU is interrupted The special identification of the package is encapsulated in the PDU and sent. The method includes: interrupting the segment concatenation of the current SDU, performing segment concatenation on the SDU that needs to be inserted and assembling it into a PDU for transmission, and then sending the remaining interrupted current SDU The data is segmented and concatenated, assembled into a PDU and sent. 2. The method according to claim 1, wherein the special identifier is a length indication field whose value is a reserved special value in the PDU, and different reserved special values represent different numbers of inserted PDUs. 3. The method according to claim 1, wherein the special identifier is one or more length indication fields that take the same reserved special value in the PDU, and the number of length indication fields is equal to the number of inserted PDUs. 4. The method according to claim 1, wherein the special identifier is more than one length indication field with different reserved special values in the PDU, and the number of length indication fields is equal to the number of inserted PDUs. 5. The method according to claim 1, wherein the special identifier is a length indication field whose value is an undefined special value in the PDU, and different undefined special values represent different numbers of inserted PDUs. 6. The method according to claim 1, wherein the special identifier is one or more length indication fields that take the same undefined special value in the PDU, and the number of length indication fields is equal to the number of inserted PDUs. 7. The method according to claim 1, wherein the special identifier is more than one length indication field with different undefined special values in the PDU, and the number of length indication fields is equal to the number of inserted PDUs. 8. The method according to claim 1, wherein the special identifier is a length indication field in the PDU whose value is a combination of a reserved special value and an undefined special value. 9. The method according to claim 1, characterized in that, the method further comprises: setting in the PDU an interrupt number field indicating the number of PDUs assembled from the SDUs that need to be inserted, then the special identifier is the number of PDUs in the PDU The length indication field and the number of breaks field take special values. 10. The method according to claim 9, wherein the special value of the length indication field is a special value reserved for the length indication field in the PDU; or a special value undefined for the length indication field in the PDU. 11. The method according to claim 2, 3, 4, 8 or 10, characterized in that the reserved special value is 1111101 or 11111111111101. 12. The method according to any one of claims 1 to 10, wherein said encapsulating the special identifier in the PDU is specifically: encapsulating the special identifier in the PDU after the PDU assembled from the SDU to be inserted. 13. The method according to any one of claims 1 to 10, wherein said encapsulating the special identifier in the PDU is specifically: encapsulating the special identifier in the PDU before the PDU assembled from the SDU to be inserted. 14. The method according to any one of claims 1 to 10, characterized in that the method further comprises: The receiver judges whether the currently received PDU carries a special identifier. If so, it determines the PDU required to recombine the SDU according to the special identifier, and completes the reassembly of the SDU according to the determined PDU; otherwise, the data in the received PDU is SDUs are reassembled in sequence. 15. The method according to claim 14, wherein said encapsulating the special identifier in the PDU is specifically: encapsulating the special identifier in a PDU after the PDU assembled from the SDU to be inserted. 16. The method according to claim 14, wherein said encapsulating the special identifier in the PDU specifically comprises: encapsulating the special identifier in the PDU before the PDU assembled from the SDU to be inserted. 17. A method for data reorganization, characterized in that the method comprises: The receiver judges whether the currently received PDU carries a special identifier. If it carries it, it determines the PDU that is not related to the SDU corresponding to the reorganized current PDU according to the special identifier, and then ignores the determined PDU to complete the reorganization of the SDU corresponding to the current PDU; otherwise, Reassemble the data in the received PDU into SDU in sequence. 18. The method according to claim 17, characterized in that, the special identification is one or more length indication domains with special values in the PDU; , to determine the number of PDUs that are not related to the SDU corresponding to the recombined current PDU. 19. The method according to claim 17, characterized in that, the special identification is a length indication field that takes a special value in the PDU; then the receiver determines and reassembles according to the special value that the length indication field in the PDU takes. The number of SDU-independent PDUs corresponding to the current PDU. 20. The method according to claim 17, wherein the special identifier is a combination of a length indication field and an interruption number field which takes a special value in the PDU; The number of PDUs not related to the SDU corresponding to the current PDU to be reassembled. 21. The method according to claim 18, wherein the special value of the length indication field is a special value reserved for the length indication field, or a special value not defined for the length indication field, or a combination of both. 22. The method according to claim 19, wherein the special value of the length indication field is a special value reserved for the length indication field, or a special value not defined for the length indication field. 23. The method according to claim 21 or 22, characterized in that the reserved special value is 1111101 or 11111111111101. 24. The method according to any one of claims 17 to 22, wherein the PDU not related to the SDU corresponding to the recombined current PDU is located before the current PDU, or located after the current PDU.

Images