Data sharding reorganization method, device, apparatus, and storage medium

Abstract

The application provides a data fragment reorganization method, device, equipment and storage medium. The method comprises the following steps: receiving at least one protocol data unit (PDU) sent by a sending end radio link control (RLC) layer; analyzing the RLC protocol header of each PDU to obtain the fragment attribute information of each PDU; storing the storage address information of homologous PDUs belonging to the same RLC service data unit (SDU) into the address storage space corresponding to the RLC SDU; in response to the fact that the homologous PDUs belonging to the same RLC SDU have all been received, sending the storage address information of each homologous PDU to a security processing chip, so that the security processing chip reads the data fragments in each homologous PDU in sequence according to the storage address information of each homologous PDU and forms an RLC SDU; and receiving the RLC SDU sent by the security processing chip. The method provided by the application can improve the efficiency of the receiving end equipment in obtaining complete RLC SDU data.

Description

Technical Field

[0001] This application relates to communication technology, and more particularly to a data fragmentation and reassembly method, apparatus, device, and storage medium. Background Technology

[0002] To ensure successful data transmission, the communication protocol stipulates that when the size of the complete data exceeds the air interface time and frequency resources available to the Media Access Control (MAC) layer of the transmitting device, the Radio Link Control (RLC) layer of the transmitting device will segment the complete data into data fragments, and then encapsulate the data fragments into Protocol Data Units (PDUs) of the RLC layer. The MAC layer of the transmitting device will then send the PDUs to the receiving device.

[0003] In existing technologies, the PDUs received by the receiving device may be stored in a scattered manner. To obtain complete data, the RLC layer of the receiving device will reorder the PDUs and move them sequentially to a contiguous storage space to form a single block of complete data. Moving and splicing PDUs in the storage space takes a lot of time, affecting the efficiency of the receiving device in obtaining complete data.

[0004] In summary, in the existing technology, the efficiency of the receiving device in obtaining complete data is low. Summary of the Invention

[0005] This application provides a data fragmentation and reconstruction method, apparatus, device, and storage medium to solve the problem of low efficiency in obtaining complete data by receiving devices in the prior art.

[0006] According to a first aspect of this application, a data fragmentation and reassembly method is provided, applied to a central processing unit (CPU), wherein the CPU is located in a receiving device, and the receiving device further includes a security processing chip, the method comprising:

[0007] Receive at least one Protocol Data Unit (PDU) sent by the Radio Link Control (RLC) layer of the transmitting end, wherein the PDU includes an RLC header and a data segment formed by the transmitting end's RLC layer after segmenting the RLC Service Data Unit (RLC SDU);

[0008] The RLC protocol header of each PDU is parsed to obtain the fragmentation attribute information of each PDU;

[0009] Based on the fragmentation attribute information of each PDU, the storage address information of PDUs belonging to the same RLC SDU are stored in the address storage space of the corresponding RLC SDU.

[0010] In response to the fact that all PDUs belonging to the same RLC SDU have been received, the storage address information of each PDU is sent to the security processing chip in the order of forming the RLC SDU, so that the security processing chip can read the data segments in each PDU in the order of forming the RLC SDU and form the RLC SDU.

[0011] Receives RLC SDUs sent by the security processing chip.

[0012] As an optional implementation, the fragmentation attribute information includes the RLC SDU identifier and fragmentation sequence number;

[0013] The step of storing the storage address information of PDUs belonging to the same RLC SDU into the address storage space of the corresponding RLC SDU based on the fragmentation attribute information of each PDU includes:

[0014] Obtain the storage address information of each PDU;

[0015] PDUs with the same RLC SDU identifier are identified as PDUs of the same origin;

[0016] Determine whether there is address storage space for the corresponding RLC SDU of each PDU of the same origin;

[0017] If it is confirmed that it exists, the storage address information of the PDU is stored in the address storage space of the corresponding RLC SDU according to the fragment sequence number of the PDU.

[0018] If it is determined that it does not exist, then the address storage space of the corresponding RLC SDU of the same source PDU is created, and the storage address information of the same source PDU is stored in the address storage space of the corresponding RLC SDU according to the fragment sequence number of the same source PDU.

[0019] As an optional implementation, creating the address storage space corresponding to the RLC SDU includes:

[0020] Create storage bits according to the preset number or the number of PDUs from the same source, and determine the created storage bits as the address storage space of the corresponding RLCSDU.

[0021] As an optional implementation, storing the storage address information of the same-source PDU into the address storage space of the corresponding RLC SDU according to the fragment sequence number of the same-source PDU includes:

[0022] For any PDU from the same source, perform the following operations:

[0023] If it is determined that there is a storage bit in the address storage space of the corresponding RLC SDU that corresponds to the fragment sequence number, then the storage address information of the PDU from the same source is stored in the corresponding storage bit;

[0024] If it is determined that there is no information storage bit corresponding to the fragment sequence number in the address storage space of the corresponding RLC SDU, then a storage bit is added in the address storage space of the corresponding RLC SDU according to the fragment sequence number of the same source PDU, and the storage address information of the same source PDU is stored in the storage bit corresponding to the fragment sequence number.

[0025] As an optional implementation, the storage address information includes data segment addresses; the step of sequentially sending the storage address information of each source PDU in the order of forming the RLC SDU to the security processing chip includes:

[0026] According to the order of each storage bit in the address storage space of the corresponding RLC SDU, the storage address information of each PDU of the same origin is read in sequence, and the data segment address in each storage address information is sent to the security processing chip.

[0027] As an optional implementation, the fragmentation attribute information also includes fragmentation type, which is any one of the following: first fragment, last fragment, or middle fragment;

[0028] After storing the storage address information of PDUs belonging to the same RLC SDU into the address storage space of the corresponding RLC SDU based on the fragmentation attribute information of each PDU, the method further includes:

[0029] Read the last PDU address information stored in the last storage bit of the corresponding RLC SDU;

[0030] If it is determined that the fragment type of the PDU corresponding to the last PDU address storage information is tail fragment, and the fragment sequence numbers of PDUs from the same source in each storage bit of the corresponding RLCSDU are consecutive, then it is determined that all PDUs of the corresponding RLCSDU have been received.

[0031] As an optional implementation, the RLC SDU includes a Sidechain Relay Adaptation Protocol (SRAP) header or a Packet Data Convergence Protocol (PDCP) header;

[0032] After storing the storage address information of PDUs belonging to the same RLC SDU into the address storage space of the corresponding RLC SDU based on the fragmentation attribute information of each PDU, the method further includes:

[0033] Obtain the SRAP header or PDCP header for each RLC SDU;

[0034] Parse the SRAP header or PDCP header of each RLC SDU to obtain the target protocol entity identification information of each RLC SDU;

[0035] Based on the target protocol entity identifier information of each RLC SDU, each RLC SDU is sent to the target protocol entity.

[0036] According to a second aspect of this application, a data fragmentation and reassembly method is provided, applied to a security processing chip located in a receiving device, the receiving device further comprising a CPU, the method comprising:

[0037] The storage address information of each PDU from the same source sent by the CPU is received sequentially in the order in which the RLC SDU is formed.

[0038] Based on the storage address information of each PDU of the same origin, data segments in each PDU of the same origin are read sequentially and formed into RLCSDU;

[0039] Send the RLC SDU to the CPU.

[0040] As an optional implementation, the storage address information includes a data fragment address; the RLC SDU is either an RLC SDU ciphertext or an RLC SDU plaintext; the RLC SDU ciphertext is obtained by the sending end's Packet Data Convergence Protocol (PDCP) layer performing a first security process using a preset key; the first security process includes at least one of the following: encryption and integrity protection;

[0041] The step of sequentially reading data segments from each PDU of the same origin and forming an RLCSDU based on the storage address information of each PDU includes:

[0042] If the RLC SDU is an RLC SDU ciphertext, then the data segments in each source PDU are read sequentially from the data segment address of each source PDU to form the RLC SDU ciphertext;

[0043] The RLC SDU ciphertext is sent to the CPU, or the RLC SDU ciphertext is subjected to a second security processing using a preset key to obtain the RLC SDU plaintext, and the RLC SDU plaintext is sent to the CPU; the second security processing includes at least one of the following: decryption and integrity verification;

[0044] If the RLC SDU is in plaintext, then the data segments in each PDU are read sequentially from the data segment address of each PDU of the same origin to form the RLC SDU in plaintext, and the RLC SDU in plaintext is sent to the CPU.

[0045] According to a third aspect of this application, a data fragmentation and reassembly apparatus is provided, applied to a CPU, the CPU being located in a receiving device, the receiving device further comprising a security processing chip, the apparatus comprising:

[0046] The first receiving module is used to receive at least one Protocol Data Unit (PDU) sent by the Radio Link Control (RLC) layer of the transmitting end. The PDU includes an RLC protocol header and a data segment formed by the transmitting end RLC layer after segmenting the RLC Service Data Unit (RLC SDU).

[0047] The parsing module is used to parse the RLC protocol header of each PDU to obtain the fragmentation attribute information of each PDU;

[0048] The storage module is used to store the storage address information of PDUs belonging to the same RLC SDU into the address storage space of the corresponding RLC SDU according to the fragmentation attribute information of each PDU.

[0049] The first transmitting module is used to send the storage address information of each PDU in the same source as the RLC SDU to the security processing chip in the order of forming the RLC SDU in response to the fact that all PDUs belonging to the same source have been received, so that the security processing chip can read the data segments in each PDU in the same source according to the storage address information of each PDU and form an RLC SDU.

[0050] The second receiving module is used to receive the RLC SDU sent by the security processing chip.

[0051] According to a fourth aspect of this application, a data fragmentation and reassembly apparatus is provided, applied to a security processing chip, the security processing chip being located in a receiving device, the receiving device further comprising a CPU, the apparatus comprising:

[0052] The third receiving module is used to receive the storage address information of each PDU of the same origin sent by the CPU in the order in which the RLC SDU is formed.

[0053] The reassembly module is used to sequentially read data segments from each PDU of the same source according to the storage address information of each PDU and form an RLC SDU;

[0054] The sending module is used to send RLC SDUs to the CPU.

[0055] According to a fifth aspect of this application, a receiving device is provided, comprising: a CPU, a security processing chip, and a memory; the CPU includes a first transceiver; the security processing chip includes a second transceiver;

[0056] The CPU, the security processing chip, and the memory circuit are interconnected;

[0057] The memory is used to store the first computer-executed instructions and the second computer-executed instructions;

[0058] Both the first transceiver and the second transceiver are used for sending and receiving data;

[0059] The CPU executes the first computer execution instructions to implement the method as described in the first aspect, and the security processing chip executes the second computer execution instructions to implement the method as described in the second aspect.

[0060] According to a sixth aspect of this application, a computer-readable storage medium is provided, wherein computer-executable instructions are stored therein, which, when executed by a processor, are used to implement the method as described in the first or second aspect.

[0061] The data fragmentation and reassembly method, apparatus, device, and storage medium provided in this application are applied to a CPU located in a receiving device. The receiving device further includes a security processing chip. The method includes: receiving at least one Protocol Data Unit (PDU) sent by the Radio Link Control (RLC) layer of a transmitting end, wherein the PDU includes an RLC protocol header and data segments formed by the transmitting end's RLC layer segmenting an RLC Service Data Unit (RLC SDU); parsing the RLC protocol header of each PDU to obtain fragmentation attribute information of each PDU; storing the storage address information of PDUs belonging to the same source within the same RLC SDU into the address storage space of the corresponding RLC SDU according to the fragmentation attribute information of each PDU; in response to the receipt of all PDUs belonging to the same source within the same RLC SDU, sequentially sending the storage address information of each PDU to the security processing chip in the order of forming the RLC SDU, so that the security processing chip sequentially reads the data segments in each PDU and forms an RLC SDU according to the storage address information of each PDU; and receiving the RLC SDU sent by the security processing chip. Since the storage address information of each PDU of the same origin is stored in the address storage space of the corresponding RLC SDU, after all PDUs of the same origin belonging to the same SDU have been received, the storage address information of each PDU of the same origin is sent to the security processing chip in sequence. The security processing chip quickly reads the data segments in each PDU of the same origin through the storage address information of each PDU of the same origin, and then splices the data segments in each PDU of the same origin to form an RLC SDU. Since the security processing chip is an application-specific integrated circuit (ASIC), its processing speed is much higher than that of the receiving end device moving and splicing PDUs through the CPU or other software or hardware. Therefore, it can quickly obtain the RLC SDU, thereby improving the efficiency of the receiving end device in obtaining RLC SDU data. Attached Figure Description

[0062] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0063] Figure 1 This is a network architecture diagram corresponding to the application scenario of the data fragmentation and reassembly method provided in the embodiments of this application;

[0064] Figure 2 This is a flowchart illustrating the data fragmentation and reassembly method provided in Embodiment 1 of this application;

[0065] Figure 3 This is a flowchart illustrating the data fragmentation and reconstruction method provided in Embodiment 2 of this application;

[0066] Figure 4 This is a flowchart illustrating the data fragmentation and reassembly method provided in Embodiment 3 of this application;

[0067] Figure 5 This is a schematic flowchart of the data fragmentation and reconstruction method provided in Embodiment 4 of this application;

[0068] Figure 6 This is a flowchart illustrating the data fragmentation and reassembly method provided in Embodiment 5 of this application;

[0069] Figure 7 This is a schematic diagram of the data fragmentation and reconstruction device provided in Embodiment Six of this application;

[0070] Figure 8 This is a schematic diagram of the data fragmentation and reconstruction device provided in Embodiment 7 of this application;

[0071] Figure 9 This is a schematic diagram of the receiving device provided according to Embodiment 8 of this application.

[0072] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0073] First, the terms used in this application will be explained.

[0074] The 3rd Generation Partnership Project (3GPP) is a standards organization that develops globally applicable communication technology specifications, starting with third-generation mobile communication systems. 3GPP standards are managed using the Release version.

[0075] Long Term Evolution (LTE) is a long-term evolution of the Universal Mobile Telecommunications System (UMTS) technical standard developed by the 3GPP organization. The first version of the LTE protocol was LTE Release 8.

[0076] The Packet Data Convergence Protocol (PDCP) layer is a layer in the radio access protocol architecture of LTE Release 8 and later versions, used for IP packet header compression and decompression, data encryption and decryption, and data integrity protection.

[0077] The Radio Link Control (RLC) layer is a layer in the radio access protocol architecture of LTE Release 8 and later versions, used to provide radio bearers for PDCP.

[0078] The Medium Access Control (MAC) layer is a layer in the radio access protocol architecture of LTE Release 8 and later versions, used to provide logical channels for the RLC layer.

[0079] In 3GPP Release 16 and later versions, the Sidelink Relay Adaptation Protocol (SRAP) layer was added to the radio access protocol architecture to support communication between user terminals.

[0080] A Protocol Data Unit (PDU) is a unit of information exchanged between peer entities at different layers of a computer network, corresponding to data processed by that layer to form a specific format.

[0081] A Service Data Unit (SDU) is a dataset of user services for a specified layer, corresponding to data that has not been processed in a particular layer.

[0082] Segmentation is an operation performed by the sender to divide the SDU into segments to ensure that every SDU that needs to be sent can be transmitted.

[0083] Reassembly is the process by which the receiving end splices together the PDUs after receiving them in order to obtain the complete data of the SDU.

[0084] In LTE and later versions of the protocol, fragmentation and reassembly are implemented by the RLC layer. Security processing, such as encryption and / or integrity calculations, is implemented by the PDCP layer.

[0085] The prior art involved in this application will be described in detail and analyzed below.

[0086] During communication between the transmitting and receiving devices, if the air interface time-frequency resources required for a complete RLC Service Data Unit (RLC SDU) to be sent by the transmitting device's RLC layer exceed the air interface time-frequency resources available to the transmitting device's MAC layer, the transmitting device's RLC layer will divide the RLC SDU into multiple data segments according to the size specified by the transmitting device's MAC layer. Each data segment will have an RLC layer protocol header added to its beginning, and each segment will be independently encapsulated into an RLC Protocol Data Unit (RLC PDU) before being sent to the transmitting device's MAC layer. The transmitting device's MAC layer then forwards these multiple RLC PDUs to the receiving device.

[0087] The MAC layer of the receiving device receives multiple RLC PDUs sent by the sending device and delivers them to the RLC layer of the receiving device. Within a specified time window, the RLC layer of the receiving device reassembles the multiple RLC PDUs belonging to the same RLC SDU received from the MAC layer of the receiving device to obtain the RLC SDU.

[0088] Since the order in which each RLC PDU arrives at the receiving device is not necessarily the same as the fragmentation order, and the receiving device may distribute and store each RLC PDU fragment in its storage space after receiving each RLC PDU fragment.

[0089] Meanwhile, the RLC SDU at the sending end's RLC layer originates from the sending end's PDCP layer. The sending end's PDCP layer can perform a first security process on the RLC SDU, which includes at least one of the following: encryption and integrity protection. Therefore, before being segmented into data fragments, the RLC SDU can be either ciphertext or plaintext.

[0090] If the RLC SDU is an encrypted RLC SDU, the receiving RLC layer needs to perform a second security process on the encrypted RLC SDU after receiving it to obtain the plaintext RLC SDU. The second security process includes at least one of the following: decryption and integrity verification.

[0091] Understandably, secondary security processing can only be performed on complete and continuous RLC SDUs, and not on data fragments or RLC PDUs.

[0092] However, regardless of whether the receiving device needs to perform secondary security processing on the RLC SDU, the RLC layer of the receiving device must reassemble the RLC PDUs into an RLC SDU after receiving all RLC PDU fragments belonging to the same RLC SDU before proceeding with subsequent processing. The reassembly process involves the receiving device's RLC layer sorting the RLC PDU fragments belonging to the same RLC SDU but scattered out of order in different storage locations. Then, it moves the data segments from each RLC PDU belonging to the same RLC SDU sequentially to a single, physically contiguous storage space, assembling them into a complete RLC SDU.

[0093] The process of moving and splicing data fragments within an RLC PDU in storage space is time-consuming, delaying the time it takes for the receiving device to acquire complete RLC SDU data and impacting its efficiency. Furthermore, when there are many fragments or a large number of RLC PDUs belonging to different RLC SDUs, the movement and splicing of data fragments within the RLC PDUs also affects the efficiency of the receiving device in acquiring complete RLC SDU data, further impacting its performance.

[0094] In summary, existing data fragmentation and reassembly methods require a significant amount of time, impacting the efficiency of the receiving device in acquiring complete RLC SDU data.

[0095] Therefore, in the face of the problems in the existing technology, the inventors, through creative research, have found that in order to improve the efficiency of the receiving device in obtaining complete RLC SDU data, the inefficient method of the CPU moving and splicing PDU fragments in memory space to obtain the SDU, which would affect the performance of the receiving device, cannot be used. Instead, the CPU can simply record the storage address information of each PDU belonging to the same source as the SDU, and after all the PDUs belonging to the same source as the RLC SDU have been received, send the storage address information of each PDU to the security processing chip in the order of forming the RLC SDU. The security processing chip then reads the data fragments in each PDU in sequence according to the storage address information of each PDU and forms an RLC SDU. This avoids the time consumed by the CPU in moving and splicing PDUs in memory space, which affects the performance of the receiving device. At the same time, the security processing chip can directly complete the splicing and any possible secondary security processing, thereby improving the efficiency of the receiving device in obtaining complete data.

[0096] Therefore, the inventor proposes the technical solution of this application, which is applied to a CPU located in a receiving device. The receiving device also includes a security processing chip. The method involves receiving at least one Protocol Data Unit (PDU) sent by the Radio Link Control (RLC) layer of the transmitting end. The PDU includes an RLC protocol header and data segments formed by the transmitting end's RLC layer segmenting the RLC Service Data Unit (RLC SDU). The RLC protocol header of each PDU is parsed to obtain the fragmentation attribute information of each PDU. Based on the fragmentation attribute information of each PDU, the storage address information of PDUs belonging to the same source in the same RLC SDU is stored in the address storage space of the corresponding RLC SDU. In response to the fact that all PDUs belonging to the same source in the same RLC SDU have been received, the storage address information of each PDU is sent to the security processing chip in the order of forming the RLC SDU, so that the security processing chip reads the data segments in each PDU in the same source according to the storage address information of each PDU and forms an RLC SDU. The method also involves receiving the RLC SDU sent by the security processing chip. Since the storage address information of each PDU of the same origin is stored in the address storage space of the corresponding RLC SDU, after all PDUs of the same origin belonging to the same SDU have been received, the storage address information of each PDU of the same origin is sent to the security processing chip in sequence. The security processing chip quickly reads the data segments in each PDU of the same origin through the storage address information of each PDU of the same origin, and then splices the data segments in each PDU of the same origin to form an RLC SDU. Since the security processing chip is usually an application-specific integrated circuit (ASIC), its processing speed is much higher than that of the receiving end device moving and splicing PDUs through the CPU or other software or hardware. Therefore, it can quickly obtain the RLC SDU, thereby improving the efficiency of the receiving end device in obtaining RLC SDU data.

[0097] The data fragmentation and reassembly method, apparatus, device, and storage medium provided in this application aim to solve the above-mentioned technical problems of the prior art. The technical solutions of this application and how they solve the aforementioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0098] The network architecture and application scenarios of the data fragmentation and reassembly method provided in the embodiments of this application will be described below. When the following description refers to the accompanying drawings, unless otherwise indicated, the same data in different drawings represent the same or similar elements.

[0099] Figure 1 This is a network architecture diagram corresponding to the application scenario of the data fragmentation and reassembly method provided in the embodiments of this application. For example... Figure 1 As shown in the embodiment of this application, a network architecture corresponding to an application scenario includes: a transmitting device 11 and a receiving device 12. The receiving device 12 includes a CPU 13 and a security processing chip 14, which can be connected via a bus. The transmitting device 11 includes a transmitting RLC layer 112 and a transmitting MAC layer 113. The receiving device includes a receiving MAC layer and a receiving PDCP layer.

[0100] When the number of RLC Service Data Units (RLC SDUs) to be transmitted exceeds the air interface time-frequency resources that the transmitting MAC layer 113 can choose to use, the transmitting RLC layer 112 will segment the RLC SDU into multiple data segments, such as... Figure 1 As shown, the RLC SDU is divided into data segment 1, data segment 2, ..., data segment n.

[0101] After dividing the RLC SDU into multiple data segments, the transmitting RLC layer 112 independently encapsulates these data segments, that is, it adds an RLC layer protocol header to each data segment to form multiple Protocol Data Units (PDUs), such as... Figure 1 As shown, data fragment 1, data fragment 2, ..., data fragment n are formed into PDU1, PDU2, ..., PDUn after adding the RLC layer protocol header. Therefore, each PDU includes the RLC protocol header and the data fragments formed by the RLC layer of the sending end after segmenting the RLC SDU.

[0102] The transmitting end RLC layer 112 sends multiple PDUs to the transmitting end MAC layer 113, and the transmitting end MAC layer 113 transmits the multiple PDUs to the receiving end MAC layer via the physical layer through the air interface time and frequency resources that it can choose to use.

[0103] The CPU 13 of the receiving device 12 receives each PDU through the receiving MAC layer, and the received PDUs are stored in the storage space of the receiving device 12. The CPU 13 can parse the RLC protocol header of each PDU to obtain the fragmentation attribute information of each PDU, and can store the storage address information of PDUs belonging to the same RLC SDU into the address storage space 121 of the corresponding RLC SDU according to the fragmentation attribute information of each PDU. Furthermore, after all PDUs belonging to the same RLC SDU have been received, the CPU 13 can send the storage address information of each PDU to the security processing chip 14 in the order of forming the RLC SDU, so that the security processing chip 14 can read the data segments in each PDU in sequence according to the storage address information of each PDU and form an RLC SDU.

[0104] The security processing chip 14 receives the storage address information of each PDU from the same source sent by the receiving device in the order of forming the RLC SDU; it reads the data segments in each PDU from the same source in sequence according to the storage address information of each PDU and forms an RLC SDU; and sends the RLC SDU to the CPU 13.

[0105] The data fragmentation and reassembly method provided in this application can be applied to 4G or 5G communication systems. The aforementioned transmitting and receiving devices can be, but are not limited to, 4G base stations (Evolutionary Node B, abbreviated as eNB or eNodeB), 5G base stations (gNodeB), 4G mobile terminals, or 5G mobile terminals. For example, the aforementioned transmitting and receiving devices can be base stations, smartphones, tablets, smartwatches, etc., and are not limited thereto.

[0106] The embodiments of this application will now be described with reference to the accompanying drawings. The embodiments described below do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0107] Example 1

[0108] Figure 2 This is a flowchart illustrating the data fragmentation and reassembly method provided in Embodiment 1 of this application. Figure 2 As shown, the executing entity of this application is a data fragmentation and reassembly device, which is located in the CPU, and the CPU is located in the receiving end device. The receiving end device also includes a security processing chip. The data fragmentation and reassembly method provided in this embodiment includes steps 201 to 205.

[0109] Step 201: Receive at least one Protocol Data Unit (PDU) sent by the Radio Link Control (RLC) layer of the transmitting end. The PDU includes an RLC protocol header and a data segment formed by the transmitting end's RLC layer after segmenting the RLC Service Data Unit (RLC SDU).

[0110] In this embodiment, RLC SDU refers to the SDU of the RLC layer. The RLC SDU on the transmitting device is transmitted from the transmitting PDCP layer to the transmitting RLC layer. PDU refers to the PDU of the RLC layer. When the size of the RLC SDU exceeds the air interface time-frequency resources that the transmitting MAC layer can choose to use, the transmitting RLC layer divides the RLC SDU data into multiple data segments and adds an RLC layer protocol header to each data segment to form multiple RLC layer PDUs. That is, each PDU includes an RLC protocol header and the data segments formed by the transmitting RLC layer after dividing the RLC SDU data.

[0111] The transmitting MAC layer then sends multiple PDUs to the corresponding protocol layer of the receiving device. Here, since the transmitting MAC layer can choose to use different air interface time and frequency resources when sending each PDU, the multiple PDUs sent may not arrive at the receiving device in fragmented order.

[0112] The CPU receives PDUs through the receiver's MAC layer and stores the received PDUs in the receiver's memory. Therefore, the CPU can obtain the storage address information of each PDU.

[0113] Step 202: Parse the RLC protocol header of each PDU to obtain the fragmentation attribute information of each PDU.

[0114] In this embodiment, since the RLC SDU can be either plaintext or ciphertext, the ciphertext is obtained by the sending end's PDCP layer after performing a first security process using a preset key. This first security process includes at least one of the following: encryption and integrity protection. Therefore, the CPU may not be able to directly parse data segments in the PDU. However, the protocol header added to the data segments by the RLC layer is unencrypted. Therefore, after receiving the PDU, the receiving device can directly read the information in the PDU's RLC protocol header to obtain the fragmentation attribute information of each PDU.

[0115] Fragmentation attribute information is used to determine the RLC SDU to which each PDU belongs, and the order of data fragments within each PDU in the RLC SDU. For example, fragmentation attribute information may include the RLC SDU identifier to which the PDU belongs and the fragmentation sequence number.

[0116] Fragment numbers are used to identify the order of data segments within a PDU in an RLC SDU. For example, complete data is divided into three data segments: a first data segment, a second data segment, and a third data segment. These three data segments are then concatenated in sequence to form the complete data before the fragmentation. Therefore, the fragment number of the PDU formed by adding an RLC layer protocol header to the first data segment can be 1, the fragment number of the PDU formed by adding an RLC layer protocol header to the second data segment can be 2, and the fragment number of the PDU formed by adding an RLC layer protocol header to the third data segment can be 3.

[0117] The CPU can determine whether each PDU belongs to the same RLC SDU and the order of PDUs belonging to the same RLC SDU based on the fragmentation attribute information of each PDU.

[0118] Step 203: Based on the fragmentation attribute information of each PDU, store the storage address information of PDUs belonging to the same RLC SDU into the address storage space of the corresponding RLC SDU.

[0119] In this embodiment, PDUs with the same SDU identifier in the fragmentation attribute information belong to the same source PDU of the same RLC SDU. Data fragments in the same source PDU are obtained by segmenting the same RLC SDU.

[0120] The storage address information can be the location where the PDU is stored in the receiving device. For example, the storage address information can be the starting address and data length, the ending address and data length of the PDU, etc. Using the PDU's storage address information, each PDU can be read from the receiving device's memory.

[0121] The address storage space is the space in the memory of the receiving device used to store the aforementioned storage address information. In this embodiment, the storage address information of PDUs belonging to the same RLC SDU can be written into the address storage space of the corresponding RLC SDU in the order of the PDUs.

[0122] Step 204: In response to the fact that all PDUs belonging to the same RLC SDU have been received, the storage address information of each PDU is sent to the security processing chip in the order in which the RLC SDU is formed, so that the security processing chip can read the data segments in each PDU in the order according to the storage address information of each PDU and form the plaintext of the RLC SDU.

[0123] In this embodiment, the CPU can determine whether all PDUs belonging to the same RLC SDU have been received based on the parsing results of the RLC protocol header of each PDU. For example, the fragmentation attribute information may also include whether the data segment in the PDU is the last data segment after the RLC SDU is segmented. After the receiving device parses the PDU, it can determine whether the PDU is the tail segment of its RLC SDU based on the fragmentation attribute information. If the PDU is determined to be the tail segment of its RLC SDU, the CPU can, after storing the storage address information of the tail segment PDU in the address storage space of the corresponding RLC SDU, determine whether all PDUs included in the RLC SDU have been received based on whether the fragmentation sequence numbers of each PDU stored in the address storage space of the corresponding RLC SDU are consecutive. Furthermore, if the fragmentation sequence numbers of each PDU stored in the address storage space of the corresponding RLC SDU are consecutive, and the tail segment of the corresponding RLC SDU is read, the CPU can determine whether all PDUs of the SDU have been received based on the number of PDUs already received belonging to the RLC SDU.

[0124] In this embodiment, the fragmentation attribute information of each PDU can also be stored together with its storage address information in the address storage space of the corresponding RLCSDU.

[0125] In this embodiment, the storage address information of the PDU may include data segment addresses, which are the storage addresses of data segments within the PDU in the receiving device. For example, a data segment address may be the starting address and data length of the data segment in the storage space of the receiving device. The receiving device sequentially sends the storage address information of each source PDU to the security processing chip. The security processing chip can read the data segments included in each source PDU from each data segment address according to the order in which the storage address information of each source PDU is received, and form an RLC SDU. In other words, the security processing chip completes the splicing of data segments to obtain the RLC SDU.

[0126] In this embodiment, if the RLC SDU is plaintext, the security processing chip can obtain the plaintext RLC SDU after reading each data segment. If the RLC SDU is ciphertext, the security processing chip also needs to perform a second security processing on the ciphertext RLC SDU according to a preset key to obtain the plaintext RLC SDU. The second security processing includes at least one of the following: decryption and integrity verification.

[0127] Step 205: Receive the RLC SDU plaintext sent by the security processing chip.

[0128] In this embodiment, the receiving device stops after sending the storage address information of the tail SDU to the security processing chip. The security processing chip reads data from the data segment addresses of each source PDU in the form of a bit stream, and outputs the resulting RLC SDU plaintext in the form of a bit stream, that is, sends it to the receiving device. The receiving device receives the RLC SDU plaintext sent by the security processing chip.

[0129] The data fragmentation and reassembly method provided in this embodiment is applied to a CPU located in a receiving device. The receiving device also includes a security processing chip. The method involves receiving at least one Protocol Data Unit (PDU) sent by the Radio Link Control (RLC) layer of the transmitting end. The PDU includes an RLC header and data segments formed by the transmitting end's RLC layer segmenting the RLC Service Data Unit (RLC SDU). The method parses the RLC header of each PDU to obtain the fragmentation attribute information of each PDU. Based on the fragmentation attribute information of each PDU, the storage address information of PDUs belonging to the same source within the same RLC SDU is stored in the address storage space of the corresponding RLC SDU. In response to the receipt of all PDUs belonging to the same source within the same RLC SDU, the storage address information of each PDU is sent sequentially to the security processing chip in the order of RLC SDU formation, so that the security processing chip can sequentially read the data segments in each PDU and form an RLC SDU based on the storage address information of each PDU. Finally, the method receives the RLC SDU sent by the security processing chip. Since the storage address information of each PDU of the same origin is stored in the address storage space of the corresponding RLC SDU, after all PDUs of the same origin belonging to the same SDU have been received, the storage address information of each PDU of the same origin is sent to the security processing chip in sequence. The security processing chip quickly reads the data segments in each PDU of the same origin through the storage address information of each PDU of the same origin, and then splices the data segments in each PDU of the same origin to form an RLC SDU. Since the security processing chip is an application-specific integrated circuit (ASIC), its processing speed is much higher than that of the receiving end device moving and splicing PDUs through the CPU or other software or hardware. Therefore, it can quickly obtain the RLC SDU, thereby improving the efficiency of the receiving end device in obtaining RLC SDU data.

[0130] Example 2

[0131] Figure 3 This is a flowchart illustrating the data fragmentation and reassembly method provided in Embodiment 2 of this application. Figure 3 As shown, the data fragmentation and reassembly method provided in this embodiment, based on embodiment one, includes the RLCSDU identifier and fragment sequence number in the fragmentation attribute information, and refines step 203, which includes steps 301 to 305.

[0132] Step 301: Obtain the storage address information of each PDU.

[0133] In this embodiment, after receiving a PDU, the receiving device can store the PDU in its memory space and obtain the PDU's storage address information. The storage address information may include the PDU's start address, end address, data length, etc., as long as the PDU can be located in the receiving device's memory based on the storage information. Here, the start address, end address, etc., can be understood as the number of the storage cell in the memory. Since the PDU is formed after being divided when the data volume of the RLC SDU is too large, the data volume of a PDU is limited. Therefore, the receiving device stores the PDU in memory cells with contiguous addresses.

[0134] Step 302: PDUs with the same RLC SDU identifier are identified as homologous PDUs.

[0135] In this embodiment, the RLC SDU identifier is added by the sending end when encapsulating the data fragments formed by the SDU segmentation. That is, the RLC layer protocol header field added by the sending end includes the RLC layer identifier. Multiple data fragments formed from the same SDU segmentation have the same RLC layer identifier. Therefore, after parsing the PDU fragmentation attribute information, the receiving device can determine PDUs with the same RLC layer identifier as homogeneous PDUs. Here, the protocol header field can include more than one protocol header; for example, the RLC layer PDU received by the receiving end includes both an RLC layer protocol header and a PDCP layer protocol header.

[0136] Step 303: Determine whether there is address storage space for the corresponding RLC SDU of each PDU of the same origin.

[0137] In this embodiment, the receiving device can receive one PDU at a time or multiple PDUs at a time. Furthermore, the multiple PDUs received by the receiving device at a time can be PDUs from the same RLC SDU or PDUs from different RLC SDUs.

[0138] The corresponding RLC SDU of a PDU refers to the RLC SDU to which the PDU belongs. Since PDUs from the same source belong to the same RLC SDU, the corresponding RLC SDUs of PDUs from the same source are also the same.

[0139] In this embodiment, the CPU can allocate address storage space for any PDU of the RLC SDU upon receiving it, to store the storage address information of each PDU within the RLC SDU. Therefore, after the receiving device obtains the fragmentation attribute information of each PDU, it needs to determine whether the corresponding RLC SDU of each PDU from the same source stores address storage space.

[0140] In this embodiment, the CPU device can determine whether it has received a PDU fragment of the corresponding RLCSDU within a specified time window, that is, whether it has received a PDU fragment belonging to the same RLC SDU as the PDU fragment received this time within a preset time period prior to the current PDU fragment reception. If it is determined that a PDU fragment of the corresponding RLC SDU has been received, then it is determined that the corresponding RLC SDU of the same source PDU has address storage space; conversely, if it is determined that a PDU fragment of the corresponding RLC SDU has not been received, then it is determined that the corresponding RLC SDU of the same source PDU does not have address storage space.

[0141] Step 304: If it is determined that the PDU exists, the storage address information of the PDU is stored in the address storage space of the corresponding RLC SDU according to the fragment sequence number of the PDU.

[0142] In this embodiment, if it is determined that there is address storage space for the corresponding RLC SDU of the same source PDU, the order of the same source PDU can be determined according to the fragment sequence number of the same source PDU, so that the storage address information of the same source PDU can be stored in the address storage space of the corresponding RLC SDU in order.

[0143] Step 305: If it is determined that there is no such PDU, then create the address storage space of the RLC SDU corresponding to the same source PDU, and store the storage address information of each same source PDU into the address storage space of the corresponding RLC SDU according to the fragment sequence number of the same source PDU.

[0144] In this embodiment, if it is determined that the corresponding RLC SDU of the same source PDU does not have an address storage space, then the address storage space of the corresponding RLC SDU can be created according to a preset number of storage bits. The address storage space can be an array structure, a linked list structure, etc.

[0145] The data fragmentation and reassembly method provided in this embodiment includes fragmentation attribute information such as the identifier of the RLC SDU and the fragmentation sequence number. It obtains the storage address information of each PDU; identifies PDUs with the same RLC SDU identifier as homogeneous PDUs; determines whether there is address storage space for the corresponding RLC SDU of each homogeneous PDU; if it is determined to exist, the storage address information of the homogeneous PDU is stored in the address storage space of the corresponding RLC SDU according to the fragmentation sequence number of the homogeneous PDU; if it is determined not to exist, an address storage space is created for the corresponding RLC SDU of the homogeneous PDU, and the storage address information of the homogeneous PDU is stored in the address storage space of the corresponding RLC SDU according to the fragmentation sequence number of the homogeneous PDU. Since the storage address information is stored in the address storage space according to the PDU's fragmentation sequence number when the corresponding RLC SDU has address storage space, and created before storing the storage address information when the corresponding RLC SDU does not have address storage space, it is possible to store the storage address information of each PDU in the address storage space of the corresponding RLC SDU.

[0146] As an optional implementation, based on Embodiment 2, the step 305 "creating the address storage space corresponding to the RLC SDU" is further refined, and the refinement includes step 401.

[0147] Step 401: Create storage bits according to the preset number or the number of PDUs from the same source, and determine the created storage bits as the address storage space of the corresponding RLC SDU.

[0148] In this embodiment, since the receiving device cannot determine the total number of PDUs in the RLC SDU before receiving the last PDU of the RLC SDU, it cannot determine how many storage bits the address storage space needs to include when creating the address storage space. However, there is an upper limit to the data in the PDUs formed by the RLC layer after dividing and repackaging the RLC SDU. For example, the RLC can divide the RLC SDU into a maximum of 100 data segments and repackage them into 100 PDUs. Therefore, a preset number can be the upper limit of the data segments formed by the RLC layer dividing the RLC SDU; for example, the preset number can be 100.

[0149] In this embodiment, when the address storage space of the RLC SDU is an array, the receiving device can create storage bits according to preset data, that is, initialize the array space to 100 storage bits.

[0150] In this embodiment, the number of PDUs of the same origin refers to the number of PDUs belonging to the same RLC SDU.

[0151] In this embodiment, the address storage space of the RLC SDU can also be a linked list structure. Since the linked list stores information through nodes, each node in the linked list is a storage bit. Each node in the linked list contains the address of the previous node or the address of the next node. Therefore, the linked list can flexibly add or insert nodes as needed, realizing flexible connection between nodes. Thus, when the address storage space of the RLC SDU is a linked list structure, the receiving device can create nodes based on the number of PDUs belonging to the same RLC SDU among the received PDUs, and determine the created nodes as the storage space of the RLC SDU corresponding to the same PDU. Then, the storage address information of the same PDUs is stored in the nodes of the linked list.

[0152] For example, if the receiving device receives and stores PDUs from the same source at one time, including a first PDU with a fragment number of 1 and a third PDU with a fragment number of 3, and the first PDU and the third PDU belong to the first RLC SDU, then the receiving device can create a linked list with 2 nodes, and can determine the address storage space of the first RLC SDU by the 2 nodes of the created linked list.

[0153] In summary, in this embodiment, the address storage space can be a linked list structure, an array structure, etc., and the storage bits can be nodes of the linked list or elements of the array.

[0154] The data fragmentation and reassembly method provided in this embodiment creates storage bits according to a preset number or the number of PDUs from the same source, and determines the created storage bits as the address storage space of the corresponding RLC SDU. Since the storage bits are created according to a preset number or the number of PDUs from the same source, it can ensure that the storage address information of the currently stored PDUs from the same source is stored in the address storage space of the corresponding PDU.

[0155] As an optional implementation, based on any of the above embodiments, the step 304 and step 305, "storing the storage address information of each PDU according to the fragmentation sequence number of each PDU into the address storage space of the corresponding RLC SDU", can be refined to include the following steps:

[0156] For any PDU from the same source, perform the following operations:

[0157] If it is determined that there is a storage bit in the address storage space of the corresponding RLC SDU that corresponds to the fragment sequence number, then the storage address information of the PDU from the same source is stored in the corresponding storage bit.

[0158] If it is determined that there is no information storage bit corresponding to the fragment sequence number in the address storage space of the corresponding RLC SDU, then a storage bit is added in the address storage space of the corresponding RLC SDU according to the fragment sequence number of the same source PDU, and the storage address information of the same source PDU is stored in the storage bit corresponding to the fragment sequence number.

[0159] In this embodiment, one storage bit is used to store the storage address information of one PDU, and the storage address information of each PDU is stored sequentially in each storage bit.

[0160] In this embodiment, if it is determined that there is a storage bit corresponding to the fragment sequence number in the address storage space of the corresponding RLC SDU, then when the address storage space of the corresponding RLC SDU is created, a storage bit is reserved to store the PDU storage address information of the fragment sequence number, and the PDU storage address information is stored in the storage bit corresponding to the fragment sequence number.

[0161] For example, the CPU device receives and stores the same source PDUs, including the second PDU. The second PDU belongs to the first SDU, and the address storage space of the first RLC SDU is an address storage array of length 100, with a fragment number of 2. Therefore, the CPU device simply stores the storage address information of the second PDU into the second element of the address storage array.

[0162] In this embodiment, if it is determined that there is no storage bit corresponding to the fragment sequence number in the address storage space of the corresponding RLC SDU, then storage bits can be added in the address storage space according to the fragment sequence number of each PDU of the same source currently stored and the existing storage bits in the address storage space.

[0163] For example, the CPU receives and stores two PDUs from the same source, the fifth PDU and the sixth PDU. The fifth and sixth PDUs belong to the first RLC SDU, whose address storage space is a linked list structure. The fifth PDU has a fragment number of 5, and the sixth PDU has a fragment number of 6. Therefore, the CPU can add two nodes to the address storage linked list to store the storage address information of the fifth and sixth PDUs. Furthermore, the CPU can adjust the order of the nodes in the linked list, as well as the previous and next nodes they point to.

[0164] The data fragmentation and reassembly method provided in this embodiment performs the following operations for any PDU from the same source: if it is determined that a storage bit corresponding to the fragmentation sequence number exists in the address storage space of the corresponding RLC SDU, then the storage address information of the PDU from the same source is stored in the corresponding storage bit; if it is determined that no storage bit corresponding to the fragmentation sequence number exists in the address storage space of the corresponding RLC SDU, then a storage bit is added to the address storage space of the corresponding RLC SDU according to the fragmentation sequence number of the PDU from the same source, and the storage address information of the PDU from the same source is stored in the storage bit corresponding to the fragmentation sequence number. Since the PDU's storage address information is stored in the storage bit corresponding to the fragmentation sequence number when a storage bit corresponding to the fragmentation sequence number exists, and a storage bit is created before the PDU's storage address information is stored in the storage bit corresponding to the fragmentation sequence number when a storage bit corresponding to the fragmentation sequence number does not exist, it can be ensured that the storage address information of each currently received PDU can be stored sequentially in the address storage space of the corresponding RLC SDU.

[0165] As an optional implementation, based on any of the above embodiments, the storage address information includes the data segment address, and the step 204, "sending the storage address information of each PDU of the same origin to the security processing chip in the order of forming the RLC SDU," is further refined, including the following steps:

[0166] According to the order of each storage bit in the address storage space of the corresponding RLC SDU, the storage address information of each PDU of the same origin is read in sequence, and the data segment address in each storage address information is sent to the security processing chip.

[0167] In this embodiment, the storage address information includes a data fragment address, which refers to the location of a data fragment in the PDU within the receiver device's memory. Here, in the communication protocol, the header length of each layer can be fixed, and the header field length in the data packet can also be fixed. Therefore, the data fragment address can be determined based on the PDU's storage address information. Currently, the data fragment address can also be determined after parsing the PDU's header field.

[0168] In this embodiment, since the PDU is obtained by adding an RLC layer protocol header after RLC SDU segmentation, and the data segments in the RLC SDU do not have an RLC layer protocol header, in order to obtain complete data, the CPU can read the storage address information of each PDU of the same origin in the order of the storage bits in the address storage space, and send the data segment address in each storage address information read to the security processing chip.

[0169] In this embodiment, the linked list is a data structure distributed in the storage space, used to record the storage address information of RLC SDU fragment data. The receiving device can find the head address of the linked list, i.e., the address of the first node in the linked list or other specific addresses, by reading any node in the linked list. Then, it can read all nodes in the entire linked list in order to obtain the data fragment addresses of each PDU and read each data fragment in sequence.

[0170] The data fragmentation and reassembly method provided in this embodiment includes data fragment addresses in the storage address information. By sequentially reading the storage address information of each source PDU according to the order of each storage bit in the address storage space of the corresponding RLC SDU, the data fragment addresses in each storage address information are sent to the security processing chip. Because the data fragment addresses are read and sent to the security processing chip sequentially according to the order of each storage bit in the address storage space of the corresponding RLC SDU, the CPU can quickly read each data fragment address and send it to the encryption / decryption information, improving the efficiency of obtaining the RLC SDU.

[0171] Example 3

[0172] Figure 4 This is a flowchart illustrating the data fragmentation and reassembly method provided in Embodiment 3 of this application. Figure 4 As shown, the data fragmentation and reassembly method provided in this embodiment, based on any of the above embodiments, further includes fragmentation type in the fragmentation attribute information. The fragmentation type is any one of the following: first fragment, last fragment, or intermediate fragment. Furthermore, after step 203, "Store the storage address information of PDUs belonging to the same RLC SDU into the address storage space of the corresponding RLC SDU according to the fragmentation attribute information of each PDU", steps 501 to 502 are also included.

[0173] Step 501: Read the last PDU address storage information stored in the last storage bit of the corresponding RLC SDU.

[0174] In this embodiment, since the storage address information of the PDU is stored in each storage bit of the address storage space according to the fragment order, the last storage bit storing the last PDU must be the one with the largest fragment sequence number among all PDUs of the RLC SDU. Therefore, it can be determined whether the last PDU is the tail fragment of the RLC SDU by determining whether the tail fragment PDU has been received.

[0175] Step 502: If it is determined that the fragment type of the PDU corresponding to the last PDU address storage information is tail fragment, and the fragment sequence numbers of PDUs from the same source in each storage bit of the corresponding RLC SDU are consecutive, then it is determined that all PDUs of the corresponding RLC SDU have been received.

[0176] In this embodiment, the fragmentation type can be obtained during PDU parsing in step 202, or it can be obtained from the PDU's RLC header when reading the PDU. The fragmentation type of the PDU is first fragment, last fragment, or intermediate fragment. For example, a PDU with the fragmentation type of first fragment may include "SN" information in the RLC header, and a PDU with the fragmentation type of last fragment may include "SI" information in the RLC header. The "SN" and "SI" information are respectively used in the RLC header to identify the first fragment PDU and the last fragment PDU.

[0177] Understandably, the PDU encapsulated from the first data segment after RLC SDU segmentation is classified as the first fragment, and the PDU encapsulated from the last data segment is classified as the last fragment. Within a single RLC SDU, only one PDU is classified as either the first or last fragment, while there can be zero, one, or more PDUs classified as intermediate fragments. Furthermore, since the first fragment PDU can be identified by its fragmentation type, a fragmentation sequence number may not be added to the protocol header of the first fragment PDU.

[0178] In this embodiment, if the PDU corresponding to the last PDU address storage information has a fragment type of "tail fragment," and the address storage space in the storage bit is stored according to the order of the PDUs after they are received and parsed, then starting from the first PDU, the fragment sequence numbers of the PDUs of the same origin in each storage bit of the corresponding RLC SDU can be obtained sequentially. Furthermore, if the fragment sequence numbers of the PDUs are consecutive during the process of reading the PDU with the fragment type of "first fragment," then it can be determined that all PDUs of the RLC SDU have been received.

[0179] Of course, if the fragment sequence number of the PDU is not consecutive during the process of reading the PDU with the fragment type of the first fragment, then the PDUs of the RLC SDU have not been collected.

[0180] The data fragmentation and reassembly method provided in this embodiment includes fragmentation type in the fragmentation attribute information. The fragmentation type can be any of the following: first fragment, last fragment, or intermediate fragment. The method reads the last PDU address storage information stored in the last storage bit of the corresponding RLC SDU. If it is determined that the fragmentation type of the PDU corresponding to the last PDU address storage information is the last fragment, and the fragmentation sequence numbers of the same source PDUs in each storage bit of the corresponding RLC SDU are consecutive, then it is determined that all PDUs of the corresponding RLC SDU have been received. Since the fragmentation type of the last PDU is read from the address storage information of the last PDU stored in the last storage bit of the corresponding RLC SDU, and when the fragmentation type of the last PDU is the last fragment, the fragmentation sequence numbers of the same source PDUs in each storage bit of the corresponding RLC SDU are read sequentially. During the process of reading the PDU with the fragmentation type of first fragment, if the fragmentation sequence numbers of the same source PDUs are consecutive, it is determined that all PDUs of the RLC SDU have been received. Therefore, it can quickly and accurately determine whether all PDUs of the RLC SDU have been received.

[0181] Example 4

[0182] Figure 5 This is a schematic flowchart of the data fragmentation and reassembly method provided in Embodiment 4 of this application. Figure 5 As shown, the data fragmentation and reassembly method provided in this embodiment, based on any of the above embodiments, includes a Sidechain Relay Adaptation Protocol (SRAP) header or a Packet Data Convergence Protocol (PDCP) header in the RLC SDU, and further includes steps 601 to 603 after step 205 "receiving the RLC SDU sent by the security processing chip".

[0183] Step 601: Obtain the SRAP header or PDCP header of each RLC SDU.

[0184] In this embodiment, the CPU can directly obtain the SRAP header or PDCP header from the plaintext of the RLC SDU. Simultaneously, since the PDCP layer is used for first or second security processing, for data packets requiring encryption and / or integrity protection, the sending-end PDCP layer, after adding the PDCP protocol header, performs the first security processing, forming the ciphertext of the RLC SDU, and transmits it to the sending-end RLC layer. For data packets without encryption and / or integrity protection requirements, the sending-end PDCP layer, after adding the PDCP protocol header, forms the plaintext of the RLC SDU and transmits it to the sending-end RLC layer. Alternatively, the SRAP header or PDCP header can be obtained from the header field of the first PDU of the RLC SDU. Therefore, compared to the intermediate and final PDUs, the first PDU may also include the protocol header of the Packet Data Convergence Protocol (PDCP) layer or the protocol header of the sidechain relay adapted to the SRAP layer.

[0185] In this embodiment, the CPU can also obtain the SRAP header or PDCP header from the first PDU of the RLC SDU.

[0186] The security processing chip is hardware within the receiving device. Logically, it can belong to the hardware entity of the receiving end's PDCP layer and is part of the PDCP protocol entity, used to implement the functions of the receiving end's PDCP protocol layer. For example, it performs a second security processing on RLC SDU ciphertext.

[0187] The SRAP layer is located between the PDCP layer and the RLC layer, and is used to forward data packets to other devices that are connected to the receiving device.

[0188] Therefore, the receiving device can obtain the SRAP header or PDCP header of the RLC SDU after receiving the plaintext of the RLC SDU or after receiving the first PDU, and parse out the target protocol entity identification information of the RLC SDU.

[0189] Step 602: Parse the SRAP header or PDCP header of each RLC SDU to obtain the target protocol entity identifier information of each RLC SDU.

[0190] In this embodiment, the target protocol entity identification information includes a target receiving device and a target protocol entity. Here, the target receiving device can be a receiving end device or another device that is communicatively connected to the receiving end device. The target protocol entity can be a protocol entity in the receiving end device, such as a PDCP protocol entity, or a protocol entity in another device that is communicatively connected to the receiving end device, such as a PDCP protocol entity in another device that is communicatively connected to the receiving end device.

[0191] Step 603: Based on the target protocol entity identifier information, send the RLC SDU in plaintext to the target protocol entity.

[0192] In this embodiment, the receiving device can determine whether it needs to send the RLC SDU plaintext to the PDCP layer or SRAP layer of the receiving device based on the target receiving device and the target protocol entity. The PDCP layer then performs further processing on the RLC SDU plaintext, or the SRAP layer relays the RLC SDU plaintext.

[0193] In this embodiment, when it is necessary to relay the plaintext of the RLC SDU, the SRAP layer sends the complete SDU to the RLC layer of the receiving device. The RLC layer of the receiving device then segments and re-encapsulates the SDU according to the air interface time-frequency resources of the MAC layer of the receiving device to form a new RLC PDU. The MAC layer of the receiving device then sends the new RLC PDU to the MAC layer of the target receiving device.

[0194] The data fragmentation and reassembly method provided in this embodiment includes a Sidechain Relay Adaptation Protocol (SRAP) header or a Packet Data Convergence Protocol (PDCP) header in the RLC SDU. The method obtains the SRAP or PDCP header of each RLC SDU; parses the SRAP or PDCP header of each RLC SDU to obtain the target protocol entity identifier information of each RLC SDU; and sends each RLC SDU to the target protocol entity based on the target protocol entity identifier information. Since the target protocol entity identifier information is obtained by parsing the SRAP or PDCP header, the target receiving device of the RLC SDU can be determined, allowing for processing of the RLC SDU or forwarding of the RLC SDU to the target receiving device, thus improving the processing efficiency of the receiving device for RLC SDUs.

[0195] Example 5

[0196] Figure 6 This is a flowchart illustrating the data fragmentation and reassembly method provided in Embodiment 5 of this application. Figure 6 As shown, the data fragmentation and reassembly method provided in this embodiment is applied to a security processing chip, which is located in a receiving device. The receiving device also includes a CPU, and the method includes steps 701 to 702.

[0197] Step 701: Receive the storage address information of each PDU from the same source sent by the CPU in the order in which the RLC SDU is formed.

[0198] Step 702: Read the data segments in each PDU according to the storage address information of each PDU and form an RLC SDU.

[0199] In this embodiment, after receiving the storage address information of each PDU from the same source, the security processing chip can determine the storage address of the data segment in each PDU from the storage address information of each PDU from the same source, referred to as the data segment address. It can also obtain the data segment in each PDU from each data segment address through direct storage access (DMA) and store the obtained data segment in a continuous space to form an RLC SDU.

[0200] Step 703: Send the RLC SDU to the CPU.

[0201] In this embodiment, the security processing chip can send the storage address of the RLC SDU to the CPU. The CPU can obtain the RLC SDU by accessing the storage address of the RLC SDU, or it can directly send the formed RLC SDU to the CPU.

[0202] The data fragmentation and reassembly method provided in this embodiment is applied to a secure processing chip located in the receiving device, which also includes a CPU. The method involves sequentially receiving the storage address information of each source PDU sent by the CPU in the order of forming the RLC SDU; sequentially reading data fragments from each source PDU according to their storage address information and forming an RLC SDU; and then sending the RLC SDU to the CPU. Since the secure processing chip reads data fragments from the PDU's storage space, excessive CPU power consumption can be avoided, preventing it from affecting the performance of the receiving device. Furthermore, because the secure processing chip is an application-specific integrated circuit (ASIC), it can read and write data to memory very quickly, thus enabling rapid assembly of data fragments from the PDU into an RLC SDU, improving the efficiency of the receiving device in acquiring the RLC SDU.

[0203] As an optional implementation, the storage address information includes the data fragment address; the RLC SDU is either RLCSDU ciphertext or RLC SDU plaintext. The RLC SDU ciphertext is obtained by the sending end's Packet Data Convergence Protocol (PDCP) layer performing a first security process using a preset key; the first security process includes at least one of the following: encryption and integrity protection. The data fragmentation and reassembly method provided in this embodiment, based on Embodiment 5, refines step 702, "reading data fragments from each source PDU sequentially according to the storage address information of each source PDU and forming an RLC SDU," by including steps 7021 to 7023.

[0204] Step 7021: If the RLC SDU is an RLC SDU ciphertext, then read the data segments from each source PDU sequentially from the data segment address of each source PDU to form the RLC SDU ciphertext.

[0205] In this embodiment, since the RLC SDU is an RLC SDU ciphertext, the data segments in the PDU are also ciphertext. The security processing chip can use DMA to splice the data segments in each PDU of the same origin together to form an RLC SDU ciphertext.

[0206] Step 7022: Send the RLC SDU ciphertext to the CPU, or use a preset key to perform a second security processing on the RLC SDU ciphertext to obtain the RLC SDU plaintext, and send the RLC SDU plaintext to the CPU; the second security processing includes at least one of the following: decryption and integrity verification.

[0207] In this embodiment, if the security processing chip stores a preset key, the preset key can be used to perform a second security processing on the RLC SDU ciphertext to obtain the RLC SDU plaintext. The RLC SDU plaintext is stored in a contiguous storage space of the receiving device. Similarly, the security processing chip can send the storage address of the RLC SDU plaintext, or the RLC SDU plaintext itself, to the CPU.

[0208] If the security processing chip does not store a preset key, it cannot decrypt the RLC SDU ciphertext. Instead, it can directly send the storage address of the RLC SDU ciphertext or the RLC SDU ciphertext itself to the CPU.

[0209] Step 7023: If the RLC SDU is RLC SDU plaintext, then read the data segments from each source PDU sequentially from the data segment address of each source PDU to form RLC SDU plaintext, and send the RLC SDU plaintext to the CPU.

[0210] In this embodiment, if the RLC SDU is in plaintext, the security processing chip can obtain the RLC SDU plaintext after reading the data segments in each PDU, and then send the storage address of the RLC SDU plaintext or the RLC SDU plaintext itself to the CPU.

[0211] The data fragmentation and reassembly method provided in this embodiment includes data fragment addresses in the storage address information; the RLC SDU is either RLC SDU ciphertext or RLC SDU plaintext; the RLC SDU ciphertext is obtained by the sending end packet data aggregation protocol (PDCP) layer performing a first security processing using a preset key; the first security processing includes at least one of the following: encryption and integrity protection; if the RLC SDU is RLC SDU ciphertext, then data fragments in each source PDU are sequentially read from the data fragment addresses of each source PDU to form the RLC SDU ciphertext; the RLC SDU ciphertext is sent to the CPU, or, the RLC SDU ciphertext is subjected to a second security processing using a preset key to obtain the RLC SDU plaintext, and the RLC SDU plaintext is sent to the CPU; the second security processing includes at least one of the following: decryption and integrity verification; if the RLC SDU is RLC SDU plaintext, then data fragments in each source PDU are sequentially read from the data fragment addresses of each source PDU to form the RLC SDU plaintext, and the RLC SDU plaintext is sent to the CPU. Since the security processing chip can convert RLC SDU ciphertext into RLC SDU plaintext before sending it, it can realize the security processing function of PDCP layer while splicing PDU, thus improving the processing speed of RLC SDU by the receiving device.

[0212] Example 6

[0213] Figure 7 This is a schematic diagram of the data fragmentation and reconstruction apparatus provided in Embodiment Six of this application. Figure 7 As shown, the data fragmentation and reassembly device 70 provided in this embodiment is applied to a CPU, which is located in a receiving device. The receiving device also includes a security processing chip. The data fragmentation and reassembly device 70 includes:

[0214] The first receiving module 71 is used to receive at least one Protocol Data Unit (PDU) sent by the Radio Link Control (RLC) layer of the transmitting end. The PDU includes an RLC protocol header and a data segment formed by the transmitting end's RLC layer after segmenting the RLC Service Data Unit (RLC SDU).

[0215] The parsing module 72 is used to parse the RLC protocol header of each PDU to obtain the fragmentation attribute information of each PDU.

[0216] Storage module 73 is used to store the storage address information of PDUs belonging to the same RLC SDU into the address storage space of the corresponding RLC SDU according to the fragmentation attribute information of each PDU.

[0217] The first transmitting module 74 is used to send the storage address information of each PDU in the same source as the RLC SDU to the security processing chip in the order of forming the RLC SDU, in response to the fact that all PDUs belonging to the same source have been received. This allows the security processing chip to read the data segments in each PDU in the same source according to the storage address information of each PDU and form an RLC SDU.

[0218] The second receiving module 75 is used to receive the RLC SDU sent by the security processing chip.

[0219] As an optional implementation, the fragmentation attribute information includes the identifier of the RLC SDU and the fragmentation sequence number; the storage module 73 is specifically used to: obtain the storage address information of each PDU; identify PDUs with the same RLC SDU identifier as homogeneous PDUs; determine whether there is an address storage space for the corresponding RLC SDU of each homogeneous PDU; if it is determined to exist, store the storage address information of the homogeneous PDU into the address storage space of the corresponding RLC SDU according to the fragmentation sequence number of the homogeneous PDU; if it is determined not to exist, create the address storage space of the corresponding RLC SDU of the homogeneous PDU, and store the storage address information of the homogeneous PDU into the address storage space of the corresponding RLC SDU according to the fragmentation sequence number of the homogeneous PDU.

[0220] As an optional implementation, the storage module 73 is further configured to create storage bits according to a preset number or the number of PDUs of the same source, and to determine the created storage bits as the address storage space of the corresponding RLC SDU.

[0221] As an optional implementation, the storage module 73 is further configured to perform the following operations for any PDU of the same origin: if it is determined that there is a storage bit corresponding to the fragment sequence number in the address storage space of the corresponding RLC SDU, then the storage address information of the PDU of the same origin is stored in the corresponding storage bit; if it is determined that there is no information storage bit corresponding to the fragment sequence number in the address storage space of the corresponding RLC SDU, then a storage bit is added in the address storage space of the corresponding RLC SDU according to the fragment sequence number of the PDU of the same origin, and the storage address information of the PDU of the same origin is stored in the storage bit corresponding to the fragment sequence number.

[0222] As an optional implementation, the first sending module 74 is specifically used to sequentially read the storage address information of each PDU of the same origin according to the order of each storage bit in the address storage space of the corresponding RLC SDU, and send the data segment address in each storage address information to the security processing chip.

[0223] As an optional implementation, the fragmentation attribute information also includes a fragmentation type, which can be any of the following: first fragment, last fragment, or intermediate fragment; the data fragmentation and reassembly device 70 also includes a determination module, which is used to read the last PDU address storage information stored in the last storage bit of the corresponding RLC SDU; if it is determined that the fragmentation type of the PDU corresponding to the last PDU address storage information is the last fragment, and the fragmentation sequence numbers of the PDUs of the same source in each storage bit of the corresponding RLC SDU are consecutive, then it is determined that all PDUs of the corresponding RLC SDU have been received.

[0224] As an optional implementation, the RLC SDU includes a Sidechain Relay Adaptation Protocol (SRAP) header or a Packet Data Convergence Protocol (PDCP) header; the first sending module is further configured to: obtain the SRAP header or PDCP header of each RLC SDU; parse the SRAP header or PDCP header of each RLC SDU to obtain the target protocol entity identification information of each RLC SDU; and send each RLC SDU to the target protocol entity based on the target protocol entity identification information of each RLC SDU.

[0225] The data fragmentation and reconstruction device provided in this embodiment can execute any of the data fragmentation and reconstruction methods provided in embodiments one to four above. The specific implementation methods and principles are similar and will not be described again here.

[0226] Example 7

[0227] Figure 8This is a schematic diagram of the data fragmentation and reconstruction apparatus provided in Embodiment 7 of this application. Figure 8 As shown, the data fragmentation and reconstruction device 80 provided in this embodiment includes: a third receiving module 81, a reconstruction module 82, and a second sending module 83.

[0228] The third receiving module 81 is used to receive the storage address information of each PDU of the same origin sent by the CPU in the order of forming the RLC SDU.

[0229] The reassembly module 82 is used to sequentially read data segments from each PDU of the same source according to the storage address information of each PDU of the same source and form an RLC SDU.

[0230] The second transmitting module 83 is used to transmit the RLC SDU to the CPU.

[0231] As an optional implementation, the storage address information includes a data segment address; the RLC SDU is either RLCSDU ciphertext or RLC SDU plaintext; the RLC SDU ciphertext is obtained by the sending end's Packet Data Convergence Protocol (PDCP) layer performing a first security process using a preset key; the first security process includes at least one of the following: encryption and integrity protection. The reassembly module 82 is specifically used to: if the RLC SDU is ciphertext, sequentially read data segments from the data segment addresses of each source PDU to form the RLC SDU ciphertext; and send the RLC SDU ciphertext to the CPU; or, perform a second security process on the RLCSDU ciphertext using a preset key to obtain the RLC SDU plaintext, and send the RLC SDU plaintext to the CPU; the second security process includes at least one of the following: decryption and integrity verification; if the RLC SDU is plaintext, sequentially read data segments from the data segment addresses of each source PDU to form the RLC SDU plaintext, and send the RLC SDU plaintext to the CPU.

[0232] The data fragmentation and reconstruction device provided in this embodiment can execute any of the data fragmentation and reconstruction methods provided in Embodiment 5 above. The specific implementation method and principle are similar, and will not be described again here.

[0233] Example 8

[0234] Figure 9 This is a schematic diagram of the receiving device according to Embodiment Six of this application. Figure 9 As shown, the receiving device 90 provided in this embodiment includes: CPU 91, security processing chip 92 and memory 93; CPU 91 includes a first transceiver 910; security processing chip includes a second transceiver 920.

[0235] CPU91, security processing chip 92, and memory 93 are interconnected by circuitry;

[0236] Memory 93 is used to store first computer-executed instructions and second computer-executed instructions;

[0237] Both the first transceiver 910 and the second transceiver 920 are used for sending and receiving data.

[0238] CPU91 executes a first computer execution instruction to implement any of the data fragmentation and reassembly methods provided in Embodiments 1 to 4 above. The security processing chip executes a second computer execution instruction to implement any of the data fragmentation and reassembly methods provided in Embodiment 5 above. The specific implementation methods and principles are similar and will not be described in detail here.

[0239] The CPU91, security processing chip 92, and memory 93 can be interconnected via a bus. This bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, Figure 8 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0240] The memory 93 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk, etc.

[0241] In an exemplary embodiment, the receiving device 70 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0242] Embodiments of this application also provide a computer-readable storage medium storing computer-executable instructions. When executed by a processor, these instructions are used to implement the data fragmentation and reassembly method provided in any of the above embodiments. Exemplarily, the computer-readable storage medium may be a read-only memory (ROM), random access memory (RAM), magnetic tape, floppy disk, or optical data storage device, etc.

[0243] It should be understood that the above-described device embodiments are merely illustrative, and the device of this application can also be implemented in other ways. For example, the module division in the above embodiments is only a logical functional division, and there may be other division methods in actual implementation. For example, multiple modules can be combined, or integrated into another system, or some features can be ignored or not executed.

[0244] Furthermore, unless otherwise specified, the functional modules in the various embodiments of this application can be integrated into one module, or each module can exist physically separately, or two or more modules can be integrated together. The integrated modules described above can be implemented in hardware or as software program modules.

[0245] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0246] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0247] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0248] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A data fragmentation and reassembly method, characterized in that, The method, applied to a central processing unit (CPU) located in a receiving device, which further includes a security processing chip, comprises: Receive at least one Protocol Data Unit (PDU) sent by the Radio Link Control (RLC) layer of the transmitting end, wherein the PDU includes an RLC header and a data segment formed by the transmitting end's RLC layer after segmenting the RLC Service Data Unit (RLC SDU); The RLC protocol header of each PDU is parsed to obtain the fragmentation attribute information of each PDU; Based on the fragmentation attribute information of each PDU, the storage address information of PDUs belonging to the same RLC SDU is stored in the address storage space of the corresponding RLC SDU. The storage address information is the location where the PDU is stored in the receiving device. In response to the fact that all PDUs belonging to the same RLC SDU have been received, the storage address information of each PDU is sent to the security processing chip in the order of forming the RLC SDU, so that the security processing chip can read the data segments in each PDU in the order of forming the RLC SDU and form the RLC SDU. Receive RLC SDU sent by the security processing chip; The storage address information includes a data fragment address; the RLC SDU is either RLC SDU ciphertext or RLC SDU plaintext; the RLC SDU ciphertext is obtained by the sending end packet data aggregation protocol (PDCP) layer using a preset key for first security processing; the first security processing includes at least one of the following: encryption and integrity protection; The security processing chip sequentially reads data segments from each PDU based on its storage address information and forms an RLC SDU, including: If the RLC SDU is an RLC SDU ciphertext, then the data segments in each source PDU are read sequentially from the data segment address of each source PDU to form the RLC SDU ciphertext; The RLC SDU ciphertext is sent to the CPU, or the RLC SDU ciphertext is subjected to a second security processing using a preset key to obtain the RLC SDU plaintext, and the RLC SDU plaintext is sent to the CPU; the second security processing includes at least one of the following: decryption and integrity verification; If the RLC SDU is in plaintext, then the data segments in each PDU are read sequentially from the data segment address of each PDU of the same origin to form the RLC SDU in plaintext, and the RLC SDU in plaintext is sent to the CPU.

2. The method according to claim 1, characterized in that, The fragmentation attribute information includes the RLC SDU identifier and fragmentation sequence number; The step of storing the storage address information of PDUs belonging to the same RLC SDU into the address storage space of the corresponding RLC SDU based on the fragmentation attribute information of each PDU includes: Obtain the storage address information of each PDU; PDUs with the same RLC SDU identifier are identified as PDUs of the same origin; Determine whether there is address storage space for the corresponding RLC SDU of each PDU of the same origin; If it is confirmed that it exists, the storage address information of the PDU is stored in the address storage space of the corresponding RLCSDU according to the fragment sequence number of the PDU. If it is determined that it does not exist, then the address storage space of the corresponding RLC SDU of the same source PDU is created, and the storage address information of the same source PDU is stored in the address storage space of the corresponding RLC SDU according to the fragment sequence number of the same source PDU.

3. The method according to claim 2, characterized in that, The creation of the address storage space corresponding to the RLC SDU includes: Create storage bits according to the preset number or the number of PDUs from the same source, and determine the created storage bits as the address storage space of the corresponding RLC SDU.

4. The method according to claim 3, characterized in that, The step of storing the storage address information of the same PDU into the address storage space of the corresponding RLC SDU according to the fragment sequence number of the same PDU includes: For any PDU from the same source, perform the following operations: If it is determined that there is a storage bit in the address storage space of the corresponding RLC SDU that corresponds to the fragment sequence number, then the storage address information of the PDU from the same source is stored in the corresponding storage bit; If it is determined that there is no information storage bit corresponding to the fragment sequence number in the address storage space of the corresponding RLC SDU, then a storage bit is added in the address storage space of the corresponding RLC SDU according to the fragment sequence number of the same source PDU, and the storage address information of the same source PDU is stored in the storage bit corresponding to the fragment sequence number.

5. The method according to claim 3, characterized in that, The storage address information includes data segment addresses; the step of sending the storage address information of each PDU of the same origin to the security processing chip in the order of forming the RLC SDU includes: According to the order of each storage bit in the address storage space of the corresponding RLC SDU, the storage address information of each PDU of the same origin is read in sequence, and the data segment address in each storage address information is sent to the security processing chip.

6. The method according to any one of claims 3-5, characterized in that, The sharding attribute information also includes sharding type, which is any one of the following: first shard, last shard, or middle shard. After storing the storage address information of PDUs belonging to the same RLC SDU into the address storage space of the corresponding RLC SDU based on the fragmentation attribute information of each PDU, the method further includes: Read the last PDU address information stored in the last storage bit of the corresponding RLC SDU; If it is determined that the fragment type of the PDU corresponding to the last PDU address storage information is tail fragment, and the fragment sequence numbers of PDUs from the same source in each storage bit of the corresponding RLC SDU are consecutive, then it is determined that all PDUs of the corresponding RLC SDU have been received.

7. The method according to any one of claims 1-5, characterized in that, The RLC SDU includes a Sidechain Relay Adaptation Protocol (SRAP) header or a Packet Data Convergence Protocol (PDCP) header. After storing the storage address information of PDUs belonging to the same RLC SDU into the address storage space of the corresponding RLC SDU based on the fragmentation attribute information of each PDU, the method further includes: Obtain the SRAP header or PDCP header for each RLC SDU; Parse the SRAP header or PDCP header of each RLC SDU to obtain the target protocol entity identification information of each RLC SDU; Based on the target protocol entity identifier information of each RLC SDU, each RLC SDU is sent to the target protocol entity.

8. A data fragmentation and reassembly method, characterized in that, The method, applied to a security processing chip located in a receiving device, which further includes a CPU, comprises: The storage address information of each PDU from the same source sent by the CPU is received sequentially in the order in which the RLC SDU is formed. The storage address information is the location where the PDU is stored in the receiving device. Based on the storage address information of each PDU of the same origin, data segments in each PDU of the same origin are read sequentially and formed into an RLC SDU; Send the RLC SDU to the CPU; The storage address information includes a data fragment address; the RLC SDU is either RLC SDU ciphertext or RLC SDU plaintext; the RLC SDU ciphertext is obtained by the sending end packet data aggregation protocol (PDCP) layer using a preset key for first security processing; the first security processing includes at least one of the following: encryption and integrity protection; The step of sequentially reading data segments from each PDU of the same origin and forming an RLCSDU based on the storage address information of each PDU includes: If the RLC SDU is an RLC SDU ciphertext, then the data segments in each source PDU are read sequentially from the data segment address of each source PDU to form the RLC SDU ciphertext; The RLC SDU ciphertext is sent to the CPU, or the RLC SDU ciphertext is subjected to a second security processing using a preset key to obtain the RLC SDU plaintext, and the RLC SDU plaintext is sent to the CPU; the second security processing includes at least one of the following: decryption and integrity verification; If the RLC SDU is in plaintext, then the data segments in each PDU are read sequentially from the data segment address of each PDU of the same origin to form the RLC SDU in plaintext, and the RLC SDU in plaintext is sent to the CPU.

9. A data fragmentation and reassembly device, characterized in that, The device is applied to a CPU, which is located in a receiving device, and the receiving device also includes a security processing chip. The device comprises: The first receiving module is used to receive at least one Protocol Data Unit (PDU) sent by the Radio Link Control (RLC) layer of the transmitting end. The PDU includes an RLC protocol header and a data segment formed by the transmitting end RLC layer after segmenting the RLC Service Data Unit (RLC SDU). The parsing module is used to parse the RLC protocol header of each PDU to obtain the fragmentation attribute information of each PDU; The storage module is used to store the storage address information of PDUs belonging to the same RLC SDU into the address storage space of the corresponding RLC SDU according to the fragmentation attribute information of each PDU. The storage address information is the location where the PDU is stored in the receiving device. The first transmitting module is used to, in response to the fact that all PDUs belonging to the same source as the same RLC SDU have been received, send the storage address information of each PDU to the security processing chip in the order of forming the RLC SDU, so that the security processing chip can read the data segments in each PDU in the order of forming the RLC SDU and form the RLC SDU. The second receiving module is used to receive RLC SDUs sent by the security processing chip; The storage address information includes a data fragment address; the RLC SDU is either RLC SDU ciphertext or RLC SDU plaintext; the RLC SDU ciphertext is obtained by the sending end packet data aggregation protocol (PDCP) layer using a preset key for first security processing; the first security processing includes at least one of the following: encryption and integrity protection; The security processing chip sequentially reads data segments from each PDU based on its storage address information and forms an RLC SDU, including: If the RLC SDU is an RLC SDU ciphertext, then the data segments in each source PDU are read sequentially from the data segment address of each source PDU to form the RLC SDU ciphertext; The RLC SDU ciphertext is sent to the CPU, or the RLC SDU ciphertext is subjected to a second security processing using a preset key to obtain the RLC SDU plaintext, and the RLC SDU plaintext is sent to the CPU; the second security processing includes at least one of the following: decryption and integrity verification; If the RLC SDU is in plaintext, then the data segments in each PDU are read sequentially from the data segment address of each PDU of the same origin to form the RLC SDU in plaintext, and the RLC SDU in plaintext is sent to the CPU.

10. A data fragmentation and reassembly device, characterized in that, The device is applied to a security processing chip, which is located in a receiving device, the receiving device further including a CPU, and the apparatus includes: The third receiving module is used to receive the storage address information of each PDU of the same origin sent by the CPU in the order of forming the RLC SDU. The storage address information is the location where the PDU is stored in the receiving device. The reassembly module is used to sequentially read data segments from each PDU of the same source according to the storage address information of each PDU and form an RLC SDU; The second transmitting module is used to transmit RLC SDUs to the CPU; The storage address information includes a data fragment address; the RLC SDU is either RLC SDU ciphertext or RLC SDU plaintext; the RLC SDU ciphertext is obtained by the sending end packet data aggregation protocol (PDCP) layer using a preset key for first security processing; the first security processing includes at least one of the following: encryption and integrity protection; The reorganization module is specifically used for: If the RLC SDU is an RLC SDU ciphertext, then the data segments in each source PDU are read sequentially from the data segment address of each source PDU to form the RLC SDU ciphertext; The RLC SDU ciphertext is sent to the CPU, or the RLC SDU ciphertext is subjected to a second security processing using a preset key to obtain the RLC SDU plaintext, and the RLC SDU plaintext is sent to the CPU; the second security processing includes at least one of the following: decryption and integrity verification; If the RLC SDU is in plaintext, then the data segments in each PDU are read sequentially from the data segment address of each PDU of the same origin to form the RLC SDU in plaintext, and the RLC SDU in plaintext is sent to the CPU.

11. A receiving device, characterized in that, include: The system comprises a CPU, a security processing chip, and a memory; the CPU includes a first transceiver; the security processing chip includes a second transceiver. The CPU, the security processing chip, and the memory circuit are interconnected; The memory is used to store the first computer-executed instructions and the second computer-executed instructions; Both the first transceiver and the second transceiver are used for sending and receiving data; The CPU executes the first computer execution instructions to implement the method as described in any one of claims 1-7, and the security processing chip executes the second computer execution instructions to implement the method as described in claim 8.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-8.

Images